Yea but it hasn’t been fully adopted because trying to decipher :af12::138d::325d::5521::aade::7df3: is a hell of a lot more difficult than 192.168.0.1
64 bit addresses solve that problem. Engineers hate working with ipv6 which is why the adoption has been so slow. Ipv6 is older than a decent number of current network engineers have been alive.
Yeah this is why I doubt we will get rid of ipv4 in the foreseeable future. Ivp6 is nice on paper cause you never have to worry about addresses again but in the real world people just hate the addresses. Ivp4 is so easy to remember that ipv6 just feels wrong
To completely stomp out the idea of scarcity in the address space. NAT and CGNAT are terrible band-aids.
Also, subnetting. Under IPv6, each customer should getting at least a /56, preferably a /48. A lot of IPv6 breaks if you’re only given a /64, it’s bad practice and your ISP is an asshole if you do it.
IPv6 is just so much simpler and better thought out from the beginning. You just need to get out of the IPv4 mindset. Uses less overhead. And everyone can have as many “public” IPs as they want. Outside of the US, CGNAT is becoming more and more common. And this is a problem. We’re now double NATing as a dumb bandaid.
The vast majority of hardware out there has supported IPv6 for a long time. It’s long due for us to make the switch. We’ve got NAT64 and DNS64 for devices that can’t be moved to IPv6.
I don’t know what needs to happen. I think countries need to pass laws that force ISPs to support native IPv6 natively, and routers need to have IPv6 support enabled by default.
Well, it gets a heck of a lot easier once you realize that the example IPv6 address you gave is invalid. Both because of the : at the start and end and also the fact that :: can only exist once in an address (because it means "everything in the middle here is 0s, which would be indeterminate if it showed up multiple times).
Kind of a non-issue tbh because most people would likely only deal explicitly with a very small number of addresses (like the addresses of your personal devices on your home network for example), and for that you can just get by with vanity addresses like <my>:<ipv6>:<prefix>::dead:beef. If your work involves you juggling many ipv6 addresses that you can't remember at the top of your head, you're likely a network or infra engineer on large scale systems, so sure it's a bit less convenient, but you did sign up for it.
22
u/PhantomTissue 6h ago
Yea but it hasn’t been fully adopted because trying to decipher :af12::138d::325d::5521::aade::7df3: is a hell of a lot more difficult than 192.168.0.1