Search RFCs
RFC 9436
PIM Message Type Space Extension and Reserved Bits,August 2023
- File formats:
- Also available:XML file for editing
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 8736
- Updates:
- RFC 3973,RFC 5015,RFC 5059,RFC 6754,RFC 7761,RFC 8364
- Authors:
- S. Venaas
A. Retana - Stream:
- IETF
- Source:
- pim (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9436
Discuss this RFC: Send questions or comments to the mailing listpim@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9436
Abstract
The PIM version 2 messages share a common message header format. Thecommon header definition contains eight reserved bits. This documentspecifies how these bits may be used by individual message types andextends the PIM type space.
This document updates RFCs 7761 and 3973 by defining the use of theReserved field in the PIM common header. This document furtherupdates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754, and8364, by specifying the use of the bits for each PIM message.
This document obsoletes RFC 8736.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.