- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Mar 2020 11:29:25 +0000
- To: public-webrtc-logs@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc: == connectionState error: State with no defined outcome == Imagine the following: - SDP-negotiate a PeerConnection with two *unbundled* m-sections - Fire ICE candidates at only the first m-section. Don't negotiate the second one. The result is that the first DTLS transport gets to "connected", the second DTLS transport remains "new". In the table in https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnectionstate, there is no description that corresponds to the combination of "new" and "connected" transports. What should the state be? Thanks to @fippo for demonstrating the bug. (It currently results in state "connecting" in Chrome, but media flows on the first m-section.) Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2499 using your GitHub account
Received on Thursday, 26 March 2020 11:29:27 UTC