Request Routing Redirection Interface for Content Delivery Network Interconnection
RFC 7975, “Request Routing Redirection Interface for Content Delivery Network Interconnection”, is a Proposed Standard document published in October 2016 by B. Niven-Jenkins, R. van Brandenburg. The canonical text is published by the RFC Editor.
Abstract
The Request Routing interface comprises (1) the asynchronous advertisement of footprint and capabilities by a downstream Content Delivery Network (CDN) that allows an upstream CDN to decide whether to redirect particular user requests to that downstream CDN; and (2) the synchronous operation of an upstream CDN requesting whether a downstream CDN is prepared to accept a user request and of a downstream CDN responding with how to actually redirect the user request. This document describes an interface for the latter part, i.e., the CDNI Request Routing Redirection interface.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7975 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7974 An Experimental TCP Option for Host Identification
- RFC 7976 Updates to Private Header Extension Usage in Session Initiation Protocol Requests and Responses
- RFC 7973 Assignment of an Ethertype for IPv6 with Low-Power Wireless Personal Area Network Encapsulation
- RFC 7977 The WebSocket Protocol as a Transport for the Message Session Relay Protocol
- RFC 7972 Entertainment Identifier Registry URN Namespace Definition
- RFC 7978 Transparent Interconnection of Lots of Links : RBridge Channel Header Extension
- RFC 7971 Application-Layer Traffic Optimization Deployment Considerations
- RFC 7979 Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA Protocol Parameters Registries