Documentation request: QUIC in IIS

[shirhatti]

Issue originally posted at https://github.com/microsoft/msquic/issues/735 by @Jehoel

---

(As a preface, I apologise if this is the wrong place to post a question specific to IIS, though it does concern msquic - if this is the wrong place I hope that a blue-badger can route it to the right people internally)

Describe the feature you'd like supported

I'd like official documentation on the Windows, Windows Server, IIS, or msquic documentation sites describing how the in-box QUIC implementation works with IIS.

I noticed that in Windows 10 2004 that IIS seems to support QUIC natively (yay!), but the Help button in the Bindings dialog opens up the documentation for Windows Server 2012 (wat):

...which means I have no idea what the current level of support for QUIC, HTTP/3 and HTTP/2 is inside IIS - nor how I can configure it if I need to.

I also noticed that ARR hasn't been updated since version 3.0 was released in 2013, and it's unclear to what extent ARR 3.0 supports QUIC and HTTP/2 or not. As IIS is frequently used as a reverse-proxy on Windows, especially with ASP.NET Core applications surely it's important for everyone to understand the current (and future/planned) level of support for QUIC in Microsoft's web-server stack.

I'd also like to know to what extent we can use QUIC without TLS in IIS. As far as I can tell QUIC is only configurable with a HTTPS binding and not HTTP, but due to the lack of documentation I have no way of knowing for sure.

Finally, I'd have thought that adding QUIC support in-box to IIS would be worthy of a big announcement, but the IIS team blog hasn't been updated since 2018, nor anything relevant in the wider IIS blog site. Regarding HTTP/2: there's only a single article from a team-member's personal blog from 2015.

Proposed solution

What are the benefits/reasons for having this feature?

It makes Microsoft look less bad.

Additional context

None.