draft-ietf-teas-te-express-path-04.txt   draft-ietf-teas-te-express-path-05.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft J. Drake Internet-Draft J. Drake
Intended status: Informational Juniper Networks Intended status: Informational Juniper Networks
Expires: April 3, 2016 S. Giacalone Expires: April 3, 2016 S. Giacalone
Unaffiliated Unaffiliated
S. Previdi S. Previdi
Cisco Systems Cisco Systems
October 1, 2015 October 1, 2015
Performance-based Path Selection for Explicitly Routed LSPs using TE Performance-based Path Selection for Explicitly Routed LSPs using TE
Metric Extensions Metric Extensions
draft-ietf-teas-te-express-path-04 draft-ietf-teas-te-express-path-05
Abstract Abstract
In certain networks, it is critical to consider network performance In certain networks, it is critical to consider network performance
criteria when selecting the path for an explicitly routed RSVP-TE criteria when selecting the path for an explicitly routed RSVP-TE
LSP. Such performance criteria can include latency, jitter, and loss LSP. Such performance criteria can include latency, jitter, and loss
or other indications such as the conformance to link performance or other indications such as the conformance to link performance
objectives and non-RSVP TE traffic load. This specification objectives and non-RSVP TE traffic load. This specification
describes how a path computation function may use network performance describes how a path computation function may use network performance
data, such as is advertised via the OSPF and ISIS TE metric data, such as is advertised via the OSPF and ISIS TE metric
skipping to change at page 3, line 49 skipping to change at page 3, line 49
in [RFC7471] and [I-D.ietf-isis-te-metric-extensions] are followed. in [RFC7471] and [I-D.ietf-isis-te-metric-extensions] are followed.
Additionally, the end-to-end performance that is computed for an LSP Additionally, the end-to-end performance that is computed for an LSP
path should be built from the individual link data. Any end-to-end path should be built from the individual link data. Any end-to-end
characterization used to determine an LSP's performance compliance characterization used to determine an LSP's performance compliance
should be fully reflected in the Traffic Engineering Database so that should be fully reflected in the Traffic Engineering Database so that
a path calculation can also determine whether a path under a path calculation can also determine whether a path under
consideration would be in compliance. consideration would be in compliance.
1.1. Basic Requirements 1.1. Basic Requirements
The following are the requirements that motivate this document. The following are the requirements considered for a path computation
function that uses network performance criteria.
1. Select a TE tunnel's path based upon a combination of existing 1. Select a TE tunnel's path based upon a combination of existing
constraints as well as on link-latency, packet loss, jitter, link constraints as well as on link-latency, packet loss, jitter, link
performance objectives conformance, and bandwidth consumed by performance objectives conformance, and bandwidth consumed by
non-RSVP-TE traffic. non-RSVP-TE traffic.
2. Ability to define different end-to-end performance requirements 2. Ability to define different end-to-end performance requirements
for each TE tunnel regardless of common use of resources. for each TE tunnel regardless of common use of resources.
3. Ability to periodically verify with the TE LSDB that a TE 3. Ability to periodically verify with the TE LSDB that a TE
 End of changes. 2 change blocks. 
2 lines changed or deleted 3 lines changed or added

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