Re: [dcp] Re: draft DCP charter for discussion
Mark Handley <mjh@aciri.org> Fri, 07 December 2001 01:34 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 UAA20825
for <dcp-archive@odin.ietf.org>; Thu, 6 Dec 2001 20:34:46 -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 UAA23661;
Thu, 6 Dec 2001 20:34:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA23628
for <dcp@optimus.ietf.org>; Thu, 6 Dec 2001 20:34:42 -0500 (EST)
Received: from vulture.aciri.org (adsl-63-196-11-253.dsl.snfc21.pacbell.net
[63.196.11.253]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20798
for <dcp@ietf.org>; Thu, 6 Dec 2001 20:34:39 -0500 (EST)
Received: from vulture.aciri.org (localhost [127.0.0.1])
by vulture.aciri.org (8.11.6/8.11.1) with ESMTP id fB71X8L42719;
Thu, 6 Dec 2001 17:33:10 -0800 (PST)
(envelope-from mjh@vulture.aciri.org)
From: Mark Handley <mjh@aciri.org>
X-Organisation: ACIRI
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: Aaron Falk <falk@isi.edu>, dcp <dcp@ietf.org>,
Transport Area Directorate <tsv@newdev.harvard.edu>
Subject: Re: [dcp] Re: draft DCP charter for discussion
In-reply-to: Your message of "Thu, 06 Dec 2001 13:18:46 PST."
<179010012.1007644726@localhost>
Date: Thu, 06 Dec 2001 17:33:08 -0800
Message-ID: <42717.1007688788@vulture.aciri.org>
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
>so what is the relationship between DCP and the "congestion control >building blocks"/"congestion manager" approach that was all the rage a few >IETFs ago? I think fractionally less than the relationship between TCP and CM. You could implement TCP in such a way that it used CM. Similarly you could implement DCP in such a way that it used CM. But you don't have to in either case. However, while TCP essentially has only one type of congestion control feedback, DCP is more flexible - the feedback type and CC dynamics can depend on the negotiated CCID. Thus while you could use a CM to share congestion state between TCP flows and/or DCP flows that use TCP-like dynamics. And you could use a CM to share congestion state between DCP flows using TFRC feedback and dynamics. But I wouldn't like to speculate on how you'd share congestion state between a flow using TCP-like feedback and dynamics, and one using TFRC feedback and dynamics. I don't think that the existence or non-existence of a CM greatly affects the design of a protocol like DCP, although of course with would impact the implementation. Cheers, Mark _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp
- [dcp] draft DCP charter for discussion Aaron Falk
- [dcp] Re: draft DCP charter for discussion Craig Partridge
- Re: [dcp] Re: draft DCP charter for discussion Sally Floyd
- Re: [dcp] draft DCP charter for discussion Stephen Casner
- [dcp] Re: draft DCP charter for discussion Harald Tveit Alvestrand
- Re: [dcp] Re: draft DCP charter for discussion Mark Handley