Skip to main content

Performance-based Path Selection for Explicitly Routed LSPs using TE Metric Extensions
draft-ietf-mpls-te-express-path-00

Document Type Replaced Internet-Draft (mpls WG)
Expired & archived
Authors Alia Atlas , John Drake , Spencer Giacalone , David Ward , Stefano Previdi , Clarence Filsfils
Last updated 2014-04-19 (Latest revision 2013-10-16)
Replaces draft-atlas-mpls-te-express-path
Replaced by draft-ietf-teas-te-express-path
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Associated WG milestone
Jul 2015
Submit draft-ietf-mpls-te-express-path
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-teas-te-express-path
Consensus boilerplate Unknown
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 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
John Drake
Spencer Giacalone
David Ward
Stefano Previdi
Clarence Filsfils

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)