Retry stays in the transcript
03HelloRetryRequest changes the offered key share without erasing the first ClientHello from the authenticated history.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 2.1 ↗
RFC 9846 · § 2.1EXAMPLE
3 / 3
03
Second ClientHello
Send the requested share; keep the initial exchange bound into the transcript.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
An unacceptable key share can trigger HelloRetryRequest.
- An unacceptable key share can trigger HelloRetryRequest.
- The client sends an appropriate new share in a second ClientHello.
- The transcript incorporates the initial ClientHello and retry rather than resetting.
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