Skip to main content

Component Link Recording and Resource Control for TE Links

Document Type Expired Internet-Draft (mpls WG)
Expired & archived
Authors Anca Zamfir , Zafar Ali
Last updated 2024-01-16 (Latest revision 2011-04-27)
Replaces draft-zamfir-explicit-resource-control-bundle
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Experimental
Additional resources Mailing list discussion
Stream WG state Dead WG Document
Other - see Comment Log
Document shepherd (None)
IESG IESG state Expired
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Adrian Farrel
IESG note
Send notices to

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Anca Zamfir
Zafar Ali

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