| Internet-Draft | IGMP IANA | October 2023 |
| Haberman | Expires 25 April 2024 | [Page] |
This document specifies revised IANA Considerations for the Internet Group Management Protocol and the Multicast Listener Discovery protocol. This document specifies the guidance provided to IANA to manage values associated with various fields within the protocol headers of the group management protocols.¶
This document obsoletes RFC 3228 and updates RFC 4443.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 April 2024.¶
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.¶
The following sections describe the allocation guidelines associated with the specified fields within the Internet Group Management Protocol (IGMP) [I-D.ietf-pim-3376bis] and the Multicast Listener Discovery (MLD) [I-D.ietf-pim-3810bis] headers. Some of these registries were created previously, while others are created by this document.¶
This document obsoletes [RFC3228] and updates [RFC4443].¶
The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].¶
The registration procedures used in this document are defined in [RFC8126].¶
The IGMP header contains the following fields that carry values assigned from IANA-managed name spaces: Type and Code. Code field values are defined relative to a specific Type value.¶
[RFC3228] created an IANA registry for the IGMP Type field. This document updates that registry in two ways:¶
[RFC3228] created an IANA registry for Code values for existing IGMP Type fields. The registration procedure for the existing registries is changed to Standards Action. The policy for assigning Code values for new IGMP Types MUST be defined in the document defining the new Type value.¶
As with IGMP, the MLD header also contains Type and Code fields. Assignment of those fields within the MLD header is defined in [RFC4443].¶
The IANA is requested to create a single registry for the bits in the Flags field of the Multicast Listener Query Message [I-D.ietf-pim-3810bis] and the IGMPv3 Query Message [I-D.ietf-pim-3376bis]. The format for the registry is:¶
+----------+------------+-------------+-----------+ | Resv Bit | Short Name | Description | Reference | +----------+------------+-------------+-----------+ | 0 | | | | | 1 | | | | | 2 | | | | | 3 | | | | +----------+------------+-------------+-----------+¶
The assignment of new bit flags within the Flags field requires Standards Action.¶
The IANA is requested to create a single registry for the bits in the Flags field of the Multicast Listener Report Message and the IGMPv3 Report Message. The format for the registry is:¶
+-----------+------------+-------------+-----------+ | Flags Bit | Short Name | Description | Reference | +-----------+------------+-------------+-----------+ | 0 | | | | | 1 | | | | | 2 | | | | | 3 | | | | | 4 | | | | | 5 | | | | | 6 | | | | | 7 | | | | | 8 | | | | | 9 | | | | | 10 | | | | | 11 | | | | | 12 | | | | | 13 | | | | | 14 | | | | | 15 | | | | +-----------+------------+-------------+-----------+¶
The assignment of new bit flags within the Flags field require Standards Action.¶
This document only defines IANA registy actions and there are no associated security issues.¶
Bill Fenner was the author of RFC 3228, which forms a portion of the content contained herein.¶