File formats:

Status:

EXPERIMENTAL

Updated by:

RFC 8736, RFC 9436

Authors:

IJ. Wijnands
S. Venaas
M. Brig
A. Jonasson

Stream:

IETF

Source:

pim (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8364

Discuss this RFC: Send questions or comments to the mailing list pim@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8364

Abstract

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.