2 ms·
> Consider that the majority of the IP addresses in the network are individual subscriber IP addresses, not servers. So we can have a transitional situation in
by lmm 7y ago
> Consider that the majority of the IP addresses in the network are individual subscriber IP addresses, not servers. So we can have a transitional situation in which major service providers use the old 32 bit address space (so they are reachable by every client, 32 or 64 bit), while we put new subscribers into the 64 bit address space.
> The users who remain in the 32 bit space will increasingly find that they can't connect to some servers that are in the beyond-32 parts of 64 space, so they will have to upgrade their systems.
> Users in 32 space cannot do peer-to-peer with 64 users outside of that space, of course.
i.e. exactly the same situation that we currently have, only it would be less visible whether you've upgraded, and harder to debug when you had?
The hard part of deploying IPv6 isn't that the protocol is different (indeed the protocol is significantly simpler e.g. removing fragmentation). The hard part is that it's necessarily a new global routing table, that you necessarily can't use it between two hosts unless every router in between them supports it and has the routes set up. A more IPv4-like packet format would not change that at all.
- kazinator 7y agoYou might not have identified the really hard part. Which is this: reams of application code is hard-coded to the AF_INET address family, and its binary sockaddr_in structure, and related data types and functions. But that's a problem facing any proposed or actual IP facelift.