IETF Logo Mail Archive

Re: [hybi] Review of draft-ietf-hybi-thewebsocketprotocol-13

"Richard L. Barnes" <rbarnes@bbn.com> Tue, 06 September 2011 16:56 UTC

Return-Path: <rbarnes@bbn.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 4EA6721F8B4A; Tue, 6 Sep 2011 09:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level:
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDAaLgeGW3xB; Tue, 6 Sep 2011 09:56:47 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id B508B21F8B3B; Tue, 6 Sep 2011 09:56:24 -0700 (PDT)
Received: from ros-dhcp192-1-51-76.bbn.com ([192.1.51.76]:61410) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1R0yyR-000Kr3-9e; Tue, 06 Sep 2011 12:58:11 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <634914A010D0B943A035D226786325D422C0EB8E2B@EXVMBX020-12.exch020.serverdata.net>
Date: Tue, 06 Sep 2011 12:58:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABBB8204-4201-4201-8AF1-5BA2A40FB999@bbn.com>
References: <942CCA6B-B784-441B-96CA-3506FFC439E1@bbn.com> <CALiegfmyQ5h4S2FgBnrh2VLr8+q-h0sLiGsww7T+1VwYNRo4wQ@mail.gmail.com> <72E40A0F-C923-472F-9534-538B89F7A444@bbn.com> <634914A010D0B943A035D226786325D422C0EB8D18@EXVMBX020-12.exch020.serverdata.net> <365A444D-CF7D-41A0-A446-7306DE4CDBBC@bbn.com> <c8ic67por9b7638k4cuoqr4blvneo2hlh3@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D422C0EB8E1A@EXVMBX020-12.exch020.serverdata.net> <634914A010D0B943A035D226786325D422C0EB8E2B@EXVMBX020-12.exch020.serverdata.net>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
X-Mailer: Apple Mail (2.1084)
Cc: "hybi@ietf.org" <hybi@ietf.org>, General Area Review Team <gen-art@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [hybi] Review of draft-ietf-hybi-thewebsocketprotocol-13
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: Tue, 06 Sep 2011 16:56:48 -0000

>> In total:
>> 
>> 3 bits: opcode of first frame
>> 1 bit: continuation state
>> 4 bit: UTF-8 DFA state
>> ============
>> 
>> 1 octet state
> 
> forgot of course:
> 
> for servers:
> 
> client mask (4 octets)
> last frame end % 4 : 2 Bits => to know where within mask to start for unmasking the next masked frame received

Server shouldn't need to remember this, since each fragmented frame comes with its own masking key.  At least that's how I read the spec; there's nothing in Section 5.4 that seems to indicate that masking keys get carried over from one fragment to another.


> Plus any extension state as Björn already mentioned.
> 
> Whatever. There is state anyway. WS is not stateless.

Yep.  I was just talking about state related to UTF-8 processing.

--Richard

v2.23.0 | Report a Bug | By Email