[pntaw] TURN over websockets

[Sergio Garcia Murillo <[e-mail]>]

Hi all,

I will shoot first.

It is great to finally see some real interest in what I consider to be 
the blocking point for webrtc in order to run business on top of it, 
which is the ability to be able to connect through corporate firewalls.

I have seen some people arguing that with just TURN over TCP on port 443 
the problem will be solved, but I seriously doubt it. Neither TURN over 
SSL would do, as most web filters do DPI and will not enable the 
connection. Also, I have heard lots of voices that says we are trying to 
override network admin policies with dirty tricks. With whom, I could agree.

So, the only way I see to move forward and overcome this issues is by 
playing according to the WEB rules, and use HTTP standards to enable 
media connectivity in WebRTC that would play nicely with current 
corporate HTTP proxies and web filters.

And,  for me the most viable solution would be to enable TURN over 
websockets. As most WebRTC services relay on websockets in one way or 
another for signaling, we could assume that media would work on 100% of 
the cases where signaling is working today.
Also, as it is an http based solution, network administrators could 
apply corporate policies and block connections to not-trusted TURN servers.

Best regards
Sergio