RFC 6770: Use Cases for Content Delivery Network Interconnection
In plain English — editorial summary, not part of the RFC
Content Delivery Networks (CDNs) are commonly used for improving the End User experience of a content delivery service while keeping cost at a reasonable level. This document focuses on use cases that correspond to identified industry needs and that are expected to be realized once open interfaces and protocols supporting the interconnection of CDNs are specified and implemented. This document can be used to motivate the definition of the requirements to be supported by CDN Interconnection (CDNI) interfaces. It obsoletes RFC 3570. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6770
- Published
- November 2012
- Authors
- G. Bertrand; E. Stephan; T. Burbridge; P. Eardley; K. Ma; G. Watson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 3570
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 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 6707Content Distribution Network Interconnection (CDNI) Problem StatementCurrent
September 2012
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 8006Content Delivery Network Interconnection (CDNI) MetadataCurrent
December 2016
- RFC 8007Content Delivery Network Interconnection (CDNI) Control Interface / TriggersCurrent
December 2016
- RFC 8008Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities SemanticsUpdated
December 2016
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
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?