Internet Protocol Version 8 (IPv8)
What the draft proposes
An Internet-Draft posted to the IETF outlines a radical re-think of how networks are operated, secured and observed under the label "Internet Protocol Version 8" or IPv8. The draft describes a managed protocol suite in which every manageable element is authorized with OAuth2 JWT tokens served from a local cache, every required service is delivered in a single DHCP8 lease response, and every packet leaving a network is validated at egress against DNS8 and WHOIS8 records. Telemetry, authentication, name resolution, time sync, access control and translation are rolled into a single "Zone Server" platform — a one-stop shop for network state.
Bold claims and compatibility
The document claims IPv4 is a proper subset of IPv8: set the routing-prefix field to zero and you have an IPv4 address. No device changes, the draft asserts — "100% backward compatible" and "no flag day." It also proposes a striking address fix for exhaustion: each Autonomous System Number would receive 4,294,967,296 host addresses, and the global routing table would be structurally bounded at one entry per ASN. The draft carries the usual IETF caveats — it's a working document that expires in October 2026 — and is accompanied by companion specs covering things like eBGP8, IS-IS8, VRF and 8to4.
Why this matters — and where the controversy will be
The emotional core here is obvious: order out of chaos. Fragmentation of DHCP, DNS, NTP, logging and auth is a real operational headache. IPv8 promises to simplify life for operators, especially smaller ones. But centralizing so many functions into a managed Zone Server — and tying every element to OAuth tokens — raises immediate questions about privacy, single points of failure, vendor lock-in and who gets to run the "local cache" of truth. Is this salvation or a land-grab? The draft will need hard scrutiny from operators, vendors and privacy advocates before anyone treats it as a plan rather than a provocative blueprint.
Comments