- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Mon, 30 Jun 2025 13:22:07 +0000
- To: public-webrtc-logs@w3.org
This also needs some thought what the deployment model is going to be. I assume this is going via some load balancer in front of the server whose CA-signed certificate will be different from the servers (typically) self-signed certificate. This makes "gathering" the candidate a bit more involved for the server and there might be multiple load balancer IPs which map to multiple candidates. Not as simple as TURNs with round-robin DNS or colocating TURNs and the server but might be worth the effort. Verification via SAN dNSName as described in https://www.rfc-editor.org/rfc/rfc9525 should be straightforward. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/236#issuecomment-3019141034 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 June 2025 13:22:09 UTC