[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: Updated agenda for CDNP BOF



Here's what I just sent in to the secretariat. I've included all submitted
drafts, and corrected the version numbers on the drafts that were wrong.  I
haven't made any other changes.  If you don't like my one-line
characterization of your draft, please send me a better one.

I will also be working on a somewhat more open-ended description of the
problem and solution to take account of the newer drafts received, but I
haven't finished that work yet.

Several people want to make short presentations at the BOF. I will be
talking with them and working out what we can actually manage in the time
available.  So the proposed agenda may change again.

Note that we have a huge number of drafts (9).  The more people who are able
to read all of them and comment intelligently on the relationships among
them, the better off we will be.

--Mark

Mark Stuart Day
Senior Scientist
Cisco Systems
+1 (781) 663-8310
markday@cisco.com

-----Original Message-----
From: Mark Day [mailto:markday@cisco.com]
Sent: Friday, December 01, 2000 10:22 AM
To: agenda@ietf.org
Subject: Updated agenda for CDNP BOF


Content Distribution Internetworking BOF (cdnp)

Chair: Mark Day, markday@cisco.com

Problem to be solved:

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

Outline of proposed solution:

Recent discussions have proposed treating a CDN as containing a direction
system, a distribution system, and an accounting system.  The proposed
approach to CDN interoperation is through supporting the transfer of
information between the corresponding systems of two peered networks.  We
propose the development of three protocols or protocol families, one for
each of the kinds of systems that can be peered.

There are 9 internet-drafts available:

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

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

-- An examination of accounting issues to be considered:
http://www.ietf.org/internet-drafts/draft-gilletti-cdnp-aaa-reqs-00.txt

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

-- A summary of known mechanisms for routing requests to a surrogate:
http://www.ietf.org/internet-drafts/draft-cain-cdnp-known-request-routing-00
.txt

-- A description of OACP, a proposed peering mechanism for caches:
http://www.ietf.org/internet-drafts/draft-rzewski-oacp-00.txt

-- A description of a proposed mechanism for content signalling:
http://www.ietf.org/internet-drafts/draft-rzewski-cndistcs-00.txt

-- A proposed log format and communication mechanism for accounting:
http://www.ietf.org/internet-drafts/draft-rzewski-cnacct-00.txt

-- A proposed mechanism for request routing using DNS:
http://www.ietf.org/internet-drafts/draft-deleuze-cdnp-dnsmap-peer-00.txt

Proposed agenda:

* Agenda bashing (2 min)
* Introduction/Overview of CDNs (5 min)
* Motivation for Peering (5 min)
* Discussion of Problem: Do the drafts adequately define a problem? (10 min)
* Discussion of Solution: Do the drafts adequately outline a solution? (10
min)
* Discussion of proposed WG charter (28 min)
* Thumbs up/down