[dcp] Re: [e2e] DCP mail list
demir <demir@usc.edu> Fri, 30 November 2001 21:52 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 QAA09565
for <dcp-archive@odin.ietf.org>; Fri, 30 Nov 2001 16:52:01 -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 QAA21887;
Fri, 30 Nov 2001 16:52:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA21853
for <dcp@ns.ietf.org>; Fri, 30 Nov 2001 16:52:02 -0500 (EST)
Received: from usc.edu (root@usc.edu [128.125.253.136])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09510;
Fri, 30 Nov 2001 16:51:34 -0500 (EST)
Received: from sal-sun057.usc.edu (sal-sun057.usc.edu [128.125.5.156])
by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
id NAA14087; Fri, 30 Nov 2001 13:51:44 -0800 (PST)
Received: from localhost (demir@localhost)
by sal-sun057.usc.edu (8.10.1/8.10.1/usc) with ESMTP
id fAULphk25537; Fri, 30 Nov 2001 13:51:43 -0800 (PST)
Date: Fri, 30 Nov 2001 13:51:43 -0800 (PST)
From: demir <demir@usc.edu>
To: <falk@ISI.EDU>
cc: <tsvwg@ietf.org>, <end2end-interest@postel.org>, <ietf@ietf.org>,
<dcp@ietf.org>
In-Reply-To: <20011130113142.A2807@isi.edu>
Message-ID: <Pine.GSO.4.33.0111301350470.25535-100000@sal-sun057.usc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [dcp] Re: [e2e] 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
I am very happy to be part of this email list. Thank you very much. Dr. Alper K. Demir On Fri, 30 Nov 2001 falk@ISI.EDU wrote: > 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
- [dcp] DCP mail list falk
- [dcp] Re: [e2e] DCP mail list demir