Earlier quoted context omitted.
I guess there's a large pool of IP addresses used by residential ISPs that could be recycled relatively easily. When I lived in Ireland I only got a public IPv6, my IPv4 was behind CG-NAT. The nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. I could see ISPs making a quick buck by switching to CG-NAT on IPv4 so they can sell off their IPv4 blocks. Those IPs being recycled for…
> WThe nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. No issues? So, how are people supposed to be able to access your machine then?
AWS adds an extra 5.5M IPv4 addresses
81–90 of 283 posts
Re: AWS adds an extra 5.5M IPv4 addresses
#82Earlier quoted context omitted.
How does IPv4's use translate to anti-trust?
Promoting the continued dominance of a standard which causes artificial scarcity.
They need to go after other service provider, not isp. ISP provide CGNAT to facilitate access to ipv4 only service.
Re: AWS adds an extra 5.5M IPv4 addresses
#83IPv6 will never happen without someone forcing hands of big corps and ISPs to switch to Ipv6. Imagine all social media and streaming services, disable ipv4 within a month. These are not critical services but still will force ISPs to make the switch.
The funny thing is social media and streaming is already there: facebook.com has IPv6 address 2a03:2880:f119:8083:face:b00c:0:25de instagram.com has IPv6 address 2406:da00:ff00::23ae:4dc1 snapchat.com has IPv6 address 2001:4860:4802:36::15 netflix.com has IPv6 address 2600:1f14:62a:de82:822d:a423:9e4c:da8d youtube.com has IPv6 address 2404:6800:4006:810::200e The holdouts are somewhere else. Imagine if cloudflare and…
Meanwhile on the user side support has tripled from about 11% in 2016 to 33% recently [3].
I guess when you run a scalable web service, you need comparatively few publicly available ip addresses, and everyone has ipv4 anyways, while when you run an ISP, you need way more ip addresses. So the problem is way more pronounced for ISPs than the service providers. I guess the number of deployments with carrier grade NAT without ipv6 support is quite low.
[0]: http://www.delong.com/ipv6_alexa500.html
[1]: http://web.archive.org/web/20180826104925/http://www.delong....
[2]: http://web.archive.org/web/20161019011050/http://www.delong....
Re: AWS adds an extra 5.5M IPv4 addresses
#84Meanwhile, Hetzner just added a staggering $19/address setup fee and a soon doubling of prices for IPv4 addresses from them ostensibly due to the rising costs of getting addresses, yet still has virtually no support for IPv6 on their offerings outside of a /64 per dedicated server. https://docs.hetzner.com/general/others/ipv4-pricing/
Re: AWS adds an extra 5.5M IPv4 addresses
#85Last October, Amazon bought ~4 million addresses by bribing the corrupt technocrats of a radioamateur "non-profit" organization. Fuck Amazon, fuck those corrupt technocrats (like the ICANN/.org team who tried to sell the TLD). It's incredible what this kind of people can get away with. Previous discussion on HN: https://news.ycombinator.com/item?id=24753654
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
Re: AWS adds an extra 5.5M IPv4 addresses
#86low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Public auctions (which they didn't use) are currently in the $45-50 per IP ballpark. At that price it's $247.5 million worth of IPs. At auction the larger networks tend to go for less money per IP since there is a smaller market of people who want and can buy them (you have to be approved by ARIN/RIPE/etc. for the allocation size), which drives the price down.
Re: AWS adds an extra 5.5M IPv4 addresses
#87Meanwhile, Hetzner just added a staggering $19/address setup fee and a soon doubling of prices for IPv4 addresses from them ostensibly due to the rising costs of getting addresses, yet still has virtually no support for IPv6 on their offerings outside of a /64 per dedicated server. https://docs.hetzner.com/general/others/ipv4-pricing/
Re: AWS adds an extra 5.5M IPv4 addresses
#88Earlier quoted context omitted.
Why would you need anything other than a /64 on your server?
Maybe they mean that things like flexible/assignable ips and load balancers aren't available on v6.
Re: AWS adds an extra 5.5M IPv4 addresses
#89IPv6 will never happen without someone forcing hands of big corps and ISPs to switch to Ipv6. Imagine all social media and streaming services, disable ipv4 within a month. These are not critical services but still will force ISPs to make the switch.
Re: AWS adds an extra 5.5M IPv4 addresses
#90Earlier quoted context omitted.
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
I think the question is why not sell them openly instead sell them via backgate..