15:47:43 RRSAgent has joined #privacy 15:47:43 logging to http://www.w3.org/2015/10/22-privacy-irc 15:47:45 RRSAgent, make logs 263 15:47:47 Zakim, this will be 15:47:47 I don't understand 'this will be', trackbot 15:47:48 Meeting: Privacy Interest Group Teleconference 15:47:48 Date: 22 October 2015 15:47:55 rrsagent, make logs public 15:50:00 Present+ Lukasz_Olejnik 15:54:01 present+ npdoty 15:55:15 tara has joined #privacy 15:56:49 regrets+ wseltzer 15:57:09 Zakim, clear agenda 15:57:09 agenda cleared 15:57:35 christine has joined #privacy 15:57:44 agenda+ Welcome and introductions 15:57:58 agenda+ Geofencing API http://www.w3.org/TR/geofencing/ 15:58:14 agenda+ Privacy and Security Questionnaire https://www.w3.org/wiki/Privacy_and_security_questionnaire 15:58:21 agenda+ Outstanding items 15:58:28 agenda+ AOB 15:59:04 regrets+ Lukasz_Olejnik 16:00:38 Waiting for more folks to join the WebEx before getting started... 16:03:18 kodonog has joined #privacy 16:04:07 volunteers to scribe? 16:04:30 moneill2 has joined #privacy 16:04:47 moneill2 or kodonog, care to scribe for us today? 16:05:35 ok 16:05:44 present+ moneill2 16:05:47 present+ kodonog 16:05:51 present+ tara 16:05:57 present+ christine 16:06:07 present+ mandyam 16:06:16 scribenick: moneill2 16:06:23 chair: christine, tara 16:08:02 Zakim, take up agendum 1 16:08:02 agendum 1. "Welcome and introductions" taken up [from npdoty] 16:08:05 Gary is giving background 16:08:10 S/Gary/Giri/ 16:08:28 Gary is chair of geolocation group 16:08:33 S/Gary/Giri/ 16:08:36 I can see the first slide w/sidebar. 16:10:14 Zakim, take up agendum 2 16:10:14 agendum 2. "Geofencing API http://www.w3.org/TR/geofencing/" taken up [from npdoty] 16:10:29 interoperabilty has been problem on mobile web. Geofencing ability to draw a geometrical shape determine if user device is inside or outside fence 16:11:05 Qualcom had pre-standard implementations on Android 16:12:13 18month ago restarted geolocation group, came up with geofencing API. Based on service workers, allowing web developer to persist a process 16:12:58 [slide 2] 16:13:36 no consensus on https origins 16:14:31 geofencing API uses https origins, better privacy than geolocation 16:16:03 there is a privacy & security section 16:16:26 s//Giri:/G 16:16:49 [slide 4] 16:17:26 only circular region defined so far 16:17:37 [slide 5] 16:19:20 [slide 4] 16:20:14 Present+ Lukasz_Olejnik 16:20:34 present+ Lukasz 16:20:46 requires a developer opt-in. Service workers requires data persistence 16:21:07 yeah, that persistence kind of scares me, since it's potentially entirely in the background 16:22:15 pervasive monitoring risk, what is users home location etc. is a problem. some solutions being talked about by browsers 16:23:01 should this be solved in API, or in meta context 16:23:09 q+ 16:23:44 ack ch 16:24:13 some potentially scary things about user awareness 16:24:38 we need to give some guidance 16:25:05 if I load a page on my friend's computer and then it works in the background forever, can I just track my friend's location into the future forever? 16:25:12 this is broader than geofencing, more and more sensor API functionality 16:25:16 q 16:25:21 ack me 16:26:03 maybe some best practices requirements for service workers? 16:26:36 have we talked to service worker group? 16:26:56 Ping needs to raise this right now 16:27:45 clear visibility/transparency display in browser UI 16:28:27 Had there been any discussion of using the Permissions API? 16:30:12 moneill2: revocability and expiry of permissions 16:30:22 q? 16:30:36 geolocation is in permission spec 16:32:37 guidance from PING on deviceorientation, access to sensors determine pin entry etc. 16:33:28 effort in device api working group 16:33:58 regarding deviceorientation: https://lists.w3.org/Archives/Public/public-geolocation/2015Aug/0003.html 16:34:19 +q 16:34:27 giri: deviceorientation is widely deployed, but never issued a Last Call 16:34:40 perpective on how we can coordinate at TPAC 16:35:09 christine is tara 16:35:31 s//tara:/ 16:35:53 geolocation TPAC agenda available, in joint meeting with automotive working group 16:36:33 ack christine 16:36:51 can you be at IETF/PING meeting 16:37:37 q+ on timeline 16:37:51 +q 16:38:18 ack np 16:38:18 npdoty, you wanted to comment on timeline 16:38:40 Nick will be at TPAC, when do we need to resolve thee issues 16:39:04 you are fading out gary 16:39:53 giri: on timeline, still have technical issues re: geofencing spec that need to be resolved 16:40:10 ... concerned about the stability of the questionnaire 16:40:28 ... if it's in good shape, can settle on a collective response to the questionnaire in quick order 16:40:35 ... would like it to be done no later than the end of November 16:40:36 still some tech issues, need to be resolved first, in questionaire is in good face, put to bed by end Nov 16:41:34 we need to keep changing questionaire 16:41:57 general issue with service workers, needs to be sorted 16:42:06 q? 16:42:41 serviceworkers not on PING list as of now, but it will be 16:42:53 ack moneill 16:43:16 moneill2: where do we find out about what's happening with service workers? is there a general requirement about data persistence for service workers? 16:43:35 giri: process persistence for service workers which requires some data persistence 16:44:03 ... then there are actual identifiers for the service worker themselves (scope URL), those identifiers also seem to persist 16:44:42 ... and underlying geolocation data is persisted in the sense of boundaries 16:45:04 ... Web Apps Working Group is working on Service Workers 16:45:17 https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#security-considerations 16:45:33 https://lists.w3.org/Archives/Public/public-webapps/ 16:46:15 giri: on our first geofencing implementation, we wanted a level of process persistence, and had a Persistent Web Workers, which we had trouble commercializing because of the problem of end user management 16:46:31 ... should we add UI to the browser? can the user see which worker is active? shut down workers? 16:46:55 ... had concluded that that kind of UI was going to be necessary 16:46:59 user manageability of erviceworkers was not resolved, ened up as a trade off, ui is necessary, dont know if it will happen 16:47:24 thanks gary 16:47:55 I'll add Geofencing and Service Workers to our ongoing wiki list 16:47:56 Present+ chaals 16:48:02 Zakim, take up agendum 3 16:48:02 agendum 3. "Privacy and Security Questionnaire https://www.w3.org/wiki/Privacy_and_security_questionnaire" taken up [from npdoty] 16:48:29 Greg is regrets, who's been working on this particular item 16:48:49 maybe talk about TPAC agenda, in short time left, TPAC great opportunity 16:49:02 Topic: TPAC preparation 16:49:50 q+ 16:50:11 webapps sound like a priority, e.g serviceworkers 16:50:36 ack chaals 16:51:05 webapps group is now webplatform , meeting on tuesday about serviceworkers 16:52:27 webplatfor is also covering everything html, chaals is joint chaire, user context has clerar privacy issues 16:52:34 chaals, is there a link on that? I'm not familiar with that particular a11y work 16:53:14 serviceworker discussion, should we try to raise discussion earlier 16:53:33 issues should be raised online on GitHub 16:54:00 question has this been taken into account 16:54:17 other TPAC items? 16:55:21 webpayment WG announced, al lot of privacy questions, early stage a good time to discuss privacy 16:56:08 -> https://w3c.github.io/indie-ui/indie-ui-context.html latest draft of User Context spec, now a deliverable for some WAI group... 16:56:15 Topic: AOB 16:56:31 https://www.w3.org/wiki/Privacy/Privacy_Reviews 16:56:54 +q 16:57:10 ack mon 16:57:36 moneill2: Permissions API (WebAppSec), it would be good to talk to people there at TPAC 16:57:39 s/some WAI group/the ARIA working group/ 16:57:46 ... in terms of user awareness and control 16:58:20 npdoty: sure, I'll try to look at that while at TPAC, and can share some comments on the list 16:59:04 [unfortunately I won't be in the meetings, although I will be at TPAC and hope to catch up with people there] 16:59:18 26 November is Thanksgiving (US) 16:59:33 3 December? 17:00:22 bye 17:00:36 trackbot, end meeting 17:00:36 Zakim, list attendees 17:00:36 As of this point the attendees have been npdoty, runnegar, tara, JoeHallCDT, LCPolan, KatieHS, Haritos-Shea, Lukasz_Olejnik, moneill2, kodonog, christine, mandyam, chaals 17:00:44 RRSAgent, please draft minutes 17:00:44 I have made the request to generate http://www.w3.org/2015/10/22-privacy-minutes.html trackbot 17:00:45 RRSAgent, bye 17:00:45 I see no action items