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

[webrtc-pc] Errors when identifying a m-line in addIceCandidate()

From: Adam Bergkvist via GitHub <sysbot+gh@w3.org>
Date: Thu, 17 Mar 2016 07:33:00 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-141502993-1458199979-sysbot+gh@w3.org>
adam-be has just created a new issue for 

== Errors when identifying a m-line in addIceCandidate() ==
We have two pieces of information in an ice candidate to identify a 
m-line sdpMid and sdpMLineIndex.

The successful case is when both identifiers points to the same m-line
 or if one identifies an m-line while the other is null.

We have the following uncertain/error cases
1. Both are set, one identifies an m-line while the other is bogus.
2. Both are set and point to different m-lines.
3. One is set, and points to an non-existent m-line (clearly an 

So the first question is: what should we do in 1 and 2 ?

The second question is where this should be specified. 
addIceCandidate() is specified to do some synchronous checks on the 
candidate argument and then start a 'process to apply' the candidate. 
We could either check for the above errors  in the synchronous section
 and specify it in the webrtc-pc document. The alternative is to let 
these checks be part of the 'process to apply' candidate and let the 
error be asynchronously reported to JavaScript. In the second case, 
JSEP would need to specify this.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/551 using your GitHub account
Received on Thursday, 17 March 2016 07:33:02 UTC

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