RFC 6707: Content Distribution Network Interconnection (CDNI) Problem Statement
In plain English — editorial summary, not part of the RFC
Content Delivery Networks (CDNs) provide numerous benefits for cacheable content: reduced delivery cost, improved quality of experience for End Users, and increased robustness of delivery. For these reasons, they are frequently used for large-scale content delivery. As a result, existing CDN Providers are scaling up their infrastructure, and many Network Service Providers (NSPs) are deploying their own CDNs. It is generally desirable that a given content item can be delivered to an End User regardless of that End User's location or attachment network. This is the motivation for interconnecting standalone CDNs so they can interoperate as an open content delivery infrastructure for the end-to-end delivery of content from Content Service Providers (CSPs) to End Users. However, no standards or open specifications currently exist to facilitate such CDN Interconnection. The goal of this document is to outline the problem area of CDN Interconnection for the IETF CDNI (CDN Interconnection) working group. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6707
- Published
- September 2012
- Authors
- B. Niven-Jenkins; F. Le Faucheur; N. Bitar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6770Use Cases for Content Delivery Network InterconnectionCurrent
November 2012
- RFC 7736Content Delivery Network Interconnection (CDNI) Media Type RegistrationCurrent
December 2015
- RFC 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 8006Content Delivery Network Interconnection (CDNI) MetadataCurrent
December 2016
- RFC 8007Content Delivery Network Interconnection (CDNI) Control Interface / TriggersCurrent
December 2016
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
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?