Tell HN: IPv6-only still pretty much unusable

Re:Tell HN: IPv6-only still pretty much unusable by Dagger2 on Wednesday December 07, 2022 @06:04PM (#33901666)

The majority of the problems seem to come from the fact that v6 addresses are longer than v4 ones. That's why we need socket(AF_INET6)s and AAAA records and a DNS API that supports multiple address families and dual stack and new firewalling and updates to all protocols that embed v4 addresses.

You're going to have the exact same problems with any protocol that has addresses longer than v4's.

[ Parent | on HN ]

Re:Tell HN: IPv6-only still pretty much unusable by p_l on Wednesday December 07, 2022 @07:33PM (#33902483)

BSD Sockets ensured that we have problems using anything other than what the software was originally written for, unless it's a program recent enough to use the one bit of API that got back ported from OSI-oriented Ed networks, the getaddressinfo() call.

Otherwise there's a ton of low level IPv4 details leaking all around the basic idea of connecting from one service to another.

[ Parent | on HN ]

Re:Tell HN: IPv6-only still pretty much unusable by anyfoo on Wednesday December 07, 2022 @08:42PM (#33903009)

I find that hard to believe. That may be true for endpoints, but I'm talking about the network infrastructure in between. There, I believe that the vast differences in the protocols on higher level (autoconfiguration, link-local addresses, temporary addresses, Neighbor Discovery as part of ICMP6 instead of ARP, ICMP6 itself, and so on and so forth) are much, much more work to implement than dealing with new DNS records and APIs, and the new struct sockaddr variants.

My point is exactly that I have a strong suspicion that the longer addresses are not the problem for slow adoption, the different network protocols and semantics are.

[ Parent | on HN ]