Content Terminology in CDN Interconnection
draft-deventer-cdni-content-terminology-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Oskar van Deventer , Ray van Brandenburg | ||
| Last updated | 2011-07-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This internet-draft describes how the term content might take on various meanings in different Content Delivery Network (CDN) interconnection scenarios. In order to solve this ambiguity, some additional terminology to describe content in CDNs is introduced, in alignment with terminology developed by the ETSI MCD CDN-I Working Group.
Authors
Oskar van Deventer
Ray van Brandenburg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)