<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-intarea-v4-via-v6-09" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="v4-via-v6">IPv4 routes with an IPv6 next hop</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-intarea-v4-via-v6-09"/>
    <author fullname="Juliusz Chroboczek">
      <organization>IRIF, Université Paris-Cité</organization>
      <address>
        <postal>
          <street>Case 7014</street>
          <street>75205 Paris Cedex 13</street>
          <street>France</street>
        </postal>
        <email>jch@irif.fr</email>
      </address>
    </author>
    <author initials="W." surname="Kumari" fullname="Warren Kumari">
      <organization>Google, LLC</organization>
      <address>
        <email>warren@kumari.net</email>
      </address>
    </author>
    <author initials="T." surname="Høiland-Jørgensen" fullname="Toke Høiland-Jørgensen">
      <organization>Red Hat</organization>
      <address>
        <email>toke@toke.dk</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Internet</area>
    <workgroup>Internet Area Working Group</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 64?>

<t>V4-via-v6 routing is a technique that uses IPv6 next-hop addresses for
forwarding IPv4 packets, and thus makes it possible to route IPv4 packets
across a network where some routers have not been assigned IPv4 addresses.
This document describes v4-via-v6 routing, and defines related operational
procedures, notably the origination of ICMPv4 packets by nodes that might
not have an IPv4 address.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://wkumari.github.io/draft-chroboczek-intarea-v4-via-v6/draft-ietf-intarea-v4-via-v6.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-intarea-v4-via-v6/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Internet Area Working Group Working Group mailing list (<eref target="mailto:int-area@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/int-area/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/int-area/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/wkumari/draft-chroboczek-intarea-v4-via-v6"/>.</t>
    </note>
  </front>
  <middle>
    <?line 73?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The dominant form of routing in the Internet is next-hop routing, where
a routing protocol constructs a routing table (or routing information
base, RIB) which is used by a forwarding process to forward packets.  The
routing table is a data structure that maps network prefixes in a given
family (IPv4 or IPv6) to next hops, pairs of an outgoing interface and
a neighbor's network address, for example:</t>
      <artwork><![CDATA[
    destination                      next hop
  2001:db8:0:1::/64               eth0, fe80::1234:5678
  203.0.113.0/24                  eth0, 192.0.2.1
]]></artwork>
      <t>When a packet is forwarded according to a given routing table entry, the
forwarding plane typically maps the next-hop address to a link-layer
address (a "MAC address") by using an address resolution protocol (for
example the Neighbor Discovery protocol (ND) <xref target="RFC4861"/> in the case of
IPv6 over Ethernet, and the Address Resolution Protocol (ARP) <xref target="RFC0826"/>
in the case of IPv4 over Ethernet).  The link-layer address is then used
to construct the link-layer frames that encapsulate forwarded packets.</t>
      <t>It is apparent from the description above that there is no fundamental
