<?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="84aa6f93ccfa8bdf" weblate-flags="read-only">
        <source>Inter-domain routing</source>
        <target state="translated">Inter-domain routing</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">5</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1d97688b164b9577" weblate-flags="read-only">
        <source>Exercises</source>
        <target state="translated">Exercises</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">9</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="409f4e61bddb41f8" weblate-flags="read-only">
        <source>Consider the interdomain topology shown in the figure below.</source>
        <target state="translated">Consider the interdomain topology shown in the figure below.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">24</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8f4f2ca0988a712f" weblate-flags="read-only">
        <source>In this network, what are the paths :</source>
        <target state="translated">In this network, what are the paths :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">56</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8812872ad63a124a" weblate-flags="read-only">
        <source>from `AS1` to `AS4`</source>
        <target state="translated">from `AS1` to `AS4`</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">58</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8527343be4e49a68" weblate-flags="read-only">
        <source>from `AS4` to `AS2`</source>
        <target state="translated">from `AS4` to `AS2`</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">59</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c98cab004465b681" weblate-flags="read-only">
        <source>from `AS4` to `AS1`</source>
        <target state="translated">from `AS4` to `AS1`</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">60</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e30c656758e596ff" weblate-flags="read-only">
        <source>Consider the interdomain topology shown in the figure below. Assuming, that `AS1` advertises prefix ``2001:db8:1::/48``,  `AS2` prefix ``2001:db8:2::/48``, ... compute the routing tables of the different ASes.</source>
        <target state="translated">Consider the interdomain topology shown in the figure below. Assuming, that `AS1` advertises prefix ``2001:db8:1::/48``,  `AS2` prefix ``2001:db8:2::/48``, ... compute the routing tables of the different ASes.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">63</context>
        </context-group>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">96</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4fb597bfdcb92200" weblate-flags="read-only">
        <source>Are all ASes capable of reaching all the other ASes in this simple Internet ?</source>
        <target state="translated">Are all ASes capable of reaching all the other ASes in this simple Internet ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">93</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="07ca2b4cf8097402" weblate-flags="read-only">
        <source>In this internet, some ASes cannot reach all other ASes. Can you fix the problem by adding one shared-cost peering link or one customer-provider peering link ?</source>
        <target state="translated">In this internet, some ASes cannot reach all other ASes. Can you fix the problem by adding one shared-cost peering link or one customer-provider peering link ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">128</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7a7b191c0fa73020" weblate-flags="read-only">
        <source>Consider the network below in which a stub domain, `AS456`, is connected to two providers `AS123` and `AS789`. `AS456` advertises its prefix to both its providers. On the other hand, `AS123` advertises ``2001:db8:dead::/48`` while `AS789` advertises ``2001:db8:beef::/48`` and ``2001:db8:dead:cafe::/63``. Via which provider will the packets destined to ``2001:db8:dead:cafe::1`` will be received by `AS456` ?</source>
        <target state="translated">Consider the network below in which a stub domain, `AS456`, is connected to two providers `AS123` and `AS789`. `AS456` advertises its prefix to both its providers. On the other hand, `AS123` advertises ``2001:db8:dead::/48`` while `AS789` advertises ``2001:db8:beef::/48`` and ``2001:db8:dead:cafe::/63``. Via which provider will the packets destined to ``2001:db8:dead:cafe::1`` will be received by `AS456` ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">133</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="59939203d3f2fb96" weblate-flags="read-only">
        <source>Should `AS123` change its configuration ?</source>
        <target state="translated">Should `AS123` change its configuration ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">141</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="10df4058e7ebb2b7" weblate-flags="read-only">
        <source>Consider that the AS stub (`AS456`) shown in the figure below decides to advertise two ``/48`` prefixes instead of its allocated ``/47`` prefix.</source>
        <target state="translated">Consider that the AS stub (`AS456`) shown in the figure below decides to advertise two ``/48`` prefixes instead of its allocated ``/47`` prefix.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">143</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5398fb797fa040f6" weblate-flags="read-only">
        <source>Via which provider does `AS456` receive the packets destined to ``2001:db8:caff::bb`` and ``2001:db8:cafe::aa`` ?</source>
        <target state="translated">Via which provider does `AS456` receive the packets destined to ``2001:db8:caff::bb`` and ``2001:db8:cafe::aa`` ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">151</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0295f2da57798ae0" weblate-flags="read-only">
        <source>How is the reachability of these addresses affected when link `R1`-`R3` fails ?</source>
        <target state="translated">How is the reachability of these addresses affected when link `R1`-`R3` fails ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">153</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="a618b53bbe95cca4" weblate-flags="read-only">
        <source>Propose a configuration on R1 that achieves the same objective as the one shown in the figure but also preserves the reachability of all IP addresses inside `AS456` if one of `AS456`'s interdomain links fails.</source>
        <target state="translated">Propose a configuration on R1 that achieves the same objective as the one shown in the figure but also preserves the reachability of all IP addresses inside `AS456` if one of `AS456`'s interdomain links fails.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">155</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c494d14c02ffc12a" weblate-flags="read-only">
        <source>Consider the network shown below. In this network, the metric of each link is set to `1` except link `A-B` whose metric is set to `4` in both directions. In this network, there are two paths with the same cost between `D` and `C`. Old routers would randomly select one of these equal cost paths and install it in their forwarding table. Recent routers are able to use up to `N` equal cost paths towards the same destination.</source>
        <target state="translated">Consider the network shown below. In this network, the metric of each link is set to `1` except link `A-B` whose metric is set to `4` in both directions. In this network, there are two paths with the same cost between `D` and `C`. Old routers would randomly select one of these equal cost paths and install it in their forwarding table. Recent routers are able to use up to `N` equal cost paths towards the same destination.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">157</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="fd59a12d661c781d" weblate-flags="read-only">
        <source>A simple network</source>
        <target state="translated">A simple network</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">163</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e86473b859666c6d" weblate-flags="read-only">
        <source>On recent routers, a lookup in the forwarding table for a destination address returns a set of outgoing interfaces. How would you design an algorithm that selects the outgoing interface used for each packet, knowing that to avoid reordering, all segments of a given TCP connection should follow the same path ?</source>
        <target state="translated">On recent routers, a lookup in the forwarding table for a destination address returns a set of outgoing interfaces. How would you design an algorithm that selects the outgoing interface used for each packet, knowing that to avoid reordering, all segments of a given TCP connection should follow the same path ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">165</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e4d7dc571fa7e098" weblate-flags="read-only">
        <source>A ``traceroute6`` towards ``ipv6.google.com`` provides the following output :</source>
        <target state="translated">A ``traceroute6`` towards ``ipv6.google.com`` provides the following output :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">167</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7667148a48aaf2a8" weblate-flags="read-only">
        <source>Can you explain why at the eighth, ninth and tenth hopes several IPv6 addresses are reported in the ``traceroute6`` output ?</source>
        <target state="translated">Can you explain why at the eighth, ninth and tenth hopes several IPv6 addresses are reported in the ``traceroute6`` output ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">191</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="fae76fbd28135f1b" weblate-flags="read-only">
        <source>`Section 3.3 &lt;https://tools.ietf.org/html/rfc4443#section-3.3&gt;`_ of :rfc:`4443` explains two different reasons why an IPv6 enabled device could generate an ICMPv6 Time Exceeded message. Explain when a router could generate such a message with ``Code==0`` and when a host could generate such a message with ``Code==1``.</source>
        <target state="translated">`Section 3.3 &lt;https://tools.ietf.org/html/rfc4443#section-3.3&gt;`_ of :rfc:`4443` explains two different reasons why an IPv6 enabled device could generate an ICMPv6 Time Exceeded message. Explain when a router could generate such a message with ``Code==0`` and when a host could generate such a message with ``Code==1``.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">193</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="753f71d2a8dbc409" weblate-flags="read-only">
        <source>`Section 3.1 &lt;https://tools.ietf.org/html/rfc4443#section-3.1&gt;`_ of :rfc:`4443` seven different Codes for the ICMPv6 Destination Unreachable Message. Under which circumstances would a router generate such an ICMPv6 message with :</source>
        <target state="translated">`Section 3.1 &lt;https://tools.ietf.org/html/rfc4443#section-3.1&gt;`_ of :rfc:`4443` seven different Codes for the ICMPv6 Destination Unreachable Message. Under which circumstances would a router generate such an ICMPv6 message with :</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">195</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="862ddb02a00c07bf" weblate-flags="read-only">
        <source>``Code==0``</source>
        <target state="translated">``Code==0``</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">197</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c44280943b4abe2d" weblate-flags="read-only">
        <source>An ICMPv6 error message includes in its message body the beginning of the IPv6 packet that triggered this error. How many bytes of the original packet must be returned to allow the host to recover the original source and destination addresses and source and destination ports of the packet that caused the error ?</source>
        <target state="translated">An ICMPv6 error message includes in its message body the beginning of the IPv6 packet that triggered this error. How many bytes of the original packet must be returned to allow the host to recover the original source and destination addresses and source and destination ports of the packet that caused the error ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/routing-policies.rst</context>
          <context context-type="linenumber">213</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
