An anonymous reader writes: Several groups are currently working on specifications for plugin-free, real-time audio and video communication. The World Wide Web Consortium has one called WebRTC, rudimentary support for which is found in Chrome and Firefox. Back in August, Microsoft announced its own specification, CU-RTC-Web, because it thought WebRTC wasn't worthwhile. W3C carried out a vote to choose between the two specs, which came out strongly in favor of WebRTC. Microsoft went ahead anyway, and it has now published a prototype for the proposed specification. 'So what's Microsoft playing at, persevering with its own spec in spite of its rejection by the WebRTC group? The company's argument is twofold. First, WebRTC simply isn't complete yet, and Microsoft believes that working on its proposal can shed light on how to solve certain problems such as handling changes in network bandwidth or keeping cellular and Wi-Fi connections open in parallel to allow easy failover from one to the other. Even if Redmond's spec isn't adopted wholesale, portions of it may still be useful. Second, the company believes that WebRTC may not be as close to real standardization as its proponents might argue.'