RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
pat_thaler@agilent.com Mon, 02 February 2004 18:12 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28098 for <ips-archive@odin.ietf.org>; Mon, 2 Feb 2004 13:12:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AniYc-0007nc-QK for ips-archive@odin.ietf.org; Mon, 02 Feb 2004 13:12:27 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i12ICQKZ029974 for ips-archive@odin.ietf.org; Mon, 2 Feb 2004 13:12:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AniYc-0007nN-H1 for ips-web-archive@optimus.ietf.org; Mon, 02 Feb 2004 13:12:26 -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 NAA28069 for <ips-web-archive@ietf.org>; Mon, 2 Feb 2004 13:12:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AniYa-0003dz-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 13:12:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AniXX-0003SP-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 13:11:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AniWN-0003EK-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 13:10:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AniWN-0007O9-CZ; Mon, 02 Feb 2004 13:10:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AniVo-0007Kp-AV for ips@optimus.ietf.org; Mon, 02 Feb 2004 13:09:32 -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 NAA27739 for <ips@ietf.org>; Mon, 2 Feb 2004 13:09:28 -0500 (EST)
From: pat_thaler@agilent.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AniVm-00033r-00 for ips@ietf.org; Mon, 02 Feb 2004 13:09:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AniSs-0002Ga-00 for ips@ietf.org; Mon, 02 Feb 2004 13:06:33 -0500
Received: from msgbas1tx.cos.agilent.com ([192.25.240.37] helo=msgbas2x.cos.agilent.com) by ietf-mx with esmtp (Exim 4.12) id 1AniO3-000160-00 for ips@ietf.org; Mon, 02 Feb 2004 13:01:31 -0500
Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 1EFA176A0; Mon, 2 Feb 2004 11:01:31 -0700 (MST)
Received: from wcosbh22.cos.agilent.com (wcosbh22.cos.agilent.com [130.29.152.178]) by relcos2.cos.agilent.com (Postfix) with ESMTP id ED03C3E4; Mon, 2 Feb 2004 11:01:30 -0700 (MST)
Received: from wcosmb02.cos.agilent.com ([130.29.152.96]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 2 Feb 2004 11:01:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
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: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
Date: Mon, 02 Feb 2004 11:01:30 -0700
Message-ID: <CA56AF7C40BC6540BA471AD2CC8F305709C600@wcosmb02.cos.agilent.com>
Thread-Topic: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
Thread-Index: AcPnc+7kFxpMg6LQSzmCS94RimDCegAy5sDAAF1euxA=
To: rmangamuri@istor.com, ksandars@elipsan.com, Julian_Satran@il.ibm.com, cbm@rose.hp.com
Cc: ips@ietf.org
X-OriginalArrivalTime: 02 Feb 2004 18:01:30.0600 (UTC) FILETIME=[95F9C680:01C3E9B6]
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.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
I don't think "(read)" should be in there. We don't usually put read after Data-In. Also, I would rather have it a separate sentence. For read commands, the number of Data-In PDUs the target has sent for the command. For bidirectional commands, the number of Data-In PDUs and R2T PDUs the target has sent for the command. or For bidirectional commands, the number of Data-In PDUs and R2T PDUs the target has sent for the command. For all other commands, the number of Data-In PDUs the target has sent for the command. The more I think about it, the more I lean toward leaving 10.4.8 as it is and changing 3.2.2 to disentangle DataSN from R2TSN. Is it really worth these gymnastics to reduce bidirectional command context by one variable? -----Original Message----- From: Ramesh Mangamuri [mailto:rmangamuri@istor.com] Sent: Saturday, January 31, 2004 1:27 PM To: Ken Sandars; Julian Satran; Mallikarjun C. Cc: THALER,PAT (A-Roseville,ex1); ips@ietf.org Subject: RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands 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