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

Ninja Marnau

User Agent Requirement: Be able to handle an exception request

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Rigo Wenning
Opened on:
2012-06-06
Description:
There is software that in just a few lines of code just spawn DNT;1 or DNT;0 headers regardless of user's will. A requirement on the user agent that they can handle the full exception mechanism will allow to discard compliance statements by those agents. It will also allow also the site to test for conformance by requiring an exception. In case the UA does not react on an exception request, the server could ignore DNT signals from that UA. It would allow thus testing from the horizon of the site without wild guessing

Change proposals being collected: http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_UA_requirement_to_handle_exceptions
Related Actions Items:
Related emails:
  1. RE: [TCS] comments on 17 Feb 2015 editors draft (from michael.oneill@baycloud.com on 2015-03-21)
  2. Re: [TCS] comments on 17 Feb 2015 editors draft (from wileys@yahoo-inc.com on 2015-03-16)
  3. Re: [TCS] comments on 17 Feb 2015 editors draft (from michael.oneill@baycloud.com on 2015-03-12)
  4. Re: tracking-ISSUE-261: requirement on UAs for user-granted exceptions [TPE Last Call] (from fielding@gbiv.com on 2014-09-09)
  5. Call for Objection results (ISSUES 151 and 153) (from jbrookman@cdt.org on 2014-05-14)
  6. Re: Agenda for February 12 call (from ninja@w3.org on 2014-02-11)
  7. Re: Agenda for February 12 call (from john@consumerwatchdog.org on 2014-02-11)
  8. Agenda for February 12 call (from ninja@w3.org on 2014-02-11)
  9. Re: Agenda for January 21 call (from singer@apple.com on 2014-01-22)
  10. Agenda for January 21 call (from ninja@w3.org on 2014-01-21)
  11. Re: Agenda for January 15 (from singer@apple.com on 2014-01-14)
  12. Agenda for January 15 (from ninja@w3.org on 2014-01-14)
  13. Re: existing text on ISSUE-151 (from npdoty@w3.org on 2014-01-14)
  14. Re: existing text on ISSUE-151 (from walter.van.holst@xs4all.nl on 2014-01-12)
  15. Re: existing text on ISSUE-151 (from npdoty@w3.org on 2014-01-11)
  16. Re: Call for Objections on ISSUE-151 (from john@consumerwatchdog.org on 2014-01-08)
  17. Call for Objections on ISSUE-151 (from jbrookman@cdt.org on 2014-01-08)
  18. Re: Agenda for January 8, 2014 call (from rob@blaeu.com on 2014-01-08)
  19. Re: Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-08)
  20. Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-07)
  21. Re: Issue-151: Proposed Text (Updated) (from walter.van.holst@xs4all.nl on 2013-12-24)
  22. RE: Issue-151: Proposed Text (Updated) (from wileys@yahoo-inc.com on 2013-12-23)
  23. Re: Issue-151: Proposed Text (Updated) (from tien@eff.org on 2013-12-23)
  24. RE: Issue-151: Proposed Text (Updated) (from michael.oneill@baycloud.com on 2013-12-23)
  25. Re: Issue-151: Proposed Text (Updated) (from john@consumerwatchdog.org on 2013-12-23)
  26. Re: Issue-151: Proposed Text (Updated) (from achapell@chapellassociates.com on 2013-12-23)
  27. Re: Issue-151: Proposed Text (Updated) (from tien@eff.org on 2013-12-23)
  28. RE: Issue-151: Proposed Text (Updated) (from wileys@yahoo-inc.com on 2013-12-23)
  29. Re: Issue-151: Proposed Text (Updated) (from tien@eff.org on 2013-12-23)
  30. Issue-151: Proposed Text (Updated) (from wileys@yahoo-inc.com on 2013-12-23)
  31. Agenda for December 18, 2013 call (from ninja@w3.org on 2013-12-17)
  32. Re: Agenda for December 11, 2013 call (from jbrookman@cdt.org on 2013-12-10)
  33. Re: Agenda for December 11, 2013 call (from john@consumerwatchdog.org on 2013-12-10)
  34. RE: Agenda for December 11, 2013 call (from wileys@yahoo-inc.com on 2013-12-10)
  35. Agenda for December 11, 2013 call (from ninja@w3.org on 2013-12-10)
  36. Re: any additional Proposals on UA requirement to handle exceptions (from npdoty@w3.org on 2013-12-09)
  37. Re: any additional Proposals on UA requirement to handle exceptions (from jack@networkadvertising.org on 2013-12-05)
  38. Re: any additional Proposals on UA requirement to handle exceptions (from john@consumerwatchdog.org on 2013-12-05)
  39. Re: any additional Proposals on UA requirement to handle exceptions (from Brooks.Dobbs@kbmg.com on 2013-12-05)
  40. Re: any additional Proposals on UA requirement to handle exceptions (from achapell@chapellassociates.com on 2013-12-05)
  41. RE: any additional Proposals on UA requirement to handle exceptions (from wileys@yahoo-inc.com on 2013-12-05)
  42. any additional Proposals on UA requirement to handle exceptions (from npdoty@w3.org on 2013-12-04)
  43. Concerns with ISSUE-161 (from mts-std@schunter.org on 2013-12-04)
  44. On Issue-151, site use of exceptions API (from singer@apple.com on 2013-12-04)
  45. Updated Agenda for December 04, 2013 call - V02 (from ninja@w3.org on 2013-12-03)
  46. Draft Agenda for December 04, 2013 call - V01 (from mts-std@schunter.org on 2013-12-03)
  47. Re: Issue-151 (from john@consumerwatchdog.org on 2013-11-20)
  48. Re: Issue-151 (from npdoty@w3.org on 2013-11-20)
  49. RE: Issue-151 (from wileys@yahoo-inc.com on 2013-11-20)
  50. Re: Issue-151 (from john@consumerwatchdog.org on 2013-11-20)
  51. Issue-151 (from wileys@yahoo-inc.com on 2013-11-20)
  52. Agenda for November 20, 2013 call (from mts-std@schunter.org on 2013-11-19)
  53. resend: Call for text proposals on ISSUE-151 (by next Wednesday) (from mts-std@schunter.org on 2013-11-18)
  54. Re: Call for text proposals on ISSUE-151 (by next Wednesday) (from mts-std@schunter.org on 2013-11-14)
  55. Re: Call for text proposals on ISSUE-151 (by next Wednesday) (from john@consumerwatchdog.org on 2013-11-14)
  56. Call for text proposals on ISSUE-151 (by next Wednesday) (from mts-std@schunter.org on 2013-11-14)
  57. Agenda for November 13, 2013 call (from mts-std@schunter.org on 2013-11-12)
  58. Re: Agenda for November 13, 2013 call (from singer@apple.com on 2013-11-12)
  59. Agenda for November 13, 2013 call (from jbrookman@cdt.org on 2013-11-11)
  60. Re: issue-151 (from peter.cranstone@3pmobile.com on 2013-09-02)
  61. Re: issue-151 (from michael.oneill@baycloud.com on 2013-09-02)
  62. FW: issue-151 (from michael.oneill@baycloud.com on 2013-09-02)
  63. Re: issue-151 (from peter.cranstone@3pmobile.com on 2013-09-02)
  64. Re: issue-151 (from rigo@w3.org on 2013-09-02)
  65. Re: issue-151 (from peter.cranstone@3pmobile.com on 2013-09-02)
  66. re: issue-151 (from michael.oneill@baycloud.com on 2013-09-02)
  67. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-08-04)
  68. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-29)
  69. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-29)
  70. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-29)
  71. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-29)
  72. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from aleecia@aleecia.com on 2013-07-28)
  73. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from wileys@yahoo-inc.com on 2013-07-28)
  74. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-28)
  75. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-28)
  76. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from achapell@chapellassociates.com on 2013-07-28)
  77. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from wileys@yahoo-inc.com on 2013-07-28)
  78. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from wileys@yahoo-inc.com on 2013-07-28)
  79. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-28)
  80. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-28)
  81. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-28)
  82. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-28)
  83. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from aleecia@aleecia.com on 2013-07-28)
  84. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-28)
  85. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from peter.cranstone@3pmobile.com on 2013-07-27)
  86. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from wileys@yahoo-inc.com on 2013-07-27)
  87. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-27)
  88. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-27)
  89. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from peter.cranstone@3pmobile.com on 2013-07-27)
  90. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-27)
  91. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-27)
  92. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from peter.cranstone@3pmobile.com on 2013-07-27)
  93. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-27)
  94. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from peter.cranstone@3pmobile.com on 2013-07-27)
  95. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from michael.oneill@baycloud.com on 2013-07-27)
  96. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-26)
  97. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from peter.cranstone@3pmobile.com on 2013-07-26)
  98. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from chris.mejia@iab.net on 2013-07-26)
  99. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rob@blaeu.com on 2013-07-25)
  100. Re: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-25)
  101. RE: ISSUE-151 Re: Change proposal: new general principle for permitted uses (from wileys@yahoo-inc.com on 2013-07-25)
  102. ISSUE-151 Re: Change proposal: new general principle for permitted uses (from rigo@w3.org on 2013-07-24)
  103. Re: June Change Proposal: Issues 132, 151, 153 (from npdoty@w3.org on 2013-06-26)
  104. Re: Agenda for June 05 call on TPE (from jmayer@stanford.edu on 2013-06-05)
  105. Agenda for June 05 call on TPE (from mts-std@schunter.org on 2013-06-04)
  106. Re: issue and action cleanup proposals (from jmayer@stanford.edu on 2013-05-21)
  107. Agenda for May 22 call (from peter@peterswire.net on 2013-05-21)
  108. Re: issue and action cleanup proposals (from ylagos@futureofprivacy.org on 2013-05-21)
  109. Re: issue and action cleanup proposals (from jmayer@stanford.edu on 2013-05-19)
  110. issue and action cleanup proposals (from npdoty@w3.org on 2013-05-15)
  111. Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
  112. Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
  113. Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from rigo@w3.org on 2013-03-22)
  114. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from mts-std@schunter.org on 2013-03-20)
  115. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from jmayer@stanford.edu on 2013-03-19)
  116. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from singer@apple.com on 2013-03-19)
  117. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from jmayer@stanford.edu on 2013-03-19)
  118. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from singer@apple.com on 2013-03-19)
  119. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from jmayer@stanford.edu on 2013-03-19)
  120. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from singer@apple.com on 2013-03-19)
  121. Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from rob@blaeu.com on 2013-03-19)
  122. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from jmayer@stanford.edu on 2013-03-19)
  123. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from mts-std@schunter.org on 2013-03-19)
  124. RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from wileys@yahoo-inc.com on 2013-03-19)
  125. Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from jmayer@stanford.edu on 2013-03-18)
  126. Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from singer@apple.com on 2013-03-18)
  127. the Flu (was: Proposed Resolution to ISSUE-151 : User Agent Requirement) (from singer@apple.com on 2013-03-18)
  128. RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from wileys@yahoo-inc.com on 2013-03-18)
  129. Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22] (from mts-std@schunter.org on 2013-03-18)
  130. RE: ACTION-364: Draft section on best practices for sites requesting exceptions (from michael.oneill@baycloud.com on 2013-03-18)
  131. Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from mts-std@schunter.org on 2013-03-18)
  132. Revision on agenda -- deID decisions now on Tuesday (from peter@peterswire.net on 2013-02-04)
  133. Agenda update for Monday and Tuesday in Cambridge (compliance spec) (from peter@peterswire.net on 2013-02-04)
  134. Re: TPWG agenda for Wednesday, January 16 (from jmayer@stanford.edu on 2013-01-30)
  135. Re: TPWG agenda for Wednesday, January 16 (from singer@apple.com on 2013-01-29)
  136. Re: action-231, issue-153 requirements on other software that sets DNT headers (from tisrael@cippic.ca on 2012-08-22)
  137. agenda: 25 July 2012 call (from aleecia@aleecia.com on 2012-07-24)
  138. Re: Prototype of Do Not Track Exceptions (ISSUE-151) (from peter.cranstone@gmail.com on 2012-07-02)
  139. Re: Prototype of Do Not Track Exceptions (ISSUE-151) (from rigo@w3.org on 2012-07-02)
  140. RE: Prototype of Do Not Track Exceptions (from Vincent.Toubiana@alcatel-lucent.com on 2012-07-02)
  141. Today's call: summary on user agent compliance (from aleecia@aleecia.com on 2012-06-06)
  142. tracking-ISSUE-151 (UA-exception-req): User Agent Requirement: Be able to handle an exception request [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-06-06)

