<?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="74ed7a2807894674" weblate-flags="read-only">
        <source>The User Datagram Protocol</source>
        <target state="translated">The User Datagram Protocol</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">9</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2e2a5ff651e1ab62" weblate-flags="read-only">
        <source>The User Datagram Protocol (UDP) is defined in :rfc:`768`. It provides an unreliable connectionless transport service on top of the unreliable network layer connectionless service. The main characteristics of the UDP service are :</source>
        <target state="translated">The User Datagram Protocol (UDP) is defined in :rfc:`768`. It provides an unreliable connectionless transport service on top of the unreliable network layer connectionless service. The main characteristics of the UDP service are :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b8c8c74fe059c142" weblate-flags="read-only">
        <source>the UDP service cannot deliver SDUs that are larger than 65467 bytes [#fmtuudp]_</source>
        <target state="translated">the UDP service cannot deliver SDUs that are larger than 65467 bytes [#fmtuudp]_</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">13</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2f0056e82a5acd5a" weblate-flags="read-only">
        <source>the UDP service does not guarantee the delivery of SDUs (losses can occur and SDUs can arrive out-of-sequence)</source>
        <target state="translated">the UDP service does not guarantee the delivery of SDUs (losses can occur and SDUs can arrive out-of-sequence)</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">14</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ea41152f7e091586" weblate-flags="read-only">
        <source>the UDP service will not deliver a corrupted SDU to the destination</source>
        <target state="translated">the UDP service will not deliver a corrupted SDU to the destination</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">15</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="264a9b5ab58eed07" weblate-flags="read-only">
        <source>Compared to the connectionless network layer service, the main advantage of the UDP service is that it allows several applications running on a host to exchange SDUs with several other applications running on remote hosts. Let us consider two hosts, e.g. a client and a server. The network layer service allows the client to send information to the server, but if an application running on the client wants to contact a particular application running on the server, then an additional addressing mechanism is required other than the IP address that identifies a host, in order to differentiate the application running on a host. This additional addressing is provided by `port numbers`. When a server using UDP is enabled on a host, this server registers a `port number`. This `port number` will be used by the clients to contact the server process via UDP.</source>
        <target state="translated">Compared to the connectionless network layer service, the main advantage of the UDP service is that it allows several applications running on a host to exchange SDUs with several other applications running on remote hosts. Let us consider two hosts, e.g. a client and a server. The network layer service allows the client to send information to the server, but if an application running on the client wants to contact a particular application running on the server, then an additional addressing mechanism is required other than the IP address that identifies a host, in order to differentiate the application running on a host. This additional addressing is provided by `port numbers`. When a server using UDP is enabled on a host, this server registers a `port number`. This `port number` will be used by the clients to contact the server process via UDP.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">17</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="bc14375ead8a7214" weblate-flags="read-only">
        <source>The figure below shows a typical usage of the UDP port numbers. The client process uses port number `1234` while the server process uses port number `5678`. When the client sends a request, it is identified as originating from port number `1234` on the client host and destined to port number `5678` on the server host. When the server process replies to this request, the server's UDP implementation will send the reply as originating from port  `5678` on the server host and destined to port `1234` on the client host.</source>
        <target state="translated">The figure below shows a typical usage of the UDP port numbers. The client process uses port number `1234` while the server process uses port number `5678`. When the client sends a request, it is identified as originating from port number `1234` on the client host and destined to port number `5678` on the server host. When the server process replies to this request, the server's UDP implementation will send the reply as originating from port  `5678` on the server host and destined to port `1234` on the client host.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">19</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="67ad9440d9d8d4c8" weblate-flags="read-only">
        <source>UDP uses a single segment format shown in the figure below.</source>
        <target state="translated">UDP uses a single segment format shown in the figure below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">43</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4c1e0edaeece5044" weblate-flags="read-only">
        <source>UDP Header Format</source>
        <target state="translated">UDP Header Format</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">49</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="04022431927b3016" weblate-flags="read-only">
        <source>The UDP header contains four fields :</source>
        <target state="translated">The UDP header contains four fields :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">51</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c9bde61137421d7c" weblate-flags="read-only">
        <source>a 16 bits source port</source>
        <target state="translated">a 16 bits source port</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">53</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="93eec42e42a33314" weblate-flags="read-only">
        <source>a 16 bits destination port</source>
        <target state="translated">a 16 bits destination port</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">54</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="83ff1c82861058ba" weblate-flags="read-only">
        <source>a 16 bits length field</source>
        <target state="translated">a 16 bits length field</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">55</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b55fa98a1da62f69" weblate-flags="read-only">
        <source>a 16 bits checksum</source>
        <target state="translated">a 16 bits checksum</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">56</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2a6393e47a15d182" weblate-flags="read-only">
        <source>As the port numbers are encoded as a 16 bits field, there can be up to only 65535 different server processes that are bound to a different UDP port at the same time on a given server. In practice, this limit is never reached. However, it is worth noticing that most implementations divide the range of allowed UDP port numbers into three different ranges :</source>
        <target state="translated">As the port numbers are encoded as a 16 bits field, there can be up to only 65535 different server processes that are bound to a different UDP port at the same time on a given server. In practice, this limit is never reached. However, it is worth noticing that most implementations divide the range of allowed UDP port numbers into three different ranges :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">58</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b77c3b125e4a05f3" weblate-flags="read-only">
        <source>the privileged port numbers (1 &lt; port &lt; 1024 )</source>
        <target state="translated">the privileged port numbers (1 &lt; port &lt; 1024 )</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">60</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="837863e0a7d69599" weblate-flags="read-only">
        <source>the ephemeral port numbers ( officially [#fephemeral]_ 49152 &lt;= port &lt;= 65535 )</source>
        <target state="translated">the ephemeral port numbers ( officially [#fephemeral]_ 49152 &lt;= port &lt;= 65535 )</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">61</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="896c21309f67831e" weblate-flags="read-only">
        <source>the registered port numbers (officially 1024 &lt;= port &lt; 49152)</source>
        <target state="translated">the registered port numbers (officially 1024 &lt;= port &lt; 49152)</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">62</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="98d637a431d2f8bd" weblate-flags="read-only">
        <source>In most Unix variants, only processes having system administrator privileges can be bound to port numbers smaller than `1024`. Well-known servers such as :term:`DNS`, :term:`NTP` or :term:`RPC` use privileged port numbers. When a client needs to use UDP, it usually does not require a specific port number. In this case, the UDP implementation will allocate the first available port number in the ephemeral range. The range of registered port numbers should be used by servers. In theory, developers of network servers should register their port number officially through IANA [#fportnum]_, but few developers do this.</source>
        <target state="translated">In most Unix variants, only processes having system administrator privileges can be bound to port numbers smaller than `1024`. Well-known servers such as :term:`DNS`, :term:`NTP` or :term:`RPC` use privileged port numbers. When a client needs to use UDP, it usually does not require a specific port number. In this case, the UDP implementation will allocate the first available port number in the ephemeral range. The range of registered port numbers should be used by servers. In theory, developers of network servers should register their port number officially through IANA [#fportnum]_, but few developers do this.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">64</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0d764d4ccc5d725a" weblate-flags="read-only">
        <source>Computation of the UDP checksum</source>
        <target state="translated">Computation of the UDP checksum</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">69</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f2e0f417102e78ac" weblate-flags="read-only">
        <source>The checksum of the UDP segment is computed over :</source>
        <target state="translated">The checksum of the UDP segment is computed over :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">71</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="eef54ae82a81ed8c" weblate-flags="read-only">
        <source>a pseudo header :rfc:`2460` containing the source address, the destination address, the packet length encoded as a 32 bits number and a 32 bits bit field containing the three most significant bytes set to 0 and the low order byte set to 17</source>
        <target state="translated">a pseudo header :rfc:`2460` containing the source address, the destination address, the packet length encoded as a 32 bits number and a 32 bits bit field containing the three most significant bytes set to 0 and the low order byte set to 17</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">73</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c3229dfe5b5c51b9" weblate-flags="read-only">
        <source>the entire UDP segment, including its header</source>
        <target state="translated">the entire UDP segment, including its header</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">74</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0f33eaf17eade18e" weblate-flags="read-only">
        <source>Several types of applications rely on UDP. As a rule of thumb, UDP is used for applications where delay must be minimized or losses can be recovered by the application itself. A first class of the UDP-based applications are applications where the client sends a short request and expects a quick and short answer. The :term:`DNS` is an example of a UDP application that is often used in the wide area. However, in local area networks, many distributed systems rely on Remote Procedure Call (:term:`RPC`) that is often used on top of UDP. In Unix environments, the Network File System (:term:`NFS`) is built on top of RPC and runs frequently on top of UDP. A second class of UDP-based applications are the interactive computer games that need to frequently exchange small messages, such as the player's location or their recent actions. Many of these games use UDP to minimize the delay and can recover from losses. A third class of applications are multimedia applications such as interactive Voice over IP or interactive Video over IP. These interactive applications expect a delay shorter than about 200 milliseconds between the sender and the receiver and can recover from losses directly inside the application.</source>
        <target state="translated">Several types of applications rely on UDP. As a rule of thumb, UDP is used for applications where delay must be minimized or losses can be recovered by the application itself. A first class of the UDP-based applications are applications where the client sends a short request and expects a quick and short answer. The :term:`DNS` is an example of a UDP application that is often used in the wide area. However, in local area networks, many distributed systems rely on Remote Procedure Call (:term:`RPC`) that is often used on top of UDP. In Unix environments, the Network File System (:term:`NFS`) is built on top of RPC and runs frequently on top of UDP. A second class of UDP-based applications are the interactive computer games that need to frequently exchange small messages, such as the player's location or their recent actions. Many of these games use UDP to minimize the delay and can recover from losses. A third class of applications are multimedia applications such as interactive Voice over IP or interactive Video over IP. These interactive applications expect a delay shorter than about 200 milliseconds between the sender and the receiver and can recover from losses directly inside the application.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">83</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c463aea6549199a2" weblate-flags="read-only">
        <source>Footnotes</source>
        <target state="translated">Footnotes</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">89</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="54577316522f2993" weblate-flags="read-only">
        <source>This limitation is due to the fact that the network layer cannot transport packets that are larger than 64 KBytes. As UDP does not include any segmentation/reassembly mechanism, it cannot split a SDU before sending it. The UDP header consumes 8 bytes and the IPv6 header 60. With IPv4, the IPv4 header only consumes 20 bytes and thus the maximum UDP payload size is 65507 bytes.</source>
        <target state="translated">This limitation is due to the fact that the network layer cannot transport packets that are larger than 64 KBytes. As UDP does not include any segmentation/reassembly mechanism, it cannot split a SDU before sending it. The UDP header consumes 8 bytes and the IPv6 header 60. With IPv4, the IPv4 header only consumes 20 bytes and thus the maximum UDP payload size is 65507 bytes.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">90</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="11f44371a8181fef" weblate-flags="read-only">
        <source>A discussion of the ephemeral port ranges used by different TCP/UDP implementations may be found in http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html</source>
        <target state="translated">A discussion of the ephemeral port ranges used by different TCP/UDP implementations may be found in http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">92</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="89def345e8d3827d" weblate-flags="read-only">
        <source>The complete list of allocated port numbers is maintained by IANA_ . It may be downloaded from http://www.iana.org/assignments/port-numbers</source>
        <target state="translated">The complete list of allocated port numbers is maintained by IANA_ . It may be downloaded from http://www.iana.org/assignments/port-numbers</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../protocols/udp.rst</context>
          <context context-type="linenumber">94</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
