[Errata Held for Document Update] RFC8441 (5500)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 01 April 2020 21:02 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 (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 510683A08E2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2020 14:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id qiEpOJIyTkq1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2020 14:02:50 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 049233A0886 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 1 Apr 2020 14:02:49 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jJkSt-0001Sf-3A for ietf-http-wg-dist@listhub.w3.org; Wed, 01 Apr 2020 20:59:59 +0000
Resent-Date: Wed, 01 Apr 2020 20:59:59 +0000
Resent-Message-Id: <E1jJkSt-0001Sf-3A@lyra.w3.org>
Received: from titan.w3.org ([]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <wwwrun@rfc-editor.org>) id 1jJkSs-0001S2-5H for ietf-http-wg@listhub.w3.org; Wed, 01 Apr 2020 20:59:58 +0000
Received: from rfc-editor.org ([]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <wwwrun@rfc-editor.org>) id 1jJkSo-00044x-Qz for ietf-http-wg@w3.org; Wed, 01 Apr 2020 20:59:57 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id DE255F406D8; Wed, 1 Apr 2020 13:59:37 -0700 (PDT)
To: essen@ninenines.eu, mcmanus@ducksong.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: barryleiba@computer.org, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200401205937.DE255F406D8@rfc-editor.org>
Date: Wed, 01 Apr 2020 13:59:37 -0700
Received-SPF: pass client-ip=; envelope-from=wwwrun@rfc-editor.org; helo=rfc-editor.org
X-W3C-Hub-Spam-Status: No, score=-6.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1jJkSo-00044x-Qz 79829d154237729e1dec6d2ce1dbf11f
X-Original-To: ietf-http-wg@w3.org
Subject: [Errata Held for Document Update] RFC8441 (5500)
Archived-At: <https://www.w3.org/mid/20200401205937.DE255F406D8@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37493
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

The following errata report has been held for document update 
for RFC8441, "Bootstrapping WebSockets with HTTP/2". 

You may review the report below and at:

Status: Held for Document Update
Type: Editorial

Reported by: Loïc Hoguin <essen@ninenines.eu>
Date Reported: 2018-09-21
Held by: Barry Leiba (IESG)

Section: 3

Original Text
Using a SETTINGS parameter to opt into an otherwise incompatible
protocol change is a use of "Extending HTTP/2" defined by Section 5.5
of [RFC7540].  Specifically, the addition a new pseudo-header field,

Corrected Text
Using a SETTINGS parameter to opt into an otherwise incompatible
protocol change is a use of "Extending HTTP/2" defined by Section 5.5
of [RFC7540].  Specifically, the addition of a new pseudo-header field,

I think it's missing a word.

RFC8441 (draft-ietf-httpbis-h2-websockets-07)
Title               : Bootstrapping WebSockets with HTTP/2
Publication Date    : September 2018
Author(s)           : P. McManus
Category            : PROPOSED STANDARD
Source              : HTTP
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG