VPLS external Loop Protection Mechanism (VLPM)
draft-l2vpn-vlpm-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard Boldy | ||
| Last updated | 2013-11-04 (Latest revision 2013-05-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
In reference and response to draft-boldy-l2vpn-vplsloop-req-01, this document describes a solution in the form of a protocol function named VPLS External Loop Protection Mechanism (VLPM). VLPM is a protocol for a service provider to deploy at the PE to detect layer-2 loops in any external layer-2 segments (customer LAN) where customer deployed loop prevention methods may have failed. After detection of such a loop it facilitates configurable actions to protect the rest of the VPLS Domain from being affected without the need for inter-operation with customer network protocols, other VPLS PEs or sites.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)