20:28:24 RRSAgent has joined #crypto 20:28:24 logging to http://www.w3.org/2013/09/16-crypto-irc 20:28:30 MichaelH: Does it not still apply 20:28:40 ...Korean use case? 20:29:27 virginie: Not going to address 20:29:44 virginie: Issue 9 no conclusion 20:29:57 virginie: Issue 12 no conclusion 20:30:07 ISSUE-28? 20:30:07 ISSUE-28 -- Short-names for algorithms -- open 20:30:07 http://www.w3.org/2012/webcrypto/track/issues/28 20:30:29 ... Issue 28 As a working group decided to address it 20:30:52 ... Should be closed 20:31:01 PROPOSAL: Close ISSUE-28 20:31:20 ISSUE-32? 20:31:20 ISSUE-32 -- Section 5.2 in API draft should mention use of secure element in the context of key security -- open 20:31:20 http://www.w3.org/2012/webcrypto/track/issues/32 20:31:20 virginie: Issue 32 Covered several times 20:31:36 PROPOSAL: Close ISSUE-32 20:31:40 ISSUE-35? 20:31:40 ISSUE-35 -- Handling of wrap/unwrap operations -- open 20:31:40 http://www.w3.org/2012/webcrypto/track/issues/35 20:31:42 ... Close by email in coming weeks 20:31:56 virginie: Issue 35 Still pending extract 20:31:57 ISSUE-36? 20:31:57 ISSUE-36 -- Semantics for key generation versus key derivation -- open 20:31:57 http://www.w3.org/2012/webcrypto/track/issues/36 20:32:13 virginie: Issue 36 Addressed by Vijay proposal 20:32:57 rsleevi: No directly by Vijay, but combination of propoisals 20:33:32 ISSUE-43? 20:33:32 ISSUE-43 -- Separate method for key agreement -- open 20:33:32 http://www.w3.org/2012/webcrypto/track/issues/43 20:34:10 virginie: Issue 43 Related to 74 20:34:16 ISSUE-44? 20:34:16 ISSUE-44 -- Require creation of random IVs by default for CBC, CFB, GCM -- open 20:34:16 http://www.w3.org/2012/webcrypto/track/issues/44 20:34:24 virginie: Issue 44 Related to IV 20:34:49 rsleevi: We said close this 20:35:22 virginie: Some topics keeping this open 20:35:50 ...Today extractablity 20:36:19 https://www.w3.org/bugzilla_public/buglist.cgi?product=Web%20Cryptography&component=Web%20Cryptography%20API%20Document 20:36:26 ...Anybody having issue? 20:36:44 ...Use bugzilla to track 20:36:48 zakim, take up agenda item 2 20:36:48 'item\ 2' does not match any agenda item, wseltzer 20:36:53 zakim, take up agenda 2 20:36:53 agendum 2. "Review of action and issue" taken up [from virginie] 20:37:00 zakim, take up agenda 3 20:37:00 agendum 3. "Web Crypto API" taken up [from virginie] 20:37:49 virginie: Clear demand from Netflix for UA to maintain the attribute for special case of JWT 20:38:00 ...Microsoft supported this 20:38:18 ...Google (ryan) not a fan of proposal 20:38:23 hhalpin has joined #crypto 20:38:50 q+ to make a suggestion 20:38:53 ...other people want to comment? 20:39:21 zakim, unmute me 20:39:21 arunranga should no longer be muted 20:39:23 ...write a sentence in the spec to describe attributes for this? 20:39:39 ack arunranga 20:39:39 arunranga, you wanted to make a suggestion 20:39:58 +[IPcaller.a] 20:40:01 arunranga: Extractability has value 20:40:15 ...service provider needs security 20:40:22 -[IPcaller.a] 20:40:39 ...propose JWK be a distint specification 20:40:58 ...keep if out of WebCrypto API 20:41:19 q+ 20:41:27 virginie: Jim suggest an alternate approach 20:41:44 ack rsleevi 20:41:47 hhalpin_ has joined #crypto 20:41:59 rsleevi: Jim proposal similar to one I made earlier 20:42:42 ...usage of SE, Smart card, painting ourselves into a corner 20:43:26 q+ 20:43:47 ....ryan "Can you paste those into the irc?" 20:44:07 ...Set of undefined attributes 20:44:23 ...key format describes attributes 20:44:44 q? 20:45:00 Will mail those to the list, as discussed 20:45:14 ryan: thanks! 20:45:39 jimsch: Don't believe that will be sufficient 20:46:01 ... I know what happens for RSA and symettric key unwrap 20:46:19 ...but other key types are not well understood 20:46:50 ...Operations are divided 20:46:58 ...into multiple operations 20:47:12 markw: Ryan suggestion is good 20:47:22 ...allows us to move forward 20:47:42 ...future updates can be made when needed 20:48:16 So I think rsleevi said what I was saying, but better 20:48:52 ryan: The description of the problem with multiple key usages is not clear 20:49:19 ...only netflix has requested this; go for min solution 20:49:37 ...until we get more complete use cases 20:49:42 q? 20:49:50 q- 20:50:01 virginie: We may have a consenus 20:50:06 rsleevi, you wanted to respond to jimsch 20:50:27 ... get ryan to generate a written proposal 20:50:37 ...group to review 20:51:27 @wseltzer ACTION? 20:52:04 http://lists.w3.org/Archives/Public/public-webcrypto/2013Jul/0070.html 20:52:06 zakim, take up next agendum 20:52:06 agendum 1. "introduction" taken up [from virginie] 20:52:14 zakim, take up agendum 4 20:52:14 agendum 4. "Web Crypto Key Discovery" taken up [from virginie] 20:53:11 MichaelH: use case for multiple keys on a single device 20:53:18 ... home automation system 20:53:37 ... see email: http://lists.w3.org/Archives/Public/public-webcrypto/2013Jul/0070.html 20:53:41 q? 20:54:47 ACTION, MichaelH to make proposal to amend API 20:54:56 ACTION: MichaelH to make proposal to amend API 20:54:56 Error finding 'MichaelH'. You can review and register nicknames at . 20:55:26 ACTION: Michael Hutchinson to make proposal to amend API 20:55:26 'Michael' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., MHutchinson, mjones7). 20:55:30 +1 Viriginie 20:55:32 ACTION: MHutchinson to make proposal to amend API 20:55:32 Created ACTION-114 - Make proposal to amend api [on Michael Hutchinson - due 2013-09-23]. 20:56:08 virginie: Please register 20:56:17 [TPAC 2013: http://www.w3.org/2013/11/TPAC/ ] 20:56:49 @wseltzer .DOCUMENT NOT FOUND 20:56:50 [early-bird registration until 18 Oct; get your visa invitation letters if necessary ] 20:57:54 ...Any topic please mention it early! 20:58:15 +1 to attending to TPAC 20:58:19 +1 20:58:20 +1 20:58:22 +1 20:58:26 +1 20:58:28 +0 Status is currently unknown 20:58:31 +1 20:58:32 q+ 20:58:34 +0 20:58:39 +1 20:59:24 I said I'm attending 20:59:38 ...Just try and stop him! 20:59:57 ...Visa could be an issue 20:59:58 +1 21:00:27 ...so get your request in early 21:00:52 Next call in 2 weeks 21:01:00 Web Certificate API 21:01:05 If you submit your registration and email Beihang for a visa letter, you will get I believe by Sept 30th. 21:01:20 -bryaneyler 21:01:21 Also, note next call Dan Boneh wants some time for his review of the API. 21:01:50 -jyates 21:01:53 ...MichaelH please get proposal in so we can review that 21:01:58 -[IPcaller] 21:02:02 -Virginie_Galindo 21:02:04 -rsleevi.a 21:02:05 -[Microsoft] 21:02:05 -markw 21:02:07 -kodonog 21:02:07 -arunranga 21:02:08 -Wendy 21:02:09 bye 21:02:14 @wseltzer close scibe? 21:02:16 trackbot, end teleconf 21:02:16 Zakim, list attendees 21:02:16 As of this point the attendees have been mete, +1.617.253.aaaa, Wendy, +1.512.257.aabb, +1.408.540.aacc, virginie, markw, jyates, +1.540.809.aadd, kodonog, +1.650.275.aaee, 21:02:19 ... Virginie_Galindo, +1.512.257.aaff, +1.415.294.aagg, MichaelH, arunranga, jimschaad, bryaneyler, israelh, [IPcaller] 21:02:19 mete has left #crypto 21:02:21 -mete 21:02:24 RRSAgent, please draft minutes 21:02:24 I have made the request to generate http://www.w3.org/2013/09/16-crypto-minutes.html trackbot 21:02:25 RRSAgent, bye 21:02:33 @wseltzer thanks! 21:02:33 rrsagent, make logs public 21:02:40 rrsagent, make minutes 21:02:40 I have made the request to generate http://www.w3.org/2013/09/16-crypto-minutes.html wseltzer 21:07:07 hhalpin_, no, that starts at 20:28 21:35:01 disconnecting the lone participant, MichaelH, in SEC_WebCryp()4:00PM 21:35:03 SEC_WebCryp()4:00PM has ended 21:35:03 Attendees were mete, +1.617.253.aaaa, Wendy, +1.512.257.aabb, +1.408.540.aacc, virginie, markw, jyates, +1.540.809.aadd, kodonog, +1.650.275.aaee, Virginie_Galindo, 21:35:04 ... +1.512.257.aaff, +1.415.294.aagg, MichaelH, arunranga, jimschaad, bryaneyler, israelh, [IPcaller] 22:02:28 tantek has joined #crypto