W3C home > Mailing lists > Public > public-webcrypto@w3.org > April 2013

Re: crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API]

From: Richard Barnes <rbarnes@bbn.com>
Date: Wed, 17 Apr 2013 21:07:12 -0400
Message-Id: <CA482211-E0AA-41A4-BD9A-FC14BFFDF6A5@bbn.com>
To: Web Cryptography Working Group <public-webcrypto@w3.org>
This is the same as an earlier thread:
<http://lists.w3.org/Archives/Public/public-webcrypto/2013Mar/0099.html>

Just submitted as an issue to facilitate tracking, since I don't see a fix in the current ED.

--Richard


On Apr 17, 2013, at 9:05 PM, "Web Cryptography Working Group Issue Tracker" <sysbot+tracker@w3.org> wrote:

> 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:07:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:16 UTC