HFT Stuttgart - Univ. of Applied Sciences

Schellingstrasse 24 Stuttgart 70174 Germany +49-0711-8926-2801 jan.seedorf@hft-stuttgart.de

Yale University

51 Prospect Street New Haven CT 06511 USA +1-203-432-6400 yry@cs.yale.edu http://www.cs.yale.edu/~yry/

Ericsson

43 Nagog Park Acton MA 01720 USA +1-978-844-5100 kevin.j.ma.ietf@gmail.com

NeuStar

1800 Sutter St Suite 570 Concord CA 94520 USA jon.peterson@neustar.biz

Tongji University

4800 Cao'an Hwy Shanghai 201804 China jingxuan.zhang@tongji.edu.cn

Networks ALTO & CDNI WGs ALTO The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008.

Introduction The ability to interconnect multiple content delivery networks (CDNs) has many benefits, including increased coverage, capability, and reliability. The Content Delivery Networks Interconnection (CDNI) framework defines four interfaces to interconnect CDNs: (1) the CDNI Request Routing Interface, (2) the CDNI Metadata Interface, (3) the CDNI Logging Interface, and (4) the CDNI Control Interface. Among these four interfaces, the CDNI Request Routing Interface provides key functions, as specified in : "The CDNI Request Routing interface enables a Request Routing function in an Upstream CDN to query a Request Routing function in a Downstream CDN to determine if the Downstream CDN is able (and willing) to accept the delegated Content Request. It also allows the Downstream CDN to control what should be returned to the User Agent in the redirection message by the upstream Request Routing function." At a high level, the scope of the CDNI Request Routing Interface, therefore, contains two main tasks: (1) determining if the dCDN (downstream CDN) is willing to accept a delegated content request, and (2) redirecting the content request coming from a uCDN (upstream CDN) to the proper entry point or entity in the dCDN. Correspondingly, the Request Routing Interface is broadly divided into two functionalities: (1) the CDNI Footprint & Capabilities Advertisement interface (FCI) defined in , and (2) the CDNI Request Routing Redirection interface (RI) defined in . This document focuses on the first functionality (CDNI FCI). Specifically, CDNI FCI allows both an advertisement from a dCDN to a uCDN (push) and a query from a uCDN to a dCDN (pull) so that the uCDN knows whether it can redirect a particular user request to that dCDN. A key component in defining CDNI FCI is defining objects describing the footprints and capabilities of a dCDN. Such objects are already defined in Section 5 of . However, no protocol is defined to transport and update such objects between a uCDN and a dCDN. To define such a protocol, this document specifies an extension of the Application-Layer Traffic Optimization (ALTO) protocol by introducing a new ALTO service called "CDNI Advertisement Service". discusses the benefits in using ALTO as a transport protocol.

Terminology and Background 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 when, and only when, they appear in all capitals, as shown here. The design of CDNI FCI transport using ALTO assumes an understanding of both FCI semantics and ALTO. Hence, this document starts with a non-normative review for both.

Terminology The document uses the CDNI terms defined in , and . Also, the document uses the ALTO terms defined in and . This document uses the following abbreviations:

• ALTO: Application-Layer Traffic Optimization
• ASN: Autonomous System Number
• CDN: Content Delivery Network
• CDNI: CDN Interconnection
• dCDN: Downstream CDN
• FCI: CDNI FCI, CDNI Request Routing Footprint & Capabilities Advertisement interface
• IRD: Information Resource Directory in ALTO
• PID: Provider-defined Identifier in ALTO
• uCDN: Upstream CDN

Semantics of FCI Advertisement defines the semantics of CDNI FCI, provides guidance on what Footprint and Capabilities mean in a CDNI context, and specifies the requirements on the CDNI FCI transport protocol. The definitions in depend on . Below is a non-normative review of key related points of and . For detailed information and normative specification, the reader should refer to these two RFCs.

• Multiple types of mandatory-to-implement footprints (i.e., ipv4cidr, ipv6cidr, asn, and countrycode) are defined in . A "Set of IP-prefixes" can contain both full IP addresses (i.e., a /32 for IPv4 or a /128 for IPv6) and IP prefixes with an arbitrary prefix length. There must also be support for multiple IP address versions, i.e., IPv4 and IPv6, in such a footprint.
• Multiple initial types of capabilities are defined in including (1) Delivery Protocol, (2) Acquisition Protocol, (3) Redirection Mode, (4) Capabilities related to CDNI Logging, and (5) Capabilities related to CDNI Metadata. They are required in all cases and, therefore, considered as mandatory-to-implement capabilities for all CDNI FCI implementations.
• Footprint and capabilities are defined together and cannot be interpreted independently from each other. Specifically, integrates footprint and capabilities with an approach of "capabilities with footprint restrictions", by expressing capabilities on a per footprint basis.
• Specifically, for all mandatory-to-implement footprint types, footprints can be viewed as constraints for delegating requests to a dCDN: A dCDN footprint advertisement tells the uCDN the limitations for delegating a request to the dCDN. For IP prefixes or Autonomous System Numbers (ASNs), the footprint signals to the uCDN that it should consider the dCDN a candidate only if the IP address of the request routing source falls within the prefix set or ASN, respectively. The CDNI specifications do not define how a given uCDN determines what address ranges are in a particular ASN. Similarly, for country codes, a uCDN should only consider the dCDN a candidate if it covers the country of the request routing source. The CDNI specifications do not define how a given uCDN determines the country of the request routing source. Different types of footprint constraints can be combined together to narrow the dCDN candidacy, i.e., the uCDN should consider the dCDN a candidate only if the request routing source satisfies all the types of footprint constraints in the advertisement.
• Given that a large part of Footprint and Capabilities Advertisement may happen in contractual agreements, the semantics of CDNI Footprint and Capabilities advertisement refers to answering the following question: what exactly still needs to be advertised by the CDNI FCI? For instance, updates about temporal failures of part of a footprint can be useful information to convey via the CDNI FCI. Such information would provide updates on information previously agreed in contracts between the participating CDNs. In other words, the CDNI FCI is a means for a dCDN to provide changes/updates regarding a footprint and/or capabilities that it has previously agreed to serve in a contract with a uCDN. Hence, server push and incremental encoding will be necessary techniques.

