Skip to main content

Optimized Ingress Replication solution for EVPN

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Jorge Rabadan , Senthil Sathappan , Wim Henderickx , Ali Sajassi , Aldrin Isaac
Last updated 2015-04-27 (Latest revision 2014-10-24)
Replaces draft-rabadan-l2vpn-evpn-optimized-ir
Replaced by draft-ietf-bess-evpn-optimized-ir, draft-ietf-bess-evpn-optimized-ir, draft-ietf-bess-evpn-optimized-ir
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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
Ali Sajassi
Aldrin Isaac

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