idnits 2.17.1 draft-liu-softwire-experience-map-02.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 8 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 4 instances 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. == There are 4 instances 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 (March 3, 2014) is 3707 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC6144' is mentioned on line 91, but not defined == Missing Reference: 'RFC6145' is mentioned on line 91, but not defined ** Obsolete undefined reference: RFC 6145 (Obsoleted by RFC 7915) == Missing Reference: 'RFC6146' is mentioned on line 91, but not defined == Missing Reference: 'I-D.draft-ietf-softwire-map-t' is mentioned on line 126, but not defined == Unused Reference: 'I-D.ietf-softwire-map-t' is defined on line 300, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-softwire-map' is defined on line 306, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 312, but no explicit reference was found in the text == Unused Reference: 'I-D.cordeiro-softwire-experience-mapt' is defined on line 317, but no explicit reference was found in the text == Unused Reference: 'I-D.hazeyama-widecamp-ipv6-only-experience' is defined on line 322, but no explicit reference was found in the text == Unused Reference: 'I-D.xli-softwire-map-testing' is defined on line 329, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-softwire-map-t-05 == Outdated reference: A later version (-13) exists of draft-ietf-softwire-map-10 == Outdated reference: A later version (-09) exists of draft-xli-softwire-map-testing-03 Summary: 1 error (**), 0 flaws (~~), 17 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force X. Liu 3 Internet-Draft B. Yan 4 Intended status: Informational CNIC / Chinese Academy of Sciences 5 Expires: September 4, 2014 C. Bao 6 X. Li 7 CERNET Center / Tsinghua University 8 March 3, 2014 10 Experience from Double Translation and Encapsulation (MAP) Testing 11 draft-liu-softwire-experience-map-02 13 Abstract 15 This document discusses the experiences of using Mapping of Address 16 and Port (MAP). 18 Network setup and testing results using MAP-Translation (MAP-T), MAP- 19 Encapsulation (MAP-E) and mixed MAP-T/MAP-E are described in this 20 document. 22 Relationships among native IPv6, single translation, double 23 translation, and encapsulation are also discussed. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 4, 2014. 42 Copyright Notice 44 Copyright (c) 2014 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Technology and Terminology . . . . . . . . . . . . . . . . . 3 61 3. Network and Experiment Setup . . . . . . . . . . . . . . . . 3 62 3.1. Network Topology . . . . . . . . . . . . . . . . . . . . 3 63 3.2. Test Content . . . . . . . . . . . . . . . . . . . . . . 4 64 4. General Experiences . . . . . . . . . . . . . . . . . . . . . 6 65 5. Discussion of relationships among native IPv6, single 66 translation, double translation and encapsulation . . . . . . 6 67 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 68 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 70 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 72 9.2. Informative References . . . . . . . . . . . . . . . . . 7 73 Appendix A. Configuration Files . . . . . . . . . . . . . . . . 8 74 A.1. MAP-T Core Configuration . . . . . . . . . . . . . . . . 8 75 A.2. MAP-E Core Configuration . . . . . . . . . . . . . . . . 8 76 A.3. MAP-T CPE Configuration . . . . . . . . . . . . . . . . . 9 77 A.4. MAP-E CPE Configuration . . . . . . . . . . . . . . . . . 10 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 80 1. Introduction 82 In recent years, many researchers focus on the IPv6-only network. 84 Users or applications in IPv6-only environment may meet with 85 difficulties when visiting IPv4 resources, e.g. big data visiting or 86 migration. 88 From May 2012, CNIC (Computer Network Information Center) in Chinese 89 Academy of Sciences performed a series of experiments on the 90 comparison with native IPv6 and single translation using NAT64/DNS64 91 [RFC6144][RFC6145][RFC6146]. 93 Although many applications work correctly, there are problems that 94 single translation cannot solve, these problems are also mentioned in 95 IETF's IPv6-only experiences [RFC6586] and [I-D.draft-hazeyama- 96 widecamp-ipv6-only-experience]: 98 Several OSes and devices do not work in IPv6-only network; access 99 difficulties happen when IPv4 address literal is embedded in the 100 application; ALG problem, e.g. FTP; etc. 102 Double translation or encapsulation can solve the problems we have 103 when single translation is used. 105 This document presents our experience from the network experiment 106 using double translation and encapsulation named Mapping of Address 107 and Port (MAP). Common applications are tested in MAP-T, MAP-E, and 108 mixed MAP-T/MAP-E modes. 110 We refer to the IETF's MAP-T testing results [I-D.draft-cordeiro- 111 softwire-experience-mapt], we add some applications test with Chinese 112 applications, and try to clarify new issues on the relationships 113 among native IPv6, single translation, double translation, and 114 encapsulation in the environment. 116 Subjectively, we didn't find significant differences when using 117 applications in MAP-T, and MAP-E mode. MAP-T can support IPv6-only 118 server. 120 2. Technology and Terminology 122 In this document, the following terms are used. 124 "MAP-T" refers to MAP double stateless translation based solution for 125 providing IPv4 hosts connectivity to and across an IPv6 domain, as 126 defined by [I-D.draft-ietf-softwire-map-t]. 128 "MAP-E" refers to MAP Encapsulation based solution with an automatic 129 tunneling mechanism for providing IPv4 connectivity service to end 130 users over service provider's IPv6 network, as defined by [I-D.draft- 131 ietf-softwire-map]. 133 3. Network and Experiment Setup 135 3.1. Network Topology 136 ------ 137 | Host | 138 | 3 | 139 ------ 140 |IPv6 141 ---------- +--------+ 142 / CSTNET \ IPv4 ------ IPv6| IPv6 |IPv6 ------ IPv4 ------ 143 | IPv4 Network |----| MAP |----| only |----| MAP |----| Host | 144 \ (Net 1) / | Core | | Router | | CPE | | 1 | 145 ---------- ------ +--------+ ------ ------ 146 | | 147 |IPv6 |IPv4 ------ 148 | |-------| Host | 149 ---------- | 2 | 150 / CSTNET \ ------ 151 | IPv6 Network | 152 \ (Net 2) / 153 ---------- 155 Network Topology 157 Figure 1 159 The MAP core and MAP CPE support both MAP-T and MAP-E modes, running 160 Fedora 11 and MAP-T 2.2c and MAP-E 2.2c software developed by CERNET 161 (http://mapt.ivi2.org:8039/mapt.html). 163 We use three host machines in the experiment, Host 1 and Host 2 are 164 IPv4-only PC with Windows 7 and Linux Ubuntu 12.04, Host 3 is 165 IPv6-only PC with Windows 7. 167 Net 1 is an IPv4 network with public valid IPv4 address, Net 2 is an 168 IPv6 network with public valid IPv6 address. Both Net 1 and Net 2 169 are supported by CSTNET. 171 The configuration of MAP-T/MAP-E core, MAP-T/MAP-E CPE is shown in 172 Appendix part. DHCP function is not used in this experiment. 174 3.2. Test Content 176 We tested difference applications in different OS:Windows 7 and Linux 177 Ubuntu 12.04. 179 +------------------+--------------+---------------------------------+ 180 | content | categories | applications | 181 +------------------+--------------+---------------------------------+ 182 | Normal | Browser | Internet Explorer, Mozilla | 183 | Applications | | Firefox, Google Chrome, Safari | 184 | | On-line | Flash, Java applets | 185 | | games | | 186 | Client/Server | Web | IPv4/IPv6 website: Google.com, | 187 | Applications | | Yahoo.com; | 188 | | | IPv4 website: Baidu.com, | 189 | | | Yahoo.com.cn | 190 | | e-mail | Gmail, Yahoo mail, Hotmail | 191 | | video stream | Address-based indexing: | 192 | | | youku.com, ku6.com | 193 | | | Domain name-based indexing: | 194 | | | Sina video | 195 | Peer to Peer | File | BitTorrent | 196 | Applications | distribution | | 197 | | VOIP | Skype, Voipcheap | 198 | | IPTV | PPTV | 199 | | Instant | Client Messaging: MSN | 200 | | Messaging | Messenger, QQ, Skype | 201 | | | Web Messaging: Renren, Weibo | 202 | Security | Antivirus | 360, AVG | 203 +------------------+--------------+---------------------------------+ 205 Table 1: Test Content 207 Besides the applications tested in [draft-cordeiro-softwire- 208 experience-mapt], we add applications with Chinese characteristics, 209 like Baidu.com, Yahoo.com.cn (IPv4 website); video stream series; 210 PPTV (IPTV), QQ (Instant Messaging), 360 (Antivirus). 212 In Web test, we separate IPv4/IPv6 website and IPv4 website for 213 checking whether A or AAAA record is received. 215 In video-stream test, we separate Address-based indexing and Domain 216 name-based indexing. Since in former single translation (NAT64) 217 test, only Domain name-based indexing video-stream works well, 218 problem occurs when visiting video-stream with IPv4 address literals 219 indexing. 221 Security test, like Firewall, IPSEC, VPN are not tested in this 222 experiment. 224 Applications with IPv4 address literals, like HTTP, SSH, VNC are not 225 tested in this experiment. 227 4. General Experiences 229 For MAP-T and MAP-E test, subjectively we didn't find significant 230 differences compared to native IPv4 environment using Windows 7 and 231 Ubuntu 12.04: 233 in Internet Applications (Normal) test, the browsers and online game 234 works correctly; 236 in Internet Applications (C/S) test, we visited the website, e-mail, 237 video stream without problems, only IPv4 resources are visited; 239 in Internet Applications (P2P) test, we also had good experience with 240 file distribution, VOIP, IPTV, and instant messaging; 242 in security application, the antivirus software works correctly and 243 can be updated. 245 For mixed MAP-T/MAP-E test, since the forwarding mode is only 246 required in the IPv4 to IPv6 direction, and it can be automatically 247 identified by checking the value of the next header in IPv6 packets 248 in the IPv6 to IPv4 direction. In the test, we first set MAP core 249 with MAP-T mode and CPE with MAP-E mode; then set MAP core with MAP-E 250 mode and CPE with MAP-T mode. The applications also work correctly. 252 5. Discussion of relationships among native IPv6, single translation, 253 double translation and encapsulation 255 For the new users, we suggest to build IPv6-only network and the 256 transition of IPv4 to IPv6 includes four types: native IPv6, single 257 translation, double translation, encapsulation. 259 In this scenario, the host first tries to visit server in native mode 260 (IPv6 to IPv6); 262 If the host and server are in different environment, the host tries 263 single translation (IPv6 to IPv4); 265 If there are access difficulties using single translation (ALG, 266 IPv4-only application, etc), the host tries double translation (IPv6 267 to IPv4 to IPv6); 269 For some applications (IPSec), if double translation doesn't work, 270 the host uses encapsulation (IPv4 over IPv6). 272 The topology shown in Figure 1 concludes the four steps: 274 The process Host 1/Host 2 - CPE - IPv6 Router - core - IPv4 Internet 275 is for double translation and encapsulation; 277 The process Host 3 - IPv6 Router - IPv6 Network is for native IPv6; 279 The process Host 1/Host 2 - CPE - IPv6 Router - IPv6 Network is for 280 single translation. 282 6. Acknowledgements 284 We would like to thank Guoliang Han from CERNET/Tsinghua University, 285 and Dujuan Gu, Shuangjian Yan from CNIC/Chinese Academy of Sciences 286 on this experiment. 288 7. IANA Considerations 290 This document has no IANA implications. 292 8. Security Considerations 294 This document has no security implications. 296 9. References 298 9.1. Normative References 300 [I-D.ietf-softwire-map-t] 301 Li, X., Bao, C., Dec, W., Troan, O., Matsushima, S., and 302 T. Murakami, "Mapping of Address and Port using 303 Translation (MAP-T)", draft-ietf-softwire-map-t-05 (work 304 in progress), February 2014. 306 [I-D.ietf-softwire-map] 307 Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S., 308 Murakami, T., and T. Taylor, "Mapping of Address and Port 309 with Encapsulation (MAP)", draft-ietf-softwire-map-10 310 (work in progress), January 2014. 312 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 313 Requirement Levels", BCP 14, RFC 2119, March 1997. 315 9.2. Informative References 317 [I-D.cordeiro-softwire-experience-mapt] 318 Cordeiro, E., Carnier, R., and A. Moreiras, "Experience 319 from MAP-T Testing", draft-cordeiro-softwire-experience- 320 mapt-02 (work in progress), September 2013. 322 [I-D.hazeyama-widecamp-ipv6-only-experience] 323 Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura, 324 "Experiences from IPv6-Only Networks with Transition 325 Technologies in the WIDE Camp Autumn 2012", draft- 326 hazeyama-widecamp-ipv6-only-experience-02 (work in 327 progress), October 2012. 329 [I-D.xli-softwire-map-testing] 330 Li, X., Bao, C., Han, G., and W. Dec, "MAP 331 Interoperability Testing Results", draft-xli-softwire-map- 332 testing-03 (work in progress), January 2014. 334 [RFC6586] Arkko, J. and A. Keranen, "Experiences from an IPv6-Only 335 Network", RFC 6586, April 2012. 337 Appendix A. Configuration Files 339 A.1. MAP-T Core Configuration 341 #!/bin/sh 343 # configure system profile 344 echo 1 > /proc/sys/net/ipv4/ip_forward 345 echo 1 > /proc/sys/net/ipv6/conf/all/forwarding 346 echo 0 > /proc/sys/net/ipv6/conf/eth1/autoconf 347 echo 0 > /proc/sys/net/ipv6/conf/eth0/autoconf 349 # configure eth0 -- IPv4 interface 350 /sbin/ifdown eth0 351 /sbin/ip link set eth0 up 352 /sbin/ip addr add 159.226.15.173/30 dev eth0 353 /sbin/ip route add default via 159.226.15.129 dev eth0 355 control start 356 utils/ivictl -r -p 159.226.15.174/32 -P 2001:cc0:2003:fff0::/60 357 -R 16 -M 1 -T 358 utils/ivictl -r -d -P 2001:cc0:2003:ffff::/64 -T 359 utils/ivictl -s -i eth0 -I eth1 361 service iptables stop 362 service ip6tables stop 364 A.2. MAP-E Core Configuration 365 #!/bin/sh 367 # configure system profile 368 echo 1 > /proc/sys/net/ipv4/ip_forward 369 echo 1 > /proc/sys/net/ipv6/conf/all/forwarding 370 echo 0 > /proc/sys/net/ipv6/conf/eth1/autoconf 371 echo 0 > /proc/sys/net/ipv6/conf/eth0/autoconf 373 # configure eth0 -- IPv4 interface 374 /sbin/ifdown eth0 375 /sbin/ip link set eth0 up 376 /sbin/ip addr add 159.226.15.173/30 dev eth0 377 /sbin/ip route add default via 159.226.15.129 dev eth0 379 control start 380 utils/ivictl -r -p 159.226.15.174/32 -P 2001:cc0:2003:fff0::/60 381 -R 16 -M 1 -E 382 utils/ivictl -r -d -P 2001:cc0:2003:ffff::1/128 -E 384 utils/ivictl -s -i eth0 -I eth1 386 service iptables stop 387 service ip6tables stop 389 A.3. MAP-T CPE Configuration 391 #!/bin/sh 393 # configure system profile 394 echo 1 > /proc/sys/net/ipv4/ip_forward 395 echo 1 > /proc/sys/net/ipv6/conf/all/forwarding 396 echo 0 > /proc/sys/net/ipv6/conf/eth0.2/autoconf 397 echo 0 > /proc/sys/net/ipv6/conf/br-lan/autoconf 399 # configure eth1 -- IPv4 interface 400 ifconfig br-lan 192.168.1.1/24 402 ./control start 404 utils/ivictl -r -d -P 2001:cc0:2003:ffff::/64 405 utils/ivictl -s -i br-lan -I eth0.2 -H -N -a 192.168.1.0/24 406 -A 159.226.15.174/32 -P 2001:cc0:2003:fff0::/60 407 -R 16 -M 1 -o 0 -c 1440 -T 409 #service iptables stop 410 #service ip6tables stop 412 A.4. MAP-E CPE Configuration 414 #!/bin/sh 416 # configure system profile 417 echo 1 > /proc/sys/net/ipv4/ip_forward 418 echo 1 > /proc/sys/net/ipv6/conf/all/forwarding 419 echo 0 > /proc/sys/net/ipv6/conf/eth0.2/autoconf 420 echo 0 > /proc/sys/net/ipv6/conf/br-lan/autoconf 422 # configure eth1 -- IPv4 interface 423 ifconfig br-lan 192.168.1.1/24 425 ./control start 427 # encapsulate mode 1: /128 address is configured directly 428 utils/ivictl -r -d -P 2001:cc0:2003:ffff::1/128 429 utils/ivictl -s -i br-lan -I eth0.2 -H -N -a 192.168.1.0/24 430 -A 159.226.15.174/32 -P 2001:cc0:2003:fff0::/60 431 -R 16 -M 1 -o 0 -c 1400 -E 433 #service iptables stop 434 #service ip6tables stop 436 Authors' Addresses 438 Xiaohan Liu 439 CNIC / Chinese Academy of Sciences 440 4,4th South Street Zhongguancun, Haidian District 441 Beijing 100190 442 CN 444 Email: liuxiaohan@cnic.cn 446 Baoping Yan 447 CNIC / Chinese Academy of Sciences 448 4,4th South Street Zhongguancun, Haidian District 449 Beijing 100190 450 CN 452 Email: ybp@cnic.cn 453 Congxiao Bao 454 CERNET Center / Tsinghua University 455 Room 225, Main Building, Tsinghua University 456 Beijing 100084 457 CN 459 Email: congxiao@cernet.edu.cn 461 Xing Li 462 CERNET Center / Tsinghua University 463 Room 225, Main Building, Tsinghua University 464 Beijing 100084 465 CN 467 Email: xing@cernet.edu.cn