CHAPTER 23

Process-to-Process Delivery:
Solutions to Odd-Numbered Review Questions and Exercises

Review Questions
1. Reliability is not of primary importance in applications such as echo, daytime,
BOOTP, TFTP and SNMP. In custom software, reliability can be built into the cli-
ent/server applications to provide a more reliable, low overhead service.
3. Port addresses do not need to be universally unique as long as each IP address/port
address pair uniquely identify a particular process running on a particular host. A
good example would be a network consisting of 50 hosts, each running echo server
software. Each server uses the well known port number 7, but the IP address,
together with the port number of 7, uniquely identify a particular server program
on a particular host. Port addresses are shorter than IP addresses because their
domain, a single system, is smaller than the domain of IP addresses, all systems on
the Internet.
5. The minimum size of a UDP datagram is 8 bytes at the transport layer and 28 bytes
at the IP layer. This size datagram would contain no data–only an IP header with
no options and a UDP header. The implementation may require padding.
7. The smallest amount of process data that can be encapsulated in a UDP datagram
is 0 bytes.
9. See Table 23.1.

Table 23.1 Answer to the Question 9.

Fields in UDP Fields in TCP Explanation
Source Port Address Source Port Address
Destination Port Address Destination Port Address
Total Length There is no need for total length.
Checksum Checksum
Sequence Number UDP has no flow and error control.
Acknowledge Number UDP has no flow and error control.
Header Length UDP has no flow and error control.

1
2

Table 23.1 Answer to the Question 9.

Fields in UDP Fields in TCP Explanation
Reserved UDP has no flow and error control.
Control UDP has no flow and error control.
Window Size UDP has no flow and error control.
Urgent Pointer UDP cannot handle urgent data.
Options and Padding UDP uses no options.

11.
a. None of the control bits are set. The segment is part of a data transmission with-
out piggybacked acknowledgment.
b. The FIN bit is set. This is a FIN segment request to terminate the connection.
c. The ACK and the FIN bits are set. This is a FIN+ACK in response to a received
FIN segment.

Exercises
13. See Figure 23.1.

Figure 23.1 Solution to Exercise 13

52010 69

48 0

Data
(40 bytes)

15. The server would use the IP address 130.45.12.7, combined with the well-known
port number 69 for its source socket address and the IP address 14.90.90.33, com-
bined with an ephemeral port number as the destination socket address.
17. 16 bytes of data / 24 bytes of total length = 0.666
19. 16 bytes of data / 72 byte minimum frame size = 0.222
21. It looks as if both the destination IP address and the destination port number are
corrupted. TCP calculates the checksum and drops the segment.
23. See Figure 23.2.
25. Every second the counter is incremented by 64,000 × 2 = 128,000. The sequence
number field is 32 bits long and can hold only 232−1. So it takes (232−1)/(128,000)
seconds or 33,554 seconds.
27. See Figure 23.3.
29. The largest number in the sequence number field is 232 −1. If we start at 7000, it
takes [(232 − 1) −7000] / 1,000,000 = 4295 seconds.
 3

Figure 23.2 Solution to Exercise 23

52001 20 or 21
14532
751
785
5 0 1 1 0 0 0 2000

0 0

40 bytes of data

Figure 23.3 Solution to Exercise 27

Client Server
SYN
Ephemeral port Well-known port
14534
785
5 0 00 0 10
Checksum
SYN + ACK
Ephemeral port Well-known port
21732
785
14535
5 0 10 0 10 window size
Checksum 0

ACK
Ephemeral port Well-known port
14534
785
21733
5 0 10 0 00 window size
Checksum 0

31. See Figure 23.4.

33. See Figure 23.5.
Note that the value of cumTSN must be updated to 8.
4

Figure 23.4 Solution to Exercise 31

Before

2001 3001 5000

After receiving ACK

2500 3001 6499

After sending 1000 bytes

2500 4001 6499

Figure 23.5 Solution to Exercise 33

20 19 18 17 16 14 13 12 11 8 7 6 5 4 3 2 1
Received To process

11,14 5 cumTSN
cumTSN
1800 winSize
16,20
OutOfOrder 4 lastACK