4 ms·
> IPv4 but with 8 octets then adoption would have been a lot faster. > You can’t upgrade to IPv6 you have to port your code to IPv6. There is no physical way t
by Plasmoid 5y ago
> IPv4 but with 8 octets then adoption would have been a lot faster.
> You can’t upgrade to IPv6 you have to port your code to IPv6.
There is no physical way to increase the address space without requiring code changes. People having making the same complaint for 20 years and it's even more hollow now then it was then.
99% of the time, you will use your OS standard library functions and completely ignore the networking underneath. Literally, all the libraries will transparently handle IPv4 or IPv6 with no problem.
If you're in the 1% of software that has coding in some implicit assumption of field size for IPv4 then you are the 2020 equivalent of the Y2K problem. Grow your field sizes, fix your regexes, and use the platform support as much as possible.
Finally, you can literally just turn on IPv6. Everything will work just fine. IPv6 has private addresses, you can do all the dumb stuff from IPv4 in v6. Unsurprisingly though, most major vendors don't want to spend a lot of energy supporting those hacks.