Re: iSCSI: CmdSN during the Login phase

["Matt Wakeley" <matt_wakeley@agilent.com>]

I agree with Mark's proposal.

-Matt

Mark Bakke wrote:
> 
> Given that this is being interpreted differently by enough
> implementations, I would prefer to see us take a step back
> and look at which of Scott's three options should make the
> most sense.  It looks like options #1 and #2 are what is
> currently being implemented, regardless of what's specified.
> 
> However, a connection technically can't really be part of a
> session (sharing its work load) until it has completed a
> successful login phase.  There's also little reason for
> numbering until the login phase is complete, since the login
> and text responses during negotiation are synchronous, and
> pertain only to the connection, rather than the session.
> 
> I would recommend stating that a connection joins (or becomes,
> if it's the first one) a session after the login response
> with the F bit set is sent (on a target), or after the login
> response with the F bit set is received (on an initiator),
> and that CmdSN is not necessary until such a time, especially
> since CmdSN is per-session, not per-connection.  This is
> identical to Scott's option 3.
> 
> I think that defining it this way would remove any further
> ambiguity on when a connection is part of a session.  Since
> it appears that most implementations will have to modify their
> login code anyway, this shouldn't be too bad.
> 
> --
> Mark