- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2023 15:24:49 +0000
- To: public-webrtc-logs@w3.org
docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc: == Updates to RTCPeerConnection.connectionState should happen when new RTCDtlsTransports/RTCIceTransports are created and destroyed due to negotiation == Right now, it does not appear that webrtc-pc says to update RTCPeerConnection.connectionState when negotiation creates/destroys transports. So, for instance, if a reoffer adds an m-section with a new transport (ie; not in a bundle with a previously existing transport), the connectionState would need to go back to connecting. As another example, if the previously mentioned reoffer is rolled back, we would expect the connectionState to revert back to what it was before. We need to be updating this state on reoffers, reanswers, and rollbacks at a minimum. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2817 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 January 2023 15:24:51 UTC