draft-ietf-alto-performance-metrics-04.txt   draft-ietf-alto-performance-metrics-05.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: December 18, 2018 Yale University Expires: April 24, 2019 Yale University
Y. Lee Y. Lee
D. Dhody D. Dhody
Huawei Huawei
S. Randriamasy S. Randriamasy
Nokia Bell Labs Nokia Bell Labs
June 16, 2018 October 21, 2018
ALTO Performance Cost Metrics ALTO Performance Cost Metrics
draft-ietf-alto-performance-metrics-04 draft-ietf-alto-performance-metrics-05
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 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 https://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 December 18, 2018. This Internet-Draft will expire on April 24, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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
skipping to change at page 2, line 46 skipping to change at page 2, line 46
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 Challenge . . . . . . . . . . . . . . . . . 5 2.1. Data sources Challenge . . . . . . . . . . . . . . . . . 5
2.2. ALTO performance metrics Computation Challenges . . . . . 5 2.2. ALTO performance metrics Computation Challenges . . . . . 5
2.2.1. Configuration Parameters Challenge . . . . . . . . . 5 2.2.1. Configuration Parameters Challenge . . . . . . . . . 5
2.2.2. Availability of end to end path values Challenge . . 6 2.2.2. Availability of end to end path values Challenge . . 6
3. Cost Metric: POWDelay . . . . . . . . . . . . . . . . . . . . 6 3. Cost Metric: OWDelay . . . . . . . . . . . . . . . . . . . . 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. Cost Metric: Throughput . . . . . . . . . . . . . . . . . . . 16
8.1. Cost Metric: Link Maximum Reservable Bandwidth . . . . . 17 9. Traffic Engineering Performance Cost Metrics . . . . . . . . 18
8.2. Cost Metric: Link Residue Bandwidth . . . . . . . . . . . 18 9.1. Cost Metric: Link Maximum Reservable Bandwidth . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 9.2. Cost Metric: Link Residue Bandwidth . . . . . . . . . . . 20
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 10. Security Considerations . . . . . . . . . . . . . . . . . . . 22
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
11.1. Normative References . . . . . . . . . . . . . . . . . . 21 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.2. Informative References . . . . . . . . . . . . . . . . . 23 12.1. Normative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 12.2. Informative References . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
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 37 skipping to change at page 3, line 38
metric (Sec. 14.2 of ALTO base specification [ALTO]). metric (Sec. 14.2 of ALTO base specification [ALTO]).
+----------+--------------+----------------------------------------+ +----------+--------------+----------------------------------------+
|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 |
| | throughput | See Section x, [RFC6349] Section 3.3 |
| | 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 |
+----------+--------------+----------------------------------------+ +----------+--------------+----------------------------------------+
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
standard measurement methods such as those specified in IPPM, some standard measurement methods such as those specified in IPPM, some
skipping to change at page 6, line 18 skipping to change at page 6, line 18
Applications value information relating to bandwidth availability Applications value information relating to bandwidth availability
where as bandwidth related metrics can often be only measured at the where as bandwidth related metrics can often be only measured at the
link level. This document specifies a set of link-level bandwidth link level. This document specifies a set of link-level bandwidth
related values that may be exposed as such by an ALTO server. The related values that may be exposed as such by an ALTO server. The
server may also expose other metrics derived from their aggregation server may also expose other metrics derived from their aggregation
and having different levels of endpoint granularity, e.g. link and having different levels of endpoint granularity, e.g. link
endpoints or session endpoints. The metric specifications may also endpoints or session endpoints. The metric specifications may also
expose the utilized aggregation laws. expose the utilized aggregation laws.
3. Cost Metric: POWDelay 3. Cost Metric: OWDelay
Metric name: Metric name:
Periodic One Way Delay 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 level is specified in the destination. The spatial aggregation level is specified in the
query context (e.g., PID to PID, or endpoint to endpoint). query context (e.g., PID to PID, or endpoint to endpoint).
Method of Measurement or Calculation: Method of Measurement or Calculation:
skipping to change at page 7, line 31 skipping to change at page 7, line 31
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" : "powdelay"}, "cost-metric" : "owdelay"},
"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" : "owdelay"
} }
}, },
"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,
} }
} }
} }
skipping to change at page 11, line 18 skipping to change at page 12, line 5
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 3: Delay jitter value on source-destination endpoint pairs Example 3: PDV 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" : "pdv"},
"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
skipping to change at page 16, line 45 skipping to change at page 16, 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": 0, "ipv4:198.51.100.34": 0,
"ipv6:2000::1:2345:6789:abcd" : 0, "ipv6:2000::1:2345:6789:abcd" : 0,
} }
} }
} }
8. Traffic Engineering Performance Cost Metrics 8. Cost Metric: Throughput
Metric name:
Throughput
Metric Description:
To specify spatial and temporal throughput over the specified
source and destination. The spatial aggregation level is
specified in the query context (e.g., PID to PID, or endpoint to
endpoint).
Method of Measurement or Calculation:
See section 3.3 of [RFC6349] for Measurement Method.
Units of Measurement:
The unit is Mbps.
Measurement Point(s) with Potential Measurement Domain:
See section 2.1, Data sources.
Measurement Timing:
Similar to RTT,See section 4.3.5 of [I-D.ietf-ippm-initial-
registry] for Measurement Timing.
Use and Applications:
See section 3 for use and application.
Example 5: throughtput 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" : "throughput"},
"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":"throughput"}
}
},
"endpoint-cost-map": {
"ipv4:192.0.2.2": {
"ipv4:192.0.2.89" : 25.6,
"ipv4:198.51.100.34": 12.8,
"ipv6:2000::1:2345:6789:abcd" : 42.8,
}
}
}
9. 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.
8.1. Cost Metric: Link Maximum Reservable Bandwidth 9.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
skipping to change at page 18, line 45 skipping to change at page 20, 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,
} }
} }
} }
8.2. Cost Metric: Link Residue Bandwidth 9.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
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
skipping to change at page 20, line 5 skipping to change at page 22, 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 7: residuebw value on source-destination endpoint pairs Example 7: residbw 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"},
skipping to change at page 20, line 33 skipping to change at page 22, line 33
} }
} }
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": "residbw"
} }
}, },
"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,
} }
} }
} }
9. Security Considerations 10. 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, therefore, sharing performance is a highly sensitive ISP information, therefore, sharing
TE metric values in numerical mode requires full mutual confidence TE 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.
On 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.
10. IANA Considerations 11. 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 |
| | throughput | [thisdraft],[RFC6349],Section3.3 |
| | 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|
+----------+------------+----------------------------------------------+ +----------+------------+----------------------------------------------+
11. References 12. References
11.1. Normative References 12.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C. Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C.
Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm- Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-10 (work in progress), March 2018. bgp-14 (work in progress), October 2018.
[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-06 (work in progress), March 2018. ippm-initial-registry-07 (work in progress), June 2018.
[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, <https://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,
skipping to change at page 22, line 32 skipping to change at page 24, line 35
[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,
<https://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, <https://www.rfc-editor.org/info/rfc5305>. 2008, <https://www.rfc-editor.org/info/rfc5305>.
[RFC6349] Constantine, B., Forget, G., Geib, R., and R. Schrage,
"Framework for TCP Throughput Testing", RFC 6349,
DOI 10.17487/RFC6349, August 2011,
<https://www.rfc-editor.org/info/rfc6349>.
[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,
<https://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,
<https://www.rfc-editor.org/info/rfc7471>. <https://www.rfc-editor.org/info/rfc7471>.
skipping to change at page 23, line 16 skipping to change at page 25, line 26
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,
<https://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,
<https://www.rfc-editor.org/info/rfc7810>. <https://www.rfc-editor.org/info/rfc7810>.
11.2. Informative References 12.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. 27 change blocks. 
52 lines changed or deleted 115 lines changed or added

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