Re: [webrtc-extensions] RTP Header Extension Encryption (#47)

@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 using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 6 January 2022 02:34:32 UTC