On 05/16/2018 09:22 PM, Lee Howard wrote:>> - why new technologies and sites get invented yet IPv6 is not on them >> (deployed IoT w/ IPv4, self-driving cars w/ IPv4, new big office >> buildings w/ IPv4, and so on). > > 1. Shortsightedness > 2. Developers hacking together what they barely know > 3. Using an OS designed for embedded systems that's based on a very old > Linux without IPv6 support.
(getting ready to be lapidated) For my end-user (like, a computer and a rental server at a hosting company) point of view: * Being dual-stack is painful to configure and risky from a security point of view (hello iptables and ip6tables getting out-of-sync, IPv6 privacy extension, etc.) * IPv6-only requires NAT64 to get things to work (just see the issues mentioned by the Mythic Beasts presentation from IETF101 you linked to, even with NAT64 things don't work out of the box) * IPv4-only requires nothing, as NAT when required is already handled by devices out of my line of sight (eg. routers from where I connect, etc) Also, for my server, setting up a NAT64 is completely useless, as the NAT64 would need to run on… the same server, meaning that it needs to be dual-stack anyway. So, as an end-user, the easiest solution for me for now is `ipv6.disable=1`, and I'll switch to `ipv4.disable=1` when it will exist and the rest of the world will be ready for it. Yes, I know this is a chicken-and-egg problem. This is likely something that should be addressed by this WG (and the reason why I subscribed and lurked for a while), but I have absolutely no idea how. (and now I need to flee before being actually lapidated) _______________________________________________ sunset4 mailing list [email protected] https://www.ietf.org/mailman/listinfo/sunset4
