- From: sirzooro via GitHub <noreply@w3.org>
- Date: Sat, 28 Feb 2026 12:09:37 +0000
- To: public-webrtc-logs@w3.org
> Another nit: > > > if the connection's RTCRtpHeaderEncryptionPolicy is require and the description does not support [RFC9335] > > is a bit vague, might need to be clarified that cryptex is 1/ at session level and / or 2/ present for all RTP-based "m=" sections (borrowed from the RFC) This point is unclear. Discussion above was focused on media-level attribute, giving impression that this is the preferred way. However `RTCRtpHeaderEncryptionPolicy` affects whole WebRTC session, so session-level attribute seems better over media-level ones. WebRTC peer could still support media-level attribute as a fallback for interoperability with non-browser peers which needs more granular control for some reason. -- GitHub Notification of comment by sirzooro Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-3977079487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 February 2026 12:09:38 UTC