Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection
RFC 7975

Document Type RFC - Proposed Standard (October 2016; No errata)
Last updated 2016-10-13
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Kevin Ma
Shepherd write-up Show (last changed 2016-01-28)
IESG IESG state RFC 7975 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to "Kevin J. Ma" <kevin.j.ma@ericsson.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)             B. Niven-Jenkins, Ed.
Request for Comments: 7975                                         Nokia
Category: Standards Track                        R. van Brandenburg, Ed.
ISSN: 2070-1721                                                      TNO
                                                            October 2016

               Request Routing Redirection Interface for
             Content Delivery Network (CDN) Interconnection

Abstract

   The Request Routing interface comprises (1) the asynchronous
   advertisement of footprint and capabilities by a downstream Content
   Delivery Network (CDN) that allows an upstream CDN to decide whether
   to redirect particular user requests to that downstream CDN; and (2)
   the synchronous operation of an upstream CDN requesting whether a
   downstream CDN is prepared to accept a user request and of a
   downstream CDN responding with how to actually redirect the user
   request.  This document describes an interface for the latter part,
   i.e., the CDNI Request Routing Redirection interface.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7975.

Niven-Jenkins, et al.        Standards Track                    [Page 1]
RFC 7975               Request Routing Redirection          October 2016

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Interface Function and Operation Overview . . . . . . . . . .   4
   4.  HTTP-Based Interface for the Redirection Interface  . . . . .   6
     4.1.  Information Passed in RI Requests and Responses . . . . .   8
     4.2.  JSON Encoding of RI Requests and Responses  . . . . . . .   9
     4.3.  MIME Media Types Used by the RI Interface . . . . . . . .  11
     4.4.  DNS Redirection . . . . . . . . . . . . . . . . . . . . .  12
       4.4.1.  DNS Redirection Requests  . . . . . . . . . . . . . .  12
       4.4.2.  DNS Redirection Responses . . . . . . . . . . . . . .  14
     4.5.  HTTP Redirection  . . . . . . . . . . . . . . . . . . . .  17
       4.5.1.  HTTP Redirection Requests . . . . . . . . . . . . . .  17
       4.5.2.  HTTP Redirection Responses  . . . . . . . . . . . . .  19
     4.6.  Cacheability and Scope of Responses . . . . . . . . . . .  22
     4.7.  Error Responses . . . . . . . . . . . . . . . . . . . . .  24
     4.8.  Loop Detection and Prevention . . . . . . . . . . . . . .  28
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  29
     5.1.  Authentication, Authorization, Confidentiality, and
           Integrity Protection  . . . . . . . . . . . . . . . . . .  29
     5.2.  Privacy . . . . . . . . . . . . . . . . . . . . . . . . .  30
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  31
     6.1.  CDNI Payload Type Parameter Registrations . . . . . . . .  31
       6.1.1.  CDNI RI Redirection Request Payload Type  . . . . . .  31
       6.1.2.  CDNI RI Redirection Response Payload Type . . . . . .  31
     6.2.  RI Error Response Registry  . . . . . . . . . . . . . . .  31
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  32
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  32
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  34
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  34
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  35
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  35

Niven-Jenkins, et al.        Standards Track                    [Page 2]
Show full document text