Performance-based Path Selection for Explicitly Routed LSPs
draft-atlas-mpls-te-express-path-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Alia Atlas , John Drake , David Ward , Spencer Giacalone , Stefano Previdi , Clarence Filsfils | ||
| Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
| Replaced by | draft-ietf-mpls-te-express-path | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 SLAs and non- RSVP TE traffic load. This specification uses IGP extension data (which is defined outside the scope of this document) to perform such path selections.
Authors
Alia Atlas
John Drake
David Ward
Spencer Giacalone
Stefano Previdi
Clarence Filsfils
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)