idnits 2.17.1 draft-ietf-dnsind-test-tlds-06.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-23) 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-06.txt,', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-dnsind-test-tlds-06.txt,', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-dnsind-test-tlds-06.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-06.txt,', but the file name used is 'draft-ietf-dnsind-test-tlds-06' == 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 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == 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 (June 1998) is 9444 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: 10 errors (**), 1 flaw (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Test and Example TLDs 2 December 1997 3 Expires June 1998 5 Test and Example Top Level Domain Names 6 ---- --- ------- --- ----- ------ ----- 8 Donald E. Eastlake 3rd 9 Aliza R. Panitz 11 Status of This Document 13 This draft, file name draft-ietf-dnsind-test-tlds-06.txt, is 14 intended to be become a Best Current Practice RFC. Distribution of 15 this document is unlimited. Comments should be sent to the DNS 16 mailing list or to the authors. 18 This document is an Internet-Draft. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months. Internet-Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 ``working draft'' or ``work in progress.'' 29 To learn the current status of any Internet-Draft, please check the 30 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 31 Directories on ds.internic.net (East USA), ftp.isi.edu (West USA), 32 nic.nordu.net (North Europe), ftp.nis.garr.it (South Europe), 33 munnari.oz.au (Pacific Rim), or ftp.is.co.za (Africa). 35 Abstract 37 To reduce the likelihood of conflict and confusion, a number of top 38 level domain names are reserved for use in private testing, as 39 examples in documentation, and the like. In addition, a few second 40 level domain names reserved for use as examples are documented. 42 Table of Contents 44 Status of This Document....................................1 45 Abstract...................................................1 47 Table of Contents..........................................2 49 1. Introduction............................................3 50 2. TLDs for Testing and Documentation Examples.............3 52 3. Reserved Example Second Level Domain Names..............5 53 4. Security Considerations.................................5 55 References.................................................6 56 Author's Addresses.........................................6 57 Expiration and File Name...................................6 59 1. Introduction 61 The global Internet Domain Name System is documented in RFC 1034, 62 1035, 1591 and numerous additional Requests for Comment. It defines 63 a tree of names starting with root, ".", immediately below which are 64 top level domain names such as ".com" and ".us". Below top level 65 domain names there are normally additional levels of names. 67 2. TLDs for Testing and Documentation Examples 69 There is a need for top level domain names that can safely be used in 70 private testing, as examples in documentation, and for 71 experimentation, without fear of conflicts with actual top level 72 domain names in the global DNS, or which should be reserved to avoid 73 confusion. It is best to allocate a reasonably large number of names 74 of different lengths now to reduce the probability of a need for 75 further top level domain name creation and assignment for this 76 purpose in the foreseeable future. 78 To satisfy these needs, forty two domain names are reserved as 79 described below. 81 The following twelve top level domain names are permanently reserved. 83 .xy 84 .xz 85 .nil 86 .tld 87 .link 88 .site 89 .test 90 .bogus 91 .example 92 .invalid 93 .localhost 94 .asixtythreecharacterstopleveldomainnamewhichisthelongestallowed 96 Note: two letter top level domain names are reserved for ISO 97 3166 / Universal Postal Union two letter country codes. 98 However, ISO 3166 reserves all two letter codes beginning with 99 "x" for local use and states that they will never be assigned to 100 a country. 102 These names are available for use in testing or as examples in 103 documentation except for ".invalid", ".link", and ".localhost". 104 ".invalid" is intended for use in online construction of domain names 105 that are sure to be invalid. ".link" is reserved to avoid confusion 106 with the "link.local" domain provided in draft-ietf-dnsind-local- 107 names-*.txt and should not be used. The ".localhost" TLD has 108 traditionally been staticly defined in host DNS implementations as 109 having an A record pointing to the loop back IP address and is 110 reserved for such use. 112 The TLDs ".xy", ".nil", and ".test" are particularly recommended for 113 use in testing. If a larger number of test names is needed, the 114 numeric suffix names listed below should be used. 116 The TLDs ".xz", ".tld", ".site", ".bogus", and ".example" are 117 particularly recommended for use in documentation or as examples. If 118 a larger number of names is needed in documentation or as examples, 119 the numeric suffix names listed below should be used. 121 The above twelve names will be added to the root with a single type 122 TXT RR under each. The RDATA for these TXT RRs will contain the 123 single string 125 Reserved, see RFC NNNN. 127 [where NNNN is the number of the RFC this draft gets issued as.] 129 In addition, the thirty domain names formed by appending the digits 0 130 through 9 to "tld", "test", and "example", as listed below, are also 131 permanently reserved for test and documentation use; however, since 132 there are currently no TLDs with digits in them and the presence of 133 these names without the digit suffix should provide notice, it is not 134 intended that these thirty additional TLDs be entered into the root 135 zone. 137 .tld0 .test0 .example0 138 .tld1 .test1 .exmaple1 139 .tld2 .test2 .example2 140 .tld3 .test2 .example2 141 .tld4 .test4 .example4 142 .tld5 .test5 .exmaple5 143 .tld6 .test6 .example6 144 .tld7 .test7 .example7 145 .tld8 .test8 .example8 146 .tld9 .test9 .example9 148 3. Reserved Example Second Level Domain Names 150 IANA has also reserved the following second level domain names which 151 can be used as examples. 153 example.com 154 example.net 155 example.org 157 4. Security Considerations 159 Confusion and conflict can be caused by the use of a current or 160 potential future top level domain name in testing, experimentation, 161 as an example in documentation, or the like. Test and experimental 162 software can escape and end up being run against the global 163 operational DNS. Even examples used "only" in documentation can end 164 up being coded and released or cause conflicts due to later real use 165 and the possible acquisition of intellectual property rights in such 166 "example" names. 168 The reservation of several top level domain names for these purposes 169 will minimize such confusion and conflict. 171 References 173 RFC 1034 - P. Mockapetris, "Domain names - concepts and facilities", 174 11/01/1987. 176 RFC 1035 - P. Mockapetris, "Domain names - implementation and 177 specification", 11/01/1987. 179 RFC 1591 - J. Postel, "Domain Name System Structure and Delegation", 180 03/03/1994. 182 draft-ietf-dnsind-local-names-*.txt 184 Author's Addresses 186 Donald E. Eastlake 3rd 187 CyberCash, Inc. 188 318 Acton Street 189 Carlisle, MA 01741 USA 191 Telephone: +1 978 287 4877 192 +1 703 620-4200 (main office, Reston, VA) 193 FAX: +1 978 371 7148 194 EMail: dee@cybercash.com 196 Aliza R. Panitz 197 AccessAbility Internet Services, Inc. 198 12515 Greenbriar Road 199 Potomac, MD 20854 USA 201 Telephone: +1 301 983-3547 202 FAX: +1 301 983-4899 203 EMail: buglady@ability.net 205 Expiration and File Name 207 This draft expires June 1998. 209 Its file name is draft-ietf-dnsind-test-tlds-06.txt.