[7rurl]

The big problem with Microsoft's spec is that it doesn't specify a protocol, so it is impossible for other browsers to implement the standard. The spec only says that RTP will be used but not what specific profile or codecs. Microsoft's prototype uses a plugin for Chrome and IE that implements their proprietary protocol.

The WebRTC spec on the other hand does specify a protocol via the RTCWeb IETF specs. The SDP used in WebRTC is part of that. Also the Chrome and Firefox teams are working hard to get the two browsers talking to each without resorting to prototype plugins and instead using their own separate implementations of the WebRTC protocol.

When/if Microsoft publishes the protocol specs, then their UC-RTC-Web spec will truly be complete and we can judge it on its merits compared to WebRTC. Also in a very real sense the WebRTC spec is more complete since it does specify a protocol.

[mook]

Small correction: Chrome and Firefox teams are using basically the same implementation of WebRTC; see http://mxr.mozilla.org/mozilla-central/source/media/webrtc/t... - it's an import of the Chromium code into Mozilla. Having the source available definitely makes interoperability easier and is better than having a blobby bit, though.

[shmerl]

Another big problem is their attempt to prevent mandating any open codecs.