RFC 6707 on Content Distribution Network Interconnection (CDNI) Problem Statement

rfc-editor@rfc-editor.org Wed, 26 September 2012 03:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 05F5821F86BA; Tue, 25 Sep 2012 20:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.305
X-Spam-Status: No, score=-102.305 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FmIYfmqIURTV; Tue, 25 Sep 2012 20:22:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3F78A21F86AD; Tue, 25 Sep 2012 20:22:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 40935B1E002; Tue, 25 Sep 2012 20:18:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6707 on Content Distribution Network Interconnection (CDNI) Problem Statement
From: rfc-editor@rfc-editor.org
Message-Id: <20120926031844.40935B1E002@rfc-editor.org>
Date: Tue, 25 Sep 2012 20:18:44 -0700
Cc: cdni@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 03:22:44 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6707

        Title:      Content Distribution Network Interconnection (CDNI) 
                    Problem Statement 
        Author:     B. Niven-Jenkins, F. Le Faucheur,
                    N. Bitar
        Status:     Informational
        Stream:     IETF
        Date:       September 2012
        Mailbox:    ben@velocix.com, 
        Pages:      32
        Characters: 75060
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cdni-problem-statement-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6707.txt

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.

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

This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC