idnits 2.17.1 draft-ietf-v6ops-464xlat-07.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 20, 2012) is 4265 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 735, but not defined == Unused Reference: 'RFC6144' is defined on line 586, 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. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force M. Mawatari 3 Internet-Draft Japan Internet Exchange Co.,Ltd. 4 Intended status: BCP M. Kawashima 5 Expires: February 21, 2013 NEC AccessTechnica, Ltd. 6 C. Byrne 7 T-Mobile USA 8 August 20, 2012 10 464XLAT: Combination of Stateful and Stateless Translation 11 draft-ietf-v6ops-464xlat-07 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 February 21, 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. BCP Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 59 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 5. Motivation and Uniqueness of 464XLAT . . . . . . . . . . . . . 4 61 6. Network Architecture . . . . . . . . . . . . . . . . . . . . . 4 62 6.1. Wireline Network Architecture . . . . . . . . . . . . . . 5 63 6.2. Wireless 3GPP Network Architecture . . . . . . . . . . . . 6 64 7. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 7 65 7.1. Wireline Network Applicability . . . . . . . . . . . . . . 7 66 7.2. Wireless 3GPP Network Applicability . . . . . . . . . . . 7 67 8. Implementation Considerations . . . . . . . . . . . . . . . . 7 68 8.1. IPv6 Address Format . . . . . . . . . . . . . . . . . . . 8 69 8.2. IPv4/IPv6 Address Translation Chart . . . . . . . . . . . 8 70 8.2.1. Case of enabling only stateless XLATE on CLAT . . . . 8 71 8.2.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 10 72 8.3. IPv6 Prefix Handling . . . . . . . . . . . . . . . . . . . 12 73 8.3.1. Case of enabling only stateless XLATE on CLAT . . . . 12 74 8.3.2. Case of enabling NAT44 and stateless XLATE on CLAT . . 12 75 8.4. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 12 76 8.5. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 13 77 8.6. CLAT to CLAT communications . . . . . . . . . . . . . . . 13 78 9. Deployment Considerations . . . . . . . . . . . . . . . . . . 13 79 9.1. Traffic Engineering . . . . . . . . . . . . . . . . . . . 13 80 9.2. Traffic Treatment Scenarios . . . . . . . . . . . . . . . 14 81 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 82 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 83 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 84 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 85 13.1. Normative References . . . . . . . . . . . . . . . . . . . 15 86 13.2. Informative References . . . . . . . . . . . . . . . . . . 15 87 Appendix A. Examples of IPv4/IPv6 Address Translation . . . . . . 16 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 90 1. Introduction 92 With the exhaustion of the unallocated IPv4 address pools, it will be 93 difficult for many networks to assign IPv4 addresses to end users. 95 This document describes an IPv4 over IPv6 solution as one of the 96 techniques for IPv4 service extension and encouragement of IPv6 97 deployment. 464XLAT is not a one-for-one replacement of full IPv4 98 functionality. The 464XLAT architecture only supports IPv4 in the 99 client server model, where the server has a global IPv4 address. 100 This means it is not fit for IPv4 peer-to-peer communication or 101 inbound IPv4 connections. 464XLAT builds on IPv6 transport and 102 includes full any-to-any IPv6 communication. 104 The 464XLAT architecture described in this document uses IPv4/IPv6 105 translation standardized in [RFC6145] and [RFC6146]. It does not 106 require DNS64 [RFC6147] since an IPv4 host may simply send IPv4 107 packets, including packets to an IPv4 DNS server, which will be 108 translated on the customer side translator(CLAT) to IPv6 and back to 109 IPv4 on the provider side translator(PLAT). 464XLAT networks may use 110 DNS64 [RFC6147] to enable single stateful translation [RFC6146] 111 instead of 464XLAT double translation where possible. The 464XLAT 112 architecture encourages the IPv6 transition by making IPv4 services 113 reachable across IPv6-only networks and providing IPv6 and IPv4 114 connectivity to single-stack IPv4 or IPv6 servers and peers. 116 By combining 464XLAT with BIH [RFC6535], it is also possible to 117 provide single IPv4 to IPv6 translation service, which will be needed 118 in the future case of IPv6-only servers and peers to be reached from 119 IPv4-only hosts across IPv6-only networks. 121 2. BCP Scenario 123 This BCP only applies when the following two criteria are present: 125 1. There is an IPv6-only network that uses stateful translation 126 [RFC6146] as the only mechanism for providing IPv4 access. 128 2. There are IPv4-only applications or hosts that must communicate 129 across the IPv6-only network to reach the IPv4 Internet. 131 3. Requirements Language 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 135 document are to be interpreted as described in [RFC2119]. 137 4. Terminology 139 PLAT: PLAT is Provider side translator(XLAT) that complies with 140 [RFC6146]. It translates N:1 global IPv6 addresses to global 141 IPv4 addresses, and vice versa. 143 CLAT: CLAT is Customer side translator(XLAT) that complies with 144 [RFC6145]. It algorithmically translates 1:1 private IPv4 145 addresses to global IPv6 addresses, and vice versa. The CLAT 146 function is applicable to a router or an end-node such as a 147 mobile phone. The CLAT SHOULD perform router function to 148 facilitate packets forwarding through the stateless 149 translation even if it is an end-node. In the case where the 150 access network does not allow for a dedicated IPv6 prefix for 151 translation, a NAT44 SHOULD be used between the router 152 function and the stateless translator function. The CLAT as 153 a common home router or wireless 3GPP router is expected to 154 perform gateway functions such as DHCP server and DNS proxy 155 for local clients. The CLAT does not comply with the 156 sentence "Both IPv4-translatable IPv6 addresses and IPv4- 157 converted IPv6 addresses SHOULD use the same prefix." that is 158 described on Section 3.3 in [RFC6052] due to using different 159 IPv6 prefixes for CLAT-side and PLAT-side IPv4 addresses. 161 5. Motivation and Uniqueness of 464XLAT 163 1. Minimal IPv4 resource requirements, maximum IPv4 efficiency 164 through statistical multiplexing. 166 2. No new protocols required, quick deployment. 168 3. IPv6-only networks are simpler and therefore less expensive to 169 operate. 171 6. Network Architecture 173 Examples of 464XLAT architectures are show in the figures in the 174 following sections. 176 Wireline Network Architecture can fit in the situations that there 177 are the clients behind the CLAT in the same way regardless of the 178 type of access service, for example FTTH, Cable, or WiFi. 180 Wireless 3GPP Network Architecture can fit in the situations that 181 client and node that terminate access network is same host in the 182 same way. 184 6.1. Wireline Network Architecture 186 The private IPv4 host on this diagram can reach global IPv4 hosts via 187 translation on both CLAT and PLAT. On the other hand, the IPv6 host 188 can reach other IPv6 hosts on the Internet directly without 189 translation. This means that the CPE/CLAT can not only have the 190 function of a CLAT but also the function of an IPv6 native router for 191 native IPv6 traffic. The v4p host behind the CLAT on this diagram 192 with the private IPv4 addresses. 194 +------+ 195 | v6 | 196 | host | 197 +--+---+ 198 | 199 .---+---. 200 / \ 201 / IPv6 \ 202 | Internet | 203 \ / 204 `----+----' 205 | 206 +------+ | .---+---. .------. 207 | v6 +---+ +------+ / \ +------+ / \ 208 | host | | | | / IPv6 \ | | / IPv4 \ 209 +------+ +---+ CLAT +---+ Network +---+ PLAT +---+ Internet | 210 +--------+ | | | \ / | | \ / 211 | v4p/v6 +-+ +------+ `---------' +------+ `----+----' 212 | host | | | 213 +--------+ | +--+---+ 214 +------+ | | v4g | 215 | v4p +---+ | host | 216 | host | | +------+ 217 +------+ | 219 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 221 v6 : Global IPv6 222 v4p : Private IPv4 223 v4g : Global IPv4 225 Figure 1: Wireline Network Topology 227 6.2. Wireless 3GPP Network Architecture 229 The CLAT function on the User Equipment (UE) provides an [RFC1918] 230 address and IPv4 default route. The applications on the UE can use 231 the private IPv4 address for reaching global IPv4 hosts via 232 translation on both CLAT and PLAT. On the other hand, reaching IPv6 233 hosts (including host presented via DNS64 [RFC6147]) does not require 234 the CLAT function on the UE. 236 +------+ 237 | v6 | 238 | host | 239 +--+---+ 240 | 241 .---+---. 242 / \ 243 / IPv6 \ 244 | Internet | 245 \ / 246 UE / Mobile Phone `---------' 247 +----------------------+ | 248 | +----+ | | .---+---. .------. 249 | | v6 +----+ +------+ / \ +------+ / \ 250 | +----+ | | | / IPv6 PDP \ | | / IPv4 \ 251 | +---+ CLAT +---+ Mobile Core +---+ PLAT +--+ Internet | 252 | | | | \ GGSN / | | \ / 253 | | +------+ \ ' +------+ `----+---' 254 | +-----+ | | `-------' | 255 | | v4p +---+ | +--+---+ 256 | +-----+ | | | v4g | 257 +----------------------+ | host | 258 +------+ 260 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 262 v6 : Global IPv6 263 v4p : Private IPv4 264 v4g : Global IPv4 266 Figure 2: Wireless 3GPP Network Topology 268 7. Applicability 270 7.1. Wireline Network Applicability 272 When an ISP has IPv6 access service and provides 464XLAT, the ISP can 273 provide outgoing IPv4 service to end users across an IPv6 access 274 network. The result is that edge network growth is no longer tightly 275 coupled to the availability of scarce IPv4 addresses. 277 If another ISP operates the PLAT, the edge ISP is only required to 278 deploy an IPv6 access network. All ISPs do not need IPv4 access 279 networks. They can migrate their access network to a simple and 280 highly scalable IPv6-only environment. 282 Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE 283 camp Spring 2012. The result is described in 284 [I-D.hazeyama-widecamp-ipv6-only-experience]. 286 7.2. Wireless 3GPP Network Applicability 288 The vast majority of mobile networks are compliant to Pre-Release 9 289 3GPP standards. In Pre-Release 9 3GPP networks, GSM and UMTS 290 networks must signal and support both IPv4 and IPv6 Packet Data 291 Protocol (PDP) attachments to access IPv4 and IPv6 network 292 destinations [RFC6459]. Since there are two PDPs required to support 293 two address families, this is double the number of PDPs required to 294 support the status quo of one address family, which is IPv4. 296 For the IPv4 literal or IPv4 socket applications that require IPv4 297 connectivity, the CLAT function on the UE provides a private IPv4 298 address and IPv4 default route on the host for the applications to 299 reference and bind to. Connections sourced from the IPv4 interface 300 are immediately routed to the CLAT function and passed to the IPv6- 301 only mobile network, destined for the PLAT. In summary, the UE has 302 the CLAT function that does a stateless translation [RFC6145], but 303 only when required. The mobile network has a PLAT that does stateful 304 translation [RFC6146]. 306 464XLAT works with today's existing systems as much as possible. 307 464XLAT is compatible with existing network based deep packet 308 inspection solutions like 3GPP standardized Policy and Charging 309 Control (PCC) [TS.23203]. 311 8. Implementation Considerations 312 8.1. IPv6 Address Format 314 The IPv6 address format in 464XLAT is defined in Section 2.2 of 315 [RFC6052]. 317 8.2. IPv4/IPv6 Address Translation Chart 319 8.2.1. Case of enabling only stateless XLATE on CLAT 321 This case should be used when a prefix delegation mechanism such as 322 DHCPv6-PD [RFC3633] is available to assign a dedicated translation 323 prefix to the CLAT. 325 Destination IPv4 address 326 +----------------------------+ 327 | Global IPv4 address | 328 | assigned to IPv4 server | 329 +--------+ +----------------------------+ 330 | IPv4 | Source IPv4 address 331 | server | +----------------------------+ 332 +--------+ | Global IPv4 address | 333 ^ | assigned to IPv4 PLAT pool | 334 | +----------------------------+ 335 +--------+ 336 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 337 +--------+ 338 ^ 339 | 340 (IPv6 cloud) 341 Destination IPv6 address 342 +--------------------------------------------------------------+ 343 | IPv4-Embedded IPv6 address | 344 | defined in Section 2.2 of RFC6052 | 345 +--------------------------------------------------------------+ 346 Source IPv6 address 347 +--------------------------------------------------------------+ 348 | IPv4-Embedded IPv6 address | 349 | defined in Section 2.2 of RFC6052 | 350 +--------------------------------------------------------------+ 351 (IPv6 cloud) 352 ^ 353 | 354 +--------+ 355 | | In the case the CLAT has a 356 | | dedicated IPv6 prefix for 357 | CLAT | translation, the CLAT can 358 | | perform with only Stateless 359 | | XLATE (IPv4:IPv6=1:1). 360 +--------+ 361 ^ Destination IPv4 address 362 | +----------------------------+ 363 +--------+ | Global IPv4 address | 364 | IPv4 | | assigned to IPv4 server | 365 | client | +----------------------------+ 366 +--------+ Source IPv4 address 367 +----------------------------+ 368 | Private IPv4 address | 369 | assigned to IPv4 client | 370 +----------------------------+ 372 Case of enabling only stateless XLATE on CLAT 374 8.2.2. Case of enabling NAT44 and stateless XLATE on CLAT 376 This case should be used when a prefix delegation mechanism is not 377 available to assign a dedicated translation prefix to the CLAT. In 378 this case, NAT44 SHOULD be used so that all IPv4 source addresses are 379 mapped to a single IPv6 address. 381 Destination IPv4 address 382 +----------------------------+ 383 | Global IPv4 address | 384 | assigned to IPv4 server | 385 +--------+ +----------------------------+ 386 | IPv4 | Source IPv4 address 387 | server | +----------------------------+ 388 +--------+ | Global IPv4 address | 389 ^ | assigned to IPv4 PLAT pool | 390 | +----------------------------+ 391 +--------+ 392 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 393 +--------+ 394 ^ 395 | 396 (IPv6 cloud) 397 Destination IPv6 address 398 +--------------------------------------------------------------+ 399 | IPv4-Embedded IPv6 address | 400 | defined in Section 2.2 of RFC6052 | 401 +--------------------------------------------------------------+ 402 Source IPv6 address 403 +--------------------------------------------------------------+ 404 | IPv4-Embedded IPv6 address | 405 | defined in Section 2.2 of RFC6052 | 406 +--------------------------------------------------------------+ 407 (IPv6 cloud) 408 ^ 409 | 410 +--------+ 411 | | In the case the CLAT does not 412 | | have a dedicated IPv6 prefix 413 | CLAT | for translation, the CLAT can 414 | | perform with NAT44 and 415 | | Stateless XLATE 416 | | (IPv4:IPv6=1:1). 417 +--------+ 418 ^ Destination IPv4 address 419 | +----------------------------+ 420 +--------+ | Global IPv4 address | 421 | IPv4 | | assigned to IPv4 server | 422 | client | +----------------------------+ 423 +--------+ Source IPv4 address 424 +----------------------------+ 425 | Private IPv4 address | 426 | assigned to IPv4 client | 427 +----------------------------+ 429 Case of enabling NAT44 and stateless XLATE on CLAT 431 8.3. IPv6 Prefix Handling 433 8.3.1. Case of enabling only stateless XLATE on CLAT 435 From the delegated DHCPv6 [RFC3633] prefix, a /64 is dedicated to 436 source and receive IPv6 packets associated with the stateless 437 translation [RFC6145]. 439 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 440 as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or 441 [I-D.ietf-behave-nat64-discovery-heuristic]. 443 8.3.2. Case of enabling NAT44 and stateless XLATE on CLAT 445 In the case that DHCPv6-PD [RFC3633] is not available, the CLAT may 446 not have a dedicated IPv6 prefix for translation. If the CLAT does 447 not have a dedicated IPv6 prefix for translation, the CLAT can 448 perform NAT44 and stateless translation [RFC6145]. 450 IPv4 packets from the LAN are NAT44 to the private IPv4 host address 451 of the CLAT that is not included in LAN segment of CLAT. Then, the 452 CLAT will do a stateless translation [RFC6145] so that the IPv4 453 packets from the CLAT IPv4 host address are translated to the CLAT 454 WAN IPv6 address as described in [RFC6145]. 456 If the CLAT cannot perform ND Proxy [RFC4389] due to the restriction 457 of the implementation, the CLAT may use a dedicated IANA assigned 458 EUI-64 ID for creating a translated IPv6 address to be used in 459 stateless translation [RFC6145]. This will allow the CLAT to avoid 460 possible IPv6 address duplication issues between an IPv6 address for 461 stateless translation [RFC6145] in the CLAT and an IPv6 address 462 assigned to native IPv6 nodes behind the CLAT. This document 463 describes an example for this case in Example 2. of the Appendix A. 465 The CLAT MAY discover the Pref64::/n of the PLAT via some method such 466 as TR-069, DNS APL RR [RFC3123] or 467 [I-D.ietf-behave-nat64-discovery-heuristic]. 469 8.4. DNS Proxy Implementation 471 The CLAT SHOULD implement a DNS proxy as defined in [RFC5625]. The 472 case of an IPv4-only node behind the CLAT querying an IPv4 DNS server 473 is undesirable since it requires both stateful and stateless 474 translation for each DNS lookup. The CLAT SHOULD set itself as the 475 DNS server via DHCP or other means and proxy DNS queries for IPv4 and 476 IPv6 LAN clients. Using the CLAT enabled home router or UE as a DNS 477 proxy is a normal consumer gateway function and simplifies the 478 traffic flow so that only IPv6 native queries are made across the 479 access network. The CLAT SHOULD allow for a client to query any DNS 480 server of its choice and bypass the proxy. 482 8.5. CLAT in a Gateway 484 The CLAT is a stateless translation feature which can be implemented 485 in a common home router or mobile phone that has a tethering feature. 486 The router with CLAT function SHOULD provide common router services 487 such as DHCP of [RFC1918] addresses, DHCPv6, and DNS service. 489 8.6. CLAT to CLAT communications 491 While CLAT to CLAT IPv4 communication may work when the client IPv4 492 subnets do not overlap, this traffic flow is out of scope. 464XLAT is 493 a hub and spoke architecture focused on enabling IPv4-only services 494 over IPv6-only networks. 496 9. Deployment Considerations 498 9.1. Traffic Engineering 500 Even if the ISP for end users is different from the PLAT provider 501 (e.g. another ISP), it can implement traffic engineering 502 independently from the PLAT provider. Detailed reasons are below: 504 1. The ISP for end users can figure out IPv4 destination address 505 from translated IPv6 packet header, so it can implement traffic 506 engineering based on IPv4 destination address (e.g. traffic 507 monitoring for each IPv4 destination address, packet filtering 508 for each IPv4 destination address, etc.). The tunneling methods 509 do not have such an advantage, without any deep packet inspection 510 for processing the inner IPv4 packet of the tunnel packet. 512 2. If the ISP for end users can assign an IPv6 prefix greater than 513 /64 to each subscriber, this 464XLAT architecture can separate 514 IPv6 prefix for native IPv6 packets and the XLAT prefixes for 515 IPv4/IPv6 translation packets. Accordingly, it can identify the 516 type of packets ("native IPv6 packets" and "IPv4/IPv6 translation 517 packets"), and implement traffic engineering based on the IPv6 518 prefix. 520 9.2. Traffic Treatment Scenarios 522 This 464XLAT architecture has capabilities. One is a IPv4 -> IPv6 -> 523 IPv4 translation for sharing global IPv4 addresses as a basic 524 function, another, if combined with BIH [RFC6535], is a IPv4 -> IPv6 525 translation for reaching IPv6-only servers from IPv4-only clients 526 that can not support IPv6. IPv4-only clients must be support through 527 the long period of global transition to IPv6. 529 +--------+-------------+-----------------------+-------------+ 530 | Server | Application | Traffic Treatment | Location of | 531 | | and Host | | Translation | 532 +--------+-------------+-----------------------+-------------+ 533 | IPv6 | IPv6 | End-to-end IPv6 | None | 534 +--------+-------------+-----------------------+-------------+ 535 | IPv4 | IPv6 | Stateful Translation | PLAT | 536 +--------+-------------+-----------------------+-------------+ 537 | IPv4 | IPv4 | 464XLAT | PLAT/CLAT | 538 +--------+-------------+-----------------------+-------------+ 539 | IPv6 | IPv4 | BIH | CLAT | 540 +--------+-------------+-----------------------+-------------+ 542 Traffic Treatment Scenarios 544 The above chart shows most common traffic types and traffic 545 treatment. 547 10. Security Considerations 549 To implement a PLAT, see security considerations presented in Section 550 5 of [RFC6146]. 552 To implement a CLAT, see security considerations presented in Section 553 7 of [RFC6145]. The CLAT MAY comply with [RFC6092]. 555 11. IANA Considerations 557 IANA is requested to reserve a Modified EUI-64 identifier for 464XLAT 558 according to section 2.2.2 of [RFC5342]. Its suggested value is 02- 559 00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00- 560 00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be 561 taken in reserved or available values. 563 12. Acknowledgements 565 The authors would like to thank JPIX NOC members, JPIX 464XLAT trial 566 service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv 567 Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo 568 Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, 569 Jouni Korhonen, and Bjoern A. Zeeb for their helpful comments. 570 Special acknowledgments go to Remi Despres for his plentiful supports 571 and suggestions, especially about using NAT44 with IANA's EUI-64 ID. 572 We also would like to thank Fred Baker and Joel Jaeggli for their 573 support. 575 13. References 577 13.1. Normative References 579 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 580 Requirement Levels", BCP 14, RFC 2119, March 1997. 582 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 583 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 584 October 2010. 586 [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for 587 IPv4/IPv6 Translation", RFC 6144, April 2011. 589 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 590 Algorithm", RFC 6145, April 2011. 592 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 593 NAT64: Network Address and Protocol Translation from IPv6 594 Clients to IPv4 Servers", RFC 6146, April 2011. 596 13.2. Informative References 598 [I-D.hazeyama-widecamp-ipv6-only-experience] 599 Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura, 600 "Experiences from IPv6-Only Networks with Transition 601 Technologies in the WIDE Camp Spring 2012", 602 draft-hazeyama-widecamp-ipv6-only-experience-01 (work in 603 progress), March 2012. 605 [I-D.ietf-behave-nat64-discovery-heuristic] 606 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 607 IPv6 Prefix Used for IPv6 Address Synthesis", 608 draft-ietf-behave-nat64-discovery-heuristic-11 (work in 609 progress), July 2012. 611 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 612 E. Lear, "Address Allocation for Private Internets", 613 BCP 5, RFC 1918, February 1996. 615 [RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes 616 (APL RR)", RFC 3123, June 2001. 618 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 619 Host Configuration Protocol (DHCP) version 6", RFC 3633, 620 December 2003. 622 [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery 623 Proxies (ND Proxy)", RFC 4389, April 2006. 625 [RFC5342] Eastlake, D., "IANA Considerations and IETF Protocol Usage 626 for IEEE 802 Parameters", BCP 141, RFC 5342, 627 September 2008. 629 [RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", 630 BCP 152, RFC 5625, August 2009. 632 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 633 Customer Premises Equipment (CPE) for Providing 634 Residential IPv6 Internet Service", RFC 6092, 635 January 2011. 637 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 638 Beijnum, "DNS64: DNS Extensions for Network Address 639 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 640 April 2011. 642 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 643 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 644 Partnership Project (3GPP) Evolved Packet System (EPS)", 645 RFC 6459, January 2012. 647 [RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts 648 Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012. 650 [TS.23203] 3GPP, "Policy and charging control architecture", 3GPP 651 TS 23.203 10.7.0, June 2012. 653 Appendix A. Examples of IPv4/IPv6 Address Translation 655 The following are examples of IPv4/IPv6 Address Translation on the 656 464XLAT architecture. 658 Example 1. (Case of enabling only stateless XLATE on CLAT) 660 In the case that an IPv6 prefix greater than /64 is assigned to an 661 end user by such as DHCPv6-PD [RFC3633], only the Stateless XLATE 662 functionality should be enabled on the CLAT as the CLAT can use a 663 dedicated /64 from the assigned IPv6 prefix. 665 Host & configuration value 666 +------------------------------+ 667 | IPv4 server | 668 | [198.51.100.1] | IP packet header 669 +------------------------------+ +--------------------------------+ 670 ^ | Destination IP address | 671 | | [198.51.100.1] | 672 | | Source IP address | 673 | | [192.0.2.1] | 674 +------------------------------+ +--------------------------------+ 675 | PLAT | ^ 676 | IPv4 pool address | | 677 | [192.0.2.1 - 192.0.2.100] | | 678 | PLAT-side XLATE IPv6 prefix | | 679 | [2001:db8:1234::/96] | | 680 +------------------------------+ +--------------------------------+ 681 ^ | Destination IP address | 682 | | [2001:db8:1234::198.51.100.1] | 683 | | Source IP address | 684 | | [2001:db8:aaaa::192.168.1.2] | 685 +------------------------------+ +--------------------------------+ 686 | CLAT | ^ 687 | PLAT-side XLATE IPv6 prefix | | 688 | [2001:db8:1234::/96] | | 689 | CLAT-side XLATE IPv6 prefix | | 690 | [2001:db8:aaaa::/96] | | 691 +------------------------------+ +--------------------------------+ 692 ^ | Destination IP address | 693 | | [198.51.100.1] | 694 | | Source IP address | 695 | | [192.168.1.2] | 696 +------------------------------+ +--------------------------------+ 697 | IPv4 client | 698 | [192.168.1.2/24] | 699 +------------------------------+ 700 Delegated IPv6 prefix for client: 2001:db8:aaaa::/56 701 Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT) 703 In the case that IPv6 prefix /64 is assigned to end users, the 704 function of NAT44 and Stateless XLATE should be enabled on CLAT. 705 Because the CLAT does not have dedicated IPv6 prefix for translation. 707 Host & configuration value 708 +-------------------------------+ 709 | IPv4 server | 710 | [198.51.100.1] | IP packet header 711 +-------------------------------+ +-------------------------------+ 712 ^ | Destination IP address | 713 | | [198.51.100.1] | 714 | | Source IP address | 715 | | [192.0.2.1] | 716 +-------------------------------+ +-------------------------------+ 717 | PLAT | ^ 718 | IPv4 pool address | | 719 | [192.0.2.1 - 192.0.2.100] | | 720 | PLAT-side XLATE IPv6 prefix | | 721 | [2001:db8:1234::/96] | | 722 +-------------------------------+ +-------------------------------+ 723 ^ | Destination IP address | 724 | | [2001:db8:1234::198.51.100.1] | 725 | | Source IP address | 726 | | [2001:db8:aaaa:0:200:5e10::] | 727 +-------------------------------+ +-------------------------------+ 728 | CLAT Stateless XLATE function | ^ 729 | - - - - - - - - - - - - - - - | | 730 | PLAT-side XLATE IPv6 prefix | | 731 | [2001:db8:1234::/96] | | 732 | CLAT-side XLATE IPv6 prefix | | 733 | [2001:db8:aaaa::/64] | | 734 | CLAT-side XLATE IPv6 EUI-64 ID| | 735 | [02-00-5E-10-00-00-00-00] | | 736 + - - - - - - - - - - - - - - - + +-------------------------------+ 737 | ^ | | Destination IP address | 738 | | | | [198.51.100.1] | 739 | | | | Source IP address | 740 | | | | [10.255.255.1] | 741 + - - - - - - - - - - - - - - - + +-------------------------------+ 742 | CLAT NAT44 function | ^ 743 | - - - - - - - - - - - - - - - | | 744 | NAT44 NATed address | | 745 | [10.255.255.1/32] | | 746 +-------------------------------+ +-------------------------------+ 747 ^ | Destination IP address | 748 | | [198.51.100.1] | 749 | | Source IP address | 750 | | [192.168.1.2] | 751 +-------------------------------+ +-------------------------------+ 752 | IPv4 client | 753 | [192.168.1.2/24] | 754 +-------------------------------+ 755 Delegated IPv6 prefix for client: 2001:db8:aaaa::/64 757 Authors' Addresses 759 Masataka Mawatari 760 Japan Internet Exchange Co.,Ltd. 761 KDDI Otemachi Building 19F, 1-8-1 Otemachi, 762 Chiyoda-ku, Tokyo 100-0004 763 JAPAN 765 Phone: +81 3 3243 9579 766 Email: mawatari@jpix.ad.jp 768 Masanobu Kawashima 769 NEC AccessTechnica, Ltd. 770 800, Shimomata 771 Kakegawa-shi, Shizuoka 436-8501 772 JAPAN 774 Phone: +81 537 23 9655 775 Email: kawashimam@vx.jp.nec.com 777 Cameron Byrne 778 T-Mobile USA 779 Bellevue, Washington 98006 780 USA 782 Email: cameron.byrne@t-mobile.com