idnits 2.17.1 draft-sopher-cdni-footprint-types-extensions-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 : ---------------------------------------------------------------------------- -- 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 (December 23, 2020) is 1220 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: June 26, 2021 December 23, 2020 8 CDNI Request Routing Extensions 9 draft-sopher-cdni-footprint-types-extensions-01 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 June 26, 2021. 41 Copyright Notice 43 Copyright (c) 2020 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 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 61 2. CDNI Metadata Additonal Footprint Types . . . . . . . . . . . 3 62 2.1. CDNI Metadata IPv4v6CIDR Footprint Type . . . . . . . . . 3 63 2.1.1. CDNI Metadata IPv4v6CIDR Data Type . . . . . . . . . 4 64 2.1.1.1. CDNI Metadata IPv4v6CIDR Data Type Description . 5 65 2.1.2. CDNI Metadata IPv4v6CIDR Footprint Type Description . 5 66 2.2. CDNI Metadata ISO3166Code Footprint Type . . . . . . . . 5 67 2.2.1. CDNI Metadata ISO3166Code Data Type . . . . . . . . . 6 68 2.2.1.1. CDNI Metadata ISO3166Code Data Type Description . 6 69 2.2.2. CDNI Metadata ISO3166Code Footprint Type Description 6 70 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 71 3.1. CDNI Metadata Footprint Types . . . . . . . . . . . . . . 7 72 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 73 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 74 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 75 6.1. Normative References . . . . . . . . . . . . . . . . . . 8 76 6.2. Informative References . . . . . . . . . . . . . . . . . 9 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 79 1. Introduction 81 The Streaming Video Alliance [SVA] is a global association that works 82 to solve streaming video challenges in an effort to improve end-user 83 experience and adoption. The Open Caching Working Group [OCWG] of 84 the Streaming Video Alliance [SVA] is focused on the delegation of 85 video delivery requests from commerical CDNs to a caching layer at 86 the ISP's network. Open Caching architecture is a specific use case 87 of CDNI where the commercial CDN is the upstream CDN (uCDN) and the 88 ISP caching layer is the downstream CDN (dCDN). The Open Caching 89 Request Routing Specification [OC-RR] defines the Request Routing 90 process and the interfaces that are required for its provisioning. 91 This document defines and registers CDNI Footprint and Capabilities 92 objects[RFC8008] that are required for Open Caching Request Routing. 94 For consistency with other CDNI documents this document follows the 95 CDNI convention of uCDN (upstream CDN) and dCDN (downstream CDN) to 96 represent the commercial CDN and ISP caching layer respectively. 98 This document registers two CDNI Metadata Footprint Types (section 99 7.2 of [RFC8006]) for the defined objects: 101 o IPv4v6CIDR Footprint Type (for dCDN advertising a footprint that 102 consists of both IPv4 and IPv6 client addresses) 104 o ISO3166Code Footprint Type (e.g. for dCDN advertising a footprint 105 that is specific to a State in the USA) 107 1.1. Terminology 109 The following terms are used throughout this document: 111 o CDN - Content Delivery Network 113 Additionally, this document reuses the terminology defined in 114 [RFC6707], [RFC7336], [RFC8006], [RFC8007], [RFC8008], and [RFC8804]. 115 Specifically, we use the following CDNI acronyms: 117 o uCDN, dCDN - Upstream CDN and Downstream CDN respectively (see 118 [RFC7336] ) 120 1.2. Requirements Language 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 124 "OPTIONAL" in this document are to be interpreted as described in BCP 125 14 [RFC2119] [RFC8174] when, and only when, they appear in all 126 capitals, as shown here. 128 2. CDNI Metadata Additonal Footprint Types 130 Section 5 of [RFC8008] describes the FCI Capability Advertisement 131 Object, which includes an array of CDNI Footprint Objects. Each such 132 object has a footprint-type and a footprint-value, as described in 133 section 4.2.2.2 of [RFC8006]. This document defines additional 134 footprint types, beyond those mentioned in CDNI metadata [RFC8006]. 135 For consistency, this document follows the CDNI notation of uCDN for 136 (the commercial CDN) and dCDN (the ISP caching layer). 138 2.1. CDNI Metadata IPv4v6CIDR Footprint Type 140 As described in section 5 of [RFC8008], the FCI Capability 141 Advertisement Object includes an array of CDNI Footprint Objects. 142 Appendix B of [RFC8008] specifies the semantics of a Footprint 143 Objects array as a multiple, additive, footprint constraints. 144 Meaning, the advertisement of different footprint types narrows the 145 dCDN's candidacy cumulatively. 147 Sections 4.3.5 and 4.3.6 of [RFC8006] specify the "IPv4CIDR" and 148 "IPv6CIDR" footprint types, respectively, for listing IP addresses 149 blocks. Using Footprint Objects of these types, one can define an 150 FCI Capability Advertisement Object footprint constraints that match 151 IPv4 or IPv6 clients. However, the described "narrowing" semantic of 152 the Footprint Objects array prevents the usage of these objects 153 together in order to create a footprint constraint that matches IPv4 154 clients together with IPv6 clients. 156 Below is an example for an attempt at creating an object matching 157 IPv4 clients of subnet "192.0.2.0/24", as well as IPv6 clients of 158 subnet "2001:db8::/32". Such a definition results with an empty list 159 of clients, as the constraints are additives and a client address 160 cannot be both IPv4 and IPv6. 162 { 163 "capabilities": [ 164 { 165 "capability-type": , 166 "capability-value": , 167 }, 168 "footprints": [ 169 { 170 "footprint-type": "ipv4cidr", 171 "footprint-value": ["192.0.2.0/24"] 172 }, 173 { 174 "footprint-type": "ipv6cidr", 175 "footprint-value": ["2001:db8::/32"] 176 } 177 ] 178 } 179 ] 180 } 182 To overcome the described limitation and allow a list of footprint 183 constraints that matches both IPv4 and IPv6 client addresses, we 184 introduce below the "IPv4v6CIDR" simple data type as well as a 185 derived footprint type. 187 2.1.1. CDNI Metadata IPv4v6CIDR Data Type 189 The "IPv4v6CIDR" data type specified in Section 2.1.1.1, can be 190 either IPv4 or IPv6 address blocks. The data type is added to the 191 list of data types described in section 4.3 of [RFC8006] that are 192 used as properties of CDNI Metadata objects. 194 2.1.1.1. CDNI Metadata IPv4v6CIDR Data Type Description 196 Either an IPv4CIDR property or IPv6CIDR property, as described in 197 sections 4.3.5 and 4.3.6 of [RFC8006] respectively. 199 Type: String 201 Example IPv4v6CIDRs: 203 "192.0.2.0/24" 205 "2001:db8::/32" 207 2.1.2. CDNI Metadata IPv4v6CIDR Footprint Type Description 209 The "IPv4v6CIDR" simple data type specified in Section 2.1.1, is 210 added to the data types listed as footprint types in section 4.2.2.2 211 of [RFC8006]. 213 Below is an adjustment for the example in Section 2.1.1, now 214 embedding a footprint object of type "IPv4v6CIDR". 216 { 217 "capabilities": [ 218 { 219 "capability-type": , 220 "capability-value": , 221 }, 222 "footprints": [ 223 { 224 "footprint-type": "ipv4v6cidr", 225 "footprint-value": ["192.0.2.0/24", "2001:db8::/32"] 226 } 227 ] 228 } 229 ] 230 } 232 2.2. CDNI Metadata ISO3166Code Footprint Type 234 Section 4.3.8 of [RFC8006] specifies the "Country Code" footprint 235 type for listing [ISO3166-1] alpha-2 codes. Using Footprint Objects 236 of this type, one can define an FCI Capability Advertisement Object 237 footprint constraints that match a specific country. Here we define 238 the iso3166code simple data type, as well as a footprint type 239 allowing the dCDN to define constraints matching geographic areas 240 with better granularity, specifically using the [ISO3166-2] Country 241 Subdivision codes. 243 2.2.1. CDNI Metadata ISO3166Code Data Type 245 The "ISO3166Code" data type specified in Section 2.2.1.1, can either 246 describe a country based on an [ISO3166-1] alpha-2 code, or describe 247 a more specific subdivision using an [ISO3166-2] code. The data type 248 is added to the list of data types described in section 4.3 of 249 [RFC8006] that are used as properties of CDNI Metadata objects. 251 2.2.1.1. CDNI Metadata ISO3166Code Data Type Description 253 Either an [ISO3166-1] alpha-2 code in lowercase, or such a code 254 followed by a dash as well as a more specific subdivision [ISO3166-2] 255 alphanumeric code in lowercase. 257 Type: String 259 Example ISO3166Codes: 261 "ca" 263 "us-ny" 265 2.2.2. CDNI Metadata ISO3166Code Footprint Type Description 267 The "ISO3166Code" simple data type specified in Section 2.2.1 , is 268 added to the data types listed as footprint types in section 4.2.2.2 269 of [RFC8006] . 271 Below is an adjustment for the example in Section 2.2.1 , now 272 embedding a footprint object of type "ISO3166Code". The Footprint 273 Object in this example creates a constraints matching clients both in 274 Canada (ISO [ISO3166-1] alpha-2 code "CA") as well as in the state of 275 New-York (ISO [ISO3166-2] Subdivision code "NY") in the (ISO 276 [ISO3166-1] alpha-2 code "US"). 278 { 279 "capabilities": [ 280 { 281 "capability-type": , 282 "capability-value": , 283 }, 284 "footprints": [ 285 { 286 "footprint-type": "iso3166code", 287 "footprint-value": ["ca", "us-ny"] 288 } 289 ] 290 } 291 ] 292 } 294 3. IANA Considerations 296 3.1. CDNI Metadata Footprint Types 298 As described in section 7.2 of [RFC8006] , the "CDNI Metadata 299 Footprint Types" subregistry was created within the "Content Delivery 300 Network Interconnection (CDNI) Parameters" registry. The created 301 namespace defines the valid values for Footprint Object Types, and is 302 already populated with the types described in Section 4.2.2.2 of 303 [RFC8006] . 305 This document requests the registration of the two additional 306 footprint type as defined in Section 2.1 and Section 2.2 : 308 +--------------------+--------------------------+-------------------+ 309 | Footprint | Description | Specification | 310 | Type | | | 311 +--------------------+--------------------------+-------------------+ 312 | ipv4v6cidr | IPv4/IPv6 address block | RFCthis | 313 | iso3166code | ISO 3166-1/2 Country or | RFCthis | 314 | | Subdivision Code | | 315 +--------------------+--------------------------+-------------------+ 317 [RFC Editor: Please replace RFCthis with the published RFC number for 318 this document.] 320 4. Security Considerations 322 This specification is in accordance with the CDNI Request Routing: 323 Footprint and Capabilities Semantics. As such, it is subject to the 324 security and privacy considerations as defined in Section 8 of 325 [RFC8006] and in Section 7 of [RFC8008] respectively. 327 5. Acknowledgements 329 The authors would like to express their gratitude to Ori Finkelman 330 and Kevin J. Ma for their guidance and reviews throughout the 331 development of this document. 333 6. References 335 6.1. Normative References 337 [ISO3166-1] 338 ISO, "Codes for the representation of names of countries 339 and their subdivisions -- Part 1: Country code", 340 ISO 3166-1:2020, Edition 4, 08 2020, 341 . 343 [ISO3166-2] 344 ISO, "Codes for the representation of names of countries 345 and their subdivisions -- Part 2: Country subdivision 346 code", ISO 3166-2:2020, Edition 4, 08 2020, 347 . 349 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 350 Requirement Levels", BCP 14, RFC 2119, 351 DOI 10.17487/RFC2119, March 1997, 352 . 354 [RFC8006] Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, 355 "Content Delivery Network Interconnection (CDNI) 356 Metadata", RFC 8006, DOI 10.17487/RFC8006, December 2016, 357 . 359 [RFC8007] Murray, R. and B. Niven-Jenkins, "Content Delivery Network 360 Interconnection (CDNI) Control Interface / Triggers", 361 RFC 8007, DOI 10.17487/RFC8007, December 2016, 362 . 364 [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg, 365 R., and K. Ma, "Content Delivery Network Interconnection 366 (CDNI) Request Routing: Footprint and Capabilities 367 Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016, 368 . 370 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 371 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 372 May 2017, . 374 [RFC8804] Finkelman, O. and S. Mishra, "Content Delivery Network 375 Interconnection (CDNI) Request Routing Extensions", 376 RFC 8804, DOI 10.17487/RFC8804, September 2020, 377 . 379 6.2. Informative References 381 [OC-RR] Finkelman, O., Ed., Hofmann, J., Klein, E., Mishra, S., 382 Ma, K., Sahar, D., and B. Zurat, "Open Caching - Request 383 Routing Functional Specification", Version 1.1, October 384 2019, . 387 [OCWG] "Open Caching Home Page", 388 . 391 [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content 392 Distribution Network Interconnection (CDNI) Problem 393 Statement", RFC 6707, DOI 10.17487/RFC6707, September 394 2012, . 396 [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., 397 "Framework for Content Distribution Network 398 Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, 399 August 2014, . 401 [SVA] "Streaming Video Alliance Home Page", 402 . 404 Authors' Addresses 405 Nir B. Sopher 406 Qwilt 408 6, Ha'harash 410 Hod HaSharon 411 , 413 4524079 415 Israel 417 Email: 418 nir@apache.org 420 Sanjay Mishra 421 Verizon 422 13100 Columbia Pike 423 Silver Spring, MD 20904 424 USA 426 Email: sanjay.mishra@verizon.com