idnits 2.17.1 draft-haberman-pim-3228bis-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (Using the creation date from RFC4443, updated by this document, for RFC5378 checks: 1999-06-29) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2022) is 732 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-08) exists of draft-ietf-pim-3376bis-01 == Outdated reference: A later version (-08) exists of draft-ietf-pim-3810bis-01 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Haberman, Ed. 3 Internet-Draft JHU APL 4 Obsoletes: 3228 (if approved) April 2022 5 Updates: 4443 (if approved) 6 Intended status: Best Current Practice 7 Expires: 14 October 2022 9 IANA Considerations for Internet Group Management Protocols 10 draft-haberman-pim-3228bis-00 12 Abstract 14 This document specifies revised IANA Considerations for the Internet 15 Group Management Protocol and the Multicast Listener Discovery 16 protocol. This document specifies the guidance provided to IANA to 17 manage values associated with various fields within the protocol 18 headers of the group management protocols. 20 This document obsoletes RFC 3228 and updates RFC 4443. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on 3 October 2022. 39 Copyright Notice 41 Copyright (c) 2022 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 46 license-info) in effect on the date of publication of this document. 47 Please review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. Code Components 49 extracted from this document must include Revised BSD License text as 50 described in Section 4.e of the Trust Legal Provisions and are 51 provided without warranty as described in the Revised BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 57 2.1. Type and Code Fields . . . . . . . . . . . . . . . . . . 2 58 2.1.1. Internet Group Management Protocol . . . . . . . . . 3 59 2.1.2. Multicast Listener Discovery . . . . . . . . . . . . 3 60 2.2. Query Message Flags . . . . . . . . . . . . . . . . . . . 3 61 2.3. Report Message Flags . . . . . . . . . . . . . . . . . . 4 62 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 4. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 4 64 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 65 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 67 6.2. Informative References . . . . . . . . . . . . . . . . . 5 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 70 1. Introduction 72 The following sections describe the allocation guidelines associated 73 with the specified fields within the Internet Group Management 74 Protocol (IGMP) [I-D.ietf-pim-3376bis] and the Multicast Listener 75 Discovery (MLD) [I-D.ietf-pim-3810bis] headers. Some of these 76 registries were created previously, while others are created by this 77 document. 79 This document obsoletes [RFC3228] and updates [RFC4443]. 81 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 82 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 83 "OPTIONAL" in this document are to be interpreted as described in 84 [RFC2119]. 86 2. IANA Considerations 88 The registration procedures used in this document are defined in 89 [RFC8126]. 91 2.1. Type and Code Fields 92 2.1.1. Internet Group Management Protocol 94 The IGMP header contains the following fields that carry values 95 assigned from IANA-managed name spaces: Type and Code. Code field 96 values are defined relative to a specific Type value. 98 [RFC3228] created an IANA registry for the IGMP Type field. This 99 document updates that registry in two ways: 101 The registration procedure is changed to Standards Action. 103 The reference for the registry is changed to this document. 105 [RFC3228] created an IANA registry for Code values for existing IGMP 106 Type fields. The registration procedure for the existing registries 107 is changed to Standards Action. The policy for assigning Code values 108 for new IGMP Types MUST be defined in the document defining the new 109 Type value. 111 2.1.2. Multicast Listener Discovery 113 As with IGMP, the MLD header also contains Type and Code fields. 114 Assignment of those fields within the MLD header is defined in 115 [RFC4443]. 117 2.2. Query Message Flags 119 The IANA is requested to create a single registry for the bits in the 120 Flags field of the Multicast Listener Query Message 121 [I-D.ietf-pim-3810bis] and the IGMPv3 Query Message 122 [I-D.ietf-pim-3376bis]. The format for the registry is: 124 +----------+------------+-------------+-----------+ 125 | Resv Bit | Short Name | Description | Reference | 126 +----------+------------+-------------+-----------+ 127 | 0 | | | | 128 | 1 | | | | 129 | 2 | | | | 130 | 3 | | | | 131 +----------+------------+-------------+-----------+ 133 The assignment of new bit flags within the Flags field requires 134 Standards Action. 136 2.3. Report Message Flags 138 The IANA is requested to create a single registry for the bits in the 139 Flags field of the Multicast Listener Report Message and the IGMPv3 140 Report Message. The format for the registry is: 142 +-----------+------------+-------------+-----------+ 143 | Flags Bit | Short Name | Description | Reference | 144 +-----------+------------+-------------+-----------+ 145 | 0 | | | | 146 | 1 | | | | 147 | 2 | | | | 148 | 3 | | | | 149 | 4 | | | | 150 | 5 | | | | 151 | 6 | | | | 152 | 7 | | | | 153 | 8 | | | | 154 | 9 | | | | 155 | 10 | | | | 156 | 11 | | | | 157 | 12 | | | | 158 | 13 | | | | 159 | 14 | | | | 160 | 15 | | | | 161 +-----------+------------+-------------+-----------+ 163 The assignment of new bit flags within the Flags field require 164 Standards Action. 166 3. Security Considerations 168 This document only defines IANA registy actions and there are no 169 associated security issues. 171 4. Contributors 173 Bill Fenner was the author of RFC 3228, which forms a portion of the 174 content contained herein. 176 5. Acknowledgments 178 6. References 180 6.1. Normative References 182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 183 Requirement Levels", BCP 14, RFC 2119, 184 DOI 10.17487/RFC2119, March 1997, 185 . 187 [RFC3228] Fenner, B., "IANA Considerations for IPv4 Internet Group 188 Management Protocol (IGMP)", BCP 57, RFC 3228, 189 DOI 10.17487/RFC3228, February 2002, 190 . 192 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 193 Writing an IANA Considerations Section in RFCs", BCP 26, 194 RFC 8126, DOI 10.17487/RFC8126, June 2017, 195 . 197 6.2. Informative References 199 [I-D.ietf-pim-3376bis] 200 Haberman, B., "Internet Group Management Protocol, Version 201 3", Work in Progress, Internet-Draft, draft-ietf-pim- 202 3376bis-01, 25 October 2021, 203 . 206 [I-D.ietf-pim-3810bis] 207 Haberman, B., "Multicast Listener Discovery Version 2 208 (MLDv2) for IPv6", Work in Progress, Internet-Draft, 209 draft-ietf-pim-3810bis-01, 25 October 2021, 210 . 213 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 214 Control Message Protocol (ICMPv6) for the Internet 215 Protocol Version 6 (IPv6) Specification", STD 89, 216 RFC 4443, DOI 10.17487/RFC4443, March 2006, 217 . 219 Author's Address 221 Brian Haberman (editor) 222 Johns Hopkins University Applied Physics Lab 223 Email: brian@innovationslab.net