Edit comment LC-2593 for Tracking Protection Working Group

Quick access to LC-2589 LC-2590 LC-2591 LC-2593

Comment LC-2593

Comment Shortname:

Commenter: John Simpson <john@consumerwatchdog.org> on behalf of Do-Not-Track Community Group

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeThis specification defines the technical mechanisms for expr... Notational Conventions Requirements The key words must, mu... Requirements The key words must, must not, required, should... Formal Syntax This specification uses Augmented Backus-Naur... Terminology This specification uses the term user agent to... Determining User Preference The goal of this protocol is to... Expressing a Tracking Preference When a user has enabled a... DNT request header field The DNT header field is hereby def... HTML DOM Interfaces The NavigatorDoNotTrack interface provi... Plug-In APIs User agents often include user-installable com... Communicating a Tracking Status The companion document, Tra... Goals The following goals have been identified as reasons f... Criteria The following criteria have been identified as con... Options There have been many suggestions, but not much cons... Machine-readable Tracking Policy This can be defined as eit... Tracking response header field sent on all responses? sent... Proposal 1 (Tom, Heather, Ian) This response header proposa... Status code for Tracking Required An HTTP error response st... User-agent-managed site-specific exceptions ISSUE-43: Sites... Overview In this proposal, exceptions to Do Not Track, incl... Motivating principles and use cases The following principle... JavaScript API to prompt for exceptions A JavaScript API al... Exception management user interface A user agent might prov... Behavior for future requests with site-specific exceptions... Web-wide exceptions Users may also wish to configure except... User interface guidelines Implementers should keep in mind... Fingerprinting concerns By storing a client-side configurab... Example permission flows No Site-Specific Exception User a... Use case: Site-specific exceptions should persist It would... Closed Issues ISSUE-2: What is the meaning of DNT (Do Not T... Postponed Issues ISSUE-44: Ability to measure/detect who is...
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Auerbach, Dan Bateman, Adrian Berkower, Elise Bian, Chao Bielova, Nataliia Bos, Bert Bowman, Neil Brioche, Rudy Caprio, Dan Cargill, Carl Chao, Qu Chester, Jeffrey Colando, Amy Cunche, Mathieu Doty, Nick Fette, Ian Fielding, Roy Gao, Hanrui Glueck, Sue Gombert, Alanna Grant, Euan Hall, Joseph Harvey, Sean Heffernan, Ronan Hu, Bin Israel, Susan Jaffe, Daniel Jaffe, Jeff Krauss, Simon Kulick, Brad Kwong, Kennie Li, Jessica McDonald, Aleecia Min, Yue Neuenschwander, Erik O'Connor, Theresa O'Neill, Mike Riordan-Butterworth, Brendan Scarborough, Keith Schauf, Thomas Schunter, Matthias Seltzer, Wendy Sherman, Rob Singer, David Smith, Kevin Smith, Michael[tm] Sullivan, Bryan Tao, Weihua tian, caten Tien, Lee Toner, Alan Toubiana, Vincent Turransky, Alan van Eijk, Rob van Holst, Walter Wagner, Frank West, Heather West, Heather Wiley, Shane Wu, Jing Yan, Xuemei Zhang, Yuanzhou Zhao, Yangguang Zhou, Horace

Type: substantive editorial typo question general comment undefined

Comment:

These issues appear related. We strongly prefer that DNT settings persist across sessions until modified by the user. We do not object to the standard’s permissiveness here as a technical matter—when the DNT header is sent, servers need not “remember” previous sessions—but DNT will be significantly more valuable to users, and will better meet users’ expectations, if DNT need not reset each time users visit a website. A non-normative reference about the value of persistence may be appropriate here.

Related issues: (space separated ids)

WG Notes:

Resolution:

(Please make sure the resolution is adapted for public consumption)