Not Duplicate All of MsQuic API?

[nibanks]

I wonder if there is a way to not have to duplicate all of the MsQuic API in the process of making msh3.... HTTP/3 really adds very minimal logic/functionality (i.e. headers) on top of QUIC, at least at a protocol level. But practically, all functionality exposed by QUIC would likely also need to be exposed by HTTP/3. There are two paths forward (I think):

Wrap Functionality

The current design path has required no dependency on msquic.h from msh3.h. It is its own API. But this means the header has to redefine anything that is simply a pass through, resulting in a lot of duplication.

Passthrough Functionality

Instead of redefining everything, we could directly rely on definitions from msquic.h. This would change the dependency graph a little for clients. They'd depend on msquic.h directly.