Avoiding Repeated Preemption of Low-Priority TE LSPs - Recommendations
draft-sudha-teas-rsvp-preemption-avoidance-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sudharsana Venkataraman | ||
| Last updated | 2016-01-06 (Latest revision 2015-07-05) | ||
| 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
When a high priority LSP is being setup, if there is reservation contention on a link along the path to the destination, any low priority LSP taking the link could get preempted and eventually rerouted. Low priority LSPs could suffer preemption repeatedly when they are placed in succession on heavily used links that have very less remaining bandwidth. This document describes a solution to avoid repeated preemption of low priority LSPs in the network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)