16:39:37 <RRSAgent> RRSAgent has joined #dnt
16:39:37 <RRSAgent> logging to http://www.w3.org/2013/01/23-dnt-irc
16:39:39 <Zakim> Zakim has joined #dnt
16:39:44 <npdoty> Zakim, this will be 87225
16:39:44 <Zakim> ok, npdoty; I see T&S_Track(dnt)12:00PM scheduled to start in 21 minutes
16:39:55 <npdoty> rrsagent, make logs public
16:53:21 <dwainberg> dwainberg has joined #dnt
16:55:11 <Zakim> T&S_Track(dnt)12:00PM has now started
16:55:18 <Zakim> +npdoty
16:55:43 <ninjamarnau> ninjamarnau has joined #dnt
16:55:57 <fielding> fielding has joined #dnt
16:56:15 <Zakim> +efelten_
16:56:26 <schunter> schunter has joined #dnt
16:57:05 <npdoty> agenda+ scribe, if not determined already
16:57:12 <npdoty> agenda+ action items
16:57:33 <Zakim> +??P7
16:57:54 <npdoty> Zakim, ??P7 is schunter
16:57:54 <Zakim> +schunter; got it
16:58:09 <npdoty> agenda+ issue 153
16:58:17 <Zakim> +yianni
16:58:17 <npdoty> agenda+ issue 144
16:58:22 <Wileys> Wileys has joined #dnt
16:58:23 <npdoty> agenda+ issue 137
16:58:27 <npdoty> agenda+ issue 111
16:58:30 <Zakim> +dwainberg
16:58:33 <jeffwilson> jeffwilson has joined #dnt
16:58:33 <AnnaLong> AnnaLong has joined #dnt
16:58:36 <Zakim> +Fielding
16:58:40 <npdoty> agenda+ issues marked pending review
16:58:43 <Yianni> Yianni has joined #DNT
16:58:53 <npdoty> agenda?
16:59:02 <Zakim> +JeffWilson
16:59:42 <vincent> vincent has joined #dnt
16:59:51 <Zakim> +vincent
17:00:01 <Zakim> + +49.431.98.aaaa
17:00:10 <vinay> vinay has joined #dnt
17:00:17 <ninjamarnau> zakim, aaa is ninjamarnau
17:00:17 <Zakim> sorry, ninjamarnau, I do not recognize a party named 'aaa'
17:00:24 <npdoty> Zakim, aaaa is ninjamarnau
17:00:24 <Zakim> +ninjamarnau; got it
17:00:28 <schunter> Did any volunteer to scribe?
17:00:32 <rigo> rigo has joined #dnt
17:00:34 <Zakim> +Peder_Magee
17:00:41 <npdoty> not yet -- who would like to step up to help out today?
17:00:46 <kulick> kulick has joined #dnt
17:00:49 <hefferjr> hefferjr has joined #dnt
17:00:52 <rigo> zakim, code?
17:00:52 <Zakim> the conference code is 87225 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), rigo
17:01:02 <Zakim> +DAvid
17:01:03 <Zakim> + +385345aabb
17:01:07 <vinay> zakim, aabb is vinay
17:01:07 <Zakim> +vinay; got it
17:01:08 <Zakim> +kulick
17:01:09 <Zakim> +Keith_Scarborough
17:01:10 <Zakim> +hefferjr
17:01:31 <Keith> Keith has joined #dnt
17:01:36 <Zakim> +Rigo
17:01:36 <npdoty> Zakim, who is making noise?
17:01:37 <David_MacMillan> David_MacMillan has joined #dnt
17:01:41 <rigo> zakim, mute me
17:01:42 <Zakim> Rigo should now be muted
17:01:47 <Zakim> npdoty, listening for 10 seconds I could not identify any sounds
17:01:50 <Zakim> +WileyS
17:01:52 <JC> JC has joined #DNT
17:01:53 <pmagee_2023263538> pmagee_2023263538 has joined #dnt
17:01:57 <npdoty> Zakim, DAvid is really David_MacMillan
17:01:58 <Zakim> +David_MacMillan; got it
17:02:16 <Zakim> +Brooks
17:02:17 <Brooks> Brooks has joined #dnt
17:02:17 <susanisrael> susanisrael has joined #dnt
17:02:20 <Zakim> +SusanIsrael
17:02:32 <Zakim> +Aleecia
17:02:33 <David_MacMillan> npdoty, yes
17:02:36 <aleecia> aleecia has joined #dnt
17:02:36 <Zakim> +[Microsoft]
17:02:39 <npdoty> Zakim, choose a scribe
17:02:39 <Zakim> Not knowing who is chairing or who scribed recently, I propose Rigo (muted)
17:02:46 <npdoty> rigo, can you scribe?
17:02:53 <aleecia> zakim, please mute me
17:02:53 <Zakim> Aleecia should now be muted
17:02:55 <Zakim> +bryan
17:02:58 <rigo> ack ri
17:03:00 <dwainberg> zakim, who is making noise?
17:03:11 <Zakim> dwainberg, listening for 10 seconds I heard sound from the following: schunter (65%), Peder_Magee (29%), Rigo (31%)
17:03:17 <npdoty> Zakim, choose a scribe
17:03:17 <Zakim> Not knowing who is chairing or who scribed recently, I propose dwainberg
17:03:18 <Zakim__aaa_is_isham> Zakim__aaa_is_isham has joined #dnt
17:03:25 <rigo> zakim, mute me
17:03:25 <Zakim> Rigo should now be muted
17:03:40 <npdoty> scribenick: dwainberg
17:03:45 <Zakim> +[Microsoft.a]
17:03:48 <rigo> zakim, pick a victim
17:03:48 <Zakim> Not knowing who is chairing or who scribed recently, I propose vincent
17:03:52 <adrianba> zakim, [Microsoft.a] is me
17:03:52 <Zakim> +adrianba; got it
17:03:57 <vincent> ok for me
17:04:36 <Zakim> +hwest
17:04:38 <rigo> zakim, mute me
17:04:39 <Zakim> Rigo was already muted, rigo
17:04:39 <npdoty> vincent can take over for dwainberg at what seems like a good turning point
17:04:42 <hwest> hwest has joined #dnt
17:04:55 <Zakim__aaa_is_isham> 61#
17:04:56 <vincent> dwainberg, let me know when you want to switch, ok?
17:05:00 <dwainberg> schunter: pushed out all action items because it's not clear what's going to happen w/ the schedule
17:05:06 <dwainberg> Ok. thanks vincent.
17:05:07 <Zakim__aaa_is_isham> mute 61#
17:05:43 <Zakim> +Chris_Pedigo
17:05:51 <dwainberg> schunter: action 61 for Mike O. Is he on the call?
17:05:55 <ChrisPedigo_OPA> ChrisPedigo_OPA has joined #dnt
17:06:06 <Chris_IAB> Chris_IAB has joined #dnt
17:06:11 <aleecia> +1
17:06:14 <Wileys> Closed or Pending Review?
17:06:14 <npdoty> Zakim, who is making noise?
17:06:25 <Zakim> npdoty, listening for 10 seconds I heard sound from the following: schunter (95%)
17:06:30 <schunter> Zakim, mute me
17:06:30 <Zakim> schunter should now be muted
17:06:32 <Wileys> I believe the hum is coming from Matthias's connection
17:06:37 <dwainberg> yep
17:06:39 <Zakim> + +1.916.985.aacc
17:06:44 <schunter> Hmm. Maybe I should stay on mute ;-)
17:06:48 <Zakim> +[IPcaller]
17:06:56 <schunter> I will fetch another phone. Give me 2 mins.
17:07:14 <Chris_IAB> just joined the call via Skype
17:07:16 <Zakim> +RichardWeaver
17:07:19 <rigo> ack ri
17:07:36 <Zakim> -schunter
17:07:38 <dwainberg> npdoty: Rigo has action 258
17:07:38 <rigo> zakim, unmute rigo
17:07:38 <Zakim> Rigo should no longer be muted
17:07:51 <npdoty> Zakim, [IPCaller] is Chris_IAB
17:07:51 <Zakim> +Chris_IAB; got it
17:07:53 <tedleung> tedleung has joined #dnt
17:07:55 <Zakim> +??P7
17:07:58 <jmayer> jmayer has joined #dnt
17:08:05 <schunter> Zakim, ??P7 is schunter
17:08:06 <Zakim> +schunter; got it
17:08:24 <dwainberg> rigo: action 258 was initially for Tom L, in a discussion about who is on a site composed of multiple parties.
17:08:24 <Zakim> +Jonathan_Mayer
17:08:47 <dwainberg> ... It would be unclear who is a 1st party, service provider, or 3rd party.
17:08:51 <Zakim> +Ted_Leung
17:09:20 <dwainberg> ... the spec currently says a browser may consider an actor on the page and not declared in the same party as malicious.
17:09:23 <Wileys> Malicious or just DNT=0
17:09:25 <Wileys> ?
17:09:46 <dwainberg> ... Tom argued that in the spec it should say that a 1st party site SHOULD name all 1st party entitites.
17:10:31 <npdoty> if you've joined us from area code 916 (Sacramento or Northern Northern California), can you identify yourself on IRC?
17:10:40 <dwainberg> ... then I found an email from Roy, with a decision tree. Very important that the 1st party can somewhat control what others do.
17:10:56 <dwainberg> ... and one way is that 1st party is the only one to control the same party field.
17:11:32 <dwainberg> ... the SHOULD makes sure people put sufficient attention to this fact.
17:11:38 <eberkower> eberkower has joined #dnt
17:11:56 <dwainberg> ... has many advantages beyond what a statement about malicious would do.
17:12:05 <dwainberg> ... so provided language.
17:12:36 <npdoty> q+
17:12:38 <Zakim> + +1.646.654.aadd
17:12:48 <aleecia> q?
17:12:48 <dwainberg> ... (see http://lists.w3.org/Archives/Public/public-tracking/2013Jan/0093.html)
17:13:01 <rigo> zakim, mute me
17:13:01 <Zakim> Rigo should now be muted
17:13:03 <npdoty> q-
17:13:04 <eberkower> Zakim, aadd is e berkower
17:13:04 <Zakim> I don't understand 'aadd is e berkower', eberkower
17:13:09 <dwainberg> much better. thanks, Matthias.
17:13:17 <aleecia> :-)
17:13:21 <eberkower> Zakim, aadd is eberkower
17:13:21 <Zakim> +eberkower; got it
17:13:24 <npdoty> Zakim, who is on the phone?
17:13:25 <Zakim> On the phone I see npdoty, efelten_, yianni, dwainberg, Fielding, JeffWilson, vincent, ninjamarnau, Peder_Magee, David_MacMillan, vinay, kulick, Keith_Scarborough, hefferjr, Rigo
17:13:25 <Zakim> ... (muted), WileyS, Brooks, SusanIsrael, Aleecia (muted), [Microsoft], bryan, adrianba, hwest, Chris_Pedigo, +1.916.985.aacc, Chris_IAB, RichardWeaver, schunter, Jonathan_Mayer,
17:13:25 <Zakim> ... Ted_Leung, eberkower
17:13:30 <Zakim> + +1.646.825.aaee
17:13:32 <Zakim> + +1.919.349.aaff
17:13:50 <dwainberg> schunter: Sent a batch closing email.
17:13:59 <dwainberg> ... discussion can continue on the mailing list.
17:14:22 <dwainberg> ISSUE-153
17:14:22 <trackbot> ISSUE-153 -- What are the implications on software that changes requests but does not necessarily initiate them? -- pending review
17:14:22 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/153
17:14:39 <AN> AN has joined #dnt
17:14:52 <npdoty> Zakim, aaee is probably AnnaLong
17:14:52 <Zakim> +AnnaLong?; got it
17:14:59 <Wileys> Original language vs. Matthias' new language proposal
17:15:52 <dwainberg> q+
17:16:20 <johnsimpson> johnsimpson has joined #dnt
17:16:22 <efelten> q+
17:16:27 <Wileys> Current language allows for that outcome
17:16:52 <dwainberg> brian: believe in the current draft it does say that the setting must reflect user preference
17:17:08 <npdoty> s/brian/bryan/
17:17:14 <npdoty> Zakim, who is making noise?
17:17:16 <Zakim> +johnsimpson
17:17:25 <Zakim> npdoty, listening for 10 seconds I heard sound from the following: schunter (8%)
17:17:29 <JC> +JC
17:17:33 <JC> +q
17:17:33 <jmayer> +q
17:17:52 <npdoty> q+
17:17:57 <npdoty> issue-176?
17:17:57 <trackbot> ISSUE-176 -- Requirements on intermediaries/isps and header insertion that might affect tracking -- open
17:17:57 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/176
17:18:12 <vincent> dwainberg: are we mixing up combining two issues, intermediaries vs software that are changing the setting
17:18:30 <vincent> ... in ne case we might e talking about brwoser pluggins vs isp and proxies
17:18:36 <dwainberg> brian: to the extent that a modification of a header reflects user preference, it is allowed regardless
17:19:00 <npdoty> dwainberg, would you suggest that we have different text for those two different cases (intermediaries vs. plugins)?
17:19:02 <rigo> q+ to suggest that if they interfere, they have to be able to do exceptions
17:20:07 <Wileys> Rigo - agreed - if an intermediary wants to modify the DNT signal they must support all the same elements a UA must
17:20:10 <rigo> ack dwainberg
17:20:33 <dwainberg> fielding: not sure I get that. you can have a distributed user agent.
17:20:37 <rigo> zakim, unmute
17:20:37 <Zakim> I don't understand 'unmute', rigo
17:20:40 <rigo> zakim, unmute me
17:20:40 <Zakim> Rigo should no longer be muted
17:20:42 <dwainberg> ... proxies, for example, are never user agents.
17:21:00 <dwainberg> ... no as long as we stick with the terminology, we should be ok.
17:21:19 <npdoty> bryan: given the complexity of Web architecture, and the number of different pieces, not worth distinguishing [sorry, didn't capture in real time]
17:21:20 <dwainberg> schunter: so a proxy because it's not initiating it's not a UA
17:21:34 <dwainberg> fielding: it's the UA that's responsible for sending the request.
17:21:40 <npdoty> q?
17:21:56 <dwainberg> bryan: I believe the question is at what layer is that header set
17:22:16 <dwainberg> ... at what point does the user agent end.
17:23:08 <dwainberg> schunter: so one proposal was basically it has to comply with UA requirements
17:23:31 <dwainberg> ... wouldn't this be a solution?
17:23:32 <npdoty> no matter where in the chain, it has to comply with the requirements in the spec -- that would approximate the proposal from dsinger and myself
17:23:36 <npdoty> q?
17:23:39 <fielding> what is wrong with the current text in the spec?
17:23:51 <schunter> q?
17:23:54 <Wileys> Roy - I'm with you - current text already covers the issue
17:23:59 <schunter> ack efelten
17:24:23 <schunter> Thanks for reminding me that there exists a queue ;-)
17:24:43 <dwainberg> efelten: it makes sense to avoid trying to classify all the different types of software. If you are setting or modifying the header, you have a responsibility to meet the requirements.
17:24:59 <npdoty> fielding, Wileys, I think issue-153 was asking for additional requirements to make it clear that any software (even if not an http intermediary) has to capture the user intent
17:24:59 <schunter> ack JC
17:25:00 <dwainberg> ... we can get to that goal more quickly by backing off the architetural taxonomy.
17:25:18 <dwainberg> JC: how are we addressing IT departments that deploy the UA for employees?
17:25:40 <dwainberg> rigo: it's a matter of where the declaration of the will comes from?
17:26:04 <dwainberg> bryan: the IT department use case the same as the home router case.
17:26:06 <npdoty> JC, I don't think the current spec speaks to what an IT department does
17:26:20 <fielding> now we are rehashing a closed issue
17:26:25 <schunter> I agree.
17:26:27 <npdoty> (I'm not sure there's anything our spec could do to insist who sets the preferences on a machine)
17:26:28 <dwainberg> ... if I exercise control over the domain, I should be able to set the policy.
17:26:33 <JC> Is this concensus?
17:26:44 <Zakim> -vinay
17:27:03 <JC> I just want to make sure these scenarios are covered in spec.
17:27:07 <schunter> q?
17:27:11 <schunter> ack jmayer
17:27:32 <rigo> ack ri
17:27:32 <Zakim> rigo, you wanted to suggest that if they interfere, they have to be able to do exceptions
17:27:44 <fielding> See last para of http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#determining
17:27:51 <dwainberg> jmayer: tendency to focus on specific fact patterns, but the considerations are more cross-cutting. If the question is what can/can't enterprise IT do?
17:27:58 <dwainberg> ... we can answer that.
17:28:10 <dwainberg> ... we can also answer what if settings conflict.
17:28:10 <aleecia> Rigo - we shot that idea down already
17:28:24 <Wileys> Nick, agreed on Issue-153 - I believe we're all saying the same thing:  Any party that sends/modifies a DNT signal should be required to provide all the same functionality as the UA (explicit consent, further information, controls, exceptions, etc.)
17:28:35 <dwainberg> ... I suggest we describe these things to make it clear we're thinking about them, but knock down issues one by one.
17:28:46 <schunter> q?
17:28:51 <schunter> ack npdoty
17:29:04 <dwainberg> npdoty: Do we need text on this at all?
17:29:40 <dwainberg> ... if there's some other piece of software that's not an HTTP intermediary, it has to follow the same requirements (proposed text)
17:29:50 <rigo> > Software outside of the user agent that causes a DNT header to be sent (or modifies existing headers) MUST NOT do so without following the requirements of this section; such software is responsible for assuring the expressed preference reflects the user's intent.
17:29:58 <rigo> http://lists.w3.org/Archives/Public/public-tracking/2012Aug/0001.html
17:30:01 <dwainberg> ... it would be adding one requirement, just to be clear there is no software not subject to the requirement.
17:30:11 <dwainberg> q+
17:30:28 <rigo> I think the exception mechanism is key
17:30:31 <npdoty> Wileys, oh, that wasn't what I heard. http proxies will not implement JavaScript APIs, for example
17:31:18 <Wileys> Nick, then they shouldn't be able to modify the DNT signal
17:31:35 <schunter> "Software outside of the user agent that inserts, modifies, or removes DNT information MUST NOT  do so without following the requirements on UAs of this section including that such software is responsible for assuring the expressed preference reflects the user's intent."
17:31:42 <aleecia> Rigo - the problem was some user agents (already implemented) will not even have a UI. If you want to go with SHOULD do exceptions, that sounds sane, but MUST didn't work out. We've talked about this.
17:31:42 <Wileys> We shouldn't create different rules based on position in the communication chain
17:32:11 <vincent> dwainberg: some pieces of software that have direct interaction with the user should be responsible to make sure that the signal reflect the user preference
17:32:36 <jmayer> +q
17:32:44 <schunter> q?
17:32:51 <npdoty> Wileys, I don't think that's our previous agreement regarding intermediaries
17:32:55 <schunter> ack dwainberg
17:32:58 <schunter> ack jmayer
17:33:06 <fielding> The language we use is "Implementations of HTTP that are not under control of the user must not generate or modify a tracking preference."
17:33:10 <Wileys> Aleecia, wouldn't you agree that UA's that have already implemented a DNT signal ahead of a final standard are not compliant with whatever that final standard is?
17:33:26 <rigo> +1 to wording of fielding
17:33:28 <dwainberg> jmayer: I agree, with one clarification -- the agreement is that the same requirements apply. That doesn't mean we have agreement on the requirements.
17:33:31 <Zakim> -bryan
17:33:36 <Wileys> Nick, I thought it was and should be.  Happy to have the conversation again.
17:33:47 <aleecia> Oh sure, Shane. But we have a question of implementations illustrating how people want to use DNT.
17:33:55 <schunter> Zakim, mute me
17:33:55 <Zakim> schunter should now be muted
17:33:56 <Zakim> -David_MacMillan
17:33:57 <Zakim> +bryan
17:34:07 <jmayer> s/requirements/, such as how defaults can be set./
17:34:13 <dwainberg> schunter: ok, so let's look at fine tuning the language
17:34:14 <schunter> Zakim, unmute me
17:34:14 <Zakim> schunter should no longer be muted
17:34:19 <aleecia> We're in no way obligated to follow what's happened, but when we already have implementations, we should pay attention to that as a valuable input
17:34:40 <rigo> just imagine opera mini as a UA and you'll see what we mean. This goes over a proxy and sends compressed images. It still can respect UA requirements
17:34:47 <npdoty> Wileys, okay, well, that's not what current text says, and we hadn't discussed HTTP intermediary spoofing of JavaScript when we agreed on that text
17:35:11 <dwainberg> schunter: think it's not neceesary that it's under the control of the user, but that it refelects the preference.
17:35:19 <npdoty> fielding, does a plugin or software that modifies outgoing http requests count as "implementations of http"?
17:35:27 <rigo> q+
17:35:28 <fielding> Setting the preference is control
17:35:34 <dwainberg> ... for example, an ISP that offers parental control. It's not under control, but does reflect the user's preference.
17:35:39 <Wileys> Nick, fair - I'm more focused on the philosophy of intermediaries
17:35:49 <fielding> :)
17:36:36 <Wileys> Di+q
17:36:37 <jmayer> +q
17:36:38 <Wileys> +q
17:36:45 <schunter> ack rigo
17:36:47 <rigo> ack ri
17:36:48 <dwainberg> bryan: let's be explicit wrt reflecting user preference. we're not saying the requirement must be fulfilled by every element..
17:36:56 <Zakim> +David_MacMillan
17:36:57 <aleecia> That sounds right - some notion of "if you represent a user's choice, you better be sure it's the *user's* choice"
17:36:58 <npdoty> our proposed text was referring to requirements in Section 3 on "Determining User Preference" (to respond to bryan)
17:37:19 <Wileys> Disagree with Bryan - anyone setting a preference that doesn't allow of exceptions is not compliant with the standard
17:37:27 <Wileys> s/of/for
17:37:35 <dwainberg> rigo: good example, matthias, because if I set a preference that only sends a fixed header, this is not a communication mechanism anymore, so I would argue for a more narrow interpretation of control.
17:37:51 <npdoty> bryan: we're not saying the requirement that an intermediary implement every element in the spec, the JS API for example
17:38:18 <aleecia> DNT is not a negotiation. DNT is not contracts-lite. DNT is a user preference.
17:38:21 <schunter> q?
17:38:28 <schunter> ack jmayer
17:38:46 <rigo> zakim, mute me
17:38:46 <Zakim> Rigo should now be muted
17:38:54 <npdoty> to be clear, an intermediary could allow exceptions in the sense that it could have a UI where it allowed you to choose to send DNT:0 in some cases
17:39:23 <dwainberg> jmayer: to respond to bryan. we may say in the spec you don't need the JS api if it's not practical. we might come up with cases, and some may be network level, but not necessarily because it's network level.
17:39:29 <npdoty> but http intermediaries are extremely unlikely to implement a JavaScript API; they won't commonly read those sections of the spec, even
17:39:34 <Wileys> Nick - disagree as this disintermediates the owner of the site (publisher) and creates unnecessary implementation overhead
17:39:57 <dwainberg> ... and about what degree of preference is required ... is how we deal w/ conflicts that
17:39:59 <schunter> q?
17:40:06 <schunter> ack Wileys
17:40:20 <dwainberg> bryan: yes, if we have requirements where technically applicable or feasible that's fine.
17:40:45 <npdoty> WileyS, you disagree that HTTP intermediaries could allow sending DNT:0 in individual cases? or just that they shouldn't?
17:41:01 <vincent> Wileys, would an intermediary that always deny (or accept) exception be ok?
17:41:06 <dwainberg> Wileys: I'm still on the hard line side, that intermediaries must be fully able to support other elements of the standard, especially exceptions. Disintermediating API calls breaks the balance we're trying to build.
17:41:32 <aleecia> The idea that all UAs must be browsers (which is where this ends) seems wrong to me
17:42:04 <dwainberg> ... as long as we're saying that intermediaries fully support the rest of the standard that's fine, but we should create carve-outs, because we create imbalance, or greater burden on pubs and 3rd parties.
17:42:14 <aleecia> If a party asks for an exception and a user is not able to see the ask, why not just turn the user away?
17:42:37 <npdoty> in the earlier agreed upon text we say: "An HTTP intermediary must not add, delete, or modify the DNT header field in requests forwarded through that intermediary unless that intermediary has been specifically installed or configured to do so by the user making the requests."
17:42:44 <Wileys> Aleecia - we're trying to build user friendly experiences - that doesn't meet the goal
17:42:55 <npdoty> that is, they must not modify it, *unless* it was user-configured to do so
17:43:02 <aleecia> I agree, Shane. Neither option does, is the problem.
17:43:09 <dwainberg> schunter: we should take your proposal as a working assumption, and require all elements on whatever thing is doing the modification, and then look at the other UA requirements that are impossible or hard to satisfy at the network level.
17:43:36 <npdoty> q+
17:43:46 <Wileys> Aleecia, removing intermdiaries that are unable to fully support the standard is the cleanest path forward
17:44:29 <aleecia> The cleanest path forward is to shoot DNT in the head. Doesn't mean it's the best...
17:44:44 <dwainberg> brian: starting w/ that analysis is a good thing to do. we should avoid definining everything in terms of UA te hnology, because that is overly limiting.
17:44:51 <npdoty> s/brian/bryan/
17:44:52 <vincent> Wileys, if the intermediary inform the user that it'll always grant (or deny) exception request, why it is not ok?
17:45:04 <aleecia> It's entirely reasonable that someone be able to deliberately choose to turn on DNT but do so through a light-weight way that does not even have a UI in some cases
17:45:07 <dwainberg> schunter: let's not decide at this point, but let's follow Shane's approach and do the analysis.
17:45:10 <npdoty> q?
17:45:14 <dwainberg> ... anyone disagree?
17:45:32 <aleecia> What's not reasonable is for a UA to decide for users what DNT should be
17:45:51 <aleecia> (where "reasonable" encompasses some pragmatic issues)
17:46:11 <Wileys> Aleecia, why is that reasonable?  Supporting a standard means just that - supporting ALL of that standard.  I don't believe just being able to turn on DNT=1 means you're standard compliant.
17:46:14 <dwainberg> npdoty: the text dsinger and I proposed would apply to any software. I don't think it makes much sense to require all the other elements of the spec. It makes to apply all sections on determining user preference...
17:46:41 <npdoty> s/any software/any software for all the requirements in the section on Determining User Preference/
17:46:45 <schunter> q?
17:46:47 <npdoty> q-
17:46:47 <aleecia> Shane we are so far down the road that supporting DNT will not mean supporting all of DNT. You can predict everything I'd say in response here :-)
17:46:56 <schunter> ack npdoty
17:47:12 <vincent> dwainberg, switch?
17:47:14 <npdoty> schunter: volunteer to go through the spec and analyze which requirements would be a problem for an intermediary?
17:47:23 <dwainberg> yes, thanks, vincent
17:47:24 <aleecia> If you *really* want that approach, cool, but then you need to live with it everywhere ;-)
17:47:25 <dwainberg> :)
17:47:26 <vincent> scribenick: vincent
17:47:34 <bryan> bryan has joined #dnt
17:47:39 <npdoty> action: schunter to review which requirements in the spec would be problematic for an intermediary
17:47:40 <trackbot> Created ACTION-356 - Review which requirements in the spec would be problematic for an intermediary [on Matthias Schunter - due 2013-01-30].
17:47:40 <jmayer> q+
17:47:46 <vincent> schunter: next issue is 144
17:47:50 <vincent> issue-144
17:47:50 <trackbot> ISSUE-144 -- User-granted Exceptions: Constraints on user agent behavior while granting and for future requests? -- open
17:47:50 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/144
17:48:20 <jmayer> -q
17:48:28 <vincent> schunter: currently with the new exception approach it means that the UA saw and retransmit the exception informatio and are allowed to modify as long as it reflects user preference
17:48:45 <npdoty> q+
17:48:47 <vincent> ... david's point was that we can just close issue 144
17:49:28 <vincent> npdoty: just to clarify, we have two different question on issue 144, one about the UI and one about the future requirement
17:49:43 <schunter> q?
17:49:43 <npdoty> q-
17:49:43 <Wileys> Aleecia - I already thought I did.  If I say my company is W3C DNT compliant, then I would expect that to mean we agree with the full standard.
17:50:01 <vincent> schunter: collect opinion, anyone want to keep 144 open?
17:50:03 <schunter> q?
17:50:06 <npdoty> question 1: do we have any UI requirements? our answer: no.
17:50:26 <npdoty> question 2: once an exception granted, what is future behavior? our answer: send dnt:0 when an exception persists.
17:50:36 <schunter> q?
17:50:40 <npdoty> npdoty: I'm not aware of objections to those
17:50:40 <vincent> schunter: I suggest to move 144 to pending review and will be in the next batch for closing
17:50:50 <schunter> q?
17:50:55 <vincent> ... no discussion, it seems that we have a consensus
17:51:08 <jmayer> +q
17:51:08 <vincent> schunter: move to issue 137
17:51:12 <npdoty> issue-137?
17:51:12 <trackbot> ISSUE-137 -- Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s) -- open
17:51:12 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/137
17:51:12 <vincent> issue-137
17:51:13 <trackbot> ISSUE-137 -- Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s) -- open
17:51:13 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/137
17:51:42 <schunter> q?
17:51:47 <schunter> ack jmayer
17:52:34 <vincent> jmayer: I can't speak if the new technical design allow to know if the sp is a 1st party/3rd party
17:52:57 <schunter> q?
17:53:33 <vincent> ... roy opposed to flag for the sp flag (if I understand correctly?)
17:53:50 <rigo> q+
17:54:14 <vincent> roy: couple of different things, in some cases the SP can't reveal that the 1st party is not sending the response (for contractual reason)
17:54:32 <vincent> ... even if the sp had to do this, it would not do it
17:54:35 <aleecia> I do not understand why those contracts would exist, at all. That seems broken and astonishingly wrong. What am I missing?
17:54:41 <vincent> ... the 1st party could do that
17:55:03 <vincent> ... the other issue is "what does sending a S in the response tell the user"
17:55:04 <jmayer> aleecia, I also would like to hear more about these claimed contractual obligations.
17:55:25 <npdoty> is the ability of the first-party to list its service providers likely to resolve jonathan's requirement?
17:55:35 <npdoty> if not, I think we should ask for an alternative proposal
17:55:43 <schunter> q?
17:55:46 <rigo> ack ri
17:55:47 <aleecia> If 1st parties are required to list SPs that works for me
17:56:00 <aleecia> If 1st parties may optionally list SPs, no
17:56:02 <rigo> zakim, unmute me
17:56:02 <Zakim> Rigo should no longer be muted
17:56:05 <npdoty> (or maybe we had a previous 's' proposal text that would count as the alternative)
17:56:10 <jmayer> npdoty, I want to make sure a service provider can always be identified. I don't care so much about the technical mechanism.
17:56:25 <aleecia> Since I do not understand why there is this contractual obligation, I don't know if that's likely
17:56:27 <fielding> But first parties aren't required to list SPs because that is undue burden for a feature that nobody has implemented
17:56:29 <jmayer> Not that this means a MUST, not a MAY for identifying service providers.
17:56:38 <jmayer> s/Not/Note/
17:56:53 <efelten> q+
17:56:53 <vincent> rigo: I would support Roy, because the SP does not have control over the data, it would only bring only statistical data about who is SP on what but no privacy material
17:57:00 <aleecia> Roy, to flog this again: add-ons are very likely to use this data
17:57:09 <aleecia> In the US, SPs are *not* part of 1st parties
17:57:09 <fielding> If there eventually becomes benefit to list all same parties, then that benefit will lead to implementation (far more effectively than a SHOULD).
17:57:10 <npdoty> jmayer, aleecia, so do we have an alternative to Roy's most recent text that we should compare to?
17:57:13 <vincent> ... the defintion of SP is such that they are part of the 1st party
17:57:31 <vincent> ... nice for those who want to make statistics only
17:57:45 <aleecia> presumably the text prior to Roy's mods, but I'd have to look to confirm
17:57:54 <vincent> schunter: SP follow the same privacy practices in the EU language of the data processor
17:58:24 <aleecia> we need to build something that works in areas other than the EU...
17:58:24 <jmayer> npdoty, yes, mandatory service provider flag language has floated about for a year
17:58:47 <vincent> ... if the SP has not the same privacy principle, that it is considered as a 3rd party
17:58:47 <aleecia> because in the EU, there are legal liability issues, and we cannot visit those upon DNT implementors
17:58:49 <schunter> q?
17:58:58 <schunter> ack efelten
17:59:19 <schunter> Zakim, mute me
17:59:19 <Zakim> schunter should now be muted
17:59:21 <fielding> The text I have does require identification of the data controller (first party), so that is a means to detect a service provider when it is using its own domain.
17:59:31 <npdoty> jmayer, great, I think it might be good to clarify what the exact text is (even if we're just pointing to a previous email/proposal)
17:59:35 <vincent> efelten: there is a case where users have a reason to know the difference, imagine that there is a primary site that include content from SP.com
17:59:52 <vincent> .. SP.com indicate that it is a 1st party
18:00:14 <aleecia> which is a good step. but we know service providers don't always use their own domains.
18:00:36 <jmayer> Off to class.  I sure hope we don't batch close this issue...
18:00:37 <rigo> in case firstparty.com has not indicated fp.com "same party" I wouldn't believe any "1" from fp.com
18:00:40 <vincent> ... it could mean that SP is a first party and can use the data for itself, if it s a pure service provider SP can not use the data for itself
18:00:43 <Zakim> -Jonathan_Mayer
18:00:48 <schunter> Zakim, unmute me
18:00:48 <Zakim> schunter should no longer be muted
18:00:50 <schunter> q?
18:00:53 <vincent> ... it's a case where the difference matters
18:00:59 <rigo> q+
18:01:09 <rigo> q-
18:01:20 <aleecia> My guess is if we go down that path, we'll see more SPs not using their own domains.
18:01:24 <fielding> aleecia, the only reason that 1st party does not include its service providers is because we defined it that way. It is not a US thing. In EU, they have data controller and data processor.
18:01:39 <vincent> schunter: this issue will take longer than the last one, would like to have several proposal for the next face to face and try to find common ground
18:01:58 <vincent> schunter: postponed the issue until f2f
18:02:12 <npdoty> q+
18:02:16 <aleecia> yes - in the EU, to use the terms we have here, the 1st party is responsible for the SP. not so in the US
18:02:18 <schunter> q?
18:02:24 <vincent> ... propose alternative text into the spec
18:02:33 <vincent> ... fro the enxt f2f
18:03:12 <vincent> roy: the 1st party member is not really an alternative to the S flag, it's a solution to indicate multiple 1st parties
18:03:26 <rigo> zakim, unmute rigo
18:03:26 <Zakim> Rigo was not muted, rigo
18:03:29 <vincent> ... would not be a complete alternative
18:04:04 <vincent> rigo: if somebody is sending back S instead of 1, it'll be fine to?
18:04:30 <aleecia> so that's where i'm having trouble: the idea that there's no way to visualize the difference between a service provider and a 1st party
18:04:36 <vincent> roy: yes, but we would have to change the meaning of 1
18:04:42 <aleecia> users should be able to have visibility into where their data flows
18:04:54 <vincent> schunter: but it would not give much information
18:05:07 <vincent> rigo: legally tehre is no protection between 1 and S
18:05:10 <npdoty> q+ to ask about volunteers for text
18:05:11 <aleecia> this is basically FIPPS -- it's "no secret databases" into current times
18:05:17 <efelten> S does not have the same meaning as 1.   S means data can be used on behalf of a (separate) first party.  1 means you can use the data yourself.
18:05:19 <fielding> aleecia, there is no way to visualize the difference between contractors and employees.  It is NOT a privacy problem and has nothing to do with DNT.
18:05:39 <vincent> schunter: proposal is to add 2 lines to the spec to have a concrete proposal to discuss during the f2f
18:05:40 <rigo> ed, I haven't really understood your use case. Can you put that in email?
18:05:57 <vincent> npdoty: make sens, do we have an action item?
18:06:03 <aleecia> of course we can visualize the difference between 1st parties and SPs.
18:06:26 <aleecia> this is not contract employees working for a first party. this is an entirely different company
18:06:29 <vincent> schunter: roy can you write this text and then send it to jmay or the complete list?
18:06:32 <aleecia> with different data practices
18:06:32 <npdoty> fielding, would you be willing to take that action?
18:06:46 <vincent> fielding: lack of time
18:07:12 <vincent> schunter: will see with dsinger
18:07:16 <schunter> q?
18:07:22 <schunter> ack npdoty
18:07:22 <Zakim> npdoty, you wanted to ask about volunteers for text
18:07:22 <aleecia> it doesn't have to be a privacy *problem* at all, just a way for users to see where their data goes.
18:07:26 <vincent> ... anything else on issue 137?
18:07:29 <fielding> aleecia, not according to our definitions.
18:07:35 <vincent> issue-111
18:07:35 <trackbot> ISSUE-111 -- Signaling state/existence of site-specific exceptions -- open
18:07:35 <trackbot> http://www.w3.org/2011/tracking-protection/track/issues/111
18:07:57 <npdoty> action: singer to add service provider option text (with jmayer) as an issue in the draft with an option box
18:07:57 <trackbot> Created ACTION-357 - Add service provider option text (with jmayer) as an issue in the draft with an option box [on David Singer - due 2013-01-30].
18:08:01 <fielding> and the letter "s" does not inform the user of where their data goes.
18:08:03 <aleecia> not according to what you've proposed for definitions :-)
18:08:13 <vincent> schunter: we had this postponed, the point is that if you get DNT:0 you don't know if it's a general preference or an exception
18:08:32 <Wileys> All of the UAs in the room said they will support site-specific exceptions - if we remove them from the specification then we can equate an exception to site-wide exception (as the publisher)
18:08:36 <Wileys> +q
18:08:44 <fielding> I did not propose those definitions.
18:08:44 <aleecia> either we let users block data collection, which we aren't, or at least we have to offer users a way to see what's going on. if we cannot even do that -- this is untenably broken.
18:08:45 <schunter> q?
18:08:53 <vincent> ... do we need some extra signal to tell if the 0 is an exception or a general preference
18:08:54 <npdoty> action-357: the goal is to have a concise alternative/additional text for the "s flag" or otherwise an alternative to roy's most recent proposal
18:08:54 <trackbot> Notes added to ACTION-357 Add service provider option text (with jmayer) as an issue in the draft with an option box.
18:08:54 <schunter> ack Wileys
18:09:18 <aleecia> if you want to back away from giving users the ability to have transparency, then we need to let them just block collection. full stop.
18:09:38 <npdoty> q+
18:09:43 <fielding> aleecia, that simply isn't relevant. Go ahead and block the entire Web.
18:09:45 <vincent> Wileys: somewhat tide to what we decide on site-specific exception, the publisher receiving DNT:0 could know if the 3rd parties are covered
18:09:55 <aleecia> having DNT mean "your data flings around and you have no control over it, and no idea what's even happened" is not a reasonable outcome.
18:09:59 <adrianba> q+
18:10:21 <vincent> schunter: we agreed that we have explicit-explicit api, so there can be a case where you have explicit list
18:10:36 <Wileys> Okay - if explicit lists exist, then the publisher will need a way to determine which of their 3rd parties are not covered.
18:10:57 <vincent> schunter: there can be arbitrary wierd user preferences supported by wierd user agent
18:11:40 <vincent> Wileys: then the publisher need to know which 3rd party are not covered either to ask new exceptions, modify user experience or block third party
18:11:55 <schunter> q?
18:12:11 <schunter> ack npdoty
18:12:14 <vincent> schunter: this would have to be handled o the server side cause user could modify the browser
18:13:12 <vincent> npdoty: two points: 1) wether we provide the explicit list, the exception does not inform the publisher that there is an all--target exception
18:13:33 <schunter> Even if we have DNT0e (for: you  have a site-wide exception), my self-compiled user agent can still continue sending DNT1 to all third parties.
18:13:51 <schunter> q?
18:13:55 <schunter> ack adrianba
18:13:59 <Zakim> -johnsimpson
18:14:00 <johnsimpson> johnsimpson has left #dnt
18:14:13 <vincent> npdoty: there is a JS API now to know if there is an exception for this lsit (I missed some of it)
18:14:21 <aleecia> SPs have to be knowable. it's just that simple. i'm not asking for users to be able to block SPs, which would be an entirely sensible thing, but if users cannot even know who the SPs are, this is a bankrupt exercise.
18:14:38 <npdoty> I was trying to clarify that we need to solve this whether or not explicit lists are supported in our JS API
18:14:49 <rigo> q+ to say that it doesn't exclude a summary treatment, this is not a feature to me
18:15:03 <Zakim> -vincent
18:15:20 <vincent> I'm ot on the call anymore
18:15:27 <npdoty> scribenick: npdoty
18:15:30 <Zakim> -AnnaLong?
18:15:48 <npdoty> adrianba: propose that we remove the array of domains
18:15:49 <npdoty> q+
18:16:30 <npdoty> schunter: be optimistic, leave things as they are; if we find that there are mixed signals, we can come back to it then
18:16:48 <npdoty> adrianba: I expect us to request that this feature be marked "at risk"
18:16:56 <schunter> q?
18:17:01 <npdoty> ... will send a mail with problems, shouldn't send time solving them
18:17:02 <schunter> ack rigo
18:17:02 <Zakim> rigo, you wanted to say that it doesn't exclude a summary treatment, this is not a feature to me
18:17:29 <fielding> aleecia, SPs have requirements on data is siloing, non-disclosure, and no independent use -- all to ensure privacy; the corresponding benefit they get is that they are not treated as a third party.
18:17:52 <adrianba> q+
18:17:53 <npdoty> rigo: explicit/explicit domains can be complex, if you allow for *.* and the UA is clear, the specification would not force you to implement it, just doesn't exclude others from doing it
18:17:57 <npdoty> ... what is the hindrance?
18:18:00 <aleecia> i'm not suggesting treating SPs as third parties.
18:18:08 <schunter> ack npdoty
18:18:10 <aleecia> but i am saying no secret data stores.
18:18:11 <npdoty> ... can't be forced to implement it, don't see why exclude it
18:18:15 <aleecia> pretty basic.
18:18:49 <Zakim> -Peder_Magee
18:19:28 <Wileys> The question is "Can we really believe that?"  If not, publisher need a way to poll.
18:19:36 <fielding> alecia, and I am saying that if a first party can keep a secret data store, then a service provider can too -- there is no difference to the user's privacy risk.
18:20:08 <aleecia> huh? no. the identity of the SPs is the issue here. users should know who they're dealing with, that's all.
18:20:22 <npdoty> npdoty: we don't currently require the UA to send DNT:0 to the first party if there is an all-trackers, site-wide exception
18:20:23 <vincent> npdoty, I'm having phone problem, can't join
18:21:02 <npdoty> ... because the user is still indicating to the first party that they want the first party compliance
18:21:11 <rigo> aleecia, the service provider has no own rights. So if the service provider lacks secure storage, it is the fault of the first party not ordering the sp to have secure storage
18:21:19 <aleecia> if that means the 1st parties list the SPs rather than the SPs list themselves, that's fine
18:21:22 <schunter> ack adrianba
18:21:50 <aleecia> Rigo - that's not the point at all. (and isn't quite true in the US i expect...)
18:21:54 <npdoty> schunter: so you might send DNT: 1e or DNT: 0e, to indicate the difference between the first party and the third party
18:22:07 <npdoty> adrianba: in response to nick's question, depends on the wildcard
18:22:09 <Zakim> -ninjamarnau
18:22:14 <npdoty> ... a query method with the same signature as the set method
18:22:20 <rigo> +1 to adrianba on the relation to the domain wildcards
18:22:26 <rigo> which is precisely my point
18:22:27 <fielding> aleecia, they should know who is the data controller. The notion that the user ever knows "who they are dealing with" on the Internet is not realistic.
18:22:38 <npdoty> ... if you call the query method with the same parameters, then it will tell you whether that set method has been called in the past
18:22:43 <Zakim> + +33.6.50.34.aagg
18:22:51 <npdoty> ... changes it from being a simple property to a method
18:22:55 <aleecia> ephemeral data and packet forwarding are an entirely different issue, Roy
18:22:56 <vincent> zakim, aagg is vincent
18:22:56 <Zakim> +vincent; got it
18:23:02 <npdoty> ... call the query method with the same arguments
18:23:14 <npdoty> ... tell the site whether it previously recorded that exception
18:23:25 <rigo> +1 to adrianba
18:23:27 <npdoty> q+
18:23:41 <vincent> schunter: from your point fo view the query api is enough to inform the site?
18:24:04 <vincent> adrianba: I think the API need to be able to know if it's a web wide or site wide exception
18:24:34 <vincent> the primary purpose of this is to not bother the user but know when the site get the exception
18:24:35 <aleecia> this is just so basic. it's pretty much Shane's "discoverable" approach, in a different context.
18:25:00 <npdoty> q?
18:25:12 <rigo> +1
18:25:14 <schunter> ack npdoty
18:25:16 <adrianba> +1
18:25:29 <vincent> schunter: what I'll do is leave this open and wait until we have the wild-card api
18:25:45 <aleecia> blocking users' ability to find out what's happened with their data, even after the fact, is a broken approach
18:25:46 <Wileys> Aleecia, the difference here is the legal concept of "agency" and/or "service provider" - depending on which side of the pond we're on.  In both cases, a company is not compelled to disclose those that work on its behalf as legally they are the same party in that context.
18:25:50 <npdoty> adrianba, can you read over the confirmSiteSpecificTrackingException code and see if that's all you need?
18:25:53 <schunter> q?
18:25:53 <vincent> npdoty, did not capture that
18:26:09 <vincent> schunter: anything else o issue 111?
18:26:11 <adrianba> npdoty, yes, hadn't seen that was added
18:26:24 <Wileys> Aleecia, from a domain listing perspective though I don't see how we'll be able to avoid listing the domains for our service providers/agents so they get the appropriate DNT signal.
18:26:25 <aleecia> If a SP screws up and accidentally publishes all the data they hold, we sue the SP, right?
18:26:29 <npdoty> npdoty: dsinger already wrote up a confirmSiteSpecificException, which does have the same parameters, as adrianba indicated, so that might be sufficient
18:26:31 <adrianba> npdoty, don't think it was in when i reviewed for this on monday
18:26:50 <vincent> schunter: that's all from my point of view, reminder: registration for the f2f
18:27:03 <aleecia> thursday 31st?
18:27:05 <vincent> ... please register before the end of the month
18:27:07 <kulick> If we are unable to attend the f2f, will there be a dial-in line that can be used?
18:27:14 <Wileys> Aleecia - it depends, if an SP/vendor is hosting an element of my business and that is breached - then I'm sued and I in turn sue my SP/vendor.
18:27:17 <npdoty> https://www.w3.org/2002/09/wbs/49311/tpwgmit2013/
18:27:42 <vincent> schunter: any questio about the f2f, how do we register people that would attend but are not part of the group?
18:27:55 <kulick> q
18:27:59 <schunter> q?
18:28:02 <vincent> xxx: how do we register people that would attend but are not part of the group?
18:28:09 <npdoty> s/xxx/bryan/
18:28:10 <kulick> If we are unable to attend the f2f, will there be a dial-in line that can be used?
18:28:10 <Zakim> -Chris_Pedigo
18:28:13 <Zakim> - +1.916.985.aacc
18:28:14 <Wileys> Aleecia, good example was a recent breach by Epsilon of email addresses for some of its largest clients - their clients are being sued by their customers and they are in turn suing Espilon
18:28:15 <vincent> npdoty: send an email to the chair
18:28:20 <Zakim> - +1.919.349.aaff
18:28:21 <rigo> kulick, I think so
18:28:21 <Zakim> -hwest
18:28:22 <Zakim> -RichardWeaver
18:28:22 <Zakim> -hefferjr
18:28:23 <Zakim> -bryan
18:28:24 <Zakim> -SusanIsrael
18:28:25 <Zakim> -efelten_
18:28:25 <Zakim> -adrianba
18:28:25 <Zakim> -Ted_Leung
18:28:26 <Zakim> -yianni
18:28:26 <Zakim> -Chris_IAB
18:28:27 <Zakim> -Rigo
18:28:28 <Zakim> -JeffWilson
18:28:28 <aleecia> But they're not the same entity...
18:28:29 <Zakim> -Keith_Scarborough
18:28:29 <Zakim> -schunter
18:28:30 <Zakim> -dwainberg
18:28:31 <Zakim> -kulick
18:28:33 <Zakim> -[Microsoft]
18:28:33 <Zakim> -vincent
18:28:34 <Zakim> -Fielding
18:28:35 <npdoty> adrianba, it's possible that dsinger has been adding that recently, I haven't kept up with his schedule ;)
18:28:36 <aleecia> …as that example demonstrates.
18:28:39 <Chris_IAB> npdoty, when did you send the f2f registration email?
18:28:42 <npdoty> Zakim, list attendees
18:28:42 <Zakim> As of this point the attendees have been npdoty, efelten_, schunter, yianni, dwainberg, Fielding, JeffWilson, vincent, +49.431.98.aaaa, ninjamarnau, Peder_Magee, +385345aabb,
18:28:45 <Zakim> ... vinay, kulick, Keith_Scarborough, hefferjr, Rigo, WileyS, David_MacMillan, Brooks, SusanIsrael, Aleecia, [Microsoft], bryan, adrianba, hwest, Chris_Pedigo, +1.916.985.aacc,
18:28:45 <Zakim> ... RichardWeaver, Chris_IAB, Jonathan_Mayer, Ted_Leung, +1.646.654.aadd, eberkower, +1.646.825.aaee, +1.919.349.aaff, AnnaLong?, johnsimpson, +33.6.50.34.aagg
18:28:49 <Zakim> -eberkower
18:28:57 <npdoty> rrsagent, draft minutes
18:28:57 <RRSAgent> I have made the request to generate http://www.w3.org/2013/01/23-dnt-minutes.html npdoty
18:29:13 <Zakim> -Aleecia
18:29:31 <npdoty> Zakim, bye
18:29:31 <npdoty> rrsagent, bye
18:29:31 <RRSAgent> I see 2 open action items saved in http://www.w3.org/2013/01/23-dnt-actions.rdf :
18:29:31 <RRSAgent> ACTION: schunter to review which requirements in the spec would be problematic for an intermediary [1]
18:29:31 <RRSAgent>   recorded in http://www.w3.org/2013/01/23-dnt-irc#T17-47-39
18:29:31 <RRSAgent> ACTION: singer to add service provider option text (with jmayer) as an issue in the draft with an option box [2]
18:29:31 <RRSAgent>   recorded in http://www.w3.org/2013/01/23-dnt-irc#T18-07-57
18:29:31 <Zakim> leaving.  As of this point the attendees were npdoty, efelten_, schunter, yianni, dwainberg, Fielding, JeffWilson, vincent, +49.431.98.aaaa, ninjamarnau, Peder_Magee, +385345aabb,
18:29:31 <Zakim> Zakim has left #dnt
18:29:34 <Zakim> ... vinay, kulick, Keith_Scarborough, hefferjr, Rigo, WileyS, David_MacMillan, Brooks, SusanIsrael, Aleecia, [Microsoft], bryan, adrianba, hwest, Chris_Pedigo, +1.916.985.aacc,
18:29:34 <Zakim> ... RichardWeaver, Chris_IAB, Jonathan_Mayer, Ted_Leung, +1.646.654.aadd, eberkower, +1.646.825.aaee, +1.919.349.aaff, AnnaLong?, johnsimpson, +33.6.50.34.aagg