4 ms·
IPv6 isn't going to happen. Most people's needs are met by NAT for clients and SNI routing for servers. We ran out of IPv4 addresses years ago. If it was actual
by apitman 2y ago
IPv6 isn't going to happen. Most people's needs are met by NAT for clients and SNI routing for servers. We ran out of IPv4 addresses years ago. If it was actually a problem it would have happened then. It makes me said for the p2p internet but it's true.
- justahuman74 2y ago> If it was actually a problem It became a problem precisely the moment AWS starting charging for ipv4 addresses. "IPv4 will cost our company X dollars in 2026, supporting IPv6 by 2026 will cost Y dollars, a Z% saving" There's now a tangible motivator for various corporate systems to at least support ipv6 everywhere - which was the real ipv6 impediment. Residential ISP appear to be very capable of moving to v6, there are lots of examples of that happening in their backends, and they've demonstrated already that they're plenty capable of giving end users boxes the just so happen to do ipv6.
- apitman 2y agoYes and setting up a single IPv4 VPS as load balancer with SNI routing in front of IPv6-only instances solves that. Most people are probably using ELB anyway
- immibis 2y agoWhat do you mean not going to happen? It's already happening. It's about 45% of internet packets.
- paulddraper 2y agoNot happening for 55%. Try to connect to github.com over IPv6.
- remram 2y agoIt doesn't work now so it's never going to work?
- apitman 2y agoGitHub might work someday. Wide enough adoption that you can host a service without an IPv4 address will never happen.
- sroussey 2y agoHonestly, it could be a feature rather than a bug…
- paulddraper 2y agoIf it doesn't work for a website as large as technically forward as GitHub in 2024, the odds are not looking good.
- immibis 2y agoYes, that's one of the rare exceptions of a company trying to obsolete itself. It's actually one reason a bunch of people are moving away from Github.
- apitman 2y agoThe sun is about 45% of the way through its life.
- ElijahLynn 2y ago"We are introducing a new charge for public IPv4 addresses. Effective February 1, 2024 there will be a charge of $0.005 per IP per hour for all public IPv4 addresses" https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address...
- apitman 2y agoYes and setting up a single IPv4 VPS as load balancer with SNI routing in front of IPv6-only instances solves that. Most people are probably using ELB anyway.