Re: W3C Web Crypto WG - our call today @ 20:00 UTC

On Mon, Jan 27, 2014 at 9:29 AM, Jim Schaad <ietf@augustcellars.com> wrote:

> Mark,
>
>
>
> How many of these are currently documented in the current editors draft?
>

If it's RESOLVED then the current Editor's Draft (24 January) contains the
editor's proposed resolution.

...Mark



>
>
> *From:* Mark Watson [mailto:watsonm@netflix.com]
> *Sent:* Monday, January 27, 2014 8:24 AM
> *To:* GALINDO Virginie
> *Cc:* public-webcrypto@w3.org; wseltzer@w3.org; hhalpin@w3.org
> *Subject:* Re: W3C Web Crypto WG - our call today @ 20:00 UTC
>
>
>
> All,
>
>
>
> To assist discussion on the 15 pre-LC bugs, and since bugs are not (yet)
> copied to the mailing list, here is their current status:
>
>
>
> *Bug 19416* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=19416> -
> KeyUsage should be explicitly spelled out as an enforced parameter
>
>
>
> RESOLVED FIXED according to the discussion in Shenzhen.
>
>
>
> *Bug 24056* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=24056> -
> Algorithms supporting encrypt/decrypt should also support wrap/unwrap
>
>
>
> RESOLVED FIXED according to the discussion in Shenzhen.
>
>
>
> *Bug 22677* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22677> -
> wrapKey requires encrypt key usage
>
>
>
> RESOLVED FIXED based on list discussion.
>
>
>
> *Bug 20611* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20611> -
> Specify the text encoding for JWK key format
>
>
>
> OPEN - awaiting reply from Ryan
>
>
>
> *Bug 23954* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23954> -
> Please specify RsaOaepParams label semantics
>
>
>
> RESOLVED INVALID
>
>
>
> *Bug 23498* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23498> -
> Should the nonce, IV, and associated data be separated?
>
>
>
> RESOLVED INVALID based on the response from Ryan on the list, which
> received no replies.
>
>
>
> *Bug 19705* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=19705> -
> Default value of keyUsage is not very useful
>
>
>
> RESOLVED FIXED (defaults are removed)
>
>
>
> *Bug 22570* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22570> -
> AES-GCM should provide distinct inputs/outputs for the tag
>
>
>
> OPEN
>
>
>
> *Bug 21435* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21435> -
> Specify whether algorithm parameters are required for AES CBC & CTR
> importKey
>
>
>
> RESOLVED WORKSFORME (this bug was raised and closed by me with no other
> comments)
>
>
>
> *Bug 23831* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23831> - add
> HMAC-SHA1 to the list of recommended algorithms
>
>
>
> OPEN
>
>
>
> *Bug 23445* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23445> - typo
> with BigInteger?
>
>
>
> OPEN - I will make a proposal for this before the meeting
>
>
>
> *Bug 23500* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23500> - Raw
> AES access?
>
>
>
> OPEN - list discussion:
> http://lists.w3.org/Archives/Public/public-webcrypto/2014Jan/0029.html
>
>
>
> *Bug 23729* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23729> - Key
> usages future compatibility
>
>
>
> OPEN - agreed to switch to DOMStrings in Shenzhen, I believe
>
>
>
> *Bug 23503* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23503> -
> Should algorithms (ECC in particular) be extensible?
>
>
>
> OPEN - discussed on list. I believe we already have the requested
> extensibility. Propose WORKSFORME.
>
>
>
> *Bug 23495* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23495> -
> Should an informative note mention that entropy is expected? (and an error
> defined ?)
>
>
>
> OPEN - discussed on list. Propose WORKSFORME.
>
>
>
> ...Mark
>
>
>
>
>
> On Mon, Jan 27, 2014 at 7:40 AM, GALINDO Virginie <
> Virginie.GALINDO@gemalto.com> wrote:
>
> Hi all,
>
>
>
> As announced, our call will be maintained today at 20:00 UTC.
>
>
>
> The suggested agenda is :
>
> -          Welcome
>
> -          Bug/issue review of Web Crypto API
>
> -          Identifying the LC date
>
> -          Discussing the hardware token workshop
>
> -          AOB [please add your suggestion]
>
>
>
> To join, use the following channels :
>
> Bridge : +1.617.761.6200, 27978# (CRYPT)
> IRC channel :  irc.w3.org:6665 #crypto
>
>
>
> Talk to you soon.
>
> Virginie
>
> Gemalto
>
> Chair of the web crypto WG
>
>
>
>
> ------------------------------
>
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus
>
>
>