rfc8312bis
neqo
| rfc8312bis | neqo | |
|---|---|---|
| 1 | 12 | |
| 13 | 1,762 | |
| - | 0.4% | |
| 0.0 | 9.7 | |
| about 1 year ago | 1 day ago | |
| C | Rust | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rfc8312bis
-
S2n-QUIC (Rust implementation of QUIC)
CUBIC is a good baseline congestion controller. It's the default one that is being used in Linux, so it should provide adequate performance for a wide range of use-cases. Plus it's not so "olde" - the specification is actively improved (see https://github.com/NTAP/rfc8312bis), and the implementation of the algorithm inside s2n-quic even lead to the discovery of spec gaps that had been fixed as part of this effort.
Like most other QUIC libraries the congestion controller is also pluggable. So if a different one makes more sense for a particular use-case, it could be integrated in the future.
neqo
- What's the status of Servo right now?
-
Any rust implementations of WebTransport ?
Neqo (Mozilla) and Quiche (Cloudflare) both implement QUIC and HTTP/3. I believe they are both developing an implementation of WebTransport.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
neqo
-
Firefox – Fix parsing of content-length http3 header
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.
-
Which QUIC crate should I use
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.
-
QUIC is now RFC 9000
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
-
QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
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
-
Experiments with h3 clients + Envoy
mozilla/neqo
What are some alternatives?
s2n-quic - An implementation of the IETF QUIC protocol
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
trident - Storage orchestrator for containers
udp2raw - A Tunnel which Turns UDP Traffic into Encrypted UDP/FakeTCP/ICMP Traffic by using Raw Socket,helps you Bypass UDP FireWalls(or Unstable UDP Environment)
delight - A Spark UI and Spark History Server alternative with CPU and Memory metrics! Delight is free, cross-platform, and open-source.
quinn - Async-friendly QUIC implementation in Rust
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
hysteria - Hysteria is a powerful, lightning fast and censorship resistant proxy.
s2n - An implementation of the TLS/SSL protocols
quicly - A modular QUIC stack designed primarily for H2O