draft-ietf-cdni-requirements-14.txt   draft-ietf-cdni-requirements-15.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: June 27, 2014 Comcast Expires: July 18, 2014 Comcast
Dec 24, 2013 Jan 14, 2014
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-14 draft-ietf-cdni-requirements-15
Abstract Abstract
Content delivery is frequently provided by specifically architected Content delivery is frequently provided by specifically architected
and provisioned Content Delivery Networks (CDNs). As a result of and provisioned Content Delivery Networks (CDNs). As a result of
significant growth in content delivered over IP networks, existing significant growth in content delivered over IP networks, existing
CDN providers are scaling up their infrastructure. Many Network CDN providers are scaling up their infrastructure. Many Network
Service Providers and Enterprise Service Providers are also deploying Service Providers and Enterprise Service Providers are also deploying
their own CDNs. To deliver contents from the Content Service their own CDNs. To deliver contents from the Content Service
Provider (CSP) to end users, the contents may traverse across Provider (CSP) to end users, the contents may traverse across
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 June 27, 2014. This Internet-Draft will expire on July 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 31 skipping to change at page 2, line 31
4. CDNI Control Interface Requirements . . . . . . . . . . . . . 8 4. CDNI Control Interface Requirements . . . . . . . . . . . . . 8
5. CDNI Request Routing Redirection Interface Requirements . . . 11 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. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
14.1. Normative References . . . . . . . . . . . . . . . . . . . 23 14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 23 14.2. Informative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
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
skipping to change at page 8, line 24 skipping to change at page 8, line 24
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 literals, 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. identify the IP address of a
order to allow another entity to make a more informed User Agent) in order to allow another entity to make a more
decision (e.g. make a more informed request routing decision informed decision (e.g. make a more informed request routing
by attempting to derive location information from the third decision by attempting to derive location information from
party reference). the third 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
skipping to change at page 12, line 5 skipping to change at page 12, line 5
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 geographic region of the User * information from which the geographic region pertaining to
Agent that originated the request can be inferred (e.g. the IP address of the User Agent that originated the
User Agent fully qualified domain name in case of HTTP- request can be inferred (e.g. User Agent fully qualified
based Request Routing, DNS Proxy fully qualified domain domain name in case of HTTP-based Request Routing, DNS
name in case of DNS-based Request Routing) Proxy fully qualified domain name in case of 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
skipping to change at page 13, line 6 skipping to change at page 13, line 6
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-compute the message digest or digital
URIs embedded in the HTTP Adaptive Streaming manifest file. signature over the invariant portion of the chunk 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
correlate the HTTP Adaptive Stream manifest file to the correlate the HTTP Adaptive Stream manifest file to the
related chunks referenced in the manifest file. related chunks referenced in the manifest file.
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.
skipping to change at page 21, line 39 skipping to change at page 21, line 39
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 Downstream
Delegation (leading to that request being served by that CDN) CDN can determine the Upstream CDN that redirected the request
can be established with non-repudiation (i.e. "non-repudiation directly to the Downstream CDN (leading to that request being
with proof of origin" as defined in [RFC4949]). served by that CDN, or being further redirected).
SEC-4 {MED} The CDNI solution should be able to ensure non- SEC-4 {MED} The CDNI solution should be able to ensure that for any
repudiation by the Downstream CDN of transaction logs given transaction log generated by the Downstream CDN and
generated by the Downstream CDN and communicated to an communicated to an Upstream CDN, the Upstream CDN can confirm
Upstream CDN. This would ensure that the Downstream CDN the transmitted log record corresponds to a request
cannot repudiate transmitted Log records, therefore redirection by the Upstream CDN.
discouraging the Downstream CDN from spoofing a transaction
log (attempting to appear as if it corresponds to a request
redirected by the Upstream CDN when that request has not been
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
skipping to change at page 23, line 29 skipping to change at page 23, line 25
Ray Brandenburg, Matt Caufield, and Gilles Bertrand provided valuable Ray Brandenburg, Matt Caufield, and Gilles Bertrand provided valuable
inputs for HTTP Adaptive Streaming, CDNI Metadata interface, and CDNI inputs for HTTP Adaptive Streaming, CDNI Metadata interface, and CDNI
Logging interface, respectively. Logging interface, respectively.
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.ietf-cdni-framework] [I-D.ietf-cdni-framework]
Peterson, L. and B. Davie, "Framework for CDN Peterson, L. and B. Davie, "Framework for CDN
Interconnection", draft-ietf-cdni-framework-06 (work in Interconnection", draft-ietf-cdni-framework-07 (work in
progress), October 2013. progress), November 2013.
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", RFC 6707, September 2012. Statement", RFC 6707, September 2012.
14.2. Informative References 14.2. Informative References
[ATIS-0800042] [ATIS-0800042]
"ATIS IPTV Content on Demand Service, "ATIS IPTV Content on Demand Service,
https://www.atis.org/docstore/product.aspx?id=25670", https://www.atis.org/docstore/product.aspx?id=25670",
 End of changes. 12 change blocks. 
34 lines changed or deleted 32 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/