[webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description

• From: Soares Chen via GitHub <sysbot+gh@w3.org>
• Date: Fri, 19 May 2017 03:27:37 +0000
• To: public-webrtc-logs@w3.org
• Message-ID: <issues.opened-229861272-1495164456-sysbot+gh@w3.org>

soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:

== addIceCandidate may add ice candidate to the wrong remote description ==
In step 2 and 3 of 4.6.2:

> 2. Let `remoteDescription` be connection's `pendingRemoteDescription` if not null, otherwise connection's `currentRemoteDescription`.
> 3. Add candidate to `remoteDescription`.

An `RTCPeerConnection` object could have both `pendingRemoteDescription` and `currentRemoteDescription` set with different ufrags, i.e. during ICE restart. If `addIceCandidate` is called with ufrag of previous ICE generation, i.e. `currentRemoteDescription`, the step still adds the candidate to the current generation, i.e. `pendingRemoteDescription`.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1227 using your GitHub account

Received on Friday, 19 May 2017 03:27:44 UTC