ALTO Background and Benefits Application-Layer Traffic Optimization (ALTO) defines an approach for conveying network layer (topology) information to "guide" the resource provider selection process in distributed applications that can choose among several candidate resources providers to retrieve a given resource. Usually, it is assumed that an ALTO server conveys information that these applications cannot measure or have difficulty measuring themselves . Originally, ALTO was motivated by optimizing cross-ISP traffic generated by P2P applications . However, ALTO can also be used for improving the request routing in CDNs. In particular, Section 5 of explicitly mentions ALTO as a candidate protocol to improve the selection of a CDN surrogate or origin. The following reasons make ALTO a suitable candidate protocol for dCDN selection as part of CDNI request routing and, in particular, for an FCI protocol:

• Application Layer-oriented: ALTO is a protocol specifically designed to improve application layer traffic (and application layer connections among hosts on the Internet) by providing additional information to applications that these applications could not easily retrieve themselves. This matches the need of CDNI, where a uCDN wants to improve application layer CDN request routing by using information (provided by a dCDN) that the uCDN could not easily obtain otherwise. Hence, ALTO can help a uCDN to select a proper dCDN by first providing dCDNs' capabilities as well as footprints (see ) and then providing costs of surrogates in a dCDN by ALTO cost maps.
• Security: The identification between uCDNs and dCDNs is an important requirement (see ). ALTO maps can be signed and hence provide inherent origin protection. Please see Section 15.1.2 of for detailed protection strategies.
• RESTful design: The ALTO protocol has undergone extensive revisions in order to provide a RESTful design regarding the client-server interaction specified by the protocol. It is flexible and extensible enough to handle existing and potential future data formats defined by CDNI. It can provide the consistent client-server interaction model for other existing CDNI interfaces or potential future extensions and therefore reduce the learning cost for both users and developers, although they are not in the scope of this document. A CDNI FCI interface based on ALTO would inherit this RESTful design. Please see .
• Error-handling: The ALTO protocol provides extensive error-handling in the whole request and response process (see Section 8.5 of ). A CDNI FCI interface based on ALTO would inherit this extensive error-handling framework. Please see .
• Map Service: The semantics of an ALTO network map is an exact match for the needed information to convey a footprint by a dCDN, in particular, if such a footprint is being expressed by IP-prefix ranges. Please see .
• Filtered Map Service: The ALTO map filtering service would allow a uCDN to query only for parts of an ALTO map. For example, the ALTO filtered property map service can enable a uCDN to query properties of a part of footprints efficiently. Please see .
• Server-initiated notifications and incremental updates: When the footprint or the capabilities of a dCDN change (i.e., unexpectedly from the perspective of a uCDN), server-initiated notifications would enable a dCDN to inform a uCDN about such changes directly. Consider the case where - due to failure - part of the footprint of the dCDN is not functioning, i.e., the CDN cannot serve content to such clients with reasonable QoS. Without server-initiated notifications, the uCDN might still use a recent network and cost map from the dCDN, and therefore redirect requests to the dCDN which it cannot serve. Similarly, the possibility for incremental updates would enable efficient conveyance of the aforementioned (or similar) status changes by the dCDN to the uCDN. The newest design of ALTO supports server pushed incremental updates .
• Content availability on hosts: A dCDN might want to express CDN capabilities in terms of certain content types (e.g., codecs/ formats, or content from certain content providers). ALTO Entity Property Map would enable a dCDN to make such information available to a uCDN. This would enable a uCDN to access whether a dCDN has the capabilities for a given type of content requested.
• Resource availability on hosts or links: The capabilities on links (e.g., maximum bandwidth) or caches (e.g., average load) might be useful information for a uCDN for optimized dCDN selection. For instance, if a uCDN receives a streaming request for content with a certain bitrate, it needs to know if it is likely that a dCDN can fulfill such stringent application-level requirements (i.e., can be expected to have enough consistent bandwidth) before it redirects the request. In general, if ALTO could convey such information via ALTO Entity Property Map , it would enable more sophisticated means for dCDN selection with ALTO. ALTO Path Vector Extension is designed to allow ALTO clients to query information such as capacity regions for a given set of flows.

