[secdir] [new-work] WG Review: Content Delivery Networks Interconnection (cdni)

The IESG <iesg@ietf.org> Fri, 22 November 2013 18:12 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 876E31AE171; Fri, 22 Nov 2013 10:12:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1385143957; bh=vBm5uwmlLcpeT1H+Hb0vDe5cDYco5q90/UcqwjpraQs=; h=MIME-Version:From:To:Message-ID:Date:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=doDSeEAhBDhCgzuY9mRQE7fbDxZ0NJEWYynnyuwH4z8or35A+Mm2clzGEBWFDN53l C8a2Jm6saN81+Y0AIOySOP4zntD4jbaX+Jndr/noAjohc/ySuM2LCr7eZy4Lq9N6as opGnHCzr/44GObEoRsEk/VKyZEnKFmHFQgvtkMo0=
X-Original-To: new-work@ietfa.amsl.com
Delivered-To: new-work@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C88A91AE19F; Fri, 22 Nov 2013 10:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id s477Bh2Ifibp; Fri, 22 Nov 2013 10:12:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9B71AE171; Fri, 22 Nov 2013 10:12:33 -0800 (PST)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: new-work@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131122181233.16611.44151.idtracker@ietfa.amsl.com>
Date: Fri, 22 Nov 2013 10:12:33 -0800
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.15
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
X-Mailman-Approved-At: Mon, 25 Nov 2013 08:03:40 -0800
Subject: [secdir] [new-work] WG Review: Content Delivery Networks Interconnection (cdni)
X-BeenThere: secdir@ietf.org
Reply-To: iesg@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2013 18:12:37 -0000

The Content Delivery Networks Interconnection (cdni) working group in the
Transport Area of the IETF is undergoing rechartering. The IESG has not
made any determination yet. The following draft charter was submitted,
and is provided for informational purposes only. Please send your
comments to the IESG mailing list (iesg at ietf.org) by 2013-12-02.

Content Delivery Networks Interconnection (cdni)
Current Status: Active WG

  Daryl Malas <d.malas@cablelabs.com>
  Francois Le Faucheur <flefauch@cisco.com>

Assigned Area Director:
  Spencer Dawkins <spencerdawkins.ietf@gmail.com>

Mailing list
  Address: cdni@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/cdni
  Archive: http://www.ietf.org/mail-archive/web/cdni/


  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
  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
  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 
  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
  their respective User Agents). The CDNI WG aims at delivering a 
  targeted, deployable solution in a short timeframe 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

  The working group will focus on the following items:
  - 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
    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 "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 specification of the "CDNI Request Routing Redirection interface".
    interface will allow an upstream CDN Request Routing system to obtain

    from the downstream CDN the information necessary to perform request 
    redirection. It is actually a logical bundling of two separate but
   *  Footprint & Capability Advertisement interface: Asynchronous 
      operations to exchange routing information (e.g., the network 
      footprint and capabilities served by a given CDN) that enables CDN 
      selection for subsequent user requests; and       
   *  Request Routing Redirection interface: Synchronous operations to
      select a delivery CDN (surrogate) for a given user request.
  - 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.

  - A specification for "CDNI URI Signing". This document will specify a 
    mechanism that allows interconnected CDNs to support access control 
    by signing content URIs. This may involve extensions to the CDNI 
    interfaces (e.g. CDNI Metadata interface, CDNI Logging interface).
  The WG will discuss and address the security, management and
  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 
  - New protocols for ingestion of content or metadata between a CSP and
  - 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, if and where 

  Done     - Submit CDNI problem statement to IESG as Informational
  Done     - Submit CDNI use cases to IESG as Informational
  Sep 2013 - Submit CDNI requirements to IESG as Informational
  Dec 2013 - Submit CDNI framework to IESG as Informational
  Dec 2013 - Submit specification of the CDNI Logging interface to IESG
as Proposed Standard
  Dec 2013 - Submit specification of the CDNI Metadata interface to IESG
as Proposed Standard
  Apr 2014 - Submit specification of the CDNI Control interface to IESG
as proposed Standard
  Apr 2014 - Submit specification of the CDNI Request Routing Redirection
interface to IESG as Proposed Standard
  Sep 2014 - Submit specification of the CDNI Footprint & Capabilities
Advertisement interface to IESG as Proposed Standard
  Sep 2014 - Submit specification of URI Signing for CDNI to IESG as
Proposed Standard
  Oct 2014 - Recharter or dissolve

new-work mailing list