Hacker News Reader

Comment by ramshanker | Hacker News Reader

Slightly tangent: Indian government has mandated all ISPs to upgrade all customers as IPv6 compatible by 31st December 2022. So India will be 100% IPv6 compatible by end of the year.

Once that happens, I wouldn't be surprised if IPv4 is deprecated along with 2G.

View on HN

"T-Mobile’s path to IPv6 Only":

> For the past 10 years [US] T-Mobile has worked towards creating an IPv6 environment and we are now getting very close to our goal. Stephan presents learning on how to successfully enable IPv6-only using DNS64 with or without 464XLAT. He will do a live demo of the different IP interfaces on an Android handset. Finally, he will discuss and give some best practices on how to handle DNS, applications, and websites that are having issues with DNS64.

* https://www.youtube.com/watch?v=nNMNglk_CvE

Apple mandated that all app in the iOS/mobile App Store had to support working on IPv6-only networks:

* https://developer.apple.com/support/ipv6/

Perhaps they should to the same thing for the macOS App Store.

>Apple mandated that all app in the iOS/mobile App Store had to support working on IPv6-only networks:

464XLAT is allowed, so ipv4-only services work fine.

iPhones on T-Mobile do not use 464XLAT, they use native IPv6 only. Some system frameworks like URLSession can do the NAT64 translation of hard-coded IPv4 addresses but it still goes over IPv6. In the video linked above: https://youtu.be/nNMNglk_CvE?t=1651

Precisely what I meant is that unless you use very low level networking functions in your app, you will have no problems with that requirement even if your server is ipv4-only, as is my case.

Reply on news.ycombinator.com