RFC 3568: Known Content Network (CN) Request-Routing Mechanisms

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…

Read RFC 3568 on the RFC Editor

Outgoing relationships (16 related RFCs)

Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 2246: The TLS Protocol Version 1.0
Normative reference — RFC 1738: Uniform Resource Locators (URL)
Normative reference — RFC 2326: Real Time Streaming Protocol (RTSP)
Normative reference — RFC 1889: RTP: A Transport Protocol for Real-Time Applications
Normative reference — RFC 1546: Host Anycasting Service
Normative reference — RFC 3238: IAB Architectural and Policy Considerations for Open Pluggable Edge Services
Normative reference — RFC 3466: A Model for Content Internetworking (CDI)
Informative reference — RFC 1035: Domain names - implementation and specification
Informative reference — RFC 1034: Domain names - concepts and facilities
Informative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Informative reference — RFC 2181: Clarifications to the DNS Specification
Informative reference — RFC 2606: Reserved Top Level DNS Names
Informative reference — RFC 3272: Overview and Principles of Internet Traffic Engineering
Informative reference — RFC 3221: Commentary on Inter-Domain Routing in the Internet
Informative reference — RFC 2386: A Framework for QoS-based Routing in the Internet

Incoming relationships (2 related RFCs)

Updated by, Normatively referenced by — RFC 8996: Deprecating TLS 1.0 and TLS 1.1
Informatively referenced by — RFC 7971: Application-Layer Traffic Optimization (ALTO) Deployment Considerations