W3C home > Mailing lists > Public > public-tracking@w3.org > August 2012

Re: ACTION-222 (Document out-of-band js api)

From: David Wainberg <david@networkadvertising.org>
Date: Wed, 22 Aug 2012 09:43:20 -0400
Message-ID: <5034E1F8.1050100@networkadvertising.org>
To: ifette@google.com
CC: "public-tracking@w3.org Group WG" <public-tracking@w3.org>
Does it even have to change the DNT signal? I'd think all it has to do 
is store the exception -- a single value -- and then transmit back to 
the server the fact than the exception is present. Ideally, it would be 
sent in the header, accompanying the DNT signal. All the logic of what 
to do with it is in the server. The UA doesn't have to think at all 
about the if or when it alters the DNT.

On 7/25/12 11:54 AM, Ian Fette (イアンフェッティ) wrote:
> I think we have two ways to go with an out-of-band consent mechanism. 
> This is largely necessitated in my mind by the fact that a significant 
> percentage of users (mostly because of default browser settings and/or 
> add-ons, but also including some number of users who have explicitly 
> configured their settings in this way) block third party cookies. If 
> third party cookies are blocked, a third party site has no way of 
> remembering that they have an OOB exception, as they can't place a 
> cookie on the computer saying "by the way, this user has granted an 
> OOB exception".
>
> 1. The exception mechanism could do nothing more than switch from 
> DNT:1 to DNT:0 for the site. The browser should probably stay out of 
> the way, UI-wise, and just store the exception when a website notifies 
> the browser that it believes the user has consented to an out-of-band 
> exception. If the browser pops up UI, then it's not really 
> out-of-band. A passive indicator might be fine here such that users 
> who are highly concerned get transparency into the fact that this is 
> happening, but nothing that would require interaction for the 
> out-of-band exception to be stored.
>
> 2. The exception mechanism could do more than switch from DNT:1 to 
> DNT:0, such as enabling third party cookies for that origin (which 
> seems reasonable if the user has opted-in on that site). In this case 
> I would prefer that the UI were still passive (gives people a way to 
> audit what's going on and whack people who are using this 
> inappropriately), but depending on how much additional power is given 
> to a site (just storing cookies, or more?) I could see "active" UI 
> that a user has to interact with being involved here...
>
> Either way, I think we also need to let a site define what it believes 
> is part of the "same party" here. e.g. if a user has given an 
> out-of-band consent to google, we would want to be able to get 
> https://www.google.com and http://www.google.com at the same time, etc.
Received on Wednesday, 22 August 2012 13:43:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:54 UTC