Related notes:

Noted during issue cleanup, this may be a sub-issue of issue-194 around user consent.

Nick Doty, 29 May 2013, 02:17:20

Change to pending Review. Open Call for Objections: https://www.w3.org/2002/09/wbs/49311/tpwg-exception-151/

Ninja Marnau, 21 Jan 2014, 13:39:20

Changed status to open to make editors' work easier

Ninja Marnau, 22 Jan 2014, 14:23:14

Option A was determined as the least objectionable option (http://www.w3.org/2014/02/12-dnt-minutes#item02) in this Call for Objections (https://www.w3.org/2002/09/wbs/49311/tpwg-exception-151/results).

Ninja Marnau, 11 Mar 2014, 20:34:59

CfO decision is to leave text as is, so no need for further review.

Roy Fielding, 13 Mar 2014, 07:42:05

Changelog:

Created issue 'User Agent Requirement: Be able to handle an exception request' nickname UA-exception-req owned by Rigo Wenning on product Tracking Preference Expression (DNT), description 'There is software that in just a few lines of code just spawn DNT;1 or DNT;0 headers regardless of user's will. A requirement on the user agent that they can handle the full exception mechanism will allow to discard compliance statements by those agents. It will also allow also the site to test for conformance by requiring an exception. In case the UA does not react on an exception request, the server could ignore DNT signals from that UA. It would allow thus testing from the horizon of the site without wild guessing' non-public

Rigo Wenning, 6 Jun 2012, 16:38:26

Status changed to 'open'

Matthias Schunter, 30 Jan 2013, 21:34:56

Status changed to 'pending review'

Matthias Schunter, 19 Jun 2013, 21:38:55

Status changed to 'open'

Matthias Schunter, 19 Jun 2013, 22:13:57

Description changed to 'There is software that in just a few lines of code just spawn DNT;1 or DNT;0 headers regardless of user's will. A requirement on the user agent that they can handle the full exception mechanism will allow to discard compliance statements by those agents. It will also allow also the site to test for conformance by requiring an exception. In case the UA does not react on an exception request, the server could ignore DNT signals from that UA. It would allow thus testing from the horizon of the site without wild guessing

Change proposals being collected: http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_UA_requirement_to_handle_exceptions'

Nick Doty, 20 Nov 2013, 23:18:05

nickname changed to 'Ninja Marnau'

Ninja Marnau, 21 Jan 2014, 13:39:20

Status changed to 'pending review'

Ninja Marnau, 21 Jan 2014, 13:39:46

Status changed to 'open'

Ninja Marnau, 22 Jan 2014, 14:23:14

Status changed to 'closed'

Roy Fielding, 13 Mar 2014, 07:42:05


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, 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: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $