CDNI extensions for HTTPS delegation

Content delivery over HTTPS using one or more CDNs along the path requires credential management. This specifically applies when an entity delegates delivery of encrypted content to another trusted entity. Several delegation methods are currently proposed within different IETF working groups. They specify different methods for provisioning HTTPS delivery credentials. This document extends the CDNI Metadata interface to setup HTTPS delegation between an upstream CDN (uCDN) and downstream CDN (dCDN). Furthermore, it includes a proposal of IANA registry to enable the adding of new methods. Section 2 is about terminology used in this document. Section 3 presents delegation methods specified at the IETF. Section 4 addresses the extension for handling HTTPS delegation in CDNI. Section 5 describes simple data types. Section 6 is about an IANA registry for delegation methods. Section 7 raises the security issues.

This document uses terminology from CDNI framework documents such as: CDNI framework document , CDNI requirements and CDNI interface specifications documents: CDNI Metadata interface and CDNI Control interface / Triggers .

There are currently two Internet drafts within the TLS and ACME working groups adopted to handle delegation of HTTPS delivery between entities. This I-D proposes standardizing HTTPS delegation between the entities using CDNI interfaces. This document considers the following two I-D that supports HTTPS delegation: - Sub-certificates - Short-term certificates in ACME using STAR API

This section defines a CDNI extension to the current Metadata interface model that allows bootstrapping delegation methods between a uCDN and a delegate dCDN.

This extension reuses PathMetadata object, as defined in , by adding new "Delegation methods" objects as specified in the following sections. This allows to explicitly indicate support for the given method. Therefore, the presence (or lack thereof) of an AcmeStarDelegationMethod, SubcertsDelegationMethod, and/or further delegation methods, imply support (or lack thereof) for the given method. Example: The PathMatch object can reference a path-metadata that points at the delegation information. Delegation metadata are added to PathMetaData object.

The existence of the "MI.AcmeStarDelegationMethod" object in a PathMetaData Object shall enable the use of one of the AcmeStarDelegation Methods, chosen by the delegate. The delegation method will be activated for the set of Path defined in the PathMatch. See next section for more details about delegation methods metadata specification.

This section defines the delegation methods objects metadata. Those metadata allows bootstrapping a secured delegatioin by providing the dCDN with the needed parameters to set it up.

This section defines the AcmeStarDelegationMethod object which describes metadata related to the use of Acme Star API presented in As expressed in , when an origin has set a delegation to a specific domain (i.e. dCDN), the dCDN should present to the end-user client, a short-term certificate bound to the master certificate. Property: starproxy Description: Used to advertise the STAR Proxy to the dCDN. Endpoint type defined in RFC8006, section 4.3.3 Type: Endpoint Mandatory-to-Specify: Yes Property: acmeserver Description: used to advertise the ACME server to the dCDN. Endpoint type is defined in RFC8006, section 4.3.3 Type: Endpoint Mandatory-to-Specify: Yes Property: credentialslocationuri Description: expresses the location of the credentials to be fetched by the dCDN. Link type is as defined in RFC8006, section 4.3.1 Type: Link Mandatory-to-Specify: Yes Property: periodicity Description: expresses the credentials renewal periodicity. See next section on simple meta data type. Type: Periodicity Mandatory-to-Specify: Yes As an example, AcmeStarDelegationMethod object could express the Acme-Star delegation as the following:

This section defines the SubcertsDelegationMethod object which describes metadata related to the use of Subcerts as presented in As expressed in , when an origin has set a delegation to a specific domain (i.e. dCDN), the dCDN should present the Origin or uCDN certificate or "delegated_credential" during the TLS handshake to the end-user client application, instead of its own certificate. Property: credentialsdelegatingentity Description: Endpoint ID (IP) of the delegating Entity (uCDN). Endpoint type defined in RFC8006, section 4.3.3 Type: Endpoint Mandatory-to-Specify: Yes Property: credentialrecipiententity Description: Endpoint ID (IP) of the delegated entity (dCDN). Endpoint type is defined in RFC8006, section 4.3.3 Type: Endpoint Mandatory-to-Specify: Yes Property: credentialslocationuri Description: expresses the location of the credentials to be fetched by the dCDN. Link type is as defined in RFC8006, section 4.3.1 Type: Link Mandatory-to-Specify: Yes Property: periodicity Description: expresses the credentials renewal periodicity. See next section on simple meta data type. Type: Periodicity Mandatory-to-Specify: Yes As an example, when a uCDN has delegated HTTPS delivery to dCDN, a SubcertsDelegationMethod object can express the SubCerts delegation as the following:

This section describes the simple data types that are used for properties for objects in this document.

A time value expressed in seconds to indicate a periodicity. Type: Integer

This document requests the registration of the following entries under the "CDNI Payload Types" registry hosted by IANA regarding “CDNI delegation”:

Purpose: The purpose of this Payload Type is to distinguish AcmeStarDelegationMethod MI objects (and any associated capability advertisement) Interface: MI/FCI Encoding: see Section 4.2.1

Purpose: The purpose of this Payload Type is to distinguish SubcertsDelegationMethod MI objects (and any associated capability advertisement) Interface: MI/FCI Encoding: see Section 4.2.2

Extensions proposed here do not change Security Considerations as outlined in the CDNI Metadata and Footprint and Capabilities RFCs .