metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 8736: PIM Message Type Space Extension and Reserved Bits

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9436.

Current document in this lineage: RFC 9436 — PIM Message Type Space Extension and Reserved Bits

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8736
Published
February 2020
Authors
S. Venaas; A. Retana
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
8
Also known as
—
Obsoletes:
RFC 6166
Obsoleted by:
RFC 9436
Updates:
RFC 3973, RFC 5015, RFC 5059, RFC 6754, RFC 7761, RFC 8364

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 6166 (2011)
  2. RFC 8736 (2020)
  3. RFC 9436 (2023) ✓

Read the full history of PIM Message Type Space Extension and Reserved Bits →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8736-pim-message-type-space-extension-and-reserved-bits