Le 2014-04-15 09:56, Philip Homburg a écrit : >>> Right, to a certain extent that is true, of course; but not in the same >>> drive-by fashion where a single packet can put everyone offline (if the >>> option is not in the regular announcements). >> >> Sure it can. Just send them to a non-existing default gateway. Unless I >> misunderstood your point. > > Right now, on any network that doesn't do IPv6, sending RAs has marginal > effect. Certainly traffic within the site would be unaffected if there are > no IPv6 addresses in DNS. > > With an RA that kills IPv4, that changes dramatically. Sounds like something > no sane OS vendor would enable by default.
You can do the same today with a rogue DHCPv4 server. > From an OS perspective, I'd rather have this option in DHCPv4. That part > of the code knows about IPv4. Getting the IPv6 stack to tell the > IPv4 stack to shutdown is complicated Please tell me how this is complicated: $ grep "option no-ipv4" /var/db/dhclient6.leases.eth0 && pkill dhclient For the systems I know, it would be trivial to implement. I could go and submit a patch to NetworkManager today. > and probably won't be implemented > until enough people bitch about it (and how stupid the IETF was) for quite > some time. This is an argument that always comes back with any proposal. I totally disagree with it. Anyone could code this up and submit a patch to Android. Then when the next release happens, bam, lots of support overnight. Simon -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
