idnits 2.17.1 draft-arends-private-use-tld-00.txt: -(98): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(99): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 4 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 194 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 39 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 3, 2019) is 1636 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: 'ISO3166-1' is mentioned on line 64, but not defined == Missing Reference: 'RFC1591' is mentioned on line 68, but not defined == Missing Reference: 'ICANN ISO' is mentioned on line 178, but not defined == Missing Reference: 'RFC20' is mentioned on line 87, but not defined == Unused Reference: 'RFC 20' is defined on line 163, but no explicit reference was found in the text == Unused Reference: 'RFC 1591' is defined on line 166, but no explicit reference was found in the text == Unused Reference: 'ISO 3166-1' is defined on line 173, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1591 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO 3166-1' Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Independent Submission E. Lewis 2 Internet-Draft R. Arends 3 ICANN 4 Expires: May 3, 2020 Date: November 3, 2019 6 User Assigned ISO 3166-1 Alpha-2 Codes 7 and the DNS Root Zone 9 draft-arends-private-use-tld-00 11 Abstract 13 The ISO 3166 standard is used for the definition of eligible designations for 14 country code Top Level Domains. This standard is maintained by the ISO 3166 15 Maintenance Agency. The ISO 3166 standard contains a set of User-Assigned 16 code elements. This document describes that these values can be used as top 17 level domains for private DNS resolution. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on May 3, 2020. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1 54 2. Private-Use Top-Level Domain . . . . . . . . . . . . . . . . 1 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 1 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 1 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 1 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 1 59 7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 1 61 1. Introduction 63 The practice governing the delegation of ASCII two-letter domain names in 64 the DNS [STD 13] root zone is to employ the ISO 3166-1 standard [ISO3166-1]. 65 The ISO 3166-1 standard provides for multiple types of codings, with the 66 ASCII two-letter codes (known as "alpha 2" codes) being used in the DNS to 67 potentially represent countries and territories as country-code top-level 68 domains (ccTLDs) [RFC1591]. The interrelationship is documented in "ICANN 69 and the ISO, A Common Interest in ISO Standard 3166" [ICANN ISO]. 71 In addition to these assigned codes, there are values designated as "User 72 Assigned". Quoting ISO 3166-1:2013 clause 8.1.3 "User-assigned code elements" 73 : 75 "If users need code elements to represent country names not included 76 in this part of ISO 3166, the series of letters AA, QM to QZ, XA to 77 XZ, and ZZ, and the series AAA to AAZ, QMA to QZZ, XAA to XZZ, and 78 ZZA to ZZZ respectively and the series of numbers 900 to 999 are 79 available. 81 NOTE Users are advised that the above series of codes are not 82 universals, those code elements are not compatible between different 83 entities." 85 For the purposes of this document, ISO 3166-1 "alpha-2 user-assigned codes" 86 are defined to be AA, QM to QZ, XA to XZ, and ZZ. The ranges ("to") are 87 alphabetic and contain only characters in the US-ASCII definition [RFC20]. 88 The codes are case insensitive. 90 The quoted text explicitly states "code elements to represent country names" 91 with the emphasis on the term "country names". Using code elements to 92 represent something different than "country names" might at first appear to 93 go against the intended use of the standard. However, many organisations, 94 including the ISO, have used the user-assigned range to represent entities 95 other than country names. The following list is not meant to be exhaustive, 96 but to illustrate the different uses of the user-assigned range: 98 ISO 3901 uses “ZZ” for direct registrants independent of any country. 99 ISO 4217 uses the “XA..XZ” range for transactions and precious metals. 100 ISO 6166 uses "XS" for securities cleared through Euroclear/Clearstream. 102 ICAO uses “ZZ” for UN travel documents. 103 RFC5646 contains a section and examples dedicated to Private Use Sub-tags 105 WIPO has 5 User Assigned code elements allocated to identify regional 106 agencies and patent offices, and allocated "XX" for "Unknown states, 107 other entities or organizations”. 109 CABForum uses "XX" to signify a location not covered by ISO3166-1. 111 [references to be added in -01] 113 2. Private-Use Top-Level Domain 115 Two areas of identifier use have been identified that can benefit from the 116 use of private-use namespace: 118 1. Local-only usage. In locally configured environments where 119 Internet traffic will not traverse the global Internet. While it is 120 preferred that such usages use sub-domains within another domain 121 registered for the specific hosting entity, not all such configurations 122 have such a domain available. This is analogous to the use of private 123 addressing described in [RFC 1918]. 125 2. Use by DNS-like applications. Some applications use network identifiers 126 that are similar in appearance to domain names, and may be interpreted 127 by software as domain names, but are not intended to use the global 128 DNS resolution service (such as connecting to the DNS root servers via 129 port 53 and performing recursive lookups). Using namespace allocated 130 for private-use will guard against conflicts with the global DNS 131 resolution system. 133 This document recommends ZZ as a private-use TLD that can be used to support 134 these two functions. The User Assigned classification of the ZZ code element 135 in the ISO 3166-1 alpha 2 standard allows for the assumption that these codes 136 will never risk requiring delegation through future assignment to represent a 137 country or territory. 139 3. IANA Considerations 141 To Be Added. 143 4. Security Considerations 145 Names appearing to be domain names ending in alpha-2 user-assigned codes 146 will be independent of the root zone, hence nothing can be said about their 147 security implications from the root zone perspective. 149 5. Acknowledgements 151 This document is based on a earlier draft by Ed Lewis. David Conrad, Jaap 152 Akkerhuis, Kal Feher, Andrew Sullivan, Kim Davies so far have played a role. 154 6. References 156 6.1. Normative References 158 [STD 13] Mockapetris, P., "Domain names - concepts and facilities", 159 STD 13, RFC 1034, November 1987 and Mockapetris, P., 160 "Domain names - implementation and specification", 161 STD 13, RFC 1035, November 1987. 163 [RFC 20] Cerf, V., "ASCII format for network interchange", 164 STD 80, RFC 20, October 1969. 166 [RFC 1591] Postel, J., "Domain Name System Structure and Delegation", 167 RFC 1591, March 1994. 169 [RFC 1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and 170 E. Lear, "Address Allocation for Private Internets", 171 BCP 5, RFC 1918, February 1996. 173 [ISO 3166-1] ISO 3166-1:2013 "Codes for the representation of names of 174 countries and their subdivisions -- Part 1: Country codes" 176 6.2. URIs 178 [ICANN ISO] https://www.icann.org/resources/pages/ 179 icann-iso-3166-2012-05-09-en 181 7. Author's Address 183 Edward Lewis 184 ICANN 186 Email: edward.lewis@icann.org 188 Roy Arends 189 ICANN 191 Email: roy.arends@icann.org 193 Arends Expires May 3, 2020 [Page 1]