IETF Logo Mail Archive

Re: [hybi] Changing meaning of 1007 status code ("frame" => "message")

John Tamplin <jat@google.com> Tue, 06 September 2011 17:02 UTC

Return-Path: <jat@google.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 882A921F8BAC for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 10:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.921
X-Spam-Level:
X-Spam-Status: No, score=-105.921 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 k2l6yXuWtVHf for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 10:02:15 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB3D21F8BA7 for <hybi@ietf.org>; Tue, 6 Sep 2011 10:02:14 -0700 (PDT)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id p86H3x8g029426 for <hybi@ietf.org>; Tue, 6 Sep 2011 10:04:00 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1315328640; bh=uz4+EvS/q4+unuMVi3XVHwSoWYE=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=I+EniAbBYqy4aA/+rZpanNQjZx3blnv0mLzFKNxSxAC//atRN1PLkHbmYM5RrShhE DADHLez3B3lR40Q0Q29ow==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=JVltM9T7vGrXiZZZoXBxMS9Nf7EDrQ0MIaylpirh2TNM3iVWZxpIYUDnBdaoVZ+1q 9fN++BScTw4wQ0kxFoC8Q==
Received: from yws29 (yws29.prod.google.com [10.192.19.29]) by wpaz24.hot.corp.google.com with ESMTP id p86H3P8S004309 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <hybi@ietf.org>; Tue, 6 Sep 2011 10:03:58 -0700
Received: by yws29 with SMTP id 29so3944006yws.11 for <hybi@ietf.org>; Tue, 06 Sep 2011 10:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GIRzMsaWuRdapPHi7u9Pb3LYQTefFQ14qeF++IcpvpQ=; b=F4MAM+xc62HqI4jx2GAQ+2Nzs0rJeHeYAe9+I8qcdhdPRHCW7/buo5SVVy5Bqj8c7V Sgl6gWdhIguvUR5oWDVQ==
Received: by 10.150.48.8 with SMTP id v8mr4222874ybv.401.1315328637911; Tue, 06 Sep 2011 10:03:57 -0700 (PDT)
Received: by 10.150.48.8 with SMTP id v8mr4222848ybv.401.1315328637152; Tue, 06 Sep 2011 10:03:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Tue, 6 Sep 2011 10:03:37 -0700 (PDT)
In-Reply-To: <1AC3D19D-9E20-45EF-AC3C-B11091AF9E98@bbn.com>
References: <CALiegf=D5K9H0uckc_zLVbaLieyu082g8kooAXa-3LkG+g_XGQ@mail.gmail.com> <1AC3D19D-9E20-45EF-AC3C-B11091AF9E98@bbn.com>
From: John Tamplin <jat@google.com>
Date: Tue, 06 Sep 2011 13:03:37 -0400
Message-ID: <CABLsOLA4JX5noeKv8SFaZ94ppUwUSwdvL-59spqVgj5j-0hWDQ@mail.gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: multipart/alternative; boundary="000e0cd70d3c2e2e0904ac48d03e"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] Changing meaning of 1007 status code ("frame" => "message")
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 17:02:15 -0000

On Tue, Sep 6, 2011 at 12:59 PM, Richard L. Barnes <rbarnes@bbn.com> wrote:

> As suggested in the other thread:
> "
>  1007 indicates that an endpoint is terminating the connection
>   because it has received a text message that was not valid UTF-8
> [RFC3629].
> "
> Text frames are the only UTF-8 things that are currently specified, and
> future UTF-8 things should have their own error codes.


I suggest it would be more useful for 1007 to mean that the payload contents
were invalid for the frame type/negotiated extensions/etc.  For text
messages, that would mean invalid UTF8 sequences.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email