There were several requests for QUIC support, which is still experimental. There is Google Chromium documentation. Appropriate IETF discussion can be found in this video. This paper can be a good point to start learning the protocol. Current status of the QUIC discussions can be found at IEFT meetings.

The source code of QUIC library.

Also see this video from BlackHat'16 https://www.youtube.com/watch?v=wCa5nylzJCo , which discusses the protocol from security point of view.

ngtcp2 and nghttp3 have compatible licenses and can be used as a foundation for the QUIC handshakes and HTTP/3, while https://github.com/lxin/quic provides the in-kernel QUIC transport.

Design considerations

Do not multiplex multiple streams into one packet to avoid multiple streams stall in case of the packet loss.

Tools

• https://github.com/google/quic-trace
• QUICvis https://quic.edm.uhasselt.be/
• quiclog for network traffic observability and the protocol debugging, also see the FOSDEM talk for the usage examples

References

• https://h3.edm.uhasselt.be/, Resource Multiplexing and Prioritizationin HTTP/2 over TCP versus HTTP/3 over QUIC in particular
• RFC 8999 Version-Independent Properties of QUIC
• RFC 9000 QUIC: A UDP-Based Multiplexed and Secure Transport
• RFC 9001 Using TLS to Secure QUIC
• RFC 9002 QUIC Loss Detection and Congestion Control
• QPACK: Field Compression for HTTP/3
• RFC 9218 Extensible Prioritization Scheme for HTTP
• Extending HTTP Semantics (draft)
• Revision of HTTP caching (draft)
• QUIC discussion in our HTTP/2 implementation HTTP/2 #309