Status of This Memo

This is an Internet Standards Track document.¶

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9436.¶

Copyright Notice

Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

The PIM version 2 messages share a common message header format defined in the PIM Sparse Mode specification [RFC7761]. The common header definition contains eight reserved bits. While all message types use this common header, there is no document formally specifying that these bits are to be used per message type.¶

This document updates the definition of the Reserved field and refers to it as the "Flag Bits field". It specifies that the flag bits are to be separately used on a per-message-type basis. It updates the "PIM Message Types" registry to indicate the per-message-type usage.¶

This document updates [RFC7761] and [RFC3973] by defining the use of the Reserved field in the PIM common header. This document further updates [RFC7761] and [RFC3973], along with [RFC5015], [RFC5059], [RFC6754], and [RFC8364], by specifying the use of the bits for each PIM message.¶

The originally defined PIM message types were in the range from 0 to 15. Message type 15 had been reserved by [RFC6166] for type space extension. In Section 5, this document specifies the use of the Flag Bits field for message types 13, 14, and 15 in order to extend the PIM type space. The type space extension in [RFC6166] was made obsolete by [RFC8736]. This document obsoletes [RFC8736].¶

4. Flag Bit Definitions

Unless otherwise specified, all the flag bits for each PIM type are Unassigned [RFC8126]. They MUST be set to zero on transmission, and they MUST be ignored upon receipt. The specification of a new PIM type MUST indicate whether the bits should be treated differently.¶

When defining flag bits, it is helpful to have a well-defined way of referring to a particular bit. The most significant of the flag bits, the bit immediately following the Type field, is referred to as bit 7. The least significant, the bit right in front of the Checksum field, is referred to as bit 0. This is shown in the diagram below.¶

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|PIM Ver| Type  |7 6 5 4 3 2 1 0|           Checksum            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

5. PIM Type Space Extension

This document extends types 13, 14, and 15 such that each becomes 16 new types, resulting in 48 types available for future PIM extensions. This extension is achieved by defining a Subtype field (see Figure 3) using the four most significant flag bits (bits 4-7). The notation type.subtype is used to reference the new extended types. The remaining four flag bits (bits 0-3, abbreviated as FB below) are to be defined by each extended type.¶

Each of the extended types is represented by the eight bits resulting from the concatenation of the Type and Subtype fields. No relationship is expected or implied between extended type messages with a common Type field.¶

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|PIM Ver| Type  |Subtype|  FB   |           Checksum            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

7. IANA Considerations

This document updates the "PIM Message Types" registry to indicate which flag bits are defined for use by each of the PIM message types and changes their registration status to Unassigned except where the bits have already been specified, as shown in Table 1. The registration policy remains IETF Review [RFC8126]. Assignments to this registry MUST define any non-default usage (see Section 4) of the flag bits in addition to the type.¶

Extended type 15.15 is Reserved [RFC8126] for future extensions.¶

Because this document obsoletes [RFC8736], IANA has changed the references to [RFC8736] in the registry to point to this document instead.¶

The updated "PIM Message Types" registry is shown below.¶

The unassigned types above, as explained in Section 5, use the extended type notation of type.subtype. Each extended type only has 4 flag bits available. New extended message types should be assigned consecutively, starting with 13.0, then 13.1, etc.¶

Authors' Addresses