RFC 3568
Known Content Network (CN) Request-Routing Mechanisms, July 2003
- File formats:
- Status:
- INFORMATIONAL
- Updated by:
- RFC 8996
- Authors:
- A. Barbir
B. Cain
R. Nair
O. Spatscheck - Stream:
- IETF
- Source:
- cdi (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3568
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3568
Abstract
This document presents a summary of Request-Routing techniques that are used to direct client requests to surrogates based on various policies and a possible set of metrics. The document covers techniques that were commonly used in the industry on or before December 2000. In this memo, the term Request-Routing represents techniques that is commonly called content routing or content redirection. In principle, Request-Routing techniques can be classified under: DNS Request-Routing, Transport-layer Request-Routing, and Application-layer Request-Routing. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.