Performance-based Path Selection for Explicitly Routed LSPs
draft-atlas-mpls-te-express-path-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2012-12-27 (latest revision 2012-06-25)
Replaced by draft-ietf-mpls-te-express-path
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-atlas-mpls-te-express-path-01.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 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 (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.)