- From: docfaraday via GitHub <noreply@w3.org>
- Date: Fri, 12 Jun 2026 00:05:20 +0000
- To: public-webrtc@w3.org
docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc: == We need to specify a comparison algorithm for RTCIceCandidate == If we want to avoid copies of remote candidates piling up in the return of RTCIceTransport.getRemoteCandidates(), we're going to need to detect duplicates. Even if we say "If you pass dupes to addIceCandidate, you get dupes", that doesn't save us because we also need to incorporate candidates from remote descriptions, which can be set repeatedly. There are lots of ways we could do this. * Do we just string compare the candidate-attribute + ufrag and call it a day? * If we compare only specific fields, which fields are compared? Surely at least ufrag, address, port, protocol, and tcpType. But should we pay attention to others? (type? component? priority?) * How sophisticated should address comparison be? Do we normalize IPv6? Do we normalize weird IPv4 representations? IDNA? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3120 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 June 2026 00:05:21 UTC