Bootstrapping WebSockets with HTTP/3
RFC 9220

Thanks to Vijay Gurbani for their General Area Review Team (Gen-ART) review
(https://mailarchive.ietf.org/arch/msg/gen-art/MA9WZc8SHIyjFmEN_0yCkUuFodo).

-------------------------------------------------------------------------------
All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

Section 3. , paragraph 2, nit:
>  RST exceptions are represented with an stream error (Section 8 of [HTTP3]) o
>                                      ^^
Use "a" instead of "an" if the following word doesn't start with a vowel sound,
e.g. "a sentence", "a university".

I concur with the others:

* Please finish or remove your Acknowledgments section.

* This needs a reference to HTTP/2.

* This was pretty dense for such a short document.

Hi,

Thanks for this document.  Given how short this document is, I found it somewhat harder to read than I expected, and hence I have a few minor and editorial suggestions (that you are welcome to take or leave) that may improve readability.

   [RFC8441] defines an extension to HTTP/2 which is also useful in
   HTTP/3.

1. I would suggest adding the referenced doc title here rather than leading the introduction with just the RFC reference number.
2. I think that you need at least an informative reference to HTTP/2.
3. The references to both HTTP/2 and HTTP/3 should be included when they are cited in the first sentence.

  3.  Websockets Upgrade over HTTP/3

4. I would suggest moving the 2nd paragraph that considers stream closure to the end of section 3, since the 1st, 3rd and 4th paragraphs all seem to be more closely related in their subject matter.

Thanks,
Rob

Thank you to Tirumaleswar Reddy for the SECDIR review.

I was dreading reviewing this document - I understand what websockets are, and how to use them, but much of how they are actually implemented is black magic to me.
Same for HTTP/3 - it's better and faster and securer(!) and all-around-wonderful... but "Bootstrapping WebSockets with HTTP/3" sounded suspiciously like "prefabulated amulite, surmounted by a malleable logarithmic casing in such a way that the two main spurving bearings were in a direct line with the panametric fan."

It turns out that this document simply reduces to a previous document which I also didn't understand, and so I manage to remain in blissful ignorance.
Kerphew!

Like Rob, I find this short document pretty hard to understand for non HTTP expert. Hence, a very superficial review of mine.

I was about to raise the same comment as Martin about the TODO acknowledgement section.