- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2020 17:44:27 +0000
- To: public-webrtc-logs@w3.org
I'd prefer the former. The one thing I believe is really important is that we do have the two options: * `negotiate` (default) which indicates that it will try to negotiate encryption for all header extensions and silently fall back to sending and receiving non-encrypted header extensions in case it couldn't negotiate encryption for them. From a technical perspective, something like `a=encrypted-hdrs:optional` would be sent from the local side and if the remote side sends either `a=encrypted-hdrs:optional` or `a=encrypted-hdrs:required`, **both encrypt. Otherwise, they both send the extensions in plaintext.** * `require` which indicates that it will only send encrypted header extensions or none at all. From a technical perspective, something like `a=encrypted-hdrs:required` would be sent from the local side and if the remote side sends either `a=encrypted-hdrs:optional` or `a=encrypted-hdrs:required`, **both encrypt. Otherwise, neither side sends any header extensions.** (Side note: I guess I kinda have suggested a negotiation logic by describing how I think it could work now. So, /cc @juberti) -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-666557349 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 July 2020 17:44:29 UTC