Skip to main content

Optimized Ingress Replication solution for EVPN

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Jorge Rabadan , Senthil Sathappan , Wim Henderickx
Last updated 2014-10-27 (Latest revision 2014-07-04)
Replaced by draft-rabadan-bess-evpn-optimized-ir
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-rabadan-bess-evpn-optimized-ir
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Network Virtualization Overlay (NVO) networks using EVPN as control plane may use ingress replication (IR) or PIM-based trees to convey the overlay multicast traffic. PIM provides an efficient solution to avoid sending multiple copies of the same packet over the same physical link, however it may not always be deployed in the NVO core network. IR avoids the dependency on PIM in the NVO network core. While IR 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 IR in NVO networks.


Jorge Rabadan
Senthil Sathappan
Wim Henderickx

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)