RFC 9466: PIM Assert Message Packing
In plain English — editorial summary, not part of the RFC
When PIM Sparse Mode (PIM-SM), including PIM Source-Specific Multicast (PIM-SSM), is used in shared LAN networks, there is often more than one upstream router. This can lead to duplicate IP multicast packets being forwarded by these PIM routers. PIM Assert messages are used to elect a single forwarder for each IP multicast traffic flow between these routers. This document defines a mechanism to send and receive information for multiple IP multicast flows in a single PackedAssert message. This optimization reduces the total number of PIM packets on the LAN and can therefore speed up the election of the single forwarder, reducing the number of duplicate IP multicast packets incurred.
Document record
- Document ID
- RFC9466
- Published
- October 2023
- Authors
- Y. Liu; T. Eckert; M. McBride; Z. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9465PIM Null-Register PackingCurrent
September 2023
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 9468Unsolicited Bidirectional Forwarding Detection (BFD) for Sessionless ApplicationsCurrent
August 2023
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9454Update to OSPF TerminologyCurrent
August 2023
- RFC 9479IS-IS Application-Specific Link AttributesCurrent
October 2023
- RFC 9452Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) DataCurrent
August 2023
- RFC 9451Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)Current
August 2023
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?