W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

Re: Fingerprinting Guidance for Web Specification Authors

From: Jeffrey Walton <noloader@gmail.com>
Date: Tue, 1 Dec 2015 12:17:20 -0500
Message-ID: <CAH8yC8mphLLnyx33jikeaMENH5mBahpTfbqrWoL6uQDr9twGOw@mail.gmail.com>
To: Arthur Barstow <art.barstow@gmail.com>
Cc: public-webapps <public-webapps@w3.org>
On Tue, Dec 1, 2015 at 11:52 AM, Arthur Barstow <art.barstow@gmail.com> wrote:
> Editors, All - please see "Fingerprinting Guidance for Web Specification
> Authors" <http://www.w3.org/TR/2015/NOTE-fingerprinting-guidance-20151124/>
> and reflect it in your spec, accordingly.

Tracking can be a tricky problem because it occurs at many layers in a
typical stack. It starts when the first TCP SYN is sent. If browsers
use an underlying transport like TCP/IP, should something be said
about it (ie., its in scope or out of scope)?

ETAGS were not mentioned in the document. In the context of the PING
working group, I would expect to see a treatment.

Received on Tuesday, 1 December 2015 17:17:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:58 UTC