Component Link Recording and Resource Control for TE Links
draft-ietf-mpls-explicit-resource-control-bundle-10
| Document | Type |
Expired Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Anca Zamfir , Zafar Ali | ||
| Last updated | 2015-10-14 (Latest revision 2011-04-27) | ||
| Replaces | draft-zamfir-explicit-resource-control-bundle | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Experimental | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| 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 is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)