MsQuic user introductions

[Guillaume Hetier (guhetier)]

You are using MsQuic? Let us know how with a post in this discussion!

Knowing our users lets us prioritize work and keep improving MsQuic in the best possible direction.

You can also give us a wave on Discord!

[Giovanni Marzot (gmarzot)]

someone has to be first. I am doing some work in relation to the MoQ WG and have been developing a python asyncio package that implements the MoQT protocol, aiomoqt. As an alternative to the Python QUIC library, aioquic I am exploring Python/Cython bindings to MsQuic

[William Yang (qzhuyan)]

MoQ looks very promising! great work!

[Henri Prudhomme (Henripru)]

QUIC as an RFC fits a lot of blue-chip use cases for modern p2p communication. Features I particularly like from msquic:

1. cross-platform
2. certificate-based, client-server authentication and encryption
3. reliable, ordered, high-bandwidth packet streaming

Other reasons it is desirable are its licensing, simplicity, and live community.

[William Yang (qzhuyan)]

EMQX implements MQTT over QUIC with msquic, providing better connectivity in IoT scenarios.

[Hari Hara Naveen S (Johan511)]

I am using MsQuic to implement the MOQT draft and test how it performs in various scenarios. Choosing MsQuic has been by far the best decision I have made in this project thanks to it's in-depth documentation, friendly community and commitment to open-source. Looking forward to see more features and improvements soon.
:)

[Bob (bobvhood)]

Hi Everyone, We have created VpnHood! Which is entirely on .NET. I have already made a QUIC echo server to evaluate its accessibility in restricted areas, such as China. Additionally, I prepared the platform to establish a tunnel connection using QUIC instead of TCP or pure UDP. We hope to integrate QUIC soon.

[Bob (bobvhood)]

We would like to use MSQUIC on our project to demonstrate it as a sample purely in .NET. We sacrificed some performance for code readability and have a high-level modular design. The interesting thing is that VpnHood achieved better performance in some scenarios.

[Mike (mikebiz)]

Starting my journey with msquic to build out some POCs. Can I find a current release with the msquic.h/.lib/.dll that I can deploy to my dev machine? I'm working on a multi-tier overlay network for network packet distribution and the first tier will be based on quic to manage connections.

[Anthony Rossi (anrossi)]

Welcome to the project! We're currently working out some kinks with the release automation. For now, you could use one of the old releases to get started. Unless you need a feature introduced in a newer release, then you'll need to build the binaries.

[Akash Balasubhramanyam (akashblsbrmnm)]

Starting to adopt to QUIC over TCP. Doing some research on adopting the libraries. I'm working on an Embedded Platform. Has anyone tried building with Yocto project ?

[William Yang (qzhuyan)]

Curious to know why over tcp?

For the one over udp we have a PoC here running on esp32 , not using msquic

https://github.com/emqx/ESP32-QUIC

Starting to adopt to QUIC over TCP. Doing some research on adopting the libraries. I'm working on an Embedded Platform. Has anyone tried building with Yocto project ?

[Akash Balasubhramanyam (akashblsbrmnm)]

I'm also thinking of considering ngtcp2 and nghttp3 for my project. I am working on a project for replacing websocket tcp with quic protocol. This is for C firmware on embedded platforms.

[Guillaume Hetier (guhetier)]

I'm interested too in why using QUIC over TCP. There is a lot of discussion around QMUX (which is largely QUIC over TCP+TLS), but this is not an accepted RFC yet.

Do you have a constraint preventing UDP, or are you trying to use QUIC instead of TCP?

[vindicatorr]

👋 It's been 3 years since I've touched msquic, and I'm peeking at it again.

On Linux, without msquic, one gets Unable to bind an HTTP/3 endpoint. This could be because QUIC has not been configured using UseQuic, or the platform doesn't support QUIC or HTTP/3. from ASP.NET's WebHostBuilderQuicExtensions.UseQuic.

Building is easy, but I set -DQUIC_USE_EXTERNAL_OPENSSL=ON -DQUIC_USE_SYSTEM_LIBCRYPTO=ON -DQUIC_TLS_LIB=openssl so it can make use of what I already have.

But out of curiousity, I ran pacman to see what quic packages exist and I noticed libngtcp2 which I already have installed.
It's required by curl, and I'm in IRC with them right now. They pointed out that they used to use MSH3, but dropped it last year: http://github.com/curl/curl/pull/17729
https://daniel.haxx.se/blog/2025/07/29/carving-out-msh3/

I hope at some point there becomes a single winner so replication isn't needed, but if curl has dropped it, that's a big hit.

[Guillaume Hetier (guhetier)]

Hi! Welcome back!
The .Net part might be better answered by .Net folks (Marie Píchová (@ManickaP))

While msh3 is using MsQuic, it isn't a project supported by Microsoft.
We are currently working on using OpenSSL 3.5 by default when it is available, this is a bit of debt we need to buy back as OpenSSL 3.5 support is major distribution finally increases, so soon, the default build options should use the system openssl.