reason why the destination prefix and the next-hop address should be in
the same address family: there is nothing preventing an IPv6 packet from
being forwarded through a next hop with an IPv4 address (in which case the
next hop's MAC address will typically be obtained using ARP), or,
conversely, an IPv4 packet from being forwarded through a next hop with an
IPv6 address (in which case it will be resolved using ND).  (In fact, it
is even possible to store link-layer addresses directly in the next-hop
entry of the routing table, thus avoiding the use of an address resolution
protocol altogether, which was commonly done in networks using the OSI
protocol suite.)</t>
      <t>This document focuses on the specific case of routing IPv4 packets through
an IPv6 next hop.  This case is particularly interesting, since it makes
it possible to build networks that have no IPv4 addresses except at the
edges and still provide IPv4 connectivity to edge hosts. In addition,
since an IPv6 next hop can use a link-local address that is autonomously
configured, the use of such routes enables a mode of operation where the
network core has no statically assigned IP addresses of either family,
which significantly reduces the amount of manual configuration required.
(See also <xref target="RFC7404"/> for a discussion of the issues involved with such an
approach.)</t>
      <t>A route towards an IPv4 prefix that uses an IPv6 next hop is called
a "v4-via-v6" route.  While v4-via-v6 routing is applicable both to hosts
and to routers, this document focuses on its implementation in routers.
Applying v4-via-v6 routing to hosts will require solving the issue of host
configuration, for example by extending either DHCPv4 or DHCPv6 to publish
an IPv4 default route with an IPv6 next hop.</t>
      <t><xref target="RFC8950"/> discusses advertising of IPv4 Network Layer Reachability
Information (NLRI) with a next-hop address that belongs to the IPv6
protocol, but confines itself to how this is carried and advertised in the
BGP protocol. This document, on the other hand, discusses the concept of
v4-via-v6 routes independently of any specific routing protocol, their
design and operational considerations, and the implications of using them.</t>
      <t>{ Editor note, to be removed before publication. This document is heavily based
on draft-ietf-babel-v4viav6. When draft-ietf-babel-v4viav6 was
going through IESG eval, Warren raised concerns that something this
fundamental deserved to be documented in a separate, standalone document, so
that it can be more fully discussed, and, more importantly, referenced
cleanly in the future.}</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="operation">
      <name>Operation</name>
      <t>Next-hop routing is implemented by two separate components, the routing
protocol and the forwarding plane, that communicate through a shared
data structure, the routing table.</t>
      <section anchor="structure-of-the-routing-table">
        <name>Structure of the routing table</name>
        <t>The routing table is a data structure that maps address prefixes to
next hops, pairs of the form (interface, address).  In traditional
next-hop routing, the routing table maps IPv4 prefixes to IPv4 next hops,
and IPv6 prefixes to IPv6 next hops.  With v4-via-v6 routing, the routing
table is extended so that an IPv4 prefix may map to either an IPv6 or an
IPv4 next hop.</t>
        <t>Resolution may be recursive: the next hop may itself be a prefix that
requires further resolution to map to the outgoing interface and L2
address.  V4-via-v6 routing does not prevent recursive resolution.</t>
      </section>
      <section anchor="operation-of-the-forwarding-plane">
        <name>Operation of the forwarding plane</name>
        <t>The forwarding plane is the part of the routing implementation that is
executed for every packet to be forwarded.  As a packet arrives, the
forwarding plane consults the routing table, selects a single entry
matching the packet, and forwards the packet through the outgoing
interface to the associated next-hop address.</t>
        <t>With v4-via-v6 routing, the address family of the next-hop address is no
longer determined by the address family of the prefix: since the routing
table may map an IPv4 prefix to either an IPv4 or an IPv6 next hop, the
forwarding plane must be able to determine, on a per-packet basis, which
address resolution protocol (ARP for IPv4, ND for IPv6) to consult.</t>
      </section>
      <section anchor="operation-of-routing-protocols">
        <name>Operation of routing protocols</name>
        <t>The routing protocol is the part of the routing implementation that is
executed asynchronously from the forwarding plane, and whose role is to
build the routing table.  Since v4-via-v6 routing is a generalization of
traditional next-hop routing, v4-via-v6 can interoperate with existing
routing protocols: a traditional routing protocol produces a traditional
next-hop routing table, which can be used by an implementation supporting
v4-via-v6 routing.</t>
        <t>However, in order to use the additional flexibility provided by v4-via-v6
routing, routing protocols need to be extended with the ability to
populate the routing table with v4-via-v6 routes when an IPv4 address is
not available or when the available IPv4 addresses are not suitable for
use as a next hop.</t>
        <t>Some protocols already support the advertisement of IPv4 routes with an
IPv6 next hop, including Babel <xref target="RFC9229"/> and BGP <xref target="RFC8950"/>.  Other
protocols advertise both IPv4 and IPv6 prefixes over a single neighbor
association, but they use completely separate data planes for IPv4 and
IPv6, and do not implement v4-via-v6 routing.  These protocols include:</t>
        <ul spacing="normal">
          <li>
            <t>Multiple Instance Routing in OSPFv3 (<xref target="RFC5838"/>),</t>
          </li>
          <li>
            <t>Integrated Routing in IS-IS (<xref target="RFC5308"/>), and</t>
          </li>
          <li>
            <t>Multi-Topology (MT) Routing in IS-IS (<xref target="RFC5120"/>).</t>
          </li>
        </ul>
      </section>
      <section anchor="interaction-with-bfd">
        <name>Interaction with BFD</name>
        <t>When Bidirectional Forwarding Detection (BFD) is used to monitor the liveliness
of a v4-via-v6 route, only the data from the IPv6 BFD session should be used for
input to the v4-via-v6 routing process.</t>
      </section>
    </section>
    <section anchor="sec-icmp">
      <name>ICMP Considerations</name>
      <t>The Internet Control Message Protocol (ICMP) <xref target="RFC0792"/> is a protocol
related to IPv4 that is primarily used to carry diagnostic and debugging
information.  Within this document we use the term "ICMPv4" to refer to
ICMP.  ICMPv4 packets may be originated by end hosts (e.g., the
"destination unreachable, port unreachable" ICMPv4 packet), but they may
also be originated by intermediate routers (e.g., most other kinds of
"destination unreachable" packets).</t>
      <t>Some protocols deployed in the Internet rely on ICMPv4 packets sent by
intermediate routers.  Most notably, path MTU Discovery (PMTUd) <xref target="RFC1191"/>
is an algorithm executed by end hosts to discover the maximum packet size
that a path is able to carry.  While there exist variants of PMTUd that
are purely end-to-end <xref target="RFC8899">RFC4821</xref>, the variant most commonly
deployed in the Internet has a hard dependency on ICMPv4 packets
originated by intermediate routers: if intermediate routers are unable to
send ICMPv4 packets, PMTUd may lead to persistent black-holing of IPv4
traffic.</t>
      <t>A router must therefore be able to generate ICMPv4 Destination Unreachable
messages (as required by <xref target="RFC1812"/> Section 5.2.7.1).  The source address
of these messages must be one of the addresses assigned to the outgoing
interface; if no such address has been assigned, then one of the other
addresses assigned to the router, known as the "router-id", must be used
(<xref target="RFC1812"/> Section 4.3.2.4).</t>
      <t>Routers implementing the mechanism described in this document do not need
to have any IPv4 addresses assigned to any of their interfaces, and <xref target="RFC1812"/>
does not specify what happens if no router-id has been assigned.  If
a router does not have any IPv4 addresses assigned, the router <bcp14>MUST</bcp14> use
the dummy address 192.0.0.8 as the source address of outgoing ICMPv4 packets
(which is compatible with <xref target="RFC7600"/>, Section 4.8, Requirement R-22).</t>
      <t>Using the dummy address as the source of ICMPv4 packet causes a number of
drawbacks:</t>
      <ul spacing="normal">
        <li>
          <t>using the same address on multiple routers may hamper debugging and
fault isolation, e.g., when using the <em>traceroute</em> utility (but see
<xref target="I-D.draft-ietf-intarea-extended-icmp-nodeid"/> for a possible solution
to this problem);</t>
        </li>
        <li>
          <t>packets originating from 192.0.0.8 might be considered as spoofed
traffic and dropped by firewalls at network boundaries.</t>
        </li>
      </ul>
      <t>For these reasons, even if a router performs v4-via-v6 routing on all
interfaces, it <bcp14>MAY</bcp14> be assigned one or more IPv4 addresses.</t>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>(RFC Editor: please remove this section before publication.)</t>
      <t>(This section records the status of known implementations of the protocol
defined by this specification at the time of writing, and is based on
a proposal described in RFC 7942.  The description of implementations in
this section is intended to assist the IETF in its decision processes in
progressing drafts to RFCs.  Please note that the listing of any
individual implementation here does not imply endorsement by the IETF.
Furthermore, no effort has been spent to verify the information presented
here that was supplied by IETF contributors.  This is not intended as, and
must not be construed to be, a catalog of available implementations or
their features.  Readers are advised to note that other implementations
may exist.)</t>
      <section anchor="arista-eos">
        <name>Arista EOS</name>
        <t>Arista has supported static IPv4 routes with IPv6 next hops since EOS-4.30.1.</t>
      </section>
      <section anchor="the-babel-routing-protocol">
        <name>The Babel routing protocol</name>
        <t>As noted above, this document is heavily based on RFC9229
(née draft-ietf-babel-v4viav6), and this functionality is supported by babeld.</t>
        <t>Pasted below is email sent to the babel mailing list (archived
at https://mailarchive.ietf.org/arch/msg/babel/QtFi3F4TFfF7fXXlkHSpEnuT44Y/)</t>
        <t>An IPv4 route across three nodes with IPv6 addresses only:</t>
        <artwork><![CDATA[
$ ip route show 10.0.0.2
10.0.0.2 via inet6 fe80::216:3eff:fe00:1 dev lxcbr0 proto babel onlink
]]></artwork>
        <t>Here's how it's logged by babeld:</t>
        <artwork><![CDATA[
10.0.0.2/32 from 0.0.0.0/0 metric 384 (384) refmetric 288 id
02:16:3e:ff:fe:9a:5e:22 seqno 36425 chan (255) age 15 via lxcbr0 neigh
fe80::216:3eff:fe00:1 (installed)
]]></artwork>
        <t>Traceroute is a little confusing:</t>
        <artwork><![CDATA[
$ traceroute 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
 1  192.0.0.8 (192.0.0.8)  0.079 ms  0.019 ms  0.014 ms
 2  192.0.0.8 (192.0.0.8)  0.040 ms  0.023 ms  0.042 ms
 3  192.0.0.8 (192.0.0.8)  0.061 ms  0.030 ms  0.030 ms
 4  10.0.0.2 (10.0.0.2)  0.060 ms  0.040 ms  0.039 ms
]]></artwork>
        <t>PMTUD works fine (thanks to Toke):</t>
        <artwork><![CDATA[
19:58:47.402871 IP 192.168.0.27.60046 > 10.0.0.2.22: Flags [.],\
seq 33:1481, ack 33, win 502, options [nop,nop,TS val 917354570\
ecr 1849974691], length 1448
19:58:47.402874 IP 192.168.0.27.60046 > 10.0.0.2.22: Flags [P.],\
seq 1481:1537, ack 33, win 502, options [nop,nop,TS val 917354570\
ecr 1849974691], length 56
19:58:47.402906 IP 192.0.0.8 > 192.168.0.27: ICMP 10.0.0.2 \
unreachable- need to frag (mtu 1420), length 556
19:58:47.402919 IP 10.0.0.2.22 > 192.168.0.27.60046: Flags [.],\
ack 33, win 509, options [nop,nop,TS val 1849974692 \
ecr 917354569,nop,nop,sac 1 {1481:1537}], length 0
19:58:47.402934 IP 192.168.0.27.60046 > 10.0.0.2.22: Flags [.], \
seq 33:1401, ack 33, win 502, options [nop,nop,TS val 917354570 \
ecr 1849974692], length 1368
]]></artwork>
        <t>-- Juliusz</t>
      </section>
      <section anchor="linux">
        <name>Linux</name>
        <t>Linux has supported v4-via-v6 routes since kernel version 5.2, released on
2019-07-07.</t>
        <section anchor="example">
          <name>Example:</name>
          <artwork><![CDATA[
rincewind ~ #
ip -4 r a 192.0.2.23/32 via inet6 2001:db8::2342

rincewind ~ # ip r s 192.0.2.23/32
192.0.2.23 via inet6 2001:db8::2342 dev wlp36s0.25
]]></artwork>
        </section>
      </section>
      <section anchor="mikrotik-routeros">
        <name>Mikrotik RouterOS</name>
        <t>Mikrotik RouterOS has supported v4-via-v6 routes since (at least) version
7.11beta2</t>
        <t>{Editor note: I'm not sure when support was added. I tested this in Version
7.11beta2, and it worked there, but I believe that this functionality has
existed for a while. I'll try to find out when it was added.}</t>
        <section anchor="example-1">
          <name>Example</name>
          <artwork><![CDATA[
[wkumari@Dulles-CCR] /ip/route> print
Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; c - CONNECT, s - STATIC,
d -DHCP, v - VPN; H - HW-OFFLOADED
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#      DST-ADDRESS       GATEWAY                             DISTANCE
0  As  192.0.2.0/24      fe80::201:5cff:feb2:1646%1_Comcast         1
]]></artwork>
        </section>
      </section>
      <section anchor="cisco-nx-os">
        <name>Cisco NX-OS</name>
        <t>Cisco NX-OS has supported v4-via-v6 routes "for more than 8 years"
  -- Krishnaswamy Ananthamurthy</t>
      </section>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>V4-via-v6 routing makes it easy to forward IPv4 traffic across interfaces
that have not been assigned IPv4 addresses, and therefore has the
potential to reduce the number of IPv4 addresses consumed and hopefully
simplify the management of double-stack networks.  Since it promises IPv4
routing essentially "for free" once IPv6 addressing has been set up, it
has the potential to slightly accelerate the deployment of IPv6.</t>
      <t>Just like any other extension to an existing technology, however, it
requires changes to existing infrastructure.  Even though v4-via-v6 routes
are similar in structure to traditional next-hop routes, at least some
monitoring and management tools will not be able to interpret them.
Deployment of v4-via-v6 routing in a network requires testing and
potentially updating of all tools and scripts that manipulate or examine
routes.</t>
      <t>V4-via-v6 routing encourages a model of deployment where some routers have
no IPv4 addresses even though they forward IPv4 traffic.  Such routers
make debugging of IPv4 routing issues somewhat more difficult, most
notably by making the output of the <em>traceroute</em> utility less informative
than it would otherwise be (see <xref target="sec-icmp"/>).  Even if the procedures
described in <xref target="I-D.draft-ietf-intarea-extended-icmp-nodeid"/> are deployed
on all such routers, older versions of <em>traceroute</em> will not be able to
interpret the additional information.  Network administrators might want
to provision IPv4 addresses on all routers in order to simplify debugging.</t>
      <t>To ensure proper manageability and visibility for network operators,
implementations <bcp14>MUST</bcp14> implement the following behaviors:</t>
      <ol spacing="normal" type="1"><li>
          <t>Routing Table Representation: When displaying the routing table (on
a command-line interface or a management protocol), the next hop for
a v4-via-v6 route must be explicitly shown as an IPv6 address.
Implementations <bcp14>MUST NOT</bcp14> attempt to synthesize a dummy or mapped IPv4
next-hop address for display purposes, as this can mislead operators
during troubleshooting.</t>
        </li>
        <li>
          <t>YANG Data Model Interaction: Standard routing YANG models (such as those
defined in RFC 8349, "A YANG Data Model for Routing Management") represent
next hops within container structures restricted by IP address family.  To
support  v4-via-v6 routing:</t>
        </li>
      </ol>
      <ul spacing="normal">
        <li>
          <t>The implementation's YANG datastore <bcp14>MUST</bcp14> allow the next hop of an IPv4 route
entry to point to a leaf of type 'ipv6-address'.</t>
        </li>
        <li>
          <t>If an implementation's strict schema validation prevents mixing address
families in standard containers, augmented schemas or local deviations <bcp14>MUST</bcp14>
be used to explicitly allow an IPv6 next-hop within the IPv4 routing context.</t>
        </li>
      </ul>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The techniques described in this document make routing more flexible by
allowing IPv4 routes to propagate across a section of a network that has
only been assigned IPv6 addresses.  This additional flexibility might
invalidate otherwise reasonable assumptions made by network
administrators, which could potentially cause security issues.</t>
      <t>For example, if an island of IPv4-only hosts is separated from the IPv4
Internet by routers that have not been assigned IPv4 addresses, a network
administrator might reasonably assume that the IPv4-only hosts are
unreachable from the IPv4 Internet.  This assumption is broken if the
intermediary routers implement v4-via-v6 routing, which might make the
IPv4-only hosts reachable from the IPv4 Internet.  If this is not
desirable, then the network administrator must filter out the undesirable
traffic in the forwarding plane by implementing suitable packet filtering
rules.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>No IANA actions are requested by this document.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC1812">
          <front>
            <title>Requirements for IP Version 4 Routers</title>
            <author fullname="F. Baker" initials="F." role="editor" surname="Baker"/>
            <date month="June" year="1995"/>
            <abstract>
              <t>This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1812"/>
          <seriesInfo name="DOI" value="10.17487/RFC1812"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC0792">
          <front>
            <title>Internet Control Message Protocol</title>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="September" year="1981"/>
          </front>
          <seriesInfo name="STD" value="5"/>
          <seriesInfo name="RFC" value="792"/>
          <seriesInfo name="DOI" value="10.17487/RFC792"/>
        </reference>
        <reference anchor="RFC0826">
          <front>
            <title>An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware</title>
            <author fullname="D. Plummer" initials="D." surname="Plummer"/>
            <date month="November" year="1982"/>
            <abstract>
              <t>The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="37"/>
          <seriesInfo name="RFC" value="826"/>
          <seriesInfo name="DOI" value="10.17487/RFC826"/>
        </reference>
        <reference anchor="RFC1191">
          <front>
            <title>Path MTU discovery</title>
            <author fullname="J. Mogul" initials="J." surname="Mogul"/>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <date month="November" year="1990"/>
            <abstract>
              <t>This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1191"/>
          <seriesInfo name="DOI" value="10.17487/RFC1191"/>
        </reference>
        <reference anchor="RFC4821">
          <front>
            <title>Packetization Layer Path MTU Discovery</title>
            <author fullname="M. Mathis" initials="M." surname="Mathis"/>
            <author fullname="J. Heffner" initials="J." surname="Heffner"/>
            <date month="March" year="2007"/>
            <abstract>
              <t>This document describes a robust method for Path MTU Discovery (PMTUD) that relies on TCP or some other Packetization Layer to probe an Internet path with progressively larger packets. This method is described as an extension to RFC 1191 and RFC 1981, which specify ICMP-based Path MTU Discovery for IP versions 4 and 6, respectively. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4821"/>
          <seriesInfo name="DOI" value="10.17487/RFC4821"/>
        </reference>
        <reference anchor="RFC4861">
          <front>
            <title>Neighbor Discovery for IP version 6 (IPv6)</title>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <author fullname="W. Simpson" initials="W." surname="Simpson"/>
            <author fullname="H. Soliman" initials="H." surname="Soliman"/>
            <date month="September" year="2007"/>
            <abstract>
              <t>This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4861"/>
          <seriesInfo name="DOI" value="10.17487/RFC4861"/>
        </reference>
        <reference anchor="RFC5120">
          <front>
            <title>M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)</title>
            <author fullname="T. Przygienda" initials="T." surname="Przygienda"/>
            <author fullname="N. Shen" initials="N." surname="Shen"/>
            <author fullname="N. Sheth" initials="N." surname="Sheth"/>
            <date month="February" year="2008"/>
            <abstract>
              <t>This document describes an optional mechanism within Intermediate System to Intermediate Systems (IS-ISs) used today by many ISPs for IGP routing within their clouds. This document describes how to run, within a single IS-IS domain, a set of independent IP topologies that we call Multi-Topologies (MTs). This MT extension can be used for a variety of purposes, such as an in-band management network "on top" of the original IGP topology, maintaining separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or forcing a subset of an address space to follow a different topology. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5120"/>
          <seriesInfo name="DOI" value="10.17487/RFC5120"/>
        </reference>
        <reference anchor="RFC5308">
          <front>
            <title>Routing IPv6 with IS-IS</title>
            <author fullname="C. Hopps" initials="C." surname="Hopps"/>
            <date month="October" year="2008"/>
            <abstract>
              <t>This document specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes two new TLVs: a reachability TLV and an interface address TLV to distribute the necessary IPv6 information throughout a routing domain. Using this method, one can route IPv6 along with IPv4 and OSI using a single intra-domain routing protocol. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5308"/>
          <seriesInfo name="DOI" value="10.17487/RFC5308"/>
        </reference>
        <reference anchor="RFC5838">
          <front>
            <title>Support of Address Families in OSPFv3</title>
            <author fullname="A. Lindem" initials="A." role="editor" surname="Lindem"/>
            <author fullname="S. Mirtorabi" initials="S." surname="Mirtorabi"/>
            <author fullname="A. Roy" initials="A." surname="Roy"/>
            <author fullname="M. Barnes" initials="M." surname="Barnes"/>
            <author fullname="R. Aggarwal" initials="R." surname="Aggarwal"/>
            <date month="April" year="2010"/>
            <abstract>
              <t>This document describes a mechanism for supporting multiple address families (AFs) in OSPFv3 using multiple instances. It maps an AF to an OSPFv3 instance using the Instance ID field in the OSPFv3 packet header. This approach is fairly simple and minimizes extensions to OSPFv3 for supporting multiple AFs. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5838"/>
          <seriesInfo name="DOI" value="10.17487/RFC5838"/>
        </reference>
        <reference anchor="RFC5881">
          <front>
            <title>Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)</title>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <author fullname="D. Ward" initials="D." surname="Ward"/>
            <date month="June" year="2010"/>
            <abstract>
              <t>This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over IPv4 and IPv6 for single IP hops. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5881"/>
          <seriesInfo name="DOI" value="10.17487/RFC5881"/>
        </reference>
        <reference anchor="RFC5883">
          <front>
            <title>Bidirectional Forwarding Detection (BFD) for Multihop Paths</title>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <author fullname="D. Ward" initials="D." surname="Ward"/>
            <date month="June" year="2010"/>
            <abstract>
              <t>This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over multihop paths, including unidirectional links. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5883"/>
          <seriesInfo name="DOI" value="10.17487/RFC5883"/>
        </reference>
        <reference anchor="RFC7404">
          <front>
            <title>Using Only Link-Local Addressing inside an IPv6 Network</title>
            <author fullname="M. Behringer" initials="M." surname="Behringer"/>
            <author fullname="E. Vyncke" initials="E." surname="Vyncke"/>
            <date month="November" year="2014"/>
            <abstract>
              <t>In an IPv6 network, it is possible to use only link-local addresses on infrastructure links between routers. This document discusses the advantages and disadvantages of this approach to facilitate the decision process for a given network.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7404"/>
          <seriesInfo name="DOI" value="10.17487/RFC7404"/>
        </reference>
        <reference anchor="RFC7600">
          <front>
            <title>IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)</title>
            <author fullname="R. Despres" initials="R." surname="Despres"/>
            <author fullname="S. Jiang" initials="S." role="editor" surname="Jiang"/>
            <author fullname="R. Penno" initials="R." surname="Penno"/>
            <author fullname="Y. Lee" initials="Y." surname="Lee"/>
            <author fullname="G. Chen" initials="G." surname="Chen"/>
            <author fullname="M. Chen" initials="M." surname="Chen"/>
            <date month="July" year="2015"/>
            <abstract>
              <t>This document specifies a stateless solution for service providers to progressively deploy IPv6-only network domains while still offering IPv4 service to customers. The solution's distinctive properties are that TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during domain traversal and that IPv4 fragmentation rules are fully preserved end to end. Each customer can be assigned one public IPv4 address, several public IPv4 addresses, or a shared address with a restricted port set.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7600"/>
          <seriesInfo name="DOI" value="10.17487/RFC7600"/>
        </reference>
        <reference anchor="RFC8899">
          <front>
            <title>Packetization Layer Path MTU Discovery for Datagram Transports</title>
            <author fullname="G. Fairhurst" initials="G." surname="Fairhurst"/>
            <author fullname="T. Jones" initials="T." surname="Jones"/>
            <author fullname="M. Tüxen" initials="M." surname="Tüxen"/>
            <author fullname="I. Rüngeler" initials="I." surname="Rüngeler"/>
            <author fullname="T. Völker" initials="T." surname="Völker"/>
            <date month="September" year="2020"/>
            <abstract>
              <t>This document specifies Datagram Packetization Layer Path MTU Discovery (DPLPMTUD). This is a robust method for Path MTU Discovery (PMTUD) for datagram Packetization Layers (PLs). It allows a PL, or a datagram application that uses a PL, to discover whether a network path can support the current size of datagram. This can be used to detect and reduce the message size when a sender encounters a packet black hole. It can also probe a network path to discover whether the maximum packet size can be increased. This provides functionality for datagram transports that is equivalent to the PLPMTUD specification for TCP, specified in RFC 4821, which it updates. It also updates the UDP Usage Guidelines to refer to this method for use with UDP datagrams and updates SCTP.</t>
              <t>The document provides implementation notes for incorporating Datagram PMTUD into IETF datagram transports or applications that use datagram transports.</t>
              <t>This specification updates RFC 4960, RFC 4821, RFC 6951, RFC 8085, and RFC 8261.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8899"/>
          <seriesInfo name="DOI" value="10.17487/RFC8899"/>
        </reference>
        <reference anchor="RFC8950">
          <front>
            <title>Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next Hop</title>
            <author fullname="S. Litkowski" initials="S." surname="Litkowski"/>
            <author fullname="S. Agrawal" initials="S." surname="Agrawal"/>
            <author fullname="K. Ananthamurthy" initials="K." surname="Ananthamurthy"/>
            <author fullname="K. Patel" initials="K." surname="Patel"/>
            <date month="November" year="2020"/>
            <abstract>
              <t>Multiprotocol BGP (MP-BGP) specifies that the set of usable next-hop address families is determined by the Address Family Identifier (AFI) and the Subsequent Address Family Identifier (SAFI). The AFI/SAFI definitions for the IPv4 address family only have provisions for advertising a next-hop address that belongs to the IPv4 protocol when advertising IPv4 Network Layer Reachability Information (NLRI) or VPN-IPv4 NLRI.</t>
              <t>This document specifies the extensions necessary to allow the advertising of IPv4 NLRI or VPN-IPv4 NLRI with a next-hop address that belongs to the IPv6 protocol. This comprises an extension of the AFI/SAFI definitions to allow the address of the next hop for IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, the encoding of the next hop to determine which of the protocols the address actually belongs to, and a BGP Capability allowing MP-BGP peers to dynamically discover whether they can exchange IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 next hop. This document obsoletes RFC 5549.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8950"/>
          <seriesInfo name="DOI" value="10.17487/RFC8950"/>
        </reference>
        <reference anchor="RFC9229">
          <front>
            <title>IPv4 Routes with an IPv6 Next Hop in the Babel Routing Protocol</title>
            <author fullname="J. Chroboczek" initials="J." surname="Chroboczek"/>
            <date month="May" year="2022"/>
            <abstract>
              <t>This document defines an extension to the Babel routing protocol that allows announcing routes to an IPv4 prefix with an IPv6 next hop, which makes it possible for IPv4 traffic to flow through interfaces that have not been assigned an IPv4 address.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9229"/>
          <seriesInfo name="DOI" value="10.17487/RFC9229"/>
        </reference>
        <reference anchor="I-D.draft-ietf-intarea-extended-icmp-nodeid">
          <front>
            <title>ICMP Message Extension for Originating Node Identification</title>
            <author fullname="Bill Fenner" initials="B." surname="Fenner">
              <organization>Arista Networks</organization>
            </author>
            <author fullname="Reji Thomas" initials="R." surname="Thomas">
              <organization>Arista Networks</organization>
            </author>
            <date day="6" month="October" year="2026"/>
            <abstract>
              <t>   RFC5837 describes a mechanism for Extending ICMP for Interface and
   Next-Hop Identification, which allows providing additional
   information in an ICMP error that helps identify interfaces
   participating in the path.  This is especially useful in environments
   where a given interface may not have a unique IP address to respond
   to, e.g., a traceroute.

   This document introduces a similar ICMP extension for Node
   Identification.  It allows providing a unique IP address and/or a
   textual name for the node, in the case where each node may not have a
   unique IP address (e.g., a deployment in which all interfaces have
   IPv6 addresses and all next-hops are IPv6 next-hops, even for IPv4
   routes).

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-intarea-extended-icmp-nodeid-07"/>
        </reference>
      </references>
    </references>
    <?line 458?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>This document is based on <xref target="RFC9229"/>, which was produced by the IETF
Babel working group.</t>
      <t>We are grateful to Joe Abley, Krishnaswamy Ananthamurthy, Vint Cerf, Joe
Clarke, Lorenzo Colitti, Bill Fenner, Tobias Fiebig, John Gilmore, Bob
Hinden, Jen Linkova, David Lamparter, Gyan Mishra, tom petch, Herbie
Robinson, Behcet Sarikaya, David Schinazi, Ole Troan, and Éric Vyncke for
helpful comments and suggestions about this document.</t>
    </section>
    <section numbered="false" anchor="changes">
      <name>Changes</name>
      <t>This section is to be removed before publication, and the primary change log is
the git repository. This is just a place to note some of the more substantive
changes.</t>
      <section numbered="false" anchor="version-07-08">
        <name>Version 07-08</name>
        <ul spacing="normal">
          <li>
            <t>Use ICMPv4 consistently (rather than plain ICMP).</t>
          </li>
          <li>
            <t>Clarify that the requirements about ICMPv4 merely rephrase what is
already required by RFC 1812.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-06-07">
        <name>Version 06-07</name>
        <ul spacing="normal">
          <li>
            <t>Made the reference to RFC 7600 informative.</t>
          </li>
          <li>
            <t>Downgraded the suggestion to assign an IPv4 address from <bcp14>SHOULD</bcp14> to <bcp14>MAY</bcp14>.</t>
          </li>
          <li>
            <t>Changed the first author's affiliation (but don't get used to it,
