Re: [rtcweb] draft-schwartz-rtcweb-return

On Thu, Mar 26, 2015 at 11:20 AM, Cullen Jennings <fluffy@cisco.com> wrote:

> I'd like to point out that the combination of
> ietf-tram-turn-server-discovery and draft-schwartz-rtcweb-return allow any
> network you are connected to more or less MITM your media and do things
> like rate limit it, generate analytics on who you are talking to, force
> your traffic through an intermediary that is in a  different legal
> jurisdiction and so on.
>

This is true on any network, right?  If you can do NAT, you can do all of
those things.

> They are also not clear on how the browser gets the credentials to use the
> discovered TURN server. This seems like a major lacking before we can
> significantly discuss this.
>

I agree that turn-server-discovery should address this.

> As we have seen from the google proxy deployments, enough revenue can be
> generated from this relaying info to pay for the relay. I'm not keen on
> that happening automatically with no user consent or awareness.
>

It's already happening automatically, since 1999, thanks to WPAD, which
allows the network to automatically configure proxies for all web traffic
with no user intervention on all major browsers.

But I don't get how this will work for enterprise deployments - It's just
> very unclear how the JS would end with the appropriate set of TURN servers
> to use.
>

It would be helpful if you could point to text that you think is unclear.

>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>