RE: iSCSI: Negotiation clarifications still needed

[Bill Studenmund <wrstuden@wasabisystems.com>]

On Thu, 30 May 2002 pat_thaler@agilent.com wrote:

> I can't parse (on page 68):
>
> A value is whatever follows the = that follows the key-name up to a
> zero-byte delimiter that separates a key=value pair from the next or
> up to the end of data (for the last key=value pair if the PDU C flag
> bit is set to 0).
>
> I think I know what he meant but I can't get the text to parse clearly.
> It is trying to do too much in one sentence.
> How about:
> A value is whatever follows the = that follows the key-name up to a
> zero-byte delimiter. The zero-byte delimiter separates a key=value
> pair from the next and follows the last key=value pair when the PDU C flag
> bit is set to 0.
>
> The text on the bottom of page 72 is sufficient to produce the behavior
> we want but it doesn't make clear the reason for having the C bit. We
> don't need the C bit to know that the last value was incomplete. We need
> it to allow us to prepare a multi-PDU buffer of key-value pairs for
> transmission.
> How about:
> Key=value pairs may span PDU boundaries.
>
> The C flag bit allows an initiator or target to prepare a set of
> key values larger than the PDU size for transmission and send the set in
> multiple
> PDUs ensuring that it will not receive key-value pairs while those PDUs are
> being transmitted. An initiator or target wishing to do this indicates that
> more
> text follows by setting the C flag bit in the Text Request or Text
> Response to 1. A target or initiator receiving a Text Request or
> Text Response, respectively, with the C flag bit set to 1 MUST answer with a
> Text Response or Text Request with no data segment (DataSegmentLength
> 0). A Text Request or Text Response PDU having the C flag
> bit set to 1 MUST NOT have the F bit set to 1.

Sounds good. I like the new wording.

Take care,

Bill