Re: iscsi - InitiatorName key during login

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

08 has some contradictory statements. InitiatorName is mandatory on every first login on every connection.

Julo

andy currid <andy@windriver.com> Sent by: owner-ips@ece.cmu.edu 08-10-01 18:34 Please respond to andy currid

To:        ips@ece.cmu.edu         cc:                 Subject:        iscsi - InitiatorName key during login

iSCSI version 8 is unclear as to whether InitiatorName is required
in the first login PDU of every login in a session, or just the
leading login.

Chapter 5, Login Phase, states -

 "The login phase sequence of commands and responses proceeds as follows:

   - login initial request
   - login partial response (optional)
   - more login requests and responses (optional)
   - login final-response (mandatory)

  The initial login request MUST include the InitiatorName and
  SessionType key=value pairs."

Taken in the context, this wording implies that for any login, the
first login PDU must contain the InitiatorName key.

Appendix D.13, InitiatorName, states that InitiatorName is Leading
Only and that "this key MUST be provided by the initiator of the TCP
connection to the remote endpoint before the end of the login phase".

This wording implies that InitiatorName is supplied in the leading
login only, and need not necessrily appear in the first login PDU
of the leading login.

So which is correct?

It seems to me that requiring that InitiatorName be present in the
first PDU of the leading login is a must, to allow targets to verify
up front whether or not they wish to proceed further with this
initiator. I don't think there's much incremental benefit to having
InitiatorName appear in the first login PDU of every login.

Andy
--
Andy Currid                                       andy@windriver.com
Server Products Group                       http://www.windriver.com
Wind River Networks                         Phone : (1) 510 749 2191
500 Wind River Way, Alameda, CA 94501       Fax   : (1) 510 749 2560