In my last post (a long time ago) I introduced the issue of NATs and Firewalls, and the tools WebRTC uses to overcome them. First off, my apologies for the lengthy hiatus after promising to continue the discussion of NAT/Firewall traversal. Since that entry, I became a Dad for the 2nd time, and lets just […]
Brief
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 […]
Updated: Why the WebRTC API has it wrong – Interview with WebRTC Object API (ORTC) co-author Iñaki Baz
Updated 25 Aug 2013 – some minor edits fixing some ORTC API references and added ORTC sample code. In my post on WebRTC standardization I mentioned that one of the controversial points of discussion in the W3C context was whether the SDP Offer/Answer model and the current API provided the level of flexibility a wide range of […]
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 […]
An Intro to WebRTC’s NAT/Firewall Problem
Most folks that set out to write an application, or build an architecture, begin with nothing but features and functionality in mind. Many might start out assuming they will be traversing flat, reliable, and secure networks. Inevitably, reality sets in as one starts to demo or prototype much beyond the friendly confines of the lab, […]