draft-ietf-alto-performance-metrics-00.txt   draft-ietf-alto-performance-metrics-01.txt 
ALTO Working Group Q. Wu ALTO Working Group Q. Wu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track Y. Yang Intended status: Standards Track Y. Yang
Expires: March 10, 2017 Yale University Expires: September 4, 2017 Yale University
Y. Lee Y. Lee
D. Dhody D. Dhody
Huawei Huawei
S. Randriamasy S. Randriamasy
Nokia Bell Labs Nokia Bell Labs
September 6, 2016 March 3, 2017
ALTO Performance Cost Metrics ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-00 draft-ietf-alto-performance-metrics-01
Abstract Abstract
Cost Metric is a basic concept in Application-Layer Traffic Cost Metric is a basic concept in Application-Layer Traffic
Optimization (ALTO). It is used in both the Cost Map Service and the Optimization (ALTO). It is used in both the Cost Map Service and the
Endpoint Cost Service. Future extensions to ALTO may also use Cost Endpoint Cost Service.
Metric.
Different applications may benefit from different Cost Metrics. For Different applications may benefit from different Cost Metrics. For
example, a Resource Consumer may prefer Resource Providers that have example, a Resource Consumer may prefer Resource Providers that
low delay to the Resource Consumer. However the base ALTO protocol offers a low delay delivery to the Resource Consumer. However the
[ALTO] has documented only a single cost metric, i.e., the generic base ALTO protocol [ALTO] has documented only one single cost metric,
"routingcost" metric (Sec. 14.2 of ALTO base specification [ALTO]). i.e., the generic "routingcost" metric (Sec. 14.2 of ALTO base
specification [ALTO]).
In this document, we proposes a set of Cost Metrics, derived and This document, proposes a set of Cost Metrics, derived and aggregated
aggregated from routing protocols with different granularity and from routing protocols with different granularity and scope, such as
scope, such as BGP-LS,OSPF-TE and ISIS-TE, or from end to end traffic BGP-LS,OSPF-TE and ISIS-TE, or from end to end traffic management
management tool. We currently document 11 new Performance Metric to tools. It currently documents Network Performance Cost Metrics
measure network delay, jitter, packet loss, hop count, and bandwidth. reporting on network delay, jitter, packet loss, hop count, and
The metrics documented in this document provide a relatively bandwidth. These metrics may be exposed by an ALTO Server to allow
comprehensive set of Cost Metrics for ALTO and allow applications to applications to determine "where" to connect based on network
determine "where" to connect based on end to end network performance performance criteria. Additional Cost Metrics involving ISP specific
criteria. Additional Cost Metrics such as financial cost metrics may considerations or other network technologies may be documented in
be documented in other documents. further versions of this draft.
Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", Requirements Language The key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as described in and "OPTIONAL" in this document are to be interpreted as described in
RFC 2119 [RFC2119]. RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 March 10, 2017. This Internet-Draft will expire on September 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Data sources, computation of defined cost metrics . . . . . . 5 2. Challenges on data sources and computation of ALTO
performance metrics . . . . . . . . . . . . . . . . . . . . . 5
2.1. Data sources . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Data sources . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Computation of metrics . . . . . . . . . . . . . . . . . 5 2.2. Computation of ALTO performance metrics . . . . . . . . . 5
3. Cost Metric: OWDelay . . . . . . . . . . . . . . . . . . . . 6 3. Cost Metric: POWDelay . . . . . . . . . . . . . . . . . . . . 6
4. Cost Metric: PDV . . . . . . . . . . . . . . . . . . . . . . 8 4. Cost Metric: RTT . . . . . . . . . . . . . . . . . . . . . . 8
5. Cost Metric: Packet Loss . . . . . . . . . . . . . . . . . . 9 5. Cost Metric: PDV . . . . . . . . . . . . . . . . . . . . . . 9
6. Cost Metric: Hop Count . . . . . . . . . . . . . . . . . . . 11 6. Cost Metric: Hop Count . . . . . . . . . . . . . . . . . . . 11
7. Cost Metric: Bandwidth . . . . . . . . . . . . . . . . . . . 13 7. Cost Metric: Packet Loss . . . . . . . . . . . . . . . . . . 13
8. Cost Metric: Maximum Bandwidth . . . . . . . . . . . . . . . 14 8. Traffic Engineering Performance Cost Metrics . . . . . . . . 15
9. Cost Metric: Maximum Reservable Bandwidth . . . . . . . . . . 16 8.1. Cost Metric: Link Maximum Reservable Bandwidth . . . . . 16
10. Cost Metric: RTT . . . . . . . . . . . . . . . . . . . . . . 18 8.2. Cost Metric: Link Residue Bandwidth . . . . . . . . . . . 17
11. Cost Metric: Residue Bandwidth . . . . . . . . . . . . . . . 20 8.3. Cost Metric: Link Available Bandwidth . . . . . . . . . . 19
12. Cost Metric: Available Bandwidth . . . . . . . . . . . . . . 22 8.4. Cost Metric: Link Utilized Bandwidth . . . . . . . . . . 21
13. Cost Metric: Utilized Bandwidth . . . . . . . . . . . . . . . 24 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23
14. Security Considerations . . . . . . . . . . . . . . . . . . . 26 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 11.1. Normative References . . . . . . . . . . . . . . . . . . 24
16.1. Normative References . . . . . . . . . . . . . . . . . . 27 11.2. Informative References . . . . . . . . . . . . . . . . . 26
16.2. Informative References . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
Cost Metric is a basic concept in Application-Layer Traffic Cost Metric is a basic concept in Application-Layer Traffic
Optimization (ALTO). It is used in both the Cost Map Service and the Optimization (ALTO). It is used in both the Cost Map Service and the
Endpoint Cost Service. In particular, applications may benefit from Endpoint Cost Service. In particular, applications may benefit from
knowing network performance measured on several Cost Metrics. For knowing network performance measured on several Cost Metrics. For
example, a more delay sensitive application may focus on latency, and example, a more delay sensitive application may focus on latency, and
a more bandwidth-sensitive application may focus on available a more bandwidth-sensitive application may focus on available
bandwidth. bandwidth.
The objective of this document is to introduce 11 new performance This document introduces a set new cost metrics, listed in Table 1,
cost metrics, listed in Table 1, to support the aforementioned to support the aforementioned applications and allow them to
applications and allow applications to determine "where" to connect determine "where" to connect based on network performance criteria.
based on end to end network performance criteria. Hence, this Hence, this document extends the base ALTO protocol [ALTO], which
document extends the base ALTO protocol [ALTO], which defines only a defines only a single cost metric, i.e., the generic "routingcost"
single cost metric, i.e., the generic "routingcost" metric (Sec. 14.2 metric (Sec. 14.2 of ALTO base specification [ALTO]).
of ALTO base specification [ALTO]).
+-----------+--------------+------------------------+ +----------+--------------+---------------------------------------------+
| Namespace | Property | Reference | |Namespace | Property | Reference |
+-----------+--------------+------------------------+ +----------+--------------+---------------------------------------------+
| | owdelay | [RFCxxxx], Section 3 | | | owdelay | See Section 3,[RFC2679] Section 3.6 |
| | pdv | [RFCxxxx], Section 4 | | | rtt | See Section 4,[RFC2681] Section 2.6 |
| | pktloss | [RFCxxxx], Section 5 | | | pdv | See Section 5,[RFC3393] Section 2.6 |
| | hopcount | [RFCxxxx], Section 6 | | | hopcount | See Section 6,[RFC7285] |
| | bandwidth | [RFCxxxx], Section 7 | | | pktloss | See Section 7,[RFC7680] Section 2.6 |
| | maxbw | [RFCxxxx], Section 8 | | | maxresbw | See Section 8.1,[RFC5305] Section 3.5 |
| | maxresbw | [RFCxxxx], Section 9 | | | residbw | See Section 8.2,[RFC7810] Section 4.5 |
| | rtt | [RFCxxxx], Section 10 | | | availbw | See Section 8.3,[RFC7810] Section 4.6 |
| | residbw | [RFCxxxx], Section 11 | | | utilbw | See Section 8.4,[RFC7810 Section 4.7 |
| | availbw | [RFCxxxx], Section 12 | +----------+--------------+---------------------------------------------+
| | utilbw | [RFCxxxx], Section 13 | Table 1.
+-----------+--------------+------------------------+
Table 1.
An ALTO server may provide a subset of the cost metrics documented in The purpose of this draft is to list the metrics likely to be exposed
this document. These cost metrics can be retrieved and aggregated to ALTO Clients, including those already specified in other
from routing protocol or other traffic measurement management tool standardization groups and as such it does not claim novelty on all
(See Figure 1). Note that these cost metrics are optional metrics the specified metrics. Some metrics may have values produced by
and Not all these cost metrics need to be exposed to the application. explicitely specified measurement methods such as those specified in
IPPM, some may be ISP dependent such as those registered in ISIS or
OSPF-TE. In this case, this document will refer to the relevant
specifications.
If some of these cost metrics have privacy concern, the alto server An ALTO server may provide a subset of the cost metrics described in
should not provide them to the client. this document. These cost metrics can be retrieved and aggregated
from routing protocols or other traffic measurement management tools
(See Figure 1). Note that these cost metrics are optional and not
all them need to be exposed to applications. If some are subject to
privacy concerns, the ALTO server should not provide them to the
client.
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+
| Client | | Client | | Client | | Client | | Client | | Client |
+----^---+ +---^----+ +---^----+ +----^---+ +---^----+ +---^----+
| | | | | |
+-----------|-----------+ +-----------|-----------+
NBI |ALTO protocol NBI |ALTO protocol
| |
| |
+--+-----+ retrieve +---------+ +--+-----+ retrieve +---------+
skipping to change at page 4, line 30 skipping to change at page 4, line 35
+--------+ | +---------+ +--------+ | +---------+
| |
| +---------+ | +---------+
| |Management | |Management
---| | ---| |
| Tool | | Tool |
+---------+ +---------+
Figure 1.End to End Path Cost Metrics Exposing Figure 1.End to End Path Cost Metrics Exposing
When an ALTO server supports a cost metric defined in this document, When an ALTO server supports a cost metric defined in this document,
the server SHOULD announce the metric in its IRD. it SHOULD announce this metric in its IRD.
The definitions of a set of cost metrics can allow us to extend the Additionally, further versions of this document may define network
ALTO base protocol (e.g., allowing output and constraints use metric values that stem from both measurements and provider policy as
different cost metrics), but such extensions are not in the scope of for example, many end to end path bandwidth related ALTO metrics.
this document. ALTO may convey such information, not available via 3rd party
measurement tools. Besides, IPPM informational RFC 5136 points the
difficulty to have a unified nomenclature for network capacity
related measurements.
One challenge in describing the metrics is that performance metrics As for the reliability and trust in the exposed metric values,
often depend on configuration parameters. For example, the value of applications will rapidly give up using ALTO-based guidance if they
packet loss rate depends on the measurement interval and varies over feel the exposed information does not preserve their performance
time. To handle this issue, ALTO server may collect data on time level or even degrades it.
periods covering the past, present or only collect data on present
time. The ALTO may further aggregate these data to provide an
abstract and unified view that can be more useful to applications.
To make the ALTO client understand whether the performance data is
past data or present data, the ALTO server needs to expose to the
client the validity period of each performance metric.
Following the ALTO base protocol, this document uses JSON to specify Following the ALTO base protocol, this document uses JSON to specify
the value type of each defined metric. See [RFC4627] for JSON data the value type of each defined metric. See [RFC4627] for JSON data
type specification. type specification.
2. Data sources, computation of defined cost metrics 2. Challenges on data sources and computation of ALTO performance
metrics
The cost metrics described in this document are similar, in that they
may use similar data sources and have similar issues in their
calculation. Hence, instead of specifying such issues for each
metric individually, we specify the common issue in this section.
2.1. Data sources 2.1. Data sources
An ALTO server needs data sources to compute the cost metrics An ALTO server needs data sources to compute the cost metrics
described in this document. This document does not define the exact described in this document. This document does not define the exact
data sources. For example, the ALTO server may use log servers or data sources. For example, the ALTO server may use log servers or
the OAM system as its data source [ALTO-DEPLOYMENT]. In particular, the OAM system as its data source [ALTO-DEPLOYMENT]. In particular,
the cost metrics defined in this document can be computed using the cost metrics defined in this document can be computed using
routing systems as the data sources. Mechanisms defined in routing systems as the data sources. Mechanisms defined in
[RFC3630], [RFC3784], [OSPF-TE], [ISIS-TE], [BGP-LS] and [BGP-PM] [RFC3630], [RFC3784], [OSPF-TE], [ISIS-TE], [BGP-LS] and [BGP-PM]
that allow an ALTO Server to retrieve and derive the necessary that allow an ALTO Server to retrieve and derive the necessary
information to compute the metrics that we described in this information to compute the metrics that we describe in this document.
document.
2.2. Computation of metrics One challenge lies in the data sources originating the ALTO metric
values. The very purpose of ALTO is to guide application traffic
with provider network centric information that may be exposed to ALTO
Clients in the form of network performance metric values. Not all of
them metrics have values produced by standardized measurement methods
or routing protocols. Some of them involve provider-centric policy
considerations. Some of them may describe wireless or cellular
networks. To reliably guide users and applications while preserving
provider privacy, ALTO performance metric values may also add
abstraction to measurements or provide unitless performance scores.
An ALTO server processes measurements from data sources to compute 2.2. Computation of ALTO performance metrics
exposed metrics. It may need performance data processing tasks such
as aggregating the results across multiple systems, removing
outliers, and creating additional statistics.
One specific challenge in deriving the metrics in this document is The metric values exposed by an ALTO server may result from
that these performance metrics depend on some configuration additional processing on measurements from data sources to compute
parameters. For example, the value of packet loss rate depends on exposed metrics. This may invlove data processing tasks such as
the measurement interval and varies over time. If the ALTO server aggregating the results across multiple systems, removing outliers,
uses aforementioned routing protocol based mechanisms as data and creating additional statistics.
sources, then the measurement interval may be preconfigured by the
routing protocol. For example, Section 5 of [ISIS-TE] defines a
default measurement interval of 30 seconds. This document uses the
term Measurement Interval to refer to the measurement interval used
by the data sources. In the [ISIS-TE] case, it is a measurement
interval set by routing protocol. The Measurement Interval(s) of the
data sources can be different from the interval that this document
derives the metric, e.g., the interval used by this document is
multiple of measurement interval of the data sources. Hence, an ALTO
server needs to resolve the mismatch, when it happens.
Another issue of converting from data source measurements to ALTO One challenge in describing the metrics is that performance metrics
exposed metric values is that the measurement results that the ALTO often depend on configuration parameters. For example, the value of
Server retrieves may be defined for only links, and hence, the server packet loss rate depends on the measurement interval and varies over
will need to compose the link metrics to obtain path metrics used in time. To handle this issue, an ALTO server may collect data on time
services such as the Cost Map Service. In this definition, we define periods covering the past and present or only collect data on present
the metrics to be independent of link or path, considering that time. The ALTO server may further aggregate these data to provide an
future ALTO extensions may define link-based services, and hence the abstract and unified view that can be more useful to applications.
defined metrics should still be usable. To make the ALTO client better understand how to use these
performance data, the ALTO server may provide the client with the
validity period of the exposed metric values.
3. Cost Metric: OWDelay Another challenge relates to the availability of end to end path
values for certain metrics. Applications value information relating
to bandwidth availability where as bandwidth related metrics can
often be only measured at the link level. This document specifies a
set of link-level bandwidth related values that may be exposed as
such by an ALTO server. The server may also expose other metrics
derived from their aggregation and having different levels of
endpoint granularity, e.g. link endpoints or session endpoints. The
metric specifications may also expose the utilised aggregation laws.
3. Cost Metric: POWDelay
Metric name: Metric name:
Periodic One Way Delay Periodic One Way Delay
Metric Description: Metric Description:
To specify spatial and temporal aggregated delay of a stream of To specify spatial and temporal aggregated delay of a stream of
packets exchanged between the specified source and destination or packets exchanged between the specified source and destination or
the time that the packet spends to travel from source to the time that the packet spends to travel from source to
destination. The spatial aggregation unit is specified in the destination. The spatial aggregation level is specified in the
query context (e.g., PID to PID, or endpoint to endpoint); and the query context (e.g., PID to PID, or endpoint to endpoint).
temporal unit is specified as the measurement interval in the
query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 8.3 of [I-D.ietf-ippm-initial-registry] for See section 8.3 of [I-D.ietf-ippm-initial-registry] for
Measurement Method. Measurement Method.
Units of Measurement: Units of Measurement:
See section 7.4.4 of [I-D.ietf-ippm-initial-registry] for See section 8.4.3 of [I-D.ietf-ippm-initial-registry] for
Measurement Unit. The unit is expressed in seconds. Measurement Unit. The unit is expressed in seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 8.3.5 of [I-D.ietf-ippm-initial-registry] for See section 8.3.5 of [I-D.ietf-ippm-initial-registry] for
Measurement Timing. Measurement Timing.
Use and Applications: Use and Applications:
This is intended to be a constraint attribute value. A Cost Mode The Metric value Type is a single 'JSONNumber' type value
is encoded as a US-ASCII string. The Metric value Type is a containing a non-negative integer component that may be followed
single 'JSONNumber' type value containing a non-negative integer by an exponent part. The Cost Mode is encoded as a US-ASCII
component that may be followed by an exponent part. string.
This metric could be used as a cost metric constraint attribute This metric could be used as a cost metric constraint attribute
used either together with cost metric attribute 'routingcost' or used either together with cost metric attribute 'routingcost' or
on its own or as a returned cost metric in the response. on its own or as a returned cost metric in the response.
Example 1: Delay value on source-destination endpoint pairs Example 1: Delay value on source-destination endpoint pairs
POST /endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json Accept: application/alto-endpointcost+json,application/alto-error+json
{ {
"cost-type": {"cost-mode" : "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric" : "delay"}, "cost-metric" : "powdelay"},
"endpoints" : { "endpoints" : {
"srcs": [ "ipv4:192.0.2.2" ], "srcs": [ "ipv4:192.0.2.2" ],
"dsts": [ "dsts": [
"ipv4:192.0.2.89", "ipv4:192.0.2.89",
"ipv4:198.51.100.34", "ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd" "ipv6:2000::1:2345:6789:abcd"
] ]
} }
} }
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcost+json Content-Type: application/alto-endpointcost+json
{ {
"meta" :{ "meta" :{
"cost-type": {"cost-mode" : "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric" : "delay" "cost-metric" : "powdelay"
} }
}, },
"endpoint-cost-map" : { "endpoint-cost-map" : {
"ipv4:192.0.2.2": { "ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 10, "ipv4:192.0.2.89" : 10,
"ipv4:198.51.100.34" : 20, "ipv4:198.51.100.34" : 20,
"ipv6:2000::1:2345:6789:abcd" : 30, "ipv6:2000::1:2345:6789:abcd" : 30,
} }
} }
} }
4. Cost Metric: PDV 4. Cost Metric: RTT
Metric name: Metric name:
Pakcet Delay Variation Round Trip Delay
Metric Description: Metric Description:
To specify spatial and temporal aggregated jitter (packet delay To specify spatial and temporal aggregated round trip delay
variation) with respect to the minimum delay observed on the between the specified source and destination or the time that the
stream over the specified source and destination. The spatial packet spends to travel from source to destination and then from
aggregation unit is specified in the query context (e.g., PID to destination to source. The spatial aggregation level is specified
PID, or endpoint to endpoint); and the temporal unit is specified in the query context (e.g., PID to PID, or endpoint to endpoint).
as the measurement interval in the query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 5.3 of [I-D.ietf-ippm-initial-registry] for See section 4.3 of [I-D.ietf-ippm-initial-registry] for
Measurement Method. Measurement Method.
Units of Measurement: Units of Measurement:
See section 5.4.4 of [I-D.ietf-ippm-initial-registry] for See section 4.4.3 of [I-D.ietf-ippm-initial-registry] for
Measurement Unit. The unit is expressed in seconds. Measurement Unit. The unit is expressed in seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 5.3.5 of [I-D.ietf-ippm-initial-registry] for See section 4.3.5 of [I-D.ietf-ippm-initial-registry] for
Measurement Timing. Measurement Timing.
Measurement Timing:Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 2: Delayjitter value on source-destination endpoint pairs Example 7: Round Trip Delay value on source-destination endpoint pairs
POST /endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json Accept: application/alto-endpointcost+json,application/alto-error+json
{ {
"cost-type": {"cost-mode" : "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric" : "delayjitter"}, "cost-metric" : "rtt"},
"endpoints" : { "endpoints" : {
"srcs": [ "ipv4:192.0.2.2" ], "srcs": [ "ipv4:192.0.2.2" ],
"dsts": [ "dsts": [
"ipv4:192.0.2.89", "ipv4:192.0.2.89",
"ipv4:198.51.100.34", "ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd" "ipv6:2000::1:2345:6789:abcd"
] ]
} }
} }
HTTP/1.1 200 OK
Content-Length: TBA HTTP/1.1 200 OK
Content-Type: application/alto-endpointcost+json Content-Length: TBA
{ Content-Type: application/alto-endpointcost+json
"meta": { {
"cost type": { "meta" :{
"cost-mode": "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric":"delayjitter" "cost-metric" : "rtt"
} }
}, },
"endpoint-cost-map": { "endpoint-cost-map" : {
"ipv4:192.0.2.2": { "ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 0 "ipv4:192.0.2.89" : 4,
"ipv4:198.51.100.34" : 1 "ipv4:198.51.100.34" : 3,
"ipv6:2000::1:2345:6789:abcd" : 5 "ipv6:2000::1:2345:6789:abcd" : 2,
}
}
} }
}
}
5. Cost Metric: Packet Loss 5. Cost Metric: PDV
Metric name: Metric name:
Packet loss Packet Delay Variation
Metric Description: Metric Description:
To specify spatial and temporal aggregated packet loss over the To specify spatial and temporal aggregated jitter (packet delay
specified source and destination. The spatial aggregation unit is variation) with respect to the minimum delay observed on the
specified in the query context (e.g., PID to PID, or endpoint to stream over the specified source and destination. The spatial
endpoint); and the temporal unit is specified as the measurement aggregation level is specified in the query context (e.g., PID to
interval in the query context. PID, or endpoint to endpoint).
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. See section 5.3 of [I-D.ietf-ippm-initial-registry] for
Measurement Method.
Units of Measurement: Units of Measurement:
The unit is percentile. See section 5.4.4 of [I-D.ietf-ippm-initial-registry] for
Measurement Unit. The unit is expressed in seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. See section 5.3.5 of [I-D.ietf-ippm-initial-registry] for
Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 3: pktloss value on source-destination endpoint pairs Example 2: Delay jitter value on source-destination endpoint pairs
POST /endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json Accept: application/alto-endpointcost+json,application/alto-error+json
{ {
"cost-type": {"cost-mode" : "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric" : "pktloss"}, "cost-metric" : "delayjitter"},
"endpoints" : { "endpoints" : {
"srcs": [ "ipv4:192.0.2.2" ], "srcs": [ "ipv4:192.0.2.2" ],
"dsts": [ "dsts": [
"ipv4:192.0.2.89", "ipv4:192.0.2.89",
"ipv4:198.51.100.34", "ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd" "ipv6:2000::1:2345:6789:abcd"
] ]
}
} }
}
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcost+json Content-Type: application/alto-endpointcost+json
{ {
"meta": { "meta": {
"cost type": { "cost type": {
"cost-mode": "numerical", "cost-mode": "numerical",
"cost-metric":"pktloss"} "cost-metric":"delayjitter"
} }
}, },
"endpoint-cost-map": { "endpoint-cost-map": {
"ipv4:192.0.2.2": { "ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.89" : 0
"ipv4:198.51.100.34": 1, "ipv4:198.51.100.34" : 1
"ipv6:2000::1:2345:6789:abcd" : 2, "ipv6:2000::1:2345:6789:abcd" : 5
} }
} }
} }
6. Cost Metric: Hop Count 6. Cost Metric: Hop Count
The metric hopcount is mentioned in [ALTO] as an example. This The metric hopcount is mentioned in [ALTO] as an example. This
section further clarifies its properties. section further clarifies its properties.
Metric name: Metric name:
Hop count Hop count
Metric Description: Metric Description:
To specify the number of hops in the path between the source To specify the number of hops in the path between the source
endpoint and the destination endpoint. The hop count is a basic endpoint and the destination endpoint. The hop count is a basic
measurement of distance in a network and can be exposed as Router measurement of distance in a network and can be exposed as Router
Hops, IP hops or other hops in direct relation to the routing Hops, IP hops or other hops in direct relation to the routing
prtocols originating this information. it might also result from protocols originating this information. It might also result from
the aggregation of such information. the aggregation of such information.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. See section 2.2, Computation of metrics.
Units of Measurement: Units of Measurement:
The unit is integer number. The unit is integer number.
skipping to change at page 13, line 43 skipping to change at page 13, line 44
}, },
"endpoint-cost-map": { "endpoint-cost-map": {
"ipv4:192.0.2.2": { "ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 5, "ipv4:192.0.2.89" : 5,
"ipv4:198.51.100.34": 3, "ipv4:198.51.100.34": 3,
"ipv6:2000::1:2345:6789:abcd" : 2, "ipv6:2000::1:2345:6789:abcd" : 2,
} }
} }
} }
7. Cost Metric: Bandwidth 7. Cost Metric: Packet Loss
Metric name:
Bandwidth
Metric Description:
To specify spatial and temporal aggregated bandwidth over the
specified source and destination. The spatial aggregation unit is
specified in the query context (e.g., PID to PID, or endhost to
endhost); and the temporal unit is specified as the measurement
interval in the query context.
This is just a definition of a class of cost metric 'bandwidth'.
The use of this cost metric is always in conjunction with what it
represents, which could be Max Bandwidth (maxbw), Residual
Bandwidth (residuebw) etc.
Method of Measurement or Calculation:
See section 2.2, Computation of metrics.
Units of Measurement:
The units are bytes per second.
Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources.
Measurement Timing:
See section 2.1, second paragraph for Measurement Timing.
Use and Applications:
See section 3 for use and application.
8. Cost Metric: Maximum Bandwidth
Metric name: Metric name:
Maximum Bandwidth Packet loss
Metric Description: Metric Description:
To specify spatial and temporal maximum bandwidth over the To specify spatial and temporal aggregated packet loss over the
specified source and destination. The values correspond to the specified source and destination. The spatial aggregation level
maximum bandwidth that can be used (motivated from RFC 3630 Sec. is specified in the query context (e.g., PID to PID, or endpoint
2.5.6.). The spatial aggregation unit is specified in the query to endpoint).
context (e.g., PID to PID, or endhost to endhost); and the
temporal unit is specified as the measurement interval in the
query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. See section 2.6 of [RFC7680] for Measurement Method.
Units of Measurement: Units of Measurement:
See definition for the Bandwidth Cost Metric. The unit is percentile.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. See section 2 and section3 of [RFC7680] for Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 5: maxbw value on source-destination endpoint pairs Example 3: pktloss value on source-destination endpoint pairs
POST/ endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json Accept: application/alto-endpointcost+json,application/alto-error+json
{ {
"cost-type": { "cost-mode": "numerical", "cost-type": {"cost-mode" : "numerical",
"cost-metric": "maxbw"}, "cost-metric" : "pktloss"},
"endpoints": { "endpoints" : {
"srcs": [ "ipv4 : 192.0.2.2" ], "srcs": [ "ipv4:192.0.2.2" ],
"dsts": [ "dsts": [
"ipv4:192.0.2.89", "ipv4:192.0.2.89",
"ipv4:198.51.100.34", "ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd" "ipv6:2000::1:2345:6789:abcd"
] ]
} }
} }
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcost+json Content-Type: application/alto-endpointcost+json
{ {
"meta": { "meta": {
"cost-type": { "cost type": {
"cost-mode": "numerical", "cost-mode": "numerical",
"cost-metric": "maxbw" "cost-metric":"pktloss"}
} }
}, },
"endpoint-cost-map": { "endpoint-cost-map": {
"ipv4:192.0.2.2": { "ipv4:192.0.2.2": {
"ipv4:192.0.2.89": 0, "ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34" : 2000, "ipv4:198.51.100.34": 1,
"ipv6:2000::1:2345:6789:abcd": 5000, "ipv6:2000::1:2345:6789:abcd" : 2,
} }
} }
} }
9. Cost Metric: Maximum Reservable Bandwidth 8. Traffic Engineering Performance Cost Metrics
This section introduces ALTO network performance metrics that may be
aggregated from network metrics measured on links and specified in
other documents. In particular, the bandwidth related metrics
specified in this section are only available through link level
measurements. For some of these metrics, the ALTO Server may further
expose aggregated values while specifying the aggregation laws.
8.1. Cost Metric: Link Maximum Reservable Bandwidth
Metric name: Metric name:
Maximum Reservable Bandwidth Maximum Reservable Bandwidth
Metric Description: Metric Description:
To specify spatial and temporal maximum reservable bandwidth over To specify spatial and temporal maximum reservable bandwidth over
the specified source and destination. The value is corresponding the specified source and destination. The value is corresponding
to the maximum bandwidth that can be reserved (motivated from RFC to the maximum bandwidth that can be reserved (motivated from RFC
3630 Sec. 2.5.7.). The spatial aggregation unit is specified in 3630 Sec. 2.5.7.). The spatial aggregation unit is specified in
the query context (e.g., PID to PID, or endpoint to endpoint); and the query context (e.g., PID to PID, or endpoint to endpoint).
the temporal unit is specified as the measurement interval in the
query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. Maximum Reserveable Bandwidth is the bandwidth measured between
two directly connected IS-IS neighbors or OSPF neighbor, See
section 3.5 of [RFC5305] for Measurement Method.
Units of Measurement: Units of Measurement:
See definition of the Bandwidth Cost Metric. The unit of measurement is byte per seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. See section 3.5 of [RFC5305] and section 5 of [RFC7810] for
Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 6: maxresbw value on source-destination endpoint pairs Example 6: maxresbw value on source-destination endpoint pairs
POST/ endpointcost/lookup HTTP/1.1 POST/ endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
skipping to change at page 18, line 44 skipping to change at page 17, line 44
}, },
" endpoint-cost-map": { " endpoint-cost-map": {
"ipv4:192.0.2.2" { "ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34": 2000, "ipv4:198.51.100.34": 2000,
"ipv6:2000::1:2345:6789:abcd": 5000, "ipv6:2000::1:2345:6789:abcd": 5000,
} }
} }
} }
10. Cost Metric: RTT 8.2. Cost Metric: Link Residue Bandwidth
Metric name:
Round Trip Delay
Metric Description:
To specify spatial and temporal aggregated round trip delay
between the specified source and destination or the time that the
packet spends to travel from source to destination and then from
destination to source. The spatial aggregation unit is specified
in the query context (e.g., PID to PID, or endpoint to endpoint);
and the temporal unit is specified as the measurement interval in
the query context.
Method of Measurement or Calculation:
See section 2.2, Computation of metrics.
Units of Measurement:
See definition for the bandwidth Cost Metric.
Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources.
Measurement Timing:
See section 2.1, second paragraph for Measurement Timing.
Use and Applications:
See section 3 for use and application.
Example 7: Round Trip Delay value on source-destination endpoint pairs
POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com
Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json
{
"cost-type": {"cost-mode" : "numerical",
"cost-metric" : "rtt"},
"endpoints" : {
"srcs": [ "ipv4:192.0.2.2" ],
"dsts": [
"ipv4:192.0.2.89",
"ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd"
]
}
}
HTTP/1.1 200 OK
Content-Length: TBA
Content-Type: application/alto-endpointcost+json
{
"meta" :{
"cost-type": {"cost-mode" : "numerical",
"cost-metric" : "rtt"
}
},
"endpoint-cost-map" : {
"ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 4,
"ipv4:198.51.100.34" : 3,
"ipv6:2000::1:2345:6789:abcd" : 2,
}
}
}
11. Cost Metric: Residue Bandwidth
Metric name: Metric name:
Residue Bandwidth Residue Bandwidth
Metric Description: Metric Description:
To specify spatial and temporal residual bandwidth over the To specify spatial and temporal residual bandwidth over the
specified source and destination. The value is calculated by specified source and destination. The value is calculated by
subtracting tunnel reservations from Maximum Bandwidth (motivated subtracting tunnel reservations from Maximum Bandwidth (motivated
from [RFC7810], Sec.4.5.). The spatial aggregation unit is from [RFC7810], Sec.4.5.). The spatial aggregation unit is
specified in the query context (e.g., PID to PID, or endpoint to specified in the query context (e.g., PID to PID, or endpoint to
endpoint); and the temporal unit is specified as the measurement endpoint).
interval in the query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. Residue Bandwidth is the Unidirectional Residue bandwidth measured
between two directly connected IS-IS neighbors or OSPF neighbor,
See section 4.5 of [RFC7810] for Measurement Method.
Units of Measurement: Units of Measurement:
See definition of the general Bandwidth. The unit of measurement is byte per seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. See section 5 of [RFC7810] for Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 8: residuebw value on source-destination endpoint pairs Example 8: residuebw value on source-destination endpoint pairs
POST/ endpointcost/lookup HTTP/1.1 POST/ endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
skipping to change at page 22, line 45 skipping to change at page 19, line 45
}, },
"endpoint-cost-map" { "endpoint-cost-map" {
"ipv4:192.0.2.2" { "ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34": 2000, "ipv4:198.51.100.34": 2000,
"ipv6:2000::1:2345:6789:abcd": 5000, "ipv6:2000::1:2345:6789:abcd": 5000,
} }
} }
} }
12. Cost Metric: Available Bandwidth 8.3. Cost Metric: Link Available Bandwidth
Metric name: Metric name:
Available Bandwidth Available Bandwidth
Metric Description: Metric Description:
To specify spatial and temporal availaible bandwidth over the To specify spatial and temporal availaible bandwidth over the
specified source and destination. The value is calculated by specified source and destination. The value is calculated by
subtracting the measured bandwidth used for the actual forwarding subtracting the measured bandwidth used for the actual forwarding
of best effort traffic from Residue Bandwidth (motivated from of best effort traffic from Residue Bandwidth (motivated from
[RFC7810], Sec.4.6.). The spatial aggregation unit is specified [RFC7810], Sec.4.6.). The spatial aggregation level is specified
in the query context (e.g., PID to PID, or endpoint to endpoint); in the query context (e.g., PID to PID, or endpoint to endpoint).
and the temporal unit is specified as the measurement interval in
the query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. Available bandwidth is the Unidirectional Available bandwidth
measured between two directly connected IS-IS neighbors or OSPF
neighbor, See section 4.6 of [RFC7810] for Measurement Method.
Units of Measurement: Units of Measurement:
See definition of the general Bandwidth. The unit of measurement is byte per seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. See section 5 of [RFC7810] for Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application. Besides, knowledge about
available bandwidth is essential for applications to distribute or
schedule their transmissions. The example below illustrates how
this metric is provided in the form of an ALTO calendar, as
specified in [XXXX] to help deciding "where" and "when" to
transmit.
Example 9: availbw value on source-destination endpoint pairs Example 9: availbw value on source-destination endpoint pairs
This example assumes that the ALTO Server provides the values for
metric "availbw" in the form of an ALTO calendar and declares it
in its IRD.
POST /endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcostparams+json Content-Type: application/alto-endpointcostparams+json
Accept: application/alto-endpointcost+json,application/alto-error+json Accept: application/alto-endpointcost+json,application/alto-error+json
{ {
"cost-type": { "cost-mode": "numeric", "cost-type": { "cost-mode": "numerical",
"cost-metric": "availbw"}, "cost-metric": "availbw"},
"endpoints": { "calendared" : [true],
"endpoints": {
"srcs": [ "ipv4 : 192.0.2.2" ], "srcs": [ "ipv4 : 192.0.2.2" ],
"dsts": [ "dsts": [
"ipv4:192.0.2.89", "ipv4:192.0.2.89",
"ipv4:198.51.100.34", "ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd" "ipv6:2000::1:2345:6789:abcd"
] ]
} }
} }
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: TBA Content-Length: TBA
Content-Type: application/alto-endpointcost+json Content-Type: application/alto-endpointcost+json
{ {
"meta": { "meta": {
"cost-type": { "cost-type": {
"cost-mode": "numeric", "cost-mode": "numerical", "cost-metric": "availbw"
"cost-metric": "availbw"
} }
"calendar-response-attributes" : [
"calendar-start-time" : Tue, 1 Mar 2017 13:00:00 GMT,
"time-interval-size" : "1 hour",
"numb-intervals" : 8
]
}, },
"endpoint-cost-map": { "endpoint-cost-map": {
"ipv4:192.0.2.2" { "ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : [6,5,7,8,4,10,7,6], "ipv4:192.0.2.89" : [6,5,7,8,4,10,7,6],
"ipv4:198.51.100.34" : [7,4,6,8,5,9,6,7], "ipv4:198.51.100.34" : [7,4,6,8,5,9,6,7],
"ipv6:2000::1:2345:6789:abcd" : [7,6,8,5,7,9,6,8], "ipv6:2000::1:2345:6789:abcd" : [7,6,8,5,7,9,6,8],
} }
} }
} }
13. Cost Metric: Utilized Bandwidth 8.4. Cost Metric: Link Utilized Bandwidth
Metric name: Metric name:
Utilized Bandwidth Utilized Bandwidth
Metric Description: Metric Description:
To specify spatial and temporal utilized bandwidth over the To specify spatial and temporal utilized bandwidth over the
specified source and destination. The value is corresponding to specified source and destination. The value is corresponding to
the actual measured bandwidth used for all traffic (motivated from the actual measured bandwidth used for all traffic (motivated from
[RFC7810], Sec.4.7.). The spatial aggregation unit is specified [RFC7810], Sec.4.7.). The spatial aggregation level is specified
in the query context (e.g., PID to PID, or endpoint to endpoint); in the query context (e.g., PID to PID, or endpoint to endpoint).
and the temporal unit is specified as the measurement interval in
the query context.
Method of Measurement or Calculation: Method of Measurement or Calculation:
See section 2.2, Computation of metrics. Link Utilizated bandwidth is Unidirectional utilization bandwidth
measured between two directly connected IS-IS neighbors or OSPF
neighbor, See section 4.7 of [RFC7810] for Measurement Method.
Units of Measurement: Units of Measurement:
See definition of the general Bandwidth. The unit of measurement is byte per seconds.
Measurement Point(s) with Potential Measurement Domain: Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2.1, second paragraph for Measurement Timing. Link Utilized bandwidth is Unidirectional utilization bandwidth
measured between two directly connected IS-IS neighbors or OSPF
neighbor, See section 5 of [RFC7810] for Measurement Timing.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 10: utilbw value on source-destination endpoint pairs Example 10: utilbw value on source-destination endpoint pairs
POST /endpointcost/lookup HTTP/1.1 POST /endpointcost/lookup HTTP/1.1
Host: alto.example.com Host: alto.example.com
Content-Length: TBA Content-Length: TBA
skipping to change at page 26, line 45 skipping to change at page 23, line 45
}, },
"endpoint-cost-map": { "endpoint-cost-map": {
"ipv4:192.0.2.2" { "ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34" : 2000, "ipv4:198.51.100.34" : 2000,
"ipv6:2000::1:2345:6789:abcd" : 5000, "ipv6:2000::1:2345:6789:abcd" : 5000,
} }
} }
} }
14. Security Considerations 9. Security Considerations
The properties defined in this document present no security The properties defined in this document present no security
considerations beyond those in Section 15 of the base ALTO considerations beyond those in Section 15 of the base ALTO
specification [ALTO]. specification [ALTO].
However concerns addressed in Sections "15.1 Authenticity and However concerns addressed in Sections "15.1 Authenticity and
Integrity of ALTO Information", "15.2 Potential Undesirable Guidance Integrity of ALTO Information", "15.2 Potential Undesirable Guidance
from Authenticated ALTO Information" and "15.3 Confidentiality of from Authenticated ALTO Information" and "15.3 Confidentiality of
ALTO Information" remain of utmost importance. Indeed, TE ALTO Information" remain of utmost importance. Indeed, TE
performance is a highly sensitive ISP information and sharing TE performance is a highly sensitive ISP information and sharing TE
metric values in numerical mode requires full mutual confidence metric values in numerical mode requires full mutual confidence
between the entities managing the ALTO Server and Client. Numerical between the entities managing the ALTO Server and Client. Numerical
TE performance information will most likely be distributed by ALTO TE performance information will most likely be distributed by ALTO
Servers to Clients under strict and formal mutual trust agreements. Servers to Clients under strict and formal mutual trust agreements.
One the other hand, ALTO Clients must be cognizant on the risks On the other hand, ALTO Clients must be cognizant on the risks
attached to such information that they would have acquired outside attached to such information that they would have acquired outside
formal conditions of mutual trust. formal conditions of mutual trust.
15. IANA Considerations 10. IANA Considerations
IANA has added the following entries to the ALTO cost map Properties IANA has created and now maintains the "ALTO Cost Metric Registry",
registry, defined in Section 3 of [RFCXXX]. listed in Section 14.2, Table 3 of [RFC7285]. This registry is
located at <http://www.iana.org/assignments/alto-protocol/alto-
protocol.xhtml#cost-metrics>. This document requests to add the
following entries to "ALTO Cost Meric Registry".
+-----------+--------------+------------------------+ +----------+--------------+---------------------------------------------+
| Namespace | Property | Reference | |Namespace | Property | Reference |
+-----------+--------------+------------------------+ +----------+--------------+---------------------------------------------+
| | owdelay | [RFCxxxx], Section 3 | | | owdelay | [thisdraft] Section 3,[RFC2679] Section 3.6 |
| | pdv | [RFCxxxx], Section 4 | | | rtt | [thisdraft] Section 4,[RFC2681],Section 2.6 |
| | pktloss | [RFCxxxx], Section 5 | | | pdv | [thisdraft] Section 5,[RFC3393],Section 2.6 |
| | hopcount | [RFCxxxx], Section 6 | | | hopcount | [thisdraft] Section 6,[RFC7285] |
| | bandwidth | [RFCxxxx], Section 7 | | | pktloss | [thisdraft] Section 7,[RFC7680],Section 2.6 |
| | maxbw | [RFCxxxx], Section 8 | | | maxresbw | [thisdraft] Section 8.1,[RFC5305],Section 3.5|
| | maxresbw | [RFCxxxx] Section 9 | | | residbw | [thisdraft] Section 8.2,[RFC7810],Section 4.5|
| | rtt | [RFCxxxx], Section 10 | | | availbw | [thisdraft] Section 8.3,[RFC7810],Section 4.6|
| | residbw | [RFCxxxx], Section 11 | | | utilbw | [thisdraft] Section 8.4,[RFC7810,Section4.7] |
| | availbw | [RFCxxxx], Section 12 | +----------+--------------+---------------------------------------------+
| | utilbw | [RFCxxxx], Section 13 |
+-----------+--------------+------------------------+
16. References 11. References
16.1. Normative References 11.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Previdi, S., Wu, Q., Gredler, H., Ray, S., Previdi, S., Wu, Q., Gredler, H., Ray, S.,
jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg, jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg,
"BGP-LS Advertisement of IGP Traffic Engineering "BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm- Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-03 (work in progress), May 2016. bgp-04 (work in progress), October 2016.
[I-D.ietf-ippm-initial-registry] [I-D.ietf-ippm-initial-registry]
Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza, Morton, A., Bagnulo, M., Eardley, P., and K. D'Souza,
"Initial Performance Metric Registry Entries", draft-ietf- "Initial Performance Metric Registry Entries", draft-ietf-
ippm-initial-registry-01 (work in progress), July 2016. ippm-initial-registry-02 (work in progress), October 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,
September 1999, <http://www.rfc-editor.org/info/rfc2679>.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
September 1999, <http://www.rfc-editor.org/info/rfc2681>.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393,
DOI 10.17487/RFC3393, November 2002,
<http://www.rfc-editor.org/info/rfc3393>.
[RFC4627] Crockford, D., "The application/json Media Type for [RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, JavaScript Object Notation (JSON)", RFC 4627,
DOI 10.17487/RFC4627, July 2006, DOI 10.17487/RFC4627, July 2006,
<http://www.rfc-editor.org/info/rfc4627>. <http://www.rfc-editor.org/info/rfc4627>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <http://www.rfc-editor.org/info/rfc5234>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, October
2008, <http://www.rfc-editor.org/info/rfc5305>.
[RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S., [RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S.,
Previdi, S., Roome, W., Shalunov, S., and R. Woundy, Previdi, S., Roome, W., Shalunov, S., and R. Woundy,
"Application-Layer Traffic Optimization (ALTO) Protocol", "Application-Layer Traffic Optimization (ALTO) Protocol",
RFC 7285, DOI 10.17487/RFC7285, September 2014, RFC 7285, DOI 10.17487/RFC7285, September 2014,
<http://www.rfc-editor.org/info/rfc7285>. <http://www.rfc-editor.org/info/rfc7285>.
[RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
Previdi, "OSPF Traffic Engineering (TE) Metric Previdi, "OSPF Traffic Engineering (TE) Metric
Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
<http://www.rfc-editor.org/info/rfc7471>. <http://www.rfc-editor.org/info/rfc7471>.
[RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Loss Metric for IP Performance Metrics
(IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January
2016, <http://www.rfc-editor.org/info/rfc7680>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<http://www.rfc-editor.org/info/rfc7752>. <http://www.rfc-editor.org/info/rfc7752>.
[RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and [RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and
Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions",
RFC 7810, DOI 10.17487/RFC7810, May 2016, RFC 7810, DOI 10.17487/RFC7810, May 2016,
<http://www.rfc-editor.org/info/rfc7810>. <http://www.rfc-editor.org/info/rfc7810>.
16.2. Informative References 11.2. Informative References
[I-D.ietf-alto-deployments] [I-D.ietf-alto-deployments]
Stiemerling, M., Kiesel, S., Scharf, M., Seidel, H., and Stiemerling, M., Kiesel, S., Scharf, M., Seidel, H., and
S. Previdi, "ALTO Deployment Considerations", draft-ietf- S. Previdi, "ALTO Deployment Considerations", draft-ietf-
alto-deployments-16 (work in progress), July 2016. alto-deployments-16 (work in progress), July 2016.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, July 2011. Development", RFC 6390, July 2011.
Authors' Addresses Authors' Addresses
 End of changes. 108 change blocks. 
422 lines changed or deleted 363 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/