4 ms·
You can do the same thing with v6, the difference is problem space. TLS is about the client and the server upgrading while IP is about every box inbetween as we
by zamadatix 8y ago
You can do the same thing with v6, the difference is problem space. TLS is about the client and the server upgrading while IP is about every box inbetween as well. If you look at TLS and HTTP version changes when the inbetween infrastructure is involved (even just a single corporate FW, not the whole path) you're held to legacy versions just the same as IP is held to legacy versions.
Eventually some protocol is the bottom of what a group agrees to speak rather than individuals and that protocol has a completely different set of deployment issues than abstraction layers that can be built between end stations at higher levels.
- fpoling 8y agoIt is not only about intermediate boxes. Just consider how relatively smoothly various parts of WiFi stack was upgraded or how 2G->4G transition happens with mobiles phones. The biggest problem with IPv6 is that it a different protocol that requires special support on all levels starting from applications and down to managed switches.
- votepaunchy 8y ago> consider how relatively smoothly various parts of WiFi stack was upgraded Has WiFi been upgraded? I believe new devices still have support back to 802.11b.
- dtech 8y agoUsually, devices have an "802.11n+" options nowadays, dropping support for 11b and 11g has some benefits. It's often enabled by default on new devices, especially since most 11b/11g devices don't support WPA2-PSK so couldn't connect anyway
- Macha 8y ago11b maybe, but most 11g devices should support WPA2, 11g lasted a long while before 11n was widespread.
- fpoling 8y agoThe new WiFi installations do not run old protocols. Surely they may support the older versions, but by default the newer protocols are used. Compare that with IPv6 when after 20 years the protocol is still disabled by default on ISP provided routers in Europe.