Re: [webrtc-pc] Updates to RTCPeerConnection.connectionState should happen when new RTCDtlsTransports/RTCIceTransports are created and destroyed due to negotiation (#2817)

Furthermore, I think maybe we need to ignore RTCDtls/IceTransports in "new". Suppose the following occurs:

1. ICE is in checking from a previous negotiation.
2. We do a sLD(offer) that creates a new transport. We don't bother updating the connectionState/iceConnectionState (see above comment).
3. ICE connects! The old set of transports is now ready.
4. We handle the event on the RTCIceTransport, see the new transport that we aren't using yet, and set RTCPeerConnection.iceConnectionState to "checking"!

This seems wrong.

-- 
GitHub Notification of comment by docfaraday
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2817#issuecomment-1689956462 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 August 2023 13:21:52 UTC