Component Link Recording and Resource Control for TE Links
draft-ietf-mpls-explicit-resource-control-bundle-10

Document Type Expired Internet-Draft (mpls WG)
Last updated 2015-10-14 (latest revision 2011-04-27)
Replaces draft-zamfir-explicit-resource-control-bundle
Stream IETF
Intended RFC status Experimental
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
IESG note Loa Andersson (loa@pi.nu) is the Document Shepherd
Send notices to martin.vigoureux@alcatel-lucent.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mpls-explicit-resource-control-bundle-10.txt

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.

Authors

Anca Zamfir (ancaz@cisco.com)
Zafar Ali (zali@cisco.com)

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