Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : H.721     
  ITU-T A.5 justification information for referenced document IETF RFC 2236 (1997) in draft H.721
1. Clear description of the referenced document:
Name: IETF RFC 2236 (1997)
Title: Internet Group Management Protocol Version 2 (1997/11)
2. Status of approval:
Approved standards track document.
3. Justification for the specific reference:
IETF RFC2250 deals with IGMPv2 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=2236
5. Other useful information describing the "Quality" of the document:
This RFC has been in existence since November 1997. IGMP v2 is very widely used and is a de-facto standard for host-to-router IP multicast membership control.
6. The degree of stability or maturity of the document:
RFC 2236 was published in November 1997. It is a standards-track document and is currently in the "Proposed Standard" state. 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 2236 is an update for a previous document describing IGMP v1.
8. Any explicit references within that referenced document should also be listed:
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC 2113] Katz, D., "IP Router Alert Option," RFC 2113, February 1997./
[RFC 1112] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1112, August 1989.
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.
Note: This form is based on Recommendation ITU-T A.5