Can IPv8 Seamlessly Replace IPv4 and IPv6? A Deep Dive into the New Backward‑Compatible Protocol

IPv6 adoption remains below 50 % of global traffic (Google search data) and many networks still rely on CGNAT to mitigate IPv4 exhaustion. To address this bottleneck, an industry source submitted an IPv8 core protocol draft to the IETF.

Backward‑compatible address format

IPv8 defines a 64‑bit address expressed as r.r.r.r.n.n.n.n, where the first 32 bits ( r.r.r.r) are an Autonomous System Number (ASN) routing prefix and the last 32 bits ( n.n.n.n) identify the host. The draft states that IPv4 is a true subset of IPv8: when the ASN prefix is 0.0.0.0, the address is interpreted exactly as an IPv4 address. For example, 0.0.0.0.192.168.1.1 maps to 192.168.1.1. Consequently, any device that already implements IPv4 can communicate using IPv8 without firmware or software changes.

Address space and allocation

IPv8’s 64‑bit space yields a theoretical maximum of 2^64 ≈ 1.844 × 10⁹ unique addresses—far fewer than IPv6’s 2^128 but still orders of magnitude larger than the 4.3 × 10⁹ IPv4 addresses. The draft allocates roughly 4.29 × 10⁹ host addresses to each ASN, which is sufficient for large‑scale organizational needs and eliminates the need for CGNAT.

Routing scalability (BGP8)

The proposal introduces a BGP8 routing table bound to ASN units. By enforcing a /16 minimum prefix rule, BGP8 aims to curb routing‑table growth and reduce processing load on core routers.

Integrated security and management platform

IPv8 consolidates network services into a regional server platform that provides:

DHCP8 for address allocation

DNS8 for name resolution

NTP8 for time synchronization

OAuth2/JWT authentication

NetLog8 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, enforcing a zero‑trust model.

Draft status and reference

The IPv8 draft is a discussion document; it is not an IETF standard and the discussion period ends in October 2026. The full draft is available at https://datatracker.ietf.org/doc/draft-thain-ipv8/.

In summary, IPv8 attempts to solve IPv4 exhaustion and the slow IPv6 rollout by offering a drop‑in compatible protocol with a manageable 64‑bit address space, ASN‑bound routing, and an integrated security framework.