[dcp] Re: DCP charter.....

Bernard Aboba <aboba@internaut.com> Wed, 05 December 2001 05:48 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 AAA27906 for <dcp-archive@odin.ietf.org>; Wed, 5 Dec 2001 00:48:55 -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 AAA23409; Wed, 5 Dec 2001 00:48:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA23380 for <dcp@optimus.ietf.org>; Wed, 5 Dec 2001 00:48:48 -0500 (EST)
Received: from internaut.com ([64.38.134.99]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27901 for <dcp@ietf.org>; Wed, 5 Dec 2001 00:48:46 -0500 (EST)
Received: from localhost (aboba@localhost) by internaut.com (8.9.3/8.9.3) with ESMTP id VAA15057; Tue, 4 Dec 2001 21:36:25 -0800 (PST) (envelope-from aboba@internaut.com)
Date: Tue, 4 Dec 2001 21:36:25 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: Sally Floyd <floyd@aciri.org>
cc: "Mike O'Dell" <mo@ccr.org>, tsv@newdev.harvard.edu, dcp@ietf.org
In-Reply-To: <200112050108.fB518Mr75964@elk.aciri.org>
Message-ID: <Pine.BSF.4.21.0112042118590.15040-100000@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [dcp] Re: DCP charter.....
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

> Yep, you could look at the DCP web page at:
>  http://www.aciri.org/kohler/dcp/
> and at the four internet drafts on that page.

Looked at the drafts and  the major application cited was telephony and
streaming media (control? data?).  While I can see how some of the DCP
services might be desirable, the drafts don't really provide a complete
picture of how DCP will be used, or a convincing argument as to why
alternatives (such as RTP deployed with layered codecs) isn't
sufficient.  As a result, it isn't clear from these documents whether we
have a solution in search of a problem. 

>  Drafts for DCP, 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 DCP draft is declared suitable for
>  further work, with some areas listed for possible extension.  (2) The
>  current DCP draft is declared unsuitable for further work, and more
>  formal functional requirement exploration begins.

Seems to me that a more in depth "problem statement" might be helpful,
too. Given that we're finally starting to ship telephony/streaming
media software using other transports, some good arguments will be
needed to persuade folks to change horses in mid-ride. This is
particularly true given how long it seems to ship passable support for new
transports. 



_______________________________________________
dcp mailing list
dcp@ietf.org
https://www1.ietf.org/mailman/listinfo/dcp