RFC 7694 on Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
rfc-editor@rfc-editor.org Wed, 04 November 2015 04:20 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 042F11A9132 for <ietf-announce@ietfa.amsl.com>; Tue, 3 Nov 2015 20:20:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 ONPi_EmVhuxo for <ietf-announce@ietfa.amsl.com>; Tue, 3 Nov 2015 20:20:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id E28151A9136 for <ietf-announce@ietf.org>; Tue, 3 Nov 2015 20:19:59 -0800 (PST)
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
Subject: RFC 7694 on Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151104041901.726D018019D@rfc-editor.org>
Date: Tue, 03 Nov 2015 20:19:01 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/W1vDKzYz9sdu5YooBhYonDDTIVI>
Cc: drafts-update-ref@iana.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 04:20:06 -0000
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