CVS WWW/2011/tracking-protection/drafts

Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv29750

Modified Files:
	CambridgeBareBones.html 
Log Message:
Revised 6.5 to clarify lack of consensus, and to add fourth option

--- /w3ccvs/WWW/2011/tracking-protection/drafts/CambridgeBareBones.html	2013/02/06 03:42:55	1.3
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/CambridgeBareBones.html	2013/02/08 22:40:13	1.4
@@ -1662,14 +1662,8 @@
       <h3>Disregarding Non-Compliant User Agents</h3>
 
       <p class="note">
-        This section has been the topic of active debate. One option not 
-		reflected below but where we may have consensus is the idea that
-		a party may transmit back to the user agent a signal that it
-		rejects the header as a matter of policy.  It will then be
-		incumbent upon the user agent how to message that to the user or
-		otherwise process such a rejection.  The TPE spec would need to
-		include a standardized format for expressing the rejection of
-		a syntactically correct DNT signal on policy grounds.
+        This section has been and will continue to be the topic of active debate.  We do
+		not expect to resolve this issue at the Cambridge meeting.
       </p>
       <p class="option">
         Third parties MUST NOT disregard DNT:1 headers whose syntax is
@@ -1686,6 +1680,13 @@
         operator MUST signal to the user agent that it is disregarding the
         header as described in the companion [[!TRACKING-DNT]] document.
       </p>
+	  
+	  <p class=option>
+	  If the operator of a third-party domain does not intend to comply with a
+	  DNT:1 signal whose syntax is correctly formed, the operator MUST send a 
+	  signal to the user agent that it is disregarding the header as
+	  described in the companion [[!TRACKING-DNT]] document.
+	  </p>
       <p class="option">
         No provision on disregarding non-compliant user agents.
       </p>

Received on Friday, 8 February 2013 22:40:14 UTC