A Registry for PIM Message Typescisco SystemsTasman DriveSan JoseCA95134USAstig@cisco.comThis document provides instructions to IANA for the creation of
a registry for PIM message types. It specifies 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.Apart from this document, there is no existing document
specifying a registry for PIM message types. PIM version 1 made use of IGMP
and there is an IGMP registry
listing the message types used by PIM version 1. PIM version 2 however is not
based on IGMP, and a separate PIM message type registry is needed. There are
currently several RFCs specifying new PIM version 2 message types that should
be in this new registry. They are the RFCs for PIM Dense Mode
, PIM Sparse Mode and
Bidirectional PIM .
This document specifies the initial content of the new PIM message type
registry based on those existing RFCs. This document also specifies a
procedure for registering new PIM message types.In addition to this, this document reserves one message type. This type
may be used for a future extension of the message type space. How
exactly the extension should be done is left to a future document.This document only creates an IANA registry. There may be a
security benefit in a well-known place for finding information on which
PIM message types are valid and what they mean. Apart from that there are
no security considerations.This document requests IANA to create a PIM message type
registry. This should be placed in the "Protocol Independent Multicast (PIM)"
branch of the tree. Each entry in the registry consists of message type,
message name and references to the documents defining the type.The initial content of the registry should be as follows.
Assignment of new message types is done according to the "IETF Review"
model, see [RFC5226].Thanks to Toerless Eckert for his suggestion to reserve a type
for future message type space extension.IGMP Type Numbers