Re: [hybi] Fwd: failed TLS handshake: which close code?

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 24 October 2011 13:19 UTC

Return-Path: <lunohod.baikonur@googlemail.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 A4AC021F8D88 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.972
X-Spam-Level:
X-Spam-Status: No, score=-102.972 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 nfuyXv5QWwEq for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:19:39 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id AD21B21F8D7E for <hybi@ietf.org>; Mon, 24 Oct 2011 06:19:39 -0700 (PDT)
Received: by iabn5 with SMTP id n5so9081709iab.31 for <hybi@ietf.org>; Mon, 24 Oct 2011 06:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Sxo8Rul4FeoarZXnhKcOn3oP/O7TgH/UMUbbQGBLxto=; b=bgEAAIWFg8pGXWPlL/xKs7P115wg9TQ6X1XAN9tafQKJyiLBqZ5etMdJte95K1Up6r Vzo2/798lnQSbZrZTQ3E6kDWgkVn8BxADy3VYRf++uZBe7Ylsrk/AFzRgUw9qr4rxkLQ cLp+7DCmmqaaPFSMpOSBzk3c0pf+yc+i91wkc=
MIME-Version: 1.0
Received: by 10.42.152.201 with SMTP id j9mr30423023icw.55.1319462378267; Mon, 24 Oct 2011 06:19:38 -0700 (PDT)
Sender: lunohod.baikonur@googlemail.com
Received: by 10.42.247.199 with HTTP; Mon, 24 Oct 2011 06:19:38 -0700 (PDT)
In-Reply-To: <0ED03DDD-1AF9-41F9-B5F0-2968BF16E378@zaphoyd.com>
References: <634914A010D0B943A035D226786325D42D0B036D6D@EXVMBX020-12.exch020.serverdata.net> <CADkeqZXXRkXCRrONLr5thwOqNVUxNWU0Q-9E0R0i=4S-bc-LFw@mail.gmail.com> <CADkeqZXDvu-JY8aZHJJPRH-_JnF196JjA_JG6X_1yrYSiAekuA@mail.gmail.com> <0ED03DDD-1AF9-41F9-B5F0-2968BF16E378@zaphoyd.com>
Date: Mon, 24 Oct 2011 14:19:38 +0100
X-Google-Sender-Auth: bDJj9Y8Dd0ETweu2JSbltEE-mQI
Message-ID: <CADkeqZVvU31ML8tDAeYwnndvPZ9W8vEuzJksBm-4d1qv7MWObw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary="90e6ba6e889c59e26a04b00b4682"
Cc: hybi@ietf.org
Subject: Re: [hybi] Fwd: failed TLS handshake: which close code?
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: Mon, 24 Oct 2011 13:19:40 -0000

On Mon, Oct 24, 2011 at 2:09 PM, Peter Thorson <webmaster@zaphoyd.com>wrote:

>
> On Oct 24, 2011, at 8:04 , Alexey Melnikov wrote:
>
> > That was supposed to be sent to the mailing list. The WG should consider
> adding multiple codes if needed.
> >
> > TLS handshake probably deserves a separate 1XXX close code.
>
> What is the procedure right now for adding more 1XXX close codes?


People should suggest specific close codes on the mailing list and, ideally,
suggest their description.

For codes recommended this week or next (basically before the final RFC is
published), there is a good chance that they can be included directly into
the RFC-to-be.

Close codes suggested later can still be added to the registry (they will
need a review by a yet-to-be-appointed Expert Reviewer -- IESG will take
care of this), but they will not appear in the RFC.

All of the codes will be seen in the IANA registry (<
http://www.iana.org/assignments/websocket/websocket.xml>)


> In addition to TLS stuff, I still think (and a few here have agreed) that
> we also need a 1XXX code similar in meaning to HTTP 500/"internal server
> error"

Agreed.