A family of 5 where you need the bandwidth if everyone starts streaming videos at the same time. For gaming you'd advertise ping times, I haven't really seen that recently.
That matches what the presentation says: IPv6 is growing roughly as the internet grows, i.e. new ISPs go with it, because if you are starting from scratch, might as well do things in the modern way. (If you mean vanilla web startup, I think they have enough problems without risking to bork things up by misconfiguring a feature nobody really asks for...)
> When it comes to consumer ISPs, who are the people paying for the high-end packages?
Movie watchers and other media addicts; and they don't really care about IP addresses.
IMHO a lot of bigger ISPs have looked at the struggles of early adopters and decided the effort is not worth it. Most of their budgets these days go towards traffic shaping and caching, where IPv6 doesn't really help much. Established businesses are not clamouring for the feature, so why bother?
I agree that at some point things will change. I think the point of the article was that we thought we had reached that threshold a few years ago, but it looks like it wasn't really the case.
Docker doesn't support IPv6, I think.
A conslutant friend told a story about a customer who had been through a few mergers and demergers. One nightly database dump there involved parts of one database being copied to another, both internal to the same company, through five layers of NAT. One of the routers had a 1500-line NAT configuration.
When it comes to consumer ISPs, who are the people paying for the high-end packages?
> The issue is that most businesses are now so well-acquainted with NAT-ting, they don't really care for IP addresses. In fact, the more opaque your network topology is to the outside, the better from a security point of view. Every app works through http these days (because proxies are mandatory, again for security), so there is little need for real addresses.
Existing large businesses are happy with their current ways of doing things, sure. But those have never been the early adopters. IPv6 suits the startups (anyone who's working with containers hits problems from reusing the same subnets sooner or later) and it suits businesses that have to merge existing networks. No-one wants to be first, but there will come a point where the IPv4 costs are high enough to be worth doing something about.