Re: iSCSI: CmdSN in Login-retry

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

Stephen,

Your question IS more relevant than the security digest.

I am not sure that we ever envisioned retrying a Login.  (except completely
restarting it).
The only definite thing discussed  was that a failed Login should leave no
traces (no partial changes).

In 08 we intend to make Login a SHOULD be immediate (the 0 in immediate was
a typo - that I catched only when making it I).
That is already expressed in the change material I've sent out (including
text req/resp and login req/resp).

There are no scheduled phone calls except for some ongoing work on security
of which you are probably aware and updates of which appear on the list all
the time.

Julo



"Wheat, Stephen R" <stephen.r.wheat@intel.com>@ece.cmu.edu on 23-08-2001
20:50:08

Please respond to "Wheat, Stephen R" <stephen.r.wheat@intel.com>

Sent by:  owner-ips@ece.cmu.edu


To:   ips@ece.cmu.edu
cc:
Subject:  iSCSI: CmdSN in Login-retry



Hi Julian,

My questions pale in comparison to the very interesting security digest
debate.  BTW, I hope David's Pandora's box does stay closed for 1.0.

Section 7.1 states that a Retry command MUST use the original CmdSN.  This
doesn't make sense for a Login Retry.

Is there an exception here?  If not, please briefly explain the logic of a
Login Retry having the original CmdSN.

How does this enter into the debate on whether Login and Login-Text
messages
should be sent Immediate?  Has consensus been met on that yet?

BTW, is there an occasional forum where several people meet to thrash out
subtle details, or is this the only forum for questions, tiny and big?
Obviously people can meet FTF or on the phone whenever they want, but is
there a scheduled forum?

Thanks,
Stephen