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

Re: Should setConfiguration fire onnegotiationneeded?

From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 23 Oct 2015 10:54:16 -0700
Message-ID: <CAJrXDUH0AKbMj_Ajt7n0RWEJj7H6u0cvXiLDcLNxAodEt6tbbQ@mail.gmail.com>
To: Taylor Brandstetter <deadbeef@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
I *think* the rule implies that, yes, it should fire onnn.   But it would
be nice if the spec were more explicit about it so that we make sure the
behavior is the same across browsers.


‚Äč

On Wed, Oct 21, 2015 at 1:32 PM, Taylor Brandstetter <deadbeef@google.com>
wrote:

> If setConfiguration changes the ICE candidate policy or the set of
> STUN/TURN servers, the changes won't go into effect until the next
> gathering phase, which will occur on an ICE restart.
>
> An ICE restart obviously requires signaling. So it seems to me that in
> these cases, setConfiguration should fire onnegotiationneeded, according to this
> rule <http://w3c.github.io/webrtc-pc/#setting-negotiation-needed>: "If an
> operation is performed on an RTCPeerConnection that requires signaling, the
> connection will be marked as needing negotiation."
>
> Thoughts?
>
Received on Friday, 23 October 2015 17:55:28 UTC

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