idnits 2.17.1 draft-ietf-dnsind-test-tlds-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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-08.txt,', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-dnsind-test-tlds-08.txt,', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-dnsind-test-tlds-08.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-08.txt,', but the file name used is 'draft-ietf-dnsind-test-tlds-08' == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 7 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. 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 (September 1998) is 9355 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) -- Missing reference section? 'RFC 1886' on line 157 looks like a reference Summary: 11 errors (**), 1 flaw (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Example, Test, & Fictitious TLDs 2 Expires September 1998 4 Example, Test, and Fictitious Top Level DNS Names 5 -------- ----- --- ---------- --- ----- --- ----- 7 Donald E. Eastlake 3rd 8 Aliza R. Panitz 10 Status of This Document 12 This draft, file name draft-ietf-dnsind-test-tlds-08.txt, is intended to 13 be become a Best Current Practice RFC. Distribution of this document 14 is unlimited. Comments should be sent to the DNS mailing list 15 or to the authors. 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months. Internet-Drafts may be updated, replaced, or obsoleted by 24 other documents at any time. It is not appropriate to use Internet- 25 Drafts as reference material or to cite them other than as a 26 ``working draft'' or ``work in progress.'' 28 To learn the current status of any Internet-Draft, please check the 29 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 30 Directories on ds.internic.net (East USA), ftp.isi.edu (West USA), 31 ftp.nordu.net (North Europe), ftp.nis.garr.it (South Europe), 32 munnari.oz.au (Pacific Rim), or ftp.is.co.za (Africa). 34 [Changes in this draft from the last version resulted from discussion 35 with IANA.] 37 * 39 Abstract 41 To reduce the likelihood of conflict and confusion, a number of top 42 level domain names are reserved for use in creating names for 43 fictional purposes, private testing, as examples in documentation, 44 and the like. In addition, a few second level domain names reserved 45 for use as examples are documented. 47 Table of Contents 49 Status of This Document....................................1 51 Abstract...................................................2 52 Table of Contents..........................................2 54 1. Introduction............................................3 55 2. TLDs for Fictional, Testing, & Documentation Examples...3 57 3. Reserved Example Second Level Domain Names..............6 58 4. Security Considerations.................................6 60 References.................................................7 61 Authors Addresses..........................................7 62 Expiration and File Name...................................7 64 * 66 1. Introduction 68 The global Internet Domain Name System is documented in [RFC 1034, 69 1035, 1591] and numerous additional Requests for Comment. It defines 70 a tree of names starting with root, ".", immediately below which are 71 top level domain names such as ".com" and ".us". Below top level 72 domain names there are normally additional levels of names. 74 2. TLDs for Fictional, Testing, & Documentation Examples 76 There is a need for top level domain (TLD) names that can be used for 77 creating names which, without fear of conflicts with current or 78 future actual TLD names in the global DNS, can be used for (1) 79 realistic fictional names for literary or other purposes, (2) private 80 testing of existing DNS related code, (3) examples in documentation, 81 (4) DNS related experimentation, (5) invalid DNS names, or (6) other 82 similar uses. 84 For example, without guidance, a site might set up some local 85 additional unused top level domains for testing of its local DNS code 86 and configuration. Later, these TLDs might come into actual use on 87 the global Internet. As a result, local attempts to reference the 88 real data in these zones could be thwarted by the local test 89 versions. Or a work of fictional literature might be written with 90 realistic fake domain names under a fake TLD, perhaps in URLs, which 91 later caused confusion when that TLD came into actual use. Or test or 92 example code might be written that accesses a TLD that is in use with 93 the thought that the test code would only be run in restricted 94 testbed net or the example never actually run. Later, the test code 95 could escape from the testbed or the example be actually coded and 96 run on the Internet. Depending on the nature of the test or example, 97 it might be best for it to be referencing a TLD permanently reserved 98 for such purposes. 100 To safely satisfy these needs, domain names are reserved as described 101 below. It is best to allocate a variety of names of different 102 lengths now to reduce the probability of a need for further top level 103 domain name creation and assignment for this purpose in the 104 foreseeable future. 106 The following eight top level domain names are reserved. 108 * 109 .xy 110 .xz 111 .nil 112 .tld 113 .test 114 .example 115 .invalid 116 .localhost 118 Note: two letter top level domain names are reserved for ISO 119 3166 / Universal Postal Union two letter country codes. 120 However, ISO 3166 reserves all two letter codes beginning with 121 "x" for local use and states that they will never be assigned to 122 a country. 124 These names are available for special use in forming fictional names, 125 in testing, as examples in documentation, etc. except for 126 ".localhost" which is reserved for use as the local name of the 127 loopback IP addresses (IPv4 and IPv6). 129 ".invalid" is intended for use in online construction of domain names 130 that are sure to be and are self labeled as invalid. By appending 131 ".invalid" to a domain name, you are sure of constructing a name that 132 is not valid. The ".localhost" TLD has traditionally been staticly 133 defined in host DNS implementations as having an A record pointing to 134 the loop back IP address and is reserved for such use. 136 ".test" is particularly recommended for use in testing of current or 137 new DNS related code.. 139 ".example" is particularly recommended for use in documentation or as 140 examples. 142 It is recommended that fictional domain names be constructed using 143 ".xy", ".xz", ".nil", and ".tld". 145 [At the time of the issuance of this draft as an RFC, IANA will 146 determine which, if any, of the above names will actually be entered 147 into the IETF recommended root zone with a single TXT RR for each 148 that will contain the string 150 Reserved, see RFC nnnn. 152 or such other information as IANA determines. This text within 153 square brackets will be modified to indicate which names are actually 154 entered in root and what RR or RRs will be stored under them. 156 Other data will not be stored under these names in the root zone 157 except that the loopback A and AAAA [RFC 1886] resource records may 158 be stored under ".localhost". However, to assure proper operation of 160 * 161 hosts even when unable to access a root server, ".localhost" should 162 still be locally staticly configured. 164 [Note to RFC-Editor: replace nnnn above with the number of the RFC 165 this draft gets issued as.]] 167 * 169 3. Reserved Example Second Level Domain Names 171 The Internet Assigned Numbers Authority (IANA) also currently has the 172 following second level domain names reserved which can be used as 173 examples. 175 example.com 176 example.net 177 example.org 179 4. Security Considerations 181 Confusion and conflict can be caused by the use of a current or 182 future top level domain name as a fictitious name in literature, in 183 experimentation or testing, as an example in documentation, or the 184 like. Test and experimental software can escape and end up being run 185 against the global operational DNS. Even examples used "only" in 186 documentation can end up being coded and released or cause conflicts 187 due to later real use and the possible acquisition of intellectual 188 property rights in such "example" names. 190 The reservation of several top level domain names for these purposes 191 will minimize such confusion and conflict. 193 * 195 References 197 RFC 1034 - P. Mockapetris, "Domain names - concepts and facilities", 198 11/01/1987. 200 RFC 1035 - P. Mockapetris, "Domain names - implementation and 201 specification", 11/01/1987. 203 RFC 1591 - J. Postel, "Domain Name System Structure and Delegation", 204 03/03/1994. 206 RFC 1886 - S. Thomson, C. Huitema, "DNS Extensions to support IP 207 version 6", December 1995. 209 Authors Addresses 211 Donald E. Eastlake 3rd 212 CyberCash, Inc. 213 318 Acton Street 214 Carlisle, MA 01741 USA 216 Telephone: +1 978 287 4877 217 +1 703 620-4200 (main office, Reston, VA) 218 FAX: +1 978 371 7148 219 email: dee@cybercash.com 221 Aliza R. Panitz 222 AccessAbility Internet Services, Inc. 223 12515 Greenbriar Road 224 Potomac, MD 20854 USA 226 Telephone: +1 301 983-3547 227 FAX: +1 301 983-4899 228 email: buglady@ability.net 230 Expiration and File Name 232 This draft expires September 1998. 234 Its file name is draft-ietf-dnsind-test-tlds-08.txt. 236 *