- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Mar 2018 18:57:47 +0000
- To: public-webrtc-logs@w3.org
My idea was for these fields to go on `RTCIceCandidateStats`, only for "local-candidate"s. I hadn't considered the case of multiple STUN servers producing the same server reflexive address. Though this wouldn't be a new problem. `RTCIceCandidateStats` has a `url` field, which is "**The** URL of the TURN or STUN server that translated this IP address". So it assumes every candidate is associated with at most one server. The "candidate gathered" event has a [URL field like this](https://www.w3.org/TR/webrtc/#dom-rtcpeerconnectioniceevent-url) too. So, the spec seems to assume that the implementation will choose one STUN server for each srflx candidate. I know Chrome will just go with the first one that responds. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/339#issuecomment-371245694 using your GitHub account
Received on Wednesday, 7 March 2018 18:57:51 UTC