PIM Message Type Space Extension and Reserved Bits
RFC 8736

Received changes through RFC Editor sync (created alias RFC 8736, changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-02-29, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-pim-reserved-bits and RFC 6166, created updates relation between draft-ietf-pim-reserved-bits and RFC 3973, created updates relation between draft-ietf-pim-reserved-bits and RFC 5015, created updates relation between draft-ietf-pim-reserved-bits and RFC 5059, created updates relation between draft-ietf-pim-reserved-bits and RFC 6754, created updates relation between draft-ietf-pim-reserved-bits and RFC 7761, created updates relation between draft-ietf-pim-reserved-bits and RFC 8364)