forked from orifinkelman-zz/cdni-extensions
-
Notifications
You must be signed in to change notification settings - Fork 1
/
draft-ietf-cdni-footprint-types-extensions.xml
555 lines (545 loc) · 24.7 KB
/
draft-ietf-cdni-footprint-types-extensions.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="4"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<rfc category="std" docName="draft-ietf-cdni-footprint-types-extensions-00" updates='8006,8008' ipr="trust200902">
<front>
<title abbrev="CDNI Footprint Types Extensions">
CDNI Request Routing Extensions
</title>
<author fullname="Nir B. Sopher" initials="N." surname="Sopher">
<organization>
Qwilt
</organization>
<address>
<postal>
<street>
6, Ha'harash
</street>
<city>
Hod HaSharon
</city>
<region>
</region>
<code>
4524079
</code>
<country>
Israel
</country>
</postal>
<email>
nir@apache.org
</email>
</address>
</author>
<author fullname="Sanjay Mishra" initials="S." surname="Mishra">
<organization>Verizon</organization>
<address>
<postal>
<street>13100 Columbia Pike</street>
<city>Silver Spring</city>
<region>MD</region>
<code>20904</code>
<country>USA</country>
</postal>
<phone></phone>
<email>sanjay.mishra@verizon.com</email>
</address>
</author>
<date />
<abstract>
<t>
Open Caching architecture is a use case of Content Delivery Networks Interconnection (CDNI) in which the
commercial Content Delivery Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer serves as the
downstream CDN (dCDN). This document supplements to the CDNI Metadata Footprint Types defined in RFC 8006.
The Footprint Types defined in this document can be used for Footprint objects as part of
the Footprint & Capabilities Advertisement interface (FCI) defined in RFC 8008. The defined Footprint Types
are derived from requirements raised by Open Caching but are also applicable to CDNI use cases in general.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
The Streaming Video Alliance <xref target="SVA" format="default" /> is a global association
that works to solve streaming video challenges in an effort to improve end-user experience
and adoption. The Open Caching Working Group <xref target="OCWG" format="default" /> of the
Streaming Video Alliance <xref target="SVA" format="default" /> is focused on the delegation
of video delivery requests from commerical CDNs to a caching layer at the ISP's network.
Open Caching architecture is a specific use case of CDNI where the commercial CDN is the
upstream CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN).
The <xref target="OC-RR"> Open Caching Request Routing Specification </xref>
defines the Request Routing process and the interfaces that are required for its provisioning.
This document defines and registers CDNI Footprint and Capabilities objects<xref target="RFC8008" />
that are required for Open Caching Request Routing.
</t>
<t>
For consistency with other CDNI documents this document follows the
CDNI convention of uCDN (upstream CDN) and dCDN (downstream CDN) to represent the commercial CDN and ISP caching
layer respectively.
</t>
<t>
This document registers two CDNI Metadata Footprint Types (section 7.2 of
<xref target="RFC8006" />) for the defined objects:
<list style="symbols">
<t>
ISO3166-2Code Footprint Type (e.g. for dCDN advertising a footprint that is specific to
a State in the USA)
</t>
<t>
Collection Footprint Type (for dCDN advertising a footprint that consists of a group built
from multiple Footprints Types. E.g. both IPv4 and IPv6 client addresses)
</t>
</list>
</t>
<section anchor="terminology" title="Terminology">
<t>
The following terms are used throughout this document:
<list style="symbols">
<t>
CDN - Content Delivery Network
</t>
</list>
</t>
<t>
Additionally, this document reuses the terminology defined in
<xref target="RFC6707" />,
<xref target="RFC7336" />,
<xref target="RFC8006" />,
<xref target="RFC8007" />,
<xref target="RFC8008" />, and
<xref target="RFC8804" />.
Specifically, we use the following CDNI acronyms:
<list style="symbols">
<t>
uCDN, dCDN - Upstream CDN and Downstream CDN respectively (see
<xref target="RFC7336" />
)
</t>
</list>
</t>
</section>
<section title="Requirements Language">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14
<xref target="RFC2119" />
<xref target="RFC8174" />
when, and only when, they appear in all capitals, as shown here.
</t>
</section>
</section>
<section anchor="cdni-metadata-additional-footprint-types" title="CDNI Metadata Additonal Footprint Types">
<t>
Section 5 of <xref target="RFC8008" /> describes the FCI Capability Advertisement Object, which
includes an array of CDNI Footprint Objects. Each such object has a footprint-type and
a footprint-value, as described in section 4.2.2.2 of <xref target="RFC8006" />.
This document defines additional footprint types, beyond those mentioned in CDNI metadata
<xref target="RFC8006" />.
For consistency, this document follows the CDNI notation of uCDN for
(the commercial CDN) and dCDN (the ISP caching layer).
</t>
<section anchor="cdni-metadata-iso3166-2code-footprint-type" title="CDNI Metadata ISO3166-2Code Footprint Type">
<t>
Section 4.3.8 of <xref target="RFC8006" />
specifies the "Country Code" footprint type
for listing <xref target="ISO3166-1"/> alpha-2 codes. Using Footprint Objects of this type, one can define an
FCI Capability Advertisement Object footprint constraints that match a specific country.
Here we define the iso3166-2code simple data type, as well as a footprint type
allowing the dCDN to define constraints matching geographic areas
with better granularity, specifically using the <xref target="ISO3166-2"/> Country Subdivision codes.
</t>
<section anchor="cdni-metadata-iso3166-2code-data-type" title="CDNI Metadata ISO3166-2Code Data Type">
<t>
The "ISO3166-2Code" data type specified in
<xref target="cdni-metadata-iso3166-2code-data-type-description" />,
describes a country specific subdivision using an <xref target="ISO3166-2"/> code.
The data type is added to the list of data types described in section 4.3 of
<xref target="RFC8006" /> that are used as properties of CDNI Metadata objects.
</t>
<section anchor="cdni-metadata-iso3166-2code-data-type-description" title="CDNI Metadata ISO3166-2Code Data Type Description">
<t>
A <xref target="ISO3166-2"/> code in lower case. Each code consists of two parts, separated by a hyphen.
The first part is the <xref target="ISO3166-1"/> code of the country. The second part is a string of up to three alphanumeric characters.
</t>
<t>
<list style="empty">
<t>
Type: String
</t>
<t>
Example ISO3166-2Codes:
</t>
<t>
"us-nj"
</t>
<t>
"us-ny"
</t>
</list>
</t>
</section>
</section>
<section anchor="cdni-metadata-iso3166-2code-footprint-type-description" title="CDNI Metadata ISO3166-2Code Footprint Type Description">
<t>
The "ISO3166-2Code" simple data type specified in
<xref target="cdni-metadata-iso3166-2code-data-type" />
, is added
to the data types listed as footprint types in section 4.2.2.2 of
<xref target="RFC8006" />
.
</t>
<t>
Below is an adjustment for the example in
<xref target="cdni-metadata-iso3166-2code-data-type" />,
now embedding a footprint object of type "ISO3166-2Code". The Footprint Object in this example creates
a constraint matching clients in the states of New Jersey and New York (ISO <xref target="ISO3166-2"/> codes "US-NJ" and "US-NY" respectively).
</t>
<figure>
<artwork>
<![CDATA[
{
"capabilities": [
{
"capability-type": <CDNI capability object type>,
"capability-value": <CDNI capability object>,
"footprints": [
{
"footprint-type": "iso3166-2code",
"footprint-value": ["us-nj", "us-ny"]
}
]
}
]
}
]]>
</artwork>
</figure>
</section>
</section>
<section anchor="cdni-metadata-footprint-union-footprint-type" title="CDNI Metadata FootprintUnion Footprint Type">
<t>
As described in section 5 of <xref target="RFC8008" />,
the FCI Capability Advertisement Object includes an array of CDNI Footprint Objects.
Appendix B of <xref target="RFC8008" /> specifies the
semantics of a Footprint Objects array as a multiple, additive, footprint constraints.
Meaning, the advertisement of different footprint types narrows
the dCDN's candidacy cumulatively.
</t>
<t>
Sections 4.3.5 and 4.3.6 of <xref target="RFC8006" /> specify the "IPv4CIDR" and "IPv6CIDR"
footprint types, respectively, for listing IP unscoped addresses blocks. Using Footprint Objects of these
types, one can define an FCI Capability Advertisement Object footprint constraints that match IPv4
or IPv6 clients. However, the described "narrowing" semantic of the Footprint Objects array prevents
the usage of these objects together in order to create a footprint constraint that matches IPv4
clients together with IPv6 clients.
</t>
<t>
Below is an example for an attempt at creating an object matching
IPv4 clients of subnet "192.0.2.0/24", as well as IPv6 clients of subnet "2001:db8::/32".
Such a definition results with an empty list of clients, as the constraints are additives and
a client address cannot be both IPv4 and IPv6.
</t>
<figure>
<artwork>
<![CDATA[
{
"capabilities": [
{
"capability-type": <CDNI capability object type>,
"capability-value": <CDNI capability object>,
"footprints": [
{
"footprint-type": "ipv4cidr",
"footprint-value": ["192.0.2.0/24"]
},
{
"footprint-type": "ipv6cidr",
"footprint-value": ["2001:db8::/32"]
}
]
}
]
}
]]>
</artwork>
</figure>
<t>
To overcome the described limitation, and allow a list of footprint constraints that
matches both IPv4 and IPv6 client addresses, we introduce below the "FootprintUnion" footprint type.
This footprint type allows the collection of multiple footprint-objects into a unified object.
It is useful for resolving the above limitaion, as well as for unifying footprints of additional types such as
countrycode and iso3166-2code.
</t>
<section anchor="cdni-metadata-footprint-union-data-type" title="CDNI Metadata FootprintUnion Data Type">
<t>
The "FootprintUnion" data type is based on the Footprint Object already defined in
section 4.2.2.2 of <xref target="RFC8006" />. It includes a footprint-type property and a footprint-value
array values.
</t>
</section>
<section anchor="cdni-metadata-footprint-union-footprint-type-description" title="CDNI Metadata FootprintUnion Footprint Type Description">
<t>
The "footprintunion" data type specified in <xref target="cdni-metadata-footprint-union-data-type" />,
is added to the data types listed as footprint types in section 4.2.2.2 of <xref target="RFC8006" />.
</t>
<t>
Below is an adjustment for the example in <xref target="cdni-metadata-footprint-union-data-type" />,
now embedding a footprint object of type "footprintunion".
</t>
<figure>
<artwork>
<![CDATA[
{
"capabilities": [
{
"capability-type": <CDNI capability object type>,
"capability-value": <CDNI capability object>,
"footprints": [
{
"footprint-type": "footprintunion",
"footprint-value": [
{
"footprint-type": "ipv4cidr",
"footprint-value": ["192.0.2.0/24"]
},
{
"footprint-type": "ipv6cidr",
"footprint-value": ["2001:db8::/32"]
}
]
}
]
}
]
}
]]>
</artwork>
</figure>
<t>
An additional example is the collection of countrycode and iso3166-2code based footprint objects. In the example below
we create a constraint covering autonomous system 64496 within the US (ISO <xref target="ISO3166-1"/> alpha-2 code "US"),
as well as Ontario province of Canada (ISO <xref target="ISO3166-2"/> code "CA-ON").
</t>
<figure>
<artwork>
<![CDATA[
{
"capabilities": [
{
"capability-type": <CDNI capability object type>,
"capability-value": <CDNI capability object>,
"footprints": [
{
"footprint-type": "asn",
"footprint-value": ["as64496"]
},
{
"footprint-type": "footprintunion",
"footprint-value": [
{
"footprint-type": "countrycode",
"footprint-value": ["us"]
},
{
"footprint-type": "iso3166-2code",
"footprint-value": ["ca-on"]
}
]
}
]
}
]
}
]]>
</artwork>
</figure>
</section>
</section>
</section>
<section anchor="IANA" title="IANA Considerations">
<section anchor="IANA.cdni.metadata.footprint.types" title="CDNI Metadata Footprint Types">
<t>
As described in section 7.2 of
<xref target="RFC8006" />
, the "CDNI Metadata Footprint Types" subregistry
was created within the "Content Delivery Network Interconnection (CDNI) Parameters" registry. The created
namespace defines the valid values for Footprint Object Types, and is already populated with the types
described in Section 4.2.2.2 of
<xref target="RFC8006" />
.
</t>
<t>
This document requests the registration of the two additional footprint type
as defined in
<xref target="cdni-metadata-footprint-union-footprint-type" />
and
<xref target="cdni-metadata-iso3166-2code-footprint-type" />
:
</t>
<texttable>
<ttcol align="left">
Footprint Type
</ttcol>
<ttcol align="left">
Description
</ttcol>
<ttcol align="left">
Specification
</ttcol>
<c>
FCI.iso3166-2code
</c>
<c>
ISO 3166-2 Country or Subdivision Code
</c>
<c>
RFCthis
</c>
<c>
FCI.footprintunion
</c>
<c>
Footprint Object as specified in <xref target="RFC8006" />
</c>
<c>
<xref target="RFC8006" />
</c>
</texttable>
<t>
[RFC Editor: Please replace RFCthis with the published RFC
number for this document.]
</t>
</section>
</section>
<section anchor="Security" title="Security Considerations">
<t>
This specification is in accordance with the CDNI Request Routing:
Footprint and Capabilities Semantics. As such, it is subject to the security and privacy considerations as
defined in Section 8 of
<xref target="RFC8006" />
and in Section 7 of
<xref target="RFC8008" />
respectively.
</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>
The authors would like to express their gratitude to Ori Finkelman and
Kevin J. Ma for their guidance and reviews throughout the development of this
document.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.8006"?>
<?rfc include="reference.RFC.8007"?>
<?rfc include="reference.RFC.8008"?>
<?rfc include="reference.RFC.8174"?>
<?rfc include="reference.RFC.8804"?>
<reference anchor="ISO3166-1" target="https://www.iso.org/standard/72482.html">
<front>
<title>
Codes for the representation of names of countries and their subdivisions -- Part 1: Country code
</title>
<author>
<organization>ISO</organization>
</author>
<date month="08" year="2020"/>
</front>
<seriesInfo name="ISO" value="3166-1:2020"/>
<seriesInfo name="Edition" value="4"/>
</reference>
<reference anchor="ISO3166-2" target="https://www.iso.org/standard/72483.html">
<front>
<title>
Codes for the representation of names of countries and their subdivisions -- Part 2: Country subdivision code
</title>
<author>
<organization>ISO</organization>
</author>
<date month="08" year="2020"/>
</front>
<seriesInfo name="ISO" value="3166-2:2020"/>
<seriesInfo name="Edition" value="4"/>
</reference>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.6707"?>
<?rfc include="reference.RFC.7336"?>
<reference anchor="SVA" target="https://www.streamingvideoalliance.org">
<front>
<title>
Streaming Video Alliance Home Page
</title>
<author />
<date />
</front>
</reference>
<reference anchor="OCWG" target="https://www.streamingvideoalliance.org/technical-groups/open-caching/">
<front>
<title>
Open Caching Home Page
</title>
<author />
<date />
</front>
</reference>
<reference anchor="OC-RR" target="https://www.streamingvideoalliance.org/books/open-cache-request-routing-functional-specification/">
<front>
<title>
Open Caching - Request Routing Functional Specification
</title>
<author initials="O." surname="Finkelman" fullname="Ori Finkelman" role="editor">
<organization>
Qwilt
</organization>
</author>
<author initials="J." surname="Hofmann" fullname="Jason Hofmann">
<organization>
Limelight Networks
</organization>
</author>
<author initials="E." surname="Klein" fullname="Eric Klein">
<organization>
Disney Streaming Services
</organization>
</author>
<author initials="S." surname="Mishra" fullname="Sanjay Mishra">
<organization>
Verizon
</organization>
</author>
<author initials="K." surname="Ma" fullname="Kevin J. Ma">
<organization>
Disney Streaming Services
</organization>
</author>
<author initials="D." surname="Sahar" fullname="Dan Sahar">
<organization>
Qwilt
</organization>
</author>
<author initials="B." surname="Zurat" fullname="Bill Zurat">
<organization>
Disney Streaming Services
</organization>
</author>
<date day="4" month="October" year="2019" />
</front>
<seriesInfo name="Version" value="1.1" />
</reference>
</references>
</back>
</rfc>