from November 2011 by subject


"cross-site" (tags: ISSUE-17, ISSUE-51)

[ACTION-20] First parties signaling exceptions to third parties

[comment] Names and Titles of specifications

[editorial comment] Link from Conformance spec to DNT spec

[ISSUE-81, ACTION-13] Response Header Format

[tracking-syntax] DOM Interface NavigatorDoNotTrack

Action 13 - Mandatory Server Response

Action 31 - Propose a user-agent managed site-specific exception

Action 32 -- Proposed language for site-specific exception

Action-17: Closed

Agenda for 2011-11-09 TPWG call

Agenda for 2011-11-23 TPWG call

Agenda: Tracking Protection WG Meeting 2011-10-31 & 11-01

clean up

compliance spec revisions

Doodle poll for third face-to-face meeting

For those following device finger-printing ad issues

Frequently asked questions

Fwd: TPAC Updates (2 November)

FYI: Do-not-track and third-party login

fyi: Research Report on Usability of DNT Preference Management

Headers modified along the way against user (non) choices

ISSUE 17: Data use by 1st Party

ISSUE-100: What is a user?

ISSUE-101: What is a user? add to defns

ISSUE-103: We're not sure where the exceptions should be and ensure they are categorically captured in the base 3rd party prohibition statement.

Issue-17, Issue-51 First party obligations

Issue-17, Issue-51 First party obligations; Issue-5 Definition of Tracking


Issue-77 and the Tracking Compliance and Scope spec

ISSUE-95: May an institution or network provider set a tracking preference for a user?

Issue-95: User Setting DNT Response (Draft)

ISSUE-98: Should we consider applicable laws and regulations, such as the Article 5, paragraph 3 ePriv Dir

Issues with Identity providers

New input document: DAA Self-Regulatory Principles for Multi-Site Data


Press around the publication of first WDs

Proposed Agenda for 2011-11-16 TPWG call

Proposed Agenda for 2011-11-30 TPWG call

Response Header/URI Hybrid [Its aliiive!]

Summary of First Party vs. Third Party Tests

Summary of Options for 1P Learning of 3P DNT Status

tainted uris and tracking Re: "cross-site"

tainted uris in document and HTTP redirection

Third f2f meeting

TPE add mention of regulations to goals

TPE as approved for FPWD

TPE Document S3

TPE Document, S2.3 P1

TPE is ready for review

TPE paragraph to describe section on Plug-in APIs

TPE removing first vs third-party issues

TPE site-specific exemption

tracking-ISSUE-102: Short names & titles of specifications [Tracking Definitions and Compliance]

tracking-ISSUE-104: Could use a better defn of user agent, rather than browser [Tracking Definitions and Compliance]

tracking-ISSUE-99: How does DNT work with identity providers? [Tracking Definitions and Compliance]

Use Case of Performance Tracing Software

User intended interactions [1st & 3rd Parties]

Last message date: Wednesday, 30 November 2011 23:28:46 UTC