19:20:19 RRSAgent has joined #crypto 19:20:19 logging to http://www.w3.org/2014/10/20-crypto-irc 19:20:21 RRSAgent, make logs public 19:20:21 Zakim has joined #crypto 19:20:23 Zakim, this will be CRYPT 19:20:23 ok, trackbot; I see SEC_WebCryp()3:00PM scheduled to start 20 minutes ago 19:20:24 Meeting: Web Cryptography Working Group Teleconference 19:20:24 Date: 20 October 2014 19:22:41 w3 has joined #crypto 19:48:29 virginie has joined #crypto 19:48:34 agenda? 19:48:46 agenda+ Welcome 19:49:01 agenda+ Status of Web Crypto API bugs 19:49:27 agenda+ Resolution on extensibility/patchability bug 19:49:50 agenda+ Resolution on exit from Last Call for the Web Crypto API (if relevant) 19:50:12 agenda+ Web Crypto API milestones 19:50:44 agenda+ TPAC F2F meeting on 30th of October (discussing agenda) 19:50:47 agenda? 19:58:04 rsleevi has joined #crypto 19:59:09 SEC_WebCryp()3:00PM has now started 19:59:16 + +1.415.373.aaaa 19:59:19 Zakim, what's the code? 19:59:19 the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), harry 19:59:55 + +1.650.275.aabb 20:00:09 Karen_ has joined #crypto 20:00:12 kodonog has joined #crypto 20:00:19 +??P5 20:00:20 +[IPcaller] 20:00:25 Zakim, IPcaller is hhalpin 20:00:25 +hhalpin; got it 20:00:39 +[Microsoft] 20:00:47 selfissued has joined #crypto 20:01:10 +Karen 20:01:23 Zakim, pick a scribe 20:01:23 Not knowing who is chairing or who scribed recently, I propose rsleevi 20:01:29 It was me - I'm muted now 20:01:32 Zakim, pick a scribe 20:01:32 Not knowing who is chairing or who scribed recently, I propose Karen 20:01:34 +karen_oDonoghue 20:01:58 +Virginie_Galindo 20:01:59 rbarnes_ has joined #crypto 20:02:02 rbarnes_ has left #crypto 20:02:13 +[Microsoft.a] 20:02:14 rbarnes has joined #crypto 20:02:15 chair: Virgine Galindo 20:02:20 zakim, who is on the phone? 20:02:20 On the phone I see +1.415.373.aaaa, rsleevi, ??P5, hhalpin, [Microsoft], Karen, karen_oDonoghue, Virginie_Galindo, [Microsoft.a] 20:02:21 scribe: Karen 20:03:00 Zakim, P5 is rbarnes 20:03:01 sorry, harry, I do not recognize a party named 'P5' 20:03:15 And Mike 20:03:18 bal has joined #crypto 20:03:23 +Wendy 20:03:43 and all i know about IETF errata is that i always mark them "rejected" :) 20:03:44 zakim, who is on the phone? 20:03:44 On the phone I see +1.415.373.aaaa, rsleevi, rbarnes, hhalpin, selfissued, Karen, karen_oDonoghue, Virginie_Galindo, bal, Wendy 20:04:06 zakim, who is here? 20:04:08 FYI, I will only be able to stay on the call for the first 30 minutes 20:04:08 On the phone I see trevp, rsleevi, rbarnes, hhalpin, selfissued, Karen, karen_oDonoghue, Virginie_Galindo, bal, Wendy 20:04:08 On IRC I see bal, rbarnes, selfissued, kodonog, Karen_, rsleevi, virginie, w3, Zakim, RRSAgent, harry, tantek, tobie, schuki, timeless, Karen, slightlyoff, terri, wseltzer, 20:04:08 ... trackbot 20:04:20 agenda? 20:05:06 harry: my proposal was just for a box where you would link to the updates. i don't care if you put stuff in the box with errata, full WG process, or an IANA registry 20:05:34 markw has joined #crypto 20:06:00 vgb has joined #crypto 20:06:08 virginie: one bug left: extensibility 20:06:18 there's still some debate going on re the mailing list 20:06:33 +[Microsoft] 20:06:41 zakim, [microsoft] is me 20:06:41 +vgb; got it 20:06:44 but I think rbarnes has a proposal, Microsoft has some concerns, and then the CFRG might end up wrapping up with a decision before we get out of Last Call. 20:07:29 virginie: status of web crypto API 20:07:50 +markw 20:07:50 we could go for extensibility bug first for the fun of it 20:08:20 ... we made status of the bugs 20:09:14 Note re the infamous "Rich Salz security considerations bug" Graham should ship a doc to CFRG quite shortly. 20:09:37 mark: extensibility, implemented proposal from Richard 20:09:50 If he doesn't do it, I'll do it on his behalf. It will just be an Informational Note that is basically his blog post with some padding for everyone on CFRG to discuss. 20:09:52 Note : the list of bug is available here : https://www.w3.org/Bugs/Public/buglist.cgi?quicksearch=web%20crypto&list_id=45901 20:10:09 ... implemented a couple of proposals 20:11:05 virginie: 15 bugs open, most of them have been discussed 20:11:07 Zakim, who is on the phone ? 20:11:07 On the phone I see trevp, rsleevi, rbarnes, hhalpin, selfissued, Karen, karen_oDonoghue, Virginie_Galindo, bal, Wendy, vgb, markw 20:11:53 richard: algorithm alias - string name map to object name 20:12:16 24878 20:12:17 https://www.w3.org/Bugs/Public/show_bug.cgi?id=24878 20:12:59 MichaelH has joined #crypto 20:13:09 +Michael_Hutchinson 20:13:10 mark: should be easy to implement, just have to make a decision 20:13:13 there was consensus on the list previously 20:13:15 actually, i think it was ryan's proposal :) 20:13:27 kodonog has joined #crypto 20:13:48 virginie: no objection. 20:14:12 The rest of them seemed sensible - I think Ryan is right re HMAC key length being larger than block size 20:14:29 so that should just be closed as a "WONTFIX" 20:15:09 https://www.w3.org/Bugs/Public/show_bug.cgi?id=26950 20:15:45 q? 20:15:48 ... any bug that deserves attention? 20:15:57 Yeah, that one should be closed - no reason to restrict key length to output length 20:15:57 q+ 20:16:09 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25815 20:16:26 without looking up the references, i can live with closing that one 20:16:30 ryan looks right enough :) 20:16:32 26950 20:16:46 where "that one" == 26950 20:16:48 mark: 25815 20:17:44 I'm no expert there but it seems that if one had plaintext and one wanted key, keeping key longer than output of hash seems sensible. 20:17:51 ack harry 20:18:38 sorry I cannot follow this :( 20:18:54 Basically, Markw is normalizing the error codes 20:18:58 q? 20:19:01 mark: Should we say import/export will always report Data Error 20:19:07 mark, can you briefly enter your comments? 20:19:14 s/Data Error/DataError/ 20:19:33 As long as we don't have separate padding errors :) 20:19:46 mark: can implement change 20:19:55 Virginie: No objection 20:20:17 https://www.w3.org/Bugs/Public/show_bug.cgi?id=26950 20:20:19 harry: may be Ryan can explan on 26950 20:20:24 q+ 20:20:28 The objective of the bog was to ensure that validation errors on import/export all return the same error so that there is no requirement on UAs to distinguish error cases themselves - they are free to delegate checking to libraries 20:20:41 ack 20:20:42 s/big/bug (25815)/ 20:20:48 s/bog/bug (25815)/ 20:21:01 Does everyone agree with Ryan this should be a WONTFIX? 20:21:05 q- rbarnes 20:21:28 Almost all cases for import/export are already normalized to DataError, so my proposal is to standardize on that, rather then OperationError for import/output 20:21:31 Ryan: comment 3 was intentional text 20:21:43 ... to generalize hmac construct 20:22:03 ... to have max security strength 20:22:46 Richard: no point that the extra security going over the hmac length 20:23:57 + +1.703.948.aacc 20:24:02 Ryan: if you to generate a hmac key of L,it will not be the max security. see reference 20:25:18 virginie: this bug is not a problem? 20:25:31 Richard: no 20:25:51 So just chime in on Bugzilla and it will be a WONTFIX 20:25:54 virginie: you read the document and we have it resolved. 20:25:57 of course, i have no idea what the process requirement is for exiting LC. but i'm not going to object. 20:26:36 virginie: mark - can you give a short description on where we are on making a agreement? 20:26:57 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25618 20:27:07 mark: where need extensibility 20:27:42 ... add note saying so and reference 20:27:56 zakim, who is on the phone? 20:27:56 On the phone I see trevp, rsleevi, rbarnes, hhalpin, selfissued, Karen, karen_oDonoghue, Virginie_Galindo, bal, Wendy, vgb, markw, Michael_Hutchinson, +1.703.948.aacc 20:28:42 mark: cleanup exten for EC 20:29:16 ... need - format of the private key 20:29:59 virginie: everyone agree with Mark? 20:30:37 ... let's do a formal vote 20:31:06 Changes based on Richard's proposal have been implemented. Extension specifications will be explicitly listed in the specification - list to be updated with Errata. No longer possible to completely override existing algorithms. New hash algorithms can be added. EC curve extensisbility inteneded to allow a variety of new curves, not just those that align with NIST ones. 20:31:15 ... for extensibility 20:31:20 PROPOSED RESOLUTION: If you're happy with Mark's proposal, +1, if not, -1 20:31:33 I think the idea is to avoid "monkey patching" 20:31:39 q+ 20:31:59 trevp: does this resolution make it more difficult to add new algorithms as a new spec? 20:32:10 markw: you can still add new algorithms 20:32:21 Mark: we can still add new algorithms 20:33:10 bal, before you leave could you type in IRC whether or not you agree with Richard's "forward reference" solution re errata updating? 20:33:23 -Michael_Hutchinson 20:33:25 -Karen 20:33:44 bal: They are assuming an uncompresssed for same IPR reasons everyone else does 20:33:49 sorry, the line is off for me... 20:33:53 ... for PKCS#8, that's already taken care of 20:33:54 One remaining change is necessary to make the format of private EC keys defined by the extensions specification (currently it is asymmetrical: import assumed ECPrivateKey but export does not - or vice versa. Needs to be symmetrical, without the assumption). 20:33:59 +Michael_Hutchinson 20:34:23 q+ 20:34:40 can some scribe? 20:35:03 -rbarnes 20:35:06 -bal 20:35:11 q? 20:35:26 [bal and rbarnes leave, after saying this solution is fine with them] 20:35:33 +1 20:35:35 +Karen.a 20:35:45 self-issued: Is this an explicit decision to not use compressed curves? 20:35:57 trevorp: It's just unclear where you put it - would you put it in x co-ordinate 20:36:01 ... but yeah, we can deal with that later 20:36:06 scribe: hhalpin 20:36:15 I am back 20:36:16 virginie: Would your common be objection? 20:36:31 trevor: I think some details need to be fleshed out 20:36:32 q+ 20:36:44 ... but we can anticipate a lot of things 20:36:51 ... but dont want to preclude ourselves 20:37:32 selfissued: discussions here won't change that 20:37:39 mike: you should review JOSE draft 35 20:37:40 selfissued, please type up your point 20:37:45 zakim, who is making noise? 20:37:57 vgb, listening for 10 seconds I heard sound from the following: Michael_Hutchinson (49%), Virginie_Galindo (49%) 20:37:58 If you have concerns about the JWK langauge, you shoudl review the -35 draft 20:38:08 And send comments to jose@ietf.org 20:38:11 q? 20:38:18 Disussinos here won't change JWK 20:38:28 harry: don't think it is a blocking bug 20:38:33 But I don't think there's anything blocking WebCrypto from proceeding in JWK 20:38:38 ... can fix in JWK in future 20:39:01 i.e. we can specify that in the extension spec 20:39:08 and that we should clarify this with JWK 20:39:27 Travor: I am not rejecting anything, just want to make sure extension is possible 20:39:29 so I don't think its blocking exiting Last Call per se 20:40:06 There was an explicit JOSE working group decision not to use compressed point representations 20:40:07 ryan: compressed point is not supported in the spec 20:40:31 ... the spec is going to be a living one 20:41:06 ... if is need for compressed curve, we consider 20:41:11 https://www.w3.org/Bugs/Public/show_bug.cgi?id=25618 20:41:28 Virginie: any objection to mark's proposal? 20:41:59 ... Ryan and Richard agree 20:42:06 +1 (on the basis that we fix the one remaining change to make the format of private EC keys defined by the extensions specification.) 20:42:08 +1 20:42:08 +1 to closing with Mark's proposal (regarding one more small change he needs to make) 20:42:09 +1 20:42:13 +1 20:42:17 =1 20:42:19 +1 20:42:34 Travor: +1 20:42:36 [+1 is "no objection"] 20:42:45 Trevorp: 0 (abstain) 20:42:53 s/Travor: +1// 20:43:07 i believe bal and rbarnes expressed +1 before leaving 20:43:32 Virginie: agree to exit last call? 20:43:37 +1 20:43:40 q+ 20:43:44 +1 20:43:57 ... we can leave 2 weeks for people online 20:43:58 We should go over the errata discussion real quick 20:44:06 PROPOSED: Exit last call 20:44:19 mark: let people on the call to vote or talk 20:44:25 Basically, the answer is "yes" we can update errata re forward references 20:44:30 +1 20:44:55 If people want to delve into errata management, I'm happy to do that. 20:45:00 +1 20:45:00 [with the understanding that this decision will go out on the mailing list, per usual WG practice] 20:45:05 +1 20:45:11 +1 20:45:16 s/list,/list for the next two weeks,/ 20:45:29 +1 20:46:38 RESOLVED: Exit last call, after confirming on mailing list 20:47:08 ACTION: hhalpin to create Last Call Exit request document 20:47:09 Created ACTION-148 - Create last call exit request document [on Harry Halpin - due 2014-10-27]. 20:47:14 q+ 20:47:16 virginie: thank you everyone for making the efforts 20:48:38 ... F2F meeting on 10/30th 20:49:08 ... agenda: webcrypto roadmap, key discovery 20:49:26 q+ 20:49:34 ... may be news of security recommendation from IETF 20:49:45 q- 20:49:51 ... tools, respository 20:49:55 q- 20:49:59 q+ 20:50:13 q? 20:50:14 ... debrief of the workshop in Sept and rechartering 20:50:15 q- 20:50:55 wendy: web app security WG is also re-chartering and interested what items will fit between groups 20:51:03 ... credential API 20:51:26 ... I will help to coordinate 20:51:41 virginie: anything else? 20:51:45 q- 20:51:59 q? 20:52:05 agenda? 20:52:20 q+ 20:53:05 Wendy: thank you virginie and everyone! next step would be implementation and testing 20:53:10 q- 20:53:39 mark: multiple implementations exit already 20:54:15 wendy: yes, we need to test them to get a uniform platform 20:54:21 thanks everyone! 20:54:31 -markw 20:54:34 -rsleevi 20:54:35 bye 20:54:35 - +1.703.948.aacc 20:54:36 -Michael_Hutchinson 20:54:36 -selfissued 20:54:37 trackbot, end meeting 20:54:37 -Virginie_Galindo 20:54:37 Zakim, list attendees 20:54:37 As of this point the attendees have been +1.415.373.aaaa, +1.650.275.aabb, rsleevi, hhalpin, Karen, karen_oDonoghue, Virginie_Galindo, rbarnes, selfissued, Wendy, bal, trevp, vgb, 20:54:40 rsleevi has left #crypto 20:54:41 ... markw, Michael_Hutchinson, +1.703.948.aacc 20:54:41 -trevp 20:54:41 -Wendy 20:54:44 -vgb 20:54:45 RRSAgent, please draft minutes 20:54:45 I have made the request to generate http://www.w3.org/2014/10/20-crypto-minutes.html trackbot 20:54:46 RRSAgent, bye 20:54:46 I see 1 open action item saved in http://www.w3.org/2014/10/20-crypto-actions.rdf : 20:54:46 ACTION: hhalpin to create Last Call Exit request document [1] 20:54:46 recorded in http://www.w3.org/2014/10/20-crypto-irc#T20-47-08 20:54:48 -Karen.a