idnits 2.17.1 draft-yao-dnsop-tld-names-00.txt: 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: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 15, 2012) is 4209 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Yao 3 Internet-Draft CNNIC 4 Intended status: Informational October 15, 2012 5 Expires: April 13, 2013 7 TLD names usage advice 8 draft-yao-dnsop-tld-names-00.txt 10 Abstract 12 This document analyzes the TLD names usage and gives some advices. 14 Status of this Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on April 13, 2013. 31 Copyright Notice 33 Copyright (c) 2012 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 This document may contain material from IETF Documents or IETF 47 Contributions published or made publicly available before November 48 10, 2008. The person(s) controlling the copyright in some of this 49 material may not have granted the IETF Trust the right to allow 50 modifications of such material outside the IETF Standards Process. 51 Without obtaining an adequate license from the person(s) controlling 52 the copyright in such materials, this document may not be modified 53 outside the IETF Standards Process, and derivative works of it may 54 not be created outside the IETF Standards Process, except to format 55 it for publication as an RFC or to translate it into languages other 56 than English. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Current situations for TLD names . . . . . . . . . . . . . . . 3 63 2.1. TLD names in the DNS zones . . . . . . . . . . . . . . . . 3 64 2.2. TLD names in the DNS stub resolvers . . . . . . . . . . . . 3 65 2.3. TLD names in the application . . . . . . . . . . . . . . . 3 66 3. TLD name usage advice . . . . . . . . . . . . . . . . . . . . . 4 67 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 68 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 69 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 70 7. Change History . . . . . . . . . . . . . . . . . . . . . . . . 4 71 7.1. draft-yao-dnsop-tld-name: Version 00 . . . . . . . . . . . 4 72 8. Normative References . . . . . . . . . . . . . . . . . . . . . 4 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 1. Introduction 77 The new generic top-level domain (gTLD) program of ICANN will 78 introduce thousands of new TLD names to the root of the domain name 79 system (DNS). Many new TLD names are the names or brands of some 80 companies. These companies may want to use these TLD names directly 81 in the application. If ABCD company has the TLD name "ABCD", this 82 company may try to configure some DNS records for "ABCD" and uses it 83 in some applications such as web and email. The users might put the 84 URL http://ABCD/ or http://ABCD./ in the web browser to visit ABCD's 85 homepage. The user might try to send the email to 86 "administrator@abcd.". These operations might work or not, depending 87 on the different scenarios or contexts. In order to have a good 88 users' experences, some advice should be made to the TLD name owners. 89 This document analyzes the TLD names usage and gives some advices. 91 1.1. Terminology 93 All the basic terms used in this specification are defined in the 94 documents [RFC1034] and [RFC1035]. 96 2. Current situations for TLD names 98 2.1. TLD names in the DNS zones 100 TLD names are legal in the DNS zones. The user can configure any 101 records for it. 103 2.2. TLD names in the DNS stub resolvers 105 Different DNS stub resolvers may not always return the same result 106 due to different configuration. This is caused by what is known as 107 the "search path" option. The stub resolvers may try to search the 108 TLD name adding a search path such as "example.com". And only if the 109 query gets a nonexistent domain (NXDOMAIN) response for the TLD name 110 adding a search path, the stub resolver would try TLD name directly. 112 2.3. TLD names in the application 114 Many application protocols do not insist that domain names always be 115 fully qualified. That means that the domain names in the application 116 can use single label instead of multi-labels. But many applications 117 implemented refuse to regard the TLD names as the domain names. For 118 example, for easy connection in the LAN, some users may configure the 119 below record in the windows systym's hosts file. 121 192.168.1.1 apple. 123 then we can easily connect to apple machine via 125 http://apple./ 126 or 127 http://apple/ 129 The users trying to visit the homepage of apple will go to the local 130 machine directly instead of trying to search the name via DNS. 132 3. TLD name usage advice 134 This document suggests not to configure TLD names with other RRs 135 other than with NS related record in the root or TLD DNS server. If 136 the users decide to use it, they should know that TLD names might not 137 be universally reachable. 139 4. IANA Considerations 141 There is no IANA consideration. 143 5. Security Considerations 145 TBD 147 6. Acknowledgements 149 TBD 151 7. Change History 153 [[anchor10: RFC Editor: Please remove this section.]] 155 7.1. draft-yao-dnsop-tld-name: Version 00 157 o TLD name usage and advice 159 8. Normative References 161 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 162 STD 13, RFC 1034, November 1987. 164 [RFC1035] Mockapetris, P., "Domain names - implementation and 165 specification", STD 13, RFC 1035, November 1987. 167 Author's Address 169 Jiankang YAO 170 CNNIC 171 No.4 South 4th Street, Zhongguancun 172 Beijing 174 Phone: +86 10 58813007 175 Email: yaojk@cnnic.cn