Microsoft goes its own way with Web audio/video spec, despite W3C rebuff

Posted by BernardSwiss on Jan 20, 2013 3:22 AM EDT
Ars Technica; By Peter Bright
Mail this story
Print this story

Redmond first announced CU-RTC-Web in August. Along with the specification itself, the company produced a rationale; a list of reasons why it felt that WebRTC was a bad fit for the problem at hand, and why CU-RTC-Web was a superior solution. Perhaps the most specific complaint was that WebRTC was quite deeply linked to a specification called SDP, an open industry standard used extensively for VoIP and video conferencing systems in conjunction with SIP, with Microsoft arguing that this is over-complicated and hinders interoperability with non-SDP systems. SDP is used to negotiate the parameters of the connection; things like the bandwidth, the IP addresses and port numbers to use, and so on.

It just happens that Microsoft has non-SDP products of its own—Skype (which remains stubbornly proprietary and undocumented) and Lync (which can bridge with SIP systems, and hence understands SDP, but offers alternative APIs too).

Full Story

» Read more about: Story Type: News Story; Groups: Intellectual Property, Microsoft, Standards

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.