Optimized Ingress Replication solution for EVPN
draft-rabadan-l2vpn-evpn-optimized-ir-00

Document Type Replaced Internet-Draft (individual)
Last updated 2014-10-27 (latest revision 2014-07-04)
Replaced by draft-rabadan-bess-evpn-optimized-ir
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
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
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rabadan-l2vpn-evpn-optimized-ir-00.txt

Abstract

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.

Authors

Jorge Rabadan (jorge.rabadan@alcatel-lucent.com)
Senthil Sathappan (senthil.sathappan@alcatel-lucent.com)
Wim Henderickx (wim.henderickx@alcatel-lucent.com)

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