Re: Minor edits to draft-ietf-ips-iSCSI-00.txt

[julian_satran@il.ibm.com]

Marjorie,

Thanks,
Julo

"KRUEGER,MARJORIE (HP-Roseville,ex1)" <marjorie_krueger@hp.com> on
08/11/2000 04:37:47

Please respond to "KRUEGER,MARJORIE (HP-Roseville,ex1)"
      <marjorie_krueger@hp.com>

To:   Julian Satran/Haifa/IBM@IBMIL
cc:
Subject:  Minor edits to draft-ietf-ips-iSCSI-00.txt




1.2.9 Message Framing

paragraph 7

  "There are differing interpretations of whether the Urgent pointer
   points to the last (only) byte of urgent data (as defined by
   RFC1122), or the byte after the urgent data (typically BSD
   implementations). iSCSI has implemented a mechanism to resolve which
                           ^^^^^^^^^^^^^^^ (should be "SHALL implement")
   interpretation is being used on the data received. Bit 7 in the first
   byte of the iSCSI message (F bit in the opcode field) that shall
                                                         ^^^^ (delete)
   always be zero.  Bit 7 in the following byte (opcode specific fields)
   shall always be one.  When an iSCSI implementation receives an out of
   order TCP segment with the Urgent pointer defined, it shall look at
   the byte pointed to by the Urgent pointer.  If the bit is clear, the
   sender is RFC1122 compliant.  If the bit is set, the sender has
   implemented the BSD interpretation, and must "back up" one byte to
   find the beginning of the iSCSI message"

If this bit is always 0, shouldn't the header template in section 2.1
simply
represent this as 0 instead of F?

Marjorie Krueger
Networked Storage Architecture
Hewlett-Packard Storage Organization
tel: +1 916 785 2656
fax: +1 916 785 0391
email: marjorie_krueger@hp.com