content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [iSCSI] CmdSN for Text Command
Date: Wed, 14 May 2003 21:45:54 +0200
Message-ID: <838D8D2617300146B7F47E4D9AE7FF10A94C8E@SANSRV1.SAN-RAD.CO.IL>
Thread-Topic: [iSCSI] CmdSN for Text Command
Thread-Index: AcMaTwmogGTFwuLLRkq04XtvbdLVaQAAaEmA
From: "Shai Amir" <Shai@SANRAD.COM>
To: "Eddy Quicksall" <eddy_quicksall@ivivity.com>,
   "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>, <ips@ece.cmu.edu>
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Notice the part in brackets "similar to linked SCSI commands". For =
linked SCSI commands each command will have a new CmdSN.
It is the same thing here.
Actually I don't see a reason why to send a non-immediate test request. =
This would make the CmdSN not relevant.

Shai


-----Original Message-----
From: Eddy Quicksall [mailto:eddy_quicksall@ivivity.com]
Sent: Wednesday, May 14, 2003 7:25 PM
To: Lakshmi Ramasubramanian; ips@ece.cmu.edu
Subject: RE: [iSCSI] CmdSN for Text Command


I don't think the empty text command is to be treated like a new =
command. I
think they are talking about what paragraph 10.10.3 is calling "a =
sequence
of text requests and responses".

Eddy

-----Original Message-----
From: Lakshmi Ramasubramanian [mailto:nramas@windows.microsoft.com]=20
Sent: Wednesday, May 14, 2003 1:15 PM
To: ips@ece.cmu.edu
Subject: [iSCSI] CmdSN for Text Command

Section 10.10.4 Target Transfer Tag (Text Request)
says that if F bit is set to 0 in Text Response, initiator
must send an empty text command so that the target can
send the next text response. Should the initiator use
the original CmdSN when it sends the empty text command
or should it use the next CmdSN (Assuming Immediate Bit
is NOT set in any of the Text Command PDUs)?

Thanks!
 -lakshmi