Skip to main content

QUIC Retry Offload

Document Type Expired Internet-Draft (quic WG)
Expired & archived
Authors Martin Duke , Nick Banks
Last updated 2022-11-30 (Latest revision 2022-05-25)
Replaces draft-duke-quic-retry-offload
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state Parked WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


QUIC uses Retry packets to reduce load on stressed servers, by forcing the client to prove ownership of its address before the server commits state. QUIC also has an anti-tampering mechanism to prevent the unauthorized injection of Retry packets into a connection. However, a server operator may want to offload production of Retry packets to an anti-Denial-of-Service agent or hardware accelerator. "Retry Offload" is a mechanism for coordination between a server and an external generator of Retry packets that can succeed despite the anti-tampering mechanism.


Martin Duke
Nick Banks

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)