EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding
draft-lin-bess-evpn-irb-mcast-04
Document | Type | Replaced Internet-Draft (candidate for bess WG) | |
---|---|---|---|
Authors | Wen Lin , Zhaohui Zhang , John Drake , Eric Rosen , Jorge Rabadan , Ali Sajassi | ||
Last updated | 2018-04-27 (latest revision 2017-10-24) | ||
Replaced by | draft-ietf-bess-evpn-irb-mcast | ||
Stream | IETF | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | Replaced by draft-ietf-bess-evpn-irb-mcast | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-lin-bess-evpn-irb-mcast-04.txt
Abstract
Ethernet VPN (EVPN) provides a service that allows a single Local Area Network (LAN), i.e., a single IP subnet, to be distributed over multiple sites. The sites are interconnected by an IP or MPLS backbone. Intra-subnet traffic (either unicast or multicast) always appears to the endusers to be bridged, even when it is actually carried over the IP backbone. When a single "tenant" owns multiple such LANs, EVPN also allows IP unicast traffic to be routed between those LANs. This document specifies new procedures that allow inter- subnet IP multicast traffic to be routed among the LANs of a given tenant, while still making intra-subnet IP multicast traffic appear to be bridged. These procedures can provide optimal routing of the inter-subnet multicast traffic, and do not require any such traffic to leave a given router and then reenter that same router. These procedures also accommodate IP multicast traffic that needs to travel to or from systems that are outside the EVPN domain.
Authors
Wen Lin
(wlin@juniper.net)
Zhaohui Zhang
(zzhang@juniper.net)
John Drake
(jdrake@juniper.net)
Eric Rosen
(erosen@juniper.net)
Jorge Rabadan
(jorge.rabadan@nokia.com)
Ali Sajassi
(sajassi@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)