16:01:02 <RRSAgent> RRSAgent has joined #crypto
16:01:02 <RRSAgent> logging to http://www.w3.org/2013/12/16-crypto-irc
16:01:04 <trackbot> RRSAgent, make logs public
16:01:06 <trackbot> Zakim, this will be CRYPT
16:01:06 <Zakim> ok, trackbot; I see SEC_WebCryp()11:00AM scheduled to start now
16:01:07 <trackbot> Meeting: Web Cryptography Working Group Teleconference
16:01:07 <trackbot> Date: 16 December 2013
16:01:19 <hhalpin> Zakim, what's the code?
16:01:19 <Zakim> the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), hhalpin
16:01:46 <markw> Zakim, who is on the phone ?
16:01:46 <Zakim> apparently Team_(crypto)16:00Z has ended, markw
16:01:47 <Zakim> On IRC I see RRSAgent, jyates, hhalpin, markw, mountie, rigo, Zakim, timeless, slightlyoff, wseltzer, trackbot
16:02:00 <jyates> what is the passcode?
16:02:05 <hhalpin> Zakim, who's on the phone?
16:02:05 <Zakim> apparently Team_(crypto)16:00Z has ended, hhalpin
16:02:06 <Zakim> On IRC I see RRSAgent, jyates, hhalpin, markw, mountie, rigo, Zakim, timeless, slightlyoff, wseltzer, trackbot
16:03:12 <hhalpin> Zakim, who's on the phone?
16:03:12 <Zakim> apparently Team_(crypto)16:00Z has ended, hhalpin
16:03:14 <Zakim> On IRC I see RRSAgent, jyates, hhalpin, markw, mountie, rigo, Zakim, timeless, slightlyoff, wseltzer, trackbot
16:04:38 <virginie> virginie has joined #crypto
16:05:28 <hhalpin> So, people are not having trouble dialing in using the normal code
16:05:39 <gjs> gjs has joined #crypto
16:05:41 <hhalpin> however, is anyone on IRC dialing in and having trouble dialing in?
16:05:51 <virginie> yeap, i do
16:05:55 <israelh> israelh has joined #crypto
16:06:03 <mountie> I had trouble shortly
16:06:04 <hhalpin> Can you explain what your trouble is precisely?
16:06:14 <hhalpin> Dialing in *before* the telcon will mean the code wont' work :)
16:06:20 <karen_> karen_ has joined #crypto
16:07:08 <hhalpin> There does seem to be some problems with Zakim, he's not associating the phone properly to the telco
16:07:56 <virginie> which passcode did u use ?
16:08:05 <hhalpin> The same one as normal
16:08:07 <hhalpin> CRYPT
16:08:36 <karen_> what is the conf code?
16:08:49 <hhalpin> CRYPT
16:08:54 <nvdbleek> nvdbleek has joined #crypto
16:09:01 <hhalpin> What happens when you try it?
16:09:18 <nvdbleek> zakim, code?
16:09:18 <Zakim> the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), nvdbleek
16:09:19 <karen_> conf code invalid
16:09:23 <jyates> 27978#
16:09:43 <markw> Zakim, who is on the phone ?
16:09:43 <Zakim> apparently Team_(crypto)16:00Z has ended, markw
16:09:44 <karen_> that is what I entered. Will try again
16:09:44 <hhalpin> hhalpin has changed the topic to: WebCrypto conference code: 27978 "CRYPT"
16:09:44 <Zakim> On IRC I see nvdbleek, karen_, israelh, gjs, virginie, RRSAgent, jyates, hhalpin, markw, mountie, rigo, Zakim, timeless, slightlyoff, wseltzer, trackbot
16:10:18 <virginie> zakim, who is on the phone ?
16:10:18 <Zakim> apparently Team_(crypto)16:00Z has ended, virginie
16:10:20 <Zakim> On IRC I see nvdbleek, karen_, israelh, gjs, virginie, RRSAgent, jyates, hhalpin, markw, mountie, rigo, Zakim, timeless, slightlyoff, wseltzer, trackbot
16:10:20 <hhalpin> topic: Dec 16th 2013 Web Crypto Call
16:10:39 <hhalpin> Zakim, pick a scribe
16:10:39 <Zakim> sorry, hhalpin, I don't know what conference this is
16:10:44 <hhalpin> Zakim, this is crypt
16:10:45 <Zakim> ok, hhalpin; that matches SEC_WebCryp()11:00AM
16:10:50 <hhalpin> Zakim, pick a scribe?
16:10:50 <Zakim> I don't understand your question, hhalpin.
16:11:06 <virginie> zakim, who is on the phone ?
16:11:09 <Zakim> On the phone I see markw, +1.617.253.aabb, ??P57, [IPcaller], [Microsoft], virginie, +1.323.425.aacc, Karen
16:11:15 <karen_> Got in after the 3rd try
16:11:31 <nvdbleek> zakim, I am +1.323.425
16:11:31 <Zakim> +nvdbleek; got it
16:11:37 <jyates> aabb is jyates
16:12:21 <hhalpin> Zakim, pick a scribe
16:12:21 <Zakim> Not knowing who is chairing or who scribed recently, I propose nvdbleek
16:12:37 <hhalpin> Zakim, IPcaller is hhalpin
16:12:37 <Zakim> +hhalpin; got it
16:13:05 <virginie> zakim, who is on the phone ?
16:13:05 <Zakim> On the phone I see markw, +1.617.253.aabb, ??P57, hhalpin, [Microsoft], virginie, nvdbleek, Karen
16:13:23 <virginie> agenda ?
16:13:39 <mountie> Zakim, ??P57 is mountie
16:13:39 <Zakim> +mountie; got it
16:15:15 <karen_> virginie: agenda: timeline and future work
16:15:28 <karen_> ... may not have technical topic
16:16:03 <karen_> harry: can you repeat?
16:16:25 <karen_> harry: we discussed hosting workshop
16:16:36 <karen_> ... we may need to bring more people on
16:17:21 <karen_> Virginie: still not have a fixed date from Ryan
16:17:30 <hhalpin> markw - have you had any issues with working on the spec?
16:17:35 <karen_> ... there is an update of the spec, Dec. 10th
16:17:40 <virginie> https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html
16:18:24 <hhalpin> q+
16:18:36 <karen_> Virginie: hope to have something after Jan
16:19:08 <karen_> Harry: we can wait for one more week, otherwise add another editor
16:19:18 <markw> q+
16:19:25 <karen_> ... W3C prefer to have at least 2 co-editors
16:19:31 <hhalpin> q- hhalpin
16:19:37 <virginie> ack markw
16:19:43 <karen_> Mark: the only difficult is to get Ryan to say go ahead
16:20:00 <karen_> Mark - it is difficult to hear you
16:20:15 <hhalpin> Ideally, we would want Ryan on the phone, but we can propose over the mailing list first
16:20:26 <hhalpin> to make sure Ryan is fine with having a co-editor.
16:20:30 <karen_> Virginie: action - clarify editor status with Mark and Ryan
16:20:37 <markw> (for minutes) I am happy to be co-editor
16:21:04 <markw> q-
16:21:05 <hhalpin> Next version we can push off till end of Jan at earliest really
16:21:14 <hhalpin> But given amount of work, it may take till February at least
16:21:36 <hhalpin> I'd like "all hands on deck" to push bugfixes to spec out after Christmas vacation
16:21:44 <markw> q+
16:21:53 <karen_> Virginie: expect to have a spec by Jan 13th
16:22:33 <karen_> Mark: we can publish with mention of remaining bugs
16:22:43 <hhalpin> There was *lots* of clarifying text!
16:23:11 <karen_> Virginie: it seems to take too long to clarify bugs
16:23:36 <karen_> Mark: it is useful to draw up a list, editorial and technical
16:23:52 <karen_> ... it'll be difficult to draw a date for the technical ones
16:24:04 <hhalpin> The issue with Bugzilla and editorial/technical ones seem mixed up - happy to move technical ones back to Issue Tracker if that helps
16:24:19 <karen_> Virginal: priority list on the call?
16:24:31 <karen_> Mark: good
16:24:46 <virginie> +1
16:24:46 <israelh> -1
16:24:47 <hhalpin> Some groups meet during winter break, others don't.
16:24:52 <nvdbleek> -1
16:24:57 <hhalpin> It's up to group
16:24:57 <mountie> +1
16:25:04 <markw> -1
16:25:04 <karen_> +1
16:25:11 <markw> I have a conflict that day
16:25:21 <karen_> a poll to maintain a call on Jan 13th
16:25:44 <karen_> Virginie: try to see if Ryan can be there.
16:25:56 <karen_> ... if he cannot make it either, we will cancel
16:26:13 <karen_> ... next one will keep
16:26:23 <hhalpin> Wait a sec, the next meeting is Jan 13th, right?
16:26:26 <karen_> Virginie: any concern?
16:26:34 <hhalpin> The poll was over Dec 30th, Karen.
16:26:39 <karen_> mountie?
16:26:50 <hhalpin> s/a call on Jan 13th/a call on Dec 30th/
16:27:56 <virginie> http://www.w3.org/2012/webcrypto/track/actions/64
16:28:03 <virginie> action related to integration of SEED
16:28:03 <trackbot> Error finding 'related'. You can review and register nicknames at <http://www.w3.org/2012/webcrypto/track/users>.
16:28:34 <hhalpin> One idea is we should maintain a wiki of requested algorithms
16:28:46 <hhalpin> Melvin also wanted some ECC curves
16:28:57 <hhalpin> q+
16:29:20 <karen_> Virginie: Mountie - do you have suggestions?
16:29:34 <karen_> mountie: we are preparing some text
16:30:01 <karen_> Virginie: that's good. best to proceed is to preparing text
16:30:23 <karen_> ... should we maintain a wiki for requested algorithm?
16:31:11 <karen_> ... while people are pushing algorithms
16:31:35 <karen_> Virginie: we will create a wiki page to track requested crypto algo
16:31:42 <hhalpin> My logic is that while yet another wiki page might not be so fun, we're having a few recommendations for algorithms that aren't uniformly implemented in browsers
16:31:47 <hhalpin> q- hhalpin
16:31:57 <hhalpin> q- markw
16:32:16 <karen_> harry: Ryan pushed back on algos that are not implemented in browsers.
16:32:19 <hhalpin> ACTION virginie and hhalpin to create a wiki-page for suggested algorithms from mailing lists
16:32:19 <trackbot> Created ACTION-134 - And hhalpin to create a wiki-page for suggested algorithms from mailing lists [on Virginie GALINDO - due 2013-12-23].
16:32:29 <karen_> virginie: now discuss future work
16:32:30 <hhalpin> (btw, I think ryan pushing back is reasonable!)
16:32:34 <markw> markw has joined #crypto
16:32:40 <hhalpin> (but we should not lose track of requests for algorithms)
16:33:07 <karen_> virginie: let's look at where we are on future work
16:33:13 <virginie> Future work wiki : http://www.w3.org/2012/webcrypto/wiki/WG_Future_Work
16:34:32 <karen_> .... potential - web payment activity
16:34:45 <karen_> ... no leader for hardware token
16:35:21 <karen_> ... how do you want to be involved in this future work? suggestions?
16:35:26 <hhalpin> q+
16:35:53 <karen_> israel: we are interested in streams.
16:36:12 <karen_> ...in re-org now. by mid Jan, will know
16:36:42 <karen_> virginie: are couple of people are interested in hardware tokens. Nick would you be interested in?
16:37:21 <karen_> Nick: cannot commit at this time. may be January
16:38:12 <israelh> q+
16:38:21 <karen_> harry: suggestion - if we have interest but have trouble to have people to lead (stream), may be have a workshop in June
16:38:26 <hhalpin> http://www.w3.org/2011/identity-ws/
16:38:27 <hhalpin> in 2011
16:38:29 <hhalpin> workshop
16:38:40 <hhalpin> Does group want to do a workshop to get more energy?
16:39:05 <karen_> ... the group must say we are interested in
16:39:20 <hhalpin> Generally, there's about 6 months between a workshop and future work :)
16:39:27 <hhalpin> We would not need a workshop just to add streams
16:39:40 <hhalpin> but we would as regards anything around hardware tokens
16:39:46 <karen_> israel: the issue seems to be competitive proposals on streams
16:40:06 <karen_> ... webapp needs to have a uniformed proposal
16:40:28 <karen_> ... confusion in webapps' proposal prevents this moving forward
16:40:53 <karen_> harry: will be happy to push webapps WG
16:41:40 <karen_> ... clarify: workshop on hardware token
16:42:12 <hhalpin> ACTION: hhalpin to press on W3C Team re unified Streams proposal
16:42:13 <trackbot> Created ACTION-135 - Press on w3c team re unified streams proposal [on Harry Halpin - due 2013-12-23].
16:42:19 <karen_> Virginie: propose the scope on the workshop - hardware token, storage?
16:42:45 <karen_> ... write down different topics, submit to the workshop
16:42:55 <karen_> ... Harry can discuss with W3C
16:43:00 <karen_> Harry: great
16:43:29 <karen_> Virginie: I will write the scope with Harry and share with the group in Jan
16:43:54 <karen_> virginie: will reformulate the wiki by priority
16:44:13 <karen_> ... certificate mgmt will be a higher priority
16:44:23 <karen_> ... anything else?
16:44:39 <virginie> zakim, who is on the phone ?
16:44:39 <Zakim> On the phone I see markw, +1.617.253.aabb, mountie, hhalpin, [Microsoft], virginie, nvdbleek, Karen
16:45:21 <karen_> ... we will keep this call time at least for the next two
16:45:50 <virginie> https://www.w3.org/Bugs/Public/buglist.cgi?component=Web%20Cryptography%20API%20Document&product=Web%20Cryptography&resolution=---
16:46:15 <karen_> ... spec needs your support. if you have suggestions for resolving bugs, that'll be great
16:46:27 <hhalpin> thanks everyone!
16:46:30 <hhalpin> Next call Jan 13th
16:46:33 <karen_> ... thanks! talked to you Dec 13th
16:46:33 <Zakim> -[Microsoft]
16:46:34 <Zakim> -nvdbleek
16:46:34 <Zakim> -markw
16:46:34 <Zakim> - +1.617.253.aabb
16:46:35 <Zakim> -virginie
16:46:39 <Zakim> -hhalpin
16:46:41 <Zakim> -mountie
16:46:51 <gjs> gjs has left #crypto
16:46:52 <Zakim> -Karen
16:46:53 <Zakim> SEC_WebCryp()11:00AM has ended
16:46:53 <Zakim> Attendees were markw, +1.617.253.aaaa, +1.617.253.aabb, [Microsoft], virginie, +1.323.425.aacc, Karen, nvdbleek, hhalpin, mountie
16:47:24 <virginie> s/Next call Jan 13th/Next call Dec 30th unless cancelled
16:48:12 <hhalpin> RRSAgent, draft minutes
16:48:12 <RRSAgent> I have made the request to generate http://www.w3.org/2013/12/16-crypto-minutes.html hhalpin
17:52:35 <anders> anders has joined #crypto
18:46:20 <nvdbleek> nvdbleek has joined #crypto