Simple definition
HTTP/3 can use QUIC's 0-RTT resumption to reduce connection setup latency, subject to replay-related limitations.
Purpose and use
HTTP/3 0-RTT can send selected application data while resuming a QUIC connection, before the new handshake completes.
How does it work?
The client reuses information from an earlier connection, and the server can accept or reject this early data.
Example and verification
Before enabling it for an application, identify eligible requests and verify that replay cannot duplicate sensitive operations.
Points to watch
The improvement reduces startup waiting rather than eliminating all latency. Early data has replay-protection limitations.
In short
0-RTT requires suitable application policy beyond the server merely supporting HTTP/3.