RFC 8736 · PROPOSED STANDARD · 2020

PIM Message Type Space Extension and Reserved Bits

Overview

RFC 8736, “PIM Message Type Space Extension and Reserved Bits”, is a Proposed Standard document published in February 2020 by S. Venaas, A. Retana. It updates RFC 3973, RFC 5015, RFC 5059, RFC 6754, RFC 7761, RFC 8364. It obsoletes RFC 6166. It has been obsoleted by RFC 9436 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.

Abstract

The PIM version 2 messages share a common message header format. The common header definition contains eight reserved bits. This document specifies how these bits may be used by individual message types and creates a registry containing the per-message-type usage. This document also extends the PIM type space by defining three new message types. For each of the new types, four of the previously reserved bits are used to form an extended type range.

This document updates RFCs 7761 and 3973 by defining the use of the currently Reserved field in the PIM common header. This document further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754, and 8364, by specifying the use of the currently reserved bits for each PIM message.

This document obsoletes RFC 6166.

Abstract as published in the RFC, via rfc-editor.org.

What “Proposed Standard” means

An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.

Read this RFC

The canonical text of RFC 8736 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.

Relationships to other RFCs
This RFC obsoletes
RFC 6166
Obsoleted by
RFC 9436
Other RFCs from 2020

Who Is Online

In total there are 41 users online: 0 registered, 34 guests and 7 bots.

Most users ever online was 1,226 on 13 Jun 2026, 3:56 am.

Bots: AhrefsBot Applebot Bingbot Googlebot Other Bot SemrushBot Sogou

Users active in the past 15 minutes. Total registered members: 354