Comparing IPv4 to IPv6 translation solutions

Ivan Pepelnjak
16 Jul 2010
With no usable mechanism in hand to address the IPv4 to IPv6 translation issue after a decade of trying, the time was ripe for new proposals to solve the IP addressing issue. As always, we got more than we asked for.
Some solutions try to avoid migration to IPv6 completely. These include Large Scale NAT (LSN); NAT44, which translates an IPv4 address to another IPv4 address; and NAT444.
Some try to implement dual stack and optimize IPv4 address utilization at the same time (DS-Lite and A+P).
In the end, only NAT64 goes all the way and addresses the problem by giving IPv6-only clients access to IPv4-only servers.
Here's a brief analysis of the most popular solutions.
IPv4 to IPv6 translation solutions: Large Scale NAT (NAT44)
Landline residential internet users have always received a unique public IPv4 address after being connected to the internet. Mobile operators were frequently using private IP address space and Network Address Translation (NAT) as they initially designed their networks as closed gardens using IP only to access Wireless Application Protocol (WAP) 1.0 content. LSN (see diagram below) addresses the IPv4 address shortage by rolling out large-scale private-IPv4-to-public-IPv4 NAT (thus the NAT44 acronym) to most residential users.


No Comments Yet! Be the first to share what you think!

This website uses cookies

This provides customers with a personalized experience and increases the efficiency of visiting the site, allowing us to provide the most efficient service. By using the website and accepting the terms of the policy, you consent to the use of cookies in accordance with the terms of this policy.