- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Aug 2020 08:18:27 +0000
- To: public-webrtc-logs@w3.org
I think this is a good idea and the location (an object on construction of `RTCPeerConnection`) makes sense there, too. I'm not sure we should complain about the added complexity by it considering what a bag of surprises SDP can be for security if left unfiltered. This API addition is really only a bouncer and I think we should be able to manage that. Heck, perhaps it's even a good idea to be forced to at least virtually untangle `RTCPeerConnection` into the three sections *audio*, *video* and *data* (while obviously *audio* and *video* are technically more close together than *data*). More delicate constraints already exist in other places such as the transceiver API which I think is a good model to follow when it comes to exposing more options in other places (say SCTP settings). -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2561#issuecomment-671223066 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 August 2020 08:18:28 UTC