ISSUE-197: How do we notify the user why a Disregard signal is received?

Ninja Marnau

How do we notify the user why a Disregard signal is received?

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Opened on:
2013-05-07
Description:
This discusses the "D" flag (disregard)
Related Actions Items:
Related emails:
  1. Re: Possibly closing ISSUE-197 without a call for objections (from ninja@w3.org on 2014-01-21)
  2. Re: Possibly closing ISSUE-197 without a call for objections --- delete last sentence (from singer@apple.com on 2014-01-15)
  3. Re: Possibly closing ISSUE-197 without a call for objections --- delete last sentence (from jbrookman@cdt.org on 2014-01-15)
  4. Re: Possibly closing ISSUE-197 without a call for objections (from dwainberg@appnexus.com on 2014-01-15)
  5. Possibly closing ISSUE-197 without a call for objections (from jbrookman@cdt.org on 2014-01-15)
  6. Re: Agenda for January 15 (from singer@apple.com on 2014-01-14)
  7. Agenda for January 15 (from ninja@w3.org on 2014-01-14)
  8. Re: [resend] re-phrasing the note in Disregard; ISSUE-197 (from ninja@w3.org on 2014-01-08)
  9. Re: Agenda for January 8, 2014 call (from rob@blaeu.com on 2014-01-08)
  10. Re: Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-08)
  11. Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-07)
  12. Agenda for December 18, 2013 call (from ninja@w3.org on 2013-12-17)
  13. Re: Batch closing of TPE issues (Deadline: December 03) (from mts-std@schunter.org on 2013-12-17)
  14. Re: Your concerns with ISSUE_197? (from dwainberg@appnexus.com on 2013-12-11)
  15. Re: Your concerns with ISSUE_197? (from mts-std@schunter.org on 2013-12-09)
  16. Re: Your concerns with ISSUE_197? (from dwainberg@appnexus.com on 2013-12-09)
  17. RE: Batch closing of TPE issues (Deadline: December 03) (from bs3131@att.com on 2013-12-05)
  18. RE: Batch closing of TPE issues (Deadline: December 03) (from wileys@yahoo-inc.com on 2013-12-05)
  19. Your concerns with ISSUE_197? (from mts-std@schunter.org on 2013-12-04)
  20. Concerns with ISSUE-161 (from mts-std@schunter.org on 2013-12-04)
  21. RE: Batch closing of TPE issues (Deadline: December 03) (from michael.oneill@baycloud.com on 2013-12-04)
  22. RE: Batch closing of TPE issues (Deadline: December 03) (from bs3131@att.com on 2013-12-04)
  23. Re: Batch closing of TPE issues (Deadline: December 03) (from kulick@yahoo-inc.com on 2013-12-04)
  24. Updated Agenda for December 04, 2013 call - V02 (from ninja@w3.org on 2013-12-03)
  25. Re: Batch closing of TPE issues (Deadline: December 03) (from dwainberg@appnexus.com on 2013-12-03)
  26. Re: Batch closing of TPE issues (Deadline: December 03) (from jack@networkadvertising.org on 2013-12-03)
  27. Re: Batch closing of TPE issues (Deadline: December 03) (from mts-std@schunter.org on 2013-12-03)
  28. Re: Batch closing of TPE issues (Deadline: December 03) (from kulick@yahoo-inc.com on 2013-11-21)
  29. Re: Batch closing of TPE issues (Deadline: December 03) (from singer@apple.com on 2013-11-15)
  30. Re: Batch closing of TPE issues (Deadline: December 03) (from jack@networkadvertising.org on 2013-11-14)
  31. Re: Batch closing of TPE issues (Deadline: December 03) (from mts-std@schunter.org on 2013-11-14)
  32. Re: Batch closing of TPE issues (Deadline: December 03) (from achapell@chapellassociates.com on 2013-11-14)
  33. Batch closing of TPE issues (Deadline: December 03) (from mts-std@schunter.org on 2013-11-14)
  34. ISSUE-197: How do we notify the user why a Disregard signal is received? (from sysbot+tracker@w3.org on 2013-05-07)

Related notes:

[npdoty]: might already be covered, in TPE, by existing text

7 May 2013, 18:53:45

apparently was closed by mistake. See http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_Disregard_signal

Roy Fielding, 15 Jan 2014, 17:23:12

See my email for final consensus text: http://lists.w3.org/Archives/Public/public-tracking/2014Jan/0099.html

Ninja Marnau, 21 Jan 2014, 13:35:53

Changed status to open by request of TPE editors:

Consensus definition:
A tracking status value of D means that the origin server is unable or unwilling to respect a tracking preference received from the requesting user agent. An origin server that sends this tracking status value must detail within the server's corresponding privacy policy the conditions under which a tracking preference might be disregarded.

For example, an origin server might disregard the DNT field received from specific user agents (or via specific network intermediaries) that are deemed to be non-conforming, might be collecting additional data from specific source network locations due to prior security incidents, or might be compelled to disregard certain DNT requests to comply with a local law, regulation, or order.

Note: This specification was written assuming that the D tracking status value would only be used in situations that can be adequately described to users as an exception to normal behavior. If this turns out not to be the case, either the logic that is leading to the D signal may need re-examination, or this specification, or both.

Ninja Marnau, 22 Jan 2014, 15:24:28

incorporated in TPE in r1.239 with a minor editorial tweak

Roy Fielding, 13 Mar 2014, 07:50:21

As we are approaching Last Call with the TPE spec

Ninja Marnau, 9 Apr 2014, 15:22:23

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 197.html,v 1.1 2019/02/01 09:32:34 vivien Exp $