[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Revised charter proposal (for IESG)
Our most-recently-submitted charter proposal (back in July) is pretty far
removed from our current reality. This revision updates links to drafts and
moves milestones into the future, as well as removing text that IESG members
previously objected to.
I introduced a Feb 1 date for making some progress on our AAA draft or
dropping it, as a concrete realization of what we discussed at IETF52.
I'm happy to respond to comments and questions, but I hope the overall
changes are hugely uncontroversial. ;-)
Content Distribution Internetworking (cdi)
Mark Day <email@example.com>
Phil Rzewski <firstname.lastname@example.org>
Applications Area Directors:
Ned Freed <email@example.com>
Patrik Faltstrom <firstname.lastname@example.org>
Applications Area Advisor:
Patrik Faltstrom <email@example.com>
General discussion: firstname.lastname@example.org
To subscribe: email@example.com
Description of Working Group:
The goal of this working group is to define protocols to allow the
interoperation of separately-administered content networks.
A content network is an architecture of network elements, arranged for
efficient delivery of digital content. Such content includes, but is not
limited to, web pages and images delivered via HTTP, and streaming or
continuous media delivered via RTSP.
The working group will first define requirements for three modes of
content internetworking: interoperation of request-routing systems,
interoperation of distribution systems, and interoperation of accounting
systems. These requirements are intended to lead to a follow-on effort to
define protocols for interoperation of these systems.
In its initial form, the working group is not chartered to deliver those
protocols, but we encourage individual submission of internet-drafts
describing protocols intended to meet the evolving requirements. We
anticipate rechartering of the working group to specify protocols, after the
requirements documents are stable and rough consensus emerges about the
number and relationship of such protocols.
In addition to defining requirements, the working group will develop a
number of supporting documents. These documents are: a shared vocabulary
for the problem domain, scenarios, an overall architecture for
interoperation, and a summary of request-routing mechanisms currently in
use. The total expected deliverables are as follows, including the current
draft corresponding to each:
3. System Architecture
4. Request-Routing Known Mechanisms
5. Requirements for Request-Routing
6. Requirements for Distribution
7. Requirements for Accounting
Goals and Milestones
February 1, 2002: Start WG last calls for vocabulary, scenarios, system
architecture, request-routing known mechanisms.
February 1, 2002: Deadline for new accounting requirements draft or dropping
accounting requirements from deliverables.
March 1, 2002: Start WG last calls for request-routing requirements and
March 17-22, 2002: Meet at IETF53 to resolve issues
May 1, 2002: All supporting (non-requirements) documents published as RFCs
by this date.
June 1, 2002: Request-routing requirements and distribution requirements
published as RFCs by this date.
In addition to the drafts listed with specific deliverables, the following
CDI-related drafts have been written by participants in the group.