IETF Logo Mail Archive

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

Peter Thorson <webmaster@zaphoyd.com> Mon, 24 October 2011 13:10 UTC

Return-Path: <webmaster@zaphoyd.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 78AB221F8C8A for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 BK+MpEOSkMVg for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 06:10:34 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1B17721F8C16 for <hybi@ietf.org>; Mon, 24 Oct 2011 06:10:26 -0700 (PDT)
Received: from c-68-51-77-246.hsd1.il.comcast.net ([68.51.77.246]:36917 helo=[10.0.1.82]) by sh78.surpasshosting.com with esmtpa (Exim 4.69) (envelope-from <webmaster@zaphoyd.com>) id 1RIKHr-0006m7-Jo; Mon, 24 Oct 2011 09:09:55 -0400
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="iso-8859-1"
From: Peter Thorson <webmaster@zaphoyd.com>
In-Reply-To: <CADkeqZXDvu-JY8aZHJJPRH-_JnF196JjA_JG6X_1yrYSiAekuA@mail.gmail.com>
Date: Mon, 24 Oct 2011 08:09:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1251.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Source:
X-Source-Args:
X-Source-Dir:
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:10:52 -0000

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? 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"

v2.23.0 | Report a Bug | By Email