IPv8 proposal has recently attracted attention as a possible new approach to internet addressing. Some discussions have described it as \u201cIPv4, but better,\u201d while others have framed it as a potential alternative to IPv6.<\/p>\n\n\n\n
But before going any further, one point must be absolutely clear:<\/p>\n\n\n\n
IPv8 is not an official internet standard. It is not currently deployed as a global internet protocol. It is not an approved replacement for IPv6.<\/strong><\/p>\n\n\n\n At the time of writing, IPv8 proposal refers to an IETF Internet-Draft<\/strong> called draft-thain-ipv8-00, published on April 14, 2026<\/strong>, with an expiry date of October 16, 2026<\/strong>. The draft lists its intended status as \u201cStandards Track,\u201d but that does not mean it has already become a standard. It remains a proposal.\u00a0<\/p>\n\n\n\n The IETF explains that Internet-Drafts are working documents with no formal status. They can change, be removed, or never progress into an official RFC or internet standard. <\/p>\n\n\n\n That distinction matters.IPv8 should not be presented as the next official version of the internet. It is better understood as a proposal<\/strong> that highlights a much bigger issue: even as IPv6 adoption grows, IPv4 compatibility remains one of the strongest forces shaping real-world internet infrastructure.<\/p>\n\n\n The IPv8 proposal describes a managed network protocol suite built around a 64-bit addressing model.<\/p>\n\n\n\n \u2022<\/strong> According to the draft, an IPv8 address would use this format: r.r.r.r.n.n.n.n<\/p>\n\n\n\n \u2022<\/strong> The first 32 bits, represented as r.r.r.r, would act as a routing prefix. The second 32 bits, represented as n.n.n.n, would preserve an IPv4-style host address format.\u00a0<\/p>\n\n\n\n The proposal\u2019s most important idea is backward compatibility. The draft claims that IPv4 would become a subset of IPv8. In this model, an address where the routing prefix is set to zero would represent a standard IPv4 address. <\/p>\n\n\n\n \u2022<\/strong> In simple terms, the proposal tries to expand address capacity while keeping the familiar IPv4 structure.<\/p>\n\n\n\n \u2022<\/strong> That is why IPv8 has gained attention. It does not ask the internet to abandon the IPv4 model completely. Instead, it suggests a way to extend it.<\/p>\n\n\n\n \u2022<\/strong> The fact that a draft claims compatibility does not mean the internet has adopted it, vendors support it, routers implement it, or network operators are ready to deploy it.<\/p>\n\n\n\n IPv8 is interesting because it reflects a frustration many network operators and infrastructure teams already understand.<\/p>\n\n\n\n \u2022<\/strong> IPv6 was created to solve the IPv4 address exhaustion problem. Technically, IPv6 provides a vastly larger address space and has become a real part of the modern internet.<\/p>\n\n\n\n \u2022<\/strong> Google continuously measures IPv6 availability among users accessing Google services, and its public statistics show that IPv6 adoption is a major part of today\u2019s internet traffic. In March 2026, Internet Society reported that Google\u2019s IPv6 access measurement exceeded 50% for the first time, reaching 50.10% on March 28, 2026. Internet Society also noted that IPv6 deployment levels vary significantly by country and measurement source.\u00a0<\/p>\n\n\n\n \u2022<\/strong> So IPv6 has not \u201cfailed.\u201d<\/p>\n\n\n\n \u2022<\/strong> But IPv6 has also not made IPv4 disappear.<\/p>\n\n\n\n \u2022<\/strong> The internet still operates in a hybrid state. Many organizations continue to rely on IPv4, IPv6, NAT, CGNAT, dual-stack systems, translation layers, legacy applications, cloud networking rules, firewall policies, access lists, reputation databases, and geolocation systems at the same time.<\/p>\n\n\n\n That complexity is the real reason IPv8 has become a talking point. The proposal is not important because it is guaranteed to become a standard. It is important because it shows that IPv4 compatibility still has strategic value.<\/p>\n\n\n\n IPv4 scarcity is not theoretical.<\/p>\n\n\n\n \u2022<\/strong> In February 2011, the Number Resource Organization announced that the central pool of available IPv4 address space had been fully depleted. That meant there were no longer IPv4 addresses available for allocation from IANA to the five Regional Internet Registries.\u00a0<\/p>\n\n\n\n \u2022<\/strong> In November 2019, RIPE NCC announced that it had made its final IPv4 allocation from its available pool. RIPE NCC also noted that recovered addresses would be allocated through a waiting list and that small recovered amounts would not come close to meeting the millions of addresses needed by networks in its service region.\u00a0<\/p>\n\n\n\n \u2022<\/strong> IPv4 remains valuable because it is widely compatible. It works with legacy systems, security tools, allowlists, geolocation databases, hosting environments, VPN services, proxy networks, enterprise firewalls, compliance workflows, and business applications that were built around IPv4 over many years.<\/p>\n\n\n\n That is why IPv4 leasing remains relevant even as IPv6 adoption grows.<\/p>\n\n\n\n Companies do not lease IPv4 addresses because they are ignoring the future. They lease IPv4 because their infrastructure still needs reliable IPv4 reachability today.<\/p>\n\n\n\n The IPv8 proposal is not just about adding more addresses. It also describes a broader managed network model involving authentication, telemetry, name resolution, access control, translation, and routing validation. The draft describes concepts such as DHCP8, DNS8, WHOIS8, NetLog8, OAuth-based authorization, and a Zone Server platform. <\/p>\n\n\n\n Whether those ideas are practical at global scale is a separate question.<\/p>\n\n\n\n To become reality, any new internet protocol would need broad support from standards bodies, router vendors, operating systems, cloud providers, ISPs, enterprises, security tools, and application developers. That is an enormous adoption challenge.<\/p>\n\n\n\n But the proposal\u2019s existence is still meaningful. It shows that the internet infrastructure community continues to look for ways to balance three competing needs:<\/p>\n\n\n\n \u2022<\/strong> More address capacity\u00a0<\/p>\n\n\n\n \u2022<\/strong> Better security and manageability\u00a0<\/p>\n\n\n\n \u2022<\/strong> Compatibility with existing IPv4-based systems\u00a0<\/p>\n\n\n\n IPv6 solves the address capacity problem. But for many businesses, address space is not the only issue. They also care about operational familiarity, risk reduction, tooling compatibility, routing behavior, and whether their infrastructure works with customers, partners, platforms, and legacy systems.<\/p>\n\n\n\n That is why IPv4 remains commercially important.<\/p>\n\n\n\n For companies that rely on web scraping, proxy networks, hosting, VPN services, telecom infrastructure, SaaS platforms, cybersecurity testing, data collection, and data-for-AI workflows, IPv4 is still a practical requirement.<\/p>\n\n\n\n IPv6 may support long-term modernization, but many real-world systems still depend on IPv4-based routing, access control, IP reputation, geolocation, monitoring, and compatibility.<\/p>\n\n\n\n This is where IPv4 leasing becomes important.<\/p>\n\n\n\n Buying IPv4 address blocks outright can be expensive and operationally heavy. Leasing gives companies a more flexible way to access IPv4 resources without committing to full ownership. This can be especially useful for businesses that need to scale infrastructure, test markets, support distributed systems, or expand IP capacity for specific operational needs.<\/p>\n\n\n\n In this context, IPv8 is not something businesses should plan around as an active deployment path today. It is only a proposal.<\/p>\n\n\n\n Instead, IPv8 should be seen as a reminder of why IPv4-compatible infrastructure still matters.<\/p>\n\n\n\n Read more: <\/strong>IPv4 Leasing for Proxy Infrastructure Matters in 2026<\/strong><\/a><\/p>\n\n\n\n At PubConcierge, we focus on the practical side of IP infrastructure: helping businesses access IPv4 resources through flexible leasing solutions.<\/p>\n\n\n\n Our perspective is shaped by a simple market reality. IPv6 adoption is growing, but many companies still need IPv4 for day-to-day operations.<\/p>\n\n\n\n For these businesses, the question is not only what the internet may look like in the future. The more immediate question is how to maintain reliable, compatible, and scalable infrastructure now.<\/p>\n\n\n\n IPv8 may remain only a proposal. IPv6 may continue expanding. But IPv4 compatibility is still a business requirement for many operators.<\/p>\n\n\n\n If your company needs IPv4 resources for scraping, proxy networks, hosting, VPN services, telecom operations, SaaS platforms, or data-for-AI workflows, PubConcierge<\/strong> can help you explore flexible IPv4 leasing options.<\/p>\n\n\n\n Talk to PubConcierge about IPv4 leasing options for your infrastructure.<\/strong><\/p>\n\n\n\n BOOK a 30-min Strategy Session!\n<\/strong><\/a><\/p>\n\n\n\n <\/p>\n\n\n\n Q1: Is IPv8 an official internet standard?<\/strong><\/p>\n\n\n\n No. IPv8 is not an official internet standard. At the time of writing, IPv8 refers to an IETF Internet-Draft called draft-thain-ipv8-00. Internet-Drafts are working documents with no formal status and may change or be removed. <\/p>\n\n\n\n Q2: Is IPv8 replacing IPv6?<\/strong><\/p>\n\n\n\n No. IPv8 is not replacing IPv6. IPv6 is the current standardized successor to IPv4, while IPv8 is only a proposal.<\/p>\n\n\n\n Q3: Is IPv8 deployed on the internet today?<\/strong><\/p>\n\n\n\n No. IPv8 should not be described as a deployed global internet protocol. It is a draft proposal, not an adopted standard.<\/p>\n\n\n\n Q4: Why is IPv8 being discussed?<\/strong><\/p>\n\n\n\n IPv8 is being discussed because it proposes a model that keeps IPv4 compatibility while expanding address capacity. The discussion reflects ongoing industry interest in simpler, more compatible approaches to internet addressing.<\/p>\n\n\n\n Q5: Does IPv8 prove that IPv6 failed?<\/strong><\/p>\n\n\n\n No. IPv6 adoption continues to grow. Internet Society reported that Google\u2019s IPv6 access measurement exceeded 50% for the first time on March 28, 2026, while also noting that deployment varies widely by country and data source. <\/p>\n\n\n\n Q6: What does IPv8 mean for IPv4 leasing?<\/strong><\/p>\n\n\n\n IPv8 does not change the IPv4 leasing market today. Since it is only a proposal, businesses should not treat it as an active replacement strategy. However, the proposal reinforces a key point: IPv4 compatibility remains important for many real-world infrastructure use cases.<\/p>\n\n\n\n Q7: Why do companies still need IPv4 if IPv6 exists?<\/strong><\/p>\n\n\n\n Many businesses still depend on IPv4 because their systems, customers, vendors, security tools, geolocation databases, routing practices, and operational workflows are built around IPv4. IPv6 adoption is growing, but the internet remains hybrid.<\/p>\n\n\n\n Q8: Is IPv4 leasing a long-term strategy?<\/strong><\/p>\n\n\n\n IPv4 leasing can be a practical strategy for companies that need flexible access to IPv4 resources without buying address blocks outright. It should be evaluated alongside IPv6 planning, compliance requirements, technical architecture, and business goals.<\/p>\n\n\n\n About this analysis<\/strong><\/p>\n\n\n\n This article was prepared by the PubConcierge team, which specializes in IPv4 leasing and IP infrastructure strategy for companies operating in data collection, proxy infrastructure, hosting, VPN, telecom, SaaS, and AI data workflows.<\/p>\n\n\n\n Our perspective is based on practical experience helping businesses access and manage IPv4 resources in a market where IPv6 adoption is increasing, but IPv4 compatibility remains essential for many commercial use cases.<\/p>\n\n\n\n Reviewed for: technical accuracy, infrastructure relevance, IPv4 leasing context, and commercial applicability.<\/p>\n\n\n\n Sources and methodology<\/strong><\/p>\n\n\n\n This article is based on publicly available technical and industry sources, including:<\/p>\n\n\n\n \u2022<\/strong> The IETF Internet-Draft for IPv8, published as draft-thain-ipv8-00<\/a><\/p>\n\n\n\n \u2022<\/strong> IETF guidance on the status of Internet-Drafts<\/a><\/p>\n\n\n\n \u2022<\/strong> IANA IP version number assignments<\/a><\/p>\n\n\n\n \u2022 Google IPv6 adoption statistics<\/a>\u00a0<\/p>\n\n\n\n \u2022 Internet Society IPv6 adoption analysis<\/a><\/p>\n\n\n\n \u2022 Number Resource Organization IPv4 exhaustion announcement<\/a><\/p>\n\n\n\n \u2022 RIPE NCC IPv4 exhaustion update<\/a> Important note: Because IPv8 is currently only a proposal, this article intentionally avoids presenting it as an adopted protocol, official standard, or guaranteed replacement for IPv6.<\/strong><\/p>\n\n\n\n Legal and technical disclaimer<\/strong><\/p>\n\n\n\n This article is provided for informational and educational purposes only. It does not constitute legal, regulatory, technical, financial, or procurement advice.<\/em><\/p>\n\n\n\n Internet protocol standards, IP address policy, routing practices, and IPv4 leasing requirements may vary by jurisdiction, registry, network operator, and business use case. Readers should consult qualified legal, compliance, technical, and network operations professionals before making decisions related to IP leasing, routing, address transfers, infrastructure deployment, or regulatory obligations.<\/em><\/p>\n\n\n\n References to IPv8, IPv6, IPv4, IETF Internet-Drafts, IANA registries, or Regional Internet Registry policies are based on publicly available information at the time of writing. IPv8 is discussed here only as a proposal and should not be interpreted as an adopted internet standard.<\/em><\/p>\n\n\n\n PubConcierge does not guarantee that any specific protocol proposal, including IPv8, will be adopted, standardized, implemented, or supported by network operators, vendors, or internet governance bodies.<\/em><\/p>\n\n\n\n Stay up to date on growth infrastructure, email best practices, and startup scaling strategies by following PubConcierge on LinkedIn<\/strong><\/a>.<\/strong><\/em><\/p>\n","protected":false},"excerpt":{"rendered":" IPv8 proposal has recently attracted attention as a possible new approach to internet addressing. Some discussions have described it as \u201cIPv4, but better,\u201d while others have framed it as a potential alternative to IPv6. But before going any further, one point must be absolutely clear: IPv8 is not an official internet standard. It is not… Continue reading IPv8 Proposal Explained: What It Reveals About IPv4 Compatibility<\/span><\/a><\/p>\n","protected":false},"author":7,"featured_media":1064,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ub_ctt_via":"","footnotes":""},"categories":[5,39,38],"tags":[64],"class_list":["post-1063","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ip-leasing","category-ipv4-ipv6","category-proxy","tag-ip-leasing","entry"],"featured_image_src":"https:\/\/www.pubconcierge.com\/blog\/wp-content\/uploads\/2026\/04\/PUBCONCIERGE-IPv8-Proposal-Explained-What-It-Reveals-About-IPv4-Compatibility.jpg","author_info":{"display_name":"Raluca Sima","author_link":"https:\/\/www.pubconcierge.com\/blog\/author\/raluca-sima\/"},"authors":[],"_links":{"self":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/1063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/comments?post=1063"}],"version-history":[{"count":3,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/1063\/revisions"}],"predecessor-version":[{"id":1068,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/1063\/revisions\/1068"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/media\/1064"}],"wp:attachment":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/media?parent=1063"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/categories?post=1063"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/tags?post=1063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What is the IPv8 proposal?<\/strong><\/h2>\n\n\n\n
Why IPv8 is attracting attention<\/strong><\/h2>\n\n\n\n
IPv4 exhaustion is real, but IPv4 demand has not disappeared<\/strong><\/h2>\n\n\n\n
What IPv8 proposal says about real-world infrastructure<\/strong><\/h2>\n\n\n\n
Why this matters for IPv4 leasing<\/strong><\/h2>\n\n\n\n
PubConcierge perspective: practical IPv4 access for today\u2019s infrastructure<\/strong><\/h2>\n\n\n\n
FAQ<\/strong><\/h2>\n\n\n\n
Last updated: April 2026.<\/p>\n\n\n\n
<\/p>\n\n\n\n