- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jun 2021 15:22:35 +0000
- To: public-webrtc-logs@w3.org
I'm slowly making progress on enabling this together with @ricea. The idea is that WebRTC would at some point hook into https://fetch.spec.whatwg.org/#concept-connection-obtain (or perhaps something lower-level as mt points out above), with parameters that make sense for it. That would then take care of any domain resolving (if needed) and setting up and returning a connection. My hope is that we can also move some other logic there, such as port blocking, what `localhost` means, etc. (I think since mt's comment above implementations have reached agreement on sharing port blocking logic across HTTP/WebRTC/WebTransport connections, with the exception of one or two ports that are safelisted for WebRTC use.) -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/73#issuecomment-863332885 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 June 2021 15:23:04 UTC