| Internet-Draft | Content Delivery Network Interconnection | November 2021 |
| Sopher & Mishra | Expires 11 May 2022 | [Page] |
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.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 11 May 2022.¶
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The Streaming Video Alliance [SVA] 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 [OCWG] of the Streaming Video Alliance [SVA] 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 Open Caching Request Routing Specification [OC-RR] defines the Request Routing process and the interfaces that are required for its provisioning. This document defines and registers CDNI Footprint and Capabilities objects[RFC8008] that are required for Open Caching Request Routing.¶
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.¶
This document registers two CDNI Metadata Footprint Types (section 7.2 of [RFC8006]) for the defined objects:¶
The following terms are used throughout this document:¶
Additionally, this document reuses the terminology defined in [RFC6707], [RFC7336], [RFC8006], [RFC8007], [RFC8008], and [RFC8804]. Specifically, we use the following CDNI acronyms:¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Section 5 of [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 [RFC8006]. This document defines additional footprint types, beyond those mentioned in CDNI metadata [RFC8006]. For consistency, this document follows the CDNI notation of uCDN for (the commercial CDN) and dCDN (the ISP caching layer).¶
Section 4.3.8 of [RFC8006] specifies the "Country Code" footprint type for listing [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 subdivisioncode simple data type, as well as a footprint type allowing the dCDN to define constraints matching geographic areas with better granularity, specifically using the [ISO3166-2] Country Subdivision codes.¶
The "SubdivisionCode" data type specified in Section 2.1.1.1, describes a country specific subdivision using an [ISO3166-2] code. The data type is added to the list of data types described in section 4.3 of [RFC8006] that are used as properties of CDNI Metadata objects.¶
A [ISO3166-2] code in lower case. Each code consists of two parts, separated by a hyphen. The first part is the [ISO3166-1] code of the country. The second part is a string of up to three alphanumeric characters.¶
The "SubdivisionCode" simple data type specified in Section 2.1.1 , is added to the data types listed as footprint types in section 4.2.2.2 of [RFC8006] .¶
Below is an adjustment for the example in Section 2.1.1, now embedding a footprint object of type "SubdivisionCode". The Footprint Object in this example creates a constraints matching clients both in Nova-Scotia province of Canada (ISO [ISO3166-2] code "CA-NS"), as well as in the state of New-York In the US (ISO [ISO3166-2] code "US-NY").¶
{
"capabilities": [
{
"capability-type": <CDNI capability object type>,
"capability-value": <CDNI capability object>,
"footprints": [
{
"footprint-type": "subdivisioncode",
"footprint-value": ["ca-ns", "us-ny"]
}
]
}
]
}
¶
As described in section 5 of [RFC8008], the FCI Capability Advertisement Object includes an array of CDNI Footprint Objects. Appendix B of [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.¶
Sections 4.3.5 and 4.3.6 of [RFC8006] specify the "IPv4CIDR" and "IPv6CIDR" footprint types, respectively, for listing IP 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.¶
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.¶
{
"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"]
}
]
}
]
}
¶
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 subdivisioncode.¶
The "FootprintUnion" data type is based on the Footprint Object already defined in section 4.2.2.2 of [RFC8006]. It includes a footprint-type property and a footprint-value array values.¶
The "footprintunion" data type specified in Section 2.2.1, is added to the data types listed as footprint types in section 4.2.2.2 of [RFC8006].¶
Below is an adjustment for the example in Section 2.2.1, now embedding a footprint object of type "footprintunion".¶
{
"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"]
}
]
}
]
}
]
}
¶
An additional example is the collection of countrycode and subdivisioncode based footprint objects. In the example below we create a constraint covering autonomous system 64496 within the US (ISO [ISO3166-1] alpha-2 code "US"), as well as Nova-Scotia province of Canada (ISO [ISO3166-2] code "CA-NS").¶
{
"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": "subdivisioncode",
"footprint-value": ["ca-ns"]
}
]
}
]
}
]
}
¶
As described in section 7.2 of [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 [RFC8006] .¶
This document requests the registration of the two additional footprint type as defined in Section 2.2 and Section 2.1 :¶
| Footprint Type | Description | Specification |
|---|---|---|
| FCI.subdivisioncode | ISO 3166-2 Country or Subdivision Code | RFCthis |
| FCI.footprintunion | Footprint Object as specified in [RFC8006] | RFCthis |
[RFC Editor: Please replace RFCthis with the published RFC number for this document.]¶
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 [RFC8006] and in Section 7 of [RFC8008] respectively.¶
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.¶