HTTP Upgrade in H3 is silliness

[LPardue]

Fixes #2889

[MikeBishop]

Is it worth adding a reference to RFC 8441? That's an alternative that covers what people looking for this functionality were probably trying to do.

[LPardue]

That's a good point, let me craft something up and I'll update the PR soon.

[MikeBishop]

Ping @LPardue, unless you'd like me to take it over.

[LPardue]

I'll get an update out tomorrow

[LPardue]

I'm actually not convinced that referencing 8441 will help clarify things here because the extension is H2 specific. No H3-equivalent exists (or at least, no H3 setting to enable the equivalent CONNECT behaviour exists).

[bagder]

I agree. I think referencing 8441 might just add to the confusion - even if something like 8441 certainly can be introduced.

[LPardue]

Some others have shown interest for defining/framing this capability in HTTP/3. I think that activity should consider ore broadly what text makes sense in the core document.

[MikeBishop]

Fair enough. Let's merge the rebased version, then, and leave the right way to do this for an H3 extension.