RFC Errata
RFC 3810, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", June 2004
Note: This RFC has been updated by RFC 4604
Source of RFC: magma (int)See Also: RFC 3810 w/ inline errata
Errata ID: 8029
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Marco Seravalli
Date Reported: 2024-07-12
Verifier Name: RFC Editor
Date Verified: 2024-07-12
Section 2.2 says:
Both Multicast Address Specific Queries and Multicast Address and Source Specific Queries are only sent in response to State Change Reports, never in response to Current State Reports. This distinction between the two types of reports is needed to avoid the router treating all Multicast Listener Reports as potential changes in state. By doing so, the fast leave mechanism of MLDv2, described in more detail in section 2.2, might not be effective if a State Change Report is lost, and only the following Current State Report is received by the router. Nevertheless, it avoids an increased processing at the router and it reduces the MLD traffic on the link. More details on the necessity of distinguishing between the two report types can be found in Appendix A1.
It should say:
Both Multicast Address Specific Queries and Multicast Address and Source Specific Queries are only sent in response to State Change Reports, never in response to Current State Reports. This distinction between the two types of reports is needed to avoid the router treating all Multicast Listener Reports as potential changes in state. By doing so, the fast leave mechanism of MLDv2, described in more detail in section 2.3, might not be effective if a State Change Report is lost, and only the following Current State Report is received by the router. Nevertheless, it avoids an increased processing at the router and it reduces the MLD traffic on the link. More details on the necessity of distinguishing between the two report types can be found in Appendix A1.
Notes:
IIUC the fast leave mechanism is not explain in section 2.2 but in 2.3