But until all web sites and services have migrated to IPv6, each smartphone still needs an IPv4 address, right? How does introducing IPv6 internally solve the problem you described, if a significant portion of traffic is still using IPv4?
But until all web sites and services have migrated to IPv6, each smartphone still needs an IPv4 address, right? How does introducing IPv6 internally solve the problem you described, if a significant portion of traffic is still using IPv4?
For those smartphones, the other half of the equation is 464XLAT adaptors at the edge of your network. So no, the smartphones don't get given IPv4 addresses at all.
What happens there is split into two scenarios
1. User goes to Facebook. Facebook has IPv6, everything just works, no extra expense
2. User goes to My Cat Blog. My Cat Blog is IPv4-only but two layers of NAT64 make it work anyway [ Edited: My previous explanation here was just wrong. Sorry. Go read up on 464XLAT if you care, the phone needs to know what's going on here, so this is easier to deliver for a phone network than to home computers... ]
Case 2 isn't much better than CG-NAT for IPv4 services - your smartphone still doesn't have a "real" IPv4 address. BUT the ISP only needs to spend on it in proportion to continued use of IPv4. As sites big or small offer IPv6, their users automatically stop relying on 464XLAT for those sites and cut the costs of the equipment, whereas people who choose CG-NAT are stuck paying for that forever.
It's probably uncommon, but I wonder what happens if a T-mobile customer has an older 3G-capable device that doesn't support CLAT.
[0] https://www.internetsociety.org/resources/deploy360/2014/cas...