[dcp] WG Action: Datagram Congestion Control Protocol (dccp) (fwd)
Aaron Falk <falk@isi.edu> Wed, 03 July 2002 01:51 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28100 for <dcp-archive@odin.ietf.org>; Tue, 2 Jul 2002 21:51:18 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA08651 for dcp-archive@odin.ietf.org; Tue, 2 Jul 2002 21:52:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA08641; Tue, 2 Jul 2002 21:52:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA08604 for <dcp@optimus.ietf.org>; Tue, 2 Jul 2002 21:52:00 -0400 (EDT)
Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28094 for <dcp@ietf.org>; Tue, 2 Jul 2002 21:51:10 -0400 (EDT)
Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by nit.isi.edu (8.11.6/8.11.6) with ESMTP id g631put28447 for <dcp@ietf.org>; Tue, 2 Jul 2002 18:51:56 -0700
Date: Tue, 02 Jul 2002 18:51:55 -0700
From: Aaron Falk <falk@isi.edu>
To: dcp@ietf.org
Message-ID: <11060000.1025661115@nit.isi.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: [dcp] WG Action: Datagram Congestion Control Protocol (dccp) (fwd)
Sender: dcp-admin@ietf.org
Errors-To: dcp-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Datagram Control Protocol <dcp.ietf.org>
X-BeenThere: dcp@ietf.org
Content-Transfer-Encoding: 7bit
It's official: we're a working group! Note the wrong mail list info on the announcement. I'm working on getting that fixed and will advise this group about the resolution when it happens. --aaron ---------- Forwarded Message ---------- Date: Tuesday, July 02, 2002 09:10:49 AM -0400 From: Steve Coya <scoya@cnri.reston.va.us> To: IETF-Announce Subject: WG Action: Datagram Congestion Control Protocol (dccp) A new IETF working group has been created in the Transport Area. Please contact the Area Directors or the WG chair for more information. Datagram Congestion Control Protocol (dccp) ------------------------------------------- Current Status: Active Working Group Chair(s): Aaron Falk <falk@isi.edu> Transport Area Director(s): Scott Bradner <sob@harvard.edu> Allison Mankin <mankin@isi.edu> Transport Area Advisor: Allison Mankin <mankin@isi.edu> Mailing Lists: General Discussion:dccp@ietf.org To Subscribe: dccp-request@ietf.org In Body: (un)subscribe Archive: www.ietf.org/mail-archive/working-groups/dccp/current/maillist.html Description of Working Group: The Datagram Control Protocol working group is chartered to develop and standardize the Datagram Congestion Control Protocol (DCCP). DCCP is a minimal general purpose transport-layer protocol providing only two core functions: - the establishment, maintenance and teardown of an unreliable packet flow. - congestion control of that packet flow. Within the constraints of providing these core functions, DCCP aims to be a general purpose protocol, minimizing the overhead of packet header size or end-node processing as much as possible. Therefore, DCCP is as simple as possible, and as far as reasonably possible, it should avoid providing higher-level transport functionality. DCCP will provide a congestion-controlled, unreliable packet stream, without TCP's reliability or in-order delivery semantics. Additional unicast, flow-based application functionality can be layered over DCCP. SCOPE Drafts for DCCP, and several associated congestion control IDs, already exist. The first task before the working group will be an abbreviated functional requirement validation of those drafts. There are two possible outcomes: 1) The current DCCP draft is declared suitable for further work, with some areas listed for possible extension. 2) The current DCCP draft is declared unsuitable for further work, and more formal functional requirement exploration begins. Prior to the final development of the protocol, the working group will investigate areas of functionality that should be integrated into DCCP because they are difficult or impossible to layer above it. These areas include security and multi-homing/mobility, at a minimum. The protocol will be for both IPv4 and IPv6. It will not encompass multicast. It is strictly a unicast transport. For security, the working group will endeavor to ensure that DCCP incorporates good non-cryptographic mechanisms that make it resistant to denial-of-service attacks on DCCP connections and DCCP servers. A related topic that will be explored is whether DCCP can be a candidate to replace UDP in the transport of security management protocols such as IKE and JFK. The working group will also investigate DCCP's relationship with RTP (the Real-time Transport Protocol). Once the DCCP specification has stabilized, the WG will produce a document providing guidance to potential users of DCCP. The precise form of this document will be determined by WG discussion, but it might include example APIs, an applicability statement, or other forms of guidance about appropriate usage of DCCP. Goals and Milestones: SEP 02 Publish summary of required protocol functions/requirements DEC 02 Decision to build on proposed DCCP protocol, alternate protocol, or quit and go home APR 03 Publish DCCP protocol as proposed standard (including applicability statement) APR 03 Publish TCP equivalent congestion profile as proposed standard APR 03 Publish TCP Friendly Rate Control congestion profile as Proposed Standard JUN 03 Publish document providing guidance to users of DCCP as an Informational RFC. ---------- End Forwarded Message ---------- _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/