RFC 7336: Framework for Content Distribution Network Interconnection (CDNI)
In plain English — editorial summary, not part of the RFC
This document presents a framework for Content Distribution Network Interconnection (CDNI). The purpose of the framework is to provide an overall picture of the problem space of CDNI and to describe the relationships among the various components necessary to interconnect CDNs. CDNI requires the specification of interfaces and mechanisms to address issues such as request routing, distribution metadata exchange, and logging information exchange across CDNs. The intent of this document is to outline what each interface needs to accomplish and to describe how these interfaces and mechanisms fit together, while leaving their detailed specification to other documents. This document, in combination with RFC 6707, obsoletes RFC 3466.
Document record
- Document ID
- RFC7336
- Published
- August 2014
- Authors
- L. Peterson; B. Davie; R. van Brandenburg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 58
- Also known as
- —
- Obsoletes:
- RFC 3466
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7736Content Delivery Network Interconnection (CDNI) Media Type RegistrationCurrent
December 2015
- RFC 6770Use Cases for Content Delivery Network InterconnectionCurrent
November 2012
- RFC 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 8008Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities SemanticsUpdated
December 2016
- RFC 5716Requirements for Federated File SystemsCurrent
January 2010
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 7711PKIX over Secure HTTP (POSH)Current
November 2015
- RFC 7712Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)Current
November 2015
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?