VPLS External Loop Detection and Protection Requirements
draft-boldy-l2vpn-vplsloop-req-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Richard Boldy | ||
| Last updated | 2013-09-23 (Latest revision 2013-03-22) | ||
| 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
Virtual Private LAN Service (VPLS) implementations, as defined in [RFC4761] and [RFC4762], are highly susceptible to layer-2 loops external to the PE customer-facing interface. Such loops impact performance and can have a detrimental affect on all VPLS traffic throughout the entire instance under certain conditions. Current Layer-2 loop detection and protection mechanisms do not function effectively here. This document describes the requirements for a protocol function to offer VPLS service providers a mechanism for detecting such layer-2 loops and facilitating configurable actions without the need for inter-operation with customer network protocols, other VPLS PEs or customer sourced frames.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)