<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="626f4765b6b0e1ae" weblate-flags="read-only">
        <source>This is an unpolished draft of the third edition of this e-book. If you find any error or have suggestions to improve the text, please create an issue via https://github.com/CNP3/ebook/issues?milestone=4 or help us by providing pull requests to close the existing issues.</source>
        <target state="translated">This is an unpolished draft of the third edition of this e-book. If you find any error or have suggestions to improve the text, please create an issue via https://github.com/CNP3/ebook/issues?milestone=4 or help us by providing pull requests to close the existing issues.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">6</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="6ce0814c3f82fd89" weblate-flags="read-only">
        <source>Sharing resources</source>
        <target state="translated">Sharing resources</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0c84055ad0df07aa" weblate-flags="read-only">
        <source>Medium Access Control</source>
        <target state="translated">Medium Access Control</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">15</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c60f184ec7a8a7d2" weblate-flags="read-only">
        <source>To understand the operation of Medium Access Control algorithms, it is often interesting to use a geometric representation of the transmission of frames on a shared medium. This representation is suitable if the communicating devices are attached to a single cable. Consider a simple scenario with a host connected at one end of a cable. For simplicity, let us consider a cable that has a length of one kilometer. Let us also consider that the propagation delay of the electrical signal is five microseconds per kilometer. The figure below shows the transmission of a 2000 bits frame at 100 Mbps by host A on the cable.</source>
        <target state="translated">To understand the operation of Medium Access Control algorithms, it is often interesting to use a geometric representation of the transmission of frames on a shared medium. This representation is suitable if the communicating devices are attached to a single cable. Consider a simple scenario with a host connected at one end of a cable. For simplicity, let us consider a cable that has a length of one kilometer. Let us also consider that the propagation delay of the electrical signal is five microseconds per kilometer. The figure below shows the transmission of a 2000 bits frame at 100 Mbps by host A on the cable.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">17</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="67cd599e3fe7f2e2" weblate-flags="read-only">
        <source>If the transmitting host is located at another position on the shared medium than one of the edges, then the geometrical pattern that represents the transmission of a frame is slightly different. If the transmitting host is placed in the middle of the cable, then the signal is transmitted in both directions on the cable. The figure below shows the transmission of one 100 bits frame at 100 Mbps by host C on the same cable.</source>
        <target state="translated">If the transmitting host is located at another position on the shared medium than one of the edges, then the geometrical pattern that represents the transmission of a frame is slightly different. If the transmitting host is placed in the middle of the cable, then the signal is transmitted in both directions on the cable. The figure below shows the transmission of one 100 bits frame at 100 Mbps by host C on the same cable.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">42</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2717ad5523b46e97" weblate-flags="read-only">
        <source>In a shared medium, a collision may happen if two hosts transmit at almost the same time as shown in the example below.</source>
        <target state="translated">In a shared medium, a collision may happen if two hosts transmit at almost the same time as shown in the example below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">66</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2eedebcaeacfe23e" weblate-flags="read-only">
        <source>Consider the following scenario for the ALOHA medium access control algorithm. Three hosts are attached to a one-kilometer long cable and transmit 1000 bits frames at 1 Mbps. Each arrow represents a request to transmit a frame on the corresponding host. Each square represents 250 microseconds in the figure. Represent all the transmitted frames and list the frames that collide.</source>
        <target state="translated">Consider the following scenario for the ALOHA medium access control algorithm. Three hosts are attached to a one-kilometer long cable and transmit 1000 bits frames at 1 Mbps. Each arrow represents a request to transmit a frame on the corresponding host. Each square represents 250 microseconds in the figure. Represent all the transmitted frames and list the frames that collide.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">92</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="57193e82d7d37aea" weblate-flags="read-only">
        <source>Same question as above, but now consider that the hosts transmit 1000 bits frames at 100 Mbps. The cable has a length of 2 kilometers. C is in the middle of the cable. Each square in the figure below corresponds to 10 microseconds.</source>
        <target state="translated">Same question as above, but now consider that the hosts transmit 1000 bits frames at 100 Mbps. The cable has a length of 2 kilometers. C is in the middle of the cable. Each square in the figure below corresponds to 10 microseconds.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">119</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="06e150e36e7f3a51" weblate-flags="read-only">
        <source>In ALOHA, the hosts rely on acknowledgments to detect whether their frame has been received correctly by the destination. Consider a network running at 100 Mbps where the host exchange 1000 bits frames and acknowledgments of 100 bits. Draw the frames sent by hosts A and B in the figure below. Assume that a square corresponds to 10 microseconds and that the cable has a length of 2 kilometers.</source>
        <target state="translated">In ALOHA, the hosts rely on acknowledgments to detect whether their frame has been received correctly by the destination. Consider a network running at 100 Mbps where the host exchange 1000 bits frames and acknowledgments of 100 bits. Draw the frames sent by hosts A and B in the figure below. Assume that a square corresponds to 10 microseconds and that the cable has a length of 2 kilometers.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">150</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="674b48c59816178a" weblate-flags="read-only">
        <source>Same question as above, but now assume that the retransmission timer of each host is set to 50 microseconds.</source>
        <target state="translated">Same question as above, but now assume that the retransmission timer of each host is set to 50 microseconds.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">175</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="bd20fb06961fde2a" weblate-flags="read-only">
        <source>In practice, hosts transmit variable length frames. Consider a cable having a bandwidth of 100 Mbps and a length of 2 kilometers.</source>
        <target state="translated">In practice, hosts transmit variable length frames. Consider a cable having a bandwidth of 100 Mbps and a length of 2 kilometers.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">203</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9fa8718dd7ecfc49" weblate-flags="read-only">
        <source>With CSMA, hosts need to listen to the communication channel before starting their transmission. Consider again a 2 kilometers long cable where hosts send frames at 100 Mbps. Show in the figure below the correct transmission of frames with CSMA.</source>
        <target state="translated">With CSMA, hosts need to listen to the communication channel before starting their transmission. Consider again a 2 kilometers long cable where hosts send frames at 100 Mbps. Show in the figure below the correct transmission of frames with CSMA.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">231</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="778f04fad42bda42" weblate-flags="read-only">
        <source>CSMA/CD does not use acknowledgments but instead assumes that each host can detect collisions by listening while transmitting. Consider a 2 kilometers long cable running at 10 Mbps. Show in the figure below the utilization of the communication channel and the collisions that would occur. For this exercise, do not attempt to retransmit the frames that have collided.</source>
        <target state="translated">CSMA/CD does not use acknowledgments but instead assumes that each host can detect collisions by listening while transmitting. Consider a 2 kilometers long cable running at 10 Mbps. Show in the figure below the utilization of the communication channel and the collisions that would occur. For this exercise, do not attempt to retransmit the frames that have collided.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">260</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7ee201e72e9ad076" weblate-flags="read-only">
        <source>Consider again a network that uses CSMA/CD. This time, the bandwidth is set to 1 Gbps and the cable has a length of two kilometers. When a collision occurs, consider that the hosts B and C retransmit immediately while host A waits for the next slot.</source>
        <target state="translated">Consider again a network that uses CSMA/CD. This time, the bandwidth is set to 1 Gbps and the cable has a length of two kilometers. When a collision occurs, consider that the hosts B and C retransmit immediately while host A waits for the next slot.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">290</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="529ab017bae5ec8b" weblate-flags="read-only">
        <source>An important part of the CSMA/CD algorithm is the exponential backoff. To illustrate the operation of this algorithm, let us consider a cable that has a length of one kilometer. The bandwidth of the network is set to 10 Mbps. Assume that when a collision occurs, host A always selects the highest possible random delay according to the exponential backoff algorithm while host B always selects the shortest one. In this network, the slot time is equal to the time required to transmit 100 bits. We further assume that a host can detect collision immediately (i.e. as soon as the other frame arrives).</source>
        <target state="translated">An important part of the CSMA/CD algorithm is the exponential backoff. To illustrate the operation of this algorithm, let us consider a cable that has a length of one kilometer. The bandwidth of the network is set to 10 Mbps. Assume that when a collision occurs, host A always selects the highest possible random delay according to the exponential backoff algorithm while host B always selects the shortest one. In this network, the slot time is equal to the time required to transmit 100 bits. We further assume that a host can detect collision immediately (i.e. as soon as the other frame arrives).</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">316</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e26c0bd9f63bb7bc" weblate-flags="read-only">
        <source>Fairness and congestion control</source>
        <target state="translated">Fairness and congestion control</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">343</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3d3891054ca609d8" weblate-flags="read-only">
        <source>Consider the network below. Compute the max-min fair allocation for the hosts in this network assuming that nodes `Sx` always send traffic towards node `Dx`. Furthermore, link `R1-R2` has a bandwidth of 10 Mbps while link `R2-R3` has a bandwidth of 20 Mbps.</source>
        <target state="translated">Consider the network below. Compute the max-min fair allocation for the hosts in this network assuming that nodes `Sx` always send traffic towards node `Dx`. Furthermore, link `R1-R2` has a bandwidth of 10 Mbps while link `R2-R3` has a bandwidth of 20 Mbps.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">345</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="cfcd865bb14a8534" weblate-flags="read-only">
        <source>To understand congestion control algorithms, it can also be useful to represent the exchange of packets by using a graphical representation. As a first example, let us consider a very simple network composed of two hosts interconnected through a switch.</source>
        <target state="translated">To understand congestion control algorithms, it can also be useful to represent the exchange of packets by using a graphical representation. As a first example, let us consider a very simple network composed of two hosts interconnected through a switch.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">382</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4c96a9a4076217ad" weblate-flags="read-only">
        <source>Suppose now that host A uses a window of three segments and sends these three segments immediately. The segments will be queued in the router before being transmitted on the output link and delivered to their destination. The destination will reply with a short acknowledgment segment. A possible visualization of this exchange of packets is represented in the figure below. We assume for this figure that the router marks the packets to indicate congestion as soon as its buffer is non-empty when its receives a packet on its input link. In the figure, a `(c)` sign is added to each packet to indicate that it has been explicitly marked.</source>
        <target state="translated">Suppose now that host A uses a window of three segments and sends these three segments immediately. The segments will be queued in the router before being transmitted on the output link and delivered to their destination. The destination will reply with a short acknowledgment segment. A possible visualization of this exchange of packets is represented in the figure below. We assume for this figure that the router marks the packets to indicate congestion as soon as its buffer is non-empty when its receives a packet on its input link. In the figure, a `(c)` sign is added to each packet to indicate that it has been explicitly marked.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">399</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d69a557684e74b9b" weblate-flags="read-only">
        <source>In practice, a router is connected to multiple input links. The figure below shows an example with two hosts.</source>
        <target state="translated">In practice, a router is connected to multiple input links. The figure below shows an example with two hosts.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">432</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3ae65b6343d6b71d" weblate-flags="read-only">
        <source>In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`.</source>
        <target state="translated">In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">491</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1fd94d68f5b4b11b" weblate-flags="read-only">
        <source>Consider the network depicted in the figure below.</source>
        <target state="translated">Consider the network depicted in the figure below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">538</context>
        </context-group>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">613</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="75f0cecd876c2f93" weblate-flags="read-only">
        <source>In this network, compute the minimum round-trip-time between `A` (resp. `B`) and `D`. Perform the computation if the hosts send segments containing 1000 bits.</source>
        <target state="translated">In this network, compute the minimum round-trip-time between `A` (resp. `B`) and `D`. Perform the computation if the hosts send segments containing 1000 bits.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">558</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ebeb561fba7df32c" weblate-flags="read-only">
        <source>How is the maximum round-trip-time influenced if the buffers of router `R1` store 10 packets ?</source>
        <target state="translated">How is the maximum round-trip-time influenced if the buffers of router `R1` store 10 packets ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">559</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0428e1019a6bdc2b" weblate-flags="read-only">
        <source>If hosts `A` and `B` send to `D` 1000 bits segments and use a sending window of four segments, what is the maximum throughput that they can achieve ?</source>
        <target state="translated">If hosts `A` and `B` send to `D` 1000 bits segments and use a sending window of four segments, what is the maximum throughput that they can achieve ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">560</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="286afd2e10d3c5e0" weblate-flags="read-only">
        <source>Assume now that `R1` is using round-robin scheduling instead of a FIFO buffer. One queue is used to store the packets sent by `A` and another for the packets sent by `B`. `A` sends one 1000 bits packet every second while `B` sends packets at 10 Mbps. What is the round-trip-time measured by each of these two hosts if each of the two queues of `R1` can store 5 packets ?</source>
        <target state="translated">Assume now that `R1` is using round-robin scheduling instead of a FIFO buffer. One queue is used to store the packets sent by `A` and another for the packets sent by `B`. `A` sends one 1000 bits packet every second while `B` sends packets at 10 Mbps. What is the round-trip-time measured by each of these two hosts if each of the two queues of `R1` can store 5 packets ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">561</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="da5ca3344d25b98b" weblate-flags="read-only">
        <source>When analyzing the reaction of a network using round-robin schedulers, it is sometimes useful to consider that the packets sent by each source are equivalent to a fluid and that each scheduler acts as a tap. Using this analogy, consider the network below. In this network, all the links are 100 Mbps and host `B` is sending packets at 100 Mbps. If A sends at 1, 5, 10, 20, 30, 40, 50, 60, 80 and 100 Mbps, what is the throughput that destination `D` will receive from `A`. Use this data to plot a graph that shows the portion of the traffic sent by host `A` which is received by host `D`.</source>
        <target state="translated">When analyzing the reaction of a network using round-robin schedulers, it is sometimes useful to consider that the packets sent by each source are equivalent to a fluid and that each scheduler acts as a tap. Using this analogy, consider the network below. In this network, all the links are 100 Mbps and host `B` is sending packets at 100 Mbps. If A sends at 1, 5, 10, 20, 30, 40, 50, 60, 80 and 100 Mbps, what is the throughput that destination `D` will receive from `A`. Use this data to plot a graph that shows the portion of the traffic sent by host `A` which is received by host `D`.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">564</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d2f96dcd7dc4c12a" weblate-flags="read-only">
        <source>Compute the max-min fair bandwidth allocation in the network below.</source>
        <target state="translated">Compute the max-min fair bandwidth allocation in the network below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">582</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="48aa6ce61d0f7c55" weblate-flags="read-only">
        <source>Simple network topology</source>
        <target state="translated">Simple network topology</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">588</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ed687a14a326adc7" weblate-flags="read-only">
        <source>Consider the simple network depicted in the figure below.</source>
        <target state="translated">Consider the simple network depicted in the figure below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">591</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="bcbf713218995567" weblate-flags="read-only">
        <source>In this network, a 250 Kbps link is used between the routers. The propagation delays in the network are negligible. Host `A` sends 1000 bits long segments so that it takes one msec to transmit one segment on the `A-R1` link. Neglecting the transmission delays for the acknowledgments, what is the minimum round-trip time measured on host `A` with such segments ?</source>
        <target state="translated">In this network, a 250 Kbps link is used between the routers. The propagation delays in the network are negligible. Host `A` sends 1000 bits long segments so that it takes one msec to transmit one segment on the `A-R1` link. Neglecting the transmission delays for the acknowledgments, what is the minimum round-trip time measured on host `A` with such segments ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">609</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="592403e7d25579a5" weblate-flags="read-only">
        <source>If host `A` uses a window of two segments and needs to transmit five segments of data. How long does the entire transfer lasts ?</source>
        <target state="translated">If host `A` uses a window of two segments and needs to transmit five segments of data. How long does the entire transfer lasts ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">610</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2ff97deae46c647c" weblate-flags="read-only">
        <source>Same question as above, but now host `A` uses the simple DECBIT congestion control mechanism and a maximum window size of four segments.</source>
        <target state="translated">Same question as above, but now host `A` uses the simple DECBIT congestion control mechanism and a maximum window size of four segments.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">611</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5fd411973fe9098d" weblate-flags="read-only">
        <source>Hosts `A` and `B` use the simple congestion control scheme described in the book and router `R1` uses the DECBIT mechanism to mark packets as soon as its buffers contain one packet. Hosts `A` and `B` need to send five segments and start exactly at the same time. How long does each hosts needs to wait to receive the acknowledgment for its fifth segment ?</source>
        <target state="translated">Hosts `A` and `B` use the simple congestion control scheme described in the book and router `R1` uses the DECBIT mechanism to mark packets as soon as its buffers contain one packet. Hosts `A` and `B` need to send five segments and start exactly at the same time. How long does each hosts needs to wait to receive the acknowledgment for its fifth segment ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">630</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ef6154c2f011bd25" weblate-flags="read-only">
        <source>Discussion questions</source>
        <target state="translated">Discussion questions</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">633</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1bce67ada4fa00a6" weblate-flags="read-only">
        <source>In a deployed CSMA/CD network, would it be possible to increase or decrease the duration of the slotTime ? Justify your answer</source>
        <target state="translated">In a deployed CSMA/CD network, would it be possible to increase or decrease the duration of the slotTime ? Justify your answer</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">639</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="550e7bbfa78cb8f3" weblate-flags="read-only">
        <source>Consider a CSMA/CD network that contains hosts that generate frames at a regular rate. When the transmission rate increases, the amount of collisions increases. For a given network load, measured in bits/sec, would the number of collisions be smaller, equal or larger with short frames than with long frames ?</source>
        <target state="translated">Consider a CSMA/CD network that contains hosts that generate frames at a regular rate. When the transmission rate increases, the amount of collisions increases. For a given network load, measured in bits/sec, would the number of collisions be smaller, equal or larger with short frames than with long frames ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">641</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3ba3183c5c7018f2" weblate-flags="read-only">
        <source>Slotted ALOHA improves the performance of ALOHA by dividing the time in slots. However, this basic idea raises two interested questions. First how would you enforce the duration of these slots ? Second, should a slot include the time to transmit a data frame or the time to transmit a data frame and the corresponding acknowledgment ?</source>
        <target state="translated">Slotted ALOHA improves the performance of ALOHA by dividing the time in slots. However, this basic idea raises two interested questions. First how would you enforce the duration of these slots ? Second, should a slot include the time to transmit a data frame or the time to transmit a data frame and the corresponding acknowledgment ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">643</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="602d94c41f9df882" weblate-flags="read-only">
        <source>Like ALOHA, CSMA relies on acknowledgments to detect where a frame has been correctly received. When a host senses an idle channel, if should transmit its frame immediately. How should it react if it detects that another host is already transmitting ? Consider two options :</source>
        <target state="translated">Like ALOHA, CSMA relies on acknowledgments to detect where a frame has been correctly received. When a host senses an idle channel, if should transmit its frame immediately. How should it react if it detects that another host is already transmitting ? Consider two options :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">645</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0aadd05dfe10b485" weblate-flags="read-only">
        <source>the host continues to listen until the communication channel becomes free. It transmits as soon as the communication channel becomes free.</source>
        <target state="translated">the host continues to listen until the communication channel becomes free. It transmits as soon as the communication channel becomes free.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">647</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="932a6526b82325b8" weblate-flags="read-only">
        <source>the host stops to listen and waits for a random time before sensing again the communication channel to check whether it is free.</source>
        <target state="translated">the host stops to listen and waits for a random time before sensing again the communication channel to check whether it is free.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/ex-sharing.rst</context>
          <context context-type="linenumber">648</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
