- From: Taylor Brandstetter <deadbeef@google.com>
- Date: Wed, 21 Oct 2015 13:32:16 -0700
- To: public-webrtc@w3.org
Received on Wednesday, 21 October 2015 20:32:45 UTC
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 Wednesday, 21 October 2015 20:32:45 UTC