W3C

- DRAFT -

Web Cryptography Working Group Teleconference

16 Nov 2015

See also: IRC log

Attendees

Present
virginie, wseltzer, jimsch, MikeJones
Regrets
markw
Chair
Virginie
Scribe
wseltzer

Contents


<trackbot> Date: 16 November 2015

virginie: MarkW sent regrets
... objective to get status, timeline
... timeline

<virginie> - 16/11 we gather feedback from the WG on PR readiness - we give editors 2 weeks to finalize - we meet on 30/11 and get PR consensus on the final text - we have a 2 weeks validation/objection period - we kickoff PR->CR on the 14 of dec

you mean CR->PR

<virginie> tests : https://diafygi.github.io/webcrypto-examples/

virginie: I'd like to have someone else review the tests

<virginie> Note : those tests lead to the report by Harry http://www.w3.org/2012/webcrypto/CR-report/

https://github.com/diafygi/webcrypto-examples/blob/master/index.html

virginie: I want it to be clear in the test report that we're only testing presence of API, not the correctness of its crypto implementation
... we're still discussing maintenance mode, in which we put other algorithms into a note for now, to be moved to API later

jimsch: do you have documents for 2 new algorithms?

virginie: we'll put it into note

<jimsch> The two new EC key agreement curves

virginie: we don't have that yet

<virginie> note : action to check when IANNA needs to be informed about the web crypto

MikeJones: you want to send to IANA when it's final; though you can update the registration later

<virginie> - 16/11 we gather feedback from the WG on PR readiness - we give editors 2 weeks to finalize - we meet on 30/11 and get PR consensus on the final text - we have a 2 weeks validation/objection period - we kickoff CR->PR on the 14 of dec

<virginie> http://www.w3.org/2015/Process-20150901/#rec-pr

jimsch: it makes sense to send to IANA when the group concludes it's done

<virginie> note : the process mentions a minimum of 28 days for AC review to happen

MikeJones: RFC 7518, send to jose-reg-review@ietf.org

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/11/16 21:03:35 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/PR->CR/CR->PR/
No ScribeNick specified.  Guessing ScribeNick: wseltzer
Inferring Scribes: wseltzer

WARNING: No "Topic:" lines found.

Present: virginie wseltzer jimsch MikeJones
Regrets: markw
Found Date: 16 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/16-crypto-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]