ISSUE-42: Flatten AlgorithmParameters
Flatten AlgorithmParameters
- State:
- CLOSED
- Product:
- design for Web Crypto API
- Raised by:
- Richard Barnes
- Opened on:
- 2013-04-18
- Description:
- 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>] - Related Actions Items:
- No related actions
- Related emails:
- Re: Defaults: Getting concrete (round 2) (from rbarnes@bbn.com on 2013-04-23)
- Re: Defaults: Getting concrete (round 2) (from rbarnes@bbn.com on 2013-04-23)
- Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (from sleevi@google.com on 2013-04-22)
- Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (from watsonm@netflix.com on 2013-04-22)
- Re: PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (from sleevi@google.com on 2013-04-22)
- PROPOSAL for ISSUE-12: Should the API distinguish between algorithm and operation parameters? (from watsonm@netflix.com on 2013-04-22)
- crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] (from sysbot+tracker@w3.org on 2013-04-18)
- Re: crypto-ISSUE-42: Flatten AlgorithmParameters [design for Web Crypto API] (from rbarnes@bbn.com on 2013-04-17)
Related notes:
No additional notes.
Display change log
