IPv8: A New Candidate for Replacing IPv4 and IPv6 and Its Role in the Future Internet
IPv8 is a proposed new internet protocol introduced in April 2026 by developer Jamie Tain. Its main innovation is 64-bit addressing (2⁶⁴ ≈ 18 quintillion addresses) while being fully backward compatible with IPv4 (an IPv8 address with a zero routing prefix behaves exactly like a regular IPv4 address). Unlike IPv6, which requires dual-stack deployment and complex migration, IPv8 needs no changes to existing devices or applications. IPv8 also introduces a unified management platform (Zone Server) combining DHCP, DNS, NTP, and authentication, along with built-in security based on OAuth2 tokens. Currently, this is an individual Internet-Draft with no official status, and its future remains uncertain. Another unrelated technology also named IPv8 exists – a decentralized peer-to-peer overlay network from the Tribler project, which has nothing to do with the IETF protocol.
IP address basics: If you need to refresh your memory on how “classic” IP addresses work, what IPv4 is, and why we are running out of addresses, we recommend reading our article: IP Address: Everything You Need to Know.
1. First things first: what is an IP address and how does the internet work under the hood?
To understand why a new protocol like IPv8 is being discussed, it helps to know the basics. An IP address (Internet Protocol address) is a unique numeric identifier for any device connected to a network. Think of it like a postal address: you write the street and house number on an envelope so the letter reaches the right destination. On the internet, the IP address tells routers where to send data packets.
Today, the most widely used protocol is IPv4. Its address is 32 bits long – it looks like four numbers from 0 to 255 separated by dots (e.g., 93.184.216.34). There are only about 4.3 billion such addresses, and they have all been allocated. That is why IPv6 (128 bits, enough addresses for every grain of sand on Earth) was created, but adoption has been slow because migration is complex and costly.
What are backbone networks? The internet is a network of networks. Different local networks are connected through powerful communication links owned by major providers – these are called backbone networks. Data travels across continents and cities through these backbones. Routers (specialized computers) look at the destination IP address and decide which direction to forward the packet. That process is routing. Routing tables store information about which backbone paths lead to which blocks of addresses.
2. Prelude: why did IPv8 emerge?
In April 2026, a new Internet-Draft appeared in the IETF (Internet Engineering Task Force) titled “Internet Protocol Version 8 (IPv8)”. The author is Jamie Tain from One Limited. He essentially proposed a brand-new IP protocol that could replace the aging IPv4 and perhaps leapfrog IPv6. The main problem with IPv4 is address exhaustion. Experts have long expected worldwide IPv6 deployment, but that has not fully happened. Today, about 48.22% of Google’s traffic runs over IPv6, and globally the figure is around 43%. Many ISPs have chosen to keep IPv4 and use CGNAT, despite its drawbacks, because the transition to IPv6 has been too expensive and complex. IPv8, according to its author, aims to solve the address shortage without a painful migration – with full compatibility for old devices, but also a radical rethinking of network management.
3. What does an IPv8 address look like?
Visually, an IPv8 address resembles two IPv4 addresses concatenated. Where an IPv4 address is 93.184.216.34, the new format would look like “0.0.251.240.93.184.216.34”. The first half (0.0.251.240) is the routing prefix (network/operator identifier), and the second half is the device’s local address inside that network. If the prefix is zero (0.0.0.0.192.168.1.10), that address is effectively a normal IPv4 address and is routed according to legacy rules.
Technical details of the 64-bit address (as per the IETF draft):
- IPv8 address space: 2⁶⁴ ≈ 18,446,744,073,709,551,616 addresses (about 18 quintillion).
- Each Autonomous System (ASN) owner receives 2³² addresses (4,294,967,296) for its hosts.
- The global BGP8 routing table would contain only one entry per ASN, with a minimum prefix length of /16, drastically reducing its size.
- The IPv4 address space is a true proper subset of IPv8, giving 100% backward compatibility.
4. Backward compatibility: “seamless” without a transition period
The most significant difference between IPv8 and IPv6 is complete backward compatibility. Every existing device, application, or network using IPv4 would continue to work without any change. No dual-stack deployment, no tunnels, no “X-day” when something breaks. Because an IPv8 address with a zero routing prefix becomes a normal IPv4 address, all legacy packets would be processed as before. This is a fundamental departure from IPv6, which requires parallel support for both protocols and inevitably creates transition pain.
5. What else does IPv8 offer? Unified network management (Zone Server)
The author of IPv8 did not stop at expanding the address space. He also tried to solve another headache for network administrators – fragmented management. Today, DHCP, DNS, authentication systems, monitoring, and time synchronisation protocols each live their own lives. They are configured separately, log errors differently, and have different security models.
In IPv8, all these services are unified into a single platform – the Zone Server. A device connects to the network and receives in one DHCP8 request:
- IP address
- DNS server (DNS8)
- Time server (NTP8)
- Access tokens (OAuth2 JWT) for authentication
- Access control rules (ACL8)
Additionally, network telemetry is collected by the NetLog8 protocol, and routes are verified through WHOIS8 (every outgoing packet must pass validation in DNS8 and be registered in WHOIS8 – otherwise it is blocked). The network thus becomes more manageable and more secure compared to today’s “zoo” of disjointed protocols.
6. Security as a built-in feature, not an add-on
In IPv4 and IPv6, security is something added on top (IPsec, TLS). IPv8 proposes security by design. Every network element is authorised through OAuth2 JWT tokens. The document introduces the Zone Server concept – a unified platform combining DHCP, DNS, NTP, monitoring, authentication, and access control. Another important innovation for network resilience is the Cost Factor (CF) metric: routers choose the best path considering not only hop count but also latency, loss, and even geographic distance. Distributed control also helps fight DDoS attacks and route spoofing more effectively.
7. Comparison: IPv4, IPv6, and IPv8
| Feature | IPv4 | IPv6 | IPv8 |
|---|---|---|---|
| Address size | 32 bits | 128 bits | 64 bits |
| Number of addresses | ~4.3 × 10⁹ | ~3.4 × 10³⁸ | ~1.8 × 10¹⁹ |
| Backward compatibility with IPv4 | — | No (dual stack needed) | Yes (100% subset) |
| Migration requirement | — | Long dual-stack period, tunnels | None (seamless integration) |
| Network management | Separate services (DHCP, DNS) | Separate, though DHCPv6 options exist | Unified Zone Server (DHCP8, DNS8, WHOIS8, ACL8) |
| Built-in security | No | IPsec optional | Yes (OAuth2 JWT, tokenisation, L3 authentication) |
8. Namesakes and historical background: IPv8 is older than it seems
Using the number “8” for a new protocol may seem like a jump, but there are historical reasons. IPv5 existed as an experimental “Internet Stream Protocol” and never saw mass deployment. Interestingly, version 8 was once assigned (in the late 1990s) to the PIP (P Internet Protocol), which never took off. Version 7 was reserved for TUBA (“TCP/UDP over Bigger Addresses”). So this new initiative does not so much “jump over” versions as revive a forgotten name.
However, there is also a completely separate technology named IPv8 – a peer-to-peer overlay network from the Tribler project (py-ipv8). It appeared much earlier (~2010) and has nothing to do with an IETF network protocol. That IPv8 solves a different problem: it allows applications to communicate directly, abstracting away IP addresses, and manages trust relationships between nodes. It is an application-layer P2P library, not a candidate for a new internet protocol.
9. Community reaction and adoption prospects
Despite the ambitious name, the document is not an IETF standard. It is merely an individual Internet-Draft that expires in six months (expiration date 16 October 2026) and currently has no status or working group support. Discussion will continue until October 2026, but real chances for approval are slim. Experts call IPv8 “too good to be true”, and some suspect the document was partially AI-generated.
What supporters say: — IPv8 solves the biggest pain point – migration without downtime or lost investment. — Centralised Zone Server management simplifies configuration and monitoring. — Built-in authentication could drastically reduce address spoofing attacks.
What critics say: — IPv8 introduces a single point of management (Zone Server), contradicting the decentralised nature of the internet. — The IPv8 stack (BGP8, OSPF8, SNMPv8, ARP8) would require replacing too many currently working components, which is practically impossible. — IPv6, despite slow adoption, already works on nearly half the network (~43% of global traffic) and has strong vendor support; rewriting everything from scratch is not worthwhile.
The author himself does not claim that IPv8 should immediately replace IPv6; rather, he invites discussion about the future of internet architecture. Most likely, this initiative will remain an interesting concept, but it will nonetheless raise important questions about how IP protocols should evolve.
10. Conclusion: The end of IPv4 or a new turn?
IPv8 is an ambitious and beautiful project on paper. It offers a simple way out of the address crisis without breaking existing infrastructure, while modernising network security and management. However, its future is very uncertain. Real deployment would require rewriting significant parts of the internet stack, convincing equipment manufacturers and ISPs, and overcoming the inertia that has prevented mass IPv6 adoption for over 20 years. The expiring individual draft is an invitation to a conversation, not a ready-to-use standard. Yet the very fact of its appearance on the IETF platform and the lively debate it has sparked show that the industry is still searching for the best path forward. Perhaps some of IPv8’s ideas (such as embedding authentication into the protocol) will eventually make their way into IPv6 or an entirely new architecture. For now, the internet will continue to run on a mix of IPv4, CGNAT, and slowly growing IPv6.
