3 ms·
Everyone else is just rolling v6 out to meet the requirement of a client (typically government) contract. I'm holding out for ipv8, where someone sensibly just
by b112 5y ago
Everyone else is just rolling v6 out to meet the requirement of a client (typically government) contract.
I'm holding out for ipv8, where someone sensibly just slaps a 1. in front of ipv4 style addresses, which to stacks means route to old ipv4.
Then we have all we need with an extra octlet. We could even reserve a bunch for off-planet communicates, eg 100. = moon, 101 = mars, etc.
All existing tools, code, etc would see, route, etc 4 octlets to 1. addresses. Anything encountering 4 octlets would do the same. Old stuff could function forever, just with no ability to connect beyond 1.
No dual stack, no crazy issues, no 30 year old, broken attempt to re-engineer what didn't need to be done.
What were they thinking?! Yay! Let's eschew simplicity, and instead make a massive change as difficult to upgrade as possible!
- b112 5y agoWikipedia quote, 2050... "IPv6 was a failed standard, an attempt to.... " "replaced by more sensible IPv8..."
- GekkePrutser 5y agoOne thing to consider is that when IPv6 was invented, there wasn't nearly as big a userbase on IPv4 as there is now. At that time a clean-slate approach made more sense than it does now. But yes these days things are different. And not all its features imagined to be big have panned out that way (and to be fair, even IPv4 contains several features which are no longer in use).