RFC 3568: Known Content Network (CN) Request-Routing Mechanisms
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3568
- Published
- July 2003
- Authors
- A. Barbir; B. Cain; R. Nair; O. Spatscheck
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 2651The Architecture of the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2294Representing the O/R Address hierarchy in the X.500 Directory Information TreeCurrent
March 1998
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
- RFC 3719Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)Current
February 2004
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?