IPv8 Draft Promises Full IPv4 Compatibility – What It Means for the Internet

Background

IPv6 adoption has been slow; the protocol was first discussed in 1992, began standardization in 1996, and was released in December 1998. Current IPv6 market coverage is just over 50 % (based on Google search data), and many networks still rely on CGNAT to mitigate IPv4 address exhaustion.

IPv8 Address Model

The IPv8 core protocol draft defines a 64‑bit address space formatted as r.r.r.r.n.n.n.n. The first four octets ( r.r.r.r) constitute a 32‑bit ASN routing prefix; the last four octets ( n.n.n.n) form a 32‑bit host identifier. When the ASN prefix is 0.0.0.0, the address is interpreted exactly like a standard IPv4 address (e.g., 0.0.0.0.192.168.1.1 maps to 192.168.1.1), making IPv8 100 % backward compatible with IPv4.

Address Space

The 64‑bit space yields a theoretical maximum of 2^64 ≈ 1.844 × 10^11 unique addresses. Each autonomous system (ASN) would receive roughly 2^32 ≈ 4.29 × 10^9 host addresses, which the draft claims is sufficient for large‑scale deployments and eliminates the need for CGNAT.

Routing Table Design

IPv8 introduces a BGP8 routing table bound to ASN units. Combined with a /16 minimum prefix rule, this design is intended to suppress routing‑table growth and reduce processing load on core routers.

Security and Management Platform

A unified regional server platform integrates the following services:

DHCP8 for address allocation

DNS8 for name resolution

NTP8 for time synchronization

OAuth2 JWT for authentication

NetLog8 for telemetry

WHOIS8 for route verification

All outbound packets must pass DNS8 resolution and WHOIS8 registration, and devices must present a valid authentication token before communication, establishing a default‑untrusted model.

Discussion Timeline

The draft is open for discussion until October 2026. Full draft text: https://datatracker.ietf.org/doc/draft-thain-ipv8/