16:51:27 RRSAgent has joined #dnt 16:51:27 logging to http://www.w3.org/2015/01/28-dnt-irc 16:51:29 RRSAgent, make logs world 16:51:29 Zakim has joined #dnt 16:51:31 Zakim, this will be TRACK 16:51:31 ok, trackbot; I see T&S_Track(dnt)12:00PM scheduled to start in 9 minutes 16:51:32 Meeting: Tracking Protection Working Group Teleconference 16:51:32 Date: 28 January 2015 16:56:42 T&S_Track(dnt)12:00PM has now started 16:56:49 +npdoty 16:58:19 schunter has joined #dnt 16:59:15 moneill2 has joined #dnt 17:00:29 +[FTC] 17:00:37 WileyS has joined #dnt 17:00:43 +Carl_Cargill 17:01:21 fielding has joined #dnt 17:01:22 +[IPcaller] 17:01:31 chair: schunter 17:01:32 Carl_Cargill has joined #DNT 17:01:33 +rvaneijk 17:01:41 zakim, [IPCaller] is me 17:01:41 +moneill2; got it 17:01:41 regrets+ dsinger, justin 17:01:45 +Fielding 17:01:46 rvaneijk has joined #dnt 17:02:04 +WileyS 17:02:26 dwainberg has joined #dnt 17:03:14 +dwainberg 17:03:26 agenda for January 28: https://lists.w3.org/Archives/Public/public-tracking/2015Jan/0004.html 17:03:27 +??P60 17:03:32 +hefferjr 17:03:33 Zakim, ??P60 is schunter 17:03:33 +schunter; got it 17:03:38 I hear no one on the call - is it working? 17:03:53 I hear typing now - I guess we're good 17:04:08 Thank you Nick 17:04:13 TPE changes since LCWD are diffed at http://www.w3.org/2011/tracking-protection/drafts/diffs/TPE-LCWD-to-20141217.html 17:04:33 Compliance changes since WD are diffed at http://services.w3.org/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FTR%2F2014%2FWD-tracking-compliance-20141125%2F&doc2=http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html 17:04:43 scribenick: npdoty 17:04:52 +Chris_Pedigo 17:04:56 schunter: welcome back. agenda for today, looking at TPE review and then Compliance 17:05:01 … any comments for the agenda? 17:06:06 Topic: TPE changes 17:06:13 schunter: ask fielding to walk us through the changes 17:06:27 … goal is moving to next step, Candidate Recommendation 17:06:44 … give the group two weeks to review, if the changes are okay, then would like to move this to Candidate Recommendation 17:06:46 http://www.w3.org/2011/tracking-protection/drafts/diffs/TPE-LCWD-to-20141217.html 17:07:41 fielding: this is a diff of changes from the Last Call draft 17:07:50 … slight change in wording about the HTTP specs 17:09:14 … line 433, in response to a comment, removed the %31 notation, everyone understands “1” and “0” 17:09:41 +Amy_Colando 17:09:59 … line 459, moved javascript property back to navigator 17:10:11 … based on discussion with browser folks 17:10:46 … “nullable” property, just clarifies 17:11:02 … added a note about possible extension text 17:11:20 … value for “G” was added, and a new section for a Gateway response 17:11:42 q? 17:11:43 … (section hasn’t changed since last list discussion of that topic) 17:11:50 I haven't 17:12:02 … wileys, did you review that section? 17:12:05 But I don't believe my issues were significant enough to hold up the process 17:12:14 section 6.2.4 of http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html 17:12:59 fielding: 6.3.1, just a little more text to describe “G” as a potential answer 17:13:24 … 6.3.2 changed MAY to can because not interoperability requirement 17:13:53 … note about status-id resolution, which is a response to a Last Call comment 17:14:00 +WaltMichel 17:14:08 Walt_Michel has joined #DNT 17:14:36 … do we need a wider character set to allow in the well-known URL request? 17:14:43 … don’t currently see any reason to do so 17:15:40 … fixes in the references 17:16:31 … in exceptions API section, changes to improve the definitions of origin, based on conversations with browser folks 17:16:37 … definitions are much shorter, an improvement 17:16:48 kulick has joined #dnt 17:16:55 +kulick 17:17:23 schunter: makes it easier to re-use algorithms. now points to existing references, RFCs and Recommendations 17:17:41 fielding: +1. just a terminology change, but makes it easier for implementers 17:18:34 … clarified later in that section that lack of exception might not imply DNT:1 (for example, if user generally sends nothing) 17:18:44 +WSeltzer 17:19:11 … in the StoreExceptionPropertyBag, added “expires” and “maxAge” parameters 17:19:15 -Amy_Colando 17:19:47 fielding: make it the same as what cookies are able to describe 17:20:32 … per moneill 17:20:36 … may have further comments on that 17:20:41 … (do we need both?) 17:21:20 … description of those parameters 17:21:35 … using referenced terminology, rfc6265 17:22:12 … in 7.6, changed to refer to DNT preference rather than header field (since it might be expressed through the DOM as well) 17:23:12 … suggestion about the use of a “t” qualifier for transferred consent 17:23:55 … addition from dsinger that claims are being made by the site and not the user agent 17:24:36 … “Nonetheless, at the time of the call” 17:25:00 … explanation of why the API doesn’t need a return value / asynchronous response 17:25:31 … additional references, others just moved around 17:25:37 schunter: any comments or questions? 17:25:40 q? 17:25:52 q+ 17:26:15 schunter: set a two-week deadline for comments 17:26:22 ack np 17:26:48 ChrisPedigoDCN has joined #dnt 17:26:56 npdoty: About the Gateway response, do we have any feedback from implementers or commenters? 17:27:09 q? 17:27:22 I will in the next week 17:28:08 npdoty: process points before transition to CR 17:28:14 ... we need to respond to all LC comments 17:28:37 ... and bring info to the Director, including potential responses from commenters 17:28:45 Other things remaining for me: 1) mark DNT-extensions as at-risk; 2) look into changing the ABNF of representation to a more JSONish description (editorial) 17:28:53 ... Group needs to decide it wants to move forward. 17:29:17 ... So: we decide we want to move forward, present to director 17:29:51 fielding: Editorial marking for "at-risk" features? 17:29:57 ... For the DNT extension mechanism 17:30:04 npdoty: I'll look into that 17:30:26 schunter: In 2 weeks, we'll freeze the document. 17:30:52 ... then go into CR transition 17:30:56 Are there any companies that have signed-up for candidate review? 17:31:03 What happens if no one signs up? 17:31:31 Actually implement DNT on the server side 17:32:10 And if no one implements? 17:32:31 npdoty: CR is a Call for Implementations, but you don’t have to commit to ahead of time 17:32:41 fielding: if nobody implements it, it won’t go to a full Rec 17:32:57 Thank you 17:32:59 +1, need implementations to progress further 17:33:08 Topic: Compliance 17:33:31 scribenickk: wseltzer 17:33:45 scribenick: wseltzer 17:33:49 http://services.w3.org/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FTR%2F2014%2FWD-tracking-compliance-20141125%2F&doc2=http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html 17:34:22 npdoty: Diff between current ED and what we published in November as WD 17:35:02 ... 1st significant change, sec 1 "Scope" 17:35:26 ... Change proposals and comments addressed 17:35:36 ... Issue-209 17:36:11 ... Definitions: clarifying that party status is just with respect to a given user action 17:36:40 ... Server compliance: changes in indicating compliance/non-compliance 17:37:12 ... Added paragraph on DNT:0 (moved) 17:37:46 ... 1st party compliance, one-word change to fix an ambiguity I had introduced 17:38:15 ... 3.3.1.3 ... use defined term "tracking data" 17:38:53 ... 3,3,2,1 remove line so as not to duplicate requirement from general permitted uses 17:39:11 pmagee has joined #dnt 17:39:26 ... UGE, improve handling 17:39:57 https://lists.w3.org/Archives/Public/public-tracking/2014Dec/0028.html 17:39:57 ... That was the full set of editorial corrections. 17:40:02 -moneill2 17:40:03 ... Still a few comments in email 17:40:39 Perhaps we could change: 17:40:40 > A party MUST provide public transparency of the time periods for which data collected for permitted uses are retained. 17:40:41 to: 17:40:42 > A party MUST publicly describe definite time periods for which data collected for permitted uses are retained. 17:41:26 https://lists.w3.org/Archives/Public/public-tracking/2015Jan/0001.html 17:42:34 ... don't think there's more to do on non-normative text 17:42:43 ... welcome group's review 17:43:01 +??P15 17:43:42 q? 17:43:45 q+ 17:43:59 q? 17:44:13 ack fie 17:44:15 schunter: not yet to 2-week deadline 17:44:30 fielding: there was an issue on server log files 17:44:47 ... not sure if current text is sufficient to cover temporary log-file use 17:45:11 http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#server-compliance 17:45:15 npdoty: server compliance section 17:45:52 fielding: does the text there cover, or are we waiting for more text? 17:45:58 npdoty: I'm not anticipating more text 17:46:33 fielding: I think it covers sufficientl 17:46:41 ... chairs can do a call to close issue-134 17:46:45 +1 17:46:58 schunter: other comments? 17:47:24 fielding: the text in the document hasn't gotten any comments in a while 17:47:30 issue-134? 17:47:30 issue-134 -- Would we additionally permit logs that are retained for a short enough period? -- open 17:47:30 http://www.w3.org/2011/tracking-protection/track/issues/134 17:47:44 ... so I'd suggest chairs call to close issue-134. 17:48:37 npdoty: still waiting for cfo response on isseu 235, 219 17:48:54 ... several issues we've resolved or editorial, need to revirew with group 17:49:28 http://www.w3.org/wiki/Privacy/TPWG#Change_proposals 17:49:54 http://www.w3.org/2011/tracking-protection/track/products/5 17:49:57 fielding: is this compliance current or compliance next? 17:50:01 npdoty: Current 17:50:12 if the Tracker is out of date, that’s something we should ask Justin about 17:50:24 schunter: we made some progress on CFOs 17:50:34 issue-235? 17:50:34 issue-235 -- Auditability requirement in Reasonable Security section -- raised 17:50:34 http://www.w3.org/2011/tracking-protection/track/issues/235 17:50:49 schunter: we determined consensus to remove auditability language 17:51:03 issue-219? 17:51:03 issue-219 -- Limitations on use in a 3rd party context of data collected in a 1st party context -- raised 17:51:03 http://www.w3.org/2011/tracking-protection/track/issues/219 17:51:41 schunter: whether parties can collect info as first parties and use in third-party context? We determined consensus not to permit 3d pty use of 1st pty data 17:51:50 ... One important point, there can be UGE 17:52:01 or prior consent 17:52:20 ... that was closer to user expectations 17:53:03 yeah, we use “UGE” when we could more precisely refer to “user-granted exceptions, in band or out of band, or other prior consent” 17:53:11 I can make those changes to the draft this week 17:53:15 q? 17:53:55 schunter: interesting, on 219, Roy had objections to both cases, but there was no third option 17:53:57 and then have fewer issue blocks 17:54:41 q? 17:54:44 I reserve the right to object to sound proposals as well ;-) 17:54:55 schunter: AOB? 17:55:26 -WaltMichel 17:55:28 q+ 17:55:34 ack n 17:56:13 npdoty: take a couple weeks to review issue resolution, couple weeks to review document overall 17:56:20 ... hope that's all we have left before LC 17:56:50 q? 17:57:03 -WileyS 17:57:05 -kulick 17:57:05 -Chris_Pedigo 17:57:06 -Carl_Cargill 17:57:06 -??P15 17:57:07 -hefferjr 17:57:07 [adjourned, meet again next week] 17:57:07 -[FTC] 17:57:09 -npdoty 17:57:09 -schunter 17:57:11 -dwainberg 17:57:18 -WSeltzer 17:57:19 -rvaneijk 17:57:24 -Fielding 17:57:25 T&S_Track(dnt)12:00PM has ended 17:57:25 Attendees were npdoty, [FTC], Carl_Cargill, rvaneijk, moneill2, Fielding, WileyS, dwainberg, hefferjr, schunter, Chris_Pedigo, Amy_Colando, WaltMichel, kulick, WSeltzer 17:57:36 RRSAgent, please draft the minutes 17:57:36 I have made the request to generate http://www.w3.org/2015/01/28-dnt-minutes.html npdoty 19:57:18 Zakim has left #dnt 21:56:16 npdoty has joined #dnt 22:15:42 npdoty has joined #dnt