Share |

Microsoft proposes alternative spec for Web audio/video chat standard

Microsoft in its blog post recently outlined its position with WebRTC, an emerging Web standard that aims to enable real-time audio and video conferencing on the Web without requiring any plugins. The Redmond company has raised a number of concerns about the current draft specification and publish its own successor, called CU-RTC-Web.

They said the current specifications of WebRTC is incomplete. It is still in progress and subject to change by the W3C working group. It is based largely on technology that Google acquired in its 2010 acquisition of Global IP solutions. Google released the attached software under an open source license and drafted the original proposal. The standard has since gained the support of Mozilla, Opera, Ericsson, Cisco, and a number of other parties.

Microsoft claimed that the standards are too prescriptive and requires too much of the logic transport network browser implemented. As a result, the company says it will not offer enough flexibility for Web developers who want to customize how their real-time communication services will respond to changes in the quality of network .

Microsoft introduced its own WebRTC proposal called "a customizable, ubiquitous Real Time Communication over the Web," or rather, CU-RTC-Web. This is a step towards bringing real-time VoIP communication - aka Skype - in different browsers without the need for an application or plug-in. It also aims to be more flexible and customizable than the version currently offered by Google and Mozilla.

According to Microsoft, "It is designed to honor the key tenets of web architecture, it supports a customizable response to changes in the quality of the network, ubiquitous deployability with existing network infrastructure, and flexibility to support popular media formats and codecs, as well as openness to future change."

Microsoft claimed that the existing WebRTC measures falls short of it is showing signs of offering real world interoperability with existing VoIP phones, and mobile phone from behind the firewall and across routers. Instead, the current version - which is supported by Firefox, Opera and Chrome - video focuses on communication between web browsers under favorable conditions, and does not allow an application to control how The media is sent over the network.

Matthew Kaufman, the teacher architect for Microsoft, Skype WebRTC, told the media that the existing proposal WebRTC is working to create a black box within the browser: all pre-determined from the way media is sent in over the network on what codec you need to be used, leaving little room for optimization. However CU-RTC-Microsoft Web plan offers the customization and flexibility developers need while also supporting legacy devices.

Kaufman also pointed out that Google and Mozilla want to lock down their specifications in the VP8 video codec open sourced by Google back in 2010. Microsoft does not want to route it, stating that "a successful standard can not be tied to individual codecs, data format or situation."
 
"We are looking forward to continuing to work in the IETF and the W3C, with an open and useful dialogue that converges to a standard that is both future-proof and require a response communication on the web today," Microsoft stated. http://html5labs.com sa support sa">"The company would love to get community feedback on the details of its CU-RTC-Web proposal.”