<?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" id="16bc8c79e549f898">
        <source>Internet email protocols</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">5</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b29f9fb9a24338d6">
        <source>Many Internet protocols are ASCII_-based protocols where the client sends requests as one line of ASCII_ text terminated by `CRLF` and the server replies with one of more lines of ASCII_ text. Using such ASCII_ messages has several advantages compared to protocols that rely on binary encoded messages</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">7</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="40c93d2a2fe6aa66">
        <source>the messages exchanged by the client and the server can be easily understood by a developer or network engineer by simply reading the messages</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">9</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="688d9b3ce58b78b7">
        <source>it is often easy to write a small prototype that implements a part of the protocol</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">10</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="e4d5dd5e93b6b429">
        <source>it is possible to test a server manually by using telnet</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="aac2e6c2fb6122a1">
        <source>Telnet is a protocol that allows to obtain a terminal on a remote server. For this, telnet opens a TCP connection with the remote server on port 23. However, most `telnet` implementations allow the user to specify an alternate port as `telnet hosts port` When used with a port number as parameter, `telnet` opens a TCP connection to the remote host on the specified port. `telnet` can thus be used to test any server using an ASCII-based protocol on top of TCP. Note that if you need to stop a running `telnet` session, ``Ctrl-C`` will not work as it will be sent by `telnet` to the remote host over the TCP connection. On many `telnet` implementations you can type ``Ctrl-]`` to freeze the TCP connection and return to the telnet interface.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">13</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="3a05736b668aa6d2">
        <source>Use your preferred email tool to send an email message to yourself containing a single line of text. Most email tools have the ability to show the `source` of the message, use this function to look at the message that you sent and the message that you received. Can you find an explanation for all the lines that have been added to your single line email ?</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">16</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="5118845ca2835c4b">
        <source>The TCP protocol supports 65536 different ports numbers. Many of these port numbers have been reserved for some applications. The official repository of the reserved port numbers is maintained by the Internet Assigned Numbers Authority (IANA_) on http://www.iana.org/assignments/port-numbers [#fservices]_. Using this information, what is the default port number for the POP3 protocol ? Does it run on top of UDP or TCP ?</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">18</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="e5d96ac7057169e5">
        <source>The Post Office Protocol (POP) is a rather simple protocol described in :rfc:`1939`. POP operates in three phases. The first phase is the authorization phase where the client provides a username and a password. The second phase is the transaction phase where the client can retrieve emails. The last phase is the update phase where the client finalizes the transaction. What are the main POP commands and their parameters ? When a POP server returns an answer, how can you easily determine whether the answer is positive or negative ?</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">20</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="3caab7117650dbd8">
        <source>On smartphones, users often want to avoid downloading large emails over a slow wireless connection. How could a POP client only download emails that are smaller than 5 KBytes ?</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">22</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c463aea6549199a2">
        <source>Footnotes</source>
        <target state="translated">Notes de pied de page</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">26</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" id="bece4ed3785fe6f7">
        <source>On Unix hosts, a subset of the port assignments is often placed in `/etc/services`.</source>
        <target></target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/email.rst</context>
          <context context-type="linenumber">27</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
