rfc9778v2.txt		rfc9778.txt
	skipping to change at line 84 ¶		skipping to change at line 84 ¶
	4. References		4. References
	4.1. Normative References		4.1. Normative References
	4.2. Informative References		4.2. Informative References
	Contributors		Contributors
	Author's Address		Author's Address
	1. Introduction		1. Introduction
	The sections that follow describe the allocation guidelines		The sections that follow describe the allocation guidelines
	associated with the specified fields within the Internet Group		associated with the specified fields within the Internet Group
	Management Protocol (IGMP) [RFC9776] and the Multicast Listener		Management Protocol (IGMP) [STD100] and the Multicast Listener
	Discovery (MLD) [RFC9777] headers. Some of these registries were		Discovery (MLD) [STD101] headers. Some of these registries were
	created previously, while others are created by this document.		created previously, while others are created by this document.
	This document obsoletes [RFC3228] and unifies guidelines for IPv4 and		This document obsoletes [RFC3228] and unifies guidelines for IPv4 and
	IPv6 group management protocols.		IPv6 group management protocols.
	1.1. Conventions Used in This Document		1.1. Conventions Used in This Document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in
	skipping to change at line 141 ¶		skipping to change at line 141 ¶
	2.1.2. Multicast Listener Discovery		2.1.2. Multicast Listener Discovery
	As with IGMP, the MLD header also contains Type and Code fields.		As with IGMP, the MLD header also contains Type and Code fields.
	Assignment of those fields within the MLD header is defined in		Assignment of those fields within the MLD header is defined in
	[RFC4443] with a registration policy of IETF Review; see		[RFC4443] with a registration policy of IETF Review; see
	<https://www.iana.org/assignments/icmpv6-parameters>.		<https://www.iana.org/assignments/icmpv6-parameters>.
	2.2. IGMP/MLD Query Message Flags		2.2. IGMP/MLD Query Message Flags
	IANA has created the "IGMP/MLD Query Message Flags" registry for the		IANA has created the "IGMP/MLD Query Message Flags" registry for the
	bits in the Flags field of the MLDv2 Query Message [RFC9777] and the		bits in the Flags field of the MLDv2 Query Message [STD101] and the
	IGMPv3 Query Message [RFC9776]. It has been populated as follows:		IGMPv3 Query Message [STD100]. It has been populated as follows:
	+===========+============+=============+===========+		+===========+============+=============+===========+
	| Flags Bit | Short Name | Description | Reference |		| Flags Bit | Short Name | Description | Reference |
	+===========+============+=============+===========+		+===========+============+=============+===========+
	| 0 | E | Extension | [RFC9279] |		| 0 | E | Extension | [RFC9279] |
	+-----------+------------+-------------+-----------+		+-----------+------------+-------------+-----------+
	| 1-3 | Unassigned |		| 1-3 | Unassigned |
	+-----------+--------------------------------------+		+-----------+--------------------------------------+
	Table 1: IGMP/MLD Query Message Flags Registry		Table 1: IGMP/MLD Query Message Flags Registry
	The Flags Bit value in the registry above corresponds to the column		The Flags Bit value in the registry above corresponds to the column
	header in the packet format diagrams in Sections 4.1 and 4.2 of		header in the packet format diagrams in Sections 4.1 and 4.2 of
	[RFC9776] and Sections 5.1 and 5.2 of [RFC9777].		[STD100] and Sections 5.1 and 5.2 of [STD101].
	The assignment of new bit flags within the Flags field requires		The assignment of new bit flags within the Flags field requires
	Standards Action.		Standards Action.
	2.3. IGMP/MLD Report Message Flags		2.3. IGMP/MLD Report Message Flags
	IANA has created the "IGMP/MLD Report Message Flags" registry for the		IANA has created the "IGMP/MLD Report Message Flags" registry for the
	bits in the Flags field of the MLDv2 Report Message and the IGMPv3		bits in the Flags field of the MLDv2 Report Message and the IGMPv3
	Report Message. It has been populated as follows:		Report Message. It has been populated as follows:
	skipping to change at line 178 ¶		skipping to change at line 178 ¶
	| Flags Bit | Short Name | Description | Reference |		| Flags Bit | Short Name | Description | Reference |
	+===========+============+=============+===========+		+===========+============+=============+===========+
	| 0 | E | Extension | [RFC9279] |		| 0 | E | Extension | [RFC9279] |
	+-----------+------------+-------------+-----------+		+-----------+------------+-------------+-----------+
	| 1-15 | Unassigned |		| 1-15 | Unassigned |
	+-----------+--------------------------------------+		+-----------+--------------------------------------+
	Table 2: IGMP/MLD Report Message Flags Registry		Table 2: IGMP/MLD Report Message Flags Registry
	The Flags Bit value in the registry above corresponds to the column		The Flags Bit value in the registry above corresponds to the column
	header in the packet format diagrams in [RFC9777] and [RFC9776].		header in the packet format diagrams in [STD101] and [STD100].
	The assignment of new bit flags within the Flags field requires		The assignment of new bit flags within the Flags field requires
	Standards Action.		Standards Action.
	3. Security Considerations		3. Security Considerations
	Security analyzers such as firewalls and network intrusion detection		Security analyzers such as firewalls and network intrusion detection
	monitors often rely on unambiguous interpretations of the fields		monitors often rely on unambiguous interpretations of the fields
	described in this memo. As new values for the fields are assigned,		described in this memo. As new values for the fields are assigned,
	existing security analyzers that do not understand the new values may		existing security analyzers that do not understand the new values may
	skipping to change at line 214 ¶		skipping to change at line 214 ¶
	[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for		[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
	Writing an IANA Considerations Section in RFCs", BCP 26,		Writing an IANA Considerations Section in RFCs", BCP 26,
	RFC 8126, DOI 10.17487/RFC8126, June 2017,		RFC 8126, DOI 10.17487/RFC8126, June 2017,
	<https://www.rfc-editor.org/info/rfc8126>.		<https://www.rfc-editor.org/info/rfc8126>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC9776] Haberman, B., Ed., "Internet Group Management Protocol,		[STD100] Internet Standard 100,
			<https://www.rfc-editor.org/info/std100>.
			At the time of writing, this STD comprises the following:
			Haberman, B., Ed., "Internet Group Management Protocol,
	Version 3", STD 100, RFC 9776, DOI 10.17487/RFC9776, March		Version 3", STD 100, RFC 9776, DOI 10.17487/RFC9776, March
	2025, <https://www.rfc-editor.org/info/rfc9776>.		2025, <https://www.rfc-editor.org/info/rfc9776>.
	[RFC9777] Haberman, B., Ed., "Multicast Listener Discovery Version 2		[STD101] Internet Standard 101,
			<https://www.rfc-editor.org/info/std101>.
			At the time of writing, this STD comprises the following:
			Haberman, B., Ed., "Multicast Listener Discovery Version 2
	(MLDv2) for IPv6", STD 101, RFC 9777,		(MLDv2) for IPv6", STD 101, RFC 9777,
	DOI 10.17487/RFC9777, March 2025,		DOI 10.17487/RFC9777, March 2025,
	<https://www.rfc-editor.org/info/rfc9777>.		<https://www.rfc-editor.org/info/rfc9777>.
	4.2. Informative References		4.2. Informative References
	[RFC3228] Fenner, B., "IANA Considerations for IPv4 Internet Group		[RFC3228] Fenner, B., "IANA Considerations for IPv4 Internet Group
	Management Protocol (IGMP)", BCP 57, RFC 3228,		Management Protocol (IGMP)", BCP 57, RFC 3228,
	DOI 10.17487/RFC3228, February 2002,		DOI 10.17487/RFC3228, February 2002,
	<https://www.rfc-editor.org/info/rfc3228>.		<https://www.rfc-editor.org/info/rfc3228>.
End of changes. 6 change blocks.
	8 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.48.