Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) extension for signaling Objective Function and Metric Bound

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Zafar Ali  , George Swallow  , Clarence Filsfils  , Luyuan Fang  , Kenji Kumaki  , Ruediger Kunze 
Last updated 2013-01-17 (latest revision 2012-07-16)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
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


In particular networks such as those used by financial institutions, network performance criteria such as latency are becoming as critical to data path selection. However cost is still an important consideration. This leads to a situation where path calculation involves multiple metrics an more complex objective functions. When using GMPLS control plane, the ingress node may need to request remote node to perform path computation or expansion. In such cases, ingress node needs to convey the required objective function to the remote node, to enable it to perform the desired path computation. Similarly, there are cases the ingress needs to indicate a TE metric bound for a loose segment that is expanded by a remote node. This document defines extensions to the RSVP-TE Protocol to allow an ingress node to request the required objective function for the path computation, as well as a metric bound to influence route computation decisions at a remote node(s).


Zafar Ali (
George Swallow (
Clarence Filsfils (
Luyuan Fang (
Kenji Kumaki (
Ruediger Kunze (

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