IceTransportState after consent failure

[aboba]

In the May editor's draft, it is stated that a consent failure causes a transition to the "checking" state:

"In this state the RTCIceTransport is checking candidate pairs but has not yet found a successful candidate pair, or liveness checks have failed (such as those in [CONSENT]) on a previously successful candidate pair."

Is this correct, or should the failure of liveness checks result in a transition to the "disconnected" state?

Proposed revised text for "checking" and "disconnected":

Checking
In this state the RTCIceTransport is checking candidate pairs but has not yet found a successful candidate pair.

Disconnected
The RTCIceTransport has received at least one local and remote candidate, and a local and remote RTCIceCandidateComplete dictionary was not added as the last candidate, but all appropriate candidate pairs thus far have been tested and failed (or consent checks [CONSENT], once successful, have now failed). Other candidate pairs may become available for testing as new candidates are trickled, and therefore the "failed" state has not been reached.

[aboba]

Actually, it is possible to transition to checking due to a consent failure if all candidate pairs have not yet been checked:

The RTCIceTransport has received at least one remote candidate, and a local and remote RTCIceCandidateComplete dictionary was not added as the last candidate. In this state the RTCIceTransport is checking candidate pairs but has not yet found a successful candidate pair, or liveness checks have failed (such as those in [CONSENT]) on a previously successful candidate pair.