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 792 (1981) in draft H.721
1. Clear description of the referenced document:
Name: IETF RFC 792 (1981)
Title: Internet Control Message Protocol
2. Status of approval:
Standards Track, Approved by the IESG (Internet Engineering Steering Group), September 1981
3. Justification for the specific reference:
IETF RFC792 deals with ICMP 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=792
5. Other useful information describing the "Quality" of the document:
The status of RFC792 is "STANDARD".
6. The degree of stability or maturity of the document:
The status of this referred RFC is "Proposed Standard". Errata Exist. Updated by RFCs 4884, 950
7. Relationship with other existing or emerging documents:
References within the referenced RFC are listed under item (8).
8. Any explicit references within that referenced document should also be listed:
[1] Postel, J. (ed.), "Internet Protocol - DARPA Internet Program/
Protocol Specification," RFC 791, USC/Information Sciences/
Institute, September 1981./
/
[2] Cerf, V., "The Catenet Model for Internetworking," IEN 48,/
Information Processing Techniques Office, Defense Advanced/
Research Projects Agency, July 1978./
/
[3] Strazisar, V., "Gateway Routing: An Implementation/
Specification", IEN 30, Bolt Beranek and Newman, April 1979./
/
[4] Strazisar, V., "How to Build a Gateway", IEN 109, Bolt Beranek/
and Newman, August 1979./
/
[5] Mills, D., "DCNET Internet Clock Service," RFC 778, COMSAT/
Laboratories, April 1981.
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):
All RFCs are 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.
Note: This form is based on Recommendation ITU-T A.5