quiche VS quinn

Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.

Neqo (Mozilla) and Quiche (Cloudflare) both implement QUIC and HTTP/3. I believe they are both developing an implementation of WebTransport.

quiche

There is also https://github.com/cloudflare/quiche by Cloudflare and https://github.com/mozilla/neqo by Mozilla.

As an code hobbyist I'm working on an opensource project where I would be happy to use QUIC. I did a little research and found Quinn and Quiche but also the Mozilla's implementation for which I couldn't find crate Neqo.

Check out Cloudflare's open source implementation of QUIC written in Rust (aka Quiche)

Background: I wanted a secured UDP network for some of my devices (before I knew of WireGuard®) but could not find one that I can customize to support sending unreliable data (e.g. video stream) (before I knew of Datagram extension). quic-go was hard to compile last time I tried and I couldn't use/extend its QUIC APIs as they are under "internal" package. Others I found require C/C++ libraries which are difficult to cross-compile. I really like quiche APIs and even tried its C bindings but, you know, Cgo is not Go.

enet - Golden standard, tested and reliable - Not native rust - Does not seem to be popular in rust turbulence - Readme says it is not stable, but last meaningful commit was 1 year ago - Lacking documentation and examples - Not very popular laminar - Last meaningful release was 3 years ago (ignoring changes that fix typos etc.) - Despite this, everywhere (book, readme) there are mentions that it is under "active development" - Created for Amethyst, which is dead. I am kinda fearful that the same thing will happen to this lib. Tachyon - New and not tested in the battle - Many features that other libraries have planned, Tachyon actually has implemented - Lacking documentation (except for one big readme file), tests, examples Quinn - Big, under active development (daily commits), very popular because web development. - Modular, ability to just use core implemetation: quinn-proto - Do i really need TLS certificates and cryptography for my playing with friends game server? - Stream based, I would need to implement recv/send messages on top of it (not that hard tbh) - Only reliable stream and "unreliable" messages.

I'm personally following the development H3 (Hyperium) (HTTP/3 implementation), which is built on top of Quinn (QUIC implementation). Sadly the project has slowed down due to personal circumstances of its main developer and WebTransport isn't currently in their roadmap.

quinn

As an code hobbyist I'm working on an opensource project where I would be happy to use QUIC. I did a little research and found Quinn and Quiche but also the Mozilla's implementation for which I couldn't find crate Neqo.

Maybe check out laminar and quinn, which implement custom protocols on top of UDP (quinn implements QUIC), to get an idea on how to do things.

Is it possible to compile quicly cli (referenced in the blog post) with musl instead of glibc. I had to add signal.h and it then compiled successfully but I got illegal instruction segfault when executing cli.

https://github.com/h2o/quicly

There are a few Rust alternatives for QUIC. Anyone tried them and have comments.

https://github.com/cloudflare/quiche

https://github.com/quinn-rs/quinn

https://github.com/mozilla/neqo

See also quinn

quinn-rs/quinn