Content Delivery Networks Interconnection (cdni)
------------------------------------------------

Charter
Last Modified: 2011-12-09

Current Status: Active Working Group

Chair(s):
    Richard Woundy  <[email protected]>
    Francois Le Faucheur  <[email protected]>

Transport Area Director(s):
    David Harrington  <[email protected]>
    Wesley Eddy  <[email protected]>

Transport Area Advisor:
    David Harrington  <[email protected]>

Mailing Lists:
    General Discussion:[email protected]
    To Subscribe:      https://www.ietf.org/mailman/listinfo/cdni
    Archive:           http://www.ietf.org/mail-archive/web/cdni/

Description of Working Group:

A Content Delivery Network (CDN) is an infrastructure of network
elements operating at layer 4 through layer 7, arranged for the
efficient distribution and delivery of digital content. Such content
includes, but is not limited to, web pages and images delivered via
HTTP, and streaming of continuous media delivered via HTTP, RTSP, RTMP,
etc. CDNs typically provide services to multiple Content Service
Providers (CSPs).

CDNs provide numerous benefits: a shared platform for multi-service
content delivery, reduced transmission costs 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 of the significant growth in content delivered over IP
networks, existing CDN providers are scaling up their infrastructure and
many Network Service Providers and Enterprise Service Providers are
deploying their own CDNs. Subject to the policy of the CSP, it is
generally desirable that a given item of content can be delivered to an
end user regardless of that end user's location or attachment network.
This creates a need for interconnecting (previously) standalone CDNs so
they can interoperate and collectively behave as a single delivery
infrastructure.

The goal of the CDNI Working Group is to allow the interconnection of
separately administered CDNs in support of the end-to-end delivery of
content from CSPs through multiple CDNs and ultimately to end users (via
their respective User Agents). The CDNI WG aims at delivering a
targeted, deployable solution in a short timeframe (18-24 months) as
needed by the industry. It is expected that the CDNI interfaces will be
realized using existing IETF protocols for transport and message
exchange, and using existing object notation grammars/languages for the
definition of CDNI objects and semantics. In the event that protocol
extensions or new protocols are deemed necessary by the WG, the WG will
recharter.

The working group will focus on the following items:

- A "problem statement" document providing a description of the problem
 and a common terminology.

- A "use case" document describing scenarios for usage and applications
 of the CDNI solution and protocols.

- A "framework" document providing a description of the different
 components of the CDNI architecture and how they interact with one
 another. This document will also include a "threat analysis"
 discussing the security concerns and threats, the trust model and
 privacy issues specific to CDNI.

- A "requirements" document. This document lists the requirements for
 the CDNI architecture and the CDNI interfaces. In particular, this
 document will focus on identifying a reasonable set of more urgent and
 important requirements that will be addressed in the initial set of
 CDNI protocols and solutions produced by the working group. This
 document will list the requirements stemming from the threat analysis
 and to be met by each of the CDNI interfaces.

- A specification of the "CDNI request-routing interface". This
 interface will allow an upstream CDN request routing system to obtain
 from the downstream CDN the information necessary to perform request
 redirection.

- A specification of the "CDNI metadata interface". This interface will
 allow the CDNs to exchange content distribution metadata of inter-CDN
 scope. Content distribution metadata refers to the subset of content
 metadata that is relevant to the distribution of the content and
 therefore is to be processed by CDNs (for example, this may include
 information enabling: content acquisition, geo-blocking, enforcement
 of availability windows or access control).

- A specification of the "CDNI logging interface". This interface will
 allow CDN logging systems to exchange logging information associated
 with actions that are relevant across CDNs (such as content
 distribution, content delivery and content routing actions) for
 purposes of accounting, analytics, monitoring, etc.

- A specification of the "CDNI control interface". In particular, this
 interface will allow an upstream CDN to remove or invalidate content
 in a downstream CDN.

The WG will discuss and address the security, management and operational
issues specific to CDNI, inside the above documents and specifications.

The working group will only define solutions for aspects of the CDN
Interconnection problem space that require direct communication or
interoperation between CDNs.

In particular, the WG will not define:

- New session, transport or network protocols.

- New protocols for delivering content from a CDN to an End User/User
 Agent.

- New protocols for ingestion of content or metadata between a CSP and a
 CDN.

- New protocols for acquiring content across CDNs.

- Protocols and algorithms for intra-CDN operations.

- Support for Transparent Caching across CDNs.

- New applications consuming CDNI logs.

- Digital Right Management (DRM) mechanisms.

The CDNI WG will work with other IETF WGs to assess, and where
appropriate, leverage protocols developed by those WGs, in order to
realize the CDNI requirements and CDNI interfaces. For example, the WG
may assess the suitability of the ALTO protocol as a protocol to enable
downstream CDNs to exchange information which may aid an upstream CDN
with making CDNI request routing decisions. The CDNI WG will also
coordinate with relevant groups outside the IETF such as UltraViolet.

Goals and Milestones:

  Dec 2011       Submit CDNI problem statement to IESG as Informational

  Mar 2012       Submit CDNI use cases to IESG as Informational

  Jun 2012       Submit CDNI framework to IESG as Informational

  Jun 2012       Submit CDNI requirements to IESG as Informational

  Dec 2012       Submit specification of the CDNI Request Routing interface to
               IESG as Proposed Standard

  Dec 2012       Submit specification of the CDNI Logging interface to IESG as
               Proposed Standard

  Dec 2012       Submit specification of the CDNI Control interface to IESG as
               proposed Standard

  Jun 2013       Submit specification of the CDNI Metadata Distribution
               interface to IESG as Proposed Standard

  Jun 2013       Recharter or dissolve


Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Sep 2011 Jan 2012   <draft-ietf-cdni-problem-statement-02.txt>
               Content Distribution Network Interconnection (CDNI) Problem
               Statement

Sep 2011 Dec 2011   <draft-ietf-cdni-requirements-02.txt>
               Content Distribution Network Interconnection (CDNI)
               Requirements

Sep 2011 Dec 2011   <draft-ietf-cdni-use-cases-01.txt>
               Use Cases for Content Delivery Network Interconnection

Request For Comments:

 None to date.

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.