Exit Zen
159
../../protocols/wifi.rst:26
English
74 Mbps
0/100 · 7
159
../../protocols/tcp.rst:523
English
When losses are not isolated or when the windows are small, the performance of the `fast retransmit` heuristic decreases. In such environments, it is necessary to allow a TCP sender to use a selective repeat strategy instead of the default go-back-n strategy. Implementing selective-repeat requires a change to the TCP protocol as the receiver needs to be able to inform the sender of the out-of-order segments that it has already received. This can be done by using the Selective Acknowledgments (SACK) option defined in :rfc:`2018`. This TCP option is negotiated during the establishment of a TCP connection. If both TCP hosts support the option, SACK blocks can be attached by the receiver to the segments that it sends. SACK blocks allow a TCP receiver to indicate the blocks of data that it has received correctly but out of sequence. The figure below illustrates the utilization of the SACK blocks.
0/9040 · 904
160
../../glossary.rst:68
English
a Service Data Unit is the unit information transferred between applications
0/760 · 76
160
../../principles/dv.rst:169
English
:math:`[A=\infty,B=0,C=\infty,E=1]` to router `C`
0/490 · 49
160
../../principles/reliability.rst:581
English
The receiver FSM of the Alternating bit protocol discards all frames that contain an invalid CRC. This is the safest approach since the received frame can be completely different from the frame sent by the remote host. A receiver should not attempt at extracting information from a corrupted frame because it cannot know which portion of the frame has been affected by the error.
0/3790 · 379
160
../../principles/sharing.rst:744
English
The congestion control scheme should be `fair`. Most congestion schemes aim at achieving `max-min fairness`. An allocation of transmission rates to sources is said to be `max-min fair` if :
0/1890 · 189
160
../../protocols/email.rst:262
English
g
0/100 · 1
160
../../protocols/ipv6.rst:538
English
Destination Unreachable. Such an ICMPv6 message is sent when the destination address of a packet is unreachable. The code field of the ICMP header contains additional information about the type of unreachability. The following codes are specified in RFC 4443
0/2580 · 258
160
../../protocols/wifi.rst:26
English
150 Mbps
0/100 · 8
160
../../protocols/tcp.rst:529
English
TCP selective acknowledgments
0/290 · 29
161
../../glossary.rst:60
English
segment
0/100 · 7
161
../../principles/dv.rst:170
English
:math:`[A=\infty,B=0,C=1,E=\infty]` to router `E`
0/490 · 49
161
../../principles/reliability.rst:584
English
The figure below illustrates the operation of the alternating bit protocol.
0/750 · 75
161
../../principles/transport.rst:834
English
For a discussion on how the sending buffer can change, see e.g. [SMM1998]_
0/740 · 74
161
../../principles/sharing.rst:746
English
no link in the network is congested
0/350 · 35
161
../../protocols/email.rst:262
English
49
0/100 · 2
161
../../protocols/ipv6.rst:536
English
``0`` : No route to destination. This indicates that the router that sent the ICMPv6 message did not have a route towards the packet's destination
0/1460 · 146
161
../../protocols/wifi.rst:26
English
70/250
0/100 · 6
161
../../protocols/tcp.rst:531
English
A SACK option contains one or more blocks. A block corresponds to all the sequence numbers between the `left edge` and the `right edge` of the block. The two edges of the block are encoded as 32 bit numbers (the same size as the TCP sequence number) in an SACK option. As the SACK option contains one byte to encode its type and one byte for its length, a SACK option containing `b` blocks is encoded as a sequence of :math:`2+8 \times b` bytes. In practice, the size of the SACK option can be problematic as the optional TCP header extension cannot be longer than 40 bytes. As the SACK option is usually combined with the :rfc:`1323` timestamp extension, this implies that a TCP segment cannot usually contain more than three SACK blocks. This limitation implies that a TCP receiver cannot always place in the SACK option that it sends, information about all the received blocks.
0/8800 · 880
162
../../glossary.rst:62
English
a segment is the unit of information transfer in the transport layer
0/680 · 68