idnits 2.17.1 draft-ietf-dnsind-test-tlds-10.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-10.txt.', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-dnsind-test-tlds-10.txt.', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-dnsind-test-tlds-10.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-10.txt.', but the file name used is 'draft-ietf-dnsind-test-tlds-10' == 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 (December 1998) is 9264 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 Expires December 1998 4 Reserved Top Level DNS Names 5 -------- --- ----- --- ----- 7 Donald E. Eastlake 3rd 8 Aliza R. Panitz 10 Status of This Document 12 This draft is file name draft-ietf-dnsind-test-tlds-10.txt. 13 Distribution of this document is unlimited. Comments should be sent 14 to the DNS mailing list or to the 15 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 view the entire list of current Internet-Drafts, please check the 29 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 30 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 31 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 32 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 34 Abstract 36 To reduce the likelihood of conflict and confusion, a few top level 37 domain names are reserved for use in private testing, as examples in 38 documentation, and the like. In addition, a few second level domain 39 names reserved for use as examples are documented. 41 Table of Contents 43 Status of This Document....................................1 45 Abstract...................................................2 46 Table of Contents..........................................2 48 1. Introduction............................................3 49 2. TLDs for Testing, & Documentation Examples..............3 50 3. Reserved Example Second Level Domain Names..............4 51 4. IANA Considerations.....................................4 52 5. Security Considerations.................................4 54 References.................................................5 55 Authors Addresses..........................................5 56 Expiration and File Name...................................5 58 1. Introduction 60 The global Internet Domain Name System is documented in [RFC 1034, 61 1035, 1591] and numerous additional Requests for Comment. It defines 62 a tree of names starting with root, ".", immediately below which are 63 top level domain names such as ".com" and ".us". Below top level 64 domain names there are normally additional levels of names. 66 2. TLDs for Testing, & Documentation Examples 68 There is a need for top level domain (TLD) names that can be used for 69 creating names which, without fear of conflicts with current or 70 future actual TLD names in the global DNS, can be used for private 71 testing of existing DNS related code, examples in documentation, DNS 72 related experimentation, invalid DNS names, or other similar uses. 74 For example, without guidance, a site might set up some local 75 additional unused top level domains for testing of its local DNS code 76 and configuration. Later, these TLDs might come into actual use on 77 the global Internet. As a result, local attempts to reference the 78 real data in these zones could be thwarted by the local test 79 versions. Or test or example code might be written that accesses a 80 TLD that is in use with the thought that the test code would only be 81 run in a restricted testbed net or the example never actually run. 82 Later, the test code could escape from the testbed or the example be 83 actually coded and run on the Internet. Depending on the nature of 84 the test or example, it might be best for it to be referencing a TLD 85 permanently reserved for such purposes. 87 To safely satisfy these needs, four domain names are reserved as 88 listed and described below. 90 .test 91 .example 92 .invalid 93 .localhost 95 ".test" is particularly recommended for use in testing of 96 current or new DNS related code. 98 ".example" is particularly recommended for use in documentation 99 or as examples. 101 ".invalid" is intended for use in online construction of domain 102 names that are sure to be invalid and which are obviously invalid. 104 The ".localhost" TLD has traditionally been statically defined 105 in host DNS implementations as having an A record pointing to the 106 loop back IP address and is reserved for such use. Any other use 107 would conflict with widely deployed code which assumes this use. 109 3. Reserved Example Second Level Domain Names 111 The Internet Assigned Numbers Authority (IANA) also currently has the 112 following second level domain names reserved which can be used as 113 examples. 115 example.com 116 example.net 117 example.org 119 4. IANA Considerations 121 IANA has stated that it does not object to the top level domain 122 reservations in this document. 124 5. Security Considerations 126 Confusion and conflict can be caused by the use of a current or 127 future top level domain name in experimentation or testing, as an 128 example in documentation, to indicate invalid names, or as a synonym 129 for the loop back address. Test and experimental software can escape 130 and end up being run against the global operational DNS. Even 131 examples used "only" in documentation can end up being coded and 132 released or cause conflicts due to later real use and the possible 133 acquisition of intellectual property rights in such "example" names. 135 The reservation of several top level domain names for these purposes 136 will minimize such confusion and conflict. 138 References 140 RFC 1034 - P. Mockapetris, "Domain names - concepts and facilities", 141 11/01/1987. 143 RFC 1035 - P. Mockapetris, "Domain names - implementation and 144 specification", 11/01/1987. 146 RFC 1591 - J. Postel, "Domain Name System Structure and Delegation", 147 03/03/1994. 149 Authors Addresses 151 Donald E. Eastlake 3rd 152 CyberCash, Inc. 153 318 Acton Street 154 Carlisle, MA 01741 USA 156 Telephone: +1 978 287 4877 157 +1 703 620-4200 (main office, Reston, VA) 158 FAX: +1 978 371 7148 159 email: dee@cybercash.com 161 Aliza R. Panitz 162 500 Stamford Dr. No. 310 163 Newark, DE 19711 USA 165 Telephone: +1 302-738-1554 166 email: buglady@fuschia.net 168 Expiration and File Name 170 This draft expires December 1998. 172 Its file name is draft-ietf-dnsind-test-tlds-10.txt.