Re:IPv6 Traffic Crosses the 50% Mark for the First Time
by ninkendo on Thursday April 16, 2026 @07:36AM
(#47791594)
T-Mobile does: https://www.internetsociety.org/deploy360/2014/case-study-t-...
They use 464XLAT, basically NAT64/DNS64 with some extra cooperation on the OS’s part for backwards compatibility with apps that hard-code IPv4. You get only a v6 address, and your OS basically synthesizes an v4 network on your device in cooperation with their NAT64 router. But all the bytes going from your device through to their towers are ipv6. Talking to a v4-only website uses carrier-grade NAT64 when leaving the t-mobile network.
Re:IPv6 Traffic Crosses the 50% Mark for the First Time
by neojima on Thursday April 16, 2026 @11:46AM
(#47795074)
Additionally, their fixed-wireless product gives you a physical CPE that does the CLAT (NAT46) side of the 464XLAT.
To the local network, it looks like there's native IPv4, but it's translated to IPv6 by the gateway, and sent to the "nearest" NAT64 PoP to be translated back and sent along its merry way.
Re:IPv6 Traffic Crosses the 50% Mark for the First Time
by farfatched on Thursday April 16, 2026 @04:44AM
(#47790357)
According to https://www.ipv6.org.uk/wp-content/uploads/2023/11/13_IPv6-M... , Google is.
The author of the RFC is the author of the slides.
That seems to be a promising approach.