Re: [webrtc-pc] State gaps in connectionState algorithm (#2827)

Another problem unique to this table is the complexity added by DTLS into the logic produce sentences contain both AND and OR, which is ambiguous. E.g.

_"None of the previous states apply **_AND_** all RTCIceTransports are in the "new" or "closed" state, and all RTCDtlsTransports are in the "new" or "closed" state, **_OR_** there are no transports."_

The sanest interpretation is that lack of transports isn't meant to override previous states. It seems logical to apply the same thinking to the other states as written, since doing so creates a predictable pattern of each state deferring to the one preceding it, which seems like an intentional pattern that makes sense, and seems intended

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 14 February 2023 00:15:33 UTC