RFC 8188 on Encrypted Content-Encoding for HTTP
rfc-editor@rfc-editor.org Fri, 23 June 2017 22:00 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF385129ADA for <ietf-announce@ietfa.amsl.com>; Fri, 23 Jun 2017 15:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 TW_-YBIszcAz for <ietf-announce@ietfa.amsl.com>; Fri, 23 Jun 2017 15:00:31 -0700 (PDT)
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 7A8CC129B02 for <ietf-announce@ietf.org>; Fri, 23 Jun 2017 15:00:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4AB55B81B7B; Fri, 23 Jun 2017 14:59:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8188 on Encrypted Content-Encoding for HTTP
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: <20170623215949.4AB55B81B7B@rfc-editor.org>
Date: Fri, 23 Jun 2017 14:59:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hPl12HlaQCZ55Y0h7svxNiagRe8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Fri, 23 Jun 2017 22:00:33 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8188
Title: Encrypted Content-Encoding for HTTP
Author: M. Thomson
Status: Standards Track
Stream: IETF
Date: June 2017
Mailbox: martin.thomson@gmail.com
Pages: 16
Characters: 33404
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-encryption-encoding-09.txt
URL: https://www.rfc-editor.org/info/rfc8188
DOI: 10.17487/RFC8188
This memo introduces a content coding for HTTP that allows message
payloads to be encrypted.
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/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