Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1141     
  ITU-T A.5 justification information for referenced document IETF RFC 2915 (2000) in draft X.1141
1. Clear description of the referenced document:
Name: IETF RFC 2915 (2000)
Title: The Naming Authority Pointer (NAPTR) DNS Resource Record, IETF RFC, 2000.
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-1 develops a profile based on The Naming Authority Pointer (NAPTR) DNS Resource Record as discussed in [23].
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=2915
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:
[1] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[2] Mockapetris, P., "Domain names - concepts and facilities", STD/
13, RFC 1034, November 1987./
/
[3] Moats, R., "URN Syntax", RFC 2141, May 1997./
/
[4] Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for/
specifying the location of services (DNS SRV)", RFC 2782,/
February 2000./
/
[5] Crocker, D., "Augmented BNF for Syntax Specifications: ABNF",/
RFC 2234, November 1997./
/
[6] Daniel, R., "A Trivial Convention for using HTTP in URN/
Resolution", RFC 2169, June 1997./
/
[7] Daniel, R. and M. Mealling, "Resolution of Uniform Resource/
Identifiers using the Domain Name System", RFC 2168, June 1997./
/
[8] IEEE, "IEEE Standard for Information Technology - Portable/
Operating System Interface (POSIX) - Part 2: Shell and Utilities/
(Vol. 1)", IEEE Std 1003.2-1992, January 1993./
/
[9] Berners-Lee, T., Fielding, R.T. and L. Masinter, "Uniform/
Resource Identifiers (URI): 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