This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25257 - Explanation missing for ICE connection state transition from connected to disconnected state.
Summary: Explanation missing for ICE connection state transition from connected to dis...
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-04 10:54 UTC by Kiran
Modified: 2014-06-09 08:33 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-04-04 10:54:54 UTC 
Eplanation for ICE connection state transition from connected to disconnected state is missing in section 4.4.3 of [1].
The following missing explanation,

. (connected, lost connectivity): disconnected

should be added to the list.
After addition, the list of explanation bullets will be as shown below.

. new RTCPeerConnection(): new
. (new, remote candidates received): checking
. (checking, found usable connection): connected
. (checking, gave up): failed
. (connected, finished all checks): completed
. (completed, lost connectivity): disconnected
. (connected, lost connectivity): disconnected
. (any state, ICE restart occurs): new
. close(): closed

[1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtciceconnectionstate-enum
Comment 1 Kiran 2014-06-09 04:29:44 UTC 
Harald commented that he neither object nor support this, but suggests to change the lead-in [1] to 

"Some example transitions might be"

(This comment is added for tracking)

http://lists.w3.org/Archives/Public/public-webrtc/2014Apr/0006.html
Comment 2 Adam Bergkvist 2014-06-09 08:33:26 UTC 
Updated the header to clarify that this is not a complete list of state transitions (as Harald commented).

Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/bb2f77ba69dcd8e041970c2a08c47672dca22128

Closing this bug as WONTFIX.