Do web developers need to be concerned by the end of IPv4? Or is this strictly a hosting level concern?
What can the average PHP/JavaScript/Ajax etc. developer do to mitigate the impact of the changeover?
Discuss!
(if this has come up before I apologies, but my search revealed nothing)
Difficulty in detecting and managing unknown or unauthorized IPv6 assets on existing IPv4 production networks. The added complexity of operating parallel IPv4 and IPv6 networks. A lack of IPv6 maturity in security products. The proliferation of IPv6 and IPv4 tunnels can complicate defenses.
The rationale for transition is either the lack of IPv4 address space or the required use of new features in IPv6, or both. The IPv6 specification requires 100 per cent compatibility for the existing protocols. Compatibility is also required for existing applications during the transition.
Every device will need an IP address and there are far too few available addresses within the IPv4 system to handle the sheer quantity of connections. It's a problem that's been predicted and solved for many years, in theory at least. But IPv6 is being adopted at a glacially slow pace.
On the serverside, make sure you're not making assumptions about the format of the remote IP address - hacks like packing the IP address of a poster in a single 32-bit database field are a bad idea. If you are using subnet masks for bans or something, that will need changes as well.
Also, when validating fields for IP addresses, don’t forget to take both formats (152.115.4.70 and 2001:db8:1f70::999:de8:7648:6e8) into account.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With