Re: [storm] I-D Action: draft-ietf-storm-iser-03.txt
Michael Ko <Michael@huaweisymantec.com> Sat, 10 September 2011 00:42 UTC
Return-Path: <Michael@huaweisymantec.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F410A21F86EE for <storm@ietfa.amsl.com>; Fri, 9 Sep 2011 17:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level:
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=0.306, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8zYtLf8oLq-6 for <storm@ietfa.amsl.com>; Fri, 9 Sep 2011 17:42:13 -0700 (PDT)
Received: from mta1.huaweisymantec.com (mta1.huaweisymantec.com [218.17.155.14]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1E121F85D1 for <storm@ietf.org>; Fri, 9 Sep 2011 17:42:12 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_odJdYyeyvbulVHpBd7Gj5Q)"
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0LRA00CJF7DIE150@hstga01-in.huaweisymantec.com> for storm@ietf.org; Sat, 10 Sep 2011 08:44:07 +0800 (CST)
Received: from m90003900a ([69.199.248.19]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0LRA0069Z7DFEY00@hstml01-in.huaweisymantec.com> for storm@ietf.org; Sat, 10 Sep 2011 08:44:06 +0800 (CST)
Message-id: <52D3969270BF4653A2AE00109DA2FA7D@china.huawei.com>
From: Michael Ko <Michael@huaweisymantec.com>
To: david.black@emc.com, storm@ietf.org
References: <20110907011701.5649.63232.idtracker@ietfa.amsl.com> <2ECF865CEAF1472F84800EC7A9F229F1@china.huawei.com> <7C4DFCE962635144B8FAE8CA11D0BF1E058B27F52C@MX14A.corp.emc.com>
Date: Fri, 09 Sep 2011 17:44:02 -0700
X-Priority: 3
X-MSMail-priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
Subject: Re: [storm] I-D Action: draft-ietf-storm-iser-03.txt
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Sep 2011 00:42:14 -0000
David, I intend to add the following paragraph in section 14. Except as noted, all changes are backwards compatible with RFC 5046. However, there are some changes which reflect existing implementation and are not backwards compatible with RFC 5046. As a result, a hypothetical implementation based on RFC 5046 will not interoperate with an implementation based on this version of the specification. Mike ----- Original Message ----- From: david.black@emc.com To: Michael@huaweisymantec.com ; storm@ietf.org Sent: Friday, September 09, 2011 8:34 AM Subject: RE: [storm] I-D Action: draft-ietf-storm-iser-03.txt Mike, Thanks for submitting this updated draft. In Section 14 (Appendix A), please add a discussion of backwards compatibility with RFC 5046 - it's important to explain how an implementation based on this draft will interact with a hypothetical implementation based on RFC 5046. As part of this, it's important to identify changes that are incompatible with RFC 5046, but compatible with existing implementations because the implementations did something different from RFC 5046. As a start, it would help to identify each numbered change as backwards-compatible (with RFC 5046) vs. backwards-incompatible (because RFC 5046 got it wrong in 20/20 hindsight). Thanks, --David From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf Of Michael Ko Sent: Wednesday, September 07, 2011 12:59 PM To: storm@ietf.org Subject: Re: [storm] I-D Action: draft-ietf-storm-iser-03.txt The summary of changes since RFC 5046 can be found in section 14. In particular, the following changes were made since the -02 version of the draft: 8. Added two 64-bit fields in iSER header in section 9.2 for the Read Base Offset and the Write Base Offset to accommodate a non-zero Base Offset. This allows one implementation such as the OFED stack to be used in both the Infiniband and the iWARP environment. Changes were made in the definition of Base Offset, Advertisement, and Tagged Buffer. Changes were also made in sections 2.4.1, 2.5, 2.6, 7.3.1, 7.3.3, 7.3.5, 7.3.6, 9.1, 9.3, 9.4, 9.5.1, and 9.5.2. 9. Remove iWARP specific behavior. Changes were made in the definition section on RDMA Operation and Send Message Type. Changes affecting Send with Invalidate were made in sections 2.4.1, 2.5, 2.6, 4.1, and 7.3.2. Changes affecting Terminate were made in sections 10.1.2.1 and 10.1.2.2. (Forgot to mention here that section 15 was also updated to remove iWARP specific behavior.) 10. Denial of service descriptions for the initiator in section 5.1.1 was removed since it is applicable for the target only. Mike ----- Original Message ----- From: internet-drafts@ietf.org To: i-d-announce@ietf.org Cc: storm@ietf.org Sent: Tuesday, September 06, 2011 6:17 PM Subject: [storm] I-D Action: draft-ietf-storm-iser-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the STORage Maintenance Working Group of the IETF. Title : iSCSI Extensions for RDMA Specification Author(s) : Michael Ko Alexander Nezhinsky Filename : draft-ietf-storm-iser-03.txt Pages : 91 Date : 2011-09-06 iSCSI Extensions for RDMA provides the RDMA data transfer capability to iSCSI by layering iSCSI on top of an RDMA-Capable Protocol. An RDMA-Capable Protocol provides RDMA Read and Write services, which enable data to be transferred directly into SCSI I/O Buffers without intermediate data copies. This document describes the extensions to the iSCSI protocol to support RDMA services as provided by an RDMA- Capable Protocol. This document obsoletes RFC5046 Table of Contents A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-storm-iser-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-storm-iser-03.txt _______________________________________________ storm mailing list storm@ietf.org https://www.ietf.org/mailman/listinfo/storm
- [storm] I-D Action: draft-ietf-storm-iser-03.txt internet-drafts
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… david.black
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… david.black
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… david.black
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… david.black
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… Michael Ko
- Re: [storm] I-D Action: draft-ietf-storm-iser-03.… david.black