Just remember that IPv6 was introduced in 1995. At the time it probably seemed to be just fine.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
how would I get up to date with the latest IP tech stuff?
That's a pretty broad question, but if you want to get familiar with IPv6 I used this from Hurricane Electric years ago and enjoyed it; https://ipv6.he.net/certification/
I interpret this blogpost, which is excellent btw, not as 'IPv6 is a badly designed protocol' but rather as 'we haven't done a good job at evolving our network design as a hole'.
The author explains that the only real issue with IPv6 itself, is that roaming between wireless routers wasn't addressed (he calls it 'mobile IP') and that it could be properly fixed by using another identifier for sessions (uuid,port instead of sourceIP,sourcePORT,destIP,destPORT). Which would be doable with QUIC over UDP.
I remember trying to wrap my head around it close to 20 years ago back in tech school & while i know IPv6 is used out in the real world at the ISP/backbone level, every corporation I've ever worked for uses a class A IPv4 network internally (and maybe a few class D's too). every network I've ever used at home is class C IPv4.
IPv6 is some nebulous thing that exists but I've never needed to do anything with it...
The good thing is that for most people IPv6 happens and is used transparently. They don't notice whether and how their web-browser and OS uses IPv6 or IPv4.
IPv6 certainly introduced additional complexity to networking, network routing/decision-making, and administration. But it was/is a technical necessity.
Thank you for the link to this story. It connected together a few dots and made some things finally makes sense.
I've finally read this article that's been open in a mobile browser tab since it was posted. It's a great read, and I love all the twists and buts.
I wasn't expecting that QUIC would show up at the end as a possible saviour.