W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2017

[webrtc-stats] Add stats for the negotiated DTLS-SRTP and DTLS cipher suites.

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Oct 2017 23:50:18 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-264413624-1507679403-sysbot+gh@w3.org>
taylor-b has just created a new issue for https://github.com/w3c/webrtc-stats:

== Add stats for the negotiated DTLS-SRTP and DTLS cipher suites. ==
Presumably this would go on `RTCTransportStats`. Chrome's non-standard stats implementation included these, with the names "srtpCipher" and "dtlsCipher". They would be `DOMString`s that use cipher suite names defined in RFCs, such as "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA".

Any reason not to do this? It seems like it would actually help in implementing one of the requirements of rtcweb-security-arch:

>    UI Requirements:   A user-oriented client MUST provide an "inspector"
>       interface which allows the user to determine the security
>       characteristics of the media.
>    ...
>       *  The "security characteristics" MUST indicate the cryptographic
>          algorithms in use (For example: "AES-CBC" or "Null Cipher".)
>          However, if Null ciphers are used, that MUST be presented to
>          the user at the top-level UI.

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/248 using your GitHub account
Received on Tuesday, 10 October 2017 23:50:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:47 UTC