Date: Mon, 25 Oct 2021 20:07:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259439] ctld: MaxRecvDataSegmentLength is sent only in response to initiator's MaxRecvDataSegmentLength Message-ID: <bug-259439-227-cKLoCDkXck@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259439-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259439 Alexander Motin <mav@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mav@FreeBSD.org --- Comment #1 from Alexander Motin <mav@FreeBSD.org> --- As I have told in https://reviews.freebsd.org/D32605, unlike the initiator, for target this is not a bug, at most a sub-optimal parameter negotiation. We may indeed try to unconditionally announce our MaxRecvDataSegmentLength value, but what if initiator not sending its own value will try to reject the received one? Our minimalistic negotiation code is not ready for real disputes. I haven't see many initiators not sending MaxRecvDataSegmentLength, so can't guess what can be on their minds. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259439-227-cKLoCDkXck>