Re: [Ips] iSER: draft-ietf-ips-iser-05.txt
Mike Ko <mako@almaden.ibm.com> Tue, 29 November 2005 18:52 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhAaJ-0001gK-Bn; Tue, 29 Nov 2005 13:52:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhAaI-0001fJ-3a for ips@megatron.ietf.org; Tue, 29 Nov 2005 13:52:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19541 for <ips@ietf.org>; Tue, 29 Nov 2005 13:51:23 -0500 (EST)
Received: from e2.ny.us.ibm.com ([32.97.182.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhAuO-0007by-JJ for ips@ietf.org; Tue, 29 Nov 2005 14:12:58 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id jATIpsV3011465 for <ips@ietf.org>; Tue, 29 Nov 2005 13:51:54 -0500
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jATIpsG7123200 for <ips@ietf.org>; Tue, 29 Nov 2005 13:51:54 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id jATIpsQl025156 for <ips@ietf.org>; Tue, 29 Nov 2005 13:51:54 -0500
Received: from d01ml604.pok.ibm.com (d01ml604.pok.ibm.com [9.56.227.90]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id jATIpsMT025151; Tue, 29 Nov 2005 13:51:54 -0500
In-Reply-To: <0F31272A2BCBBE4FA01344C6E69DBF50295FF8@thoth.ivivity.com>
Importance: Normal
MIME-Version: 1.0
To: Sanjay Goyal <sanjayg@ivivity.com>
Subject: Re: [Ips] iSER: draft-ietf-ips-iser-05.txt
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OF500B9847.41156CC0-ON852570C8.006708BB-882570C8.00679BED@us.ibm.com>
From: Mike Ko <mako@almaden.ibm.com>
Date: Tue, 29 Nov 2005 10:51:38 -0800
X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Release 7.0HF90 | November 16, 2005) at 11/29/2005 13:51:54, Serialize complete at 11/29/2005 13:51:54
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: ips@ietf.org
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
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>
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org
Sanjay, There is the possibility that an iSER initiator might prefer to operate in iSCSI mode and therefore not offer RDMAExtensions in its Login Request. But if the target can support and prefers iSER mode, it can offer RDMAExtensions in its Login Response. It is then up to the initiator to determine if it wants to support iSER for this session. The iSER draft is written to allow such possibilities. Mike Sent by: ips-bounces@ietf.org To: <ips@ietf.org> cc: Subject: [Ips] iSER: draft-ietf-ips-iser-05.txt Hi below is the description as per draft-ietf-ips-iser-05.txt section 6.3 -------------- An iSER-enabled node is not required to initiate the RDMAExtensions key exchange if it prefers to operate in the Traditional iSCSI mode. However, if the RDMAExtensions key is to be negotiated, an initiator MUST offer the key in the first Login Request PDU in the LoginOperationalNegotiation stage of the leading connection, and a target MUST offer the key in the first Login Response PDU with which it is allowed to do so (i.e., the first Login Response PDU issued after the first Login Request PDU with the C bit set to 0) in the LoginOperationalNegotiation stage of the leading connection. In response to the offered key=value pair of RDMAExtensions=yes, an initiator MUST respond in the next Login Request PDU with which it is allowed to do so, and a target MUST respond in the next Login Response PDU with which it is allowed to do so. ---------- What is confusing to me is "if the RDMAExtensions key is to be negotiated, an initiator MUST offer the key in the first Login Request PDU in the LoginOperationalNegotiation stage of the leading connection" which is later followed by "In response to the offered key=value pair of RDMAExtensions=yes, an initiator MUST respond in the next Login Request PDU with which it is allowed to do so" If the Initiator did not exchange the key in first Login Request, means that it doesnot want to negotiate, why would it get the key in the first Login Response as Target should not send it to begin with. Please clarify, Regards, Sanjay Goyal 678-990-1550 x204 iVivity Inc. Norcross, GA 30093 _______________________________________________ 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] iSER: draft-ietf-ips-iser-05.txt Sanjay Goyal
- Re: [Ips] iSER: draft-ietf-ips-iser-05.txt Mike Ko
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Sanjay Goyal
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Mike Ko
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt John Hufferd