Hi Vinayak, I still believe the mobility procedure using the UMR can be applied in the GW-based proxy-ARP/ND solution. In this model, the gateway would advertise the UMR along with only those MAC/IP Advertisement routes that correspond to MACs moving across domains. The leaf routers can then leverage these MAC/IP routes to execute the required mobility procedures.
Thanks. Jorge From: Joshi, Vinayak <[email protected]> Date: Sunday, September 14, 2025 at 8:07 PM To: 'BESS' <[email protected]> Subject: [bess] Re: GW-based Proxy ARP/ND Solution with EVPN UMR & Inter-DC Mobility You don't often get email from [email protected]. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Hi, Any thoughts on this? In case of GW-based Proxy ARP/ND Solution inform the PEs about mobility across DCs when the GW is not expected to sent out RT-2? Regards, Vinayak From: Joshi, Vinayak Sent: Tuesday, September 9, 2025 6:11 PM To: 'BESS' <[email protected]> Subject: GW-based Proxy ARP/ND Solution with EVPN UMR & Inter-DC Mobility Hi all, Is it correct to say that GW-based Proxy ARP/ND Solution (https://www.ietf.org/archive/id/draft-sajassi-bess-evpn-umr-mobility-03.html#name-gw-based-proxy-arp-nd-solut) should not be deployed when inter-DC mobility of end hosts is possible? This is because even if the GW maintains mobility sequence number per network (local/interconnects) it does not advertise MAC/IP routes into the local DC (DC 1 in the draft) in this solution. Hence, it doesn’t help PEs in DC1 to recognize MAC move to DC2. Regards, Vinayak
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
