Pollution in 1/8 (2010)
labs.ripe.net
labs.ripe.net
TL;DW: if you need to use example IPs in your documentation, use the ones listed in RFC3849 and RFC5737!
That said, 50 Mbps of traffic sounds like a non-issue for someone like Cloudflare, so I'm not surprised they took the prefix.
Edit: A post by Cloudflare (linked in another subthread here) mentioned 10 Gbps of traffic at the time Cloudflare started using it. Which, as it would be spread over multiple locations, is probably a relatively minor annoyance.
Jokes aside, where and why does this happen? Is it a genuine issue for some operators to route it?
https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...
It seems "too late" to revert this decision. Otherwise people will experience "Internet stopped working", blaming their ISP.
APNIC may decide to keep a working DNS server on 1.1.1.1, but ethically, routing traffic to someone else than Cloudflare is not great.
That being said, the use by Cloudflare is an excellent way to reclaim this part of the IP space, I don't see why they would terminate this collaboration.
That said, if a lot of people rely on 1.1.1.1 as DNS, it's worth considering whether reassignment qualifies as 'better' use of this resource. Not to mention the hassle caused by making changes to popular [anything].
Cloudflare: distant stare with vietnam flashbacks
> Only recently, in 2008, 1/8 was moved from "the IANA reserved" to the "IANA unallocated" pool of addresses. In January 2010 it was finally allocated to APNIC in order to be distributed to Local Internet Registries in the Asia-Pacific region.
:O
We engineers have accepted the available private address space <https://en.wikipedia.org/wiki/Private_network> but just think about how intuitive it is to an outsider? We make millions of people memorize 192.168.X.X to setup their home routers instead of the common sense letting the millions use the 1/8 privately? Just my opinion, but perhaps holding us back from IPv6 deployment is UI people don't see how an ordinary user would be able to remember a full "fd00::" address for day-to-day home networking or typing into their iPhone.
I don't have as much knowledge in computer ports background story, but last I checked <https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbe...> it's full of defunct, barely-used single players hogging up the coveted lower numbers, again leaving the millions to deal with possibly stepping on others' toes by using them "unofficially" and causing "pollution".
Last example is thinking about how many billions of wifi and cellular devices are forced into the tiniest slivers of the spectrum <https://upload.wikimedia.org/wikipedia/commons/c/c7/United_S...>. The engineers working so hard to cram even more signals into the 2.4GHz and 5GHz slivers need someone who is going to look up and realize it's time to expand the walls of the box they are trapped in. The only firm allocations should be for physics constraints, such as weather radar, but also means Wifi 6 should be a non-start due to not penetrating concrete, one of the most common materials of home construction.
Given these examples, the argument I'm trying to make is I find it insulting to consider the fact that people used the 1/8 block "pollution". It's the natural human guess at usable example numbers and the like, and much in the same way that repeated "human-error" in accidents is being re-argued as "engineering-error", I find the misallocation of the 1/8 block to be directly the fault of the RFC creators for not giving it to the people.
Port numbers are kinda obsolete on the internet since everyone uses port 443 to bypass middleboxes that block all the other ports in the name of "security". Hardcoding a number for each protocol instead of including IP+port in DNS responses was a stupid mistake
All consumer devices being forced to share ISM bands is BS, but let's be real even if more spectrum was opened up back in the 2000s, a lot of devices would still use the same range of frequencies because they wanna use the same cheap ICs and antennas
Good wifi performance requires an AP in every room. The lack of 6ghz penetration is great for high-end setups because it eliminates the hidden node problem
I would argue that if anyone had considered the possibility of people randomly choosing 1/8 addresses, the error was in reserving 1/8 in the first place. This only happened because there were no consequences to making up addresses.
BTW, 10/8 is private, and pretty easy to type.
The final barrier is crappy consumer routers with terrible default settings. Not much we can do but wait for these devices to die because the average user won't buy a new one until that happens
Is that distorted by cellular providers?
I know my wired ISP does not provide IPv6, even when I explicitly asked for it. They do CGNAT for most customers and assign a static IPv4 to anyone who complains (and then try to start charging for it a year later).
The ISP at my previous home was also IPv4 only (although, thankfully, no CGNAT).
When I was using Spectrum, was pleased to find they had (barely-passable) support, SLAAC wasn't a thing IIRC. Google Fiber has done well and so did AT&T's offering
There is a very strong pattern of variability[1] associated with day-of-week. Namely, there is a 5.1% increase of IPv6 traffic on weekends.
This pattern isn't reflected in Cloudflare's version of this chart[2]. Naturally, a curious mind asks, "Why would this be so?"
1. Seasonality - https://en.wikipedia.org/wiki/Seasonality