This article is focused on the US, a country which was never really going to feel the brunt of the IPv4 crunch. For an example of a real victim, look at Qatar, a country which only has a single IP address for the entire country (everyone sits behind a NAT): https://en.wikinews.org/wiki/Qatari_proxy_IP_address_tempora... [0] Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily)…
> Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily) to block the entire country from accessing Wikipedia
Can't they just block IPs from editing? Seems like that would solve the problem
This article is focused on the US, a country which was never really going to feel the brunt of the IPv4 crunch. For an example of a real victim, look at Qatar, a country which only has a single IP address for the entire country (everyone sits behind a NAT): https://en.wikinews.org/wiki/Qatari_proxy_IP_address_tempora... [0] Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily)…
> Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily) to block the entire country from accessing Wikipedia Can't they just block IPs from editing ? Seems like that would solve the problem
That's what they do. But this still prevents everyone in Qatar (who does not have an IP ban exception) from editing.
This article is focused on the US, a country which was never really going to feel the brunt of the IPv4 crunch. For an example of a real victim, look at Qatar, a country which only has a single IP address for the entire country (everyone sits behind a NAT): https://en.wikinews.org/wiki/Qatari_proxy_IP_address_tempora... [0] Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily)…
> Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily) to block the entire country from accessing Wikipedia Can't they just block IPs from editing ? Seems like that would solve the problem
Not a comment on the article, but IPv6 adoption relies on significant upgrades of existing hardware. Think of the size of the lookup table that a new bit of hardware has to be able to look up against and store compared to IPv4. Significantly more processing power is required, particularly if the hardware is a device that does inspection of some sort, even if basic! It isn't just a case of switching end machines to us…
Is that really that significant a problem? Moore's Law should have dealt with memory and processing power issues severalfold in the time since IPv6 rollout was called for.
It strikes me that it's more likely a lack of strategic investment in infrastructure.
This article is focused on the US, a country which was never really going to feel the brunt of the IPv4 crunch. For an example of a real victim, look at Qatar, a country which only has a single IP address for the entire country (everyone sits behind a NAT): https://en.wikinews.org/wiki/Qatari_proxy_IP_address_tempora... [0] Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily)…
To be fair, Qatar's situation has nothing to do with the IPv4 crisis. It's a country-wide firewall/proxy that exists due to political reasons and it wouldn't behave any differently if it was implemented in IPv6.
This is an extremely US-centric article. ARIN was never in as dire straits as the other RIRs. In Europe and Asia the situation is much worse. For example, lack of IPv4 addresses delayed DigitalOcean's growth in Amsterdam, and carrier-grade NAT is already being used by some consumer ISPs in Europe and Asia.
The article also ignores the fact that running dual-stack (like Comcast) requires just as many IPv4 addresses as before. Even after ISPs get IPv6 working flawlessly, their customers still need to access IPv4 websites, and that means CGNAT or some messy kind of tunneling will still be necessary.
Then don't run dual stack. Run native IPv6 and NAT64/DNS64. Or in DO's case make IPv4 access optional for smaller droplets and charge $1/month extra for it. In reality things like DB servers or backend app servers don't need public IPv4 addresses, and this would speed up IPv6 adoption considerably.
This article is focused on the US, a country which was never really going to feel the brunt of the IPv4 crunch. For an example of a real victim, look at Qatar, a country which only has a single IP address for the entire country (everyone sits behind a NAT): https://en.wikinews.org/wiki/Qatari_proxy_IP_address_tempora... [0] Whenever someone from Qatar decides to vandalize Wikipedia, Wikipedia is forced (temporarily)…
To be fair, Qatar's situation has nothing to do with the IPv4 crisis. It's a country-wide firewall/proxy that exists due to political reasons and it wouldn't behave any differently if it was implemented in IPv6.
Exactly - Qatar is not exactly some poor country. They have the cash to buy all the IP's they want, should they so choose.