sctp
neqo
Our great sponsors
| sctp | neqo | |
|---|---|---|
| 1 | 12 | |
| 210 | 1,759 | |
| 3.3% | 1.2% | |
| 7.9 | 9.6 | |
| 9 days ago | about 14 hours ago | |
| Go | Rust | |
| MIT License | 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.
sctp
-
QUIC is now RFC 9000
I am sure there are even more implementations that I am not aware of.
* https://github.com/pion/sctp
* https://github.com/aiortc/aiortc/blob/main/src/aiortc/rtcsct...
* https://source.chromium.org/chromium/chromium/src/+/main:thi...
* https://github.com/sctplab/usrsctp
People don't make these decisions for technical reasons only. Career wise it is a bad choice to spend your time working on pre-existing technologies. You don't become a distinguished engineer by iterating on existing technologies. You become one by being the creator of something new.
I think QUIC is great and does a good job solving the problems it was designed to solve. It is disingenuous to pretend these decisions were made only for technical reasons.
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
There is also https://github.com/cloudflare/quiche by Cloudflare and https://github.com/mozilla/neqo by Mozilla.
-
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.
There are a few Rust alternatives for QUIC. Anyone tried them and have comments.
https://github.com/cloudflare/quiche
-
QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
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 :)
What are some alternatives?
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
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)
quinn - Async-friendly QUIC implementation in Rust
hysteria - Hysteria is a powerful, lightning fast and censorship resistant proxy.
quicly - A modular QUIC stack designed primarily for H2O
shadowsocks-rust - A Rust port of shadowsocks
usrsctp - A portable SCTP userland stack
s2n-quic - An implementation of the IETF QUIC protocol
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
orchid - Orchid: VPN, Personal Firewall