Just fyi IPv8 was written by LLM with full on hallucinated citations and references. It isn’t being taken seriously by anyone.
It didn’t even make sense. It relies on DNS for nat and the like. Deranged networking plans from the non-mind of an LLM.
I recommend taking the time to learn IPv6 properly. It’s actually quite elegant and brings back the peer to peer, endpoint to endpoint connection ability of the old internet.
I wouldn’t even say it was a good idea. Like the end to end NAT free internet is the ideal. IPv6 was built for that.
Even if IPv8 was not slop it would reenforce the idea of nat and hierarchy.
IPv6 allows for a democratized internet where anyone can choose to self host. And anyone can connect to anyone who is self hosting.
Because of this it’s a bit more complicated. But ideology it much better than IPv8. It brings us back what made the internet great in the 90s and 2000s, but at scale.
it would obviously involve code updates for compability, and I don’t pretend to know how it would work long term, but it makes the most sense… By prepending the zeros, you expand the number of networks dramatically.
I would guess that no matter what, everything gets an upgrade… But I think this might make it more seamless.
nitpick, but I would say “an RFC”, as there’s been a number of these over the years
you’ve gotten a couple responses so far, but I think the central issue is that “complexity” isn’t the problem with IPv6 (and one could certainly argue that IPv6 is actually simpler)–the problem is compatibility. This article lays out the issue very well, and also links to this article (which is a more specific look at the IPv8 proposal you refer to). Both point to the same conclusion, which is that fundamentally–on first principles–existing hardware does not know how to handle the upgrade, which will require some sort of dual-stacking, which is the issue IPv6 currently has. (Not its technical merit.)
in an ideal world, ipv6 would solve that problem…
😔
I saw the rfc for IPV8 recently… It makes so much more sense than ipv6…and is backward compatible with ipv4…
Basically they’re proposing prefacing 4 more octets into an IP address, so 172.16.5.1 would become 0.0.0.0.172.16.5.1
Any existing IPs would just assume the 0.0.0.0 in front of them…
Again…solves the problem on much the same way.
Just fyi IPv8 was written by LLM with full on hallucinated citations and references. It isn’t being taken seriously by anyone.
It didn’t even make sense. It relies on DNS for nat and the like. Deranged networking plans from the non-mind of an LLM.
I recommend taking the time to learn IPv6 properly. It’s actually quite elegant and brings back the peer to peer, endpoint to endpoint connection ability of the old internet.
Oi…well that sucks ass. A good idea, badly conceptualized I guess.
I wouldn’t even say it was a good idea. Like the end to end NAT free internet is the ideal. IPv6 was built for that.
Even if IPv8 was not slop it would reenforce the idea of nat and hierarchy.
IPv6 allows for a democratized internet where anyone can choose to self host. And anyone can connect to anyone who is self hosting.
Because of this it’s a bit more complicated. But ideology it much better than IPv8. It brings us back what made the internet great in the 90s and 2000s, but at scale.
That’s not how header backward compatibility works. IPv4 routers would discard the packet, not prepend zeroes.
it would obviously involve code updates for compability, and I don’t pretend to know how it would work long term, but it makes the most sense… By prepending the zeros, you expand the number of networks dramatically.
I would guess that no matter what, everything gets an upgrade… But I think this might make it more seamless.
Everyone seems to think that IPv6 is a complicated solution to a simple problem, it’s not. If you want to learn more, I managed to track down an article I read a while ago from one of the original IPng engineers. https://github.com/becarpenter/book6/blob/main/01. Introduction and Foreword/Why IPv6 is so complicated.md
nitpick, but I would say “an RFC”, as there’s been a number of these over the years
you’ve gotten a couple responses so far, but I think the central issue is that “complexity” isn’t the problem with IPv6 (and one could certainly argue that IPv6 is actually simpler)–the problem is compatibility. This article lays out the issue very well, and also links to this article (which is a more specific look at the IPv8 proposal you refer to). Both point to the same conclusion, which is that fundamentally–on first principles–existing hardware does not know how to handle the upgrade, which will require some sort of dual-stacking, which is the issue IPv6 currently has. (Not its technical merit.)
True, good point. AN RFC…
To be fair, I never got IPV6… was too confusing. I’ve always been able to rattle off IPv4 addresses in my sleep. IPV6 just wasn’t as natural.
deleted by creator