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

Re: What should happen to the ICE gathering state when iceTransports is changed?

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 15 Jul 2014 10:59:06 -0700
Message-ID: <CABkgnnVErMb1+j=SVvSVJ7OeroE73NkUamac9e_LKT9L6Kvf3g@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Bernard Aboba <Bernard.Aboba@microsoft.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 15 July 2014 10:04, Justin Uberti <juberti@google.com> wrote:
> More generally, I wonder if iceTransports changes should always take effect
> on the next ICE restart, meaning that even changes of relay->all during
> gathering would have no effect until ICE restart occurs. One mode of
> operation = less chance for apps to get it wrong.

I think that we need to wait for a restart too.

That does increase the cost of making the switch, which isn't without
consequence, but I think that - again - it's the only option that
stands a good chance of not breaking stuff.  I really don't know how
ICE (assuming trickle) might behave in reaction to a release of a new
set of candidates at arbitrary points.  Early on: sure, fine.  After
nomination is done, I really don't think it's going to produce a
good/useful outcome in all cases.  Not without a lot of work, anyway.
Received on Tuesday, 15 July 2014 17:59:33 UTC

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