draft-ietf-httpbis-client-hints-06.txt   draft-ietf-httpbis-client-hints-latest.txt 
HTTP Working Group I. Grigorik HTTP Working Group I. Grigorik
Internet-Draft Google Internet-Draft Google
Intended status: Experimental July 16, 2018 Intended status: Experimental November 20, 2018
Expires: January 17, 2019 Expires: May 24, 2019
HTTP Client Hints HTTP Client Hints
draft-ietf-httpbis-client-hints-06 draft-ietf-httpbis-client-hints-latest
Abstract Abstract
An increasing diversity of Web-connected devices and software An increasing diversity of Web-connected devices and software
capabilities has created a need to deliver optimized content for each capabilities has created a need to deliver optimized content for each
device. device.
This specification defines an extensible and configurable set of HTTP This specification defines an extensible and configurable set of HTTP
request header fields, colloquially known as Client Hints, to address request header fields, colloquially known as Client Hints, to address
this. They are intended to be used as input to proactive content this. They are intended to be used as input to proactive content
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 17, 2019. This Internet-Draft will expire on May 24, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 9, line 27 skipping to change at page 9, line 27
balance privacy concerns with bandwidth limitations. However, balance privacy concerns with bandwidth limitations. However,
implementers should also be aware that explaining the privacy implementers should also be aware that explaining the privacy
implications of passive fingerprinting to users may be implications of passive fingerprinting to users may be
challenging. challenging.
o Implementations specific to certain use cases or threat models MAY o Implementations specific to certain use cases or threat models MAY
avoid transmitting some or all of Client Hints header fields. For avoid transmitting some or all of Client Hints header fields. For
example, avoid transmission of header fields that can carry higher example, avoid transmission of header fields that can carry higher
risks of linkability. risks of linkability.
Implementers SHOULD support Client Hints opt-in mechanisms and MUST Implementers SHOULD support Client Hints opt-in mechanisms and MUST
clear persisted opt-in preferences when site data, browsing history, clear persisted opt-in preferences when any one of site data,
browsing cache, or similar, are cleared. browsing history, browsing cache, or similar, are cleared.
6. IANA Considerations 6. IANA Considerations
This document defines the "Accept-CH", "DPR", "Viewport-Width", and This document defines the "Accept-CH", "DPR", "Viewport-Width", and
"Width" HTTP request fields, "Accept-CH", "Accept-CH-Lifetime", and "Width" HTTP request fields, "Accept-CH", "Accept-CH-Lifetime", and
"Content-DPR" HTTP response field, and registers them in the "Content-DPR" HTTP response field, and registers them in the
Permanent Message Header Fields registry. Permanent Message Header Fields registry.
6.1. Accept-CH 6.1. Accept-CH
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/