RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request


I agree the issues are intertwined.  The first issue is covered by ISSUE-143.

In the second issue, the functional difference is the user proactively sets their UA to never allow an exception versus it being there by default (step 1 - turn on DNT, step 2 - proactively select an option that says "NEVER allow an exception to DNT").  This of course suggests that (1) a user understands what DNT truly means prior to activating it and (2) understands what the exception process entails.  Even in a scenario where users are making active and informed choices, specific to item #2 - shouldn't servers know this state PRIOR to requesting an exception?  Should there be a new flag in the header request that states "DNT:1!" - DNT:1 and user will not accept exception requests.  This at least speeds the discussion between the Server and the User.  

- Shane

-----Original Message-----
From: David Singer [] 
Sent: Monday, March 18, 2013 5:40 PM
To: (
Subject: Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request

On Mar 18, 2013, at 9:14 , Shane Wiley <> wrote:

> Matthias,
> For a balanced ecosystem with equal rights for publishers and user agents, I believe this should be a MUST.  Otherwise, as we've already begun to see in the real-world, network devices and appendages will begin to set DNT:1 outside of user control and in some cases, knowledge.  I also believe this is highly tied to Issue-143 which attempts to solve for a similar issue.

I think you have two different issues here.  Can other network devices and appendages set DNT:1 without the user's knowledge/desire/consent?  I think we're clear: no; but if we want to tighten this up, we can.

Must user-agents implement the API?  If someone could explain to me the functional difference between:
* user-agent does not implement the exception API
* user-agent does, but the user has told it never to accept an exception

I don't believe that there is any.

I also think that the model that the exception is implemented by the user-agent, but the header comes from their configuration of their proxy/router, works and ought to be OK. Between them, they cover it.

David Singer
Multimedia and Software Standards, Apple Inc.

Received on Tuesday, 19 March 2013 04:01:53 UTC