draft-ietf-cdni-problem-statement-02.txt   draft-ietf-cdni-problem-statement-03.txt 
Network Working Group B. Niven-Jenkins Network Working Group B. Niven-Jenkins
Internet-Draft Velocix (Alcatel-Lucent) Internet-Draft Velocix (Alcatel-Lucent)
Intended status: Informational F. Le Faucheur Intended status: Informational F. Le Faucheur
Expires: July 19, 2012 Cisco Expires: July 24, 2012 Cisco
N. Bitar N. Bitar
Verizon Verizon
January 16, 2012 January 21, 2012
Content Distribution Network Interconnection (CDNI) Problem Statement Content Distribution Network Interconnection (CDNI) Problem Statement
draft-ietf-cdni-problem-statement-02 draft-ietf-cdni-problem-statement-03
Abstract Abstract
Content Delivery Networks (CDNs) provide numerous benefits: reduced Content Delivery Networks (CDNs) provide numerous benefits: reduced
delivery cost for cacheable content, improved quality of experience delivery cost for cacheable content, improved quality of experience
for End Users and increased robustness of delivery. For these for End Users and increased robustness of delivery. For these
reasons they are frequently used for large-scale content delivery. reasons they are frequently used for large-scale content delivery.
As a result, existing CDN providers are scaling up their As a result, existing CDN Providers are scaling up their
infrastructure and many Network Service Providers (NSPs) are infrastructure and many Network Service Providers (NSPs) are
deploying their own CDNs. It is generally desirable that a given deploying their own CDNs. It is generally desirable that a given
content item can be delivered to an End User regardless of that End content item can be delivered to an End User regardless of that End
User's location or attachment network. This creates a requirement User's location or attachment network. This creates a requirement
for interconnecting standalone CDNs so they can interoperate as an for interconnecting standalone CDNs so they can interoperate as an
open content delivery infrastructure for the end-to-end delivery of open content delivery infrastructure for the end-to-end delivery of
content from Content Service Providers (CSPs) to End Users. However, content from Content Service Providers (CSPs) to End Users. However,
no standards or open specifications currently exist to facilitate no standards or open specifications currently exist to facilitate
such CDN interconnection. such CDN interconnection.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 19, 2012. This Internet-Draft will expire on July 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 9, line 41 skipping to change at page 9, line 41
multiple affiliate NSPs. These NSPs typically operate independent multiple affiliate NSPs. These NSPs typically operate independent
CDNs. As they evolve their services (e.g. for seamless support of CDNs. As they evolve their services (e.g. for seamless support of
content services to nomadic users across affiliate NSPs) there is a content services to nomadic users across affiliate NSPs) there is a
need for interconnection of these CDNs, that represents a first use need for interconnection of these CDNs, that represents a first use
case for CDNI. However there are no open specifications, nor common case for CDNI. However there are no open specifications, nor common
best practices, defining how to achieve such CDN interconnection. best practices, defining how to achieve such CDN interconnection.
CSPs have a desire to be able to get (some of) their content to very CSPs have a desire to be able to get (some of) their content to very
large number of End Users and/or over many/all geographies and/or large number of End Users and/or over many/all geographies and/or
with a high quality of experience, all without having to maintain with a high quality of experience, all without having to maintain
direct business relationships with many different CDN providers (or direct business relationships with many different CDN Providers (or
having to extend their own CDN to a large number of locations). Some having to extend their own CDN to a large number of locations). Some
NSPs are considering interconnecting their respective CDNs (as well NSPs are considering interconnecting their respective CDNs (as well
as possibly over-the-top CDNs) so that this collective infrastructure as possibly over-the-top CDNs) so that this collective infrastructure
can address the requirements of CSPs in a cost effective manner. can address the requirements of CSPs in a cost effective manner.
This represents a second use case for CDNI. In particular, this This represents a second use case for CDNI. In particular, this
would enable the CSPs to benefit from on-net delivery (i.e. within would enable the CSPs to benefit from on-net delivery (i.e. within
the Network Service Provider's own network/CDN footprint) whenever the Network Service Provider's own network/CDN footprint) whenever
possible and off-net delivery otherwise, without requiring the CSPs possible and off-net delivery otherwise, without requiring the CSPs
to maintain direct business relationships with all the CDNs involved to maintain direct business relationships with all the CDNs involved
in the delivery. Again, for this requirement, CDN providers (NSPs or in the delivery. Again, for this requirement, CDN Providers (NSPs or
over-the-top CDN operators) are faced with a lack of open over-the-top CDN operators) are faced with a lack of open
specifications and best practices. specifications and best practices.
NSPs have often deployed CDNs as specialized cost-reduction projects NSPs have often deployed CDNs as specialized cost-reduction projects
within the context of a particular service or environment, some NSPs within the context of a particular service or environment, some NSPs
operate separate CDNs for separate services. For example, there may operate separate CDNs for separate services. For example, there may
be a CDN for managed IPTV service delivery, a CDN for web-TV delivery be a CDN for managed IPTV service delivery, a CDN for web-TV delivery
and a CDN for video delivery to Mobile terminals. As NSPs integrate and a CDN for video delivery to Mobile terminals. As NSPs integrate
their service portfolio, there is a need for interconnecting these their service portfolio, there is a need for interconnecting these
CDNs, representing a third use case for CDNI. Again, NSPs face the CDNs, representing a third use case for CDNI. Again, NSPs face the
problem of lack of open interfaces for CDN interconnection. problem of lack of open interfaces for CDN interconnection.
For operational reasons (e.g. disaster, flash crowd) or commercial For operational reasons (e.g. disaster, flash crowd) or commercial
reasons, an over-the-top CDN may elect to make use of another CDN reasons, an over-the-top CDN may elect to make use of another CDN
(e.g. an NSP CDN with on-net Surrogates for a given footprint) for (e.g. an NSP CDN with on-net Surrogates for a given footprint) for
serving a subset of the user requests (e.g. requests from users serving a subset of the user requests (e.g. requests from users
attached to that NSP), which results in a fourth use case for CDNI. attached to that NSP), which results in a fourth use case for CDNI.
Again, for this requirement, CDN providers (over-the-top CDN Again, for this requirement, CDN Providers (over-the-top CDN
providers or NSPs) are faced with a lack of open specifications and Providers or NSPs) are faced with a lack of open specifications and
best practices. best practices.
Use cases for CDN Interconnection are further discussed in Use cases for CDN Interconnection are further discussed in
[I-D.ietf-cdni-use-cases]. [I-D.ietf-cdni-use-cases].
3. CDN Interconnection Model & Problem Area for IETF 3. CDN Interconnection Model & Problem Area for IETF
Interconnecting CDNs involves interactions among multiple different Interconnecting CDNs involves interactions among multiple different
functions and components that form each CDN. Only some of those functions and components that form each CDN. Only some of those
require standardization. This section discusses the problem area for require standardization. This section discusses the problem area for
skipping to change at page 26, line 40 skipping to change at page 26, line 40
[I-D.bertrand-cdni-experiments] [I-D.bertrand-cdni-experiments]
Bertrand, G., Faucheur, F., and L. Peterson, "Content Bertrand, G., Faucheur, F., and L. Peterson, "Content
Distribution Network Interconnection (CDNI) Experiments", Distribution Network Interconnection (CDNI) Experiments",
draft-bertrand-cdni-experiments-01 (work in progress), draft-bertrand-cdni-experiments-01 (work in progress),
August 2011. August 2011.
[I-D.ietf-cdni-use-cases] [I-D.ietf-cdni-use-cases]
Gilles, B., Emile, S., Watson, G., Burbridge, T., Eardley, Gilles, B., Emile, S., Watson, G., Burbridge, T., Eardley,
P., and K. Ma, "Use Cases for Content Delivery Network P., and K. Ma, "Use Cases for Content Delivery Network
Interconnection", draft-ietf-cdni-use-cases-01 (work in Interconnection", draft-ietf-cdni-use-cases-02 (work in
progress), December 2011. progress), January 2012.
[I-D.jenkins-alto-cdn-use-cases] [I-D.jenkins-alto-cdn-use-cases]
Niven-Jenkins, B., Watson, G., Bitar, N., Medved, J., and Niven-Jenkins, B., Watson, G., Bitar, N., Medved, J., and
S. Previdi, "Use Cases for ALTO within CDNs", S. Previdi, "Use Cases for ALTO within CDNs",
draft-jenkins-alto-cdn-use-cases-01 (work in progress), draft-jenkins-alto-cdn-use-cases-01 (work in progress),
June 2011. June 2011.
[MPEG-DASH] [MPEG-DASH]
"Information technology - MPEG systems technologies - Part "Information technology - MPEG systems technologies - Part
6: Dynamic adaptive streaming over HTTP (DASH), (DIS 6: Dynamic adaptive streaming over HTTP (DASH), (DIS
 End of changes. 9 change blocks. 
11 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/