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 27815 - IANA Considerations for "ext"
Summary: IANA Considerations for "ext"
Status: RESOLVED MOVED
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: 2015-01-12 20:38 UTC by jimsch
Modified: 2016-05-24 00:28 UTC (History)
2 users (show)

See Also:

Attachments

Description jimsch 2015-01-12 20:38:20 UTC 
Consider this to be an early IANA considerations review.

There is sufficient information in the document to understand what the "ext" parameter is to be used for and how it is encoded.  However it would be nice if there was a single location where this information was placed for easy reference.  I would like the to see the following paragraph (or similar) added to section 38.2 (December draft).

The "ext" parameter is used to indicate if, after importing a key into the system, a subsequent export of the key is to be allowed.  The type associated with this parameter is a Boolean.  There is no default behavior defined for this parameter.
Comment 1 Mark Watson 2016-05-24 00:28:22 UTC 
Moved to https://github.com/w3c/webcrypto/issues/78