Mobility Procedures in Presence of Unknown MAC Route
draft-sajassi-bess-evpn-umr-mobility-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ali Sajassi , Lukas Krattiger , Krishnaswamy Ananthamurthy , Jorge Rabadan , John Drake | ||
| Last updated | 2023-09-13 (Latest revision 2023-03-12) | ||
| 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
Interconnect Solution for Ethernet VPN [RFC9014] defines Unknown MAC Route (UMR) utilization for Data Center Interconnect (DCI) when EVPN MPLS or EVPN VXLAN is used as overlay network for such interconnects. The introduction of UMR for such scenarios impacts MAC mobility procedures that are not discussed in [RFC9014]. This document describes additional changes and enhancements needed for MAC mobility procedures when UMR is used.
Authors
Ali Sajassi
Lukas Krattiger
Krishnaswamy Ananthamurthy
Jorge Rabadan
John Drake
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)