Skip to main content

Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3403.
Author Michael H. Mealling
Last updated 2015-10-14 (Latest revision 2002-05-07)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3403 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Patrik Fältström
IESG note
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3403

        Title:      Dynamic Delegation Discovery System (DDDS)
                    Part Three: The Domain Name System (DNS) Database
        Author(s):  M. Mealling
        Status:     Standards Track
        Date:       October 2002
        Pages:      14
        Characters: 31058
        Obsoletes:  2915, 2168
        I-D Tag:    draft-ietf-urn-dns-ddds-database-09.txt


This document describes a Dynamic Delegation Discovery System (DDDS)
Database using the Domain Name System (DNS) as a distributed database
of Rules.  The Keys are domain-names and the Rules are encoded using
the Naming Authority Pointer (NAPTR) Resource Record (RR).

Since this document obsoletes RFC 2915, it is the official
specification for the NAPTR DNS Resource Record.  It is also part of
a series that is completely specified in "Dynamic Delegation
Discovery System (DDDS) Part One: The Comprehensive DDDS"
(RFC 3401).  It is very important to note that it is impossible to
read and understand any document in this series without reading the

This document is a product of the Uniform Resource Names Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.