CDNI interfaces update for HTTPS delegation

When content is delivered over HTTPS using one or more CDNs along the path, credential management is required. This is specifically required when an entity delegates delivery of encrypted content to another trusted entity. This document presents updates needed in CDNI Control and Metadata interfaces to setup HTTPS delegation between an uCDN and dCDN. Several delegation methods are currently proposed within several IETF working groups (refer to for an overview of delegation works ongoing at the IETF). They specify separately the provisioning of their credentials. This document specifies an update to the CDNI control / Triggers and Metadata interfaces to support these methods. Furthermore, it includes a proposal of registry to enable the adding of new methods in the future. Section 2 is about terminology used in this document. Section 3 presents delegation methods specified at the IETF. Section 4 introduces a secured delegation object for CDNI. Section 5 addresses the delegation methods objects. Section 6 describes simple data types. Section 7 is about an IANA registry for delegation methods. Section 8 raises the security issues. Section 9 opens the discussion.

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

A few methods are currently being proposed at the IETF to handle delegation of HTTPS delivery between entities respecting those constraints (refer to ). Note that many of these methods are still an ongoing work at the IETF within specific WGs. We however anticipate the need to handle delegation in interconnected CDNs and a need to address within the CDNI WG. Despite the types of delegation methods, we need a common framework in CDNI that would provide new requirements on the CDNI interfaces. This document considers the following methods supporting HTTPS delegation and may be used between two or more CDNs with applicable interface support following the CDNI framework, such as the CI/Triggers and Metadata Interface: - Sub-certificates likely to be a TLS WG draft. - Short-term certificates in ACME using STAR API

As expressed in , when HTTPS origin delivery is requested for a specific domain, the delegate, i.e. a dCDN, presents the Origin, or uCDN certificate or even, "delegated_credential" instead of its own certificate at the TLS handshake to the end. When HTTPS delegation has been set for a specific domain, the dCDN should present the Origin or uCDN certificate or "delegated_credential" instead of its own certificate when content delivery is requested. The SecuredDelegation object metadata aims at describing a secured delegation between an uCDN and dCDN by indicating the delegated domain, the start and end of a delegation, and the delegation method used. property: delegateddomain type: HostMatch Description: It describes the delegated hostname, restricted to Hostname. HostMatch is defined in RFC8006 section 4.3.3. This value should match the SAN value in certificates. property: pathpattern type: PathPattern Description: a PathPattern object contains a PathPattern object with a path to match against a resource's URI path in order to trigger the delegation. It is described in RFC8006, 4.1.4. property: timewindow type: TimeWindow Description: Describes delegation start and end times. Timewindow is defined in RFC8006 section 4.2. Property: delegationmethod type: DelegationMethod Description: the delegation method(s) used between a uCDN and a dCDN (ex. Subcerts, short term cert, etc.), as defined in the next section. As an example: a SecuredDelegation object (which contains a TimeWindow object, DelegationMethod and a HostMatch) that only allows the dCDN to deliver content to clients between 09:00 01/01/2000 UTC and 17:00 01/01/2000 UTC:

Such as object shall be conveyed over the CDNI metadata interface.

This section defines the delegation methods objects metadata used by a securedDelegation. Each method consists of 4 phases: Bootstrapping: bootstrapping a secured delegation consists in providing the dCDN with enough parameters to set it up, e.g. ACME servers, Key Servers, etc.. Credential renewal: In case of certificates based approaches, and , there is a need in CDNI to periodically provision and update credentials (certificates or private keys) on the dCDNs for a given delegated domain. Expiration/Revocation: expiration of delegation can occur for multiple reasons: changes in delegation rights, delegation validity is over. In or approaches, the uCDN may implicitly enforce revocation and will prevent any dCDN to renew certificates, or access credentials, when delegation is expired. Logging: Regarding logging aspects, we consider to log usages and errors related to a delegated domain. As an example, CDNI logs include: supported delegation method(s), credentials renewal requests, credential revocation notice, mutual agreement for selected credential method to use, credentials download status for a specific domain, as well as errors, related to credentials transfer, or crypto aspects such as bad cypher suite supports, revoked delegations, etc.

This section defines the AcmeStarDelegationMethod object which describes metadata related to the use of Acme Star API presented in Property: starproxy Type: Endpoint Description: Used to advertise the STAR Proxy to the dCDN. Endpoint type defined in RFC8006, section 4.3.3 Property: acmeserver Type: Endpoint Description: used to advertise the ACME server to the dCDN. Endpoint type is defined in RFC8006, section 4.3.3 Property: credentialslocationuri Type: Link Description: expresses the location of the credentials to be fetched by the dCDN. Link type is as defined in RFC8006, section 4.3.1 Property: periodicity Type: Periodicity description: expresses the credentials renewal periodicity. See next section on simple meta data type. As an example, AcmeStarDelegationMethod object could express the Acme-Star-delegation as the following:

TBD

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

A time value expressed in seconds. 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 5.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 5.2

The CI/T interface and Metadata interface need only to specify mechanisms for delegation between uCDN and dCDN without the use of actual transfer of encrypting keys within the interface messages. The uCDN actions must be limited to in specifying its support for methods it prefers for delegation, actual delegation and revocation of any delegation. The dCDN similarly, must indicate delegation methods it supports. Any subsequent communications enabling delegation must be limited to the agreed delegation method. Additionally, the HTTPS delegation framework must comply with security considerations as specified within RFC 8007 [CDNI Control Interfaces].

More prospective works include: - Keyless SSL / LURK : No WG is currently addressing Lurk. - Out-of-Band encoding redirection Should they be considered as delegation methods for CDNI?