Re: New Version Notification for draft-sbarta-tolerating-00.txt

Please don't pick explicit status code numbers in drafts before adoption.  The best practice is to notate the proposed status code as "1TBD" or similar, as the final value will be chosen by the working group.  Otherwise, there is a risk of early implementations polluting the codepoint space.

Personally, I don't understand why a new status code is needed at all.  A response header seems sufficient to accomplish the same result.

--Ben
________________________________
From: Silas Barta <sbarta@gmail.com>
Sent: Thursday, April 3, 2025 11:20 AM
To: Willy Tarreau <w@1wt.eu>
Cc: Ryan Globus <rglobus@apple.com>; Ben Schwartz <bemasc@meta.com>; ietf-http-wg@w3.org <ietf-http-wg@w3.org>
Subject: Re: New Version Notification for draft-sbarta-tolerating-00.txt

Okay, reviewing the 100 series, I concur, this makes more sense there. I can't believe I didn't consider it. So, for the next revision, I think I should make this either its own 100-series status code -- say 197 Tolerating -- or a standardized

Okay, reviewing the 100 series, I concur, this makes more sense there. I can't believe I didn't consider it.

So, for the next revision, I think I should make this either its own 100-series status code -- say 197 Tolerating -- or a standardized header within the existing 103 Early Hints.

Thoughts?

On Thu, Apr 3, 2025 at 4:40 AM Willy Tarreau <w@1wt.eu<mailto:w@1wt.eu>> wrote:
On Wed, Apr 02, 2025 at 08:26:42AM -0700, Ryan Globus wrote:
> I agree with Ben that a 1xx status code makes more sense for this use case, given their definitions in https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes<https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc9110.html*name-status-codes__;Iw!!Bt8RZUm9aw!4goQzEO8cbXFnZHZ88ycZRAkugN41pK_xLWHd9MWtB6wgJeCiIBIR5oYVlrnOaf-fFOx0-hTPw$>:
>
> * 1xx (Informational): The request was received, continuing process
> * 3xx (Redirection): Further action needs to be taken in order to complete the request
>
> Best,
> Ryan

Agreed!

Willy

Received on Thursday, 3 April 2025 18:35:52 UTC