Re: [hybi] [EXTERNAL] Re: WebSocket Close Code: Timeout

Hi all,

On 01/02/2024 07:57, Jones, Morgan wrote:
>
> Adam,
>
> Ah, thank you for the heads-up. Looks like Dr. Alexey Melnikov is the 
> point of contact for close codes despite a lot of those discussions 
> taking place on the hybi list.
>
> I assume these emails were not making their way to him so I’ve 
> forwarded him the thread.
>
I am sorry I missed the original request. Typically one requests new 
allocations in the 3XXX range by emailing IANA directly <iana@iana.org> 
or using the online web form 
<https://www.iana.org/form/protocol-assignment> and pointing to the 
<https://www.iana.org/assignments/websocket/websocket.xhtml> registry in 
the form.

Requests in the 3XXX range don't need my approval.

Morgan, if you want to email me directly, I can help you with the 
submission process.

Best Regards,

Alexey

> Thanks,
>
> Morgan Jones
>
> Advanced Network Systems
>
> Applications Lead // Viasat Secure Mobile
>
> *From:* Adam Rice <ricea@google.com>
> *Sent:* Wednesday, January 31, 2024 11:36 PM
> *To:* Jones, Morgan <Morgan.Jones@viasat.com>
> *Cc:* hybi@ietf.org
> *Subject:* [EXTERNAL] Re: [hybi] WebSocket Close Code: Timeout
>
> The hybi working group no longer exists, so there's no-one to do the 
> work. I don't know whether it would be possible to just go ahead and 
> register the code with IANA yourself. I don't know by what process 
> code 3003 got added. RFC6455
>
> The hybi working group no longer exists, so there's no-one to do the work.
>
> I don't know whether it would be possible to just go ahead and 
> register the code with IANA yourself. I don't know by what process 
> code 3003 got added.
>
> RFC6455 says that codes 1000-2999 have to be set in a "permanent and 
> readily available public specification" which is maybe why it's easier 
> to add a code in the 3000 range.
>
> Thanks,
>
> Adam
>
> On Wed, 31 Jan 2024 at 11:22, Jones, Morgan <Morgan.Jones@viasat.com> 
> wrote:
>
>     Hi there,
>
>     We are still in need of this status code.
>
>     Thanks,
>     Morgan Jones
>     Software Engineer | Viasat Secure Mobile
>
>     -----Original Message-----
>     From: Jones, Morgan
>     Sent: Monday, April 24, 2023 4:40 PM
>     To: 'hybi@ietf.org' <hybi@ietf.org>
>     Subject: WebSocket Close Code: Timeout
>
>     Hello,
>
>     I would like to reserve a status code similar to HTTP 408 Request
>     Timeout, simply meaning "Timeout".
>
>     The description is similar to 408: The server has decided to shut
>     down the connection. This is useful for WebSocket connections that
>     should have an upper limit on their time spent open.
>
>     I can see how this would be common enough to take the next code in
>     the list, 1016, but it also seems that 3003 is being used for
>     Forbidden in a similar manner to 403 (despite 3001 mismatching),
>     so I would like to propose 3008 as an alternative.
>
>     Let me know what you think. Our usecase is that we'd like to time
>     out certain WebSocket connections after an upper limit.
>
>     Thanks,
>     Morgan Jones
>     Viasat Secure Mobile
>
>     _______________________________________________
>     hybi mailing list
>     hybi@ietf.org
>     https://www.ietf.org/mailman/listinfo/hybi
>     <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/hybi__;!!NiYMbFKv!Lg0pps4IZx-WkgChQ_ZbX2XJGKJKzj12ExEkqMHLT4ST_KTdAB-8DHCQmo7v4-ERcHAiKZvqgZEFxHY$>
>