| HN Mirror

> Hadn't thought of that, but it might not be a huge savings unless you were to go ipv6 only.

Even a small number of devices/services not supporting IPv6 can have huge costs:

> Our [American Indian] tribal network started out IPv6, but soon learned we had to somehow support IPv4 only traffic. It took almost 11 months in order to get a small amount of IPv4 addresses allocated for this use. In fact there were only enough addresses to cover maybe 1% of population. So we were forced to create a very expensive proxy/translation server in order to support this traffic.

> We learned a very expensive lesson. 71% of the IPv4 traffic we were supporting was from ROKU devices. 9% coming from DishNetwork & DirectTV satellite tuners, 11% from HomeSecurity cameras and systems, and remaining 9% we replaced extremely outdated Point of Sale(POS) equipment. So we cut ROKU some slack three years ago by spending a little over $300k just to support their devices.

* https://community.roku.com/t5/Features-settings-updates/It-s...

* Discussion: https://news.ycombinator.com/item?id=35047624

Sadly the post is now behind a login: what happened later was Apple donate a bunch of Apple TV devices to the tribal ISP and that cut their IPv4 usage by an order of magnitude (or some ridiculous number) and there were major savings. The ISP then recommended AppleTV to all of their customers to get the best viewing experience (because of the latency/overhead of CG-NAT when streaming video).

So the more you move over the more headroom you have for the broken IPv4-only systems. AIUI, the rollout of MAP-T/E has helped in that things are more stateless, and more work is done at the CPE, but there's still overhead.