Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

No index entries found.

Understanding 464XLAT ALG Traffic Support

When you deploy IPv6 applications on mobile networks, be aware that some mobile operators cannot provide IPv6 support for their users, because some phone applications do not support an IPv6-only environment.

The solution is to use the NAT64 mechanism to access the IPv4-only content in the operator’s network and to use 464XLAT traffic to enable IPv4-only applications to work on IPv6-only networks.

The 464XLAT architecture is a combination of stateless translation on the customer-side translator (CLAT) and stateful translation on the provider-side translator (PLAT). The 464XLAT architecture is used to translate the packet information of a device using the combination of stateless (translates private IPv4 address to global IPv6 addresses, and vice versa) and stateful (translates IPv6 addresses to global IPv4 addresses, and vice versa) translation.

Figure 12 illustrates the 464XLAT architecture, which provides IPv4 connectivity across an IPv6-only network by combining existing and well-known stateful protocol translation on PLAT in the core and stateless protocol on CLAT at the edge. The private IPv4 host can reach global IPv4 hosts through both CLAT and PLAT translation. Conversely, the IPv6 host can directly reach other IPv6 hosts on the Internet without translation. This means that the customer premises equipment (CPE) can support CLAT and also operate as an IPv6 native router for native IPv6 traffic.

Figure 12: 464XLAT Architecture

464XLAT Architecture

Related Documentation

Modified: 2016-05-01