Smooth Evolution of Existing EVPN IRB Network
draft-wang-bess-evpn-irb-smooth-evolution-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yubao Wang | ||
| Last updated | 2022-05-24 (Latest revision 2021-11-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
EVPN IRB has been deployed following [RFC9135]'s early draft for a long time. This draft discusses how can these existing deployments smoothly evolved into an IP-aliasing ([I-D.sajassi-bess-evpn-ip-aliasing]) enhanced EVPN symmetric IRB scenario, especially when two of an IP-VRF's BDs (whose IRB interfaces are attached to the same IP-VRF) have been attched to a common ES before that network evolution. In such case, when these two BDs are evolved into IP-aliasing enhanced EVPN symmetric IRB as per [I-D.sajassi-bess-evpn-ip-aliasing] or distributed Bump-in-the- wire as per [I-D.wang-bess-evpn-distributed-bump-in-the-wire], the IP A-D per EVI routes of these two BDs may conflict with each other in the context of the IP-VRF instance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)