RFC 8441 on Bootstrapping WebSockets with HTTP/2

rfc-editor@rfc-editor.org Wed, 19 September 2018 00:21 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 D98E6130EAA for <ietf-announce@ietfa.amsl.com>; Tue, 18 Sep 2018 17:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 XN5RBG-Jzbf6 for <ietf-announce@ietfa.amsl.com>; Tue, 18 Sep 2018 17:21:35 -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 45438130DC4 for <ietf-announce@ietf.org>; Tue, 18 Sep 2018 17:21:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3439AB80200; Tue, 18 Sep 2018 17:21:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg0NDEgb24gQm9vdHN0cmFwcGluZyBXZWJTb2NrZXRzIHdpdGggSFRUUC8y?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20180919002135.3439AB80200@rfc-editor.org>
Date: Tue, 18 Sep 2018 17:21:35 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/9SDyR--HRBvSZKic3CZvaUt8YEI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 00:21:37 -0000

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

        
        RFC 8441

        Title:      Bootstrapping WebSockets with HTTP/2 
        Author:     P. McManus
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2018
        Mailbox:    mcmanus@ducksong.com
        Pages:      8
        Characters: 16639
        Updates:    RFC 6455

        I-D Tag:    draft-ietf-httpbis-h2-websockets-07.txt

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

        DOI:        10.17487/RFC8441

This document defines a mechanism for running the WebSocket Protocol
(RFC 6455) over a single stream of an HTTP/2 connection.

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