they'll likely rename us again).</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-05-06">
        <name>Version 05-06</name>
        <ul spacing="normal">
          <li>
            <t>Rewrote abstract.</t>
          </li>
          <li>
            <t>Added RFC 7942 boilerplate.</t>
          </li>
          <li>
            <t>Added positive factors to Operational Considerations.</t>
          </li>
          <li>
            <t>Editorial changes.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-04-05">
        <name>Version 04-05</name>
        <ul spacing="normal">
          <li>
            <t>Minor editorial changes.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-03-04">
        <name>Version 03-04</name>
        <ul spacing="normal">
          <li>
            <t>Added a section about operational considerations.</t>
          </li>
          <li>
            <t>Made it clear that ARP/ND are not necessarily used.</t>
          </li>
          <li>
            <t>Removed any mention of v4-only, since it's not quite correct that
v4-via-v6 is v4-only.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-02-03">
        <name>Version 02-03</name>
        <ul spacing="normal">
          <li>
            <t>Warren is a smart guy, but he still pushed a branch instead of the main
one, so -03 is actually what -02 should have been.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-01-02">
        <name>Version 01-02</name>
        <ul spacing="normal">
          <li>
            <t>Addressed comments from Vint and Jen.</t>
          </li>
        </ul>
      </section>
      <section numbered="false" anchor="version-00-01">
        <name>Version 00-01</name>
        <ul spacing="normal">
          <li>
            <t>Added note that this works just as well for IPv6 routes with an IPv4 next
