IETF Logo Mail Archive

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

Philipp Serafin <phil127@gmail.com> Tue, 06 September 2011 14:48 UTC

Return-Path: <phil127@gmail.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 59E1321F8997 for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 07:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 LuHg5LbPamQE for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 07:48:43 -0700 (PDT)
Received: from mail-qw0-f52.google.com (mail-qw0-f52.google.com [209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9457E21F86EA for <hybi@ietf.org>; Tue, 6 Sep 2011 07:48:43 -0700 (PDT)
Received: by qwb8 with SMTP id 8so5421895qwb.25 for <hybi@ietf.org>; Tue, 06 Sep 2011 07:50:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=LwVIMrkDKY3W5erBhMaS/wyMPRBJcEAVvlzB0QzJ/D8=; b=H0VGVDCLaLeDiQvCY1wELSbIWGslwFF+UlwGKox5DfDFAFbxsRGE+oFAU05IkbiLBn mfX8BXSyBfAWl3zoRNVbV1GCl4oC1XGvMq5D5WqYNjrQ3hOxyVkcSgRZQ4hkIzwPJHFR mojH9vVqMhAAQuo3b/B+9AeKzXwJp/ga3RGrU=
Received: by 10.229.63.164 with SMTP id b36mr4032469qci.65.1315320630117; Tue, 06 Sep 2011 07:50:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.44.21 with HTTP; Tue, 6 Sep 2011 07:50:00 -0700 (PDT)
In-Reply-To: <72E40A0F-C923-472F-9534-538B89F7A444@bbn.com>
References: <942CCA6B-B784-441B-96CA-3506FFC439E1@bbn.com> <CALiegfmyQ5h4S2FgBnrh2VLr8+q-h0sLiGsww7T+1VwYNRo4wQ@mail.gmail.com> <72E40A0F-C923-472F-9534-538B89F7A444@bbn.com>
From: Philipp Serafin <phil127@gmail.com>
Date: Tue, 06 Sep 2011 16:50:00 +0200
Message-ID: <CAMaigV=0S+Q=A=RwS-j1Hy70EuuTtjYgrm+VW3ecorMb6U_3Nw@mail.gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, hybi@ietf.org
Content-Type: multipart/alternative; boundary="0016e64f53f8ec842604ac46f236"
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 14:48:44 -0000

My impression so far was that data opcodes (like "Text" or "Binary") refer
to the *message* a frame belongs to and not to the frame itself.
As I understood it, there are no "Text frames" or "Binary frames" at all,
only "Text" or "Binary" messages.


> In contrast, *not* requiring breaking at UTF-8 code points means that
> clients can't do any meaningful validation on text frames.  Which means you
> might as well get rid of text frames entirely.
>
> --Richard
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

v2.23.0 | Report a Bug | By Email