Found 2 records.

Status: Held for Document Update (2)

RFC 8441, "Bootstrapping WebSockets with HTTP/2", September 2018

Errata ID: 5500
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Loïc Hoguin
Date Reported: 2018-09-21
Held for Document Update by: Barry Leiba
Date Held: 2020-04-01

Section 3 says:

Using a SETTINGS parameter to opt into an otherwise incompatible
protocol change is a use of "Extending HTTP/2" defined by Section 5.5
of [RFC7540].  Specifically, the addition a new pseudo-header field,

It should say:

Using a SETTINGS parameter to opt into an otherwise incompatible
protocol change is a use of "Extending HTTP/2" defined by Section 5.5
of [RFC7540].  Specifically, the addition of a new pseudo-header field,

Notes:

I think it's missing a word.

Errata ID: 8250
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Christoph Göpfert
Date Reported: 2025-01-14
Held for Document Update by: RFC Editor
Date Held: 2025-01-21

Section 4 says:

   o  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.  

It should say:

   o  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

--VERIFIER NOTES--
This is regarding the link generated in the rfc2html output, not the RFC itself (https://www.rfc-editor.org/rfc/rfc8441.txt).

Report New Errata