- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Wed, 15 Oct 2014 12:44:45 +0200
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Usecase: PeerConnection in peer-A establishing two separate ICE/DTLS transports (audio and video) with peer-B (which supports rtcp-mux but does not support Bundle). - ICE procedures begin in peer-A. - At some point the ICE is completed in the audio transport. Q: Should PC fire oniceconnectionstatechange(connected)? - For some reason ICE is still not connected in the video transport. Q: Should PC later fire oniceconnectionstatechange(completed) due the ICE status in the audio transport? - Later timeout or any other error happens in the video transport so its ICE procedures end with error. Q. Should P fire oniceconnectionstatechange(failed) or oniceconnectionstatechange(disconnected)? I hope my questions are clear: Basically I mean that PeerConnection provides a "single and unique ICE status" while the fact it can deal with more than a single ICE transport. -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Wednesday, 15 October 2014 10:45:36 UTC