IGMP and MLD Proxy for EVPN
draft-ietf-bess-evpn-igmp-mld-proxy-02
| Document | Type | Expired Internet-Draft (bess WG) | |
|---|---|---|---|
| Last updated | 2018-12-27 (latest revision 2018-06-25) | ||
| Replaces | draft-sajassi-bess-evpn-igmp-mld-proxy | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-bess-evpn-igmp-mld-proxy-02.txt
Abstract
Ethernet Virtual Private Network (EVPN) solution [RFC 7432] is becoming pervasive in data center (DC) applications for Network Virtualization Overlay (NVO) and DC interconnect (DCI) services, and in service provider (SP) applications for next generation virtual private LAN services. This draft describes how to support efficiently endpoints running IGMP for the above services over an EVPN network by incorporating IGMP proxy procedures on EVPN PEs.
Authors
Ali Sajassi
(sajassi@cisco.com)
Samir Thoria
(sthoria@cisco.com)
Keyur Patel
(keyur@arrcus.com)
Derek Yeung
(derek@arrcus.com)
John Drake
(jdrake@juniper.net)
Wen Lin
(wlin@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)