draft-ietf-cdni-requirements-11.txt   draft-ietf-cdni-requirements-12.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: April 24, 2014 Comcast Expires: May 8, 2014 Comcast
Oct 21, 2013 Nov 4, 2013
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-11 draft-ietf-cdni-requirements-12
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 April 24, 2014. This Internet-Draft will expire on May 8, 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 . . . 11 5. CDNI Request Routing Redirection Interface Requirements . . . 10
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
14.1. Normative References . . . . . . . . . . . . . . . . . . . 23 14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
14.2. Informative References . . . . . . . . . . . . . . . . . . 23 14.2. Informative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 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
(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
skipping to change at page 6, line 48 skipping to change at page 6, line 48
. \ / \ * / . . \ / \ * / .
. ---------------------- ---------*------------ . . ---------------------- ---------*------------ .
. * . . * .
. * Delivery . . * Delivery .
. * . . * .
. +--*---+ . . +--*---+ .
...............Request............................| User |..Request.. ...............Request............................| User |..Request..
| Agent| | Agent|
+------+ +------+
<==> interfaces inside the scope of CDNI <==> interfaces inside the scope of CDNI
**** and .... interfaces outside the scope of CDNI
**** interfaces outside the scope of CDNI
.... 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.
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 to benefit from upgrade, to the Content Service Provider delivering content
content delivery through interconnected CDNs. through a single CDN, to benefit from content delivery
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
skipping to change at page 8, line 10 skipping to change at page 8, line 6
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 CDN topology cannot be of interconnected CDNs (i.e. the topology of interconnected
restricted to a tree, a loop-free topology, 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
skipping to change at page 9, line 24 skipping to change at page 9, line 18
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 along success or failure indication. The failure indication and the
with the reason are used if the Downstream CDN cannot delete reason are included if the Downstream CDN cannot delete the
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,
skipping to change at page 10, line 27 skipping to change at page 10, line 20
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
protocols 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 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
skipping to change at page 11, line 33 skipping to change at page 11, line 27
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 routing of the request by avoiding the mechanism should allow redirection of the request on an
loop (as opposed to the request loop being simply interrupted alternate CDN path (as opposed to the request not being
without routing the request). 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 enforcment 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
skipping to change at page 18, line 23 skipping to change at page 18, line 23
* 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, for specific sets of, or for specific content items all content items, for specific sets of content items, or for
delivered using HTTP. A CDNI implementation that does not specific content items delivered using HTTP. A CDNI
support this optional CDNI Metadata Distribution Interface implementation that does not support this optional CDNI
mechanism shall ignore this log format indication and generate Metadata Distribution interface mechanism shall ignore this
CDNI logging format for HTTP Adaptive Streaming using the log format indication and generate CDNI logging format for
default set of CDNI Logging fields. (Note: this function is HTTP Adaptive Streaming using the default set of CDNI Logging
not concluded to be in Metadata Interface or Control fields. (Note: This function may be part of the CDNI Metadata
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
skipping to change at page 20, line 35 skipping to change at page 20, line 35
(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 extensibility LI-14 [HIGH] The CDNI Logging interface shall support the exchange
to allow proprietary information fields to be carried. These
information fields shall be agreed upon ahead of time between
the corresponding CDNs.
LI-15 [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-16 [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-17 [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
protection by not disclosing information that can be used to
identify the user (e.g. method that anonymize the IP address
carried in the logging field). The use of the privacy
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.
skipping to change at page 22, line 46 skipping to change at page 22, line 46
gwatson@velocix.com gwatson@velocix.com
13. Acknowledgements 13. Acknowledgements
This document leverages the earlier work of the IETF CDI working This document leverages the earlier work of the IETF CDI working
group in particular as documented in [I-D.cain-request-routing-req], group in particular as documented in [I-D.cain-request-routing-req],
[I-D.amini-cdi-distribution-reqs] and [I-D.gilletti-cdnp-aaa-reqs]. [I-D.amini-cdi-distribution-reqs] and [I-D.gilletti-cdnp-aaa-reqs].
The authors would like to thank Gilles Bertrand, Christophe Caillet, The authors would like to thank Gilles Bertrand, Christophe Caillet,
Bruce Davie, Phil Eardly, Ben Niven-Jenkins, Agustin Schapira, Emile Bruce Davie, Phil Eardly, Ben Niven-Jenkins, Agustin Schapira, Emile
Stephan, Eric Burger, Susan He, Kevin Ma, Daryl Malas, and Iuniana Stephan, Eric Burger, Susan He, Kevin Ma, Daryl Malas, Iuniana
Oprescu for their input. Serge Manning along with Robert Streijl, Oprescu, and Spencer Dawkins for their input. Serge Manning along
Vishwa Prasad, Percy Tarapore, Mike Geller, and Ramki Krishnan with Robert Streijl, Vishwa Prasad, Percy Tarapore, Mike Geller, and
contributed to this document by addressing the requirements of the Ramki Krishnan contributed to this document by addressing the
ATIS Cloud Services Forum. requirements of the ATIS Cloud Services Forum.
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
[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 IPTV Content on Demand Service,
https://www.atis.org/docstore/product.aspx?id=25670",
December 2010.
[I-D.amini-cdi-distribution-reqs] [I-D.amini-cdi-distribution-reqs]
Amini, L., "Distribution Requirements for Content Amini, L., "Distribution Requirements for Content
Internetworking", draft-amini-cdi-distribution-reqs-02 Internetworking", draft-amini-cdi-distribution-reqs-02
(work in progress), November 2001. (work in progress), November 2001.
[I-D.cain-request-routing-req] [I-D.cain-request-routing-req]
Cain, B., "Request Routing Requirements for Content Cain, B., "Request Routing Requirements for Content
Internetworking", draft-cain-request-routing-req-03 (work Internetworking", draft-cain-request-routing-req-03 (work
in progress), November 2001. in progress), November 2001.
[I-D.gilletti-cdnp-aaa-reqs] [I-D.gilletti-cdnp-aaa-reqs]
"CDI AAA Requirements, "CDI AAA Requirements,
draft-gilletti-cdnp-aaa-reqs-01.txt", June 2001. draft-gilletti-cdnp-aaa-reqs-01.txt", June 2001.
[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-05 (work in Interconnection", draft-ietf-cdni-framework-06 (work in
progress), September 2013. progress), October 2013.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma, [RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma,
K., and G. Watson, "Use Cases for Content Delivery Network K., and G. Watson, "Use Cases for Content Delivery Network
Interconnection", RFC 6770, November 2012. Interconnection", RFC 6770, November 2012.
Authors' Addresses Authors' Addresses
 End of changes. 24 change blocks. 
49 lines changed or deleted 56 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/