RE: iSCSI padding should be 0

["Fischer, Michael" <Michael_Fischer@adaptec.com>]

Julian,

I hate to butt in with this minor point, I think you guys are doing a great
job in hammering out the specification and do not presume to know better.

However, according to RFC2119 the word MUST indicates that it is a
requirement of the specification and therefore implies that the receiver
will need to check the value.  If it MUST be zero and is not, then that
would indicate a protocol error.

Michael Fischer

-----Original Message-----
From: Julian_Satran/Haifa/IBM%IBMIL [mailto:julian_satran@il.ibm.com]
Sent: Friday, July 27, 2001 8:46 AM
To: eddy_quicksall@ivivity.com
Cc: ips
Subject: Re: iSCSI padding should be 0



Perhaps we should say MUST be sent as 0 and keep quiet about what the
receiver should  do (check for 0 - we don't want that).

Thanks,Julo

"Eddy Quicksall" <eddy_quicksall@ivivity.com> on 27-07-2001 18:18:33

Please respond to eddy_quicksall@ivivity.com

To:   Julian Satran/Haifa/IBM@IBMIL, ips@ece.cmu.edu
cc:
Subject:  iSCSI padding should be 0




Julian,

Section 2.1 says the padding should be 0. I guess that is correct because
one may not use CRC and therefore may not want to set them to 0. Wouldn't
it
be better if section 2.1 was more specific and mentioned when they must be
0
if there is a CRC. Also, I noticed at the UNH plug fest that at least one
person thought "should" meant "must". Therefore, I don't think it should
say
"should" ... I think it should not mention the 0'ness unless there is a CRC
present.

Also,

        transmission.  Padding bytes, when presents in a segment covered by
a
        CRC, have to be set to 0 and are included in the CRC.

should say "when present in".

Eddy_Quicksall@iVivity.com