Using ECN to Signal Congestion Within an MPLS Domain
draft-shayman-mpls-ecn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark Shayman , Robert Jaeger | ||
| Last updated | 2000-11-20 | ||
| 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
We propose the addition of Explicit Congestion Notification (ECN) together with congestion signaling back to the ingress in order to provide notification to the ingress label switching router (LSR) if congestion is experienced along a label switched path (LSP). This information could be used by the ingress LSR to mitigate congestion by employing dynamic traffic engineering techniques such as shifting flows to alternate paths.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)