draft-ietf-cdni-requirements-01.txt   draft-ietf-cdni-requirements-02.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 21, 2012 Comcast Expires: June 9, 2012 Comcast
October 19, 2011 December 7, 2011
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-01 draft-ietf-cdni-requirements-02
Abstract Abstract
Content Delivery Networks (CDNs) are frequently used for large-scale Content Delivery Networks (CDNs) are frequently used for large-scale
content delivery. As a result, existing CDN providers are scaling up content delivery. As a result, existing CDN providers are scaling up
their infrastructure and many Network Service Providers (NSPs) are their infrastructure and many Network Service Providers (NSPs) are
deploying their own CDNs. There is a requirement for interconnecting deploying their own CDNs. There is a requirement for interconnecting
standalone CDNs so that their collective CDN footprint can be standalone CDNs so that their collective CDN footprint can be
leveraged for the end-to-end delivery of content from Content Service leveraged for the end-to-end delivery of content from Content Service
Providers (CSPs) to end users. The Content Distribution Network Providers (CSPs) to end users. The Content Distribution Network
skipping to change at page 2, line 27 skipping to change at page 2, line 27
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 21, 2012. This Internet-Draft will expire on June 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 3, line 12 skipping to change at page 3, line 12
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. CDNI Model and CDNI Interfaces . . . . . . . . . . . . . . . . 4 2. CDNI Model and CDNI Interfaces . . . . . . . . . . . . . . . . 4
3. Generic CDNI Requirements . . . . . . . . . . . . . . . . . . 6 3. Generic CDNI Requirements . . . . . . . . . . . . . . . . . . 6
4. CDNI Control Interface Requirements . . . . . . . . . . . . . 7 4. CDNI Control Interface Requirements . . . . . . . . . . . . . 7
5. CDNI Request Routing Interface Requirements . . . . . . . . . 9 5. CDNI Request Routing Interface Requirements . . . . . . . . . 10
6. CDNI Metadata Distribution Interface Requirements . . . . . . 13 6. CDNI Metadata Distribution Interface Requirements . . . . . . 13
7. CDNI Logging Interface Requirements . . . . . . . . . . . . . 15 7. CDNI Logging Interface Requirements . . . . . . . . . . . . . 16
8. CDNI Security Requirements . . . . . . . . . . . . . . . . . . 17 8. CDNI Security Requirements . . . . . . . . . . . . . . . . . . 18
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
11. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 11. Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
13.1. Normative References . . . . . . . . . . . . . . . . . . . 19 13.1. Normative References . . . . . . . . . . . . . . . . . . . 20
13.2. Informative References . . . . . . . . . . . . . . . . . . 19 13.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
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, existing CDN for large-scale content delivery. As a result, existing CDN
skipping to change at page 4, line 29 skipping to change at page 4, line 29
delivering a given content may not expand close enough to the End delivering a given content may not expand close enough to the End
User's current location or attachment network to realize the cost User's current location or attachment network to realize the cost
benefit and user experience that a more distributed CDN would benefit and user experience that a more distributed CDN would
provide. This creates a requirement for interconnecting standalone provide. This creates a requirement for interconnecting standalone
CDNs so that their collective CDN footprint can be leveraged for the CDNs so that their collective CDN footprint can be leveraged for the
end-to-end delivery of content from Content Service Providers (CSPs) end-to-end delivery of content from Content Service Providers (CSPs)
to End Users. The Content Distribution Network Interconnection to End Users. The Content Distribution Network Interconnection
(CDNI) working group has been chartered to develop an interoperable (CDNI) working group has been chartered to develop an interoperable
and scalable solution for such CDN interconnection. and scalable solution for such CDN interconnection.
[I-D.jenkins-cdni-problem-statement] outlines the problem area that [I-D.ietf-cdni-problem-statement] outlines the problem area that the
the CDNI working group is chartered to address. CDNI working group is chartered to address.
[I-D.bertrand-cdni-use-cases] discusses the use cases for CDN [I-D.ietf-cdni-use-cases] discusses the use cases for CDN
Interconnection. [I-D.davie-cdni-framework] discusses the technology Interconnection. [I-D.davie-cdni-framework] discusses the technology
framework for the CDNI solution and interfaces. 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
categorizes the CDNI requirements as "High Priority", "Medium categorizes the CDNI requirements as "High Priority", "Medium
Priority", and "Low Priority". Priority", and "Low Priority".
1.1. Terminology 1.1. Terminology
skipping to change at page 8, line 11 skipping to change at page 8, line 11
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.
CNTL-1 [HIGH] The CDNI Control interface shall allow the Upstream CNTL-1 [HIGH] The CDNI Control interface shall allow the Upstream
CDN to request that the Downstream CDN (and, if cascaded CDN to request that the Downstream CDN (and, if cascaded
CDNs are supported by the solution, that the potential CDNs are supported by the solution, that the potential
cascaded Downstream CDNs) perform the following actions on cascaded Downstream CDNs) perform the following actions on
an object or object set: an object or object set:
* Mark an object(s) and/or its CDNI metadata as "stale" * Mark an object or set of objects and/or its CDNI
and revalidate them before they are delivered again metadata as "stale" and revalidate them before they are
delivered again
* Delete an object(s) and/or its CDNI metadata from the * Delete an object or set of objects and/or its CDNI
CDN surrogates and any storage. Only the object(s) and metadata from the CDN surrogates and any storage. Only
CDNI metadata that pertain to the requesting Upstream the object(s) and CDNI metadata that pertain to the
CDN are allowed to be purged. requesting Upstream CDN are allowed to be purged.
CNTL-2 [HIGH] The CDNI Control interface shall allow the downstream CNTL-2 [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 if cascaded CDNs are supported by the solution, by and if cascaded CDNs are supported by the solution, by
potential cascaded Downstream CDNs), in a manner appropriate potential cascaded Downstream CDNs), in a manner appropriate
for the action (e.g. synchronously or asynchronously). for the action (e.g. synchronously or asynchronously). The
confirmation receipt should include a success or failure
indication. The failure indication is used if the
Downstream CDN cannot delete the content in its storage.
CNTL-3 [HIGH] The CDNI Control interface shall support initiation CNTL-3 [HIGH] The CDNI Control interface shall support initiation
and control by the Upstream CDN of pre-positioned CDNI and control by the Upstream CDN of pre-positioned CDNI
metadata acquisition by the Downstream CDN. metadata acquisition by the Downstream CDN.
CNTL-4 [MED] The CDNI Control interface should support initiation CNTL-4 [MED] The CDNI Control interface should support initiation
and control by the Upstream CDN of pre-positioned content and control by the Upstream CDN of pre-positioned content
acquisition by the Downstream CDN. acquisition by the Downstream CDN.
CNTL-5 [LOW] The CDNI Control interface may allow a CDN to CNTL-5 [LOW] The CDNI Control interface may allow a CDN to
skipping to change at page 11, line 50 skipping to change at page 12, line 6
CDNI Request-Routing loop prevention mechanism should allow CDNI Request-Routing loop prevention mechanism should allow
routing of the request by avoiding the loop (as opposed to routing of the request by avoiding the loop (as opposed to
the request loop being simply interrupted without routing the the request loop being simply interrupted without routing the
request). request).
REQ-10 [MED] The CDNI Request-Routing protocol should support a REQ-10 [MED] The CDNI Request-Routing protocol should support a
mechanism allowing enforcment of a limit on the number of mechanism allowing enforcment of a limit on the number of
successive CDN redirections for a given request. successive CDN redirections for a given request.
REQ-11 [LOW] The CDNI Request-Routing protocol may support a REQ-11 [LOW] The CDNI Request-Routing protocol may support a
mechanism allowing an upstream CDN to avoid redirecting a mechanism allowing an Upstream CDN to avoid redirecting a
request to a downstream CDN if that is likely to result in request to a Downstream CDN if that is likely to result in
the total redirection time exceeding some limit. the total redirection time exceeding some limit.
REQ-12 [HIGH] The CDNI Request-Routing protocol shall allow the REQ-12 [HIGH] The CDNI Request-Routing protocol shall allow the
Upstream CDN to include, in the query to the Downstream CDN, Upstream CDN to include, in the query to the Downstream CDN,
the necessary information to allow the Downstream CDN to the necessary information to allow the Downstream CDN to
process the redirection query. This could, for example, process the redirection query. This could, for example,
include: include:
* information from which the location of the user-agent * information from which the location of the user-agent
that originated the request can be inferred (e.g. User that originated the request can be inferred (e.g. User
skipping to change at page 14, line 5 skipping to change at page 14, line 11
content from an upstream source (e.g. Acquisition protocol content from an upstream source (e.g. Acquisition protocol
and Uniform Resource Identifier in Upstream CDN- or rules to and Uniform Resource Identifier in Upstream CDN- or rules to
construct this URI). construct this URI).
META-6 [HIGH] The CDNI metadata shall allow signaling of one or META-6 [HIGH] The CDNI metadata shall allow signaling of one or
more upstream sources, where each upstream source can be in more upstream sources, where each upstream source can be in
the Upstream CDN, in another CDN, the CSP origin server or the Upstream CDN, in another CDN, the CSP origin server or
any arbitrary source designated by the Upstream CDN. Note any arbitrary source designated by the Upstream CDN. Note
that some upstream sources (e.g. the content origin server) that some upstream sources (e.g. the content origin server)
may or may not be willing to serve the content to the may or may not be willing to serve the content to the
Downstream CDN, if this policy is known to the upstream CDN Downstream CDN, if this policy is known to the Upstream CDN
then it may omit those sources when exchanging CDNI then it may omit those sources when exchanging CDNI
metadata. metadata.
META-7 [HIGH] The CDNI Metadata Distribution interface shall allow META-7 [HIGH] The CDNI Metadata Distribution interface shall allow
the Upstream CDN to request addition and modification of the Upstream CDN to request addition and modification of
CDNI Metadata into the Downstream CDN. CDNI Metadata into the Downstream CDN.
META-8 [HIGH] The CDNI Metadata Distribution interface shall allow META-8 [HIGH] The CDNI Metadata Distribution interface shall allow
removal of obsolete CDNI Metadata from the Downstream CDN removal of obsolete CDNI Metadata from the Downstream CDN
(this could, for example, be achieved via an explicit (this could, for example, be achieved via an explicit
skipping to change at page 15, line 19 skipping to change at page 15, line 27
* 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 or blocked; expiration time may also be included to
remove content) remove content)
* delegation whitelist/blacklist (i.e. Information * delegation whitelist/blacklist (i.e. Information
defining which downstream CDNs the content may/may not defining which Downstream CDNs the content may/may not
be delivered through) be delivered through)
META-15 [HIGH] The CDNI Metadata interface shall be able to exchange META-15 [HIGH] The CDNI Metadata interface shall be able to exchange
a set of well-accepted metadata elements with specified a set of well-accepted metadata elements with specified
semantics (e.g. start of time window, end of time window). semantics (e.g. start of time window, end of time window).
META-16 [HIGH] The CDNI Metadata interface shall allow exchange of META-16 [HIGH] The CDNI Metadata interface shall allow exchange of
opaque metadata element, whose semantic is not defined in opaque metadata element, whose semantic is not defined in
CDNI but established by private CDN agreement. CDNI but established by private CDN agreement.
skipping to change at page 16, line 12 skipping to change at page 16, line 20
interface. We observe that while the CDNI Logging interface is interface. 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.
LOG-1 [HIGH] The CDNI logging architecture and interface shall LOG-1 [HIGH] The CDNI logging architecture and interface shall
ensure reliable logging of CDNI events. ensure reliable logging of CDNI events.
LOG-2 [HIGH] The CDNI Logging interface shall provide logging of LOG-2 [HIGH] The CDNI Logging interface shall provide logging of
deliveries to User Agents performed by the Downstream CDN as deliveries and incomplete deliveries to User Agents performed
a result of request redirection by the Upstream CDN. by the Downstream CDN as a result of request redirection by
the Upstream CDN.
LOG-3 [MED] In the case of cascaded CDNs, the CDNI Logging LOG-3 [MED] In the case of cascaded CDNs, the CDNI Logging
interface shall allow the Downstream CDN to report to the interface shall allow the Downstream CDN to report to the
Upstream CDN logging for deliveries performed by the Upstream CDN logging for deliveries and incomplete deliveries
Downstream CDN itself as well as logging for deliveries performed by the Downstream CDN itself as well as logging for
performed by cascaded CDNs on behalf of the Downstream CDN. deliveries and incomplete deliveries performed by cascaded
CDNs on behalf of the Downstream CDN.
LOG-4 [HIGH] The CDNI Logging interface shall provide logging of LOG-4 [HIGH] The CDNI Logging interface shall provide logging of
distribution performed by the Upstream CDN as a result of distribution performed by the Upstream CDN as a result of
acquisition request by the Downstream CDN. acquisition request by the Downstream CDN.
LOG-5 [HIGH] The CDNI Logging interface shall support batch/offline LOG-5 [HIGH] The CDNI Logging interface shall support batch/offline
exchange of logging records. exchange of logging records.
LOG-6 [MED] The CDNI Logging interface should also support LOG-6 [MED] The CDNI Logging interface should also support
additional timing constraints for some types of logging additional timing constraints for some types of logging
skipping to change at page 16, line 41 skipping to change at page 17, line 5
applications) applications)
LOG-7 [HIGH] The CDNI Logging interface shall define a log file LOG-7 [HIGH] The CDNI Logging interface shall define a log file
format and a set of fields to be exported through the Logging format and a set of fields to be exported through the Logging
protocol, with some granularity (e.g. On a per content type protocol, with some granularity (e.g. On a per content type
basis). basis).
LOG-8 [HIGH] The CDNI Logging interface shall define a transport LOG-8 [HIGH] The CDNI Logging interface shall define a transport
mechanisms to exchange CDNI Logging files. mechanisms to exchange CDNI Logging files.
LOG-9 [LOW] The CDNI Logging interface may allow a CDN to query LOG-9 [MED] The CDNI Logging interface may 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).
LOG-10 [LOW] The CDNI Logging interface may support aggregate/ LOG-10 [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).
LOG-11 [LOW] The CDNI Logging interface may provide "quality" LOG-11 [LOW] The CDNI Logging interface shall support logging of
metrics in the logging of deliveries to User Agents performed performance data for deliveries to User Agents performed by
by the Downstream CDN. the Downstream CDN as a result of request redirection by the
Upstream CDN. Performance data may include various traffic
statistics (the specific parameters are to be determined).
The CDNI Logging interface shall support the Upstream CDN to
indicate the nature and contents of the performance data to
be reported by the Downstream CDN.
LOG-12 [MED] The CDNI Logging interface shall support logging of
consumed resources (e.g. storage, bandwidth) to the Upstream
CDN for deliveries where content is stored by the Downstream
CDN for delivery to User Agents. The information logged may
include the type of storage (e.g., Origin, Intermediate,
Edge, Cache) as well as the amount of storage (e.g., total
GB, GB used, per time period, per content domain) all of
which may impact the cost of the services.
LOG-13 [MED] In the case of cascaded CDNs, the CDNI Logging
interface shall support the Downstream CDN to report consumed
resources (e.g. storage, bandwidth) to the Upstream CDN where
content is stored by the Downstream CDN itself as well as
logging for storage resources when content storage is
performed by cascaded CDNs on behalf of the Downstream CDN.
LOG-14 [HIGH] The CDNI Logging interface shall support logging of
deleted objects from the Downstream CDN to the Upstream CDN
as a result of explicit delete requests on via the CDNI
Control interface from the Upstream CDN.
LOG-15 [HIGH] The CDNI Logging interface shall support extensibility
to allow proprietary information fields to be carried. These
information fields must be agreed upon ahead of time between
the corresponding CDNs.
LOG-16 [HIGH] The CDNI Logging interface shall support the exchange
of extensible log file formats to support proprietary
information fields. These information fields must be agreed
upon ahead of time between the corresponding CDNs.
8. CDNI Security Requirements 8. CDNI Security Requirements
This section identifies the requirements related to the CDNI This section identifies the requirements related to the CDNI
security. Some of those are expected to affect multiple or all security. Some of those 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
skipping to change at page 18, line 43 skipping to change at page 19, line 40
12. Acknowledgements 12. 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, and Daryl Malas for their Stephan, Eric Burger, Susan He, Kevin Ma, and Daryl Malas for their
input. input. Serge Manning along with Robert Streijl, Vishwa Prasad, Percy
Tarapore, Mike Geller, and Ramki Krishnan contributed to this
document by addressing the requirements of the ATIS Cloud Services
Forum.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.bertrand-cdni-use-cases]
Bertrand, G., Stephan, E., Watson, G., Burbridge, T.,
Eardley, P., and K. Ma, "Use Cases for Content Delivery
Network Interconnection", draft-bertrand-cdni-use-cases-02
(work in progress), July 2011.
[I-D.davie-cdni-framework] [I-D.davie-cdni-framework]
Davie, B. and L. Peterson, "Framework for CDN Davie, B. and L. Peterson, "Framework for CDN
Interconnection", draft-davie-cdni-framework-00 (work in Interconnection", draft-davie-cdni-framework-01 (work in
progress), July 2011. progress), October 2011.
[I-D.jenkins-cdni-problem-statement] [I-D.ietf-cdni-problem-statement]
Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", draft-jenkins-cdni-problem-statement-02 (work Statement", draft-ietf-cdni-problem-statement-01 (work in
in progress), March 2011. progress), October 2011.
[I-D.ietf-cdni-use-cases]
Bertrand, G., Emile, S., Watson, G., Burbridge, T.,
Eardley, P., and K. Ma, "Use Cases for Content Delivery
Network Interconnection", draft-ietf-cdni-use-cases-00
(work in progress), September 2011.
[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.
13.2. Informative References 13.2. Informative References
[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
 End of changes. 22 change blocks. 
51 lines changed or deleted 96 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/