Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1142     
  ITU-T A.5 justification information for referenced document IETF RFC 2732 (1999) in draft X.1142
1. Clear description of the referenced document:
Name: IETF RFC 2732 (1999)
Title: Format for Literal IPv6 Addresses in URL's, IETF RFC, December 1999.
2. Status of approval:
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
Draft Rec. X.websec-2 refers to Format for Literal IPv6 Addresses in URL's as a means for ensuring distributed computing.
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=2732
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 RFCs are listed under item (8).
8. Any explicit references within that referenced document should also be listed:
[ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 2373, July 1998./
/
[STD-PROC] Bradner, S., The Internet Standards Process -- Revision 3,/
BCP 9, RFC 2026, October 1996./
/
[URL] Fielding, R., Masinter, L. and T. Berners-Lee, "Uniform/
Resource Identifiers: Generic Syntax", RFC 2396, August/
1998./
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