Re: iSER Specification login/text operational keys
Mike Ko <[email protected]>
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <OFF878BCD8.A19221D6-ON85256ECA.0077B346-88256ECA.007904CA@us.ibm.com> |
The intent is to not use HeaderDigest, DataDigest, OFMarker, and IFMarker when RDMAExtensions is negotiated to yes. Should the iSCSI spec be changed for any reason such that the defaults for these 4 keys are not off by default, then these 4 keys must be negotiated to None/No for an iSER connection. Otherwise no explicit negotiation for these 4 keys are intended if the default is None/No. For InitiatorRecvDataSegmentLength and TargetRecvDataSegmentLength, if both the initiator and the target are willing to accept the default value, then no explicit negotiation is required for an iSER connection. Hope this helps. Mike Sent by: [email protected] To: [email protected] cc: Subject: [rddp] iSER Specification login/text operational keys Hello all, Sections 8.1 and 8.6 of the iSER specification state that if RDMAExtensions is negotiated to Yes on the leading connection of a session, then HeaderDigest,DataDigests, OFMarker and IFMarker, if they are negotiated, must be negotiated to None/No. In Section 5.3, points 2 and 8 say that the keys HeaderDigest,DataDigests, OFMarker and IFMarker MUST be negotiated to None/No. Does this mean that these keys must be offered for negotiation when RDMAExtensions=Yes, even if they simply select the value None? (Since these keys are off by default, negotiation is not required to arrive at the result None/No. ) Does similar reasoning apply to InitiatorRecvDataSegmentLength and TargetRecvDataSegmentLength? Any help is appreciated. Thanks, Minti Patel InterOperability Lab University of New Hampshire _______________________________________________ rddp mailing list [email protected] https://www1.ietf.org/mailman/listinfo/rddp