The WebRTCStandards.info team on a live Q&A
Yesterday we had our second live WebRTC Q&A session. On the session we had Dan Burnett, Alex Gouaillard and myself.
Below are the highlights of the session. For more details see the session recording and presentation.
WebRTC ICE
On Feb 25 there was a virtual interim standards meeting in which 4 or 5 items were discussed. The 2 main topics regarding ICE were:
Debugging – There have been many changes done in the sender and receiver objects, many of which we covered in our updates. Problem is that many of these changes are not yet reflected in the statistics which makes debugging harder. The objective is to align the statistics with those changes and also add more information such as round-trip statistics to STUN checks
End of Candidates – There will be API to let the browser know when the remote side is done sending candidates
More on this in the recording. We will also provide more information about these item in our future updates.
Video codecs
Reviewed current state of MTI video codec IETF decision and actual current state of video codec support in browsers.
This resumed with several questions about usage of VP9 and patent issues related to SVC and VP9.
Microsoft and WebRTC/ORTC
There are many that are still worried about the fact that Microsoft decided to skip WebRTC 1.0 and go directly to ORTC. This shouldn’t be a great concern today. WebRTC is already adopting a lot of the ORTC functionality. We have provided several updates about sender and receiver objects that are actually ORTC additions to the WebRTC standard.
If you are still not clear about the difference between WebRTC 1.0 and ORTC and how sessions are established without exchanging SDP, read this post.
WebRTC on mobile devices
This topic continues to come back which means that WebRTC on mobile is still not a simple goal to achieve.
In the session we explained on which mobile OSs WebRTC is supported today in the browser and WebView (Android of course), what’s the challenge with browsers in iOS (Apple mandatory rendering requirements) and the different options of adding WebRTC on mobile to your service. Doing this work yourself and compiling it into your application, using an SDK or a Hybrid application.
We also talked about a few of the commonly used SDKs by large companies such as IBM.
There were more questions
More questions were asked and discussed during the session. You can see those in the CrowdCast session page and hear the answers in the recording.
Some of the feedback received from people who participated in the session:
“Great Webinar”
“Thanks Alex, Dan and Amir. Good session”
Make sure to register for our updates and join our next live Q&A.
[…] WebRTC Q&A Highlights – Session #2 […]