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

"Jones, Morgan" <Morgan.Jones@viasat.com> Thu, 01 February 2024 07:57 UTC

Return-Path: <prvs=3761709fa4=morgan.jones@viasat.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 4A066C14F6B5 for <hybi@ietfa.amsl.com>; Wed, 31 Jan 2024 23:57:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level:
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=viasat.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4podc-HsS573 for <hybi@ietfa.amsl.com>; Wed, 31 Jan 2024 23:57:48 -0800 (PST)
Received: from mta-us-central-02.viasat.com (mta-us-central-02.viasat.com [8.37.103.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56FF1C14F6A7 for <hybi@ietf.org>; Wed, 31 Jan 2024 23:57:48 -0800 (PST)
Received: from pps.filterd (wdc1mta01.viasat.com [127.0.0.1]) by wdc1mta01.viasat.com (8.17.1.19/8.17.1.19) with ESMTP id 4116voTj004249; Thu, 1 Feb 2024 07:57:46 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viasat.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pp1; bh=JOEzW9pd63IfNFy9IbAuYrnyXyP1utZ626JeGN1DXuE=; b=Wr6eP6h25YkYXgK6+iKp8TKvXpAqzgDGy9n3latMbPml3lMyTFYPsO1NKzx0aAbF0jfX O2biiORSBy+C+lo7jTb3Eu/g5PmFN/QDEJSF2rQCiHL6I+n03VNouHsIybAcIFrZoPyl 6CYIum8VcbXOu+s7HxY4SwlaZphg1UFWiQ5B7Z9IELGnK5/4hGa2Z3Y2vuGrrbR38JvU Xqls6tjb1Ej8cf1f0PqTnuxig6o1wSj9rv36pgCcCjmCp1P/GowAvzRq2DmBeONvFXOY lWjhGprp+z2VozAjyEFSeRLlOOooJdon8WOPJW3YAKTqTm5JlPvuwwGJNgloWdZPNnAp pg==
From: "Jones, Morgan" <Morgan.Jones@viasat.com>
To: Adam Rice <ricea@google.com>, "alexey.melnikov@isode.com" <alexey.melnikov@isode.com>
CC: "hybi@ietf.org" <hybi@ietf.org>
Thread-Topic: [EXTERNAL] Re: [hybi] WebSocket Close Code: Timeout
Thread-Index: Adl3Bg5Vq8MNHqYySWuWWXri7qKlDDc5hMFgAEv4bgAADg6t8A==
Date: Thu, 01 Feb 2024 07:57:41 +0000
Message-ID: <559614142e5c40d0bda63c6758fd5cfb@viasat.com>
References: <602d83f1fc1b40fea701a5cd8ae4b3f0@viasat.com> <465d67cbde4b4a58a30e58fe43f3b597@viasat.com> <CAHixhFpmYNjrjTdKJqjSdBusHQUL29h486QJBwjg-71GByoZog@mail.gmail.com>
In-Reply-To: <CAHixhFpmYNjrjTdKJqjSdBusHQUL29h486QJBwjg-71GByoZog@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_559614142e5c40d0bda63c6758fd5cfbviasatcom_"
MIME-Version: 1.0
X-Proofpoint-ORIG-GUID: _dVe0AaHwMgJxWhZrTNRRpSwd6TMiOKV
X-Proofpoint-GUID: _dVe0AaHwMgJxWhZrTNRRpSwd6TMiOKV
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-01-31_10,2024-01-31_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 mlxscore=0 suspectscore=0 priorityscore=1501 impostorscore=0 clxscore=1011 bulkscore=0 spamscore=0 lowpriorityscore=0 malwarescore=0 phishscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311290000 definitions=main-2402010063
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/hXaaigGUeZgeZsFLCLXZJF8kGaM>
Subject: Re: [hybi] [EXTERNAL] Re: WebSocket Close Code: Timeout
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 01 Feb 2024 07:57:52 -0000

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.

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<mailto: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<mailto:hybi@ietf.org>' <hybi@ietf.org<mailto: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<mailto: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$>