Re: [hybi] [Technical Errata Reported] RFC6455 (3433)

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 22 December 2012 09:56 UTC

Return-Path: <alexey.melnikov@isode.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 47D2321F8B2B for <hybi@ietfa.amsl.com>; Sat, 22 Dec 2012 01:56:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFVZQCDnLIIn for <hybi@ietfa.amsl.com>; Sat, 22 Dec 2012 01:56:33 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 275E821F8B28 for <hybi@ietf.org>; Sat, 22 Dec 2012 01:56:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1356170185; d=isode.com; s=selector; i=@isode.com; bh=KXaY3NrTR4v4/b3vIn/Xt7YrJ0gLG9mtsm1nwQD02FA=; 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=fW0fIBvPy0wv8Dcfuw6mxez7a2TnpOIfji7EbTyOktdvl352zOkghjWiz/LfU8dLzfT2W5 k9VEHQnLnsPHYJYYvIy6HK+3uWb7kQN5bA8X937NEbW8J6QoouXlKsmS/tkBMreIYTCaFI YAoIyFVPK08cb/cE19zxDMPn4fDc8IM=;
Received: from [192.168.1.4] (ppp95-165-96-64.pppoe.spdop.ru [95.165.96.64]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UNWDxABRr2vE@statler.isode.com>; Sat, 22 Dec 2012 09:56:24 +0000
Message-ID: <50D583DC.9040003@isode.com>
Date: Sat, 22 Dec 2012 09:56:44 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Takeshi Yoshino <tyoshino@google.com>, barryleiba@computer.org
References: <20121221000236.0EC14B1E002@rfc-editor.org> <CAH9hSJZAd-ZAvQvS1pvOx9=qwK_xpJ90O4atuj6Aqm-AckeO-g@mail.gmail.com>
In-Reply-To: <CAH9hSJZAd-ZAvQvS1pvOx9=qwK_xpJ90O4atuj6Aqm-AckeO-g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------000108050104090902060601"
Cc: e_lawrence@hotmail.com, "hybi@ietf.org" <hybi@ietf.org>, presnick@qti.qualcomm.com, "ifette+ietf@google.com" <ifette+ietf@google.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [hybi] [Technical Errata Reported] RFC6455 (3433)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 22 Dec 2012 09:56:34 -0000

On 21/12/2012 04:41, Takeshi Yoshino wrote:
> +1
>
> Both "If multiple ..." and "However, the ..." were added from 
> https://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-14.
>
> In the release note by Alexey 
> (http://www.ietf.org/mail-archive/web/hybi/current/msg08863.html), it's said
> > Clarified that some header fields can appear multiple times. (per WG 
> discussion)
>
> This is the thread where the decision was made (multiple headers are 
> allowed)
> http://www.ietf.org/mail-archive/web/hybi/current/msg08690.html
>
> I think it was just cut n' pasted but left not updated. IIRC, we 
> didn't have any discussion to add asymmetric constraints like this.
>
> There were similar bug which was fixed on -15 release.
> http://www.ietf.org/mail-archive/web/hybi/current/msg09057.html

Thanks, Takeshi. I agree that the erratum should be approved.

> Takeshi
>
>
> On Fri, Dec 21, 2012 at 9:02 AM, RFC Errata System 
> <rfc-editor@rfc-editor.org <mailto: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:
>     http://www.rfc-editor.org/errata_search.php?rfc=6455&eid=3433
>
>     --------------------------------------
>     Type: Technical
>     Reported by: Eric Lawrence <e_lawrence@hotmail.com
>     <mailto:e_lawrence@hotmail.com>>
>
>     Section: 11.3.2
>
>     Original Text
>     -------------
>     However, the |Sec-WebSocket-Extensions| header field MUST NOT
>     appear more than once in an HTTP response.
>
>
>     Corrected Text
>     --------------
>     The |Sec-WebSocket-Extensions| header field MAY appear multiple
>     times in an HTTP response (which is logically the same as a single
>     |Sec-WebSocket-Extensions| header field that contains all values).
>
>
>     Notes
>     -----
>     Section 4.2.2 Step 5 subpart 6 (top of page 25) clearly explains
>     that this header field may appear multiple times in the server's
>     response: "If multiple extensions are to be used, they can all be
>     listed in a single |Sec-WebSocket-Extensions| header field or
>     split between multiple instances of the |Sec-WebSocket-Extensions|
>     header field. This completes the server's handshake..."
>
>     Instructions:
>     -------------
>     This errata 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 (IESG)
>     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
>     Area                : Applications
>     Stream              : IETF
>     Verifying Party     : IESG
>     _______________________________________________
>     hybi mailing list
>     hybi@ietf.org <mailto:hybi@ietf.org>
>     https://www.ietf.org/mailman/listinfo/hybi
>
>