RFC 8775: PIM Designated Router Load Balancing
In plain English — editorial summary, not part of the RFC
On a multi-access network, one of the PIM-SM (PIM Sparse Mode) routers is elected as a Designated Router. One of the responsibilities of the Designated Router is to track local multicast listeners and forward data to these listeners if the group is operating in PIM-SM. This document specifies a modification to the PIM-SM protocol that allows more than one of the PIM-SM routers to take on this responsibility so that the forwarding load can be distributed among multiple routers.
Document record
- Document ID
- RFC8775
- Published
- April 2020
- Authors
- Y. Cai; H. Ou; S. Vallepalli; M. Mishra; S. Venaas; A. Green
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8736PIM Message Type Space Extension and Reserved BitsObsoleted
February 2020
- RFC 8652A YANG Data Model for the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)Current
November 2019
- RFC 8564Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)Current
April 2019
- RFC 8556Multicast VPN Using Bit Index Explicit Replication (BIER)Current
April 2019
- RFC 9166A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) SnoopingCurrent
February 2022
- RFC 8364PIM Flooding Mechanism (PFM) and Source Discovery (SD)Updated
March 2018
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
- RFC 9262Tree Engineering for Bit Index Explicit Replication (BIER-TE)Current
October 2022
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?