|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3404 (2002)
|
|
Title:
|
Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application, IETF RFC, 2002.
|
|
|
2.
|
Status of approval:
|
|
|
Approved as Proposed Standard in 2002-10.
|
|
3.
|
Justification for the specific reference:
|
|
|
This reference describes a specification for taking Uniform Resource Identifiers (URI) and locating an authoritative server for information about that URI.
|
|
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=3404
|
|
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 3405y, October 2002./
/
[6] Sollins, K. and L. Masinter, "Functional Requirements for/
Uniform Resource Names", RFC 1737, December 1994./
/
/
/
/
/
Mealling Standards Track [Page 13]/
/
RFC 3404 DDDS Based URI Resolution October 2002/
/
/
[7] Arms, B., "The URN Implementors, Uniform Resource Names: A/
Progress Report", D-Lib Magazine, February 1996./
/
[8] Moats, R., "URN Syntax", RFC 2141, May 1997./
/
[9] Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for/
specifying the location of services (DNS SRV)", RFC 2782,/
February 2000./
/
[10] Daniel, R., "A Trivial Convention for using HTTP in URN/
Resolution", RFC 2169, June 1997./
/
[11] Mealling, M., "URI Resolution Services Necessary for URN/
Resolution", RFC 2483, January 1999./
/
[12] Moore, K., Browne, S., Cox, J. and J. Gettler, "Resource/
Cataloging and Distribution System", Technical Report CS-97-346,/
December 1996./
/
[13] Sollins, K., "Architectural Principles of Uniform Resource Name/
Resolution", RFC 2276, January 1998./
/
[14] Daniel, R. and M. Mealling, "Resolution of Uniform Resource/
Identifiers using the Domain Name System", RFC 2168, June 1997./
/
[15] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource/
Identifiers (URI): Generic Syntax", RFC 2396, August 1998./
/
[16] Daigle, L., van Gulik, D., Iannella, R. and P. Falstrom, "URN/
Namespace Definition Mechanisms", RFC 2611, BCP 33, June 1999./
/
[17] Petke, R. and I. King, "Registration Procedures for URL Scheme/
Names", RFC 2717, BCP 35, November 1999./
/
[18] Mealling, M. and R. Daniel, "The Naming Authority Pointer/
(NAPTR) DNS Resource Record", RFC 2915, August 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
|
|
