[rddp] RDDP Atlanta agenda

Black_David@emc.com Sat, 26 October 2002 00:45 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 UAA16933 for <rddp-archive@odin.ietf.org>; Fri, 25 Oct 2002 20:45:35 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9Q0lV610238 for rddp-archive@odin.ietf.org; Fri, 25 Oct 2002 20:47:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q0lVv10235 for <rddp-web-archive@optimus.ietf.org>; Fri, 25 Oct 2002 20:47:31 -0400
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 UAA16929 for <rddp-web-archive@ietf.org>; Fri, 25 Oct 2002 20:45:02 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q0lBv10227; Fri, 25 Oct 2002 20:47:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q0kIv10209 for <rddp@optimus.ietf.org>; Fri, 25 Oct 2002 20:46:18 -0400
Received: from mailhub.lss.emc.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16922 for <rddp@ietf.org>; Fri, 25 Oct 2002 20:43:51 -0400 (EDT)
From: Black_David@emc.com
Received: from emc.com (emcmail.lss.emc.com [168.159.48.78]) by mailhub.lss.emc.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g9Q0k7D24715 for <rddp@ietf.org>; Fri, 25 Oct 2002 20:46:07 -0400 (EDT)
Received: from mxic1.isus.emc.com ([168.159.129.100]) by emc.com (8.10.1/8.10.1) with ESMTP id g9Q0k7705439 for <rddp@ietf.org>; Fri, 25 Oct 2002 20:46:07 -0400 (EDT)
Received: by MXIC1 with Internet Mail Service (5.5.2653.19) id <VRWCVVBP>; Fri, 25 Oct 2002 20:46:06 -0400
Message-ID: <277DD60FB639D511AC0400B0D068B71E0564C494@CORPMX14>
To: rddp@ietf.org
Date: Fri, 25 Oct 2002 20:46:01 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [rddp] RDDP Atlanta agenda
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>

It is time to start setting the agenda for the Atlanta meeting.
If you want to discuss issues with drafts at the Atlanta meeting,
please request a slot to do so, by sending mail to the rddp WG
chair (black_david@emc.com).

Currently, I know of the need for slots for the following:
	- draft-romanow-rdma-over-ip-problem-statement-00.txt
	- draft-bailey-roi-ddp-rdma-arch-00.txt
	- draft-stewart-rddp-sctp-00.txt
	- draft-williams-iwarp-ift-00.txt
	- draft-shah-iwarp-ddp-00.txt
	- draft-recio-iwarp-rdma-00.txt
The above draft version numbers may advance during the next week.
If/when this happens, I would ask the draft author to post the new
version to a web site and send a URL to the list in addition to submitting
the draft to the secretariat - this is to deal with the likely backlog
in draft submission processing at the secretariat.  I've left
draft-black-rdma-concerns-00.txt off the above list, as I don't think
it needs a slot, but attendees should read it (and its version number
may also advance in the next week).

As always the slots will be allocated for discussions according
to what is outlined below.

	It is not the purpose of a WG session to have
	presentation of the content of a document. It
	is assumed that all attendees will have read the
	drafts in advance of the meeting.

	For documents that are work-in-progress, the
	presentation should cover issues resolved since
	the last draft followed by open issues, and
	controversial topics with the intent to reach a
	resolution of said issues and topics.

	For new work items, the presentation should focus on
	what the problem is and why it is necessary for the
	work group to address it.  The solution should only
	be sketched.  Lengthy presentations of drafts will
	be cut off.

	The appropriate way of bringing new work to the working
	group is to post an Internet Draft, send a pointer to
	the draft to the mailing list and promote
	discussion on the list. Slots on the agenda should be used
	to discuss outstanding topics that haven't been settled
	on the mailing list.

	In all cases only a limited number of slides should be used.
	Speakers should budget their at least 25% of their time to
	allow for discussion/questions.

Thanks,
--David (rddp WG chair)

----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953 **NEW**     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