draft-ietf-alto-multi-cost-06.txt   draft-ietf-alto-multi-cost-07.txt 
Network Working Group S. Randriamasy Network Working Group S. Randriamasy
Internet-Draft W. Roome Internet-Draft W. Roome
Intended status: Standards Track Nokia Bell Labs Intended status: Standards Track Nokia Bell Labs
Expires: September 11, 2017 N. Schwan Expires: September 11, 2017 N. Schwan
Thales Deutschland Thales Deutschland
March 10, 2017 March 10, 2017
Multi-Cost ALTO Multi-Cost ALTO
draft-ietf-alto-multi-cost-06 draft-ietf-alto-multi-cost-07
Abstract Abstract
The ALTO (Application Layer-Traffic Optimization) Protocol The ALTO (Application Layer-Traffic Optimization) Protocol
([RFC7285]) defines several services that return various metrics ([RFC7285]) defines several services that return various metrics
describing the costs between network endpoints. An ALTO Server may describing the costs between network endpoints. An ALTO Server may
offer a variety of cost metrics, based on latency,bandwidth, hop offer a variety of cost metrics, based on latency,bandwidth, hop
count, jitter, or whatever else the ALTO Server deems useful. For count, jitter, or whatever else the ALTO Server deems useful. For
example, when downloading a file that is mirrored on several sites, a example, when downloading a file that is mirrored on several sites, a
user application may consider more than one metric, perhaps trading user application may consider more than one metric, perhaps trading
skipping to change at page 3, line 4 skipping to change at page 3, line 4
4.1.1. Capabilities . . . . . . . . . . . . . . . . . . . . 12 4.1.1. Capabilities . . . . . . . . . . . . . . . . . . . . 12
4.1.2. Accept Input Parameters . . . . . . . . . . . . . . . 13 4.1.2. Accept Input Parameters . . . . . . . . . . . . . . . 13
4.1.3. Response . . . . . . . . . . . . . . . . . . . . . . 16 4.1.3. Response . . . . . . . . . . . . . . . . . . . . . . 16
4.2. Endpoint Cost Service Extensions . . . . . . . . . . . . 16 4.2. Endpoint Cost Service Extensions . . . . . . . . . . . . 16
4.2.1. Capabilities . . . . . . . . . . . . . . . . . . . . 16 4.2.1. Capabilities . . . . . . . . . . . . . . . . . . . . 16
4.2.2. Accept Input Parameters . . . . . . . . . . . . . . . 16 4.2.2. Accept Input Parameters . . . . . . . . . . . . . . . 16
4.2.3. Response . . . . . . . . . . . . . . . . . . . . . . 17 4.2.3. Response . . . . . . . . . . . . . . . . . . . . . . 17
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1. Information Resource Directory . . . . . . . . . . . . . 18 5.1. Information Resource Directory . . . . . . . . . . . . . 18
5.2. Multi-Cost Filtered Cost Map: Example #1 . . . . . . . . 20 5.2. Multi-Cost Filtered Cost Map: Example #1 . . . . . . . . 20
5.3. Multi-Cost Filtered Cost Map: Example #2 . . . . . . . . 21 5.3. Multi-Cost Filtered Cost Map: Example #2 . . . . . . . . 22
5.4. Multi-Cost Filtered Cost Map: Example #3 . . . . . . . . 23 5.4. Multi-Cost Filtered Cost Map: Example #3 . . . . . . . . 23
5.5. Multi-Cost Filtered Cost Map: Example #4 . . . . . . . . 24 5.5. Multi-Cost Filtered Cost Map: Example #4 . . . . . . . . 25
5.6. Endpoint Cost Service . . . . . . . . . . . . . . . . . . 26 5.6. Endpoint Cost Service . . . . . . . . . . . . . . . . . . 26
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
7. Privacy And Security Considerations . . . . . . . . . . . . . 27 7. Privacy And Security Considerations . . . . . . . . . . . . . 27
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.1. Normative References . . . . . . . . . . . . . . . . . . 28 9.1. Normative References . . . . . . . . . . . . . . . . . . 28
9.2. Informative References . . . . . . . . . . . . . . . . . 28 9.2. Informative References . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
skipping to change at page 18, line 20 skipping to change at page 18, line 20
the same cardinality as the "multi-cost-types" input parameter, the same cardinality as the "multi-cost-types" input parameter,
and contain the cost type values in that order. If a cost type is and contain the cost type values in that order. If a cost type is
not available for a particular source and destination, the ALTO not available for a particular source and destination, the ALTO
Server MUST use the JSON "null" value for that array element. If Server MUST use the JSON "null" value for that array element. If
none of the cost types are available for a particular source and none of the cost types are available for a particular source and
destination, the ALTO Server MAY omit the entry for that source destination, the ALTO Server MAY omit the entry for that source
and destination. and destination.
5. Examples 5. Examples
The examples exposed in this section use cost metrics such as
'hopcount', and 'bandwidthscore' that are not registered at the IANA.
These metrics are only here for illustrative purposes and reflect
widely valued information by applications.
5.1. Information Resource Directory 5.1. Information Resource Directory
The following is an example of an ALTO Server's Information Resource The following is an example of an ALTO Server's Information Resource
Directory. In addition to Network and Cost Map resources, it defines Directory. In addition to Network and Cost Map resources, it defines
two Filtered Cost Map and an Endpoint Cost Service, which all two Filtered Cost Map and an Endpoint Cost Service, which all
understand the multi-cost extensions. understand the multi-cost extensions.
GET /directory HTTP/1.1 GET /directory HTTP/1.1
Host: alto.example.com Host: alto.example.com
Accept: application/alto-directory+json,application/alto-error+json Accept: application/alto-directory+json,application/alto-error+json
 End of changes. 4 change blocks. 
3 lines changed or deleted 8 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/