rfc9778v1.txt   rfc9778.txt 
skipping to change at line 135 skipping to change at line 135
* The reference for the registry has been changed to this document. * The reference for the registry has been changed to this document.
Note that the policy for assigning Code values for new IGMP Types Note that the policy for assigning Code values for new IGMP Types
MUST be defined in the document defining the new Type value. MUST be defined in the document defining the new Type value.
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. [RFC4443] with a registration policy of IETF Review; see
<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 [RFC9777] and the
IGMPv3 Query Message [RFC9776]. It has been populated as follows: IGMPv3 Query Message [RFC9776]. 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 [RFC9777] and [RFC9776]. header in the packet format diagrams in Sections 4.1 and 4.2 of
[RFC9776] and Sections 5.1 and 5.2 of [RFC9777].
The initial contents of this registry contain the E-bit defined in
[RFC9279].
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 181 skipping to change at line 180
| 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 [RFC9777] and [RFC9776].
The initial contents of this registry includes the E-bit defined in
[RFC9279].
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
fail, resulting in either loss of connectivity if the analyzer fail, resulting in either loss of connectivity if the analyzer
 End of changes. 3 change blocks. 
8 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.48.