draft-ietf-urn-ddds-toc-02.txt   draft-ietf-urn-ddds-toc-03.txt 
Network Working Group M. Mealling URN M. Mealling
Internet-Draft VeriSign Internet-Draft VeriSign
Expires: August 20, 2002 February 19, 2002 Expires: November 5, 2002 May 7, 2002
Dynamic Delegation Discovery System (DDDS) Part One: The Dynamic Delegation Discovery System (DDDS) Part One: The
Comprehensive DDDS Standard Comprehensive DDDS Standard
draft-ietf-urn-ddds-toc-02.txt draft-ietf-urn-ddds-toc-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at http://
http://www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 20, 2002. This Internet-Draft will expire on November 5, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This document specifies the exact documents that make up the complete This document specifies the exact documents that make up the complete
Dynamic Delegation Discovery System (DDDS) standard. The DDDS is an Dynamic Delegation Discovery System (DDDS) standard. The DDDS is an
abstract algorithm for applying dynamically retrieved string abstract algorithm for applying dynamically retrieved string
skipping to change at page 5, line 8 skipping to change at page 5, line 8
called Applications and do not actually make up part of the DDDS core called Applications and do not actually make up part of the DDDS core
specification. Applications require databases in which to store specification. Applications require databases in which to store
their Rules. These databases are called DDDS Databases and are their Rules. These databases are called DDDS Databases and are
usually specified in separate documents. But again, these Database usually specified in separate documents. But again, these Database
specifications are not included in the DDDS core specification specifications are not included in the DDDS core specification
itself. itself.
4. DDDS Applications 4. DDDS Applications
No implementation can begin without an Application specification, as No implementation can begin without an Application specification, as
this is what provides the concrete instantiation details for the this is what provides the concrete instantiation details for the DDDS
DDDS. Without them the DDDS is nothing more than a general Algorithm. Without them the DDDS is nothing more than a general
algorithm. Application documents define the following: algorithm. Application documents define the following:
o the Application Unique String (the thing the delegation rules act o the Application Unique String (the thing the delegation rules act
on) on)
o the First Well Known Rule (the Rule that says where the process o the First Well Known Rule (the Rule that says where the process
starts) starts)
o the list of valid Databases (you can't just use any Database) o the list of valid Databases (you can't just use any Database)
skipping to change at page 7, line 12 skipping to change at page 7, line 12
Database" (RFC XXXX) [1] (This document is the official Database" (RFC XXXX) [1] (This document is the official
specification for the NAPTR DNS Resource Record) specification for the NAPTR DNS Resource Record)
6. Security Considerations 6. Security Considerations
Any known security issues that arise from the use of algorithms and Any known security issues that arise from the use of algorithms and
databases must be specified in the respective specifications. They databases must be specified in the respective specifications. They
must be completely and fully described. It is not required that the must be completely and fully described. It is not required that the
database and algorithms be secure or that it be free from risks, but database and algorithms be secure or that it be free from risks, but
that the known risks be identified. Publication of a new database that the known risks be identified. Publication of a new database
type or algorithm do require a security review, and the security type or algorithm does require a security review, and the security
considerations section should be subject to continuing evaluation. considerations section should be subject to continuing evaluation.
Additional security considerations should be addressed by publishing Additional security considerations should be addressed by publishing
revised versions of the database and algorithm specifications. revised versions of the database and algorithm specifications.
7. IANA Considerations 7. IANA Considerations
While this document itself does not create any new requirements for While this document itself does not create any new requirements for
the IANA, the documents in this series create many varied the IANA, the documents in this series create many varied
requirements. The IANA Considerations sections in those documents requirements. The IANA Considerations sections in those documents
should be reviewed by the IANA to determine the complete set of new should be reviewed by the IANA to determine the complete set of new
registries and requirements. Any new algorithms, databases or registries and requirements. Any new algorithms, databases or
applications should take great care in what they require the IANA to applications should take great care in what they require the IANA to
do in the future. do in the future.
References References
[1] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [1] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Two: The Algorithm", RFC XXXX, draft-ietf-urn-ddds-06.txt (work Two: The Algorithm", RFC XXXX, draft-ietf-urn-ddds-07.txt (work
in progress), February 2002. in progress), May 2002.
[2] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [2] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Three: The DNS Database", RFC ZZZZ, draft-ietf-urn-dns-ddds- Three: The DNS Database", RFC ZZZZ, draft-ietf-urn-dns-ddds-
database-08.txt (work in progress), February 2002. database-09.txt (work in progress), May 2002.
[3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Four: The URI Resolution Application", RFC YYYY, draft-ietf-urn- Four: The URI Resolution Application", RFC YYYY, draft-ietf-urn-
uri-res-ddds-06.txt (work in progress), February 2002. uri-res-ddds-06.txt (work in progress), February 2002.
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Five: URI.ARPA Assignment Procedures", RFC VVVV, draft-ietf-urn- Five: URI.ARPA Assignment Procedures", RFC VVVV, draft-ietf-urn-
net-procedures-10.txt (work in progress), February 2002. net-procedures-10.txt (work in progress), February 2002.
[5] Sollins, K., "Architectural Principles of Uniform Resource Name [5] Sollins, K., "Architectural Principles of Uniform Resource Name
 End of changes. 9 change blocks. 
12 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/