draft-seedorf-cdni-request-routing-alto-08.txt   draft-seedorf-cdni-request-routing-alto-09.txt 
CDNI J. Seedorf CDNI J. Seedorf
Internet-Draft NEC Internet-Draft HFT Stuttgart - Univ. of Applied Sciences
Intended status: Informational Y. Yang Intended status: Standards Track Y. Yang
Expires: September 6, 2015 Yale Expires: January 3, 2018 Tongji/Yale
J. Peterson J. Peterson
Neustar Neustar
March 5, 2015 July 2, 2017
CDNI Footprint and Capabilities Advertisement using ALTO Content Delivery Network Interconnection (CDNI) Request Routing: CDNI
draft-seedorf-cdni-request-routing-alto-08 Footprint and Capabilities Advertisement using ALTO
draft-seedorf-cdni-request-routing-alto-09
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 43
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 September 6, 2015. This Internet-Draft will expire on January 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . 9 4.2. Protocol Errors . . . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
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 18 skipping to change at page 3, line 18
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) [RFC7285] service called 'CDNI Footprint & Optimization (ALTO) [RFC7285] service called 'CDNI Footprint &
Capabilities Advertisement Service'. This service is used to Capabilities Advertisement Service'. This service is used to
transport CDNI FCI JSON objects, which are defined in a separate transport CDNI FCI JSON objects, which are defined in a separate
document [I-D.ma-cdni-capabilities]. An abstraction for managing document in [RFC8008].
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
[RFC6707]. [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
skipping to change at page 5, line 25 skipping to change at page 5, line 25
operational relationships two peering CDNs may form. For the operational relationships two peering CDNs may form. For the
Internet, we see provider-customer and peering as two main Internet, we see provider-customer and peering as two main
relations; providers may use different charging models (e.g., relations; providers may use different charging models (e.g.,
95-percentile, total volume) and may provide different SLAs. 95-percentile, total volume) and may provide different SLAs.
Given such unknown characteristics of CDN peering business Given such unknown characteristics of CDN peering business
agreements, we should design the protocol to support as much agreements, we should design the protocol to support as much
diverse potential business and operational models as possible. diverse potential business and operational models as possible.
3.2. Semantics for Footprint/Capabilities Advertisment 3.2. Semantics for Footprint/Capabilities Advertisment
The CDNI document on "Footprint and Capabilities Semantics" The CDNI document on "Footprint and Capabilities Semantics" [RFC8008]
[I-D.ietf-cdni-footprint-capabilities-semantics] defines the defines the semantics for the CDNI FCI. It thus provides guidance on
semantics for the CDNI FCI. It thus provides guidance on what what Footprint and Capabilities mean in a CDNI context and how a
Footprint and Capabilities mean in a CDNI context and how a protocol protocol solution should in principle look like. Here we briefly
solution should in principle look like. Here we briefly summarize summarize the key points of the semantics of Footprint and
the key points of the semantics of Footprint and Capabilities (for a Capabilities (for a detailed discussion, the reader is referred to
detailed discussion, the reader is referred to [RFC8008]):
[I-D.ietf-cdni-footprint-capabilities-semantics]):
o Often, footprint and capabilities are tied together and cannot be o Often, footprint and capabilities are tied together and cannot be
interpreted independently from each other. In such cases, i.e. interpreted independently from each other. In such cases, i.e.
where capabilities must be expressed on a per footprint basis, it where capabilities must be expressed on a per footprint basis, it
may be beneficial to combine footprint and capabilities may be beneficial to combine footprint and capabilities
advertisement. advertisement.
o Given that a large part of Footprint and Capabilities o Given that a large part of Footprint and Capabilities
Advertisement will actually happen in contractual agreements, the Advertisement will actually happen in contractual agreements, the
semantics of CDNI Footprint and Capabilities advertisement refer semantics of CDNI Footprint and Capabilities advertisement refer
skipping to change at page 8, line 19 skipping to change at page 8, line 19
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' [RFC7285]. The ALTO protocol and encoding, and transaction model' [RFC7285]. The ALTO protocol
specification [RFC7285] defines several such services, e.g. the ALTO specification [RFC7285] defines several 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 [RFC8008]; this document specifies how to
specifies how to transport such JSON objects via the ALTO protocol transport such JSON objects via the ALTO protocol with the ALTO 'CDNI
with the ALTO 'CDNI Footprint & Capabilities Advertisement Service'. 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].
skipping to change at page 12, line 37 skipping to change at page 11, line 40
contained herein are those of the authors and should not be contained herein are those of the authors and should not be
interpreted as necessarily representing the official policies or interpreted as necessarily representing the official policies or
endorsements, either expressed or implied, of the GreenICN project, endorsements, either expressed or implied, of the GreenICN project,
the European Commission, or NICT. the European Commission, or NICT.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic [RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic
Optimization (ALTO) Problem Statement", RFC 5693, October Optimization (ALTO) Problem Statement", RFC 5693,
2009. DOI 10.17487/RFC5693, October 2009,
<http://www.rfc-editor.org/info/rfc5693>.
[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, DOI 10.17487/RFC6707, September
2012, <http://www.rfc-editor.org/info/rfc6707>.
[RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma, [RFC6770] Bertrand, G., Ed., Stephan, E., Burbridge, T., Eardley,
K., and G. Watson, "Use Cases for Content Delivery Network P., Ma, K., and G. Watson, "Use Cases for Content Delivery
Interconnection", RFC 6770, November 2012. Network Interconnection", RFC 6770, DOI 10.17487/RFC6770,
November 2012, <http://www.rfc-editor.org/info/rfc6770>.
[RFC7285] Alimi, R., Penno, R., Yang, Y., Kiesel, S., Previdi, S., [RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S.,
Roome, W., Shalunov, S., and R. Woundy, "Application-Layer Previdi, S., Roome, W., Shalunov, S., and R. Woundy,
Traffic Optimization (ALTO) Protocol", RFC 7285, September "Application-Layer Traffic Optimization (ALTO) Protocol",
2014. RFC 7285, DOI 10.17487/RFC7285, September 2014,
<http://www.rfc-editor.org/info/rfc7285>.
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed.,
"Framework for Content Distribution Network "Framework for Content Distribution Network
Interconnection (CDNI)", RFC 7336, August 2014. Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336,
August 2014, <http://www.rfc-editor.org/info/rfc7336>.
[RFC7337] Leung, K. and Y. Lee, "Content Distribution Network [RFC7337] Leung, K., Ed. and Y. Lee, Ed., "Content Distribution
Interconnection (CDNI) Requirements", RFC 7337, August Network Interconnection (CDNI) Requirements", RFC 7337,
2014. DOI 10.17487/RFC7337, August 2014,
<http://www.rfc-editor.org/info/rfc7337>.
8.2. Informative References [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg,
R., and K. Ma, "Content Delivery Network Interconnection
(CDNI) Request Routing: Footprint and Capabilities
Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016,
<http://www.rfc-editor.org/info/rfc8008>.
[I-D.peterson-CDNI-strawman] 8.2. Informative References
Peterson, L. and J. Hartman, "Content Distribution Network
Interconnection (CDNI) Problem Statement", draft-peterson-
CDNI-strawman-01 (work in progress), May 2011.
[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.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
skipping to change at page 13, line 44 skipping to change at page 13, line 13
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-06 Advertisement Interface", draft-ma-cdni-capabilities-09
(work in progress), June 2014. (work in progress), April 2016.
[I-D.liu-cdni-cost]
Liu, H., "A Cost Perspective on Using Multiple CDNs",
draft-liu-cdni-cost-00 (work in progress), October 2011.
[I-D.ietf-cdni-metadata]
Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma,
"CDN Interconnection Metadata", draft-ietf-cdni-
metadata-09 (work in progress), March 2015.
[I-D.ietf-cdni-logging]
Faucheur, F., Bertrand, G., Oprescu, I., and R.
Peterkofsky, "CDNI Logging Interface", draft-ietf-cdni-
logging-15 (work in progress), February 2015.
[I-D.ietf-cdni-footprint-capabilities-semantics]
Seedorf, J., Peterson, J., Previdi, S., Brandenburg, R.,
and K. Ma, "CDNI Request Routing: Footprint and
Capabilities Semantics", draft-ietf-cdni-footprint-
capabilities-semantics-05 (work in progress), March 2015.
Authors' Addresses Authors' Addresses
Jan Seedorf Jan Seedorf
NEC Laboratories Europe, NEC Europe Ltd. HFT Stuttgart - Univ. of Applied Sciences
Kurfuersten-Anlage 36 Schellingstrasse 24
Heidelberg 69115 Stuttgart 70174
Germany Germany
Phone: +49 (0) 6221 4342 221 Phone: +49-0711-8926-2801
Email: jan.seedorf@neclab.eu Email: jan.seedorf@hft-stuttgart.de
URI: http://www.neclab.eu
Y.R. Yang Y.R. Yang
Yale University Tongji/Yale University
51 Prospect Street 51 Prospect Street
New Haven 06511 New Haven, CT 06511
USA United States of America
Email: yry@cs.yale.edu Email: yry@cs.yale.edu
URI: http://www.cs.yale.edu/~yry/ URI: http://www.cs.yale.edu/~yry/
Jon Peterson Jon Peterson
NeuStar NeuStar
1800 Sutter St Suite 570 1800 Sutter St Suite 570
Concord CA 94520 Concord, CA 94520
USA United States of America
Email: jon.peterson@neustar.biz Email: jon.peterson@neustar.biz
 End of changes. 25 change blocks. 
85 lines changed or deleted 66 lines changed or added

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