- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 May 2020 16:27:45 +0000
- To: public-webrtc-logs@w3.org
the e2ee key is exchanged in a different path than sfu signaling, so it may be updated on the sender shortly after the new participant has joined and the sfu jas already requested the key frame. Updating the key on a key frame makes a lot of sense to me. Anyway, I am always in favor of more APIs that allow lower level control of the underlaying objects. Do you foresee any way this API could cause any issue to existing code? El jue., 14 may. 2020 18:17, Iñaki Baz Castillo <notifications@github.com> escribió: > Let me insist, please. What is this API needed for? And if the answer is > e2ee, why? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-628739263>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIFN43V35GF5LLGQSVQW43RRQKQDANCNFSM4M63A53A> > . > -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-628745687 using your GitHub account
Received on Thursday, 14 May 2020 16:27:47 UTC