IETF Logo Mail Archive

Re: [hybi] Clarify the role of closing handshake

Takeshi Yoshino <tyoshino@google.com> Mon, 14 February 2011 19:49 UTC

Return-Path: <tyoshino@google.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DDF23A6DB1 for <hybi@core3.amsl.com>; Mon, 14 Feb 2011 11:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.686
X-Spam-Level:
X-Spam-Status: No, score=-105.686 tagged_above=-999 required=5 tests=[AWL=0.290, 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hB3VabzcAz1s for <hybi@core3.amsl.com>; Mon, 14 Feb 2011 11:49:23 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 7294F3A6DA6 for <hybi@ietf.org>; Mon, 14 Feb 2011 11:49:23 -0800 (PST)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p1EJnk1P030459 for <hybi@ietf.org>; Mon, 14 Feb 2011 11:49:46 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1297712986; bh=aOSLlrKzmi6GPUkBIVv2Shha4bY=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=HTdoMnM4qlfTmp7C9nxY32KWftp8gUcUlJdchT0PJYyY3WoE6gz/rGrP8kLugCqqo IThNnDdHpxlNmrvlT/EPA==
Received: from iwc10 (iwc10.prod.google.com [10.241.65.138]) by hpaq12.eem.corp.google.com with ESMTP id p1EJmV2L027450 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Mon, 14 Feb 2011 11:49:45 -0800
Received: by iwc10 with SMTP id 10so5089879iwc.28 for <hybi@ietf.org>; Mon, 14 Feb 2011 11:49:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=VVk5Rrm+TtZNnH7zZEhCOsyi9pMCyTo+3Vbnh/dEaJM=; b=Ukp/CenO2Zlp6Wadqs+fnrBHaS+D3BOylj+PPT0IE0D8zivdxsEPiG0Yqeumc/YjMY iY0m/2rJ4MDABQwIs18g==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=knVFa7eJcwH76Np2afiUujuyiaVYwucE2lCI+09EUv8gGKW8euo+zKW3OiqC54Fr6o CDUngs49ajfRTsZQ/dng==
Received: by 10.42.178.134 with SMTP id bm6mr5467431icb.523.1297712984540; Mon, 14 Feb 2011 11:49:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.17.201 with HTTP; Mon, 14 Feb 2011 11:49:24 -0800 (PST)
In-Reply-To: <AANLkTikHf00MhSPXhfjDv9MuG=tMQ6V3FG2VvGoV+o-8@mail.gmail.com>
References: <AANLkTi=wAwQHGbu_vVS5o9yNuC-M=e_hWwtU5F6UPGqm@mail.gmail.com> <AANLkTimGHPmGSB1hCr2VJ3O8bFJiEkvdkvqptt6A8mBA@mail.gmail.com> <CA566BAEAD6B3F4E8B5C5C4F61710C1126E04F34@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com> <AANLkTimRezbkgnicmSqhX+Go5UYAazTU9WWHpH8oe_7K@mail.gmail.com> <AANLkTinh1jUbei-FhMAkRcGoT9-z7RJQv4Q_7DweiwcL@mail.gmail.com> <7785FB1F-C733-4AE1-BACF-44556B1074A8@gmail.com> <AANLkTinfcj-rYiv4vDUBz3cmRqALttq61=hb0mC41L9h@mail.gmail.com> <AANLkTikHf00MhSPXhfjDv9MuG=tMQ6V3FG2VvGoV+o-8@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 14 Feb 2011 11:49:24 -0800
Message-ID: <AANLkTi=O6peLVFks-+phmQ=MTtrXddixj5_LYKvg6xWv@mail.gmail.com>
To: Brodie Thiesfield <brofield@gmail.com>
Content-Type: multipart/alternative; boundary="90e6ba6e8d9c76c650049c435923"
X-System-Of-Record: true
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Clarify the role of closing handshake
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Feb 2011 19:49:24 -0000

On Fri, Feb 11, 2011 at 05:59, Brodie Thiesfield <brofield@gmail.com> wrote:
>
> termination. I would suggest reusing the 2xx for normal, 4xx for
> client error (or message sender error) and 5xx for server error (or
> message receiver) form since they are already familiar. Disallow other
>

+1 for using these terms, message sender error and message receiver error

Status codes that I could imagine would be useful as well as a few
> codes to cover the list that Yuta mentioned:
>
> 4xx
> * timeout
> * invalid opcode
> * invalid encoding
> * unexpected
> * too long
>
> 5xx
> * overloaded / service unavailable
> * not supported
>
> But as I said, at the very least, the 200/400/500 + optional text message.
>

Sounds not bad.

This must be aligned with what discussed on another thread about opening
handshake status code. Having very similar code for two purposes can be
confusing.

v2.23.0 | Report a Bug | By Email