- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2016 01:07:41 +0000
- To: public-webrtc@w3.org
taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc: == Rules for negotiation-needed flag need to be updated for transceivers. == I found a few problems with the current rules regarding the negotiation-needed flag: - It's still described overall in terms of tracks, not transceivers (such as in section 4.8.1). - It's only cleared by `setLocalDescription`, but `setRemoteDescription` should be able to clear it as well in some cases. - `createAnswer` sets the flag? I don't see the reasoning behind this. I'd expect setting a description to possibly set the flag, but not generating one. - The act of firing `negotiationneeded` after reaching the stable signaling state also clears the flag? This means if the next SDP exchange didn't finish negotiating something (such as if it was initiated by the remote peer), the event wouldn't be fired again. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/803 using your GitHub account
Received on Tuesday, 20 September 2016 01:07:50 UTC