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

[webrtc-pc] Meaning of "Liveness checks have failed" for `disconnected` ICE state is not clear

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Jun 2016 23:45:37 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-158800123-1465256736-sysbot+gh@w3.org>
taylor-b has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Meaning of "Liveness checks have failed" for `disconnected` ICE 
state is not clear ==
This definition leaves me with a couple question:

- What is a liveness check? Is it a [STUN consent 
check](https://tools.ietf.org/html/draft-ietf-rtcweb-stun-consent-freshness-16)?
- "Checks" is plural. So how many checks must fail before entering 
`disconnected`? Does the state return to `connected` when the next 
check succeeds?

I looked through the meeting minutes to try to find the answers, but 
[the minutes from when it was 
introduced](https://www.w3.org/2012/09/17-webrtc-minutes.html) barely 
reference it.

In my opinion it's important the the definition is unambiguous, 
because some developers use this state for ICE restart logic and even 
updating the call UI. So it's important that its behavior is 
consistent across browsers.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/692 using your GitHub account
Received on Monday, 6 June 2016 23:45:38 UTC

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