CDNI Advertisement Service The ALTO protocol relies upon the ALTO Information Service framework which consists of multiple services. All ALTO services are "provided through a common transport protocol, messaging structure and encoding, and transaction model" . The ALTO protocol specification defines multiple initial services, e.g., the ALTO network map service and cost map service. This document defines a new ALTO service, called "CDNI Advertisement Service", which conveys JSON objects of media type "application/alto-cdni+json". These JSON objects are used to transport BaseAdvertisementObject objects defined in . This document specifies how to transport such BaseAdvertisementObject objects via the ALTO protocol with the ALTO "CDNI Advertisement Service". Similar to other ALTO services, this document defines the ALTO information resource for the "CDNI Advertisement Service" as follows. Note that the encoding of BaseAdvertisementObject reuses the one defined in and therefore also follows the recommendations of I-JSON (Internet JSON) , which is required by .

Media Type The media type of the CDNI Advertisement resource is "application/alto-cdni+json" (see ).

HTTP Method A CDNI Advertisement resource is requested using the HTTP GET method.

Accept Input Parameters There are no applicable Accept Input parameters.

Capabilities There are no applicable capabilities.

Uses The "uses" field MUST NOT appear unless the CDNI Advertisement resource depends on other ALTO information resources. If the CDNI Advertisement resource has dependent resources, the resource IDs of its dependent resources MUST be included into the "uses" field. This document only defines one potential dependent resource for the CDNI Advertisement resource. See for details of when and how to use it. Future documents may extend the CDNI Advertisement resource and allow other dependent resources.

Response The "meta" field of a CDNI Advertisement response MUST include the "vtag" field defined in Section 10.3 of . This field provides the version of the retrieved CDNI FCI resource. If a CDNI Advertisement response depends on other ALTO information resources, it MUST include the "dependent-vtags" field, whose value is an array to indicate the version tags of the resources used, where each resource is specified in "uses" of its Information Resource Directory (IRD) entry. The data component of an ALTO CDNI Advertisement response is named "cdni-advertisement", which is a JSON object of type CDNIAdvertisementData: ; } CDNIAdvertisementData; ]]> Specifically, a CDNIAdvertisementData object is a JSON object that includes only one property named "capabilities-with-footprints", whose value is an array of BaseAdvertisementObject objects. It provides capabilities with footprint restrictions for uCDN to decide the dCDN selection. If the value of this property is an empty array, it means the corresponding dCDN cannot provide any mandatory-to-implement CDNI capabilities for any footprints. The syntax and semantics of BaseAdvertisementObject are well defined in Section 5.1 of . A BaseAdvertisementObject object includes multiple properties, including capability-type, capability-value, and footprints, where footprints are defined in Section 4.2.2.2 of . To be self-contained, below is an equivalent specification of BaseAdvertisementObject described in the ALTO-style notation (see Section 8.2 of ). As mentioned above, the normative specification of BaseAdvertisementObject is in . ; } BaseAdvertisementObject; object { JSONString footprint-type; JSONString footprint-value<1..*>; } Footprint; ]]> For each BaseAdvertisementObject, the ALTO client MUST interpret footprints appearing multiple times as if they appeared only once. If footprints in a BaseAdvertisementObject is null or empty or not appearing, the ALTO client MUST understand that the capabilities in this BaseAdvertisementObject have the "global" coverage, i.e., the corresponding dCDN can provide them for any request routing source. Note: Further optimization of BaseAdvertisement objects to effectively provide the advertisement of capabilities with footprint restrictions is certainly possible. For example, these two examples below both describe that the dCDN can provide capabilities ["http/1.1", "https/1.1"] for the same footprints. However, the latter one is smaller in its size. ] }, { "capability-type": "FCI.DeliveryProtocol", "capability-value": { "delivery-protocols": [ "https/1.1" ] }, "footprints": [ ] } ] } } EXAMPLE 2 { "meta": {...}, "cdni-advertisement": { "capabilities-with-footprints": [ { "capability-type": "FCI.DeliveryProtocol", "capability-value": { "delivery-protocols": [ "https/1.1", "http/1.1" ] }, "footprints": [ ] } ] } } ]]> Since such optimizations are not required for the basic interconnection of CDNs, the specifics of such mechanisms are outside the scope of this document. This document only requires the ALTO server to provide the initial FCI-specific CDNI Payload Types defined in as the mandatory-to-implement CDNI capabilities.

Examples

IRD Below is the IRD of a simple, example ALTO server. The server provides both base ALTO information resources (e.g., network maps) and CDNI FCI related information resources (e.g., CDNI Advertisement resources), demonstrating a single, integrated environment. Specifically, the IRD announces nine information resources as follows:

• two network maps,
• one CDNI Advertisement resource without dependency,
• one CDNI Advertisement resource depending on a network map,
• one filtered CDNI Advertisement resource to be defined in ,
• one property map including "cdni-capabilities" as its entity property,
• one filtered property map including "cdni-capabilities" and "pid" as its entity properties, and
• two update stream services:
  • one for updating CDNI Advertisement resources,
  • one for updating property maps

