RE: iSCSI: StatSN Field in R2T messages.

["Julian Satran" <Julian_Satran@il.ibm.com>]

Yes StatSN should be included in the "except" list.

The text should read:

The numbered-response(s) or R2T(s), requested by a SNACK, MUST be delivered as exact replicas of the ones the initiator missed except for the fields ExpCmdSN, MaxCmdSN and ExpDataSN which MUST carry the current values. R2T(s)requested by SNACK MUST carry also the current value of StatSN.

Julo

"Gwendal Grignou" <ggrignou@silverbacksystems.com> Sent by: owner-ips@ece.cmu.edu 06/28/2002 04:23 AM Please respond to "Gwendal Grignou"

To:        "'Paul Koning'" <ni1d@arrl.net>         cc:        <ips@ece.cmu.edu>         Subject:        RE: iSCSI: StatSN Field in R2T messages.

Gwendal> GG: I totally agree not to send StatSN in DataIN if S=0, so
>  Gwendal> to reduce in the same way the number of field to process in
>  Gwendal> the R2T message, couldn't we mark the bytes 24 to 27 as
>  Gwendal> reserved in the R2T message?
> 
> If we weren't in last call, that would be a good suggestion to
> consider.  But we are in last call, which is the wrong time to make
> message format changes unless they are essential for fixing bugs.
> 
>                  paul

I understand, but then I have a question about 9.16:
"The numbered-response(s) or R2T(s), requested by a SNACK, MUST be
delivered as exact replicas of the ones the initiator missed except for
the fields ExpCmdSN, MaxCmdSN and ExpDataSN which MUST carry the current
values."

What about StatSN? For R2T, shall the target send the StatSN used the
first time, or should it carry the current value? An old StatSN might
confuse the initiator.
Should I read "... except for the fields ExpCmdSN, MaxCmdSN, ExpDataSN
(and StatSN for R2T(s)) which MUST carry the current values?"

Gwendal.