Re: [Editorial Errata Reported] RFC8441 (8250)

I would prefer if the RFC editor could simply sort out errata reports that are not about the RFCs, but about the HTMLizer’s guesses in presenting these RFCs.
We could have some boilerplate text why these errors occur and why we don’t put in the amount of work needed on our tooling not to have them.

Grüße, Carsten


> On 2025-01-14, at 17:45, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC8441,
> "Bootstrapping WebSockets with HTTP/2".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8250
> 
> --------------------------------------
> Type: Editorial
> Reported by: Christoph Göpfert <christoph.goepfert@hrz.tu-chemnitz.de>
> 
> Section: 4
> 
> Original Text
> -------------
> On requests bearing the :protocol pseudo-header field, the :authority pseudo-header field is interpreted according to Section 8.1.2.3 of [RFC7540] instead of Section 8.3 of that document.
> 
> 
> Corrected Text
> --------------
> On requests bearing the :protocol pseudo-header field, the :authority pseudo-header field is interpreted according to Section 8.1.2.3 of [RFC7540] instead of Section 8.3 of [RFC7540].
> 
> 
> Notes
> -----
> "Section 8.3" is incorrectly linked to the non-existing section 8.3 of RFC 8441 rather than section 8.3 of RFC 7540
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC8441 (draft-ietf-httpbis-h2-websockets-07)
> --------------------------------------
> Title               : Bootstrapping WebSockets with HTTP/2
> Publication Date    : September 2018
> Author(s)           : P. McManus
> Category            : PROPOSED STANDARD
> Source              : HTTP
> Stream              : IETF
> Verifying Party     : IESG
>

Received on Tuesday, 14 January 2025 20:11:03 UTC