15:53:24 RRSAgent has joined #dnt 15:53:24 logging to http://www.w3.org/2013/06/19-dnt-irc 15:53:26 RRSAgent, make logs world 15:53:26 Zakim has joined #dnt 15:53:28 Zakim, this will be 15:53:28 I don't understand 'this will be', trackbot 15:53:29 Meeting: Tracking Protection Working Group Teleconference 15:53:29 fpf has joined #dnt 15:53:29 Date: 19 June 2013 15:53:33 Zakim, this will be TRACK 15:53:34 ok, npdoty; I see T&S_Track(dnt)12:00PM scheduled to start in 7 minutes 15:53:58 cblouch has joined #dnt 15:54:17 adrianba has joined #dnt 15:54:58 aleecia has joined #dnt 15:55:44 T&S_Track(dnt)12:00PM has now started 15:55:50 npdoty, I will be heavily multitasking. If I seem to be ignoring the call or IRC at some point, that means I've wandered off right then. I'll do what I can. 15:55:51 + +1.703.265.aaaa 15:57:01 +npdoty 15:57:24 zakim, aaaa is cblouch 15:57:24 +cblouch; got it 15:57:33 WaltMichel has joined #DNT 15:57:43 jackhobaugh has joined #dnt 15:58:12 +Fielding 15:58:19 +Craig_Spiezle 15:58:26 + +1.215.286.aabb 15:58:51 + +1.703.993.aacc 15:58:52 + +1.212.768.aadd 15:58:52 +Aleecia 15:58:56 zakim, aacc is paulohm 15:58:56 +paulohm; got it 15:59:05 + +1.202.347.aaee 15:59:09 + +1.202.210.aaff 15:59:12 npdoty, I will be heavily multitasking. If I seem to be ignoring the call or IRC at some point, that means I've wandered off right then. I'll do what I can. 15:59:13 dwainberg has joined #dnt 15:59:14 Chris_IAB has joined #dnt 15:59:17 Brooks has joined #dnt 15:59:19 Lmastria_DAA has joined #dnt 15:59:25 jchester2 has joined #dnt 15:59:26 + +1.202.331.aagg 15:59:30 peter-4As has joined #dnt 15:59:32 samsilberman has joined #dnt 15:59:32 Zakim, aabb may be susanisrael 15:59:33 +susanisrael?; got it 15:59:34 + +1.202.787.aahh 15:59:34 CraigSpiezle has joined #dnt 15:59:38 marc_ has joined #dnt 15:59:42 zakim, aabb is WaltMichel 15:59:42 sorry, WaltMichel, I do not recognize a party named 'aabb' 15:59:42 Zakim, aaee is jackhobaugh 15:59:43 +jackhobaugh; got it 15:59:47 202 210-4464 is marc 15:59:49 +Rigo 15:59:57 + +1.646.827.aaii 15:59:59 +Brooks 16:00:00 zakim, mute me 16:00:00 Rigo should now be muted 16:00:00 +jchester2 16:00:02 Zakim, susanisrael is really waltmichel 16:00:02 +waltmichel; got it 16:00:05 zakim, mute me 16:00:05 jchester2 should now be muted 16:00:11 Zakim, aaff is marc_ 16:00:11 +marc_; got it 16:00:14 zakim, aaii is dwainberg 16:00:14 +dwainberg; got it 16:00:21 Zakim, who is on the phone 16:00:21 I don't understand 'who is on the phone', npdoty 16:00:22 efelten has joined #dnt 16:00:23 Zakim, who is on the phone? 16:00:23 On the phone I see cblouch, npdoty, Fielding, Craig_Spiezle, waltmichel, paulohm, +1.212.768.aadd, Aleecia, jackhobaugh, marc_, +1.202.331.aagg, +1.202.787.aahh, Rigo (muted), 16:00:25 hefferjr has joined #dnt 16:00:26 ... dwainberg, Brooks, jchester2 (muted) 16:00:26 +vinay 16:00:26 +[IPcaller] 16:00:27 kulick has joined #dnt 16:00:28 zakim, [IPCaller] is me 16:00:29 +moneill2; got it 16:00:32 +Keith_Scarborough 16:00:35 +[Apple] 16:00:37 zakim, [apple] has dsinger 16:00:37 +dsinger; got it 16:00:42 johnsimpson has joined #dnt 16:00:44 + +1.650.595.aajj 16:00:51 + +1.781.482.aakk 16:00:54 Zakim, aadd may be [DAA] 16:00:54 +[DAA]?; got it 16:00:55 Ari has joined #dnt 16:00:56 + +1.937.215.aall 16:00:57 Keith has joined #dnt 16:01:01 + +1.609.258.aamm 16:01:02 + +1.408.836.aann 16:01:08 Zakim, aamm is me 16:01:09 +efelten; got it 16:01:16 zakim, aakk is samsilberman 16:01:16 +hefferjr 16:01:16 +samsilberman; got it 16:01:20 +BerinSzoka 16:01:27 WileyS has joined #DNT 16:01:29 Zakim, who is on the phone? 16:01:29 On the phone I see cblouch, npdoty, Fielding, Craig_Spiezle, waltmichel, paulohm, [DAA]?, Aleecia, jackhobaugh, marc_, +1.202.331.aagg, +1.202.787.aahh, Rigo (muted), dwainberg, 16:01:32 ... Brooks, jchester2 (muted), vinay, moneill2, Keith_Scarborough, [Apple], +1.650.595.aajj, samsilberman, +1.937.215.aall, efelten, +1.408.836.aann, hefferjr, BerinSzoka 16:01:32 [Apple] has dsinger 16:01:32 +MIT531 16:01:32 + +1.415.470.aaoo 16:01:36 +Jonathan_Mayer 16:01:41 + +1.240.994.aapp 16:01:46 ninjamarnau has joined #dnt 16:01:54 +Peder_Magee 16:01:59 +WileyS 16:02:06 peterswire has joined #dnt 16:02:13 Zakim, aall is Yianni 16:02:15 rvaneijk has joined #dnt 16:02:15 +Yianni; got it 16:02:17 robsherman has joined #dnt 16:02:21 + +49.431.98.aaqq 16:02:35 zakim, aaqq is ninjamarnau 16:02:35 +ninjamarnau; got it 16:02:41 zakim, MIT531 has rsherman, wseltzer 16:02:41 +rsherman, wseltzer; got it 16:02:44 Zakim, aahh is billscannell 16:02:44 +billscannell; got it 16:03:00 + +1.917.934.aarr 16:03:04 +??P84 16:03:05 pmagee2023263538 has joined #dnt 16:03:05 susanisrael has joined #dnt 16:03:08 I just joined 16:03:19 npd_test has joined #dnt 16:03:19 zakim, ??p84 is Chris_IAB 16:03:20 +Chris_IAB; got it 16:03:22 + +1.310.292.aass 16:03:32 sidstamm has joined #dnt 16:03:41 aass is john simpson 16:03:42 zakim, pick a victim 16:03:42 Not knowing who is chairing or who scribed recently, I propose Keith_Scarborough 16:03:49 scribenick: susanisrael 16:03:52 I joined from 52-661-100-xxxx 16:04:01 +[Microsoft] 16:04:06 fine by me 16:04:10 good sound 16:04:11 zakim, aass is john simpson 16:04:11 I don't understand 'aass is john simpson', johnsimpson 16:04:12 cOlsen has joined #dnt 16:04:12 JC has joined #DNT 16:04:16 -[Microsoft] 16:04:18 +[Mozilla] 16:04:21 Zakim, Mozilla has sidstamm 16:04:21 hwest has joined #dnt 16:04:21 +sidstamm; got it 16:04:25 +hwest 16:04:28 zakim, aass is johnsimpson 16:04:29 +johnsimpson; got it 16:04:37 schunter has joined #dnt 16:04:40 +[Microsoft] 16:04:52 +[FTC] 16:04:56 can we put a link here to the doc? 16:04:59 Zakim, aaoo is omer_tene 16:04:59 +omer_tene; got it 16:05:03 peterswire: thanks for joining everyone. the text to start with is the email i circulated, proposing how to proceed toward last call, circulated last friday, jointly signed by Mattias and me. 16:05:15 npdoty, can you please provide links to these docs here? 16:05:21 http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance-june.html 16:05:25 + +31.65.141.aatt 16:05:25 -Jonathan_Mayer 16:05:35 npdoty, awesome, thanks :) 16:05:39 Zakim, aatt is me 16:05:39 +rvaneijk; got it 16:05:50 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0145.html 16:06:01 ...will walk through that for discussion. The june draft is the version from June 14. we are now proposing the june draft for discussion with goal to end up with last call draft. 16:06:10 +Chris_Pedigo 16:06:16 Zakim, who is on the phone? 16:06:17 On the phone I see cblouch, npdoty, Fielding, Craig_Spiezle, waltmichel, paulohm, [DAA]?, Aleecia, jackhobaugh, marc_, +1.202.331.aagg, billscannell, Rigo (muted), dwainberg, 16:06:17 ... Brooks, jchester2 (muted), vinay, moneill2, Keith_Scarborough, [Apple], +1.650.595.aajj, samsilberman, Yianni, efelten, +1.408.836.aann, hefferjr, BerinSzoka, omer_tene, 16:06:21 ... MIT531, +1.240.994.aapp, Peder_Magee, WileyS, ninjamarnau, +1.917.934.aarr, Chris_IAB, johnsimpson, [Mozilla], hwest, [Microsoft], [FTC], rvaneijk, Chris_Pedigo 16:06:21 [Mozilla] has sidstamm 16:06:21 [Apple] has dsinger 16:06:21 MIT531 has rsherman, wseltzer 16:06:21 + +1.202.639.aauu 16:06:22 mecallahan has joined #dnt 16:06:23 justin and heather the compliance spec document have left open that this could be listed as a formal editors draft[?] 16:06:31 laurengelman has joined #dnt 16:06:54 +??P94 16:06:56 ....have been working closely with people at w3c who will be working together to provide good customer service to everyone.... 16:07:01 Zakim, aapp is peterswire 16:07:01 +peterswire; got it 16:07:23 ChrisPedigo_OPA has joined #dnt 16:07:31 the first item talks about sending a group of annotations to the june draft. You have available a couple of things, one from yianni june 10 and a subsequent version explaining differences from previous draft.... 16:07:39 Zakim, ??P94 is laurengelman 16:07:39 +laurengelman; got it 16:07:43 Yianni's comparison is attached: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0051.html 16:08:12 ....also on annotations for each section it clearly labels the currently open issues......you can see what issues in play or go issue by issue and see what changes have happened. 16:08:14 zakim, MIT531 has thomas 16:08:14 +thomas; got it 16:08:20 -rvaneijk 16:08:20 Chapell has joined #DNT 16:08:51 +[Microsoft.a] 16:08:54 ....in general the june draft was an effort by thomas and others who have experience with this kind of spec. As call with Aleecia showed, things can be dropped in any editing process. 16:08:57 zakim, [Microsoft.a] is me 16:08:57 +adrianba; got it 16:09:30 Zakim, aann may be kulick 16:09:30 +kulick?; got it 16:09:32 +rvaneijk 16:09:37 .....we will hopefully have streamlined user friendly process going forward for editorial and small grammatical changes which will be posted to email list, but will raise anything to group that seems to be substantive. 16:09:43 having trouble getting onto conf line 16:10:03 Does the issue tracker now reflect the June draft? I am confused.. 16:10:15 rvaneijk_ has joined #dnt 16:10:20 peter's email from June 14: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0145.html 16:10:24 ....for substantive proposals for issues where you would like to have different substance than the june draft, my email says we invite any of you to propose new text for anything in the june draft.....if you ask to open an issue we willl...... 16:10:58 ...there may be many proposals on same issues, so in that case we'll use discretion, won't have exactly one issue for each proposal but will group proposals when they are on same issue..... 16:11:00 q? 16:11:26 want to underscore that this is an invitation for you to contribute where you think there are things we should discuss..... 16:11:30 Mike_Zaneis has joined #dnt 16:11:33 +Jonathan_Mayer 16:11:33 anyone else having trouble 16:11:37 Peter: What is the deadline for proposing changes? Thks 16:11:38 can't dial-in 16:11:51 at the end we will have to come back to the whole group to see whether the whole doc is acceptable.... 16:11:58 deadline for this is a week from today.... 16:12:09 [Wednesday, June 26] 16:12:18 SO WEDNESDAY JUNE 26 is deadline for submitting/opening issues.... 16:12:45 Zakim, aauu may be mecallahan 16:12:45 +mecallahan?; got it 16:12:49 npdoty thanks - trying from cell and land line 16:13:06 if today you all agree to follow this process we will close the currently open issues and this is at some level bureaucratic, not an attempt to close off issues.....you have full power to open issues.....which will be proposed amendments to the june draft... 16:13:07 yes it is zakim thanks. 16:13:44 q? 16:13:45 bc everyone in group gets to have proposals, we will then know the universe of things that we need to work on. there would be new sequentially numbered easy to read list of issues, linked to old issue numbers.... 16:13:52 JoAnn has joined #dnt 16:14:06 The phone lines are not working. I've also tried on landline and cell. 16:14:37 timing: our last call deadline is end of july, july 31. It does not seem wise to be deciding on the last day....so the wednesday before that will be a key planned meeting to decide where the group is..... 16:15:12 +[IPcaller] 16:15:13 i would like to propose no punting rule from jmayer. we are trying to get the text done. It would take an affirmative decision by the group to extend beyond July 31. 16:15:24 kj has joined #dnt 16:15:35 Mazel Tov, Peter! 16:15:42 Zakim, who is making noise? 16:15:54 npdoty, listening for 11 seconds I could not identify any sounds 16:15:58 on personal side i will not be doing W3C work in early august. I am getting married Aug 2 and going on honeymoon and i will not be taking do not track calls during the first part of august.... 16:16:07 q? 16:16:24 so i am trying to show you the seriousness of doing our work during the first part of july. there is no easy way to push th is off..... 16:16:47 + +1.202.253.aavv 16:16:51 vincent has joined #dnt 16:16:59 -[IPcaller] 16:17:08 + +1.604.639.aaww 16:17:17 some other aspects of how we propose to operate during this period. Beginning next Wednesday, we are going to have a procedure of discussion of sort of looking at counterproposals that we have been talking about with stafff at w3c.... 16:17:22 Zakim, aaww is me 16:17:22 +schunter; got it 16:17:23 zakim, MIT531 also has tlr 16:17:23 +tlr; got it 16:17:27 +[IPcaller] 16:17:36 we will let you know what issues will be discussed and try to move them along. 16:18:06 Fifth times the charm. (202) 253-1466 is Mike_Zaneis 16:18:18 + +1.646.666.aaxx 16:18:21 tlr: essential plan is to use decision process as documented. there is one piece in early part where we will deviate. In current process it has close control of who drafts what by chair..... 16:18:26 zakim, aavv is Mike_Zaneis 16:18:26 +Mike_Zaneis; got it 16:18:29 -[IPcaller] 16:18:45 zakim, aaxx is chapell 16:18:45 +chapell; got it 16:18:51 Zakim, aarr may be susanisrael 16:19:10 zakim, who is making noise? 16:19:14 as peter just said for the next week there is an opportunity to put basic text on table to inform issues list. there will be opportunity to discuss and make counterproposals. Once all on table we will have call for objections and work through objections to arrive at decisions on issues. 16:19:22 dsinger, listening for 10 seconds I heard sound from the following: +1.650.595.aajj (4%), MIT531 (92%) 16:19:56 q? 16:19:57 we should be able to do a good round of triage, there will be issues we think might be useful to resolve but not crucial and those might go on different time scale. 16:20:00 I am not sure I understand how you will resolve two conflicting proposals for an issue. 16:20:21 we will decide timeline, but it depends on what issues and proposals are on table a week from now. 16:20:27 zakim, mute aajj 16:20:27 +1.650.595.aajj should now be muted 16:20:50 peterswire: so we will be moving on schedule to resolve issues and if they don't resolve we will put them out for people to decide by July 24 call. 16:21:28 For the record, Thomas. I am concerned there is an attempt perhaps by the W3C to rush through this process. I am especially concerned that items which clearly need due-diligence are and won't be addressed sufficiently. I expect W3C to be held accountable by the public for the process it adopts to address the issues at hand and will be presented. 16:21:39 peterswire: up to now we have had many meetintgs. In next period the core work of the group should happen on the list. we will be looking at text. that is where the hard work of the group will happen..... 16:22:22 i will have new policy for this period. Will inform group when i have meetings or calls with members of the working group.....will be done based on "on the record and transparent process....." 16:22:57 so if discussion is not on list, the fact that it took place will be noted on the list.....more traditional w3c process. 16:23:13 q+ 16:23:14 this is to try to assure people that they will be seeing what the real deliberations are. 16:23:30 q? 16:23:31 q+ 16:23:36 i am trying to explain what i had prepared for today to say this is the process the chairs propose. 16:23:56 q+ 16:24:09 ack fielding 16:24:13 royfielding: i don't see value in closing issues just because there is a new june draft. there is small number of issues we have managed to close. I don't think new and old issues are comparable. 16:24:52 ...the notion of closing issues as a beaurocratic matter is wrong. the idea is that when we go to last call and go to cr we have a record of all the issues..... 16:25:28 I note that compliance only has 33 open issues . It shouldn't be too hard to go through them but give them a little thought each. 16:25:44 if we close based on nondecision we have to go further. doesn't make sense to me. I encourage chairs to make use of other status in issue tracker to note when issue not closed. I don't think clean slate is worthwhile. 16:26:17 +Dan_Auerbach 16:26:37 peterswire: one thing that has happened in compliance spec is that many issues seemed interdependent so people were reluctant to close almost anything. One goal for next period is to know what is up for grabs, what people are working on. 16:26:37 q+ on issues 16:27:12 so working with staff we think having one draft and one set of issues will provide maximum clarity and people will know what is disucssed. 16:27:20 ack johnsimpson 16:27:53 +q 16:28:02 johnsimpson: this clarifying sort of situation i am perhaps remarkably dense, perhaps from being on vacation. so i understand you are closing all issues with june draft and it is incumbent on us to propose new text if we want an issue to remain open, right? 16:28:12 peterswire: that's correct. 16:28:48 johnsimpson: but there is language on a number of issues that was proposed that is not in the text so should we find it and re-propose if we think it's really really important? 16:29:31 peterswire: it doesn't have to be that important. it's easier for you to know which things you want, which language than for me and w3c staff. You get to help us to understand your current view. 16:29:40 To clarify, a closed issue in the W3C means that the WG has made a decision (using any of the available means to make a decision) and the topic is no longer to be discussed until new information is available that might overturn that decision. Closing issues for bureaucratic reasons is inappropriate because it messes up both the history of discussion and the record of what has been decided. 16:30:31 me suggest to re-submit the text from the Working Draft into the right section of the June Draft 16:30:31 johnsimpson: example: in public draft there was security and fraud language with graduated response. this was dropped in june draft. other language was submitted. so your advice would be there should be 2 submissions re issue, and if not they will not be considered. 16:30:36 johnsimpson, to clarify, the first submission did not have graduated response language, but Roy did propose it later... 16:30:56 It would make more sense to create a new product in the issue tracker, specific to the new draft, and only assign those issues to the new draft that still apply and are requested by someone. 16:31:17 peterswire: yes, if you think there should be language re graduated response then propose to list. If we think your language and chris's are same issue we will combine, if different, not. 16:31:29 q? 16:31:33 ack aleecia 16:31:41 queue later 16:31:41 q+ 16:31:45 q+ aleecia 16:31:45 q+ 16:31:47 sorry 16:31:47 zakim, mute aleecia 16:31:47 Aleecia should now be muted 16:31:49 ack dsinger 16:31:49 dsinger, you wanted to comment on issues 16:31:54 zakim, unmute me 16:31:54 jchester2 should no longer be muted 16:32:07 to clarify 12 open issues, 33 includes pending review 16:32:10 +1 to dsinger 16:32:17 I remain unclear how "consensus" will be decided or conflicting proposals will be resolved over the next 5 weeks. Some more clarification would be helpful to the entire group. 16:32:26 dsinger: can i suggest we open have 33 open issue and many can be marked or split and someone could go through for an hour and mark, retain, split. 16:32:52 q+ 16:33:02 q- 16:33:03 peterswire, to clarify (respectfully), are you telling us how it's going to be, or are you asking for feedback on your proposed new process? 16:33:03 q+ 16:33:07 q+ 16:33:11 q- 16:33:11 I think peterswire's point to dsinger is that even if we retain the same 12 issues, we'd need to clarify what the text proposals (in diff from the June draft) 16:33:12 q+ 16:33:17 peterswire: david you have a lot of experience so let me ask you. concern has been there have been many rounds. doing the archaeology re: someone's preferred language seems a difficult task. Proposal to have little archaeology. 16:33:25 q? 16:33:38 -BerinSzoka 16:33:47 dsinger: you are talking about issues with work done on them. take def of tracking. June draft has one. SO i suggest moving to pending review. 16:33:49 peterswire, to clarify (respectfully), are you telling us how it's going to be, or are you asking for feedback on your proposed new process? I'm not being cheeky, just want to understand. 16:34:16 npdoty, could you please enqueue jmayer 16:34:21 q+ jmayer 16:34:26 peterswire: i am not hung up on issue number. one variation is "issue 5 open, on tracking, and people beginning today submit preferred language. 16:34:33 thomas do you have advice? 16:34:37 thanks, sorry, losing syntax 16:34:54 I'm just asking that each issue be considered, and if its status changes, there are notes to explain what and why, that's all. 16:35:25 tlr: 2 concerns: 1) roy's to keep the record and not conflate closed or put aside for admin reasons with closed with or without prejudice. Roy right? (roy: yes). 16:35:28 -Brooks 16:35:38 I completely agree some can now be closed; because they are not relevant, because they have been split into more specific issues, and so on. Some can be postponed, and so on. 16:36:05 Some can go into 'pending review' as the June draft addresses them. 16:36:08 we could keep open issues, but still ask that everyone send their considered text proposals still needed for that issue (so that we don't have to search for every previous text proposal when going through the decision process) 16:36:17 zakim, who is making noise? 16:36:19 + +1.678.492.aayy 16:36:28 dsinger, listening for 10 seconds I heard sound from the following: jchester2 (4%), MIT531 (94%) 16:36:29 tlr: second set of concerns have 2 competing goals. we have significant but incomplete state of affairs in records. I have tried to spend time on this and have had to do archaeology or ask people state of affairs. Bottom line is tracker is not in very good shape. 16:36:47 +BerinSzoka 16:37:14 I completely support cleaning up the tracker; I just want it done with a little thought, and tracing notes, on each issue. That's all. 16:37:18 tlr: so second set of concerns is we have a lot of good material in previous editor's draft, lot of good material in tracker, but not very orderly tracker. Need to know what people are currently supporting. 16:37:25 peterswire, to clarify (respectfully), are you telling us how it's going to be, or are you asking for feedback on your proposed new process? I'm not being cheeky, just want to understand. 16:38:10 tlr: process will allow us to collect very quickly a list of where the real issues are. And i would like to ask indulgence to have a clean split for current issues and structure for coming weeks. But roy's point of keeping rercord is well taken. 16:39:10 …a new product is fine by me, and leaving the old one alone. 16:39:13 tlr: so will suggest slight modification to process. suggest we leave the issues in compliance spec alone. asking everyone's help to make sure we have a clean set of issues to work against. 16:39:33 q? 16:40:00 ack tlr 16:40:07 may be similar list of issues to those in trackers, but looking for your support to get clean, currently live set of issues to work against. We are asking for your help. Roy's concern is well taken but i think we can address it. 16:40:34 unmute aleecia 16:40:40 peterswire: thomas has made a proposal that seems sensible to me and i will go through queue to see if any reaction. 16:40:40 (have muted locally) 16:40:48 zakim, unmute aleecia 16:40:48 Aleecia should no longer be muted 16:41:41 tlr proposal: new product Compliance June, on which we create issues around specific text proposals to the June draft, leaving existing Compliance issues alone (although in some cases they will be directly connected to a Compliance issue) 16:41:44 ack jchester 16:41:55 jeffchester: I have real process concerns. as a member of very small ngo group/civil society, one week is not sufficient to do this kind of hard work. I don't want to have to drop everything i am doing. I have a feeling w3c is trying to rush this. 1 week not sufficient. 16:41:56 +1 to Jeff Chester (1-week is not enough time) 16:42:02 ...peter i cannot see you endorsing. 16:42:12 I think if we leave the open issues 'as is' on the old product, then we're clear. we can then review them as needed. Thomas' approach seems fine to me. 16:42:26 thanks, David 16:42:32 peterswire: we have a deadline, and I am trying to move the process under the deadline. we have tried to see if we can get to closure. 16:42:49 zakim, mute me 16:42:49 jchester2 should now be muted 16:42:52 -rvaneijk 16:42:53 ack fielding 16:42:59 jeffchester: giving the group a week to make substantial proposals on this does not do service to this crucial privacy measure. 16:43:41 q? 16:43:53 royfielding: re: tlr proposal, i suggest one change. If an issue exists it should be possible to pull it out, not renumber issue, and attach to new doc. Almost identical but not with new numbers., 16:44:04 q? 16:44:09 tlr: ok for old issues, but not for new ones that mix issues. 16:44:15 roy: leave that to chairs 16:44:16 kj_ has joined #dnt 16:44:21 tlr: +1 16:44:28 we may not need a whole bunch of new text, where some issues are going to be presenting the text that we have already 16:44:34 ack Chris_IAB 16:44:38 chris_iab: is this a proposal or are you telling us how it will be done. 16:44:42 +1 to Nick 16:45:14 peterswire: this is proposed approach, subject to discussion/modification, and we will see what the group decides. 16:45:19 ack aleecia 16:46:46 aleecia: i think i agree with goals but i am extremely concerned with way it's going in practice. what i hear from thomas is we will not just have clean slate but really clean state, so no issues live unless re-raissed. so ojectiions to having to sustained objections to sustained objectsions. 16:46:53 if you have been talking about something over 2.5 years, there should be at least a viable text proposal. 16:47:15 To be clear: what I hear Thomas proposing is that we create a new 'product', and open issues against that. That we *leave the issues* on the existing product, and will go through them at some point to make sure that they are addressed, etc. I can live with that. I even volunteer to help the pass on the old issues. 16:47:20 I think tlr is suggesting that we need a process to clarify specific alternate text proposals requiring collaborative work, rather than generating new text or new objections 16:47:23 I request that Thomas, on behalf of the W3C, send a letter to the group--which should be made public--given the rationale for the process he has proposed. 16:47:28 what is a viable text that opposes the inclusion of text? 16:47:45 to clarify, I don't have real issue with the new process being proposed, just the very tight timeline 16:47:49 rigo, "change proposal: Strike section foo" 16:47:50 ....it's frustrating if you did not have time to look at things in that week or two. I would be in favor of extending the deadline. we have done it before. Draft is more readable. We have things we cannot decide in 6 weeks. we are not at last call. 16:47:54 rigo, that's a one-liner 16:48:24 on a moving target? That's what Aleecia complains about ... 16:48:24 It can't be done in the time frame proposed. It's setting up the privacy issues to fail. 16:48:24 ....i am willing to put in more time. So 1) extend the charter, 2) i think that asking us to re-raise things in 2 weeks is unreasonable. 16:48:31 -BerinSzoka 16:49:01 q? 16:49:02 the charter runs to 4/2014, right? 16:49:08 peterswire, tlr, and npdoty, to clarify, I don't have real issue with the new process being proposed (that process seems reasonable), just the very tight timeline-- it's too tight, with the new process, and the only thing at stake here is the Internet. 16:49:15 peterswire: so i hear proposal to extend the charter. I have been operating with the sense that many people do not want to extend. one of the things re: sustained objections, is we have tried to make it as easy as possible. 16:49:26 tlr, which is in tension to moving forward. I think it is a question of mechanics 16:49:31 q? 16:49:35 dwainberg, get on the cue to ask that good question 16:49:39 +q 16:49:40 q? 16:49:52 tlr, perhaps create an issue on "same-party" and note her opposition there 16:49:55 dwainberg, I think the suggestion is more specifically changing the timeline to change the Last Call date, which might ultimately need to extend the charter 16:49:59 cannot hear 16:50:00 the june draft was less than 7 pages. I think it should be a short matter. The idea is to push now so we do not have to push into fall and winter. This is what i think group has been saying instead of extend charter. 16:50:00 lots of background noise 16:50:03 Zakim, who is making noise? 16:50:15 npdoty, listening for 11 seconds I heard sound from the following: Jonathan_Mayer (76%) 16:50:40 to be clear, I had two proposals. One was extend the deadline. The other was: do not do this "clean slate" approach on issue management. 16:50:59 +Aleecia 16:51:20 jmayer: 2 points: on using june draft. with a week, can't produce new text in 1 week so we will go to old text and will end up where we were before. so we are trying to de-clutter but may end up re-cluttered very shortly. 16:52:01 aleecia, what did you think about fielding/tlr on new product, which may create new issues or move issues onto a new product? 16:52:14 q? 16:52:19 I think Jonathan's idea is a good one. 16:52:23 ack jmayer 16:52:24 ....peter has suggested we consider alternatives, and i am not process with chair reconciliation so i suggest we consider contingency plans. suggest we get back to substance. has been a month since we worked through substantive compliance issues. 16:52:51 a slightly different approach would be to come up with various compromise proposals. that would be my alternative process proposals. 16:52:55 q? 16:53:00 ack Chris_IAB 16:53:11 For the record, I think the old compliance document was enough of a mess to be almost unworkable, and that the June document is a much better basis going ahead. 16:53:24 npdoty, as I said: I think it is a bad idea. It will turn the current issue list into an historic archive. 16:53:28 chris_iab: dwainberg asked good question. when does current charter expire? want to understand charter deadline vs. wedding deadline. 16:54:04 aleecia, I thought fielding's amendment was intended to prevent that, by keeping and moving issues that do fit text proposal diffs 16:54:07 Wiping away 2.5 years of work while asking us to recreate it in 1 or at most 2 weeks is a big ask 16:54:18 tlr: charter runs to early 2014 but premised on timeline that assumes group goes to last call in july. In sunnyvale we agreed to press forward to last call deadline and i think it matters for once to stick to deadline. 16:54:50 npdoty, if we do that, I expect we will migrate about 80% or more of issues. Would be faster to find the 20% to drop, and in keeping with normal process 16:55:24 tlr: we can't just go on like this and keep extending deadlines. of course if as a group we can come to a single proposal on a particular issue but i don't think we should just go on and on talking so i support the approach of driving to july 31 to resolve set of very significant issues. 16:55:54 -kulick? 16:55:59 q? 16:56:21 I think if we leave the issues on the current draft alone, then we don't lose the past. Giving us a clean product makes sense; keeping the history visible and usable also makes sense. 16:56:22 chris_iab. I don't have issues with process but have issues with the timeline during the season of vacations, etc. it will take time for people to pivot to new approach whether better or not. 16:56:51 -marc_ 16:56:53 peterswire: heard 3 approaches: mine/staff's, aleecia's to extend, jmayer, contingency plan to work toward closure. 16:56:53 + +1.408.836.aazz - is perhaps kulick? 16:57:01 yes, that is kulick 16:57:25 peterswire: propose we raise each with +1/-1. then see what group decides. 16:57:38 Peter: Who is missing from the call and this vote? 16:57:41 q+ 16:57:55 so 1) decision now to say no last call deadline July 31. call on aleecia to say if that's proposal. 16:58:19 aleecia: yes, propose publishing another working draft and extend deadline for last call. 16:58:24 ack tlr 16:58:26 q+ 16:58:31 tlr: do you have another deadline that we could really stick to? 16:58:58 Cant hear at all now 16:59:00 too much noise 16:59:00 can't hear due to background noise 16:59:23 aleecia: happy to accept friendly amendment of another date for last call doc, and would suggest looking through issues to do this. Am hard pressed to see how we get to closure on permitted uses and what it means to de-identify data in time for last call. 16:59:23 q? 16:59:30 q- 16:59:38 can peter mute/unmute? #60 is mute and #61 is unmute 16:59:42 q+ 16:59:45 ....would leave those open, and how can we go to last call without those. I don't see how we get there. 16:59:53 that noise should not be me 16:59:57 q+ 16:59:58 or it is 60# 17:00:02 aleecia: suggest going through issues to get there. 17:00:15 painful for me too 17:00:17 we keep getting background noise.. 17:00:23 -samsilberman 17:00:26 That's a reasonable process that Aleecia is proposing. Otherwise the process adopted by WC3 appears to be designed not to address key concerns. 17:00:30 zakim, who is making noise? 17:00:32 zakim, who is making noise? 17:00:41 dsinger, listening for 10 seconds I could not identify any sounds 17:00:51 rigo, listening for 10 seconds I could not identify any sounds 17:00:58 chris_iab: am i the only one hearing all background noise. OK better. all this about deadlines....I run an industry working group and i appreciate that we want to bring work to logical end but that's the key, "logical end.".... 17:00:59 W3C groups have in the past gone to Last Call without closing every single issue, Last Call is an attempt to close enough issues that it can be revealed to wider public review 17:01:08 I think the WG should be terminated if we can't agree on a resolution to ISSUE-5 (definition of what it is the user is asking to turn off) in the next two weeks. 17:01:09 dan_auerbach has joined #dnt 17:01:49 q? 17:01:55 ....we are talking about something with massive effect on billions of dollars, way industry run. I like new process and roy's suggestions, but also aleecia's suggestion to look at issues to determine a new deadline. then we are talking about new firm deadline. 17:01:55 ack Chris_IAB 17:02:08 notes to fielding, that the June draft has a definition that matches what we've been saying for at least a year... 17:02:18 q+ 17:02:22 Interesting thought, Roy Fielding 17:02:27 ....i agree with jmayer that if we don't get there we then pull plug. I am worried about pivot time. I dont want to put internet at risk bc i have vacation. 17:02:41 q+ 17:02:57 dsinger, it matches what you have been saying … not the group, and is completely inconsistent with the other decisions we have made. 17:03:00 peterswire: as email to group has said we have been going around on these issues. 17:03:02 ack Mike_Zaneis 17:03:06 peter, hit "hide keypad", then you'll have a mute buton 17:03:19 thx! 17:03:29 fielding, offline I'd like to hear what's inconsistent from your perspective 17:04:03 q? 17:04:05 mike zaneis: reacting to suggestions put forward. when charter extension has come up in past, then people want to revisit original charter bc a lot has changed re: browser controls etc. So if we have discussion of whether group goes on.... 17:04:07 close q 17:04:13 q+ 17:04:14 Zakim, please close the queue 17:04:15 ok, npdoty, the speaker queue is closed 17:04:15 think Roy is concerned that it would mean first parties are tracking... 17:04:54 should discuss under what mission. Maybe charter is not appropriate in scope......so if we can have the discusison if charter is extended then we should. Without saying whether i support extending. 17:05:19 Mike could be right-- we may need to reduce the scope to something less controversial and divisive, in order to get consensus on something meaningful 17:05:36 peterswire: my understanding is this would not be extension of charter but last call. 17:05:47 q- 17:05:57 mike zaneis: i understand but it seems that based on that whole group would have to be extended. 17:06:20 If we need to move Last Call, pursuant to the current timeline, we will need to extend the charter 17:06:24 wanted to make the point that Last Call isn't the end of work or the finalization of everything, there are three additional milestones after Last Call 17:06:27 -1 to extending the last call deadline 17:06:30 -npdoty 17:06:34 ...august will be dead month. have to think about how much more time in fall. Will push back testing. So then should discuss extending charter. 17:06:43 The inconsistency is that users do not want all personalization to be turned off -- what they want is not to be followed across unrelated contexts, and thus not have their activity on one site shared or known by other sites. That's what do not track means to them, and that's what we should define it as meaning for our drafts. 17:06:48 Last Call is a chance to get wider public review and more feedback from implementers 17:06:49 tlr: so do you support july 31 deadline? 17:06:53 without evidence that we will make substantive progress 17:07:13 mike zaneis: i think we should try, but if we don't succeed let's discuss scope of charter. 17:07:20 +npdoty 17:07:25 q? 17:07:37 ack schunter 17:07:45 Fielding +1 - although that assumes we agree on the definition of "unrelated contexts" 17:07:49 mattias: agree that just because some of us on holiday we should not break the internet. shifting from 2 year discussion mode to 3 week panic mode is radical. 17:08:29 dsinger: compliance draft is not organized hard to understand. June draft helps. Let's see what the real issues are then see whether we need to extend. 17:08:32 ack dsinger 17:08:42 David's analysis is correct, in my view. We need to examine the current state of the text. 17:08:50 +1 17:08:52 -1 17:08:53 -1 17:08:54 -1 17:08:54 peterswire: so +1 means you want to extend right now. 17:08:55 -1 17:08:56 +1 17:08:56 without evidence htat we will make progress 17:08:57 +1 17:08:58 +1 17:08:58 -1 17:09:03 Lmastria_DAA has joined #dnt 17:09:06 -1 17:09:06 +1 17:09:06 -1 17:09:07 +1 17:09:09 -1 17:09:12 +1 17:09:13 +1 publish a working draft and extend the last call deadline; -1 to oppose 17:09:14 0 17:09:15 -1 (not until we do the research) 17:09:16 +1 17:09:17 -1 17:09:22 +1 17:09:22 -1 17:09:25 i agree with davd and jeff that in a couple weeks we may be in better position to decide. 17:09:27 -1 17:09:33 -1 17:09:37 peterswire: can someone do rought count. 17:09:39 -1 17:09:40 -1 17:09:40 about 9 +1 17:09:47 about 9 -1 17:09:52 lol 17:09:55 15 -1s 17:09:56 it sounds to me like several of the -1s agree that we need to first make progress 17:10:01 before switching to +1 17:10:01 but some more came by as I was counting 17:10:02 -1 let's push and revisit 17:10:03 That's so unusual for this group :-) 17:10:21 just a sec 17:10:24 peterswire: can you say what you are trying to express on irc. 17:10:28 [the sum appears to be -4] 17:10:29 -1 let's push and revisit - may need to revisit charter as well tho 17:10:30 It's hard to make progress when all we do is debate process. 17:10:43 +q 17:10:50 I agree with singer 17:11:30 substantive discussion based on past record 17:11:33 peterswire: split but no consensus to extend. Now jmayer proposal to go to contingency plan if not wound up by july and look at compromise proposals, without renumbering issues. 17:11:44 cannot understand!!!! 17:11:46 hard to hear 17:12:19 i didn't want to interrupt -- i'm in transit to talking is difficult -- but i think several people including David, myself Jeff, Susan, that we shouldn't extend right now 17:12:35 -paulohm 17:12:39 Jonathan, can we just get the proposal to +1 or -1? 17:12:42 Noting time is tight 17:12:45 my way of framing that is to say that we need to make progress first 17:12:48 jmayer: that's it. get back to substantive work. should be proud of what we have done so far. have come to fork in road. think june draft whitewashes disagreements, or could move goalpost, go to chair decisions, and i am not comfortable with either. 17:13:01 ....want to come up with contingency plan. 17:13:27 peterswire: so not use chair decision, talk substance in next period, have contingency plan if no last call. 17:13:45 So is this: +1 to discuss how we *would* shut down? 17:13:45 jmayer: yes, not super-wedded to how we proceed. 17:14:05 what's the positive proposal? just discuss compromises until end of July? 17:14:26 peterswire: so if no chair decision and no extension how should we spend time til end of july. 17:14:37 process is good, please use mine... 17:14:42 Jonathan's approach is reasonable and is, in my opinion, the honorable way to proceed. 17:14:53 q+ 17:15:02 zakim, reopen queue 17:15:02 ok, tlr, the speaker queue is open 17:15:04 jmayer: ask stakeholder orgs to put together compromise proposals. {didnt catch other alternative}. prefer giving up to coming up with false consensus. 17:15:08 q+ 17:15:08 count is +1 : 13; -1: 19. Nick seems to have voted both ways 17:15:12 q+ dan_auerbach 17:15:26 q- 17:15:37 (I was getting on the queue earlier to explain my IRC comment) 17:15:59 thx to dan 17:16:04 oops, then it's +1: 12, -1: 19 17:16:13 chris_iab: reply to jonathan and mike. If there is core set of things we don't agree on maybe we need to re-evaluate scope of group. Maybe we have bitten off too much. Is there something we can do as a group that is a meaningful step forward? 17:16:13 zakim, who is speaking? 17:16:24 johnsimpson, listening for 10 seconds I could not identify any sounds 17:16:31 instead of having "stake holder groups" make compromise positions, why not have some of the more moderate members create compromise proposals and the top 5 remaining open controversial issues. 17:16:31 doesn't mean would drop everything for future. Maybe the way to do that is scope alteration. 17:16:46 q+ to ask for a ten-word description of Jonathan's proposal, to which we could +1/-1 17:16:49 ack Lmastria_DAA 17:17:22 +1 17:17:31 lmastria: wanted to react to one proposal jmayer made: I think we did come up with compromises in sunnyvale. It strikes me that the june draft is moving in that direction, to compromise. So not sure why we would need to do that again. 17:17:51 jmayer: i think the proposal i have in mind is compatible with document. 17:17:53 having trouble hearing jonathan 17:18:08 [i can't hear jonathan well enough to scribe] 17:18:13 q? 17:18:24 cannot hear jonathan, can he put it in IRC? 17:18:26 Could jmayer type his proposal in? Mine is to develop asap our issue list with the june draft, using it and the current compliance issue list, and see where we are. 17:18:40 -Aleecia 17:18:47 sorry - 17:19:15 npdoty: i am not sure i caught jmayer last point, but i think he suggested we work on june draft. Is it different from chair's proposal? Not sure what we would be voting on. 17:20:01 peterswire: hard to get crisp sense of jmayer proposal. discuss contingency plan if no resolution by end of july? 17:20:25 q? 17:20:32 q+ 17:20:40 close q 17:20:46 ack np 17:20:46 npdoty, you wanted to ask for a ten-word description of Jonathan's proposal, to which we could +1/-1 17:20:49 jmayer: maintain longstanding decision process and don't rush through new process of consensus and then develop contingency plan if last call draft is not resolved by end of july. 17:21:00 how about: work hard issue by issue, determine consensus or lack thereof by longstanding decision process, make contingency plan if lack of consensus persists 17:21:05 -1 on "long-standing decision process" because what jmayer means by that is we continue failing to use the W3C documented process. 17:21:09 jmayer: to decide on that text, use longstanding decision process. 17:21:15 So there are 2 proposals. One would be on what we do next in terms of issues, and not try and review all the issues in the next week. We pick key issues to discuss. Next is that we prepare a contigency plan. 17:21:18 jmayer proposal: a) maintain decision process and not use the chair reconciliation; and, b) develop a contingency plan 17:21:24 q+ 17:21:27 q? 17:21:30 ack sch 17:21:32 peterswire: first: longstanding decision process, second, contingency plan if no decision. 17:22:21 we have long had the decision process in place for issues that cannot be resolved otherwise, and we have a set of issues that have proven difficult to resolve 17:22:24 mattias: longstanding decision process hasn't work so we have to change something fundamentally. at risk of.....[can't hear] 17:22:26 it was hard to hear 17:22:26 Never mind. 17:22:28 OK. 17:22:41 ack fielding 17:22:48 -Yianni 17:23:00 My suggestion was to make more use of the chairs decisions (since we did not move and cannot move on some open issues with the long standing process). 17:23:24 marc has joined #dnt 17:23:30 royfielding: i think jmayer description of longstanding decision process is a non-decision process. Most w3c groups actually close issues whether they all agree or not, but they recognize they have discussed. 17:23:33 -1 17:23:34 jmayer proposal: contingency plan for end of July, and working without using chairs' reconciliation proposal 17:23:35 -1 17:23:38 call for +1/-1 17:23:39 -1 17:23:40 -1 17:23:40 -1 17:23:40 +1 to contingency planning 17:23:40 +1 17:23:43 -1 17:23:44 -1 17:23:44 -1 17:23:45 -1 17:23:47 -1 17:23:48 -1 17:23:49 -1 17:23:51 -1 17:23:53 -1 17:23:56 +1 17:23:58 -1 17:23:58 +1 17:23:58 -[Mozilla] 17:24:00 -1 17:24:08 +1 contigency planning 17:24:13 -1 17:24:17 -1 17:24:23 peterswire: more -1 than +1. 17:24:31 zakim, mute me 17:24:31 Rigo was already muted, rigo 17:24:32 5 +1s vs. 18 -1s 17:24:39 ... and articulated support for contingency planning 17:24:56 +q 17:25:09 peterswire: near end of time. have chair proposal. Considered alternatives, which did not get majority support. so no alternative received more support than w3c proposal. 17:25:09 q? 17:25:12 q+ 17:25:39 I think Roy and I are agreeing. Will send instructions, and we will have *much* more information a week from now. 17:25:41 peterswire, I think there was one more proposal that hasn't been discussed 17:25:47 can we get a precise written guide on way forward as agreed today? 17:25:48 We are missing it appears other NGO and also EU representatives. Can Peter address how that impacts his decision. 17:25:48 ....will have issues you want to raise that will be affirmatively raised in 1 week. Will see on public list. Will look at text. Clarify issues. 17:25:51 -q 17:26:00 +q 17:26:06 unmute me 17:26:11 zakim, unmute me 17:26:11 jchester2 should no longer be muted 17:26:15 ack jchester 17:27:08 jeffchester: i sort of want to underscore what john simpson just asked. want precise written guide on how to proceed in next week. decision must be reviewed by policy makers, public, justin not on call, rob had to leave. do need something in writing. 17:27:15 Thank you 17:27:17 ack Chris_IAB 17:27:24 peterswire: agree we will get something in writing: 17:27:35 zakim, mute me 17:27:35 jchester2 should now be muted 17:27:59 chris_iab: there was a hybrid proposal which was to move forward and re-evaluate if we don't get to consensus 17:28:15 peterswire: that's consistent with the idea of evaluating July 24. 17:28:47 q? 17:28:52 q? 17:28:58 peterswire: i hope we work well and effectively and can get to last call but recognize it's not inevitable. 17:29:03 q+ jmayer 17:29:04 -Fielding 17:29:10 ack jmayer 17:29:23 -waltmichel 17:29:36 jmayer: clarifying question. I though we just agreed on firm deadline. But now you said we will reconsider. 17:30:16 peterswire: i did not mean to change what i said. would take an affirmative decision of group to extend if we work diligently and don't get to last call. I don't support that. 17:30:18 -omer_tene 17:30:19 -Mike_Zaneis 17:30:21 johnsimpson has left #dnt 17:30:21 -[Microsoft] 17:30:22 - 17:30:23 -vinay 17:30:24 ...we will get you more information. 17:30:25 -Chris_Pedigo 17:30:26 - +1.202.331.aagg 17:30:26 -peterswire 17:30:27 thanks. 17:30:28 -dwainberg 17:30:28 -mecallahan? 17:30:29 -[DAA]? 17:30:29 -jchester2 17:30:30 thx 17:30:30 -kulick? 17:30:30 -Peder_Magee 17:30:32 -[FTC] 17:30:32 -Jonathan_Mayer 17:30:32 -moneill2 17:30:32 -efelten 17:30:32 -Rigo 17:30:33 -MIT531 17:30:33 - +1.650.595.aajj 17:30:33 -[Apple] 17:30:34 -cblouch 17:30:34 -adrianba 17:30:35 -Craig_Spiezle 17:30:35 - +1.678.492.aayy 17:30:35 -chapell 17:30:37 -johnsimpson 17:30:37 -Dan_Auerbach 17:30:38 -Chris_IAB 17:30:38 -ninjamarnau 17:30:40 -hwest 17:30:43 Zakim, list attendees 17:30:43 As of this point the attendees have been +1.703.265.aaaa, npdoty, cblouch, Fielding, Craig_Spiezle, +1.215.286.aabb, +1.703.993.aacc, +1.212.768.aadd, Aleecia, paulohm, 17:30:46 ... +1.202.347.aaee, +1.202.210.aaff, +1.202.331.aagg, susanisrael?, +1.202.787.aahh, jackhobaugh, Rigo, +1.646.827.aaii, Brooks, jchester2, waltmichel, marc_, dwainberg, vinay, 17:30:46 ... moneill2, Keith_Scarborough, dsinger, +1.650.595.aajj, +1.781.482.aakk, [DAA]?, +1.937.215.aall, +1.609.258.aamm, +1.408.836.aann, efelten, hefferjr, samsilberman, BerinSzoka, 17:30:50 ... +1.415.470.aaoo, Jonathan_Mayer, +1.240.994.aapp, Peder_Magee, WileyS, Yianni, +49.431.98.aaqq, ninjamarnau, rsherman, wseltzer, billscannell, +1.917.934.aarr, Chris_IAB, 17:30:50 ... +1.310.292.aass, [Microsoft], sidstamm, hwest, johnsimpson, [FTC], omer_tene, +31.65.141.aatt, rvaneijk, Chris_Pedigo, +1.202.639.aauu, peterswire, laurengelman, thomas, 17:30:51 rrsagent, please draft the minutes 17:30:51 I have made the request to generate http://www.w3.org/2013/06/19-dnt-minutes.html npdoty 17:30:54 ... adrianba, kulick?, mecallahan?, [IPcaller], +1.202.253.aavv, +1.604.639.aaww, schunter, tlr, +1.646.666.aaxx, Mike_Zaneis, chapell, Dan_Auerbach, +1.678.492.aayy, 17:30:54 ... +1.408.836.aazz 17:30:54 -npdoty 17:30:54 -laurengelman 17:30:54 -Keith_Scarborough 17:30:57 -jackhobaugh 17:30:59 - +1.917.934.aarr 17:31:00 -billscannell 17:31:14 -hefferjr 17:31:32 cblouch has left #dnt 17:32:09 -schunter 17:37:09 disconnecting the lone participant, WileyS, in T&S_Track(dnt)12:00PM 17:37:11 T&S_Track(dnt)12:00PM has ended 17:37:11 Attendees were +1.703.265.aaaa, npdoty, cblouch, Fielding, Craig_Spiezle, +1.215.286.aabb, +1.703.993.aacc, +1.212.768.aadd, Aleecia, paulohm, +1.202.347.aaee, +1.202.210.aaff, 17:37:12 ... +1.202.331.aagg, susanisrael?, +1.202.787.aahh, jackhobaugh, Rigo, +1.646.827.aaii, Brooks, jchester2, waltmichel, marc_, dwainberg, vinay, moneill2, Keith_Scarborough, 17:37:12 ... dsinger, +1.650.595.aajj, +1.781.482.aakk, [DAA]?, +1.937.215.aall, +1.609.258.aamm, +1.408.836.aann, efelten, hefferjr, samsilberman, BerinSzoka, +1.415.470.aaoo, 17:37:12 ... Jonathan_Mayer, +1.240.994.aapp, Peder_Magee, WileyS, Yianni, +49.431.98.aaqq, ninjamarnau, rsherman, wseltzer, billscannell, +1.917.934.aarr, Chris_IAB, +1.310.292.aass, 17:37:16 ... [Microsoft], sidstamm, hwest, johnsimpson, [FTC], omer_tene, +31.65.141.aatt, rvaneijk, Chris_Pedigo, +1.202.639.aauu, peterswire, laurengelman, thomas, adrianba, kulick?, 17:37:16 ... mecallahan?, [IPcaller], +1.202.253.aavv, +1.604.639.aaww, schunter, tlr, +1.646.666.aaxx, Mike_Zaneis, chapell, Dan_Auerbach, +1.678.492.aayy, +1.408.836.aazz 18:46:01 schunter has joined #dnt 19:43:25 npdoty has joined #dnt 20:00:35 Zakim has left #dnt 21:30:21 schunter has joined #dnt 21:33:26 npdoty has joined #dnt 22:41:55 npdoty has joined #dnt 22:48:00 npdoty_ has joined #dnt 23:45:00 schunter has joined #dnt