> But it's built on top of similar unfulfilled promise: we're running out IPv4 addresses.
It’s not an unfulfilled promise. We’re out of IPv4 addresses and have been for almost a decade.
NAT444444444444444444444 is not the solution.
It’s not an unfulfilled promise. We’re out of IPv4 addresses and have been for almost a decade.
NAT444444444444444444444 is not the solution.
Transfering IPv4 prefixes comes with a 2 year transfer restriction period.
IPv4 addresses currently cost about $50, and you have to buy an entire subnet at once, minimum /24.
It makes perfect sense to start charging for them if you're running out of them and don't want to buy additional prefixes.
Not to mention that there's also additional cost involved in case someone was using that particular address (or even worse multiple addresses from the same /24) for spam or malicious purposes, because that means that the entire prefix is currently trashed and there's some effort involved for it to be removed from all the independently maintained blacklists etc.
Cloudflare in front of web services and it just works(tm).
For everything else - Argo can do arbitrary TCP (requires cloudflared though) and then you can start bugging your ISP about the very real need for IPv6.
Well... yeah? That's adding support for both stacks; just because you farmed it out to a middle-man doesn't mean that it's not there.
Not strictly true. It means that you only have to worry about IPv6 addresses in Layer 7, and you can forget about layers 2 and 3 altogether.
And Layer 7 isn’t a problem for people who should be deploying IPv6 right now because https://ipv6bingo.com/