CDNI interfaces update for HTTPS delegation
draft-fieau-cdni-interfaces-https-delegation-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      F. Fieau, Ed.
Internet-Draft                                                E. Stephan
Intended status: Standards Track                                  Orange
Expires: September 14, 2017                                    S. Mishra
                                                                 Verizon
                                                          March 13, 2017

              CDNI interfaces update for HTTPS delegation
            draft-fieau-cdni-interfaces-https-delegation-00

Abstract

   Content delivery includes one or more CDNs and in many instances
   involves cascaded delegation when handling encrypted data.  The
   delivery of such content over HTTPS though raises credential
   management issues.  Two models of HTTPS delegation can be considered:
   direct delegation, and "cascaded" delegation.  While the first model
   of delegation is addressed by most of the work at the IETF, in the
   latter case, it is up to downstream CDN(s) delivering the content to
   an end-user to present legacy credentials of either the origin or of
   the upstream CDN which delegated the delivery to the aforementioned
   dCDN.  This document presents updates needed in CDNI Control and
   Metadata interfaces to setup HTTPS delegation between an uCDN and
   dCDN.

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 September 14, 2017.

Copyright Notice

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

Fieau, et al.          Expires September 14, 2017               [Page 1]
Internet-Draft      CDNI update for HTTPS delegation          March 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  HTTPS Delegation Models . . . . . . . . . . . . . . . . . . .   3
   4.  Known delegation methods  . . . . . . . . . . . . . . . . . .   4
   5.  Delegation definition . . . . . . . . . . . . . . . . . . . .   6
   6.  Credentials management  . . . . . . . . . . . . . . . . . . .   7
   7.  Handling delegation expiration  . . . . . . . . . . . . . . .   7
   8.  Logging delegation related data . . . . . . . . . . . . . . .   8
   9.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Security considerations . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In most cases, content is delivered over HTTP or HTTPS using one and
   more CDNs along the delivery path in the direction of end-user.  The
   delivery of the content over HTTPS raises credential management
   issues.  This document presents updates needed in CDNI Control and
   Metadata interfaces to setup HTTPS delegation between an uCDN and
   dCDN.

   It is up to the downstream CDN which delivers the content to the end-
   user to present credentials of either the origin or of the upstream
   CDN which delegated the delivery to the aforementioned dCDN.  The
   domain of the certificate presented to the end-user must match the
   domain delivering content.  However, in a model when an entity other
   than the origin has been delegated to serve secured content on behalf
   of the certificate owner, then in such case of "cascaded" delegation,
Show full document text