Re: ISCSI: CmdSN in non-leading login

["John Hufferd" <hufferd@us.ibm.com>]

That works for me.
Thanks.

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136, Cell: (408) 499-9702
Internet address: hufferd@us.ibm.com


Julian Satran@IBMIL
05/12/2002 04:20 AM

To:    John Hufferd/San Jose/IBM@IBMUS@IBMDE
cc:    ips@ece.cmu.edu, "Mark S. Edwards" <marke@muttsnuts.com>,
       owner-ips@ece.cmu.edu
From:  Julian Satran/Haifa/IBM@IBMIL
Subject:    Re: ISCSI: CmdSN in non-leading login  (Document link: John
       Hufferd)

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