ALTO session for CDN Interconnection
draft-stephan-cdni-alto-session-ext-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stephan Emile , Selim Ellouze | ||
| Last updated | 2014-10-19 (Latest revision 2014-04-17) | ||
| 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
The selection of a downstream CDN by an upstream CDN is based on multi-dimensional criteria. Various protocols, such as BGP or ALTO, may be used by a downstream CDN to expose content routing information and interconnection preferences to an upstream CDN. The selection of such a protocol is premature as the WG, and especially the Footprint/ Capabilities Design Team, is currently working on this topic. So this draft does not promote the usage of the ALTO protocol for CDN interconnection. It presents the limitations of the current ALTO protocol in the case it would be selected for CDN interconnection. It specifies the mechanism for controlling the session initialization and for limiting the information exchanged. Then it discusses the need of incremental update and proposes to study the usage of Netconf /Yang to provide ALTO server with notifications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)