[hybi] [Technical Errata Reported] RFC6455 (6997)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 17 June 2022 12:31 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFA3C14F724 for <hybi@ietfa.amsl.com>; Fri, 17 Jun 2022 05:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7b1TOKHzqH8z for <hybi@ietfa.amsl.com>; Fri, 17 Jun 2022 05:31:25 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6B58C15AAEC for <hybi@ietf.org>; Fri, 17 Jun 2022 05:31:23 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id ABE1185CA2; Fri, 17 Jun 2022 05:31:23 -0700 (PDT)
To: ifette+ietf@google.com, Alexey.Melnikov@isode.com, superuser@gmail.com, francesca.palombini@ericsson.com, Salvatore.Loreto@ericsson.com, Gabriel.Montenegro@microsoft.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: daniel.egger@axiros.com, hybi@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220617123123.ABE1185CA2@rfcpa.amsl.com>
Date: Fri, 17 Jun 2022 05:31:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/RdvYM9q8LoFNdQHMqIUlx5QtlNc>
Subject: [hybi] [Technical Errata Reported] RFC6455 (6997)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2022 12:31:29 -0000
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/eid6997 -------------------------------------- Type: Technical Reported by: Daniel Egger <daniel.egger@axiros.com> Section: 4.3, 9.1 Original Text ------------- extension-param = token [ "=" (token | quoted-string) ] ; When using the quoted-string syntax variant, the value ; after quoted-string unescaping MUST conform to the ; 'token' ABNF. Corrected Text -------------- extension-param = token [ "=" (token | quoted-string) ] Notes ----- The text reads as if any quoted-string which was supplied as a value has to follow the same rules as a token. That precludes the use of any token separators inside a quoted-string which is the whole reason why quoted-string exists as explained in RFC 2616: Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters MUST be in a quoted string to be used within a parameter value (as defined in section 3.6). Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can 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 Area : Applications Stream : IETF Verifying Party : IESG
- [hybi] [Technical Errata Reported] RFC6455 (6997) RFC Errata System