Re: [rddp] RDDP Draft Status
"Talpey, Thomas" <Thomas.Talpey@netapp.com> Tue, 08 November 2005 21:28 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 1EZb0q-0005AW-PY; Tue, 08 Nov 2005 16:28:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZb0o-0005AR-Re for rddp@megatron.ietf.org; Tue, 08 Nov 2005 16:28:14 -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 QAA06953 for <rddp@ietf.org>; Tue, 8 Nov 2005 16:27:47 -0500 (EST)
Received: from mx2.netapp.com ([216.240.18.37]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZbGg-0001VO-NQ for rddp@ietf.org; Tue, 08 Nov 2005 16:44:40 -0500
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2.netapp.com with ESMTP; 08 Nov 2005 13:28:00 -0800
X-IronPort-AV: i="3.97,305,1125903600"; d="scan'208"; a="336420311:sNHT16930908"
Received: from svlexc03.hq.netapp.com (svlexc03.corp.netapp.com [10.57.156.149]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id jA8LRxel001075; Tue, 8 Nov 2005 13:27:59 -0800 (PST)
Received: from lavender.hq.netapp.com ([10.56.11.75]) by svlexc03.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 8 Nov 2005 13:27:59 -0800
Received: from exnane01.hq.netapp.com ([10.97.0.61]) by lavender.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 8 Nov 2005 13:27:59 -0800
Received: from tmt.netapp.com ([10.97.6.51]) by exnane01.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 8 Nov 2005 16:27:57 -0500
Message-Id: <6.2.3.4.2.20051108160502.065a38e0@exnane01.nane.netapp.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Tue, 08 Nov 2005 16:27:33 -0500
To: rddp@ietf.org
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Subject: Re: [rddp] RDDP Draft Status
In-Reply-To: <F222151D3323874393F83102D614E05501551C8C@CORPUSMX20A.corp. emc.com>
References: <F222151D3323874393F83102D614E05501551C8C@CORPUSMX20A.corp.emc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 08 Nov 2005 21:27:57.0853 (UTC) FILETIME=[49CB54D0:01C5E4AB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: jon.peterson@neustar.biz
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=unsubscribe>
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>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
If folks haven't seen them, the new IETF "Tools" pages are really spectacular and provide very easy access to these statuses. Here's the URL for the RDDP WG: http://tools.ietf.org/wg/rddp/ Something I like very much as an author, is the ability to view all versions of any active draft, and be able to diff them against one another and check for ID-nits, etc. You can get a taste of what the tools can do with the links below. Highly recommended! <http://tools.ietf.org/wg/rddp/draft-ietf-rddp-arch/> <http://tools.ietf.org/wg/rddp/draft-ietf-rddp-problem-statement/> I spoke with the RFC Editors just now here in Vancouver on the Problem Statement and Architecture documents, which they requested some clarifications on, and we provided of course. (These were mostly references and a dead URL or two.) The editors report that all issues are now resolved, and the documents should move forward to "AUTH48" (authors' 48-hour) status shortly. I'm pretty sure my coauthors and I will approve that! :-) Tom. At 03:42 PM 11/8/2005, Black_David@emc.com wrote: >Since it's IETF week, and the RDDP WG is not meeting, >I thought I'd report on the status of the WG's drafts. >This is what I (as your WG chair) believe the status >to be - please send me any corrections. > >Problem Statement and Architecture Drafts - Both are in > the RFC Editor Queue. The RFC Editor has been actively > editing them, as queries on editing issues have been > seen recently, so RFC publication should happen > soon (for some value of "soon" ;-) ). > >All 6 remaining drafts (Applicability, Security, RDMAP, > DDP, MPA, and SCTP) are in Expert Review by our > Area Director (Jon Peterson). In discussion with > Jon, we (Jon and yours truly) have decided to take > the Applicability and Security drafts forward to > IETF Last Call and the IESG first, and then follow > up with the other 4 drafts. A new version of the > Applicability draft will be needed before IETF Last > Call, and a new version of the security draft will > probably be needed. I hope to get a complete set > of comments and instructions to the authors of > these two drafts this week or early next week. > >Thanks, >--David >---------------------------------------------------- >David L. Black, Senior Technologist >EMC Corporation, 176 South St., Hopkinton, MA 01748 >+1 (508) 293-7953 FAX: +1 (508) 293-7786 >black_david@emc.com Mobile: +1 (978) 394-7754 >---------------------------------------------------- > >_______________________________________________ >rddp mailing list >rddp@ietf.org >https://www1.ietf.org/mailman/listinfo/rddp _______________________________________________ rddp mailing list rddp@ietf.org https://www1.ietf.org/mailman/listinfo/rddp
- [rddp] RDDP Draft Status Black_David
- Re: [rddp] RDDP Draft Status Talpey, Thomas