idnits 2.17.1 draft-ietf-v6ops-464xlat-05.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 3, 2012) is 4314 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '02-00-5E-10-00-00-00-00' is mentioned on line 700, but not defined == Unused Reference: 'RFC6144' is defined on line 553, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 6144 ** Obsolete normative reference: RFC 6145 (Obsoleted by RFC 7915) == Outdated reference: A later version (-02) exists of draft-hazeyama-widecamp-ipv6-only-experience-01 == Outdated reference: A later version (-17) exists of draft-ietf-behave-nat64-discovery-heuristic-10 -- Obsolete informational reference (is this intentional?): RFC 3633 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 5342 (Obsoleted by RFC 7042) Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force M. Mawatari 3 Internet-Draft Japan Internet Exchange Co.,Ltd. 4 Intended status: BCP M. Kawashima 5 Expires: January 4, 2013 NEC AccessTechnica, Ltd. 6 C. Byrne 7 T-Mobile USA 8 July 3, 2012 10 464XLAT: Combination of Stateful and Stateless Translation 11 draft-ietf-v6ops-464xlat-05 13 Abstract 15 This document describes an architecture (464XLAT) for providing 16 limited IPv4 connectivity across an IPv6-only network by combining 17 existing and well-known stateful protocol translation RFC 6146 in the 18 core and stateless protocol translation RFC 6145 at the edge. 464XLAT 19 is a simple and scalable technique to quickly deploy limited IPv4 20 access service to IPv6-only edge networks without encapsulation. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 4, 2013. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 58 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Motivation and Uniqueness of 464XLAT . . . . . . . . . . . . . 4 60 5. Network Architecture . . . . . . . . . . . . . . . . . . . . . 4 61 5.1. Wireline Network Architecture . . . . . . . . . . . . . . 4 62 5.2. Wireless 3GPP Network Architecture . . . . . . . . . . . . 5 63 6. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 6 64 6.1. Wireline Network Applicability . . . . . . . . . . . . . . 6 65 6.2. Wireless 3GPP Network Applicability . . . . . . . . . . . 7 66 7. Implementation Considerations . . . . . . . . . . . . . . . . 7 67 7.1. IPv6 Address Format . . . . . . . . . . . . . . . . . . . 7 68 7.2. IPv4/IPv6 Address Translation Chart . . . . . . . . . . . 7 69 7.2.1. Case of enabling only stateless XLATE on CLAT . . . . 7 70 7.2.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 9 71 7.3. IPv6 Prefix Handling . . . . . . . . . . . . . . . . . . . 11 72 7.3.1. Case of enabling only stateless XLATE on CLAT . . . . 11 73 7.3.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 11 74 7.4. Traffic Treatment Scenarios . . . . . . . . . . . . . . . 12 75 7.5. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 12 76 7.6. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 12 77 7.7. CLAT to CLAT communications . . . . . . . . . . . . . . . 12 78 8. Deployment Considerations . . . . . . . . . . . . . . . . . . 13 79 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13 80 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 81 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 82 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 83 12.1. Normative References . . . . . . . . . . . . . . . . . . . 14 84 12.2. Informative References . . . . . . . . . . . . . . . . . . 14 85 Appendix A. Examples of IPv4/IPv6 Address Translation . . . . . . 16 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 88 1. Introduction 90 The IANA unallocated IPv4 address pool was exhausted on February 3, 91 2011. Each RIR's unallocated IPv4 address pool will exhaust in the 92 near future. It will be difficult for many networks to assign IPv4 93 addresses to end users, despite substantial IP connectivity growth 94 required for fast growing edge networks. 96 This document describes an IPv4 over IPv6 solution as one of the 97 techniques for IPv4 service extension and encouragement of IPv6 98 deployment. 464XLAT is not a one for one replacement of full IPv4 99 functionality. The 464XLAT architecture only supports IPv4 in the 100 client server model, where the server has global IPv4 address. This 101 means it is not fit for IPv4 peer-to-peer communication or inbound 102 IPv4 connections. 464XLAT builds on IPv6 transport and includes full 103 any to any IPv6 communication. 105 The 464XLAT architecture described in this document uses IPv4/IPv6 106 translation standardized in [RFC6145] and [RFC6146]. It does not 107 require DNS64 [RFC6147] since an IPv4 host may simply send IPv4 108 packets, including packets to an IPv4 DNS server, which will be 109 translated on the CLAT to IPv6 and back to IPv4 on the PLAT. 464XLAT 110 networks may use DNS64 [RFC6147] to enable single stateful 111 translation [RFC6146] instead of 464XLAT double translation where 112 possible. The 464XLAT architecture encourages IPv6 transition by 113 making IPv4 services reachable across IPv6-only networks and 114 providing IPv6 and IPv4 connectivity to single-stack IPv4 or IPv6 115 servers and peers. 117 By combining 464XLAT with BIH [RFC6535], it is also possible to 118 provide single IPv4 to IPv6 translation service, which will be needed 119 in the future case of IPv6-only servers and peers to be reached from 120 legacy IPv4-only hosts across IPv6-only networks. 122 2. Requirements Language 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 126 document are to be interpreted as described in [RFC2119]. 128 3. Terminology 129 PLAT: PLAT is Provider side translator(XLAT) that complies with 130 [RFC6146]. It translates N:1 global IPv6 packets to global 131 IPv4 packets, and vice versa. 133 CLAT: CLAT is Customer side translator(XLAT) that complies with 134 [RFC6145]. It algorithmically translates 1:1 private IPv4 135 packets to global IPv6 packets, and vice versa. The CLAT 136 function is applicable to a router or an end-node such as a 137 mobile phone. CLAT SHOULD perform router function to 138 facilitate packets forwarding through the stateless 139 translation even if it is an end-node. In the case where the 140 access network does not allow for a dedicated IPv6 prefix for 141 translation, a NAT44 SHOULD be used between the router 142 function and the stateless translator function. The CLAT as 143 a common home router or 3G router is expected to perform 144 gateway functions such as DHCP server and DNS proxy for local 145 clients. The CLAT does not comply with the sentence "Both 146 IPv4-translatable IPv6 addresses and IPv4-converted IPv6 147 addresses SHOULD use the same prefix." that is described on 148 Section 3.3 in [RFC6052] due to using different IPv6 prefixes 149 for CLAT-side and PLAT-side IPv4 addresses. 151 4. Motivation and Uniqueness of 464XLAT 153 1. Minimal IPv4 resource requirements, maximum IPv4 efficiency 154 through statistical multiplexing 156 2. No new protocols required, quick deployment 158 3. IPv6-only networks are simpler and therefore less expensive to 159 operate 161 5. Network Architecture 163 464XLAT architecture is shown in the following figure. 165 5.1. Wireline Network Architecture 167 The private IPv4 host on this diagram can reach global IPv4 hosts via 168 translation on both CLAT and PLAT. On the other hand, the IPv6 host 169 can reach other IPv6 hosts on the Internet directly without 170 translation. This means that the CPE can not only have the function 171 of CLAT but also the function of IPv6 native router for IPv6 native 172 traffic. 174 ---- 175 | v6 | 176 ---- 177 | 178 ---- | .---+---. .------. 179 | v6 |-----+ / \ / \ 180 ---- | ------ / IPv6 \ ------ / IPv4 \ 181 +---| CLAT |---+ Internet +---| PLAT |---+ Internet | 182 ------- | ------ \ / ------ \ / 183 |v4p/v6 |--+ `---------' `----+----' 184 ------- | | 185 ----- | ----- 186 | v4p |----+ | v4g | 187 ----- | ----- 189 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 191 v6 : Global IPv6 192 v4p : Private IPv4 193 v4g : Global IPv4 195 Figure 1: Wireline Network Topology 197 5.2. Wireless 3GPP Network Architecture 199 The CLAT function on the UE provides an [RFC1918] address and IPv4 200 default route. The applications on the UE can use the private IPv4 201 address for reaching global IPv4 hosts via translation on both CLAT 202 and PLAT. On the other hand, reaching IPv6 hosts (including host 203 presented via DNS64 [RFC6147]) does not require the CLAT function on 204 the UE. 206 ---- 207 | v6 | 208 ---- 209 | 210 .---+---. 211 / \ 212 / IPv6 \ 213 | Internet | 214 \ / 215 UE / Mobile Phone `---------' 216 +----------------------+ | 217 | ---- | | .---+---. .------. 218 | | v6 |----+ | / \ / \ 219 | ---- | ------| / IPv6 PDP \ ------ / IPv4 \ 220 | +---| CLAT |---+ Mobile Core +---| PLAT |--+ Internet | 221 | | ------| \ GGSN / ------ \ / 222 | | | \ ' `----+---' 223 | ------ | | `-------' | 224 | | v4p |---+ | ----- 225 | ------ | | | v4g | 226 +----------------------+ ----- 228 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 230 v6 : Global IPv6 231 v4p : Private IPv4 232 v4g : Global IPv4 234 Figure 2: Wireless 3GPP Network Topology 236 6. Applicability 238 6.1. Wireline Network Applicability 240 When an ISP has IPv6 464XLAT, the ISP can provide outgoing IPv4 241 service to end users across an IPv6 access network. The result is 242 that edge network growth is no longer tightly coupled to the 243 availability of scarce IPv4 addresses. 245 If the IXP or another provider operates the PLAT, the edge ISP is 246 only required to deploy an IPv6 access network. All ISPs do not need 247 IPv4 access networks. They can migrate their access network to a 248 simple and highly scalable IPv6-only environment. 250 Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE 251 camp Spring 2012. The result is described in 253 [I-D.hazeyama-widecamp-ipv6-only-experience]. 255 6.2. Wireless 3GPP Network Applicability 257 The vast majority of mobile networks are compliant to Pre-Release 9 258 3GPP standards. In Pre-Release 9 3GPP networks, GSM and UMTS 259 networks must signal and support both IPv4 and IPv6 Packet Data 260 Protocol (PDP) attachments to access IPv4 and IPv6 network 261 destinations [RFC6459]. Since there are 2 PDPs required to support 2 262 address families, this is double the number of PDPs required to 263 support the status quo of 1 address family, which is IPv4. 265 464XLAT in combination with stateful translation [RFC6146] and DNS64 266 [RFC6147] allows 85% of the Android applications to continue to work 267 with single translation or native IPv6 access. For the remaining 15% 268 of applications that require IPv4 connectivity, the CLAT function on 269 the UE provides a private IPv4 address and IPv4 default-route on the 270 host for the applications to reference and bind to. Connections 271 sourced from the IPv4 interface are immediately routed to the CLAT 272 function and passed to the IPv6-only mobile network, destine to the 273 PLAT. In summary, the UE has the CLAT function that does a stateless 274 translation [RFC6145], but only when required. The mobile network 275 has a PLAT that does stateful translation [RFC6146]. 277 464XLAT works with today's existing systems as much as possible. 278 464XLAT is compatible with existing network based deep packet 279 inspection solutions like 3GPP standardized Policy and Charging 280 Control (PCC) [TS.23203]. 282 7. Implementation Considerations 284 7.1. IPv6 Address Format 286 IPv6 address format in 464XLAT is defined in Section 2.2 of 287 [RFC6052]. 289 7.2. IPv4/IPv6 Address Translation Chart 291 7.2.1. Case of enabling only stateless XLATE on CLAT 293 This case should be used when a prefix delegation mechanism such as 294 DHCPv6-PD [RFC3633] is available to assign a dedicated translation 295 prefix to the CLAT. 297 Source IPv4 address 298 +----------------------------+ 299 | Global IPv4 address | 300 | assigned to IPv4 pool@PLAT | 301 +--------+ +----------------------------+ 302 | IPv4 | Destination IPv4 address 303 | server | +----------------------------+ 304 +--------+ | Global IPv4 address | 305 ^ | assigned to IPv4 server | 306 | +----------------------------+ 307 +--------+ 308 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 309 +--------+ 310 ^ 311 | 312 Source IPv6 address (IPv6 cloud) 313 +--------------------------------------------------------------+ 314 | IPv4-Embedded IPv6 address | 315 | defined in Section 2.2 of RFC6052 | 316 +--------------------------------------------------------------+ 317 Destination IPv6 address 318 +--------------------------------------------------------------+ 319 | IPv4-Embedded IPv6 address | 320 | defined in Section 2.2 of RFC6052 | 321 +--------------------------------------------------------------+ 322 (IPv6 cloud) 323 ^ 324 | 325 +--------+ 326 | | In the case CLAT has a 327 | | dedicated IPv6 prefix for 328 | CLAT | translation, the CLAT can 329 | | perform with only Stateless 330 | | XLATE (IPv4:IPv6=1:1). 331 +--------+ 332 ^ Source IPv4 address 333 | +----------------------------+ 334 +--------+ | Private IPv4 address | 335 | IPv4 | | assigned to IPv4 client | 336 | client | +----------------------------+ 337 +--------+ Destination IPv4 address 338 +----------------------------+ 339 | Global IPv4 address | 340 | assigned to IPv4 server | 341 +----------------------------+ 343 Case of enabling only stateless XLATE on CLAT 345 7.2.2. Case of enabling NAT44 and stateless XLATE on CLAT 347 This case should be used when a prefix delegation mechanism is not 348 available to assign a dedicated translation prefix to the CLAT. In 349 this case, NAT44 SHOULD be used so that all IPv4 source addresses are 350 mapped to a single IPv6 address. 352 Source IPv4 address 353 +----------------------------+ 354 | Global IPv4 address | 355 | assigned to IPv4 pool@PLAT | 356 +--------+ +----------------------------+ 357 | IPv4 | Destination IPv4 address 358 | server | +----------------------------+ 359 +--------+ | Global IPv4 address | 360 ^ | assigned to IPv4 server | 361 | +----------------------------+ 362 +--------+ 363 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 364 +--------+ 365 ^ 366 | 367 Source IPv6 address (IPv6 cloud) 368 +--------------------------------------------------------------+ 369 | IPv4-Embedded IPv6 address | 370 | defined in Section 2.2 of RFC6052 | 371 +--------------------------------------------------------------+ 372 Destination IPv6 address 373 +--------------------------------------------------------------+ 374 | IPv4-Embedded IPv6 address | 375 | defined in Section 2.2 of RFC6052 | 376 +--------------------------------------------------------------+ 377 (IPv6 cloud) 378 ^ 379 | 380 +--------+ 381 | | In the case CLAT does not have 382 | | a dedicated IPv6 prefix for 383 | CLAT | translation, the CLAT can 384 | | perform with NAT44 and 385 | | Stateless XLATE 386 | | (IPv4:IPv6=1:1). 387 +--------+ 388 ^ Source IPv4 address 389 | +----------------------------+ 390 +--------+ | Private IPv4 address | 391 | IPv4 | | assigned to IPv4 client | 392 | client | +----------------------------+ 393 +--------+ Destination IPv4 address 394 +----------------------------+ 395 | Global IPv4 address | 396 | assigned to IPv4 server | 397 +----------------------------+ 399 Case of enabling NAT44 and stateless XLATE on CLAT 401 7.3. IPv6 Prefix Handling 403 7.3.1. Case of enabling only stateless XLATE on CLAT 405 From the delegated DHCPv6 [RFC3633] prefix, a /64 is dedicated to 406 source and receive IPv6 packets associated with the stateless 407 translation [RFC6145]. 409 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 410 as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or 411 [I-D.ietf-behave-nat64-discovery-heuristic]. 413 7.3.2. Case of enabling NAT44 and stateless XLATE on CLAT 415 In the case that DHCPv6-PD [RFC3633] is not available, the CLAT does 416 not have dedicated IPv6 prefix for translation. If the CLAT does not 417 have a dedicated IPv6 prefix for translation, the CLAT can perform 418 with NAT44 and stateless translation [RFC6145]. 420 Incoming source IPv4 packets from the LAN of [RFC1918] addresses are 421 NAT44 to the CLAT IPv4 host address. Then, the CLAT will do a 422 stateless translation [RFC6145] so that the IPv4 packets from the 423 CLAT IPv4 host address are translated to the CLAT WAN IPv6 address as 424 described in [RFC6052]. 426 Its subnet prefix is made of the delegated prefix, completed if 427 needed to a /64 by a subnet ID = 0. Its interface ID is the 464XLAT 428 interface ID (Section 10). 430 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 431 as TR-069, DNS APL RR [RFC3123] or 432 [I-D.ietf-behave-nat64-discovery-heuristic]. 434 7.4. Traffic Treatment Scenarios 436 +--------+-------------+-----------------------+-------------+ 437 | Server | Application | Traffic Treatment | Location of | 438 | | and Host | | Translation | 439 +--------+-------------+-----------------------+-------------+ 440 | IPv6 | IPv6 | End-to-end IPv6 | None | 441 +--------+-------------+-----------------------+-------------+ 442 | IPv4 | IPv6 | Stateful Translation | PLAT | 443 +--------+-------------+-----------------------+-------------+ 444 | IPv4 | IPv4 | 464XLAT | PLAT/CLAT | 445 +--------+-------------+-----------------------+-------------+ 446 | IPv6 | IPv4 | Stateless Translation | CLAT | 447 +--------+-------------+-----------------------+-------------+ 449 Traffic Treatment Scenarios 451 The above chart shows most common traffic types and traffic 452 treatment. 454 7.5. DNS Proxy Implementation 456 The CLAT SHOULD implement a DNS proxy as defined in [RFC5625]. The 457 case of an IPv4-only node behind CLAT querying an IPv4 DNS server is 458 undesirable since it requires both stateful and stateless translation 459 for each DNS lookup. The CLAT SHOULD set itself as the DNS server 460 via DHCP or other means and proxy DNS queries for IPv4 and IPv6 461 clients. Using the CLAT enabled home router or UE as a DNS proxy is 462 a normal consume gateway function and simplifies the traffic flow so 463 that only IPv6 native queries are made across the access network. 464 The CLAT SHOULD allow for a client to query any DNS server of its 465 choice and bypass the proxy. 467 7.6. CLAT in a Gateway 469 The CLAT is a stateless translation feature which can be implemented 470 in a common home router or mobile phone that has a mobile router 471 feature. The router with CLAT function SHOULD provide common router 472 services such as DHCP of [RFC1918] addresses, DHCPv6, and DNS 473 service. The router SHOULD set itself as the DNS server advertised 474 via DHCP or other means to the clients so that it may implement the 475 DNS proxy function to avoid double translation of DNS request. 477 7.7. CLAT to CLAT communications 479 While CLAT to CLAT IPv4 communication may work when the client IPv4 480 subnets do not overlap, this traffic flow is out of scope. 464XLAT is 481 a hub and spoke architecture focused on enabling IPv4-only services 482 over IPv6-only access networks. 484 8. Deployment Considerations 486 Even if the Internet access provider for consumers is different from 487 the PLAT provider (e.g. another internet access provider), it can 488 implement traffic engineering independently from the PLAT provider. 489 Detailed reasons are below: 491 1. The Internet access provider for consumers can figure out IPv4 492 destination address from translated IPv6 packet header, so it can 493 implement traffic engineering based on IPv4 destination address 494 (e.g. traffic monitoring for each IPv4 destination address, 495 packet filtering for each IPv4 destination address, etc.). The 496 tunneling methods do not have such a advantage, without any deep 497 packet inspection for processing the inner IPv4 packet of the 498 tunnel packet. 500 2. If the Internet access provider for consumers can assign IPv6 501 prefix greater than /64 for each subscriber, this 464XLAT 502 architecture can separate IPv6 prefix for native IPv6 packets and 503 XLAT prefix for IPv4/IPv6 translation packets. Accordingly, it 504 can identify the type of packets ("native IPv6 packets" and 505 "IPv4/IPv6 translation packets"), and implement traffic 506 engineering based on IPv6 prefix. 508 This 464XLAT architecture has two capabilities. One is a IPv4 -> 509 IPv6 -> IPv4 translation for sharing global IPv4 addresses, another, 510 if combined with BIH [RFC6535], is a IPv4 -> IPv6 translation for 511 reaching IPv6-only servers from IPv4-only clients that can not 512 support IPv6. IPv4-only clients must be support through the long 513 period of global transition to IPv6. 515 9. Security Considerations 517 To implement a PLAT, see security considerations presented in Section 518 5 of [RFC6146]. 520 To implement a CLAT, see security considerations presented in Section 521 7 of [RFC6145]. The CLAT MAY comply with [RFC6092]. 523 10. IANA Considerations 525 IANA is requested to reserve a Modified EUI-64 identifier for 464XLAT 526 according to section 2.2.2 of [RFC5342]. Its suggested value is 02- 527 00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00- 528 00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be 529 taken in reserved or available values. 531 11. Acknowledgements 533 The authors would like to thank JPIX NOC members, JPIX 464XLAT trial 534 service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv 535 Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo 536 Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, and 537 Jouni Korhonen for their helpful comments. Special acknowledgments 538 go to Remi Despres for his plentiful supports and suggestions, 539 especially about using NAT44 with IANA's EUI-64 ID. We also would 540 like to thank Fred Baker and Joel Jaeggli for their support. 542 12. References 544 12.1. Normative References 546 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 547 Requirement Levels", BCP 14, RFC 2119, March 1997. 549 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 550 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 551 October 2010. 553 [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for 554 IPv4/IPv6 Translation", RFC 6144, April 2011. 556 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 557 Algorithm", RFC 6145, April 2011. 559 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 560 NAT64: Network Address and Protocol Translation from IPv6 561 Clients to IPv4 Servers", RFC 6146, April 2011. 563 12.2. Informative References 565 [I-D.hazeyama-widecamp-ipv6-only-experience] 566 Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura, 567 "Experiences from IPv6-Only Networks with Transition 568 Technologies in the WIDE Camp Spring 2012", 569 draft-hazeyama-widecamp-ipv6-only-experience-01 (work in 570 progress), March 2012. 572 [I-D.ietf-behave-nat64-discovery-heuristic] 573 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 574 IPv6 Prefix Used for IPv6 Address Synthesis", 575 draft-ietf-behave-nat64-discovery-heuristic-10 (work in 576 progress), June 2012. 578 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 579 E. Lear, "Address Allocation for Private Internets", 580 BCP 5, RFC 1918, February 1996. 582 [RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes 583 (APL RR)", RFC 3123, June 2001. 585 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 586 Host Configuration Protocol (DHCP) version 6", RFC 3633, 587 December 2003. 589 [RFC5342] Eastlake, D., "IANA Considerations and IETF Protocol Usage 590 for IEEE 802 Parameters", BCP 141, RFC 5342, 591 September 2008. 593 [RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", 594 BCP 152, RFC 5625, August 2009. 596 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 597 Customer Premises Equipment (CPE) for Providing 598 Residential IPv6 Internet Service", RFC 6092, 599 January 2011. 601 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 602 Beijnum, "DNS64: DNS Extensions for Network Address 603 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 604 April 2011. 606 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 607 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 608 Partnership Project (3GPP) Evolved Packet System (EPS)", 609 RFC 6459, January 2012. 611 [RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts 612 Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012. 614 [TS.23203] 3GPP, "Policy and charging control architecture", 3GPP 615 TS 23.203 10.7.0, June 2012. 617 Appendix A. Examples of IPv4/IPv6 Address Translation 619 The following are examples of IPv4/IPv6 Address Translation on the 620 464XLAT architecture. 622 Example 1. (Case of enabling only stateless XLATE on CLAT) 624 In the case that IPv6 prefix greater than /64 is assigned to end 625 users by such as DHCPv6-PD [RFC3633], only the function of Stateless 626 XLATE should be enabled on CLAT. Because the CLAT can use dedicated 627 a /64 from the assigned IPv6 prefix for Stateless XLATE. 629 Host & configuration value 630 +------------------------------+ 631 | IPv4 server | 632 | [198.51.100.1] | IP packet header 633 +------------------------------+ +--------------------------------+ 634 ^ | Source IP address | 635 | | [192.0.2.1] | 636 | | Destination IP address | 637 | | [198.51.100.1] | 638 +------------------------------+ +--------------------------------+ 639 | PLAT | ^ 640 | IPv4 pool address | | 641 | [192.0.2.1 - 192.0.2.100] | | 642 | PLAT-side XLATE IPv6 prefix | | 643 | [2001:db8:1234::/96] | | 644 +------------------------------+ +--------------------------------+ 645 ^ | Source IP address | 646 | | [2001:db8:aaaa::192.168.1.2] | 647 | | Destination IP address | 648 | | [2001:db8:1234::198.51.100.1] | 649 +------------------------------+ +--------------------------------+ 650 | CLAT | ^ 651 | PLAT-side XLATE IPv6 prefix | | 652 | [2001:db8:1234::/96] | | 653 | CLAT-side XLATE IPv6 prefix | | 654 | [2001:db8:aaaa::/96] | | 655 +------------------------------+ +--------------------------------+ 656 ^ | Source IP address | 657 | | [192.168.1.2] | 658 | | Destination IP address | 659 | | [198.51.100.1] | 660 +------------------------------+ +--------------------------------+ 661 | IPv4 client | 662 | [192.168.1.2/24] | 663 +------------------------------+ 664 Delegated IPv6 prefix for client: 2001:db8:aaaa::/56 666 Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT) 668 In the case that IPv6 prefix /64 is assigned to end users, the 669 function of NAT44 and Stateless XLATE should be enabled on CLAT. 670 Because the CLAT does not have dedicated IPv6 prefix for translation. 672 Host & configuration value 673 +-------------------------------+ 674 | IPv4 server | 675 | [198.51.100.1] | IP packet header 676 +-------------------------------+ +-------------------------------+ 677 ^ | Source IP address | 678 | | [192.0.2.1] | 679 | | Destination IP address | 680 | | [198.51.100.1] | 681 +-------------------------------+ +-------------------------------+ 682 | PLAT | ^ 683 | IPv4 pool address | | 684 | [192.0.2.1 - 192.0.2.100] | | 685 | PLAT-side XLATE IPv6 prefix | | 686 | [2001:db8:1234::/96] | | 687 +-------------------------------+ +-------------------------------+ 688 ^ | Source IP address | 689 | | [2001:db8:aaaa:200:5e10:0:0] | 690 | | Destination IP address | 691 | | [2001:db8:1234::198.51.100.1] | 692 +-------------------------------+ +-------------------------------+ 693 | CLAT Stateless XLATE function | ^ 694 | - - - - - - - - - - - - - - - | | 695 | PLAT-side XLATE IPv6 prefix | | 696 | [2001:db8:1234::/96] | | 697 | CLAT-side XLATE IPv6 prefix | | 698 | [2001:db8:aaaa::/64] | | 699 | CLAT-side XLATE IPv6 EUI-64 ID| | 700 | [02-00-5E-10-00-00-00-00] | | 701 + - - - - - - - - - - - - - - - + +-------------------------------+ 702 | ^ | | Source IP address | 703 | | | | [10.255.255.1] | 704 | | | | Destination IP address | 705 | | | | [198.51.100.1] | 706 + - - - - - - - - - - - - - - - + +-------------------------------+ 707 | CLAT NAT44 function | ^ 708 | - - - - - - - - - - - - - - - | | 709 | NAT44 NATed address | | 710 | [10.255.255.1/32] | | 711 +-------------------------------+ +-------------------------------+ 712 ^ | Source IP address | 713 | | [192.168.1.2] | 714 | | Destination IP address | 715 | | [198.51.100.1] | 716 +-------------------------------+ +-------------------------------+ 717 | IPv4 client | 718 | [192.168.1.2/24] | 719 +-------------------------------+ 720 Delegated IPv6 prefix for client: 2001:db8:aaaa::/64 722 Authors' Addresses 724 Masataka Mawatari 725 Japan Internet Exchange Co.,Ltd. 726 KDDI Otemachi Building 19F, 1-8-1 Otemachi, 727 Chiyoda-ku, Tokyo 100-0004 728 JAPAN 730 Phone: +81 3 3243 9579 731 Email: mawatari@jpix.ad.jp 733 Masanobu Kawashima 734 NEC AccessTechnica, Ltd. 735 800, Shimomata 736 Kakegawa-shi, Shizuoka 436-8501 737 JAPAN 739 Phone: +81 537 23 9655 740 Email: kawashimam@vx.jp.nec.com 742 Cameron Byrne 743 T-Mobile USA 744 Bellevue, Washington 98006 745 USA 747 Email: cameron.byrne@t-mobile.com