draft-ietf-cdni-requirements-12.txt   draft-ietf-cdni-requirements-13.txt 
Network Working Group K. Leung, Ed. Network Working Group K. Leung, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational Y. Lee, Ed. Intended status: Informational Y. Lee, Ed.
Expires: May 8, 2014 Comcast Expires: May 30, 2014 Comcast
Nov 4, 2013 Nov 26, 2013
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-12 draft-ietf-cdni-requirements-13
Abstract Abstract
Content Delivery Networks (CDNs) are frequently used for content Content Delivery Networks (CDNs) are frequently used for content
delivery. As a result of significant growth in content delivered delivery. As a result of significant growth in content delivered
over IP networks, existing CDN providers are scaling up their over IP networks, existing CDN providers are scaling up their
infrastructure. Many Network Service Providers and Enterprise infrastructure. Many Network Service Providers and Enterprise
Service Providers are also deploying their own CDNs. To deliver Service Providers are also deploying their own CDNs. To deliver
contents from the Content Service Provider (CSP) to end users, the contents from the Content Service Provider (CSP) to end users, the
contents may traverse across multiple CDNs. This creates a need for contents may traverse across multiple CDNs. This creates a need for
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 8, 2014. This Internet-Draft will expire on May 30, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. CDNI Model and CDNI Interfaces . . . . . . . . . . . . . . . . 4 2. CDNI Model and CDNI Interfaces . . . . . . . . . . . . . . . . 4
3. Generic CDNI Requirements . . . . . . . . . . . . . . . . . . 7 3. Generic CDNI Requirements . . . . . . . . . . . . . . . . . . 7
4. CDNI Control Interface Requirements . . . . . . . . . . . . . 8 4. CDNI Control Interface Requirements . . . . . . . . . . . . . 8
5. CDNI Request Routing Redirection Interface Requirements . . . 10 5. CDNI Request Routing Redirection Interface Requirements . . . 11
6. CDNI Footprint & Capabilities Advertisement Interface 6. CDNI Footprint & Capabilities Advertisement Interface
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 13 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 13
7. CDNI Metadata Interface Requirements . . . . . . . . . . . . . 15 7. CDNI Metadata Interface Requirements . . . . . . . . . . . . . 15
8. CDNI Logging Interface Requirements . . . . . . . . . . . . . 19 8. CDNI Logging Interface Requirements . . . . . . . . . . . . . 19
9. CDNI Security Requirements . . . . . . . . . . . . . . . . . . 21 9. CDNI Security Requirements . . . . . . . . . . . . . . . . . . 21
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
11. Security Considerations . . . . . . . . . . . . . . . . . . . 22 11. Security Considerations . . . . . . . . . . . . . . . . . . . 22
12. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 12. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
skipping to change at page 3, line 17 skipping to change at page 3, line 17
The volume of video and multimedia content delivered over the The volume of video and multimedia content delivered over the
Internet is rapidly increasing and expected to continue doing so in Internet is rapidly increasing and expected to continue doing so in
the future. In the face of this growth, Content Delivery Networks the future. In the face of this growth, Content Delivery Networks
(CDNs) provide numerous benefits: reduced delivery cost for cacheable (CDNs) provide numerous benefits: reduced delivery cost for cacheable
content, improved quality of experience for end users, and increased content, improved quality of experience for end users, and increased
robustness of delivery. For these reasons CDNs are frequently used robustness of delivery. For these reasons CDNs are frequently used
for large-scale content delivery. As a result of the significant for large-scale content delivery. As a result of the significant
growth in content delivered over IP networks, existing CDN providers growth in content delivered over IP networks, existing CDN providers
are scaling up their infrastructure and many Network Service are scaling up their infrastructure and many Network Service
Providers and Enterprise Service Providers are deploying their own Providers and Enterprise Service Providers are deploying their own
CDNs. Subject to the policy of the CSP, it is generally desirable CDNs. Subject to the policy of the Content Service Provider (CSP),
that a given item of content can be delivered to an end user it is generally desirable that a given item of content can be
regardless of that end user's location or attachment network. This delivered to an end user regardless of that end user's location or
creates a need for interconnecting (previously) standalone CDNs so attachment network. This creates a need for interconnecting
they can interoperate and collectively behave as a single delivery (previously) standalone CDNs so they can interoperate and
infrastructure. The Content Distribution Network Interconnection collectively behave as a single delivery infrastructure. The Content
(CDNI) working group has been chartered to develop an interoperable Distribution Network Interconnection (CDNI) working group has been
and scalable solution for such CDN interconnections. chartered to develop an interoperable and scalable solution for such
CDN interconnections.
CDNI Problem Statement [RFC6707] outlines the problem area that the CDNI Problem Statement [RFC6707] outlines the problem area that the
CDNI working group is chartered to address. Use Cases for CDNI CDNI working group is chartered to address. Use Cases for CDNI
[RFC6770] discusses the use cases for CDN Interconnection. Framework [RFC6770] discusses the use cases for CDN Interconnection. Framework
for CDN Interconnection [I-D.ietf-cdni-framework] discusses the for CDN Interconnection [I-D.ietf-cdni-framework] discusses the
technology framework for the CDNI solution and interfaces. technology framework for the CDNI solution and interfaces.
The goal of the present document is to document the requirements for The goal of the present document is to document the requirements for
the CDNI solution and interfaces. In order to meet the timelines the CDNI solution and interfaces. In order to meet the timelines
defined in the working group charter, the present document defined in the working group charter, the present document
skipping to change at page 3, line 50 skipping to change at page 3, line 51
This document uses the terminology defined in [RFC6707] as well as in This document uses the terminology defined in [RFC6707] as well as in
section 1.1 of Framework for CDN Interconnection section 1.1 of Framework for CDN Interconnection
[I-D.ietf-cdni-framework]. In addition, the key words "High [I-D.ietf-cdni-framework]. In addition, the key words "High
Priority", "Medium Priority" and "Low Priority" in this document are Priority", "Medium Priority" and "Low Priority" in this document are
to be interpreted in the following way: to be interpreted in the following way:
o "High Priority" indicates requirements that are to be supported by o "High Priority" indicates requirements that are to be supported by
the CDNI interfaces. A requirement is stated as "High Priority" the CDNI interfaces. A requirement is stated as "High Priority"
when it is established by the working group that it can be met to when it is established by the working group that it can be met to
achieve the goal of a deployable solution in a short timeframe as achieve the goal of a deployable solution in a short timeframe as
needed by the industry. This is tagged as "[HIGH]". needed by the industry. This is tagged as "{HIGH}".
o "Medium Priority" indicates requirements that are to be supported o "Medium Priority" indicates requirements that are to be supported
by the CDNI interfaces unless the WG realizes at a later stage by the CDNI interfaces unless the WG realizes at a later stage
that attempting to meet this requirement does not achieve the goal that attempting to meet this requirement does not achieve the goal
of a deployable solution in a short timeframe as needed by the of a deployable solution in a short timeframe as needed by the
industry. This is tagged as "[MED]". industry. This is tagged as "{MED}".
o "Low Priority" indicates requirements that are to be supported by o "Low Priority" indicates requirements that are to be supported by
the CDNI interfaces provided that dedicating WG resources to this the CDNI interfaces provided that dedicating WG resources to this
work does not prevent addressing "High Priority" and "Medium work does not prevent addressing "High Priority" and "Medium
Priority" requirements and that attempting to meet this Priority" requirements and that attempting to meet this
requirement is not an obstacle to achieving the goal of a requirement is not an obstacle to achieving the goal of a
deployable solution in a short timeframe as needed by the deployable solution in a short timeframe as needed by the
industry. This is tagged as "[LOW]". industry. This is tagged as "{LOW}".
2. CDNI Model and CDNI Interfaces 2. CDNI Model and CDNI Interfaces
For convenience, the "CDNI Expanded Model and CDNI Interfaces" figure For convenience, the "CDNI Expanded Model and CDNI Interfaces" figure
and brief descriptions of the CDNI interfaces in and brief descriptions of the CDNI interfaces in
[I-D.ietf-cdni-framework] are replicated below. [I-D.ietf-cdni-framework] are replicated below.
o CDNI Control interface (CI): Operations to bootstrap and o CDNI Control interface (CI): Operations to bootstrap and
parameterize the other CDNI interfaces, as well as operations to parameterize the other CDNI interfaces, as well as operations to
pre-position, revalidate, and purge both metadata and content. pre-position, revalidate, and purge both metadata and content.
skipping to change at page 7, line 9 skipping to change at page 7, line 9
<==> interfaces inside the scope of CDNI <==> interfaces inside the scope of CDNI
**** and .... interfaces outside the scope of CDNI **** and .... interfaces outside the scope of CDNI
Figure 1: CDNI Expanded Model and CDNI Interfaces Figure 1: CDNI Expanded Model and CDNI Interfaces
3. Generic CDNI Requirements 3. Generic CDNI Requirements
This section identifies generic requirements independent of the This section identifies generic requirements independent of the
individual CDNI interfaces. Some of those are expected to affect individual CDNI interfaces. Some of those are expected to affect
multiple or all interfaces. multiple or all interfaces. Management is an important aspect of CDN
operation. The fault and performance management is covered in CDNI
Logging interface requirements. The other types of management are
specific to the CDN provider and not needed for interoperability
between CDN providers.
GEN-1 [MED] Wherever possible, the CDNI interfaces should reuse or GEN-1 {MED} Wherever possible, the CDNI interfaces should reuse or
leverage existing IETF protocols. leverage existing IETF protocols.
GEN-2 [HIGH] The CDNI solution shall not require a change, or an GEN-2 {HIGH} The CDNI solution shall not require a change, or an
upgrade, to the User Agent to benefit from content delivery upgrade, to the User Agent to benefit from content delivery
through interconnected CDNs. through interconnected CDNs.
GEN-3 [HIGH] The CDNI solution shall not require a change, or an GEN-3 {HIGH} The CDNI solution shall not require a change, or an
upgrade, to the Content Service Provider delivering content upgrade, to the Content Service Provider delivering content
through a single CDN, to benefit from content delivery through a single CDN, to benefit from content delivery
through interconnected CDNs. through interconnected CDNs.
GEN-4 [HIGH] The CDNI solution shall not depend on intra-CDN GEN-4 {HIGH} The CDNI solution shall not depend on intra-CDN
information to be exposed to other CDNs for effective and information to be exposed to other CDNs for effective and
efficient delivery of the content. Examples of intra-CDN efficient delivery of the content. Examples of intra-CDN
information include surrogate topology, surrogate status, information include surrogate topology, surrogate status,
cached content, etc. cached content, etc.
GEN-5 [HIGH] The CDNI solution shall support delivery to the user GEN-5 {HIGH} The CDNI solution shall support delivery to the user
agent based on HTTP [RFC2616]. (Note that while delivery and agent based on HTTP [RFC2616]. (Note that while delivery and
acquisition "data plane" protocols are out of the CDNI acquisition "data plane" protocols are out of the CDNI
solution scope, the CDNI solution "control plane" protocols solution scope, the CDNI solution "control plane" protocols
are expected to participate in enabling, selecting or are expected to participate in enabling, selecting or
facilitating operations of such acquisition and delivery facilitating operations of such acquisition and delivery
protocols. Hence it is useful to state requirements on the protocols. Hence it is useful to state requirements on the
CDNI solution in terms of which acquisition and delivery CDNI solution in terms of which acquisition and delivery
protocols). protocols).
GEN-6 [HIGH] The CDNI solution shall support acquisition across GEN-6 {HIGH} The CDNI solution shall support acquisition across
CDNs based on HTTP [RFC2616]. (The note above applies to CDNs based on HTTP [RFC2616]. (The note above applies to
this requirement too) this requirement too)
GEN-7 [LOW] The CDNI solution may support delivery to the user GEN-7 {LOW} The CDNI solution may support delivery to the user
agent based on protocols other than HTTP. agent based on protocols other than HTTP.
GEN-8 [LOW] The CDNI solution may support acquisition across CDNs GEN-8 {LOW} The CDNI solution may support acquisition across CDNs
based on protocols other than HTTP. based on protocols other than HTTP.
GEN-9 [MED] The CDNI solution should support cascaded CDN GEN-9 {MED} The CDNI solution should support cascaded CDN
redirection (CDN1 redirects to CDN2 that redirects to CDN3) redirection (CDN1 redirects to CDN2 that redirects to CDN3)
to an arbitrary number of levels beyond the first level. to an arbitrary number of levels beyond the first level.
GEN-10 [MED] The CDNI solution should support an arbitrary topology GEN-10 {MED} The CDNI solution should support an arbitrary topology
of interconnected CDNs (i.e. the topology of interconnected of interconnected CDNs (i.e. the topology of interconnected
CDNs cannot be restricted to a tree, ring, star, etc.). CDNs cannot be restricted to a tree, ring, star, etc.).
GEN-11 [HIGH] The CDNI solution shall prevent looping of any CDNI GEN-11 {HIGH} The CDNI solution shall prevent looping of any CDNI
information exchange. information exchange.
GEN-12 [HIGH] When making use of third party reference, the CDNI GEN-12 {HIGH} When making use of third party reference, the CDNI
solution shall consider the potential issues associated with solution shall consider the potential issues associated with
the use of various format of third-party references (e.g. the use of various format of third-party references (e.g.
NAT or IPv4/IPv6 translation potentially breaking third-party NAT or IPv4/IPv6 translation potentially breaking third-party
references based on an IP addresses such as URI containing references based on an IP addresses such as URI containing
IPv4 or IPv6 address litterals, split DNS situations IPv4 or IPv6 address litterals, split DNS situations
potentially breaking third-party references based on DNS potentially breaking third-party references based on DNS
fully qualified domain names) and wherever possible avoid, fully qualified domain names) and wherever possible avoid,
minimize or mitigate the associated risks based on the minimize or mitigate the associated risks based on the
specifics of the environments where the reference is used specifics of the environments where the reference is used
(e.g. likely or unlikely presence of NAT in the path). In (e.g. likely or unlikely presence of NAT in the path). In
particular, this applies to situations where the CDNI particular, this applies to situations where the CDNI
solution needs to construct and convey uniform resource solution needs to construct and convey uniform resource
identifiers for directing/redirecting a content request, as identifiers for directing/redirecting a content request, as
well as to situations where the CDNI solution needs to pass well as to situations where the CDNI solution needs to pass
on a third party reference (e.g. to identify a User Agent) in on a third party reference (e.g. to identify a User Agent) in
order to allow another entity to make a more informed order to allow another entity to make a more informed
decision (e.g. make a more informed request routing decision decision (e.g. make a more informed request routing decision
by attempting to derive location information from the third by attempting to derive location information from the third
party reference). party reference).
GEN-13 [HIGH] The CDNI solution shall support HTTP Adaptive GEN-13 {HIGH} The CDNI solution shall support HTTP Adaptive
Streaming content. Streaming content.
4. CDNI Control Interface Requirements 4. CDNI Control Interface Requirements
The primary purpose of the CDNI Control interface (CI) is to initiate The primary purpose of the CDNI Control interface (CI) is to initiate
the interconnection across CDNs, bootstrap the other CDNI interfaces the interconnection across CDNs, bootstrap the other CDNI interfaces
and trigger actions into the Downstream CDN by the Upstream CDN (such and trigger actions into the Downstream CDN by the Upstream CDN (such
as delete object from caches or trigger pre-positioned content as delete object from caches or trigger pre-positioned content
acquisition). The working group attempts to align requirements with acquisition). The working group attempts to align requirements with
the appropriate interface; however, solutions to these requirements the appropriate interface; however, solutions to these requirements
may apply to a different interface or another interface in addition may apply to a different interface or another interface in addition
to the interface it is associated with. to the interface it is associated with.
CI-1 [HIGH] The CDNI Control interface shall allow the Upstream CDN CI-1 {HIGH} The CDNI Control interface shall allow the Upstream CDN
to request that the Downstream CDN, including downstream to request that the Downstream CDN, including downstream
cascaded CDNs, delete an object or set of objects and/or its cascaded CDNs, delete an object or set of objects and/or its
CDNI metadata from the CDN surrogates and any storage. Only CDNI metadata from the CDN surrogates and any storage. Only
the object(s) and CDNI metadata that pertain to the requesting the object(s) and CDNI metadata that pertain to the requesting
Upstream CDN are allowed to be purged. Upstream CDN are allowed to be purged.
CI-2 [MED] The CDNI Control interface should allow for multiple CI-2 {MED} The CDNI Control interface should allow for multiple
content items identified by a Content Collection ID to be content items identified by a Content Collection ID to be
purged using a single Content Purge action. purged using a single Content Purge action.
CI-3 [MED] The CDNI Control interface should allow the Upstream CDN CI-3 {MED} The CDNI Control interface should allow the Upstream CDN
to request that the Downstream CDN, including downstream to request that the Downstream CDN, including downstream
cascaded CDNs, mark an object or set of objects and/or its cascaded CDNs, mark an object or set of objects and/or its
CDNI metadata as "stale" and revalidate them before they are CDNI metadata as "stale" and revalidate them before they are
delivered again. delivered again.
CI-4 [HIGH] The CDNI Control interface shall allow the Downstream CI-4 {HIGH} The CDNI Control interface shall allow the Downstream
CDN to report on the completion of these actions (by itself, CDN to report on the completion of these actions (by itself,
and including downstream cascaded CDNs), in a manner and including downstream cascaded CDNs), in a manner
appropriate for the action (e.g. synchronously or appropriate for the action (e.g. synchronously or
asynchronously). The confirmation receipt should include a asynchronously). The confirmation receipt should include a
success or failure indication. The failure indication and the success or failure indication. The failure indication and the
reason are included if the Downstream CDN cannot delete the reason are included if the Downstream CDN cannot delete the
content in its storage. content in its storage.
CI-5 [MED] The CDNI Control interface should support initiation and CI-5 {MED} The CDNI Control interface should support initiation and
control by the Upstream CDN of pre-positioned CDNI metadata control by the Upstream CDN of pre-positioned CDNI metadata
acquisition by the Downstream CDN. acquisition by the Downstream CDN.
CI-6 [MED] The CDNI Control interface should support initiation and CI-6 {MED} The CDNI Control interface should support initiation and
control by the Upstream CDN of pre-positioned content control by the Upstream CDN of pre-positioned content
acquisition by the Downstream CDN. acquisition by the Downstream CDN.
CI-7 [LOW] The CDNI Control interface may allow a CDN to establish, CI-7 {LOW} The CDNI Control interface may allow a CDN to establish,
update and terminate a CDN interconnection with another CDN update and terminate a CDN interconnection with another CDN
whereby one CDN can act as a Downstream CDN for the other CDN whereby one CDN can act as a Downstream CDN for the other CDN
(that acts as an Upstream CDN). (that acts as an Upstream CDN).
CI-8 [LOW] The CDNI Control interface may allow control of the CDNI CI-8 {LOW} The CDNI Control interface may allow control of the CDNI
interfaces between any two CDNs independently for each interfaces between any two CDNs independently for each
direction (e.g. For the direction where CDN1 is the Upstream direction (e.g. For the direction where CDN1 is the Upstream
CDN and CDN2 is the Downstream CDN, and for the direction CDN and CDN2 is the Downstream CDN, and for the direction
where CDN2 is the Upstream CDN and CDN1 is the Downstream where CDN2 is the Upstream CDN and CDN1 is the Downstream
CDN). CDN).
CI-9 [LOW] The CDNI Control interface may allow bootstrapping of CI-9 {LOW} The CDNI Control interface may allow bootstrapping of
the Request-Routing interface. For example, this can the Request-Routing interface. For example, this can
potentially include: potentially include:
* negotiation of the Request-Routing method (e.g. DNS vs * negotiation of the Request-Routing method (e.g. DNS vs
HTTP, if more than one method is specified) HTTP, if more than one method is specified)
* discovery of the Request-Routing protocol endpoints * discovery of the Request-Routing protocol endpoints
* information necessary to establish secure communication * information necessary to establish secure communication
between the Request-Routing protocol endpoints. between the Request-Routing protocol endpoints.
CI-10 [LOW] The CDNI Control interface may allow bootstrapping of CI-10 {LOW} The CDNI Control interface may allow bootstrapping of
the CDNI Metadata interface. This information could, for the CDNI Metadata interface. This information could, for
example, include: example, include:
* discovery of the CDNI Metadata signaling protocol * discovery of the CDNI Metadata signaling protocol
endpoints endpoints
* information necessary to establish secure communication * information necessary to establish secure communication
between the CDNI Metadata signaling protocol endpoints. between the CDNI Metadata signaling protocol endpoints.
CI-11 [LOW] The CDNI Control interface may allow bootstrapping of > CI-11 {LOW} The CDNI Control interface may allow bootstrapping of
the Content Acquisition interface. This could, for example, the Content Acquisition interface. This could, for example,
include exchange and negotiation of the Content Acquisition include exchange and negotiation of the Content Acquisition
methods to be used across the CDNs (e.g. HTTP, HTTPS, FTP, methods to be used across the CDNs (e.g. HTTP, HTTPS, FTP,
ATIS C2[ATIS-0800042]). ATIS C2[ATIS-0800042]).
CI-12 [LOW] The CDNI Control interface may allow bootstrapping of CI-12 {LOW} The CDNI Control interface may allow bootstrapping of
the CDNI Logging interface. This information could, for the CDNI Logging interface. This information could, for
example, include: example, include:
* discovery of the Logging protocol endpoints * discovery of the Logging protocol endpoints
* information necessary to establish secure communication * information necessary to establish secure communication
between the Logging protocol endpoints between the Logging protocol endpoints
* negotiation/definition of the log file format and set of * negotiation/definition of the log file format and set of
fields to be exported through the Logging protocol, with fields to be exported through the Logging protocol, with
skipping to change at page 11, line 5 skipping to change at page 11, line 11
* negotiation/definition of parameters related to * negotiation/definition of parameters related to
transaction Logs export (e.g., export protocol, file transaction Logs export (e.g., export protocol, file
compression, export frequency, directory). compression, export frequency, directory).
5. CDNI Request Routing Redirection Interface Requirements 5. CDNI Request Routing Redirection Interface Requirements
The main function of the CDNI Request Routing Redirection interface The main function of the CDNI Request Routing Redirection interface
(RI) is to allow the Request-Routing systems in interconnected CDNs (RI) is to allow the Request-Routing systems in interconnected CDNs
to communicate to facilitate redirection of the request across CDNs. to communicate to facilitate redirection of the request across CDNs.
RI-1 [HIGH] The CDNI Request Routing Redirection interface shall RI-1 {HIGH} The CDNI Request Routing Redirection interface shall
support efficient request-routing for small objects. This support efficient request-routing for small objects. This
may, for example, call for a mode of operation (e.g. DNS- may, for example, call for a mode of operation (e.g. DNS-
based request routing) where freshness and accuracy of CDN/ based request routing) where freshness and accuracy of CDN/
Surrogate selection can be traded-off against reduced request- Surrogate selection can be traded-off against reduced request-
routing load (e.g. Via lighter-weight queries and caching of routing load (e.g. Via lighter-weight queries and caching of
request-routing decisions). request-routing decisions).
RI-2 [HIGH] The CDNI Request Routing Redirection interface shall RI-2 {HIGH} The CDNI Request Routing Redirection interface shall
support efficient request-routing for large objects. This support efficient request-routing for large objects. This
may, for example, call for a mode of operation (e.g. HTTP- may, for example, call for a mode of operation (e.g. HTTP-
based request routing) where freshness and accuracy of CDN/ based request routing) where freshness and accuracy of CDN/
Surrogate selection justifies a per-request decision and a Surrogate selection justifies a per-request decision and a
per-request CDNI Request-Routing protocol call. per-request CDNI Request-Routing protocol call.
RI-3 [HIGH] The CDNI Request Routing Redirection interface shall RI-3 {HIGH} The CDNI Request Routing Redirection interface shall
support recursive CDNI request routing. support recursive CDNI request routing.
RI-4 [HIGH] The CDNI Request Routing Redirection interface shall RI-4 {HIGH} The CDNI Request Routing Redirection interface shall
support iterative CDNI request routing. support iterative CDNI request routing.
RI-5 [MED] In case of detection of a request redirection loop, the RI-5 {MED} In case of detection of a request redirection loop, the
CDNI Request Routing Redirection Interface's loop prevention CDNI Request Routing Redirection Interface's loop prevention
mechanism should allow redirection of the request on an mechanism should allow redirection of the request on an
alternate CDN path (as opposed to the request not being alternate CDN path (as opposed to the request not being
redirected at all). redirected at all).
RI-6 [MED] The CDNI Request Routing Redirection interface should RI-6 {MED} The CDNI Request Routing Redirection interface should
support a mechanism allowing enforcement of a limit on the support a mechanism allowing enforcement of a limit on the
number of successive CDN redirections for a given request. number of successive CDN redirections for a given request.
RI-7 [LOW] The CDNI Request Routing Redirection interface may RI-7 {LOW} The CDNI Request Routing Redirection interface may
support a mechanism allowing an Upstream CDN to avoid support a mechanism allowing an Upstream CDN to avoid
redirecting a request to a Downstream CDN if that is likely to redirecting a request to a Downstream CDN if that is likely to
result in the total redirection time exceeding some limit. result in the total redirection time exceeding some limit.
RI-8 [HIGH] The CDNI Request Routing Redirection interface shall RI-8 {HIGH} The CDNI Request Routing Redirection interface shall
allow the Upstream CDN to include, in the query to the allow the Upstream CDN to include, in the query to the
Downstream CDN, the necessary information to allow the Downstream CDN, the necessary information to allow the
Downstream CDN to process the redirection query. This could, Downstream CDN to process the redirection query. This could,
for example, include: for example, include:
* information from which the location of the user-agent that * information from which the location of the user-agent that
originated the request can be inferred (e.g. User Agent originated the request can be inferred (e.g. User Agent
fully qualified domain name in case of HTTP-based Request fully qualified domain name in case of HTTP-based Request
Routing, DNS Proxy fully qualified domain name in case of Routing, DNS Proxy fully qualified domain name in case of
DNS-based Request Routing) DNS-based Request Routing)
* requested resource information (e.g. Resource URI in case * requested resource information (e.g. Resource URI in case
of HTTP-based Request Routing, Resource hostname in case of HTTP-based Request Routing, Resource hostname in case
of DNS-based Request Routing) of DNS-based Request Routing)
* additional available request information (e.g. request * additional available request information (e.g. request
headers in case of HTTP-based Request Routing). headers in case of HTTP-based Request Routing).
RI-9 [LOW] The CDNI Request Routing Redirection interface may also RI-9 {LOW} The CDNI Request Routing Redirection interface may also
allow the Upstream CDN to convey information pointing to CDNI allow the Upstream CDN to convey information pointing to CDNI
metadata applicable (individually or through inheritance) to metadata applicable (individually or through inheritance) to
the requested content. For illustration, the CDNI metadata the requested content. For illustration, the CDNI metadata
pointed to could potentially include metadata that is pointed to could potentially include metadata that is
applicable to any content, metadata that is applicable to a applicable to any content, metadata that is applicable to a
content collection (to which the requested content belongs) content collection (to which the requested content belongs)
and/or metadata that is applicable individually to the and/or metadata that is applicable individually to the
requested content. requested content.
RI-10 [HIGH] The CDNI Request Routing Redirection interface shall RI-10 {HIGH} The CDNI Request Routing Redirection interface shall
allow the Downstream CDN to include the following information allow the Downstream CDN to include the following information
in the response to the Upstream CDN: in the response to the Upstream CDN:
* status code, in particular indicating acceptance or * status code, in particular indicating acceptance or
rejection of request (e.g. Because the Downstream CDN is rejection of request (e.g. Because the Downstream CDN is
unwilling or unable to serve the request). In case of unwilling or unable to serve the request). In case of
rejection, an error code is also to be provided, which rejection, an error code is also to be provided, which
allows the Upstream CDN to react appropriately (e.g. allows the Upstream CDN to react appropriately (e.g.
Select another Downstream CDN, or serve the request Select another Downstream CDN, or serve the request
itself) itself)
* redirection information (e.g. Resource URI in case of * redirection information (e.g. Resource URI in case of
HTTP-based Request Routing, equivalent of a DNS record in HTTP-based Request Routing, equivalent of a DNS record in
case of DNS-based Request Routing). case of DNS-based Request Routing).
RI-11 [HIGH] The CDNI Request Routing Redirection interface shall RI-11 {HIGH} The CDNI Request Routing Redirection interface shall
allow for per-chunk request routing of HTTP Adaptive Streaming allow for per-chunk request routing of HTTP Adaptive Streaming
content. content.
RI-12 [LOW] The CDNI Request Routing Redirection interface may allow RI-12 {LOW} The CDNI Request Routing Redirection interface may allow
the Upstream CDN to use the information conveyed by the the Upstream CDN to use the information conveyed by the
Downstream CDN during the Recursive Request Routing process to Downstream CDN during the Recursive Request Routing process to
rewrite an HTTP Adaptive Streaming manifest file. rewrite an HTTP Adaptive Streaming manifest file.
RI-13 [LOW] The CDNI Request-Routing interface may allow the RI-13 {LOW} The CDNI Request-Routing interface may allow the
Upstream CDN to re-sign the invariant portion of the chunk Upstream CDN to re-sign the invariant portion of the chunk
URIs embedded in the HTTP Adaptive Streaming manifest file. URIs embedded in the HTTP Adaptive Streaming manifest file.
RI-14 [MED] The CDNI Request Routing Redirection interface should RI-14 {MED} The CDNI Request Routing Redirection interface should
allow the use of HTTP cookie to associate the chunks with the allow the use of HTTP cookie to associate the chunks with the
HTTP Adaptive Stream manifest file (which is verified by the HTTP Adaptive Stream manifest file (which is verified by the
URI signature) based on the Authorization Group ID (which is URI signature) based on the Authorization Group ID (which is
an identifier used to correlate the manifest file to the an identifier used to correlate the manifest file to the
related chunks). related chunks).
RI-15 [MED] The CDNI Request Routing Redirection interface should RI-15 {MED} The CDNI Request Routing Redirection interface should
allow for an efficient method of transferring request routing allow for an efficient method of transferring request routing
information for multiple chunks from the Downstream CDN to the information for multiple chunks from the Downstream CDN to the
Upstream CDN as part of the recursive request routing process. Upstream CDN as part of the recursive request routing process.
6. CDNI Footprint & Capabilities Advertisement Interface Requirements 6. CDNI Footprint & Capabilities Advertisement Interface Requirements
The main function of the CDNI Footprint & Capabilities Advertisement The main function of the CDNI Footprint & Capabilities Advertisement
interface (FCI) is to allow the Downstream CDN to advertise the interface (FCI) is to allow the Downstream CDN to advertise the
information regarding its footprint and capabilities to the Upstream information regarding its footprint and capabilities to the Upstream
CDN. CDN.
FCI-1 [HIGH] The CDNI Footprint & Capabilities Advertisement FCI-1 {HIGH} The CDNI Footprint & Capabilities Advertisement
interface shall allow the Downstream CDN to communicate to the interface shall allow the Downstream CDN to communicate to the
Upstream CDN coarse information about the Downstream CDN Upstream CDN coarse information about the Downstream CDN
ability and/or willingness to handle requests from the ability and/or willingness to handle requests from the
Upstream CDN. For example, this could potentially include a Upstream CDN. For example, this could potentially include a
binary signal ("Downstream CDN ready/not-ready to take binary signal ("Downstream CDN ready/not-ready to take
additional requests from Upstream CDN") to be used in case of additional requests from Upstream CDN") to be used in case of
excessive load or failure condition in the Downstream CDN. excessive load or failure condition in the Downstream CDN.
FCI-2 [MED] The CDNI Footprint & Capabilities Advertisement FCI-2 {MED} The CDNI Footprint & Capabilities Advertisement
interface should allow the Downstream CDN to communicate to interface should allow the Downstream CDN to communicate to
the Upstream CDN aggregate information to facilitate CDN the Upstream CDN aggregate information to facilitate CDN
selection during request routing, such as Downstream CDN selection during request routing, such as Downstream CDN
capabilities, resources and affinities (i.e. Preferences or capabilities, resources and affinities (i.e. Preferences or
cost). This information could, for example, include: cost). This information could, for example, include:
* supported content types and delivery protocols * supported content types and delivery protocols
* footprint (e.g. layer-3 coverage) * footprint (e.g. layer-3 coverage)
skipping to change at page 14, line 13 skipping to change at page 14, line 19
Reachability information of Downstream CDN Request Routing Reachability information of Downstream CDN Request Routing
system). system).
[Note: Some of this information - such as supported content [Note: Some of this information - such as supported content
types and delivery protocols- may also potentially be taken types and delivery protocols- may also potentially be taken
into account by the distribution system in the Upstream CDN into account by the distribution system in the Upstream CDN
for pre-positioning of content and/or metadata in the for pre-positioning of content and/or metadata in the
Downstream CDN in case of pre-positioned content acquisition Downstream CDN in case of pre-positioned content acquisition
and/or pre-positioned CDNI metadata acquisition.] and/or pre-positioned CDNI metadata acquisition.]
FCI-3 [MED] In the case of cascaded redirection, the CDNI Footprint FCI-3 {MED} In the case of cascaded redirection, the CDNI Footprint
& Capabilities Advertisement interface should allow the & Capabilities Advertisement interface should allow the
Downstream CDN to also include in the information communicated Downstream CDN to also include in the information communicated
to the Upstream CDN, information on the capabilities, to the Upstream CDN, information on the capabilities,
resources and affinities of CDNs to which the Downstream CDN resources and affinities of CDNs to which the Downstream CDN
may (in turn) redirect requests received by the Upstream CDN. may (in turn) redirect requests received by the Upstream CDN.
In that case, the CDNI Request-Routing interface shall prevent In that case, the CDNI Request-Routing interface shall prevent
looping of such information exchange. looping of such information exchange.
FCI-4 [LOW] The CDNI Footprint & Capabilities Advertisement FCI-4 {LOW} The CDNI Footprint & Capabilities Advertisement
interface may allow the Downstream CDN to communicate to the interface may allow the Downstream CDN to communicate to the
Upstream CDN aggregate information on CDNI administrative Upstream CDN aggregate information on CDNI administrative
limits and policy. This information can be taken into account limits and policy. This information can be taken into account
by the Upstream CDN Request Routing system in its CDN by the Upstream CDN Request Routing system in its CDN
Selection decisions. This information could, for example, Selection decisions. This information could, for example,
include: include:
* maximum number of requests redirected by the Upstream CDN * maximum number of requests redirected by the Upstream CDN
to be served simultaneously by the Downstream CDN to be served simultaneously by the Downstream CDN
* maximum aggregate volume of content (e.g. in Terabytes) to * maximum aggregate volume of content (e.g. in Terabytes) to
be delivered by the Downstream CDN over a time period. be delivered by the Downstream CDN over a time period.
FCI-5 [MED] The CDNI Footprint & Capabilities Advertisement FCI-5 {MED} The CDNI Footprint & Capabilities Advertisement
interface should support advertisement of the following types interface should support advertisement of the following types
of capabilities: of capabilities:
* delivery protocol (e.g., HTTP vs. RTMP) * delivery protocol (e.g., HTTP vs. RTMP)
* acquisition protocol (for acquiring content from an * acquisition protocol (for acquiring content from an
Upstream CDN) Upstream CDN)
* redirection mode (e.g., DNS Redirection vs. HTTP * redirection mode (e.g., DNS Redirection vs. HTTP
Redirection) Redirection)
* capabilities related to CDNI Logging (e.g., supported * capabilities related to CDNI Logging (e.g., supported
logging mechanisms) logging mechanisms)
* capabilities related to CDNI Metadata (e.g., authorization * capabilities related to CDNI Metadata (e.g., authorization
algorithms or support for proprietary vendor metadata) algorithms or support for proprietary vendor metadata)
FCI-6 [LOW] The CDNI Control interface may allow exchange and FCI-6 {LOW} The CDNI Control interface may allow exchange and
negotiation of delivery authorization mechanisms to be negotiation of delivery authorization mechanisms to be
supported across the CDNs (e.g. URI signature based supported across the CDNs (e.g. URI signature based
validation). validation).
7. CDNI Metadata Interface Requirements 7. CDNI Metadata Interface Requirements
The primary function of the CDNI Metadata interface (MI) is to allow The primary function of the CDNI Metadata interface (MI) is to allow
the Distribution system in interconnected CDNs to communicate to the Distribution system in interconnected CDNs to communicate to
ensure Content Distribution Metadata with inter-CDN scope can be ensure Content Distribution Metadata with inter-CDN scope can be
exchanged across CDNs. We observe that while the CDNI Metadata exchanged across CDNs. We observe that while the CDNI Metadata
Distribution protocol is currently discussed as a single "protocol", Distribution protocol is currently discussed as a single "protocol",
further analysis will determine whether the corresponding further analysis will determine whether the corresponding
requirements are to be realized over a single interface and protocol, requirements are to be realized over a single interface and protocol,
or over multiple interfaces and protocols. For example, a subset of or over multiple interfaces and protocols. For example, a subset of
the CDNI metadata might be conveyed in-band along with the actual the CDNI metadata might be conveyed in-band along with the actual
content acquisition across CDNs (e.g. content MD5 in HTTP header) content acquisition across CDNs (e.g. content MD5 in HTTP header)
while another subset might require an out-of-band interface & while another subset might require an out-of-band interface &
protocol (e.g. geo-blocking information). protocol (e.g. geo-blocking information).
MI-1 [HIGH] The CDNI Metadata interface shall allow the Upstream MI-1 {HIGH} The CDNI Metadata interface shall allow the Upstream
CDN to provide the Downstream CDN with content distribution CDN to provide the Downstream CDN with content distribution
metadata of inter-CDN scope. metadata of inter-CDN scope.
MI-2 [HIGH] The CDNI Metadata interface shall support exchange of MI-2 {HIGH} The CDNI Metadata interface shall support exchange of
CDNI metadata for both the dynamic content acquisition model CDNI metadata for both the dynamic content acquisition model
and the pre-positioning content acquisition model. and the pre-positioning content acquisition model.
MI-3 [HIGH] The CDNI Metadata interface shall support a mode where MI-3 {HIGH} The CDNI Metadata interface shall support a mode where
no, or a subset of, the Metadata is initially communicated to no, or a subset of, the Metadata is initially communicated to
the Downstream CDN along with information about how/where to the Downstream CDN along with information about how/where to
acquire the rest of the CDNI Metadata (i.e. Dynamic CDNI acquire the rest of the CDNI Metadata (i.e. Dynamic CDNI
metadata acquisition). metadata acquisition).
MI-4 [MED] The CDNI Metadata interface should support a mode where MI-4 {MED} The CDNI Metadata interface should support a mode where
all the relevant Metadata is initially communicated to the all the relevant Metadata is initially communicated to the
Downstream CDN (i.e. Pre-positioned CDNI metadata Downstream CDN (i.e. Pre-positioned CDNI metadata
acquisition). acquisition).
MI-5 [HIGH] Whether in the pre-positioned content acquisition model MI-5 {HIGH} Whether in the pre-positioned content acquisition model
or in the dynamic content acquisition model, the CDNI Metadata or in the dynamic content acquisition model, the CDNI Metadata
interface shall provide the necessary information to allow the interface shall provide the necessary information to allow the
Downstream CDN to acquire the content from an upstream source Downstream CDN to acquire the content from an upstream source
(e.g. Acquisition protocol and Uniform Resource Identifier in (e.g. Acquisition protocol and Uniform Resource Identifier in
Upstream CDN- or rules to construct this URI). Upstream CDN- or rules to construct this URI).
MI-6 [HIGH] The CDNI metadata shall allow signaling of one or more MI-6 {HIGH} The CDNI metadata shall allow signaling of one or more
upstream sources, where each upstream source can be in the upstream sources, where each upstream source can be in the
Upstream CDN, in another CDN, the CSP origin server or any Upstream CDN, in another CDN, the CSP origin server or any
arbitrary source designated by the Upstream CDN. Note that arbitrary source designated by the Upstream CDN. Note that
some upstream sources (e.g. the content origin server) may or some upstream sources (e.g. the content origin server) may or
may not be willing to serve the content to the Downstream CDN, may not be willing to serve the content to the Downstream CDN,
if this policy is known to the Upstream CDN then it may omit if this policy is known to the Upstream CDN then it may omit
those sources when exchanging CDNI metadata. those sources when exchanging CDNI metadata.
MI-7 [HIGH] The CDNI Metadata interface (possibly in conjunction MI-7 {HIGH} The CDNI Metadata interface (possibly in conjunction
with the CDNI Control interface) shall allow the Upstream CDN with the CDNI Control interface) shall allow the Upstream CDN
to request addition and modification of CDNI Metadata into the to request addition and modification of CDNI Metadata into the
Downstream CDN. Downstream CDN.
MI-8 [HIGH] The CDNI Metadata interface (possibly in conjunction MI-8 {HIGH} The CDNI Metadata interface (possibly in conjunction
with the CDNI Control interface) shall allow removal of with the CDNI Control interface) shall allow removal of
obsolete CDNI Metadata from the Downstream CDN (this could, obsolete CDNI Metadata from the Downstream CDN (this could,
for example, be achieved via an explicit removal request from for example, be achieved via an explicit removal request from
the Upstream CDN or via expiration of a Time-To-Live the Upstream CDN or via expiration of a Time-To-Live
associated to the Metadata). associated to the Metadata).
MI-9 [HIGH] The CDNI Metadata interface shall allow association of MI-9 {HIGH} The CDNI Metadata interface shall allow association of
CDNI Metadata at the granularity of individual object. This CDNI Metadata at the granularity of individual object. This
is necessary to achieve fine-grain Metadata distribution at is necessary to achieve fine-grain Metadata distribution at
the level of an individual object when necessary. the level of an individual object when necessary.
MI-10 [HIGH] The CDNI Metadata interface shall allow association of MI-10 {HIGH} The CDNI Metadata interface shall allow association of
CDNI Metadata at the granularity of an object set. This is CDNI Metadata at the granularity of an object set. This is
necessary to achieve scalable distribution of metadata when a necessary to achieve scalable distribution of metadata when a
large number of objects share the same distribution policy. large number of objects share the same distribution policy.
MI-11 [HIGH] The CDNI Metadata interface shall support multiple MI-11 {HIGH} The CDNI Metadata interface shall support multiple
levels of inheritance with precedence to more specific levels of inheritance with precedence to more specific
metadata. For example, the CDNI Metadata Distribution metadata. For example, the CDNI Metadata Distribution
protocol may support metadata that is applicable to any protocol may support metadata that is applicable to any
content, metadata that is applicable to a content collection content, metadata that is applicable to a content collection
and metadata that is applicable to an individual content where and metadata that is applicable to an individual content where
content level metadata overrides content collection metadata content level metadata overrides content collection metadata
that overrides metadata for any content. that overrides metadata for any content.
MI-12 [HIGH] The CDNI Metadata interface shall ensure that MI-12 {HIGH} The CDNI Metadata interface shall ensure that
conflicting metadata with overlapping scope are prevented or conflicting metadata with overlapping scope are prevented or
deterministically handled. deterministically handled.
MI-13 [HIGH] The CDNI Metadata interface shall allow signaling of MI-13 {HIGH} The CDNI Metadata interface shall allow signaling of
content distribution control policies. For example, this content distribution control policies. For example, this
could potentially include: could potentially include:
* geo-blocking information (i.e. Information defining * geo-blocking information (i.e. Information defining
geographical areas where the content is to be made geographical areas where the content is to be made
available or blocked) available or blocked)
* availability windows (i.e. Information defining time * availability windows (i.e. Information defining time
windows during which the content is to be made available windows during which the content is to be made available
or blocked; expiration time may also be included to remove or blocked; expiration time may also be included to remove
content) content)
* delegation whitelist/blacklist (i.e. Information defining * delegation whitelist/blacklist (i.e. Information defining
which Downstream CDNs the content may/may not be delivered which Downstream CDNs the content may/may not be delivered
through) through)
MI-14 [HIGH] The CDNI Metadata interface shall be able to exchange a MI-14 {HIGH} The CDNI Metadata interface shall be able to exchange a
set of metadata elements with specified semantics (e.g. start set of metadata elements with specified semantics (e.g. start
of time window, end of time window). of time window, end of time window).
MI-15 [HIGH] The CDNI Metadata interface shall allow exchange of MI-15 {HIGH} The CDNI Metadata interface shall allow exchange of
opaque metadata element, whose semantic is not defined in CDNI opaque metadata element, whose semantic is not defined in CDNI
but established by private CDN agreement. but established by private CDN agreement.
MI-16 [HIGH] The CDNI Metadata interface shall allow signaling of MI-16 {HIGH} The CDNI Metadata interface shall allow signaling of
authorization checks and validation that are to be performed authorization checks and validation that are to be performed
by the surrogate before delivery. For example, this could by the surrogate before delivery. For example, this could
potentially including the need to validate URI signed potentially including the need to validate URI signed
information (e.g. Expiry time, Client IP address). information (e.g. Expiry time, Client IP address).
MI-17 [MED] The CDNI Metadata interface should allow signaling of MI-17 {MED} The CDNI Metadata interface should allow signaling of
CDNI-relevant surrogate cache behavior parameters. For CDNI-relevant surrogate cache behavior parameters. For
example, this could potentially include: example, this could potentially include:
* control of whether the query string of HTTP URI is to be * control of whether the query string of HTTP URI is to be
ignored by surrogate cache ignored by surrogate cache
* enforcement of caching directives by Downstream CDN that * enforcement of caching directives by Downstream CDN that
are different than the ones signalled in the HTTP headers are different than the ones signalled in the HTTP headers
(e.g. "Expires" field) (e.g. "Expires" field)
* rate-pacing by Downstream CDN for content delivery (e.g. * rate-pacing by Downstream CDN for content delivery (e.g.
Progressive Download) Progressive Download)
MI-18 [HIGH] The CDNI Metadata interface shall provide indication of MI-18 {HIGH} The CDNI Metadata interface shall provide indication of
related content (e.g. HTTP Adaptive Bit Rate chunks) by the related content (e.g. HTTP Adaptive Bit Rate chunks) by the
Content Collection ID (CCID) metadata. This could be used by Content Collection ID (CCID) metadata. This could be used by
the Downstream CDN for operations on the group of content. the Downstream CDN for operations on the group of content.
For example, this could potentially include: For example, this could potentially include:
* content acquisition for the entire set of files when one * content acquisition for the entire set of files when one
piece of content is requested piece of content is requested
* local file management and storage bundles all the files * local file management and storage bundles all the files
for the content for the content
* purging the entire set of files associated with the * purging the entire set of files associated with the
content content
* logging of the delivery of the content for the session * logging of the delivery of the content for the session
when at least one file in the set was delivered when at least one file in the set was delivered
MI-19 [MED] ] The CDNI Metadata interface should support an optional MI-19 {MED} The CDNI Metadata interface should support an optional
mechanism allowing the Upstream CDN to indicate to the mechanism allowing the Upstream CDN to indicate to the
Downstream CDN which CDNI Log fields are to be provided for Downstream CDN which CDNI Log fields are to be provided for
all content items, for specific sets of content items, or for all content items, for specific sets of content items, or for
specific content items delivered using HTTP. A CDNI specific content items delivered using HTTP. A CDNI
implementation that does not support this optional CDNI implementation that does not support this optional CDNI
Metadata Distribution interface mechanism shall ignore this Metadata Distribution interface mechanism shall ignore this
log format indication and generate CDNI logging format for log format indication and generate CDNI logging format for
HTTP Adaptive Streaming using the default set of CDNI Logging HTTP Adaptive Streaming using the default set of CDNI Logging
fields. (Note: This function may be part of the CDNI Metadata fields. (Note: This function may be part of the CDNI Metadata
interface or the CDNI Control interface.) interface or the CDNI Control interface.)
MI-20 [MED] The CDNI Metadata interface should allow the Upstream MI-20 {MED} The CDNI Metadata interface should allow the Upstream
CDN to signal to the Downstream CDN the Content Collection ID CDN to signal to the Downstream CDN the Content Collection ID
value for all, for specific sets of, or for specific content value for all, for specific sets of, or for specific content
items delivered using HTTP. Whenever the Downstream CDN is items delivered using HTTP. Whenever the Downstream CDN is
instructed by the Upstream CDN to report the Content instructed by the Upstream CDN to report the Content
Collection ID field in the log records, the Downstream CDN is Collection ID field in the log records, the Downstream CDN is
to use the value provided through the CDNI Metadata interface to use the value provided through the CDNI Metadata interface
for the corresponding content. Note the Session ID field for the corresponding content. Note the Session ID field
along with Content Collection ID may be used for HTTP Adaptive along with Content Collection ID may be used for HTTP Adaptive
Streaming content. Streaming content.
MI-21 [MED] The CDNI Metadata interface should allow the Upstream MI-21 {MED} The CDNI Metadata interface should allow the Upstream
CDN to signal to the Downstream CDN the Authorization Group ID CDN to signal to the Downstream CDN the Authorization Group ID
value for all the related HTTP Adaptive Streaming content value for all the related HTTP Adaptive Streaming content
(i.e. manifest file and chunks). The authorization result of (i.e. manifest file and chunks). The authorization result of
a content (e.g. manifest file) is transferred over to related a content (e.g. manifest file) is transferred over to related
content (e.g. chunks). content (e.g. chunks).
8. CDNI Logging Interface Requirements 8. CDNI Logging Interface Requirements
This section identifies the requirements related to the CDNI Logging This section identifies the requirements related to the CDNI Logging
interface (LI). We observe that while the CDNI Logging interface is interface (LI). We observe that while the CDNI Logging interface is
currently discussed as a single "protocol", further analysis will currently discussed as a single "protocol", further analysis will
determine whether the corresponding requirements are to be realized determine whether the corresponding requirements are to be realized
over a single interface and protocol, or over multiple interfaces and over a single interface and protocol, or over multiple interfaces and
protocols. protocols.
LI-1 [HIGH] The CDNI logging architecture and interface shall LI-1 {HIGH} The CDNI logging architecture and interface shall
ensure reliable transfer of CDNI logging information across ensure reliable transfer of CDNI logging information across
CDNs. CDNs.
LI-2 [HIGH] The CDNI Logging interface shall provide logging of LI-2 {HIGH} The CDNI Logging interface shall provide logging of
deliveries and incomplete deliveries to User Agents performed deliveries and incomplete deliveries to User Agents performed
by the Downstream CDN as a result of request redirection by by the Downstream CDN as a result of request redirection by
the Upstream CDN. the Upstream CDN.
LI-3 [MED] In the case of cascaded CDNs, the CDNI Logging interface LI-3 {MED} In the case of cascaded CDNs, the CDNI Logging interface
should allow the Downstream CDN to report to the Upstream CDN should allow the Downstream CDN to report to the Upstream CDN
logging for deliveries and incomplete deliveries performed by logging for deliveries and incomplete deliveries performed by
the Downstream CDN itself as well as logging for deliveries the Downstream CDN itself as well as logging for deliveries
and incomplete deliveries performed by cascaded CDNs on behalf and incomplete deliveries performed by cascaded CDNs on behalf
of the Downstream CDN. of the Downstream CDN.
LI-4 [HIGH] The CDNI Logging interface shall support batch/offline LI-4 {HIGH} The CDNI Logging interface shall support batch/offline
exchange of logging records. exchange of logging records.
LI-5 [MED] The CDNI Logging interface should also support LI-5 {MED} The CDNI Logging interface should also support
additional timing constraints for some types of logging additional timing constraints for some types of logging
records (e.g. near-real time for monitoring and analytics records (e.g. near-real time for monitoring and analytics
applications) applications)
LI-6 [HIGH] The CDNI Logging interface shall define a log file LI-6 {HIGH} The CDNI Logging interface shall define a log file
format and a set of fields to be exported for various CDNI format and a set of fields to be exported for various CDNI
logging events. logging events.
LI-7 [HIGH] The CDNI Logging interface shall define a transport LI-7 {HIGH} The CDNI Logging interface shall define a transport
mechanism to exchange CDNI Logging files. mechanism to exchange CDNI Logging files.
LI-8 [MED] The CDNI Logging interface should allow a CDN to query LI-8 {MED} The CDNI Logging interface should allow a CDN to query
another CDN for relevant current logging records (e.g. For another CDN for relevant current logging records (e.g. For
on-demand access to real-time logging information). on-demand access to real-time logging information).
LI-9 [LOW] The CDNI Logging interface may support aggregate/ LI-9 {LOW} The CDNI Logging interface may support aggregate/
summarized logs (e.g. total bytes delivered for a content summarized logs (e.g. total bytes delivered for a content
regardless of individual User Agents to which it was regardless of individual User Agents to which it was
delivered). delivered).
LI-10 [LOW] The CDNI Logging interface may support logging of LI-10 {LOW} The CDNI Logging interface may support logging of
performance data for deliveries to User Agents performed by performance data for deliveries to User Agents performed by
the Downstream CDN as a result of request redirection by the the Downstream CDN as a result of request redirection by the
Upstream CDN. Performance data may include various traffic Upstream CDN. Performance data may include various traffic
statistics (the specific parameters are to be determined). statistics (the specific parameters are to be determined).
The CDNI Logging interface may support the Upstream CDN to The CDNI Logging interface may support the Upstream CDN to
indicate the nature and contents of the performance data to be indicate the nature and contents of the performance data to be
reported by the Downstream CDN. reported by the Downstream CDN.
LI-11 [MED] The CDNI Logging interface should support logging of LI-11 {MED} The CDNI Logging interface should support logging of
consumed resources (e.g. storage, bandwidth) to the Upstream consumed resources (e.g. storage, bandwidth) to the Upstream
CDN for deliveries where content is stored by the Downstream CDN for deliveries where content is stored by the Downstream
CDN for delivery to User Agents. The information logged may CDN for delivery to User Agents. The information logged may
include the type of storage (e.g., Origin, Intermediate, Edge, include the type of storage (e.g., Origin, Intermediate, Edge,
Cache) as well as the amount of storage (e.g., total GB, GB Cache) as well as the amount of storage (e.g., total GB, GB
used, per time period, per content domain) all of which may used, per time period, per content domain) all of which may
impact the cost of the services. impact the cost of the services.
LI-12 [MED] In the case of cascaded CDNs, the CDNI Logging interface LI-12 {MED} In the case of cascaded CDNs, the CDNI Logging interface
should support the Downstream CDN to report consumed resources should support the Downstream CDN to report consumed resources
(e.g. storage, bandwidth) to the Upstream CDN where content is (e.g. storage, bandwidth) to the Upstream CDN where content is
stored by the Downstream CDN itself as well as logging for stored by the Downstream CDN itself as well as logging for
storage resources when content storage is performed by storage resources when content storage is performed by
cascaded CDNs on behalf of the Downstream CDN. cascaded CDNs on behalf of the Downstream CDN.
LI-13 [HIGH] The CDNI Logging interface shall support logging of LI-13 {HIGH} The CDNI Logging interface shall support logging of
deleted objects from the Downstream CDN to the Upstream CDN as deleted objects from the Downstream CDN to the Upstream CDN as
a result of explicit delete requests on via the CDNI Control a result of explicit delete requests on via the CDNI Control
interface from the Upstream CDN. interface from the Upstream CDN.
LI-14 [HIGH] The CDNI Logging interface shall support the exchange LI-14 {HIGH} The CDNI Logging interface shall support the exchange
of extensible log file formats to support proprietary of extensible log file formats to support proprietary
information fields. These information fields shall be agreed information fields. These information fields shall be agreed
upon ahead of time between the corresponding CDNs. upon ahead of time between the corresponding CDNs.
LI-15 [HIGH] The CDNI Logging interface shall allow a CDN to notify LI-15 {HIGH} The CDNI Logging interface shall allow a CDN to notify
another CDN about which CDNI logging information is available another CDN about which CDNI logging information is available
for transfer and/or no longer available (e.g. it exceeded some for transfer and/or no longer available (e.g. it exceeded some
logging retention period or some logging retention volume). logging retention period or some logging retention volume).
LI-16 [MED] The CDNI Logging interface should support the ability LI-16 {MED} The CDNI Logging interface should support the ability
for the Downstream CDN to include the Content Collection ID for the Downstream CDN to include the Content Collection ID
and Session ID fields in CDNI log entries generated for HTTP and Session ID fields in CDNI log entries generated for HTTP
Adaptive Streaming content. Adaptive Streaming content.
LI-17 [MED] The CDNI Logging interface should provide privacy LI-17 {MED} The CDNI Logging interface should provide privacy
protection by not disclosing information that can be used to protection by not disclosing information that can be used to
identify the user (e.g. method that anonymize the IP address identify the user (e.g. method that anonymize the IP address
carried in the logging field). The use of the privacy carried in the logging field). The use of the privacy
protection mechanism is optional. protection mechanism is optional.
9. CDNI Security Requirements 9. CDNI Security Requirements
This section identifies the requirements related to the CDNI This section identifies the requirements related to the CDNI
security. Some of these are expected to affect multiple or all security. Some of these are expected to affect multiple or all
protocols. protocols.
SEC-1 [HIGH] All the CDNI interface shall support secure operation SEC-1 {HIGH} All the CDNI interface shall support secure operation
over unsecured IP connectivity (e.g. The Internet). This over unsecured IP connectivity (e.g. The Internet). This
includes authentication, confidentiality, integrity protection includes authentication, confidentiality, integrity protection
as well as protection against spoofing and replay. as well as protection against spoofing and replay.
SEC-2 [HIGH] The CDNI solution shall provide sufficient protection SEC-2 {HIGH} The CDNI solution shall provide sufficient protection
against Denial of Service attacks. This includes protection against Denial of Service attacks. This includes protection
against spoofed delivery requests sent by user agents directly against spoofed delivery requests sent by user agents directly
to a Downstream CDN attempting to appear as if they had been to a Downstream CDN attempting to appear as if they had been
redirected by a given Upstream CDN when they have not. redirected by a given Upstream CDN when they have not.
SEC-3 [MED] The CDNI solution should be able to ensure that for any SEC-3 {MED} The CDNI solution should be able to ensure that for any
given request redirected to a Downstream CDN, the chain of CDN given request redirected to a Downstream CDN, the chain of CDN
Delegation (leading to that request being served by that CDN) Delegation (leading to that request being served by that CDN)
can be established with non-repudiation. can be established with non-repudiation.
SEC-4 [MED] The CDNI solution should be able to ensure non- SEC-4 {MED} The CDNI solution should be able to ensure non-
repudiation by the Downstream CDN of transaction logs repudiation by the Downstream CDN of transaction logs
generated by the Downstream CDN and communicated to an generated by the Downstream CDN and communicated to an
Upstream CDN. This would ensure that the Downstream CDN Upstream CDN. This would ensure that the Downstream CDN
cannot repudiate transmitted Log records, therefore cannot repudiate transmitted Log records, therefore
discouraging the Downstream CDN from spoofing a transaction discouraging the Downstream CDN from spoofing a transaction
log (attempting to appear as if it corresponds to a request log (attempting to appear as if it corresponds to a request
redirected by the Upstream CDN when that request has not been redirected by the Upstream CDN when that request has not been
redirected by this Upstream CDN). redirected by this Upstream CDN).
SEC-5 [LOW] The CDNI solution may provide a mechanism allowing an SEC-5 {LOW} The CDNI solution may provide a mechanism allowing an
Upstream CDN that has credentials to acquire content from the Upstream CDN that has credentials to acquire content from the
CSP origin server (or another CDN), to allow establishment of CSP origin server (or another CDN), to allow establishment of
credentials authorizing the Downstream CDN to acquire the credentials authorizing the Downstream CDN to acquire the
content from the CSP origin server (or the other CDN) (e.g. content from the CSP origin server (or the other CDN) (e.g.
In case the content cannot be acquired from the Upstream CDN). In case the content cannot be acquired from the Upstream CDN).
10. IANA Considerations 10. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
 End of changes. 98 change blocks. 
106 lines changed or deleted 111 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/