- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Nov 2021 03:32:07 +0000
- To: public-webrtc-logs@w3.org
Based on draft-ietf-avtcore-cryptex, it seems like it works as follows: - An Offer or Answer from a browser supporting cryptex contains `a=cryptex` on all m-lines, indicating the ability to receive Encrypted Header Extensions. - On the Offerer, `RTCRtpTransceiver.encryptionNegotiated` is set to "true" for those m-lines where the Answerer responded with `a=cryptex`. For these m-lines, the Offerer will send Encrypted Header Extensions. - On the Answerer, `RTCRtpTransceiver.encryptionNegotiated` is set to "true" for those m-lines where the Offerer Offered `a=cryptex`. For these m-lines, the Answerer will send Encrypted Header Extensions. - If `RTCConfiguration.rtpHeaderEncryptionPolicy` = "require" on an Offerer, then it will expect `a=cryptex` on all m-lines in the Answer. If not, negotiation will fail. - If `RTCConfiguration.rtpHeaderEncryptionPolicy` = "require" on an Answerer, then it will expect `a=cryptex` on all m-lines in the Offer. If not, negotiation will fail. - If `RTCConfiguration.rtpHeaderEncryptionPolicy` = "negotiate" on an Offerer, then it will expect an Answer with `a=cryptex` present on all m-lines within a BUNDLE, or on no -lines within a BUNDLE. If not, negotiation will fail. - If `RTCConfiguration.rtpHeaderEncryptionPolicy` = "negotiate" on an Answerer, then it will expect an Offer with `a=cryptex` present on all m-lines within a BUNDLE, or on no -lines within a BUNDLE. If not, negotiation will fail. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-968506363 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 November 2021 03:32:09 UTC