A Basic Example This basic example demonstrates a simple CDNI Advertisement resource, which does not depend on other resources. There are three BaseAdvertisementObjects in this resource and these objects' capabilities are http/1.1 delivery protocol, [http/1.1, https/1.1] delivery protocol, and https/1.1 acquisition protocol, respectively.

Incremental Updates A benefit of using ALTO to provide CDNI Advertisement resources is that such resources can be updated using ALTO incremental updates . Below is an example that also shows the benefit of having both JSON merge patch and JSON patch to encode updates. At first, an ALTO client requests updates for "my-default-cdnifci", and the ALTO server returns the "control-uri" followed by the full CDNI Advertisement response. Then when there is a change in the delivery-protocols in that http/1.1 is removed (from [http/1.1, https/1.1] to only https/1.1) due to maintenance of the http/1.1 clusters, the ALTO server regenerates the new CDNI Advertisement resource and pushes the full replacement to the ALTO client. Later on, the ALTO server notifies the ALTO client that "192.0.2.0/24" is added into the "ipv4" footprint object for delivery-protocol https/1.1 by sending the change encoded by JSON patch to the ALTO client.

CDNI Advertisement Service using ALTO Network Map

Network Map Footprint Type: altopid The ALTO protocol defines a concept called Provider-defined Identifier (PID) to represent a group of IPv4 or IPv6 addresses which can be applied the same management policy. The PID is an alternative to the pre-defined CDNI footprint types (i.e., ipv4cidr, ipv6cidr, asn, and countrycode). To leverage this concept, this document defines a new CDNI Footprint Type called "altopid". A CDNI Advertisement resource can depend on an ALTO network map resource and use "altopid" footprints to compress its CDNI Footprint Payload. Specifically, the "altopid" footprint type indicates that the corresponding footprint value is a list of PIDNames as defined in . These PIDNames are references of PIDs in a network map resource. Hence a CDNI Advertisement resource using "altopid" footprints depends on a network map. For such a CDNI Advertisement resource, the resource id of its dependent network map MUST be included in the "uses" field of its IRD entry, and the "dependent-vtags" field with a reference to this network map MUST be included in its response (see the example in ).

Examples The following examples use the same IRD given in .

ALTO Network Map for CDNI Advertisements Below provides a sample network map whose resource id is "my-eu-netmap". This map is referenced by the CDNI Advertisement example in .

ALTO PID Footprints in CDNI Advertisements This example shows a CDNI Advertisement resource that depends on a network map described in .

Incremental Updates In this example, the ALTO client is interested in changes of "my-cdnifci-with-pid-footprints" and its dependent network map "my-eu-netmap". Considering two changes, the first one is to change footprints of the https/1.1 delivery protocol capability, and the second one is to remove the "south-france" PID from the footprints of the https/1.1 acquisition protocol capability.

Filtered CDNI Advertisement using CDNI Capabilities Sections 3 and 4 describe CDNI Advertisement Service which can be used to enable a uCDN to get capabilities with footprint restrictions from dCDNs. However, since always getting full CDNI Advertisement resources from dCDNs is inefficient, this document introduces a new service named "Filtered CDNI Advertisement Service", to allow a client to filter a CDNI Advertisement resource using a client-given set of CDNI capabilities. For each entry of the CDNI Advertisement response, an entry will only be returned to the client if it contains at least one of the client given CDNI capabilities. The relationship between a filtered CDNI Advertisement resource and a CDNI Advertisement resource is similar to the relationship between a filtered network/cost map and a network/cost map.

Media Type A filtered CDNI Advertisement resource uses the same media type defined for the CDNI Advertisement resource in : "application/alto-cdni+json".

HTTP Method A filtered CDNI Advertisement resource is requested using the HTTP POST method.

Accept Input Parameters The input parameters for a filtered CDNI Advertisement resource are supplied in the entity body of the POST request. This document specifies the input parameters with a data format indicated by the media type "application/alto-cdnifilter+json" which is a JSON object of type ReqFilteredCDNIAdvertisement, where: ; } ReqFilteredCDNIAdvertisement; ]]> with fields:

capability-type:

The same as Base Advertisement Object's capability-type defined in Section 5.1 of .

capability-value:

The same as Base Advertisement Object's capability-value defined in Section 5.1 of .

cdni-capabilities:

A list of CDNI capabilities defined in Section 5.1 of for which footprints are to be returned. If this list is empty, the ALTO server MUST interpret it as a request for the full CDNI Advertisement resource. The ALTO server MUST interpret entries appearing in this list multiple times as if they appeared only once. If the ALTO server does not define any footprints for a CDNI capability, it MUST omit this capability from the response.

Capabilities There are no applicable capabilities.

Uses Same to the "uses" field of the CDNI Advertisement resource (see ).

Response If the request is invalid, the response MUST indicate an error, using ALTO protocol error handling specified in Section 8.5 of . Specifically, a filtered CDNI Advertisement request is invalid if:

