[dcp] DCP mail list

falk@ISI.EDU Fri, 30 November 2001 19:32 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 OAA00753 for <dcp-archive@odin.ietf.org>; Fri, 30 Nov 2001 14:32:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17410 for <dcp-web-archive@ietf.org>; Fri, 30 Nov 2001 14:32:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17382 for <dcp@ns.ietf.org>; Fri, 30 Nov 2001 14:32:29 -0500 (EST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00729; Fri, 30 Nov 2001 14:32:17 -0500 (EST)
Received: from new.isi.edu (new.isi.edu [128.9.160.38]) by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id fAUJWEg15888; Fri, 30 Nov 2001 11:32:14 -0800 (PST)
Received: (from afalk@localhost) by new.isi.edu (8.11.6/8.8.6) id fAUJVgx02810; Fri, 30 Nov 2001 11:31:42 -0800
Date: Fri, 30 Nov 2001 11:31:42 -0800
From: falk@ISI.EDU
To: tsvwg@ietf.org, end2end-interest@postel.org, ietf@ietf.org
Cc: dcp@ietf.org
Message-ID: <20011130113142.A2807@isi.edu>
Mail-Followup-To: tsvwg@ietf.org, end2end-interest@postel.org, ietf@ietf.org, dcp@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Subject: [dcp] DCP mail list
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

Hello-

A mail list has been created to discuss the Datagram Control Protocol
(DCP).  DCP 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, DCP aims
to be a general purpose protocol, minimizing the overhead of packet
header size or end-node processing as much as possible.  Therefore,
DCP is as simple as possible, and as far as reasonably possible,
it should avoid providing higher-level transport functionality.
DCP will provide an congestion-controlled, unreliable packet stream,
without TCP's reliability or in-order delivery semantics.  Additional
unicast, flow-based application functionality can be layered over
DCP.

Subscribe to this list through the web page at
http://www.ietf.org/mailman/listinfo/dcp.

Updated drafts have been submitted to the IETF and can be found at
http://www.aciri.org/kohler/dcp/.

A draft working group charter will be sent to the list in the next
couple days.

A BoF is scheduled at IETF-52 in Salt Lake City on Tuesday at 5pm.
The BoF agenda can be found at http://www.ietf.org/ietf/01dec/dcp.txt.

--aaron

_______________________________________________
dcp mailing list
dcp@ietf.org
http://www.ietf.org/mailman/listinfo/dcp