Hi Sasha, About this: Is such a situation considered as a locally detected MAC Move event for the purpose of Section 15 of 7432bis? Specifically, should it result in starting the Duplicate MAC Detection timer and starting count of these events as described in Section 15.1 of 7432bis so that, if the number of these events detected while the timer is running exceeds the limit, this would result in declaring MAC address in question (and suppressing further advertisement of RT-2 for this MAC address)? Not really. Note that the bullets in section 15 start with: A PE detecting a locally attached MAC address for which it had previously received a MAC/IP Advertisement route .. For a local move between two ESes on the same PE, you’ll need to send an update with the new ESI. However, there are no withdrawals of the previous route since the ESI is not part of the key. In my opinion, updates with different ESIs should not increment the sequence number, as it serves no functional purpose.
Of course, implementations will have mechanisms to prevent local loops and avoid constant updates, but that is a local implementation matter. My two cents. Thanks. Jorge From: Alexander Vainshtein <alexander.vainsht...@rbbn.com> Date: Wednesday, December 25, 2024 at 12:47 AM To: draft-ietf-bess-rfc7432...@ietf.org <draft-ietf-bess-rfc7432...@ietf.org> Cc: bess@ietf.org <bess@ietf.org> Subject: MAC Move events between different ES in the same EVPN PE 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 all, I am asking for clarification on the following issue related to Section 15 of 7432bis<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-10#section-15>. Suppose that an EVPN PE that supports MAC learning from the data plane is attached to two different customer sites with at least one of the PE-CE links being part of a MH ES (in any MH mode). Suppose further that the DP that has previously locally learned a certain MAC address from one of its PE-CE links and has advertised an appropriate RT-2 for it locally learns the same MAC address from another of these links so that now it has to advertise it with the new ESI value in the NLRI of RT-2? Is such a situation considered as a locally detected MAC Move event for the purpose of Section 15 of 7432bis? Specifically, should it result in starting the Duplicate MAC Detection timer and starting count of these events as described in Section 15.1 of 7432bis so that, if the number of these events detected while the timer is running exceeds the limit, this would result in declaring MAC address in question (and suppressing further advertisement of RT-2 for this MAC address)? Your timely feedback would be highly appreciated. Regards, and lots of thanks in advance, Sasha Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
