Issue 219: No "failed" state in DtlsTransport

Peter Thatcher has pointed out that there is no "failed" state in the DtlsTransport, and it would be a good idea to differentiate the "closed" state (which can be entered by calling stop()) from the "failed" state, where something has gone wrong.

Proposed change to the RTCDtlsTransportState descriptions:


The DTLS connection has been closed intentionally via a call to stop(). Calling transport.stop() will also result in a transition to the "closed" state.


The DTLS connection has been closed as the result of an error (such as a DTLS alert or a failure to validate the remote fingerprint).

Received on Tuesday, 22 September 2015 16:32:06 UTC