- From: Justin Uberti via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Nov 2018 16:56:38 +0000
- To: public-webrtc-logs@w3.org
Yeah, I think there are two different questions here: 1) should it be possible to configure 'enterprise' TURN (or perhaps STUN) servers, used in addition to any application servers. This is what RETURN aimed to solve, but we never got around to fully deciding on this. 2) should it be possible to configure one's own TURN servers, to be used *instead* of the application servers. I don't think this is likely to be workable, as this will violate the assumptions of some applications (who are forcing data onto their own relays for traffic optimization, anonymization, etc) I think @jan-ivar is right in that getDefaultIceServers was an attempt at a cheap compromise, and while I think the [minutes](https://www.w3.org/2015/10/29-webrtc-minutes) are pretty clear that it requires application participation, I would not be surprised if not everyone had the same interpretation. Anyway, to make a long story short, my position is that getDefaultIceServers doesn't provide much value, and while I think we should solve 1) in the future, we should be able to do so without a JS-exposed API. -- GitHub Notification of comment by juberti Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2023#issuecomment-438736042 using your GitHub account
Received on Wednesday, 14 November 2018 16:56:40 UTC