4 ms·
IPv6 clients can be backward compatible, servers aren't. There shouldn't really be any rush to move servers into IPv6, it's end users' ISPs that should. Someho
by marcosdumay 5y ago
IPv6 clients can be backward compatible, servers aren't.
There shouldn't really be any rush to move servers into IPv6, it's end users' ISPs that should. Somehow things are happening completely backwards.
- rootusrootus 5y agoWhy put in the effort to give users IPv6 if there's nowhere for them to go? I recall that DJB made pretty much this argument in the distance past when he predicted IPv6 would fail.
- bombcar 5y agoWe basically needed ipv5 what would have been literally ipv4 but with 128 bit address-safe.
- welterde 5y agoHow exactly would have that solved anything? It would have exactly the same transition issues IPv6 has, since the main issue is that IPv4-only hosts cannot communicate with IPv6-only hosts. And there is no way around that - for any alternative proposal.
- bombcar 5y agoBy making the transition from ipv4 to ipv5 as painless as possible and more like the switch from 32 bit to 64 bit addressing in CPU architectures. At some point everything is 32 byte safe by default and then it’s just working. IPv4 to IPv6 is nowhere as simple, IPv6 brings tons of new baggage along with it.
- welterde 5y agoSwitch of CPU architecture is only a local problem. Switching the communication protocol is a local, remote and all the parts in between problem.
- commandersaki 5y agoDJB did have a proposal called AutoIPv6 which had both interoperability between v4 and v6: https://web.archive.org/web/20021017164820/http://cr.yp.to/proto/ipv6.html https://web.archive.org/web/20021017164820/http://cr.yp.to/p... . So in theory it's doable, but in practice I don't think the technologies used worked out. Ultimately tunnelling and anycast is the way to do interoperability.
- welterde 5y agoIt doesn't really solve the main issue here in that IPv4-only hosts (which are not aware of IPv6-anything, have no 6to4, AutoIPv6, anything) cannot talk to IPv6 hosts. For the inverse direction there is the DNS64+NAT64 combo which works fairly well.
- commandersaki 5y agoI don't really see the issue to worry about IPv4-only hosts that are not IPv6-aware. Virtually all TCP/IP stacks connected to the Internet have IPv6-capabilities.
- welterde 5y agoBut if IPv6 is disabled or are not using 6to4/6rd if no native connectivity is available are they really IPv6 capable?
- tsimionescu 5y ago> There shouldn't really be any rush to move servers into IPv6, it's end users' ISPs that should. The problem is people who run servers typically pay for their IPs, while people who run clients typically don't. So, as an end-user, I don't care if I have an IPv4 or an IPv6. As someone running a server, I might. As an ISP, I of course care if I need to acquire more IPv4's to cover all my clients. But, if all the world's servers are IPv4, I still need to provide IPv4 IPs to my clients, even if I run dual stack, so IPv6 is at best an extra cost, it doesn't save me any money. > IPv6 clients can be backward compatible, servers aren't. Not sure what you mean. How would an IPv4-only server send a reply packet to an IPv6-only client? There is CGNAT of course, but there we're again in dual-stack territory.
- marcosdumay 5y ago> But, if all the world's servers are IPv4, I still need to provide IPv4 IPs to my clients That's the incorrect part. You don't need it. You can translate 6 to 4, it's not exactly CGNAT but it appears exactly the same for the IPv4 servers. That will save you from getting an address to any of your users, only the translation servers need it.
- tsimionescu 5y agoCan you provide any docs or technology name? I still don't understand how the routing devices can tell which IPv6 to route the reply to if they receive two reply packets from the same server to the same IPv4 address. With CGNAT they would assign a TCP/UDP source port in the outgoing request, and use that to route based on destination port in the incoming reply, with all the disadvantages that brings. Can it be done without stateful connection tracking?
- marcosdumay 5y agoIt's literally called 6to4. And yes, it's stateful. https://en.wikipedia.org/wiki/6to4 https://en.wikipedia.org/wiki/6to4
- 5y ago