Re: iscsi.04 comments

[julian_satran@il.ibm.com]

Sandeep,


1) - quote from the 2.8.3

   Some basic key=value pairs are described in Appendix A & D. All these
   keys except the X- extension formatted MUST be supported by iSCSI
   initiators and targets.

   2)the WN is allways for the next - BHS by itself does not need a WN - it
   is allways the first and you know what it is and how long it is (44
   bytes)

   3)I will qualify it with within a connection (I thought it was obvious
   but probably it is not).

   4)It is not ambiguous but I see your point - I will try to make it
   uniform (either all 0 or all 0x'ffffffff')

   Thanks,
   Julo

Sandeep Joshi <sandeepj@lucent.com> on 26/02/2001 18:03:37

Please respond to Sandeep Joshi <sandeepj@lucent.com>

To:   ips@ece.cmu.edu
cc:
Subject:  iscsi.04 comments





Julian,

A few questions/comments..

1) The following suggestion seems to be missing from
   this draft
      http://ips.pdl.cs.cmu.edu/mail/msg03273.html

2) There is a WN before the BHS and every AHS.
   So what are the WN bits (6-4) for a BHS ?
   Right now, there is 0=ext_cdb, 1=bidi, 2=longdata.
   All the other values (3-7) seem to be reserved.

3) Section 2.17 R2T - see statement before the fig.
    "outstanding R2T MUST be fulfilled by the initiator
    in the order they were received".
   Is this _within_ a command or connection or session.
   I presume its not within a session.
   Could you please qualify and disambiguate?

4) In Section 2.5 & Sec 2.6 for TaskMgmt commands the
   RefTaskTag, if reserved, is to be set to zero.
   In other commands (e.g. NOP-OUT), an invalid task tag is
   indicated by 0xffffffff.  How about making it uniform
   throughout as 0xff... (or maybe this is an oversight)

-Sandeep