4 ms·
> The main progress has been WebRTC Yes, it is a kind of combination of the best approaches to NAT traversal from the SIP world, supporting both STUN & TURN an
by nbaksalyar 9y ago
> The main progress has been WebRTC
Yes, it is a kind of combination of the best approaches to NAT traversal from the SIP world, supporting both STUN & TURN and ICE with the Trickle addon.
Some very good references on the topic I found recently: https://webrtchacks.com/ https://webrtchacks.com/ and https://www.html5rocks.com/en/tutorials/webrtc/infrastructure/ https://www.html5rocks.com/en/tutorials/webrtc/infrastructur....
- jbeda 9y agoThe WebRTC stuff was based on libjingle originally. We built that as part of the Windows Google Talk client. It was all based on XMPP and not SIP. The techniques were used in many contexts at the time.
- adamfisk 9y agoYeah exactly. This signaling protocol doesn't really matter, and both SIP and XMPP to me are way over engineered and super inefficient- silly that they're text based at all. Essentially like HTTP 1.0 and 1.1 vs HTTP/2 - we just don't have the latter in the signaling case yet, or at least not standardized that I know of.