Exit Zen
43
../../exercises/tcp-2.rst:637
English
Open questions
0/140 · 14
44
../../exercises/tcp-2.rst:639
English
Unless otherwise noted, we assume for the questions in this section that the following conditions hold.
0/1030 · 103
45
../../exercises/tcp-2.rst:641
English
the sender/receiver performs a single :manpage:`send(3)` of `x` bytes
0/690 · 69
46
../../exercises/tcp-2.rst:642
English
the round-trip-time is fixed and does not change during the lifetime of the TCP connection. We assume a fixed value of 100 milliseconds for the round-trip-time and a fixed value of 200 milliseconds for the retransmission timer.
0/2270 · 227
47
../../exercises/tcp-2.rst:643
English
the delay required to transmit a single TCP segment containing MSS bytes is small and set to 1 milliseconds, independently of the MSS size
0/1380 · 138
48
../../exercises/tcp-2.rst:644
English
the transmission delay for a TCP acknowledgment is negligible
0/610 · 61
49
../../exercises/tcp-2.rst:645
English
the initial value of the congestion window is one MSS-sized segment
0/670 · 67
50
../../exercises/tcp-2.rst:646
English
the value of the duplicate acknowledgment threshold is fixed and set to 3
0/730 · 73
51
../../exercises/tcp-2.rst:647
English
TCP always acknowledges each received segment
0/450 · 45
52
../../exercises/tcp-2.rst:649
English
To understand the operation of the TCP congestion control, it is often useful to write time-sequence diagrams for different scenarios. The example below shows the operation of the TCP congestion control scheme in a very simple scenario. The initial congestion window (``cwnd``) is set to 1000 bytes and the receive window (``rwin``) advertised by the receiver (supposed constant for the entire connection) is set to 2000 bytes. The slow-start threshold (``ssthresh``) is set to 64000 bytes.
0/4900 · 490
53
../../exercises/tcp-2.rst:684
English
Can you explain why the sender only sends one segment first and then two successive segments (the delay between the two segments on the figure is due to graphical reasons) ?
0/1730 · 173
54
../../exercises/tcp-2.rst:686
English
Can you explain why the congestion window is increased after the reception of the first acknowledgment ?
0/1040 · 104
55
../../exercises/tcp-2.rst:688
English
How long does it take for the sender to deliver 3 KBytes to the receiver ?
0/740 · 74
56
../../exercises/tcp-2.rst:691
English
Same question as above but now with a small variation. Recent TCP implementations use a large initial value for the congestion window. Draw the time-sequence diagram that corresponds to an initial value of 10000 bytes for this congestion window.
0/2450 · 245
57
../../exercises/tcp-2.rst:715
English
Same question as the first one, but consider that the MSS on the sender is set to 500 bytes. How does this modification affect the entire delay ?
0/1450 · 145
58
../../exercises/tcp-2.rst:738
English
Assuming that there are no losses and that there is no congestion in the network. If the sender writes `x` bytes on a newly established TCP connection, derive a formula that computes the minimum time required to deliver all these `x` bytes to the receiver. For the derivation of this formula, assume that `x` is a multiple of the maximum segment size and that the receive window and the slow-start threshold are larger than `x`.
0/4280 · 428
59
../../exercises/tcp-2.rst:740
English
In question 1, we assumed that the receiver acknowledged every segment received from the sender. In practice, many deployed TCP implementations use delayed acknowledgments. Assuming a delayed acknowledgment timer of 50 milliseconds, modify the time-sequence diagram below to reflect the impact of these delayed acknowledgment. Does their usage decreases or increased the transmission delay ?
0/3910 · 391
60
../../exercises/tcp-2.rst:775
English
Let us now explore the impact of congestion on the slow-start and congestion avoidance mechanisms. Consider the scenario below. For graphical reasons, it is not possible anymore to show information about the segments on the graph, but you can easily infer them.
0/2610 · 261
61
../../exercises/tcp-2.rst:832
English
Redraw the same figure assuming that the second segment that was delivered by the sender in the figure experienced congestion. In a network that uses Explicit Congestion Notification, this segment would be marked by routers and the receiver would return the congestion mark in the corresponding acknowledgment.
0/3100 · 310
62
../../exercises/tcp-2.rst:834
English
Same question, but assume now that the fourth segment delivered by the sender experienced congestion (but was not discarded).
0/1250 · 125