Network Working Group J. Yao Internet-Draft CNNIC Intended status: Informational October 15, 2012 Expires: April 13, 2013 TLD names usage advice draft-yao-dnsop-tld-names-00.txt Abstract This document analyzes the TLD names usage and gives some advices. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on April 13, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this Yao Expires April 13, 2013 [Page 1] Internet-Draft tldname October 2012 material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Current situations for TLD names . . . . . . . . . . . . . . . 3 2.1. TLD names in the DNS zones . . . . . . . . . . . . . . . . 3 2.2. TLD names in the DNS stub resolvers . . . . . . . . . . . . 3 2.3. TLD names in the application . . . . . . . . . . . . . . . 3 3. TLD name usage advice . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. Change History . . . . . . . . . . . . . . . . . . . . . . . . 4 7.1. draft-yao-dnsop-tld-name: Version 00 . . . . . . . . . . . 4 8. Normative References . . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Yao Expires April 13, 2013 [Page 2] Internet-Draft tldname October 2012 1. Introduction The new generic top-level domain (gTLD) program of ICANN will introduce thousands of new TLD names to the root of the domain name system (DNS). Many new TLD names are the names or brands of some companies. These companies may want to use these TLD names directly in the application. If ABCD company has the TLD name "ABCD", this company may try to configure some DNS records for "ABCD" and uses it in some applications such as web and email. The users might put the URL http://ABCD/ or http://ABCD./ in the web browser to visit ABCD's homepage. The user might try to send the email to "administrator@abcd.". These operations might work or not, depending on the different scenarios or contexts. In order to have a good users' experences, some advice should be made to the TLD name owners. This document analyzes the TLD names usage and gives some advices. 1.1. Terminology All the basic terms used in this specification are defined in the documents [RFC1034] and [RFC1035]. 2. Current situations for TLD names 2.1. TLD names in the DNS zones TLD names are legal in the DNS zones. The user can configure any records for it. 2.2. TLD names in the DNS stub resolvers Different DNS stub resolvers may not always return the same result due to different configuration. This is caused by what is known as the "search path" option. The stub resolvers may try to search the TLD name adding a search path such as "example.com". And only if the query gets a nonexistent domain (NXDOMAIN) response for the TLD name adding a search path, the stub resolver would try TLD name directly. 2.3. TLD names in the application Many application protocols do not insist that domain names always be fully qualified. That means that the domain names in the application can use single label instead of multi-labels. But many applications implemented refuse to regard the TLD names as the domain names. For example, for easy connection in the LAN, some users may configure the below record in the windows systym's hosts file. Yao Expires April 13, 2013 [Page 3] Internet-Draft tldname October 2012 192.168.1.1 apple. then we can easily connect to apple machine via http://apple./ or http://apple/ The users trying to visit the homepage of apple will go to the local machine directly instead of trying to search the name via DNS. 3. TLD name usage advice This document suggests not to configure TLD names with other RRs other than with NS related record in the root or TLD DNS server. If the users decide to use it, they should know that TLD names might not be universally reachable. 4. IANA Considerations There is no IANA consideration. 5. Security Considerations TBD 6. Acknowledgements TBD 7. Change History [[anchor10: RFC Editor: Please remove this section.]] 7.1. draft-yao-dnsop-tld-name: Version 00 o TLD name usage and advice 8. Normative References [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", Yao Expires April 13, 2013 [Page 4] Internet-Draft tldname October 2012 STD 13, RFC 1034, November 1987. [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987. Author's Address Jiankang YAO CNNIC No.4 South 4th Street, Zhongguancun Beijing Phone: +86 10 58813007 Email: yaojk@cnnic.cn Yao Expires April 13, 2013 [Page 5]