Known CDN Request Mapping Mechanisms
draft-cain-cdnp-known-req-map-00

Document Type Expired Internet-Draft (individual)
Last updated 2000-11-14
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-cain-cdnp-known-req-map-00.txt

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 (bcain@mediaone.net)
Fred Douglis (douglis@research.att.com)
Mark Green (markg@home.net)
Markus Hofmann (hofmann@bell-labs.com)
Raj Nair (nair@arrowpoint.com)
Doug Potter (dougpott@cisco.com)
Oliver Spatscheck (spatsch@cs.arizona.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)