Please Whitelist This Site? I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :) If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads. If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK. Thanks for your understanding! Sincerely, Charles Kozierok Author and Publisher, The TCP/IP Guide

NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The TCP/IP Guide  9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)       9  TCP/IP Transport Layer Protocols            9  Transmission Control Protocol (TCP) and User Datagram Protocol (UDP)                 9  TCP/IP Transmission Control Protocol (TCP)                      9  TCP Message Formatting and Data Transfer

TCP Maximum Segment Size (MSS) and Relationship to IP Datagram Size 1 2 3 4 5 6 TCP Immediate Data Transfer: "Push" Function

The TCP connection establishment process is employed by a pair of devices to create a TCP connection between them. Once all the setup is done, transmission control blocks (TCBs) set up, parameters have been exchanged and so forth, the devices are ready to get down to business: transferring data.

The sending of data between TCP devices on a connection is accomplished using the sliding window system we explored in the fundamentals section. It's now time to take a more detailed look at exactly how sliding windows are implemented to allow data to be sent and received. For ease of explanation, we'll assume that our connection is between a client and a server—this is easier than the whole “Device A / Device B” thing.

Each of the two devices on a connection must keep track of the data it is sending, as well as the data it is receiving from the other device. This is done by conceptually dividing the bytes into the categories we saw in the sliding windows overview. For data being transmitted, there are four transmit categories:

1. Transmit Category #1: Bytes Sent And Acknowledged
   
   
2. Transmit Category #2: Bytes Sent But Not Yet Acknowledged
   
   
3. Transmit Category #3: Bytes Not Yet Sent For Which Recipient Is Ready
   
   
4. Transmit Category #4: Bytes Not Yet Sent For Which Recipient Is Not Ready

For data being received, there is no need to separate into “received and acknowledged” and “received and unacknowledged” the way the transmitter separates its first two categories into “sent and acknowledged” and “sent but not yet acknowledged. The reason, of course, is that the transmitter must wait for acknowledgment of each transmission, while the receiver doesn’t need “acknowledgment” that it received something.

Thus, one receive category corresponds to Transmit Categories #1 and #2, while the other two correspond to Transmit Category #3 and Transmit Category #4 respectively, making three receive categories overall. To help make more clear how the categories relate, I am numbering them as follows:

• Receive Category #1+2: Bytes Received And Acknowledged. This is the receiver’s complement to Transmit Categories #1 and #2.
  
  
• Receive Category #3: Bytes Not Yet Received For Which Recipient Is Ready. This is the receiver’s complement to Transmit Category #3.
  
  
• Receive Category #4: Bytes Not Yet Received For Which Recipient Is Not Ready. This is the receiver’s complement to Transmit Category #4.

TCP Maximum Segment Size (MSS) and Relationship to IP Datagram Size 1 2 3 4 5 6 TCP Immediate Data Transfer: "Push" Function