Browse Prior Art Database

Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS) (RFC8220) Disclosure Number: IPCOM000250896D
Original Publication Date: 2017-Sep-01
Included in the Prior Art Database: 2017-Sep-13
Document File: 86 page(s) / 89K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

O. Dornon: AUTHOR [+4]


In the Virtual Private LAN Service (VPLS), the Provider Edge (PE) devices provide a logical interconnect such that Customer Edge (CE) devices belonging to a specific VPLS instance appear to be connected by a single LAN. The Forwarding Information Base (FIB) for a VPLS instance is populated dynamically by Media Access Control (MAC) address learning. Once a unicast MAC address is learned and associated with a particular Attachment Circuit (AC) or pseudowire (PW), a frame destined to that MAC address only needs to be sent on that AC or PW.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                         O. Dornon Request for Comments: 8220                                   J. Kotalwar Category: Informational                                        V. Hemige ISSN: 2070-1721                                                    Nokia                                                                   R. Qiu                                                                                                                      Z. Zhang                                                   Juniper Networks, Inc.                                                           September 2017

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


   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.

Dornon, et al.                Informational                     [Page 1]
 RFC 8220                      PIM Snooping                September 2017

 Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community. ...