W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2014

Re: iceTransports=relay - use vs gather

From: Justin Uberti <juberti@google.com>
Date: Sat, 18 Oct 2014 11:03:09 -0700
Message-ID: <CAOJ7v-1rU-5KP9HopqAjsYB41fNBUw8E+vJo=7XY9bOfhODvng@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Cc: Philipp Hancke <fippo@goodadvice.pages.de>, public-webrtc <public-webrtc@w3.org>
I think the text just needs to say "The ICE engine must only use media
relay candidates as its local candidates." The remote candidates can be
anything, but this isn't clear from the text.

I think this is what Philipp is trying to say, but use vs gather is
confusing, as Emil points out.

On Sat, Oct 18, 2014 at 7:55 AM, Emil Ivov <emcho@jitsi.org> wrote:

> I don't think so. If you truly want to avoid leakages for privacy
> reasons, then you would never *use* anything than relay, otherwise you
> would leak local IP addresses as peer reflexive.
>
> On Sat, Oct 18, 2014 at 4:49 PM, Philipp Hancke
> <fippo@goodadvice.pages.de> wrote:
> > http://w3c.github.io/webrtc-pc/#rtcicetransports-enum says the following
> > about the "relay" value:
> >
> >         The ICE engine must only use media relay candidates such as
> >         candidates passing through a TURN server. This can be used to
> >         reduce leakage of IP addresses in certain use cases.
> >
> > The "use" seems wrong. ORTC uses "gather" instead
> > (
> http://ortc.org/wp-content/uploads/2014/08/ortc.html#rtcicegatherpolicy*)
> > which does not imply ignoring host/srflx candidates a peer sent.
> >
>
>
>
> --
> https://jitsi.org
>
>
Received on Saturday, 18 October 2014 18:03:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:42 UTC