RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
"Ramesh Mangamuri" <rmangamuri@istor.com> Sat, 31 January 2004 21:32 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06090 for <ips-archive@odin.ietf.org>; Sat, 31 Jan 2004 16:32:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1An2iv-00037g-57 for ips-archive@odin.ietf.org; Sat, 31 Jan 2004 16:32:17 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0VLWHAU011998 for ips-archive@odin.ietf.org; Sat, 31 Jan 2004 16:32:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1An2iu-00037R-VC for ips-web-archive@optimus.ietf.org; Sat, 31 Jan 2004 16:32:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06083 for <ips-web-archive@ietf.org>; Sat, 31 Jan 2004 16:32:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1An2it-0000Z7-00 for ips-web-archive@ietf.org; Sat, 31 Jan 2004 16:32:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1An2i0-0000TH-00 for ips-web-archive@ietf.org; Sat, 31 Jan 2004 16:31:21 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1An2hn-0000NF-00 for ips-web-archive@ietf.org; Sat, 31 Jan 2004 16:31:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1An2hi-0002zY-5Z; Sat, 31 Jan 2004 16:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1An2h3-0002xN-Ol for ips@optimus.ietf.org; Sat, 31 Jan 2004 16:30:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06028 for <ips@ietf.org>; Sat, 31 Jan 2004 16:30:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1An2h1-0000MT-00 for ips@ietf.org; Sat, 31 Jan 2004 16:30:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1An2g8-0000GA-00 for ips@ietf.org; Sat, 31 Jan 2004 16:29:24 -0500
Received: from host28.istor.com ([66.134.214.28] helo=mail1irv.inside.istor.com) by ietf-mx with esmtp (Exim 4.12) id 1An2ff-00009b-00 for ips@ietf.org; Sat, 31 Jan 2004 16:28:55 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Sat, 31 Jan 2004 13:27:08 -0800
Message-ID: <7D036BD3216A084DB1BD9D62BCEAF2905717A3@mail1irv.inside.istor.com>
Thread-Topic: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
Thread-Index: AcPnc+7kFxpMg6LQSzmCS94RimDCegAy5sDA
From: Ramesh Mangamuri <rmangamuri@istor.com>
To: Ken Sandars <ksandars@elipsan.com>, Julian Satran <Julian_Satran@il.ibm.com>, "Mallikarjun C." <cbm@rose.hp.com>
Cc: pat_thaler@agilent.com, ips@ietf.org
Content-Transfer-Encoding: quoted-printable
Sender: ips-admin@ietf.org
Errors-To: ips-admin@ietf.org
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Id: IP Storage <ips.ietf.org>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Hello Ken/Julian: I have another proposal here for section 10.4.8: Suggestion --------------------------- 10.4.8 ExpDataSN The number of Data-In (read) PDUs (for bidirectional commands this is R2Ts + Data-Ins) the target has sent for the command. This field is reserved if the response code is not Command Completed at Target, or the command is Write only command. How does this sound??? -Rams -----Original Message----- From: Ken Sandars [mailto:ksandars@elipsan.com] Sent: Friday, January 30, 2004 12:57 PM To: 'Julian Satran'; 'Mallikarjun C.' Cc: pat_thaler@agilent.com; ips@ietf.org Subject: RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands Hi Julo, As requested, two alternative proposals for section 10.4.8: Suggestion 1 -------------------------- 10.4.8 ExpDataSN The number of R2T and Data-In (read) PDUs the target has sent for the command. This field is reserved if the response code is not Command Completed at Target. Suggestion 2 -------------------------- 10.4.8 ExpDataSN The number of R2T and Data-In (read) PDUs the target has sent for the command. This field is reserved if the response code is not Command Completed at Target or the target sent no Data-In PDUs for the command. ---------------------------------------- I'm more than happy with any answer which clarifies when the field is reserved. Thanks, Ken Sandars Elipsan UK > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On > Behalf Of Mallikarjun C. > Sent: 30 January 2004 20:29 > To: Ken Sandars > Cc: 'Julian Satran'; pat_thaler@agilent.com; ips@ietf.org > Subject: Re: [Ips] iSCSI: Correct value for ExpDataSN for > bidirectional commands > > > Ken, > > I am not sure we need to restrict the wording > to commands with at least one Data-In PDU. Do > you see an issue? > > In any case, if you have a specific wording suggestion, > please send it to Julian directly (he owns the pen). > > Regards. > > Mallikarjun > > > > Ken Sandars wrote: > > > Hi Mallikarjun, > > > > One final clarification request, and I can sleep easy on > this topic! > > > > Will the new wording for 10.4.8 be more general to indicate that > > ExpDataSN is the number of DataIn and R2T PDUs that were sent? > > > > Is this field only valid for commands which have at least > one Data-In > > PDU? > > > > > > Thanks again, > > Ken Sandars > > Elipsan UK > > > > > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www1.ietf.org/mailman/listinfo/ips > > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips
- [Ips] iSCSI: Correct value for ExpDataSN for bidi… Ken Sandars
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Mallikarjun C.
- [Ips] iSCSI: Correct value for ExpDataSN for bidi… Ken Sandars
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Julian Satran
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Mallikarjun C.
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … wrstuden
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Mallikarjun C.
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … pat_thaler
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … wrstuden
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Julian Satran
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Mallikarjun C.
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Ken Sandars
- Re: [Ips] iSCSI: Correct value for ExpDataSN for … Mallikarjun C.
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Ken Sandars
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Ramesh Mangamuri
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … pat_thaler
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … pat_thaler
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Ramesh Mangamuri
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Ken Sandars
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … pat_thaler
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … wrstuden
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … wrstuden
- RE: [Ips] iSCSI: Correct value for ExpDataSN for … Julian Satran