Visual RFC.
ALL RFCs / RFC 9293
Read the RFC ↗
RFC 9293 / CONNECTION LIFECYCLE

Resets & idle probes

11

A reset aborts a connection. Keep-alive probes, when enabled, test an idle connection without implying guaranteed failure detection.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 9293 · § 3.5.3EXAMPLE
4 / 4
Resets & idle probesA reset passes a validation gate before abort, while a separate idle-probe exchange remains non-destructive.ABRUPT TERMINATIONIncoming RSTcheck state + sequencevalidateConnection abortsapplication errorOPTIONAL IDLE KEEP-ALIVELocal TCPPeer TCPprobeACKOne missing probe reply is not proof of failure
04
Keep an idle connection active.

A missing reply to one probe alone is not proof of a failed connection.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A control flag is interpreted in context.

  • RST validation depends on the TCP state and sequence information.
  • TCP must not answer a received RST with another RST.
  • Keep-alives are optional, default off, and must be configurable per connection; one unanswered probe cannot establish that the peer is dead.
DETAILS

RFC 5961 describes additional reset defenses with specific applicability. They are not a substitute for cryptographic protection.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A reliable byte stream
  2. Headers & connections
  3. Three-way handshake
  4. Sequence & acknowledgment
  5. Initial sequence numbers
  6. Loss & retransmission
  7. Flow control
  8. Congestion control
  9. Segments & small writes
  10. Graceful close
  11. Resets & idle probes
  12. Security & the consolidated spec
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