- From: Cullen Jennings (fluffy) <fluffy@cisco.com>
- Date: Mon, 19 Dec 2016 20:37:34 +0000
- To: Tim Panton <thp@westhawk.co.uk>
- CC: WebRTC WG <public-webrtc@w3.org>, Harald Alvestrand <harald@alvestrand.no>
> On Dec 19, 2016, at 10:27 AM, T H Panton <thp@westhawk.co.uk> wrote: > > >> On 19 Dec 2016, at 16:52, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: >> >> I'd like to be able to know what crypto the DTLS is using - some future browser will negotiate stuff that is INHO less secure than what the IETF specified and I'd like my javascript to be able to see that. > > That doesn't feel like a stats thing... Perhaps it belongs on the RTCDtlsTransport . > Unless the crypto will change value more often than the RTCDtlsTransport will change state ? > > T. I don't really have any strong opinions on where in the API I should get it just as long as there is a way. But, I agree it sounds like better as an attribute of Transport. I guess a a rough guideline, things that don't change probably are mostly not appropriate for stats.
Received on Monday, 19 December 2016 20:38:17 UTC