TCP Protocol: From Packet Structure to Reliable Transmission Mechanisms

This article is not an introductory guide to the TCP protocol but is intended for learners who already have some foundational knowledge of networking. Before reading, it is recommended that you at least understand the basic concepts and working principles of TCP. This article aims to help you systematically connect fragmented TCP knowledge points into a complete framework.

To better understand the content, we recommend reviewing the following foundational materials first:

1. Ruan Yifeng’s blog post "Introduction to the TCP Protocol," which explains the core concepts of TCP in an easy-to-understand manner.
2. A video tutorial by "Code Novice" titled "Computer Networks - Analysis of a TCP Communication Process," which visually demonstrates the entire TCP communication process.

TCP (Transmission Control Protocol), as one of the core protocols of the transport layer, provides connection-oriented, reliable, byte-stream-based transmission services for upper-layer applications. Its reliability is achieved through the following core mechanisms:

1. Ordered Transmission: Data chunks are numbered using a sequence number mechanism.
2. Acknowledgment (ACK): The ACK mechanism ensures data delivery confirmation.
3. Error Recovery: Lost packets are handled through timeout retransmission.
4. Rate Adjustment:
   • End-to-end flow control (sliding window mechanism)
   • Network-level congestion control algorithms

A TCP packet is essentially a binary data transmission unit, consisting of a fixed header and a variable data section. The standard header is 20 bytes long (excluding options), with the following structure:

0                   1                   2                   3   
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Source Port          |       Destination Port        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Sequence Number                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    Acknowledgment Number                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Data |           |U|A|P|R|S|F|                               |
| Offset| Reserved  |R|C|S|S|Y|I|            Window             |
|       |           |G|K|H|T|N|N|                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|           Checksum            |         Urgent Pointer        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    Options (if Data Offset > 5)               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Data                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Port Identification (16 bits each)

• Source Port: Identifies the sender’s application port.
• Destination Port: Identifies the receiver’s application port.
• Together, they define the endpoints of a TCP connection.

Sequence Control Fields (32 bits each)

• Sequence Number (Seq):
  • Indicates the position of the first byte of the current segment in the byte stream.
  • Randomly initialized during connection setup (ISN - Initial Sequence Number).
• Acknowledgment Number (Ack):
  • Indicates the next expected byte sequence number.
  • Implicitly confirms all data before this sequence number has been received successfully.

Control Flags (1 bit each)

• URG: Urgent pointer valid flag.
• ACK: Acknowledgment number valid flag (usually set to 1 after connection establishment).
• PSH: Instructs the receiver to immediately deliver data to the application layer.
• RST: Forces an abnormal connection reset.
• SYN: Synchronizes sequence numbers (used for connection setup).
• FIN: Graceful connection termination flag.

Flow Control Field

• Window Size: A 16-bit field indicating the available buffer space (in bytes) on the receiver’s side, forming the basis of sliding window flow control.

When first encountering the TCP packet structure, the numerous fields may seem overwhelming. It’s advisable not to rush to memorize all details at once but to gradually understand each field’s role in the context of actual communication processes discussed in later sections.

The TCP connection establishment process involves exchanging specific control packets (three-way handshake) to achieve the following goals:

1. Synchronize initial sequence numbers (ISN).
2. Exchange TCP parameters (e.g., window size, MSS).
3. Create and initialize socket data structures in both endpoints’ kernels.

This socket is essentially a complex state machine. TCP simulates the concept of a "connection" by maintaining this state machine. Notably, a TCP connection is not a physical link but a logical state maintained by both parties.

Detailed Three-Way Handshake Process

Let’s analyze the process using an example where a client (192.168.1.100) connects to a server (203.179.24.36:80):

1. SYN Packet (Client → Server)

   Sequence Number (Seq) = 123456789 (randomly generated ISN)  
   Acknowledgment Number (Ack) = 0  
   Control Flags = SYN  
   Window Size = 65535

   • Client enters the SYN_SENT state.
   • MSS option is typically negotiated here.

2. SYN-ACK Packet (Server → Client)

   Sequence Number (Seq) = 987654321 (server’s ISN)  
   Acknowledgment Number (Ack) = 123456790 (client’s ISN + 1)  
   Control Flags = SYN|ACK  
   Window Size = 8192

   • Server enters the SYN_RCVD state.
   • The acknowledgment of the client’s SYN is implicit in the Ack field.

Key Design Considerations

1. ISN Randomization:

   • Prevents interference from stale connections (old packets from the same connection tuple may still be in the network).
   • Security measure to prevent sequence number prediction attacks.

2. Sequence Number Semantics:

   • SYN and FIN flags each consume one sequence number.
   • During data transmission, sequence numbers increment by the byte count.

3. Why Three-Way Handshake?

   • Ensures bidirectional communication capability.
   • Prevents delayed connection requests from unexpectedly reaching the server.

Four-Way Handshake Example

Assume the current sequence numbers are:

• Active closer: Seq = 2000000000
• Passive closer: Seq = 3000000000

1. First FIN (Active → Passive)

   Seq = 2000000000  
   Ack = 3000000000  
   Flags = FIN|ACK

   • Active party enters FIN_WAIT_1.

2. Second FIN (Passive → Active)

   Seq = 3000000000  
   Ack = 2000000001  
   Flags = ACK

   • Passive party enters CLOSE_WAIT.
   • Active party moves to FIN_WAIT_2 upon receipt.

3. Third FIN (Passive → Active)

Deep Dive into TIME_WAIT State

The TIME_WAIT state lasts for 2MSL (Maximum Segment Lifetime), serving the following purposes:

1. Ensures Reliable Termination:

   • Guarantees the final ACK reaches the peer.
   • If the ACK is lost, the passive party retransmits FIN, and the active party can still respond.

2. Cleans Up Stale Packets:

   • Waits long enough for residual packets in the network to expire.
   • Prevents old data from being mistaken for new connections with the same tuple.

3. Practical Implications:

   • May cause port exhaustion on high-performance servers.
   • Can be mitigated using the SO_REUSEADDR socket option.

Through this carefully designed state machine, TCP achieves reliable end-to-end communication over the unreliable IP layer. Understanding these state transitions is crucial for diagnosing network issues and optimizing TCP performance.

Sliding Window Demonstration

Consider the following scenario:

• Initial sequence number: 1
• Send window size: 4 segments
• MTU: Fixed size

Phase 1: Initial Transmission

[Sender Actions]  
1. Send Segment 1 (Seq=1, Len=100) → Sequence space moves to 101  
2. Send Segment 2 (Seq=101, Len=150) → Sequence space moves to 251  
3. Send Segment 3 (Seq=251, Len=200) → Sequence space moves to 451  
4. Send Segment 4 (Seq=451, Len=50) → Sequence space moves to 501  
(Window exhausted; waits for ACKs)

Phase 2: Receiver Processing

[Receiver Actions]  
1. Successfully receives Segments 1, 2, 3 (450 bytes total).  
2. Sends Ack=451 (expects next byte 451).  
3. Receives Segment 4.  
4. Sends Ack=501.

Phase 3: Window Advancement

[Sender Actions]  
1. Upon Ack=451, window slides to 451.  
2. Upon Ack=501, window slides to 501.  
3. N...