Considerations on Request Routing for CDNI
draft-stiemerling-cdni-routing-cons-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Stiemerling | ||
| Last updated | 2011-07-04 | ||
| 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
Request routing in CDNs and also in the case of interconnecting multiple CDNs requires to match against a set functional requirements but also operational requirements. This memo discusses a few operational requirements and the impact to the current request routing proposals.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)