AFAIK Firefox prefers AES GCM by default. Chrome still puts it at the bottom of the negotation list (for whatever reason) even when opting in but I think there's a CL for that - just can't find it. @fippo will know for sure. But in any case, there's nothing the W3C should do about this. IMO this is an IETF and implementation matter. But I agree, we should push for AES GCM by default. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2551#issuecomment-651642017 using your GitHub accountReceived on Tuesday, 30 June 2020 08:29:55 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:51 UTC