- From: Peter Thatcher via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Sep 2016 10:48:26 +0000
- To: public-webrtc@w3.org
pthatcherg has just created a new issue for https://github.com/w3c/webrtc-pc: == Inconsistency between PeerConnectionState and IceConnectionState == Two edge cases with current text: 1. If there are no IceTransports (initial state): The PeerConnectionState will be "new" and the IceConnectionState will be "closed". 2. If all IceTransports are in the closed state but the PC is not in the closed state (state when all m-lines are rejected): The PeerConnectionState will be "new" and the IceConnectionState will be "closed". I think both of these could be fixed by: 1. Appending to the text for the "new" IceConnectionState the following: "or all transports are in the closed state." This would match the PeerConnectionState. 2. Changing the text for the "closed" IceConnectionState to the following: " The RTCPeerConnection object's isClosed slot is true." This would match the PeerConnectionState. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/810 using your GitHub account
Received on Thursday, 22 September 2016 10:48:35 UTC