Re: [pntaw] New version of draft-hutton-rtcweb-nat-firewall-considerations

... I was, of course, referring to the "TURN over websockets" draft, as
"this draft".

On Sat, Sep 21, 2013 at 5:57 PM, Oleg Moskalenko <mom040267@gmail.com>wrote:

> HTTP Connect, indeed, may allow a similar functionality. But it will
> require two things: a proxy configuration in the browsers, and an HTTP
> Proxy set by enterprise IT department. That may be a challenge for a new
> WebRTC project in an enterprise environment.
>
> This draft allows transparent connection and operation, unlike the HTTP
> proxy case.
>
> There are tools (websockify) which make possible to use this draft with
> the existing TURN servers. Putting the burden on the TURN server provider
> and maintainer is easier in most cases than negotiating new IT requirements
> with the enterprise IT managers.
>
> Of course, advanced TURN servers may include it as part of the TURN server
> implementation.
>
> Oleg
>
>
>
> On Sat, Sep 21, 2013 at 3:48 PM, Hutton, Andrew <
> andrew.hutton@siemens-enterprise.com> wrote:
>
>>
>> I just don't see any advantage in the TURN over Websockets approach over
>> the HTTP Connect initiated tunnel which works without any new protocol and
>> therefore works with existing TURN servers.
>>
>> Andy
>>
>>
>>
>> ________________________________________
>> From: pntaw-bounces@ietf.org [pntaw-bounces@ietf.org] on behalf of
>> Sergio Garcia Murillo [sergio.garcia.murillo@gmail.com]
>> Sent: Saturday, September 21, 2013 8:47 AM
>> To: Bernard Aboba
>> Cc: pntaw@ietf.org
>> Subject: Re: [pntaw] New version of
>> draft-hutton-rtcweb-nat-firewall-considerations
>>
>> >
>> > "So in 100% cases that TURN over TLS works, TURN over (secure)
>> > websockets works too."
>> >
>> > [BA] Agree they would both traverse that firewall equally well, but
>> > TURN over (secure) websockets only works if the TURN server supports
>> > it, which most won't.   This makes mandating TURN over Webosckets
>> > support in the browser a hard sell.
>>
>> We are already working on providing a working prototype of TURN over
>> websocket that will show how easy would be to add it to both browser and
>> server. In fact, on first phase, we will not change the TURN server at
>> all but use a websockify proxy https://github.com/kanaka/websockify to
>> the WS to TCP conversion.
>>
>> Best regards
>> Sergio
>>
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>>
>
>