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

[Madison Church <[e-mail]>]

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 at https://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

Thank you, 
RFC Editor/mc

> On Jun 28, 2025, at 10:15 AM, RFC Errata System <[e-mail]> 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 <[e-mail]>
> 
> 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