Retevia is able to support several IPv6 transition technologies. We are happy to discuss the benefits and limitations of each with you.
The easiest to implement, NAT64 only requires using Retevia’s DNS resolvers. When your client does a DNS lookup for a system that doesn’t have IPv6, we create a unique IPv6 address on our systems. The client then sends traffic to our system over IPv6, and we do the translation. It works well for web traffic, but isn’t good for multi-way traffic like head-to-head gaming. It only works if the user’s system (PC, phone, tablet) supports IPv6 (and therefore, not for some TVs or video devices, or some games).
With broad support from home gateways, DS-Lite encapsulates IPv4 traffic in IPv6, and sends it to our systems over IPv6. We then do traditional NAT44 (NAPT) on that traffic. It works well for supporting legacy IPv6 consumer electronics, using well-understood NAT technology, with its inherent limitations.
MAP is “Mapping Address and Port,” and comes in two variations: MAP-T is Translation and MAP-E is Encapsulation. The distinction is the header details. Both provide somewhat broader support than DS-Lite does, but may not be supported by as many home routers.
Essentially double translation, 464xlat is basically NAT46 (for example, from a home device without IPv6) plus NAT64 (from IPv6 to a server without IPv6). It therefore supports many applications, including some that otherwise fail in the absence of IPv4. It works on several handsets, and has proven to be a good choice for several mobile operators, although it can be used on home networks, too.