W3C home > Mailing lists > Public > www-tag@w3.org > April 2018

Re: `Accept-CH` header is weird

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 26 Apr 2018 14:31:08 +0200
Cc: Ilya Grigorik <ilya@grigorik.com>, Alex Russell <slightlyoff@google.com>, Eric Rescorla <ekr@rtfm.com>, "public-privacy (W3C mailing list)" <public-privacy@w3.org>, TAG List <www-tag@w3.org>
Message-Id: <05233351-150C-4B01-98C1-2514B81D7E0D@mnot.net>
To: Nick Doty <npdoty@ischool.berkeley.edu>
Hi Nick,

> On 25 Apr 2018, at 11:11 pm, Nick Doty <npdoty@ischool.berkeley.edu> wrote:
> 
> Thanks for the pointers, Ilya. I hadn't followed that when network information hints were removed from the httpwg Client Hints spec that they appeared in another spec. Would there be any way for us to keep track of all of these Client Hint proposals? Is there a registry somewhere or a page aggregating the active work? Or do we just need to follow all W3C WGs and WICG and IETF HTTP WG?

No.

As I'm sure you're aware, any protocol element can have privacy impact, so if you want to be aware of potential privacy impact, you're going to need to track a lot of things.

> For example, I know that geolocation had been discussed as a possible Client Hint in the HTTP WG, but didn't seem to be an active work in progress. Was that picked up in some other venue?

Not to my knowledge.


>> On Apr 18, 2018, at 9:18 AM, Ilya Grigorik <ilya@grigorik.com> wrote:
>> 
>> Nick, re device capability hints are defined in:
>> 	• https://w3c.github.io/device-memory/
>> 	• https://wicg.github.io/netinfo/
> PING folks, these two are probably worth reviewing. I believe we discussed netinfo at a previous meeting, although I'm not sure we wrote up comments, and it didn't include HTTP headers at that time.
> 
> Cheers,
> Nick

--
Mark Nottingham   https://www.mnot.net/
Received on Thursday, 26 April 2018 12:31:37 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 26 April 2018 12:31:38 UTC