- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Sat, 29 Nov 2014 23:57:36 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
[BA] Assuming this relates entirely to the behavior of SDP within the WebRTC 1.0 API and not to any browser capability, I am going to close this issue. Peter Thatcher said: "The browser should always support trickle ICE, right, so there's no capability needed (since it would always be true anyway). For WebRTC 1.0, this is to control whether the SDP generated does trickle or not (ie whether it waits for all the candidates before sending an offer). But that is something that could be done completely in JS on top of ORTC. I don't think ORTC needs to add anything. I think Martin is right about this." Bernard Aboba said: "Maybe I don't understand the purpose of 'canTrickleIceCandidates' in the WebRTC 1.0 API. My impression was that this was to enable an application to understand whether the browser supports Trickle ICE. In WebRTC 1.0 this would be communicated via SDP; however if it was desired to build a WebRTC 1.0 shim on top of ORTC, wouldn't ORTC also need an equivalent capability?" Martin Thomson said: "An API like this doesn't need to include canTrickleIceCandidates, which is a property derived from parsing SDP for the most part."
Received on Saturday, 29 November 2014 23:58:09 UTC