3 ms·
There are <20M address in the IPv4 private address space, vs. maybe ~100M smartphones in the USA. So, yes, you need to reuse addresses internally if you have mo
by rahimnathwani 7y ago
There are <20M address in the IPv4 private address space, vs. maybe ~100M smartphones in the USA. So, yes, you need to reuse addresses internally if you have more than 20% market share.
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?
- berti 7y agoI remember reading a few articles about a US mobile carrier successfully going IPv6 only with 464XLAT. Turns out my memory was correct and it was T-Mobile [0]. [0] https://www.internetsociety.org/resources/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/ https://www.internetsociety.org/resources/deploy360/2014/cas...
- Nyandalized 7y agoI believe every effort should be done to further the transition and make it less cumbersome in the future. Just the mental effect of "we're already partially using it" is invaluable
- tialaramex 7y agoThe _internal_ problem is addressing all your _internal_ systems, so that's what IPv6 immediately solves. You don't need everybody's cat blog to migrate to IPv6 to be able to connect to your 15 000 Cisco routers in 48 data centres distributed around the country, only the 15 000 Cisco routers need IPv6 addresses for that part. 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.
- rahimnathwani 7y agoHmmm, it seems that the necessary client-side stuff is included in Android >=JB, and iOS >=12: https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464XLAT https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464X... 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.