Link Aggregation Member Interface Status Signal
draft-zi-pwe3-link-aggr-member-status-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zi Kang , Liu Jun | ||
| Last updated | 2005-10-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
Link Aggregation can be used as Attachment Circuit (AC) of the PWE3 service. Link Aggregation is treated as a single interface. But changes in the the member interface may affect use of the aggregated link. This draft suggests a method to signal the status of the member interface of Link Aggregation AC to remote Provider Edge (PE) device. With this status information, the remote PE can decide to discard traffic over bandwidth, avoid congestion at local PE and avoid wasted bandwidth of the Packet Switched Network (PSN). This mechanism is required in PWE3 applications because pseudo-wires provide layer 1/layer 2 services, carrying traffic that may not respond to loss events by executing congestion avoidance
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)