Re: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
"Mallikarjun C." <cbm@rose.hp.com> Fri, 30 January 2004 00:21 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02538 for <ips-archive@odin.ietf.org>; Thu, 29 Jan 2004 19:21:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmMOm-0004oJ-2T for ips-archive@odin.ietf.org; Thu, 29 Jan 2004 19:20:40 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U0KeDb018491 for ips-archive@odin.ietf.org; Thu, 29 Jan 2004 19:20:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmMOl-0004oA-Tc for ips-web-archive@optimus.ietf.org; Thu, 29 Jan 2004 19:20:39 -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 TAA02510 for <ips-web-archive@ietf.org>; Thu, 29 Jan 2004 19:20:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmMOk-0000d5-00 for ips-web-archive@ietf.org; Thu, 29 Jan 2004 19:20:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmMNo-0000XY-00 for ips-web-archive@ietf.org; Thu, 29 Jan 2004 19:19:41 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AmMNC-0000SI-00 for ips-web-archive@ietf.org; Thu, 29 Jan 2004 19:19:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmMNB-0004fO-DN; Thu, 29 Jan 2004 19:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmMMp-0004fA-OS for ips@optimus.ietf.org; Thu, 29 Jan 2004 19:18:39 -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 TAA02487 for <ips@ietf.org>; Thu, 29 Jan 2004 19:18:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmMMo-0000Re-00 for ips@ietf.org; Thu, 29 Jan 2004 19:18:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmMLq-0000LP-00 for ips@ietf.org; Thu, 29 Jan 2004 19:17:39 -0500
Received: from palrel12.hp.com ([156.153.255.237]) by ietf-mx with esmtp (Exim 4.12) id 1AmMKw-0000GK-00 for ips@ietf.org; Thu, 29 Jan 2004 19:16:42 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160]) by palrel12.hp.com (Postfix) with ESMTP id 312A11C009D7 for <ips@ietf.org>; Thu, 29 Jan 2004 16:16:42 -0800 (PST)
Received: from rose.hp.com (dhcp-roseor-bdj055.rose.hp.com [15.23.139.55]) by rosemail.rose.hp.com (Postfix) with ESMTP id 4FE287FFF for <ips@ietf.org>; Thu, 29 Jan 2004 16:12:11 -0800 (PST)
Message-ID: <4019A260.6050005@rose.hp.com>
Date: Thu, 29 Jan 2004 16:16:32 -0800
From: "Mallikarjun C." <cbm@rose.hp.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ips@ietf.org
Subject: Re: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
References: <OF8BE28E7E.7A596F11-ONC2256E2A.005225CB-C2256E2A.0053A4BC@il.ibm.com> <401950D8.6060701@rose.hp.com> <Pine.NEB.4.53.0401291442150.912@neverwinter.home-net.icnt.net>
In-Reply-To: <Pine.NEB.4.53.0401291442150.912@neverwinter.home-net.icnt.net>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sorry, I must have missed that thread. I wish you had suggested the clarification to be put into the spec. The spec/appendix is clearly saying something different (which I am fine with). -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Hewlett-Packard MS 5668 Roseville CA 95747 cbm [at] rose.hp.com wrstuden@wasabisystems.com wrote: > On Thu, 29 Jan 2004, Mallikarjun C. wrote: > > >>Not sure why the initiator needs to be reported on the >>total # of R2Ts in the final response....I presume >>any mismatch in R2Ts is already factored into the status. >> >>_If_ we indeed want to include R2Ts, I think it would be >>necessary to make changes (10.4.8, E.2.2, and perhaps 6) >>because I believe the current spec semantics are clear >>that R2Ts are not included. > > > While I'll be honest that I don't understand _why_ R2Ts are factored into > the DataSN space along with Data-In PDUs, I've understood they were > comingled for over a year. I think it was about 16 months ago I asked > about this (before draft 20), and Julian explained that they shared the > same space. > > So I don't think it's supposed to be something new. > > Take care, > > Bill _______________________________________________ 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