- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Nov 2021 12:54:29 +0000
- To: public-webrtc-logs@w3.org
I am not sure I understand why "a=cryptex" isn't session-level rather than media level. If an endpoint supports receiving and decrypting cryptex, then it should be able to handle receiving it on any m-line. The above example would most likely be a gateway that fronts a legacy video system that doesn't support cryptex. But in that scenario, why can't the gateway decrypt cryptex and pass it along to the legacy video system in cleartext? -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-968881992 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 12:54:31 UTC