51st IETF - Content Distribution Internetworking WG (cdi), UPDATED

agenda@ietf.org Tue, 31 July 2001 21:42 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24444; Tue, 31 Jul 2001 17:42:56 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA08307 for ietf-123-outbound.10@ietf.org; Tue, 31 Jul 2001 15:15:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA07433 for <all-ietf@loki.ietf.org>; Tue, 31 Jul 2001 14:04:56 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04277 for <all-ietf>; Tue, 31 Jul 2001 14:04:55 -0400 (EDT)
Message-Id: <200107311804.OAA04277@ietf.org>
To: ietf-announce:;
From: agenda@ietf.org
Subject: 51st IETF - Content Distribution Internetworking WG (cdi), UPDATED
Date: Tue, 31 Jul 2001 14:04:55 -0400
Sender: dinaras@cnri.reston.va.us

Content Distribution Internetworking WG (cdi)

Monday, August 06 at 1530-1730
================================

CHAIRS: Mark Day <markday@cisco.com>
        Phil Rzewski <philr@inktomi.com>

DESCRIPTION:

Problem to be solved:

There are a number of Content Networks (CNs) deployed and/or planned,
including Content Distribution Networks (CDNs) and cache clusters.
Consistent with the general history of internetworking, people are
starting to think about ways to interconnect these different CNs, and
talking about "peering at the content level", "CDN peering," or "content
peering." Regardless of name, the goal is to allow different CNs --
implemented using differing technology or under different administrative
domains -- to cooperate with each other, forming a larger "virtual CN."

Background of proposed solution:

At the first CDI BOF in San Diego (December 12, 2000), rough consensus
was formed around the statement of the problem and need to work toward
creation of protocols to provide a solution. Since that BOF, the group
has continued its original focus of considering the problem in terms
of the three component systems of a Content Network: request-routing,
distribution, and accounting. The proposed approach to CN interoperation
has been to support the transfer of information between the corresponding
systems of two peered networks.

There are 4 internet-drafts of a "background" nature, which are older than
the other drafts. We will discuss whether these drafts can proceed to a
working group last call.

-- An introduction to the problem area and proposed vocabulary:
http://www.ietf.org/internet-drafts/draft-day-cdnp-model-06.txt

-- Some scenarios of use:
http://www.ietf.org/internet-drafts/draft-day-cdnp-scenarios-03.txt

-- A description of a proposed architecture for interoperation:
http://www.ietf.org/internet-drafts/draft-green-cdnp-gen-arch-03.txt

-- Known mechanisms for request-routing
http://www.ietf.org/internet-drafts/draft-cain-cdnp-known-request-routing-02
.txt

There are 3 internet-drafts of a "requirements" nature.  We will likewise
discuss whether these drafts can proceed to a working group last call.

-- Request-routing requirements for CDI
http://www.ietf.org/internet-drafts/draft-cain-request-routing-req-02.txt

-- Distribution requirements for CDI
http://www.ietf.org/internet-drafts/draft-amini-cdi-distribution-reqs-01.txt

-- Authentication/Authorization/Accounting requirements for CDI
http://www.ietf.org/internet-drafts/draft-gilletti-cdnp-aaa-reqs-01.txt

We also anticipate that there may be one or more new internet-drafts
representing concrete proposals meeting some or all of the draft
requirements. If so, we will take some of the time for short presentations
of those proposals.

AGENDA:

* Agenda bashing
* Summary of charter / group activity since prior BOF
* Summary & discussion of "background" drafts
* Summary & discussion of "requirements" drafts
* Summary & discussion of protocol proposals