Skip to main content

IANA Considerations for Internet Group Management Protocols
draft-haberman-pim-3228bis-00

Document Type Active Internet-Draft (individual)
Author Brian Haberman
Last updated 2022-04-15
Stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-haberman-pim-3228bis-00
Network Working Group                                   B. Haberman, Ed.
Internet-Draft                                                   JHU APL
Obsoletes: 3228 (if approved)                                 April 2022
Updates: 4443 (if approved)                                             
Intended status: Best Current Practice                                  
Expires: 14 October 2022

      IANA Considerations for Internet Group Management Protocols
                     draft-haberman-pim-3228bis-00

Abstract

   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.

Status of This Memo

   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 3 October 2022.

Copyright Notice

   Copyright (c) 2022 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

Haberman                 Expires 14 October 2022                [Page 1]
Internet-Draft                  IGMP IANA                     April 2022

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Type and Code Fields  . . . . . . . . . . . . . . . . . .   2
       2.1.1.  Internet Group Management Protocol  . . . . . . . . .   3
       2.1.2.  Multicast Listener Discovery  . . . . . . . . . . . .   3
     2.2.  Query Message Flags . . . . . . . . . . . . . . . . . . .   3
     2.3.  Report Message Flags  . . . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   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].

2.  IANA Considerations

   The registration procedures used in this document are defined in
   [RFC8126].

2.1.  Type and Code Fields

Haberman                 Expires 14 October 2022                [Page 2]
Internet-Draft                  IGMP IANA                     April 2022

2.1.1.  Internet Group Management Protocol

   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:

      The registration procedure is changed to Standards Action.

      The reference for the registry is changed to this document.

   [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.

2.1.2.  Multicast Listener Discovery

   As with IGMP, the MLD header also contains Type and Code fields.
   Assignment of those fields within the MLD header is defined in
   [RFC4443].

2.2.  Query Message Flags

   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.

Haberman                 Expires 14 October 2022                [Page 3]
Internet-Draft                  IGMP IANA                     April 2022

2.3.  Report Message Flags

   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.

3.  Security Considerations

   This document only defines IANA registy actions and there are no
   associated security issues.

4.  Contributors

   Bill Fenner was the author of RFC 3228, which forms a portion of the
   content contained herein.

5.  Acknowledgments

6.  References

6.1.  Normative References

Haberman                 Expires 14 October 2022                [Page 4]
Internet-Draft                  IGMP IANA                     April 2022

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3228]  Fenner, B., "IANA Considerations for IPv4 Internet Group
              Management Protocol (IGMP)", BCP 57, RFC 3228,
              DOI 10.17487/RFC3228, February 2002,
              <https://www.rfc-editor.org/info/rfc3228>.

   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/info/rfc8126>.

6.2.  Informative References

   [I-D.ietf-pim-3376bis]
              Haberman, B., "Internet Group Management Protocol, Version
              3", Work in Progress, Internet-Draft, draft-ietf-pim-
              3376bis-01, 25 October 2021,
              <https://www.ietf.org/archive/id/draft-ietf-pim-3376bis-
              01.txt>.

   [I-D.ietf-pim-3810bis]
              Haberman, B., "Multicast Listener Discovery Version 2
              (MLDv2) for IPv6", Work in Progress, Internet-Draft,
              draft-ietf-pim-3810bis-01, 25 October 2021,
              <https://www.ietf.org/archive/id/draft-ietf-pim-3810bis-
              01.txt>.

   [RFC4443]  Conta, A., Deering, S., and M. Gupta, Ed., "Internet
              Control Message Protocol (ICMPv6) for the Internet
              Protocol Version 6 (IPv6) Specification", STD 89,
              RFC 4443, DOI 10.17487/RFC4443, March 2006,
              <https://www.rfc-editor.org/info/rfc4443>.

Author's Address

   Brian Haberman (editor)
   Johns Hopkins University Applied Physics Lab
   Email: brian@innovationslab.net

Haberman                 Expires 14 October 2022                [Page 5]