idnits 2.17.1 draft-ietf-v6ops-464xlat-06.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 (August 7, 2012) is 4277 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 711, but not defined == Unused Reference: 'RFC6144' is defined on line 564, 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-11 -- 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. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force M. Mawatari 2 Internet-Draft Japan Internet Exchange Co.,Ltd. 3 Intended status: BCP M. Kawashima 4 Expires: February 8, 2013 NEC AccessTechnica, Ltd. 5 C. Byrne 6 T-Mobile USA 7 August 7, 2012 9 464XLAT: Combination of Stateful and Stateless Translation 10 draft-ietf-v6ops-464xlat-06 12 Abstract 14 This document describes an architecture (464XLAT) for providing 15 limited IPv4 connectivity across an IPv6-only network by combining 16 existing and well-known stateful protocol translation RFC 6146 in the 17 core and stateless protocol translation RFC 6145 at the edge. 464XLAT 18 is a simple and scalable technique to quickly deploy limited IPv4 19 access service to IPv6-only edge networks without encapsulation. 21 Status of this Memo 23 This Internet-Draft is submitted 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 February 8, 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. BCP Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 58 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 5. Motivation and Uniqueness of 464XLAT . . . . . . . . . . . . . 4 60 6. Network Architecture . . . . . . . . . . . . . . . . . . . . . 4 61 6.1. Wireline Network Architecture . . . . . . . . . . . . . . 5 62 6.2. Wireless 3GPP Network Architecture . . . . . . . . . . . . 5 63 7. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 6 64 7.1. Wireline Network Applicability . . . . . . . . . . . . . . 6 65 7.2. Wireless 3GPP Network Applicability . . . . . . . . . . . 7 66 8. Implementation Considerations . . . . . . . . . . . . . . . . 7 67 8.1. IPv6 Address Format . . . . . . . . . . . . . . . . . . . 7 68 8.2. IPv4/IPv6 Address Translation Chart . . . . . . . . . . . 7 69 8.2.1. Case of enabling only stateless XLATE on CLAT . . . . 7 70 8.2.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 9 71 8.3. IPv6 Prefix Handling . . . . . . . . . . . . . . . . . . . 11 72 8.3.1. Case of enabling only stateless XLATE on CLAT . . . . 11 73 8.3.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 11 74 8.4. Traffic Treatment Scenarios . . . . . . . . . . . . . . . 12 75 8.5. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 12 76 8.6. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 12 77 8.7. CLAT to CLAT communications . . . . . . . . . . . . . . . 12 78 9. Deployment Considerations . . . . . . . . . . . . . . . . . . 13 79 10. Security Considerations . . . . . . . . . . . . . . . . . . . 13 80 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 81 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 82 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 83 13.1. Normative References . . . . . . . . . . . . . . . . . . . 14 84 13.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. BCP Scenario 124 This BCP only applies when the following two criteria are present: 126 1. There is an IPv6-only access network that uses stateful 127 translation [RFC6146] 129 2. There are IPv4-only applications or hosts that must communicate 130 across the IPv6-only access network to reach the IPv4 Internet 132 3. Requirements Language 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in [RFC2119]. 138 4. Terminology 140 PLAT: PLAT is Provider side translator(XLAT) that complies with 141 [RFC6146]. It translates N:1 global IPv6 packets to global 142 IPv4 packets, and vice versa. 144 CLAT: CLAT is Customer side translator(XLAT) that complies with 145 [RFC6145]. It algorithmically translates 1:1 private IPv4 146 packets to global IPv6 packets, and vice versa. The CLAT 147 function is applicable to a router or an end-node such as a 148 mobile phone. CLAT SHOULD perform router function to 149 facilitate packets forwarding through the stateless 150 translation even if it is an end-node. In the case where the 151 access network does not allow for a dedicated IPv6 prefix for 152 translation, a NAT44 SHOULD be used between the router 153 function and the stateless translator function. The CLAT as 154 a common home router or 3G router is expected to perform 155 gateway functions such as DHCP server and DNS proxy for local 156 clients. The CLAT does not comply with the sentence "Both 157 IPv4-translatable IPv6 addresses and IPv4-converted IPv6 158 addresses SHOULD use the same prefix." that is described on 159 Section 3.3 in [RFC6052] due to using different IPv6 prefixes 160 for CLAT-side and PLAT-side IPv4 addresses. 162 5. Motivation and Uniqueness of 464XLAT 164 1. Minimal IPv4 resource requirements, maximum IPv4 efficiency 165 through statistical multiplexing 167 2. No new protocols required, quick deployment 169 3. IPv6-only networks are simpler and therefore less expensive to 170 operate 172 6. Network Architecture 174 464XLAT architecture is shown in the following figure. 176 6.1. Wireline Network Architecture 178 The private IPv4 host on this diagram can reach global IPv4 hosts via 179 translation on both CLAT and PLAT. On the other hand, the IPv6 host 180 can reach other IPv6 hosts on the Internet directly without 181 translation. This means that the CPE can not only have the function 182 of CLAT but also the function of IPv6 native router for IPv6 native 183 traffic. 185 ---- 186 | v6 | 187 ---- 188 | 189 ---- | .---+---. .------. 190 | v6 |-----+ / \ / \ 191 ---- | ------ / IPv6 \ ------ / IPv4 \ 192 +---| CLAT |---+ Internet +---| PLAT |---+ Internet | 193 ------- | ------ \ / ------ \ / 194 |v4p/v6 |--+ `---------' `----+----' 195 ------- | | 196 ----- | ----- 197 | v4p |----+ | v4g | 198 ----- | ----- 200 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 202 v6 : Global IPv6 203 v4p : Private IPv4 204 v4g : Global IPv4 206 Figure 1: Wireline Network Topology 208 6.2. Wireless 3GPP Network Architecture 210 The CLAT function on the UE provides an [RFC1918] address and IPv4 211 default route. The applications on the UE can use the private IPv4 212 address for reaching global IPv4 hosts via translation on both CLAT 213 and PLAT. On the other hand, reaching IPv6 hosts (including host 214 presented via DNS64 [RFC6147]) does not require the CLAT function on 215 the UE. 217 ---- 218 | v6 | 219 ---- 220 | 221 .---+---. 222 / \ 223 / IPv6 \ 224 | Internet | 225 \ / 226 UE / Mobile Phone `---------' 227 +----------------------+ | 228 | ---- | | .---+---. .------. 229 | | v6 |----+ | / \ / \ 230 | ---- | ------| / IPv6 PDP \ ------ / IPv4 \ 231 | +---| CLAT |---+ Mobile Core +---| PLAT |--+ Internet | 232 | | ------| \ GGSN / ------ \ / 233 | | | \ ' `----+---' 234 | ------ | | `-------' | 235 | | v4p |---+ | ----- 236 | ------ | | | v4g | 237 +----------------------+ ----- 239 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 241 v6 : Global IPv6 242 v4p : Private IPv4 243 v4g : Global IPv4 245 Figure 2: Wireless 3GPP Network Topology 247 7. Applicability 249 7.1. Wireline Network Applicability 251 When an ISP has IPv6 464XLAT, the ISP can provide outgoing IPv4 252 service to end users across an IPv6 access network. The result is 253 that edge network growth is no longer tightly coupled to the 254 availability of scarce IPv4 addresses. 256 If the IXP or another provider operates the PLAT, the edge ISP is 257 only required to deploy an IPv6 access network. All ISPs do not need 258 IPv4 access networks. They can migrate their access network to a 259 simple and highly scalable IPv6-only environment. 261 Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE 262 camp Spring 2012. The result is described in 264 [I-D.hazeyama-widecamp-ipv6-only-experience]. 266 7.2. Wireless 3GPP Network Applicability 268 The vast majority of mobile networks are compliant to Pre-Release 9 269 3GPP standards. In Pre-Release 9 3GPP networks, GSM and UMTS 270 networks must signal and support both IPv4 and IPv6 Packet Data 271 Protocol (PDP) attachments to access IPv4 and IPv6 network 272 destinations [RFC6459]. Since there are 2 PDPs required to support 2 273 address families, this is double the number of PDPs required to 274 support the status quo of 1 address family, which is IPv4. 276 464XLAT in combination with stateful translation [RFC6146] and DNS64 277 [RFC6147] allows 85% of the Android applications to continue to work 278 with single translation or native IPv6 access. For the remaining 15% 279 of applications that require IPv4 connectivity, the CLAT function on 280 the UE provides a private IPv4 address and IPv4 default-route on the 281 host for the applications to reference and bind to. Connections 282 sourced from the IPv4 interface are immediately routed to the CLAT 283 function and passed to the IPv6-only mobile network, destine to the 284 PLAT. In summary, the UE has the CLAT function that does a stateless 285 translation [RFC6145], but only when required. The mobile network 286 has a PLAT that does stateful translation [RFC6146]. 288 464XLAT works with today's existing systems as much as possible. 289 464XLAT is compatible with existing network based deep packet 290 inspection solutions like 3GPP standardized Policy and Charging 291 Control (PCC) [TS.23203]. 293 8. Implementation Considerations 295 8.1. IPv6 Address Format 297 IPv6 address format in 464XLAT is defined in Section 2.2 of 298 [RFC6052]. 300 8.2. IPv4/IPv6 Address Translation Chart 302 8.2.1. Case of enabling only stateless XLATE on CLAT 304 This case should be used when a prefix delegation mechanism such as 305 DHCPv6-PD [RFC3633] is available to assign a dedicated translation 306 prefix to the CLAT. 308 Source IPv4 address 309 +----------------------------+ 310 | Global IPv4 address | 311 | assigned to IPv4 pool@PLAT | 312 +--------+ +----------------------------+ 313 | IPv4 | Destination IPv4 address 314 | server | +----------------------------+ 315 +--------+ | Global IPv4 address | 316 ^ | assigned to IPv4 server | 317 | +----------------------------+ 318 +--------+ 319 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 320 +--------+ 321 ^ 322 | 323 Source IPv6 address (IPv6 cloud) 324 +--------------------------------------------------------------+ 325 | IPv4-Embedded IPv6 address | 326 | defined in Section 2.2 of RFC6052 | 327 +--------------------------------------------------------------+ 328 Destination IPv6 address 329 +--------------------------------------------------------------+ 330 | IPv4-Embedded IPv6 address | 331 | defined in Section 2.2 of RFC6052 | 332 +--------------------------------------------------------------+ 333 (IPv6 cloud) 334 ^ 335 | 336 +--------+ 337 | | In the case CLAT has a 338 | | dedicated IPv6 prefix for 339 | CLAT | translation, the CLAT can 340 | | perform with only Stateless 341 | | XLATE (IPv4:IPv6=1:1). 342 +--------+ 343 ^ Source IPv4 address 344 | +----------------------------+ 345 +--------+ | Private IPv4 address | 346 | IPv4 | | assigned to IPv4 client | 347 | client | +----------------------------+ 348 +--------+ Destination IPv4 address 349 +----------------------------+ 350 | Global IPv4 address | 351 | assigned to IPv4 server | 352 +----------------------------+ 354 Case of enabling only stateless XLATE on CLAT 356 8.2.2. Case of enabling NAT44 and stateless XLATE on CLAT 358 This case should be used when a prefix delegation mechanism is not 359 available to assign a dedicated translation prefix to the CLAT. In 360 this case, NAT44 SHOULD be used so that all IPv4 source addresses are 361 mapped to a single IPv6 address. 363 Source IPv4 address 364 +----------------------------+ 365 | Global IPv4 address | 366 | assigned to IPv4 pool@PLAT | 367 +--------+ +----------------------------+ 368 | IPv4 | Destination IPv4 address 369 | server | +----------------------------+ 370 +--------+ | Global IPv4 address | 371 ^ | assigned to IPv4 server | 372 | +----------------------------+ 373 +--------+ 374 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 375 +--------+ 376 ^ 377 | 378 Source IPv6 address (IPv6 cloud) 379 +--------------------------------------------------------------+ 380 | IPv4-Embedded IPv6 address | 381 | defined in Section 2.2 of RFC6052 | 382 +--------------------------------------------------------------+ 383 Destination IPv6 address 384 +--------------------------------------------------------------+ 385 | IPv4-Embedded IPv6 address | 386 | defined in Section 2.2 of RFC6052 | 387 +--------------------------------------------------------------+ 388 (IPv6 cloud) 389 ^ 390 | 391 +--------+ 392 | | In the case CLAT does not have 393 | | a dedicated IPv6 prefix for 394 | CLAT | translation, the CLAT can 395 | | perform with NAT44 and 396 | | Stateless XLATE 397 | | (IPv4:IPv6=1:1). 398 +--------+ 399 ^ Source IPv4 address 400 | +----------------------------+ 401 +--------+ | Private IPv4 address | 402 | IPv4 | | assigned to IPv4 client | 403 | client | +----------------------------+ 404 +--------+ Destination IPv4 address 405 +----------------------------+ 406 | Global IPv4 address | 407 | assigned to IPv4 server | 408 +----------------------------+ 410 Case of enabling NAT44 and stateless XLATE on CLAT 412 8.3. IPv6 Prefix Handling 414 8.3.1. Case of enabling only stateless XLATE on CLAT 416 From the delegated DHCPv6 [RFC3633] prefix, a /64 is dedicated to 417 source and receive IPv6 packets associated with the stateless 418 translation [RFC6145]. 420 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 421 as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or 422 [I-D.ietf-behave-nat64-discovery-heuristic]. 424 8.3.2. Case of enabling NAT44 and stateless XLATE on CLAT 426 In the case that DHCPv6-PD [RFC3633] is not available, the CLAT does 427 not have dedicated IPv6 prefix for translation. If the CLAT does not 428 have a dedicated IPv6 prefix for translation, the CLAT can perform 429 with NAT44 and stateless translation [RFC6145]. 431 Incoming source IPv4 packets from the LAN of [RFC1918] addresses are 432 NAT44 to the CLAT IPv4 host address. Then, the CLAT will do a 433 stateless translation [RFC6145] so that the IPv4 packets from the 434 CLAT IPv4 host address are translated to the CLAT WAN IPv6 address as 435 described in [RFC6052]. 437 Its subnet prefix is made of the delegated prefix, completed if 438 needed to a /64 by a subnet ID = 0. Its interface ID is the 464XLAT 439 interface ID (Section 10). 441 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 442 as TR-069, DNS APL RR [RFC3123] or 443 [I-D.ietf-behave-nat64-discovery-heuristic]. 445 8.4. Traffic Treatment Scenarios 447 +--------+-------------+-----------------------+-------------+ 448 | Server | Application | Traffic Treatment | Location of | 449 | | and Host | | Translation | 450 +--------+-------------+-----------------------+-------------+ 451 | IPv6 | IPv6 | End-to-end IPv6 | None | 452 +--------+-------------+-----------------------+-------------+ 453 | IPv4 | IPv6 | Stateful Translation | PLAT | 454 +--------+-------------+-----------------------+-------------+ 455 | IPv4 | IPv4 | 464XLAT | PLAT/CLAT | 456 +--------+-------------+-----------------------+-------------+ 457 | IPv6 | IPv4 | Stateless Translation | CLAT | 458 +--------+-------------+-----------------------+-------------+ 460 Traffic Treatment Scenarios 462 The above chart shows most common traffic types and traffic 463 treatment. 465 8.5. DNS Proxy Implementation 467 The CLAT SHOULD implement a DNS proxy as defined in [RFC5625]. The 468 case of an IPv4-only node behind CLAT querying an IPv4 DNS server is 469 undesirable since it requires both stateful and stateless translation 470 for each DNS lookup. The CLAT SHOULD set itself as the DNS server 471 via DHCP or other means and proxy DNS queries for IPv4 and IPv6 472 clients. Using the CLAT enabled home router or UE as a DNS proxy is 473 a normal consume gateway function and simplifies the traffic flow so 474 that only IPv6 native queries are made across the access network. 475 The CLAT SHOULD allow for a client to query any DNS server of its 476 choice and bypass the proxy. 478 8.6. CLAT in a Gateway 480 The CLAT is a stateless translation feature which can be implemented 481 in a common home router or mobile phone that has a mobile router 482 feature. The router with CLAT function SHOULD provide common router 483 services such as DHCP of [RFC1918] addresses, DHCPv6, and DNS 484 service. The router SHOULD set itself as the DNS server advertised 485 via DHCP or other means to the clients so that it may implement the 486 DNS proxy function to avoid double translation of DNS request. 488 8.7. CLAT to CLAT communications 490 While CLAT to CLAT IPv4 communication may work when the client IPv4 491 subnets do not overlap, this traffic flow is out of scope. 464XLAT is 492 a hub and spoke architecture focused on enabling IPv4-only services 493 over IPv6-only access networks. 495 9. Deployment Considerations 497 Even if the Internet access provider for consumers is different from 498 the PLAT provider (e.g. another internet access provider), it can 499 implement traffic engineering independently from the PLAT provider. 500 Detailed reasons are below: 502 1. The Internet access provider for consumers can figure out IPv4 503 destination address from translated IPv6 packet header, so it can 504 implement traffic engineering based on IPv4 destination address 505 (e.g. traffic monitoring for each IPv4 destination address, 506 packet filtering for each IPv4 destination address, etc.). The 507 tunneling methods do not have such a advantage, without any deep 508 packet inspection for processing the inner IPv4 packet of the 509 tunnel packet. 511 2. If the Internet access provider for consumers can assign IPv6 512 prefix greater than /64 for each subscriber, this 464XLAT 513 architecture can separate IPv6 prefix for native IPv6 packets and 514 XLAT prefix for IPv4/IPv6 translation packets. Accordingly, it 515 can identify the type of packets ("native IPv6 packets" and 516 "IPv4/IPv6 translation packets"), and implement traffic 517 engineering based on IPv6 prefix. 519 This 464XLAT architecture has two capabilities. One is a IPv4 -> 520 IPv6 -> IPv4 translation for sharing global IPv4 addresses, another, 521 if combined with BIH [RFC6535], is a IPv4 -> IPv6 translation for 522 reaching IPv6-only servers from IPv4-only clients that can not 523 support IPv6. IPv4-only clients must be support through the long 524 period of global transition to IPv6. 526 10. Security Considerations 528 To implement a PLAT, see security considerations presented in Section 529 5 of [RFC6146]. 531 To implement a CLAT, see security considerations presented in Section 532 7 of [RFC6145]. The CLAT MAY comply with [RFC6092]. 534 11. IANA Considerations 536 IANA is requested to reserve a Modified EUI-64 identifier for 464XLAT 537 according to section 2.2.2 of [RFC5342]. Its suggested value is 02- 538 00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00- 539 00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be 540 taken in reserved or available values. 542 12. Acknowledgements 544 The authors would like to thank JPIX NOC members, JPIX 464XLAT trial 545 service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv 546 Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo 547 Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, and 548 Jouni Korhonen for their helpful comments. Special acknowledgments 549 go to Remi Despres for his plentiful supports and suggestions, 550 especially about using NAT44 with IANA's EUI-64 ID. We also would 551 like to thank Fred Baker and Joel Jaeggli for their support. 553 13. References 555 13.1. Normative References 557 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 558 Requirement Levels", BCP 14, RFC 2119, March 1997. 560 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 561 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 562 October 2010. 564 [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for 565 IPv4/IPv6 Translation", RFC 6144, April 2011. 567 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 568 Algorithm", RFC 6145, April 2011. 570 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 571 NAT64: Network Address and Protocol Translation from IPv6 572 Clients to IPv4 Servers", RFC 6146, April 2011. 574 13.2. Informative References 576 [I-D.hazeyama-widecamp-ipv6-only-experience] 577 Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura, 578 "Experiences from IPv6-Only Networks with Transition 579 Technologies in the WIDE Camp Spring 2012", 580 draft-hazeyama-widecamp-ipv6-only-experience-01 (work in 581 progress), March 2012. 583 [I-D.ietf-behave-nat64-discovery-heuristic] 584 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 585 IPv6 Prefix Used for IPv6 Address Synthesis", 586 draft-ietf-behave-nat64-discovery-heuristic-11 (work in 587 progress), July 2012. 589 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 590 E. Lear, "Address Allocation for Private Internets", 591 BCP 5, RFC 1918, February 1996. 593 [RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes 594 (APL RR)", RFC 3123, June 2001. 596 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 597 Host Configuration Protocol (DHCP) version 6", RFC 3633, 598 December 2003. 600 [RFC5342] Eastlake, D., "IANA Considerations and IETF Protocol Usage 601 for IEEE 802 Parameters", BCP 141, RFC 5342, 602 September 2008. 604 [RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", 605 BCP 152, RFC 5625, August 2009. 607 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 608 Customer Premises Equipment (CPE) for Providing 609 Residential IPv6 Internet Service", RFC 6092, 610 January 2011. 612 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 613 Beijnum, "DNS64: DNS Extensions for Network Address 614 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 615 April 2011. 617 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 618 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 619 Partnership Project (3GPP) Evolved Packet System (EPS)", 620 RFC 6459, January 2012. 622 [RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts 623 Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012. 625 [TS.23203] 3GPP, "Policy and charging control architecture", 3GPP 626 TS 23.203 10.7.0, June 2012. 628 Appendix A. Examples of IPv4/IPv6 Address Translation 630 The following are examples of IPv4/IPv6 Address Translation on the 631 464XLAT architecture. 633 Example 1. (Case of enabling only stateless XLATE on CLAT) 635 In the case that IPv6 prefix greater than /64 is assigned to end 636 users by such as DHCPv6-PD [RFC3633], only the function of Stateless 637 XLATE should be enabled on CLAT. Because the CLAT can use dedicated 638 a /64 from the assigned IPv6 prefix for Stateless XLATE. 640 Host & configuration value 641 +------------------------------+ 642 | IPv4 server | 643 | [198.51.100.1] | IP packet header 644 +------------------------------+ +--------------------------------+ 645 ^ | Source IP address | 646 | | [192.0.2.1] | 647 | | Destination IP address | 648 | | [198.51.100.1] | 649 +------------------------------+ +--------------------------------+ 650 | PLAT | ^ 651 | IPv4 pool address | | 652 | [192.0.2.1 - 192.0.2.100] | | 653 | PLAT-side XLATE IPv6 prefix | | 654 | [2001:db8:1234::/96] | | 655 +------------------------------+ +--------------------------------+ 656 ^ | Source IP address | 657 | | [2001:db8:aaaa::192.168.1.2] | 658 | | Destination IP address | 659 | | [2001:db8:1234::198.51.100.1] | 660 +------------------------------+ +--------------------------------+ 661 | CLAT | ^ 662 | PLAT-side XLATE IPv6 prefix | | 663 | [2001:db8:1234::/96] | | 664 | CLAT-side XLATE IPv6 prefix | | 665 | [2001:db8:aaaa::/96] | | 666 +------------------------------+ +--------------------------------+ 667 ^ | Source IP address | 668 | | [192.168.1.2] | 669 | | Destination IP address | 670 | | [198.51.100.1] | 671 +------------------------------+ +--------------------------------+ 672 | IPv4 client | 673 | [192.168.1.2/24] | 674 +------------------------------+ 675 Delegated IPv6 prefix for client: 2001:db8:aaaa::/56 677 Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT) 679 In the case that IPv6 prefix /64 is assigned to end users, the 680 function of NAT44 and Stateless XLATE should be enabled on CLAT. 681 Because the CLAT does not have dedicated IPv6 prefix for translation. 683 Host & configuration value 684 +-------------------------------+ 685 | IPv4 server | 686 | [198.51.100.1] | IP packet header 687 +-------------------------------+ +-------------------------------+ 688 ^ | Source IP address | 689 | | [192.0.2.1] | 690 | | Destination IP address | 691 | | [198.51.100.1] | 692 +-------------------------------+ +-------------------------------+ 693 | PLAT | ^ 694 | IPv4 pool address | | 695 | [192.0.2.1 - 192.0.2.100] | | 696 | PLAT-side XLATE IPv6 prefix | | 697 | [2001:db8:1234::/96] | | 698 +-------------------------------+ +-------------------------------+ 699 ^ | Source IP address | 700 | | [2001:db8:aaaa:200:5e10:0:0] | 701 | | Destination IP address | 702 | | [2001:db8:1234::198.51.100.1] | 703 +-------------------------------+ +-------------------------------+ 704 | CLAT Stateless XLATE function | ^ 705 | - - - - - - - - - - - - - - - | | 706 | PLAT-side XLATE IPv6 prefix | | 707 | [2001:db8:1234::/96] | | 708 | CLAT-side XLATE IPv6 prefix | | 709 | [2001:db8:aaaa::/64] | | 710 | CLAT-side XLATE IPv6 EUI-64 ID| | 711 | [02-00-5E-10-00-00-00-00] | | 712 + - - - - - - - - - - - - - - - + +-------------------------------+ 713 | ^ | | Source IP address | 714 | | | | [10.255.255.1] | 715 | | | | Destination IP address | 716 | | | | [198.51.100.1] | 717 + - - - - - - - - - - - - - - - + +-------------------------------+ 718 | CLAT NAT44 function | ^ 719 | - - - - - - - - - - - - - - - | | 720 | NAT44 NATed address | | 721 | [10.255.255.1/32] | | 722 +-------------------------------+ +-------------------------------+ 723 ^ | Source IP address | 724 | | [192.168.1.2] | 725 | | Destination IP address | 726 | | [198.51.100.1] | 727 +-------------------------------+ +-------------------------------+ 728 | IPv4 client | 729 | [192.168.1.2/24] | 730 +-------------------------------+ 731 Delegated IPv6 prefix for client: 2001:db8:aaaa::/64 733 Authors' Addresses 735 Masataka Mawatari 736 Japan Internet Exchange Co.,Ltd. 737 KDDI Otemachi Building 19F, 1-8-1 Otemachi, 738 Chiyoda-ku, Tokyo 100-0004 739 JAPAN 741 Phone: +81 3 3243 9579 742 Email: mawatari@jpix.ad.jp 744 Masanobu Kawashima 745 NEC AccessTechnica, Ltd. 746 800, Shimomata 747 Kakegawa-shi, Shizuoka 436-8501 748 JAPAN 750 Phone: +81 537 23 9655 751 Email: kawashimam@vx.jp.nec.com 753 Cameron Byrne 754 T-Mobile USA 755 Bellevue, Washington 98006 756 USA 758 Email: cameron.byrne@t-mobile.com