draft-ietf-urn-dns-ddds-database-05.txt   draft-ietf-urn-dns-ddds-database-06.txt 
Network Working Group M. Mealling Network Working Group M. Mealling
Internet-Draft Verisign Internet-Draft VeriSign
Expires: November 23, 2001 May 25, 2001 Expires: February 26, 2002 August 28, 2001
A DDDS Database Using The Domain Name System A DDDS Database Using The Domain Name System
draft-ietf-urn-dns-ddds-database-05 draft-ietf-urn-dns-ddds-database-06
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.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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://www.ietf.org/ietf/1id-abstracts.txt. http://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 November 23, 2001. This Internet-Draft will expire on February 26, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
NAPTR Resource Record. NAPTR Resource Record.
Since this document officially obsoletes RFC 2915, it is the official Since this document officially obsoletes RFC 2915, it is the official
specification for the NAPTR DNS Resource Record. specification for the NAPTR DNS Resource Record.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3. DDDS Database Specification . . . . . . . . . . . . . . . . . 5 3. DDDS Database Specification . . . . . . . . . . . . . . . . 5
4. NAPTR RR Format . . . . . . . . . . . . . . . . . . . . . . . 7 4. NAPTR RR Format . . . . . . . . . . . . . . . . . . . . . . 7
4.1 Packet Format . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 Packet Format . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Master File Format . . . . . . . . . . . . . . . . . . . . . . 9 4.2 Additional Information Processing . . . . . . . . . . . . . 9
5. Application Specifications . . . . . . . . . . . . . . . . . . 10 4.2.1 Additional Section processing by DNS servers . . . . . . . . 9
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.2 Additional Section processing by resolver/applications . . . 9
6.1 URN Example . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.3 Master File Format . . . . . . . . . . . . . . . . . . . . . 9
6.2 E164 Example . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Application Specifications . . . . . . . . . . . . . . . . . 10
7. Advice for DNS Administrators . . . . . . . . . . . . . . . . 14 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6.1 URN Example . . . . . . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6.2 E164 Example . . . . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Advice for DNS Administrators . . . . . . . . . . . . . . . 14
References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 16
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . 17
References . . . . . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . 19
Full Copyright Statement . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The NAPTR DNS Resource Record was originally produced by the URN The NAPTR DNS Resource Record was originally produced by the URN
Working Group as a way to encode rule-sets in DNS so that the Working Group as a way to encode rule-sets in DNS so that the
delegated sections of a URI could be decomposed in such a way that delegated sections of a URI could be decomposed in such a way that
they could be changed and re-delegated over time. The result was a they could be changed and re-delegated over time. The result was a
Resource Record that included a regular expression that would be used Resource Record that included a regular expression that would be used
by a client program to rewrite a string into a domain name. Regular by a client program to rewrite a string into a domain name. Regular
expressions were chosen for their compactness to expressivity ratio expressions were chosen for their compactness to expressivity ratio
skipping to change at page 9, line 7 skipping to change at page 9, line 7
A <domain-name> which is the next domain-name to query for A <domain-name> which is the next domain-name to query for
depending on the potential values found in the flags field. This depending on the potential values found in the flags field. This
field is used when the regular expression is a simple replacement field is used when the regular expression is a simple replacement
operation. Any value in this field MUST be a fully qualified operation. Any value in this field MUST be a fully qualified
domain-name. Name compression is not to be used for this field. domain-name. Name compression is not to be used for this field.
This field and the REGEXP field together make up the Substitution This field and the REGEXP field together make up the Substitution
Expression in the DDDS Algorithm. They are also mutually Expression in the DDDS Algorithm. They are also mutually
exclusive. If a record is returned that has values for both exclusive. If a record is returned that has values for both
fields then it is considered to be in error and should be ignored. fields then it is considered to be in error and should be ignored.
4.2 Master File Format 4.2 Additional Information Processing
Additional section processing requires upgraded DNS servers, thus it
will take many years before applications can expect to see relevant
records in the additional information section.
4.2.1 Additional Section processing by DNS servers
DNS servers MAY add RRsets to the additional information section that
are relevant to the answer and have the same authenticity as the data
in the answer section. Generally this will be made up of A and SRV
records but the exact records depends on the application.
4.2.2 Additional Section processing by resolver/applications
Applications MAY inspect the Additional Information section for
relevant records but Applications MUST NOT require that records of
any type be in the Additional Information section of any DNS response
in order for clients to function. All Applications must be capable
of handling responses from nameservers that never fill in the
Additional Information part of a response.
4.3 Master File Format
The master file format follows the standard rules in RFC-1035[1]. The master file format follows the standard rules in RFC-1035[1].
Order and preference, being 16-bit unsigned integers, shall be an Order and preference, being 16-bit unsigned integers, shall be an
integer between 0 and 65535. The Flags and Services and Regexp integer between 0 and 65535. The Flags and Services and Regexp
fields are all quoted <character-string>s. Since the Regexp field fields are all quoted <character-string>s. Since the Regexp field
can contain numerous backslashes and thus should be treated with can contain numerous backslashes and thus should be treated with
care. See Section 10 for how to correctly enter and escape the care. See Section 10 for how to correctly enter and escape the
regular expression. regular expression.
5. Application Specifications 5. Application Specifications
skipping to change at page 19, line 9 skipping to change at page 19, line 9
[14] Daniel, R. and M. Mealling, "Resolution of Uniform Resource [14] Daniel, R. and M. Mealling, "Resolution of Uniform Resource
Identifiers using the Domain Name System", RFC 2168, June 1997. Identifiers using the Domain Name System", RFC 2168, June 1997.
[15] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC [15] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC
2279, January 1998. 2279, January 1998.
Author's Address Author's Address
Michael Mealling Michael Mealling
Verisign VeriSign
505 Huntmar Park Drive 505 Huntmar Park Drive
Herndon, VA 22070 Herndon, VA 22070
US US
Phone: +1 770 921-2251 Phone: +1 770 921-2251
EMail: michaelm@netsol.com EMail: michael@research.netsol.com
URI: http://www.verisign.com URI: http://www.verisign.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
 End of changes. 7 change blocks. 
24 lines changed or deleted 49 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/