AFAIK, the default value of '0' logically equals to that what we can achieve with iceTransports set to "none" (don't gather any candidate).

I suggest adding candidatePoolSize attribute to RTCConfiguration.

This attribute can be modified by invoking updateIce / setConfiguration (based on the consnsus).

And the default value to 1.

I don't have very strong objections to '0' but support '1' with and optimistic assumption that every node/ browser implementing this specification will support Bundle.

This will avoid latency incured in candidate gathering.

App developer can set it to '0', in case, if the app is running in mobile device (if it feels to reduce battery drain out at the expense of latency).

------- Original Message -------

Sender : Martin Thomson<martin.thomson@gmail.com>

Date : May 13, 2014 02:15 (GMT+09:00)

Title : Re: [rtcweb] Default candidate pool size

wrote:
>
> My personal opinion is that candidate pooling is useful here and we
> should probably leave the default in the hands of the browser. I
> could live with 0 however.

I tend to agree.  The selection of a default seems like a good
opportunity for browsers to optimize.  For instance, a mobile device
might choose to defer gathering until it knows that it needs them;
whereas a device with a good source of power might prefer the latency
benefits associated with early gathering.  No point in us specifying
this.