Skip to main content

Content Distribution Network Interconnection (CDNI) Problem Statement

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Ben Niven-Jenkins , François Le Faucheur , Dr. Nabil N. Bitar
Last updated 2011-09-09 (Latest revision 2011-03-13)
Replaced by RFC 6707
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-cdni-problem-statement
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Content Delivery Networks (CDNs) provide numerous benefits: reduced delivery cost for cacheable content, 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 creates a requirement 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 for the IETF with a view towards creating a working group. This working group would work on interoperable and scalable solutions for CDN interconnection.


Ben Niven-Jenkins
François Le Faucheur
Dr. Nabil N. Bitar

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)