ietf-corpus from Lantern
rfc-6166

A Registry for PIM Message Types

S. Venaas
date2011-04 streamIETF areartg wgpim statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc6166 doi10.17487/RFC6166
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]

obsoleted by

Extracted elements (7)

design-rationale §1

PIM version 2 is not based on IGMP (unlike PIM version 1), so it requires its own separate message type registry rather than reusing the existing IGMP registry.

multicast

design-rationale §1

Type 15 is reserved for a future extension of the message type space because the current 4-bit type field allows only 16 values, making exhaustion plausible. The mechanism for extension is left to a future document.

multicast, registry

normative-requirement §3.2 REQUIRED

Assignment of new PIM message types MUST follow the 'IETF Review' model as defined in RFC 5226.

registry, multicast, process

protocol-element §3

The PIM message type field is a 4-bit integer with possible values from 0 to 15, defining the type of each PIM version 2 message.

multicast

registry §3

IANA has created a PIM message type registry placed in the 'Protocol Independent Multicast (PIM)' branch. Each entry consists of a 4-bit integer message type (values 0–15), a message name, and references to defining documents.

registry, multicast

registry §3.1

Initial registry content assigns types 0–10 to named PIM messages (Hello, Register, Register Stop, Join/Prune, Bootstrap, Assert, Graft, Graft-Ack, Candidate RP Advertisement, State Refresh, DF Election), leaves 11–14 unassigned, and reserves type 15 for future extension of the type space.

registry, multicast

security-consideration §2

This document only creates an IANA registry. A well-known location for information on valid PIM message types provides a minor security benefit, but there are no other security considerations.

security, multicast, registry