Network Working Group Yuping Diao Internet-Draft Guangdong Commercial College Intended status: standard Yongping Diao Expires: December 13, 2012 China Telecom Ming Liao China Mobile June 13, 2012 DNS Extension for Autonomous Internet(AIP) draft-diao-aip-dns-00.txt Abstract With the reality of Internet, Autonomous Internet technology in this article constructs independent autonomous extensible domain name architecture and domain name hierarchy through current domain name architecture, provides independent root DNS server, inner/outer DNS resolution mechanism for each autonomous internet network system, and provides reformation and transition solution from current Internet to realize autonomy even in unilateral action. Status of this Memo This Internet-Draft is submitted to IETF 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 December 13, 2012. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. Diao, et al. Expires December 13, 2012 [Page 1]

Internet-Draft DNS Extension for Autonomous Internet June 2012 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. Diao, et al. Expires December 13, 2012 [Page 2]

Internet-Draft DNS Extension for Autonomous Internet June 2012 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Specification of Requirements . . . . . . . . . . . . . . . 4 2. Autonomous Internet DNS Design . . . . . . . . . . . . . . . . 4 2.1. AIP DNS Design Goal . . . . . . . . . . . . . . . . . . . . 4 2.2. AIP DNS Hierarchy . . . . . . . . . . . . . . . . . . . . . 5 2.3. AIP DNS Architecture and Transformation . . . . . . . . . . 6 3. AIP DNS Resolution Procedure. . . . . . . . . . . . . . . . . . 7 3.1. Domain Name Resolution within AIP Network . . . . . . . . . 7 3.2. Domain Name Resolution between AIP Networks . . . . . . . . 8 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Diao, et al. Expires December 13, 2012 [Page 3]

Internet-Draft DNS Extension for Autonomous Internet June 2012 1 . Introduction 1.1 . Specification of Requirements RFC2119]. 2 . Autonomous Internet DNS Design 2.1 . AIP DNS Design Goal Diao, et al. Expires December 13, 2012 [Page 4]

Internet-Draft DNS Extension for Autonomous Internet June 2012 2.2 . AIP DNS Hierarchy Diao, et al. Expires December 13, 2012 [Page 5]

Internet-Draft DNS Extension for Autonomous Internet June 2012 2.3 . AIP DNS Architecture and Transformation Diao, et al. Expires December 13, 2012 [Page 6]

Internet-Draft DNS Extension for Autonomous Internet June 2012 Each AIP network is almost the same as the current Internet, and the internal domain name resolution and IP node communication have not any change. The only change is that the destination domain name need add domain name suffix of the destination AIP network when IP nodes communicate between different AIP networks. Therefore, each AIP network will add a device called "AIP DNS gateway" (AIP DNS GW) to support domain name resolution between AIP networks. On one hand, it forwards its external DNS resolution request to the destination AIP network, returns the DNS resolution result to internal requester; On the other hand, it receives DNS resolution request from external AIP networks, feedback the DNS resolution result to the external AIP network requester, which at first it would get the internal DNS resolution result according to the traditional way. In order to realize the transition from Internet to Autonomous Internet, each partition of current Internet should first realize possible self-government and gradually reduce its dependence on the foreign domain names, such as COM, NET et al. Then to each AIP network, we can establish a new autonomous DNS, or Upgrade one part of current Internet DNS (core part or non core part) to a new autonomous DNS. Unilateral action: It is not likely the whole Internet can be transformed synchronally in one time. In order not to affect existing domain name resolution before the Internet core part transforms into an AIP network, any country can set up an AIP DNS independently and connect to the Internet through the original link; or any two countries in agreement can set up their AIP networks and connect to each others. There is something different in the unilateral action. On one hand, the upgrade work is including of new added local AIP network root DNS server to construct an independent DNS, and an AIP DNS GW deployment to support domain name resolution between AIP networks. On the other hand, it is necessary to add a pre-transformed AIP DNS GW in each AIP network connecting to the Internet (core part) DNS instead of the original transformation requirement for Internet core part. The pre-transformed AIP DNS GW would initiatively add the domain name suffix to the domain name from the existing Internet (core part), which is the only difference from normal AIP DNS GW. 3 . AIP DNS Resolution Procedure 3.1 . Domain Name Resolution within AIP Network Diao, et al. Expires December 13, 2012 [Page 7]

Internet-Draft DNS Extension for Autonomous Internet June 2012 3.2 . Domain Name Resolution between AIP Networks Diao, et al. Expires December 13, 2012 [Page 8]

Internet-Draft DNS Extension for Autonomous Internet June 2012 Step 4: Local DNS server send the query to the returned DNS server (AIP DNS GW A) IP address again. 1) When receive the query, AIP DNS GW A inquire its cache and return the result. But if there is no record for the query, AIP DNS GW A would send query to AIP DNS GW B in AIP network B. 2) When receive the query, AIP DNS GW B inquire its cache and return the result. But if there is no record for the query, AIP DNS GW B would get rid of the local AIP network domain name suffix ".B" from external domain name "Nb2.B", then send query with th internal domain name "Nb2" to root DNS server of local AIP network B. 3) Root DNS server of local AIP network B return a primary DNS server IP address of queried domain (sub-domain of root domain name, such as COM) to AIP DNS GW B. 4) AIP DNS GW B sends the query to the last step 3) returned DNS server IP address again. After receive the query, this DNS server inquire (its cache) and return the corresponding record or the corresponding lower-level DNS server IP address. 5) AIP DNS GW B repeats last step 4) until it finds the correct record, namely the IP address Gb2 of the domain name Nb2. 6) AIP DNS GW B turns the internal domain name "Nb2" into externa domain name "Nb2.B" in the returned result by adding local AIP network domain name suffix "B", and then caches the result and return the result to AIP DNS GW A. Step 5: AIP DNS GW A caches the returned result and return the result to local DNS server. Step 6: Local DNS server caches the returned result and returns the result to source host Na1. Therefore, host Na1 (Ga1) now can communicate with host Nb2 (Gb2) after it gets the IP address of the destination host Nb2. 4 . Conclusion Diao, et al. Expires December 13, 2012 [Page 9]

Internet-Draft DNS Extension for Autonomous Internet June 2012 Authors' Addresses Yuping Diao Information Institute of Guangdong Commercial College, 21 Luntou Road, Haizhu District, Guangzhou 510320, China. Email: teacherdddd@yahoo.com.cn Yongping Diao China Telecom-Guangzhou Institute, 109 West Zhongshan Ave, Guangzhou 510630, China. Phone: +86 20 38639732 Email: diaoyp@yahoo.com Ming Liao China Mobile Group Guangdong Co., Ltd. Guangzhou Branch, 610 Tianhe North Road, Guangzhou 510631, China. Email: 644247110@qq.com Diao, et al. Expires December 13, 2012 [Page 11]