Hi Marcel, > I would initially hide it behind a main.conf option, but have it > defaulting to disable to comply with this updated RFC once it has > been accepted.
Ack. I'll send a patch to the list, not sure I'll get around to doing it before Easter though as I need some time to familiarise myself with the config parsing code first. :-) BTW, the draft *is* accepted, it's just not made it through the final editing queue. That's just about fixing spelling mistakes and making sure references are current and so on, there's no question that the requirement is going to be the way it is. So there's no real reason to wait for it to be assigned an RFC number. > However with 6to4, I actually do not know how many users are actually > depending on our support of 6to4. Others that have used this feature, > might want to comment here. I can provide some background here. There was actually quite substantial usage of 6to4 back in 2007-2009 or so. At that point it was actually the majority of all IPv6 traffic. However it soon became clear that it was providing so poor quality connectivity that it was actually preventing content providers from enabling IPv6 on their sites (because once you publish AAAAs, the users' OS/browser try IPv6/6to4 rather than IPv4, which has a truly appaling failure rate, and the users get mad because "the site isn't working"). So we went to the OS and browser vendors like Microsoft and Apple and got them to ensure that 6to4 was preferred below IPv4. The getaddrinfo() algorithm was similarly updated to avoid 6to4 (see RFC6724). In the same time period the browser vendors implemented "Happy Eyeballs" (RFC6555) which also helps gloss over problematic IPv6/6to4 connectivity by essentially trying both address families in parallel and using the one that comes back with a connection first. Anyway the result was that 6to4 (and Teredo, a similar technology) is hardly ever used anymore and hasn't been for 3-4 years. This is fortunate, because it made it possible for big sites like Google and Facebook to finally deploy IPv6. You can see this in Google's graph at http://www.google.com/intl/en/ipv6/statistics.html, the 6to4/Teredo plot crashed in mid-2011 and has stayed at 0 ever since. Tore _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
