W3C home > Mailing lists > Public > public-tracking-commit@w3.org > January 2013

CVS WWW/2011/tracking-protection/drafts

From: CVS User rfieldin <cvsmail@w3.org>
Date: Wed, 30 Jan 2013 21:10:26 +0000
Message-Id: <E1U0evK-0004Vb-Op@gil.w3.org>
To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv17331

Modified Files:
Log Message:
ACTION-359: Add proposal for ISSUE-161 to allow an indicator of non-compliance within the tracking status value for testing and deployment

--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/01/23 07:05:46	1.180
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html	2013/01/30 21:10:26	1.181
@@ -532,10 +532,7 @@
           A <dfn>tracking status value</dfn> is a short notation for
           communicating how a designated resource conforms to the tracking
           protection protocol, as defined by this document and
-          [[!TRACKING-COMPLIANCE]].  There is no form of negative response;
-          i.e., an origin server that does not wish to claim conformance
-          to this protocol would not supply a tracking status resource and
-          would not send a Tk header field in responses.
+          [[!TRACKING-COMPLIANCE]].
           For a site-wide tracking status resource, the designated resource
@@ -556,6 +553,13 @@
+          <tr><td><dfn>!</dfn></td>
+              <td><strong>Non-compliant</strong>: The origin server is unable
+                or unwilling to claim that the designated resource conforms to
+                the tracking protection protocol, but is able to provide a
+                valid tracking status representation for the sake of testing
+                and greater transparency (as defined below).</td>
+          </tr>
               <td><strong>None</strong>: The designated resource does not
                 perform tracking of any kind, not even for a <a>permitted use</a>,
@@ -607,6 +611,24 @@
                 state-changing request.</td>
+        <div class="option"><p>
+          The <code><a>!</a></code> (non-compliant) tracking status value has
+          been provided to ease testing and deployment on production systems
+          during the initial periods of testing compliance and during
+          adjustment periods due to future protocol changes or shifting
+          regulatory constraints. Note that this value does not indicate that
+          the DNT signal will be ignored, nor that tracking will occur as a
+          result of accessing the designated resource.
+        </p>
+        <p>
+          An origin server that sends <code><a>!</a></code> as a tracking
+          status value MUST provide, in the corresponding tracking status
+          representation, a valid <code><a>first-party</a></code> member; the
+          origin server MUST also provide <code><a>policy</a></code> and
+          <code><a>control</a></code> members if such information is not
+          directly obtainable by performing a retrieval action on the
+          <code><a>first-party</a></code> resource(s).
+        </p></div>
           For the site-wide tracking status and Tk header field, the tracking
           status values <code><a>1</a></code> and <code><a>3</a></code>
@@ -628,7 +650,8 @@
           by the following ABNF.
         <pre class="abnf">
-<dfn>tracking-v</dfn>    = "1"   ; "1" — first-party
+<dfn>tracking-v</dfn>    = "!"   ; "!" - non-compliant
+              / "1"   ; "1" — first-party
               / "3"   ; "3" — third-party
               / %x43  ; "C" - consent
               / %x4E  ; "N" - none
@@ -646,6 +669,10 @@
           distinguishing between a service provider acting for some other site
           and the same service provider acting on one of its own sites.
+        <p class="issue" data-number="161" title="Do we need a tracking status value for partial compliance or rejecting DNT?">
+          <b>[PENDING REVIEW]</b> See option above for addition of
+          <code><a>!</a></code> to the TSV.
+        </p>
         <section id='status-qualifier-value'>
Received on Wednesday, 30 January 2013 21:10:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 21:10:32 GMT