• the value of "capability-type" is null;
• the value of "capability-value" is null;
• the value of "capability-value" is inconsistent with "capability-type".

When a request is invalid, the ALTO server MUST return an "E_INVALID_FIELD_VALUE" error defined in Section 8.5.2 of , and the "value" field of the error message SHOULD indicate this CDNI capability. The ALTO server returns a filtered CDNI Advertisement resource for a valid request. The format of a filtered CDNI Advertisement resource is the same as a full CDNI Advertisement resource (See .) The returned filtered CDNI Advertisement resource MUST contain all the BaseAdvertisementObject objects satisfying the following condition: The CDNI capability object of each included BaseAdvertisementObject object MUST follow two constraints:

• The "cdni-capabilities" field of the input includes a CDNI capability object X having the same capability type as it.
• All the mandatory properties in its capability value is a superset of mandatory properties in capability value of X semantically.

See for a concrete example. The version tag included in the "vtag" field of the response MUST correspond to the full CDNI Advertisement resource from which the filtered CDNI Advertisement resource is provided. This ensures that a single, canonical version tag is used independently of any filtering that is requested by an ALTO client.

Examples The following examples use the same IRD example as in .

A Basic Example This example filters the full CDNI Advertisement resource in by selecting only the http/1.1 delivery protocol capability. Only the second BaseAdvertisementObjects in the full resource will be returned because the second object's capability is http/1.1 and https/1.1 delivery protocols which is the superset of https/1.1 delivery protocol.

Incremental Updates In this example, the ALTO client only cares about the updates of one advertisement object for delivery protocol capability whose value includes "https/1.1". Thus, it adds its limitation of capabilities in "input" field of the POST request.

Query Footprint Properties using ALTO Property Map Service Besides the requirement of retrieving footprints of given capabilities, another common requirement for uCDN is to query CDNI capabilities of given footprints. Considering each footprint as an entity with properties including CDNI capabilities, a natural way to satisfy this requirement is to use the ALTO property map as defined in . This section describes how ALTO clients look up properties for individual footprints. First, it describes how to represent footprint objects as entities in the ALTO property map. Then it describes how to represent footprint capabilities as entity properties in the ALTO property map. Finally, it provides examples of the full property map and the filtered property map supporting CDNI capabilities, and their incremental updates.

Representing Footprint Objects as Property Map Entities A footprint object has two properties: footprint-type and footprint-value. A footprint-value is an array of footprint values conforming to the specification associated with the registered footprint type ("ipv4cidr", "ipv6cidr", "asn", "countrycode", and "altopid"). Considering each ALTO entity defined in also has two properties: entity domain type and domain-specific identifier, a straightforward approach to represent a footprint as an ALTO entity is to represent its footprint-type as an entity domain type, and its footprint value as a domain-specific identifier. Each existing footprint type can be represented as an entity domain type as follows:

• According to , "ipv4" and "ipv6" are two predefined entity domain types, which can be used to represent "ipv4cidr" and "ipv6cidr" footprints respectively. Note that both "ipv4" and "ipv6" domains can include not only hierarchical addresses but also individual addresses. Therefore, a "ipv4cidr" or "ipv6cidr" footprint with the longest prefix can also be represented by an individual address entity. When the uCDN receives a property map with individual addresses in an "ipv4" or "ipv6" domain, it can translate them as corresponding "ipv4cidr" or "ipv6cidr" footprints with the longest prefix.
• "pid" is also a predefined entity domain type, which can be used to represent "altopid" footprints. Note that "pid" is a resource-specific entity domain. To represent an "altopid" footprint, the specifying information resource of the corresponding "pid" entity domain MUST be the dependent network map used by the CDNI Advertisement resource providing this "altopid" footprint.
• However, no existing entity domain type can represent "asn" and "countrycode" footprints. To represent footprint-type "asn" and "countrycode", this document registers two new entity domains in in addition to the ones in .

Here is an example of representing a footprint object of "ipv4cidr" type as a set of "ipv4" entities in the ALTO property map. The representation of the footprint object of "ipv6cidr" type is similar. "ipv4:192.0.2.0/24", "ipv4:198.51.100.0/24" ]]> And here is an example of corresponding footprint object of "ipv4cidr" type represented by an individual address in an "ipv4" domain in the ALTO property map. The translation of the entities in an "ipv6" domain is similar. { "footprint-type": "ipv4cidr", "footprint-value": ["203.0.113.100/32"] } ]]>

ASN Domain The ASN domain associates property values with Autonomous Systems in the Internet.

Entity Domain Type The entity domain type of the ASN domain is "asn" (in lowercase).

Domain-Specific Entity Identifiers The entity identifier of an entity in an ASN domain MUST be encoded as a string consisting of the characters "as" (in lowercase) followed by the ASN as a decimal number without leading zeros.

Hierarchy and Inheritance There is no hierarchy or inheritance for properties associated with ASN.

COUNTRYCODE Domain The COUNTRYCODE domain associates property values with countries.

Entity Domain Type The entity domain type of the COUNTRYCODE domain is "countrycode" (in lowercase).

Domain-Specific Entity Identifiers The entity identifier of an entity in a COUNTRYCODE domain is encoded as an ISO 3166-1 alpha-2 code in lowercase.

