Mastodawn

e. hashman 🇵🇸

You've heard of IPv6, but are you ready for IPv8? https://www.ietf.org/archive/id/draft-thain-ipv8-00.html

Internet Protocol Version 8 (IPv8)

Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification

e. hashman 🇵🇸Apr 30

IPv8 update: https://seclists.org/nanog/2026/Apr/96

nanog: IPv8 / BGP8 / CF

Thomas Wodarek Apr 30

Yep, that appeared in my inbox earlier and 🍿 stands ready
@ehashman

warthog9 Apr 30

@ehashman twitch

@ehashman Going in, I thought I might be. But I was not, in fact, ready.

@ehashman I WAS NOT READY

silverwizard Apr 16

uh, what? what?! @ehashman

✧✦Catherine✦✧Apr 16

Jonathan Yu Apr 16

@ehashman I kinda lost it at the JWTs but it kept spiraling

silverwizard Apr 16

@chrisvest @ehashman I'm so worried this is a serious proposal

Thomas Wodarek Apr 16

2^32 addresses is enough for any single ASN, right?

(I didn't get further than the abstract, too late to read further)

aismallard Apr 16

@ehashman what.

aismallard Apr 16

@ehashman this feels ipv6 defeatist. like it’s just impossible to move the internet off of ipv4

nickapos Apr 16

@ehashman It will be great for isps with a captive audience. 100% packet traceability 0% privacy.
What are we waiting for

Nelson Lopez Apr 16

@ehashman what in the fuck...?

@ehashman
Is this... for real?

Daveography 🇨🇦

Noooo, I still haven't figured out IPv6

@ehashman that’s just IPv6 with two extra cylinders so it goes faster 💁‍♀️

wake me when they release an RFC for IPv11… 🙃

@ehashman commercials for ipv8 will involve a disembodied hand slamming a router down onto the table followed by a deep voice saying "could have had ipv8"

Sebastian Cohnen Apr 16

@ehashman funny that IPv6 is only mentioned in two places, each with exactly the same two sentences!

synlogic4242 Apr 16

@ehashman cant tell if its serious or parody.

- uses 8 in the header's version field
- "no existing device requires modification"

Why isn't it dated April 1?

grindhold Apr 16

@ehashman "Devices communicate only with their designated service gateway. The service gateway communicates only with the designated cloud service. Lateral movement between devices or zones is architecturally prevented by the absence of any permitted route to any other destination." WTF

@grindhold
@ehashman
My thoughts exactly when I was reading the document. Had to double-check if it was published on April 1st.

@ehashman absolutely nuts, it's too late to be seeing this shit.

Ólafur Jens Sigurðsson Apr 16

@ehashman what ever happened to v7?

e. hashman 🇵🇸Apr 16

@ojs same thing that happened to IPv5 😢

@ehashman this is getting too much traction, it's just your standard net.krank shitpost

Conor Nash Apr 16

@ehashman I’ll raise you one https://en.wikipedia.org/wiki/IPv9_(China)

IPv9 (China) - Wikipedia

Marián Kyral Apr 16

@ehashman Soon will be replaced by IPvA

LambrosThe2st Apr 16

nice protocol

@ehashman Hmm, let's wait and see what @tschaefer has to say about it.

Thomas Schäfer Apr 16

@moellus @ehashman

For a fools day RFC it is just bad.

For a RFC to taken seriously it's to foolish.

Jan Sandbrink Apr 16

@ehashman WTF, is this a serious proposal?

I only made it to the introduction part until thinking that the language is more marketing than usually expected from an RFC.

RE: https://cloudisland.nz/@ehashman/116412184116807348

@ehashman ... jesus christ.

@ehashman uhh... accidental quote.. toot... reply? what a fascinating feature 👀

Simon Sapin Apr 16

@ehashman it’s… not published on april 1st?

Stuart Longland (VK4MSL)Apr 16

@ehashman Right… so we can expect this … when… 2044? 2054?

#IPv6 was first presented as a draft in 1998 and some places still don't have it.

Markus Probst Apr 16

@stuartl @ehashman Don't take this draft seriously. It seems like IPv4 with 64 bit ip addresses and full backwards compatibility for IPv4. No mention of IPv6 besides it having failed its job (not my opinion, just a summary).
I

Stuart Longland (VK4MSL)Apr 16

@0xIO32 @ehashman Yeah well, I half expected a publication date of 2026-04-01.

The thing is, it took about 4~5 years before IPv6 started appearing in operating systems.

It wasn't until the 10 year mark (2008) we started to see ISPs offering it.

World IPv6 day didn't happen until 13 years later (2011).

2026 (28 years later) and lots of ISPs and websites still live in 1984 worshipping RFC791 like it's new juice.

Dual-stack is the most practical spot where we are just now. The way things are going, this will be the case well into 2030 and beyond. So the idea of an IPv8, yeah… doesn't seem credible. It's taken this long to get any real traction on IPv6 and we're still barely half-way there.

Ben Hutchings Apr 16

@ehashman Why use v8 when the clearly superior v10 was proposed years ago: https://datatracker.ietf.org/doc/draft-omar-ipv10/10/

Internet Protocol version 10 (IPv10) Specification

This document specifies version 10 of the Internet Protocol (IPv10), sometimes referred to as IP Mixture (IPmix).

IETF Datatracker

@ehashman He lost me at the first JWT reference. Wha’?

@ehashman v8? Let's wait for v42, that will answer (and end) all questions!

Magnus Hedemark Apr 16

@Ganneff @ehashman only the question.

But you'll have to wait a few billion more years if you want to know what the question was that IPv42 answers.

David E. Smith Apr 16

@ehashman April 1 was a couple weeks ago

Philip Mallegol-Hansen Apr 16

@ehashman @bagder Given the timeline on IPv6 rollout, I feel like anyone who is alive today can safely ignore it as “future tech” 😂

@ehashman This reads like an April Fools joke

"Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route."

I can see why people think it is a joke.

How to slow down transit times.

I only got as far as this, not sure what a "WHOIS8 registered active route" is. Probably don't want to know.

Eeeuuuuggghh.

This is of course trash but a certain type of person will love it.

Anyway the funniest thing to me is the mixed decimal and hex notation, so I guess 30 is less than 1f. Also that notation is not defined anywhere, they just use it randomly.

@ehashman this is how I learned that you can post AI gibberish on the IETF website by calling it an Internet Draft