Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
RFC 8220
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['multicast']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "Z. Zhang": changed name from "Zhaohui Zhang" to "Z. Zhang", changed order from "4" to "5" |
|
2026-05-20
|
(System) | Changed author "R. Qiu": changed name from "Ray Qiu" to "R. Qiu", changed order from "3" to "4" |
|
2026-05-20
|
(System) | Changed author "V. Hemige": changed name from "Venu Hemige" to "V. Hemige", set affiliation to "Nokia", changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "J. Kotalwar": changed name from "Jayant Kotalwar" to "J. Kotalwar", changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "O. Dornon": changed name from "Olivier Dornon" to "O. Dornon", changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes the procedures and recommendations for Virtual Private LAN Service (VPLS) Provider Edges (PEs) … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2017-09-12
|
(System) | Received changes through RFC Editor sync (created alias RFC 8220, changed abstract to 'This document describes the procedures and recommendations for Virtual Private LAN … Received changes through RFC Editor sync (created alias RFC 8220, changed abstract to '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.', changed pages to 43, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-09-12, changed IESG state to RFC Published) |
|
2017-09-12
|
(System) | RFC published |