Hierarchy and Inheritance There is no hierarchy or inheritance for properties associated with country codes.

Representing CDNI Capabilities as Property Map Entity Properties This document defines a new entity property type called "cdni-capabilities". An ALTO server can provide a property map resource mapping the "cdni-capablities" entity property type for a CDNI Advertisement resource that it provides to an "ipv4", "ipv6", "asn" or "countrycode" entity domain.

Defining Information Resource Media Type for Property Type cdni-capabilities The entity property type "cdni-capabilities" allows defining resource-specific entity properties. When resource-specific entity properties are defined with entity property type "cdni-capabilities", the defining information resource for a "cdni-capabilities" property MUST be a CDNI Advertisement resource provided by the ALTO server. The media type of the defining information resource for a "cdni-capabilities" property is therefore: application/alto-cdni+json

Intended Semantics of Property Type cdni-capabilities A "cdni-capabilities" property for an entity is to indicate all the CDNI capabilities that a corresponding CDNI Advertisement resource provides for the footprint represented by this entity. Thus, the value of a "cdni-capabilities" property MUST be a JSON array. Each element in a "cdni-capabilities" property MUST be an JSON object as format of CDNICapability (see ). The value of a "cdni-capabilities" property for an "ipv4", "ipv6", "asn", "countrycode" or "altopid" entity MUST include all the CDNICapability objects satisfying the following conditions: (1) they are provided by the defining CDNI Advertisement resource; and (2) the represented footprint object of this entity is in their footprint restrictions.

Examples The following examples use the same IRD example given by .

Property Map This example shows a full property map in which entities are footprints and entities' property is "cdni-capabilities".

Filtered Property Map This example uses the filtered property map service to get "pid" and "cdni-capabilities" properties for two footprints "ipv4:192.0.2.0/24" and "ipv6:2001:db8::/32".

Incremental Updates In this example, the ALTO client is interested in updates for the properties "cdni-capabilities" and "pid" of two footprints "ipv4:192.0.2.0/24" and "countrycode:fr".

IANA Considerations This document defines two new media types: "application/alto-cdni+json", as described in , and "application/cdnifilter+json", as described in . It also defines a new CDNI metadata footprint type (), two new ALTO entity domain types (), and a new ALTO entity property type ().

application/alto-cdni+json Media Type

Type name:

application

Subtype name:

alto-cdni+json

Required parameters:

N/A

Optional parameters:

N/A

Encoding considerations:

Encoding considerations are identical to those specified for the "application/json" media type. See .

Security considerations:

Security considerations related to the generation and consumption of ALTO Protocol messages are discussed in Section 15 of .

Interoperability considerations:

N/A

Published specification:

of RFCthis

Applications that use this media type:

ALTO servers and ALTO clients either stand alone or are embedded within other applications that provides CDNI interfaces for uCDNs or dCDNs.

Fragment identifier considerations:

N/A

Additional information:

Magic number(s):

N/A

File extension(s):

N/A

Macintosh file type code(s):

N/A

Person & email address to contact for further information:

See Authors' Addresses section.

Intended usage:

COMMON

Restrictions on usage:

N/A

Author:

See Authors' Addresses section.

Change controller:

Internet Engineering Task Force (mailto:iesg@ietf.org).

application/alto-cdnifilter+json Media Type

Type name:

application

Subtype name:

alto-cdnifilter+json

Required parameters:

N/A

Optional parameters:

N/A

Encoding considerations:

Encoding considerations are identical to those specified for the "application/json" media type. See .

Security considerations:

Security considerations related to the generation and consumption of ALTO Protocol messages are discussed in Section 15 of .

Interoperability considerations:

N/A

Published specification:

of RFCthis

Applications that use this media type:

ALTO servers and ALTO clients either stand alone or are embedded within other applications that provides CDNI interfaces for uCDNs or dCDNs and supports CDNI capability-based filtering.

Fragment identifier considerations:

N/A

Additional information:

Magic number(s):

N/A

File extension(s):

N/A

Macintosh file type code(s):

N/A

Person & email address to contact for further information:

See Authors' Addresses section.

Intended usage:

COMMON

Restrictions on usage:

N/A

Author:

See Authors' Addresses section.

Change controller:

Internet Engineering Task Force (mailto:iesg@ietf.org).

CDNI Metadata Footprint Type Registry This document updates the CDNI Metadata Footprint Types Registry created by Section 7.2 of . A new footprint type is to be registered, listed in . CDNI Metadata Footprint Type

Footprint Type	Description	Specification
altopid	A list of PID names	of RFCthis

[RFC Editor: Please replace RFCthis with the published RFC number for this document.]

ALTO Entity Domain Type Registry This document updates the ALTO Entity Domain Type Registry created by Section 11.2 of . Two new entity domain types are to be registered, listed in . Additional ALTO Entity Domain Types

Identifier	Entity Address Encoding	Hierarchy & Inheritance	Media Type of Defining Resource
asn	See of RFCthis	None	None
countrycode	See of RFCthis	None	None

[RFC Editor: Please replace RFCthis with the published RFC number for this document.]

