RFC 8164 on Opportunistic Security for HTTP/2

rfc-editor@rfc-editor.org Thu, 11 May 2017 03:58 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 AF37E1279E5 for <ietf-announce@ietfa.amsl.com>; Wed, 10 May 2017 20:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 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] 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 pCJuMqahvTLm for <ietf-announce@ietfa.amsl.com>; Wed, 10 May 2017 20:58:51 -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 2D8C0126FDC for <ietf-announce@ietf.org>; Wed, 10 May 2017 20:58:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6BF67B81739; Wed, 10 May 2017 20:58:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8164 on Opportunistic Security for HTTP/2
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: <20170511035841.6BF67B81739@rfc-editor.org>
Date: Wed, 10 May 2017 20:58:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/VevI5FiVaEschcCvwkxOIWluAZM>
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: Thu, 11 May 2017 03:58:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8164

        Title:      Opportunistic Security for HTTP/2 
        Author:     M. Nottingham, 
                    M. Thomson
        Status:     Experimental
        Stream:     IETF
        Date:       May 2017
        Mailbox:    mnot@mnot.net, 
                    martin.thomson@gmail.com
        Pages:      10
        Characters: 19620
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpbis-http2-encryption-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8164

        DOI:        10.17487/RFC8164

This document describes how "http" URIs can be accessed using
Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive
monitoring attacks.  This mechanism not a replacement for "https"
URIs; it is vulnerable to active attacks.


This document is a product of the Hypertext Transfer Protocol Bis 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