[hybi] Re: [Editorial Errata Reported] RFC6455 (8491)

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 02 July 2025 17:54 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: hybi@mail2.ietf.org
Delivered-To: hybi@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B9DD53D02AC1 for <hybi@mail2.ietf.org>; Wed, 2 Jul 2025 10:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level:
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpBZR7rtsEgS for <hybi@mail2.ietf.org>; Wed, 2 Jul 2025 10:54:43 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3267C3D02AAB for <hybi@ietf.org>; Wed, 2 Jul 2025 10:54:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1751478882; d=isode.com; s=june2016; i=@isode.com; bh=OC0x3jIK0ZBP00tYAi+rVG2J+Bj2aBUvItK+j1B4aG4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Jt+mg3RbJhZd7TqfZAGHFs1Q4KV/LbL/91sRpDKvh58j7J63ZR8DUNBczaSs8TUsvwDfPw DflQRT8xcM/PXCmFY8Rii7t1f9l8QBV2MWWDZig+gPMvpW595OeSiqohIzKfcrq0OJeTAt EcYohgwJTrNUWJoVE4uLcuVjSFkT4SE=;
Received: from [172.20.10.3] ((unknown) [148.252.146.98]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <aGVyYBmrysRx@waldorf.isode.com>; Wed, 2 Jul 2025 18:54:41 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <a51d8b76-a6cb-409b-abbd-55b4baf53bca@isode.com>
Date: Wed, 02 Jul 2025 18:54:39 +0100
User-Agent: Mozilla Thunderbird
To: Madison Church <mchurch@staff.rfc-editor.org>, Orie Steele <orie@transmute.industries>, andy@hxr.us
References: <20250628151539.170AA26B2D9@rfcpa.rfc-editor.org> <3B85F499-CD43-47E7-93C4-ACB5B917C80C@staff.rfc-editor.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <3B85F499-CD43-47E7-93C4-ACB5B917C80C@staff.rfc-editor.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------2G6NDPTcUA0lQjgYk300V4K9"
Content-Language: en-GB
Message-ID-Hash: JUN27E6OC2CS5JE44QRNP5HUDUIAGA6G
X-Message-ID-Hash: JUN27E6OC2CS5JE44QRNP5HUDUIAGA6G
X-MailFrom: alexey.melnikov@isode.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-hybi.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: samuel871211@gmail.com, RFC Editor <rfc-editor@rfc-editor.org>, ifette+ietf@google.com, hybi@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [hybi] Re: [Editorial Errata Reported] RFC6455 (8491)
List-Id: Server-Initiated HTTP <hybi.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/iHwQkGh3DrTddist5utD84aqRtg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Owner: <mailto:hybi-owner@ietf.org>
List-Post: <mailto:hybi@ietf.org>
List-Subscribe: <mailto:hybi-join@ietf.org>
List-Unsubscribe: <mailto:hybi-leave@ietf.org>

Hi all,

On 02/07/2025 17:14, Madison Church wrote:
> Hi Andy and Orie,
>
> We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. As Stream Approvers, please review and set the Status and Type accordingly (see the definitions athttps://www.rfc-editor.org/errata-definitions/) Note that this errata report comes from the BiDirectional or Server-Initiated HTTP (hybi) Working Group, which is concluded.
>
> You may review the report at:https://www.rfc-editor.org/errata/eid8491  
>
> Information on how to verify errata reports can be found at:https://www.rfc-editor.org/how-to-verify/ 
>
> Further information on errata can be found at:https://www.rfc-editor.org/errata.php

This erratum should be rejected:

   Sec-WebSocket-Extensions = extension-list
   extension-list = 1#extension

The "1#extension" is ","-separated. ";" is used to specify extension parameters that apply to the specific extension.

Best Regards,
Alexey

> Thank you,
> RFC Editor/mc
>
>> On Jun 28, 2025, at 10:15 AM, RFC Errata System<rfc-editor@rfc-editor.org> wrote:
>>
>> The following errata report has been submitted for RFC6455,
>> "The WebSocket Protocol".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid8491
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: YuSheng Chen<samuel871211@gmail.com>
>>
>> Section: section-9.1
>>
>> Original Text
>> -------------
>>    is exactly equivalent to
>>
>>          Sec-WebSocket-Extensions: foo, bar; baz=2
>>
>> Corrected Text
>> --------------
>>    is exactly equivalent to
>>
>>          Sec-WebSocket-Extensions: foo; bar; baz=2
>>
>> Notes
>> -----
>> Should be semicolon-separated
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it
>> will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> will log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC6455 (draft-ietf-hybi-thewebsocketprotocol-17)
>> --------------------------------------
>> Title               : The WebSocket Protocol
>> Publication Date    : December 2011
>> Author(s)           : I. Fette, A. Melnikov
>> Category            : PROPOSED STANDARD
>> Source              : BiDirectional or Server-Initiated HTTP APP
>> Stream              : IETF
>> Verifying Party     : IESG