17:54:17 RRSAgent has joined #tagmem 17:54:17 logging to http://www.w3.org/2014/01/16-tagmem-irc 17:54:19 RRSAgent, make logs public 17:54:19 Zakim has joined #tagmem 17:54:21 Zakim, this will be TAG 17:54:21 ok, trackbot, I see TAG_Weekly()1:00PM already started 17:54:22 Meeting: Technical Architecture Group Teleconference 17:54:22 Date: 16 January 2014 17:55:02 twirl has joined #tagmem 17:55:33 +plinss 17:55:48 zakim, who is on the phone? 17:55:48 On the phone I see dka, plinss 17:58:39 +??P3 18:00:46 annevk has joined #tagmem 18:00:53 Domenic__ has joined #tagmem 18:01:54 I don't seem to have gotten the conference code 18:01:56 Zakim, passcode? 18:01:56 the conference code is 0824 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), annevk 18:02:07 nice trick thanks 18:02:28 +[IPcaller] 18:02:38 Zakim, [IP is me 18:02:38 +annevk; got it 18:03:13 scribe: annevk 18:03:15 + +1.650.253.aaaa 18:03:17 RRSAgent, draft minutes 18:03:17 I have made the request to generate http://www.w3.org/2014/01/16-tagmem-minutes.html annevk 18:03:19 + +1.408.355.aabb 18:03:24 that's me 18:03:37 RRSAgent, make logs public? 18:03:44 RRSAgent, make logs public 18:04:15 zakim, aabb is slightlyoff_ 18:04:15 +slightlyoff_; got it 18:04:25 zakim, aaaa is Domenic__ 18:04:25 +Domenic__; got it 18:04:53 regrets, but I'll be back as of next week 18:05:07 sorry for missing so many of these after I said I'd be back... injury :( 18:05:10 that seems backward? i am 408-355... not sure how all this works though 18:06:47 ht has joined #tagmem 18:06:51 congrats! 18:07:00 Topic: Minutes 18:07:11 PL: Any comments on the F2F minutes? 18:07:19 PL: Anyone had a chance to review them yet? 18:07:29 I haven't reviewed them... 18:07:37 happy to approve 18:07:41 PL: Does anyone want more time or should we just approve them as is? 18:07:52 Approve, I think 18:08:06 AK: Happy to approve them, had a quick look 18:08:14 RESOLUTION: London F2F minutes approved 18:08:19 Topic: Status 18:08:35 AR: I have done little since I landed the weekend. 18:08:45 AR: I plan to have my actions done by next week, as planned 18:09:15 AK: I did some more work on URLs and revived the IDNA discussion 18:09:35 DD: Seems to be an interesting discussion 18:09:50 https://github.com/w3ctag/spec-reviews/blob/f362beea9bfd9b9ef657e0260b0ef38e3c4b7bcc/2013/08/Push%20API.md 18:09:57 SK: I have a Push API review ^^ 18:10:19 SK: I think we should approve the review and resolve this issue 18:10:50 AK: I kinda forgot how we wrapped this up during the F2F 18:10:59 AR: I was meant to follow up 18:11:14 AR: I'd like to see a new draft before we have a new discussion 18:11:46 AR: And I'd like to have a collective opinion on the northbound protocol (site server to push server) 18:12:10 PL: I recall we asked them to set up an overall architecture document with regards to the protocols and API involved 18:13:14 PL: Anything else? 18:13:17 I don't think we should until we have a conversation about how their API might look 18:13:28 SK: Nope 18:14:02 AR: I think we should give them another crack at a draft and then have a discussion with them 18:14:05 -twirl 18:14:31 twirl, you're not connected 18:14:56 +??P3 18:15:03 PL: We agreed to work with Brian on the use of promises and service worker integration 18:15:13 s/PL/DKA/ 18:15:55 SK: We agreed that this part regarding the Push API in the browser should not be stopped by discussion on the northbound protocol 18:16:08 SK: and the protocol between the UA and the push server 18:16:21 wait, I thought UA/push-service was pretty clearly not in scope? 18:16:43 slightlyoff, citation needed 18:17:00 the entire debate over their charter? 18:17:02 (Although personally I don't care much for that part) 18:17:10 slightlyoff, the WebApps WG charter is super broad 18:17:31 PL: What are our next steps here? 18:17:40 SK: There's a big question considering service workers 18:17:46 SK: I don't know how to correctly resolve that 18:17:47 next steps: we should work with them to get a new draft in place, ASAP 18:17:57 and once they have that, we can try to identify outstanding issues 18:18:01 (like northbound sketch) 18:18:13 -twirl 18:18:19 twirl, you dropped 18:18:53 +??P3 18:19:46 DKA: My status update; welcome to the new members! 18:20:17 DKA: I want to give an update on the workshop between W3C and IETF on strengthening the internet against pervasive monitoring (SPRINT?) 18:20:26 DKA: I'm on the program committee! 18:20:42 DKA: The deadline for submissions is Monday 18:20:51 DKA: I'd like to put something together for tomorrow 18:21:19 seems I've dropped off 18:21:28 -Domenic__ 18:21:36 DKA: If people could think of technologies that help strengthen web security that'd be useful for the workshop 18:21:39 still watching here 18:21:48 DKA: In particular, slightlyoff, if you could help me with that in the next few days that'd be great 18:21:54 yes, I can 18:22:16 DKA: I'm going to use the document we have in GitHub tomorrow and fill it out further 18:22:45 -dka 18:22:50 PL: If you can let us know on when there's an update ready that'd be great 18:22:53 DKA: will do 18:23:25 sounds good 18:23:30 https://github.com/w3ctag/secure-the-web 18:24:27 DD: I want to update the promises guide document this weekend and have it ready for review by Tuesday 18:24:49 RRSAgent, draft minutes 18:24:49 I have made the request to generate http://www.w3.org/2014/01/16-tagmem-minutes.html annevk 18:25:18 -twirl 18:25:19 -annevk 18:25:21 -slightlyoff_ 18:25:25 -plinss 18:25:26 TAG_Weekly()1:00PM has ended 18:25:26 Attendees were dka, plinss, twirl, [IPcaller], annevk, +1.650.253.aaaa, +1.408.355.aabb, slightlyoff_, Domenic__ 18:31:33 TAG_Weekly()1:00PM has now started 18:31:40 +??P0 18:31:46 -??P0 18:31:48 TAG_Weekly()1:00PM has ended 18:31:48 Attendees were 18:33:16 Zakim, dude, go away 18:33:16 I don't understand 'dude, go away', annevk 18:33:19 Zakim, bye 18:33:20 Zakim has left #tagmem 18:33:26 RRSAgent, bye 18:33:26 I see no action items