Skip to main content

PIM Null-Register Packing
RFC 9465

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['Multicast']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "A. Gopal": changed name from "Ananya Gopal" to "A. Gopal", cleared country (was "USA")
2026-05-20
(System) Changed author "R. Banthia": changed name from "Raunak Banthia" to "R. Banthia", cleared country (was "USA")
2026-05-20
(System) Changed author "R. Chokkanathapuram Sundaram": changed name from "Ramakrishnan Sundaram" to "R. Chokkanathapuram Sundaram", cleared country (was "USA")
2026-05-20
(System) Changed author "V. Kamath": changed name from "Vikas Kamath" to "V. Kamath", cleared country (was "USA")
2026-05-20
(System) Metadata update from RFC Editor
2023-09-29
(System)
Received changes through RFC Editor sync (created alias RFC 9465, changed title to 'PIM Null-Register Packing', changed abstract to 'In PIM Sparse Mode (PIM-SM) …
Received changes through RFC Editor sync (created alias RFC 9465, changed title to 'PIM Null-Register Packing', changed abstract to 'In PIM Sparse Mode (PIM-SM) networks, PIM Null-Register messages are sent by the Designated Router (DR) to the Rendezvous Point (RP) to signal the presence of multicast sources in the network. There are periodic PIM Null-Registers sent from the DR to the RP to keep the state alive at the RP as long as the source is active. The PIM Null-Register message carries information about a single multicast source and group.

This document defines a standard to send information about multiple multicast sources and groups in a single PIM message. This document refers to the new messages as the "PIM Packed Null-Register message" and "PIM Packed Register-Stop message".', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-09-29, changed IESG state to RFC Published)
2023-09-29
(System) RFC published