|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document on October 2002.
|
|
3.
|
Justification for the specific reference:
|
|
|
This document specifies IP multicast control protocol IGMPv3. J.703 (J.iptvclientctrl) uses IGMPv3 as a control protocol for linear TV distribution over IP network.
|
|
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=3376
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since October 2002, obsolescing RFC 2236. Updates RFC 2236. Updated by RFC 4604. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3376 was published in October 2002 and defines version 3 of the protocol IGMP and is required for deployment of 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 3376 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] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, November 1998./
[2] http://www.iana.org/assignments/igmp-type-numbers/
[3] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1112, August 1989./
[4] Katz, D., "IP Router Alert Option," RFC 2113, February, 1997./
[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[6] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 2236, November 1997./
[7] Fenner, B., "IANA Considerations for IPv4 Internet Group Management Protocol (IGMP)", BCP 57, RFC 3228, February 2002./
[8] Braden, R., Borman, D. and C. Partridge, "Computing the Internet checksum", RFC 1071, September 1988./
[9] Thaler, D., B. Fenner, and B. Quinn, "Socket Interface Extensions for Multicast Source Filters", Work in Progress. ITU-T Recommendation T.140 (1998) - Text conversation protocol for multimedia application, with amendment 1, (2000)./
[10] Bhattacharyya, S., et. al., "An Overview of Source-Specific Multicast (SSM)", Work in Progress./
[11] Deering, S., Fenner, W. and B. Haberman, "Multicast Listener Discovery (MLD) for IPv6", RFC 2710, October 1999./
[12] Vida, R., L. Costa, S. Fdida, S. Deering, B. Fenner, I. Kouvelas, and B. Haberman, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", Work in Progress.
|
|
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.
|
|
