idnits 2.17.1 draft-fieau-cdni-interfaces-https-delegation-05.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 (September 17, 2018) is 2045 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) == Unused Reference: 'RFC7937' is defined on line 373, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-acme-star-03 == Outdated reference: A later version (-15) exists of draft-ietf-tls-subcerts-02 Summary: 0 errors (**), 0 flaws (~~), 4 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: March 21, 2019 S. Mishra 6 Verizon 7 September 17, 2018 9 CDNI extensions for HTTPS delegation 10 draft-fieau-cdni-interfaces-https-delegation-05 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 March 21, 2019. 36 Copyright Notice 38 Copyright (c) 2018 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 . . . . . . . . . . . . . . . . . . . . . . . 8 63 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 8 64 6.1. CDNI MI AcmeStarDelegationMethod Payload Type . . . . . . 8 65 6.2. CDNI MI SubCertsDelegationMethod Payload Type . . . . . . 8 66 7. Security considerations . . . . . . . . . . . . . . . . . . . 9 67 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 68 8.1. Normative References . . . . . . . . . . . . . . . . . . 9 69 8.2. Informative References . . . . . . . . . . . . . . . . . 9 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 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 the 86 adding 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 is about an IANA 92 registry for delegation methods. Section 7 raises 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 I-D proposes standardizing HTTPS delegation between the entities 109 using CDNI interfaces. 111 This document considers the following two I-D that supports HTTPS 112 delegation: 114 - Sub-certificates [I-D.ietf-tls-subcerts] 116 - Short-term certificates in ACME using STAR API [I-D.ietf-acme-star] 118 4. Extending the CDNI metadata model 120 This section defines a CDNI extension to the current Metadata 121 interface model that allows bootstrapping delegation methods between 122 a uCDN and a delegate dCDN. 124 4.1. Extension to PathMetadata object 126 This extension reuses PathMetadata object, as defined in [RFC8006], 127 by adding new "Delegation methods" objects as specified in the 128 following sections. 130 This allows to explicitly indicate support for the given method. 131 Therefore, the presence (or lack thereof) of an 132 AcmeStarDelegationMethod, SubcertsDelegationMethod, and/or further 133 delegation methods, imply support (or lack thereof) for the given 134 method. 136 Example: 138 The PathMatch object can reference a path-metadata that points at the 139 delegation information. Delegation metadata are added to 140 PathMetaData object. 142 PathMatch: 143 { 144 "path-pattern": { 145 "pattern": "/movies/*", 146 "case-sensitive": true 147 }, 148 "path-metadata": { 149 "type": "MI.PathMetadata", 150 "href": "https://metadata.ucdn.example/video.example.com/movies" 151 } 152 } 154 Below shows the PathMetaData Object related to /movie/* 155 (located at https://metadata.ucdn.example/video.example.com/movies) 157 PathMetadata: 158 { 159 "metadata": [ 160 { 161 "generic-metadata-type": "MI.TimeWindowACL", 162 "generic-metadata-value": { 163 "times": [{ 164 "windows": [ 165 { 166 "start": "1213948800", 167 "end": "1478047392" 168 }]}], 169 "action": "allow", 170 }}, 171 { 172 "generic-metadata-type": "MI.AcmeStarDelegationMethod", 173 "generic-metadata-value": { 174 "starproxy": "10.2.2.2", 175 "acmeserver" : "10.2.3.3", 176 "credentialslocationuri": "www.ucdn.com/credentials", 177 "periodicity": 36000 178 }}] 179 } 181 The existence of the "MI.AcmeStarDelegationMethod" object in a 182 PathMetaData Object shall enable the use of one of the 183 AcmeStarDelegation Methods, chosen by the delegate. The delegation 184 method will be activated for the set of Path defined in the 185 PathMatch. See next section for more details about delegation 186 methods metadata specification. 188 4.2. Delegation methods 190 This section defines the delegation methods objects metadata. Those 191 metadata allows bootstrapping a secured delegatioin by providing the 192 dCDN with the needed parameters to set it up. 194 4.2.1. AcmeStarDelegationMethod object 196 This section defines the AcmeStarDelegationMethod object which 197 describes metadata related to the use of Acme Star API presented in 198 [I-D.ietf-acme-star] 200 As expressed in [I-D.ietf-acme-star], when an origin has set a 201 delegation to a specific domain (i.e. dCDN), the dCDN should present 202 to the end-user client, a short-term certificate bound to the master 203 certificate. 205 Property: starproxy 207 Description: Used to advertise the STAR Proxy to the dCDN. 208 Endpoint type defined in RFC8006, section 4.3.3 210 Type: Endpoint 212 Mandatory-to-Specify: Yes 214 Property: acmeserver 216 Description: used to advertise the ACME server to the dCDN. 217 Endpoint type is defined in RFC8006, section 4.3.3 219 Type: Endpoint 221 Mandatory-to-Specify: Yes 223 Property: credentialslocationuri 225 Description: expresses the location of the credentials to be 226 fetched by the dCDN. Link type is as defined in RFC8006, section 227 4.3.1 229 Type: Link 231 Mandatory-to-Specify: Yes 233 Property: periodicity 234 Description: expresses the credentials renewal periodicity. See 235 next section on simple meta data type. 237 Type: Periodicity 239 Mandatory-to-Specify: Yes 241 As an example, AcmeStarDelegationMethod object could express the 242 Acme-Star delegation as the following: 244 AcmeStarDelegationMethod: { 245 "generic-metadata-type": "MI.AcmeStarDelegationMethod", 246 "generic-metadata-value": { 247 "starproxy": "10.2.2.2", 248 "acmeserver": "10.2.3.3", 249 "credentialslocationuri": "www.ucdn.com/credentials", 250 "periodicity": 36000 251 } 252 } 254 4.2.2. SubcertsDelegationMethod object 256 This section defines the SubcertsDelegationMethod object which 257 describes metadata related to the use of Subcerts as presented in 258 [I-D.ietf-tls-subcerts] 260 As expressed in [I-D.ietf-tls-subcerts], when an origin has set a 261 delegation to a specific domain (i.e. dCDN), the dCDN should present 262 the Origin or uCDN certificate or "delegated_credential" during the 263 TLS handshake [RFC8446] to the end-user client application, instead 264 of its own certificate. 266 Property: credentialsdelegatingentity 268 Description: Endpoint ID (IP) of the delegating Entity (uCDN). 269 Endpoint type defined in RFC8006, section 4.3.3 271 Type: Endpoint 273 Mandatory-to-Specify: Yes 275 Property: credentialrecipiententity 277 Description: Endpoint ID (IP) of the delegated entity (dCDN). 278 Endpoint type is defined in RFC8006, section 4.3.3 279 Type: Endpoint 281 Mandatory-to-Specify: Yes 283 Property: credentialslocationuri 285 Description: expresses the location of the credentials to be 286 fetched by the dCDN. Link type is as defined in RFC8006, section 287 4.3.1 289 Type: Link 291 Mandatory-to-Specify: Yes 293 Property: periodicity 295 Description: expresses the credentials renewal periodicity. See 296 next section on simple meta data type. 298 Type: Periodicity 300 Mandatory-to-Specify: Yes 302 As an example, when a uCDN has delegated HTTPS delivery to dCDN, a 303 SubcertsDelegationMethod object can express the SubCerts delegation 304 as the following: 306 SubcertsDelegationMethod: { 307 "generic-metadata-type": "MI.SubcertsDelegationMethod", 308 "generic-metadata-value": { 309 "credentialsdelegatingentity": "10.2.2.2", 310 "credentialsrecepiententity": "10.2.3.3", 311 "credentialslocationuri": "www.ucdn.com/credentials", 312 "periodicity": 36000 313 } 314 } 316 5. Metadata Simple Data Type Descriptions 318 This section describes the simple data types that are used for 319 properties for objects in this document. 321 5.1. Periodicity 323 A time value expressed in seconds to indicate a periodicity. 325 Type: Integer 327 6. IANA considerations 329 This document requests the registration of the following entries 330 under the "CDNI Payload Types" registry hosted by IANA regarding 331 "CDNI delegation": 333 +----------------------------+---------------+ 334 | Payload Type | Specification | 335 +----------------------------+---------------+ 336 | MI.AcmeStarDelegationMethod| RFCthis | 337 | MI.SubCertDelegationMethod | RFCthis | 338 +----------------------------+---------------+ 340 [RFC Editor: Please replace RFCthis with the published RFC number for 341 this document.] 343 6.1. CDNI MI AcmeStarDelegationMethod Payload Type 345 Purpose: The purpose of this Payload Type is to distinguish 346 AcmeStarDelegationMethod MI objects (and any associated capability 347 advertisement) 349 Interface: MI/FCI 351 Encoding: see Section 4.2.1 353 6.2. CDNI MI SubCertsDelegationMethod Payload Type 355 Purpose: The purpose of this Payload Type is to distinguish 356 SubcertsDelegationMethod MI objects (and any associated capability 357 advertisement) 359 Interface: MI/FCI 361 Encoding: see Section 4.2.2 363 7. Security considerations 365 Extensions proposed here do not change Security Considerations as 366 outlined in the CDNI Metadata and Footprint and Capabilities RFCs 367 [RFC8006]. 369 8. References 371 8.1. Normative References 373 [RFC7937] Le Faucheur, F., Ed., Bertrand, G., Ed., Oprescu, I., Ed., 374 and R. Peterkofsky, "Content Distribution Network 375 Interconnection (CDNI) Logging Interface", RFC 7937, 376 DOI 10.17487/RFC7937, August 2016, 377 . 379 [RFC8006] Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, 380 "Content Delivery Network Interconnection (CDNI) 381 Metadata", RFC 8006, DOI 10.17487/RFC8006, December 2016, 382 . 384 [RFC8007] Murray, R. and B. Niven-Jenkins, "Content Delivery Network 385 Interconnection (CDNI) Control Interface / Triggers", 386 RFC 8007, DOI 10.17487/RFC8007, December 2016, 387 . 389 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 390 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 391 . 393 8.2. Informative References 395 [I-D.ietf-acme-star] 396 Sheffer, Y., Lopez, D., Dios, O., Pastor, A., and T. 397 Fossati, "Support for Short-Term, Automatically-Renewed 398 (STAR) Certificates in Automated Certificate Management 399 Environment (ACME)", draft-ietf-acme-star-03 (work in 400 progress), March 2018. 402 [I-D.ietf-tls-subcerts] 403 Barnes, R., Iyengar, S., Sullivan, N., and E. Rescorla, 404 "Delegated Credentials for TLS", draft-ietf-tls- 405 subcerts-02 (work in progress), August 2018. 407 [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., 408 "Framework for Content Distribution Network 409 Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, 410 August 2014, . 412 [RFC7337] Leung, K., Ed. and Y. Lee, Ed., "Content Distribution 413 Network Interconnection (CDNI) Requirements", RFC 7337, 414 DOI 10.17487/RFC7337, August 2014, 415 . 417 Authors' Addresses 419 Frederic Fieau (editor) 420 Orange 421 40-48, avenue de la Republique 422 Chatillon 92320 423 France 425 Email: frederic.fieau@orange.com 427 Emile Stephan 428 Orange 429 2, avenue Pierre Marzin 430 Lannion 22300 431 France 433 Email: emile.stephan@orange.com 435 Sanjay Mishra 436 Verizon 437 13100 Columbia Pike 438 Silver Spring MD 20904 439 USA 441 Email: sanjay.mishra@verizon.com