IETF Logo Mail Archive

Re: [rddp] RDDP status of drafts

"Talpey, Thomas" <Thomas.Talpey@netapp.com> Tue, 02 March 2004 08:40 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26499 for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 03:40:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay5RN-0007yq-Mq for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 03:39:50 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i228dnb2030660 for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 03:39:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay5RL-0007yF-1u for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 03:39:47 -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 DAA26387 for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 03:39:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay5RI-0007Wm-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:39:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay5QA-0007I4-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:38:35 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Ay5PX-00079s-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:37:55 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Ay5Lw-0003aF-D8 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:34:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay5Lp-0007DA-Va; Tue, 02 Mar 2004 03:34:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay5LA-00076N-O5 for rddp@optimus.ietf.org; Tue, 02 Mar 2004 03:33:24 -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 DAA26148 for <rddp@ietf.org>; Tue, 2 Mar 2004 03:33:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay5L8-0006im-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:33:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay5KB-0006c6-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:32:24 -0500
Received: from mx01.netapp.com ([198.95.226.53]) by ietf-mx with esmtp (Exim 4.12) id 1Ay5Ji-0006VJ-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:31:54 -0500
Received: from hawk.corp.netapp.com (hawk [10.57.156.122]) by mx01.netapp.com (8.12.10/8.12.10/NTAP-1.4) with ESMTP id i228VOJC017800; Tue, 2 Mar 2004 00:31:24 -0800 (PST)
Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.10.22.171]) by hawk.corp.netapp.com (8.12.9/8.12.9/NTAP-1.5) with ESMTP id i228VN8L006402; Tue, 2 Mar 2004 00:31:23 -0800 (PST)
Received: from tmt.netapp.com ([10.97.6.31]) by silver.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 2 Mar 2004 03:31:16 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C40030.BA76E200"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Subject: Re: [rddp] RDDP status of drafts
Date: Tue, 02 Mar 2004 00:28:40 -0800
Message-ID: <6.0.3.0.2.20040302032316.01c51488@silver.nane.netapp.com>
Thread-Topic: [rddp] RDDP status of drafts
Thread-Index: AcQAMLui5b6N+3E4RoSPEAdoWYDb6w==
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: Black_David@emc.com, Renato Recio <recio@us.ibm.com>
Cc: rddp@ietf.org
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-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.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE autolearn=no version=2.60

I believe there are some in-progress edits on the RDMAP
authors' plate, but the document wasn't resubmitted before
the meeting. Renato, can you confirm?

Tom.

At 03:12 AM 3/2/2004, Black_David@emc.com wrote:
>Here's what the WG chair believes the current status of
>drafts in the RDDP WG to be (if anything seems wrong here,
>please let me know):
>
>IETF RDDP WG Draft Status - March 2004, Seoul IETF meetings
>-----------------------------------------------------------
>
>-- Problem Statement and Architecture
>
>draft-ietf-rddp-problem-statement-03.txt
>draft-ietf-rddp-arch-04.txt
>
>To become Informational RFCs.
>
>Finished WG Last Call, and have been revised to respond to comments
>from our Area Director.  Further IESG discussion has generated
>additional comments that will require further revisions.
>
>-- Main Protocols
>
>DDP (draft-ietf-rddp-ddp-02.txt)
>RDMAP (draft-ietf-rddp-rdmap-01.txt)
>
>To become Proposed Standard RFCs.
>
>No technical issues meriting substantial meeting time.  Waiting
>on security draft (which will probably generate revisions to
>the security considerations sections in these drafts)
>before going to WG Last Call
>
>-- Applicability Statement
>
>draft-ietf-rddp-applicability-01.txt
>
>To become an Informational RFC.
>
>Believed to be in good shape - please review.
>
>-- SCTP Mapping
>
>draft-ietf-rddp-sctp-00.txt
>
>To become a Proposed Standard RFC.
>
>Despite the -00 version number, this is the fourth version of this draft,
>and
>it is relatively mature.
>
>-- TCP Mapping
>
>draft-ietf-rddp-mpa-00.txt
>
>To become an Informational RFC.
>
>The major open issues in this draft involve connection initiation/
>startup.  Substantial meeting time allocated to make progress.
>
>draft-cully-mpa-issuesresponses-00.txt
>
>Will not become an RFC.  This draft describes issues raised about
>MPA and the views of the MPA authors on those issues.
>
>-- Security
>
>draft-ietf-rddp-security-01.txt
>
>Whether this will be Informational vs. Proposed Standard is TBD.
>This draft is on the critical path to completing the DDP and RDMAP
>drafts.  Substantial meeting time has been allocated to it.
>
>
>_______________________________________________
>rddp mailing list
>rddp@ietf.org
>https://www1.ietf.org/mailman/listinfo/rddp

v2.40.3 | Report a Bug | By Email | System Status