Optimized Ingress Replication Solution for Ethernet VPNs
RFC 9574, “Optimized Ingress Replication Solution for Ethernet VPNs”, is a Proposed Standard document published in May 2024 by J. Rabadan, S. Sathappan, W. Lin, M. Katiyar, A. Sajassi. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9574 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9573 MVPN/EVPN Tunnel Aggregation with Common Labels
- RFC 9575 DRIP Entity Tag Authentication Formats and Protocols for Broadcast Remote Identification
- RFC 9572 Updates to EVPN Broadcast, Unknown Unicast, or Multicast Procedures
- RFC 9576 The Privacy Pass Architecture
- RFC 9571 Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels
- RFC 9577 The Privacy Pass HTTP Authentication Scheme
- RFC 9570 Deprecating the Use of Router Alert in LSP Ping
- RFC 9578 Privacy Pass Issuance Protocols