idnits 2.17.1 draft-sopher-cdni-footprint-types-extensions-04.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC8008, but the abstract doesn't seem to directly say this. It does mention RFC8008 though, so this could be OK. -- The draft header indicates that this document updates RFC8006, but the abstract doesn't seem to directly say this. It does mention RFC8006 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (28 July 2021) is 1002 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO3166-2' Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group N. Sopher 3 Internet-Draft Qwilt 4 Updates: 8006, 8008 (if approved) S. Mishra 5 Intended status: Standards Track Verizon 6 Expires: 29 January 2022 28 July 2021 8 CDNI Request Routing Extensions 9 draft-sopher-cdni-footprint-types-extensions-04 11 Abstract 13 Open Caching architecture is a use case of Content Delivery Networks 14 Interconnection (CDNI) in which the commercial Content Delivery 15 Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer 16 serves as the downstream CDN (dCDN). This document supplements to 17 the CDNI Metadata Footprint Types defined in RFC 8006. The Footprint 18 Types defined in this document can be used for Footprint objects as 19 part of the Footprint & Capabilities Advertisement interface (FCI) 20 defined in RFC 8008. The defined Footprint Types are derived from 21 requirements raised by Open Caching but are also applicable to CDNI 22 use cases in general. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on 29 January 2022. 41 Copyright Notice 43 Copyright (c) 2021 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 48 license-info) in effect on the date of publication of this document. 49 Please review these documents carefully, as they describe your rights 50 and restrictions with respect to this document. Code Components 51 extracted from this document must include Simplified BSD License text 52 as described in Section 4.e of the Trust Legal Provisions and are 53 provided without warranty as described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 60 2. CDNI Metadata Additonal Footprint Types . . . . . . . . . . . 3 61 2.1. CDNI Metadata ISO3166-2Code Footprint Type . . . . . . . 4 62 2.1.1. CDNI Metadata ISO3166-2Code Data Type . . . . . . . . 4 63 2.1.1.1. CDNI Metadata ISO3166-2Code Data Type 64 Description . . . . . . . . . . . . . . . . . . . . 4 65 2.1.2. CDNI Metadata ISO3166-2Code Footprint Type 66 Description . . . . . . . . . . . . . . . . . . . . . 4 67 2.2. CDNI Metadata FootprintUnion Footprint Type . . . . . . . 5 68 2.2.1. CDNI Metadata FootprintUnion Data Type . . . . . . . 6 69 2.2.2. CDNI Metadata FootprintUnion Footprint Type 70 Description . . . . . . . . . . . . . . . . . . . . . 6 71 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 72 3.1. CDNI Metadata Footprint Types . . . . . . . . . . . . . . 8 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 74 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 75 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 76 6.1. Normative References . . . . . . . . . . . . . . . . . . 9 77 6.2. Informative References . . . . . . . . . . . . . . . . . 10 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 80 1. Introduction 82 The Streaming Video Alliance [SVA] is a global association that works 83 to solve streaming video challenges in an effort to improve end-user 84 experience and adoption. The Open Caching Working Group [OCWG] of 85 the Streaming Video Alliance [SVA] is focused on the delegation of 86 video delivery requests from commerical CDNs to a caching layer at 87 the ISP's network. Open Caching architecture is a specific use case 88 of CDNI where the commercial CDN is the upstream CDN (uCDN) and the 89 ISP caching layer is the downstream CDN (dCDN). The Open Caching 90 Request Routing Specification [OC-RR] defines the Request Routing 91 process and the interfaces that are required for its provisioning. 92 This document defines and registers CDNI Footprint and Capabilities 93 objects[RFC8008] that are required for Open Caching Request Routing. 95 For consistency with other CDNI documents this document follows the 96 CDNI convention of uCDN (upstream CDN) and dCDN (downstream CDN) to 97 represent the commercial CDN and ISP caching layer respectively. 99 This document registers two CDNI Metadata Footprint Types (section 100 7.2 of [RFC8006]) for the defined objects: 102 * ISO3166-2Code Footprint Type (e.g. for dCDN advertising a 103 footprint that is specific to a State in the USA) 105 * Collection Footprint Type (for dCDN advertising a footprint that 106 consists of a group built from multiple Footprints Types. E.g. 107 both IPv4 and IPv6 client addresses) 109 1.1. Terminology 111 The following terms are used throughout this document: 113 * CDN - Content Delivery Network 115 Additionally, this document reuses the terminology defined in 116 [RFC6707], [RFC7336], [RFC8006], [RFC8007], [RFC8008], and [RFC8804]. 117 Specifically, we use the following CDNI acronyms: 119 * uCDN, dCDN - Upstream CDN and Downstream CDN respectively (see 120 [RFC7336] ) 122 1.2. Requirements Language 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 126 "OPTIONAL" in this document are to be interpreted as described in BCP 127 14 [RFC2119] [RFC8174] when, and only when, they appear in all 128 capitals, as shown here. 130 2. CDNI Metadata Additonal Footprint Types 132 Section 5 of [RFC8008] describes the FCI Capability Advertisement 133 Object, which includes an array of CDNI Footprint Objects. Each such 134 object has a footprint-type and a footprint-value, as described in 135 section 4.2.2.2 of [RFC8006]. This document defines additional 136 footprint types, beyond those mentioned in CDNI metadata [RFC8006]. 137 For consistency, this document follows the CDNI notation of uCDN for 138 (the commercial CDN) and dCDN (the ISP caching layer). 140 2.1. CDNI Metadata ISO3166-2Code Footprint Type 142 Section 4.3.8 of [RFC8006] specifies the "Country Code" footprint 143 type for listing [ISO3166-1] alpha-2 codes. Using Footprint Objects 144 of this type, one can define an FCI Capability Advertisement Object 145 footprint constraints that match a specific country. Here we define 146 the iso3166-2code simple data type, as well as a footprint type 147 allowing the dCDN to define constraints matching geographic areas 148 with better granularity, specifically using the [ISO3166-2] Country 149 Subdivision codes. 151 2.1.1. CDNI Metadata ISO3166-2Code Data Type 153 The "ISO3166-2Code" data type specified in Section 2.1.1.1, describes 154 a country specific subdivision using an [ISO3166-2] code. The data 155 type is added to the list of data types described in section 4.3 of 156 [RFC8006] that are used as properties of CDNI Metadata objects. 158 2.1.1.1. CDNI Metadata ISO3166-2Code Data Type Description 160 A [ISO3166-2] code in lower case. Each code consists of two parts, 161 separated by a hyphen. The first part is the [ISO3166-1] code of the 162 country. The second part is a string of up to three alphanumeric 163 characters. 165 Type: String 167 Example ISO3166-2Codes: 169 "ca-ns" 171 "us-ny" 173 2.1.2. CDNI Metadata ISO3166-2Code Footprint Type Description 175 The "ISO3166-2Code" simple data type specified in Section 2.1.1 , is 176 added to the data types listed as footprint types in section 4.2.2.2 177 of [RFC8006] . 179 Below is an adjustment for the example in Section 2.1.1, now 180 embedding a footprint object of type "ISO3166-2Code". The Footprint 181 Object in this example creates a constraints matching clients both in 182 Nova-Scotia province of Canada (ISO [ISO3166-2] code "CA-NS"), as 183 well as in the state of New-York In the US (ISO [ISO3166-2] code "US- 184 NY"). 186 { 187 "capabilities": [ 188 { 189 "capability-type": , 190 "capability-value": , 191 "footprints": [ 192 { 193 "footprint-type": "iso3166-2code", 194 "footprint-value": ["ca-ns", "us-ny"] 195 } 196 ] 197 } 198 ] 199 } 201 2.2. CDNI Metadata FootprintUnion Footprint Type 203 As described in section 5 of [RFC8008], the FCI Capability 204 Advertisement Object includes an array of CDNI Footprint Objects. 205 Appendix B of [RFC8008] specifies the semantics of a Footprint 206 Objects array as a multiple, additive, footprint constraints. 207 Meaning, the advertisement of different footprint types narrows the 208 dCDN's candidacy cumulatively. 210 Sections 4.3.5 and 4.3.6 of [RFC8006] specify the "IPv4CIDR" and 211 "IPv6CIDR" footprint types, respectively, for listing IP addresses 212 blocks. Using Footprint Objects of these types, one can define an 213 FCI Capability Advertisement Object footprint constraints that match 214 IPv4 or IPv6 clients. However, the described "narrowing" semantic of 215 the Footprint Objects array prevents the usage of these objects 216 together in order to create a footprint constraint that matches IPv4 217 clients together with IPv6 clients. 219 Below is an example for an attempt at creating an object matching 220 IPv4 clients of subnet "192.0.2.0/24", as well as IPv6 clients of 221 subnet "2001:db8::/32". Such a definition results with an empty list 222 of clients, as the constraints are additives and a client address 223 cannot be both IPv4 and IPv6. 225 { 226 "capabilities": [ 227 { 228 "capability-type": , 229 "capability-value": , 230 "footprints": [ 231 { 232 "footprint-type": "ipv4cidr", 233 "footprint-value": ["192.0.2.0/24"] 234 }, 235 { 236 "footprint-type": "ipv6cidr", 237 "footprint-value": ["2001:db8::/32"] 238 } 239 ] 240 } 241 ] 242 } 244 To overcome the described limitation, and allow a list of footprint 245 constraints that matches both IPv4 and IPv6 client addresses, we 246 introduce below the "FootprintUnion" footprint type. This footprint 247 type allows the collection of multiple footprint-objects into a 248 unified object. It is useful for resolving the above limitaion, as 249 well as for unifying footprints of additional types such as 250 countrycode and iso3166-2code. 252 2.2.1. CDNI Metadata FootprintUnion Data Type 254 The "FootprintUnion" data type is based on the Footprint Object 255 already defined in section 4.2.2.2 of [RFC8006]. It includes a 256 footprint-type property and a footprint-value array values. 258 2.2.2. CDNI Metadata FootprintUnion Footprint Type Description 260 The "footprintunion" data type specified in Section 2.2.1, is added 261 to the data types listed as footprint types in section 4.2.2.2 of 262 [RFC8006]. 264 Below is an adjustment for the example in Section 2.2.1, now 265 embedding a footprint object of type "footprintunion". 267 { 268 "capabilities": [ 269 { 270 "capability-type": , 271 "capability-value": , 272 "footprints": [ 273 { 274 "footprint-type": "footprintunion", 275 "footprint-value": [ 276 { 277 "footprint-type": "ipv4cidr", 278 "footprint-value": ["192.0.2.0/24"] 279 }, 280 { 281 "footprint-type": "ipv6cidr", 282 "footprint-value": ["2001:db8::/32"] 283 } 284 ] 285 } 286 ] 287 } 288 ] 289 } 291 An additional example is the collection of countrycode and 292 iso3166-2code based footprint objects. In the example below we 293 create a constraint covering autonomous system 64496 within the US 294 (ISO [ISO3166-1] alpha-2 code "US"), as well as Nova-Scotia province 295 of Canada (ISO [ISO3166-2] code "CA-NS"). 297 { 298 "capabilities": [ 299 { 300 "capability-type": , 301 "capability-value": , 302 "footprints": [ 303 { 304 "footprint-type": "asn", 305 "footprint-value": ["as64496"] 306 }, 307 { 308 "footprint-type": "footprintunion", 309 "footprint-value": [ 310 { 311 "footprint-type": "countrycode", 312 "footprint-value": ["us"] 313 }, 314 { 315 "footprint-type": "iso3166-2code", 316 "footprint-value": ["ca-ns"] 317 } 318 ] 319 } 320 ] 321 } 322 ] 323 } 325 3. IANA Considerations 327 3.1. CDNI Metadata Footprint Types 329 As described in section 7.2 of [RFC8006] , the "CDNI Metadata 330 Footprint Types" subregistry was created within the "Content Delivery 331 Network Interconnection (CDNI) Parameters" registry. The created 332 namespace defines the valid values for Footprint Object Types, and is 333 already populated with the types described in Section 4.2.2.2 of 334 [RFC8006] . 336 This document requests the registration of the two additional 337 footprint type as defined in Section 2.2 and Section 2.1 : 339 +====================+========================+===============+ 340 | Footprint Type | Description | Specification | 341 +====================+========================+===============+ 342 | FCI.iso3166-2code | ISO 3166-2 Country or | RFCthis | 343 | | Subdivision Code | | 344 +--------------------+------------------------+---------------+ 345 | FCI.footprintunion | Footprint Object as | [RFC8006] | 346 | | specified in [RFC8006] | | 347 +--------------------+------------------------+---------------+ 349 Table 1 351 [RFC Editor: Please replace RFCthis with the published RFC number for 352 this document.] 354 4. Security Considerations 356 This specification is in accordance with the CDNI Request Routing: 357 Footprint and Capabilities Semantics. As such, it is subject to the 358 security and privacy considerations as defined in Section 8 of 359 [RFC8006] and in Section 7 of [RFC8008] respectively. 361 5. Acknowledgements 363 The authors would like to express their gratitude to Ori Finkelman 364 and Kevin J. Ma for their guidance and reviews throughout the 365 development of this document. 367 6. References 369 6.1. Normative References 371 [ISO3166-1] 372 ISO, "Codes for the representation of names of countries 373 and their subdivisions -- Part 1: Country code", 374 ISO 3166-1:2020, Edition 4, August 2020, 375 . 377 [ISO3166-2] 378 ISO, "Codes for the representation of names of countries 379 and their subdivisions -- Part 2: Country subdivision 380 code", ISO 3166-2:2020, Edition 4, August 2020, 381 . 383 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 384 Requirement Levels", BCP 14, RFC 2119, 385 DOI 10.17487/RFC2119, March 1997, 386 . 388 [RFC8006] Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, 389 "Content Delivery Network Interconnection (CDNI) 390 Metadata", RFC 8006, DOI 10.17487/RFC8006, December 2016, 391 . 393 [RFC8007] Murray, R. and B. Niven-Jenkins, "Content Delivery Network 394 Interconnection (CDNI) Control Interface / Triggers", 395 RFC 8007, DOI 10.17487/RFC8007, December 2016, 396 . 398 [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg, 399 R., and K. Ma, "Content Delivery Network Interconnection 400 (CDNI) Request Routing: Footprint and Capabilities 401 Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016, 402 . 404 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 405 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 406 May 2017, . 408 [RFC8804] Finkelman, O. and S. Mishra, "Content Delivery Network 409 Interconnection (CDNI) Request Routing Extensions", 410 RFC 8804, DOI 10.17487/RFC8804, September 2020, 411 . 413 6.2. Informative References 415 [OC-RR] Finkelman, O., Ed., Hofmann, J., Klein, E., Mishra, S., 416 Ma, K., Sahar, D., and B. Zurat, "Open Caching - Request 417 Routing Functional Specification", Version 1.1, 4 October 418 2019, . 421 [OCWG] "Open Caching Home Page", 422 . 425 [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content 426 Distribution Network Interconnection (CDNI) Problem 427 Statement", RFC 6707, DOI 10.17487/RFC6707, September 428 2012, . 430 [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., 431 "Framework for Content Distribution Network 432 Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, 433 August 2014, . 435 [SVA] "Streaming Video Alliance Home Page", 436 . 438 Authors' Addresses 440 Nir B. Sopher 441 Qwilt 442 6, Ha'harash 443 Hod HaSharon 444 4524079 445 Israel 447 Email: nir@apache.org 449 Sanjay Mishra 450 Verizon 451 13100 Columbia Pike 452 Silver Spring, MD 20904 453 United States of America 455 Email: sanjay.mishra@verizon.com