ALTO Entity Property Type Registry This document updates the ALTO Entity Property Type Registry created by Section 11.3 of . A new entity property type is to be registered, listed in . Additional ALTO Entity Property Type

Identifier	Intended Semantics	Media Type of Defining Resource
cdni-capabilities	of RFCthis	application/alto-cdni+json

[RFC Editor: Please replace RFCthis with the published RFC number for this document.]

Security Considerations As an extension of the base ALTO protocol , this document fits into the architecture of the base protocol. And hence Security Considerations of the base protocol (Section 15 of ) fully apply when this extension is provided by an ALTO server. In the context of CDNI Advertisement, the following security risk scenarios should be considered:

• For authenticity and integrity of ALTO information, an attacker may disguise itself as an ALTO server for a dCDN (e.g., by starting a man-in-the-middle attack), and provide false capabilities and footprints to a uCDN using the CDNI Advertisement service. Such false information may lead a uCDN to (1) select an incorrect dCDN to serve user requests, or (2) skip uCDNs in good conditions. To address this risk, protection strategies in Section 15.1.2 of can be applied.
• For potential undesirable guidance from authenticated ALTO information, a dCDN can provide a uCDN with limited capabilities and smaller footprint coverage so that the dCDN can avoid transferring traffic for a uCDN which they should have to transfer. To reduce this risk, the protection strategies in Section 15.2.2 of can be considered.
• For confidentiality and privacy of ALTO information, footprint properties integrated with ALTO property maps may expose network location identifiers (e.g., IP addresses or fine-grained PIDs). To address this risk, the protection strategy for risk types (1) and (3) as described in Section 15.3 of can be considered.
• For availability of ALTO services, an attacker may conduct service degradation attacks using services defined in this document to disable ALTO services of a network. It may request potentially large, full CDNI Advertisement resources from an ALTO server in a dCDN continuously, to consume the bandwidth resources of that ALTO server. It may also query filtered property map services with many smaller individual footprints, to consume the computation resources of the ALTO server. To mitigate these risks, the protection strategies in Section 15.5.2 of can be applied.

Although protection strategies as described in Section 15 of should be applied to address aforementioned security and privacy considerations, two special cases need to be included as follows:

• As required by section 7 of , Therefore, the uCDN (ALTO Client) MUST be authenticated to the dCDN (ALTO Server). And the dCDN (ALTO Server) MUST support HTTP Digest Authentication and MAY also support TLS mutual authentication. The authentication method will need to be negotiated out of band and is out of scope for this document, as is the approach for provisioning and managing these credentials.
• One specific information leakage risk introduced by this document could not be addressed by these strategies. In particular, if a dCDN signs agreements with multiple uCDNs without any isolation, this dCDN may disclose extra information of one uCDN to another one. In that case, one uCDN may redirect requests which should not have to be served by this dCDN to it. To reduce the risk, a dCDN SHOULD isolate full/filtered CDNI Advertisement resources for different uCDNs. It could consider generating URIs of different full/filtered CDNI Advertisement resources by hashing its company ID, a uCDN's company ID as well as their agreements. A dCDN SHOULD avoid exposing all full/filtered CDNI Advertisement resources in one of its IRDs.

