[rddp] RDDP status of drafts

Black_David@emc.com Tue, 02 March 2004 08:18 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 DAA25524 for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 03:18:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay560-0005j3-0q for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 03:17:44 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i228Hh5R022003 for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 03:17:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay55z-0005io-PA for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 03:17:43 -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 DAA25469 for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 03:17:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay55x-0004hb-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:17:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay551-0004YO-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:16:43 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Ay54R-0004Oe-00 for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:16:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay54P-0005Yd-Sp; Tue, 02 Mar 2004 03:16:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ay53o-0005TI-4C for rddp@optimus.ietf.org; Tue, 02 Mar 2004 03:15:28 -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 DAA25278 for <rddp@ietf.org>; Tue, 2 Mar 2004 03:15:26 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ay53l-0004Ku-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:15:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ay52r-00049n-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:14:30 -0500
Received: from srexchimc2.lss.emc.com ([168.159.100.11] helo=srexchimc2.eng.emc.com) by ietf-mx with esmtp (Exim 4.12) id 1Ay51g-0003sd-00 for rddp@ietf.org; Tue, 02 Mar 2004 03:13:16 -0500
Received: from MAHO3MSX2.corp.emc.com (maho3msx2.isus.emc.com [128.221.11.32]) by srexchimc2.eng.emc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id GD38BBXF; Tue, 2 Mar 2004 03:12:47 -0500
Received: by maho3msx2.isus.emc.com with Internet Mail Service (5.5.2653.19) id <FK9AJHZN>; Tue, 2 Mar 2004 03:12:47 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A5688@corpmx14.us.dg.com>
X-Sybari-Trust: bdebc29a 1d8c424f d02de4bf 0000013d
To: rddp@ietf.org
Date: Tue, 02 Mar 2004 03:12:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] RDDP status of drafts
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.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60

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