There's only one thing in the article I disagree with:
> RIRs (ARIN, RIPE, APNIC) Go Financially Bankrupt
This is purely an argument of pragmatism, rather than having any technical merit. If a system works, and meaningfully improves over another system, I couldn't care less that people aren't able to effectively monetize it.
Also there's a subsection about tier 1 networks and those are businesses.
So IPv8 can be available around year 2300 I guess :) (i have not inspected v8 RFC yet)
Eh. It took quite a long time, but even HN has a v6 address these days:
$ dig +short news.ycombinator.com ANY
2606:7100:1:67::26
209.216.230.207There would be no reason to adopt it if IPv6 were adopted.
Because it wasn’t implemented transparently at the OS. I can’t plug in to my ip6 only network and reach an ip4 address because end user OSes don’t implement clat transparently, even today in 2026, let alone 20 years ago.
Well over half of Google’s traffic is IPv6 in the USA, and it’s recently become over 50% of all Google’s traffic worldwide at weekends.
https://www.google.com/intl/en/ipv6/statistics.html#tab=per-... https://www.google.com/intl/en/ipv6/statistics.html
news to literally anyone on a mobile internet connection (which is most internet connections!)
(I understand that the real reason here is either a) OSX went to version 10, so don't want to be behind, or b) many systems would pattern match on windows version 9*" so Windows 9 would be treated as 95/98.)
Mac OS was said to skip 9 on the way to 10 due to a combo of some Asian numerology (just as Western numerology often encourages skipping "unlucky" 13) and also trying to make a clean break more obvious between System 8 and OSX. (The X being the 10, as Apple's favorite way to write 10 for various reasons. Which is why "OSX" was always a misnomer, accidentally burning the version number into the operating system name. Part of why Apple has been trying to get everyone on the "macOS" brand lately to pull the version number back out.)
A few weeks ago, the "Internet Protocol Version 8 (IPv8)" Internet-Draft (draft-thain-ipv8-02) caught our eye. The draft proposes replacing IPv4/IPv6 with a 64-bit hierarchical structure (ASN.Host), giving every 32-bit ASN holder 4.3 billion host addresses and consolidating DHCP, DNS, NTP, Syslog, OAuth, and WHOIS into a unified "Zone Server".
Instead of just debating the theoretical viability on mailing lists, our team at goonhost.rocks decided to implement the entire specification from scratch to see what happens when you deploy it across a distributed multi-AS network.
What we built: - Linux Kernel 6.6: Native AF_INET8 (family 46) socket layer, 28-byte packet routing, and sysctl boundary filters. https://gitlab.turborigby.xyz/goonhost-experiments/linux - Musl Libc: sockaddr_in8, inet_pton8, getaddrinfo() resolver support. https://gitlab.turborigby.xyz/goonhost-experiments/musl - iproute2: Native `ip -8 route` and `ip -8 addr` CLI tooling. https://gitlab.turborigby.xyz/goonhost-experiments/iproute2 - FRRouting: BGP8 daemon with Multi-Protocol Extensions (AFI/SAFI). https://gitlab.turborigby.xyz/goonhost-experiments/frrouting - IPv8 Zone Server (Go): 10-protocol platform (DHCP8, DNS8 TYPE_A8 88, SNTP, NetLog8, OAuth8, WHOIS8, XLATE8). https://gitlab.turborigby.xyz/goonhost-experiments/zoneserve... - Nginx & cURL: Patched for 64-bit IPv8 HTTP traffic. https://gitlab.turborigby.xyz/goonhost-experiments/nginx https://gitlab.turborigby.xyz/goonhost-experiments/curl
We set up a 10-node QEMU multi-AS testbed across 4 Autonomous Systems, pushed 112,000+ active routes into the kernel FIB, and ran continuous traffic generation.
While it works smoothly in an isolated lab, our report highlights several fundamental real-world failure modes: 1. PMTU & Silent MSS Blackholing (28-byte IP header breaks 1500-byte MTU paths without 1452-byte MSS clamping). 2. Asymmetric uRPF / BCP 38 drops on multi-homed ASNs. 3. Legacy DC switch ASIC/TCAM incompatibility (EtherType 0x88B8 punts to CPU exception path). 4. Monolithic Zone Server DDoS blast radius. 5. Systemic economic crises: RIR funding model collapse (90% revenue drop) and global BGP DFZ table explosion (3M–5M+ routes).
Full research report: https://cdnnn.goonhost.rocks/IPV8_RESEARCH_REPORT.md
Unlike boring corporate providers, we just actually have a sense of humor (or more accurately, the developer has overdosed on TikToks and brainrot reels).
Satirical branding doesn't mean the bare-metal servers or the kernel code aren't real.