References Normative References Nokia Bell Labs Nokia Bell Labs Yale University Tongji University Sichuan University This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, the ALTO protocol is extended in two major directions. First, from endpoints restricted to IP addresses to entities covering a wider and extensible set of objects; second, from properties on specific endpoints to entire entity property maps. These extensions introduce additional features allowing entities and property values to be specific to a given information resource. This is made possible by a generic and flexible design of entity and property types. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The Autonomous System number is encoded as a two-octet entity in the base BGP specification. This document describes extensions to BGP to carry the Autonomous System numbers as four-octet entities. This document obsoletes RFC 4893 and updates RFC 4271. [STANDARDS-TRACK] Applications using the Internet already have access to some topology information of Internet Service Provider (ISP) networks. For example, views to Internet routing tables at Looking Glass servers are available and can be practically downloaded to many network application clients. What is missing is knowledge of the underlying network topologies from the point of view of ISPs. In other words, what an ISP prefers in terms of traffic optimization -- and a way to distribute it. The Application-Layer Traffic Optimization (ALTO) services defined in this document provide network information (e.g., basic network location structure and preferences of network paths) with the goal of modifying network resource consumption patterns while maintaining or improving application performance. The basic information of ALTO is based on abstract maps of a network. These maps provide a simplified view, yet enough information about a network for applications to effectively utilize them. Additional services are built on top of the maps. This document describes a protocol implementing the ALTO services. Although the ALTO services would primarily be provided by ISPs, other entities, such as content service providers, could also provide ALTO services. Applications that could use the ALTO services are those that have a choice to which end points to connect. Examples of such applications are peer-to-peer (P2P) and content delivery networks. I-JSON (short for "Internet JSON") is a restricted profile of JSON designed to maximize interoperability and increase confidence that software can process it successfully with predictable results. The Content Delivery Network Interconnection (CDNI) Metadata interface enables interconnected Content Delivery Networks (CDNs) to exchange content distribution metadata in order to enable content acquisition and delivery. The CDNI Metadata associated with a piece of content provides a downstream CDN with sufficient information for the downstream CDN to service content requests on behalf of an upstream CDN. This document describes both a base set of CDNI Metadata and the protocol for exchanging that metadata. This document captures the semantics of the "Footprint and Capabilities Advertisement" part of the Content Delivery Network Interconnection (CDNI) Request Routing interface, i.e., the desired meaning of "Footprint" and "Capabilities" in the CDNI context and what the "Footprint & Capabilities Advertisement interface (FCI)" offers within CDNI. The document also provides guidelines for the CDNI FCI protocol. It further defines a Base Advertisement Object, the necessary registries for capabilities and footprints, and guidelines on how these registries can be extended in the future. JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. The Application-Layer Traffic Optimization (ALTO) protocol (RFC 7285) provides network-related information, called network information resources, to client applications so that clients can make informed decisions in utilizing network resources. This document presents a mechanism to allow an ALTO server to push updates to ALTO clients to achieve two benefits: (1) updates can be incremental, in that if only a small section of an information resource changes, the ALTO server can send just the changes and (2) updates can be immediate, in that the ALTO server can send updates as soon as they are available. Informative References Sichuan University Samsung Nokia Bell Labs Yale University Tongji University This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. Distributed applications -- such as file sharing, real-time communication, and live and on-demand media streaming -- prevalent on the Internet use a significant amount of network resources. Such applications often transfer large amounts of data through connections established between nodes distributed across the Internet with little knowledge of the underlying network topology. Some applications are so designed that they choose a random subset of peers from a larger set with which to exchange data. Absent any topology information guiding such choices, or acting on suboptimal or local information obtained from measurements and statistics, these applications often make less than desirable choices. This document discusses issues related to an information-sharing service that enables applications to perform better-than-random peer selection. This memo provides information for the Internet community. Content Delivery Networks (CDNs) provide numerous benefits for cacheable content: reduced delivery cost, improved quality of experience for End Users, and increased robustness of delivery. For these reasons, they are frequently used for large-scale content delivery. As a result, existing CDN Providers are scaling up their infrastructure, and many Network Service Providers (NSPs) are deploying their own CDNs. It is generally desirable that a given content item can be delivered to an End User regardless of that End User's location or attachment network. This is the motivation for interconnecting standalone CDNs so they can interoperate as an open content delivery infrastructure for the end-to-end delivery of content from Content Service Providers (CSPs) to End Users. However, no standards or open specifications currently exist to facilitate such CDN Interconnection. The goal of this document is to outline the problem area of CDN Interconnection for the IETF CDNI (CDN Interconnection) working group. This document is not an Internet Standards Track specification; it is published for informational purposes. Many Internet applications are used to access resources such as pieces of information or server processes that are available in several equivalent replicas on different hosts. This includes, but is not limited to, peer-to-peer file sharing applications. The goal of Application-Layer Traffic Optimization (ALTO) is to provide guidance to applications that have to select one or several hosts from a set of candidates capable of providing a desired resource. This memo discusses deployment-related issues of ALTO. It addresses different use cases of ALTO such as peer-to-peer file sharing and Content Delivery Networks (CDNs) and presents corresponding examples. The document also includes recommendations for network administrators and application designers planning to deploy ALTO, such as recommendations on how to generate ALTO map information. The Request Routing interface comprises (1) the asynchronous advertisement of footprint and capabilities by a downstream Content Delivery Network (CDN) that allows an upstream CDN to decide whether to redirect particular user requests to that downstream CDN; and (2) the synchronous operation of an upstream CDN requesting whether a downstream CDN is prepared to accept a user request and of a downstream CDN responding with how to actually redirect the user request. This document describes an interface for the latter part, i.e., the CDNI Request Routing Redirection interface.

Acknowledgments The authors thank Matt Caulfield, Danny Alex Lachos Perez, Daryl Malas and Sanjay Mishra for their timely reviews and invaluable comments. Big thanks also to ALTO WG Chairs (Qin Wu and Vijay Gurbani), and all the directorate reviewers and IESG reviewers (Martin Duke, Erik Kline, Martin Vigoureux, Murray Kucherawy, Roman Danyliw, Zaheduzzaman Sarker, Eric Vyncke, and Francesca Palombini), for their thorough reviews, discussions, guidance and shepherding, that further improve this document. Jan Seedorf has been partially supported by the GreenICN project (GreenICN: Architecture and Applications of Green Information Centric Networking), a research project supported jointly by the European Commission under its 7th Framework Program (contract no. 608518) and the National Institute of Information and Communications Technology (NICT) in Japan (contract no. 167). The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the GreenICN project, the European Commission, or NICT. This document has also been supported by the Coordination Support Action entitled 'Supporting European Experts Presence in lnternational Standardisation Activities in ICT' ("StandlCT.eu") funded by the European Commission under the Horizon 2020 Programme with Grant Agreement no. 780439. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the European Commission.

Contributors Huawei

2222 Newjinqiao Rd Shanghai 200125 China +86-15316812351 x.shawn.lin@gmail.com