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

Tobias Oberstein <tobias.oberstein@tavendo.de> Mon, 24 October 2011 15:06 UTC

From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Peter Thorson <webmaster@zaphoyd.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Date: Mon, 24 Oct 2011 08:06:41 -0700
Thread-Topic: [hybi] Fwd: failed TLS handshake: which close code?
Thread-Index: AcySVaHNvvVsYFhlT5CLM5HUgEh1mgAB8xwg
Message-ID: <634914A010D0B943A035D226786325D42D0B036E7D@EXVMBX020-12.exch020.serverdata.net>
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> <CADkeqZVvU31ML8tDAeYwnndvPZ9W8vEuzJksBm-4d1qv7MWObw@mail.gmail.com> <D178BFE3-2D77-43CA-92BE-7618E41325CB@zaphoyd.com>
In-Reply-To: <D178BFE3-2D77-43CA-92BE-7618E41325CB@zaphoyd.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Fwd: failed TLS handshake: which close code?
Precedence: list

> 1011/Internal Endpoint Error
>
> 1011 indicates that an endpoint is terminating the connection due to an unexpected condition that prevents it from safely continuing. The condition is the result of an internal logic error and not the fault of the remote peer except tangentially (i.e. in cases where the > > remote peer sent a valid frame that the terminating endpoint could not understand). More information about the error may be available in the terminating endpoint's log files.

+1

1012/Service Restart
1012 indicates that the service is restarted. a client may reconnect, and if it choses to do, should reconnect using a randomized delay of 5 - 30s.

Use case:
restart a service with 100k clients connected
clients present an informative user notification ("service restarting .. reconnecting in N secs) 
clients should not reconnect all at exactly the same time .. thus the randomized delay


1013/Service Overload
1013 indicates that the service is experiencing overload. a client should only connect to a different IP (when there are multiple for the target) or reconnect to the same IP upon user action.

Use case:
clients present an informative user notification ("service overload .. try later or try different IP)

Re: [hybi] failed TLS handshake: which close code? Richard L. Barnes
[hybi] failed TLS handshake: which close code? Tobias Oberstein
[hybi] Fwd: failed TLS handshake: which close cod… Alexey Melnikov
Re: [hybi] failed TLS handshake: which close code? Alexey Melnikov
Re: [hybi] Fwd: failed TLS handshake: which close… Peter Thorson
Re: [hybi] Fwd: failed TLS handshake: which close… Alexey Melnikov
Re: [hybi] failed TLS handshake: which close code? Alexey Melnikov
Re: [hybi] failed TLS handshake: which close code? Richard L. Barnes
Re: [hybi] Fwd: failed TLS handshake: which close… Peter Thorson
Re: [hybi] failed TLS handshake: which close code? Tobias Oberstein
Re: [hybi] failed TLS handshake: which close code? Tobias Oberstein
Re: [hybi] Fwd: failed TLS handshake: which close… Tobias Oberstein
Re: [hybi] Fwd: failed TLS handshake: which close… Tobias Oberstein
Re: [hybi] Fwd: failed TLS handshake: which close… Richard L. Barnes
Re: [hybi] Fwd: failed TLS handshake: which close… Tobias Oberstein
Re: [hybi] Fwd: failed TLS handshake: which close… John Tamplin
Re: [hybi] Fwd: failed TLS handshake: which close… Richard L. Barnes
Re: [hybi] Fwd: failed TLS handshake: which close… Richard L. Barnes
Re: [hybi] Fwd: failed TLS handshake: which close… Gabriel Montenegro