RFC 7975: Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID

RFC7975

Published

October 2016

Authors

B. Niven-Jenkins; R. van Brandenburg

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

35

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7975

Topics

• HTTP
• DNS

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 8484DNS Queries over HTTPS (DoH)Current

  October 2018

• RFC 7838HTTP Alternative ServicesCurrent

  April 2016

• RFC 8164Opportunistic Security for HTTP/2Current

  May 2017

• RFC 8188Encrypted Content-Encoding for HTTPCurrent

  June 2017

• RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted

  November 2015

• RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted

  September 2015

• RFC 8336The ORIGIN HTTP/2 FrameCurrent

  March 2018

• RFC 7541HPACK: Header Compression for HTTP/2Current

  May 2015

Also filed under

• PROPOSED STANDARD
• 2016
• IETF stream
• wit area