Extended Mobility Procedures for EVPN-IRB

Document Type Replaced Internet-Draft (individual)
Authors Neeraj Malhotra  , Ali Sajassi  , Aparna Pattekar  , Avinash Lingala  , Jorge Rabadan  , John Drake 
Last updated 2019-07-22 (latest revision 2019-01-15)
Replaced by draft-ietf-bess-evpn-irb-extended-mobility
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-bess-evpn-irb-extended-mobility
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The procedure to handle host mobility in a layer 2 Network with EVPN control plane is defined as part of RFC 7432. EVPN has since evolved to find wider applicability across various IRB use cases that include distributing both MAC and IP reachability via a common EVPN control plane. MAC Mobility procedures defined in RFC 7432 are extensible to IRB use cases if a fixed 1:1 mapping between VM IP and MAC is assumed across VM moves. Generic mobility support for IP and MAC that allows these bindings to change across moves is required to support a broader set of EVPN IRB use cases, and requires further consideration. EVPN all-active multi-homing further introduces scenarios that require additional consideration from mobility perspective. Intent of this draft is to enumerate a set of design considerations applicable to mobility across EVPN IRB use cases and define generic sequence number assignment procedures to address these IRB use cases.


Neeraj Malhotra (neeraj.ietf@gmail.com)
Ali Sajassi (sajassi@cisco.com)
Aparna Pattekar (apjoshi@cisco.com)
Avinash Lingala (ar977m@att.com)
Jorge Rabadan (jorge.rabadan@nokia.com)
John Drake (jdrake@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)