RE: ISCSI: CmdSN in non-leading login

[Eddy Quicksall <eddyq@ivivity.com>]

Julian,

 

I like your 1st paragraph but I think it so clear that the examples are not necessary.

 

Eddy

-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
Sent: Sunday, May 12, 2002 7:24 AM
To: John Hufferd
Cc: ips@ece.cmu.edu; Mark S. Edwards; owner-ips@ece.cmu.edu
Subject: Re: ISCSI: CmdSN in non-leading login

John,

Here is the text I suggest for 9.12.8

CmdSN

CmdSN is either the initial command sequence number of a session (for the first Login request of a session - the "leading" login) or the command sequence number in the command stream if the login is for a new connection in an existing session.

Examples:

- A leading login phase - if the leading login carries the CmdSN 123 all other login requests in the same login phase carry the CmdSN 123 and the first non-immediate command in FullFeaturePhase also carries the CmdSN 123.

- A non-leading login phase - the current CmdSN at the time the first login on the connection is issued is 500 - the login request carries CmdSN=500 the second login request carries a CmdSN not lower than 500 (higher if non-immediate requests where issued in the session between the first and the second request in the new login phase) etc..

If the login request is a leading login request the target MUST use the value presented in CmdSN as the target value for ExpCmdSN.

Regards,
Julo