[rfc-dist] RFC 8942 on HTTP Client Hints
rfc-editor@rfc-editor.org Mon, 08 February 2021 23:38 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7DC3A1806 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 8 Feb 2021 15:38:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.92
X-Spam-Level:
X-Spam-Status: No, score=-2.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbZfMe8xZl8L for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 8 Feb 2021 15:38:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00BF83A17C2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 8 Feb 2021 15:38:12 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CDBC6F40780; Mon, 8 Feb 2021 15:37:47 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0F43AF4077D; Mon, 8 Feb 2021 15:37:47 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20210208233747.0F43AF4077D@rfc-editor.org>
Date: Mon, 08 Feb 2021 15:37:47 -0800
Subject: [rfc-dist] RFC 8942 on HTTP Client Hints
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8942
Title: HTTP Client Hints
Author: I. Grigorik,
Y. Weiss
Status: Experimental
Stream: IETF
Date: February 2021
Mailbox: ilya@igvita.com,
yoav@yoav.ws
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-client-hints-15.txt
URL: https://www.rfc-editor.org/info/rfc8942
DOI: 10.17487/RFC8942
HTTP defines proactive content negotiation to allow servers to select
the appropriate response for a given request, based upon the user
agent's characteristics, as expressed in request headers. In
practice, user agents are often unwilling to send those request
headers, because it is not clear whether they will be used, and
sending them impacts both performance and privacy.
This document defines an Accept-CH response header that servers can
use to advertise their use of request headers for proactive content
negotiation, along with a set of guidelines for the creation of such
headers, colloquially known as "Client Hints."
This document is a product of the HTTP Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
- [rfc-dist] RFC 8942 on HTTP Client Hints rfc-editor