Show HN: We Implemented the IPv8 Internet-Draft in Linux, Libc, and BGP
A team of engineers at GoonHost decided to tackle the absurd IPv8 Internet-Draft head-on, opting to implement the protocol rather than merely dismiss its lofty claims. They built a full stack from kernel modifications to BGP, meticulously testing it in a multi-AS environment. The results offer a deep, entertaining dive into why a seemingly backward-compatible protocol would technically fail in the real world and catastrophically disrupt the internet's economic and infrastructural foundations.
The Lowdown
The goonhost.rocks team undertook an ambitious project: to implement the proposed IPv8 Internet-Draft, a specification widely dismissed as impractical or even farcical by network engineers. Rather than engaging in theoretical debate, they decided to build a full stack implementation from the Linux kernel up to user-space applications to rigorously test the protocol's claims and real-world viability.
- IPv8's Extraordinary Claims: The draft promised zero address exhaustion (4.3 billion addresses per ASN), 100% backward compatibility with IPv4, and total network management via a monolithic "Zone Server" bundling all core services.
- Comprehensive Implementation: GoonHost developed a complete IPv8 stack, modifying the Linux kernel (adding
AF_INET8), Musl Libc, iproute2, and FRRouting (for BGP8). They also built an IPv8 Zone Server in Go and adapted Nginx and cURL for IPv8. - Extensive Testing: The implementation was deployed on a 10-node QEMU multi-AS testbed with over 112,000 active routes and continuous traffic generation.
- The Good (Lab Environment): In isolation, IPv8 surprisingly functioned smoothly, with successful HTTP requests, fast DHCP8/NTP8 synchronization, and efficient routing table lookups.
- The Bad (Real-World Flaws): Key issues included Path MTU problems due to the larger IPv8 header (causing silent blackholing), multi-homing failures due to strict uRPF, and legacy switch ASICs punting IPv8 packets to the CPU slow-path, severely degrading performance.
- The Catastrophic (Economic Collapse): The most severe impacts projected were the financial ruin of Regional Internet Registries (RIRs) due to decoupled address volume from fees, a speculative "run on 32-bit ASNs," and a massive increase in the global BGP routing table (DFZ route explosion) requiring billions in infrastructure upgrades, alongside the destruction of Tier-1 transit margins.
- Monolithic Zone Server Vulnerability: The design of a single "Zone Server" for all critical services presented a single point of failure and a prime DDoS target.
This impressive technical undertaking definitively demonstrated that while IPv8 might function in a pristine lab, its fundamental design choices lead to severe technical incompatibilities with existing internet infrastructure and catastrophic economic consequences for current internet governance and service models.