- From: David Dahl <ddahl@mozilla.com>
- Date: Mon, 5 Nov 2012 08:59:25 -0800 (PST)
- To: Ryan Sleevi <sleevi@google.com>
- Cc: public-webcrypto <public-webcrypto@w3.org>, Arun Ranganathan <arun@mozilla.com>, Mark Watson <watsonm@netflix.com>, Harry Halpin <hhalpin@w3.org>
----- Original Message ----- > From: "Ryan Sleevi" <sleevi@google.com> > To: "Mark Watson" <watsonm@netflix.com> > Cc: "<public-webcrypto@w3.org>" <public-webcrypto@w3.org>, "David Dahl" <ddahl@mozilla.com>, "Arun Ranganathan" > <arun@mozilla.com> > Sent: Sunday, November 4, 2012 1:44:16 AM > Subject: Re: Rethinking KeyStorage > ... > I should note that postponing would also provide Netflix and other > implementers the opportunity to experiment with various approaches to > the problem, and will likely lead to a better, more implementable > solution than if this WG were to attempt to spec something up front > that may not be implemented for quite some time. > Perhaps, as the result of such experimentation, we could link to an "Editor's Note" in the spec that explains how a set of pre-provisioned keys might be implemented? This is something of a half-measure, (and speaking out of ignorance) but I understand that this is sometimes done in the case of features that the spec does not include, but some implementations find necessary. Regards, David
Received on Monday, 5 November 2012 16:59:53 UTC