Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3643     
  ITU-T A.5 justification information for referenced document IETF RFC 3403 (2002) in draft Q.3643
1. Clear description of the referenced document:
Name: IETF RFC 3403 (2002)
Title: Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database, IETF RFC, 2002.
2. Status of approval:
Approved as Proposed Standard in 2002-10.
3. Justification for the specific reference:
This reference describes a Dynamic Delegation Discovery System (DDDS) Database using the Domain Name System (DNS) as a distributed database of Rules.
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=3403
5. Other useful information describing the "Quality" of the document:
The status of all the referred RFCs, is "Proposed Standard". Obsoletes RFC 2168, RFC 2915. Errata exist.
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] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part/
One: The Comprehensive DDDS", RFC 3401, October 2002./
/
[2] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part/
Two: The Algorithm", RFC 3402, October 2002./
/
[3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part/
Three: The Domain Name System (DNS) Database", RFC 3403, October/
2002./
/
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part/
Four: The Uniform Resource Identifiers (URI) Resolution/
Application", RFC 3404, October 2002./
/
[5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part/
Five: URI.ARPA Assignment Procedures", RFC 3405, October 2002./
/
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[7] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[8] Mockapetris, P., "Domain names - concepts and facilities", STD/
13, RFC 1034, November 1987./
/
[9] Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for/
specifying the location of services (DNS SRV)", RFC 2782,/
February 2000./
/
[10] Crocker, D., "Augmented BNF for Syntax Specifications: ABNF",/
RFC 2234, November 1997./
/
[11] Daniel, R., "A Trivial Convention for using HTTP in URN/
Resolution", RFC 2169, June 1997./
/
[12] 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./
/
[13] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource/
Identifiers (URI): Generic Syntax", RFC 2396, August 1998./
/
[14] Moats, R., "URN Syntax", RFC 2141, May 1997./
[15] Sollins, K., "Architectural Principles of Uniform Resource Name/
Resolution", RFC 2276, January 1998./
/
[16] Daniel, R. and M. Mealling, "Resolution of Uniform Resource/
Identifiers using the Domain Name System", RFC 2168, June 1997./
/
[17] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC/
2279, January 1998./
/
[18] Faltstrom, P., "E.164 number and DNS", RFC 2916, September 2000./
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