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

agenda 9 May 2012

From: Aleecia M. McDonald <aleecia@aleecia.com>
Date: Wed, 9 May 2012 02:29:08 -0700
Message-Id: <010AF5C2-EE91-47AB-8985-0F9ED17DE9D6@aleecia.com>
To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Chair: Aleecia


1. Selection of scribe
2. Any comments on minutes (as Nick posted on May 1, plus the last one posted yesterday)

3. Review of overdue action items, sorted to save time:	https://www.w3.org/2011/tracking-protection/track/actions/overdue?sort=owner

New business
4. Discussion of dropping unidentified callers on conference calls

5. Revisiting press policy
	We currently have a standing decision not to invite press as observers to meetings, and not to invite press to join conference calls. This was based on concerns with corporate policies that do not allow all TPWG members to speak in front of press, with no dissent voiced at the previous times of discussion. Dissent has emerged. We will briefly revisit to see if there is new information that the working group has not considered. If not, this will be a very quick discussion, with our current policy standing. 

6. Open issues with no associated actions to draft text, looking for initial discussion for -97 and -99 and volunteers:
	ISSUE-65, How does logged in and logged out state work  /* I was quite sure we had action items on this from the DC f2f, but now I see none */
	ISSUE-97, Re-direction, shortened URLs, click analytics -- what kind of tracking is this?
	ISSUE-99, How does DNT work with identity providers?

7. Pending review text: 
	Ian's text for ACTION-190 and ISSUE-142, Allowed uses of protocol data in first N weeks. (Revised text after discussion is included at the end of this message for convenience, since it wasn't quite in one place after revision)

8. Pending review text:
	Rigo's text for ACTION-141, regarding user agents
	(Rigo's text: http://lists.w3.org/Archives/Public/public-tracking/2012Mar/0045.html
	Shane suggests a modification: http://lists.w3.org/Archives/Public/public-tracking/2012Mar/0047.html )

9. Pending review text:
	Text for ACTION-191 and ACTION-192, Update logged-in consent proposal 
	(Shane's original text, http://lists.w3.org/Archives/Public/public-tracking/2012Apr/0199.html; 
	suggested non-normative revisions from Justin  in http://lists.w3.org/Archives/Public/public-tracking/2012May/0114.html; 
	additional normative suggestions from Jonathan in http://lists.w3.org/Archives/Public/public-tracking/2012May/0116.html; 
	Shane's second approach of leaving to local laws, http://lists.w3.org/Archives/Public/public-tracking/2012May/0118.html;
	Roy's proposal, 3rd paragraph from the end, http://lists.w3.org/Archives/Public/public-tracking/2012May/0125.html )


10. Announce next meeting & adjourn

================ Infrastructure =================

Zakim teleconference bridge:
VoIP:    sip:zakim@voip.w3.org
Phone +1.617.761.6200 passcode TRACK (87225)
IRC Chat: irc.w3.org, port 6665, #dnt

Ian's text on action-190:

Protocol data, meaning data that is transmitted by a user agent, such as a web browser, in the process of requesting content from a provider, explicitly including items such as IP addresses, cookies, and request URIs, MAY be stored for a period of 6 weeks in a form that might not otherwise satisfy the requirements of this specification. For instance, the data may not yet be reduced to the subset of information allowed to be retained for permitted uses (such as fraud detection), and technical controls limiting access to the data for permitted uses may not be in place on things like raw logs data sitting on servers waiting for processing and aggregation into a centralized logs storage service.

Within this six week period, a data collector MUST NOT share data with other parties in a manner that would be prohibited outside of the six week period. Similarly, a data collector MUST NOT use the data to build any profile, or associate the data to any profile, of a user used for purposes other than would be allowed outside of the the six week period. As examples, a data collector MAY use the raw data within a six week period to debug their system, a data collector MAY use the raw data within the six week period to build a profile of a user fraudulently or maliciously accessing the system for purposes such as blocking access to the system by that user, but the data collector MUST NOT build a profile to serve targeted advertisements based on the user's past six weeks of browsing activity.

After the six week period has passed, all other requirements of the DNT specification apply.


Received on Wednesday, 9 May 2012 09:29:40 UTC

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