- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Sun, 14 Nov 2021 19:53:39 +0000
- To: public-webrtc-logs@w3.org
["Completely Encrypting RTP Header Extensions and Contributing Sources"](https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-cryptex) has completed WGLC and is now in state "AD Review". The basics of an API proposal were discussed [here](https://docs.google.com/presentation/d/14Bzs1ia23Q5yGcuPLiQnHvkjjFi9ypXgPue94Q65UIQ/edit#slide=id.g9228bfd0b2_3_21). - All-or-nothing encryption. - Encrypt RTP headers on all m= sections or none of them. - Always attempt to negotiate it. - Add RTCConfiguration.rtpHeaderEncryptionPolicy - "negotiate": If other endpoint doesn’t support it, send unencrypted. - "require": If the other endpoint doesn’t support it, fail to negotiate (throw an exception on setRemoteDescription). - Add RTCRtpTransceiver.encryptionNegotiated flag. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-968353065 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 14 November 2021 19:53:42 UTC