neqo VS base-drafts

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

neqo

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

Mozilla has a Rust QUIC implementation (one of three good ones in Rust) https://github.com/mozilla/neqo

I'm not sure why it's not used here.

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.

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

Btw, the QUIC library that Firefox relies on is written in Rust: https://github.com/mozilla/neqo

A bit weird though that they didn't cooperate with existing Rust quic stacks like quinn.

The reason is the need to have total flexibility (control). [0]

I reckon to make it as painless as possible to integrate it into Firefox. Also probably a tiny bit of not-invented-here syndrome too :)

[0] https://github.com/mozilla/neqo/issues/81

After lots of hard work, we're excited to open-source [s2n-quic](https://github.com/aws/s2n-quic), a Rust implementation of the [IETF QUIC protocol](https://quicwg.org/). Feel free to ask any questions here in the comments or by [opening an issue](https://github.com/aws/s2n-quic/issues/new/choose). Thanks!

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.

> Every app has to implement it itself

No? I'll just link against one of the cross platform libraries that implements it, the same as for any other networking protocol. (Ex https://github.com/microsoft/msquic)

Also see: https://github.com/quicwg/base-drafts/wiki/Implementations

> same as for TLS, making fewer apps implement it without a lot of extra work

... do you not just link against a relevant networking library at this point? If not, why?!

IETF work is conducted mostly on email lists, hence the "many thousands of emails".

For some newer work like QUIC, GitHub is used to maintain a more to-the-minute shared view of the documents, and then again as mentioned in the text you quoted, GitHub Issues and PRs are used to manage the document, particularly by the most active participants.

https://github.com/quicwg/base-drafts - of course raising issues or PRs for them now won't do anything useful for you, because these RFCs were published. But you can see there were thousands of commits, one of the last being Martin Thompson's minor typographical tweaks summarised as "DOES IT NEVER END?!?".