PIM Proxy in EVPN Networks
draft-skr-bess-evpn-pim-proxy-01

Document Type Expired Internet-Draft (bess WG)
Last updated 2018-05-03 (latest revision 2017-10-30)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Revised I-D Needed - Issue raised by WG
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-skr-bess-evpn-pim-proxy-01.txt

Abstract

Ethernet Virtual Private Networks [RFC7432] are becoming prevalent in Data Centers, Data Center Interconnect (DCI) and Service Provider VPN applications. One of the goals that EVPN pursues is the reduction of flooding and the efficiency of CE-based control plane procedures in Broadcast Domains. Examples of this are Proxy ARP/ND and IGMP/MLD Proxy. This document complements the latter, describing the procedures required to minimize the flooding of PIM messages in EVPN Broadcast Domains, and optimize the IP Multicast delivery between PIM routers.

Authors

Jorge Rabadan (jorge.rabadan@nokia.com)
Jayant Kotalwar (jayant.kotalwar@nokia.com)
Senthil Sathappan (senthil.sathappan@nokia.com)
Zhaohui Zhang (zzhang@juniper.net)
Ali Sajassi (sajassi@cisco.com)

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