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

[Peter Thorson <[e-mail]>]

On Oct 24, 2011, at 8:19 , Alexey Melnikov wrote:

> On Mon, Oct 24, 2011 at 2:09 PM, Peter Thorson <[e-mail]> 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.


I that case like to propose the following code:

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.