idnits 2.17.1 draft-ietf-cdni-additional-footprint-types-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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- 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 (2 March 2022) is 757 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 (~~), 3 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: 3 September 2022 2 March 2022 8 Content Delivery Network Interconnection (CDNI) Footprint Types: 9 Subdivision Code and Union 10 draft-ietf-cdni-additional-footprint-types-01 12 Abstract 14 Open Caching architecture is a use case of Content Delivery Networks 15 Interconnection (CDNI) in which the commercial Content Delivery 16 Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer 17 serves as the downstream CDN (dCDN). This document supplements the 18 CDNI Metadata Footprint Types defined in RFC 8006. The Footprint 19 Types defined in this document can be used for Footprint objects as 20 part of the Metadata interface (MI) defined in RFC 8006 or the 21 Footprint & Capabilities Advertisement interface (FCI) defined in RFC 22 8008. The defined Footprint Types are derived from requirements 23 raised by Open Caching but are also applicable to CDNI use cases in 24 general. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on 3 September 2022. 43 Copyright Notice 45 Copyright (c) 2022 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 50 license-info) in effect on the date of publication of this document. 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. Code Components 53 extracted from this document must include Revised BSD License text as 54 described in Section 4.e of the Trust Legal Provisions and are 55 provided without warranty as described in the Revised BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 62 2. CDNI Metadata Additional Footprint Types . . . . . . . . . . 3 63 2.1. CDNI Metadata SubdivisionCode Footprint Type . . . . . . 4 64 2.1.1. CDNI Metadata SubdivisionCode Data Type . . . . . . . 4 65 2.1.1.1. CDNI Metadata SubdivisionCode Data Type 66 Description . . . . . . . . . . . . . . . . . . . . 4 67 2.1.2. CDNI Metadata SubdivisionCode Footprint Type 68 Description . . . . . . . . . . . . . . . . . . . . . 4 69 2.2. CDNI Metadata FootprintUnion Footprint Type . . . . . . . 5 70 2.2.1. CDNI Metadata FootprintUnion Data Type . . . . . . . 6 71 2.2.2. CDNI Metadata FootprintUnion Footprint Type 72 Description . . . . . . . . . . . . . . . . . . . . . 6 73 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 74 3.1. CDNI Metadata Footprint Types . . . . . . . . . . . . . . 8 75 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 76 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 77 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 78 6.1. Normative References . . . . . . . . . . . . . . . . . . 9 79 6.2. Informative References . . . . . . . . . . . . . . . . . 10 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 82 1. Introduction 84 The Streaming Video Alliance [SVA] is a global association that works 85 to solve streaming video challenges in an effort to improve end-user 86 experience and adoption. The Open Caching Working Group [OCWG] of 87 the Streaming Video Alliance [SVA] is focused on the delegation of 88 video delivery requests from commercial CDNs to a caching layer at 89 the ISP's network. Open Caching architecture is a specific use case 90 of CDNI where the commercial CDN is the upstream CDN (uCDN) and the 91 ISP caching layer is the downstream CDN (dCDN). The Open Caching 92 Request Routing Specification [OC-RR] defines the Request Routing 93 process and the interfaces that are required for its provisioning. 94 This document defines and registers CDNI Footprint and Capabilities 95 objects [RFC8008] that are required for Open Caching Request Routing. 97 For consistency with other CDNI documents this document follows the 98 CDNI convention of uCDN (upstream CDN) and dCDN (downstream CDN) to 99 represent the commercial CDN and ISP caching layer respectively. 101 This document registers two CDNI Metadata Footprint Types (section 102 7.2 of [RFC8006]) for the defined objects: 104 * SubdivisionCode Footprint Type (e.g., for dCDN advertising a 105 footprint that is specific to a State in the USA) 107 * Collection Footprint Type (for dCDN advertising a footprint that 108 consists of a group built from multiple Footprints Types. E.g., 109 both IPv4 and IPv6 client addresses) 111 1.1. Terminology 113 The following terms are used throughout this document: 115 * CDN - Content Delivery Network 117 Additionally, this document reuses the terminology defined in 118 [RFC6707], [RFC7336], [RFC8006], and [RFC8008]. Specifically, we use 119 the following CDNI acronyms: 121 * uCDN, dCDN - Upstream CDN and Downstream CDN respectively (see 122 [RFC7336] ) 124 1.2. Requirements Language 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 128 "OPTIONAL" in this document are to be interpreted as described in BCP 129 14 [RFC2119] [RFC8174] when, and only when, they appear in all 130 capitals, as shown here. 132 2. CDNI Metadata Additional Footprint Types 134 Section 5 of [RFC8008] describes the FCI Capability Advertisement 135 Object, which includes an array of CDNI Footprint Objects. Each such 136 object has a footprint-type and a footprint-value, as described in 137 section 4.2.2.2 of [RFC8006]. This document defines additional 138 footprint types, beyond those mentioned in CDNI metadata [RFC8006]. 140 2.1. CDNI Metadata SubdivisionCode 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. Herein is 146 define the subdivisioncode simple data type, as well as a footprint 147 type allowing the dCDN to define constraints matching geographic 148 areas with better granularity, specifically using the [ISO3166-2] 149 Country Subdivision codes. 151 2.1.1. CDNI Metadata SubdivisionCode Data Type 153 The "SubdivisionCode" data type specified in Section 2.1.1.1, 154 describes a country specific subdivision using an [ISO3166-2] code. 155 The data type is added to the list of data types described in section 156 4.3 of [RFC8006] that are used as properties of CDNI Metadata 157 objects. 159 2.1.1.1. CDNI Metadata SubdivisionCode Data Type Description 161 A [ISO3166-2] code in lower case. Each code consists of two parts, 162 separated by a hyphen. The first part is the [ISO3166-1] code of the 163 country. The second part is a string of up to three alphanumeric 164 characters. 166 Type: String 168 Example SubdivisionCodes: 170 "ca-ns" 172 "us-ny" 174 2.1.2. CDNI Metadata SubdivisionCode Footprint Type Description 176 The "SubdivisionCode" simple data type specified in Section 2.1.1 , 177 is added to the data types listed as footprint types in section 178 4.2.2.2 of [RFC8006] . 180 Below is an example using a footprint object of type 181 "SubdivisionCode". The Footprint Object in this example creates a 182 constraints matching clients both in the Nova-Scotia province of 183 Canada (ISO [ISO3166-2] code "CA-NS"), as well as in the state of 184 New-York In the US (ISO [ISO3166-2] code "US-NY"). 186 { 187 "capabilities": [ 188 { 189 "capability-type": , 190 "capability-value": , 191 "footprints": [ 192 { 193 "footprint-type": "subdivisioncode", 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. This 207 implies that the advertisement of different footprint types narrows 208 the 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 FCI 213 Capability Advertisement Object footprint constraints that match IPv4 214 or IPv6 clients. However, the described "narrowing" semantic of the 215 Footprint Objects array prevents the usage of these objects together 216 to create a footprint constraint that matches IPv4 clients together 217 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 in 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 match both IPv4 and IPv6 client addresses, below is 246 introduced the "FootprintUnion" footprint type. This footprint type 247 allows the collection of multiple footprint-objects into a unified 248 object. It is useful for resolving the above limitation, as well as 249 for unifying footprints of additional types such as countrycode and 250 subdivisioncode. 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]. The footprint-value 256 for a FootprintUnion object is an array of Footprint objects, where 257 the Footprint objects may be of any Footprint Type other than 258 FootprintUnion. 260 2.2.2. CDNI Metadata FootprintUnion Footprint Type Description 262 The "footprintunion" data type specified in Section 2.2.1, is added 263 to the data types listed as footprint types in section 4.2.2.2 of 264 [RFC8006]. 266 Below is an example using a footprint object of type 267 "footprintunion". 269 { 270 "capabilities": [ 271 { 272 "capability-type": , 273 "capability-value": , 274 "footprints": [ 275 { 276 "footprint-type": "footprintunion", 277 "footprint-value": [ 278 { 279 "footprint-type": "ipv4cidr", 280 "footprint-value": ["192.0.2.0/24"] 281 }, 282 { 283 "footprint-type": "ipv6cidr", 284 "footprint-value": ["2001:db8::/32"] 285 } 286 ] 287 } 288 ] 289 } 290 ] 291 } 293 The footprint union also allows to compose a countrycode and 294 subdivisioncode based footprint objects. In the example below we 295 create a constraint covering autonomous system 64496 within the US 296 (ISO [ISO3166-1] alpha-2 code "US") and the Nova-Scotia province of 297 Canada (ISO [ISO3166-2] code "CA-NS"). 299 { 300 "capabilities": [ 301 { 302 "capability-type": , 303 "capability-value": , 304 "footprints": [ 305 { 306 "footprint-type": "asn", 307 "footprint-value": ["as64496"] 308 }, 309 { 310 "footprint-type": "footprintunion", 311 "footprint-value": [ 312 { 313 "footprint-type": "countrycode", 314 "footprint-value": ["us"] 315 }, 316 { 317 "footprint-type": "subdivisioncode", 318 "footprint-value": ["ca-ns"] 319 } 320 ] 321 } 322 ] 323 } 324 ] 325 } 327 3. IANA Considerations 329 3.1. CDNI Metadata Footprint Types 331 Section 7.2 of [RFC8006] creates the "CDNI Metadata Footprint Types" 332 subregistry within the "Content Delivery Network Interconnection 333 (CDNI) Parameters" registry. 335 This document requests the registration of the two additional 336 Footprint Types as defined in Section 2.2 and Section 2.1 : 338 +=====================+=============================+===============+ 339 | Footprint Type | Description | Specification | 340 +=====================+=============================+===============+ 341 | FCI.subdivisioncode | ISO 3166-2 Subdivision | RFCthis | 342 | | Code: An alpha-2 ISO | | 343 | | 3166-1 Country Code, | | 344 | | followed by a separator | | 345 | | and up to three | | 346 | | alphanumeric characters | | 347 +---------------------+-----------------------------+---------------+ 348 | FCI.footprintunion | Footprint Object as | RFCthis | 349 | | specified in [RFC8006] | | 350 +---------------------+-----------------------------+---------------+ 352 Table 1 354 [RFC Editor: Please replace RFCthis with the published RFC number for 355 this document.] 357 4. Security Considerations 359 This specification is in accordance with the CDNI Metadata and the 360 CDNI Request Routing: Footprint and Capabilities Semantics. As such, 361 it is subject to the security and privacy considerations as defined 362 in Section 8 of [RFC8006] and in Section 7 of [RFC8008] respectively. 363 More specifically, the use of "SubdivisionCode" footprint type, 364 introduces a higher level of granularity into the published dCDN 365 Footprint. Therefore, to meet confidentiality requirements, the use 366 of transport-layer security mechanisms as specified in Section 7 of 367 [RFC8008], is required. 369 5. Acknowledgements 371 The authors would like to express their gratitude to Ori Finkelman 372 and Kevin J. Ma for their guidance and reviews throughout the 373 development of this document. 375 6. References 377 6.1. Normative References 379 [ISO3166-1] 380 ISO, "Codes for the representation of names of countries 381 and their subdivisions -- Part 1: Country code", 382 ISO 3166-1:2020, Edition 4, August 2020, 383 . 385 [ISO3166-2] 386 ISO, "Codes for the representation of names of countries 387 and their subdivisions -- Part 2: Country subdivision 388 code", ISO 3166-2:2020, Edition 4, August 2020, 389 . 391 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 392 Requirement Levels", BCP 14, RFC 2119, 393 DOI 10.17487/RFC2119, March 1997, 394 . 396 [RFC8006] Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, 397 "Content Delivery Network Interconnection (CDNI) 398 Metadata", RFC 8006, DOI 10.17487/RFC8006, December 2016, 399 . 401 [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg, 402 R., and K. Ma, "Content Delivery Network Interconnection 403 (CDNI) Request Routing: Footprint and Capabilities 404 Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016, 405 . 407 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 408 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 409 May 2017, . 411 6.2. Informative References 413 [OC-RR] Finkelman, O., Ed., Hofmann, J., Klein, E., Mishra, S., 414 Ma, K., Sahar, D., and B. Zurat, "Open Caching - Request 415 Routing Functional Specification", Version 1.1, 4 October 416 2019, . 419 [OCWG] "Open Caching Home Page", 420 . 423 [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content 424 Distribution Network Interconnection (CDNI) Problem 425 Statement", RFC 6707, DOI 10.17487/RFC6707, September 426 2012, . 428 [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., 429 "Framework for Content Distribution Network 430 Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, 431 August 2014, . 433 [SVA] "Streaming Video Alliance Home Page", 434 . 436 Authors' Addresses 438 Nir B. Sopher 439 Qwilt 440 6, Ha'harash 441 Hod HaSharon 442 4524079 443 Israel 444 Email: nir@apache.org 446 Sanjay Mishra 447 Verizon 448 13100 Columbia Pike 449 Silver Spring, MD 20904 450 United States of America 451 Email: sanjay.mishra@verizon.com