RFC 8364: PIM Flooding Mechanism (PFM) and Source Discovery (SD)
In plain English — editorial summary, not part of the RFC
Protocol Independent Multicast - Sparse Mode (PIM-SM) uses a Rendezvous Point (RP) and shared trees to forward multicast packets from new sources. Once Last-Hop Routers (LHRs) receive packets from a new source, they may join the Shortest Path Tree (SPT) for the source for optimal forwarding. This document defines a new mechanism that provides a way to support PIM-SM without the need for PIM registers, RPs, or shared trees. Multicast source information is flooded throughout the multicast domain using a new generic PIM Flooding Mechanism (PFM). This allows LHRs to learn about new sources without receiving initial data packets.
Document record
- Document ID
- RFC8364
- Published
- March 2018
- Authors
- IJ. Wijnands; S. Venaas; M. Brig; A. Jonasson
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
- RFC 8279Multicast Using Bit Index Explicit Replication (BIER)Current
November 2017
- RFC 8220Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)Current
September 2017
- RFC 8556Multicast VPN Using Bit Index Explicit Replication (BIER)Current
April 2019
- RFC 8564Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)Current
April 2019
- RFC 8652A YANG Data Model for the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)Current
November 2019
- RFC 7968Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination DataCurrent
August 2016
- RFC 8775PIM Designated Router Load BalancingCurrent
April 2020
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?