I think virginie is coming, we can wait the usual obligatory 5 minutes, otherwise I can stand in as replacement chair.

Or I can scribe :)

<scribe> scribe: hhalpin

no worries virginie, I can chair if you can't make it.

<virginie> asling/asking

1-617-324-0000 Access Code: 643 244 026

Welcome

MarkW, Engelke, Joanne

hhalpin: It seems the browser vendors didn't make this call.
... would be good to have them for final PR move

virginie: MarkW is here, so let's go over the remaining bugs

<markw> https://github.com/w3c/webcrypto/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20-milestone%3AVNext%20-label%3A%22needs%20review%22%20-label%3A%22final%20review%22

Remaining bugs

hhalpin: I'll update the algorithm update
... might be a good idea to link test-suite to final Rec so people can check on it - easier to update test-suite than Rec

markw: Key format interop bug, is under discussion
... the CfC will be resolved tomorrow, will check it in tomorrow
... Explicit salts to be added by HKDF
... under debate, optional?
... open question
... jimsch thinks its a bad idea for optional.

hhalpin: Do vendors require salts?

engelke: Let me look through the test-suite, I think it all worked
... was supported by chrome, not by Firefox
... will drop it into an email
... and will comment on the bug

Virginie: Does this require a CfC?

markw: I don't think so

hhalpin: We'll track it to browser behavior

I'll double-check with IANA over registrations and CFRG

It seems Jim's concerns are dealt with EC curves

markw: It seems that ryan wanted to keep Promise<any> not to contrain future development
... note it doesn't effect implementation
... it just needs to be done by WebIDL

virginie: Last CfC over key material formats

<markw> https://github.com/w3c/webcrypto/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20-milestone%3AVNext%20label%3A%22needs%20review%22%20

markw: I have another list

engelke: The salt *is* required, that's how the browsers work now, and if they don't get it they throw an error

markw: OK, can close this issue

virginie: Thank you very much!

I would have a meeting in two weeks, and put forward the CfC for key material now

and then put forward a CfC for PR as soon as that's closed

markw: Two things came to mind
... unwrapping non-extractable key?
... you can't wrap a non-unwrappable key
... but you can UNWRAP one of these if it was created somewhere else

engelke: These tests the conditions all succeed ones, not failure modes
... and I'd need a source for that key

markw: I'll see if I can find a sample key for a test

virginie: the decision to make it a Note did succeed

hhalpin: If you want to do any editorial changes, let's do it
... we can have it clear
... there is a separate Working Group Note
... format, so let's have it go to Note at the same time WebCrypto goes to PR

virginie: I'll send out minutes and we're doing
... Tuesday lunch at TPAC if people are around
... thanks everyone!

trackbot, end meeting

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: hhalpin
Inferring ScribeNick: hhalpin
Default Present: wseltzer, virginie, Tim, Rob, hhalpin, vgb, markw, engelke
Present: wseltzer virginie Tim Rob hhalpin vgb markw engelke
Regrets: wseltzer
Found Date: 12 Sep 2016
Guessing minutes URL: http://www.w3.org/2016/09/12-crypto-minutes.html
People with action items: