- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 31 Dec 2019 10:41:01 +0000
- To: public-webrtc-logs@w3.org
Is the solution suggesting that either `icecandidateerror` is unreliable or some ports are unusable? If yes, there are multiple issues with it: * It's not deterministic, * it's not testable, * it's brittle because `icecandidateerror` may or may not fail, so relying on it is useless, * it's brittle because it arrogates to know which ports are okay and which aren't, * it still allows for fingerprinting. I believe that's a deep rabbit hole. I'd suggest getting rid of `icecandidateerror` instead. We can live without it. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2425#issuecomment-569907228 using your GitHub account
Received on Tuesday, 31 December 2019 10:41:02 UTC