metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9574: Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9574
Published
May 2024
Authors
J. Rabadan; S. Sathappan; W. Lin; M. Katiyar; A. Sajassi
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
28
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9574-optimized-ingress-replication-solution-for-ethernet-vpns-evpns