15:52:53 RRSAgent has joined #dnt 15:52:53 logging to http://www.w3.org/2012/03/28-dnt-irc 15:53:12 Zakim, this is dnt 15:53:12 aleecia, this was already T&S_Track(dnt)12:00PM 15:53:13 ok, aleecia; that matches T&S_Track(dnt)12:00PM 15:53:23 chair: aleecia 15:53:26 agenda? 15:53:43 zakim, clear agenda 15:53:43 agenda cleared 15:54:12 agenda+ Selection of scribe 15:54:33 npdoty has joined #dnt 15:54:33 agenda+ Any comments on minutes: http://www.w3.org/2012/03/21-dnt-minutes 15:54:53 tl has joined #dnt 15:54:53 agenda+ Discussion and feedback on Draft Agenda for our Face2Face 15:55:18 agenda+ Review of overdue action items: https://www.w3.org/2011/tracking-protection/track/actions/overdue 15:55:40 + +1.408.223.aaaa 15:56:03 +npdoty 15:56:08 agenda+ Discussion of a template for combined proposals on parties and business uses 15:56:21 Zakim, who is on the phone? 15:56:21 On the phone I see aleecia, +1.408.223.aaaa, npdoty 15:56:21 agenda+ Deeper discussion of issue-22. 15:56:25 +tl 15:56:44 agenda+ Responses: Header & URI 15:56:58 agenda+ ISSUES 111, 129, 130 on site-specific exceptions 15:57:09 agenda+ Announce next meeting & adjourn 15:57:13 +dsriedel 15:57:16 (sound quality is sad, Tom) 15:57:20 zakim, mute me 15:57:20 dsriedel should now be muted 15:57:43 agenda? 15:57:43 agenda? 15:58:05 aleecia: Do I sound underwater, in a windstorm, in an auditorium, or what? 15:58:31 Bil has joined #dnt 15:58:47 eberkower has joined #dnt 15:58:51 ninjamarnau has joined #dnt 15:58:53 +ninjamarnau 15:59:19 +efelten 15:59:29 jchester2 has joined #dnt 15:59:32 efelten has joined #dnt 15:59:36 +??P37 15:59:37 sidstamm has joined #dnt 15:59:50 + +1.646.654.aabb 15:59:50 johnsimpson has joined #dnt 15:59:54 + +1.215.286.aacc 16:00:03 aleecia, I can't make the call today (other teleconf at the same time), but I'll monitor this channel 16:00:09 +jchester2 16:00:14 regrets+ sidstamm 16:00:16 schunter has joined #dnt 16:00:18 thanks, Sid 16:00:24 Zakim, ??P37 is schunter 16:00:24 +schunter; got it 16:00:29 Zakim, aabb is eberkower 16:00:30 +eberkower; got it 16:00:31 that means you want to scribe, right? :-) 16:00:39 +[Apple] 16:00:43 zakim, [apple] has dsinger 16:00:46 +dsinger; got it 16:00:47 tough to scribe if I can't hear the phone line. ;-) 16:00:57 you won't make any mistakes :-) 16:01:18 Zakim, who is on the phone? 16:01:18 On the phone I see aleecia, +1.408.223.aaaa, npdoty, tl, dsriedel (muted), ninjamarnau, efelten, schunter, eberkower, +1.215.286.aacc, jchester2, [Apple] 16:01:21 [Apple] has dsinger 16:01:53 Welcome, Jason and Bil. 16:01:59 +[IPcaller] 16:02:01 +johnsimpson 16:02:11 zakim. mute me 16:02:11 +justin_ 16:02:12 Zakim, aaaa is Bil 16:02:13 +Bil; got it 16:02:22 Lia has joined #dnt 16:02:23 zakim, mute johnsimpson 16:02:23 johnsimpson should now be muted 16:02:25 Zakim, aacc is jason 16:02:25 +jason; got it 16:02:27 + +1.866.317.aadd 16:02:39 - +1.866.317.aadd 16:02:39 (period does not work, comma does. Zakim is fussy.) 16:02:41 fielding has joined #dnt 16:02:46 jmayer has joined #dnt 16:02:58 alex has joined #dnt 16:03:09 Chair: schunter 16:03:10 + +1.866.317.aaee 16:03:15 agenda? 16:03:18 Meeting: Tracking Protection Working Group teleconference 16:03:35 + +1.202.695.aaff 16:03:36 next agendum 16:03:45 + +1.813.366.aagg 16:03:47 + +1.917.934.aahh 16:03:54 + +1.202.835.aaii 16:03:56 +jmayer 16:04:09 + +1.425.214.aajj 16:04:13 thank you! 16:04:13 +alex 16:04:14 hwest has joined #dnt 16:04:19 scribenick: jmayer 16:04:23 + +1.202.346.aakk 16:04:28 close agendum 1 16:04:33 Jason has joined #dnt 16:04:37 enewland has joined #dnt 16:04:44 hefferjr has joined #dnt 16:04:49 + +1.617.733.aall 16:04:49 (if you're calling in now, please associate your name with Zakim) 16:04:53 + +1.617.733.aamm 16:04:56 close agendum 2 16:05:05 schunter: any comments on minutes? 16:05:05 zakim, who is on the phone? 16:05:10 ... silence 16:05:11 On the phone I see aleecia, Bil, npdoty, tl, dsriedel (muted), ninjamarnau, efelten, schunter, eberkower, jason, jchester2, [Apple], [IPcaller], johnsimpson (muted), justin_, 16:05:15 ... +1.866.317.aaee, +1.202.695.aaff, +1.813.366.aagg, +1.917.934.aahh, +1.202.835.aaii, jmayer, +1.425.214.aajj, alex, +1.202.346.aakk, +1.617.733.aall, +1.617.733.aamm 16:05:17 [Apple] has dsinger 16:05:34 marc has joined #dnt 16:05:36 aleecia: have been working on dc meeting agenda 16:05:49 ... still more to nail down 16:05:52 laurengelman has joined #dnt 16:06:03 npdoty, no, I am in France, and unfamiliar with the office phones 16:06:12 ... tuesday: where we are, where we're going; compliance 16:06:17 +[Microsoft] 16:06:20 ... wednesday: compliance 16:06:29 bryan has joined #dnt 16:06:30 ... thursday: preference expression 16:06:38 fielding, I'm calling from my Google account. 16:06:45 present+ Bryan_Sullivan 16:06:47 JC has joined #DNT 16:06:49 cOlsen has joined #dnt 16:06:58 Adam has joined #dnt 16:07:03 ac has joined #dnt 16:07:14 ... any comments? 16:07:16 location? 16:07:27 zakim, mut me 16:07:27 I don't understand 'mut me', tl 16:07:33 + +1.202.326.aann 16:07:34 zakim, mute me 16:07:34 tl should now be muted 16:07:42 + +1.646.666.aaoo 16:07:45 ... location soon, expect to be able to announce today 16:07:58 + +1.206.369.aapp 16:08:04 Zakim, aaff is me 16:08:04 +Lia; got it 16:08:15 zakim, mute me 16:08:16 aleecia should now be muted 16:08:23 schunter: review of overdue actions 16:08:30 close agendum 3 16:08:35 tedleung has joined #dnt 16:08:39 adrianba has joined #dnt 16:08:44 ... ACTION-26 review 16:08:45 Zakim, aakk is me 16:08:45 +hwest; got it 16:08:46 unmute me 16:09:08 zakim, unmute me 16:09:09 aleecia should no longer be muted 16:09:26 + +44.142.864.aaqq 16:09:51 +[Microsoft.a] 16:09:56 WileyS has joined #DNT 16:10:01 ksmith has joined #DNT 16:10:04 ... Taking off since Karl isn't on calls anymore. 16:10:05 chapell has joined #DNT 16:10:14 Amy is out today 16:10:22 zakim, [Microsoft.a] is me 16:10:22 +adrianba; got it 16:10:40 + +015654aarr 16:10:50 Zakim, aarr is fieding 16:10:50 +fieding; got it 16:10:51 ... ACTION-104 16:10:52 + +1.646.395.aass 16:11:03 aleecia: amy's thinking is no text 16:11:22 schunter: ACTION-120 16:11:47 alex: need more time 16:12:00 Vinay has joined #dnt 16:12:26 thanks, Jeff 16:12:44 ifette has joined #dnt 16:12:45 action-120 due April 4 16:12:45 ACTION-120 Write a proposal on web-wide exception API (for ISSUE-113) (with npdoty) due date now April 4 16:12:48 Zakim, bridge? 16:12:48 I don't understand your question, ifette. 16:12:54 Zakim, code? 16:12:54 the conference code is 87225 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), npdoty 16:12:54 schunter: recommend getting done before f2f, start with an outline 16:12:58 alex, great! 16:13:07 ... ACTION-123? 16:13:12 I have been out for a couple of weeks. Has the dial in # changed? I keep getting a 'disconnected' error 16:13:14 jchester2: working, will report back 16:13:24 unmute me 16:13:30 Zakim, unmute tl 16:13:30 tl should no longer be muted 16:13:34 Adam_ has joined #dnt 16:13:58 Zakim, aass is WileyS 16:13:58 +WileyS; got it 16:14:13 schunter: ACTION-139? 16:14:28 + +1.404.978.aatt 16:14:38 tl: working on ACTION-139, ACTION-145 16:14:47 mischat has joined #dnt 16:14:54 + +385221aauu 16:15:03 schunter: ACTION-141? 16:15:03 +Cyril_Concolato 16:15:09 - +1.404.978.aatt 16:15:14 Jeff, again due wednesday for 123? 16:15:16 ... no rigo, will reach out 16:15:17 Apologies for audio zakim, mute me 16:15:17 Jeff, action-123 is now a week out 16:15:19 zakim, mute me 16:15:19 aleecia should now be muted 16:15:22 kevin, no change on the call in number. 16:15:22 vincent has joined #dnt 16:15:23 Nick may be able to help Kevin? 16:15:32 schunter: ACTION-145? 16:15:32 + +1.404.978.aavv 16:15:37 Zakim, aavv is ifette 16:15:37 +ifette; got it 16:16:01 zakim, unmute me 16:16:01 aleecia should no longer be muted 16:16:15 +[Microsoft.a] 16:16:30 amyc has joined #DNT 16:16:37 :-) 16:16:40 zakim, mute me 16:16:40 tl should now be muted 16:16:51 schunter: ACTION-150? 16:17:04 -ifette 16:17:13 Note that 2 weeks is during f2f 16:17:23 You could do 1 week, or 3, and I'd believe it 16:17:26 Ninja - agree that this should be handled in the companion document 16:17:27 ninjamarnau: need more time to work with shane 16:17:41 Ninja, can we try to do this in 1 week so we can discuss text at f2f? 16:18:01 schunter: done with review of action items 16:18:09 +ifette 16:18:26 ndoty, yes. thank you. I forgot that the f2f is this soon. 16:18:48 Netlag is the new jetlag, for all the cool kids. 16:18:52 rrsagent, bookmark? 16:18:52 See http://www.w3.org/2012/03/28-dnt-irc#T16-18-52 16:18:53 schunter: handing to aleecia to work on compliance 16:19:02 rrsagent, make logs member 16:19:03 Voice quality is also poor for me (incoming) 16:19:10 aleecia: sent template for cross-issue proposals to list 16:19:30 ... idea is combination of proposals around parties and operational use 16:19:51 http://lists.w3.org/Archives/Public/public-tracking/2012Mar/0434.html 16:19:58 ... questions? things to add? 16:20:24 ... first part: parties 16:20:36 ... ok to copy and paste from other proposals 16:21:08 ... issues: how large is a party? what is a first party? 16:21:19 ... what a first party must/must not do, what a third party must/must not do 16:22:15 ... comments? 16:22:56 ... unless anyone says otherwise, to be clear, the section on third parties only applies to third parties 16:23:29 +q 16:23:47 ... reviewing points of decision 16:23:50 ack jmayer 16:23:50 q? 16:24:06 why is B only referring to retention limitations? 16:24:08 jmayer: thinking about this set of design decisions, I very much like the approach 16:24:18 +q 16:24:18 aleecia has joined #dnt 16:24:32 ... not quite a "business use" 16:24:55 ... talk about an exception for data that can't be linked to a user's browsing 16:25:00 ... a lot of support for that 16:25:35 ... not a list of blanket/narrow exceptions, but purposes you couldn't accomplish with unlinkable data 16:25:59 Makes sense to me 16:26:00 +1 16:26:10 ... for financial logging, for example, which people are talking about as being very useful, would also want to see why it can't be accomplished with unlinkable data 16:26:52 can we get definition of unlinkable with examples? 16:26:56 aleecia: looking at A through C, could add another category for "allowed but only if unlinkable", or add an 8th exception 16:27:00 WileyS has joined #DNT 16:27:02 +q 16:27:41 jmayer: a cross-cutting exception because it doesn't raise serious privacy concerns (whatever purpose is fine) 16:27:44 can we define unlinkable? 16:27:49 Can you define unlinkable 16:28:00 funny! 16:28:16 i hope that is not the def... 16:28:20 ... and second noting it as a design choice for each point on the list 16:28:30 q? 16:28:35 q+ 16:28:38 unlinkability could be a sufficient option. But I do not agree that ANY purpose would be fine. Purpose limitation is still necessary imo. 16:28:53 - +1.866.317.aaee 16:29:00 ack jchester 16:29:11 zakim, unmute me 16:29:11 johnsimpson should no longer be muted 16:29:33 aleecia has joined #dnt 16:29:37 q? 16:29:41 q+ 16:29:45 q+ 16:30:00 jchester2: What are the impacts for legal compliance? 16:30:09 the term unlinkable does not yet exist in the TCS. "unidentifiable" is used but not defined. 16:30:22 sidstamm has joined #dnt 16:30:29 -WileyS 16:30:30 q+ 16:30:38 bryan, then let's define it - see FTC report, DAA multi-site principles 16:31:33 jchester2, are there particular problems you see that you think will trip us up for EU jurisdictions? 16:31:36 jchester2: Need clarity on what EU law requires. 16:31:43 is there some text you could propose and reference? 16:32:44 + +1.646.395.aaww 16:33:07 aleecia: have asked several times and haven't had pushback from EU that 1st/3rd won't work at all, just perhaps that there would be additional requirements 16:33:15 jchester2, I don't think that our 1st and 3rd party approach is generally not acceptable. But it sure is a problem that our 3rd parties are controllers as well as processors. 16:33:21 q? 16:33:24 ack tl 16:33:38 huzzah IRC back 16:34:21 scribenick: tl 16:34:27 scribenick: npdoty 16:34:29 if we mean by "unlinkable data" data that can't be associated with a person, it's not an exception, it's not even in scope, surely? 16:34:55 dsinger, why wouldn't it be in scope? 16:34:55 tl: I like the idea, having a first exception be unlinkable data can really improve the clarity of the document 16:35:13 Ninja: Thanks. We need EU clarification on so-called first parties. 16:35:14 bryan: we would need to define unidentified and unlinkability 16:35:28 because if it's data that's not associated with a person, it's no longer 'tracking' anyone 16:35:36 ... jmayer pointed to FTC and DAA documents, but we need to be sure we have an understanding and a definition 16:35:53 ifette: Art29 v FTC and these definitions 16:36:09 +1 16:36:27 ... get something out the door that offers users meaningful choice, if that satisfies regulatory requirements then great, but our primary goal shouldn't be satisfying such a regime 16:36:30 +1 16:36:34 +1 16:36:37 +1 to: we're building a tool for users. If that satisfies some regulatory regime, great. 16:36:42 The meaningful benefit should be an effective DNT regime 16:36:49 let's be mutually informed, but not wedded! 16:36:51 aleecia: agree, regulatory requirements are useful to have in mind, but not determinant of our work 16:37:23 ... implications of different regulatory regimes are large and so we should talk about them, but we may choose to go our own way 16:37:28 +q 16:37:35 q- bryan 16:37:38 q- ifette 16:37:40 ack dsinger 16:38:01 dsinger: in Brussels we had a discussion of alternative models to 1st/3rd 16:38:18 ... we don't seem to have explored these further since, when should we do that? 16:38:40 aleecia: this is a great time to write up those alternative proposals (in this form) if interested 16:38:58 ... in Brussels moved to walk down the 1st/3rd path unless/until it fails 16:39:16 aleecia has joined #dnt 16:39:26 ok. thx 16:39:29 ... if you want to write an alternate proposal, go right ahead 16:39:32 ack fielding 16:39:42 q? 16:40:01 fielding: 3rd-acting-as-1st important to me in the template itself, hard for me to evaluate otherwise 16:40:20 +q 16:40:28 aleecia: case to bundle one more piece, though I've been trying to keep this as simple as possible 16:40:31 ack jmayer 16:40:39 ack jmayer 16:40:51 jmayer, because I won't agree to third party restrictions on outsourced services 16:41:25 jmayer: three options for each business use, could add "allowed under the unlinkable exception" 16:41:41 +1 16:41:50 q+ 16:41:53 ... but rather than just a retention limit, there might be other limits -- part of a broader design space 16:42:33 ... not so rigid that retention limits are the only limits on an exception 16:42:42 q+ 16:43:07 aleecia: can use Part C of the template for that, restrictions may vary across each business use 16:44:14 jmayer: buckets of 1) never do it, 2) do it without limits, 3) unlinkable only, 4) customized set of limits 16:44:16 Maybe we should just see a proposal and what people write they write... 16:44:35 here's what I think I'm changing to the template: (1) "unlinkable" to the list of 7 uses; (1) "unlinkable" as a method similar to retention; adding agent of a first party 16:44:35 and adding a note that proposals that are not 1st/3rd party are also fine 16:45:03 my pragmatic concern is that it'll be difficult to compare proposals 16:45:07 q- 16:45:10 they'll be text-heavy 16:45:13 WileyS has joined #DNT 16:45:26 q? 16:45:32 ack amyc 16:46:03 amyc: want to support what jmayer said, don't want to get too rigid about A/B/C, may include A/B/C just to make it easier to compare 16:47:29 scribenick: jmayer 16:47:42 aleecia: circling back to unlinkable data 16:47:58 did jmayer volunteer? 16:48:01 q+ 16:48:12 ack dsinger 16:48:14 I think jmayer volunteered? 16:48:40 +q 16:49:05 zakim, unmute me 16:49:05 tl was not muted, tl 16:49:07 action: mayer to draft a permitted use/definition for unlinkable data 16:49:07 Created ACTION-153 - Draft a permitted use/definition for unlinkable data [on Jonathan Mayer - due 2012-04-04]. 16:49:08 WileyS has joined #DNT 16:49:14 ok 16:49:20 unlinkable is the same as unidentifiable 16:49:26 not 16:49:27 I would ask that the definition address these questions: Does "link" mean an association with a specific individual or device (whether the identity of that individual/device is real or not), or a limited group of individuals or devices, or a class of individuals or devices, etc? How far away from an real individual or device is the ability to "link" significant? 16:49:30 dsinger: Is unlinkable data in scope? 16:49:31 q+ 16:49:46 unlinkable is the NOT same as unidentifiable 16:50:06 ack tl 16:50:12 How is unlinkable is the NOT same as unidentifiable? 16:50:15 aleecia: We've been discussing the boundaries of unlinkable data, will work on text. 16:50:21 Breaking up badly 16:50:24 tl, breaking up badly 16:50:30 tom, more bandwidth! 16:50:39 ack bryan 16:51:05 As we said in Santa Clara: you can have data about people, but which cannot be linked to a particular person. This is hard. 16:51:06 bryan: need precision in the definition 16:51:15 zakim, mute me. 16:51:15 tl should now be muted 16:51:21 pages 20-22 of the FTC report discusses de-identified data 16:51:27 ... question: how unlinkable? 16:51:31 q? 16:51:39 zakim, increase my audio quality 16:51:39 I don't understand 'increase my audio quality', tl 16:51:39 q+ 16:51:54 ack ninjamarnau 16:51:56 zakim, please add more fuel to the internet furnaces 16:51:56 I don't understand you, tl 16:51:57 action: draft an unlinkable data/unidentifiable data/pick favorite term exception 16:51:57 Sorry, couldn't find user - draft 16:52:07 action: jmayer to draft an unlinkable data/unidentifiable data/pick favorite term exception 16:52:07 Created ACTION-154 - Draft an unlinkable data/unidentifiable data/pick favorite term exception [on Jonathan Mayer - due 2012-04-04]. 16:52:12 action-153? 16:52:12 ACTION-153 -- Jonathan Mayer to draft a permitted use/definition for unlinkable data -- due 2012-04-04 -- OPEN 16:52:12 http://www.w3.org/2011/tracking-protection/track/actions/153 16:52:37 +1 16:52:51 q? 16:53:03 is "ease of linking" really a factor in linkability? 16:53:07 ninjamarnau: some possible different meaning in eu 16:53:21 what about the ftc text? 16:53:36 aleecia: another thing to think about - aggregation at the time of collection 16:53:37 +q 16:53:47 if I can break SSL I can probably correlate data... is a prohibition against linkability really achievable ? 16:53:53 +q 16:53:54 ninja: is there a size related with the buckets you mentioned? 16:54:09 -q 16:54:09 Depends on the data being collected -- e.g. cookies may be set to "optout" but IP addresses still sent, etc 16:54:43 aleecia: will work on revisions to template 16:54:53 volunteers to write proposals? 16:54:59 -ifette 16:55:04 vincent has joined #dnt 16:55:28 I hope to write up "issues with 1st/3rd that are different or gone with x-site" 16:55:35 i plan to something 16:55:47 - +1.202.326.aann 16:55:47 sure, i'll paste together what i've already written 16:55:48 Yes 16:56:16 thanks to volunteers! 16:56:32 should be different views :) 16:56:55 Bryan, according to the FTC the ease of linking is a factor - based on whether data can be "reasonably" linked 16:57:18 aleecia: not defining compromise by who gives up what, instead looking for something that everyone can live with 16:57:52 ... would like to see some details on use cases 16:58:30 ... example: research and surveys split apart 16:58:56 q? 16:59:08 ... comments? 16:59:20 schunter: moving to tpe 16:59:27 topic: Tracking Preference Expression doc 16:59:58 tl, are you able to talk? 16:59:58 zakim, unmute me 16:59:58 tl should no longer be muted 17:00:08 yes, clearly 17:00:14 yes 17:00:42 tl: a problem when working on response header and uri 17:01:01 ... first problem: opt-in status 17:01:31 huh? 17:01:41 ... response header will handle per-request, static status resource can't 17:02:35 I assumed that agents would continue to send cookies on fetching the tracking status resource 17:02:40 fielding: don't think there's a problem 17:02:49 ... browsers will still send cookies 17:02:58 tl: ok, resolved 17:03:03 my concern is that not every technique will use cookies for identification 17:03:12 ... second problem is related, solved 17:03:38 sidstamm has left #dnt 17:04:35 valid for *at least* 24 hours, in many cases the caching would be much longer, right? 17:04:41 tl: must have a status resource, could be static or dynamically generated, expect it to be an upper bound on tracking, valid for at least 24 17:05:42 aleecia has joined #dnt 17:06:10 q? 17:06:13 designer, we already do 17:06:16 tl: if parameter changes, have to reload the resource 17:06:34 -dsriedel 17:06:40 q+ 17:06:49 s/designer/dsinger/ 17:06:50 tl: anything we're missing? 17:07:02 -Bil 17:07:12 npdoty: what about trackers that don't use cookies? 17:07:25 +q 17:07:30 ack npdoty 17:07:35 -hwest 17:08:06 tl: for fingerprinting, could use ip + ua, more would be difficult 17:08:25 In mobile 17:08:39 - +1.617.733.aall 17:08:48 +q 17:09:07 WileyS, do you have specific details on the mobile context? 17:09:21 easy fix - allow loading html/js/etc. as part of the status resource 17:09:54 jmayer, that's certainly one way, though it seems dramatic 17:10:03 schunter: is there agreement on approach? 17:10:10 tl: working on text 17:10:21 npdoty, background pages are nbd 17:11:00 schunter: any objections to the hybrid approach? comments? expect more in future 17:11:10 topic: site-specific exceptions 17:11:21 +q opt-*out* requests 17:11:30 -q opt-*out* requests 17:11:32 +q 17:11:37 -q 17:12:02 ... question: should a site be able to get an exception for all the third parties it chooses to use? 17:12:03 +q 17:12:09 q+ tl to talk about something he wanted to remember 17:12:22 add the point you want to make after "q+ " 17:12:40 ... another question: should widget providers (and similar) be able to get a web-wide exception for all the first parties it appears on? 17:12:41 Zakim will remind you 17:13:01 Aah, apparently, it doesn't work with +q, only q+ 17:13:07 zakim, mute me 17:13:07 tl should now be muted 17:13:09 +q 17:13:11 q? 17:13:17 ... yet another question: should a site be able to get an exception for specific third parties? 17:13:18 q+ 17:13:51 q+ to note that the current proposal handles both * and an enumerated list 17:14:36 ... want to give publishers flexibility and practical accommodation, but also want to make sure users are informed 17:14:37 ack tl 17:14:38 tl, you wanted to talk about something he wanted to remember 17:15:21 -[Microsoft.a] 17:15:37 current API doesn't support the Web-wide exception case, we're still waiting on alex to draft text here 17:15:41 Can the IAB, DAA, NAI etc on the call explain their view regarding this issue, on web wide exceptions. 17:16:13 losing you 17:16:17 Jeff - I can explain the "MyBlogLog" scenario again if you like 17:16:19 q? 17:16:25 +q 17:16:35 As one example... 17:16:39 ack jmayer 17:16:41 ack jmayer 17:17:13 We want a mirror image API too. Right now, you can only ask about opting *in* to getting DNT:0, not opting *out* to getting DNT:1 17:17:19 q+ 17:17:36 zakim, mute me 17:17:36 tl should now be muted 17:17:38 jmayer: take the approach of handling all 3, don't need to answer whether the * exception satisfies EU law, sites that handle EU users can make that determination on their own 17:17:52 ack jchester 17:17:54 ack jchester 17:18:24 q+ 17:18:58 q+ 17:19:11 jchester2: would like to hear where industry trade groups are 17:19:38 ... concerned about users accepting a list of companies they don't know 17:19:54 ... want to make sure there's meaningful information available about what's going on 17:19:56 jchester2, are you arguing that we shouldn't allow a "*" exception at all, because users wouldn't be informed? 17:20:08 it seems to me these aren't mutually exclusive 17:20:09 q? 17:20:14 marc, want to respond directly? 17:20:17 a "*" exception allowed, with a transparency requirement 17:20:19 q? 17:20:22 Yes 17:21:43 What is the DAA doing now on its own DNT system, including this issue? 17:22:08 marc: We shouldn't draft with an eye towards any particular legal regime or specific browser implementation. Would allow all three options to exist. 17:22:27 Neither the NAI or DAA offers the kind of real transparency a consumer requires. 17:22:27 @Jeff, you prob want to ask the DAA directly - as I don't believe they are on the call 17:22:42 Marc as head of NAI is on the DAA. 17:23:03 schunter: What sort of transparency is available about the companies on a page? 17:23:14 aleecia has joined #dnt 17:23:39 Marc: Icon gives some information, some interstitial pages (not currently required) give a list of companies involved in displaying an ad. 17:24:20 While it's interesting to learn what DAA is thinking about, once again, we may go off in an entirely different direction from what any external party might prefer 17:24:21 @Jeff - I understand that it is your opinion that neither the DAA or NAI "offers the kind of real transparency a consumer requires" 17:24:24 When you look at Aboutads, the information provided there doesn't reflect how the companies really collect data, who their partners are, etc. 17:24:46 ... At opt-out page, get list of companies. Most users choose to opt out of all companies. 17:24:46 We might want to take this offline soon? 17:24:51 yes. 17:24:56 Comsumers don't have the granularity they require--so any exception must convey what really goes on. 17:25:15 q? 17:25:30 Look at this and tell me how this helps users and their privacy: http://www.networkadvertising.org/managing/ 17:25:39 My understanding: Marc says that DAA does not offer per-thirdparty transparency or control but rather categories/groups of entitites. 17:25:48 ack ninjamarnau 17:25:50 q- marc 17:25:51 ack nmarnau 17:26:32 Q? 17:26:33 We are at loggerheads on this point I believe - Jeff is unlikely to think that the disclosure that the industry comes up with will be sufficient -- industry will think that jeff's standard is over reaching. We may want to take this offline 17:27:05 q? 17:27:14 +1 to what Alan said! 17:27:15 -q 17:27:16 I think Ninja's points here are helpful, once we understand where things stand. 17:27:17 ninjamarnau: We want first parties to carefully select their third parties. Especially given considerations of liability. 17:27:24 ack npdoty 17:27:24 npdoty, you wanted to note that the current proposal handles both * and an enumerated list 17:27:39 And thanks for Marc jumping in to help us understand 17:27:41 npdoty: Current proposal handles "*" and list. 17:27:51 ack ksith 17:27:55 ack ksmith 17:27:56 ack ksmith 17:28:03 I also appreciate Marc speaking out--although we don't agree! 17:28:15 an array of domain strings OR a "*" 17:28:20 revised template -> dlist; please let me know if I've missed or mangled anything 17:28:32 zakim, unmute me 17:28:32 tl should no longer be muted 17:28:38 ksmith: Want "pretty name" option in exception API. 17:28:57 tl: Already included. 17:29:07 q+ 17:29:49 imho users are more liklely to have a blacklist of exceptions not to grant 17:29:50 q? 17:30:00 zakim, mute me 17:30:00 tl should now be muted 17:30:07 is willing to explore in email (which I sort-of tried and failed) his concerns with the JS API in general, as time is running out, and why I wonder whether both sites and UAs will both prefer what we call "out of band" over this in-band JS API and dnt:0 17:30:22 schunter: We'll make an action. 17:30:42 ksmith: Agree that lack of transparency is a problem with a blanket exception. 17:30:53 I think currently the pretty name parameter is just a single param for the first-party site, it would be a new option if we want to do it for every 3rd-party domain (which I could see being useful or not) 17:31:05 ... existing ad chains are problematic for exceptions 17:31:05 Or the ad exchange like business model needs to be changed to better protect privacy. 17:31:08 I continue to think Kevin is completely wrong on this. See the list. 17:31:22 q- 17:31:36 -justin_ 17:31:43 q? 17:31:49 - +1.917.934.aahh 17:32:04 - +1.202.835.aaii 17:32:07 - +1.646.395.aaww 17:32:12 where is the F2F? 17:32:20 dsinger, yes, please note on email; I am still very optimistic about user-agent managed exceptions 17:32:23 schunter: Next week - last before f2f. 17:32:26 -efelten 17:32:27 - +1.813.366.aagg 17:32:27 -adrianba 17:32:29 -[IPcaller] 17:32:29 -jchester2 17:32:30 -johnsimpson 17:32:30 - +44.142.864.aaqq 17:32:31 -aleecia 17:32:34 -eberkower 17:32:34 johnsimpson has left #dnt 17:32:35 -[Apple] 17:32:37 -[Microsoft] 17:32:39 -ninjamarnau 17:32:40 npdoty: huh? 17:32:41 - +1.206.369.aapp 17:32:44 -schunter 17:32:45 -Lia 17:32:47 - +1.425.214.aajj 17:32:49 -jmayer 17:32:51 -npdoty 17:32:54 -alex 17:32:56 -fieding 17:32:57 -Cyril_Concolato 17:33:00 -tl 17:33:02 - +1.646.666.aaoo 17:33:03 -jason 17:33:17 s/fieding/fielding/ 17:33:27 - +1.617.733.aamm 17:33:29 - +385221aauu 17:33:30 T&S_Track(dnt)12:00PM has ended 17:33:30 Attendees were aleecia, +1.408.223.aaaa, npdoty, tl, dsriedel, ninjamarnau, efelten, +1.646.654.aabb, +1.215.286.aacc, jchester2, schunter, eberkower, dsinger, [IPcaller], 17:33:30 ... johnsimpson, justin_, Bil, jason, +1.866.317.aadd, +1.866.317.aaee, +1.202.695.aaff, +1.813.366.aagg, +1.917.934.aahh, +1.202.835.aaii, jmayer, +1.425.214.aajj, alex, 17:33:32 ... +1.202.346.aakk, +1.617.733.aall, +1.617.733.aamm, [Microsoft], +1.202.326.aann, +1.646.666.aaoo, +1.206.369.aapp, Lia, hwest, +44.142.864.aaqq, adrianba, +015654aarr, fieding, 17:33:34 ... +1.646.395.aass, WileyS, +1.404.978.aatt, +385221aauu, Cyril_Concolato, +1.404.978.aavv, ifette, +1.646.395.aaww 17:33:36 ksmith has left #DNT 17:37:31 tedleung has left #dnt 17:41:57 aleecia has joined #dnt 18:19:40 dsinger has joined #dnt 18:35:30 tlr has joined #dnt 18:57:16 rrsagent, make logs public 18:57:19 rrsagent, draft minutes 18:57:19 I have made the request to generate http://www.w3.org/2012/03/28-dnt-minutes.html npdoty 19:03:43 schunter1 has joined #dnt 19:11:36 schunter has joined #dnt 19:16:20 schunter has joined #dnt 19:18:33 schunter1 has joined #dnt 20:28:03 schunter has joined #dnt