ice connection state change to "connected" vs data channels

• From: Philipp Hancke <fippo@goodadvice.pages.de>
• Date: Mon, 30 Jun 2014 21:01:09 +0200
• To: public-webrtc@w3.org
• Message-ID: <53B1B3F5.9090407@goodadvice.pages.de>

The spec says the following about the ice connection state:
   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".

I ran into a bug where I accidentially dropped all ice candidates 
related to the m=application m-line and was not using BUNDLE.

I did not expect the iceConnectionState to change to connected, however 
it did.

I think the spec doesn't consider this case. Nor does the text describe 
what to do on a data channel only connection.


http://code.google.com/p/webrtc/issues/detail?id=3526  shows a way to 
reproduce this. I _think_ Firefox behaves the same way, but it's harder 
to drop all ice candidates because the local ones are included in the 
initial offer/answer.

Received on Monday, 30 June 2014 19:01:45 UTC