Re: [rtcweb] Default candidate pool size

Cullen Jennings <fluffy@iii.ca> Sat, 17 May 2014 21:06 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3997E1A0208 for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.009
X-Spam-Level:
X-Spam-Status: No, score=-1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id if_Yiu2ZL8nn for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:06:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 288F61A017C for <rtcweb@ietf.org>; Sat, 17 May 2014 14:06:05 -0700 (PDT)
Received: from sjc-vpn7-167.cisco.com (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 03F8B22E1F3; Sat, 17 May 2014 17:05:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CABkgnnVjJTnTypBqL-YLMPwo0_RSdkMLgQvD+L03jwyt_ffDqQ@mail.gmail.com>
Date: Sat, 17 May 2014 13:04:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFCA477F-653D-46FF-93CE-4338EA856C5C@iii.ca>
References: <CABcZeBNdd9Ze1G3ZOpGHVKsGKBdhEAOzg4qt7XKnX75dhQyTkA@mail.gmail.com> <CABkgnnVjJTnTypBqL-YLMPwo0_RSdkMLgQvD+L03jwyt_ffDqQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/95bJvQdrJd9rTbI6XsEUSRTLvRk
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Default candidate pool size
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 May 2014 21:06:06 -0000

I think the JS app needs a way to say what it needs in the way of pool size. 


On May 12, 2014, at 12:15 PM, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 11 May 2014 17:18, Eric Rescorla <ekr@rtfm.com> 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.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>