Nick Banks

If you're interested in using MsQuic for QUIC, let me know. I think it'd be really cool to collaborate.

I can't sign up to do any real work. I can review code, answer questions, and help with design. My team owns many of the networking protocols (IP, UDP, TCP,...

I believe QUIC can benefit a VPN solution regardless of if you use it to proxy IP packets or simply redirect TCP payload. bizzbyster already outlined many of the benefits...

@laurentsimon any idea on when you might add PR support? I will be blocking dependabot updates (i.e. [this PR](https://github.com/microsoft/msquic/pull/2412)) for this action until I can safely merge the latest without...

Why is that necessary? As you mentioned in your (1) above no token should be necessary since you'd just be querying state, not publishing anything for PRs.

In my experience, if you're debugging an incident, you need to know the exact line of code, the exact reason why a drop happened, because you need to figure out...

Looking at our (currently 79) drop reasons in MsQuic, I think the following top-level categories would be reasonable: - Internal Error (not initialized, OOM, etc.) - Rejected (internal limits reached,...

Here's an example scenario where having CPU information per event is key to diagnosing issues: https://github.com/microsoft/msquic/blob/main/docs/TSG.md#diagnosing-rss-issues

If this was supported, it would have to be per-event. When you have multiple threads firing off events in parallel, any/every thread may be generating an event at any time,...

FYI, [here](https://github.com/microsoft/msquic/blob/main/src/plugins/trace/dll/DataModel/QuicEvent.cs#L187) is the base (C#) object for events in the WPA event processing code. Generically, every event has at least an ID, timestamp, processor, thread ID, process ID and...