- From: Justin Uberti via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2020 19:55:13 +0000
- To: public-webrtc-logs@w3.org
I'm not sure we want to extend `setOfferedRtpHeaderExtensions`, because we're talking about encrypting more than just extensions. I'd suggest a new member, e.g., `rtpHeaderEncryptionPolicy`. Regarding the difference between 1. `RtpTransceiver.rtpHeaderEncryptionPolicy` and 2. `RTCConfiguration.rtpHeaderEncryptionPolicy` the main difference is that 1) needs to be done for every transceiver, which while providing more control, is easier to get wrong. -- GitHub Notification of comment by juberti Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-666647226 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 July 2020 19:55:15 UTC