<?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="fr">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="e7152480583fdc70">
        <source>Reliable transfer</source>
        <target state="translated">Transfert fiable</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">7</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ea725087c218738b">
        <source>Open questions</source>
        <target state="translated">Questions ouvertes</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a732c3a52664e4c9">
        <source>Transmission links have sometimes different upstream and downstream bandwidths. A typical example are access networks that use ADSL (Asymmetric Digital Subscriber Lines). Consider two hosts connected via an ADSL link having an upstream bandwidth of 1 Mbps and a downstream bandwidth of 50 Mbps. The propagation delay between the two hosts is 10 milliseconds. What is the maximum throughput, expressed in frames/second, that the alternating bit protocol can obtain on this link if each data frame has a length of 125 bytes and acknowledgments are 25 bytes long. Same question if the protocol is modified to support 1500 bytes long data frames.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">16</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="671ef67dc127fcd7">
        <source>How would you set the duration of the retransmission timer in the alternating bit protocol ?</source>
        <target state="translated">Comment fixeriez-vous le délai du timer de retransmission dans le protocole du bit alterné ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">19</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e81e94f1ab2feaea">
        <source>A version of the Alternating Bit Protocol supporting variable length frames uses a header that contains the following fields :</source>
        <target state="translated">Une version du protocole du bit alterné à frame de longueur variable utilise une entête qui contient les champs suivants :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">22</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="acfd9e9e8f98774c">
        <source>a `number` (0 or 1)</source>
        <target state="translated">un `nombre` (0 ou 1)</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">24</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ad8d202c44e7fd0a">
        <source>a `length` field that indicates the length of the data</source>
        <target state="translated">un champ `length` (taille) qui indique la taille des données</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">25</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="a84b234b6232fe5c">
        <source>a Cyclic Redundancy Check (`CRC`)</source>
        <target state="translated">un contrôle de redondance cyclique (`CRC`)</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">26</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="aaed863c300fb251">
        <source>Derive a mathematical expression that provides the `goodput`, i.e. the amount of payload bytes that have been transmitted during a period of time, achieved by the Alternating Bit Protocol assuming that :</source>
        <target state="translated">Obtenez une expression mathématique pour le `goodput`, c'est-à-dire la quantité de bytes pouvant être transmis pendant une période de temps donnée, issu du protocole du bit alterné en considérant que :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">30</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8bb3b9213582c0f5">
        <source>Each frame contains `D` bytes of data and `c` bytes of control information</source>
        <target state="translated">Chaque frame contient `D` bytes de donnée et `c` bytes d'information de contrôle</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">32</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="517fa75ca5f02ebb">
        <source>Each acknowledgment contains `c` bytes of control information</source>
        <target state="translated">Chaque acknowledgment contient `c` bytes de information de contrôle</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">33</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4d111b76cb1cebb4">
        <source>The bandwidth of the two directions of the link is set to `B` bits per second</source>
        <target state="translated">La bande passante dans les deux directions du câble est de `B` bits par seconde</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">34</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="43044825467e548d">
        <source>The delay between the two hosts is `s` seconds in both directions</source>
        <target state="translated">Le délai entre deux hôtes est de `s` secondes dans les deux sens</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">35</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="44def8e00fab1403">
        <source>there are no transmission errors</source>
        <target state="translated">il n'y a pas d'erreur de transmission</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">36</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f515d0d76dfe2a31">
        <source>when there are no losses</source>
        <target state="translated">dans le cas où il n'y a pas de pertes</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">40</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="43f6fcf6023fcd7a">
        <source>when every second acknowledgment is discarded due to transmission errors</source>
        <target state="translated">lorsqu'un acknowledgment sur deux est ignoré à cause des erreurs de transmission</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">42</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="dfffc1fccb9ece57">
        <source>Same question when using selective repeat instead of go-back-n. Note that the answer is not necessarily the same.</source>
        <target state="translated">Même question en utilisant du selective repeat à la place du go-back-n. Remarquez que la réponse n'est pas nécessairement la même.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">44</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="32b9b9b26dcbfee0">
        <source>Practice</source>
        <target state="translated">Exercices</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">50</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2a81ece8ff05d384">
        <source>Reliable protocols depend on error detection algorithms to detect transmission errors. The following questions will reinforce your understanding of these algorithms.</source>
        <target state="translated">Les protocoles fiables dépendent d'algorithmes de détection des erreurs de transmission. Les questions suivantes vont vous permettre d'approfondir votre compréhension de ces algorithmes.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">52</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3de916ab38a31d48">
        <source>Reliable protocols rely on different types of checksums to verify whether frames have been affected by transmission errors. The most frequently used checksums are :</source>
        <target state="translated">Les protocoles fiables reposent sur différents types de checksums afin de vérifier si des erreurs de transmission ont affecté les frames. Les checksums les plus fréquemment utilisés sont :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">54</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="f6a46967ac161458">
        <source>the Internet checksum used by UDP, TCP and other Internet protocols which is defined in :rfc:`1071` and implemented in various libraries.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">56</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6215f85de922b2aa">
        <source>the 16 bits or the 32 bits Cyclical Redundancy Checks (CRC) that are often used on disks, in zip archives and in datalink layer protocols. See http://rosettacode.org/wiki/CRC-32 for CRC-32 implementations in various languages.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">57</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8cdcb314dcda003e">
        <source>The Cyclic Redundancy Checks (CRCs) are efficient error detection codes that are able to detect :</source>
        <target state="translated">Les contrôles de redondance cyclique (CRC) sont des outils efficaces de détection d'erreurs pouvant détecter :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">62</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="77e0c17bd2bfe0b3">
        <source>all errors that affect an odd number of bits</source>
        <target state="translated">toutes les erreurs affectant un nombre impair de bits</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">64</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0df19d844ad3bb0d">
        <source>all errors that affect a sequence of bits which is shorter than the length of the CRC</source>
        <target state="translated">toutes les errors affectant une séquence de bits plus courte que la longueur du CRC</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">65</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="fc19b9f6d2e0e2ac">
        <source>Implement a small software that computes the CRC-32 for a text file. Then, modify the contents of the file to change an even number of bits or an odd number of bits inside the file. When modifying the file, remember that an ASCII file is composed of 8 bits characters that are encoded by using the ASCII table that you can find at : http://en.wikipedia.org/wiki/ASCII . You can also write a small program that produces binary files that are a small variation of each other.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">67</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ef6154c2f011bd25">
        <source>Discussion questions</source>
        <target state="translated">Questions de discussion</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">74</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="ee2d61dc4759da06">
        <source>Consider two high-end servers connected back-to-back by using a 10 Gbps interface. If the delay between the two servers is one millisecond, what is the throughput that can be achieved by a reliable protocol that is using 10,000 bits frames and a window of</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">77</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="fcb58d2637233fe2">
        <source>one frame</source>
        <target state="translated">une frame</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">79</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2710cb44c5b01416">
        <source>ten frames</source>
        <target state="translated">dix frames</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">80</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ab40f0c248e8a60a">
        <source>hundred frames</source>
        <target state="translated">cent frames</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">81</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0a9341e6c8d8c4fb">
        <source>Is it possible for a go-back-n receiver to inter-operate with a selective-repeat sender ? Justify your answer.</source>
        <target state="translated">Est-il possible pour un récepteur go-back-n de fonctionner avec un émetteur selective-repeat ? Justifiez.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">83</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="14b67d50fcff5895">
        <source>Is it possible for a selective-repeat receiver to inter-operate with a go-back-n sender ? Justify your answer.</source>
        <target state="translated">Est-il possible pour un récepteur selective-repeat de fonctionner avec un émetteur go-back-n ? Justifiez.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">85</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0752ee9fa7e71a9b">
        <source>Same question as above, but assume now that both the sender and the receiver implement selective repeat. Note that the answer can be different from the above question.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/reliability.rst</context>
          <context context-type="linenumber">91</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
