> I'll switch when IPv4 stops working. Until then, I have no reason to switch.
IPv4 has stopped working for a lot of people already, especially if they're not with a fancy-pants ISP with lots of legacy IPv4 addresses already 'in the bank'. From another discussion:
> I've actually run into this [CG NAT] helping a friend host a game server on their residential internet in a more rural part of Texas. They had to call their ISP and request a static IP address at an extra cost of something like $5/mo.
So, because I don't want to change something that works and whose predictions of demise have been grossly overstated by decades I'm a shill?
"Just switch to it." Sure, pal, You pay all of the transition costs for everyone and you got a deal.
Not everything needs or should have a public IP address much less a bunch of IOT garbage. I suspect you, like everyone else who just says, whY aReNt We On IpV6 yEt??!11 imagine that most people's security practices are like yours and most people's ability to maintain software and security practices are like yours.
They are not.
I'm holding out for a modern address space extension conceived this century that doesn't suck, or at least a naming convention that doesn't suck. But no one will change until it's really needed and "hack" that improve the Internet, even if by accident, like NAT, can't fix it.
> Sure, pal, You pay all of the transition costs for everyone and you got a deal
Except at this point the costs are reversed - IPv4 costs more than IPv6. Just look at the article we're commenting on - supporting IPv4 clients is costing them a lot more. At the same time more and more cloud hosts are charging more for IPv4. In 2023 it's supporting IPv4 that costs more, not IPv6.
> It's costing ISPs
I hate my ISP so this is actually a feature. If they add an IPv4 surcharge to my bill then I'll reconsider.