15:16:50 <RRSAgent> RRSAgent has joined #crypto
15:16:50 <RRSAgent> logging to http://www.w3.org/2013/12/02-crypto-irc
15:16:57 <hhalpin> RRSAgent, make minutes
15:16:57 <RRSAgent> I have made the request to generate http://www.w3.org/2013/12/02-crypto-minutes.html hhalpin
15:17:55 <mountie> mountie has joined #crypto
15:22:31 <nvdbleek> nvdbleek has joined #crypto
15:24:36 <nvdbleek> nvdbleek has joined #crypto
15:26:03 <nvdbleek> nvdbleek has joined #crypto
15:27:41 <nvdbleek> nvdbleek has joined #crypto
15:55:22 <Anders> Anders has joined #crypto
15:55:36 <jyates> jyates has joined #crypto
15:55:59 <Zakim> Team_(crypto)16:00Z has now started
15:56:06 <Zakim> +??P17
15:56:27 <mountie> zakim, +??P17 is mountie
15:56:27 <Zakim> sorry, mountie, I do not recognize a party named '+??P17'
15:57:02 <mountie> zakim, mountie is +??P17
15:57:02 <Zakim> sorry, mountie, I do not recognize a party named 'mountie'
15:57:04 <wseltzer> trackbot, prepare teleconf
15:57:06 <trackbot> RRSAgent, make logs public
15:57:08 <trackbot> Zakim, this will be CRYPT
15:57:08 <Zakim> ok, trackbot, I see Team_(crypto)16:00Z already started
15:57:09 <trackbot> Meeting: Web Cryptography Working Group Teleconference
15:57:09 <trackbot> Date: 02 December 2013
15:57:12 <markw> markw has joined #crypto
15:57:23 <wseltzer> zakim, ??p17 is mountie
15:57:23 <Zakim> +mountie; got it
15:58:42 <jyates> When I try to call in, using the normal code, it says that the conference is restricted at this time.
15:58:47 <jyates> Is there a new code?
15:58:49 <virginie> virginie has joined #crypto
15:59:13 <virginie> hello web crypto wg :)
15:59:48 <wseltzer> zakim, code?
15:59:48 <Zakim> the conference code is 26632 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), wseltzer
15:59:50 <mountie> 26632#
16:00:18 <mete> mete has joined #crypto
16:00:25 <Zakim> +JYates
16:01:00 <Zakim> +[IPcaller]
16:01:15 <wseltzer> wseltzer has changed the topic to: Dec. 2 call on now, 1600 UTC
16:01:23 <Zakim> +nvdbleek
16:01:23 <wseltzer> wseltzer has changed the topic to: Dec. 2 call on now, 1600 UTC, code 26632#
16:01:24 <Zakim> + +1.512.257.aaaa
16:01:30 <markw> Zakim, [IPcaller] is me
16:01:31 <Zakim> +markw; got it
16:01:40 <nvdbleek> zakim, mute me
16:01:41 <Zakim> nvdbleek should now be muted
16:01:45 <virginie> zakim, aaaa is me
16:01:45 <Zakim> +virginie; got it
16:01:51 <virginie> agenda ?
16:01:56 <virginie> agenda+
16:02:15 <virginie> zakim, who is on the phone ?
16:02:15 <Zakim> On the phone I see mountie, JYates, markw, nvdbleek (muted), virginie
16:02:26 <Zakim> +Wendy
16:02:27 <Zakim> -Wendy
16:02:31 <virginie> agenda+ welcome
16:02:43 <Zakim> +Wendy
16:02:57 <virginie> agenda+ web crypto APIs (timing for LC)
16:03:12 <virginie> agenda+ AOB
16:03:15 <virginie> agenda ?
16:03:50 <wseltzer> Regrets+ mete
16:04:38 <Zakim> +[IPcaller]
16:04:51 <wseltzer> zakim, +IPC is hhalpin
16:04:51 <Zakim> sorry, wseltzer, I do not recognize a party named '+IPC'
16:04:55 <wseltzer> zakim, [IPC is hhalpin
16:04:55 <Zakim> +hhalpin; got it
16:05:01 <hhalpin> Zakim, IPcaller is hhalpin
16:05:01 <Zakim> sorry, hhalpin, I do not recognize a party named 'IPcaller'
16:05:28 <hhalpin> We might want to change the time *back* if no one is going to make the call at this hour
16:06:13 <Zakim> +karen_oDonoghue
16:06:32 <virginie> zakim, who is on the phone ?
16:06:32 <Zakim> On the phone I see mountie, JYates, markw, nvdbleek (muted), virginie, Wendy, hhalpin, karen_oDonoghue
16:06:42 <virginie> agenda?
16:07:01 <hhalpin> Note that W3C Process does not have a clear way for decisions to be made via mailing lists, so we could come as close as possible to a decision on the phone, and then formally make decision on the call.
16:07:25 <markw> agenda item proposal: attributes for JWK
16:07:40 <wseltzer> [we can do decisions via calls for objections via email]
16:08:00 <virginie> agenda+ attributes for JWK
16:08:23 <virginie> agenda?
16:08:25 <markw> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23796 (for my agenda item proposal)
16:09:08 <hhalpin> Zakim, pick a scribe
16:09:08 <Zakim> Not knowing who is chairing or who scribed recently, I propose nvdbleek (muted)
16:09:12 <hhalpin> Nick?
16:09:45 <wseltzer> scribenick: nvdbleek
16:10:02 <nvdbleek> TOPIC : web crypto APIs (timing for LC) [from virginie]
16:10:15 <hhalpin> Being "overloaded" generally means a co-editor is needed.
16:10:16 <nvdbleek> virginie: Rayn is overloaded so we nee to defer
16:10:27 <hhalpin> Markw - can you discuss?
16:10:32 <wseltzer> s/Rayn/Ryan/
16:10:34 <markw> not yet
16:10:43 <nvdbleek> virginie: markw you have been helping Ryan?
16:10:44 <hhalpin> q+
16:10:59 <nvdbleek> virginie: So you haven't started yet markw?
16:11:32 <nvdbleek> hhalpin: As it looks like Ryan is overloaded, maybe MarkW can do the editing
16:11:45 <nvdbleek> markw: Didn't talk to Ryan yet
16:12:25 <nvdbleek> hhalpin: I will be happy with markw being co-editor if it is OK with Ryan
16:12:34 <hhalpin> s/hhalpin/markw
16:12:36 <nvdbleek> virginie: So lets talk with Ryan
16:12:52 <hhalpin> Zakim, who's on the phone?
16:12:52 <Zakim> On the phone I see mountie, JYates, markw, nvdbleek (muted), virginie, Wendy, hhalpin, karen_oDonoghue
16:13:31 <nvdbleek> virginie: mete also volunteered to help
16:13:56 <nvdbleek> TOPIC:  attributes for JWK
16:14:09 <virginie> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23796
16:14:13 <nvdbleek> virginie: Why does it need to be discussed now?
16:14:35 <nvdbleek> markw: I made a proposal that is discussed on the list and the FtF
16:14:48 <nvdbleek> markw: I made a revision to address the comments
16:15:16 <nvdbleek> markw: I hope that the current silence means that everybody is OK with the proposal
16:15:18 <hhalpin> It sounds very reasonable to me
16:15:24 <nvdbleek> virginie: Any comments on the proposal?
16:15:41 <hhalpin> We'll need to be able to represent WebCrypto keys correctly in JWK obviously
16:15:49 <hhalpin> and if JOSE WG can't do this in the core, then we have to do it in a registry
16:15:51 <nvdbleek> virginie: Apparently no comments
16:16:12 <hhalpin> q+
16:16:15 <nvdbleek> virginie: Maybe we could give a last chance to comment on the mailing list
16:16:18 <nvdbleek> markw: OK
16:16:38 <nvdbleek> virginie: I need to check on how this table is made
16:17:32 <nvdbleek> hhalpin: Why does the core JWK wants us to ???
16:18:27 <nvdbleek> markw: we will register the extra properties in the IANA registry of JOSE
16:18:41 <wseltzer> q+
16:18:54 <virginie> ack hhalpin
16:19:19 <nvdbleek> hhalpin: I would propose mark asks it to add it to the IANA registry of JOSE because it takes time
16:19:34 <hhalpin> Kare - we do we expect the IANA registry to ready to roll?
16:19:35 <Zakim> +Karen.a
16:19:39 <nvdbleek> markw: The registry isn't there yet, they first going to add a section in there document
16:20:04 <nvdbleek> ???: Adding something to an IANA registry is not time consuming
16:20:16 <karen_> karen_ has joined #crypto
16:20:35 <virginie> zakim, who is on the phone ?
16:20:35 <Zakim> On the phone I see mountie, JYates, markw, nvdbleek (muted), virginie, Wendy, hhalpin, karen_oDonoghue, Karen.a
16:20:38 <wseltzer> q-
16:21:26 <hhalpin> My experience as regards things taking a while normally comes from the media-type registration process.
16:21:27 <nvdbleek> virginie: Mark can you send a last mail on the list for a call on consensus?
16:21:38 <nvdbleek> virginie: hhalpin or wseltzer what do you think?
16:22:10 <nvdbleek> markw: I don't see why we need to do another call, because there are no objections
16:22:22 <nvdbleek> virginie: OK we will go forward with the proposal
16:22:53 <wseltzer> s/markw:/hhalpin:/
16:23:24 <hhalpin> q+
16:23:43 <virginie> http://www.w3.org/2012/webcrypto/wiki/WG_Future_Work
16:23:46 <nvdbleek> TOPIC: MISC
16:23:47 <nvdbleek> wseltzer: The main work of the WG is to finalise the API, but also to discuss future work
16:24:06 <nvdbleek> wseltzer: There is a wiki page for future work http://www.w3.org/2012/webcrypto/wiki/WG_Future_Work
16:24:24 <nvdbleek> wseltzer: goes over the topics
16:24:28 <wseltzer> s/wseltzer:/virginie:/
16:24:46 <wseltzer> s/wseltzer: The/virginie: The/
16:25:06 <nvdbleek> virginie: Is there any news on the workshop for hardware tokens
16:25:20 <nvdbleek> we also have interest
16:25:31 <hhalpin> So workshops take about 3-4 month lead time.
16:26:10 <nvdbleek> hhalpin: W3C is interested, but the spring is already full, so summer or fall
16:26:15 <hhalpin> Just to be clear on timing
16:26:53 <nvdbleek> hhalpin: So future work will be only available fall the earliest or winter
16:27:19 <hhalpin> ack hhalpin
16:27:24 <Anders> http://lists.w3.org/Archives/Public/public-webcrypto-comments/2013Nov/0006.html
16:27:28 <hhalpin> Mountie?
16:27:40 <nvdbleek> mountie: Is there any schedule for the workshop
16:27:53 <hhalpin> the workshop would happen in summer at earlist, fall at latest
16:28:02 <nvdbleek> virginie: Mountie there is no schedule yet
16:28:30 <nvdbleek> virginie: The supporters should help hhalpin and wseltzer
16:28:41 <nvdbleek> q+
16:28:47 <nvdbleek> zakim, unmute me
16:28:47 <Zakim> nvdbleek should no longer be muted
16:29:10 <hhalpin> Workshops tend to go 30-70
16:29:17 <hhalpin> We generally need 1-2 sponsors to cover costs
16:29:30 <nvdbleek> zakim, mute me
16:29:30 <Zakim> nvdbleek should now be muted
16:30:00 <nvdbleek> virginie: If there are no more topics we can close the call
16:30:06 <hhalpin> I propose that we try this time for our next call, and if we still get low attendance we move back to the previous time.
16:30:48 <nvdbleek> virginie: You should send your agenda items before Friday to put them on the agenda
16:31:17 <nvdbleek> virginie: We don't know if people didn't turned up due to the agenda or the time
16:32:07 <nvdbleek> mountie: For rechartering work what is the link with the wiki?
16:32:43 <nvdbleek> virginie: I don't think most of the topics require rechartering, only the hardware token may require rechartering
16:33:19 <mete> by hardware token we mean all the hardware related integrations right ? smart card etc.
16:35:09 <hhalpin> thanks!
16:35:10 <Zakim> -JYates
16:35:10 <virginie> bye
16:35:12 <Zakim> -mountie
16:35:12 <nvdbleek> virginie: We close the call, talk to you in two weeks
16:35:13 <hhalpin> RRSAgent, generate minutes
16:35:13 <RRSAgent> I have made the request to generate http://www.w3.org/2013/12/02-crypto-minutes.html hhalpin
16:35:14 <Zakim> -markw
16:35:14 <Zakim> -Wendy
16:35:15 <Zakim> -karen_oDonoghue
16:35:15 <Zakim> -Karen.a
16:35:18 <Zakim> -virginie
16:35:20 <Zakim> -hhalpin
16:35:29 <Zakim> -nvdbleek
16:35:30 <Zakim> Team_(crypto)16:00Z has ended
16:35:30 <Zakim> Attendees were mountie, JYates, nvdbleek, +1.512.257.aaaa, markw, virginie, Wendy, [IPcaller], hhalpin, karen_oDonoghue, Karen
17:39:53 <danny_> danny_ has joined #crypto
17:59:36 <nvdbleek> nvdbleek has joined #crypto
18:27:20 <nvdbleek> nvdbleek has joined #crypto
18:37:16 <nvdbleek> nvdbleek has joined #crypto
18:39:56 <nvdbleek> nvdbleek has joined #crypto
18:42:28 <nvdbleek> nvdbleek has joined #crypto
18:46:54 <nvdbleek> nvdbleek has joined #crypto
18:55:35 <nvdbleek> nvdbleek has joined #crypto
19:12:36 <nvdbleek> nvdbleek has joined #crypto
19:16:21 <nvdbleek> nvdbleek has joined #crypto
19:30:53 <nvdbleek> nvdbleek has joined #crypto
19:35:36 <nvdbleek> nvdbleek has joined #crypto
19:41:18 <nvdbleek> nvdbleek has joined #crypto
19:47:44 <nvdbleek> nvdbleek has joined #crypto
19:56:43 <nvdbleek> nvdbleek has joined #crypto
20:04:09 <nvdbleek> nvdbleek has joined #crypto
20:05:46 <nvdbleek> nvdbleek has joined #crypto
20:23:16 <nvdbleek> nvdbleek has joined #crypto
20:32:36 <nvdbleek> nvdbleek has joined #crypto
20:35:31 <ale> ale has joined #crypto
20:37:34 <nvdbleek> nvdbleek has joined #crypto
20:44:34 <nvdbleek> nvdbleek has joined #crypto
20:55:52 <nvdbleek> nvdbleek has joined #crypto
20:59:18 <nvdbleek> nvdbleek has joined #crypto
21:01:30 <nvdbleek> nvdbleek has joined #crypto
21:04:57 <nvdbleek> nvdbleek has joined #crypto
21:07:09 <nvdbleek> nvdbleek has joined #crypto
21:15:50 <nvdbleek> nvdbleek has joined #crypto
21:21:54 <nvdbleek> nvdbleek has joined #crypto
21:55:16 <nvdbleek> nvdbleek has joined #crypto
22:02:41 <nvdbleek> nvdbleek has joined #crypto
22:06:16 <nvdbleek> nvdbleek has joined #crypto
22:25:51 <nvdbleek> nvdbleek has joined #crypto
22:33:13 <nvdbleek> nvdbleek has joined #crypto
23:10:00 <danny_> danny_ has joined #crypto