datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

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)
Document stream: IETF
Last updated: 2013-10-16 (latest revision 2013-09-12)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: Adopted by a WG
Document shepherd: Loa Andersson

IESG State: Replaced by draft-ietf-mpls-te-express-path
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://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)