Re: [rddp] WG Last Call: Problem Statement and Architecture
"Talpey, Thomas" <Thomas.Talpey@netapp.com> Thu, 27 March 2003 20:42 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18427 for <rddp-archive@odin.ietf.org>; Thu, 27 Mar 2003 15:42:31 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2RL3wU19972 for rddp-archive@odin.ietf.org; Thu, 27 Mar 2003 16:03:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RL3wO19969 for <rddp-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 16:03:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18421 for <rddp-web-archive@ietf.org>; Thu, 27 Mar 2003 15:42:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RL32O19927; Thu, 27 Mar 2003 16:03:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RL1ZO19821 for <rddp@optimus.ietf.org>; Thu, 27 Mar 2003 16:01:35 -0500
Received: from mx01.netapp.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18371 for <rddp@ietf.org>; Thu, 27 Mar 2003 15:39:36 -0500 (EST)
Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01.netapp.com (8.12.8/8.12.8/NTAP-1.4) with ESMTP id h2RKfvqU020901 for <rddp@ietf.org>; Thu, 27 Mar 2003 12:41:58 -0800 (PST)
Received: from tmt.netapp.com (tmt [10.97.1.30]) by frejya.corp.netapp.com (8.12.8/8.12.8/NTAP-1.4) with ESMTP id h2RKfuKo011822 for <rddp@ietf.org>; Thu, 27 Mar 2003 12:41:57 -0800 (PST)
Message-Id: <5.2.0.9.2.20030327152808.00af4208@silver.nane.netapp.com>
Date: Thu, 27 Mar 2003 15:41:01 -0500
To: rddp@ietf.org
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Subject: Re: [rddp] WG Last Call: Problem Statement and Architecture
In-Reply-To: <277DD60FB639D511AC0400B0D068B71E0564C9B1@corpmx14.us.dg.co m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>
A reminder, and notice that there is one issue in the Architecture document which will be addressed in the final version. The issue is around the change made in the current document to add a ddp_post_recv() function. From a pure architecture standpoint this has been deemed unnecessary, and the previous form of ddp_recv() will be restored, along with some new explanatory text. In effect, this returns to the ddp_recv() formal function returning a message_t, rather than a necessarily pre-registered recv_message_t. The difference is subtle but important. It is not necessary to make the requirement of preregistration for receives in the architecture, therefore the simplicity argument prevails. Any comments or concerns on the reversion to the prior ddp_recv() behavior should be sent to the list as soon as possible. There are currently no additional outstanding comments or changes on either document. Thanks, Tom. At 10:24 AM 3/5/2003, Black_David@emc.com wrote: >This message announces an informal Working Group >Last Call on the RDDP problem statement and architecture >drafts that are intended to become informational RFCs: > >- RDMA over IP Problem Statement, > draft-ietf-rddp-problem-statement-01.txt >- The Architecture of Direct Data Placement (DDP) And > Remote Direct Memory Access (RDMA) On Internet > Protocols, draft-ietf-rddp-arch-01.txt > >Due to the timing of the IETF meetings in San Francisco, >this WG Last Call will run slightly longer than typical - >it will end at 9am Eastern Time on Monday, March 31st, >giving everyone a full week after the IETF meetings >to review and comment on these drafts. > >Editorial comments should be sent directly to the >draft editor: Thomas Talpey [Thomas.Talpey@netapp.com] >Technical comments and requests for changes must be >sent to the RDDP mailing list [rddp@ietf.org] for >discussion. > >Thanks, >--David [RDDP WG chair] > >---------------------------------------------------- >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] WG Last Call: Problem Statement and Archit… Black_David
- Re: [rddp] WG Last Call: Problem Statement and Ar… Talpey, Thomas
- Re: [rddp] WG Last Call: Problem Statement and Ar… Caitlin Bestler
- RE: [rddp] WG Last Call: Problem Statement and Ar… Black_David