Re: [rtcweb] Default candidate pool size

Kiran Kumar Guduru <kiran.guduru@samsung.com> Tue, 13 May 2014 12:00 UTC

Return-Path: <kiran.guduru@samsung.com>
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 79E231A008F for <rtcweb@ietfa.amsl.com>; Tue, 13 May 2014 05:00:56 -0700 (PDT)
X-Quarantine-ID: <8o7xM55X5MXu>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -4.429
X-Spam-Level:
X-Spam-Status: No, score=-4.429 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_HI=-5, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, STOCK_IMG_CTYPE=0.001] autolearn=ham
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 8o7xM55X5MXu for <rtcweb@ietfa.amsl.com>; Tue, 13 May 2014 05:00:53 -0700 (PDT)
Received: from mailout3.samsung.com (mailout3.samsung.com [203.254.224.33]) by ietfa.amsl.com (Postfix) with ESMTP id 164C31A008E for <rtcweb@ietf.org>; Tue, 13 May 2014 05:00:52 -0700 (PDT)
Received: from epcpsbgr3.samsung.com (u143.gpu120.samsung.co.kr [203.254.230.143]) by mailout3.samsung.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0N5I003SQHD8APD0@mailout3.samsung.com> for rtcweb@ietf.org; Tue, 13 May 2014 21:00:44 +0900 (KST)
Received: from epcpsbgx2.samsung.com ( [172.20.52.124]) by epcpsbgr3.samsung.com (EPCPMTA) with SMTP id 03.BA.11120.C6902735; Tue, 13 May 2014 21:00:44 +0900 (KST)
X-AuditID: cbfee68f-b7eff6d000002b70-a3-5372096cdb04
Received: from epmailer01 ( [203.254.219.141]) by epcpsbgx2.samsung.com (EPCPMTA) with SMTP id 08.66.20075.C6902735; Tue, 13 May 2014 21:00:44 +0900 (KST)
Message-id: <18.66.20075.C6902735@epcpsbgx2.samsung.com>
Date: Tue, 13 May 2014 12:00:44 +0000 (GMT)
From: Kiran Kumar Guduru <kiran.guduru@samsung.com>
To: Martin Thomson <martin.thomson@gmail.com>, Eric Rescorla <ekr@rtfm.com>
MIME-version: 1.0
X-MTR: 20140513114738324@kiran.guduru
Msgkey: 20140513114738324@kiran.guduru
X-EPLocale: en_US.windows-1252
X-Priority: 3
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale:
X-EPHeader: ML
X-EPTrCode:
X-EPTrName:
X-MLAttribute:
X-RootMTR: 20140513114738324@kiran.guduru
X-ParentMTR:
X-ArchiveUser:
X-CPGSPASS: N
MIME-version: 1.0
Content-type: multipart/related; boundary="=_NamoWEC-8eldb02oi2"
X-Generator: Namo ActiveSquare 7 7.0.0.45
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBKsWRmVeSWpSXmKPExsWyRsSkRjeHsyjYYNlZbYu1/9rZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8WXzfOaCc9sYK+5uncDYwHh5I2MXIyeHkIC6xIbV99hAbAkB E4nTu7+yQ9hiEhfurQeKcwHVLGWUWPPkCCNM0etVnVCJOYwSP+cuBkvwClhIvF/yihnEZhFQ lVj/5w7YVDaghl8n1oDVCAuYSqzcvhfMFhEIlHg/bRrYNmaBCIn7556wQFykJLH26k1WiJmC EidnQsQlgGbef7qFGSKuJnHg/Uqoq+Uklky9zARh80rMaH/KAhOf9nUNM4QtLXF+1gZGmM8W f38MFeeXOHZ7B1AvB1jvk/vBMGN2b/4CNV5AYuqZg4wQJVoSS3dwQ4T5JNYsfMsCM2XXqeXM MK33t8xlQnc9s4CTxNS/HdCw1ZR4tKiVZQKj8iwkZehsmBYI21Diy7zHjBC2osSU7odQcTuJ y9cusGCKq0r0rN7HuICRYxWjaGpBckFxUnqRsV5xYm5xaV66XnJ+7iZGYPI5/e9Z/w7Guwes DzFWAWNtIrOUaHI+MHnllcQbGpsZWZiamBobmVuaUUVYSZz3/sOkICGB9MSS1OzU1ILUovii 0pzU4kOMTBycUg2Min+D9yaz+Ll68Pw/nb18b7bAoomFDh+Wdk3Yf8IosyfNM4G3kvPbvX// dn0vd3y/c3nVhE6Zwkjnzrov7Mo+ipvNrle8/au+Snu6++Pm7CXpsjUrzrA90wxzmTC9d8n0 6zNSKpiur9q7+/TNtt4zfIuWLrn36f2TymUHdv6tUr7F8Ovlv2OGk5RYijMSDbWYi4oTAeLk RUtrAwAA
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIJsWRmVeSWpSXmKPExsVy+t/tXt0czqJgg+dbVCzW/mtnd2D0WLLk J1MAY1SaTUZqYkpqkUJqXnJ+SmZeuq2Sd3C8c7ypmYGhrqGlhbmSQl5ibqqtkotPgK5bZg7Q VCWFssScUqBQQGJxsZK+nU1RfmlJqkJGfnGJrVK0obmRnpGBnqmRnqFprJWhgYGRKVBNQlrG l83zmQvObWOsuLt1AmMD4+WNjF2MnBxCAuoSG1bfYwOxJQRMJF6v6oSyxSQu3FsPZHMB1cxh lPg5dzFYA4uAqsT6P3fAitiAGn6dWAMWFxYwlVi5fS+YLSIQKPF+2jR2EJtZIELi/rknLBDL lCTWXr3JCmLzCghKnJwJEZcAmnn/6RZmiLiaxIH3K6GOkJNYMvUyE4TNKzGj/SkLTHza1zXM ELa0xPlZGxhhjl78/TFUnF/i2O0dQL0cYL1P7gfDjNm9+QvUeAGJqWcOMkKUaEks3cENEeaT WLPwLQvMlF2nljPDtN7fMpcJ3fXMAk4SU/92sEPUaEo8WtTKMoFRdhaSMnQ2TAuEbSjxZd5j RghbUWJK90OouJ3E5WsXWDDFVSV6Vu9jXMDIsYpRNLUguaA4Kb3CSK84Mbe4NC9dLzk/dxMj ONU9W7SD8d9560OMAhyMSjy8C54VBAuxJpYVV+YeYlQBmvNow+oLjFIsefl5qUoivO6fCoOF eFMSK6tSi/Lji0pzUosPMU5kBEb4RGYp0eR8YILOK4k3NDYxNzU2tTAwNDc3o6Wwkjiv/K2k ICGB9MSS1OzU1ILUIpijmDg4pRoY3afopHkyCn5IKaxwLpi6uPbhohBX6yqd29LXf0eE2R9R mLe5zP2McYVPbP2j4zJsdnsCUratqH62tOGE0QbrEi3G6hyuzwnBD/KvLp4hW7C+lMHb35t/ 6pdsP4lMp2WBQeHhM/k6AwUuz5nKX9BZXn/03nf1JV/n3ePQ7Ejo2aKtdb3YKlaJpTgj0VCL uag4EQBRzg+e9AMAAA==
DLP-Filter: Pass
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/58ooS8007HalBCGGhhQnPxKaQPA
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
Reply-To: kiran.guduru@samsung.com
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: Tue, 13 May 2014 12:00:56 -0000

Samsung Enterprise Portal mySingle

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

 

On 11 May 2014 17:18, Eric Rescorla 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.

 

 

 

http://ext.samsung.net/mailcheck/SeenTimeChecker?do=54e220b2ece3918fbbaf790bc353b18318cc31e4135c5f6a52ccaaa5e78d7917a586a8c99dfbfbab0edbe683c853fe71db9fdddda33e82cbe4a391424e62fcf6cf878f9a26ce15a0" border="0" width="0" height="0">