15:33:18 <RRSAgent> RRSAgent has joined #dnt
15:33:18 <RRSAgent> logging to http://www.w3.org/2012/08/29-dnt-irc
15:33:42 <Zakim> Zakim has joined #dnt
15:33:59 <aleecia> Zakim, this will be DNT
15:33:59 <Zakim> ok, aleecia; I see T&S_Track(dnt)12:00PM scheduled to start in 27 minutes
15:34:22 <aleecia> Chair: schunter 
15:34:54 <aleecia> Regrets+ jeffchester
15:35:16 <aleecia> RRSAgent, make logs public
15:35:51 <aleecia> Agenda?
15:36:29 <aleecia> Agenda+ Selection of scribe
15:38:00 <aleecia> Agenda+ review of overdue action items http://www.w3.org/2011/tracking-protection/track/actions/overdue?sort=owner
15:38:07 <tl> tl has joined #dnt
15:38:34 <aleecia> Agenda+ Any comments on published minutes 
15:38:55 <aleecia> Agenda+ quick check that callers are identified
15:43:02 <aleecia> http://www.w3.org/2011/tracking-protection/track/issues/138)
15:43:16 <aleecia> Agenda?
15:43:39 <aleecia> Thank you for dropping all of that, zakim
15:44:09 <npdoty> npdoty has joined #dnt
15:44:15 <aleecia> Agenda+ service provider flag, http://www.w3.org/2011/tracking-protection/track/issues/137
15:44:51 <aleecia> Agenda+ JScript DOM properties http://www.w3.org/2011/tracking-protection/track/issues/116
15:45:43 <aleecia> Agenda+ how are sub domains handled for site specific exceptions, http://www.w3.org/2011/tracking-protection/track/issues/112
15:47:24 <aleecia> Agenda+ how can providers without HTML real estate obtain exceptions? http://www.w3.org/2011/tracking-protection/track/issues/138
15:48:38 <aleecia> Agenda+ screen raised issues to decide which issues to open and what actions to assign http://www.w3.org/2011/tracking-protection/track/products/2
15:48:57 <aleecia> Agenda+ announce next meeting and adjourn
15:49:51 <aleecia> Nick, thanks for being available -- made it possible for me to avoid cutting it very close on the last flight out
15:50:05 <npdoty> Zakim, agenda?
15:50:05 <Zakim> I see 10 items remaining on the agenda:
15:50:07 <Zakim> 1. Selection of scribe [from aleecia]
15:50:07 <Zakim> 2. review of overdue action items http://www.w3.org/2011/tracking-protection/track/actions/overdue?sort=owner [from aleecia]
15:50:07 <Zakim> 3. Any comments on published minutes [from aleecia]
15:50:07 <Zakim> 4. quick check that callers are identified [from aleecia]
15:50:07 <Zakim> 5. service provider flag, http://www.w3.org/2011/tracking-protection/track/issues/137 [from aleecia]
15:50:09 <Zakim> 6. JScript DOM properties http://www.w3.org/2011/tracking-protection/track/issues/116 [from aleecia]
15:50:12 <Zakim> 7. how are sub domains handled for site specific exceptions, http://www.w3.org/2011/tracking-protection/track/issues/112 [from aleecia]
15:50:14 <Zakim> 8. how can providers without HTML real estate obtain exceptions? http://www.w3.org/2011/tracking-protection/track/issues/138 [from aleecia]
15:50:17 <Zakim> 9. screen raised issues to decide which issues to open and what actions to assign http://www.w3.org/2011/tracking-protection/track/products/2 [from aleecia]
15:50:18 <npdoty> Meeting: Tracking Protection Working Group teleconference
15:50:20 <Zakim> 10. announce next meeting and adjourn [from aleecia]
15:50:23 <npdoty> chair: schunter
15:50:55 <Zakim> T&S_Track(dnt)12:00PM has now started
15:51:04 <Zakim> +aleecia
15:52:08 <sidstamm> sidstamm has joined #dnt
15:53:00 <aleecia> Sid, could you do me a favor and say something?
15:53:15 <aleecia> My headphones seem not to work
15:53:46 <sidstamm> I'm not on the call yet, still dialing in
15:53:50 <sidstamm> one moment
15:53:55 <BrendanIAB> BrendanIAB has joined #dnt
15:54:26 <Zakim> +[Mozilla]
15:54:31 <aleecia> Oh yes
15:54:38 <aleecia> That does work, thanks!
15:54:47 <sidstamm> Zakim, Mozilla has sidstamm
15:54:48 <Zakim> +sidstamm; got it
15:54:57 <dwainberg> dwainberg has joined #dnt
15:55:02 <aleecia> Why I can't hear myself -- eh, not worth debugging
15:55:08 <dwainberg> dwainberg has joined #dnt
15:55:11 <sidstamm> Apologies to the room, I have to leave in 35 minutes
15:55:14 <Zakim> +matial
15:55:31 <Zakim> +npdoty
15:55:31 <aleecia> Zakim, who is on the call?
15:55:33 <Zakim> On the phone I see aleecia, [Mozilla], matial, npdoty
15:55:36 <Zakim> [Mozilla] has sidstamm
15:55:48 <aleecia> Indeed, Brendan -- yes
15:55:50 <Zakim> +[Mozilla.a]
15:56:04 <aleecia> Superpowers!
15:56:24 <sidstamm> what magic code did you dial to block your caller ID, BrendanIAB?
15:56:30 <aleecia> I'm on mute -- loud background env
15:57:27 <aleecia> Perhaps Matial once had the same Skype number
15:57:31 <aleecia> Nice
15:57:38 <npdoty> Zakim, matial is actually BrendanIAB 
15:57:38 <Zakim> I don't understand 'matial is actually BrendanIAB', npdoty
15:57:42 <Zakim> +dwainberg
15:57:44 <npdoty> Zakim, matial is really BrendanIAB 
15:57:44 <Zakim> +BrendanIAB; got it
15:57:56 <efelten> efelten has joined #dnt
15:58:11 <aleecia> :-)
15:58:35 <Zakim> + +1.813.358.aaaa
15:58:37 <npdoty> q?
15:58:38 <damiano> damiano has joined #dnt
15:58:39 <Joanne> Joanne has joined #DNT
15:58:41 <npdoty> q- matial
15:58:43 <tl> tl has joined #dnt
15:58:46 <aleecia> Thanks for helping us straighten it out, Brendan. 
15:58:50 <Zakim> +efelten
15:58:57 <jmayer> jmayer has joined #dnt
15:59:08 <BrendanIAB> no worries - is why I join early.
15:59:10 <Zakim> -[Mozilla]
15:59:18 <Zakim> - +1.813.358.aaaa
15:59:46 <npdoty> rrsagent, make logs public
15:59:49 <npdoty> rrsagent, pointer?
15:59:49 <RRSAgent> See http://www.w3.org/2012/08/29-dnt-irc#T15-59-49
15:59:54 <efelten> Zakim, efelten has PaulOhm
15:59:54 <Zakim> +PaulOhm; got it
15:59:55 <Zakim> +jmayer
16:00:05 <Zakim> +Joanne
16:00:13 <suegl> suegl has joined #dnt
16:00:17 <JC> JC has joined #DNT
16:01:03 <Zakim> +[Microsoft]
16:01:04 <eberkower> eberkower has joined #dnt
16:01:09 <Zakim> +[Microsoft.a]
16:01:13 <WileyS> WileyS has joined #DNT
16:01:21 <Zakim> +[Mozilla]
16:01:22 <sidstamm> Zakim, Mozilla has sidstamm
16:01:25 <Zakim> -[Microsoft.a]
16:01:27 <Zakim> +sidstamm; got it
16:01:32 <damiano> The conference code does not work 
16:01:39 <cblouch> cblouch has joined #dnt
16:01:42 <aleecia> Zakim, code?
16:01:42 <Zakim> the conference code is 87225 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), aleecia
16:01:43 <npdoty> Zakim, code?
16:01:45 <Zakim> +[Microsoft.a]
16:01:45 <Zakim> the conference code is 87225 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), npdoty
16:01:48 <damiano> i dialed *0, but it keeps saying to hold for an operator
16:01:54 <Zakim> -[Microsoft]
16:02:00 <Zakim> +eberkower
16:02:05 <aleecia> Please dial 87225
16:02:07 <dsinger> dsinger has joined #dnt
16:02:09 <Zakim> + +1.425.455.aabb
16:02:12 <damiano> that is the one i dialed
16:02:21 <Zakim> -[Microsoft.a]
16:02:24 <Zakim> +[Microsoft]
16:02:25 <ninjamarnau> ninjamarnau has joined #dnt
16:02:27 <damiano> ok
16:02:32 <Zakim> + +1.408.423.aacc
16:02:41 <Zakim> +jeffwilson
16:02:46 <dsinger> zakim, [apple] has dsinger
16:02:46 <Zakim> sorry, dsinger, I do not recognize a party named '[apple]'
16:02:51 <aleecia> Anyone else having trouble?
16:02:54 <Zakim> +schunter
16:03:02 <Zakim> - +1.408.423.aacc
16:03:14 <suegl> suegl has joined #dnt
16:03:14 <JC> JC is at 425
16:03:15 <Zakim> +[Apple]
16:03:20 <dsinger> zakim, [apple] has dsinger
16:03:20 <Zakim> +dsinger; got it
16:03:23 <Zakim> +ninjamarnau
16:03:25 <npdoty> Zakim, aabb is JC
16:03:25 <Zakim> +JC; got it
16:03:28 <aleecia> If not, you might just try calling again, damiano?
16:03:28 <Zakim> +WileyS
16:03:35 <mischat> mischat has joined #dnt
16:03:39 <aleecia> Agenda?
16:03:51 <AN> AN has joined #dnt
16:03:55 <hwest> hwest has joined #dnt
16:03:56 <Zakim> +[Microsoft.a]
16:03:58 <Zakim> -JC
16:03:59 <WileyS> Longer delay than normal on Zakim Phone System today - wait a good 30 seconds after you dial in to enter the code for this meeting.
16:04:00 <Zakim> +Matt_AppNexus
16:04:13 <suegl> zakim, [Microsoft.a] has suegl
16:04:13 <Zakim> +suegl; got it
16:04:23 <aleecia> Ok, thanks Shane -- so not just damiano 
16:04:24 <Zakim> +hwest
16:04:30 <damiano> no operator yet
16:04:41 <Zakim> +[IPcaller]
16:04:48 <damiano> keeps saying to hold for an operator
16:04:52 <aleecia> Next agenda
16:05:11 <npdoty> volunteers to scribe?
16:05:22 <jmayer> I am, but I'm going to be very active on this topic.
16:05:22 <Chapell> Chapell has joined #DNT
16:05:25 <Zakim> + +1.425.985.aadd
16:05:54 <Zakim> +??P49
16:06:01 <Craig> Craig has joined #dnt
16:06:01 <Zakim> + +1.813.358.aaee
16:06:31 <damiano> i'm on finally
16:06:32 <jmayer> I'll fill in for David, how about that.
16:06:54 <npdoty> scribe: dwainberg 
16:06:54 <Chapell> happy to split
16:07:01 <Chris_IAB> Chris_IAB has joined #dnt
16:07:10 <aleecia> Close agenda 1
16:07:10 <npdoty> and Chapell will take over when dwainberg lets him know
16:07:16 <Chris_IAB> just connected via my mobile (blocked number)
16:07:20 <npdoty> thx both
16:07:22 <vincent> vincent has joined #dnt
16:07:24 <samsilberman> samsilberman has joined #dnt
16:07:26 <Chapell> i'm on via skype
16:07:28 <Zakim> +KevinT
16:07:29 <aleecia> Next agendum
16:07:36 <adrianba_> adrianba_ has joined #dnt
16:07:41 <Zakim> +bryan
16:07:46 <Zakim> +[Microsoft.aa]
16:07:55 <adrianba_> zakim, [Microsoft.aa] is me
16:07:55 <Zakim> +adrianba_; got it
16:07:58 <tedleung> tedleung has joined #dnt
16:08:06 <KevinT> KevinT has joined #dnt
16:08:11 <dwainberg> overdue item 1: Roy is not present
16:08:11 <Zakim> +samsilberman
16:08:32 <dwainberg> ... (Matthias working through the list of overdue actions)
16:08:37 <schunter> http://www.w3.org/2011/tracking-protection/track/actions/212
16:08:52 <fielding> fielding has joined #dnt
16:08:56 <Zakim> +tedleung
16:08:57 <dwainberg> Action 212 assigned to Shane. Shane says he will get it done by next week.
16:08:57 <trackbot> Sorry, couldn't find user - 212
16:08:57 <Zakim> -tedleung
16:09:21 <Zakim> -bryan
16:09:28 <dwainberg> hwest: both of my action items are done
16:09:29 <Zakim> +tedleung
16:09:38 <pedermagee> pedermagee has joined #dnt
16:09:43 <aleecia> Heather, please update those to Pending review if you would, please
16:09:55 <fielding> I am in a meeting and unable to join the phone -- give me Qs via irc
16:10:03 <dwainberg> (Heather's items: 225 and 237?)
16:10:09 <Zakim> + +aaff
16:10:27 <npdoty> action-229?
16:10:27 <trackbot> Getting info on ACTION-229 failed - alert sysreq of a possible bug
16:10:41 <aleecia> So also pending review
16:10:42 <tl> +q
16:10:47 <dwainberg> 232: done
16:10:52 <dwainberg> posted to mailing list
16:10:55 <Zakim> +bryan
16:11:11 <aleecia> So noted
16:11:15 <dwainberg> 234: jon says no substantive change on permitted uses proposal
16:11:26 <npdoty> q+
16:11:37 <WileyS> Aleecia, does this mean Amsterdam is simply a repeat of Seattle?
16:11:44 <aleecia> No.
16:11:59 <dwainberg> 235: Nick says no written text to share yet.
16:12:01 <WileyS> How is it not if there are no "substantive changes"?
16:12:28 <dwainberg> Moving deadline to Tuesday for 235.
16:12:41 <WileyS> Aleecia, how is it not if there are no "substantive changes"?
16:12:45 <aleecia> We'll review the proposals and go through the decision process with a call for objections, just as we've done on the tri-part state
16:12:51 <jmayer> This should be no surprise - when we opened the ACTION, I noted the outcome was virtually certain to be no substantive changes.
16:12:59 <WileyS> Aleecia, we've already done that.
16:13:24 <WileyS> Aleecia, can you please explain how this process will be different than what occured in Seattle?
16:13:39 <npdoty> thx dsinger
16:13:41 <dwainberg> 239: schunter reviewed minutes, and sent a note. Qualifiers have been reintroduced to the draft.
16:13:43 <aleecia> This is the process of getting final text. Jonathan's saying his text is final.
16:13:55 <tl> WileyS: Perhaps we should discuss this out loud later on this call?
16:13:55 <dwainberg> dsinger: qualifiers do not currently match the compliance doc.
16:14:02 <aleecia> Nick is working on new text. You may or may not be too.
16:14:43 <WileyS> Aleecia, Jonathan's text was final in Seattle - again, not seeing the difference here and I'm understanding what you feel is different this time.
16:14:43 <aleecia> (I have a lot of background noise so I'm on mute if at all possible)
16:15:00 <WileyS> I'm "not" understanding...
16:15:02 <aleecia> His is not the only proposal
16:15:10 <dsinger> insert into 6.3.1 "Note: a site may remember that it has previously asked for, and been denied, an exception, if it wishes to avoid repeatedly asking the user for an exception."
16:15:23 <Zakim> + +1.303.661.aagg
16:15:32 <dwainberg> 240: dsinger will post proposed language today. (and see ^)
16:15:48 <Simon> Simon has joined #dnt
16:15:51 <WileyS> There were two key proposals - are you suggest we'll now revert from the work completed in Seattle to consider the proposals with smaller support again?  We did this in Seattle as well - which is why we focused on the two proposals.
16:16:07 <dwainberg> 241: npdoty will write up text if we don't get to it on the call today.
16:16:19 <Zakim> + +1.678.492.aahh
16:16:38 <dwainberg> 243: schunter closing the action.
16:17:00 <npdoty> q?
16:17:08 <dwainberg> 245: schunter: hasn't been done so leaving open.
16:17:19 <schunter> q?
16:17:24 <aleecia> Shane, I think you're missing state here. This will be faster by voice. My concern is that you're not the only one not following, so perhaps you and I could talk, and I could summarize to the list
16:17:26 <schunter> ack tl
16:17:40 <Zakim> -hwest
16:17:43 <WileyS> Aleecia - sounds good.
16:17:44 <hwest> CFell off
16:17:47 <Brooks> Brooks has joined #dnt
16:17:58 <dwainberg> tl: for headers action items, don't see any emails listed on the tracker. Anything on the list, or just added to the draft?
16:18:02 <aleecia> Tom -- it's in the draft
16:18:03 <schunter> q?
16:18:07 <schunter> ack npdoty
16:18:10 <hwest> tl, the changes are an option that we re-included in the draft, we haven't sent out the editor's draft yet
16:18:18 <aleecia> Close agendum 2
16:18:28 <WileyS> He's not on the call - just sent him an email and didn't get an OOO return - hope to hear from him today.
16:18:29 <Zakim> +hwest
16:18:38 <dwainberg> npdoty: wants to follow up on 229. If Chris isn't working on this, can we reassign.
16:18:43 <WileyS> Agreed
16:18:59 <dsinger> action: dsinger to ensure that the qualifiers reflect the permissions documented in the compliance document, due 10 october
16:18:59 <trackbot> Sorry, couldn't find user - dsinger
16:19:07 <dwainberg> schunter: should we set a deadline for the next call and reassign if he doesn't respond?
16:19:13 <tl> hwest: Glad to hear that I'm not starting to loose state =]
16:19:17 <dsinger> action: david singer to ensure that the qualifiers reflect the permissions documented in the compliance document, due 10 october
16:19:17 <trackbot> Sorry, ambiguous username (more than one match) - david
16:19:17 <trackbot> Try using a different identifier, such as family name or username (eg. dsinger2, dwainberg)
16:19:20 <dwainberg> npdoty: we said that last time; maybe give him a couple of days.
16:19:25 <dsinger> action: singer to ensure that the qualifiers reflect the permissions documented in the compliance document, due 10 october
16:19:25 <trackbot> Created ACTION-249 - Ensure that the qualifiers reflect the permissions documented in the compliance document, due 10 october [on David Singer - due 2012-09-05].
16:19:27 <aleecia> I'll ping him
16:19:28 <WileyS> Not sure I want to take this one - any other volunteers?
16:19:52 <aleecia> I'll ping
16:19:56 <aleecia> And cc you
16:20:03 <schunter> q?
16:20:04 <npdoty> thanks
16:20:08 <WileyS> Thank you Aleecia
16:20:08 <kj> kj has joined #dnt
16:20:10 <dwainberg> schunter: this concludes action item discussion.
16:20:21 <dwainberg> schunter: comments on minutes posted since last week?
16:20:38 <aleecia> Close agendum 3
16:20:44 <dwainberg> npdoty: minutes posted, but not cleaned up.
16:20:49 <schunter> q?
16:20:51 <tl> zakim, who is on the phone?
16:20:51 <Zakim> On the phone I see aleecia, BrendanIAB, npdoty, [Mozilla.a], dwainberg, efelten, jmayer, Joanne, [Mozilla], eberkower, [Microsoft], jeffwilson, schunter, [Apple], ninjamarnau,
16:20:54 <Zakim> ... WileyS, [Microsoft.a], Matt_AppNexus, [IPcaller], +1.425.985.aadd, ??P49, +1.813.358.aaee, KevinT, adrianba_, samsilberman, tedleung, +aaff, bryan, +1.303.661.aagg,
16:20:54 <Zakim> ... +1.678.492.aahh, hwest
16:20:54 <Zakim> [Apple] has dsinger
16:20:54 <Zakim> [Mozilla] has sidstamm
16:20:55 <Zakim> [Microsoft.a] has suegl
16:20:55 <dwainberg> (no comments on minutes)
16:20:56 <Zakim> efelten has PaulOhm
16:21:09 <Brooks> Brooks on 678 492
16:21:11 <Craig> question.  off subject but looking for speakers for Oct 3 in San Jose (Same time as meeting in NL)
16:21:11 <schunter> Zakim, who is on the phone
16:21:11 <Zakim> I don't understand 'who is on the phone', schunter
16:21:33 <damiano> damiano 813
16:21:43 <npdoty> Zakim, aaee is damiano
16:21:43 <Zakim> +damiano; got it
16:21:46 <tl> zakim, Mozilla.a has tl
16:21:46 <Zakim> +tl; got it
16:21:51 <npdoty> Zakim, add is Craig
16:21:51 <Zakim> sorry, npdoty, I do not recognize a party named 'add'
16:21:56 <npdoty> Zakim, aadd is Craig
16:21:56 <Zakim> +Craig; got it
16:22:07 <Chapell> chapell is skype
16:22:15 <Chris_IAB> not me
16:22:16 <Craig> Craig Spiezle - Online Trust Alliance on skype
16:22:17 <Chris_IAB> I'm on my cell
16:22:25 <Chris_IAB> blocked number
16:22:32 <npdoty> Zakim, ??P49 is probably Chris_IAB 
16:22:32 <Zakim> +Chris_IAB?; got it
16:22:52 <npdoty> Zakim, [IPcaller] is Chapell 
16:22:52 <Zakim> +Chapell; got it
16:22:53 <dsinger> zakim, who is making noise?
16:22:57 <npdoty> Zakim, aagg is simon
16:22:57 <Zakim> +simon; got it
16:23:03 <Zakim> dsinger, listening for 10 seconds I heard sound from the following: npdoty (59%), dwainberg (20%)
16:23:12 <tl> zakim, who is on the phone?
16:23:12 <Zakim> On the phone I see aleecia, BrendanIAB, npdoty, [Mozilla.a], dwainberg, efelten, jmayer, Joanne, [Mozilla], eberkower, [Microsoft], jeffwilson, schunter, [Apple], ninjamarnau,
16:23:15 <Zakim> ... WileyS, [Microsoft.a], Matt_AppNexus, Chapell, Craig, Chris_IAB?, damiano, KevinT, adrianba_, samsilberman, tedleung, +aaff, bryan, simon, +1.678.492.aahh, hwest
16:23:15 <Zakim> [Apple] has dsinger
16:23:15 <Zakim> [Mozilla] has sidstamm
16:23:15 <Zakim> [Microsoft.a] has suegl
16:23:15 <Zakim> [Mozilla.a] has tl
16:23:17 <Zakim> efelten has PaulOhm
16:23:21 <npdoty> Zakim, aahh is Brooks 
16:23:21 <Zakim> +Brooks; got it
16:23:25 <aleecia> Close agendum 5
16:23:30 <aleecia> Oops
16:23:41 <aleecia> Close agendum 4
16:24:13 <WileyS> Nick - you're a "hard typer" be sure to hand exercise daily to stave off carpal tunnel synd  :-)
16:24:21 <npdoty> Topic: Service Providers
16:24:22 <dsinger> q+
16:24:26 <jmayer> +w
16:24:33 <jmayer> +q
16:24:33 <dwainberg> schunter: issue-137. Whether there should be an indication of a service provider to a 1st party.
16:24:37 <schunter> 1 - A user with DNT;1 visits a site
16:24:37 <schunter> 2 - The site sends back its own content (e.g., usually marked with Tk:1 header that says that the policies for 1st parties have been implemented)
16:24:37 <schunter> 3 - Embedded content from third parties is marked with "3" (following 3rd party policies; no concern there)
16:24:37 <schunter> 4 - Some embedded content that is marked with "1" but is coming from a different domain 
16:25:20 <WileyS> Jonathan - that was interesting that '+w" shows when I arrived on the call - that's a new Zakim feature I wasn't aware of.
16:25:31 <dsinger> +d
16:25:50 <WileyS> David - LOL, only works for me?
16:25:51 <jmayer> Neither was I, typo FTW.
16:26:07 <jmayer> +jmayer
16:26:35 <dwainberg> schunter: current spec solves this problem by saying if a site is operating on a different domain as first party, include domain in the sits attribute.
16:26:42 <WileyS> +dsinger
16:26:43 <npdoty> this is the Yahoo/yimg.com case? a different domain but entirely part of the same party
16:26:57 <WileyS> Sorry David - Zakim just isn't into you.  :-)
16:27:04 <tl> +q
16:27:05 <jmayer> (I don't think we have consensus that a TPE status means "is intended for [X] party use" vs. "complies with [X] part of the Compliance spec.")
16:27:06 <dwainberg> ... two questions: 1. is this a problem we agree needs to be solved; 2. is this a solution.
16:27:12 <schunter> q?
16:27:19 <jmayer> Heh, Apple - secretive as always.
16:27:19 <schunter> ack dsinger
16:27:21 <dwainberg> ... start w/ clarifications of the scenario.
16:27:48 <dsinger> So, the TPE now has qualifiers that match the permissions, and we expect a permission for service provision; this makes it clear that only agents that are end-points of HTTP are involved in this (not e.g. hosting or firewall providers); the only question I have is whether it's mandatory to set it
16:28:14 <schunter> Clarification: We only talk about service providers that are visible http endpoints
16:28:25 <dwainberg> dsinger: we've had a defined exception for service providers, so we've mostly dealt with this question, so question remaining is are you obliged to indicate you are a service provider?
16:28:49 <schunter> q?
16:28:53 <npdoty> we were adding back the qualifiers for "permitted uses" which I don't think includes service providers, that's defined in a different section of the Compliance doc
16:28:55 <schunter> ack jmayer
16:29:18 <dwainberg> jmayer: 2 framing point: whether something is a service provider or not is not the only ambiguity
16:29:32 <dwainberg> ... (sent an email to the list a while back)
16:29:40 <npdoty> http://lists.w3.org/Archives/Public/public-tracking/2012Aug/0197.html
16:29:41 <dwainberg> ... so this solves a lot but there may be other issues.
16:30:05 <dwainberg> ... 2. I don't we're agreed that if you're not clearly visible over http you don't have to do anything, but that's another issue.
16:30:36 <Zakim> -[Mozilla]
16:30:40 <dwainberg> schunter: if I understood correctly you're talking about service providers that exist but are not part of the http transaction.
16:30:53 <jmayer> yep
16:30:55 <schunter> q?
16:30:59 <schunter> ack tl
16:31:00 <dwainberg> ... is this right?
16:31:55 <dwainberg> tl: confused about the current state here. Roy said he removed the qualifier and added requirement to .... want to confirm I have the right state here.
16:32:20 <schunter> Unclear: a) Is the first party required to point to service providers using the same-party attribute
16:32:34 <dwainberg> ... if a service provider is acting on behalf of 1st party, it can send the 1st party response 
16:32:47 <dwainberg> ... is there a different field the first party should identify them as
16:32:56 <dwainberg> ... is the first party obliged to identify service providers?
16:33:14 <dwainberg> q+
16:33:38 <npdoty> but you're identifying an uncertainty/ambiguity, right, tl?
16:33:42 <dwainberg> tl: was asking about the state of the document.
16:33:50 <dwainberg> schunter: it's probably not clear.
16:33:51 <aleecia> Roy might be able to respond if you type into IRC
16:34:03 <dsinger> q+
16:34:12 <fielding> it's finished ;-)
16:34:31 <npdoty> fielding, tl's question, as I understand it, is the following:
16:34:32 <schunter> q?
16:34:54 <npdoty> does a user determine service provider status by following the policy link from the service-provider's domain?
16:35:26 <schunter> An optional member named same-party may be             provided with an array value containing a list of domain names             that the origin server claims are the same party, to the extent             they are referenced by the designated resource, since all data             collected via those references share the same data controller.           
16:35:29 <npdoty> or is the service provider listed in the `same-party` or some other field in the first party's tracking status resource?
16:35:55 <dwainberg> tl: right now there's no sp qualifier in the doc. so right now we don't have any 3rd party signal. 
16:36:05 <fielding> same-party is optional -- think of it as a recommended whitelist
16:36:14 <dwainberg> dsinger: assuming the compliance doc ends up with a permission for service provider there will be a qualifier to match.
16:36:17 <npdoty> dsinger, I'm not convinced that's what fielding has intended
16:36:31 <fielding> the policy URI points to the first-party
16:36:40 <npdoty> fielding, are we expecting to add a service provider to the list of tracking status qualifier values?
16:36:41 <schunter> ?roy?: Will services providers be listed as same-party?
16:36:50 <dwainberg> tl: so now if a website uses a cdn, how does the client know whether the cdn is operated on behalf of or otherwise.
16:36:53 <fielding> … or, if no policy, then the domain is owned by first-party
16:37:07 <dwainberg> dsinger: we don't currently have a way of indicating I'm acting as a service provider for whom.
16:37:08 <adrianba> q+
16:37:25 <dsinger> q-
16:37:31 <dwainberg> tl: Roy thought he'd solved it, but it sounds to me like this issue is not closed.
16:37:56 <dwainberg> schunter: take a step back and quickly summarize what we want this feature to do.
16:38:16 <npdoty> fielding, `policy` is an optional field -- does not having a policy field imply something specific about your service-provider status?
16:38:20 <dwainberg> ... I tried by email to validate what we want it to do and then we need to see if it does it.
16:38:27 <fielding> we don't need a way to indicate that "I am a service provider" -- the domains already exist for that purpose
16:38:53 <tl> fielding: When I visit example.com and see resources from examplecdn.net, how do I know whether examplecdn.net is actually operated by Example Inc, or by CDNInc on Example's behalf?
16:38:53 <dwainberg> ... service providers following the first party rule; we need a mutual pointer for both 1st and 3rd party to indicate relationship.
16:39:08 <npdoty> fielding, but sometimes a different domain isn't a service provider but is part of the same party (like yimg.com)
16:39:09 <fielding> your service provider status is irrelevant -- what matters is who is a data controller
16:39:37 <tl> fielding: Again, that doesn't satisfy the use case Ed provided.
16:39:48 <dwainberg> dsinger: I'd like to have a list of questions this and the tracking status resource are trying to answer.
16:39:57 <tl> +q
16:40:02 <fielding> tl, yes it does.  If you disagree, write the case on the mailing list.
16:40:02 <dwainberg> q-
16:40:05 <schunter> q?
16:40:11 <schunter> ack adrianba
16:41:00 <dwainberg> adrianba: question of whether you know whether the CDN operates as service provider or on its own. If there is a service provider status qualifier then the provider would say
16:41:28 <npdoty> adrianba, but fielding thinks you shouldn't ever need to indicate that you're a service provider
16:41:34 <dwainberg> ... I'm a service provider and I'm acting as first party, so I don't think we need a way to indicate which party, but we may need a way for a service provider to a 3rd party.
16:41:43 <jmayer> Worst case, it's a bit redundant.  There can be ambiguities.  Example: Multiple first parties.
16:41:44 <schunter> ack tl
16:42:08 <dsinger> yes, Adrian, the question is whether that presumption -- that the current first party agrees that foo.com is their service provider -- is OK, or whether the link needs to be confirmed one way or another
16:42:32 <dwainberg> tl: having trouble understanding the process we're using. we have requirements. In Seattle we agreed on a structure that satisfied my requirements, and Roy could live with, but that's not what we're doing.
16:42:58 <adrianba> dsinger, isn't that a problem of any site claiming to be a particular party?
16:42:59 <dwainberg> tl: I don't want to have to keep explaining myself when we already reached consensus on a protocol stack that's just not being copied into the document.
16:43:18 <dwainberg> npdoty: to clarify: do you think we had an agreement in Seattle that satisfied the concerns?
16:43:48 <dwainberg> tl: I recall clearly standing at a whiteboard with Roy standing next to me, making mods to a series of letters related to a pile of things that should be included.
16:44:06 <dwainberg> ... I recall that we had reached a configuration that Roy said had met his requirements.
16:44:12 <fielding> no
16:44:29 <dwainberg> tl: we definitely reached consensus on a very particular point.
16:44:47 <dwainberg> schunter: I read the minutes and I didn't find this piece. Either we didn't document it or we didn't reach this agreement.
16:45:07 <dwainberg> ... there's a clear statement we agreed on the basic headers.
16:45:10 <fielding> I said I would write a draft.  I did that.  We did not have consensus. I have repeated that over and over again.
16:45:28 <dwainberg> ... if we had agreements that are somewhere documented but are not in the document it's not intentional.
16:45:41 <dwainberg> ... we've had discussion and we're now trying to put it in.
16:45:57 <dwainberg> ... it's our job to work this text until we reach consensus on the text.
16:46:12 <dwainberg> tl: seems like we've lost the work. perhaps we need to do it again.
16:46:31 <fielding> I am still waiting for ANY use case to be documented that calls for what TL is requesting.  As I said I would, in Seattle.
16:46:40 <fielding> and in DC
16:46:45 <dwainberg> schunter: fine with me. small group can make a proposal to the larger group.
16:46:46 <tl> fielding: This is still Ed's example.
16:47:01 <fielding> Ed has not written his example, so I don't know.
16:47:21 <dsinger> to adrian: the concern is that some site gets pulled in, and it in turn has a service provider; the service provider says it has status first-party/service-provider but it's not servicing the actual first party, and we can't tell from the outside, since the 'who' is not identified at either end
16:47:22 <dwainberg> tl: I suspect that might work, but the communication difficulties we have are making that difficult.
16:48:32 <dsinger> to Tom: do you have the ability to suggest specific edits? that might be the best way ahead?
16:48:53 <dwainberg> dsinger: cal tl propose specific text edits that are needed. Or I can help find stuff that got lost from the draft.
16:49:53 <aleecia> You'll need to type in IRC for Roy
16:49:54 <jmayer> +q
16:50:00 <schunter> q?
16:50:03 <tl> 1030PST
16:50:13 <Zakim> -simon
16:50:18 <dwainberg> schunter: so, to move forward, we'll schedule time for fielding, tl, dsinger to get together to discuss. item remains open until then.
16:50:33 <tl> Roy, can you spend half and hour re-doing this work at 1030PST next Wednesday?
16:50:34 <dwainberg> jmayer: different actions a site might be up to that we need proposals on.
16:50:45 <fielding> Adobe objects to the service provider description unless it is backed by a use case that demonstrates the need from a privacy perspective.  It will not go in the editor's draft until that justification is made because Adobe objects.  The WG can make a formal decision to override the editor's decision.
16:50:47 <dwainberg> ... I was hoping we'd be able to close the of the service provider flag.
16:51:03 <dwainberg> Alan, can you take over scribing?
16:51:07 <tl> +q
16:51:14 <tl> ack jmayer
16:51:18 <npdoty> scribenick: Chapell 
16:51:20 <dwainberg> jmayer: it's clear where Roy's coming from on this.
16:51:32 <Chapell> yes
16:51:34 <dwainberg> ... I'm wondering if anyone shares Roy's perspective.
16:51:37 <aleecia> Ack tl
16:51:49 <dwainberg> q+
16:51:51 <Chapell> tl: we have an impasse 
16:51:54 <jmayer> Let me be more concrete: straw poll?
16:52:13 <Chapell> .... need to have a call for objections (unless roy is only person who olds that opinion)
16:52:17 <WileyS> I see issues in either direction
16:52:35 <aleecia> And Jonathan's suggestion for a straw poll sounds like a good one
16:52:43 <npdoty> q?
16:52:47 <Chapell> jmayer: wants to gauge groups pulse on the issue
16:52:48 <adrianba> dsinger, that's always a problem for a service provider or a resource from a domain that's a first party - it needs to indicate whether it thinks it is behaving as a first party (and as the spec says it can only declare what it thinks is the case)
16:52:53 <WileyS> From a privacy policy perspective, companies don't need to reveal their Service Providers (vendors) - so why should DNT be different?
16:53:01 <dsinger> Roy: I think the case is of a site that has a *distinct site name* that is not apparently part of the first party, that IS is an end-point of the HTTP transactions (not a hosting, firewall, or other intermediary), and that claims first-party tracking status: the UA needs to know (a) that it's claiming that because it is a service provider and (b) that it's providing service for someone with actual 1st party status.
16:53:22 <Chapell> mattias: the discussion re: SP is "should it be mandatory or not"
16:53:39 <dsinger> Otherwise, the UA may well identify it as 'acting out of status' and flag it to the user, etc.
16:53:49 <Chapell> tl: having it be optional is not acceptable
16:54:04 <Chapell> tl: sp must identify itself as a sp on behalf of a given first party
16:54:13 <fielding> dsinger, already solved that use case
16:54:28 <WileyS> This will allow anyone to decode any and all service providers a company has hired to work on their behalf - will be a market changing event if this goes through.
16:54:30 <Chapell> .... use case: user must be able to distinguish
16:54:31 <aleecia> Privacy policies do not seem like a bar we should lower ourselves to... Regardless of which way this goes, I'm not seeing privpols as useful framing
16:54:35 <npdoty> q?
16:54:45 <dsinger> Roy, can you point at what in the current draft covers that?
16:54:49 <dsinger> (we can't find it)
16:55:01 <schunter> q?
16:55:09 <WileyS> Aleecia, disagree strongly - privacy policies get a bad rap but are this the leading vehicle for consumer communication on these topics.
16:55:11 <jmayer> Let's start with service providers that are semi-visible over HTTP, e.g. CNAMEd in.
16:55:12 <Chapell> dsinger: says roy's text covers TL's use case
16:55:21 <jmayer> Backend service providers are a different issue.
16:55:22 <fielding> requirements must be acceptable to those who are expected to implement them
16:55:35 <WileyS> are "still" the leading vehicle...
16:56:04 <npdoty> q?
16:56:17 <Chapell> tl: if not going to straw poll, we add this to list of things we call for objections
16:56:17 <bryan> bryan has joined #dnt
16:56:18 <fielding> dsinger, service providers must always point to the first party, either via policy URI or the domain ownership.
16:56:18 <schunter> ack dwainberg
16:56:39 <Chapell> dwainberg: lots of ambiguity here
16:56:46 <WileyS> From a regulatory perspective, if a Service Provider falsely states its acting as a 1st party - when its not, you have all the evidence you need to take them to the cleaners.  I'm not sure what advocates are trying to gain here in forcing SP visibility?
16:56:47 <Chapell> .... hard to object or not without a concrete proposal
16:56:47 <jmayer> +q
16:56:51 <Chapell> .... need more info
16:57:03 <dsinger> to Roy: what is the nature of the pointer?
16:57:34 <Chapell> tl: there doesn't appear to be consensus, if more work is needed to clarify, that's ok
16:57:37 <fielding> a URI or a domain
16:57:40 <jmayer> I think we can get agreement on a minimum use case.
16:58:18 <jmayer> Example: Does Google Analytics need to set a service provider flag?
16:58:21 <jmayer> Yes or no?
16:58:34 <Chapell> mattias: we should understand which use cases have a solution and which do not
16:58:48 <fielding> Google analytics does not qualify as a service provider -- they are a third party
16:58:50 <Chapell> .... so we should go forward with a discussion to gain clarification 
16:59:18 <Chapell> .... or we risk throwing out much of what we've agreed upon
16:59:33 <Chapell> tl: suggests a 30 min call next week, pending roy's avail
16:59:47 <fielding> We have a mailing list for detailed technical discussions.  Please start using it for something other than hot air.
16:59:59 <tl> Roy: are you available for a 30min call at 1030PST next week discussing this issue synchronously?
17:00:06 <schunter> q?
17:00:12 <schunter> ack jmayer
17:00:48 <Chapell> matthias: proposes meeting with roy, tl and dsinger 
17:01:19 <fielding> no, put it on the mailing list -- I am tired of these private conversations that just waste our time.
17:01:42 <npdoty> if the group can't find a common resolution, then it can come back with multiple conflicting texts that we have to choose between
17:01:50 <Chapell> TL: given the back and forth last time and the noisy nature of the mailing list, this may not be productive using email
17:02:10 <Chapell> Matthias: first step: talking... 
17:02:25 <Chapell> .... next step: counter proposals
17:02:26 <npdoty> schunter: I believe talking in a small group first is the best way forward
17:02:39 <schunter> q?
17:02:47 <aleecia> From memory, Roy is not available by phone this week
17:03:12 <Chapell> schunter: move to issue 112
17:03:15 <aleecia> Which is why next week is suggested rather than, say, tomorrow
17:03:21 <aleecia> Agenda?
17:03:23 <dsinger> issue-112?
17:03:23 <trackbot> ISSUE-112 -- How are sub-domains handled for site-specific exceptions? -- open
17:03:23 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/112
17:03:25 <npdoty> I think schunter is taking responsibility for finding the process way forward
17:03:26 <schunter> q?
17:03:38 <tl> dsinger: If Roy isn't interested, perhaps you and I could chat, so that we can pin down the use case and the requirements that fall out it?
17:03:52 <WileyS> I sent a fairly long email on this topic - suggesting we'll need wild cards.
17:03:57 <aleecia> Zakim, take up agendum 7
17:03:57 <Zakim> agendum 7. "how are sub domains handled for site specific exceptions, http://www.w3.org/2011/tracking-protection/track/issues/112" taken up [from aleecia]
17:04:23 <Chapell> dsinger: the tech issue is that if we allow paramaters to include wildcards, then we have issues in allowing exception
17:04:29 <adrianba> q+
17:04:33 <Chapell> ..... much more complex.
17:04:36 <WileyS> We shouldn't over engineer for bad guys
17:04:42 <WileyS> We do need this
17:04:52 <Chapell> .... working with use cases - call out to advertising industry folks to specify use cases
17:04:54 <WileyS> DSinger, we've gone through this deeply in the email list
17:05:17 <Chapell> ...... exceptions for sub-domains are easier to handle
17:05:18 <dwainberg> q+
17:05:25 <schunter> ?Tom:? could you re-post pointers to the use cases that you want satisfied? Also please point out if there is documented consensus in the minutes that is not (or wrongly) reflected in the TPE draft.
17:05:33 <Chapell> .... for site exceptions do we need sub-domain trees
17:05:42 <schunter> q?
17:05:50 <schunter> ack adrianba
17:06:19 <Zakim> +npdoty.a
17:06:26 <Chapell> adrian: position from bellevue - we don't have to distinguish between multiple subdomains
17:06:41 <schunter> q?
17:06:49 <schunter> ack dwainberg
17:06:59 <npdoty> adrianba: try without, and we can add it later, but if we put it in now we can never take it out
17:07:15 <dsinger> 2 questions: (a) for site exceptions, do we need to be able to ask for *.x.com? (b) for web-wide, does x.com need to be able to ask for *.x.com as well?  The second is easy, teh first pulls in the whole public suffix question.
17:07:17 <Chapell> dwainberg: important functionality that is used by many companies
17:07:24 <Chapell> ..... creating a burden on companies and users
17:07:38 <adrianba> for example *.co.com is allowed and *.co.uk is not allowed
17:07:49 <Chapell> ..... in browsers, the code is already built and can be repurposed
17:07:56 <npdoty> not sure which part we're talking about requires industry re-engineering?
17:08:07 <Chapell> .... other than the complexity of dealing with public suffix issue, are there other objections?
17:08:08 <schunter> q?
17:08:13 <npdoty> q+
17:08:17 <dsinger> So, the big question is for those in the industry;  how complex (and particularly, maybe not fully enumerable) are the sub-domain usages in the industry?
17:08:18 <schunter> ack npdoty
17:08:34 <Chapell> npdoy: need to be specific about what we're talking about
17:08:40 <Brooks> to clarify when we say "public suffix" we are talking about new TLDs right?
17:08:41 <Chapell> .... most recent response on mailing list is nick's
17:09:03 <Zakim> + +44.186.573.aaii
17:09:05 <WileyS> Yahoo! has HUNDREDS of sub-domains (news.y.c, sports.y.c, my.y.c, maps.y.c, etc.)
17:09:25 <Chapell> ....  one issue is that it changes the breadth of the request in a way that the user may not want
17:09:41 <Chapell> ... so we're left with creating a complications for users
17:09:45 <Craig> agree.  complexitiy of mtuiple domains of the same 1P.  Subdomains can be used for content and image serving as well as other wholly owned subsidaries (WSJ & Dow Jones)
17:09:58 <schunter> q?
17:10:25 <Chapell> schunter: so how do we make progress here?
17:10:26 <WileyS> Craig - what are you agreeing to?  Support or do not support wild cards (*.y.c) for exceptions?
17:11:03 <Zakim> +dwainberg.a
17:11:18 <Chapell> dsinger: is it possible for the first party to enumerate all of the sub domains for each third party?
17:11:29 <WileyS> Yes - many ad networks use sub-domains to split load (www1.ad.net, www2.ad.net, etc.)
17:12:27 <dwainberg> yes
17:13:19 <Chapell> npdoty: 1st issue: expanding 1st party exeptions or 3rd party exceptions?
17:13:52 <dsinger> but the parts of the 1st party can and will say "I operate under first party rules, I don't need no exception"
17:14:05 <mischat_> mischat_ has joined #dnt
17:14:13 <npdoty> 1) (as dsinger just described) a first party wants to ask for a *.ad.net as it's asking for a site-wide exception, but can't just use "*"
17:14:13 <Chapell> schunter: lets focus on 3rd party case
17:14:13 <dwainberg> right, dsinger
17:14:35 <BrendanIAB> q+
17:14:53 <npdoty> 2) a first party wants to ask for a broader set of first parties on which the site-wide exception (to its third parties) should apply
17:15:40 <Zakim> -Chris_IAB?
17:15:48 <npdoty> and then 3) (Vinay's case) a Web-wide exception to apply to other subdomains of mine that will be 3rd parties on other parts of the Web
17:16:12 <schunter> q?
17:16:31 <Chapell> dwainberg: the list is either too long, or unknown to the first party
17:16:40 <Chapell> dpdoty: but you can use the wildcard?
17:16:47 <Zakim> +??P28
17:16:50 <npdoty> s/dpdoty/npdoty/
17:16:54 <aleecia> Ack BrendanIAB 
17:17:19 <tl> +q
17:17:49 <Zakim> -KevinT
17:17:50 <Chapell> brendanIAB: the pub has a very common use case... i may trust my initial first parties, but don't want to open the door to another set of third parties that the pub doesn't know
17:17:56 <dsinger> I think for site-exceptions, the case is that you do NOT want to ask for "*" (all third parties), but you also CANNOT enumerate all the specific third party sites you DO need (e.g. the list is too long, or you simply do not know all the X's for [X].ad.com).  In that case you want to ask for *.ad.com, and today you can't
17:18:03 <npdoty> the concern we heard a few months ago was the exact opposite :)
17:18:41 <dwainberg> q+
17:19:06 <npdoty> to clarify, BrendanIAB wants to have the ability to ask for an exception just for the first set of third parties and not for any re-directions (which isn't necessarily trusted)
17:19:22 <npdoty> , right?
17:19:24 <Chapell> dsinger: if a pub id delegating to subdelagators, then they need a site wide exception
17:19:57 <Chapell> dwainberg: what do we mean by delegate? does that then mean that a first party has a relatonship with ad.net who then offers the impression on an exchange...
17:19:58 <BrendanIAB> Not necessarily *want*, but calling it out as a scenario.
17:20:11 <Chapell> .... does that exception follow through the ad call to the exchange?
17:20:24 <Chapell> dsinger: not unless the publisher has asked for a site wide exception
17:20:26 <npdoty> BrendanIAB, okay, but if you don't want it and nobody else wants it, then it'll be easy for us to drop it, rather than engineering for it
17:21:30 <dsinger> notes that the question of whether DNT headers are inherited by re-directs is a DIFFERENT issue (and we previously tentatively decided 'no')
17:21:37 <Chapell> schunter: under this scenario, all exceptions are explicitly listed, and ONLY those third parties will get the exception (unless the site asks for site wide exception)
17:21:51 <npdoty> right, correct description of current state
17:21:53 <Chapell> .... whomever is on the list gets dnt 0   
17:21:56 <BrendanIAB> More specifically, it's a technical situation that I recognize, but will need to do some research and education to understand whether it's better than other options.
17:22:00 <Chapell> .... all else get dnt 1
17:22:43 <Chapell> .... if you want to specify a range of 3rd party domains that should be excepted, are wild cards ok?
17:22:55 <Chapell> .... or must each 3rd party be specifically listed?
17:23:21 <npdoty> most ad exchanges would use the * site-wide exception, because they don't know the list of third parties for which they want to request an exception
17:23:29 <Chapell> .... lets focus on the case where the 1st party has a list of domains --- shoudl the 1st party be able to shorten the list of domains by using a wild card?
17:23:40 <Chapell> dsinger: we'd prefer NOT to allow wildcards
17:23:41 <Zakim> -[Microsoft.a]
17:23:48 <Chapell> .... as it complicates things
17:23:48 <dwainberg> q+
17:23:51 <WileyS> DSinger - what were you assigning to me?  :-)
17:23:52 <aleecia> Reminder: call for objections on mandatory equal difficulty for tri-part in UAs closes today 
17:23:52 <schunter> q?
17:24:01 <Chapell> npdoty: to add an action item for BrendanIAB
17:24:23 <dwainberg> q-
17:24:26 <schunter> ack tl
17:24:28 <Zakim> -hwest
17:24:35 <schunter> q?
17:24:37 <ninjamarnau> we already discussed this issue extensively in DC. 
17:24:38 <WileyS> Aleecia, where did the pool end out?  Or is that what you're referring to with the "call for objections"?
17:24:44 <npdoty> action: BrendanIAB to research breadth of use cases for *.thirdparty.net in asking for site-wide exceptions without a wildcard
17:24:49 <npdoty> q+
17:24:57 <WileyS> Aleecia - can't type today - "poll"
17:25:03 <aleecia> I'm not sure what you're asking, but today is the final day for responses
17:25:06 <WileyS> The betting pool is another matter :-)
17:25:09 <Chapell> @WileyS -- it is summer, after all
17:25:11 <aleecia> Heh
17:25:14 <WileyS> Aleecia - thank you
17:25:23 <aleecia> You can view them all
17:25:37 <Chapell> Schunter: current spec, simple solution that does not include a wild card
17:25:40 <WileyS> Aleecia, do you have the link handy?
17:25:51 <Chapell> ..... he will call for use cases to justity the wild card solution
17:25:53 <npdoty> https://www.w3.org/2002/09/wbs/49311/tripart/
17:26:10 <Zakim> -samsilberman
17:26:11 <aleecia> Matthias & I will start to discuss on Friday (thanks, Nick!)
17:26:15 <npdoty> q-
17:26:15 <Chapell> Dwainberg: there are already use cases
17:26:24 <trackbot> trackbot has joined #dnt
17:26:35 <Chapell> dsinger: brendan is taking the lead
17:26:49 <aleecia> We don't have a time estimate yet, but should have more clarity after we compare notes and start to talk it through
17:27:15 <WileyS> Brenden - Yahoo! use case - Yahoo! applies DNT to 1st party activities as well as 3rd party.  So we'll need to request exceptions for our sub-domains which number in the 100s.  A wild-card will be needed for our situation.  For everyone else - let's not build a standard that attempts to twart bad buys by throwing the good guys under the bus.
17:27:15 <schunter> q?
17:27:19 <npdoty> q+ to note reminder
17:27:27 <schunter> ack npdoty
17:27:27 <Zakim> npdoty, you wanted to note reminder
17:27:56 <BrendanIAB> Thanks WileyS
17:28:25 <Zakim> -bryan
17:28:27 <Zakim> -Craig
17:28:28 <aleecia> Thanks, Nick
17:28:30 <npdoty> WileyS, it sounds like you're describing increasing the breadth of first party, not third party, is that right?
17:28:30 <Zakim> -Joanne
17:28:32 <Zakim> -damiano
17:28:32 <Zakim> - +44.186.573.aaii
17:28:34 <Zakim> -adrianba_
17:28:34 <Zakim> -[Apple]
17:28:34 <Zakim> -tedleung
17:28:35 <Zakim> -ninjamarnau
17:28:36 <Zakim> -jmayer
17:28:37 <Zakim> -schunter
17:28:38 <tedleung> tedleung has left #dnt
17:28:39 <Zakim> -BrendanIAB
17:28:42 <Zakim> -Brooks
17:28:44 <Zakim> -Matt_AppNexus
17:28:46 <Zakim> -[Microsoft]
17:28:49 <Zakim> -aleecia
17:28:49 <Zakim> - +aaff
17:28:51 <Zakim> -Chapell
17:28:54 <Zakim> -npdoty.a
17:28:55 <Zakim> -dwainberg.a
17:28:57 <Zakim> -WileyS
17:28:59 <npdoty> Zakim, list attendees
17:28:59 <Zakim> As of this point the attendees have been aleecia, sidstamm, npdoty, dwainberg, BrendanIAB, +1.813.358.aaaa, PaulOhm, jmayer, Joanne, [Microsoft], eberkower, +1.425.455.aabb,
17:29:03 <Zakim> ... +1.408.423.aacc, jeffwilson, schunter, dsinger, ninjamarnau, JC, WileyS, Matt_AppNexus, suegl, hwest, +1.425.985.aadd, +1.813.358.aaee, KevinT, bryan, adrianba_, samsilberman,
17:29:06 <Zakim> ... tedleung, +aaff, +1.303.661.aagg, +1.678.492.aahh, damiano, tl, Craig, Chris_IAB?, Chapell, simon, Brooks, +44.186.573.aaii
17:29:32 <npdoty> rrsagent, draft minutes
17:29:32 <RRSAgent> I have made the request to generate http://www.w3.org/2012/08/29-dnt-minutes.html npdoty
17:29:38 <Zakim> -??P28
17:29:42 <npdoty> Zakim, bye
17:29:42 <Zakim> leaving.  As of this point the attendees were aleecia, sidstamm, npdoty, dwainberg, BrendanIAB, +1.813.358.aaaa, PaulOhm, jmayer, Joanne, [Microsoft], eberkower, +1.425.455.aabb,
17:29:42 <Zakim> Zakim has left #dnt
17:29:57 <hwest> hwest has left #dnt
17:33:51 <damiano> damiano has joined #dnt
17:37:31 <brett> brett has joined #dnt
17:37:45 <brett> Don't mind me folks, just doing some sysadminning.
17:37:49 <brett> trackbot, action-229?
17:37:49 <trackbot> Sorry, brett, I don't understand 'trackbot, action-229?'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
17:37:57 <brett> action-229?
17:37:57 <trackbot> Getting info on ACTION-229 failed - alert sysreq of a possible bug
17:38:08 <brett> action-226?
17:38:08 <trackbot> ACTION-226 -- Roy Fielding to spec update to address ISSUE/116 -- due 2012-08-15 -- OPEN
17:38:08 <trackbot> http://www.w3.org/2011/tracking-protection/track/actions/226
17:38:16 <brett> action-241?
17:38:16 <trackbot> Getting info on ACTION-241 failed - alert sysreq of a possible bug
17:38:34 <brett> action-249?
17:38:34 <trackbot> ACTION-249 -- David Singer to ensure that the qualifiers reflect the permissions documented in the compliance document, due 10 october -- due 2012-09-05 -- OPEN
17:38:34 <trackbot> http://www.w3.org/2011/tracking-protection/track/actions/249
17:39:16 <brett> brett has left #dnt
18:01:02 <mischat> mischat has joined #dnt
18:55:47 <fielding> fielding has joined #dnt
19:07:13 <schunter> schunter has joined #dnt
20:03:23 <KevinT> KevinT has joined #dnt
20:05:47 <KevinT> KevinT has left #dnt