|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3810 (2004)
|
|
Title:
|
Multicast Listener Discovery Version 2 (MLDv2) for IPv6, June 2004.
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC3810 deals with MLDv2 used in IPTV terminal devices.
|
|
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=3810
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since June 2004, updating RFC 2710.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3810 was published in June 2004 and defines version 2 of the protocol MLD (Multicast Listener Discovery) and is required for deployment of IPv6 multicast networks. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 3810 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:
|
|
|
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
[3] Conta, A. and S. Deering, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 2463, December 1998./
[4] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998./
[5] Deering, S., Fenner, W. and B. Haberman, "Multicast Listener Discovery (MLD) for IPv6", RFC 2710, October 1999./
[6] Partridge, C. and A. Jackson, "IPv6 Router Alert Option," RFC 2711, October 1999./
[7] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture, RFC 3513, April 2003./
[8] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998./
[9] Thomson, S. and T. Narten, "IPv6 Stateless Address Autoconfiguration", RFC 2462, December 1998./
[10] Cain, B., Deering, S., Kouvelas, I., Fenner, B. and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002./
[11] Bhattacharyya, S., Ed., "An Overview of Source- Specific Multicast (SSM)", RFC 3569, July 2003./
[12] Thaler, D., Fenner, B. and B. Quinn, "Socket Interface Extensions for Multicast Source Filters", RFC 3678, January 2004.
|
|
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.
|
|
