Our great sponsors
-
It's definitely a valid question, with there being a lot of great QUIC implementations out there. We do believe, though, s2n-quic has a lot to offer with a high level of security, testing, performance, and features. Given that s2n-quic will eventually be integrated into AWS Services, we ultimately need direct ownership of fundamental libraries like s2n-quic, s2n-tls, etc. to be able to maintain that high level of security and performance for our customers.
-
There is also https://github.com/cloudflare/quiche by Cloudflare and https://github.com/mozilla/neqo by Mozilla.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
There is also https://github.com/cloudflare/quiche by Cloudflare and https://github.com/mozilla/neqo by Mozilla.
-
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!
-
You are correct. Definitely not to pick on the other implementations but through casual testing we've seen all of them panic on messages received over the wire. I don't think any of them have disclosure policies in place and/or there was no advisory issued.
-
quinn