hop. (Éric Vyncke)</t>
          </li>
          <li>
            <t>Cisco NX-OS has supported v4-via-v6 routes "for more than 8 years"
(Krishnaswamy Ananthamurthy)</t>
          </li>
          <li>
            <t>Mention recursive next hops, and that the next hop may be a prefix.
(Krishnaswamy Ananthamurthy)</t>
          </li>
          <li>
            <t>Hosts are routers too! (David Lamparter)</t>
          </li>
          <li>
            <t>Removed the claim that it's mainly a UI issue.</t>
          </li>
        </ul>
      </section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61823IbR5PmfT1FDT0bJh0ACIDgCZ71mOLBokekNCRt/w6v
YqOBLgA1bHTDfSAFK/Tfz1vs7bzBXK9fbL7MrKpuHCjbu6OwpUajuyorMyvz
y0Oh3W6r0paJGeqd63dPA51nVWkK/WzLmY5SjXtHOjUfSj3LFjsqGo1y84Rn
nwbtJxu1n4521DgqzTTLl0NdlLEqqtHcFoXN0nK5wKjXlw9Xyi7yoS7zqij7
3e5pt69UnI3TaI7v4zyalG1ryknbpmWUGwzqx253TxUmO1B0mwhMS5OnptxR
z1n+OAWpi8ZdfYan9E/4xqZT/R19u6MezRLPxqDDPdW+oAnVk0krM1Ra/6lR
tJbF7Gzcn0c2wX2Q3iYiv6WFdLJ8St9F+XiG72ZluSiG+/v0KN2yT6bjH9un
G/ujPHsuzL4fZJ9enkIA1QivPz9W8yi3+8Ko8SzPRtn4N/O4yS56LYEwirIx
q3u9I+N1bPYnBtr/nFA6s3Ke7CgVVeUsy8HCNqbVelIliUj0+yqxVfGbPg8z
8ANYbZTa36ISqgFx3F1ftfQPKZiRF7b8/T/0O1BZtM/pmp8vytyYcsjXbX0e
FUYfd3sD9/n4sN89lHf0uYnNB907cF9d5VE6NvzBiHj+bTz71uZ20pnkytMr
tP4U5blJ9b8wj/i+TQvc7jRvrVL+XZZNE9PSb96cN+d45pG+ddyGIq3N9JA9
Gv369/+EDqRx+/vf/zOfmrQw6ZYZ7kysX0dlc/QSb39Lf3XiR6XSLJ/j2SdW
4Lur895Jrz9UyqaTtS+6x6d9f3nSP/KP90577nJw0q8vj/zlYa/f9ZcH3RN/
eXJQX5706ssDd3k86A785VHXj3BycnrqL08P/d3Tfp/vXrcvOlu0DQbHpLGJ
23Y8X7TTLDY2xgpVu93W0QiqEY3B4B+9TrLVon0JbYh0acaz1P5aGV3OolJX
BexZsGNt2DEdxXFuCroPjin8D+nF9D6bwEU0fjRl0YL9izFEVWCXP+JZW+pF
BtM2SjByJpZy5Q0VjXM8ABIgfzJR+nlmcqOLbG7k8bzQs+jJ6DQr9chA8yKM
N00hcB4n0NVRDzOsBVaympu01LEpxrkdgYin9TULmbGZ2BRf54YsQKyzhclZ
naJELfJsbOIKI7do4miULLEsA62zU5vyUzqb6Ovzm8Za9Gipie+FMHFup7NS
EdlMv3iGQHBHJDO3cZwYpb4ga5tncTWmsSG2B8wWZ3NMhrWQktJ8QWYpUxMM
MNYdBBXWyIxUUXgJayqzcZbocZZCHTATsd1/S2s0ejfLG5O4vQF6RrAlLX13
/WoPw9rxjGaEksS05Eg3tIEZB3lC2O6u505Ha6xJrc7HyhdHZaSFInDcMS9a
FEElFjlE9YHUCdKHmYcnUpNobiGUXeYpqCZt3aNpveeF5BaRhfaAb+A9pp1m
siwwbRKNSSKxIr2DnEZZ/mU9nxNRi5agzYdovoCzh0y0+wMRl14Ltv7xNLg3
4MF7w3h0MuwOe8Ph/tFg7XFTzrqYzJx0h8Ne/2AwPDw6PgnvHnS6nV4Pf+/3
118M7/ZO+3iq3+kp9dOM9ojjOjHYyQHCisbjTMQEPjlGrikAdk6+bJF2Nff4
AhbYkEO34ygB11k6pIHr5kEGTmz62E6ipcmVv78b6Z2bs3P/3M4eaU5V0OAQ
jn8Kf2VJxXwN2rpL9sYJgee8dQLTF7YYZ3CGy8bDtxd7+hdnmt/7fTImT5hN
FFs0ekNf4jbtHG+wjD5zJNzVJLwLo57dvZNhySW8V6vDyrZeGXZPlL3BiLBE
y4xLefcocCtsRh6y8cIkhxN0psSkY3C8IjvVEKffWEpds6CjxQKegMxFns15
OLGBC15NNAKJMlzJJpaMBnZplcYRGUxYPbiRAk8+z5b+7aDmsgUDtzbkXsyy
KoE5wLCpoicKDBq+lc06bE5czsRcGOhg6dSA5eMUl9agRoa+qVdcAh9V0xl7
C9lhTdQdbKvetamzUywj0mb/ArZ5Qw/xepI0FBv0Z6MysuReRDtJ9C0YmJaC
pAh5mWTZChM2iNV/nlhRxBeIhctkokAKb4enQAp0G3q1e52Cn2Oori0VWEkM
XHGyRZnl21QPyhTb3IxLrNNpsBej4m1Pukx3VyxCS9x59JRZsRx4oBK937px
VdiLUVJmU0Mib7n1PUcF9H0+z1KQEGcpKYs3uoVbJI3/9v66HqaobGk6e2rN
vU9wQUvKZCXFwoztxI7DpvSLaIINLxK1HqXxdsXoIoACz+elHWO/5cwrOAze
CnCqoHHMMmJ8o9bwzaiy2ARhRbzZHHhZQytwK2OzKLXsRmXiKe7R7sI8ED5W
/2RjB5WgeCnEZp9suaRZ6GFQXZBPvWYZWOJ8Swlx64vDqtjcBMOcQddrg000
kvGoyizN5llVJEtS9YmdwhnHrabAiwpCdNGuSUk7yH3PAXno24CfHISTXSce
dUwqOYvY4hQlnpLt1oByDdZgLGNJb5zdaClRH3qWZAxEhHdBXDU24oYi0A2d
wIvzKK0ihji8AKEnN79W0Py4o3bvDZ5OioytOaHv9+zkAULgTCoOwv02QEhe
MeZ4kk3Im5dZgB0MW5tn0XhGinnmcG2Z0c4vauMgNrNG1BuSYZVLEkM4pJEf
kPGglD/NLBRrA786Y5+AFaR4IxhT0gtWCcUmOvPYmeT3wrax2BCWvCpbf2aU
Tf17HXWGCZY02eb0fi4xVI67mmyV38HMO2IkPadWpLGCqggFSOBCbzqpX7w+
d6COr45ovkU1Smzhd+6AwHtUJaXj/NbUC/zix48uhPr0yQuYxBDDjpeWzY13
37dOUd+wxbwzEG00sgl2nLqucTDwxZu76z033xb0Q6IemSRLpwyFGKSDpmDN
WjARpWhnyuER3MlE+PkskmKVyHNLcA2S9LTio9hs9eq7dwHvdPSKUWx5a5gx
H2cYoNVYN2OWLGW7AzS0KlfW9NgsKIbk/cUGflkb1vUwgi2DzRVQAvYlE9uI
oBjXwILJ56LGWaRx0Fu+S3MEqz8neelL2DIIHviAPE8mXnCe0f4bmQlZEdYE
GWBt+cS7mYmeKC6ggCVWYEcjUh5FEE37aYBVPx11NAPll74mX6UkYPB+/Pry
/jt42wgrdzmQPGLBME/z1ImfIlcBNyRP1cBXBKhMTkuRhXm6RbYIgQz8TkQL
h4nEWwl5yFq2RabEWJds0THAnPhBWaRlkHLMnG7JV+B1lpdsLltg4wRWGZTG
apyYKK1RwKSiuKvzSVEYek4oJxXxkMwuKEpm/1JIUPpolprygwUA/Q/3Dzst
+VffvuXru8t//eH67vKCru9fn715Ey6Ue+L+9dsf3lzUV/Wb529vbi5vL+Rl
3NUrtxQCiJ93RJN23r57uH57e/ZmRxbR1IIoN47B7LlhhYnDEKfPCDC7X52/
+7//pzfQHz/+A2xEv9c7hY2QDye94wE+wIulMhvjFfkIfi3J+JsoZ6HB/gGa
W0iXdJxx8HOqyf9Bnb/6hTjzfqj/aTRe9AbfuBu04JWbnmcrN5lnm3c2XhYm
brm1ZZrAzZX7a5xepffs55XPnu+Nm//0z4AVRrd7J//8DavQW28GlLpdy0rQ
Fg0+R9IHsLtB8wkdLqD1aVm0mlC0ASqdGVkPTluy+QhdVimZB9PA38UMOhGr
1TzDygSCdSGyL77Q9yETsQ0Pyyb4K1kM7xxCFqPM1LYkhVvWnAICl6Jo+ZcJ
+APqlXkkWA/B2mbCZ4NWmb+BRXhyuVFTwIhBQq/Vh2pXSsmbn8jnbUmlNcUU
2OGTkTBawok1TDSPOInAaFacvvfeBMY4QBo0HXkjKqdX2SuMq7ygvG2IZBhS
0dfOrY4I8jZAmHJIBfFolfOkjXwDKHEEsQPdmi3Sb/o+oQGGbKZS48xwaOvD
2prIxkyiZGGPNCS/otCiZxs5GEkfcICyrp5rWM4Be2U+gAjaawy7JF0iUasY
yRCwYklnRZ05IhDyZIoXckHk3oG/im0BI5hvJLlIvt0nlRQg1HjmAaJMIubV
DV40vgibtykMVQvDiQnxQza2nL1dx2Jg8+c0djUz4Vm5Aeg4VaEIz0FbYjiS
fM65gdHyM6OIyg1drLi5P7zyr8cJa3thIHthdSe+II55VZSs7y4QDaQyJIRM
Td52nAUysoWLyNVnE29nd+9YaYiWlr698B8kz+o0YIs6ryPFYtVmhgn+P3Q5
KpYpleNSjlfrhNemWyAFe0YUQmOLbYL5lTh90/5rfc8y2x5x6alJsczEVZ0I
QzcM8pYMfD0MATbWXoHILmIxHyynFdQGx4ZUk2mMvcG7BdcKOP7+nFPwW9Ln
lxg2hsR9us7noloQYiSSNlgAQb/OnsmAtAj5AAFCU6EHlSTYQhoC1E4SrEyi
J5/J4AnDmCqwaGPlYGMAyMGLMLd4EjcqZLjIFpIQ3XR7z5sbn+rznBhfyxRC
qchgR09UaaZ3oeL8IM8W7q4lbwhi0muUm+LvKUfNKZaike4Dx+6pjFWvLUpy
E8VLz2fHNxfhMXj18ehqT4FaswFQ0qRiLX9FQYvmOJfqg4CtpPAUIzZiX+j1
WzIsqkGJn1WyB7K+DRzASe1gxn2lRHmzy9E8BbSEilkRCL8lsD3YkwHTMTDi
3VgEc8K1F5rLleIyZmfQxs0NKAn1oslMYQIVZrT+St/AFlnKKFynFD1hE9/V
xbK39++ung70LvOEirKfPu21+DUqoU1z9iCN56/v29f3/vGDLj/OJIeZ2g/Z
Ikuy6VLv3jzsvfhurw/274mN5GpdNJYMGcn11dWFK9e8spKZle1zVRuxC/BS
3tjF03uh7EZoJUs5VJaywZMhEF4UisL2dd1vSQTDOX0SRjCXLG0MDGFJ6qtO
4/M0pNY2XVSld7ibhtEV/DqM/KkeShFkI/LXH78ozJiL0p/ED4SqJR4sYZT1
Dd6PpqZRb6FxXMHl+LT/Xqyvl7zyBVsPZX0Kc5Fb6iRIloFHlEmh2Diaphks
7djVfUfVdCp4ImR2HMDdCCafTTBw5FH1jpR8dzjFRhE1mSK6RwB9tRrsgKov
GYsJhD1zubNd05l2xJ3vNCstVZpL9onsNluJxp2d1Un2GtsP0ynObG7MyY5n
bmICSqGm7qafgxaXLnq0aUyByIvk7Pil7W1attgskmwZslS1kHOyBRhnjTkF
MXe0VNtoAytviCxXeKcQCbvl5uGHRsVv9x0+x6Ij1JzxnkohVJBIplh8OZvr
gBVWuE7YyA3CdM6jD3ZezT3sLOxvRrIskcxKozpMxcoUkrJSymIPrp+gdRFi
VrLeTJeEGxFnq5gBIKBdZm2i4xfXQ/Ker6jV471AUjeKiMSXSdSLjJ2xr5lR
hd2n7cZbOK3+WBeG2k62KwmtoEodA1RB5K+O3nLrJV1P4No4VUvtSUXJAk7w
GPBI0ki1EmaaTOy4ExLnucBX5iin+BpAViAXNY3IvBcN1fyhVk01FxtCheYi
5Ptpwb+4Zp/3+t5Z0sNOv3Pc6fkabZFV+ThAeSVAFFs+jOixNWXjHExtIAFf
wVgLHOtY5WviLpU9uHLgYAcJb6WZpSVV4cYcvCnVyzMJ61r6MaWMUyRYekfu
tm280wqEc6l5d5MRg84BWDGg3XznBB48sI/T5gYMTm0x1yvZs1Uj6dw3ITcq
abt2l+UGamqsgL6Whdq8DrJdnjiQqkJELWloysJxSW0BhS8cY8OSN7lKRnni
WmAogPOj/RGFrQaHNafswEMua8fVfL4MYpS2i27nxPN/VZm4KuYzCWvbcjf0
0RBmgkIH4PqLawaDWaglddLSd6LVzPG7dr9Pcvsh1ExXCVslZ71TCaZM6lE6
reYjLBFGP86j5xG+LRyeqquxK5V8SsB4pOWtBG3+WTRfcIjsfKtDS1pLmcYi
vHR4UfzOs/RA+Dm+ovY0wwNi6lJA/i75tsJIX+LHj3+h7w0wWKp6oTgbytM0
Fu8gBgwZvpvvfc0r9q4p9HhRNZ+QUi1lbumiLeWrGxyKQjmzbGJkvc66CdJA
uLcQMzSB5J6jhJB3GfqMRhkVB3JLzWvqSrAcBarchoG9wKV9O9FBgcFiQixb
Wto4zE8S1dxKttQ3Zz+zNfU7j+1LLtWB9fY5wm+r4eA9/q0Qve9CI11lZggk
b6LCV2WEj4VT0y0Vmj28/dB8BjA387megscn9RQjthqNFnU+xQE/6dhz2Rca
09WmhFoppevSzlnjnwEDQq8fHuaKEBigGElCMaQgU9s0WuTx6aDv/EKzdwbD
rdPGbS6NdVFiO3XhKtm3gnygeOzLhysan+qtMQguXJZlLDbHcsvElKTAOUTS
cMYpoIeg0DvhN1XEQvcOAH9ROp8KMwapxxZRNlW+1yJ6RinB7tGXDEay3MWb
LpFFNHbUlaRFSTuo7VGbyYTwZzCr4HfKoQDQExljruc1qqOIGwvO6yvXAABq
qeeDwt3EiuCYG2NC/hbbO8sL33thHYmeiZE4A8VeTJo/fbOUTxDgAZiyMkIc
xpwI4fqGIuVKPM3ERJSdp0nvAFc8xkE0bF3IUPNZUPHaUIqMHaM+Um1EdWc5
riN9+fYeeEauZ27J4B1lwLndYTOqX02wu2QhhmnDLXc7PYkZSRElxF9PlGA2
Zhhxijq71gv967VQMhAuSaB209//w7xY+tzzxVrqHaxSF5WSQbbNdY1oYLwW
g9J3UcG3TJI9c/qfWrAF4zu0wo9y6z8tgtQXSE06+2NFLv0PO/7nxXSfR9n/
1/LKHlwNHq4mV8eTv/0teXx9v7hMq4fB4Od9asdIG8zWrr+4nOXGuO7cmv2N
nhNg7aF0eP6jtgv3MlXzdK/L1r/PX/oPGqyCrpryyPVt9ntHwwNsmOHEdLvD
Hnb6k04+jEd5V0TmOIB5bPqo1GtskC8LLvvbEhdQ4WmTqY4WP93+QV98kXzu
7neBzLCFxvrgZKB38dcehaPuXv/kRFtxR93+kAkbMmXD02h4aIb9PmTzKzb4
wdGgf6gJ4end/uHhnqYwvHfIi3PEc9JHPPnWde5ayrdQDwu1aAUvLiE7tKZM
eNtO2NcHDtfufpW9jftgWWD2rr+Cbh50ZcMgcmvpoy5YVpqAqrgltqcbLns3
XO5p4t7xqYb/pKtefTXAlbzb/9y7g65/o3/grwb98O7B59496vk3DrorV/Lu
QG9brbwZnq/nPyDase8QfF1oaTYj16h3YbnSR3YfdHpiz6vR6fDwZDg47gy6
/ZPjHrVbEXm9oxOa5rgDtDk40t8EEjr9/lBfJdG00L903rf+l5wuMb/qg4Nh
b3DSg4UYP+IDcBwc22G339LZQkztL2m2aNH/D/eIaBN92js+OBwcHndlEDPO
de9kcHp6PDhC1N5C1JhOsR17g8HJFlIHf4nUdyu0EqHD3uHB8X8/tYdHG7Se
do88raIA36zQPZTcWJCxjN9IrrRD4nuSR1O9Oy8rrKDf3asn3TYrlPj6XZMZ
a/MKvzaFucqR05c5EpbvaSaeODYdnbb800U0xr77GHj+qWZWd5Pqg78mV1Ct
13Sw+/+kg3qLWPsNJTw4OqFjGf48lmIf/Mam1Qel+J81375RYxAv/kgZmkTz
OS1JOFD7DeM4RqB92J529xj/sZf/Ql+GMwZ///vfVU6DYFGx/rv+QsEZteHM
YE19k3//gNxB7YDC8YJh/2DQV6vvszPTxerLqv704jjswZ6TxcFRgScPmTJi
x419hD+zj1pyBoR7Nm79OTbtwu8TU8o9zyp13On1RqaMsIqPjVYw7J4v567i
ArjGwaOvoRDAhB+nYP9a00k+47ALtOLH9WFdNFCyzeQHDWFdCjSvCb5YU/fI
b8AfLEox9HPF9IjKalQ1vP6Smshzbs6dEN+xSiHSNun7tCJskfUv7rDhtxcV
fGjRPj+/e6/37WKfOfUN5bTTUvE+GOoL3dYXP9+e3Vyffw162/r69uz84frH
y5Y+wye5/lqP6fDf29vby/OHFiTf1vcPZw/X5y0V6zZ1VLb0E27++O72a/0a
F69/ar+9unrz9uzi8kKdI06e03m+i/uH9tnFxd3l/X1Lf3f2cPnT2c8tfXGN
sW7PLxEr8p/GU+48int0+7kY9yeM0uWWg6Cb9QkXhzWgj4djxhojwjGDo//R
+9/n2XwMnQmD9YJmnlNiV9/+rU062fjwR9q4M/EhMXlPfaKXJsoLOhoKU/Av
wPSzNCqeo/lSn9FprFk0pzhpudLqBCuzWvfYdtQunImD0i+bR6SkjOEzB4JY
60heNfvIP38ILvRZukzqTBJBapFRPtaCSq5bUOlYGh58/mc9E8bV/blrQgXe
MtxmqApu33Sh3zxKgRd92TLOKnJjAIMwy74FPlTUqVEe+NW6g4WDUPKm6Zgy
BCosiAmA+o6mlsoVjE7P1oGoKXW14BMQboV6ZYVFQokaajAfj2F3c18mlmR6
o9B6BAP8PQWYiX2UjKBEfZxUKlxfEHTCV+rloCQX/loE3l05vNFaRGB6Ki1U
4SXEyHkUWsPAk8snrjBzh8u6OnLZAHymOIhsWKOlLNMv9huw6J055RZU5eqD
LhfXFFaZUcWGe7ddXO2z7aFh0jXkXqzwa0tXRNo4uBlYUMphCY7eg1ioKreI
o5C1IIvJdPChB860+HOTUWpdad81isM9KVlkZ9u2Muk4q3LO1ctphIT1sab9
hSOlasupjIZguKq2bYeSUoeTEDmlBB5NI/PZLOFL6wifI6DpOXvNlia2NFKV
lFKCU/6Q6YgKeY8+LYoRqPjq8mBbk6QJdzHUx5gV2zD2cFTJZXV+5jo/HG6B
GPjjx1CP/bTnddGGTJs79rraLPtXk6+kwr5wpSQz2Tg8QqcSsoTaR5zb50zf
yuq2KKdaUc5mu8lqGfc2HOKE3lg690xZJpe6fYb9phIFd6Xw/l5TAEesV5Nm
o0uwfUHU0MYHbPOUQcmCe3vcPvN9KqTcNJH7SPbNbxfpBAJpLbWeruKKQ90M
IY1NSZI9k16MDHTX4j2gxV4ndB48MJvujMvBuXPx0uNui0USLb1SrZ/4pYwo
lRvpkD138tZtdgxyGpbDJ5/2WqtNl9QnsNF1EOpP5gO1/Fuyx9IeHdVHYUK3
3vU2HlBnclSWZr7gRFKxTClDbn+jxk4peJDnjjjJzl5lo4GPOO7WT7XYRSZO
shB8Rw1R8ElcuQzyUNgAzJ+cPRpIzlz/E9j989ntd/qCmihu2NA0mjqGlC+n
fH4cWMxPs0UqsPm4AEgzg4iQy3aJ55ODAYKwnbONCWgBXsY3QRI7lO5xoq6b
iTmzhQEpvUpnGPPaeXCLHyWHXOquPnDlmhcpDZspD6o3bT207StOR64q65eF
UEx9JXLwkAUXkbau6ogcGKwzc4BXcuqQtmNmJVUYkQebsMFbLoz+0i6ejtqO
0C87oOB6stm2BhpkafAjcFsRxXw2Dilp6sSl/f+BfZIr82pZtpVD5YUXXOAc
KUk1dV3qMiylkbUcnkNoZBt6itF8xwy7/aDuwoZmD2fbHwP15fymp6DZ8Qz1
0gBb3lPzMFmNdWD5wM0o7gcbis8VZtkzBfTJp0W4NY8PXqnIm5RmblqM4yKa
RnXyNApVDu4u8hbMwdJCcXfRBixtpFd9jv+FHkH5pQSbOrmZhteSWhhbKoxd
zV2EP49iPjvmSFGrxj70O7ILbEIQLnzSaoSz4ppd8c0dSWtxxY0KOgmf/RBv
3uY1Sg8JV32kuS1e6aUaqNCdAdq8D/lL6H37ipz3CsxYCjMaBaF1GuGBVSO7
tEpmaCIJcgms5UpZnj0GTNDo0MnrNX2mU88zX0hmDaRh1gn8E6RdT3RZV4b4
oFnujyQbf4B5i7MXxzOxCZVMM+mP0lUa3vcdKOH803o3NfXJNBshQpunP+7N
Q3PjbpX40unZ7dnGTr3N5L44CKk1EUyWLIUvY/rt6n4ShKrwNOLZmKqiiYnZ
DBXq41CiNRP/z51JlBRm59P6oehGmbPZE9o8f+0ah+Nm5U9JienZ/VIT/74T
9c8bJpjbIxH+kWn4PjP6DJxA9PNyYNzSP5I5PweIaNEb6hyhzCP9/g8sUPpb
BjZRYcC29CuCeVcmTSmKeshGFgReWTOyU3pxlurvbCLVyFfZSL2mA4opvoHw
39j0MXuKWnCVTzbWb7B1o5z7Yb5bYvPegLY8ohOEc70w5XjW0q9NPrJG3WGW
tKBGhFdmNoYw76PcPkbLMNQ9HVKIfgN1byHxhzyL3Cmw3/+dais/LlPoACOe
mUkWxBcCT+xjOJQBNKT4h8U9Eu1blfEX+lxixM9ItFFV/qNDkPXRSul/XLoQ
lEpK1N5M30wtGQ+AH4oIl51QcP032ijcnCtnKrj4yXGSCznYZxTViBwkRxcu
vJXqpEuvaUplnmxfzVf6hyI0b3HXBHeG0S+3QK1m3IUHeYECK51re+TlSWEk
y+DMW173vni2ujHnhhvssDoIvDDSIGTJwftm62Y3GEEt6ixao/+o3T1+if4b
cjVCgztA6Yrzmpp0mqEXUX4BfIsNI7//YBra4JsCpps96GwA3Zk9PHVz9jPz
gDntTrvZnATFPx8GtEPWK7HuRDLlLmOAoFJPTRlAiC2pv5lCWMpNUnaDmUQ/
rKXp5xym4PdeR62y4bDdPXqJDXfmOSft8D8lRSSeUVoz9E3oUWYTRGgUudff
stLRCSj6zQoKxEDcy1kzek/yvpTJqZVthcxBu3v4orRsSq58yxDNEQ7a3cFL
IwjZNeQRbXv5aHPH6widy03oXChr7dndu/3bi3BSIDXU7lF3J3eYpbKnKe00
lzO3Ls1CfrL+rYkvpTPiV/ohDPolBeoUlw7TJk63hX9zbbH9dvfgpcW6g8xc
rC3mdBBnWi0lH879OfxbFFUxY46M6FfiZvRzbyUHTM5EQJNASEaHbYpMYzIe
DlEHIy7ej+1u37eWMxAiELRGZQ/PfEYkDJDi2tTynmE3Q9bv+43huu1u7/MS
bjbUgGApoopBxCeTJOG405YfeJTDiVg2/3jIbtM17NHe/e9IPu++7GFpjhun
MfUZw8ahUnEJzniunI1sHIrs/PEkrz2YrNFslv2D3l3zunsNbaYZxzDnc9eX
T+pLOkKgVf9wLZi7o/4L5trNFkZTAAA=

-->

</rfc>
