IETF Logo Mail Archive

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

"Richard L. Barnes" <rbarnes@bbn.com> Tue, 06 September 2011 15:27 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 7D2CC21F8B9F; Tue, 6 Sep 2011 08:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.405
X-Spam-Level:
X-Spam-Status: No, score=-106.405 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 dHGn5MwsOx3A; Tue, 6 Sep 2011 08:27:33 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id D5B4421F8B90; Tue, 6 Sep 2011 08:27:33 -0700 (PDT)
Received: from ros-dhcp192-1-51-76.bbn.com ([192.1.51.76]:61117) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1R0xaS-000NBI-I4; Tue, 06 Sep 2011 11:29:20 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <CALiegfm9GT1B9zseiNfatT1L0JpqihkZ3m=oNz9fA20dx8BVBA@mail.gmail.com>
Date: Tue, 06 Sep 2011 11:29:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5AF4413-1929-46E3-B500-207BBC53D6CE@bbn.com>
References: <942CCA6B-B784-441B-96CA-3506FFC439E1@bbn.com> <CALiegfmyQ5h4S2FgBnrh2VLr8+q-h0sLiGsww7T+1VwYNRo4wQ@mail.gmail.com> <72E40A0F-C923-472F-9534-538B89F7A444@bbn.com> <CALiegfm9GT1B9zseiNfatT1L0JpqihkZ3m=oNz9fA20dx8BVBA@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Cc: General Area Review Team <gen-art@ietf.org>, hybi@ietf.org
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 15:27:34 -0000

> I strongly propose changing the meaning of 1007 status code from:
> 
>      1007 indicates that an endpoint is terminating the connection
>      because it has received data that was supposed to be UTF-8 (such
>      as in a text frame) that was in fact not valid UTF-8 [RFC3629].
> 
> to:
> 
>      1007 indicates that an endpoint is terminating the connection
>      because it has received a message that was supposed to be UTF-8
>      that was in fact not valid UTF-8 [RFC3629].

This makes sense to me, given the clarification around what "messages" are.  One slight revision just for succinctness:
"
   1007 indicates that an endpoint is terminating the connection
   because it has received a text message that was not valid UTF-8 [RFC3629].
"
Text messages are the only ones in this spec that have to be UTF-8, and future things that are also UTF-8 should have their own error codes.

Note that this is independent of whether validation is required on a frame or message level.

--Richard

v2.23.0 | Report a Bug | By Email