W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

Re: new DTLS key for call

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Sun, 18 May 2014 18:37:07 +0000
To: Justin Uberti <juberti@google.com>
CC: public-webrtc <public-webrtc@w3.org>
Message-ID: <D2212582-7BA8-4336-B0F7-E2F2840C1EC8@cisco.com>

SGTM - I probably like the first option best because it sounds easier to get done soon and does not stop the send option later but happy either way. 

On May 18, 2014, at 2:19 PM, Justin Uberti <juberti@google.com> wrote:

> Eric previously mentioned a 'DtlsIdentity' key which could go into RTCConfiguration that, if set to null, would let the app request a fresh key pair. Otherwise, by default a cached key is used.
> 
> Other approaches discussed included generating a key pair from webcrypto and allowing that to be stuffed into the PC.
> 
> 
> On Sun, May 18, 2014 at 11:12 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> 
> How can the JS tell the browser to generate a new DTLS key pair ?
> 
> (Need by section 5.7.2. of draft-ietf-rtcweb-security-arch-09.txt )
> 
> 
> 
> 
Received on Sunday, 18 May 2014 18:37:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:40 UTC