idnits 2.17.1 draft-ietf-v6ops-464xlat-10.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 (February 23, 2013) is 4077 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC6144' is defined on line 484, but no explicit reference was found in the text ** Obsolete normative reference: RFC 6145 (Obsoleted by RFC 7915) == Outdated reference: A later version (-17) exists of draft-ietf-behave-nat64-discovery-heuristic-13 -- Obsolete informational reference (is this intentional?): RFC 3633 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 5245 (Obsoleted by RFC 8445, RFC 8839) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force M. Mawatari 3 Internet-Draft Japan Internet Exchange Co.,Ltd. 4 Intended status: Informational M. Kawashima 5 Expires: August 27, 2013 NEC AccessTechnica, Ltd. 6 C. Byrne 7 T-Mobile USA 8 February 23, 2013 10 464XLAT: Combination of Stateful and Stateless Translation 11 draft-ietf-v6ops-464xlat-10 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 August 27, 2013. 39 Copyright Notice 41 Copyright (c) 2013 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Motivation and Uniqueness of 464XLAT . . . . . . . . . . . . . 4 59 4. Network Architecture . . . . . . . . . . . . . . . . . . . . . 4 60 4.1. Wireline Network Architecture . . . . . . . . . . . . . . 4 61 4.2. Wireless 3GPP Network Architecture . . . . . . . . . . . . 5 62 5. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 6 63 5.1. Wireline Network Applicability . . . . . . . . . . . . . . 6 64 5.2. Wireless 3GPP Network Applicability . . . . . . . . . . . 7 65 6. Implementation Considerations . . . . . . . . . . . . . . . . 7 66 6.1. IPv6 Address Format . . . . . . . . . . . . . . . . . . . 7 67 6.2. IPv4/IPv6 Address Translation Chart . . . . . . . . . . . 7 68 6.3. IPv6 Prefix Handling . . . . . . . . . . . . . . . . . . . 9 69 6.4. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 9 70 6.5. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 9 71 6.6. CLAT to CLAT communications . . . . . . . . . . . . . . . 9 72 7. Deployment Considerations . . . . . . . . . . . . . . . . . . 10 73 7.1. Traffic Engineering . . . . . . . . . . . . . . . . . . . 10 74 7.2. Traffic Treatment Scenarios . . . . . . . . . . . . . . . 10 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 76 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 77 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 78 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 79 11.1. Normative References . . . . . . . . . . . . . . . . . . . 11 80 11.2. Informative References . . . . . . . . . . . . . . . . . . 12 81 Appendix A. Examples of IPv4/IPv6 Address Translation . . . . . . 13 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 84 1. Introduction 86 With the exhaustion of the unallocated IPv4 address pools, it will be 87 difficult for many networks to assign IPv4 addresses to end users. 89 This document describes an IPv4 over IPv6 solution as one of the 90 techniques for IPv4 service extension and encouragement of IPv6 91 deployment. 464XLAT is not a one-for-one replacement of full IPv4 92 functionality. The 464XLAT architecture only supports IPv4 in the 93 client server model, where the server has a global IPv4 address. 94 This means it is not fit for IPv4 peer-to-peer communication or 95 inbound IPv4 connections. 464XLAT builds on IPv6 transport and 96 includes full any-to-any IPv6 communication. 98 The 464XLAT architecture described in this document uses IPv4/IPv6 99 translation standardized in [RFC6145] and [RFC6146]. It does not 100 require DNS64 [RFC6147] since an IPv4 host may simply send IPv4 101 packets, including packets to an IPv4 DNS server, which will be 102 translated on the customer side translator (CLAT) to IPv6 and back to 103 IPv4 on the provider side translator (PLAT). 464XLAT networks may use 104 DNS64 [RFC6147] to enable single stateful translation [RFC6146] 105 instead of 464XLAT double translation where possible. The 464XLAT 106 architecture encourages the IPv6 transition by making IPv4 services 107 reachable across IPv6-only networks and providing IPv6 and IPv4 108 connectivity to single-stack IPv4 or IPv6 servers and peers. 110 2. Terminology 112 PLAT: PLAT is Provider side translator(XLAT) that complies with 113 [RFC6146]. It translates N:1 global IPv6 addresses to global 114 IPv4 addresses, and vice versa. 116 CLAT: CLAT is Customer side translator(XLAT) that complies with 117 [RFC6145]. It algorithmically translates 1:1 private IPv4 118 addresses to global IPv6 addresses, and vice versa. The CLAT 119 function is applicable to a router or an end-node such as a 120 mobile phone. The CLAT should perform IP routing and 121 forwarding to facilitate packets forwarding through the 122 stateless translation even if it is an end-node. The CLAT as 123 a common home router or wireless Third Generation Partnership 124 Project (3GPP) router is expected to perform gateway 125 functions such as DHCP server and DNS proxy for local 126 clients. The CLAT uses different IPv6 prefixes for CLAT-side 127 and PLAT-side IPv4 addresses and therefore does not comply 128 with the sentence "Both IPv4-translatable IPv6 addresses and 129 IPv4-converted IPv6 addresses should use the same prefix." in 130 Section 3.3 of [RFC6052]. The CLAT does not facilitate 131 communications between a local IPv4-only node and an IPv6- 132 only node on the Internet. 134 3. Motivation and Uniqueness of 464XLAT 136 1. Minimal IPv4 resource requirements, maximum IPv4 efficiency 137 through statistical multiplexing. 139 2. No new protocols required, quick deployment. 141 3. IPv6-only networks are simpler and therefore less expensive to 142 operate than dual-stack networks. 144 4. Consistent native IP based monitoring, traffic engineering, and 145 capacity planning techniques can be applied without the 146 indirection or obfuscation of a tunnel. 148 4. Network Architecture 150 Examples of 464XLAT architectures are shown in the figures in the 151 following sections. 153 Wireline Network Architecture can fit in the situations where there 154 are clients behind the CLAT in the same way regardless of the type of 155 access service, for example FTTH, DOCSIS, or WiFi. 157 Wireless 3GPP Network Architecture fits in the situations where a 158 client terminates the wireless access network and may act as a router 159 with tethered clients. 161 4.1. Wireline Network Architecture 163 The private IPv4 host on this diagram can reach global IPv4 hosts via 164 translation on both CLAT and PLAT. On the other hand, the IPv6 host 165 can reach other IPv6 hosts on the Internet directly without 166 translation. This means that the CPE/CLAT can not only have the 167 function of a CLAT but also the function of an IPv6 native router for 168 native IPv6 traffic. The v4p host behind the CLAT on this diagram 169 has [RFC1918] addresses. 171 +------+ 172 | v6 | 173 | host | 174 +--+---+ 175 | 176 .---+---. 177 / \ 178 / IPv6 \ 179 | Internet | 180 \ / 181 `----+----' 182 | 183 +------+ | .---+---. .------. 184 | v6 +---+ +------+ / \ +------+ / \ 185 | host | | | | / IPv6 \ | | / IPv4 \ 186 +------+ +---+ CLAT +---+ Network +---+ PLAT +---+ Internet | 187 +--------+ | | | \ / | | \ / 188 | v4p/v6 +-+ +------+ `---------' +------+ `----+----' 189 | host | | | 190 +--------+ | +--+---+ 191 +------+ | | v4g | 192 | v4p +---+ | host | 193 | host | | +------+ 194 +------+ | 196 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 198 v6 : Global IPv6 199 v4p : Private IPv4 200 v4g : Global IPv4 202 Figure 1: Wireline Network Topology 204 4.2. Wireless 3GPP Network Architecture 206 The CLAT function on the User Equipment (UE) provides an [RFC1918] 207 address and IPv4 default route to the local node network stack. The 208 applications on the UE can use the private IPv4 address for reaching 209 global IPv4 hosts via translation on both the CLAT and the PLAT. On 210 the other hand, reaching IPv6 hosts (including host presented via 211 DNS64 [RFC6147]) does not require the CLAT function on the UE. 213 Presenting a private IPv4 network for tethering via NAT44 and 214 stateless translation on the UE is also an application of the CLAT. 216 +------+ 217 | v6 | 218 | host | 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 +----------------------+ | host | 238 +------+ 240 <- v4p -> XLAT <--------- v6 --------> XLAT <- v4g -> 242 v6 : Global IPv6 243 v4p : Private IPv4 244 v4g : Global IPv4 245 PDP : Packet Data Protocol 246 GGSN : Gateway GPRS Support Node 248 Figure 2: Wireless 3GPP Network Topology 250 5. Applicability 252 5.1. Wireline Network Applicability 254 When an Internet Service Provider (ISP) has IPv6 access service and 255 provides 464XLAT, the ISP can provide outgoing IPv4 service to end 256 users across an IPv6 access network. The result is that edge network 257 growth is no longer tightly coupled to the availability of scarce 258 IPv4 addresses. 260 If another ISP operates the PLAT, the edge ISP is only required to 261 deploy an IPv6 access network. All ISPs do not need IPv4 access 262 networks. They can migrate their access network to a simple and 263 highly scalable IPv6-only environment. 265 5.2. Wireless 3GPP Network Applicability 267 At the time of writing, in February 2013, the vast majority of mobile 268 networks are compliant to Pre-Release 9 3GPP standards. In Pre- 269 Release 9 3GPP networks, Global System for Mobile Communications 270 (GSM) and Universal Mobile Telecommunications System (UMTS) networks 271 must signal and support both IPv4 and IPv6 Packet Data Protocol (PDP) 272 attachments to access IPv4 and IPv6 network destinations [RFC6459]. 273 Since there are two PDPs required to support two address families, 274 this is double the number of PDPs required to support the status quo 275 of one address family, which is IPv4. 277 For the cases of connecting to an IPv4 literal or IPv4 socket that 278 require IPv4 connectivity, the CLAT function on the UE provides a 279 private IPv4 address and IPv4 default route on the host for the 280 applications to reference and bind to. Connections sourced from the 281 IPv4 interface are immediately routed to the CLAT function and passed 282 to the IPv6-only mobile network, destined for the PLAT. In summary, 283 the UE has the CLAT function that does a stateless translation 284 [RFC6145], but only when required by an IPv4-only scenario such as 285 IPv4 literals or IPv4-only sockets. The mobile network has a PLAT 286 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 6. Implementation Considerations 295 6.1. IPv6 Address Format 297 The IPv6 address format in 464XLAT is defined in Section 2.2 of 298 [RFC6052]. 300 6.2. IPv4/IPv6 Address Translation Chart 302 This chart offers an explanation about address translation 303 architecture using a combination of stateful translation at the PLAT 304 and stateless translation at the CLAT. The client on this chart is 305 delegated an IPv6 prefix from a prefix delegation mechanism such as 306 DHCPv6-PD [RFC3633], therefore it has a dedicated IPv6 prefix for 307 translation. 309 Destination IPv4 address 310 +----------------------------+ 311 | Global IPv4 address | 312 | assigned to IPv4 server | 313 +--------+ +----------------------------+ 314 | IPv4 | Source IPv4 address 315 | server | +----------------------------+ 316 +--------+ | Global IPv4 address | 317 ^ | assigned to IPv4 PLAT pool | 318 | +----------------------------+ 319 +--------+ 320 | PLAT | Stateful XLATE(IPv4:IPv6=1:n) 321 +--------+ 322 ^ 323 | 324 (IPv6 cloud) 325 Destination IPv6 address 326 +--------------------------------------------------------------+ 327 | IPv4-Embedded IPv6 address | 328 | defined in Section 2.2 of RFC6052 | 329 +--------------------------------------------------------------+ 330 Source IPv6 address 331 +--------------------------------------------------------------+ 332 | IPv4-Embedded IPv6 address | 333 | defined in Section 2.2 of RFC6052 | 334 +--------------------------------------------------------------+ 335 (IPv6 cloud) 336 ^ 337 | 338 +--------+ 339 | CLAT | Stateless XLATE(IPv4:IPv6=1:1) 340 +--------+ 341 ^ Destination IPv4 address 342 | +----------------------------+ 343 +--------+ | Global IPv4 address | 344 | IPv4 | | assigned to IPv4 server | 345 | client | +----------------------------+ 346 +--------+ Source IPv4 address 347 +----------------------------+ 348 | Private IPv4 address | 349 | assigned to IPv4 client | 350 +----------------------------+ 352 Case of enabling only stateless XLATE on CLAT 354 6.3. IPv6 Prefix Handling 356 There are two relevant IPv6 prefixes that the CLAT must be aware of. 358 First, CLAT must know its own IPv6 prefixes. The CLAT should acquire 359 a /64 for the uplink interface, a /64 for all downlink interfaces, 360 and a dedicated /64 prefix for the purpose of sending and receiving 361 statelessly translated packets. When a dedicated /64 prefix is not 362 available for translation from DHCPv6-PD [RFC3633], the CLAT may 363 perform NAT44 for all IPv4 LAN packets so that all the LAN originated 364 IPv4 packets appear from a single IPv4 address and are then 365 statelessly translated to one interface IPv6 address that is claimed 366 by the CLAT via NDP and defended with DAD. 368 Second, the CLAT must discover the PLAT-side translation IPv6 prefix 369 used as a destination of the PLAT. The CLAT will use this prefix as 370 the destination of all translation packets that require stateful 371 translation to the IPv4 Internet. It may discover the PLAT-side 372 translation prefix using [I-D.ietf-behave-nat64-discovery-heuristic]. 373 In the future some other mechanisms, such as a new DHCPv6 option, 374 will possibly be defined to communicate the PLAT-side translation 375 prefix. 377 6.4. DNS Proxy Implementation 379 The CLAT should implement a DNS proxy as defined in [RFC5625]. The 380 case of an IPv4-only node behind the CLAT querying an IPv4 DNS server 381 is undesirable since it requires both stateful and stateless 382 translation for each DNS lookup. The CLAT should set itself as the 383 DNS server via DHCP or other means and proxy DNS queries for IPv4 and 384 IPv6 LAN clients. Using the CLAT enabled home router or UE as a DNS 385 proxy is a normal consumer gateway function and simplifies the 386 traffic flow so that only IPv6 native queries are made across the 387 access network. DNS queries from the client that are not sent to the 388 DNS proxy on the CLAT must be allowed and are translated and 389 forwarded just like any other IP traffic. 391 6.5. CLAT in a Gateway 393 The CLAT feature can be implemented in a common home router or mobile 394 phone that has a tethering feature. Routers with a CLAT feature 395 should also provide common router services such as DHCP of [RFC1918] 396 addresses, DHCPv6, NDP with RA, and DNS service. 398 6.6. CLAT to CLAT communications 400 464XLAT is a hub and spoke architecture focused on enabling IPv4-only 401 services over IPv6-only networks. ICE [RFC5245] may be used to 402 support peer-to-peer communication within a 464XLAT network. 404 7. Deployment Considerations 406 7.1. Traffic Engineering 408 Even if the ISP for end users is different from the PLAT provider 409 (e.g. another ISP), it can implement traffic engineering 410 independently from the PLAT provider. Detailed reasons are below: 412 1. The ISP for end users can figure out IPv4 destination address 413 from translated IPv6 packet header, so it can implement traffic 414 engineering based on IPv4 destination address (e.g. traffic 415 monitoring for each IPv4 destination address, packet filtering 416 for each IPv4 destination address, etc.). The tunneling methods 417 do not have such an advantage, without any deep packet inspection 418 for processing the inner IPv4 packet of the tunnel packet. 420 2. If the ISP for end users can assign an IPv6 prefix greater than 421 /64 to each subscriber, this 464XLAT architecture can separate 422 IPv6 prefix for native IPv6 packets and the XLAT prefixes for 423 IPv4/IPv6 translation packets. Accordingly, it can identify the 424 type of packets ("native IPv6 packets" and "IPv4/IPv6 translation 425 packets"), and implement traffic engineering based on the IPv6 426 prefix. 428 7.2. Traffic Treatment Scenarios 430 The below table outlines how different permutations of connectivity 431 are treated in the 464XLAT architecture. 433 NOTE: 464XLAT double translation treatment will be stateless when a 434 dedicated /64 is available for translation on the CLAT. Otherwise, 435 the CLAT will have both stateful and stateless since it requires 436 NAT44 from the LAN to a single IPv4 address and then stateless 437 translation to a single IPv6 address. 439 +--------+-------------+-----------------------+-------------+ 440 | Server | Application | Traffic Treatment | Location of | 441 | | and Host | | Translation | 442 +--------+-------------+-----------------------+-------------+ 443 | IPv6 | IPv6 | End-to-end IPv6 | None | 444 +--------+-------------+-----------------------+-------------+ 445 | IPv4 | IPv6 | Stateful Translation | PLAT | 446 +--------+-------------+-----------------------+-------------+ 447 | IPv4 | IPv4 | 464XLAT | PLAT/CLAT | 448 +--------+-------------+-----------------------+-------------+ 450 Traffic Treatment Scenarios 452 8. Security Considerations 454 To implement a PLAT, see security considerations presented in Section 455 5 of [RFC6146]. 457 To implement a CLAT, see security considerations presented in Section 458 7 of [RFC6145]. The CLAT may comply with [RFC6092]. 460 9. IANA Considerations 462 This document has no actions for IANA. 464 10. Acknowledgements 466 The authors would like to thank JPIX NOC members, JPIX 464XLAT trial 467 service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv 468 Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo 469 Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, 470 Jouni Korhonen, Bjoern A. Zeeb, Hemant Singh, Vizdal Ales, Mark ZZZ 471 Smith, Mikael Abrahamsson, Tore Anderson, Teemu Savolainen, Alexandru 472 Petrescu, Gert Doering, Victor Kuarsingh, Ray Hunter, James Woodyatt, 473 Tom Taylor, and Remi Despres for their helpful comments. We also 474 would like to thank Fred Baker and Joel Jaeggli for their support. 476 11. References 478 11.1. Normative References 480 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 481 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 482 October 2010. 484 [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for 485 IPv4/IPv6 Translation", RFC 6144, April 2011. 487 [RFC6145] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation 488 Algorithm", RFC 6145, April 2011. 490 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 491 NAT64: Network Address and Protocol Translation from IPv6 492 Clients to IPv4 Servers", RFC 6146, April 2011. 494 11.2. Informative References 496 [I-D.ietf-behave-nat64-discovery-heuristic] 497 Savolainen, T., Korhonen, J., and D. Wing, "Discovery of 498 the IPv6 Prefix Used for IPv6 Address Synthesis", 499 draft-ietf-behave-nat64-discovery-heuristic-13 (work in 500 progress), November 2012. 502 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 503 E. Lear, "Address Allocation for Private Internets", 504 BCP 5, RFC 1918, February 1996. 506 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 507 Host Configuration Protocol (DHCP) version 6", RFC 3633, 508 December 2003. 510 [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment 511 (ICE): A Protocol for Network Address Translator (NAT) 512 Traversal for Offer/Answer Protocols", RFC 5245, 513 April 2010. 515 [RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", 516 BCP 152, RFC 5625, August 2009. 518 [RFC6092] Woodyatt, J., "Recommended Simple Security Capabilities in 519 Customer Premises Equipment (CPE) for Providing 520 Residential IPv6 Internet Service", RFC 6092, 521 January 2011. 523 [RFC6147] Bagnulo, M., Sullivan, A., Matthews, P., and I. van 524 Beijnum, "DNS64: DNS Extensions for Network Address 525 Translation from IPv6 Clients to IPv4 Servers", RFC 6147, 526 April 2011. 528 [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T., 529 Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation 530 Partnership Project (3GPP) Evolved Packet System (EPS)", 531 RFC 6459, January 2012. 533 [TS.23203] 3GPP, "Policy and charging control architecture", 3GPP 534 TS 23.203 10.7.0, June 2012. 536 Appendix A. Examples of IPv4/IPv6 Address Translation 538 The following is a example of IPv4/IPv6 Address Translation on the 539 464XLAT architecture. 541 In the case that an IPv6 prefix greater than /64 is assigned to an 542 end user by such as DHCPv6-PD [RFC3633], the CLAT can use a dedicated 543 /64 from the assigned IPv6 prefix. 545 Host & configuration value 546 +------------------------------+ 547 | IPv4 server | 548 | [198.51.100.1] | IP packet header 549 +------------------------------+ +--------------------------------+ 550 ^ | Destination IP address | 551 | | [198.51.100.1] | 552 | | Source IP address | 553 | | [192.0.2.1] | 554 +------------------------------+ +--------------------------------+ 555 | PLAT | ^ 556 | IPv4 pool address | | 557 | [192.0.2.1 - 192.0.2.100] | | 558 | PLAT-side XLATE IPv6 prefix | | 559 | [2001:db8:1234::/96] | | 560 +------------------------------+ +--------------------------------+ 561 ^ | Destination IP address | 562 | | [2001:db8:1234::198.51.100.1] | 563 | | Source IP address | 564 | | [2001:db8:aaaa::192.168.1.2] | 565 +------------------------------+ +--------------------------------+ 566 | CLAT | ^ 567 | PLAT-side XLATE IPv6 prefix | | 568 | [2001:db8:1234::/96] | | 569 | CLAT-side XLATE IPv6 prefix | | 570 | [2001:db8:aaaa::/96] | | 571 +------------------------------+ +--------------------------------+ 572 ^ | Destination IP address | 573 | | [198.51.100.1] | 574 | | Source IP address | 575 | | [192.168.1.2] | 576 +------------------------------+ +--------------------------------+ 577 | IPv4 client | 578 | [192.168.1.2/24] | 579 +------------------------------+ 580 Delegated IPv6 prefix for client: 2001:db8:aaaa::/56 582 Authors' Addresses 584 Masataka Mawatari 585 Japan Internet Exchange Co.,Ltd. 586 KDDI Otemachi Building 19F, 1-8-1 Otemachi, 587 Chiyoda-ku, Tokyo 100-0004 588 JAPAN 590 Phone: +81 3 3243 9579 591 Email: mawatari@jpix.ad.jp 593 Masanobu Kawashima 594 NEC AccessTechnica, Ltd. 595 800, Shimomata 596 Kakegawa-shi, Shizuoka 436-8501 597 JAPAN 599 Phone: +81 537 22 8274 600 Email: kawashimam@vx.jp.nec.com 602 Cameron Byrne 603 T-Mobile USA 604 Bellevue, Washington 98006 605 USA 607 Email: cameron.byrne@t-mobile.com