%% You should probably cite draft-ietf-bess-evpn-optimized-ir-12 instead of this revision. @techreport{ietf-bess-evpn-optimized-ir-11, number = {draft-ietf-bess-evpn-optimized-ir-11}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-optimized-ir/11/}, author = {Jorge Rabadan and Senthil Sathappan and Wen Lin and Mukul Katiyar and Ali Sajassi}, title = {{Optimized Ingress Replication Solution for Ethernet VPN (EVPN)}}, pagetotal = 34, year = , month = , day = , abstract = {Network Virtualization Overlay networks using Ethernet VPN (EVPN) as control plane may use Ingress Replication or PIM (Protocol Independent Multicast)-based trees to convey the overlay Broadcast, Unknown unicast and Multicast (BUM) 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 Network Virtualization Overlay core network. Ingress Replication avoids the dependency on PIM in the Network Virtualization Overlay network core. While Ingress Replication provides a simple multicast transport, some Network Virtualization Overlay 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.}, }