RFC 5384: The Protocol Independent Multicast (PIM) Join Attribute Format

A "Protocol Independent Multicast - Sparse Mode" Join message sent by a given node identifies one or more multicast distribution trees that that node wishes…

Read RFC 5384 on the RFC Editor

Outgoing relationships (5 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 5015: Bidirectional Protocol Independent Multicast (BIDIR-PIM)
Informative reference — RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)

Incoming relationships (9 related RFCs)

Updated by, Normatively referenced by — RFC 7887: Hierarchical Join/Prune Attributes
Normatively referenced by — RFC 6513: Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 6037: Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs
Normatively referenced by — RFC 6420: PIM Multi-Topology ID (MT-ID) Join Attribute
Normatively referenced by — RFC 6807: Population Count Extensions to Protocol Independent Multicast (PIM)
Normatively referenced by — RFC 7891: Explicit Reverse Path Forwarding (RPF) Vector
Normatively referenced by — RFC 8220: Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)
Normatively referenced by — RFC 9798: PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast
Normatively referenced by — RFC 9860: Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast Reroute