- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Mar 2025 18:19:57 +0000
- To: public-webrtc-logs@w3.org
From trying to experimentally enable PQC in Chromium/WebRTC it looks like we might want to expose the TLS group id as defined in https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-8 in webrtc stats similar to https://w3c.github.io/webrtc-stats/#dom-rtctransportstats-dtlscipher (which is a string)? The numeric id, e.g. 4588 for X25519MLKEM768 should be sufficient, resolving that to the IANA string seems a bit of a hassle. @Frosne would that work from the NSS side too? How to opt in remains a good question, by default boringssl generated a key share which has impact on the size of the handshake which is going to be a headache. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/207#issuecomment-2755382519 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 March 2025 18:19:58 UTC