7 ms·
IPv6 will never make it. Maybe IPv8 [0], which IPv6 should have actually looked like: > 1.1.1.1.1.1.1.1 [0] https://www.ietf.org/archive/id/draft-thain-ipv8-0
by purerandomness 5mo ago
IPv6 will never make it. Maybe IPv8 [0], which IPv6 should have actually looked like:
> 1.1.1.1.1.1.1.1
[0] https://www.ietf.org/archive/id/draft-thain-ipv8-00.html https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
- direwolf20 5mo agoWhy do people keep proposing alternatives to IPv6 that are no easier than IPv6 but still require the whole world to start the deployment over from 0%?
- josh3736 5mo agoFor observers, this draft was posted to HN earlier but quickly flagged and removed because the linked "IPv8" draft is absolute bunk. See the removed thread for details: https://news.ycombinator.com/item?id=47788857 https://news.ycombinator.com/item?id=47788857
- tialaramex 5mo agoHaving read that thread, I guess one of the small upsides of the world I live in is that "FIFA Peace Prize" is now available as a joke award reference. FIFA really hit it out of the park there in a way that even their normal legendary levels of corruption couldn't imagine. Edited: In hindsight I notice that "hit it out of the park" is the wrong sport metaphor for FIFA, but I stand by it anyway.
- embedding-shape 5mo ago> Edited: In hindsight I notice that "hit it out of the park" is the wrong sport metaphor for FIFA, but I stand by it anyway. For future reference, you can use: "knocked it into the top corner", "put it in the back of the net" or "smashed it past the keeper". Not a native football-talker, but hang out too much with a few.
- tialaramex 5mo ago"Back of the net" doesn't feel the same to me even though (I learn after reading far too much about a sport I do not play) "Out of the park" is basically the same thing. In my mind "out of the park" had meant the ball leaves the actual stadium but in fact (I read) "the park" in this context is actually the field of play and so "out of the park" represents in fact the vast majority of home runs and not the over-achievement I had imagined. So TIL but thanks for the suggestions.
- embedding-shape 5mo agoTrue, "back of the net" is more "someone kicked the ball really hard and it hit the back of the net really hard" instead of "the ball came across the goal line" which can be very different, so in my mind that's as close to "out of the park" as you can get in soccer :)
- po1nt 5mo agoNice idea. Always wondered why IPv6 went so ambitious with the addressing
- Ekaros 5mo agoMight as well go big. 24 extra bytes per packet is not that big deal. And having that much extra space means you can screw up design multiple times and still be able to reuse lot of infra. Also getting rid of idea that you are even trying to manually manage the address space eases many things.
- po1nt 5mo agoBut it's not human readable anymore, nor backwards compatible. The expectation was that the industry is reasonable, but it proved to be as hard as it would be to push breaking email v2 implementation.
- Dagger2 5mo agoIf you think v6 isn't backwards compatible then literally anything bigger than 32 bits will never count as backwards compatible for you. The whole point of making the address space bigger is to make it bigger, so what do you expect to achieve by complaining that the result is incompatible? As a human, I've found that e.g. "fd00::53" is perfectly readable to me, and most of the time you're interacting with strings like "news.ycombinator.com" anyway which is identical to how it works in v4, so I'm not sure how far I'd agree with that part either.
- ButlerianJihad 5mo agoOne of the craziest aspects of IPv6 implementation is the reverse DNS lookups. IPv6 uses ip6.arpa and segments each little nybble into a subdomain! https://en.wikipedia.org/wiki/Reverse_DNS_lookup#IPv6_reverse_resolution https://en.wikipedia.org/wiki/Reverse_DNS_lookup#IPv6_revers... This means there are always 32 octets to a reverse-IPv6 address, and there are no shortcuts or macros to overcome this! That means if you wish to assign a singular name that maps from a legitimate /64 Network ID, you must populate 64 bits worth of octets in a zone with this data. It is an absurd non-solution. This never should've been allowed to happen, but it will basically mean that ISPs abandon reverse DNS entirely when they migrate to IPv6 implementations.