Loop Protection in EVPN networks
draft-snr-bess-evpn-loop-protect-04
| Document | Type |
Expired Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jorge Rabadan , Senthil Sathappan , Kiran Nagaraj , Julio Bueno , Jose Manuel Crespo | ||
| Last updated | 2020-02-06 (Latest revision 2019-08-05) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Ethernet Virtual Private Networks (EVPN) is becoming the de-facto standard-based control plane solution for Data Center and layer-2 Service Provider applications. The risk of loops caused by backdoor paths accidentally created within the same broadcast domain, is a general common concern, especially among Service Providers in large Layer-2 networks. While other layer-2 Ethernet technologies use Spanning Tree based Protocols (xSTP) to provide a network-wide loop protection, EVPN has the right tools to detect and protect the network against loops in an efficient and effective way. This document describes a mechanism to provide global loop protection in EVPN networks.
Authors
Jorge Rabadan
Senthil Sathappan
Kiran Nagaraj
Julio Bueno
Jose Manuel Crespo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)