A new Request for Comments is now available in online RFC libraries. RFC 9574
Title: Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) Author: J. Rabadan, Ed., S. Sathappan, W. Lin, M. Katiyar, A. Sajassi Status: Standards Track Stream: IETF Date: May 2024 Mailbox: jorge.raba...@nokia.com, senthil.sathap...@nokia.com, w...@juniper.net, mu...@versa-networks.com, saja...@cisco.com Pages: 28 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bess-evpn-optimized-ir-12.txt URL: https://www.rfc-editor.org/info/rfc9574 DOI: 10.17487/RFC9574 Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending multiple copies of the same packet over the same physical link; however, it may not always be deployed in the NVO network core. Ingress replication avoids the dependency on PIM in the NVO network core. While ingress replication provides a simple multicast transport, some NVO networks with demanding multicast applications require a more efficient solution without PIM in the core. This document describes a solution to optimize the efficiency of ingress replication trees. This document is a product of the BGP Enabled ServiceS Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ IETF-Announce mailing list -- ietf-announce@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org