Visual RFC.
ALL RFCs / RFC 9293
Read the RFC ↗
RFC 9293 / THE TCP MODEL

Headers & connections

02

TCP headers identify endpoints and carry the sequence, acknowledgment, window, and control information that drive the connection.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 9293 · § 3.1EXAMPLE
4 / 4
Headers & connectionsThe actual categories of TCP header fields become highlighted in reading order.TCP HEADER · schematic, not to scaleSource port 50000Destination port 443Sequence numberAcknowledgment numberOffset + flagsReceive windowChecksumUrgent pointerOptions, then payloadConnection state is indexed by the pair of IP:port sockets
04
Apply stateful rules.

An arriving segment is interpreted according to the current connection state.

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

Each connection needs its own state.

  • A connection is identified by its pair of sockets, each comprising an IP address and port.
  • The checksum covers the TCP header, data, and an IP pseudo-header.
  • Header options are variable length; the data offset locates the payload.
DETAILS

A checksum detects transmission corruption. It is not a cryptographic integrity or authenticity mechanism.

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 ↗