<?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-10" 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-10"/>
    <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="19"/>
    <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>In order for the v4-via-v6 to be safely deployed, implementations should
allow the operator to enable or disable the v4-via-v6 behavior per interface.</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 461?>

<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
3e5pt69UnI3TaI7v4zyalG1ryknbpmWUGwzqx273ugqTHSi6TQSmpclTU+6o
5yx/nILUReOuPsNT+id8Y9Op/o6+3VGPZolnY9Dhnmpf0ITqyaSVGSqt/9Qo
WstidjbuzyOb4D5IbxOR39JCOlk+pe+ifDzDd7OyXBTD/X16lG7ZJ9Pxj+3T
jf1Rnj0XZt8Psk8vTyGAaoTXnx+reZTbfWHUeJZno2z8m3ncZBe9lkAYRdmY
1b3ekfE6NvsTA+1/TiidWTlPdpSKqnKW5WBhG9NqPamSRCT6fZXYqvhNn4cZ
+AGsNkrtb1EJ1YA47q6vWvqHFMzIC1v+/h/6Hags2ud0zc8XZW5MOeTrtj6P
CqOPu72B+3x82O8eyjv63MTmg+4duK+u8igdG/5gRDz/Np59a3M76Uxy5ekV
Wn+K8tyk+l+YR3zfpgVud5q3Vin/LsumiWnpN2/Om3M880jfOm5DkdZmesge
jX79+39CB9K4/f3v/5lPTVqYdMsMdybWr6OyOXqJt7+lvzrxo1Jpls/x7BMr
8N3Vee+k1x8qZdPJ2hfd49O+vzzpH/nHe6c9dzk46deXR/7ysNfv+suD7om/
PDmoL0969eWBuzwedAf+8qjrRzg5OT31l6eH/u5pv893r9sXnS3aBoNj0tjE
bTueL9ppFhsbY4Wq3W7raATViMZg8I9eJ9lq0b6ENkS6NONZan+tjC5nUamr
AvYs2LE27JiO4jg3Bd0HxxT+h/Riep9N4CIaP5qyaMH+xRiiKrDLH/GsLfUi
g2kbJRg5E0u58oaKxjkeAAmQP5ko/TwzudFFNjfyeF7oWfRkdJqVemSgeRHG
m6YQOI8T6OqohxnWAitZzU1a6tgU49yOQMTT+pqFzNhMbIqvc0MWINbZwuSs
TlGiFnk2NnGFkVs0cTRKlliWgdbZqU35KZ1N9PX5TWMterTUxPdCmDi301mp
iGymXzxDILgjkpnbOE6MUl+Qtc2zuBrT2BDbA2aLszkmw1pISWm+ILOUqQkG
GOsOggprZEaqKLyENZXZOEv0OEuhDpiJ2O6/pTUavZvljUnc3gA9I9iSlr67
frWHYe14RjNCSWJacqQb2sCMgzwhbHfXc6ejNdakVudj5YujMtJCETjumBct
iqASixyi+kDqBOnDzMMTqUk0txDKLvMUVJO27tG03vNCcovIQnvAN/Ae004z
WRaYNonGJJFYkd5BTqMs/7Kez4moRUvQ5kM0X8DZQyba/YGIS68FW/94Gtwb
8OC9YTw6GXaHveFw/2iw9rgpZ11MZk66w2GvfzAYHh4dn4R3DzrdTq+Hv/f7
6y+Gd3unfTzV7/SU+mlGe8RxnRjs5ABhReNxJmICnxwj1xQAOydftki7mnt8
AQtsyKHbcZSA6ywd0sB18yADJzZ9bCfR0uTK39+N9M7N2bl/bmePNKcqaHAI
xz+Fv7KkYr4Gbd0le+OEwHPeOoHpC1uMMzjDZePh24s9/Yszze/9PhmTJ8wm
ii0avaEvcZt2jjdYRp85Eu5qEt6FUc/u3smw5BLeq9VhZVuvDLsnyt5gRFii
ZcalvHsUuBU2Iw/ZeGGSwwk6U2LSMThekZ1qiNNvLKWuWdDRYgFPQOYiz+Y8
nNjABa8mGoFEGa5kE0tGA7u0SuOIDCasHtxIgSefZ0v/dlBz2YKBWxtyL2ZZ
lcAcYNhU0RMFBg3fymYdNicuZ2IuDHSwdGrA8nGKS2tQI0Pf1CsugY+q6Yy9
heywJuoOtlXv2tTZKZYRabN/Adu8oYd4PUkaig36s1EZWXIvop0k+hYMTEtB
UoS8TLJshQkbxOo/T6wo4gvEwmUyUSCFt8NTIAW6Db3avU7BzzFU15YKrCQG
rjjZoszybaoHZYptbsYl1uk02ItR8bYnXaa7KxahJe48esqsWA48UIneb924
KuzFKCmzqSGRt9z6nqMC+j6fZylIiLOUlMUb3cItksZ/e39dD1NUtjSdPbXm
3ie4oCVlspJiYcZ2YsdhU/pFNMGGF4laj9J4u2J0EUCB5/PSjrHfcuYVHAZv
BThV0DhmGTG+UWv4ZlRZbIKwIt5sDrysoRW4lbFZlFp2ozLxFPdod2EeCB+r
f7Kxg0pQvBRis0+2XNIs9DCoLsinXrMMLHG+pYS49cVhVWxugmHOoOu1wSYa
yXhUZZZm86wqkiWp+sRO4YzjVlPgRQUhumjXpKQd5L7ngDz0bcBPDsLJrhOP
OiaVnEVscYoST8l2a0C5BmswlrGkN85utJSoDz1LMgYiwrsgrhobcUMR6IZO
4MV5lFYRQxxegNCTm18raH7cUbv3Bk8nRcbWnND3e3byACFwJhUH4X4bICSv
GHM8ySbkzcsswA6Grc2zaDwjxTxzuLbMaOcXtXEQm1kj6g3JsMoliSEc0sgP
yHhQyp9mFoq1gV+dsU/AClK8EYwp6QWrhGITnXnsTPJ7YdtYbAhLXpWtPzPK
pv69jjrDBEuabHN6P5cYKsddTbbK72DmHTGSnlMr0lhBVYQCJHChN53UL16f
O1DHV0c036IaJbbwO3dA4D2qktJxfmvqBX7x40cXQn365AVMYohhx0vL5sa7
71unqG/YYt4ZiDYa2QQ7Tl3XOBj44s3d9Z6bbwv6IVGPTJKlU4ZCDNJBU7Bm
LZiIUrQz5fAI7mQi/HwWSbFK5LkluAZJelrxUWy2evXdu4B3OnrFKLa8NcyY
jzMM0GqsmzFLlrLdARpalStremwWFEPy/mIDv6wN63oYwZbB5gooAfuSiW1E
UIxrYMHkc1HjLNI46C3fpTmC1Z+TvPQlbBkED3xAnicTLzjPaP+NzISsCGuC
DLC2fOLdzERPFBdQwBIrsKMRKY8iiKb9NMCqn446moHyS1+Tr1ISMHg/fn15
/x28bYSVuxxIHrFgmKd56sRPkauAG5KnauArAlQmp6XIwjzdIluEQAZ+J6KF
w0TirYQ8ZC3bIlNirEu26BhgTvygLNIySDlmTrfkK/A6y0s2ly2wcQKrDEpj
NU5MlNYoYFJR3NX5pCgMPSeUk4p4SGYXFCWzfykkKH00S035wQKA/of7h52W
/Ktv3/L13eW//nB9d3lB1/evz968CRfKPXH/+u0Pby7qq/rN87c3N5e3F/Iy
7uqVWwoBxM87okk7b989XL+9PXuzI4toakGUG8dg9tywwsRhiNNnBJjdr87f
/d//0xvojx//ATai3+udwkbIh5Pe8QAf4MVSmY3xinwEv5Zk/E2Us9Bg/wDN
LaRLOs44+DnV5P+gzl/9Qpx5P9T/NBoveoNv3A1a8MpNz7OVm8yzzTsbLwsT
t9zaMk3g5sr9NU6v0nv288pnz/fGzX/6Z8AKo9u9k3/+hlXorTcDSt2uZSVo
iwafI+kD2N2g+YQOF9D6tCxaTSjaAJXOjKwHpy3ZfIQuq5TMg2ng72IGnYjV
ap5hZQLBuhDZF1/o+5CJ2IaHZRP8lSyGdw4hi1FmaluSwi1rTgGBS1G0/MsE
/AH1yjwSrIdgbTPhs0GrzN/AIjy53KgpYMQgodfqQ7UrpeTNT+TztqTSmmIK
7PDJSBgt4cQaJppHnERgNCtO33tvAmMcIA2ajrwRldOr7BXGVV5Q3jZEMgyp
6GvnVkcEeRsgTDmkgni0ynnSRr4BlDiC2IFuzRbpN32f0ABDNlOpcWY4tPVh
bU1kYyZRsrBHGpJfUWjRs40cjKQPOEBZV881LOeAvTIfQATtNYZdki6RqFWM
ZAhYsaSzos4cEQh5MsULuSBy78BfxbaAEcw3klwk3+6TSgoQajzzAFEmEfPq
Bi8aX4TN2xSGqoXhxIT4IRtbzt6uYzGw+XMau5qZ8KzcAHScqlCE56AtMRxJ
PufcwGj5mVFE5YYuVtzcH1751+OEtb0wkL2wuhNfEMe8KkrWdxeIBlIZEkKm
Jm87zgIZ2cJF5Oqzibezu3esNERLS99e+A+SZ3UasEWd15FisWozwwT/H7oc
FcuUynEpx6t1wmvTLZCCPSMKobHFNsH8Spy+af+1vmeZbY+49NSkWGbiqk6E
oRsGeUsGvh6GABtrr0BkF7GYD5bTCmqDY0OqyTTG3uDdgmsFHH9/zin4Lenz
SwwbQ+I+XedzUS0IMRJJGyyAoF9nz2RAWoR8gAChqdCDShJsIQ0BaicJVibR
k89k8IRhTBVYtLFysDEA5OBFmFs8iRsVMlxkC0mIbrq9582NT/V5ToyvZQqh
VGSwoyeqNNO7UHF+kGcLd9eSNwQx6TXKTfH3lKPmFEvRSPeBY/dUxqrXFiW5
ieKl57Pjm4vwGLz6eHS1p0Ct2QAoaVKxlr+ioEVznEv1QcBWUniKERuxL/T6
LRkW1aDEzyrZA1nfBg7gpHYw475SorzZ5WieAlpCxawIhN8S2B7syYDpGBjx
biyCOeHaC83lSnEZszNo4+YGlIR60WSmMIEKM1p/pW9giyxlFK5Tip6wie/q
Ytnb+3dXTwd6l3lCRdlPn/Za/BqV0KY5e5DG89f37et7//hBlx9nksNM7Yds
kSXZdKl3bx72Xny31wf798RGcrUuGkuGjOT66urClWteWcnMyva5qo3YBXgp
b+zi6b1QdiO0kqUcKkvZ4MkQCC8KRWH7uu63JILhnD4JI5hLljYGhrAk9VWn
8XkaUmubLqrSO9xNw+gKfh1G/lQPpQiyEfnrj18UZsxF6U/iB0LVEg+WMMr6
Bu9HU9Oot9A4ruByfNp/L9bXS175gq2Hsj6FucgtdRIky8AjyqRQbBxN0wyW
duzqvqNqOhU8ETI7DuBuBJPPJhg48qh6R0q+O5xio4iaTBHdI4C+Wg12QNWX
jMUEwp653Nmu6Uw74s53mpWWKs0l+0R2m61E487O6iR7je2H6RRnNjfmZMcz
NzEBpVBTd9PPQYtLFz3aNKZA5EVydvzS9jYtW2wWSbYMWapayDnZAoyzxpyC
mDtaqm20gZU3RJYrvFOIhN1y8/BDo+K3+w6fY9ERas54T6UQKkgkUyy+nM11
wAorXCds5AZhOufRBzuv5h52FvY3I1mWSGalUR2mYmUKSVkpZbEH10/Quggx
K1lvpkvCjYizVcwAENAuszbR8YvrIXnPV9Tq8V4gqRtFROLLJOpFxs7Y18yo
wu7TduMtnFZ/rAtDbSfblYRWUKWOAaog8ldHb7n1kq4ncG2cqqX2pKJkASd4
DHgkaaRaCTNNJnbcCYnzXOArc5RTfA0gK5CLmkZk3ouGav5Qq6aaiw2hQnMR
8v204F9cs897fe8s6WGn3znu9HyNtsiqfBygvBIgii0fRvTYmrJxDqY2kICv
YKwFjnWs8jVxl8oeXDlwsIOEt9LM0pKqcGMO3pTq5ZmEdS39mFLGKRIsvSN3
2zbeaQXCudS8u8mIQecArBjQbr5zAg8e2MdpcwMGp7aY65Xs2aqRdO6bkBuV
tF27y3IDNTVWQF/LQm1eB9kuTxxIVSGiljQ0ZeG4pLaAwheOsWHJm1wlozxx
LTAUwPnR/ojCVoPDmlN24CGXteNqPl8GMUrbRbdz4vm/qkxcFfOZhLVtuRv6
aAgzQaEDcP3FNYPBLNSSOmnpO9Fq5vhdu98nuf0QaqarhK2Ss96pBFMm9Sid
VvMRlgijH+fR8wjfFg5P1dXYlUo+JWA80vJWgjb/LJovOER2vtWhJa2lTGMR
Xjq8KH7nWXog/BxfUXua4QExdSkgf5d8W2GkL/Hjx7/Q9wYYLFW9UJwN5Wka
i3cQA4YM3833vuYVe9cUeryomk9IqZYyt3TRlvLVDQ5FoZxZNjGyXmfdBGkg
3FuIGZpAcs9RQsi7DH1Go4yKA7ml5jV1JViOAlVuw8Be4NK+neigwGAxIZYt
LW0c5ieJam4lW+qbs5/Zmvqdx/Yll+rAevsc4bfVcPAe/1aI3nehka4yMwSS
N1HhqzLCx8Kp6ZYKzR7efmg+A5ib+VxPweOTeooRW41Gizqf4oCfdOy57AuN
6WpTQq2U0nVp56zxz4ABodcPD3NFCAxQjCShGFKQqW0aLfL4dNB3fqHZO4Ph
1mnjNpfGuiixnbpwlexbQT5QPPblwxWNT/XWGAQXLssyFptjuWViSlLgHCJp
OOMU0ENQ6J3wmypioXsHgL8onU+FGYPUY4somyrfaxE9o5Rg9+hLBiNZ7uJN
l8giGjvqStKipB3U9qjNZEL4M5hV8DvlUADoiYwx1/Ma1VHEjQXn9ZVrAAC1
1PNB4W5iRXDMjTEhf4vtneWF772wjkTPxEicgWIvJs2fvlnKJwjwAExZGSEO
Y06EcH1DkXIlnmZiIsrO06R3gCse4yAati5kqPksqHhtKEXGjlEfqTaiurMc
15G+fHsPPCPXM7dk8I4y4NzusBnVrybYXbIQw7ThlrudnsSMpIgS4q8nSjAb
M4w4RZ1d64X+9VooGQiXJFC76e//YV4sfe75Yi31Dlapi0rJINvmukY0MF6L
Qem7qOBbJsmeOf1PLdiC8R1a4Ue59Z8WQeoLpCad/bEil/6HHf/zYrrPo+z/
a3llD64GD1eTq+PJ3/6WPL6+X1ym1cNg8PM+tWOkDWZr119cznJjXHduzf5G
zwmw9lA6PP9R24V7map5utdl69/nL/0HDVZBV0155Po2+72j4QE2zHBiut1h
Dzv9SScfxqO8KyJzHMA8Nn1U6jU2yJcFl/1tiQuo8LTJVEeLn27/oC++SD53
97tAZthCY31wMtC7+GuPwlF3r39yoq24o25/yIQNmbLhaTQ8NMN+H7L5FRv8
4GjQP9SE8PRu//BwT1MY3jvkxTniOekjnnzrOnct5Vuoh4VatIIXl5AdWlMm
vG0n7OsDh2t3v8rexn2wLDB7119BNw+6smEQubX0URcsK01AVdwS29MNl70b
Lvc0ce/4VMN/0lWvvhrgSt7tf+7dQde/0T/wV4N+ePfgc+8e9fwbB92VK3l3
oLetVt4Mz9fzHxDt2HcIvi60NJuRa9S7sFzpI7sPOj2x59XodHh4Mhwcdwbd
/slxj9qtiLze0QlNc9wB2hwc6W8CCZ1+f6ivkmha6F8671v/S06XmF/1wcGw
NzjpwUKMH/EBOA6O7bDbb+lsIab2lzRbtOj/h3tEtIk+7R0fHA4Oj7syiBnn
uncyOD09Hhwham8hakyn2I69weBkC6mDv0TquxVaidBh7/Dg+L+f2sOjDVpP
u0eeVlGAb1boHkpuLMhYxm8kV9oh8T3Jo6nenZcVVtDv7tWTbpsVSnz9rsmM
tXmFX5vCXOXI6cscCcv3NBNPHJuOTlv+6SIaY999DDz/VDOru0n1wV+TK6jW
azrY/X/SQb1FrP2GEh4cndCxDH8eS7EPfmPT6oNS/M+ab9+oMYgXf6QMTaL5
nJYkHKj9hnEcI9A+bE+7e4z/2Mt/oS/DGYO///3vKqdBsKhY/11/oeCM2nBm
sKa+yb9/QO6gdkDheMGwfzDoq9X32ZnpYvVlVX96cRz2YM/J4uCowJOHTBmx
48Y+wp/ZRy05A8I9G7f+HJt24feJKeWeZ5U67vR6I1NGWMXHRisYds+Xc1dx
AVzj4NHXUAhgwo9TsH+t6SSfcdgFWvHj+rAuGijZZvKDhrAuBZrXBF+sqXvk
N+APFqUY+rliekRlNaoaXn9JTeQ5N+dOiO9YpRBpm/R9WhG2yPoXd9jw24sK
PrRon5/fvdf7drHPnPqGctppqXgfDPWFbuuLn2/Pbq7Pvwa9bX19e3b+cP3j
ZUuf4ZNcf63HdPjv7e3t5flDC5Jv6/uHs4fr85aKdZs6Klv6CTd/fHf7tX6N
i9c/td9eXb15e3ZxeaHOESfP6Tzfxf1D++zi4u7y/r6lvzt7uPzp7OeWvrjG
WLfnl4gV+U/jKXcexT26/VyM+xNG6XLLQdDN+oSLwxrQx8MxY40R4ZjB0f/o
/e/zbD6GzoTBekEzzymxq2//1iadbHz4I23cmfiQmLynPtFLE+UFHQ2FKfgX
YPpZGhXP0Xypz+g01iyaU5y0XGl1gpVZrXtsO2oXzsRB6ZfNI1JSxvCZA0Gs
dSSvmn3knz8EF/osXSZ1JokgtcgoH2tBJdctqHQsDQ8+/7OeCePq/tw1oQJv
GW4zVAW3b7rQbx6lwIu+bBlnFbkxgEGYZd8CHyrq1CgP/GrdwcJBKHnTdEwZ
AhUWxARAfUdTS+UKRqdn60DUlLpa8AkIt0K9ssIioUQNNZiPx7C7uS8TSzK9
UWg9ggH+ngLMxD5KRlCiPk4qFa4vCDrhK/VyUJILfy0C764c3mgtIjA9lRaq
8BJi5DwKrWHgyeUTV5i5w2VdHblsAD5THEQ2rNFSlukX+w1Y9M6ccguqcvVB
l4trCqvMqGLDvdsurvbZ9tAw6RpyL1b4taUrIm0c3AwsKOWwBEfvQSxUlVvE
UchakMVkOvjQA2da/LnJKLWutO8axeGelCySzjr53oOJK37WZEnXQBFNqOTi
CyetjWyAFDkVSOCma+P6ljNuZ5BzDTRzbAvhy8ocI4ONaDPOxdV7tLNtu5t0
nFU51xDklETC+6Tm6QtHXdWW0yINheFq3zbLQZstnNDIKVXxaBoZ2WZrgbS0
8PkGmp6z6mwBY0sjVUkppUHlD7+OqMD46NO1GIGKwi4/tzV5m3B3RX28WrFt
Zc9LFWbeZs/cfwAgUCA2//gx1Ik/7fk9YkMG0B3HXW3i/atJYdpaXi+UZEwb
h1rotESWkGo5OMIZyJXVbdk0amXTNNtgVsvLt+FwKfTZ0nlsyn65lPIz/AqV
Trhbhu3OmgI4Yr2aNBtwgk0OooY2PpAmM1hacM+R2/++f4Y2HU3kPtJW8tvY
b4aipdY3DldC6iYNabiiXUR64TcGFRB6ndAR8cBsujMuN+jO60vvvS0WSbT0
SrV+EpkytVQGpcP/3GFct/8x+GpYNJ8U22utNoNS/8JGN0Soi5kPdBTBkp+Q
tu2oPqITugivt/GAOqajsjTzBSe4imVKmXv7GzWcSiGGEEXEyX/2dhuNhRMx
MLR+qhEvMnHeheBOatSCr+SKapCHwgZg/uTsaUFy5vqywO6fz26/0xfU3HHD
hqbRbDKkPD7VGeLAYn6aLVKBzceFSZoZRIQcu0uInxwMEBzunG1MQAvwMr4J
ktihNJQTdd3kzBk3DEhpXzpbmddOjVsPKWnlUor1QTDXVEnp4Ux5sL/pg6Bt
X3GadFVZvyyEYup3kQORLLja5gcdkYOMdcYQsE9OQ9J2zKykMCPyrBM2eMuF
0V/axdNR2xH6ZQcUXE822+lAgywN/g3uNKJY1MYhVU4dwrT/P7CvdOVnLcu2
cti98IILnCMlqaaue16GpfS2lkN9CNlsQ08xmu/kYTgS1F3Y0Owtbfvjqb7N
oOkpaHY8Qz0+wLz31NRMVmMd8D5wk4z7IYnicwVj9kwBFfMpFm4Z5ANh4pjD
2U0H0sU4LqJpVCd1o1B94a4nb8EcXC4Udz1twOVG2tfXHl7oXZRfcLCpk5tp
eC2p0bGlwtjV3GUe5lHMZ9ocKWrV2Ic+THaBTWjEBVlajXBWXLMrCrqjci2u
BFKhKeEzKeLN27xG6W3hapQ03cUrPV4DFbpGQJv3IX8pqti+Iue9AjOWwoxG
oWqdRnhg1ch6rZIZmluCXAJruYKXZ48BEzQ6h/J6TZ/pIPTMF5JZA2mYdQL/
BGnXE13WFSs+AJf7o9LGH6ze4uzF8UxsQqXcTPq2dJWG931nTDiXtd7lTf07
zQaN0H7qj6Hz0NxQXCW+pHt2e7axU28zuS8OQmpgBN8le+LLq367up8qoe4A
GvFsTNXaxMRshgr1cShRpIn/584kSgqz82n9sHaj/NrsVW2eC3cNzXGzIqmk
9PXsfkGKf3eK+voNE8xtmwhLyTR8nxl9Bk4gKns5YG/pH8mcnwNEtOgNdY4Q
65F+lwgWKP0tA5uoYGFb+hXBvCuTphTdPWQjCwKvrBnZKb04S/V3NpEq6ats
pF7TwckU30D4b2z6mD1FLbjKJxvrN9i6Uc59Ot8tsXlvQFse0cnGOQKIcjxr
6dcmH1mj7jBLWlCDxCszG0OY91FuH6NlGOqeDk9Ev4G6t5D4Q55F7nTa7/9O
NZ8flyl0gBHPzCQL4guBJ/YxHGIBGlJcxuIeifatyvgLfS6x62ck2qh2/9Hh
zPrIp/RlLl1oTKUuarumb6aWjAfAD0Wqy04oBP8bbRRuGpazHlyU5TjJhRzs
M4pqRA6SowsXdkvV1KX9NKVYT7av5iv9QxGayribgzvW6BdloFYz7g6EvECB
lY66PfLypDCS/XDmLa97cjxb3Zhzw41/WB0EXhhpXLLk4H0TeLNLjaAWdTyt
0X/U7h6/RP8NuRqhwR3sdE0DmpqHmqEXUX4BfIsNI79LYRra4JsVppu98WwA
3VlCPHVz9jPzgDntTuHZnATFP2sGtEPWK7HupDTlVGOAoFJPTRlAiC2p75pC
WMqZUtaFmUQ/+KXpZyam4PdeR62y4bDdPXqJDXfmOSft8D9xRSSeUbo19HPo
UWYTRGiUUai/ZaWjk1n0WxoUiIG4l7N59J7koynDVCvbCpmDdvfwRWnZlFz5
liGaIxy0u4OXRhCya8gj2vbykeuO1xE6L5zQeVXW2rO7d/u3F+EEQ2qoDaXu
mu4wS2VPUzpsLmeBXfqH/GT9GxhfSsfGr/QDHfQLD9TBLp2vTZxuC//m2mL7
7e7BS4t1B6y5iFzM6YDQtFpKnp77hvg3MqpixhwZ0a/Xzehn6EoOmJyJgCaB
kIwOARWZxmQ8HKIORly8H9vdvm95ZyBEIGiNyh6e+YxIGCDFtanlPcNuhqzf
9xvDddvd3ucl3Gz0AcFS3BWDiE8mScIxrC0/PCmHJrFs/lGT3aZr2KO9+9+R
FN992cPSHDdOY+qzj43DruISnPFcObPZOKzZ+eNJXnswWaPZLPsHvbvmdfca
2kwzjmHO5+68AKkv6QiBVv3DtWDujvovrDdIFN5TAAA=

-->

</rfc>
