Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)

Document Type Replaced Internet-Draft (pals WG)
Authors Olivier Dornon  , Jayant Kotalwar  , Venu Hemige  , Ray Qiu 
Last updated 2016-10-10 (latest revision 2014-10-24)
Replaces draft-hemige-serbest-l2vpn-vpls-pim-snooping
Replaced by RFC 8220
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-pals-vpls-pim-snooping
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


This document describes the procedures and recommendations for Virtual Private LAN Service (VPLS) Provider Edges (PEs) to facilitate replication of multicast traffic to only certain ports (behind which there are interested Protocol Independent Multicast (PIM) routers and/or Internet Group Management Protocol (IGMP) hosts) via Protocol Independent Multicast (PIM) snooping and proxying. With PIM snooping, PEs passively listen to certain PIM control messages to build control and forwarding states while transparently flooding those messages. With PIM proxying, Provider Edges (PEs) do not flood PIM Join/Prune messages but only generate their own and send out of certain ports, based on the control states built from downstream Join/Prune messages. PIM proxying is required when PIM Join suppression is enabled on the Customer Equipment (CE) devices and useful to reduce PIM control traffic in a VPLS domain. The document also describes PIM relay, which can be viewed as light- weight proxying, where all downstream Join/Prune messages are simply forwarded out of certain ports but not flooded to avoid triggering PIM Join suppression on CE devices.


Olivier Dornon (
Jayant Kotalwar (
Venu Hemige (
Ray Qiu (

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