datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Request Routing and Content Acquisition
draft-chen-cdni-rr-content-acquisition-01

Active Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2012-12-24
Intended RFC status: (None)
Other versions: plain text, pdf, html

Document shepherd:(None)
Shepherd writeup

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

CDNI                                                             G. Chen
Internet-Draft                                             China Telecom
Intended status: Informational                                     M. Li
Expires: June 28, 2013                                            H. Xia
                                                         ZTE Corporation
                                                                J. Liang
                                                           China Telecom
                                                       December 25, 2012

                Request Routing and Content Acquisition
               draft-chen-cdni-rr-content-acquisition-01

Abstract

   This document illustrates the details of an alternative method that
   can be used to provide request routing and content acquisition
   services.

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 June 28, 2013.

Copyright Notice

   Copyright (c) 2012 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

Chen, et al.              Expires June 28, 2013                 [Page 1]
Internet-Draft   Request Routing and Content Acquisition   December 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  CDN Interconnection Framework  . . . . . . . . . . . . . .  3
     2.2.  UniContentID . . . . . . . . . . . . . . . . . . . . . . .  5
     2.3.  Use Case Description . . . . . . . . . . . . . . . . . . .  7
       2.3.1.  Request Routing and Content Delivery . . . . . . . . .  7
       2.3.2.  Content Acquisition  . . . . . . . . . . . . . . . . .  9
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 10
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Chen, et al.              Expires June 28, 2013                 [Page 2]
Internet-Draft   Request Routing and Content Acquisition   December 2012

1.  Introduction

   The scope of CDNi work is described in [I-D.ietf-cdni-problem-
   statement]:

   - As illustrated in Figure 1, the acquisition of content between
   interconnected CDNs is out of scope of CDNi, which deserves some
   additional explanation.  The consequence of such a decision is that
   the CDNi problem space described in this document only focuses on
   defining the CDNi control plane; and the CDNi data plane (i.e., the
   acquisition and distribution of the actual content objects) is out of
   scope.

   It can be implied that the delivery process of the actual content
   objects requested by the end user from uCDN to dCDN is outside the
   scope of CDNi work.  However, in the cache miss case, i.e., the dCDN
   receives end user's request redirected by the uCDN and fails in
   locating the corresponding content in the cache, the dCDN needs to
   determine toward which uCDN it should initiate the content
   acquisition procedure.  And this should be included in scope of CDNi.

   This document illustrates the mechanism of request routing and