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

[webrtc-pc] Description of handling iceCandidatePoolSize in setConfiguration is out of sync with JSEP

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Fri, 03 Mar 2017 18:25:19 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-211765044-1488565517-sysbot+gh@w3.org>
taylor-b has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Description of handling iceCandidatePoolSize in setConfiguration is
 out of sync with JSEP ==
In JSEP, we decided that changing the candidate pool size is only 
allowed before setLocalDescription is called, and as a consequence, 
the pool will only be used for the first offer/answer exchange.

But webrtc-pc currently has a step in `setConfiguration` that says 
simply:

> Set the ICE Agent's prefetched ICE candidate pool size as defined in
 [JSEP] to the value of configuration.iceCandidatePoolSize. If the new
 ICE candidate pool size changes the existing setting, this may result
 in immediate gathering of new pooled candidates, or discarding of 
existing pooled candidates, as defined in [JSEP].

... Which doesn't say what to do if `setLocalDescription` has already 
been called.

I'd suggest throwing an InvalidModificationError like we do for 
everything else.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/1049 using your GitHub account
Received on Friday, 3 March 2017 18:25:26 UTC

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