[webrtc-pc] RTCPeerConnectionIceErrorEvent should not expose STUN reason phrase to JS (#3052)

fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCPeerConnectionIceErrorEvent should not expose STUN reason phrase to JS ==
https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnectioniceerrorevent-errortext
says the browser should use the reason phrase from the STUN packet. Which on the network looks like this:
![Image](https://github.com/user-attachments/assets/27f09cf0-9f8b-4007-8e26-a2b8acca766b)

This is basically a sidechannel that takes data from the network and exposes it to Javascript - note that this STUN packet is not authenticated.

I haven't seen much actual use for the phrase  so would propose to change the definition to errorText should *not* be taken from the reason phrase.
From what I can see Firefox does not implement onicecandidateerror and Safari's implementation seems dysfunctional

cc @alvestrand 

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3052 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 3 June 2025 16:01:08 UTC