W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2012

JSEP-01: Release of non-needed ICE candidates

From: Christer Holmberg <christer.holmberg@ericsson.com>
Date: Wed, 15 Feb 2012 15:26:30 +0100
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D87E29E@ESESSCMS0356.eemea.ericsson.se>


Assume my SIP JS app gets an offer, and some ICE candidatates, generates and sends a SIP SDP offer.

Later, the browser provides additional ICE candidates (using the ice callback function).

My SIP JS app is not interested in the additional ICE candidates.

Q1: Is it possible for the JS app to inform the browser that it does not need the additional ICE candidates? For example, if my app is given turn candidates, which I am not going to use (read: offer to the remote party), there is really no need for the browser to maintain the connection with the turn server.

Q2: Do we assume that the browser at some point (e.g. when the associated answer is provided) will be able to release resources associated with non-needed ICE candidates?


Received on Wednesday, 15 February 2012 14:26:55 UTC

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