@techreport{ietf-mpls-explicit-resource-control-bundle-10,
    number =    {draft-ietf-mpls-explicit-resource-control-bundle-10},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mpls-explicit-resource-control-bundle/10/},
    author =    {Anca Zamfir and Zafar Ali},
    title =     {{Component Link Recording and Resource Control for TE Links}},
    pagetotal = 13,
    year =      2011,
    month =     apr,
    day =       27,
    abstract =  {Record Route is a useful administrative tool that has been used extensively by the service providers. However, when TE links are bundled, identification of label resource in Record Route object (RRO) is not sufficient to determine the component link within a TE link that is being used by a given LSP. In other words, when link bundling is used, resource recording requires mechanisms to specify the component link identifier, along with the TE link identifier and Label. As it is not possible to record component link in the RRO, this document defines the extensions to RSVP-TE {[}RFC3209{]} and {[}RFC3473{]} to specify component link identifiers for resource recording purposes.},
}