%% You should probably cite draft-ietf-bess-evpn-irb-extended-mobility-21 instead of this revision. @techreport{ietf-bess-evpn-irb-extended-mobility-18, number = {draft-ietf-bess-evpn-irb-extended-mobility-18}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-extended-mobility/18/}, author = {Neeraj Malhotra and Ali Sajassi and Aparna Pattekar and Jorge Rabadan and Avinash Reddy Lingala and John Drake}, title = {{Extended Mobility Procedures for EVPN-IRB}}, pagetotal = 26, year = 2024, month = oct, day = 16, abstract = {This document specifies extensions to Ethernet VPN (EVPN) Integrated Routing and Bridging (IRB) procedures specified in RFC7432 and RFC9135 to enhance the mobility mechanisms for EVPN IRB-based networks. The proposed extensions improve the handling of host mobility and duplicate address detection in EVPN-IRB networks to cover a broader set of scenarios where host IP to MAC bindings may change across moves. These enhancements address limitations in the existing EVPN IRB mobility procedures by providing more efficient and scalable solutions. The extensions are backward compatible with existing EVPN IRB implementations and aim to optimize network performance in scenarios involving frequent IP address mobility. NOTE TO IESG (TO BE DELETED BEFORE PUBLISHING): This draft lists six authors which is above the required limit of five. Given significant and active contributions to the draft from all six authors over the course of six years, we would like to request IESG to allow publication with six authors. Specifically, the three Cisco authors are the original inventors of these procedures and contributed heavily to rev 0 draft, most of which is still intact. AT\&T is also a key contributor towards defining the use cases that this document addresses as well as the proposed solution. Authors from Nokia and Juniper have further contributed to revisions and discussions steadily over last six years to enable respective implementations and a wider adoption.}, }