RE: I-D Action: draft-ietf-httpbis-client-hints-03.txt

I worry that this makes fingerprinting easier for tracking servers, especially for subresources. 
It is true that these capabilities are already available via JS but only for browsing contexts and the extra turnaround forces some stickiness. This would make these granular user-agent capabilities immediately available to any resource, without need for a round trip.

I think that at least the availability of a user opt-in should be a MUST.

-----Original Message-----
From: [] 
Sent: 02 December 2016 18:08
Subject: I-D Action: draft-ietf-httpbis-client-hints-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Hypertext Transfer Protocol of the IETF.

        Title           : HTTP Client Hints
        Author          : Ilya Grigorik
 Filename        : draft-ietf-httpbis-client-hints-03.txt
 Pages           : 13
 Date            : 2016-12-02

   An increasing diversity of Web-connected devices and software
   capabilities has created a need to deliver optimized content for each

   This specification defines a set of HTTP request header fields,
   colloquially known as Client Hints, to address this.  They are
   intended to be used as input to proactive content negotiation; just
   as the Accept header field allows clients to indicate what formats
   they prefer, Client Hints allow clients to indicate a list of device
   and agent specific preferences.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

Received on Saturday, 3 December 2016 09:59:27 UTC