19:44:04 RRSAgent has joined #crypto 19:44:04 logging to http://www.w3.org/2015/11/30-crypto-irc 19:45:22 wseltzer has changed the topic to: Meeting Nov 30, 2000 UTC (3pm Boston) 19:50:29 hhalpin has joined #crypto 19:50:32 me waves 19:50:48 jimsch has joined #crypto 19:56:39 hhalpin has joined #crypto 19:56:58 Charles_Engelke has joined #crypto 19:58:29 I cannot appear to logon and get the password for the conference call 19:58:46 Jim - http://www.w3.org/2012/webcrypto/ 19:58:53 jyates has joined #crypto 19:58:54 1-617-324-0000 Access Code: 643 244 026 19:59:07 Password is member-only link 19:59:39 present= 19:59:44 present+ 19:59:47 present+ virginie 19:59:50 present+ hhalpin 19:59:55 zakim, who is here? 19:59:55 Present: wseltzer, virginie, hhalpin 19:59:57 On IRC I see jyates, Charles_Engelke, hhalpin, jimsch, RRSAgent, virginie, Karen, slightlyoff, tobie, timeless, Zakim, trackbot, wseltzer 20:00:00 present+ jyates 20:01:00 present+ Charles_Engelke 20:02:20 present+ jimsch 20:03:38 present+ timeless 20:04:17 scribenick: wseltzer 20:04:22 chair: Virginie 20:04:38 http://www.w3.org/2015/Process-20150901/#Reports 20:04:42 virginie: Welcome. We're checking to see whether the spec is ready to progress toward Rec 20:04:56 kodonog has joined #crypto 20:05:10 ... Discussion on mailing list over the last few weeks to finalize the WebCrypto API 20:05:19 https://github.com/w3c/webcrypto 20:05:20 ... spec in github repo 20:05:47 ... Harry, can you share recent changes? 20:06:01 hhalpin: some edits to prep for PR 20:06:11 ... and Jim giving a substantive check 20:06:15 pr-edits branch of the git repo 20:06:27 1) Normative references 20:06:32 ... Three edits: fixing normative references 20:06:34 https://github.com/w3c/webcrypto/tree/pr-edits 20:06:45 ... Added a resolution to Akamai's objection 20:06:59 ... noting the CFRG document on crypto algorithm analysis 20:07:00 2) We added a sentence to resolve the Akamai objection, noting the CFRG document which the CFRG has accepted to maintained, added to references 20:07:22 ... minor things 20:07:30 3) Editorial Notes -> Just became part of the spec text 20:07:46 Even though support BER encoding, we don't. 20:08:12 ... text from note was moved to spec 20:08:26 4) Some of preamble removed 20:08:31 ... preamble was removed, where it asked for help 20:08:38 ... and finally, changing SOTD 20:08:48 The last PR -> is to change the status section to match the PR section and to change the CSS 20:09:40 ... Last issue, I thought we could add a sentence to the algo section saying "if an algo is not in this list, it doesn't mean it's not under consideration, please check proposed algorithm note" 20:09:55 ... but I wanted to get discussion from WG/editors 20:10:01 ... or we could put that on the group homepage . 20:10:05 Only substantial change to the spec that I would see making before going to PR 20:10:08 q+ 20:10:33 jimsch: I have a slightly different proposal for dealing with editorial notes 20:10:59 ... I noted at least one ref to a section in an X9 document that wasn't filled in. 20:11:19 Let secret be the result of applying the field element to 20:11:19 octet string conversion defined in Section ? of X9.63 20:11:19 to the output of the ECDH primitive. 20:12:15 q- bal 20:12:36 wseltzer: we're looking for a copy of the X9 spec 20:13:03 hhalpin_ has joined #crypto 20:14:04 selfissued has joined #crypto 20:14:06 hhalpin: let's try to get a copy of the spec, and if not, can delete the reference 20:14:49 Not super-happy with deleting reference, but it seems to be the best thing to do if otherwise its unfixable. I would assume Sleevi may have had same issue. 20:14:49 virginie: we need to fix that before we move to PR 20:15:25 virginie: regarding proposed algorithm note, we don't currently ahve that document 20:15:34 ... so I don't want to put a dangling link 20:16:03 hhalpin: I could write the list, but we'd want someone available to maintain it 20:16:20 ... Does anyone want to edit? 20:16:39 jimsch: there are other documents we could reference instead of X9 20:16:51 ... there's an IETF ref. 20:16:57 hhalpin: sure 20:17:20 X9 - what other document could we reference? 20:17:38 hhalpin_: I'll make a "proposed algorithm" page, but won't refer to it in the spec 20:18:16 virginie: We need a WG resolution to move to PR 20:18:16 We can make that clear on the homepage, so people who find the spec and are looking for their favorite algorithm, we can at least point them to a document, even if it doesn't have an editor. 20:18:30 q? 20:18:39 Change X9 to RFC6090 20:18:52 selfissued: I had thought that issue of IANA registry adding algorithm analysis line would be done 20:18:57 hhalpin_: I'll put that in 20:19:04 jimsch: I'm willing for it not to exist 20:19:12 selfissued: N/A 20:19:18 I'm OK with anything. 20:19:19 jimsch: it's ok if the line doesn't exist 20:19:46 selfissued: for IANA, it shouldn't be missing a required field, even if the field's value is N/A 20:20:14 hhalpin_: 3 options, nothing, N/A, or ref to CFRG document 20:20:21 selfissued: nobody objected to N/A 20:20:21 n/A is fine 20:20:43 Algorithm Analysis Documents(s): n/a 20:21:24 https://lists.w3.org/Archives/Public/public-webcrypto/2015Nov/0012.html 20:21:24 Put that line after each of the Specification Document(s) lines in 34.1 20:21:50 In Section 34.1. JSON Web Signature and Encryption Algorithms Registration 20:24:30 Refreshing https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#iana-section-jws-jwa I'm not seeing the edits. Is this expected? 20:24:56 jimsch: I want to change one of the editorial issues response 20:25:00 q+ 20:25:10 q- 20:25:27 dconnolly has joined #crypto 20:25:29 hhalpin_: we should allow editorial flexibility to deal with minor issues that don't have substantive impact 20:26:07 q+ 20:27:24 jimsch: should we send notice of PR to the mailing list? 20:27:28 virginie: yes, let's do that 20:27:34 s/PR/pull request/ 20:27:39 q- 20:27:41 q- hhalpin_ 20:27:44 q- hhalpin 20:27:51 ack selfissued 20:28:31 selfissued: I had thought the current editors' draft was at the "latest" link in the CR 20:29:08 action: hhalpin to change the ED link in mercurial to point to github 20:29:08 Created ACTION-154 - Change the ed link in mercurial to point to github [on Harry Halpin - due 2015-12-07]. 20:29:14 https://github.com/w3c/webcrypto/tree/pr-edits/spec/ 20:29:16 Is there a version that gets rebuilt automatically on github? 20:30:17 selfissued: the call for review should contain a link to arendered version of the document with PR edits 20:30:27 https://raw.githubusercontent.com/w3c/webcrypto/pr-edits/spec/Overview.html 20:31:06 Let's make a README.md file that has the link to the rendered document. 20:31:46 wseltzer: we'll make sure when we send the minutes there's a rendered version to include a pointer 20:31:47 I'll have to set-up up gh-pages or make a standalone rendered version 20:31:53 No problem doing that. 20:31:57 selfissued: please point to both github and rendered version 20:33:08 virginie: provided that we have a link to rendered version, that we fix X9 links, that we allow editors to make non-substantive changes, and ask editor about link to "proposed algorithm" 20:33:36 PROPOSED: That we move the WebCrypto API to Proposed Recommendation 20:33:52 selfissued has joined #crypto 20:33:54 ... as found at https://raw.githubusercontent.com/w3c/webcrypto/pr-edits/spec/Overview.html 20:33:57 "Move the WebCrypto API [at https://github.com/w3c/webcrypto/tree/pr-edits/spec/] to Proposed Recommendation with the ability of the editors to make minor changes as needed. 20:34:06 But Wendy's its a bit more straightforward. 20:34:11 Please include both a link to a rendered version and the github branch in the review e-mail 20:34:20 harry - are you going to approve your pull request or are you going to wait for an editor to do it? 20:34:44 I'm going to give the editor a few more days, I see no reason to rush 20:34:45 virginie: if you agree, +1, disagree, -1 20:34:49 +1 20:34:50 +1 20:34:52 +0 20:34:53 +1 20:34:55 The important thing is to start the clock! 20:34:56 +1 20:34:56 +1 20:35:38 virginie: Sounds like consensus here. We submit to 2-week review on mailing list, and if no objection there, then 14 December, move to PR 20:35:54 ... Thank you for your work 20:35:59 ... Anything else to discuss? 20:36:00 q? 20:36:04 Just find that IETF reference for me ASAP Jimsch :) 20:36:15 harry - it is in the log 20:36:31 RESOLVED: That we move the WebCrypto API to Proposed Recommendation, as found at https://raw.githubusercontent.com/w3c/webcrypto/pr-edits/spec/Overview.html 20:36:57 virginie: in the meantime, if you find editors for the Proposed Algorithms note, please let us know. 20:36:59 +1 (didnt't hit return) 20:37:11 ... No further calls planned, but keep working by email. 20:37:15 q+ 20:37:26 ... Don't hesitate to use mailing list. 20:38:00 What's the e-mail list you referenced, Wendy? 20:38:18 public-web-security@w3.org (Web Security IG), selfissued 20:38:37 virginie: thank you all 20:39:40 i/public-web-security/wseltzer: For further W3C discussions on Web Security, see the Web Security IG, public-web-security@w3.org, and discussion of draft charters for Web Authentication and Hardware-Based Security 20:39:47 rrsagent, draft minutes 20:39:47 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html wseltzer 20:40:03 present+ kodonog 20:40:17 rrsagent, make logs team 20:40:20 rrsagent, make logs public 20:40:23 rrsagent, draft minutes 20:40:23 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html wseltzer 20:40:44 rrsagent, draft minutes 20:40:44 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html wseltzer 20:41:53 s/public-web-security@w3.org (Web Security IG), selfissued/wseltzer: public-web-security@w3.org (Web Security IG)/ 20:41:56 rrsagent, draft minutes 20:41:56 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html wseltzer 20:42:37 trackbot, end meeting 20:42:37 Zakim, list attendees 20:42:37 As of this point the attendees have been wseltzer, virginie, hhalpin, jyates, Charles_Engelke, jimsch, timeless, kodonog 20:42:45 RRSAgent, please draft minutes 20:42:45 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html trackbot 20:42:46 RRSAgent, bye 20:42:46 I see 1 open action item saved in http://www.w3.org/2015/11/30-crypto-actions.rdf : 20:42:46 ACTION: hhalpin to change the ED link in mercurial to point to github [1] 20:42:46 recorded in http://www.w3.org/2015/11/30-crypto-irc#T20-29-08 20:47:30 RRSAgent has joined #crypto 20:47:30 logging to http://www.w3.org/2015/11/30-crypto-irc 20:47:41 Meeting: WebCrypto WG 20:47:45 rrsagent, draft minutes 20:47:45 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html wseltzer 20:48:23 s|n/A is fine|n/a is fine 20:49:43 s/Wendy's its/Wendy's is/ 20:50:12 s/didnt't/didn't/ 20:51:12 RRSAgent, draft minutes 20:51:12 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html timeless 20:51:34 s/present=// 20:51:46 s/me waves// 20:52:31 s/I cannot appear to logon and get the password for the conference call// 20:52:48 s|Jim - http://www.w3.org/2012/webcrypto/|| 20:52:56 RRSAgent, draft minutes 20:52:56 I have made the request to generate http://www.w3.org/2015/11/30-crypto-minutes.html timeless