15:56:33 RRSAgent has joined #dnt 15:56:33 logging to http://www.w3.org/2013/05/29-dnt-irc 15:56:35 RRSAgent, make logs world 15:56:35 Zakim has joined #dnt 15:56:37 Zakim, this will be 15:56:37 I don't understand 'this will be', trackbot 15:56:38 Meeting: Tracking Protection Working Group Teleconference 15:56:38 Date: 29 May 2013 15:56:41 Zakim, this is TRACK 15:56:41 ok, npdoty; that matches T&S_Track(dnt)12:00PM 15:56:47 Zakim, who is on the phone? 15:56:47 On the phone I see +1.202.587.aaaa, JeffWilson, efelten, +1.646.654.aabb 15:56:53 Zakim, aaaa is Jules_Polonetsky 15:56:53 +Jules_Polonetsky; got it 15:56:53 aabb is eberkower 15:56:58 Zakim, aabb is eberkower 15:56:58 +eberkower; got it 15:57:02 jackhobaugh has joined #dnt 15:57:04 WaltMichel has joined #DNT 15:57:22 CraigSpiezle has joined #dnt 15:57:42 peterswire has joined #dnt 15:57:56 zakim, code? 15:57:56 the conference code is 87225 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), rigo 15:58:26 jchester2 has joined #dnt 15:58:28 Chris_IAB has joined #dnt 15:58:31 +Wendy 15:58:38 +NAI 15:58:41 hello privacy campers! 15:58:41 +Rigo 15:58:47 + +52661100aacc 15:58:55 just joined 15:58:59 Yianni has joined #DNT 15:59:05 + +1.215.286.aadd 15:59:11 +jchester2 15:59:15 zakim, mute me 15:59:15 jchester2 should now be muted 15:59:28 +npdoty 15:59:38 + +1.202.587.aaee 15:59:50 202.587 is peter and yianni 15:59:56 Zakim, aaee is peterswire 15:59:58 +peterswire; got it 15:59:59 + +1.646.827.aaff 16:00:02 Zakim, peterswire has Yianni 16:00:02 +Yianni; got it 16:00:05 phildpearce has joined #dnt 16:00:07 +[IPcaller] 16:00:10 Zakim, aadd may be susanisrael 16:00:10 zakim, [IPCaller] is me 16:00:11 +susanisrael?; got it 16:00:11 +moneill2; got it 16:00:12 paulohm has joined #dnt 16:00:27 Brooks has joined #dnt 16:00:27 fielding has joined #dnt 16:00:29 WileyS has joined #dnt 16:00:37 +phildpearce 16:00:43 +Peder_Magee 16:00:50 +Fielding 16:01:00 vinay has joined #dnt 16:01:08 magee2023263538 has joined #dnt 16:01:08 npdoty, yes 16:01:09 dwainberg has joined #dnt 16:01:10 +WileyS 16:01:11 rvaneijk has joined #dnt 16:01:18 Zakim, aacc is Chris_IAB 16:01:18 +Chris_IAB; got it 16:01:20 +rvaneijk 16:01:25 hwest has joined #dnt 16:01:26 +paulohm 16:01:32 +vinay 16:01:47 hefferjr has joined #dnt 16:01:56 +hwest 16:02:01 ChrisPedigoOPA has joined #dnt 16:02:08 robsherman has joined #dnt 16:02:31 + +1.202.257.aagg 16:02:36 zakim, aagg is robsherman 16:02:36 +robsherman; got it 16:02:39 scribenick: Yianni 16:02:58 +Chris_Pedigo 16:03:04 +Craig_Spiezle 16:03:18 JC has joined #DNT 16:03:22 David_MacMillan has joined #dnt 16:03:23 +hefferjr 16:03:24 Peter: we are getting started 16:03:31 adrianba has joined #dnt 16:03:33 Zakim, who is on the phone? 16:03:33 On the phone I see Jules_Polonetsky, JeffWilson, efelten, eberkower, Wendy, NAI, Rigo, Chris_IAB, susanisrael?, jchester2 (muted), npdoty, peterswire, +1.646.827.aaff, moneill2, 16:03:34 ...agenda for call: number of action items 16:03:37 ... phildpearce, Peder_Magee, Fielding, WileyS, rvaneijk, paulohm, vinay, hwest, robsherman, Chris_Pedigo, Craig_Spiezle, hefferjr 16:03:37 peterswire has Yianni 16:03:37 +mecallahan 16:03:48 ...discuss additional activities around consensus action summary 16:03:48 +[Microsoft] 16:03:56 ...clarify pending review stable 16:03:56 Zakim, NAI has jackhobaugh, marcgroman 16:03:56 +jackhobaugh, marcgroman; got it 16:03:58 mecallahan has joined #dnt 16:04:02 +schunter 16:04:02 ninjamarnau has joined #dnt 16:04:06 sidstamm has joined #dnt 16:04:06 ...like to thank Nick to clean up open aciton items 16:04:15 +[Mozilla] 16:04:17 + +1.650.365.aahh 16:04:18 Zakim, Mozilla has sidstamm 16:04:18 +sidstamm; got it 16:04:44 ...in terms of items that have received a lot of back and forth: one of them is action 410 16:04:51 +??P70 16:04:51 zakim, aaff is dwainberg 16:04:51 +dwainberg; got it 16:04:55 ...Walter and Rob have written about 16:05:00 zakim, who is here? 16:05:00 On the phone I see Jules_Polonetsky, JeffWilson, efelten, eberkower, Wendy, NAI, Rigo, Chris_IAB, susanisrael?, jchester2 (muted), npdoty, peterswire, dwainberg, moneill2, 16:05:01 Chapell has joined #DNT 16:05:03 ... phildpearce, Peder_Magee, Fielding, WileyS, rvaneijk, paulohm, vinay, hwest, robsherman, Chris_Pedigo, Craig_Spiezle, hefferjr, mecallahan, [Microsoft], schunter, [Mozilla], 16:05:03 ... +1.650.365.aahh, ??P70 16:05:03 peterswire has Yianni 16:05:04 [Mozilla] has sidstamm 16:05:04 NAI has jackhobaugh, marcgroman 16:05:04 ...Walter are you on the call? 16:05:05 On IRC I see sidstamm, ninjamarnau, mecallahan, adrianba, David_MacMillan, JC, robsherman, ChrisPedigoOPA, hefferjr, hwest, rvaneijk, dwainberg, magee2023263538, vinay, WileyS, 16:05:05 ... fielding, Brooks, paulohm, phildpearce, Yianni, Chris_IAB, jchester2 16:05:05 +[Microsoft.a] 16:05:06 zakim, [Microsoft.a] is me 16:05:07 +adrianba; got it 16:05:08 +Amy_Colando 16:05:10 ...Rob are you on the call? 16:05:13 Zakim, aahh is David_MacMillan 16:05:13 +David_MacMillan; got it 16:05:23 ...thank you Rob for your comments 16:05:36 ...Rob could you describe the issue and your understanding 16:06:07 Rob: disagreement with Walter, the issue may not be covering his concerns 16:06:08 marc has joined #dnt 16:06:25 ...at the moment, it is not a real big issue 16:06:36 ...agree with what Roy has said so far 16:07:05 +Brooks 16:07:14 Peter: Moving issue to closed, Roy did not support any language 16:07:23 q? 16:07:23 ...anyone to speak against closing the issue 16:07:38 +RichardWeaver 16:07:42 ...we will recirculate intent to close 16:07:49 ...we will close issue 184 and action 410 16:07:55 + +1.646.666.aaii 16:07:56 Richard_comScore has joined #dnt 16:08:03 zakim, aaii is chapell 16:08:03 +chapell; got it 16:08:10 ...action 406, new set of names around the yellow state 16:08:12 npdoty has changed the topic to: agenda: http://lists.w3.org/Archives/Public/public-tracking/2013May/0125.html 16:08:30 ...red, yellow, green has some advantages 16:08:55 +kulick 16:09:02 ...goal to be understandable, not making any legal judgment, and if we use words used elsewhere, we need to be thoughtful, such as de-identified 16:09:04 kulick has joined #dnt 16:09:18 action-406? 16:09:18 ACTION-406 -- Rob van Eijk to porpose a new set of names around yellow state -- due 2013-05-29 -- OPEN 16:09:18 http://www.w3.org/2011/tracking-protection/track/actions/406 16:09:19 We should also try to avoid technology specific terms, such as "hashed", and focus on principles 16:09:29 jeffwilson has joined #dnt 16:09:29 ...Rob in addition to substantive questions, where are we in naming 16:10:01 Rob: Shane and I have basic disagreement, on role of administrative safeguards 16:10:09 ...unlinkability is about adding new data 16:10:23 Tech + Operational + Administrative can equal "de-identified" (unlinkablity is different and must stand on its own) 16:10:25 -robsherman 16:10:28 ...identifiability is different from unlinkability, taking account of all means to identify a natural person 16:10:40 ...important to get language right 16:10:46 RE: identifiability is not linkability. linkability is the possibility to add new data to an existing profile 16:10:59 ...FTC and NAI notion of de-identification is a process, start with looking at raw data 16:11:15 ...first step consists of taking out directly identifiable elements, email address 16:11:26 ...second step, partially de-identified level 16:11:48 Important to note "reasonably identifiable" in the EU context 16:11:49 ...not reasonable linked, need to take extra effort t otake out indirect identifiers 16:11:56 q? 16:12:01 ...to accomplish full de-identified process, i have proposed a three state model 16:12:18 This is a very important proposal, and we thank Rob for this. 16:12:22 ...raw data, to get from raw data to yellow or de-identified, you need data scrubbing 16:12:34 ...to get to full de-identified, you need to do something else 16:12:42 Yahoo! has been using a tri-state deidentification process for nearly 7 years - heavily reviewed with DPAs and A29WP 16:12:54 ...de-identification is a way to look at end result, how difficult is it for a party to identify to a user or device 16:13:04 ...a hahed pseudonym could make it very difficult 16:13:13 Shane: So what Yahoo is using to target users, such as with Genome, is all Yellow? 16:13:18 ...it is a way to address reasonable requirements of adequate level of protection 16:13:40 ...an adequate level of data proteciton is different from concept of unlinkability 16:13:46 ...Rob will post in IRC 16:14:06 Jeff - no, that data is the raw state for non-opted-out users (but the raw events are scored and only the score remains for targeting - not the event level data) 16:14:23 ...main difficulty is to determine that data that has gone through first step of de-identificaiton under strong assumption of organization safeguards is that enough to count as full de-identification 16:14:31 Peter: how do we describe these 16:14:39 PII: This standard refers to the ISO 29100 (privacy framework) definition of personally identifiable information (PII): any information that (a) can be used to identify the PII principal to whom such information relates, or (b) is or might be directly or indirectly linked to a PII principal. NOTE To determine whether a PII principal is identifiable, account should be taken of all the means which can reasonably be used by the privacy stakeholder holding the[CUT] 16:14:40 is the difference that Shane and Rob disagree on the use of organizational safeguards between red and yellow state or between yellow and green state? 16:14:44 ...we have long standing concern of technical or administrative measures 16:14:50 ...have a question about naming 16:14:56 But it also must be discussed in terms of what it may mean for a meaningful DNT standard. 16:15:00 ...first step, take out direct identifiers 16:15:08 ...second step, take out indirectly idenfifiers 16:15:12 What's the dividing line between "direct" and "non-direct" identifiers? 16:15:13 ...first, not directly identifiable 16:15:17 +q 16:15:20 ...second, not indirectly identifiable 16:15:21 "reasonable" is important 16:15:28 ...could put reasonably in front 16:15:40 ...direct identifiers have an intuitive meaning, Peters name in it 16:15:44 Peter: Why can't we use the sample color labels, which a user can better understand? 16:15:50 q? 16:15:57 ...offer that as a thought or suggestion 16:15:59 ack moneill 16:16:19 Mike Oneil: differences between unlinkability and de-identified is not just about direct and indirect 16:16:21 q? 16:16:22 I'm fine with "not directly identifiable" (aka de-identified) and "not indirectly identifiable" (aka unlinkable) 16:16:32 ...if data point from same person can be linked 16:16:34 q+ 16:16:40 If we are going to distinguish between "direct" and "indirect" we need to define what the difference is. Not enough to just give a few examples. 16:16:41 ...with yellow, there is the potential about being re-identified 16:16:57 Peter: 2 different tasks, one what do we name the state? 16:16:59 q? 16:17:06 ...second task, is it good enough to fit into the state 16:17:10 +q 16:17:14 ack ri 16:17:24 Rigo: I think we have several functions, I wanted us to think in functions 16:17:36 ...the names we use are replacements for functions we have 16:18:00 ...if I have a profile without a name but can single out that person in anyway, I can still distriminate against that person 16:18:04 q+ 16:18:13 Potential, or risk, is a core element of the middle state - organizations are committing to not re-identify (and bolstering this with technical, operational, and administrative controls). This is an "accountability" based approach. Very similar to many other organizational committments to users. 16:18:23 ...data protection function, and goal of what we do here, because people are discriminated because they are singled out 16:18:32 ...if we go to yellow, we need at least a pool of 50 people 16:18:33 wait, who's discriminating? 16:18:41 ...not too much of a controversy about it 16:18:41 +[IPcaller] 16:18:49 Peter: does that inform your view on the naming? 16:18:49 Rigo, no issues there - please provide wording to match the concern. 16:18:52 zakim, ipcaller is Walter 16:18:52 +Walter; got it 16:18:54 Thanks Rigo. "singling out" is the important issue imo. 16:19:08 + +1.650.465.aajj 16:19:13 Rigo: shouldn't care too much about the name, just do not want to allow discrimination 16:19:15 -David_MacMillan 16:19:22 Peter: name can confuse or lead to assumptions 16:19:24 kj has joined #dnt 16:19:36 +q 16:19:40 Ed Felten: if we are relying on a difference between direct or indirect, we need a technical definition 16:19:43 zakim, aajj is David_MacMillan 16:19:44 +David_MacMillan; got it 16:19:45 ...very difficult line to draw 16:19:46 Ninja and Rigo - your callout is well aligned with the intentions of the tri-state proposal 16:19:59 ack efelten 16:20:06 Peter: one problem with label is that any labels will have difficult line drawing 16:20:13 ...are there better summary terms 16:20:17 ack rvan 16:20:23 zakim, unmute me 16:20:23 jchester2 should no longer be muted 16:20:49 Rob: one response to Rigo, we should first try to get 3 stages rights, then we have a foundation to build on, what permitted uses are allowed in what state 16:20:59 q? 16:21:05 ...second, linkability is the key element, the second element is data retention 16:21:06 ack jche 16:21:11 WileyS, Rob, ok, not interfering too much with your plan to tackle one thing at a time 16:21:13 first get the 3 states right it allows to have a discuuion about the permitted uses Linkability is key Data retention 16:21:34 Jeff Chester: I don't see a distinction, you do not need a name, it is direct not indirect at all 16:21:48 WileyS: what is the current location in the Spec for that wording? 16:21:51 ...agree with Rob, that if we get this right, we can move forward 16:21:53 q? 16:21:53 zakim, mute me 16:21:54 jchester2 should now be muted 16:21:59 jchester: a persistent identifier can be used for targeting 16:22:00 ...personally like the red, yellow, green 16:22:04 Rob - correct me if I'm wrong, but I believe we agree on the states and the process, and only disagree on naming. Fair? 16:22:20 +q 16:22:37 Jeff, once a record has been made "not directly identifiable" then it can no longer be used for targeting. 16:22:37 q? 16:22:50 WileyS, I do not mind the tri-state. My concerns are about the measures and requirements in the yellow state. whatever we call this state. 16:22:51 Rob: differeneces between getting to one state or another, describing state is in terms of requirements 16:23:01 ack mone 16:23:23 Mike Oneil: getting to one word is the problem, yellow state is de-id but still linked, green state is unlinked 16:23:33 ...we should use both linked and unlinked, de-identified and identified 16:23:37 Ninja - that's fair. The goal of the yellow state is force this data to only be used for analytical purposes - no active use in production situations (profiling, targeting, etc.). 16:24:02 Peter: action item for 2 weeks, Peter would write up, glad to help, directly and indirectly identified language 16:24:12 ...other proposals red, yellow, green, jeff supporting 16:24:23 ...Jeff would you write up an action item text describing names for that 16:24:34 peterswire, npdoty, many (most) of us from industry won't be able to make next week's call due to a DAA event 16:24:38 I'm fine with pictorally displaying red, yellow, green but I think we need more meaningful terms for policy discussions. 16:24:39 ...trying to get text generated, understand problem of drawing lines between the two 16:24:42 vincent has joined #dnt 16:24:45 What does Rob plan to do on the states? 16:24:45 ...open to other language names 16:24:53 ...I will provide direct and indirect language 16:25:06 action: swire to draft directly/indirectly -identified language proposal 16:25:07 Created ACTION-412 - Draft directly/indirectly -identified language proposal [on Peter Swire - due 2013-06-05]. 16:25:07 s/pictorally/pictorially 16:25:08 +vincent 16:25:12 q? 16:25:14 ...Mike you said several pieces, if you have other naming approaches, we will look at in two weeks 16:25:22 action-412 due 06-10 16:25:22 Set ACTION-412 Draft directly/indirectly -identified language proposal due date to 06-10. 16:25:40 Peter: Jeff Chester action 411 on issue 10 16:25:47 zakim, unmute me 16:25:47 jchester2 should no longer be muted 16:26:06 Jeff Chester: we have nothing to say, I think at this point we have to let it pass 16:26:13 zakim, mute me 16:26:13 jchester2 should now be muted 16:26:19 Peter: we will move to pending review stable 16:26:31 ...shift to pending review stable 16:26:31 item would still be pending review (so keep reviewing it!), not closed. 16:26:43 Recognizing the interdependence of many issues within the compliance spec, we are introducing a new issue category “Pending Review Stable.” The category will fall between “Pending Review” and “Closed.” “Pending Review Stable” means that discussions of the issue will cease until other issues are stable. When the Editors decide to add proposed text to the Tracking Compliance and Scope, the issue will move from open to pending review. When the [CUT] 16:27:00 Peter: this is language we circulated to group some time ago 16:27:02 note for nick: move ISSUE 10 to Pending Review Stable, with note 16:27:21 ...we are trying to clean up action items and merge issues when possible, so website will accurately show we things are at today 16:27:29 ...that will allow us to focus on remaining items 16:27:38 ...idea of pending review stable is interdependence of many issues 16:27:55 [continued] When the Chairs decide the text is stable, a note will be added to the issue-tracker stating the issue is “Pending Review Stable.” There could potentially be multiple stable options when the Chairs decide an issue is “Pending Review Stable.” Discussion of an issue in “Pending Review Stable” can re-start if there is a new proposal that gains significant support. 16:27:56 jmayer has joined #dnt 16:28:02 +Jonathan_Mayer 16:28:15 ...5 or 6 interrelated issues, hard to finalize until they know how different sets of issues fit together 16:28:38 ...there would still be pending review, and pending review stable would not be closed 16:28:54 ...pending review stable is that discussion of issues would cease until we could look at whole package 16:29:00 Jonathan. Do you have any comments on action 411, issue 10. We just allowed it to move to pending review before you joined call. 16:29:28 ...if Editors add proposed text it goes from open to pending review, then when language is stable, we will add a note of pending review stable 16:29:43 q? 16:29:50 ...we do not expect to discuss a pending review stable unless a new proposal is made with substantial support 16:30:11 q? 16:30:15 johnsimpson has joined #dnt 16:30:21 ...hope would be if we have lots of issues in pending review stable, we could look at things in a whole package 16:30:57 ...going back to action item lists, we have other actions scheduled to be done by this date 16:31:08 action-402? 16:31:08 ACTION-402 -- Shane Wiley to work with Dan to follow up on defining the "yellow" to "green" transaction with strong enough measures -- due 2013-05-28 -- OPEN 16:31:08 http://www.w3.org/2011/tracking-protection/track/actions/402 16:31:11 Yianni, I put the notes on the mailinglist, it is too big to past in IRC. 16:31:11 ...action 402 - shane and dan, three states 16:31:47 http://www.w3.org/2011/tracking-protection/track/actions/overdue 16:31:58 Shane: we take language of Dan as is, we will be adding a few additional non-normative examples that do not go to as strong a technical measure to meet end point 16:32:01 +q 16:32:11 +johnsimpson 16:32:15 ...the question is moving from red to yellow, from raw to not directly identifiable 16:32:23 apologies for joining late 16:32:26 ...we will need new language for next week 16:32:26 -q 16:32:33 Peter: extend new language until two weeks 16:32:39 action-402 due 06-10 16:32:40 Set ACTION-402 Work with Dan to follow up on defining the "yellow" to "green" transaction with strong enough measures due date to 06-10. 16:32:48 Shane: we have plan to assemble language, just need to get the language in fron of Dan 16:32:55 I apologize. Have to go testify at USTR on data protection issues. 16:33:03 -jchester2 16:33:12 action-403? 16:33:12 ACTION-403 -- Justin Brookman to write language on red / yellow / green -- due 2013-05-15 -- OPEN 16:33:12 http://www.w3.org/2011/tracking-protection/track/actions/403 16:33:19 Peter: on action list, Shane had 402, Justin is assigned to 403 16:33:20 Yianni: URL is here http://lists.w3.org/Archives/Public/public-tracking/2013May/0135.html 16:33:28 Thanks Rob 16:33:44 Shane: Justin has a mission with respect to 403 for him to resolve 16:34:06 Peter: could you coordinate with Justin 16:34:32 justin may have a separate issue with red-yellow-green, so will maintain his own action 16:34:37 Shane: Justin has a very unique concern, maybe more appropriate for Dan to work with Justin, they have same concern 16:34:48 WileyS: Justin added this action-403 for himself to have a specific angle on the question of red/yellow/green and suggest to wait until he gets back. Suggest to add Dan to it as he may have same concerns 16:35:16 Peter: rigo any update on audience measurement 16:35:39 Rigo: Susan will go back to Jeff Chester where we will figure out what the issues are to try to get a better understanding 16:35:51 ...tricky issue is common understanding of what we are talking about 16:35:57 q+ 16:36:03 ...after this call, I will have a call with Susan 16:36:08 q? 16:36:16 ack rvan 16:36:41 Rob: in the text Rigo and Susan are working on, the data is not applied to individual, audience attribution is not what we are dealing with 16:36:53 ...I am worried about the application of the data to the individual 16:37:00 q+ 16:37:08 Rigo: I know about concern, Susan said this is not what we are talking about 16:37:14 q? 16:37:18 ...audience attribution is not what we are talking about 16:37:27 ack hefferjr 16:37:40 Ronan.. make sure Neilson is included in audience measurement discussion 16:37:54 +Dan_Auerbach 16:38:01 rigo and susan, can you CC Ronan on email thread? 16:38:04 Rigo: whatever we do will be in full and open scrutiny 16:38:24 Peter: RIchard you wanted to keep action 370 open 16:38:27 dan_auerbach has joined #dnt 16:38:32 action-370? 16:38:32 ACTION-370 -- Richard Weaver to propose narrower "market research" use (with David Stark, Justin, Susan, Ronan, Rachel, Chris_M, EBerkower) -- due 2013-02-27 -- CLOSED 16:38:32 http://www.w3.org/2011/tracking-protection/track/actions/370 16:38:46 ...would you be comfortable closing action 370, for narrowing audience measurement 16:39:00 ...if audience measurement is in another action item, we are okay with closing 16:39:01 action-404? 16:39:01 ACTION-404 -- Susan Israel to further Fact finding on scope of audience measurement and the DAA exception (one page of text) -- due 2013-05-29 -- OPEN 16:39:01 http://www.w3.org/2011/tracking-protection/track/actions/404 16:39:28 q+ 16:39:34 Richard: we want to make sure that we are clearlly talking about audience measurement and not market research 16:39:43 Peter: we will not close action 370 16:40:28 Nick: on action 370, we will leave action item open if you want to add proposed text 16:40:45 ...we have an issue open, we only keep an action open if someone plans to take an action 16:40:58 Richard: we just don't want to close the door 16:41:05 sounds good, will follow up offline 16:41:22 Peter: next one on list is action 407 16:41:27 action-370: don't want the issue to drop, as ESOMAR folks may be interested in a refined proposal based on what comes up 16:41:27 Notes added to ACTION-370 Propose narrower "market research" use (with David Stark, Justin, Susan, Ronan, Rachel, Chris_M, EBerkower). 16:41:28 ...text around browser education 16:41:50 Chris: Alan and I have not had a chance to work on, 16:41:56 ...requesting an extra week 16:42:10 Peter: have that action due two weeks from now 16:42:18 ...David on for action 408 16:42:30 action-407 due 06-10 16:42:30 Set ACTION-407 (with Alan Chapell) to draft text regarding browser education as discussed in Sunnyvale (Item 6 in Draft Framework, also in consensus action summary) due date to 06-10. 16:42:35 David: waiting for feedback 16:42:37 -RichardWeaver 16:42:39 action-408 due 06-10 16:42:39 Set ACTION-408 Review security/fraud text (with chris mejia and dan auerbach) due date to 06-10. 16:42:44 Peter: assign for two weeks 16:42:59 Nick: lost about other action, will do action 409 later today 16:43:04 action-409: Nick will update today 16:43:04 Notes added to ACTION-409 Circulate (with yianni, tlr, peter) regarding "graduated response" and old actions. 16:43:05 Peter: completes list of action items 16:43:20 Topic: Activity on Consensus Action items 16:43:25 ...next thing on agenda is additional items on consensus action summary 16:43:41 ...there will be a call on data retention 16:43:58 ...other issues are audience measurement 16:44:07 q? 16:44:10 q- 16:44:18 ...any other things we should be assigning on item 2 of action summary 16:44:47 ...the other issues, meaning of de-id have been discussed today, we have gone through procedural issues of pending review stable 16:45:10 http://www.w3.org/2011/tracking-protection/track/issues/31 16:45:12 issue-31? 16:45:12 ISSUE-31 -- Minimization -- to what extent will minimization be required for use of a particular exemption? (conditional exemptions) -- open 16:45:12 http://www.w3.org/2011/tracking-protection/track/issues/31 16:45:51 jmayer, I think you had a concern on minimization and how to handle it as an issue? 16:46:21 q? 16:46:25 Peter: minimization language is an open issue 16:46:32 http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#data-minimization-and-transparency 16:46:34 I think that the draft has relatively stable text on minimization and general requirements: http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance#permitted-use-requirements 16:46:38 q+ 16:46:41 ...the idea here would be a follow up seperate issue on data retention 16:47:02 Rigo: I think there are distinct issues here 16:47:24 ...Ian Fette had an issue of even being exposed to data that you didn't want before you could clean them up 16:47:35 ...he talked about an issue of short retention 16:47:47 ...we do not consider this controversal, this is issue 31 16:48:09 my only concern with that text is the last word "unlinkable" 16:48:17 ...data minimization is critical to Rob, reason to collect and retain data 16:48:43 fielding, we would certainly want to update it based on updated definitions throughout the document 16:49:02 q+ 16:49:04 Peter: Rigo do you a suggestion of how to list this 16:49:09 ack rigo 16:49:24 Rigo: would suggest to close issue 31, after hearing from Rob and Shane 16:49:32 ack rvan 16:49:51 Rob: data retention is something connected to each permitted use, might be different data retention for each permitted use 16:50:06 ...is data retention tied to any other issues? 16:50:32 issue-134? 16:50:32 ISSUE-134 -- Would we additionally permit logs that are retained for a short enough period? -- open 16:50:32 http://www.w3.org/2011/tracking-protection/track/issues/134 16:50:49 in terms of short-term retention of logs, that's consolidated into issue-134 16:50:51 Peter: follow up with Thomas about short term retention is not lost 16:50:59 ...if it is part of broader discussion then it will go into that 16:51:21 ...last item I have on the list is a question of keeping issue 188 and 191 to deal with de-identification 16:51:31 issue-188? 16:51:31 ISSUE-188 -- Definition of de-identified (or previously, unlinkable) data -- open 16:51:31 http://www.w3.org/2011/tracking-protection/track/issues/188 16:51:31 ...seperate issue for normative text and for non-normative text 16:51:33 issue-191? 16:51:33 ISSUE-191 -- Non-normative Discussion of De-Identification -- raised 16:51:33 http://www.w3.org/2011/tracking-protection/track/issues/191 16:51:34 suggestion is to note in ISSUE-31 that it is superseded by ISSUE-134 16:51:43 ...Jonathan Mayer asked to keep the issues seperate 16:52:01 Jonathan: happy to provide input 16:52:26 issue-31: might be related to issue-134 around short-term retention of logs 16:52:26 Notes added to ISSUE-31 Minimization -- to what extent will minimization be required for use of a particular exemption? (conditional exemptions). 16:52:32 Jonathan: Explained in email, issue is in defining de-id there is a substantive standard, what is the aim of de-identification 16:52:52 ...to make it hard or impossible. Then non-normative examples that are essentia to illustrating the standard 16:53:15 ...we could have no non-normative examples, or detailed non-normative examples 16:53:40 ...Dan and Shane are far apart on non-normative examples 16:53:43 q? 16:53:44 AFAI understand, normative and non-normative considerations of de-identification are different tasks and should be continued 16:54:11 hey i'm on the call now. what is the red/yellow/green ISSUE? 16:54:11 ...the non-normative is an important issue seperate from normative language 16:54:21 issue-188? 16:54:21 ISSUE-188 -- Definition of de-identified (or previously, unlinkable) data -- open 16:54:21 http://www.w3.org/2011/tracking-protection/track/issues/188 16:54:23 issue-191? 16:54:23 ISSUE-191 -- Non-normative Discussion of De-Identification -- raised 16:54:23 http://www.w3.org/2011/tracking-protection/track/issues/191 16:54:38 Peter: I hope that within our group that people that will tell these two seperate things 16:54:39 Shane, would you say your action 402 is more related to the non-normative examples? 16:54:39 i don't feel strongly about combining into one or not, so long as the substance of both issues is accounted for 16:54:45 Agree with Jonathan - we'll likely not find agreement here as Jonathan and Dan want pure technical solutions and are not willing to accept anything that relies on technical, operational, and administrative controls as a fair solution. 16:54:59 note to nick: make sure there are clear links between issues 188 and 191 16:54:59 ...make sure we have linking between two issues 16:55:14 ...we have more time, if anyone wants to bring anything up 16:55:16 Nick - to be honest I hoping to provide draft text for both on 402 (normative and non-normative) 16:55:20 ...next week Matthias will chair 16:55:26 ...in two weeks we will be back on compliance 16:55:38 ...I hope people are trying to figure out overall packages they can live with 16:55:43 dan, the red/yellow/green is the discussion between Rob and Shane on reducing identification data into pseudonymity and unlinkability 16:55:43 -Chris_Pedigo 16:55:44 -mecallahan 16:55:46 Nick - but agree with Jonathan while we'll likely agree on normative, we'll not agree on non-normative 16:55:46 -Dan_Auerbach 16:55:46 -kulick 16:55:46 -peterswire 16:55:46 ...thank you for your good work 16:55:47 -Craig_Spiezle 16:55:47 -JeffWilson 16:55:48 -paulohm 16:55:48 -Peder_Magee 16:55:49 -moneill2 16:55:49 -susanisrael? 16:55:49 -rvaneijk 16:55:50 -David_MacMillan 16:55:50 -Chris_IAB 16:55:51 -[Mozilla] 16:55:51 -Brooks 16:55:52 -hwest 16:55:52 -Rigo 16:55:52 -Amy_Colando 16:55:52 -??P70 16:55:53 -vincent 16:55:53 -Jules_Polonetsky 16:55:53 -WileyS 16:55:53 -adrianba 16:55:53 -efelten 16:55:53 -johnsimpson 16:55:53 -eberkower 16:55:54 -vinay 16:56:00 -dwainberg 16:56:01 -NAI 16:56:02 -[Microsoft] 16:56:03 -chapell 16:56:07 -schunter 16:56:08 -Walter 16:56:08 -npdoty 16:56:09 johnsimpson has left #dnt 16:56:24 -phildpearce 16:56:25 -Fielding 16:56:42 Zakim, list attendees 16:56:43 As of this point the attendees have been +1.202.587.aaaa, JeffWilson, efelten, +1.646.654.aabb, Jules_Polonetsky, eberkower, Wendy, Rigo, +52661100aacc, +1.215.286.aadd, jchester2, 16:56:46 ... npdoty, +1.202.587.aaee, +1.646.827.aaff, Yianni, susanisrael?, moneill2, phildpearce, Peder_Magee, Fielding, WileyS, Chris_IAB, rvaneijk, paulohm, vinay, hwest, 16:56:46 ... +1.202.257.aagg, robsherman, Chris_Pedigo, Craig_Spiezle, hefferjr, mecallahan, [Microsoft], jackhobaugh, marcgroman, schunter, +1.650.365.aahh, sidstamm, dwainberg, adrianba, 16:56:49 ... Amy_Colando, David_MacMillan, Brooks, RichardWeaver, +1.646.666.aaii, chapell, kulick, Walter, +1.650.465.aajj, vincent, Jonathan_Mayer, johnsimpson, Dan_Auerbach 16:56:51 rrsagent, please draft the minutes 16:56:51 I have made the request to generate http://www.w3.org/2013/05/29-dnt-minutes.html npdoty 16:57:25 -Wendy 17:01:10 -hefferjr 17:07:57 robsherman has joined #dnt 17:12:38 robsherman has joined #dnt 17:16:23 kulick has joined #dnt 17:35:00 disconnecting the lone participant, Jonathan_Mayer, in T&S_Track(dnt)12:00PM 17:35:03 T&S_Track(dnt)12:00PM has ended 17:35:03 Attendees were +1.202.587.aaaa, JeffWilson, efelten, +1.646.654.aabb, Jules_Polonetsky, eberkower, Wendy, Rigo, +52661100aacc, +1.215.286.aadd, jchester2, npdoty, +1.202.587.aaee, 17:35:03 ... +1.646.827.aaff, Yianni, susanisrael?, moneill2, phildpearce, Peder_Magee, Fielding, WileyS, Chris_IAB, rvaneijk, paulohm, vinay, hwest, +1.202.257.aagg, robsherman, 17:35:04 ... Chris_Pedigo, Craig_Spiezle, hefferjr, mecallahan, [Microsoft], jackhobaugh, marcgroman, schunter, +1.650.365.aahh, sidstamm, dwainberg, adrianba, Amy_Colando, David_MacMillan, 17:35:04 ... Brooks, RichardWeaver, +1.646.666.aaii, chapell, kulick, Walter, +1.650.465.aajj, vincent, Jonathan_Mayer, johnsimpson, Dan_Auerbach 17:38:06 robsherman has joined #dnt 18:10:50 robsherman1 has joined #dnt 18:40:03 Zakim, bye 18:40:03 Zakim has left #dnt 18:40:04 rrsagent, bye 18:40:04 I see 1 open action item saved in http://www.w3.org/2013/05/29-dnt-actions.rdf : 18:40:04 ACTION: swire to draft directly/indirectly -identified language proposal [1] 18:40:04 recorded in http://www.w3.org/2013/05/29-dnt-irc#T16-25-06