%% You should probably cite draft-ali-ccamp-rc-objective-function-metric-bound-05 instead of this revision.
@techreport{ali-ccamp-rc-objective-function-metric-bound-01,
    number =    {draft-ali-ccamp-rc-objective-function-metric-bound-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ali-ccamp-rc-objective-function-metric-bound/01/},
    author =    {Zafar Ali and George Swallow and Clarence Filsfils and Luyuan Fang and Ruediger Kunze},
    title =     {{Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) extension for signaling Objective Function and Metric Bound}},
    pagetotal = 12,
    year =      2012,
    month =     mar,
    day =       12,
    abstract =  {When using GMPLS control plane, the ingress node may need to request remote node to perform route computation or expansion. In such cases, ingress node needs to convey the required objective function for the path computation algorithm to the remote node, so that the remote node can perform the route computation or expansion. Similarly, there are cases the ingress needs to indicate a TE metric bound for the loose segment which is 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).},
}