RFC 8220: Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
In plain English — editorial summary, not part of the RFC
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 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, PEs do not flood PIM Join/Prune messages but only generate their own and send them 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 Edge (CE) devices and is useful for reducing PIM control traffic in a VPLS domain. This document also describes PIM relay, which can be viewed as lightweight proxying, where all downstream Join/Prune messages are simply forwarded out of certain ports and are not flooded, thereby avoiding the triggering of PIM Join suppression on CE devices.
Document record
- Document ID
- RFC8220
- Published
- September 2017
- Authors
- O. Dornon; J. Kotalwar; V. Hemige; R. Qiu; Z. Zhang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8279Multicast Using Bit Index Explicit Replication (BIER)Current
November 2017
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
- RFC 8364PIM Flooding Mechanism (PFM) and Source Discovery (SD)Updated
March 2018
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 7900Extranet Multicast in BGP/IP MPLS VPNsUpdated
June 2016
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 8556Multicast VPN Using Bit Index Explicit Replication (BIER)Current
April 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?