Reusage MPLS RSVP Labels during MBB
draft-sboyapati-mpls-rsvp-label-reusage-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | sureshkb@juniper.net | ||
| Last updated | 2018-01-03 (Latest revision 2017-07-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
MPLS is the heart and soul of the service provider network. MPLS can carry any data payload which gives the flexibility to the service provider to provision new service with any expense. In a scaled MPLS RSVP router during MBB/Global repair, router needs to program large number of labels into PFE. This operation results in lot of label re-computation and label programming. This draft is proposing a solution to label reusage
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)