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

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:

* 1xx (Informational): The request was received, continuing process
* 3xx (Redirection): Further action needs to be taken in order to complete the request

Best,
Ryan

> On Apr 2, 2025, at 8:16 AM, Silas Barta <sbarta@gmail.com> wrote:
> 
> No -- I'm comparing it to the redirection status codes like 301 and 302.
> 
> On Wed, Apr 2, 2025 at 7:44 AM Ben Schwartz <bemasc@meta.com <mailto:bemasc@meta.com>> wrote:
>>    A 397 response MUST be followed by another HTTP response, similar to
>>    other 300-series HTTP status codes, where such response makes the
>>    best guess at what the client intended
>> 
>> This seems like a mistake.  Did you mean "100-series"?
>> 
>> --Ben Schwartz
>> From: Silas Barta <sbarta@gmail.com <mailto:sbarta@gmail.com>>
>> Sent: Tuesday, April 1, 2025 1:57 PM
>> To: ietf-http-wg@w3.org <mailto:ietf-http-wg@w3.org> <ietf-http-wg@w3.org <mailto:ietf-http-wg@w3.org>>
>> Subject: Fwd: New Version Notification for draft-sbarta-tolerating-00.txt
>>  
>> Dear HTTP Working Group,
>> 
>> I submit this Internet Draft for your consideration.
>> 
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
>> Date: Tue, Apr 1, 2025 at 12:51 PM
>> Subject: New Version Notification for draft-sbarta-tolerating-00.txt
>> To: Silas Barta <sbarta@gmail.com <mailto:sbarta@gmail.com>>
>> 
>> 
>> A new version of Internet-Draft draft-sbarta-tolerating-00.txt has been
>> successfully submitted by Silas Barta and posted to the
>> IETF repository.
>> 
>> Name:     draft-sbarta-tolerating
>> Revision: 00
>> Title:    An HTTP Status Code to Indicate Request Noncomformity While Still Making Best-Effort Response
>> Date:     2025-04-01
>> Group:    Individual Submission
>> Pages:    5
>> URL:      https://www.ietf.org/archive/id/draft-sbarta-tolerating-00.txt <https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-sbarta-tolerating-00.txt__;!!Bt8RZUm9aw!_6_aSVrFB7STV7sE_BjACiI1ZgaiauKh9U1CeeJdHeAcMKdndPlcJlsmDG37b5azw27mLzG8eg$>
>> Status:   https://datatracker.ietf.org/doc/draft-sbarta-tolerating/ <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-sbarta-tolerating/__;!!Bt8RZUm9aw!_6_aSVrFB7STV7sE_BjACiI1ZgaiauKh9U1CeeJdHeAcMKdndPlcJlsmDG37b5azw24AfENRZA$>
>> HTMLized: https://datatracker.ietf.org/doc/html/draft-sbarta-tolerating <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-sbarta-tolerating__;!!Bt8RZUm9aw!_6_aSVrFB7STV7sE_BjACiI1ZgaiauKh9U1CeeJdHeAcMKdndPlcJlsmDG37b5azw24DFrqUjQ$>
>> 
>> 
>> Abstract:
>> 
>>    This document specifies a Hypertext Transfer Protocol (HTTP) status
>>    code for use when resource was accessed in a nonconforming manner
>>    but the request will be tolerated with reservation, while directing
>>    the client adhere to relevant protocols.
>> 
>> 
>> 
>> The IETF Secretariat
>> 
>>