metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6166: A Registry for PIM Message Types

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

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

This document provides instructions to IANA for the creation of a registry for PIM message types. It specifies the initial content of the registry, based on existing RFCs specifying PIM message types. It also specifies a procedure for registering new types. In addition to this, one message type is reserved, and may be used for a future extension of the message type space. [STANDARDS-TRACK]

Document record

Document ID
RFC6166
Published
April 2011
Authors
S. Venaas
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
4
Also known as
—
Obsoleted by:
RFC 8736

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/6166-a-registry-for-pim-message-types