IPv8: The Draft of a New Internet — Transit AI<br>Sign in

Sign up

Account

Sign out

Blog · July 16, 2026 · Knox Hutchinson<br>IPv8: The Draft of a New Internet

Update (July 20, 2026): This read-through took the draft seriously on its engineering merits and left the deployment question open. The follow-up closes it: Why IPv8 Will Never Work (and the Ideas Worth Stealing) .

The IPv6 Paradox: Winning the Stat, Losing the War

What IPv8 Actually Proposes

The Zone Server: Your Whole Network Stack in One Pair of Boxes

A Home Network Under IPv8

How Big Does a Zone Server Have to Be?

Where It Gets Expensive

The Skeptic’s Section

Why We’re Watching

In April, an Internet-Draft landed with the least modest title possible: Internet Protocol Version 8 (draft-thain-ipv8-00, J. Thain, One Limited, 14 April 2026). It is an individual submission — not adopted by any IETF working group, intended status Standards Track, expires in October. Most drafts like this sink without a ripple.

This one is worth your time anyway, for two reasons. First, its diagnosis of why IPv6 stalled is the most honest one I’ve seen written down in an IETF document. Second, it proposes something genuinely different — not a bigger address, but a managed network protocol , where DHCP, DNS, NTP, telemetry, authentication, and egress policy are one integrated system instead of six products that have never heard of each other. The centerpiece is a thing called a Zone Server , and the first question every operator should ask about it is the one this post tries to answer: what does that box have to be, and when does running it get expensive?

The IPv6 Paradox: Winning the Stat, Losing the War

Let’s be fair to IPv6 before we bury it. On March 28, 2026 — about two weeks before this draft was published — native IPv6 crossed 50% of traffic to Google for the first time: 50.10%, eighteen years after World IPv6 Day was supposed to kick things off. France sits around 86%, Germany and India in the mid-70s. The draft’s claim that IPv6 “carries a minority of global internet traffic” was, strictly speaking, out of date the day it was posted.

So why does every network engineer reading this still spend their day in RFC 1918 space?

Because the headline number measures the easy half of the problem. Mobile carriers and eyeball ISPs deployed IPv6 where it was one vendor decision applied to millions of subscribers. The other half — enterprise internal networks, the place where you and I actually work — barely moved. The campus is v4. The data center underlay is v4. The management network is definitely v4. And the transition model that was supposed to fix this made a promise nobody priced: dual-stack , which is not a migration but a commitment to run two networks, two addressing plans, two firewall policies, and two sets of failure modes, indefinitely, for zero operational reward.

That’s the draft’s real critique, and it’s the part that lands:

“The operational cost of the dual-stack transition model, combined with the absence of management improvement, proved commercially unacceptable.”

IPv6 gave us more addresses and nothing else. No better DHCP. No unified identity. No answer to the fact that DHCP, DNS, NTP, syslog, SNMP, and authentication were “specified independently over four decades, share no common identity model, no common authentication mechanism, and no common telemetry format” — that’s the draft again, and it’s just true. After 25 years, the incentive to endure dual-stack pain in exchange for only bigger addresses turned out to be approximately zero. The 50% milestone doesn’t refute that; it confirms it. We got half an internet upgraded — the half where one throat could be choked — and a permanent tax on everyone else.

What IPv8 Actually Proposes

The draft’s answer is a 64-bit address with a structure a network engineer can read at a glance:

r.r.r.r.n.n.n.n<br>└──┬───┘└──┬───┘<br>│ └── 32-bit host address — IPv4 semantics, unchanged<br>└────────── 32-bit ASN routing prefix<br>Your ASN is your prefix. AS64496’s address space is 64496.n.n.n.n — the draft defines an ASN dot notation so 64496.192.0.2.1 is a legal way to write an address. Every ASN holder gets 2³² hosts. A few consequences fall out of that one decision:

IPv4 is a proper subset, not a peer. An IPv8 address with r.r.r.r = 0.0.0.0 is an IPv4 address, processed by standard IPv4 rules. No dual stack, no flag day, no translation for legacy traffic — an IPv4-only device or application just keeps working, unmodified. This is the draft’s answer to the incentive problem that killed IPv6 adoption: you don’t migrate to IPv8, you get absorbed by it.

The global routing table becomes structurally bounded. One entry per ASN — about 175,000 today — instead of BGP4’s 900,000+ prefixes and counting. A /16 minimum injectable prefix rule kills deaggregation at AS boundaries, and every BGP8 advertisement must validate against a WHOIS8 route registry before installation. Bogon filtering stops being a manually maintained...