idnits 2.17.1 draft-ma-v6ops-terminal-test-01.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 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 16, 2012) is 4299 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? 'RFC0791' on line 83 looks like a reference -- Missing reference section? 'RFC2460' on line 83 looks like a reference Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Q. Ma 3 Internet-Draft L. Li 4 Intended status: Informational T. Yang 5 Expires: January 17, 2013 China Mobile 6 July 16, 2012 8 Terminal Test of IPv6 support and DNS Query 9 draft-ma-v6ops-terminal-test-01 11 Abstract 13 This document introduces the terminal test under the WLAN environment 14 .The test includes the ability for terminal to obtain IPv6 address, 15 the sequence of DNS records query and termina behaviors in the 16 condition of DNS records abnormal, for example DNS records are 17 incorrect or absent. Several personal computers and smart phones 18 with different operational system have been tested. The test results 19 have been discussed and to share with internet community. 21 Status of this Memo 23 This Internet-Draft is submitted to IETF in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on January 17, 2013. 38 Copyright Notice 40 Copyright (c) 2012 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Terminal test . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2.1. Test topology and process . . . . . . . . . . . . . . . . . 3 58 2.2. test cases . . . . . . . . . . . . . . . . . . . . . . . . 4 59 2.3. Test results and analysis . . . . . . . . . . . . . . . . . 5 60 3. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 63 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 With fast development of global Internet, the demands for IP address 69 are rapidly increasing at present. IANA announced that the global 70 free pool of IPv4 depleted on February 3, 2011. IPv6 is only way to 71 satisfy demands of internet development. Operators have to 72 accelerate the process of deploying IPv6 networks in order to address 73 IP address strains. 75 DNS server provides name resolution and resource location services. 76 Domain Name Service translates queries for domain names (which are 77 meaningful to humans) into IP addresses for the purpose of locating 78 computer services and devices worldwide. Until IPv6 completely 79 supplants IPv4, most internet applications implement IPv4 and IPv6 80 protocol stacks either independently or in a hybrid form. In order 81 to establish transition strategy, China Mobile processed some tests 82 to make it clear that the behaviors of DNS server and terminal in a 83 dual stack ( IPv4 [RFC0791]+IPv6 [RFC2460] ) deployment and IPv6 only 84 deployment under the WLAN environment. 86 This document has described detailed testing topology, cases and 87 process. The testing results have been summarized and analyzed to 88 provide explicit conclusions for further deployment. 90 2. Terminal test 92 2.1. Test topology and process 94 +--------------+ +--------+ +-------+ +-------------+ 95 |PC/smart phone|-----| AP |-----| AC |-----|DNS Server | 96 +--------------+ +--------+ +-------+ | +-------------+ 97 | 98 | +-------------+ 99 +--|Web Server | 100 +-------------+ 102 Figure 1: Test topology 104 Figure 1 shows the configuration of terminal test environment. The 105 terminals include personal computer and smartphone, As an access 106 point, AP provided WLAN access environment. As an access controller 107 and DHCP server, AC assigned a terminal IP address and other 108 configuration information. The resource records in the DNS server 109 were deployed to some different conditions. 111 The tester make the terminal connected to AP, then input a domain 112 name in the terminal browser and try to visit the corresponding Web 113 page. The traffic flow between terminal and DNS/WEB server was 114 captured by packet analyzer. For PC terminal, message flow is 115 captured by a wireshark software in the PC. For smartphone terminal, 116 the message flow is captured from air interface. The massage flow is 117 analyzed and the results were summarized. 119 2.2. test cases 121 1.The ability for terminal to obtain IPv6 address 123 The DHCP server was set to assign the terminal IPv6 address using 124 stateless address autoconfiguration or DHCPv6, respectively. By 125 analyzing the packet to determine whether The terminals were able to 126 obtain IPv6 address and configuration information. 128 2.The behavior of DNS record query sequence 130 We tested terminal in three network scenarios in our labotory. 132 1)Terminals and DNS server all have dual stack (IPv4+IPv6) address; 134 2)terminals have dual stack (IPv4+IPv6) address and DNS server has 135 only IPv6 address; 137 3)Terminals and DNS server all have only IPv6 address; 139 There were four deployments of resource record corresponding to a 140 domain name in the DNS server: both A and AAAA record; only AAAA 141 record, nonexistent DNS record and error condition. The error 142 condition include: A record incorrect, AAAA record incorrect and both 143 incorrect. Table 1 shows the deployments of DNS records. 145 TABLE 1. Different deployments of DNS records 147 Domain name DNS record condition IP address 148 ----------------------------------------------------------------------- 149 www.a.com both A and AAAA 10.10.100.2/2002:200:200::2 150 www.b.com only AAAA 2002:200:200::2 151 www.c.com A incorrect 10.10.100.100/2002:200:200::2 152 www.d.com AAAA incorrect 10.10.100.2/2002:200:200::200 153 www.e.com both incorrect 10.10.100.100/2002:200:200::200 155 In above cases, terminal was connected to WLAN network and tried to 156 set up a TCP connection to visit a web page. The process of message 157 interactive between terminal and DNS/WEB server was captured and 158 analyzed. 160 2.3. Test results and analysis 162 (1)The IPv6 support in the operating systems is not perfect. Some 163 operating sysytems are not able to obtain IPv6 address and DNS using 164 DHCPv6. 166 (2) The sequence of DNS query depends on the operating system of 167 terminal.In the case of dual stack, termianls will look up A and AAAA 168 record in turn. Some terminals look up the DNS record using IPv6 169 address firstly, while others using IPv4 address firstly. 171 (3) Certain operating systems have naive algorithm. In the case of 172 assigned only IPv6 address, the terminal requests an A type record 173 firstly. It is unnecessary for a terminal with only IPv6 address to 174 look up an A type record. 176 (4) Certain terminals carry unnecessary DNS queries. When there is 177 only AAAA record in the DNS sever and terminal have dual stack 178 addresses, certain operating system will look up an A record 179 corresponding to a domain name several times after getting AAAA 180 record, even after having visited the web page with AAAA record 181 successfully. For a non-existent domain name, most terminals prefer 182 to query all DNS records including A and AAAA, though they have 183 received the "no such name" reply corresponding to the first query. 185 (5) When obtaining both A and AAAA record , certain of terminals 186 prefer using AAAA record to visit the web site. If terminals fail to 187 set up a TCP connection using AAAA record due to incorrect AAAA 188 record, it will retry two times with AAAA record, and then turn to 189 use the A record. 191 (6)Without IPv4 address, some operating sysytems can not visit the 192 web page properly with only IPv6 address, and of course all the 193 tested teminals can work with only IPv4 address without IPv6 address. 195 (7)The happy eyeballs (RFC6555) mechanism is used to improve the 196 dual-stack users experience. Amony all the tested operating 197 sysytems, the happy eyeballs mechanism is not observed. 199 3. Conclusion 201 The test results show that the IPv6 support in the operational 202 systems are not perfect. There are many unnecessary DNS queries and 203 traffic flows. It has the potential to cause a DNS server and 204 network overloaded. In the development of transition strategy form 205 IPv4 to IPv6, the test results will be taken into account and pay 206 more attention. 208 4. Security Considerations 210 It needs to be further identified. 212 5. IANA Considerations 214 TBD 216 6. Acknowledgement 218 Thanks for the contributions from Fan Peng. 220 Authors' Addresses 222 Ma Qiongfang 223 China Mobile 224 32, Xuanwumenxi Ave. 225 Xicheng District, Beijing 01719 226 China 228 Email: maqiongfang@chinamobile.com 230 Li Lianyuan 231 China Mobile 232 32, Xuanwumenxi Ave. 233 Xicheng District, Beijing 01719 234 China 236 Email: lilianyuan@chinamobile.com 238 Yang Tianle 239 China Mobile 240 32, Xuanwumenxi Ave. 241 Xicheng District, Beijing 01719 242 China 244 Email: yangtianle@chinamobile.com