Early data still needs replay handling
05A repeated encrypted early request can cause repeated application effects.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 8 ↗
RFC 9846 · § 8EXAMPLE
3 / 3
03
Replay-aware application
Apply server replay controls and application duplicate handling.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
TLS provides no inherent universal replay protection for 0-RTT.
- TLS provides no inherent universal replay protection for 0-RTT.
- Clients may send only early data they judge safe to replay.
- Applications must address duplicate effects across separate TLS connections.
The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy