idnits 2.17.1 draft-ietf-urn-dns-ddds-database-09.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3403 5 Title: Dynamic Delegation Discovery System (DDDS) 6 Part Three: The Domain Name System (DNS) Database 7 Author(s): M. Mealling 8 Status: Standards Track 9 Date: October 2002 10 Mailbox: michael@neonym.net 11 Pages: 14 12 Characters: 31058 13 Obsoletes: 2915, 2168 15 I-D Tag: draft-ietf-urn-dns-ddds-database-09.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3403.txt 19 This document describes a Dynamic Delegation Discovery System (DDDS) 20 Database using the Domain Name System (DNS) as a distributed database 21 of Rules. The Keys are domain-names and the Rules are encoded using 22 the Naming Authority Pointer (NAPTR) Resource Record (RR). 24 Since this document obsoletes RFC 2915, it is the official 25 specification for the NAPTR DNS Resource Record. It is also part of 26 a series that is completely specified in "Dynamic Delegation 27 Discovery System (DDDS) Part One: The Comprehensive DDDS" 28 (RFC 3401). It is very important to note that it is impossible to 29 read and understand any document in this series without reading the 30 others. 32 This document is a product of the Uniform Resource Names Working Group 33 of the IETF. 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.