RFC 7337: Content Distribution Network Interconnection (CDNI) Requirements
In plain English — editorial summary, not part of the RFC
Content delivery is frequently provided by specifically architected and provisioned Content Delivery Networks (CDNs). As a result of significant growth in content delivered over IP networks, existing CDN providers are scaling up their infrastructure. Many Network Service Providers (NSPs) and Enterprise Service Providers (ESPs) are also deploying their own CDNs. To deliver contents from the Content Service Provider (CSP) to end users, the contents may traverse across multiple CDNs. This creates a need for interconnecting (previously) standalone CDNs so that they can collectively act as a single delivery platform from the CSP to the end users. The goal of the present document is to outline the requirements for the solution and interfaces to be specified by the CDNI working group.
Document record
- Document ID
- RFC7337
- Published
- August 2014
- Authors
- K. Leung; Y. Lee
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 7323TCP Extensions for High PerformanceCurrent
September 2014
- RFC 7390Group Communication for the Constrained Application Protocol (CoAP)Current
October 2014
- RFC 7273RTP Clock Source SignallingCurrent
June 2014
- RFC 7272Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP)Current
June 2014
- RFC 7413TCP Fast OpenCurrent
December 2014
- RFC 7414A Roadmap for Transmission Control Protocol (TCP) Specification DocumentsUpdated
February 2015
- RFC 7417Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) DomainsCurrent
December 2014
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?