Re: [webrtc-pc] Partially connected peerconnection might have "new" connectionstate. (#2031)

@alvestrand: 
Note that connected + closed should be connected, not connecting, we'd have to say something like 
"Any of the RTCIceTransports or RTCDtlsTransports are in the "connecting" or "checking" state, or any of them is in the "connected" state and any of them is in the "new" state  and none of them are in the "failed" state."

But here it's not really clear that the "no failed" condition always applies. This table could be much cleaner if we could say that "failed" has a higher precedence that the other states, is there any allowed way to do that?

I'd also be in favor of also excluding "completed" from "new", for similar reasons. 
That would allow us to simplify the "new" section to:
"All of the RTCIceTransports or RTCDtlsTransports are in the "new" or "closed" state, or there are no transports."

Then "connected" would have to become for example:
"Any of the RTCIceTransports or RTCDtlsTransports are in the "connecting" or "checking" or "connected" or "completed" state and not all of them are in the "connected" or "completed" or "closed" state and none of them is in the "failed" state."

Another thing to consider is that the current definition of "disconnected" is written to avoid clashing with "connecting". We might have to tweak it as well, depending on how we change "connecting".

@fippo: I'm seeing this behavior in my in-progress WebRTC CL, that's what prompted this issue.

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

Received on Thursday, 22 November 2018 13:27:54 UTC