Known CDN Request Mapping Mechanisms
draft-cain-cdnp-known-req-map-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bradley Cain , Fred Douglis , Mark A. Green , Markus Hofmann , Raj Nair , Doug Potter , Oliver Spatscheck | ||
| Last updated | 2000-11-14 | ||
| 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 memo presents a number of known mechanisms used to direct client application requests to surrogate servers based on various policies. In this memo we group mechanisms commonly called request routing, content routing or content redirection under the term request mapping. There exist multiple request mapping mechanisms. At a high-level, these may be classified under: DNS Request Mapping, Transport-layer Mapping, and Application-layer Mapping.
Authors
Bradley Cain
Fred Douglis
Mark A. Green
Markus Hofmann
Raj Nair
Doug Potter
Oliver Spatscheck
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)