W3C home > Mailing lists > Public > public-tracking@w3.org > December 2014

Re: Indirect DNT Processing (Proposed)

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 17 Dec 2014 12:34:09 -0800
Message-Id: <10F5BC1F-605F-49A2-9CFC-B45CC30FB5C8@gbiv.com>
To: Tracking Protection Working Group <public-tracking@w3.org>
Okay, here is my attempt to address the comments that were made during
and prior to today's teleconference.

....Roy

http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#TSV-G

   6.2.4  Gateway (G)

   A tracking status value of G means the server is acting as a gateway to an
   exchange involving multiple parties. This might occur if a response to the
   designated resource involves an automated selection process, such as
   dynamic bidding, where the party that is selected determines how the
   request data will be treated with respect to an expressed tracking
   preference. Similar to the ? value, the G TSV indicates that the actual
   tracking status is dynamic and will be provided in the response message's
   Tk header field, presumably using information forwarded from the selected
   party.

   This tracking status value is only valid as a site-wide status. A server
   MUST NOT send G as the tracking status value in a Tk header field or
   within the representation of a request-specific tracking status resource.

   If G is present in the site-wide tracking status:
     * the gateway MUST send a link within its site-wide tracking status
       representation to a privacy policy that explains what limitations are
       placed on parties that might receive data via that gateway;
     * the gateway MUST forward any expressed tracking preference in the
       request to each party that receives data from that request;
     * the gateway MUST have a contract in place with each of the parties to
       whom it provides request data such that only the selected party is
       allowed to retain tracking data from a request with an expressed
       tracking preference of DNT:1; and,
     * the gateway MUST send a Tk header field in responses to requests on
       the designated resource and include within that field's value a
       status-id specific to the selected party, such that information about
       the selected party can be obtained via the request-specific tracking
       status resource (see section 6.4.2 Request-specific Tracking Status).

   With respect to tracking performed by the gateway itself, the G response
   can be considered equivalent to the T (tracking) response defined below.
   The other information within the site-wide tracking status representation
   indicates how the gateway intends to comply with an expressed tracking
   preference, aside from the potential sharing of data implied by the
   gateway process.
Received on Wednesday, 17 December 2014 20:34:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:15 UTC