Hi,
On Tue, May 20, 2014 at 10:13:57AM +0200, Marco Hogewoning wrote:
In simple terms, I don?t want to take the risk.
Wouldn't it be much more safe to completely turn off IPv6 on the meeting LAN, then? And WiFi, as wired ethernet is way more reliable anyway.
I don;t think the issues right now are with IPv6 per se, what I’ve seen so far it is the lack of IPv4 that is causing issues. Just a random list if what comes to mind right now: - Android sucks in multiple dimensions - Skype does not work - Every time OS X restarts the dhcp-client (on exponential back off), it sends signal that makes my VPN client believe it lost connectivity and causes it to drop all sockets and reconnect. I can assume other people will get hit by at least some of the above and there are of course others. Forcing people, who might not be able to do something about this or implement work arounds, to use this or by default give them something that we know is broken should (‘must’?) be considered bad practice. In the long run this is likely to cause damage to the reputation of IPv6 in general or RIPE NCC. “I switched to the IPv4 and it al works, so IPv6 still suck golfballs through a garden hose” Marco