- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2020 17:08:22 +0000
- To: public-webrtc@w3.org
aboba has just created a new issue for https://github.com/w3c/webrtc-extensions: == RTP Header Extension Encryption == Justin Uberti did a presentation in AVTCORE today about the status of RTP Header Extension support in WebRTC: https://www.ietf.org/proceedings/108/slides/slides-108-avtcore-rtp-header-extension-encryption-full-01 Current WebRTC implementations (both browsers and SFUs) do not support the negotiation envisaged in RFC 6904, which appears too complex to implement properly. The result has been leaking of RTP header extensions including audio levels), due to bugs in libsrtp and libwebrtc that remained undetected for years. This has lead to discussions of how we can make RTP header extension encryption deployable from a protocol and API standpoint. With respect to APIs, two approaches have been suggested: 1. Add an argument to `setOfferedRtpHeaderExtensions` to indicate whether all the extensions should be encrypted (the default) or not. 2. Add a member to RTCConfiguration: 'negotiate' or 'require' Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47 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 17:08:28 UTC