As I described in The Current Plan for Haskell QUIC, I have released the followings:
tls v1.5.5 provides the
Network.TLS.QUIC module. If you are interested in how this module has been improved, please read Improving QUIC APIs of the TLS library in Haskell.
As I explained in Implementing HTTP/3 in Haskell, http2 v3.0.0 or later provides both client and server libraries with the abstraction for HTTP requests and responses. These version resist to some HTTP/2 DoS attacks.
quic provides the QUIC APIs based on Haskell's lightweight threads. The architecture described in Implementation status of QUIC in Haskell is still valid. Runner modules for client and server are divided into
According to private discussion after Migration API for QUIC clients,
Network.QUIC.Client provides both automatic migration and manual migration.
As explained in Developing QUIC Loss Detection and Congestion Control in Haskell, this library implements the congestion control defined in RFC9002.
This library provides HTTP/3 (on QUIC). The encoder does not use the dynamic table at this moment.
warp-quic library is to provide Web Application Interface(WAI) to HTTP/3. In other words, this is a QUIC wrapper for Warp.
mighttpd2 version 4.0.0 now provides the HTTP/3 (on QUIC) functionality based on
warp-quic. Also, the configuration is now based on Dhall.
To create UDP connected sockets on Linux, mighttpd2 drops capabilities except
CAP_NET_BIND_SERVICE as described in Haskell vs Linux capabilities.
I wrote an article about implementation of QUIC in Haskell in Internet Infrastructure Review（IIR）Vol.52. This article is written in Japanese but will be translated into English within a month.