RFC 7694 on Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
rfc-editor@rfc-editor.org Wed, 04 November 2015 04:24 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D26311A9175 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 3 Nov 2015 20:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 bpHQxgaf_5h4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 3 Nov 2015 20:24:37 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C19C1A9173 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 3 Nov 2015 20:24:36 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZtpYu-0003dS-RO for ietf-http-wg-dist@listhub.w3.org; Wed, 04 Nov 2015 04:20:40 +0000
Resent-Date: Wed, 04 Nov 2015 04:20:40 +0000
Resent-Message-Id: <E1ZtpYu-0003dS-RO@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <wwwrun@rfc-editor.org>) id 1ZtpYo-0003aX-Si for ietf-http-wg@listhub.w3.org; Wed, 04 Nov 2015 04:20:34 +0000
Received: from rfc-editor.org ([4.31.198.49]) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <wwwrun@rfc-editor.org>) id 1ZtpYg-0002bt-Ni for ietf-http-wg@w3.org; Wed, 04 Nov 2015 04:20:32 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id 726D018019D; Tue, 3 Nov 2015 20:19:01 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Message-Id: <20151104041901.726D018019D@rfc-editor.org>
Date: Tue, 03 Nov 2015 20:19:01 -0800
Received-SPF: pass client-ip=4.31.198.49; envelope-from=wwwrun@rfc-editor.org; helo=rfc-editor.org
X-W3C-Hub-Spam-Status: No, score=-7.8
X-W3C-Hub-Spam-Report: AWL=2.086, BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ZtpYg-0002bt-Ni 69945aad71bd86a157df86c6655d40ea
X-Original-To: ietf-http-wg@w3.org
Subject: RFC 7694 on Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
Archived-At: <http://www.w3.org/mid/20151104041901.726D018019D@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30435
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 7694
Title: Hypertext Transfer Protocol (HTTP) Client-Initiated
Content-Encoding
Author: J. Reschke
Status: Standards Track
Stream: IETF
Date: November 2015
Mailbox: julian.reschke@greenbytes.de
Pages: 7
Characters: 13676
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-cice-03.txt
URL: https://www.rfc-editor.org/info/rfc7694
DOI: http://dx.doi.org/10.17487/RFC7694
In HTTP, content codings allow for payload encodings such as for
compression or integrity checks. In particular, the "gzip" content
coding is widely used for payload data sent in response messages.
Content codings can be used in request messages as well; however,
discoverability is not on par with response messages. This document
extends the HTTP "Accept-Encoding" header field for use in responses,
to indicate the content codings that are supported in requests.
This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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/rfc.html
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