Exit Zen
87
../../principles/reliability.rst:304
English
Recovering from transmission errors
0/350 · 35
87
../../principles/sharing.rst:402
English
[KT1975]_ analyzes in detail the performance of several CSMA variants. Under some assumptions about the transmission channel and the traffic, the analysis compares ALOHA, slotted ALOHA, persistent and non-persistent CSMA. Under these assumptions, ALOHA achieves a channel utilization of only 18.4% of the channel capacity. Slotted ALOHA is able to use 36.6% of this capacity. Persistent CSMA improves the utilization by reaching 52.9% of the capacity while non-persistent CSMA achieves 81.5% of the channel capacity.
0/5160 · 516
87
../../principles/transport.rst:521
English
In the previous sections, we have described services that are provided by the transport layer. However, it is important to note that the notion of service is more general than in the transport layer. As explained earlier, the network layer also provides a service, which in most networks is an unreliable connectionless service. There are network layers that provide a connection-oriented service. Similarly, the datalink layer also provides services. Some datalink layers will provide a connectionless service. This will be the case in Local Area Networks for examples. Other datalink layers, e.g. in public networks, provide a connection oriented service.
0/6570 · 657
88
../../glossary.rst:146
English
Intermediate System- Intermediate System. A link-state intradomain routing that was initially defined for the ISO CLNP protocol but was extended to support IP v4 and IP v6. IS-IS is often used in ISP networks. It is defined in [ISO10589]_
0/2380 · 238
88
../../principles/network.rst:365
English
For example, consider the `label forwarding table` of a network node below.
0/750 · 75
88
../../principles/reliability.rst:306
English
In this section, we develop a reliable datalink protocol running above the physical layer service. To design this protocol, we first assume that the physical layer provides a perfect service. We will then develop solutions to recover from the transmission errors.
0/2630 · 263
88
../../principles/sharing.rst:407
English
Carrier Sense Multiple Access with Collision Detection
0/540 · 54
89
../../glossary.rst:105
English
ISN
0/100 · 3
89
../../principles/network.rst:369 • ../../principles/network.rst:410 • ../../principles/network.rst:420 • ../../principles/network.rst:430 • ../../principles/network.rst:440
English
index
0/100 · 5
89
../../principles/reliability.rst:308
English
The datalink layer is designed to send and receive frames on behalf of a user. We model these interactions by using the `DATA.req` and `DATA.ind` primitives. However, to simplify the presentation and to avoid confusion between a `DATA.req` primitive issued by the user of the datalink layer entity, and a `DATA.req` issued by the datalink layer entity itself, we will use the following terminology :
0/3990 · 399
90
../../glossary.rst:107
English
The Initial Sequence Number of a TCP connection is the sequence number chosen by the client ( resp. server) that is placed in the `SYN` (resp. `SYN+ACK`) segment during the establishment of the TCP connection.
0/2090 · 209
90
../../principles/network.rst:369 • ../../principles/network.rst:410 • ../../principles/network.rst:420 • ../../principles/network.rst:430 • ../../principles/network.rst:440
English
outgoing interface
0/180 · 18
90
../../principles/reliability.rst:310
English
the interactions between the user and the datalink layer entity are represented by using the classical `DATA.req` and the `DATA.ind` primitives
0/1430 · 143
90
../../principles/sharing.rst:418
English
Frame transmission on a shared bus
0/340 · 34
91
../../glossary.rst:36 • ../../glossary.rst:271
English
ISO
0/100 · 3
91
../../principles/network.rst:369 • ../../principles/network.rst:410 • ../../principles/network.rst:420 • ../../principles/network.rst:430 • ../../principles/network.rst:440
English
label
0/100 · 5
91
../../principles/reliability.rst:311
English
the interactions between the datalink layer entity and the framing sub-layer are represented by using `send` instead of `DATA.req` and `recvd` instead of `DATA.ind`
0/1640 · 164
91
../../principles/sharing.rst:420
English
Now that we have looked at how a frame is actually transmitted as an electrical signal on a shared bus, it is interesting to look in more detail at what happens when two hosts transmit a frame at almost the same time. This is illustrated in the figure below, where hosts A and B start their transmission at the same time (point `(1)`). At this time, if host C senses the channel, it will consider it to be free. This will not last a long time and at point `(2)` the electrical signals from both host A and host B reach host C. The combined electrical signal (shown graphically as the superposition of the two curves in the figure) cannot be decoded by host C. Host C detects a collision, as it receives a signal that it cannot decode. Since host C cannot decode the frames, it cannot determine which hosts are sending the colliding frames. Note that host A (and host B) will detect the collision after host C (point `(3)` in the figure below).
0/9430 · 943
92
../../glossary.rst:38
English
The International Standardization Organization is an agency of the United Nations that is based in Geneva and develop standards on various topics. Within ISO, country representatives vote to approve or reject standards. Most of the work on the development of ISO standards is done in expert working groups. Additional information about ISO may be obtained from https://www.iso.org
0/3800 · 380
92
../../principles/network.rst:371 • ../../principles/network.rst:412 • ../../principles/network.rst:414 • ../../principles/network.rst:422 • ../../principles/network.rst:432 • ../../principles/network.rst:442
English
0
0/100 · 1