In the WebRTC standardisation post I mentioned that one of the controversial discussions in the IETF context was the mandatory to implement (MTI) video codec battle for WebRTC. While there are some technical arguments on the topic (i.e this VP8 vs H.264 – subjective evaluation and this performance comparisons discussion), there is no dispute both are high quality and […]
Strong WebRTC Signals at the IIT Real-Time Communications Conference
Last week I attended the Illinois Institute of Technology Real-Time Communications (IIT-RTC) Conference in Chicago. This event has a history of attracting key players from around the RTC world. It features discussion that is distilled down to the key trends and technology challenges in the industry, with very little “fluff” on top. This year the […]
getUserMedia – What happens when there’s missing media sources?
As discussed in previous posts, the mission of the W3C WebRTC WG is to define client-side APIs to enable Real-Time Communications in Web-browsers. At a very high-level overview, there are three main steps to be taken when setting up a WebRTC session: Obtain local media – provides access to local media input devices such as webcams and microphones […]
Signalling Options for WebRTC Applications
As I described in the standardization post, the model used in WebRTC for real-time, browser-based applications does not envision that the browser will contain all the functions needed to function as a telephone or video conferencing unit. Instead, is specifies the browser will contain the functions that are needed to run a Web application which would […]
WebRTC MUST implement DTLS-SRTP but… MUST NOT implement SDES?
As I anticipated in my post on WebRTC standardization, the IETF 87th meeting took place last week in Berlin, Germany. One of the agenda items for WebRTC was whether SDES should be part (and how) of WebRTC. According to the IETF drafts, any WebRTC compliant implementation must support the RTP/SAVPF profile which builds on top of […]