- From: <bugzilla@jessica.w3.org>
- Date: Fri, 26 Sep 2014 15:11:05 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25198 --- Comment #6 from Mark Watson <watsonm@netflix.com> --- I think this would make sense for the fields that are not extensible: KeyFormat and KeyType. KeyAlgorithm.name is extensible, though the defined process for registering new algorithms and (unless I am mis-understanding) making it an enum would interact badly with that extensibility point. I believe future specifications could also add new methods to SubtleCrypto, which might come with new algorithms and new KeyUsage values, so I suggest we leave KeyUsage as a DOMString. [Note that we can't use a key generated or imported with an existing algorithm with a new KeyUsage, because the import/generate procedures in the specification are specific about what usages are valid and we have not provided for extensibility on that axis.] -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 26 September 2014 15:11:06 UTC