Exit Zen
127
../../protocols/tcp.rst:364
English
In a go-back-n transport protocol such as TCP, the retransmission timeout must be correctly set in order to achieve good performance. On one hand, if the retransmission timeout expires too early, then bandwidth is wasted by retransmitting segments that have already been correctly received. On the other hand, if the retransmission timeout expires too late, then bandwidth is wasted because the sender is idle waiting for the expiration of its retransmission timeout.
0/4670 · 467
128
../../glossary.rst:217
English
NFS
0/100 · 3
128
../../principles/reliability.rst:429
English
Even parity
0/110 · 11
128
../../principles/transport.rst:690
English
Three-way handshake : recovery from a duplicate `CR`
0/520 · 52
128
../../protocols/bgp.rst:450
English
The layered structure of the global Internet
0/440 · 44
128
../../protocols/email.rst:252
English
61
0/100 · 2
128
../../protocols/ipv6.rst:409
English
FDDI
0/100 · 4
128
../../protocols/ethernet.rst:413
English
Virtual Local Area Networks in a switched Ethernet network
0/580 · 58
128
../../protocols/tcp.rst:366
English
A good setting of the retransmission timeout clearly depends on an accurate estimation of the round-trip-time of each TCP connection. The round-trip-time differs between TCP connections, but may also change during the lifetime of a single connection. For example, the figure below shows the evolution of the round-trip-time between two hosts during a period of 45 seconds.
0/3730 · 373
129
../../glossary.rst:219
English
The Network File System is defined in :rfc:`1094`
0/490 · 49
129
../../principles/reliability.rst:431 • ../../principles/reliability.rst:448
English
000
0/100 · 3
129
../../principles/transport.rst:692
English
A second scenario is when the initiating entity sends a `CR` segment that does not reach the remote entity and receives a duplicate `CA` segment from a previous connection attempt. This duplicate `CA` segment cannot contain a valid acknowledgment for the `CR` segment as the sequence number of the `CR` segment was extracted from the transport clock of the initiating entity. The `CA` segment is thus rejected and the `CR` segment is retransmitted upon expiration of the retransmission timer.
0/4920 · 492
129
../../principles/sharing.rst:621
English
The IEEE 802.5 Token Ring technology is defined in [IEEE802.5]_. We use Token Ring as an example to explain the principles of the token-based MAC algorithms in ring-shaped networks. Other ring-shaped networks include the defunct FDDI [Ross1989]_ or Resilient Pack Ring [DYGU2004]_ . A good survey of the early token ring networks may be found in [Bux1989]_ .
0/3580 · 358
129
../../protocols/bgp.rst:454
English
The domains on the Internet can be divided in about four categories according to their role and their position in the AS-level topology.
0/1360 · 136
129
../../protocols/email.rst:254
English
11
0/100 · 2
129
../../protocols/ipv6.rst:409
English
4352 bytes
0/100 · 10
129
../../protocols/ethernet.rst:415
English
IEEE defined in the [IEEE802.1q]_ standard a special header to encode the VLAN identifiers. This 32 bit header includes a 12 bit VLAN field that contains the VLAN identifier of each frame. The format of the [IEEE802.1q]_ header is described below.
0/2470 · 247
129
../../protocols/tcp.rst:372
English
Evolution of the round-trip-time between two hosts
0/500 · 50
130
../../glossary.rst:220
English
NTP
0/100 · 3
130
../../principles/dv.rst:59
English
The first condition ensures that the router discovers the shortest path towards each destination. The second condition is used to take into account the changes of routes that may occur after a link failure or a change of the metric associated to a link.
0/2530 · 253