logoalt Hacker News

Show HN: We Implemented the IPv8 Internet-Draft in Linux, Libc, and BGP

52 pointsby turborigbytoday at 12:45 PM31 commentsview on HN

Comments

kstrausertoday at 3:31 PM

I appreciate this. IPv8 is a terrible, terrible idea, and it’s good to see someone actually built it out to prove the depths of its terribleness. Well done.

Magicrafter13today at 5:13 PM

It's 2026 and we're turning troll/fake spec submissions into actual usable technology. What a time to be alive.

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.

show 1 reply
ameliaquiningtoday at 4:34 PM

Question for someone who knows more about this stuff than I do: Why don't the problems in the "economic collapse" section also apply to IPv6? Or do they, and we've only been saved by lack of adoption?

show 1 reply
ahmetozertoday at 3:09 PM

Thanks for testing, in year 2026, still IPv6 is not fully well utilized homes, corporates especially it is worse at clouds (AWS, GCP) if you not limit north to south, they are not good for east-to-west compared to telco providers. For example, GCP uses IP forwarding for IPv6 real IP address is not allocated at machine. At some of the components which is EKS is not support every case at IPv6.

So IPv8 can be available around year 2300 I guess :) (i have not inspected v8 RFC yet)

show 1 reply
citruscomputingtoday at 4:51 PM

Did you implement it, or did Claude implement it?

wbsuntoday at 2:41 PM

isn't any ipv6+ supposed to use any string address and no DNS is required at all? :D

TD-Linuxtoday at 3:10 PM

There is no "IPv8". Any crackpot can submit an internet-draft to the IETF, and this person happened to call theirs IPv8. If the submitter actually read the draft rather than feeding it to the slop cannon, they would have realized it is also a LLM hallucination that someone uploaded to IETF.

show 5 replies
nairboontoday at 3:06 PM

Where is IPv7?

show 2 replies
turborigbytoday at 12:51 PM

Hey HN,

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

show 1 reply
foo-bar-baz529today at 3:26 PM

The whole site appears to be satire, based on the homepage. I think we can ignore this article of theirs as well.

show 2 replies