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

["Hutton, Andrew" <[e-mail]>]

On: 22 September 2013 01:57 Oleg Moskalenko WroteL
> 
> 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.

[AndyH] - The case of an enterprise WebRTC project taking place under the control of the enterprise IT department although within scope is not the prime reason for wanting the HTTP Connect mechanism.  There are various options for this use case and the important thing is that the browser behavior is standardized and understood by the IT department.

Probably more important at least for early deployments is making sure that a WebRTC service external to the enterprise is accessible when there is no IT department or when the IT department is not WebRTC aware and just wants it to work.  The power of WebRTC is that it brings new type of media to the web and it just has to work by default with additional controls possible if the network administrator wants to use them. If an enterprise already has a Web/HTTP Proxy deployed and a firewall configured to allow web traffic to flow via the proxy then this should also work when accessing WebRTC services. This has nothing to do with an enterprise deploying WebRTC for its own use.


> 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.

[AndyH] As I tried to explain above the use case of prime importance is getting WebRTC to work with existing infrastructure and without requiring an enterprise to deploy stuff just because an enterprise user wants to use a WebRTC service maybe on a single use basis such communicating with a suppliers call centre.


> 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
>