Re: [webrtc-pc] Unclear how URLs are processed (#2660)

FWIW.
STUN and TURN urls are special by the  IETF:
https://www.rfc-editor.org/rfc/rfc7064
https://www.rfc-editor.org/rfc/rfc7065

I am not sure that attempting to fit them into a generic URL scheme is something that should be done at W3C level .
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).

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2660#issuecomment-1493425199 using your GitHub account


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

Received on Sunday, 2 April 2023 19:50:10 UTC