Optimized Ingress Replication solution for EVPN
draft-rabadan-bess-evpn-optimized-ir-02
| Document | Type |
Replaced Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jorge Rabadan , Senthil Sathappan , Wim Henderickx , Ali Sajassi , Aldrin Isaac | ||
| 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 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-bess-evpn-optimized-ir | |
| Consensus boilerplate | Yes | ||
| 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:
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
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.)