Optimized Ingress Replication solution for EVPN
draft-rabadan-bess-evpn-optimized-ir-02

Document Type Replaced Internet-Draft (bess WG)
Last updated 2016-02-06 (latest revision 2016-01-25)
Replaces draft-rabadan-l2vpn-evpn-optimized-ir
Replaced by draft-ietf-bess-evpn-optimized-ir
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-evpn-optimized-ir
Consensus Boilerplate Yes
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-bess-evpn-optimized-ir-02.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@nokia.com)
Senthil Sathappan (senthil.sathappan@nokia.com)
Wim Henderickx (wim.henderickx@nokia.com)
Ali Sajassi (sajassi@cisco.com)
Aldrin Isaac (aisaac@juniper.net)

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