15:51:00 RRSAgent has joined #privacy 15:51:00 logging to http://www.w3.org/2012/07/19-privacy-irc 15:51:10 rrsagent, make logs public 15:51:22 Meeting: Privacy Interest Group July Teleconference 15:51:31 zakim, ping me in 8 minutes 15:51:31 ok, matt 15:52:01 fjh has joined #privacy 15:57:31 christine has joined #privacy 15:58:11 Priv_IG()12:00PM has now started 15:58:17 + +1.613.304.aaaa 15:58:24 + +33.4.92.96.aabb 15:58:36 +npdoty 15:59:08 Joanne has joined #privacy 15:59:21 +??P11 15:59:30 zakim, code? 15:59:30 the conference code is 7464 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), matt 15:59:30 Zakim, aaaa is probably tara 15:59:32 +tara?; got it 15:59:32 matt, you asked to be pinged at this time 15:59:48 tara has joined #privacy 15:59:59 alissa has joined #privacy 16:00:36 613. 16:00:47 +justin 16:00:55 +KevinT 16:00:58 Zakim who is making noise? 16:01:08 + +358.504.87aacc 16:01:09 +matt 16:01:10 chair: tara 16:01:22 +??P34 16:01:40 Zakim, agenda+ Introductions 16:01:40 agendum 1 added 16:01:40 zakim, mute me 16:01:41 matt should now be muted 16:01:52 Zakim, agenda+ Dependencies (including Geo) 16:01:53 agendum 2 added 16:01:59 Zakim, agenda+ Liaisons 16:01:59 agendum 3 added 16:01:59 Zakim, Kevin T is really Joanne 16:02:00 I don't understand 'Kevin T is really Joanne', Joanne 16:02:11 Zakim, agenda+ Privacy Considerations 16:02:11 agendum 4 added 16:02:24 Zakim, KevinT is really Joanne 16:02:24 +Joanne; got it 16:02:31 We have received apologies from JC Canon, Trent Adams, Piero Bonatti, Susan Israel, Erin Kenneally 16:02:35 MarkL has joined #privacy 16:02:48 regrets+ JC, Trent, Piero, SusanIsrael, ErinKenneally 16:02:49 robin has joined #privacy 16:02:53 Regrets: JC Canon, Trent Adams, Piero Bonatti, Susan Israel, Erin Kenneally 16:02:54 Hi Everyone! 16:03:29 Hi all - apologies if I get this wrong: I am an IRC n00b 16:03:44 No problem. 16:04:06 Zakim, who is on the phone? 16:04:06 On the phone I see tara?, +33.4.92.96.aabb, npdoty, ??P11, justin, Joanne, +358.504.87aacc, matt (muted), ??P34 16:04:09 +bilcorry 16:04:17 Let us know if you're on IRC but not on the phone so we can repeat things you might miss. 16:04:32 thanks - am working on dialling in now... 16:04:40 Ashok_Malhotra has joined #privacy 16:05:06 i'm on irc but not the phone 16:05:09 bilcorry has joined #privacy 16:05:27 + +1.202.379.aadd 16:05:37 scribenick: Joanne 16:05:42 Zakim, who is on the call? 16:05:42 On the phone I see tara?, +33.4.92.96.aabb, npdoty, ??P11, justin, Joanne, +358.504.87aacc, matt (muted), ??P34, bilcorry, +1.202.379.aadd 16:05:52 Zakim, mute me 16:05:52 bilcorry should now be muted 16:05:56 +James 16:05:56 Zakim, agenda? 16:05:57 I see 4 items remaining on the agenda: 16:06:00 1. Introductions [from npdoty] 16:06:01 2. Dependencies (including Geo) [from npdoty] 16:06:04 3. Liaisons [from npdoty] 16:06:05 4. Privacy Considerations [from npdoty] 16:06:08 zakim, unmute me 16:06:17 matt should no longer be muted 16:06:28 I may not know who is talking . Please let me know who is speaking 16:06:48 Christin: anyone here for the first time? 16:06:55 s/Christin/Tara/ 16:07:10 I'm here for the first time... 16:07:15 Tara: intros 16:07:26 rudy: with Comcast global policy 16:07:44 +Ashok_Malhotra 16:08:11 Tara: next item looking at the dependencies 16:08:21 +33.4.92.96.aabb is : Karima :-) 16:08:25 zakim, mute me 16:08:25 Ashok_Malhotra should now be muted 16:08:31 Zakim, aabb is kboudaou 16:08:31 +kboudaou; got it 16:08:33 Matt: part of W3C team with geo-locations WG 16:08:46 Topic: Geo (with Matt) 16:08:52 ...first version of spec and will be released as recommendation soon 16:08:59 -> http://www.w3.org/TR/geolocation-API/#security 16:09:31 ...spec provides bunch of info on how to prtect invidual privacy on sites that use the API 16:09:51 ...alissia can speak about the CDT proposal 16:09:58 Patrick has joined #privacy 16:10:38 ...group came to consensus on section after much debate and now the hard part testing 16:10:39 GEOPRIV, http://datatracker.ietf.org/wg/geopriv/charter/ 16:10:53 ...found sites could conform to the requirements 16:10:58 ...not an easy task 16:11:46 concept that "an API should never be allowed to lie!" 16:11:46 ...challenges is the API can lie about where you are and the API should not be able to lie. lots of conserns 16:11:52 ...looked at this for a long time 16:12:04 +q 16:12:36 Tara: are there things PNG can do to be useful to your WG? what can we learn? 16:12:44 s/PNG/PING/ 16:12:54 Matt: right people involved from teh get-go is important 16:13:22 Richard Barnes from BBN was also involved 16:13:55 ... could actually see PING as a horizontal thing to get people involved across groups 16:13:59 ...PNG should be a horizontial thing and influence the work. Having privacy people involved from the beginning is important 16:14:18 q+ to ask about TAG review 16:14:23 ack christine 16:14:35 -npdoty 16:14:41 Christine: very helpful and couldn't agree more in having privacy people in the beginning 16:15:26 ...what are lessons learned in identifying privacy vulenbilities (sp). Example, how did the gropu think about privacy for that spec 16:15:27 +npdoty 16:15:34 -q 16:16:05 Matt: lessons I learned - a lot of engineers don't necessarily look at the privacy implications 16:16:44 ... radically different legal requirements (mandated in one country, prohibited in another) 16:16:47 +??P22 16:17:08 ...Vodafone involvement showed how laws vary across some countries. what is ok in one country may not be allowed in another country. how do you write a spec with varying laws and test that these things are possible to enforce 16:17:11 -??P22 16:17:58 ...one way to test is to read the privacy policy and test against that. trust the company does what they say are they are doing 16:18:07 -> http://www.w3.org/2008/geolocation/drafts/API/Implementation-Report.html#website-tests 16:18:08 \ 16:18:15 ...difficult to test and will link to test results 16:18:29 ...had more than just the three listed 16:18:44 ...non-trival task 16:18:46 ack npdoty 16:18:46 npdoty, you wanted to ask about TAG review 16:19:23 zakim, unmute me 16:19:23 Ashok_Malhotra should no longer be muted 16:19:32 Nick: wanted to ask about tag management. was tag review useful for uncovering privacy issues, and what role tag can play in reviewing areas around privacy? 16:20:07 Matt: not real formal but did talk to tag for an hour or two. not sure if we can call it a tag review or not 16:20:34 unknow: this version of the spec a lot better. thank you Matt 16:20:44 +??P31 16:20:52 s/unknow/Ashok/ 16:21:44 +q 16:21:46 q? 16:22:07 Hannes: privacy experts wasn't really heard. what do you think was done well around the privacy mechanisms. somewhat negative about the development within the group and get them to listen 16:22:26 Matt: did best to make sure all comments were responded to 16:22:27 ack alissa 16:22:36 ...Alissia may be able to comment more 16:23:11 Allisia (sp): disagree with Hannes characteristication (sp). 16:23:27 s/Allisia/Alissa/g 16:24:09 ....sending privacy rules around. did end up with strong normative language. Testing was difficult to make sure reqs in Sec 3 were meet 16:25:02 copying of sections of requirements on recipients wholesale into other specs, like device APIs, which might be advantageous 16:25:17 ...took some of this text wholesale and put them into their APIs. Reqs around receipents getting geo-location info hard to enforce 16:25:42 Matt: this did not just breeze right through. 16:25:54 Tara: last chance to comment 16:26:06 q+ 16:26:08 Privacy was pretty much our biggest hurdle, the technical stuff was insignificant compared to privacy actually. 16:26:10 ...going once, going twice 16:26:13 ack npdoty 16:27:14 +[IPcaller] 16:27:21 zakim, [IPcaller] is me 16:27:21 +fjh; got it 16:27:26 Nick: on the ques on testibility. we want to make it easy to test to determine conformance. should we make reqs more technicla and make privacy reqs testable against the spec 16:28:20 Matt: what is interesting about w3c testing people is we have to show that everything normative is implementable. low bar. not very strong. we want above and beyond w3c reqs 16:28:49 q? 16:29:47 unknown: how did deployment act in repsect to privacy? did that lead to any improvements in deployments? is there truly privacy prtoections 16:29:55 s/unknown/Hannes/ 16:30:50 Matt: it changed on the browser side and the receipent side. no one hasn't reporoted on redeployment since Nick wrote the paper 16:31:05 we thought about doing an updated study to see if there were deployment changes over time, but it's a hard thing to measure in a comparable way 16:31:36 ...browser is deployed with active consent to sharing location data. not sure about reciepent 16:31:39 -??P34 16:31:51 zakim, who is here? 16:31:51 On the phone I see tara?, kboudaou, ??P11, justin, Joanne, +358.504.87aacc, matt, bilcorry (muted), +1.202.379.aadd, James, Ashok_Malhotra, npdoty, ??P31, fjh 16:31:54 On IRC I see Patrick, bilcorry, Ashok_Malhotra, robin, MarkL, alissa, tara, Joanne, christine, fjh, RRSAgent, Zakim, npdoty, kboudaou, MacTed, matt, wseltzer 16:32:18 +??P34 16:32:20 Tara: that you Matt and hope we benfit from your experience and take advantage of that. 16:32:20 Zakim ??P11 is christine 16:32:35 Zakim, ??P11 is christine 16:32:35 +christine; got it 16:32:50 Zakim, justin is really alissa 16:32:50 +alissa; got it 16:33:10 Matt: love to help and am neutral about the deployments. will love to help and Alissia can input based on her experience 16:33:22 Tara: 3rd item ont eh agenda 16:33:36 Topic: IAB Privacy Program 16:33:37 http://tools.ietf.org/html/draft-iab-privacy-considerations-03 16:33:50 Tara: moving to alissa 16:34:21 Alissa: IAB protocols. Look at ToC's and run through the doc 16:34:37 Worked for me! Cool! 16:34:54 ...terminology section around privacy and describes terms used in the protocals 16:35:32 tara has joined #privacy 16:35:43 ...tired to make link between abstract threats and how internet proptocals. talk about ways threats can be mitigated 16:35:56 ...data minization 16:36:22 ...uyser participantion involving hte user in decisions about hisher data to minize threats 16:36:50 ...that is the setup to give designers who aren't use to think about privacy reasons to care about it 16:37:25 ...section 6 designed to give designers on how to think about privacy when designing protocoals 16:38:16 ...taks about difficulty around managing body list, etc. maxium utility of systems built using proptocals 16:38:26 ...love feedback on the doc 16:38:46 ...hoping to now get this to the folks out in th e ITF 16:38:47 zakim, mute me 16:38:47 matt should now be muted 16:38:51 ... section 7, an example, based on SIP, managing a buddy list, experience with all of the privacy problems that can appear in Internet protocols 16:38:51 ...main work item 16:39:10 ...privacy survey Hannes has been spreadheading 16:39:50 ...hoping to get feedback from people in the field 16:39:56 q? 16:40:15 Tara: that is a lot. impressive accomplishment 16:40:38 ...help out group ...feedback on survey items 16:40:43 ...questions? 16:40:46 q+ 16:41:10 Christine: compliments to Alissa and Hannes and others in the IAB program 16:41:13 ack npdoty 16:41:40 Nick: curous whether there is any experience with anyone trying to use the doc yet? 16:42:54 Alissa: not aware of anyone yet. I have pointed a few people to it working on early drafts and have gotten feedback. It is overkill. this was expected. I have tired to use it 16:43:13 Hannes: feedback has reulted in additional terminology and clarifications 16:43:21 Tata: more questions? 16:43:29 ...thanks again Alissa 16:43:31 s/Tata/tara/ 16:43:48 16:44:35 Topic: Privacy Considerations 16:44:43 tara: open to comment on how this should go forward 16:44:46 q+ 16:44:59 Tara: we are trying to get a sense of the best way to move forward on the document. Opening up for comment based upon experience on how to move forward 16:45:04 ack npdoty 16:46:29 Nick: we have discussed the importance of having privacy policy involved. write a guide for WG around when to seek out privacy expertise. some of this may be architure issues 16:46:35 rudy_ has joined #privacy 16:46:38 +q 16:47:22 ack christine 16:47:24 -q 16:47:25 Tara: when to bring people in with research and look for commonailities across groups to provide guidance 16:47:34 * decisional tool (help authors when they're making authoring decisions) 16:47:53 * issue spotting (helping WGs find when they should seek out expertise in understanding the privacy issues) 16:48:30 * architectural considerations (common issues that turn up on the Web that we'd like to handle in a consistent way) 16:48:36 -Ashok_Malhotra 16:48:43 q? 16:48:46 Christine: thank you Nick. I agree and we seem to be in agreement. A good way to make this happening is first provide guidance to WGs on when they need to invole PNG and TAG. Then identify common problems across the groups 16:48:51 +q 16:48:57 ack alissa 16:50:09 It could be that influencing a WG on privacy is a lot like influencing end users on privacy… i.e. hard. ;-) 16:50:09 +1 to alissa re difficulty of adding-in privacy into WG later, needs to be part of WG overall 16:50:15 alissa: might be controversial. it is diff to have influence over the trajectory of a WG by inserting a random timeline. you need to be involved the work of the group. 16:50:46 isn't that called "privacy by design" :) 16:50:53 ...advocate building this capability into those working across the w3c 16:51:18 Christine: agree and if we can get there that would be fantastic 16:51:46 Alissa: difficule, not necessarily controversal. its how we get there 16:51:58 q+ 16:52:21 In both cases, it's a problem of persuading people to adopt different privacy-related behaviours (and people's motivation for changing behaviour is notoriously tricky) 16:52:22 Nick: maybe that answers the question of when. having this integrated in the discussion from the beginning stages 16:52:45 Hannes: it is easy to say you need to consider security at the beginning same for privacy 16:53:24 I should also clarify: this is Robin Wilton, not Robin Berjon (Hannes is referring to a doc by Robin B) 16:53:26 ...what is the foundation you want to rely on. some people think data minization is the idea others think user consent is the best. there are other design regimes 16:53:44 ack fjh 16:53:50 ....need to ask the bigger question otherwise difficult to adivse 16:54:26 Sorry, that got converted to an emoji. I meant "Hannes is referring to a document by Robin Berjon" 16:54:28 fjh: it is a hard proble. it can't be bolt on later and needs to be done at the beginning. 16:54:36 +q 16:54:41 parties who aren't even in the Working Group may be relevant too; charter needs to get the right constituencies involved 16:54:42 Tara: challenges to get the right people involved 16:54:44 s/proble/problem/ 16:55:04 s/parties who/fjh: parties who/ 16:55:07 -q 16:55:10 s/beginning/beginning, including getting involvement of various constituencies./ 16:55:18 ack christine 16:55:40 Christine: may not have the answers today. 16:55:52 Hannes: I believe you are asking my thoughts 16:57:17 ...if you start with something like js api. if some scoping is included in the doc. the most improtant qustions are - is asking the user consnet on the api. sme other work that falls outside the js mechansim allow a much richer choice of approach to look into 16:57:26 -bilcorry 16:57:34 ...not bound by design decisionsof of the past 16:58:17 Tara: eye on the time. lots of considerations and putting together task force to wrk on doc, plus best praitces 16:58:25 ...move to mailing list and next agenda 16:58:26 if when/how to integrate into the process sounds like a good starting point for writing, I'm happy to help with that 16:58:37 and that might be something that doesn't duplicate the IAB document 16:58:38 ...last thing - the next call 16:58:56 16 August might be hard for me 16:58:58 Topic: Next call 16:59:10 ...week of Aug 16 around same time. Is there a conflict? can move to the aug 23rd 16:59:14 Thank you 16:59:14 August 16th? August 23rd? 16:59:24 Aug 23rd fine with me 16:59:27 ..August 23rd at this same time 16:59:31 16th *may* be an NSTIC meeting, according to OIX website... 16:59:56 ...tentative for Aug 23rd 17:00:11 Thanks Tara and Matt 17:00:18 -alissa 17:00:20 thanks 17:00:20 -christine 17:00:22 -Joanne 17:00:23 -npdoty 17:00:23 -fjh 17:00:25 - +358.504.87aacc 17:00:27 Thanks. Bye ! 17:00:27 -??P34 17:00:27 -tara? 17:00:28 -James 17:00:29 fjh has left #privacy 17:00:31 quit 17:00:35 - +1.202.379.aadd 17:00:36 rrsagent, draft minutes 17:00:36 I have made the request to generate http://www.w3.org/2012/07/19-privacy-minutes.html npdoty 17:00:37 -kboudaou 17:00:39 robin has left #privacy 17:00:47 -??P31 17:02:11 rrsagent, bye 17:02:11 I see no action items