HTTP Client Hints
draft-ietf-httpbis-client-hints-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

HTTP Working Group                                           I. Grigorik
Internet-Draft                                                    Google
Intended status: Experimental                           January 26, 2018
Expires: July 30, 2018

                           HTTP Client Hints
                   draft-ietf-httpbis-client-hints-05

Abstract

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

   This specification defines an extensible and configurable 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 user agents to
   indicate what formats they prefer, Client Hints allow user agents to
   indicate device and agent specific preferences.

Note to Readers

   Discussion of this draft takes place on the HTTP working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   https://lists.w3.org/Archives/Public/ietf-http-wg/ [1].

   Working Group information can be found at http://httpwg.github.io/
   [2]; source code and issues list for this draft can be found at
   https://github.com/httpwg/http-extensions/labels/client-hints [3].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 30, 2018.

Grigorik                  Expires July 30, 2018                 [Page 1]
Internet-Draft              HTTP Client Hints               January 2018

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
   2.  Client Hint Request Header Fields . . . . . . . . . . . . . .   4
     2.1.  Sending Client Hints  . . . . . . . . . . . . . . . . . .   4
     2.2.  Server Processing of Client Hints . . . . . . . . . . . .   4
       2.2.1.  Advertising Support via Accept-CH Header Field  . . .   5
       2.2.2.  The Accept-CH-Lifetime Header Field . . . . . . . . .   5
       2.2.3.  Interaction with Caches . . . . . . . . . . . . . . .   6
   3.  Client Hints  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  The DPR Header Field  . . . . . . . . . . . . . . . . . .   6
       3.1.1.  Confirming Selected DPR . . . . . . . . . . . . . . .   7
     3.2.  The Width Header Field  . . . . . . . . . . . . . . . . .   7
     3.3.  The Viewport-Width Header Field . . . . . . . . . . . . .   7
     3.4.  The Save-Data Header Field  . . . . . . . . . . . . . . .   8
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Accept-CH . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.2.  Accept-CH-Lifetime  . . . . . . . . . . . . . . . . . . .  10
     6.3.  Content-DPR . . . . . . . . . . . . . . . . . . . . . . .  10
     6.4.  DPR . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.5.  Save-Data . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.6.  Viewport-Width  . . . . . . . . . . . . . . . . . . . . .  11
     6.7.  Width . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  12