datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Content Distribution Network Interconnection (CDNI) Problem Statement
draft-ietf-cdni-problem-statement-08

RFC
Document Stream: IETF
Last updated: 2012-06-25
Replaces: draft-jenkins-cdni-problem-statement
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (cdni)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6707
IANA Action State: No IC 
On agenda of 2012-07-05 IESG telechat
Responsible AD: Martin Stiemerling
IESG Note: Richard Woundy (richard_woundy@cable.comcast.com) is the Document Shepherd.
Send notices to: cdni-chairs@tools.ietf.org, draft-ietf-cdni-problem-statement@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-cdni-problem-statement.

Abstract:
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.

Authors:
Ben Niven-Jenkins <ben@velocix.com>
Francois Le Faucheur <flefauch@cisco.com>
Nabil Bitar <nabil.bitar@verizon.com>

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