- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jan 2022 02:34:31 +0000
- To: public-webrtc-logs@w3.org
@murillo128 @alvestrand From the conversation on the AVTCORE mailing list, it seems like the proposed API is workable, no? Where `RTCConfiguration.rtpHeaderEncryptionPolicy` = "require" the browser can throw an exception on setRemoteDescription() if the other end does not support receiving cryptex an on any bundle. Where `RTCConfiguration.rtpHeaderEncryptionPolicy` = "negotiate", the browser must not send cryptex on any bundle without "a=cryptex" (e.g. the Offer Harald describes needs to be accepted by the browser). This would be the case whether "a=cryptex" is IDENTICAL or TRANSPORT. The browser will respond to the mixed Offer with an Answer containing "a=cryptex" on every m-line. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-1006237012 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 January 2022 02:34:32 UTC