|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4604 (2006)
|
|
Title:
|
Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast
|
|
|
2.
|
Status of approval:
|
|
|
Approved Proposed Standard (standards track) RFC approved August 2006.
|
|
3.
|
Justification for the specific reference:
|
|
|
This RFC is well-known as the Internet Group Management Protocol Version 3 (IGMPv3) and the Multicast Listener Discovery Protocol Version 2 (MLDv2) that allow a host to inform its neighboring routers of its desire to receive IPv4 and IPv6 multicast transmissions, respectively. This document updates the IGMPv3 and MLDv2 specifications.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4604
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since August 2006, obsolescing RFC 3810. It updates RFC 3376, RFC 3810. There are no errata.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4604 was published in August 2006 and defines version 3 of the protocol IGMP and version 2 of the multicast listener discovery protocol is required for deployment of multicast networks. RFC 4604 updates the IGMPv3 and MLDv2 specifications.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4604 is a basic component of the basic suite of internet protocols and standards and is widely used by the internet community.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[IGMPv2] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 2236, November 1997./
[IGMPv3] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002./
[MSFAPI] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface Extensions for Multicast Source Filters", RFC 3678, January 2004./
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, August 1989./
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[SSM] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", RFC 4607, August 2006./
[MLDv2] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004./
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast Listener Discovery (MLD) for IPv6", RFC 2710, October 1999./
Informative References/
[IANA-ALLOC] Internet Assigned Numbers Authority, http://www.iana.org/assignments/multicast-addresses./
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast Addresses", RFC 3306, August 2002.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
