I love opening up my computer in the morning and seeing tweets like this one:
https://twitter.com/ibc_tw/status/496977209073364992
The text is:
I’ve tested #WebRTC with Chrome talking to a ICE-Lite WebRTC server on IPv6. It just works. Nice.
And THAT is the way it should be. For all the work we do as a community and industry to advance the deployment of IPv6, in the end the user experience should be exactly that… it should “just work”. Users shouldn’t notice – or care – that their traffic goes over IPv4 or IPv6.
Kudos to the Chrome team for making it so that WebRTC “just worked” over IPv6. And kudos to Iñaki Baz Castillo for noticing!
Now, let’s get out there and make everything else “just work” over IPv6! 🙂
If you’d like to get started with making your applications or network work with IPv6, please check out our “Start Here” page to find resources tailored to your type of role and organization – and please let us know if you need more information.
UPDATE: A bit more information about what made the WebRTC application “just work” in Chrome. Per Iñaki Baz Castillo, he had this bit of JavaScript code in the WebRTC app that the browser downloaded:
var pc_constraints = {
mandatory: { googIPv6: true }
};
That bit of code made his app work over IPv6.