while profiling webrtc, I noticed quite a lot of (relative) cpu time is spent in srtp protect/unprotect. This mostly is due to the fact that libsrtp is using its own C implementations of AES and SHA-1. As libsrtp on GitHub (https://github.com/cisco/libsrtp
) supports using OpenSSL (optimized with AES-NI and assembler implementations), it probably would make sense to also change that to BoringSSL in the libsrtp that is used by webrtc.
Is this already planned, and if not would you accept CLs for this? Where should they go?