Issue 219: No "failed" state in DtlsTransport from Bernard Aboba on 2015-09-22 (public-ortc@w3.org from September 2015)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Tue, 22 Sep 2015 16:31:36 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <BLUPR03MB149A40CE1BAFC755434C383EC450@BLUPR03MB149.namprd03.prod.outlook.com>

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:

closed

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.

failed

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