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 2535 (1999) in draft X.1141
1. Clear description of the referenced document:
Name: IETF RFC 2535 (1999)
Title: Domain Name System Security Extensions, IETF RFC, 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-1 uses techniques from Domain Name System Security Extensions as discussed in [21] for security.
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=2535
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:
[RFC 1033] Lottor, M., "Domain Administrators Operations Guide", RFC/
1033, November 1987./
/
[RFC 1034] Mockapetris, P., "Domain Names - Concepts and/
Facilities", STD 13, RFC 1034, November 1987./
/
[RFC 1035] Mockapetris, P., "Domain Names - Implementation and/
Specifications", STD 13, RFC 1035, November 1987./
[RFC 1305] Mills, D., "Network Time Protocol (v3)", RFC 1305, March/
1992./
/
[RFC 1530] Malamud, C. and M. Rose, "Principles of Operation for the/
TPC.INT Subdomain: General Principles and Policy", RFC/
1530, October 1993./
/
[RFC 2401] Kent, S. and R. Atkinson, "Security Architecture for the/
Internet Protocol", RFC 2401, November 1998./
/
[RFC 1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC/
1982, September 1996./
/
[RFC 1995] Ohta, M., "Incremental Zone Transfer in DNS", RFC 1995,/
August 1996./
/
[RFC 2030] Mills, D., "Simple Network Time Protocol (SNTP) Version 4/
for IPv4, IPv6 and OSI", RFC 2030, October 1996./
/
[RFC 2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message/
Bodies", RFC 2045, November 1996./
/
[RFC 2065] Eastlake, D. and C. Kaufman, "Domain Name System Security/
Extensions", RFC 2065, January 1997./
/
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC 2136] Vixie, P., Thomson, S., Rekhter, Y. and J. Bound,/
"Dynamic Updates in the Domain Name System (DNS UPDATE)",/
RFC 2136, April 1997./
/
[RFC 2137] Eastlake, D., "Secure Domain Name System Dynamic Update",/
RFC 2137, April 1997./
/
[RFC 2181] Elz, R. and R. Bush, "Clarifications to the DNS/
Specification", RFC 2181, July 1997./
/
[RFC 2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[RFC 2537] Eastlake, D., "RSA/MD5 KEYs and SIGs in the Domain Name/
System (DNS)", RFC 2537, March 1999./
/
[RFC 2539] Eastlake, D., "Storage of Diffie-Hellman Keys in the/
Domain Name System (DNS)", RFC 2539, March 1999./
[RFC 2536] Eastlake, D., "DSA KEYs and SIGs in the Domain Name/
System (DNS)", RFC 2536, March 1999./
/
[RFC 2538] Eastlake, D. and O. Gudmundsson, "Storing Certificates in/
the Domain Name System", RFC 2538, March 1999./
/
[RFC 2541] Eastlake, D., "DNS Operational Security Considerations",/
RFC 2541, March 1999./
/
[RSA FAQ] - RSADSI Frequently Asked Questions periodic posting./
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