draft-ietf-urn-dns-ddds-database-08.txt   draft-ietf-urn-dns-ddds-database-09.txt 
Network Working Group M. Mealling Network Working Group 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 Three: The DNS Dynamic Delegation Discovery System (DDDS) Part Three: The DNS
Database Database
draft-ietf-urn-dns-ddds-database-08.txt draft-ietf-urn-dns-ddds-database-09.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 describes a Dynamic Delegation Discovery System This document describes a Dynamic Delegation Discovery System
Database using the Domain Name System as a distributed database of Database using the Domain Name System as a distributed database of
Rules. The Keys are domain-names and the Rules are encoded using the Rules. The Keys are domain-names and the Rules are encoded using the
skipping to change at page 5, line 23 skipping to change at page 5, line 23
case where either the input or the output to the substitution case where either the input or the output to the substitution
expression contains code points outside of the ASCII/Unicode expression contains code points outside of the ASCII/Unicode
equivalence in UTF-8, any UTF-8 is interpreted as a series of equivalence in UTF-8, any UTF-8 is interpreted as a series of
code-points instead of as a series of bytes. This is to ensure code-points instead of as a series of bytes. This is to ensure
that the internationalized features of the POSIX Extended Regular that the internationalized features of the POSIX Extended Regular
Expressions are able to match their intended code-points. Expressions are able to match their intended code-points.
Substitution expressions MUST NOT be written where they depend on Substitution expressions MUST NOT be written where they depend on
a specific POSIX locale since this would cause substutition a specific POSIX locale since this would cause substutition
expressions to loose their ability to be universally applicable. expressions to loose their ability to be universally applicable.
All DNS resource records have a Time To Live (TTL) associated with
them. When the number of seconds has passed since the record was
retrieved the record is no longer valid and a new query must be
used to retrieve the new records. Thus, as mentioned in the DDDS
Algorithm, there can be the case where a given Rule expires. In
the case where an application attemps to fall back to previously
retrieved sets of Rules (either in the case of a bad delegation
path or some network or server failure) the application MUST
ensure that none of the records it is relying on have expired. In
the case where even a single record has expired, the application
is required to start over at the beginning of the algorithm.
Key Format: Key Format:
A Key is a validly constructed DNS domain-name. A Key is a validly constructed DNS domain-name.
Lookup Request: Lookup Request:
In order to request a set of rules for a given Key, the client In order to request a set of rules for a given Key, the client
issues a request, following standard DNS rules, for NAPTR Resource issues a request, following standard DNS rules, for NAPTR Resource
Records for the given domain-name. Records for the given domain-name.
Lookup Response: Lookup Response:
The response to a request for a given Key (domain-name) will be a The response to a request for a given Key (domain-name) will be a
skipping to change at page 18, line 9 skipping to change at page 18, line 9
resolvable before, this may or may not be considered a problem. resolvable before, this may or may not be considered a problem.
Regular expressions should be checked for sanity, not blindly passed Regular expressions should be checked for sanity, not blindly passed
to something like PERL since arbitrary code can be included and to something like PERL since arbitrary code can be included and
subsequently processed. subsequently processed.
References References
[1] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [1] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
One: The Comprehensive DDDS Standard", RFC WWWW, draft-ietf- One: The Comprehensive DDDS Standard", RFC WWWW, draft-ietf-
urn-ddds-toc-02.txt (work in progress), February 2002. urn-ddds-toc-03.txt (work in progress), May 2002.
[2] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [2] 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.
[3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [3] 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-07.txt (work in progress), February 2002. database-09.txt (work in progress), May 2002.
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Four: The URI Resolution Application", RFC YYYY, draft-ietf- Four: The URI Resolution Application", RFC YYYY, draft-ietf-
urn-uri-res-ddds-06.txt (work in progress), February 2002. urn-uri-res-ddds-07.txt (work in progress), May 2002.
[5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part [5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Five: URI.ARPA Assignment Procedures", RFC VVVV, draft-ietf- Five: URI.ARPA Assignment Procedures", RFC VVVV, draft-ietf-
urn-net-procedures-10.txt (work in progress), February 2002. urn-net-procedures-11.txt (work in progress), May 2002.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement [6] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997. Levels", RFC 2119, BCP 14, March 1997.
[7] Mockapetris, P., "Domain names - implementation and [7] Mockapetris, P., "Domain names - implementation and
specification", RFC 1035, STD 13, Nov 1987. specification", RFC 1035, STD 13, Nov 1987.
[8] Mockapetris, P., "Domain names - concepts and facilities", RFC [8] Mockapetris, P., "Domain names - concepts and facilities", RFC
1034, STD 13, Nov 1987. 1034, STD 13, Nov 1987.
 End of changes. 10 change blocks. 
11 lines changed or deleted 23 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/