AC-Influenced DF Election per EVI
draft-wang-bess-evpn-ac-df-per-evi-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yubao Wang | ||
| Last updated | 2022-01-12 (Latest revision 2021-07-11) | ||
| 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
The AC-influenced DF Election (AC-DF) per [RFC8584] is too dependent on EAD/EVI routes. For example, when no failures occured on an ESI, that AC-DF procedures will give incorrect results if no EAD/EVI routes are advertised. But in some light-weighted EVPNs (i.e. PBB EVPNs), no EAD/EVI routes will be advertised at all. This draft proposes some new extensions to support AC-influenced DF Election without any EAD/EVI routes advertised in advance of any <ESI, EVI> failures.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)