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

[webrtc-pc] Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState

From: Soares Chen via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Jun 2017 03:28:45 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-234712308-1496978923-sysbot+gh@w3.org>
soareschen has just created a new issue for https://github.com/w3c/webrtc-pc:

== Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState ==
Each `RTCDtlsTransport` have an underlying `RTCIceTransport`. Intuitively the transport state for the DTLS connection is dependent on the state of the underlying ICE connection. e.g.:

- When `RTCDtlsTransportState` is `connected`, underlying `RTCIceTransportState` should be `completed` (or `connected`?) and underlying `RTCIceGathererState` should be `complete` (or `gathering`?)
- When `RTCIceTransportState` is `closed`, the associated `RTCDtlsTransportState` must be either `closed` or `failed`.
- Nonsense state relation should be disallowed, e.g. having `RTCDtlsTransportState` to be `connected`, but underlying `RTCIceTransportState` is `failed`.

Is there any way the spec allow us to make these kind of assumptions? Or should the spec impose requirements about the state relation between DTLS and ICE? 

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1362 using your GitHub account
Received on Friday, 9 June 2017 03:28:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC