URI Signing for CDN Interconnection (CDNI)
draft-ietf-cdni-uri-signing-10

Document Type Active Internet-Draft (cdni WG)
Last updated 2016-10-04
Replaces draft-leung-cdni-uri-signing
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Revised I-D Needed - Issue raised by WGLC
Document shepherd Kevin Ma
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alexey Melnikov
Send notices to (None)
CDNI                                                  R. van Brandenburg
Internet-Draft                                                       TNO
Intended status: Standards Track                                K. Leung
Expires: April 7, 2017                               Cisco Systems, Inc.
                                                               P. Sorber
                                            Comcast Cable Communications
                                                               M. Miller
                                                     Cisco Systems, Inc.
                                                         October 4, 2016

               URI Signing for CDN Interconnection (CDNI)
                     draft-ietf-cdni-uri-signing-10

Abstract

   This document describes how the concept of URI signing supports the
   content access control requirements of CDNI and proposes a URI
   signing method as a JSON Web Token (JWT) [RFC7519] profile.

   The proposed URI signing method specifies the information needed to
   be included in the URI to transmit the signed JWT as well as the
   claims needed by the signed JWT to authorize a UA.  The mechanism
   described can be used both in CDNI and single CDN scenarios.

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 April 7, 2017.

Copyright Notice

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

van Brandenburg, et al.   Expires April 7, 2017                 [Page 1]
Internet-Draft              CDNI URI Signing                October 2016

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Background and overview on URI Signing  . . . . . . . . .   4
     1.3.  CDNI URI Signing Overview . . . . . . . . . . . . . . . .   5
     1.4.  URI Signing in a non-CDNI context . . . . . . . . . . . .   7
   2.  JWT Format and Processing Requirements  . . . . . . . . . . .   7
     2.1.  JWT Claims  . . . . . . . . . . . . . . . . . . . . . . .   8
       2.1.1.  URI Container Forms . . . . . . . . . . . . . . . . .  10
         2.1.1.1.  URI Simple Container (uri:) . . . . . . . . . . .  11
         2.1.1.2.  URI Pattern Container (uri-pattern:)  . . . . . .  11
         2.1.1.3.  URI Regular Expression Container (uri-regex:) . .  12
   3.  Relationship with CDNI Interfaces . . . . . . . . . . . . . .  12
     3.1.  CDNI Control Interface  . . . . . . . . . . . . . . . . .  12
     3.2.  CDNI Footprint & Capabilities Advertisement Interface . .  12
     3.3.  CDNI Request Routing Redirection Interface  . . . . . . .  13
     3.4.  CDNI Metadata Interface . . . . . . . . . . . . . . . . .  13
     3.5.  CDNI Logging Interface  . . . . . . . . . . . . . . . . .  14
   4.  URI Signing Message Flow  . . . . . . . . . . . . . . . . . .  15
     4.1.  HTTP Redirection  . . . . . . . . . . . . . . . . . . . .  16
     4.2.  DNS Redirection . . . . . . . . . . . . . . . . . . . . .  18
   5.  HTTP Adaptive Streaming . . . . . . . . . . . . . . . . . . .  21
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
     6.1.  CDNI Payload Type . . . . . . . . . . . . . . . . . . . .  21
       6.1.1.  CDNI UriSigning Payload Type  . . . . . . . . . . . .  21
     6.2.  CDNI Logging Record Type  . . . . . . . . . . . . . . . .  22
       6.2.1.  CDNI Logging Record Version 2 for HTTP  . . . . . . .  22
     6.3.  CDNI Logging Field Names  . . . . . . . . . . . . . . . .  22
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
Show full document text