draft-ietf-alto-performance-metrics-02.txt   draft-ietf-alto-performance-metrics-03.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: January 3, 2018 Yale University Expires: June 25, 2018 Yale University
Y. Lee Y. Lee
D. Dhody D. Dhody
Huawei Huawei
S. Randriamasy S. Randriamasy
Nokia Bell Labs Nokia Bell Labs
July 2, 2017 December 22, 2017
ALTO Performance Cost Metrics ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-02 draft-ietf-alto-performance-metrics-03
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. Endpoint Cost Service.
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 offer example, a Resource Consumer may prefer Resource Providers that offer
a low delay delivery to the Resource Consumer. However the base ALTO a low delay delivery to the Resource Consumer. However the base ALTO
skipping to change at page 2, line 13 skipping to change at page 2, line 13
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.
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 https://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 January 3, 2018. This Internet-Draft will expire on June 25, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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 (https://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. Challenges on data sources and computation of ALTO 2. Challenges on data sources and computation of ALTO
performance metrics . . . . . . . . . . . . . . . . . . . . . 5 performance metrics . . . . . . . . . . . . . . . . . . . . . 5
2.1. Data sources . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Data sources Challenge . . . . . . . . . . . . . . . . . 5
2.2. Computation of ALTO performance metrics . . . . . . . . . 5 2.2. ALTO performance metrics Computation Challenges . . . . . 5
2.2.1. Configuration Parameters Challenge . . . . . . . . . 5
2.2.2. Availability of end to end path values Challenge . . 6
3. Cost Metric: POWDelay . . . . . . . . . . . . . . . . . . . . 6 3. Cost Metric: POWDelay . . . . . . . . . . . . . . . . . . . . 6
4. Cost Metric: RTT . . . . . . . . . . . . . . . . . . . . . . 8 4. Cost Metric: RTT . . . . . . . . . . . . . . . . . . . . . . 8
5. Cost Metric: PDV . . . . . . . . . . . . . . . . . . . . . . 10 5. Cost Metric: PDV . . . . . . . . . . . . . . . . . . . . . . 10
6. Cost Metric: Hop Count . . . . . . . . . . . . . . . . . . . 12 6. Cost Metric: Hop Count . . . . . . . . . . . . . . . . . . . 12
7. Cost Metric: Packet Loss . . . . . . . . . . . . . . . . . . 14 7. Cost Metric: Packet Loss . . . . . . . . . . . . . . . . . . 14
8. Traffic Engineering Performance Cost Metrics . . . . . . . . 16 8. Traffic Engineering Performance Cost Metrics . . . . . . . . 16
8.1. Cost Metric: Link Maximum Reservable Bandwidth . . . . . 17 8.1. Cost Metric: Link Maximum Reservable Bandwidth . . . . . 17
8.2. Cost Metric: Link Residue Bandwidth . . . . . . . . . . . 18 8.2. Cost Metric: Link Residue Bandwidth . . . . . . . . . . . 18
8.3. Cost Metric: Link Available Bandwidth . . . . . . . . . . 20 8.3. Cost Metric: Link Available Bandwidth . . . . . . . . . . 20
8.4. Cost Metric: Link Utilized Bandwidth . . . . . . . . . . 22 8.4. Cost Metric: Link Utilized Bandwidth . . . . . . . . . . 23
9. Security Considerations . . . . . . . . . . . . . . . . . . . 24 9. Security Considerations . . . . . . . . . . . . . . . . . . . 25
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
11.1. Normative References . . . . . . . . . . . . . . . . . . 25 11.1. Normative References . . . . . . . . . . . . . . . . . . 26
11.2. Informative References . . . . . . . . . . . . . . . . . 27 11.2. Informative References . . . . . . . . . . . . . . . . . 27
Appendix A. Open Issue List . . . . . . . . . . . . . . . . . . 27 Appendix A. Open Issue List . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
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.
skipping to change at page 3, line 41 skipping to change at page 3, line 43
|Namespace | Property | Reference | |Namespace | Property | Reference |
+----------+--------------+---------------------------------------------+ +----------+--------------+---------------------------------------------+
| | owdelay | See Section 3,[RFC2679] Section 3.6 | | | owdelay | See Section 3,[RFC2679] Section 3.6 |
| | rtt | See Section 4,[RFC2681] Section 2.6 | | | rtt | See Section 4,[RFC2681] Section 2.6 |
| | pdv | See Section 5,[RFC3393] Section 2.6 | | | pdv | See Section 5,[RFC3393] Section 2.6 |
| | hopcount | See Section 6,[RFC7285] | | | hopcount | See Section 6,[RFC7285] |
| | pktloss | See Section 7,[RFC7680] Section 2.6 | | | pktloss | See Section 7,[RFC7680] Section 2.6 |
| | maxresbw | See Section 8.1,[RFC5305] Section 3.5 | | | maxresbw | See Section 8.1,[RFC5305] Section 3.5 |
| | residbw | See Section 8.2,[RFC7810] Section 4.5 | | | residbw | See Section 8.2,[RFC7810] Section 4.5 |
| | availbw | See Section 8.3,[RFC7810] Section 4.6 | | | availbw | See Section 8.3,[RFC7810] Section 4.6 |
| | utilbw | See Section 8.4,[RFC7810 Section 4.7 | | | utilbw | See Section 8.4,[RFC7810] Section 4.7 |
+----------+--------------+---------------------------------------------+ +----------+--------------+---------------------------------------------+
Table 1. Table 1.
The purpose of this draft is to list the metrics likely to be exposed The purpose of this draft is to list the metrics likely to be exposed
to ALTO Clients, including those already specified in other to ALTO Clients, including those already specified in other
standardization groups and as such it does not claim novelty on all standardization groups and as such it does not claim novelty on all
the specified metrics. Some metrics may have values produced by the specified metrics. Some metrics may have values produced by
explicitly specified measurement methods such as those specified in standard measurement methods such as those specified in IPPM, some
IPPM, some may be ISP dependent such as those registered in ISIS or may be ISP dependent such as those registered in ISIS or OSPF-TE. In
OSPF-TE. In this case, this document will refer to the relevant this case, this document will refer to the relevant specifications.
specifications.
An ALTO server may provide a subset of the cost metrics described in An ALTO server may provide a subset of the cost metrics described in
this document. These cost metrics can be retrieved and aggregated this document. These cost metrics can be retrieved and aggregated
from routing protocols or other traffic measurement management tools from routing protocols or other traffic measurement management tools
(See Figure 1). Note that these cost metrics are optional and not (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 all them need to be exposed to applications. For example, those that
privacy concerns, the ALTO server should not provide them to the are subject to privacy concerns should not be provided to
client. unauthorized ALTO clients.
+--------+ +--------+ +--------+ +--------+ +--------+ +--------+
| Client | | Client | | Client | | Client | | Client | | Client |
+----^---+ +---^----+ +---^----+ +----^---+ +---^----+ +---^----+
| | | | | |
+-----------|-----------+ +-----------|-----------+
NBI |ALTO protocol NBI |ALTO protocol
| |
| |
+--+-----+ retrieve +---------+ +--+-----+ retrieval +---------+
| ALTO |<----------------| Routing | | ALTO |<----------------| Routing |
| Server | and aggregation| | | Server | and aggregation| |
| |<-------------+ | Protocol| | |<-------------+ | Protocol|
+--------+ | +---------+ +--------+ | +---------+
| |
| +---------+ | +---------+
| |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,
it SHOULD announce this metric in its IRD. it MUST announce this metric in its IRD.
Additionally, further versions of this document may define network Additionally, future versions of this document may define network
metric values that stem from both measurements and provider policies metric values that stem from both measurements and provider policies
as for example, many end-to-end path bandwidth related ALTO metrics. such as many metrics related to end-to-end path bandwidth.
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.
As for the reliability and trust in the exposed metric values, As for the reliability and trust in the exposed metric values,
applications will rapidly give up using ALTO-based guidance if they applications SHOULD rapidly give up using ALTO-based guidance if they
feel the exposed information does not preserve their performance feel the exposed information does not preserve their performance
level or even degrades it. level or even degrades it.
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. Challenges on data sources and computation of ALTO performance 2. Challenges on data sources and computation of ALTO performance
metrics metrics
2.1. Data sources 2.1. Data sources Challenge
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 describe in this document. information to compute the metrics that we describe in this document.
One challenge lies in the data sources originating the ALTO metric One challenge lies in the data sources originating the ALTO metric
values. The very purpose of ALTO is to guide application traffic values. The very important purpose of ALTO is to guide application
with provider network centric information that may be exposed to ALTO traffic with provider network centric information that may be exposed
Clients in the form of network performance metric values. Not all of to ALTO Clients in the form of network performance metric values.
these metrics have values produced by standardized measurement Not all of these metrics have values produced by standardized
methods or routing protocols. Some of them involve provider-centric measurement methods or routing protocols. Some of them involve
policy considerations. Some of them may describe wireless or provider-centric policy considerations. Some of them may describe
cellular networks. To reliably guide users and applications while wireless or cellular networks. To reliably guide users and
preserving provider privacy, ALTO performance metric values may also applications while preserving provider privacy, ALTO performance
add abstraction to measurements or provide unitless performance metric values may also add abstraction to measurements or provide
scores. unitless performance scores.
2.2. Computation of ALTO performance metrics 2.2. ALTO performance metrics Computation Challenges
The metric values exposed by an ALTO server may result from The metric values exposed by an ALTO server may result from
additional processing on measurements from data sources to compute additional processing on measurements from data sources to compute
exposed metrics. This may involve data processing tasks such as exposed metrics. This may involve data processing tasks such as
aggregating the results across multiple systems, removing outliers, aggregating the results across multiple systems, removing outliers,
and creating additional statistics. and creating additional statistics. There are two challenges on
computation of ALTO performance metrics.
One challenge in describing the metrics is that performance metrics 2.2.1. Configuration Parameters Challenge
often depend on configuration parameters. For example, the value of
packet loss rate depends on the measurement interval and varies over
time. To handle this issue, an ALTO server may collect data on time
periods covering the previous and current time or only collect data
on present time. The ALTO server may further aggregate these data to
provide an abstract and unified view that can be more useful to
applications. 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.
Another challenge relates to the availability of end-to-end path Performance metrics often depend on configuration parameters. For
values for certain metrics. Applications value information relating example, the value of packet loss rate depends on the measurement
to bandwidth availability where as bandwidth related metrics can interval and varies over time. To handle this issue, an ALTO server
often be only measured at the link level. This document specifies a may collect data on time periods covering the previous and current
set of link-level bandwidth related values that may be exposed as time or only collect data on present time. The ALTO server may
such by an ALTO server. The server may also expose other metrics further aggregate these data to provide an abstract and unified view
derived from their aggregation and having different levels of that can be more useful to applications. To make the ALTO client
endpoint granularity, e.g. link endpoints or session endpoints. The better understand how to use these performance data, the ALTO server
metric specifications may also expose the utilised aggregation laws. may provide the client with the validity period of the exposed metric
values.
2.2.2. Availability of end to end path values Challenge
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 utilized aggregation laws.
3. Cost Metric: POWDelay 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
skipping to change at page 8, line 25 skipping to change at page 8, line 4
"cost-metric" : "powdelay"}, "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" : "powdelay"
"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: RTT 4. Cost Metric: RTT
Metric name: Metric name:
Round Trip Delay Round Trip Delay
Metric Description: Metric Description:
To specify spatial and temporal aggregated round trip delay To specify spatial and temporal aggregated round trip delay
skipping to change at page 10, line 5 skipping to change at page 9, line 16
Measurement Timing: Measurement Timing:
See section 4.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.
Use and Applications: Use and Applications:
See section 3 for use and application. See section 3 for use and application.
Example 7: Round Trip Delay value on source-destination endpoint pairs Example 2: 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" : "rtt"}, "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
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" : "rtt"
"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,
}
} }
}, }
"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,
}
}
}
5. Cost Metric: PDV 5. Cost Metric: PDV
Metric name: Metric name:
Packet Delay Variation Packet Delay Variation
Metric Description: Metric Description:
To specify spatial and temporal aggregated jitter (packet delay To specify spatial and temporal aggregated jitter (packet delay
skipping to change at page 12, line 5 skipping to change at page 11, line 16
Measurement Timing: Measurement Timing:
See section 5.3.5 of [I-D.ietf-ippm-initial-registry] for See section 5.3.5 of [I-D.ietf-ippm-initial-registry] for
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: Delay jitter value on source-destination endpoint pairs Example 3: Delay jitter 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" : "delayjitter"},
"endpoints" : {
"srcs": [ "ipv4:192.0.2.2" ],
"dsts": [
"ipv4:192.0.2.89",
"ipv4:198.51.100.34",
"ipv6:2000::1:2345:6789:abcd"
]
}
}
Example 3: 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" : "delayjitter"}, "cost-metric" : "delayjitter"},
skipping to change at page 14, line 25 skipping to change at page 14, line 25
"cost-metric" : "hopcount"}, "cost-metric" : "hopcount"},
"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-metric":"hopcount"} "cost-mode": "numerical",
} "cost-metric":"hopcount"}
}, }
"endpoint-cost-map": { },
"ipv4:192.0.2.2": { "endpoint-cost-map": {
"ipv4:192.0.2.89" : 5, "ipv4:192.0.2.2": {
"ipv4:198.51.100.34": 3, "ipv4:192.0.2.89" : 5,
"ipv6:2000::1:2345:6789:abcd" : 2, "ipv4:198.51.100.34": 3,
} "ipv6:2000::1:2345:6789:abcd" : 2,
} }
} }
}
7. Cost Metric: Packet Loss 7. Cost Metric: Packet Loss
Metric name: Metric name:
Packet loss Packet loss
Metric Description: Metric Description:
To specify spatial and temporal aggregated packet loss over the To specify spatial and temporal aggregated packet loss over the
skipping to change at page 16, line 5 skipping to change at page 16, line 5
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 2 and section3 of [RFC7680] 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 3: pktloss value on source-destination endpoint pairs Example 5: 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" : "pktloss"}, "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
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-metric":"pktloss"} "cost-mode": "numerical",
} "cost-metric":"pktloss"}
}, }
"endpoint-cost-map": { },
"ipv4:192.0.2.2": { "endpoint-cost-map": {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.2": {
"ipv4:198.51.100.34": 1, "ipv4:192.0.2.89" : 0,
"ipv6:2000::1:2345:6789:abcd" : 2, "ipv4:198.51.100.34": 1,
} "ipv6:2000::1:2345:6789:abcd" : 2,
} }
} }
}
8. Traffic Engineering Performance Cost Metrics 8. Traffic Engineering Performance Cost Metrics
This section introduces ALTO network performance metrics that may be This section introduces ALTO network performance metrics that may be
aggregated from network metrics measured on links and specified in aggregated from network metrics measured on links and specified in
other documents. In particular, the bandwidth related metrics other documents. In particular, the bandwidth related metrics
specified in this section are only available through link level specified in this section are only available through link level
measurements. For some of these metrics, the ALTO Server may further measurements. For some of these metrics, the ALTO Server may further
expose aggregated values while specifying the aggregation laws. expose aggregated values while specifying the aggregation laws.
skipping to change at page 18, line 25 skipping to change at page 18, line 25
"cost-metric": "maxresbw"}, "cost-metric": "maxresbw"},
"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-metric": "maxresbw" "cost-mode": "numerical",
} "cost-metric": "maxresbw"
}, }
" endpoint-cost-map": { },
"ipv4:192.0.2.2" { " endpoint-cost-map": {
"ipv4:192.0.2.89" : 0, "ipv4:192.0.2.2" {
"ipv4:198.51.100.34": 2000, "ipv4:192.0.2.89" : 0,
"ipv6:2000::1:2345:6789:abcd": 5000, "ipv4:198.51.100.34": 2000,
} "ipv6:2000::1:2345:6789:abcd": 5000,
} }
} }
}
8.2. Cost Metric: Link Residue Bandwidth 8.2. Cost Metric: Link 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
skipping to change at page 20, line 5 skipping to change at page 20, line 5
See section 2.1, Data sources. See section 2.1, Data sources.
Measurement Timing: Measurement Timing:
See section 5 of [RFC7810] 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 7: 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
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": "residubw"}, "cost-metric": "residubw"},
"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": "residubw" "cost-metric": "residubw"
} }
}, },
"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,
} }
} }
} }
8.3. Cost Metric: Link 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
skipping to change at page 21, line 39 skipping to change at page 22, line 5
Use and Applications: Use and Applications:
See section 3 for use and application. Besides, knowledge about See section 3 for use and application. Besides, knowledge about
available bandwidth is essential for applications to distribute or available bandwidth is essential for applications to distribute or
schedule their transmissions. The example below illustrates how schedule their transmissions. The example below illustrates how
this metric is provided in the form of an ALTO calendar, as this metric is provided in the form of an ALTO calendar, as
specified in [XXXX] to help deciding "where" and "when" to specified in [XXXX] to help deciding "where" and "when" to
transmit. transmit.
Example 9: availbw value on source-destination endpoint pairs Example 8: availbw value on source-destination endpoint pairs
This example assumes that the ALTO Server provides the values for This example assumes that the ALTO Server provides the values for
metric "availbw" in the form of an ALTO calendar and declares it metric "availbw" in the form of an ALTO calendar and declares it
in its IRD. 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
skipping to change at page 22, line 22 skipping to change at page 23, line 5
"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-metric": "availbw" "cost-mode": "numerical", "cost-metric": "availbw"
} }
"calendar-response-attributes" : [ "calendar-response-attributes" : [
"calendar-start-time" : Tue, 1 Mar 2017 13:00:00 GMT, "calendar-start-time" : Tue, 1 Mar 2017 13:00:00 GMT,
"time-interval-size" : "1 hour", "time-interval-size" : "1 hour",
"numb-intervals" : 8 "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],
} }
} }
} }
8.4. Cost Metric: Link 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
skipping to change at page 24, line 5 skipping to change at page 24, line 21
Measurement Timing: Measurement Timing:
Link Utilized bandwidth is Unidirectional utilization bandwidth Link Utilized bandwidth is Unidirectional utilization bandwidth
measured between two directly connected IS-IS neighbors or OSPF measured between two directly connected IS-IS neighbors or OSPF
neighbors, See section 5 of [RFC7810] for Measurement Timing. neighbors, 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 9: 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
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" : "utilbw"}, "cost-metric" : "utilbw"},
"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": "utilbw"
"cost-metric": "utilbw"
}
},
"endpoint-cost-map": {
"ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34" : 2000,
"ipv6:2000::1:2345:6789:abcd" : 5000,
}
} }
} },
"endpoint-cost-map": {
"ipv4:192.0.2.2" {
"ipv4:192.0.2.89" : 0,
"ipv4:198.51.100.34" : 2000,
"ipv6:2000::1:2345:6789:abcd" : 5000,
}
}
}
9. 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
skipping to change at page 25, line 23 skipping to change at page 26, line 5
formal conditions of mutual trust. formal conditions of mutual trust.
10. IANA Considerations 10. IANA Considerations
IANA has created and now maintains the "ALTO Cost Metric Registry", IANA has created and now maintains the "ALTO Cost Metric Registry",
listed in Section 14.2, Table 3 of [RFC7285]. This registry is listed in Section 14.2, Table 3 of [RFC7285]. This registry is
located at <http://www.iana.org/assignments/alto-protocol/alto- located at <http://www.iana.org/assignments/alto-protocol/alto-
protocol.xhtml#cost-metrics>. This document requests to add the protocol.xhtml#cost-metrics>. This document requests to add the
following entries to "ALTO Cost Meric Registry". following entries to "ALTO Cost Meric Registry".
+----------+--------------+---------------------------------------------+ +----------+--------------+----------------------------------------------+
|Namespace | Property | Reference | |Namespace | Property | Reference |
+----------+--------------+---------------------------------------------+ +----------+--------------+----------------------------------------------+
| | owdelay | [thisdraft] Section 3,[RFC2679] Section 3.6 | | | owdelay | [thisdraft] Section 3,[RFC2679] Section 3.6 |
| | rtt | [thisdraft] Section 4,[RFC2681],Section 2.6 | | | rtt | [thisdraft] Section 4,[RFC2681],Section 2.6 |
| | pdv | [thisdraft] Section 5,[RFC3393],Section 2.6 | | | pdv | [thisdraft] Section 5,[RFC3393],Section 2.6 |
| | hopcount | [thisdraft] Section 6,[RFC7285] | | | hopcount | [thisdraft] Section 6,[RFC7285] |
| | pktloss | [thisdraft] Section 7,[RFC7680],Section 2.6 | | | pktloss | [thisdraft] Section 7,[RFC7680],Section 2.6 |
| | maxresbw | [thisdraft] Section 8.1,[RFC5305],Section 3.5| | | maxresbw | [thisdraft] Section 8.1,[RFC5305],Section 3.5|
| | residbw | [thisdraft] Section 8.2,[RFC7810],Section 4.5| | | residbw | [thisdraft] Section 8.2,[RFC7810],Section 4.5|
| | availbw | [thisdraft] Section 8.3,[RFC7810],Section 4.6| | | availbw | [thisdraft] Section 8.3,[RFC7810],Section 4.6|
| | utilbw | [thisdraft] Section 8.4,[RFC7810,Section4.7] | | | utilbw | [thisdraft] Section 8.4,[RFC7810,Section4.7] |
+----------+--------------+---------------------------------------------+ +----------+--------------+----------------------------------------------+
11. References 11. References
11.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., Ginsberg, L., Previdi, S., Wu, Q., Gredler, H., Ray, S.,
jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg, Tantsura, J., and C. Filsfils, "BGP-LS Advertisement of
"BGP-LS Advertisement of IGP Traffic Engineering IGP Traffic Engineering Performance Metric Extensions",
Performance Metric Extensions", draft-ietf-idr-te-pm- draft-ietf-idr-te-pm-bgp-08 (work in progress), August
bgp-06 (work in progress), June 2017. 2017.
[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-04 (work in progress), June 2017. ippm-initial-registry-05 (work in progress), October 2017.
[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 [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679,
September 1999, <http://www.rfc-editor.org/info/rfc2679>. September 1999, <https://www.rfc-editor.org/info/rfc2679>.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681, Delay Metric for IPPM", RFC 2681, DOI 10.17487/RFC2681,
September 1999, <http://www.rfc-editor.org/info/rfc2681>. September 1999, <https://www.rfc-editor.org/info/rfc2681>.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393, Metric for IP Performance Metrics (IPPM)", RFC 3393,
DOI 10.17487/RFC3393, November 2002, DOI 10.17487/RFC3393, November 2002,
<http://www.rfc-editor.org/info/rfc3393>. <https://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>. <https://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>. <https://www.rfc-editor.org/info/rfc5234>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, October Engineering", RFC 5305, DOI 10.17487/RFC5305, October
2008, <http://www.rfc-editor.org/info/rfc5305>. 2008, <https://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>. <https://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>. <https://www.rfc-editor.org/info/rfc7471>.
[RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, [RFC7680] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton,
Ed., "A One-Way Loss Metric for IP Performance Metrics Ed., "A One-Way Loss Metric for IP Performance Metrics
(IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January (IPPM)", STD 82, RFC 7680, DOI 10.17487/RFC7680, January
2016, <http://www.rfc-editor.org/info/rfc7680>. 2016, <https://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>. <https://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>. <https://www.rfc-editor.org/info/rfc7810>.
11.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.
 End of changes. 57 change blocks. 
235 lines changed or deleted 256 lines changed or added

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