General Considerations for Bandwidth Reservation in Protection
draft-mo-mpls-protection-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Li Mo | ||
| Last updated | 2000-07-06 | ||
| 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
Protection issues for MPLS LSP have been discussed in recent IETF meetings. Various drafts have different proposals on establishing the working and protection LSP ([1]-[5]). But how to reserve bandwidth for the protection LSP has not be discussed. If the bandwidth for the protection LSP is reserved in a similar fashion as that of the working LSP, the bandwidth utilization in the network would be very poor. In this draft, an algorithm for reserve bandwidth for protection LSP is presented which enables very efficient bandwidth reservation for single fault protection.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)