draft-seedorf-cdni-request-routing-alto-07.txt   draft-seedorf-cdni-request-routing-alto-08.txt 
CDNI J. Seedorf CDNI J. Seedorf
Internet-Draft NEC Internet-Draft NEC
Intended status: Informational Y. Yang Intended status: Informational Y. Yang
Expires: December 29, 2014 Yale Expires: September 6, 2015 Yale
J. Peterson J. Peterson
Neustar Neustar
June 27, 2014 March 5, 2015
CDNI Footprint and Capabilities Advertisement using ALTO CDNI Footprint and Capabilities Advertisement using ALTO
draft-seedorf-cdni-request-routing-alto-07 draft-seedorf-cdni-request-routing-alto-08
Abstract Abstract
Network Service Providers (NSPs) are currently considering to deploy Network Service Providers (NSPs) are currently considering to deploy
Content Delivery Networks (CDNs) within their networks. As a Content Delivery Networks (CDNs) within their networks. As a
consequence of this development, there is a need for interconnecting consequence of this development, there is a need for interconnecting
these local CDNs. The necessary interfaces for inter-connecting CDNs these local CDNs. The necessary interfaces for inter-connecting CDNs
are currently being defined in the Content Delivery Networks are currently being defined in the Content Delivery Networks
Interconnection (CDNI) WG. This document focuses on the CDNI Interconnection (CDNI) WG. This document focuses on the CDNI
Footprint & Capabilities Advertisement interface (FCI). Footprint & Capabilities Advertisement interface (FCI).
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 December 29, 2014. This Internet-Draft will expire on September 6, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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 29 skipping to change at page 2, line 29
3. Assumptions and High-Level Design Considerations . . . . . . 4 3. Assumptions and High-Level Design Considerations . . . . . . 4
3.1. General Assumptions and Considerations . . . . . . . . . 4 3.1. General Assumptions and Considerations . . . . . . . . . 4
3.2. Semantics for Footprint/Capabilities Advertisment . . . . 5 3.2. Semantics for Footprint/Capabilities Advertisment . . . . 5
3.3. Advantages of using ALTO as the CDNI FCI protocol . . . . 7 3.3. Advantages of using ALTO as the CDNI FCI protocol . . . . 7
3.4. Selection of a Downstream CDN with ALTO . . . . . . . . . 7 3.4. Selection of a Downstream CDN with ALTO . . . . . . . . . 7
4. CDNI FCI ALTO Service . . . . . . . . . . . . . . . . . . . . 8 4. CDNI FCI ALTO Service . . . . . . . . . . . . . . . . . . . . 8
4.1. Server Response Encoding . . . . . . . . . . . . . . . . 8 4.1. Server Response Encoding . . . . . . . . . . . . . . . . 8
4.1.1. CDNI FCI Map . . . . . . . . . . . . . . . . . . . . 8 4.1.1. CDNI FCI Map . . . . . . . . . . . . . . . . . . . . 8
4.1.2. Meta Information . . . . . . . . . . . . . . . . . . 8 4.1.2. Meta Information . . . . . . . . . . . . . . . . . . 8
4.1.3. Data Information . . . . . . . . . . . . . . . . . . 8 4.1.3. Data Information . . . . . . . . . . . . . . . . . . 8
4.2. Protocol Errors . . . . . . . . . . . . . . . . . . . . . 8 4.2. Protocol Errors . . . . . . . . . . . . . . . . . . . . . 9
4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Useful ALTO extensions for CDNI Request Routing . . . . . . . 10 5. Useful ALTO extensions for CDNI Request Routing . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Many Network Service Providers (NSPs) are currently considering or Many Network Service Providers (NSPs) are currently considering or
have already started to deploy Content Delivery Networks (CDNs) have already started to deploy Content Delivery Networks (CDNs)
within their networks. As a consequence of this development, there within their networks. As a consequence of this development, there
is a need for interconnecting these local CDNs. Content Delivery is a need for interconnecting these local CDNs. Content Delivery
Networks Interconnection (CDNI) has the goal of standardizing Networks Interconnection (CDNI) has the goal of standardizing
protocols to enable such interconnection of CDNs [RFC6707]. protocols to enable such interconnection of CDNs [RFC6707].
skipping to change at page 3, line 15 skipping to change at page 3, line 15
o CDNI Logging Interface o CDNI Logging Interface
o CDNI Control Interface o CDNI Control Interface
This document focuses solely on the CDNI Request Routing Interface, This document focuses solely on the CDNI Request Routing Interface,
which can be further divided into two interfaces (see [RFC6707] for a which can be further divided into two interfaces (see [RFC6707] for a
detailed description): the CDNI Request Routing Redirection interface detailed description): the CDNI Request Routing Redirection interface
(RI), and the CDNI Footprint & Capabilities Advertisement interface (RI), and the CDNI Footprint & Capabilities Advertisement interface
(FCI). This document specifies a new Application Layer Traffic (FCI). This document specifies a new Application Layer Traffic
Optimization (ALTO) [I-D.ietf-alto-protocol] service called 'CDNI Optimization (ALTO) [RFC7285] service called 'CDNI Footprint &
Footprint & Capabilities Advertisement Service'. This service is Capabilities Advertisement Service'. This service is used to
used to transport a CDNI FCI JSON objects, which are defined in a transport CDNI FCI JSON objects, which are defined in a separate
separate document [I-D.ma-cdni-capabilities]. document [I-D.ma-cdni-capabilities]. An abstraction for managing
individual CDNI capabilities in an opaque manner is defined as
'FCIBase' object in [I-D.ietf-cdni-footprint-capabilities-semantics].
Throughout this document, we use the terminology for CDNI defined in Throughout this document, we use the terminology for CDNI defined in
[I-D.ietf-cdni-problem-statement]. [RFC6707].
2. ALTO within CDNI Request Routing 2. ALTO within CDNI Request Routing
The main purpose of the CDNI Request Routing Interface is described The main purpose of the CDNI Request Routing Interface is described
in [RFC6707] as follows: "The CDNI Request Routing interface enables in [RFC6707] as follows: "The CDNI Request Routing interface enables
a Request Routing function in an Upstream CDN to query a Request a Request Routing function in an Upstream CDN to query a Request
Routing function in a Downstream CDN to determine if the Downstream Routing function in a Downstream CDN to determine if the Downstream
CDN is able (and willing) to accept the delegated Content Request. CDN is able (and willing) to accept the delegated Content Request.
It also allows the Downstream CDN to control what should be returned It also allows the Downstream CDN to control what should be returned
to the User Agent in the redirection message by the upstream Request to the User Agent in the redirection message by the upstream Request
Routing function." On a high level, the scope of the CDNI Request Routing function." On a high level, the scope of the CDNI Request
Routing Interface therefore contains two main tasks: Routing Interface therefore contains two main tasks:
o A) Determining if the downstream CDN is willing to accept a o A) Determining if the downstream CDN is willing to accept a
delegated content request delegated content request
o B) Redirecting the content request coming from an upstream CDN to o B) Redirecting the content request coming from an upstream CDN to
the proper entry point or entity in the downstream CDN the proper entry point or entity in the downstream CDN
More precisely, in [I-D.ietf-cdni-framework] the request routing More precisely, in [RFC7336] the request routing interface is broadly
interface is broadly divided into two functionalities: divided into two functionalities:
o 1) the asynchronous advertisement of footprint and capabilities by o 1) the asynchronous advertisement of footprint and capabilities by
a dCDN that allows a uCDN to decide whether to redirect particular a dCDN that allows a uCDN to decide whether to redirect particular
user requests to that dCDN (the CDNI FCI) user requests to that dCDN (the CDNI FCI)
o 2) the synchronous operation of actually redirecting a user o 2) the synchronous operation of actually redirecting a user
request (the CDNI RI) request (the CDNI RI)
Application Layer Traffic Optimization (ALTO) Application Layer Traffic Optimization (ALTO) [RFC7285] is an
[I-D.ietf-alto-protocol] is an approach for guiding the resource approach for guiding the resource provider selection process in
provider selection process in distributed applications that can distributed applications that can choose among several candidate
choose among several candidate resources providers to retrieve a resources providers to retrieve a given resource. By conveying
given resource. By conveying network layer (topology) information, network layer (topology) information, an ALTO server can provide
an ALTO server can provide important information to "guide" the important information to "guide" the resource provider selection
resource provider selection process in distributed applications. process in distributed applications. Usually, it is assumed that an
Usually, it is assumed that an ALTO server conveys information these ALTO server conveys information these applications cannot measure
applications cannot measure themselves [RFC5693]. themselves [RFC5693].
Originally, ALTO was motivated by the huge amount of cross-ISP Originally, ALTO was motivated by the huge amount of cross-ISP
traffic generated by P2P applications [RFC5693]. Recently, however, traffic generated by P2P applications [RFC5693]. Recently, however,
ALTO is also being considered for improving the request routing in ALTO is also being considered for improving the request routing in
CDNs [I-D.jenkins-alto-cdn-use-cases]. In this context, it has also CDNs [I-D.jenkins-alto-cdn-use-cases]. In this context, it has also
been proposed to use ALTO for selecting an entry-point in a been proposed to use ALTO for selecting an entry-point in a
downstream NSP's network (see section 3.4 "CDN delivering Over-The- downstream NSP's network (see section 3.4 "CDN delivering Over-The-
Top of a NSP's network" in [I-D.jenkins-alto-cdn-use-cases]). Also, Top of a NSP's network" in [I-D.jenkins-alto-cdn-use-cases]). Also,
the CDNI problem statement explicitly mentions ALTO as a candidate the CDNI problem statement explicitly mentions ALTO as a candidate
protocol for "algorithms for selection of CDN or Surrogate by protocol for "algorithms for selection of CDN or Surrogate by
Request-Routing systems" [I-D.ietf-cdni-problem-statement]. Request-Routing systems" [RFC6707].
3. Assumptions and High-Level Design Considerations 3. Assumptions and High-Level Design Considerations
In this section we list some assumptions and design issues to be In this section we list some assumptions and design issues to be
considered when using ALTO for the CDNI Footprint and Capabilities considered when using ALTO for the CDNI Footprint and Capabilities
Advertisement interface. Advertisement interface.
3.1. General Assumptions and Considerations 3.1. General Assumptions and Considerations
Below we list some general assumptions and considerations: Below we list some general assumptions and considerations:
o As explicitly being out-of-scope for CDNI o As explicitly being out-of-scope for CDNI [RFC6707], it is assumed
[I-D.ietf-cdni-problem-statement], it is assumed that ingestion of that ingestion of content or acquiring content across CDNs is not
content or acquiring content across CDNs is not part of request part of request routing as considered within CDNI standardization
routing as considered within CDNI standardization work. The focus work. The focus of using ALTO (as considered in this document) is
of using ALTO (as considered in this document) is hence on request hence on request routing only, assuming that the content (desired
routing only, assuming that the content (desired by the end user) by the end user) is available in the downstream CDN (or can be
is available in the downstream CDN (or can be aquired by the aquired by the downstream CDN by some means).
downstream CDN by some means).
o Federation Model: "Footprint and Capabilities Advertisement" and o Federation Model: "Footprint and Capabilities Advertisement" and
in general CDN request routing depends on the federation model in general CDN request routing depends on the federation model
among the CDN providers. Designing a suitable solution thus among the CDN providers. Designing a suitable solution thus
depends on whether a solution is needed for different settings, depends on whether a solution is needed for different settings,
where CDNs consist of both NSP CDNs (serving individual ASes) and where CDNs consist of both NSP CDNs (serving individual ASes) and
general, traditional CDNs (such as Akamai). We assume that CDNI general, traditional CDNs (such as Akamai). We assume that CDNI
is not designed for a setting where only NSP CDNs each serve a is not designed for a setting where only NSP CDNs each serve a
single AS only. single AS only.
skipping to change at page 6, line 47 skipping to change at page 6, line 47
o The following capabilities seem useful as 'base' capabilities, o The following capabilities seem useful as 'base' capabilities,
i.e. ones that are needed in any case and therefore constitute i.e. ones that are needed in any case and therefore constitute
mandatory capabilities to be supported by the CDNI FCI: mandatory capabilities to be supported by the CDNI FCI:
* Delivery Protocol (e.g., HTTP vs. RTMP) * Delivery Protocol (e.g., HTTP vs. RTMP)
* Acquisition Protocol (for aquiring content from a uCDN) * Acquisition Protocol (for aquiring content from a uCDN)
* Redirection Mode (e.g., DNS Redirection vs. HTTP Redirection as * Redirection Mode (e.g., DNS Redirection vs. HTTP Redirection as
discussed in [I-D.ietf-cdni-framework]) discussed in [RFC7336])
* Capabilities related to CDNI Logging (e.g., supported logging * Capabilities related to CDNI Logging (e.g., supported logging
mechanisms) 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)
3.3. Advantages of using ALTO as the CDNI FCI protocol 3.3. Advantages of using ALTO as the CDNI FCI protocol
The following reasons make ALTO a suitable candidate protocol for The following reasons make ALTO a suitable candidate protocol for
skipping to change at page 7, line 44 skipping to change at page 7, line 44
client-server interaction specified by the protocol. A CDNI FCI client-server interaction specified by the protocol. A CDNI FCI
interface based on ALTO would inherit this RESTful design. interface based on ALTO would inherit this RESTful design.
o Error-handling: The ALTO protocol has undergone extensive o Error-handling: The ALTO protocol has undergone extensive
revisions in order to provide sophisticated error-handling, revisions in order to provide sophisticated error-handling,
inparticular regarding unexpected cases. A CDNI FCI interface inparticular regarding unexpected cases. A CDNI FCI interface
based on ALTO would inherit this thought-through and mature error- based on ALTO would inherit this thought-through and mature error-
handling. handling.
o Filtered network map: The ALTO Map Filtering Service (see o Filtered network map: The ALTO Map Filtering Service (see
[I-D.ietf-alto-protocol] for details) would allow a uCDN to query [RFC7285] for details) would allow a uCDN to query only for parts
only for parts of an ALTO map. of an ALTO map.
3.4. Selection of a Downstream CDN with ALTO 3.4. Selection of a Downstream CDN with ALTO
Under the considerations stated in Section 3, ALTO can help the Under the considerations stated in Section 3, ALTO can help the
upstream CDN provider to select a proper downstream CDN provider for upstream CDN provider to select a proper downstream CDN provider for
a given end user request as follows: Each downstream CDN provider a given end user request as follows: Each downstream CDN provider
hosts an ALTO server which provides ALTO services which convey CDNI hosts an ALTO server which provides ALTO services which convey CDNI
FCI information to an ALTO client at the upstream CDN provider. FCI information to an ALTO client at the upstream CDN provider.
4. CDNI FCI ALTO Service 4. CDNI FCI ALTO Service
The ALTO protocol is based on an ALTO Information Service Framework The ALTO protocol is based on an ALTO Information Service Framework
which consists of several services, where all ALTO services are which consists of several services, where all ALTO services are
'provided through a common transport protocol, messaging structure 'provided through a common transport protocol, messaging structure
and encoding, and transaction model" [I-D.ietf-alto-protocol]. The and encoding, and transaction model' [RFC7285]. The ALTO protocol
ALTO protocol specification [I-D.ietf-alto-protocol] defines several specification [RFC7285] defines several such services, e.g. the ALTO
such services, e.g. the ALTO map service. map service.
This document defines a new ALTO Service called 'CDNI Footprint & This document defines a new ALTO Service called 'CDNI Footprint &
Capabilities Advertisement Service' which conveys JSON objects of Capabilities Advertisement Service' which conveys JSON objects of
media type 'application/alto-fcimap+json'. This media type and JSON media type 'application/alto-fcimap+json'. This media type and JSON
object format is defined in [I-D.ma-cdni-capabilities]; this document object format is defined in [I-D.ma-cdni-capabilities]; this document
specifies how to transport such JSON objects via the ALTO protocol specifies how to transport such JSON objects via the ALTO protocol
with the ALTO 'CDNI Footprint & Capabilities Advertisement Service'. with the ALTO 'CDNI Footprint & Capabilities Advertisement Service'.
An abstraction for managing individual CDNI capabilities in an opaque
manner is defined as 'FCIBase' object in
[I-D.ietf-cdni-footprint-capabilities-semantics].
4.1. Server Response Encoding 4.1. Server Response Encoding
4.1.1. CDNI FCI Map 4.1.1. CDNI FCI Map
The media type of the CDNI FCI Map is 'application/alto-cdni- The media type of the CDNI FCI Map is 'application/alto-cdni-
fcimap+json'. The HTTP Method, Accept Input Parameters, fcimap+json'. The HTTP Method, Accept Input Parameters,
Capabilities, Uses, and Response of the CDNI FCI Map are specified in Capabilities, Uses, and Response of the CDNI FCI Map are specified in
[I-D.ma-cdni-capabilities]. [I-D.ma-cdni-capabilities].
4.1.2. Meta Information 4.1.2. Meta Information
The 'meta' field of a FCIMapData response MUST include 'vtag', which The 'meta' field of a FCIMapData response MUST include 'vtag', which
is an ALTO Version Tag of the retrieved FCIMapData according to is an ALTO Version Tag of the retrieved FCIMapData according to
[I-D.ietf-alto-protocol] (Section 10.3.). It thus contains a [RFC7285] (Section 10.3.). It thus contains a 'resource-id'
'resource-id' attribute, and a 'tag' is an identifier string. attribute, and a 'tag' is an identifier string.
4.1.3. Data Information 4.1.3. Data Information
The data component of a CDNI FCI Map resource is named 'fcimap' which The data component of a CDNI FCI Map resource is named 'fcimap' which
is a JSON object of type FCIMapData. This JSON object of type is a JSON object of type FCIMapData. This JSON object of type
FCIMapData is derived from ResponseEntityBase as specified in the FCIMapData is derived from ResponseEntityBase as specified in the
ALTO protocol [I-D.ietf-alto-protocol] (Section 8.4.) and specified ALTO protocol [RFC7285] (Section 8.4.) and specified in
in [I-D.ma-cdni-capabilities]. [I-D.ma-cdni-capabilities].
4.2. Protocol Errors 4.2. Protocol Errors
Protocol errors are handled as specified in the ALTO protocol Protocol errors are handled as specified in the ALTO protocol
[I-D.ietf-alto-protocol] (Section 8.5.). [RFC7285] (Section 8.5.).
4.3. Example 4.3. Example
The following example shows an CDNI FCI Map as in The following example shows an CDNI FCI Map as in
[I-D.ma-cdni-capabilities], however with meta-information as defined [I-D.ma-cdni-capabilities], however with meta-information as defined
in Section 4.1.2 of this document. in Section 4.1.2 of this document.
GET /fcimap HTTP/1.1 GET /fcimap HTTP/1.1
Host: alto.example.com Host: alto.example.com
Accept: application/alto-fcimap+json,application/alto-error+json Accept: application/alto-fcimap+json,application/alto-error+json
skipping to change at page 11, line 13 skipping to change at page 12, line 10
bandwidth) before it redirects the request. In general, if ALTO bandwidth) before it redirects the request. In general, if ALTO
could convey such information via new endpoint properties, it could convey such information via new endpoint properties, it
would enable more sophisticated means for downstream CDN selection would enable more sophisticated means for downstream CDN selection
with ALTO. with ALTO.
6. Security Considerations 6. Security Considerations
One important security consideration is the proper authentication of One important security consideration is the proper authentication of
advertisement information provided by a downstream CDN. The ALTO advertisement information provided by a downstream CDN. The ALTO
protocol provides a specification for a signature of ALTO information protocol provides a specification for a signature of ALTO information
(see 8.2.2. of [I-D.ietf-alto-protocol]. ALTO thus provides a proper (see 8.2.2. of [RFC7285]. ALTO thus provides a proper means for
means for protecting the integrity of FCI information. protecting the integrity of FCI information.
More Security Considerations will be discussed in a future version of More Security Considerations will be discussed in a future version of
this document. this document.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Kevin Ma, Daryl Malas, and Matt The authors would like to thank Kevin Ma, Daryl Malas, and Matt
Caulfield for their timely reviews and invaluable comments. Caulfield for their timely reviews and invaluable comments.
Jan Seedorf is partially supported by the GreenICN project (GreenICN: Jan Seedorf is partially supported by the GreenICN project (GreenICN:
skipping to change at page 12, line 5 skipping to change at page 12, line 48
2009. 2009.
[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.
[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.
[RFC7285] Alimi, R., Penno, R., Yang, Y., Kiesel, S., Previdi, S.,
Roome, W., Shalunov, S., and R. Woundy, "Application-Layer
Traffic Optimization (ALTO) Protocol", RFC 7285, September
2014.
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg,
"Framework for Content Distribution Network
Interconnection (CDNI)", RFC 7336, August 2014.
[RFC7337] Leung, K. and Y. Lee, "Content Distribution Network
Interconnection (CDNI) Requirements", RFC 7337, August
2014.
8.2. Informative References 8.2. Informative References
[I-D.peterson-CDNI-strawman] [I-D.peterson-CDNI-strawman]
Peterson, L. and J. Hartman, "Content Distribution Network Peterson, L. and J. Hartman, "Content Distribution Network
Interconnection (CDNI) Problem Statement", draft-peterson- Interconnection (CDNI) Problem Statement", draft-peterson-
CDNI-strawman-01 (work in progress), May 2011. CDNI-strawman-01 (work in progress), May 2011.
[I-D.ietf-cdni-problem-statement]
Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem
Statement", draft-ietf-cdni-problem-statement-08 (work in
progress), June 2012.
[I-D.marocco-alto-next] [I-D.marocco-alto-next]
Marocco, E. and V. Gurbani, "Extending the Application- Marocco, E. and V. Gurbani, "Extending the Application-
Layer Traffic Optimization (ALTO) Protocol", draft- Layer Traffic Optimization (ALTO) Protocol", draft-
marocco-alto-next-00 (work in progress), January 2012. marocco-alto-next-00 (work in progress), January 2012.
[I-D.ietf-alto-protocol]
Alimi, R., Penno, R., and Y. Yang, "ALTO Protocol", draft-
ietf-alto-protocol-27 (work in progress), March 2014.
[I-D.ietf-cdni-requirements]
Leung, K. and Y. Lee, "Content Distribution Network
Interconnection (CDNI) Requirements", draft-ietf-cdni-
requirements-17 (work in progress), January 2014.
[I-D.ietf-cdni-use-cases]
Bertrand, G., Emile, S., Burbridge, T., Eardley, P., Ma,
K., and G. Watson, "Use Cases for Content Delivery Network
Interconnection", draft-ietf-cdni-use-cases-10 (work in
progress), August 2012.
[I-D.marocco-alto-ws] [I-D.marocco-alto-ws]
Marocco, E. and J. Seedorf, "WebSocket-based server-to- Marocco, E. and J. Seedorf, "WebSocket-based server-to-
client notifications for the Application-Layer Traffic client notifications for the Application-Layer Traffic
Optimization (ALTO) Protocol", draft-marocco-alto-ws-02 Optimization (ALTO) Protocol", draft-marocco-alto-ws-02
(work in progress), February 2014. (work in progress), February 2014.
[I-D.schwan-alto-incr-updates] [I-D.schwan-alto-incr-updates]
Schwan, N. and B. Roome, "ALTO Incremental Updates", Schwan, N. and B. Roome, "ALTO Incremental Updates",
draft-schwan-alto-incr-updates-02 (work in progress), July draft-schwan-alto-incr-updates-02 (work in progress), July
2012. 2012.
[I-D.jenkins-alto-cdn-use-cases] [I-D.jenkins-alto-cdn-use-cases]
Niven-Jenkins, B., Watson, G., Bitar, N., Medved, J., and Niven-Jenkins, B., Watson, G., Bitar, N., Medved, J., and
S. Previdi, "Use Cases for ALTO within CDNs", draft- S. Previdi, "Use Cases for ALTO within CDNs", draft-
jenkins-alto-cdn-use-cases-03 (work in progress), June jenkins-alto-cdn-use-cases-03 (work in progress), June
2012. 2012.
[I-D.ma-cdni-capabilities] [I-D.ma-cdni-capabilities]
Ma, K. and J. Seedorf, "CDNI Footprint & Capabilities Ma, K. and J. Seedorf, "CDNI Footprint & Capabilities
Advertisement Interface", draft-ma-cdni-capabilities-05 Advertisement Interface", draft-ma-cdni-capabilities-06
(work in progress), June 2014.
[I-D.ietf-cdni-framework]
Peterson, L., Davie, B., and R. Brandenburg, "Framework
for CDN Interconnection", draft-ietf-cdni-framework-14
(work in progress), June 2014. (work in progress), June 2014.
[I-D.liu-cdni-cost] [I-D.liu-cdni-cost]
Liu, H., "A Cost Perspective on Using Multiple CDNs", Liu, H., "A Cost Perspective on Using Multiple CDNs",
draft-liu-cdni-cost-00 (work in progress), October 2011. draft-liu-cdni-cost-00 (work in progress), October 2011.
[I-D.spp-cdni-rr-foot-cap-semantics]
Seedorf, J., Peterson, J., Previdi, S., Brandenburg, R.,
and K. Ma, "CDNI Request Routing: Footprint and
Capabilities Semantics", draft-spp-cdni-rr-foot-cap-
semantics-04 (work in progress), February 2013.
[I-D.ietf-cdni-metadata] [I-D.ietf-cdni-metadata]
Niven-Jenkins, B., Murray, R., Watson, G., Caulfield, M., Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma,
Leung, K., and K. Ma, "CDN Interconnect Metadata", draft- "CDN Interconnection Metadata", draft-ietf-cdni-
ietf-cdni-metadata-06 (work in progress), February 2014. metadata-09 (work in progress), March 2015.
[I-D.ietf-cdni-logging] [I-D.ietf-cdni-logging]
Faucheur, F., Bertrand, G., Oprescu, I., and R. Faucheur, F., Bertrand, G., Oprescu, I., and R.
Peterkofsky, "CDNI Logging Interface", draft-ietf-cdni- Peterkofsky, "CDNI Logging Interface", draft-ietf-cdni-
logging-11 (work in progress), March 2014. logging-15 (work in progress), February 2015.
[I-D.ietf-cdni-footprint-capabilities-semantics] [I-D.ietf-cdni-footprint-capabilities-semantics]
Seedorf, J., Peterson, J., Previdi, S., Brandenburg, R., Seedorf, J., Peterson, J., Previdi, S., Brandenburg, R.,
and K. Ma, "CDNI Request Routing: Footprint and and K. Ma, "CDNI Request Routing: Footprint and
Capabilities Semantics", draft-ietf-cdni-footprint- Capabilities Semantics", draft-ietf-cdni-footprint-
capabilities-semantics-02 (work in progress), February capabilities-semantics-05 (work in progress), March 2015.
2014.
Authors' Addresses Authors' Addresses
Jan Seedorf Jan Seedorf
NEC Laboratories Europe, NEC Europe Ltd. NEC Laboratories Europe, NEC Europe Ltd.
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
Germany Germany
Phone: +49 (0) 6221 4342 221 Phone: +49 (0) 6221 4342 221
Email: jan.seedorf@neclab.eu Email: jan.seedorf@neclab.eu
URI: http://www.neclab.eu URI: http://www.neclab.eu
 End of changes. 30 change blocks. 
89 lines changed or deleted 74 lines changed or added

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