W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > November 2016

Re: [webrtc-pc] STUN/TURN Auto Discovery handling

From: misi via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 Nov 2016 10:18:43 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-262476702-1479896321-sysbot+gh@w3.org>
@aboba I am not sure about pc.defaultIceServers is the right solution,
 

IMHO it is not really enough to inform the  WebApp/App about a new 
TURN server discovery through change of pc.defaultIceServers. 
This way, the App needs to monitor changes of pc.defaultIceServers to 
detect a new server discovery.

IMHO it is important to inform App that a new TURN server uri has 
discovered.
Furthermore important that discovery normally not contains any 
credential, for the TURN server.
So the newly discovered TURN server may not usable without a 
credential, and this way we need to trigger the app to request a 
credential for this (IP/FQDN) TURN server.

- IMHO an event would better to inform App after a network change has 
occurred that a TURN client discovered with anycast/dns etc a new TURN
 server.
- I think inform the App as a new event is more appropriate
  - and app could decide if that this server/IP is trusted/appropriate
 to use or not, 
  - and get credential for this TURN server
    - may ask for credential from an external "TURN service Auth 
server" 
  - and after it, configure the TURN server and with the requested 
credential to the PC on the usual way.


-- 
GitHub Notification of comment by misi
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/941#issuecomment-262476702 
using your GitHub account
Received on Wednesday, 23 November 2016 10:18:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:41 UTC