- From: Blessing Pascal <pascal.blessing@student.htldornbirn.at>
- Date: Fri, 13 Jun 2014 08:38:57 +0000
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Received on Friday, 13 June 2014 21:39:36 UTC
In 4.3.1 in the definition of the procedures after an ICE event it is unclear if the "ICE connection state" at article 2 is the same as "iceConnectionState" at article 3 (marked red below) 1. If the RTCPeerConnection ice gathering state<http://dev.w3.org/2011/webrtc/editor/webrtc.html#dom-peerconnection-ice-gathering-state> is new and the ICE transports setting<http://dev.w3.org/2011/webrtc/editor/webrtc.html#ice-transports-setting> is not set to none, the user agent MUST queue a task to start gathering ICE addresses and set the ice gathering state<http://dev.w3.org/2011/webrtc/editor/webrtc.html#dom-peerconnection-ice-gathering-state> to gathering. 2. If the ICE Agent has found one or more candidate pairs for each MediaStreamTrack that forms a valid connection, the ICE connection state is changed to "connected". 3. When the ICE Agent finishes checking all candidate pairs, if at least one connection has been found for each MediaStreamTrack, the iceConnectionState is changed to "completed"; else the iceConnectionState is changed to "failed".
Received on Friday, 13 June 2014 21:39:36 UTC