3 ms·
> 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
by 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
- tsimionescu 5y ago6to4 doesn't allow an IPv6 host to send a packet to an IPv4 address. It only allows IPv6 packets addressed to IPv6 hosts to be routed by IPv4 routers. An IPv4-only TCP/UDP server receiving such a packet would not know what to do with it, as the payload of the IPv4 packet is an IPv6 packet, not a TCP/UDP packet. On the other hand, 6to4 is stateless, so it has that going for it.
- detobate 5y agoThere are IPv4aaS methods that use IPv6 to deliver IPv4 connectivity along with IPv4 address sharing. MAP-T for example, does this statelessly: https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-comparison#section-2.5 https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-trans...