Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h4EIRH318951
	for <ipsml@ece.cmu.edu>; Wed, 14 May 2003 14:27:17 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 191A380; Wed, 14 May 2003 14:27:17 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by osgood.ece.cmu.edu (Postfix) with ESMTP
	id 827426E; Wed, 14 May 2003 14:27:15 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 7EF268950; Wed, 14 May 2003 14:27:02 -0400 (EDT)
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 72AE3894F
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 14 May 2003 14:27:02 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 573886E; Wed, 14 May 2003 14:27:02 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 2C60380; Wed, 14 May 2003 14:27:02 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id A16346E
	for <ips-outgoing@ece.cmu.edu>; Wed, 14 May 2003 14:27:00 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 7A4E48952; Wed, 14 May 2003 14:27:00 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id D861A894F
	for <ips@sos.ece.cmu.edu>; Wed, 14 May 2003 14:26:58 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 72F177A; Wed, 14 May 2003 14:26:58 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 43DF96E; Wed, 14 May 2003 14:26:58 -0400 (EDT)
Received: from mail.ivivity.com (unknown [64.238.111.99])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id 601B77A
	for <ips@ece.cmu.edu>; Wed, 14 May 2003 14:26:56 -0400 (EDT)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <2CY0S6LD>; Wed, 14 May 2003 14:26:57 -0400
Message-ID: <AEC4671C8179D61194DE0002B328BDD26A81AE@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: Lakshmi Ramasubramanian <nramas@windows.microsoft.com>, ips@ece.cmu.edu
Subject: RE: [iSCSI] CmdSN for Text Command
Date: Wed, 14 May 2003 13:25:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-12.9 required=5.0
	tests=BAYES_01,ORIGINAL_MESSAGE
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

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] 
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
