idnits 2.17.1 draft-ietf-dnsind-test-tlds-00.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-00.txt,', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-dnsind-test-tlds-00.txt,', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-dnsind-test-tlds-00.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-00.txt,', but the file name used is 'draft-ietf-dnsind-test-tlds-00' == 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. ** There is 1 instance of too long lines in the document, the longest one being 6 characters in excess of 72. 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 (January 1998) is 9598 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: 11 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 Expires January 1998 4 Test and Example Top Level Domain 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-00.txt, is intended to be 13 become an Informational RFC. Distribution of this document is 14 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 nic.nordu.net (North Europe), ftp.nis.garr.it (South Europe), 32 munnari.oz.au (Pacific Rim), or ftp.is.co.za (Africa). 34 Abstract 36 To reduce the likelihood of conflict and confusion, four top level 37 domain names are reserved for use in testing and as examples in 38 documentation. 40 Table of Contents 42 Status of This Document....................................1 43 Abstract...................................................1 45 Table of Contents..........................................2 47 1. Introduction............................................3 48 2. TLDs for Testing and Documentation Examples.............3 49 3. Security Considerations.................................3 51 References.................................................4 52 Author's Addresses.........................................4 53 Expiration and File Name...................................4 55 1. Introduction 57 The global Internet Domain Name System is documented in RFC 1034, 58 1035, 1591 and numerous additional Requests for Comment. It defines 59 a tree of names starting with root, ".", immediately below which are 60 top level domain names such as .com and .us. Below top level domain 61 names there are normally additional levels of names. 63 2. TLDs for Testing and Documentation Examples 65 There is a need for top level domain names that can safely be used in 66 testing, as examples in documentation, and experimentation, without 67 fear of conflicts with actual top level domain names in the global 68 DNS. To satisfy this need, the following four domain names are 69 permanently reserved. 71 .xx 72 .nil 73 .test 74 .example 76 Note: two letter top level domain names are reserved for ISO 3166 / 77 Universal Postal Union two letter country codes. However, ISO 3166 78 reserves "xx" for local use and states that it will never be assigned 79 to a country. 81 The above four names will be added to the root with a single type TXT 82 RR under each. The RDATA for these TXT RRs will contain the single 83 string 85 Reserved, see RFC NNNN. 87 [where NNNN is the number of the RFC this draft gets issued as.] 89 3. Security Considerations 91 Confusion and conflict can be caused by the use of a current or 92 potential future top level domain name in testing, experimentation, 93 or as an example in documentation. Test and experimental software 94 can escape and end up being run against the operational DNS. Even 95 examples used "only" in documentation can end up being coded and 96 released or cause conflicts due to later real use and the possible 97 acquisition of intellectual property rights in such "example" names. 99 The reservation of several top level domain names specifically for 100 these purposes will minimize such confusion and conflict. 102 References 104 RFC 1034 - P. Mockapetris, "Domain names - concepts and facilities", 105 11/01/1987. 107 RFC 1035 - P. Mockapetris, "Domain names - implementation and 108 specification", 11/01/1987. 110 RFC 1591 - J. Postel, "Domain Name System Structure and Delegation", 111 03/03/1994. 113 Author's Addresses 115 Donald E. Eastlake 3rd 116 CyberCash, Inc. 117 318 Acton Street 118 Carlisle, MA 01741 USA 120 Telephone: +1 508 287 4877 121 +1 703 620-4200 (main office, Reston, VA) 122 FAX: +1 508 371 7148 123 EMail: dee@cybercash.com 125 Aliza R. Panitz 126 AccessAbility Internet Services, Inc. 127 12515 Greenbriar Rd. 128 Potomac, MD 20854 USA 130 Telephone: +1 301 983-3547 131 FAX: +1 301 983-4899 132 EMail: buglady@ability.net 134 Expiration and File Name 136 This draft expires January 1998. 138 Its file name is draft-ietf-dnsind-test-tlds-00.txt.