datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

ALTO session for CDN Interconnection
draft-stephan-cdni-alto-session-ext-05

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-04-17
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                         E. Stephan
Internet-Draft                                                    Orange
Intended status: Standards Track                              S. Ellouze
Expires: October 19, 2014                                          H-log
                                                          April 17, 2014

                  ALTO session for CDN Interconnection
                 draft-stephan-cdni-alto-session-ext-05

Abstract

   The selection of a downstream CDN by an upstream CDN is based on
   multi-dimensional criteria.  Various protocols, such as BGP or ALTO,
   may be used by a downstream CDN to expose content routing information
   and interconnection preferences to an upstream CDN.  The selection of
   such a protocol is premature as the WG, and especially the Footprint/
   Capabilities Design Team, is currently working on this topic.  So
   this draft does not promote the usage of the ALTO protocol for CDN
   interconnection.  It presents the limitations of the current ALTO
   protocol in the case it would be selected for CDN interconnection.
   It specifies the mechanism for controlling the session initialization
   and for limiting the information exchanged.  Then it discusses the
   need of incremental update and proposes to study the usage of Netconf
   /Yang to provide ALTO server with notifications.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 19, 2014.

Stephan & Ellouze       Expires October 19, 2014                [Page 1]
Internet-Draft              CDNi ALTO session                 April 2014

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  CDN1 views  . . . . . . . . . . . . . . . . . . . . . . .   8
     2.2.  CDN2 views  . . . . . . . . . . . . . . . . . . . . . . .   8
     2.3.  Map Maintenance . . . . . . . . . . . . . . . . . . . . .   9
   3.  Requirements for an ALTO Session for CDNi . . . . . . . . . .   9
     3.1.  ALTO Information Customization  . . . . . . . . . . . . .   9
     3.2.  View download with HTTP GET . . . . . . . . . . . . . . .  10
     3.3.  Initialization of the Session . . . . . . . . . . . . . .  10
     3.4.  Server Discovery  . . . . . . . . . . . . . . . . . . . .  10

[include full document text]