base-drafts
s2n-quic
Our great sponsors
base-drafts | s2n-quic | |
---|---|---|
9 | 7 | |
1,609 | 1,066 | |
0.6% | 2.0% | |
0.6 | 9.3 | |
9 days ago | 3 days ago | |
Shell | Rust | |
- | 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.
base-drafts
-
Multipath TCP for Linux
QUIC is a step backwards here; it has no multipath support: https://lwn.net/Articles/964377/
Multipath: There are several areas where TCP still has an advantage over QUIC. One of those is multipath support. Multipath TCP connections can send data on different network paths simultaneously — for example, sending via both WiFi and cellular data — to provide better throughput than either path permits individually.
Server connection migration is explicitly forbidden by QUIC:
https://github.com/quicwg/base-drafts/pull/2031
- What does TCP/IP, OSI model even in means in job requirements
-
RFC 9114 – HTTP/3
https://github.com/quicwg/base-drafts/issues/253
TL;DR just like HTTP/2, we wanted to avoid friction in deploying these protocols. Having to rewrite URLs because of new schemes is pretty unpalatable, it has major impact. Instead, HTTP/3 can rely on other IETF-defined mechanisms like Alt-Svc (RFC 7838) and the more recent SVCB / HTTPS RR [1] DNS-based methods. The latter has been deployed on Cloudflare a while [2] and supported in Firefox. Other user agents have also expressed interest or intent to support it.
The net outcome is that developers can by and large focus on HTTP semantics, and let something a little further down the stack worry more about versions. Sometime devs will need to peek into that area, but not the majority.
[1] - https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-...
-
Announcing s2n-quic 1.0
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!
- The IETF QUIC Working Group
-
Crate to build network packets over UDP
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.
-
QUIC is now RFC 9000
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?!?".
- QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
s2n-quic
- Boletín AWS Open Source, Christmas Edition
-
Kani 0.28.0 has been released!
Yes, the Kani CI time for s2n-quic dropped by more than 25% with Kani 0.28.
- Best performing quic implementation?
-
From Fuzzing to Proof: Using Kani with the Bolero Property-Testing Framework
Packet parsing is a great application for this type of testing. We've used bolero/Kani in a bunch of s2n-quic's codec implementations - example.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
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.
What are some alternatives?
shadowsocks-rust - A Rust port of shadowsocks
quinn - Async-friendly QUIC implementation in Rust
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
aiortc - WebRTC and ORTC implementation for Python using asyncio
tuic - Delicately-TUICed 0-RTT proxy protocol
quicly - A modular QUIC stack designed primarily for H2O
neqo - Neqo, an implementation of QUIC in Rust
rustls - A modern TLS library in Rust
message-io - Fast and easy-to-use event-driven network library.
rfc8312bis - Revision of RFC8312 "CUBIC for Fast Long-Distance Networks"