[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Notice on drafts
- To: cdn@ops.ietf.org
- Subject: Notice on drafts
- From: "Phil Rzewski" <philr@inktomi.com>
- Date: Mon, 27 Nov 2000 23:19:14 -0800
- Delivery-date: Mon, 27 Nov 2000 23:20:40 -0800
- Envelope-to: cdn-data@psg.com
Greetings. I wanted to notify folks on this list of a few Internet Drafts
that were recently submitted to the IETF. They are:
http://www.ietf.org/internet-drafts/draft-rzewski-oacp-00.txt
http://www.ietf.org/internet-drafts/draft-rzewski-cndistcs-00.txt
http://www.ietf.org/internet-drafts/draft-rzewski-cnacct-00.txt
Some may recall that I had made a post to this mailing list a few weeks ago
expressing some worry about the use of the term "CDN Peering" and how it
seems to imply that the only networks that might want to be "peered" at the
content layer are therefore being called "CDNs". One of my worries was how
this might conflict with terminology that's already accepted in the
industry. However, I didn't want to belabor the point unless there were
written drafts that back it up.
To put the drafts in context, they're an attempt to attack "Content
Peering" by looking at a specific implementation involving different types
of networks (CDN, Hoster, Access) and how they fit together. Also FYI,
these drafts are an attempt to open up some of the "version 1.0"
functionality happening within the Content Bridge alliance.
Because they're not specifically CDN-focused, this list may not be the
ideal place to request feedback. However, since this list is looking toward
a BOF to discuss cross-network peering at the content layer, I figure this
might be a good place to start. Hopefully folks will agree that it's better
than trying to start a completely parallel "Content Peering" standards effort.
--
Phil Rzewski - Senior Architect - Inktomi Corporation
650-653-2487 (office) - 650-303-3790 (cell) - 650-653-1848 (fax)