- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Jun 2021 14:58:19 +0000
- To: public-webrtc-logs@w3.org
Agreed. We're still in the process of ensuring Fetch, WebSocket, and WebTransport are aligned and it might make sense that WebRTC only reuses some aspects. I'd love to chat once we're closer. Here are the things that come to mind with regards to sharing: * Keying. Any kind of cache and connection pooling should take into account the network partition key. * Port blocking. While not currently the case, it's our plan to enforce this while obtaining a connection. * Proxies. It would be ideal that if there's a proxy and it doesn't do UDP, the browser doesn't attempt to do UDP. (To be clear, this could use input. It's not clear how realistic this is.) * CSP. I think it would make sense if part of CSP was enforced here. * online/offline events. These events are somewhat problematic as they fire around the same time across tabs, creating a cross-site communication channel and privacy leak. It would be better if they only fired after the global state change once a tab is focused by the user. However, unless we also make and enforce the state per tab, this would be meaningless. (It's still somewhat tricky to avoid leaks entirely in the going offline case, but I think we can improve on the status quo at least.) -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/73#issuecomment-867704886 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 June 2021 14:58:31 UTC