<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ali-ccamp-rc-objective-function-metric-bound" target="https://datatracker.ietf.org/doc/html/draft-ali-ccamp-rc-objective-function-metric-bound-00">
   <front>
      <title>Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) extension for signaling Objective Function and Metric Bound</title>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         </author>
      <author initials="G." surname="Swallow" fullname="George Swallow">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <date month="March" day="5" year="2012" />
      <abstract>
	 <t>     There are scenarios where an ingress node requests remote node(s)
     to perform route computation or expansion. In such cases, there is
     a need for the ingress node to convey the required objective
     function for the path computation algorithm to the remote node
     performing route computation or expansion. Similarly, there is a
     need for the ingress node to indicate a TE metric bound for the
     loose segment expanded by the remote node(s). 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).


     
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ali-ccamp-rc-objective-function-metric-bound-00" />
   
</reference>
