Exit Zen
95
../../principles/transport.rst:542
English
Interactions between the transport layer, its user, and its network layer provider
0/820 · 82
95
../../principles/sharing.rst:443
English
The worst collision on a shared bus
0/350 · 35
95
../../principles/security.rst:978
English
Bob chooses a secret integer and sends :math:`B=g^{b} \mod p` to Mallory
0/720 · 72
95
../../exercises/ipv6.rst:898
English
We can analyze this configuration problem in more details by using ``traceroute6``. The loop appears clearly.
0/1090 · 109
95
../../protocols/bgp.rst:371
English
With such an import filter, the routers of a domain always prefer to reach destinations via their customers whenever such a route exists. Otherwise, they prefer to use `shared-cost` peering relationships and they only send packets via their providers when they do not know any alternate route. A consequence of setting the `local-pref` attribute like this is that Internet paths are often asymmetrical. Consider for example the internetwork shown in the figure below.
0/4670 · 467
95
../../protocols/email.rst:244
English
G
0/100 · 1
95
../../protocols/ethernet.rst:370
English
The state of each port is important when considering the transmission of `BPDUs`. The root switch regularly sends its own `BPDU` over all of its (`Designated`) ports. This `BPDU` is received on the `Root` port of all the switches that are directly connected to the `root switch`. Each of these switches computes its own `BPDU` and sends this `BPDU` over all its `Designated` ports. These `BPDUs` are then received on the `Root` port of downstream switches, which then compute their own `BPDU`, etc. When the network topology is stable, switches send their own `BPDU` on all their `Designated` ports, once they receive a `BPDU` on their `Root` port. No `BPDU` is sent on a `Blocked` port. Switches listen for `BPDUs` on their `Blocked` and `Designated` ports, but no `BPDU` should be received over these ports when the topology is stable. The utilization of the ports for both `BPDUs` and data frames is summarized in the table below.
0/9330 · 933
95
../../protocols/ipv6.rst:354
English
An IPv6 packet containing an TCP segment
0/400 · 40
95
../../protocols/ethernet.rst:353
English
Cost
0/100 · 4
95
../../protocols/tcp.rst:271
English
`receiving buffer` : a buffer to store all data received from the remote host that has not yet been delivered to the user. Data may be stored in the `receiving buffer` because either it was not received in sequence or because the user is too slow to process it
0/2600 · 260
96
../../glossary.rst:295
English
ISP
0/100 · 3
96
../../principles/network.rst:373 • ../../principles/network.rst:422 • ../../principles/network.rst:444
English
none
0/100 · 4
96
../../principles/transport.rst:544
English
We have already described in the datalink layers mechanisms to deal with data losses and transmission errors. These techniques are also used in the transport layer.
0/1640 · 164
96
../../principles/sharing.rst:446
English
Furthermore, on the wired networks where CSMA/CD is used, collisions are almost the only cause of transmission errors that affect frames. Transmission errors that only affect a few bits inside a frame seldom occur in these wired networks. For this reason, the designers of CSMA/CD chose to completely remove the acknowledgment frames in the datalink layer. When a host transmits a frame, it verifies whether its transmission has been affected by a collision. If not, given the negligible Bit Error Ratio of the underlying network, it assumes that the frame was received correctly by its destination. Otherwise the frame is retransmitted after some delay.
0/6540 · 654
96
../../principles/security.rst:979
English
Mallory computes :math:`S_{A}=A^{m} \mod p` and :math:`S_{B}=B^{m} \mod p`
0/740 · 74
96
../../exercises/ipv6.rst:919
English
On host ``b``, the problem is different. The packets that it sends towards host ``a`` do not seem to go beyond router ``r3``.
0/1250 · 125
96
../../protocols/bgp.rst:377
English
Asymmetry of Internet paths
0/270 · 27
96
../../protocols/email.rst:244
English
23
0/100 · 2
96
../../protocols/ethernet.rst:373
English
Port state
0/100 · 10
96
../../protocols/ipv6.rst:358
English
However, the `Next header` has broader usages than simply indicating the transport protocol which is responsible for the packet payload. An IPv6 packet can contain a chain of headers and the last one indicates the transport protocol that is responsible for the packet payload. Supporting a chain of headers is a clever design from an extensibility viewpoint. As we will see, this chain of headers has several usages.
0/4160 · 416