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

I will answer the email at AVTCORE about the IDENTICAL vs TRANSPORT, but not really sure what is the interoperability issue here.

This is my understanding:

- browsers will support receiving cryptex on all m-lines, so they will add the `cryptex` attribute on all m-lines of all bundles.
- browsers will always try to send cryptex if the other end supports cryptex (there is no api for controlling this).
- browsers will throw an exception on setRemoteDescription if the `RTCConfiguration.rtpHeaderEncryptionPolicy` is `require` and the other end does not support cryptes on any bundle.

In which case we will need to reject the SDP above? and what do we mean by "rejecting" in this case?

GitHub Notification of comment by murillo128
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 16 December 2021 15:25:22 UTC