- From: Web Cryptography Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Thu, 18 Apr 2013 01:05:55 +0000
- To: public-webcrypto@w3.org
crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API]
http://www.w3.org/2012/webcrypto/track/issues/42
Raised by: Richard Barnes
On product: design for Web Crypto API
The current spec requires that algorithm parameters be encapsulated in a "params" field within an algorithm identifier. For example:
OLD: { name: "AES-GCM", params: { iv: [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0], tlen: 128 } }
NEW: { name: "AES-GCM", iv: [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0], tlen: 128 }
The only reason this extra complexity would be necessary is if we expected an algorithm to need a parameter called "name". This does not seem very likely; I see no problem making "name" a reserved word for the purpose of algorithm parameters.
This requires the useless interface "dictionary AlgorithmParameters {};" from which individual algorithms specialize. Proposed revisions to WebIDL:
-- Remove the AlgorithmParameters definition
-- Remove the "AlgorithmParameters params;" from the Algorithm interface
-- Change all descendants of AlgorithmParameters to instead inherit from Algorithm
[Copied from mailing list <http://lists.w3.org/Archives/Public/public-webcrypto/2013Mar/0099.html>]
Received on Thursday, 18 April 2013 01:05:56 UTC