Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : H.248.1 v3 Amd.2     
  ITU-T A.5 justification information for referenced document IETF RFC 2460 (1998) in draft H.248.1 v3 Amd.2
1. Clear description of the referenced document:
Name: IETF RFC 2460 (1998)
Title: Internet Protocol, Version 6 (IPv6) Specification
2. Status of approval:
Approved as standards track document.
3. Justification for the specific reference:
H.248.1 Annex C references this RFC for the definition of an IPv6 address.
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=2460
5. Other useful information describing the "Quality" of the document:
The status of all the referred RFCs, is "Proposed Standard".
6. The degree of stability or maturity of the document:
The status of all the referred RFCs, is "Proposed Standard".
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] IETF RFC 2401 (1998), Security Architecture for the Internet Protocol /
[2] IETF RFC 2402 (1998), IP Authentication Header/
[3] IETF RFC 2406 (1998), IP Encapsulating Security Protocol (ESP) /
[4] IETF RFC 2463(1998), ICMP for the Internet Protocol Version 6 (IPv6) /
[5] IETF RFC 2373 (1998), IP Version 6 Addressing Architecture /
[6] IETF RFC 1981 (1996), Path MTU Discovery for IP version 6/
[7] IETF STD 5, RFC 791 (1981), Internet Protocol /
[8] IETF STD 2, RFC 1700 (1994), Assigned Numbers/
[9] IETF STD 51, RFC 1661 (1994), The Point-to-Point Protocol (PPP)/
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):
None
Note: This form is based on Recommendation ITU-T A.5