ISSUE-199: Limitations on the use of unique identifiers

unique-id

Limitations on the use of unique identifiers

State:
OPEN
Product:
Compliance Current
Raised by:
Nick Doty
Opened on:
2013-05-29
Description:
Note change proposal: http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Unique_Identifiers

As noted at the Sunnyvale face-to-face (and previously), the question of what limits would be present on the use of unique identifiers (for example, tracking cookies with unique IDs) for Do Not Track users has been highlighted, in particular by advocates.

This is already an ongoing discussion, and there is at least one alternative directed to it in the working/editors' draft.
Related Actions Items:
No related actions
Related emails:
  1. Batch closing of old issues (from jbrookman@cdt.org on 2015-03-24)
  2. Re: Data minimization (ISSUE-31) (from fielding@gbiv.com on 2014-07-16)
  3. Agenda for July 9 TPWG call (from npdoty@w3.org on 2014-07-08)
  4. Re: Agenda for June 25 TPWG call (from sstamm@mozilla.com on 2014-06-25)
  5. Agenda for June 25 TPWG call (from ninja@w3.org on 2014-06-24)
  6. Agenda for June 18 TPWG call (from ninja@w3.org on 2014-06-17)
  7. Re: Agenda for June 11 TPWG call (from singer@apple.com on 2014-06-10)
  8. Agenda for June 11 TPWG call (from ninja@w3.org on 2014-06-09)
  9. Agenda for June 4 TPWG call (from ninja@w3.org on 2014-06-02)
  10. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from wileys@yahoo-inc.com on 2013-10-08)
  11. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from michael.oneill@baycloud.com on 2013-10-08)
  12. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from wileys@yahoo-inc.com on 2013-10-08)
  13. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from michael.oneill@baycloud.com on 2013-10-08)
  14. Re: Further text associated with the change proposal on Unique Identifiers, issue-199 (from dwainberg@appnexus.com on 2013-10-08)
  15. Re: Further text associated with the change proposal on Unique Identifiers, issue-199 (from joe@cdt.org on 2013-10-08)
  16. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from michael.oneill@baycloud.com on 2013-10-08)
  17. RE: Further text associated with the change proposal on Unique Identifiers, issue-199 (from wileys@yahoo-inc.com on 2013-10-07)
  18. Further text associated with the change proposal on Unique Identifiers, issue-199 (from michael.oneill@baycloud.com on 2013-10-02)
  19. Re: Issue:? Fingerprinting (from jeff@democraticmedia.org on 2013-10-02)
  20. Re: Issue:? Fingerprinting (from ggieron@adtruth.com on 2013-10-02)
  21. Re: Issue:? Fingerprinting (from ggieron@adtruth.com on 2013-10-01)
  22. Re: Issue:? Fingerprinting (from joe@cdt.org on 2013-10-01)
  23. Re: Issue:? Fingerprinting (from achapell@chapellassociates.com on 2013-10-01)
  24. Re: Issue:? Fingerprinting (from jeff@democraticmedia.org on 2013-10-01)
  25. RE: Issue:? Fingerprinting (from michael.oneill@baycloud.com on 2013-10-01)
  26. Re: Issue:? Fingerprinting (from achapell@chapellassociates.com on 2013-10-01)
  27. RE: Issue:? Fingerprinting (from michael.oneill@baycloud.com on 2013-10-01)
  28. Compliance document updates for review before next WD publication (was CVS WWW/2011/tracking-protection/drafts) (from npdoty@w3.org on 2013-09-28)
  29. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-12)
  30. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  31. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-11)
  32. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  33. RE: URLS/scoring (from michael.oneill@baycloud.com on 2013-07-11)
  34. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  35. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-11)
  36. Re: URLS/scoring (from felten@CS.Princeton.EDU on 2013-07-11)
  37. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-11)
  38. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  39. RE: URLS/scoring (from michael.oneill@baycloud.com on 2013-07-11)
  40. Re: URLS/scoring (from felten@CS.Princeton.EDU on 2013-07-11)
  41. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  42. Re: URLS/scoring (from julespol@futureofprivacy.org on 2013-07-11)
  43. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  44. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-11)
  45. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  46. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  47. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-11)
  48. Re: URLS/scoring (from paul.ohm@Colorado.EDU on 2013-07-10)
  49. Re: URLS/scoring (from felten@CS.Princeton.EDU on 2013-07-10)
  50. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  51. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  52. Re: URLS/scoring (from jeff@democraticmedia.org on 2013-07-10)
  53. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  54. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  55. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  56. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  57. Re: URLS/scoring (from gelman@blurryedge.com on 2013-07-10)
  58. Re: URLS/scoring (from jeff@democraticmedia.org on 2013-07-10)
  59. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  60. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  61. Re: URLS/scoring (from peter@peterswire.net on 2013-07-10)
  62. Re: URLS/scoring (from jeff@democraticmedia.org on 2013-07-10)
  63. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  64. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  65. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  66. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  67. Re: issue-199 (from rigo@w3.org on 2013-07-10)
  68. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  69. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  70. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  71. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  72. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  73. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  74. Re: URLS/scoring (from jmayer@stanford.edu on 2013-07-10)
  75. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  76. RE: URLS/scoring (from wileys@yahoo-inc.com on 2013-07-10)
  77. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  78. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  79. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  80. Re: URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  81. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  82. Re: URLS/scoring (from rob@blaeu.com on 2013-07-10)
  83. URLS/scoring (from jbrookman@cdt.org on 2013-07-10)
  84. RE: issue-199 (from michael.oneill@baycloud.com on 2013-07-10)
  85. RE: issue-199 (from rob@blaeu.com on 2013-07-10)
  86. Re: issue-199 (from felten@CS.Princeton.EDU on 2013-07-10)
  87. RE: issue-199 (from acolando@microsoft.com on 2013-07-10)
  88. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  89. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  90. Re: issue-199 (from rigo@w3.org on 2013-07-10)
  91. RE: issue-199 (from michael.oneill@baycloud.com on 2013-07-10)
  92. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  93. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  94. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  95. Re: issue-199 (from rigo@w3.org on 2013-07-10)
  96. RE: issue-199 (from michael.oneill@baycloud.com on 2013-07-10)
  97. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  98. RE: issue-199 (from rob@blaeu.com on 2013-07-10)
  99. Re: issue-199 (from singer@apple.com on 2013-07-10)
  100. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  101. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  102. RE: issue-199 (from michael.oneill@baycloud.com on 2013-07-10)
  103. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  104. Re: issue-199 (from singer@apple.com on 2013-07-10)
  105. Re: issue-199 (from rigo@w3.org on 2013-07-10)
  106. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  107. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-10)
  108. Re: issue-199 (from felten@CS.Princeton.EDU on 2013-07-09)
  109. Re: issue-199 (from rigo@w3.org on 2013-07-09)
  110. Re: issue-199 (from john@consumerwatchdog.org on 2013-07-09)
  111. RE: issue-199 (from wileys@yahoo-inc.com on 2013-07-09)
  112. Re: June change proposal: permitted uses (from npdoty@w3.org on 2013-07-08)
  113. Re: June change proposal: permitted uses (from npdoty@w3.org on 2013-07-08)
  114. Re: June change proposal: permitted uses (from dan@eff.org on 2013-07-08)
  115. Re: issue-199 (from rigo@w3.org on 2013-07-03)
  116. Re: issue-199 (from tlr@w3.org on 2013-07-01)
  117. RE: issue-199 (from achapell@chapellassociates.com on 2013-06-30)
  118. RE: issue-199 (from michael.oneill@baycloud.com on 2013-06-30)
  119. RE: issue-199 (from achapell@chapellassociates.com on 2013-06-30)
  120. issue-199 (from michael.oneill@baycloud.com on 2013-06-30)
  121. Re: June change proposal: permitted uses (from npdoty@w3.org on 2013-06-28)
  122. tracking-ISSUE-199 (unique-id): Limitations on the use of unique identifiers [Tracking Definitions and Compliance] (from sysbot+tracker@w3.org on 2013-05-29)

Related notes:

No additional notes.

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: 199.html,v 1.1 2019/02/01 09:32:34 vivien Exp $