Performance-based Path Selection for Explicitly Routed LSPs using TE Metric Extensions
draft-atlas-mpls-te-express-path-04
| Document | Type | Replaced Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 2013-10-16 (latest revision 2013-09-12) | ||
| Replaced by | draft-ietf-mpls-te-express-path | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Loa Andersson | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-te-express-path | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-atlas-mpls-te-express-path-04.txt
Abstract
In certain networks, it is critical to consider network performance criteria when selecting the path for an explicitly routed RSVP-TE LSP. Such performance criteria can include latency, jitter, and loss or other indications such as the conformance to link performance objectives and non-RSVP TE traffic load. This specification uses network performance data, such as is advertised via the OSPF and ISIS TE metric extensions (defined outside the scope of this document) to perform such path selections.
Authors
Alia Atlas
(akatlas@juniper.net)
John Drake
(jdrake@juniper.net)
Spencer Giacalone
(Spencer.giacalone@thomsonreuters.com)
David Ward
(dward@cisco.com)
Stefano Previdi
(sprevidi@cisco.com)
Clarence Filsfils
(cfilsfil@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)