Support as co-author. I am not aware of any undisclosed IPRs. HPE has an implementation of this draft.
Thanks, Wen Juniper Business Use Only From: Stephane Litkowski via Datatracker <[email protected]> Date: Monday, November 2, 2026 at 10:33 AM To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [bess] WG Last Call: draft-ietf-bess-extended-evpn-optimized-ir-09 (Ends 2026-11-16) [External Email. Be cautious of content] This message starts a WG Last Call for: draft-ietf-bess-extended-evpn-optimized-ir-09 This Working Group Last Call ends on 2026-11-16 Abstract: In the Virtualization Overlay (NVO) network with Ethernet VPN (EVPN), optimized ingress replication uses Assisted-Replication (AR) to achieve more efficient delivery of Broadcast and Multicast (BM) traffic. An AR-LEAF, which is a Network Virtualization Edge (NVE) device, forwards received BM traffic from its tenant system to an AR- REPLICATOR. The AR-REPLICATOR then replicates it to the remaining AR-LEAFs in the network. However, when replicating the packet on behalf of its multihomed AR-LEAF, an AR-REPLICATOR may face challenges in retaining the source IP address or including the expected Ethernet Segment Identifier (ESI) label that is required for EVPN split-horizon filtering. This document extends the optimized ingress replication procedures to address such limitations. The extended procedures specified in this document allow the support of EVPN multihoming on the AR-LEAFs as well as optimized ingress replication for the rest of the EVPN NVO network. File can be retrieved from: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-bess-extended-evpn-optimized-ir-09.txt__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-2FIerZsw$ Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [email protected] in copy. Objections should be explained and suggestions to resolve them are highly appreciated. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-2if7Q3Bg$ [2] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-21MHf5XQ$ [3] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-0QvPgOLQ$ The IETF datatracker status page for this Internet-Draft is: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-bess-extended-evpn-optimized-ir/__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-0RSdeclQ$ There is also an HTMLized version available at: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-bess-extended-evpn-optimized-ir-09__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-3iVLm0-w$ A diff from the previous version is available at: https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-extended-evpn-optimized-ir-09__;!!NpxR!hna9-TwGvcRr06_NEnKzAMJnxPDkiNGFj43N2d1h1CuhN3lNZ1H1WBBL0lvGaVyDCpaMh-3jmKzDqg$ _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
