FYI We have just updated this draft to document the issues with EVPN Route Type 8 in RFC 9251, ensuring they remain visible until a solution is agreed upon.
Thanks. Jorge From: internet-dra...@ietf.org <internet-dra...@ietf.org> Date: Friday, January 10, 2025 at 2:07 PM To: Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>, Olivier Dornon (Nokia) <olivier.dor...@nokia.com>, Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>, Olivier Dornon (Nokia) <olivier.dor...@nokia.com> Subject: New Version Notification for draft-rd-bess-evpn-mcast-leave-update-01.txt 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. A new version of Internet-Draft draft-rd-bess-evpn-mcast-leave-update-01.txt has been successfully submitted by J. Rabadan and posted to the IETF repository. Name: draft-rd-bess-evpn-mcast-leave-update Revision: 01 Title: Ethernet VPN (EVPN) Multicast Leave Synch Route Update Date: 2025-01-10 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/archive/id/draft-rd-bess-evpn-mcast-leave-update-01.txt Status: https://datatracker.ietf.org/doc/draft-rd-bess-evpn-mcast-leave-update/ HTMLized: https://datatracker.ietf.org/doc/html/draft-rd-bess-evpn-mcast-leave-update Diff: https://author-tools.ietf.org/iddiff?url2=draft-rd-bess-evpn-mcast-leave-update-01 Abstract: The Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxies for Ethernet VPN (EVPN) specification describes the procedures to synchronize IGMP/MLD membership report and leave group states in all the PEs that are attached to the same Ethernet Segment. In particular, the Multicast Leave Synch route described in the same specification, synchronizes the leave procedures on all the members of the Ethernet Segment, for a multicast group and for an amount of time (the Maximum Response Time). The use of the Maximum Response Time may be different depending on whether the local state was created by IGMPv2, IGMPv3 or MLDv2. In addition, the Maximum Response Time advertised in the Multicast Leave Synch route needs to account for the time that it takes for the route to be propagated in the network, which might not be easy to predict. This document clarifies the use of the Maximum Response Time and updates the procedures for the Multicast Leave Synch route. The IETF Secretariat
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
