idnits 2.17.1 draft-ietf-dnsind-test-tlds-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Bad filename characters: the document name given in the document, 'draft-ietf-dnsind-test-tlds-13.txt.', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-dnsind-test-tlds-13.txt.', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-dnsind-test-tlds-13.txt.', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-ietf-dnsind-test-tlds-13.txt.', but the file name used is 'draft-ietf-dnsind-test-tlds-13' == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (August 1999) is 9021 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 9 errors (**), 1 flaw (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Reserved TLDs 2 February 1999 3 Expires August 1999 5 Reserved Top Level DNS Names 6 -------- --- ----- --- ----- 8 Donald E. Eastlake 3rd 9 Aliza R. Panitz 11 Status of This Document 13 This draft is file name draft-ietf-dnsind-test-tlds-13.txt. 14 Distribution of this document is unlimited. Comments should be sent 15 to the DNS mailing list or to the 16 authors. 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, 21 and its working groups. Note that other groups may also distribute 22 working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months. Internet-Drafts may be updated, replaced, or obsoleted by 26 other documents at any time. It is not appropriate to use Internet- 27 Drafts as reference material or to cite them other than as a 28 ``working draft'' or ``work in progress.'' 30 To view the entire list of current Internet-Drafts, please check the 31 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 32 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 33 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 34 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 36 Abstract 38 To reduce the likelihood of conflict and confusion, a few top level 39 domain names are reserved for use in private testing, as examples in 40 documentation, and the like. In addition, a few second level domain 41 names reserved for use as examples are documented. 43 Table of Contents 45 Status of This Document....................................1 47 Abstract...................................................2 48 Table of Contents..........................................2 50 1. Introduction............................................3 51 2. TLDs for Testing, & Documentation Examples..............3 52 3. Reserved Example Second Level Domain Names..............4 53 4. IANA Considerations.....................................4 54 5. Security Considerations.................................4 56 References.................................................5 57 Authors Addresses..........................................5 58 Expiration and File Name...................................5 60 1. Introduction 62 The global Internet Domain Name System is documented in [RFC 1034, 63 1035, 1591] and numerous additional Requests for Comment. It defines 64 a tree of names starting with root, ".", immediately below which are 65 top level domain names such as ".com" and ".us". Below top level 66 domain names there are normally additional levels of names. 68 2. TLDs for Testing, & Documentation Examples 70 There is a need for top level domain (TLD) names that can be used for 71 creating names which, without fear of conflicts with current or 72 future actual TLD names in the global DNS, can be used for private 73 testing of existing DNS related code, examples in documentation, DNS 74 related experimentation, invalid DNS names, or other similar uses. 76 For example, without guidance, a site might set up some local 77 additional unused top level domains for testing of its local DNS code 78 and configuration. Later, these TLDs might come into actual use on 79 the global Internet. As a result, local attempts to reference the 80 real data in these zones could be thwarted by the local test 81 versions. Or test or example code might be written that accesses a 82 TLD that is in use with the thought that the test code would only be 83 run in a restricted testbed net or the example never actually run. 84 Later, the test code could escape from the testbed or the example be 85 actually coded and run on the Internet. Depending on the nature of 86 the test or example, it might be best for it to be referencing a TLD 87 permanently reserved for such purposes. 89 To safely satisfy these needs, four domain names are reserved as 90 listed and described below. 92 .test 93 .example 94 .invalid 95 .localhost 97 ".test" is recommended for use in testing of current or new DNS 98 related code. 100 ".example" is recommended for use in documentation or as 101 examples. 103 ".invalid" is intended for use in online construction of domain 104 names that are sure to be invalid and which it is obvious at a glance 105 are invalid. 107 The ".localhost" TLD has traditionally been statically defined 109 in host DNS implementations as having an A record pointing to the 110 loop back IP address and is reserved for such use. Any other use 111 would conflict with widely deployed code which assumes this use. 113 3. Reserved Example Second Level Domain Names 115 The Internet Assigned Numbers Authority (IANA) also currently has the 116 following second level domain names reserved which can be used as 117 examples. 119 example.com 120 example.net 121 example.org 123 4. IANA Considerations 125 IANA has agreed to the four top level domain name reservations 126 specified in this document and will reserve them for the uses 127 indicated. 129 5. Security Considerations 131 Confusion and conflict can be caused by the use of a current or 132 future top level domain name in experimentation or testing, as an 133 example in documentation, to indicate invalid names, or as a synonym 134 for the loop back address. Test and experimental software can escape 135 and end up being run against the global operational DNS. Even 136 examples used "only" in documentation can end up being coded and 137 released or cause conflicts due to later real use and the possible 138 acquisition of intellectual property rights in such "example" names. 140 The reservation of several top level domain names for these purposes 141 will minimize such confusion and conflict. 143 References 145 RFC 1034 - P. Mockapetris, "Domain names - concepts and facilities", 146 11/01/1987. 148 RFC 1035 - P. Mockapetris, "Domain names - implementation and 149 specification", 11/01/1987. 151 RFC 1591 - J. Postel, "Domain Name System Structure and Delegation", 152 03/03/1994. 154 Authors Addresses 156 Donald E. Eastlake 3rd 157 IBM 158 65 Shindegan Hill Road, RR #1 159 Carmel, NY 10512 161 Telephone: +1 914-276-1668(h) 162 +1 914-784-7913(w) 163 FAX: +1 914-784-3833(3) 164 email: dee3@us.ibm.com 166 Aliza R. Panitz 167 500 Stamford Dr. No. 310 168 Newark, DE 19711 USA 170 Telephone: +1 302-738-1554 171 email: buglady@fuschia.net 173 Expiration and File Name 175 This draft expires August 1999. 177 Its file name is draft-ietf-dnsind-test-tlds-13.txt.