This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22642 - Operations InputKey/ExportKey do not have parameters listed for the various algorithms
Summary: Operations InputKey/ExportKey do not have parameters listed for the various a...
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-11 05:00 UTC by jimsch
Modified: 2013-07-22 19:29 UTC (History)
1 user (show)

See Also:

Attachments

Description jimsch 2013-07-11 05:00:03 UTC 
Current algorithms defined do not have the Parameters and Result listed in the various tables.
Comment 1 Ryan Sleevi 2013-07-22 19:29:48 UTC 
Tentatively resolved in https://dvcs.w3.org/hg/webcrypto-api/rev/5cf8db70af2e

However, as described in the commit note, further normative text in the algorithm-specific considerations is needed. The only time there are specific parameters for importKey are the case of HMAC.

Though exportKey takes no parameters, it also requires algorithm-specific descriptions (eg: how the SPKI for an RSA public key is extracted, or what the form of the resulting JWK is)

With the exception of JWK, the other key formats "should" be obvious - in that SPKI and PKCS8 representations for RSA, ECDH are known (RFC 5208, RFC 5915). DH is trickier - I can't find any good reference for the PKCS8 form, although RFC 3279 describes the SPKI form.