W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Ambiguous connection state when list of transports are empty

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Thu, 01 Jun 2017 16:50:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-305553346-1496335810-sysbot+gh@w3.org>
They should all be `new`. For `RTCIceGatheringState` this is already explicit: 

> new: Any of the RTCIceTransport s are in the new gathering state and none of the transports are in the gathering state, **or there are no transports**.

For the others, it's less obvious. For example:

> new: Any of the RTCIceTransport s are in the new state and none of them are in the checking, failed or disconnected state, or all RTCIceTransport s are in the closed state.

"No transports" could be thought to satisfy the condition "all transports are in the closed state", for some definition of the word "all". But we might as well make it explicit like it is for the gathering state.

@pthatcherg, maybe you have an opinion since you wrote this.

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1305#issuecomment-305553346 using your GitHub account
Received on Thursday, 1 June 2017 16:50:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:43 UTC