- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Apr 2023 23:07:49 +0000
- To: public-webrtc-logs@w3.org
> It is not clear to me why webrtc-pc even tries to specify how to parse those urls. > > These are passed to the "ICE agent" (however, JSEP is silent about this [here](https://datatracker.ietf.org/doc/html/rfc8829#section-4.1.18)). https://w3c.github.io/webrtc-pc/#set-pc-configuration does input validation of the configuration ahead of it to the ice agent, so JSEP doesn't need to. > Neither is it at implementation level where even "easy" things like throwing when a STUN url contains a "?transport" causes web compat issues such as https://github.com/twilio/twilio-video.js/issues/1934. Notably Firefox does not enforce this as [seen on stackoverflow](https://stackoverflow.com/questions/75822672/webrtc-peerconnection-is-not-establishing-in-chrome-and-edge). Thanks for finding that. I think this is a good argument for specifying url validation better, and we should probably fix Firefox here. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2660#issuecomment-1495102715 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 April 2023 23:07:51 UTC