idnits 2.17.1 draft-ietf-cdni-interfaces-https-delegation-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 29, 2019) is 1793 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-11) exists of draft-ietf-acme-star-05 == Outdated reference: A later version (-15) exists of draft-ietf-tls-subcerts-03 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CDNI Working Group F. Fieau, Ed. 3 Internet-Draft E. Stephan 4 Intended status: Standards Track Orange 5 Expires: November 30, 2019 S. Mishra 6 Verizon 7 May 29, 2019 9 CDNI extensions for HTTPS delegation 10 draft-ietf-cdni-interfaces-https-delegation-01 12 Abstract 14 The delivery of content over HTTPS involving multiple CDNs raises 15 credential management issues. This document proposes extensions in 16 CDNI Control and Metadata interfaces to setup HTTPS delegation from 17 an Upstream CDN (uCDN) to a Downstream CDN (dCDN). 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on November 30, 2019. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Known delegation methods . . . . . . . . . . . . . . . . . . 3 56 4. Extending the CDNI metadata model . . . . . . . . . . . . . . 3 57 4.1. Extension to PathMetadata object . . . . . . . . . . . . 3 58 4.2. Delegation methods . . . . . . . . . . . . . . . . . . . 5 59 4.2.1. AcmeStarDelegationMethod object . . . . . . . . . . . 5 60 4.2.2. SubcertsDelegationMethod object . . . . . . . . . . . 6 61 5. Metadata Simple Data Type Descriptions . . . . . . . . . . . 7 62 5.1. Periodicity . . . . . . . . . . . . . . . . . . . . . . . 7 63 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 7 64 6.1. CDNI MI AcmeStarDelegationMethod Payload Type . . . . . . 7 65 6.2. CDNI MI SubCertsDelegationMethod Payload Type . . . . . . 8 66 7. Security considerations . . . . . . . . . . . . . . . . . . . 8 67 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 69 8.2. Informative References . . . . . . . . . . . . . . . . . 8 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 72 1. Introduction 74 Content delivery over HTTPS using one or more CDNs along the path 75 requires credential management. This specifically applies when an 76 entity delegates delivery of encrypted content to another trusted 77 entity. 79 Several delegation methods are currently proposed within different 80 IETF working groups. They specify different methods for provisioning 81 HTTPS delivery credentials. 83 This document extends the CDNI Metadata interface to setup HTTPS 84 delegation between an upstream CDN (uCDN) and downstream CDN (dCDN). 85 Furthermore, it includes a proposal of IANA registry to enable adding 86 of new methods. 88 Section 2 is about terminology used in this document. Section 3 89 presents delegation methods specified at the IETF. Section 4 90 addresses the extension for handling HTTPS delegation in CDNI. 91 Section 5 describes simple data types. Section 6 addresses IANA 92 registry for delegation methods. Section 7 covers the security 93 issues. 95 2. Terminology 97 This document uses terminology from CDNI framework documents such as: 98 CDNI framework document [RFC7336], CDNI requirements [RFC7337] and 99 CDNI interface specifications documents: CDNI Metadata interface 100 [RFC8006] and CDNI Control interface / Triggers [RFC8007]. 102 3. Known delegation methods 104 There are currently two Internet drafts within the TLS and ACME 105 working groups adopted to handle delegation of HTTPS delivery between 106 entities. 108 This Internet Draft (I-D) proposes standardizing HTTPS delegation 109 between the entities using CDNI interfaces. 111 This document considers the following two I-Ds that supports HTTPS 112 delegation: 114 - Sub-certificates [I-D.ietf-tls-subcerts] 116 - Support for Short-term, Automatically-Renewed (STAR) certificates 117 in Automated Certificate Management Environment(ACME) 118 [I-D.ietf-acme-star] 120 4. Extending the CDNI metadata model 122 This section defines a CDNI extension to the current Metadata 123 interface model that allows bootstrapping delegation methods between 124 a uCDN and a delegate dCDN. 126 4.1. Extension to PathMetadata object 128 This extension reuses PathMetadata object, as defined in [RFC8006], 129 by adding new "Delegation methods" objects as specified in the 130 following sections. 132 This allows to explicitly indicate support for the given method. 133 Therefore, the presence (or lack thereof) of an 134 AcmeStarDelegationMethod, SubcertsDelegationMethod, and/or further 135 delegation methods, imply support (or lack thereof) for the given 136 method. 138 Example: 140 The PathMatch object can reference a path-metadata that points at the 141 delegation information. Delegation metadata are added to 142 PathMetaData object. 144 PathMatch: 145 { 146 "path-pattern": { 147 "pattern": "/movies/*", 148 "case-sensitive": true 149 }, 150 "path-metadata": { 151 "type": "MI.PathMetadata", 152 "href": "https://metadata.ucdn.example/video.example.com/movies" 153 } 154 } 156 Below shows the PathMetaData Object related to /movie/* 157 (located at https://metadata.ucdn.example/video.example.com/movies) 159 PathMetadata: 160 { 161 "metadata": [ 162 { 163 "generic-metadata-type": "MI.TimeWindowACL", 164 "generic-metadata-value": { 165 "times": [{ 166 "windows": [ 167 { 168 "start": "1213948800", 169 "end": "1478047392" 170 }]}], 171 "action": "allow", 172 }}, 173 { 174 "generic-metadata-type": "MI.AcmeStarDelegationMethod", 175 "generic-metadata-value": { 176 "star-proxy": "10.2.2.2", 177 "acme-server" : "10.2.3.3", 178 "credentials-location-uri": "www.ucdn.com/credentials", 179 "periodicity": 36000 180 }}] 181 } 183 The existence of the "MI.AcmeStarDelegationMethod" object in a 184 PathMetaData Object shall enable the use of one of the 185 AcmeStarDelegation Methods, chosen by the delegate. The delegation 186 method will be activated for the set of Path defined in the 187 PathMatch. See Section 4.2 for more details about delegation methods 188 metadata specification. 190 4.2. Delegation methods 192 This section defines the delegation methods objects metadata. Those 193 metadata allows bootstrapping a secured delegatioin by providing the 194 dCDN with the needed parameters to set it up. 196 4.2.1. AcmeStarDelegationMethod object 198 This section defines the AcmeStarDelegationMethod object which 199 describes metadata related to the use of Acme STAR API presented in 200 [I-D.ietf-acme-star] 202 As expressed in [I-D.ietf-acme-star], when an origin has set a 203 delegation to a specific domain (i.e. dCDN), the dCDN should present 204 to the end-user client, a short-term certificate bound to the master 205 certificate. 207 Property: star-proxy 209 Description: Used to advertise the STAR Proxy to the dCDN. 210 Endpoint type defined in RFC8006, Section 4.3.3. 212 Type: Endpoint 214 Mandatory-to-Specify: Yes 216 Property: acme-server 218 Description: used to advertise the ACME server to the dCDN. 219 Endpoint type is defined in RFC8006, Section 4.3.3. 221 Type: Endpoint 223 Mandatory-to-Specify: Yes 225 Property: credentials-location-uri 227 Description: expresses the location of the credentials to be 228 fetched by the dCDN. Link type is as defined in RFC8006, 229 Section 4.3.1. 231 Type: Link 233 Mandatory-to-Specify: Yes 235 Property: periodicity 236 Description: expresses the credentials renewal periodicity. See 237 Section 5.1. 239 Type: Periodicity 241 Mandatory-to-Specify: Yes 243 4.2.2. SubcertsDelegationMethod object 245 This section defines the SubcertsDelegationMethod object which 246 describes metadata related to the use of Subcerts as presented in 247 [I-D.ietf-tls-subcerts] 249 As expressed in [I-D.ietf-tls-subcerts], when an origin has set a 250 delegation to a specific domain (i.e. dCDN), the dCDN should present 251 the Origin or uCDN certificate or "delegated_credential" during the 252 TLS handshake [RFC8446] to the end-user client application, instead 253 of its own certificate. 255 Property: credentials-delegating-entity 257 Description: Endpoint ID (IP) of the delegating Entity (uCDN). 258 Endpoint type defined in RFC8006, Section 4.3.3. 260 Type: Endpoint 262 Mandatory-to-Specify: Yes 264 Property: credential-recipient-entity 266 Description: Endpoint ID (IP) of the delegated entity (dCDN). 267 Endpoint type is defined in RFC8006, Section 4.3.3. 269 Type: Endpoint 271 Mandatory-to-Specify: Yes 273 Property: credentials-location-uri 275 Description: expresses the location of the credentials to be 276 fetched by the dCDN. Link type is as defined in RFC8006, 277 Section 4.3.1. 279 Type: Link 281 Mandatory-to-Specify: Yes 283 Property: periodicity 284 Description: expresses the credentials renewal periodicity. See 285 Section 5.1. 287 Type: Periodicity 289 Mandatory-to-Specify: Yes 291 5. Metadata Simple Data Type Descriptions 293 This section describes the simple data types that are used for 294 properties for objects in this document. 296 5.1. Periodicity 298 A time value expressed in seconds to indicate a periodicity. 300 Type: Integer 302 6. IANA considerations 304 This document requests the registration of the following entries 305 under the "CDNI Payload Types" registry hosted by IANA regarding 306 "CDNI delegation": 308 +----------------------------+---------------+ 309 | Payload Type | Specification | 310 +----------------------------+---------------+ 311 | MI.AcmeStarDelegationMethod| RFCthis | 312 | MI.SubCertDelegationMethod | RFCthis | 313 +----------------------------+---------------+ 315 [RFC Editor: Please replace RFCthis with the published RFC number for 316 this document.] 318 6.1. CDNI MI AcmeStarDelegationMethod Payload Type 320 Purpose: The purpose of this Payload Type is to distinguish 321 AcmeStarDelegationMethod MI objects (and any associated capability 322 advertisement) 324 Interface: MI/FCI 326 Encoding: see Section 4.2.1 328 6.2. CDNI MI SubCertsDelegationMethod Payload Type 330 Purpose: The purpose of this Payload Type is to distinguish 331 SubcertsDelegationMethod MI objects (and any associated capability 332 advertisement) 334 Interface: MI/FCI 336 Encoding: see Section 4.2.2 338 7. Security considerations 340 Extensions proposed here do not alter nor change Security 341 Considerations as outlined in the CDNI Metadata and Footprint and 342 Capabilities RFCs [RFC8006]. 344 8. References 346 8.1. Normative References 348 [I-D.ietf-acme-star] 349 Sheffer, Y., Lopez, D., Dios, O., Pastor, A., and T. 350 Fossati, "Support for Short-Term, Automatically-Renewed 351 (STAR) Certificates in Automated Certificate Management 352 Environment (ACME)", draft-ietf-acme-star-05 (work in 353 progress), March 2019. 355 [I-D.ietf-tls-subcerts] 356 Barnes, R., Iyengar, S., Sullivan, N., and E. Rescorla, 357 "Delegated Credentials for TLS", draft-ietf-tls- 358 subcerts-03 (work in progress), February 2019. 360 [RFC8006] Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, 361 "Content Delivery Network Interconnection (CDNI) 362 Metadata", RFC 8006, DOI 10.17487/RFC8006, December 2016, 363 . 365 [RFC8007] Murray, R. and B. Niven-Jenkins, "Content Delivery Network 366 Interconnection (CDNI) Control Interface / Triggers", 367 RFC 8007, DOI 10.17487/RFC8007, December 2016, 368 . 370 8.2. Informative References 372 [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., 373 "Framework for Content Distribution Network 374 Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, 375 August 2014, . 377 [RFC7337] Leung, K., Ed. and Y. Lee, Ed., "Content Distribution 378 Network Interconnection (CDNI) Requirements", RFC 7337, 379 DOI 10.17487/RFC7337, August 2014, 380 . 382 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 383 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 384 . 386 Authors' Addresses 388 Frederic Fieau (editor) 389 Orange 390 40-48, avenue de la Republique 391 Chatillon 92320 392 France 394 Email: frederic.fieau@orange.com 396 Emile Stephan 397 Orange 398 2, avenue Pierre Marzin 399 Lannion 22300 400 France 402 Email: emile.stephan@orange.com 404 Sanjay Mishra 405 Verizon 406 13100 Columbia Pike 407 Silver Spring MD 20904 408 USA 410 Email: sanjay.mishra@verizon.com