Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

J. Rabadan, Ed.
S. Sathappan
W. Lin
M. Katiyar
A. Sajassi

Stream:

IETF

Source:

bess (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9574

Discuss this RFC: Send questions or comments to the mailing listbess@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9574

Abstract

Network Virtualization Overlay (NVO) networks using Ethernet VPNs(EVPNs) as their control plane may use trees based on ingressreplication or Protocol Independent Multicast (PIM) to convey theoverlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIMprovides an efficient solution that prevents sending multiple copiesof the same packet over the same physical link; however, it may notalways be deployed in the NVO network core. Ingress replicationavoids the dependency on PIM in the NVO network core. While ingressreplication provides a simple multicast transport, some NVO networkswith demanding multicast applications require a more efficientsolution without PIM in the core. This document describes a solutionto optimize the efficiency of ingress replication trees.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.