Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20]

Hi David,

Not sure if anyone followed-up on this.  Here is the link to the archives:

As both David W and Shane pointed out, this is still an open issue that we'd like to further discuss.  I don't think its sufficient to allow for the exception to cover the fully qualified domain only.  I know there are some concerns of abuse with the expansion of ICAAN policy, but by limiting the exception to fully qualified domains we'd be limiting significantly how a trusted third party ad services provider could use an exception.

Take the scenario of Acme, a site retargeting advertising firm.  It has three clients that it collects data on; but each client's data is owned by the client; not Acme.  Acme cannot combine/use data from Website A with data from Website B.  Acme uses the domain  For data collected on Website A, it uses; for Website B it uses; for Website C it uses  If Acme is asking for an exception, it needs it to cover all of its retargeting services for each client.  It cannot ask for a separate exception for each of its customers (could be in the hundreds).  By limiting the exception to fully qualified domains only, you would be encouraging retargeting firms to move away from cookie-based silos.

We should change the language of the current draft such that can make an exception request for * or (*.)  I would suggest we allow for a domain to ask for an exception for itself and its subdomains, but restrict how a subdomain can ask for an exception.  Specifically: can ask for an exception for and; can ask for an exception only for  (*), but not

Vinay Goel | Privacy Product Manager | Adobe Systems | Office: 917.934.0867

From: David Singer <<>>
Date: Monday, August 20, 2012 12:59 PM
To: David Wainberg <<>>
Cc: "Matthias Schunter (Intel Corporation)" <<>>, "<> (<>)" <<>>
Subject: Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20]
Resent-From: <<>>
Resent-Date: Monday, August 20, 2012 12:59 PM

On Aug 19, 2012, at 8:32 , David Wainberg <<>> wrote:

ISSUE-112 (How are sub-domains handled for site-specific exceptions?) should not be closed. I agree with Shane's last post on the issue. We should not toss out the *<> model for speculative fear of misuse. And, we have not adequately explored the repercussions of not providing that option. The issue should remain open pending further exploration.

I fear I may have missed Shane's last post.  Do you have a link to it in the archives?  Sorry!

The issue was two-fold.  If we allow suffix names, rather than fully-qualified names, then (a) the matching process is more complex and (b) we need rules such as in cookies to control (against) the use of public suffixes (see These complicate both the specification and the implementation (though it's true that any UA has to do the public suffix control in their cookie code already).



On 8/15/12 12:16 PM, Matthias Schunter (Intel Corporation) wrote:
Hi Team,

in preparation for tomorrow's TPE call, I started assessing the status of our TPE-related ISSUES:

I'd like to thank Roy and David for preparing the next major revision of the TPE spec! They have performed a huge push towards implementing all our prior discussions and draft agreements as updates to the TPE spec. As a consequence, many of our informal agreements are now documented in the text and we have the opportunity to make a large leap towards closing the remaining TPE issues.

Enclosed is a list of issues that I believe satisfy the following criteria:
   - Have been discussed before
   - Proposed text is in TPE spec
   - I believe that all participants can live with the current text

I would like to double-check that my perception is correct and then close these issues.

- Double check that you can live with the proposed resolution and the current corresponding text in the TPE
- Send any comments and clarifying questions to the mailing list
- Send a note if you cannot live with one of the proposed resolutions to the chairs and editors at:<> [In this case, some of the issues will be discussed further]

DEADLINE: August 20
- If I do not get further input on any of the issues below, I plan to close them by August 20


-----------------------------------------8>--- ISSUES to be closed + proposed Resolutions ---------------------
ISSUE-47: Should the response from the server indicate a policy that describes the DNT practices of the server?
- A policy attribute at the well-known URI may point to a site-wide policy (Section 5.4.1)
- The response header may identify a more specific policy at a different URL (Section 5.3.2)
ISSUE-61: A site could publish a list of the other domains that are associated with them
- "partners" attribute at the well-known URI identifies partner sites (Section 5.4.1)
ISSUE-84: Make DNT status available to JavaScript
- Revised text in section 4.3.3
ISSUE-107: Exact format of the response header?
- Revised response header values in Section 5.2 and syntax in 5.3
ISSUE-112: How are sub-domains handled for site-specific exceptions?<>
- Exceptions are granted for fully qualified domain names (Section 6.3.1)
How shall we express responses from a site to a user agent (headers, URIs, ...)?<>
- Well-known URI + Headers where the essential information needs to be provided with one of the mechanisms
ISSUE-128: HTTP error status code to signal that tracking is required?<>
- "409" ;-)
ISSUE-130: User-granted Exceptions b) Web-wide Exception for Third Parties (thisthirdparty, anywhere)<>
- We agreed that web-wide exceptions shall be possible. Text in Section 6.5
ISSUE-155: Remove the received member from tracking status<>
- Removed attribute has been removed
  since we assume reliable communication

David Singer
Multimedia and Software Standards, Apple Inc.

Confidentiality Notice: The contents of this e-mail (including any attachments) may be confidential to the intended recipient, and may contain information that is privileged and/or exempt from disclosure under applicable law. If you are not the intended recipient, please immediately notify the sender and destroy the original e-mail and any attachments (and any copies that may have been made) from your system or otherwise. Any unauthorized use, copying, disclosure or distribution of this information is strictly prohibited. <ACL>

Received on Thursday, 23 August 2012 15:35:29 UTC