|
Figure 16.3 |
Examples of older protocol stacks that have been replaced by TCP/IP protocols. Although the stacks shared many general concepts, the details differed, making them incompatible. |
|
|
Figure 17.3 |
The internet concept. (a) The illusion of a single network that TCP/IP software provides to users and applications, and (b) the underlying physical structure in which a computer attaches to one physical network, and routers interconnect the networks. |
|
|
Figure 17.4 |
The five layers of the TCP/IP reference model. |
|
|
Figure 25.1 |
An example internet that illustrates why TCP is an end-to-end transport protocol. TCP views IP as a mechanism that allows TCP software on a host to exchange messages with TCP software on a remote host. |
|
|
Figure 25.2 |
Example of retransmission. Items on the left correspond to events in a computer sending data, items on the right correspond to events in a computer receiving data, and time goes down the figure. The sender retransmits lost data. |
|
|
Figure 25.3 |
Timeout and retransmission on two connections that have different round-trip delays. TCP optimizes throughput by using a round-trip estimate to compute a retransmission timer. |
|
|
Figure 25.4 |
A sequence of messages that illustrates TCP flow control when the maximum segment size is 1000 octets. A sender can transmit enough data to fill the currently advertised window. |
|
|
Figure 25.5 |
The 3-way handshake used to close a connection. Acknowledgements sent in each direction are used to guarantee that all data has arrived before the connection is terminated. |
|
|
Figure 25.6 |
The TCP segment format. Each message sent from TCP on one machine to TCP on another (both data and acknowledgements) uses this format. |
|
|
Figure 26.4 |
An example NAPT translation table for TCP connections from private computers 10.0.0.1 and 10.0.0.2. NAPT changes both the IP source address and TCP port number. In the example, both connections use TCP source port 30000 (unlikely, but possible). |
|
|
Figure 28.1 |
A client and server using TCP/IP protocols to communicate across an internet. The client and server each interact with a protocol in the transport layer. |
|
|
Figure 28.2 |
Two servers on a single computer accessed by clients on two other computers. Client 1 can access server 1, while client 2 accesses server 2. |
|
|
Figure 34.2 |
TCP connections between an FTP client and server during a file transfer, with an arrow showing the direction in which each connection was formed. Although the control connection remains open, the data connection is closed after the transfer completes. |
|
|
Figure 41.1 |
The first few steps that TCP/IP protocol software takes to obtain configuration information. T1 and T2 denote timeout values. |
|
Animation 20_1 |
TCP specifies a three-way handshake to establish a TCP connection between two computers |
|
|
Animation 20_2 |
TCP specifies a three-way handshake to terminate a TCP connection |
|
|
Animation 20_3 |
TCP uses sliding window flow control. The receiver defines the window, and the sender can transmit any of the data in the window. When the sender receives an acknowledgment, the window moves ahead to include new, unsent data. |
|
|
Animation 20_4 |
By changing the size of the window, the receiver can control the rate at which data are sent. |
|
|
Animation 20_5 |
If a segment is lost, the window does not advance until the segment is retransmitted and the sender receives the acknowledgment for the segment. When the receiver gets a segment out of order, it can send an acknowledgment for the highest received data byte without sending individual acknowledgments for the intermediate data. |
|
Data file 1 |
Trace of all IP traffic on Ethernet segment, including TCP |
|
|
Data file 2 |
Anonymous FTP session with dir, get and put |
|
|
Data file 3 |
Anonymous FTP session using mput in both ascii and binary modes |
|
|
Data file 4 |
Anonymous FTP session using mget in both ascii and binary modes |
|
|
Data file 5 |
TELNET session (headers only) |
|
|
Data file 6 |
SMTP session |
|
|
Data file 7 |
WWW browser session |
|
|
Data file 8 |
X Window System application protocol messages |
