Summary of progress on Issue 59

While it is in the minutes, I want to record our progress attached directly to ISSUE-59 -- Should the first party be informed about whether the user has sent a DNT header to third parties on their site? 

What I heard on the call today:
	- We have consensus that it would be good and useful for a first party to know if a third party on their site is getting a DNT signal.

		- Concern 1: don't want this to turn into liability for the first party, which is not how this communication is envisioned. We would do well to note this intent in the recommendation to avoid ambiguity. This concern is currently resolved. 
		- Concern 2: one of the use cases for this issue was to enable a first party to present a pay wall to users if there's a DNT signal to a third party. This concern remains, but is not limited to just ISSUE-59. There is a larger concern about how users are treated, since first parties could also put up pay walls just based on seeing DNT themselves with no need for communication of 3rd party DNT status. I've gone ahead and recorded this as ISSUE-93, on behalf of Carmen. With that as a larger issue still to address, there is no particular objection to first parties knowing third party DNT status, so this concern is not in play here.
		- Concern 3: don't want a major implementation nightmare, particularly if this becomes a MUST requirement. This concern was more widely held. Resolution for now: we will work through some options of how we might implement, see how trivial or difficult that would be, and then return to this with more information.

And that is where we stand, with action-17 and action-18 for Shane and Jonathan to write options for implementation. Thanks for taking those actions. And this email summary allows me to close action-19 against myself, in summarizing where we stand on issue 59.

	Aleecia

Received on Wednesday, 19 October 2011 19:16:08 UTC