idnits 2.17.1 draft-klensin-dns-role-05.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 3467 5 Title: Role of the Domain Name System (DNS) 6 Author(s): J. Klensin 7 Status: Informational 8 Date: February 2003 9 Mailbox: klensin+srch@jck.com 10 Pages: 31 11 Characters: 84570 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-klensin-dns-role-05.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3467.txt 18 This document reviews the original function and purpose of the domain 19 name system (DNS). It contrasts that history with some of the 20 purposes for which the DNS has recently been applied and some of the 21 newer demands being placed upon it or suggested for it. A framework 22 for an alternative to placing these additional stresses on the DNS is 23 then outlined. This document and that framework are not a proposed 24 solution, only a strong suggestion that the time has come to begin 25 thinking more broadly about the problems we are encountering and 26 possible approaches to solving them. 28 This memo provides information for the Internet community. It does 29 not specify an Internet standard of any kind. Distribution of this 30 memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.