Known Content Network Request-Routing Mechanisms
RFC 3568, “Known Content Network Request-Routing Mechanisms”, is an Informational document published in July 2003 by A. Barbir, B. Cain, R. Nair, O. Spatscheck. It has since been updated by RFC 8996. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3568 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3567 Intermediate System to Intermediate System Cryptographic Authentication
- RFC 3569 An Overview of Source-Specific Multicast
- RFC 3566 The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec
- RFC 3570 Content Internetworking Scenarios
- RFC 3565 Use of the Advanced Encryption Standard Encryption Algorithm in Cryptographic Message Syntax
- RFC 3571 Framework Policy Information Base for Usage Feedback
- RFC 3564 Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
- RFC 3572 Internet Protocol Version 6 over MAPOS