19:40:20 RRSAgent has joined #crypto 19:40:20 logging to http://www.w3.org/2013/10/28-crypto-irc 19:40:22 RRSAgent, make logs public 19:40:22 Zakim has joined #crypto 19:40:24 Zakim, this will be CRYPT 19:40:24 ok, trackbot; I see SEC_WebCryp()4:00PM scheduled to start in 20 minutes 19:40:25 Meeting: Web Cryptography Working Group Teleconference 19:40:25 Date: 28 October 2013 19:46:37 MichaelH has joined #crypto 19:48:45 SEC_WebCryp()4:00PM has now started 19:48:46 +Michael_Hutchinson 19:51:36 sangrae has joined #crypto 19:55:16 jimsch has joined #crypto 19:55:54 +[IPcaller] 19:55:55 -[IPcaller] 19:55:55 +[IPcaller] 19:56:18 zakrim, [ipcaller] is jimsch 19:56:52 danny_ has joined #crypto 19:57:03 + +1.617.253.aaaa 19:58:11 617.253.aaaa is jyates 19:58:17 +Virginie_Galindo 19:59:03 +Wendy 19:59:37 israelh has joined #Crypto 20:00:11 markw has joined #crypto 20:00:29 +[IPcaller.a] 20:00:32 +[Microsoft] 20:00:34 zakim, who is here? 20:00:34 On the phone I see Michael_Hutchinson, [IPcaller], +1.617.253.aaaa, Virginie_Galindo, Wendy, [IPcaller.a], [Microsoft] 20:00:36 On IRC I see markw, israelh, danny_, jimsch, sangrae, Zakim, RRSAgent, arunranga, jyates, malaclyps, trackbot, rsleevi, timeless, slightlyoff, wseltzer 20:00:45 zakim, Microsoft has israelh 20:00:45 +israelh; got it 20:00:52 +[Netflix] 20:00:57 zakim [IPcaller.a is Sangrae 20:01:05 zakim, [IPcaller.a is Sangrae 20:01:05 +Sangrae; got it 20:01:14 Zakim, [Netflix] is me 20:01:14 +markw; got it 20:01:14 zakim, [ipcaller] is jimsch 20:01:15 +jimsch; got it 20:01:22 zakim, who is on the phone? 20:01:22 On the phone I see Michael_Hutchinson, jimsch, +1.617.253.aaaa, Virginie_Galindo, Wendy, Sangrae, [Microsoft], markw 20:01:24 [Microsoft] has israelh 20:01:45 zakim, aaaa is jyates 20:01:45 +jyates; got it 20:01:51 +arunranga 20:02:20 MichaelH has joined #crypto 20:02:24 wseltzer has changed the topic to: Agenda 28 Oct: http://lists.w3.org/Archives/Public/public-webcrypto/2013Oct/0035.html 20:02:27 zakim, mute me 20:02:27 arunranga should now be muted 20:03:01 agenda+ welcome 20:03:08 agenda+ Web Crypto API 20:03:14 agenda+ Web Crypto API 20:03:16 + +1.650.275.aabb 20:03:24 zakim, aabb is rsleevi 20:03:24 +rsleevi; got it 20:03:32 Zakim, who is on the call? 20:03:32 On the phone I see Michael_Hutchinson, jimsch, jyates, Virginie_Galindo, Wendy, Sangrae, [Microsoft], markw, arunranga (muted), rsleevi 20:03:35 [Microsoft] has israelh 20:03:38 agenda+ key discovery 20:03:42 agenda+ group life 20:03:55 + +1.703.284.aacc 20:04:06 +[Microsoft.a] 20:04:10 zakim, aacc is rbarnes 20:04:10 +rbarnes; got it 20:04:25 zakim, Microsoft.a has vgb 20:04:25 +vgb; got it 20:04:37 rbarnes has joined #crypto 20:04:48 zakim, who is on the phone? 20:04:48 On the phone I see Michael_Hutchinson, jimsch, jyates, Virginie_Galindo, Wendy, Sangrae, [Microsoft], markw, arunranga (muted), rsleevi, rbarnes, [Microsoft.a] 20:04:51 [Microsoft.a] has vgb 20:04:51 [Microsoft] has israelh 20:04:56 vgb has joined #crypto 20:05:10 MichaelH_ has joined #crypto 20:05:15 zakim, who is on the call? 20:05:15 On the phone I see Michael_Hutchinson, jimsch, jyates, Virginie_Galindo, Wendy, Sangrae, [Microsoft], markw, arunranga (muted), rsleevi, rbarnes, [Microsoft.a] 20:05:18 [Microsoft.a] has vgb 20:05:18 [Microsoft] has israelh 20:06:03 nvdbleek has joined #crypto 20:06:17 zakim, code? 20:06:17 the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), nvdbleek 20:06:18 scribenick: jimsch 20:06:23 q? 20:06:30 Scribe: Jim Schaad 20:07:17 Will skip the topic on Dan comments since Dan is not present. 20:07:45 Isreal: Questions on text for promises model 20:07:53 +nvdbleek 20:07:58 zakim, mute me 20:07:58 nvdbleek should now be muted 20:08:22 i/Scribe:/Topic: WebCrypto API 20:08:23 ... Questions on stylistic for patterns to follow 20:09:16 ... Q1 - Using a mixture of exception throughing and promise failures. Seems better to always call reject resolver 20:09:36 hhalpin has joined #crypto 20:09:50 ... Easier programing since not try catching. Now have unified handling through promises 20:09:50 q+ to respond to Q1 - exceptions versus failure 20:10:09 ack next 20:10:10 rsleevi, you wanted to respond to Q1 - exceptions versus failure 20:10:27 rsleevi: Can carry on more discussion on the maiing list. 20:10:38 MichaelH has joined #crypto 20:11:01 ... One issue with web IDO invlaalid objects are defined as exceptions, so some external things can though exceptions 20:11:15 s/IDO/IDL 20:11:23 ... Exceptions during the parameter validation, failures on the resolver for the implemention related failures 20:11:23 +[IPcaller] 20:11:30 Zakim, [IPcaller] is hhalpin 20:11:30 +hhalpin; got it 20:11:50 q? 20:12:27 Isrealh: Q2 - Reconciing the promises model and a stream based model. These are currently orthognal at this time. 20:12:55 ... Verify that things may need to change to deal with streams in the future 20:13:28 rsleevi: Streams are still messy and not finalized. Depends on where the stream spec goes 20:14:39 Isreal: Verify that we may need to modify the API when streams become supported. Should potentially note this in the current spec if not already done 20:15:12 rsleevi: Next thing to be worked on. But yes there will be some API changes to make streams first class objects 20:15:31 q+ 20:15:35 ACTION: rsleevi to add note re: streams 20:15:35 virginia When will the stream sepc be stable? 20:15:36 Created ACTION-120 - Add note re: streams [on Ryan Sleevi - due 2013-11-04]. 20:15:37 q+ to talk about Streams. 20:15:44 zakim, unmute me 20:15:44 arunranga should no longer be muted 20:16:32 Isreal: Mid next year maybe 20:16:46 q- 20:17:20 ... Q3: In the event model, did we have ability to reuse crypto opertions? Was this true? 20:17:42 zakim, mute me 20:17:42 arunranga should now be muted 20:17:45 rsleevi: No state transition to allow to go from filnish to re-init. 20:18:18 Quick point re streams - 7.4.3 20:18:28 "Feature at Risk": http://www.w3.org/2005/10/Process-20051014/tr 20:18:37 ... Need clarifition regarding parameters for nested streaming. 20:18:39 We are supposed to exit CR June next year 20:18:47 so that's cutting it a bit close 20:19:02 but adding a note re streams as a feature at risk should be fine, otherwise next version. 20:19:14 q? 20:19:23 Isreal: Need to clarify when things go in on promisses and when things need to be broken appart re parameters 20:20:14 q- 20:20:25 -[Microsoft] 20:20:56 agenda, next 20:21:18 Topic: PING review 20:21:21 -> http://www.w3.org/2012/webcrypto/track/actions/119 20:22:04 wseltzer: PING group has prepared comments on the API. With suggestion that we review their comments - may lead to new privacy considertions 20:23:04 ..... Most of the issues are in key discovery and pre-previsioned keys 20:23:21 ... Need someone to take an action to review and respond to PING 20:23:41 Virginia: Mark should look at the key discrovery items 20:23:52 ACTION markw to review PING privacy review 20:23:53 Created ACTION-121 - Review ping privacy review [on Mark Watson - due 2013-11-04]. 20:23:58 ... Should be the document editors looking at these items 20:24:04 q+ 20:24:18 Its fine to go to Last Call as long as Working Group has closed open issues 20:24:20 ... Target to answer before end of Nov, after F2F meeting 20:24:46 q+ 20:24:49 ack hhalpin 20:25:01 ack hhalpin 20:25:54 ... Should have agenda item at F2F to review privacy aspects 20:26:06 action virginie to add horizontal reviews, including privacy, to TPAC f2f agenda 20:26:07 Created ACTION-122 - Add horizontal reviews, including privacy, to tpac f2f agenda [on Virginie GALINDO - due 2013-11-04]. 20:26:11 q- 20:26:18 I think to satisfy PING is pretty simple - its mostly moving text from WebCrypto API to Key Discovery 20:26:26 with whatever otpions are necessary 20:26:57 Topic: Technical proposals on Key Discovery API 20:27:34 markw: Current status is ryan and I have been having discussions on techincal merits 20:27:44 ... Certificate references is one issue. 20:28:03 .. Possible create new interface for certifictes, did not intend to go that far initially 20:28:45 ... Looking for stratigies to identify ceritifctes associated with keys held behind the U 20:28:51 q? 20:29:20 q+ 20:29:27 s/markw/MichaelH/ 20:29:39 ack rsleevi 20:30:04 rsleevi: Working group not ready to take on the item based on lack of comments coming from the list 20:30:25 +1 rsleevi. 20:30:34 ... Understand where the use case is coming from, but need to understand more than the one case 20:31:13 MichealH: Some lack of interest on the list for all things 20:31:28 Should we just keep certificates for WebCrypto v.Next? 20:31:48 virginie: Need to test the interest of the group more formally? 20:31:56 q+ 20:32:09 ... Look at this at the F2F for assement of interest 20:32:12 I also might add having less discussion on the list and stopping new features from being added is generally means the spec is mature enough for Last Call. 20:32:51 mark: Looking for concusus on the use cse before including in the document 20:33:15 zakim, unmute me 20:33:15 arunranga should no longer be muted 20:33:16 s/including in the document/studying the proposal in detail/ 20:33:45 ???: Will ther ebe a dial in number? 20:33:54 virginie: No response to inital requerst on this 20:33:57 s/???/arunranga: 20:34:02 s/requerst/request/ 20:34:25 wseltzer: Have requested and are expecting to have availble 20:34:28 zakim, mute me 20:34:28 arunranga should now be muted 20:34:37 q? 20:34:37 So, a dial-in is likely and will be emailed to the mailing list once available. 20:34:37 q? 20:34:47 ack markw 20:34:51 q- 20:35:23 Topic: Group Life 20:35:37 virginie: Listed topics for the F2F agenda 20:36:16 ... Currently have two days laid out, but need to reclarify what was expected to have happen 20:36:41 hhalpin: Close all major issues on the first day 20:36:52 .... Look at use cses on the second day 20:37:11 ... If open issues bled intot he second day, that is more important 20:37:45 virginie: Need to look at test as well. 20:38:32 ... Edit the Wiki to add things related to the current specifications if they are missing 20:38:48 ... Agree main objective is to close open issues 20:39:21 ... New issues will only be discussed if they are really new 20:39:53 ... Want to freeze time for remote attendees to be able to get in 20:40:02 zakim, unmute me 20:40:02 nvdbleek should no longer be muted 20:40:17 ... Any europe based remote attendees? 20:40:27 nvdbleek: I think i might 20:40:40 zakim, mute me 20:40:40 nvdbleek should now be muted 20:40:46 virginie: Will make proposal on timings, let me know if that does not work well. 20:40:54 ... Should come out next week 20:41:03 q+ 20:41:05 ... Any other issues? 20:41:17 ack next 20:41:20 If we have some time, we can kill issues :) 20:41:29 Which group MichaelH? 20:41:56 Chair likely forgot 20:42:37 SysApps 20:42:47 ... Web security interset group had charter renewed. I am co-chairing and the gorup is now alive 20:43:10 ... Looking at mobile web app securtiy model 20:43:46 ... People in this group might be interesed in joining and looking at the mailing list 20:44:07 ... Contact me or wendy to get more info 20:44:10 q? 20:44:12 q+ 20:45:11 @hhalpin so do I need to ask again somewhere? 20:45:24 @MichaelH: email the chair of that group 20:45:44 SysApps 20:45:59 wseltzer has changed the topic to: See you at TPAC 20:46:07 -rbarnes 20:46:09 -nvdbleek 20:46:10 -jyates 20:46:10 -markw 20:46:11 [adjourned] 20:46:11 -rsleevi 20:46:13 -[Microsoft.a] 20:46:15 -Sangrae 20:46:15 -Virginie_Galindo 20:46:17 -Wendy 20:46:19 -jimsch 20:46:25 trackbot, end teleconf 20:46:25 Zakim, list attendees 20:46:25 As of this point the attendees have been Michael_Hutchinson, +1.617.253.aaaa, Virginie_Galindo, Wendy, israelh, Sangrae, markw, jimsch, jyates, arunranga, +1.650.275.aabb, rsleevi, 20:46:28 ... +1.703.284.aacc, [Microsoft], rbarnes, vgb, nvdbleek, hhalpin 20:46:28 -hhalpin 20:46:29 -arunranga 20:46:33 RRSAgent, please draft minutes 20:46:33 I have made the request to generate http://www.w3.org/2013/10/28-crypto-minutes.html trackbot 20:46:34 RRSAgent, bye 20:46:34 I see 1 open action item saved in http://www.w3.org/2013/10/28-crypto-actions.rdf : 20:46:34 ACTION: rsleevi to add note re: streams [1] 20:46:34 recorded in http://www.w3.org/2013/10/28-crypto-irc#T20-15-35