Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

B. Niven-Jenkins
F. Le Faucheur
N. Bitar

Stream:

IETF

Source:

cdni (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6707

Discuss this RFC: Send questions or comments to the mailing listcdni@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6707

Abstract

Content Delivery Networks (CDNs) provide numerous benefits forcacheable content: reduced delivery cost, improved quality ofexperience for End Users, and increased robustness of delivery. Forthese reasons, they are frequently used for large-scale contentdelivery. As a result, existing CDN Providers are scaling up theirinfrastructure, and many Network Service Providers (NSPs) aredeploying their own CDNs. It is generally desirable that a givencontent item can be delivered to an End User regardless of that EndUser's location or attachment network. This is the motivation forinterconnecting standalone CDNs so they can interoperate as an opencontent delivery infrastructure for the end-to-end delivery ofcontent from Content Service Providers (CSPs) to End Users. However,no standards or open specifications currently exist to facilitatesuch CDN Interconnection.

The goal of this document is to outline the problem area of CDNInterconnection for the IETF CDNI (CDN Interconnection) workinggroup. This document is not an Internet Standards Track specification; it is published for informational purposes.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.