<?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-ek-dtn-ipn-arpa-02" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="IPN dot ARPA">The ipn.arpa Zone and IPN DNS Operations</title>
    <seriesInfo name="Internet-Draft" value="draft-ek-dtn-ipn-arpa-02"/>
    <author fullname="Erik Kline">
      <organization>Aalyria Technologies, LLC</organization>
      <address>
        <email>ek.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area/>
    <workgroup>Delay/Disruption Tolerant Networking</workgroup>
    <keyword>DTN</keyword>
    <keyword>BP</keyword>
    <keyword>IPN</keyword>
    <keyword>DNS</keyword>
    <abstract>
      <?line 70?>

<t>This document requests the creation of ipn.arpa, an infrastructure DNS
namespace for the IPN node identifiers of the Bundle Protocol (BP).
Each Fully Qualified Node Number has a DNS base name of the form
N.A.ipn.arpa, where A is the Allocator Identifier and N is the Node
Number.  A BP Agent can query beneath that name for the records that a
convergence-layer discovery binding specifies, such as SRV or SVCB
records.  These records identify the convergence-layer endpoints,
including relays, that are advertised for reaching a destination.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://ekline.github.io/draft-dtn-ipn-arpa/draft-ek-dtn-ipn-arpa.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ek-dtn-ipn-arpa/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Delay/Disruption Tolerant Networking  mailing list (<eref target="mailto:dtn@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/dtn/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/dtn/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ekline/draft-dtn-ipn-arpa"/>.</t>
    </note>
  </front>
  <middle>
    <?line 81?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The Bundle Protocol (BP) <xref target="RFC9171"/> supports communication in networks
that are subject to delay and disruption.  The ipn URI scheme
<xref target="RFC9758"/> identifies BP nodes and services with numbers.  An
Allocator assigns Node Numbers, and IANA assigns an Allocator
Identifier to each Allocator.  The Allocator Identifier and the Node
Number together form a Fully Qualified Node Number (FQNN).</t>
      <t>A BP Agent can know an IPN destination without knowing a DNS domain
associated with its allocator.  The ipn.arpa namespace provides a
common starting point for discovery and links DNS administration to
allocator assignments.  Each FQNN has one DNS base name,
<tt>N.A.ipn.arpa.</tt> (<xref target="discovery-model"/>).  A BP Agent can query beneath
that name for the records that a convergence-layer (CL) discovery
binding defines.  These records advertise CL endpoints of the
destination node or of a relay that accepts Bundles for onward
forwarding.</t>
      <t>DNS discovery is optional, and it supplies only candidate next hops
(<xref target="discovery-results"/>).  It is not a BP routing protocol, and it does
not do contact planning.  The BP Agent and its configured policy
select paths and make forwarding decisions.</t>
      <t>Public provisioning is limited to eligible Allocator Identifiers
(<xref target="allocator-dns-provisioning"/>).  Names for Allocator Identifier zero
and Experimental Use Allocator Identifiers are served only by
explicitly configured local DNS (<xref target="publication-restrictions"/>,
<xref target="locally-served"/>).</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?>

<t>This document uses the following terms from <xref target="RFC9758"/>:</t>
      <dl>
        <dt>Allocator Identifier:</dt>
        <dd>
          <t>A 32-bit unsigned integer that identifies the Allocator that
assigned a Node Number (<xref section="3.2" sectionFormat="of" target="RFC9758"/>).</t>
        </dd>
        <dt>Node Number:</dt>
        <dd>
          <t>A 32-bit unsigned integer that identifies a node in the context of
an Allocator (<xref section="3.3" sectionFormat="of" target="RFC9758"/>).</t>
        </dd>
        <dt>Fully Qualified Node Number (FQNN):</dt>
        <dd>
          <t>The combination of an Allocator Identifier and a Node Number, which
identifies one node (<xref section="3.3.1" sectionFormat="of" target="RFC9758"/>).  This document
writes an FQNN as (Allocator Identifier, Node Number), for example
(978879,2).</t>
        </dd>
        <dt>Service Number:</dt>
        <dd>
          <t>An unsigned integer that identifies a service on a node
(<xref section="3.5" sectionFormat="of" target="RFC9758"/>).</t>
        </dd>
        <dt>ipn URI:</dt>
        <dd>
          <t>A URI in the 'ipn' URI scheme.  It contains an FQNN and a Service
Number (<xref section="3" sectionFormat="of" target="RFC9758"/>).  An ipn URI used as a BP Endpoint
Identifier (EID) is an "ipn EID" (<xref section="5" sectionFormat="of" target="RFC9758"/>).</t>
        </dd>
      </dl>
      <t>This document defines the following terms:</t>
      <dl>
        <dt>DNS base name:</dt>
        <dd>
          <t>The DNS name beneath ipn.arpa that represents an FQNN
(<xref target="discovery-model"/>).</t>
        </dd>
        <dt>Discovery binding:</dt>
        <dd>
          <t>The specification of DNS discovery for one CL.  It defines the
query names, record types, processing rules, and fallback behavior.
This document specifies the TCPCLv4 binding (<xref target="tcpcl-binding"/>).</t>
        </dd>
        <dt>CL-specific query name:</dt>
        <dd>
          <t>The DNS name, relative to a DNS base name, at which a discovery
binding queries for records.</t>
        </dd>
        <dt>ipn.arpa operator:</dt>
        <dd>
          <t>The entity that does the DNS provisioning and operational functions
for the ipn.arpa zone (<xref target="creation-of-ipn-arpa"/>).</t>
        </dd>
      </dl>
    </section>
    <section anchor="concept-of-operations">
      <name>Concept of Operations</name>
      <t>A BP Agent populates its Forwarding Information Base (FIB) from
configuration and from other sources.  It can also create FIB entries
from DNS records, as this section describes.</t>
      <section anchor="discovery-model">
        <name>Discovery Model</name>
        <t>Discovery uses the FQNN of the destination node.</t>
        <t>Before constructing a DNS name, a BP Agent <bcp14>MUST</bcp14> parse and interpret
the destination ipn URI or ipn EID according to <xref target="RFC9758"/>.  This
includes the text syntax of <xref section="4" sectionFormat="of" target="RFC9758"/> and the CBOR
decoding of <xref section="6.2" sectionFormat="of" target="RFC9758"/>.  The result is a numeric
Allocator Identifier, Node Number, and Service Number.  An Allocator
Identifier that the text form omits has the value zero
(<xref section="3.2.2" sectionFormat="of" target="RFC9758"/>); the DNS name still contains the
allocator label.</t>
        <t>For Allocator Identifier A and Node Number N, the DNS base name <bcp14>MUST</bcp14>
be:</t>
        <artwork><![CDATA[
N.A.ipn.arpa.
]]></artwork>
        <t>Each of N and A <bcp14>MUST</bcp14> be represented as a single label containing its
unsigned decimal value, using ASCII digits without leading zeroes.
The value zero is the single digit "0".  The labels are not padded and
are not split into individual digits.</t>
        <t>The Service Number is not part of the name, so all ipn URIs with the
same FQNN map to the same DNS base name:</t>
        <table>
          <name>Example DNS Base Names</name>
          <thead>
            <tr>
              <th align="left">ipn URI</th>
              <th align="left">DNS base name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>ipn:978879.2.345</tt></td>
              <td align="left">
                <tt>2.978879.ipn.arpa.</tt></td>
            </tr>
            <tr>
              <td align="left">
                <tt>ipn:978879.2.0</tt></td>
              <td align="left">
                <tt>2.978879.ipn.arpa.</tt></td>
            </tr>
            <tr>
              <td align="left">
                <tt>ipn:16384.345</tt></td>
              <td align="left">
                <tt>16384.0.ipn.arpa.</tt></td>
            </tr>
            <tr>
              <td align="left">
                <tt>ipn:0.16384.345</tt></td>
              <td align="left">
                <tt>16384.0.ipn.arpa.</tt></td>
            </tr>
          </tbody>
        </table>
        <t>The name comes from the parsed numbers, not from the text of the URI.
Equivalent representations of an FQNN therefore give the same name.
This includes <tt>ipn:16384.345</tt> and <tt>ipn:0.16384.345</tt>, and the
two-element and three-element CBOR encodings of an ipn EID
(<xref section="6.4" sectionFormat="of" target="RFC9758"/>).</t>
        <t>The same rule constructs names for Allocator Identifier zero,
including Private Use Node Numbers, and for Experimental Use Allocator
Identifiers.  These names are not in the public hierarchy
(<xref target="publication-restrictions"/>), but local DNS can serve them
(<xref target="locally-served"/>).</t>
        <t>The Null ipn URI (<xref section="3.1" sectionFormat="of" target="RFC9758"/>) and LocalNode ipn URIs
(<xref section="3.4.2" sectionFormat="of" target="RFC9758"/>) do not identify a remote destination.
A BP Agent <bcp14>MUST NOT</bcp14> perform DNS discovery for the Null ipn URI or for
a LocalNode ipn URI.  The BP Agent identifies these cases from the
complete FQNN after interpretation: (0,0) is the Null ipn URI, and
(0,4294967295) is a LocalNode ipn URI.  For example, an ipn URI with a
zero Allocator Identifier, a zero Node Number, and a non-zero Service
Number is the Null ipn URI (<xref section="3.4.1" sectionFormat="of" target="RFC9758"/>).  Node
Numbers 0 and 4294967295 have no special meaning under other Allocator
Identifiers; (978879,0) is an ordinary FQNN.
<xref section="5.4" sectionFormat="of" target="RFC9758"/> also prohibits the publication of LocalNode
ipn EIDs in any node identification directory, such as DNS.</t>
      </section>
      <section anchor="tcpcl-binding">
        <name>TCPCLv4 Discovery Binding</name>
        <t>This document specifies TCPCLv4 <xref target="TCPCL"/> discovery with SRV records
<xref target="RFC2782"/> at the following CL-specific query name:</t>
        <artwork><![CDATA[
_dtn-bundle._tcp.N.A.ipn.arpa.
]]></artwork>
        <t>For example, the query name for the FQNN (978879,2) is
<tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt>.  <xref target="TCPCL"/> registers the
"dtn-bundle" service name and TCP port 4556, but it does not define
this discovery procedure.</t>
        <t>The BP Agent constructs the query name directly.  Unlike conventional
reverse DNS in in-addr.arpa and ip6.arpa, this procedure needs no
preliminary PTR lookup.</t>
        <t>SRV processing follows <xref target="RFC2782"/>, including priority, weight, port,
and target processing.  The following rules apply to this binding:</t>
        <ul spacing="normal">
          <li>
            <t>A new TCPCLv4 discovery result requires a usable SRV record.  If
the lookup obtains no usable SRV record, discovery supplies no new
candidate.</t>
          </li>
          <li>
            <t>The address-record fallback in the usage rules of <xref target="RFC2782"/> does
not apply.  After an unsuccessful SRV lookup, a BP Agent <bcp14>MUST NOT</bcp14>
resolve the DNS base name for address records and connect to TCP
port 4556 as part of this binding.</t>
          </li>
          <li>
            <t>An SRV Target of "." indicates that the service is not available at
that domain (<xref target="RFC2782"/>).</t>
          </li>
        </ul>
        <t>These rules apply only to this binding; other bindings define their
own rules (<xref target="other-cls"/>).  The rules do not affect independently
obtained forwarding information or retained discovery results
(<xref target="discovery-results"/>, <xref target="caching"/>).</t>
      </section>
      <section anchor="examples">
        <name>Examples</name>
        <t>The examples describe one deployment: a fictional space agency that
offers a shared public ingress service.  Other deployments can use a
separate relay for each node, or publish the endpoints of each node.
This document does not require the architecture shown here.</t>
        <t>The agency administers Allocator Identifier 978879.  This identifier,
and the identifiers in <xref target="managing-allocator-ranges"/>, are from the
range that <xref section="9.1" sectionFormat="of" target="RFC9758"/> reserves for examples.  The
excerpts do not request public provisioning of these identifiers.
They omit routine zone infrastructure, such as SOA and NS records, and
DNSSEC records.</t>
        <table>
          <name>Example Destinations</name>
          <thead>
            <tr>
              <th align="left">FQNN</th>
              <th align="left">Destination</th>
              <th align="left">DNS base name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">(978879,1)</td>
              <td align="left">mission operations center</td>
              <td align="left">
                <tt>1.978879.ipn.arpa.</tt></td>
            </tr>
            <tr>
              <td align="left">(978879,2)</td>
              <td align="left">mars-orbiter</td>
              <td align="left">
                <tt>2.978879.ipn.arpa.</tt></td>
            </tr>
            <tr>
              <td align="left">(978879,3)</td>
              <td align="left">lunar-lander</td>
              <td align="left">
                <tt>3.978879.ipn.arpa.</tt></td>
            </tr>
          </tbody>
        </table>
        <t>The destination names are descriptive labels.  They do not depend on
the Node Numbers.</t>
        <t>Two relay BP Agents, <tt>relay-a.space-agency.example.</tt> and
<tt>relay-b.space-agency.example.</tt>, provide the ingress service for all
three destinations.  Each relay is a separate BP node with its own
Node ID, and each relay has onward routes to all three destinations.
Onward forwarding uses the cislunar and deep-space ground facilities,
routes, and contact arrangements of the agency.  These are not shown.</t>
        <t>Example A and Example B are alternative configurations of the
allocator's zone.  The agency publishes only one of them, because a
CNAME and an SRV RRset cannot coexist at the same owner name
(<xref target="dns-constraints"/>).  Both configurations use these address records:</t>
        <figure anchor="relay-addresses">
          <name>Relay Address Records</name>
          <sourcecode type="dns"><![CDATA[
$ORIGIN space-agency.example.
$TTL 3600

relay-a IN A    192.0.2.10
relay-a IN AAAA 2001:db8::10
relay-b IN A    192.0.2.11
relay-b IN AAAA 2001:db8::11
]]></sourcecode>
        </figure>
        <section anchor="example-a-service-records-in-the-allocators-zone">
          <name>Example A: Service Records in the Allocator's Zone</name>
          <t>The allocator's zone contains the SRV records for each destination:</t>
          <sourcecode type="dns"><![CDATA[
$ORIGIN 978879.ipn.arpa.
$TTL 3600

_dtn-bundle._tcp.1 IN SRV 10 1 4556 relay-a.space-agency.example.
_dtn-bundle._tcp.1 IN SRV 10 1 4556 relay-b.space-agency.example.

_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-a.space-agency.example.
_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-b.space-agency.example.

_dtn-bundle._tcp.3 IN SRV 10 1 4556 relay-a.space-agency.example.
_dtn-bundle._tcp.3 IN SRV 10 1 4556 relay-b.space-agency.example.
]]></sourcecode>
          <t>A BP Agent that uses TCPCLv4 to reach <tt>ipn:978879.2.345</tt>:</t>
          <ol spacing="normal" type="1"><li>
              <t>constructs the query name <tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt>;</t>
            </li>
            <li>
              <t>receives two SRV records, with the targets
<tt>relay-a.space-agency.example.</tt> and
<tt>relay-b.space-agency.example.</tt>, each with priority 10, weight 1,
and port 4556;</t>
            </li>
            <li>
              <t>orders the candidates as specified in <xref target="RFC2782"/>; because the
priorities and weights are equal, either relay can be first;</t>
            </li>
            <li>
              <t>resolves the selected target; for <tt>relay-a.space-agency.example.</tt>,
it receives <tt>192.0.2.10</tt> and <tt>2001:db8::10</tt>; and</t>
            </li>
            <li>
              <t>attempts a TCPCLv4 connection to <tt>[2001:db8::10]:4556</tt> or
<tt>192.0.2.10:4556</tt>.  If the attempt fails, it can try
<tt>relay-b.space-agency.example.</tt> (<tt>[2001:db8::11]:4556</tt> or
<tt>192.0.2.11:4556</tt>).  If it establishes a session with a peer that
its policy accepts (<xref target="forwarding-policy"/>), it transfers the
Bundle.</t>
            </li>
          </ol>
        </section>
        <section anchor="example-b-service-lookup-redirected-through-a-cname">
          <name>Example B: Service Lookup Redirected through a CNAME</name>
          <t>Instead of SRV records, the allocator's zone contains a CNAME for each
destination.  Each CNAME points to one shared name in the agency's
zone:</t>
          <sourcecode type="dns"><![CDATA[
$ORIGIN 978879.ipn.arpa.
$TTL 3600

_dtn-bundle._tcp.1 IN CNAME (
    _dtn-bundle._tcp.ingress.space-agency.example. )
_dtn-bundle._tcp.2 IN CNAME (
    _dtn-bundle._tcp.ingress.space-agency.example. )
_dtn-bundle._tcp.3 IN CNAME (
    _dtn-bundle._tcp.ingress.space-agency.example. )
]]></sourcecode>
          <t>The agency publishes the shared SRV RRset in its own zone:</t>
          <sourcecode type="dns"><![CDATA[
$ORIGIN space-agency.example.
$TTL 3600

_dtn-bundle._tcp.ingress IN SRV (
    10 1 4556 relay-a.space-agency.example. )
_dtn-bundle._tcp.ingress IN SRV (
    10 1 4556 relay-b.space-agency.example. )
]]></sourcecode>
          <t>The BP Agent sends the same query as in Example A.  Ordinary DNS
resolution follows the CNAME and returns the shared SRV RRset, which
contains the same two relays.  The remaining steps are the same as in
Example A.</t>
          <t>The agency maintains the relay selection in one SRV RRset.  It can
change the relays in <tt>space-agency.example.</tt> without changes to the
allocator's zone.</t>
        </section>
        <section anchor="shared-ingress">
          <name>Shared Ingress Behavior</name>
          <t>The following points apply to both configurations:</t>
          <ul spacing="normal">
            <li>
              <t>Equal SRV priorities and weights express equal preference
(<xref target="RFC2782"/>).  They do not give equal bundle volume, because one
session can carry many Bundles.  They do not indicate server load.</t>
            </li>
            <li>
              <t>Several FQNNs can share one discovery result, but each Bundle keeps
its destination EID.  For example, a Bundle for the mars-orbiter is
destined for <tt>ipn:978879.2.345</tt> when a relay receives it.  Each
relay presents its own Node ID (<xref target="cl-peer-identity"/>).</t>
            </li>
            <li>
              <t>The example uses one public DNS view.  The agency configures its
internal forwarding in its BP Agents, not in DNS, so it needs no
internal DNS overrides.</t>
            </li>
            <li>
              <t>The public records show the advertised FQNNs, the ingress service,
and the relay addresses.  They do not show the ground facilities or
contact arrangements (<xref target="privacy"/>).</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="dns-constraints">
        <name>DNS Constraints</name>
        <t>The following DNS rules apply to the configurations above:</t>
        <ul spacing="normal">
          <li>
            <t>A CNAME aliases only its own owner name
(<xref section="3.6.2" sectionFormat="of" target="RFC1034"/>).  To redirect a service lookup, the
CNAME is at the complete service owner name, such as
<tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt>.  A CNAME at
<tt>2.978879.ipn.arpa.</tt> does not redirect the lookup.</t>
          </li>
          <li>
            <t>A CNAME record and an SRV RRset cannot coexist at the same owner
name (<xref section="3.6.2" sectionFormat="of" target="RFC1034"/>).</t>
          </li>
          <li>
            <t>An SRV Target other than "." must have address records and must not
be an alias (<xref target="RFC2782"/>; <xref section="5.1" sectionFormat="of" target="RFC6672"/>).</t>
          </li>
        </ul>
      </section>
      <section anchor="other-cls">
        <name>Other Convergence Layers</name>
        <t>The discovery binding for another CL defines its query names, record
types, processing rules, and fallback behavior relative to the DNS
base name.  If a binding uses SVCB records, <xref target="RFC9460"/> and the
binding govern AliasMode, ServiceMode, parameter compatibility,
endpoint selection, and fallback.  SRV rules do not apply to other
record types.  For example, a ServiceMode SVCB TargetName of "."
means the owner name of the record (<xref section="2.5.2" sectionFormat="of" target="RFC9460"/>),
not that the service is unavailable.</t>
        <t>This document does not require a BP Agent to query for every CL that
it supports, and it does not specify an order in which to try CLs.</t>
      </section>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>If DNS does not meet the reliability or performance requirements of a
deployment, particularly during disruption, the deployment can obtain
forwarding information by other means.</t>
      <section anchor="discovery-results">
        <name>Discovery Results and Failures</name>
        <t>Discovery succeeds when a BP Agent obtains usable connection
information under the applicable discovery binding (<xref target="tcpcl-binding"/>,
<xref target="other-cls"/>).  A syntactically valid DNS answer does not always
contain usable connection information.  The binding and the
record-type specification define candidate selection and
compatibility checks.</t>
        <t>A discovery result identifies candidate CL endpoints.  A candidate can
be the destination node or a relay that accepts Bundles for onward
forwarding.  A result does not show that the destination is reachable
now, that a candidate will accept a session or a Bundle, or that the
Bundle will be delivered.</t>
        <t>DNS terminology <xref target="RFC2308"/> distinguishes these unsuccessful
outcomes:</t>
        <dl>
          <dt>NXDOMAIN:</dt>
          <dd>
            <t>The name at which resolution stopped, possibly the target of an
alias, does not exist.</t>
          </dd>
          <dt>NODATA:</dt>
          <dd>
            <t>The name exists, but it has no records of the requested type.</t>
          </dd>
          <dt>SERVFAIL, timeout, and other resolution failures:</dt>
          <dd>
            <t>The lookup did not complete.  This does not show that the service
is absent.</t>
          </dd>
        </dl>
        <t>These outcomes apply only to the DNS discovery attempt.  They do not
show that the FQNN is invalid or that other means cannot reach it.
The absence of discovery records for one CL does not show the absence
of service for another CL.  <xref target="tcpcl-binding"/> specifies the TCPCLv4
result when no usable SRV record exists.</t>
        <t>An unsuccessful discovery attempt does not invalidate forwarding
information from other sources, such as configured routes or other
routing mechanisms.  It does not require deletion of a Bundle.  The
existing policies of the BP Agent govern retries and route precedence.</t>
      </section>
      <section anchor="caching">
        <name>Caching and Operation During Disruption</name>
        <t>Positive and negative DNS caching follow the existing DNS
specifications, including <xref target="RFC2308"/>.</t>
        <t>A retained discovery result depends on the remaining TTLs of the
records that produced it: aliases, SRV or SVCB records, and address
records.  These TTLs can be different.  Copying a result into
forwarding information should not silently make it permanent
configuration.  A BP Agent does not need to repeat the lookup before
each Bundle transfer.  TTL expiry does not require it to close an
established CL session or to delete a Bundle; refreshed information
affects later connection attempts.</t>
        <t>If refresh is not possible, explicit operational policy governs any
continued use of expired discovery information.  That policy considers
possible changes to endpoints, aliases, or administrative control.
<xref target="RFC8767"/> describes how resolvers can serve stale DNS data; it does
not specify how a BP Agent retains forwarding information.</t>
        <t>TTL expiry is different from signature expiry.  Validation checks the
RRSIG validity period (<xref section="5.3.1" sectionFormat="of" target="RFC4035"/>), and the
signature expiration time limits the TTL of authenticated data
(<xref section="5.3.3" sectionFormat="of" target="RFC4035"/>).  An earlier successful validation
therefore does not stay valid indefinitely.  <xref target="bpa-validation"/>
describes the handling of validation failures.</t>
      </section>
      <section anchor="locally-served">
        <name>Locally Served Namespaces</name>
        <t>A deployment that uses a local instance of 0.ipn.arpa or of an
Experimental Use allocator subtree (<xref target="publication-restrictions"/>)
configures it explicitly with ordinary DNS administration.  The
administrator loads the zones, selects authoritative servers, and
configures resolvers to forward queries for those names.  This
document does not request automatic resolver behavior or additions to
the IANA "Locally-Served DNS Zones" registry <xref target="RFC6303"/>.</t>
        <t>The signed public ipn.arpa namespace does not give a chain of trust to
independently administered local data.  If the public namespace does
not contain a name, normal DNSSEC processing can authenticate the
nonexistence of that name.  A validator that uses only the public
chain therefore cannot authenticate a conflicting local answer.  A
validator can authenticate a signed local zone with a configured local
trust anchor (<xref section="7" sectionFormat="of" target="RFC6303"/>).  <xref section="5.10" sectionFormat="of" target="RFC6840"/>
describes how a validator selects among nested trust anchors.  The
trust anchor is necessary wherever validation occurs: in a trusted
validating resolver (<xref target="bpa-validation"/>) or in a BP Agent that
validates independently.</t>
        <t>A deployment can also accept unsigned local data under explicit local
policy.  This acceptance is a policy decision, not a successful DNSSEC
validation.  Local resolution and trust settings are best limited to
the relevant subtrees, without disabling validation for all of
ipn.arpa.</t>
        <t>Administrators should configure resolution so that queries for these
names stay within the intended administrative or experimental scope,
also when local resolution fails.  Public resolution cannot supply the
local data, and queries that reach the public DNS can disclose the
queried identifiers (<xref target="privacy"/>).  <xref target="RFC6303"/> describes the reasons
to contain such queries.  This guidance does not require resolvers in
general to recognize these namespaces.</t>
      </section>
      <section anchor="managing-allocator-ranges">
        <name>Managing Allocator Ranges</name>
        <t>An Allocator can hold a range of Allocator Identifiers
(<xref section="3.2.1" sectionFormat="of" target="RFC9758"/>).  A numeric range does not map to one
DNS subtree: each Allocator Identifier A has its own name,
<tt>A.ipn.arpa.</tt>, directly beneath ipn.arpa.  An operator that administers
several identifiers can delegate a zone for each identifier.
Alternatively, it can use DNAME records <xref target="RFC6672"/> to redirect each
allocator subtree into one zone that it manages.</t>
        <t>In the following example, the agency of <xref target="examples"/> also administers
Allocator Identifiers 974848 and 974849.  The relay address records
are those in <xref target="relay-addresses"/>.</t>
        <sourcecode type="dns"><![CDATA[
$ORIGIN ipn.arpa.
$TTL 3600

974848 IN DNAME 974848.allocators.space-agency.example.
974849 IN DNAME 974849.allocators.space-agency.example.
]]></sourcecode>
        <sourcecode type="dns"><![CDATA[
$ORIGIN 974848.allocators.space-agency.example.
$TTL 3600

_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-a.space-agency.example.
_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-b.space-agency.example.

$ORIGIN 974849.allocators.space-agency.example.

_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-a.space-agency.example.
_dtn-bundle._tcp.2 IN SRV 10 1 4556 relay-b.space-agency.example.
]]></sourcecode>
        <t>A BP Agent that discovers TCPCLv4 service for <tt>ipn:974848.2.345</tt>
constructs the usual query name (<xref target="tcpcl-binding"/>):</t>
        <artwork><![CDATA[
_dtn-bundle._tcp.2.974848.ipn.arpa.
]]></artwork>
        <t>The DNAME at <tt>974848.ipn.arpa.</tt> redirects the query to:</t>
        <artwork><![CDATA[
_dtn-bundle._tcp.2.974848.allocators.space-agency.example.
]]></artwork>
        <t>There, the BP Agent finds the same relay SRV records as in
<xref target="examples"/>.  Ordinary DNS processing does the redirection
(<xref section="3" sectionFormat="of" target="RFC6672"/>).  The BP Agent does not construct names in
the agency's zone.</t>
        <t>Each target subtree keeps its Allocator Identifier label.  Thus
(974848,2) and (974849,2) stay distinct, although their SRV records
select the same relays.  Both FQNNs are also distinct from (978879,2),
the mars-orbiter.  If both DNAMEs pointed to the same target, queries
for (974848,2) and (974849,2) would reach the same records.  Distinct
target subtrees are therefore necessary when the allocator namespaces
must stay distinct.  The decimal allocator label in the target is a
convenient convention, not a DNS requirement.</t>
        <t>One zone can contain all of these subtrees.  Each redirected Allocator
Identifier still needs its own DNAME in ipn.arpa.  The technique
reduces the number of child zones to administer, not the number of
allocator entries in the parent.</t>
        <t>The following DNAME constraints apply:</t>
        <ul spacing="normal">
          <li>
            <t>A DNAME redirects the descendants of its owner name, not the owner
name itself (<xref section="2.3" sectionFormat="of" target="RFC6672"/>).</t>
          </li>
          <li>
            <t>The source zone cannot contain records beneath the DNAME owner
(<xref section="2.4" sectionFormat="of" target="RFC6672"/>).  The data for names beneath
<tt>974848.ipn.arpa.</tt> is in the target subtree.</t>
          </li>
          <li>
            <t>A DNAME rewrites names beneath its owner, but an NS delegation
creates a zone cut.  A parent-side DNAME cannot coexist with a
delegation NS RRset at the same owner name
(<xref section="2.3" sectionFormat="of" target="RFC6672"/>).  A delegated allocator zone can
instead publish a DNAME at its own apex, with its SOA and NS records.
This arrangement keeps separate child-zone administration.</t>
          </li>
        </ul>
        <t><xref section="5.3" sectionFormat="of" target="RFC6672"/> describes DNSSEC considerations for DNAME.
Locally served instances (<xref target="locally-served"/>) can use DNAMEs in the
same way, for example at <tt>N.0.ipn.arpa.</tt>, if the administrator of that
namespace authorizes them.</t>
        <t>Implementation-specific tools, such as the <tt>$GENERATE</tt> directive of
BIND <xref target="BIND-ARM"/>, can produce repetitive records.  For example, this
BIND input produces the two DNAME records above:</t>
        <sourcecode type="dns"><![CDATA[
$ORIGIN ipn.arpa.
$TTL 3600

$GENERATE 974848-974849 $ DNAME $.allocators.space-agency.example.
]]></sourcecode>
        <t>The directive expands into ordinary records.  It adds no numeric-range
matching to DNS, and resolvers need no support for it.  The use of
such tools is optional.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="forwarding-policy">
        <name>Authentication and Forwarding Policy</name>
        <t>The use of DNS-derived forwarding information involves two separate
authentication questions.  DNSSEC authenticates the DNS data
(<xref target="dnssec"/>).  The CL authenticates the session peer
(<xref target="cl-peer-identity"/>).  The authentication of one does not
authenticate the other.</t>
        <t>The configured forwarding and security policies of the BP Agent govern
the use of DNS-derived forwarding information.  These policies can
distinguish sources of forwarding information, for example configured
routes and discovery results, or authenticated and unauthenticated
results.  A BP Agent's configured forwarding policy may permit
automatic use of authenticated discovery mappings, subject to the
security requirements of the applicable CL.</t>
      </section>
      <section anchor="dnssec">
        <name>DNSSEC</name>
        <t>Forged discovery information can redirect connection attempts, and
thus bundle transfers, to endpoints that an attacker selects.  DNSSEC
<xref target="RFC9364"/> gives data origin authentication and integrity for DNS
data.  It does not show that the advertised service is available;
ENUM makes a similar observation (<xref section="7.1" sectionFormat="of" target="RFC6116"/>).</t>
        <t>Operators publishing discovery data for this mechanism in the public
DNS <bcp14>SHOULD</bcp14> provide DNSSEC authentication of that data, including the
necessary chain of trust.  This recommendation applies to all DNS
records relied upon in discovery, including records published outside
ipn.arpa:</t>
        <ul spacing="normal">
          <li>
            <t>aliases and redirections, such as CNAME, DNAME, and SVCB AliasMode
records;</t>
          </li>
          <li>
            <t>service records and other records that carry connection parameters,
such as SRV and SVCB ServiceMode records; and</t>
          </li>
          <li>
            <t>address records for the resulting targets.</t>
          </li>
        </ul>
        <t>The ipn.arpa operator signs ipn.arpa (<xref target="creation-of-ipn-arpa"/>), and
DS records can link delegated allocator zones into that chain of trust
(<xref target="ds-management"/>).  The signature on ipn.arpa does not authenticate
records in delegated zones or in external target namespaces.  Each
record has its own security status.</t>
        <t>Validation follows standard DNSSEC processing.  For example, a CNAME
synthesized from a validated DNAME needs no signature of its own
(<xref section="3.1" sectionFormat="of" target="RFC6672"/>; <xref section="5.3.1" sectionFormat="of" target="RFC6672"/>).</t>
        <section anchor="bpa-validation">
          <name>Validation by BP Agents</name>
          <t>BP Agents using public DNS discovery <bcp14>SHOULD</bcp14> use DNSSEC validation,
either locally or through a trusted validating resolver.  When a BP
Agent relies on validation by another resolver, the resolver and the
channel to it need to satisfy the trust requirements of
<xref section="4.9.3" sectionFormat="of" target="RFC4035"/>.</t>
          <t><xref section="4.3" sectionFormat="of" target="RFC4035"/> defines the security states secure,
insecure, bogus, and indeterminate.  An insecure result means that the
validator has established that no chain of trust exists from a
configured trust anchor to the RRset.  For example, normal DNSSEC
processing proves that the delegation to the target zone is unsigned.
An insecure result does not mean that the validator failed to build a
chain.  Missing signatures where a secure chain requires them can
produce a bogus result.  A zone can contain signatures and still be
insecure if no chain of trust reaches it.</t>
          <t>An application can also receive a result whose security status is
unknown to it, for example from a resolver that does not report
validation results.  The absence of an authentication indication does
not establish that a result is insecure.</t>
          <t>This document does not require a policy of accepting only secure
results.  The configured policy of the BP Agent governs the acceptance
of insecure results and of results with unknown status.</t>
          <t>A known validation failure is a failure of the affected discovery path
(<xref target="discovery-results"/>).  It should not lead to automatic acceptance
of the same data without validation, for example through a query on a
non-validating path.  A BP Agent can still retrieve DNSSEC data to
validate it independently.  <xref target="locally-served"/> describes validation
for locally served namespaces.</t>
        </section>
      </section>
      <section anchor="cl-peer-identity">
        <name>Convergence-Layer Peer Identity</name>
        <t>The applicable CL specification and the configured security policy
govern authentication of the CL peer.  For TCPCLv4,
<xref section="4.4" sectionFormat="of" target="TCPCL"/> specifies session security, including
certificate-based peer identification, and <xref section="4.6" sectionFormat="of" target="TCPCL"/>
specifies the handling of the peer Node ID.  This document does not
change these procedures.</t>
        <t>A TCPCLv4 discovery result involves three different identifiers.  In
Example A (<xref target="examples"/>):</t>
        <ul spacing="normal">
          <li>
            <t>The discovery name, <tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt>, comes
from the destination FQNN.</t>
          </li>
          <li>
            <t>The selected SRV Target, <tt>relay-a.space-agency.example.</tt>, is the DNS
name that the BP Agent resolves to make the TCP connection.  If the
configured policy invokes network-level authentication
(<xref section="4.4.4.2" sectionFormat="of" target="TCPCL"/>), this name is the DNS-ID reference
identifier.  It is also the HostName in the TLS server_name
extension (<xref section="4.4.3" sectionFormat="of" target="TCPCL"/>).</t>
          </li>
          <li>
            <t>The peer Node ID is the Node ID of the relay, which the relay sends
in its SESS_INIT message (<xref section="4.6" sectionFormat="of" target="TCPCL"/>).</t>
          </li>
        </ul>
        <t>Network-level authentication of <tt>relay-a.space-agency.example.</tt>
authenticates the host name only.  It does not authenticate the Node
ID of the relay.  The destination EID of the Bundle stays
<tt>ipn:978879.2.345</tt>.  Discovery does not supply an expected peer Node
ID.  <xref section="4.6" sectionFormat="of" target="TCPCL"/> describes the handling of a peer Node ID
that is different from the intended Node ID or that is not
authenticated.</t>
      </section>
      <section anchor="privacy">
        <name>Privacy</name>
        <t>Public discovery records can reveal destination identifiers, their
association with services and relays, and connection endpoints.
Queries for these records can reveal to resolvers and other observers
which destinations a BP Agent tries to reach, and when.  DNSSEC does
not provide confidentiality.  <xref target="RFC9076"/> describes DNS privacy threats
and mitigations, such as resolver selection and encrypted DNS
transports.  Operators can limit what published records disclose
(<xref target="shared-ingress"/>), and they can keep queries for locally served
names within their intended scope (<xref target="locally-served"/>).</t>
      </section>
      <section anchor="resource-consumption">
        <name>Resource Consumption</name>
        <t>Bundles addressed to many distinct FQNNs, whether malicious or not,
can cause many DNS queries, much retained discovery state, and many
connection attempts.  Implementations <bcp14>SHOULD</bcp14> bound outstanding
discovery work, retained discovery state, and connection attempts,
using existing mechanisms such as resolver limits, queueing, and
connection management.</t>
      </section>
    </section>
    <section anchor="iab-considerations">
      <name>IAB Considerations</name>
      <t>In accordance with <xref section="3" sectionFormat="of" target="RFC3172"/>, the IAB is requested to
approve the zone "ipn.arpa" as an infrastructure namespace derived
from IPN identifiers.  Names in this zone are constructed from FQNNs
(<xref target="discovery-model"/>).  BP Agents use them to discover CL endpoints for
reaching IPN nodes.</t>
      <t>This follows the precedent of e164.arpa <xref target="RFC6116"/>, in which names
are derived from E.164 telephone numbers and queried directly for
service records (NAPTR).</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="creation-of-ipn-arpa">
        <name>Creation of ipn.arpa</name>
        <t>Following approval by the IAB in accordance with
<xref section="3" sectionFormat="of" target="RFC3172"/>, IANA is requested to add "ipn.arpa" to the
".arpa" domain.  <xref target="discovery-model"/> specifies the names in ipn.arpa.</t>
        <t>IANA is requested to arrange the ongoing administration of ipn.arpa,
consistent with the arrangements that the IAB approves under
<xref target="RFC3172"/>.  Administration includes the processing of the requests
in <xref target="allocator-dns-provisioning"/>.  Administration is separate from the
operation of the authoritative DNS servers for ipn.arpa, and this
document does not require IANA itself to operate those servers.  The
ipn.arpa operator does the DNS provisioning and operational functions
under these arrangements.</t>
        <t>The ipn.arpa operator <bcp14>MUST</bcp14> sign the public ipn.arpa zone using DNSSEC
and maintain a chain of trust through the arpa zone.  This requirement
applies only to the ipn.arpa zone.  <xref target="dnssec"/> gives recommendations
for the operators of delegated allocator zones and other namespaces.</t>
      </section>
      <section anchor="publication-restrictions">
        <name>Publication Restrictions</name>
        <t>This document restricts the publication of discovery data for two sets
of names in the public ipn.arpa hierarchy.  These restrictions come
from this document, not from <xref target="RFC9758"/>.  They apply only to DNS
discovery, and they do not change any allocation or its Bundle
Protocol semantics.</t>
        <t>The restrictions apply to every means of placing discovery data for
the affected FQNNs in the public ipn.arpa hierarchy:</t>
        <ul spacing="normal">
          <li>
            <t>discovery records, such as SRV, SVCB, or CNAME records, at or
beneath the restricted names;</t>
          </li>
          <li>
            <t>NS delegations of the restricted names, or of names beneath them,
to servers that publish such discovery data; and</t>
          </li>
          <li>
            <t>CNAME or DNAME records at or beneath the restricted names that
redirect discovery queries to data published elsewhere in the global
DNS.</t>
          </li>
        </ul>
        <t>Names in these subtrees are absent from the public zone.  They receive
ordinary negative answers with normal DNSSEC processing.  This document
requests no special public delegation for them.  For comparison,
home.arpa has an insecure public delegation to accommodate validators
without local trust configuration (<xref section="6.2" sectionFormat="of" target="RFC8375"/>;
<xref section="7" sectionFormat="of" target="RFC8375"/>).  This document does not request that
arrangement.  <xref target="locally-served"/> gives operational guidance for local
instances.</t>
        <section anchor="allocator-zero">
          <name>Allocator Identifier Zero</name>
          <t>"0.ipn.arpa" corresponds to Allocator Identifier zero, the Default
Allocator (<xref section="3.2.2" sectionFormat="of" target="RFC9758"/>).  Public DNS discovery for
FQNNs with Allocator Identifier zero is intentionally outside the
scope of this document.  A populated "0.ipn.arpa" zone <bcp14>MUST NOT</bcp14> be
published in the public ipn.arpa hierarchy specified by this document.
A "0.ipn.arpa" zone <bcp14>MAY</bcp14> exist in local DNS resolvers or servers that
serve it authoritatively as a locally served zone <xref target="RFC6303"/>, much as
the IN-ADDR.ARPA zones for the private address space of <xref target="RFC1918"/>
are served locally (<xref section="4.1" sectionFormat="of" target="RFC6303"/>).</t>
          <t>The restriction covers every Node Number under Allocator Identifier
zero.  This includes the Private Use Node Numbers 1 through 16383
(<xref section="3.4.3" sectionFormat="of" target="RFC9758"/>) and the Node Numbers 2097152 through
268435455 reserved for Private or Experimental Use
(<xref section="3.2.1" sectionFormat="of" target="RFC7116"/>; <xref section="9.2" sectionFormat="of" target="RFC9758"/>).</t>
          <t>The restriction does not mean that Allocator Identifier zero has only
local significance.  The registry of the Default Allocator
(<xref section="9.2" sectionFormat="of" target="RFC9758"/>) also contains assigned Node Numbers.
Public support would need administration and delegation procedures for
these allocations, and a treatment of the private ranges and of
locally served DNS data.</t>
          <t>Note to the Working Group (to be removed before publication as an
RFC): The working group can reconsider public DNS support for
Allocator Identifier zero if it chooses to take on that scope.</t>
        </section>
        <section anchor="experimental-allocators">
          <name>Experimental Use Allocator Identifiers</name>
          <t><xref section="9.1" sectionFormat="of" target="RFC9758"/> designates Allocator Identifiers 1073741824
through 2147483647 (0x40000000 through 0x7FFFFFFF) as Experimental
Use.  Experimental Use values are not assigned to any party
(<xref section="4.2" sectionFormat="of" target="RFC8126"/>), so independent experiments can use the
same identifier.  A globally authoritative mapping to discovery data
is therefore not appropriate.</t>
          <t>For each Experimental Use Allocator Identifier A, a populated subtree
beneath "A.ipn.arpa" <bcp14>MUST NOT</bcp14> be published in the public ipn.arpa
hierarchy.  Names beneath "A.ipn.arpa" <bcp14>MAY</bcp14> be served by local DNS
resolvers or servers within the scope of an experiment.</t>
        </section>
      </section>
      <section anchor="allocator-dns-provisioning">
        <name>Allocator DNS Provisioning</name>
        <t>IANA and the ipn.arpa operator are requested to maintain a procedure
that links requests for DNS provisioning at "A.ipn.arpa" to the entry
for Allocator Identifier A in the "'ipn' Scheme URI Allocator
Identifiers" registry (<xref section="9.1" sectionFormat="of" target="RFC9758"/>).  IANA and the
ipn.arpa operator determine the storage format, the request interface,
and the presentation of provisioning information.</t>
        <t>DNS provisioning is optional.  It can be requested when an Allocator
Identifier is assigned or at any later time.  A DNS entry is not a
condition for the validity or use of an allocator assignment.</t>
        <t>Eligible Allocator Identifiers are those assigned for operational use
in the registry, subject to the exclusions in this document.  This
document does not request public provisioning for:</t>
        <ul spacing="normal">
          <li>
            <t>Allocator Identifier zero (<xref target="allocator-zero"/>);</t>
          </li>
          <li>
            <t>Experimental Use Allocator Identifiers
(<xref target="experimental-allocators"/>);</t>
          </li>
          <li>
            <t>unassigned or reserved Allocator Identifiers; or</t>
          </li>
          <li>
            <t>Allocator Identifiers 974848 through 978943, which are reserved for
documentation examples (<xref section="9.1" sectionFormat="of" target="RFC9758"/>).</t>
          </li>
        </ul>
        <t>The authorized DNS administrators of the allocator manage the records
beneath the allocator name, such as node-level discovery records and
further delegations.  These procedures do not require IANA or the
ipn.arpa operator to provision individual Node Numbers.</t>
        <section anchor="request-authorization">
          <name>Request Authorization</name>
          <t>Requests to create, update, or remove NS, DNAME, or DS records for an
eligible Allocator Identifier are subject to the same administrative
authority and requester-verification procedures that IANA applies to
changes to the corresponding entry in the "'ipn' Scheme URI Allocator
Identifiers" registry.  DNS provisioning changes do not themselves
require a new review of the numeric allocation.  The same procedures
apply to a conversion between NS delegation and DNAME redirection.</t>
        </section>
        <section anchor="provisioning-alternatives">
          <name>Provisioning Alternatives</name>
          <t>The parent-zone configuration at "A.ipn.arpa" is one of the following:</t>
          <dl>
            <dt>NS delegation:</dt>
            <dd>
              <t>The requester supplies the domain names of the authoritative
nameservers, any addresses needed for glue, and any DS records
(<xref target="ds-management"/>).</t>
            </dd>
            <dt>DNAME redirection:</dt>
            <dd>
              <t>The requester supplies the fully qualified target domain name
(<xref target="managing-allocator-ranges"/>).</t>
            </dd>
          </dl>
          <t>A DNAME at the allocator name does not coexist with an NS delegation,
or with the DS records of a delegation, at that name
(<xref section="2.3" sectionFormat="of" target="RFC6672"/>).</t>
          <t>One request can cover several Allocator Identifiers within the
allocation of the requester.  The request identifies each Allocator
Identifier and its configuration.  Each allocator name still has its
own parent-zone records; DNS has no numeric-range syntax.</t>
        </section>
        <section anchor="ds-management">
          <name>DS Records for Delegated Allocator Zones</name>
          <t>The ipn.arpa operator <bcp14>MUST</bcp14> support authenticated requests to add,
update, and remove DS records for delegated allocator zones.
<xref target="request-authorization"/> applies to these requests.  The operator of
a delegated allocator zone coordinates changes to its signing keys
with updates to the DS records in ipn.arpa.</t>
          <t>This support enables secure delegations.  It does not require that
every delegated allocator zone be signed.</t>
          <t>DS records apply only to NS delegations.  A DNAME in ipn.arpa is not a
delegation.  The ipn.arpa operator signs it as ordinary data in the
ipn.arpa zone, and the target namespace has its own DNSSEC chain of
trust.</t>
        </section>
        <section anchor="request-validation">
          <name>Request Validation and Allocation Review</name>
          <t>The allocation procedures of <xref section="9.1" sectionFormat="of" target="RFC9758"/>, including
Expert Review, continue to apply to numeric assignments of Allocator
Identifiers (<xref target="request-authorization"/>).</t>
          <t>The ipn.arpa operator does the applicable DNS technical checks on
provisioning requests under its published operational procedures.
The technical requirements of IANA for delegations in the zones that
it manages <xref target="IANA-NS-REQS"/> are relevant background.  DNAME
provisioning is subject to the requirements of <xref target="RFC6672"/>.</t>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC1034">
          <front>
            <title>Domain names - concepts and facilities</title>
            <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/>
            <date month="November" year="1987"/>
            <abstract>
              <t>This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="13"/>
          <seriesInfo name="RFC" value="1034"/>
          <seriesInfo name="DOI" value="10.17487/RFC1034"/>
        </reference>
        <reference anchor="RFC2782">
          <front>
            <title>A DNS RR for specifying the location of services (DNS SRV)</title>
            <author fullname="A. Gulbrandsen" initials="A." surname="Gulbrandsen"/>
            <author fullname="P. Vixie" initials="P." surname="Vixie"/>
            <author fullname="L. Esibov" initials="L." surname="Esibov"/>
            <date month="February" year="2000"/>
            <abstract>
              <t>This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2782"/>
          <seriesInfo name="DOI" value="10.17487/RFC2782"/>
        </reference>
        <reference anchor="RFC3172">
          <front>
            <title>Management Guidelines &amp; Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")</title>
            <author fullname="G. Huston" initials="G." role="editor" surname="Huston"/>
            <date month="September" year="2001"/>
            <abstract>
              <t>This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. 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="52"/>
          <seriesInfo name="RFC" value="3172"/>
          <seriesInfo name="DOI" value="10.17487/RFC3172"/>
        </reference>
        <reference anchor="RFC4035">
          <front>
            <title>Protocol Modifications for the DNS Security Extensions</title>
            <author fullname="R. Arends" initials="R." surname="Arends"/>
            <author fullname="R. Austein" initials="R." surname="Austein"/>
            <author fullname="M. Larson" initials="M." surname="Larson"/>
            <author fullname="D. Massey" initials="D." surname="Massey"/>
            <author fullname="S. Rose" initials="S." surname="Rose"/>
            <date month="March" year="2005"/>
            <abstract>
              <t>This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of new resource records and protocol modifications that add data origin authentication and data integrity to the DNS. This document describes the DNSSEC protocol modifications. This document defines the concept of a signed zone, along with the requirements for serving and resolving by using DNSSEC. These techniques allow a security-aware resolver to authenticate both DNS resource records and authoritative DNS error indications.</t>
              <t>This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4035"/>
          <seriesInfo name="DOI" value="10.17487/RFC4035"/>
        </reference>
        <reference anchor="RFC6672">
          <front>
            <title>DNAME Redirection in the DNS</title>
            <author fullname="S. Rose" initials="S." surname="Rose"/>
            <author fullname="W. Wijngaards" initials="W." surname="Wijngaards"/>
            <date month="June" year="2012"/>
            <abstract>
              <t>The DNAME record provides redirection for a subtree of the domain name tree in the DNS. That is, all names that end with a particular suffix are redirected to another part of the DNS. This document obsoletes the original specification in RFC 2672 as well as updates the document on representing IPv6 addresses in DNS (RFC 3363). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6672"/>
          <seriesInfo name="DOI" value="10.17487/RFC6672"/>
        </reference>
        <reference anchor="RFC9364">
          <front>
            <title>DNS Security Extensions (DNSSEC)</title>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="February" year="2023"/>
            <abstract>
              <t>This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of those RFCs. A second purpose is to state that using DNSSEC for origin authentication of DNS data is the best current practice. A third purpose is to provide a single reference for other documents that want to refer to DNSSEC.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="237"/>
          <seriesInfo name="RFC" value="9364"/>
          <seriesInfo name="DOI" value="10.17487/RFC9364"/>
        </reference>
        <reference anchor="RFC9460">
          <front>
            <title>Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)</title>
            <author fullname="B. Schwartz" initials="B." surname="Schwartz"/>
            <author fullname="M. Bishop" initials="M." surname="Bishop"/>
            <author fullname="E. Nygren" initials="E." surname="Nygren"/>
            <date month="November" year="2023"/>
            <abstract>
              <t>This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9460"/>
          <seriesInfo name="DOI" value="10.17487/RFC9460"/>
        </reference>
        <reference anchor="RFC9758">
          <front>
            <title>Updates to the 'ipn' URI Scheme</title>
            <author fullname="R. Taylor" initials="R." surname="Taylor"/>
            <author fullname="E. Birrane III" initials="E." surname="Birrane III"/>
            <date month="May" year="2025"/>
            <abstract>
              <t>This document updates the specification of the 'ipn' URI scheme previously defined in RFC 6260 and the IANA registries established in RFC 7116. It also updates the rules for the encoding and decoding of these URIs when used as an Endpoint Identifier (EID) in the Bundle Protocol version 7 (BPv7) as defined in RFC 9171. These updates clarify the structure and behavior of the 'ipn' URI scheme, define new encodings of 'ipn' scheme URIs, and establish the registries necessary to manage this scheme.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9758"/>
          <seriesInfo name="DOI" value="10.17487/RFC9758"/>
        </reference>
        <reference anchor="TCPCL">
          <front>
            <title>Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4</title>
            <author fullname="B. Sipos" initials="B." surname="Sipos"/>
            <author fullname="M. Demmer" initials="M." surname="Demmer"/>
            <author fullname="J. Ott" initials="J." surname="Ott"/>
            <author fullname="S. Perreault" initials="S." surname="Perreault"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document describes a TCP convergence layer (TCPCL) for Delay-Tolerant Networking (DTN). This version of the TCPCL protocol resolves implementation issues in the earlier TCPCL version 3 as defined in RFC 7242 and provides updates to the Bundle Protocol (BP) contents, encodings, and convergence-layer requirements in BP version 7 (BPv7). Specifically, TCPCLv4 uses BPv7 bundles encoded by the Concise Binary Object Representation (CBOR) as its service data unit being transported and provides a reliable transport of such bundles. This TCPCL version also includes security and extensibility mechanisms.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9174"/>
          <seriesInfo name="DOI" value="10.17487/RFC9174"/>
        </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="RFC1918">
          <front>
            <title>Address Allocation for Private Internets</title>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="B. Moskowitz" initials="B." surname="Moskowitz"/>
            <author fullname="D. Karrenberg" initials="D." surname="Karrenberg"/>
            <author fullname="G. J. de Groot" initials="G. J." surname="de Groot"/>
            <author fullname="E. Lear" initials="E." surname="Lear"/>
            <date month="February" year="1996"/>
            <abstract>
              <t>This document describes address allocation for private internets. 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="5"/>
          <seriesInfo name="RFC" value="1918"/>
          <seriesInfo name="DOI" value="10.17487/RFC1918"/>
        </reference>
        <reference anchor="RFC2308">
          <front>
            <title>Negative Caching of DNS Queries (DNS NCACHE)</title>
            <author fullname="M. Andrews" initials="M." surname="Andrews"/>
            <date month="March" year="1998"/>
            <abstract>
              <t>RFC1034 provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces RFC1034 Section 4.3.4. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2308"/>
          <seriesInfo name="DOI" value="10.17487/RFC2308"/>
        </reference>
        <reference anchor="RFC6116">
          <front>
            <title>The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <author fullname="L. Conroy" initials="L." surname="Conroy"/>
            <author fullname="K. Fujiwara" initials="K." surname="Fujiwara"/>
            <date month="March" year="2011"/>
            <abstract>
              <t>This document discusses the use of the Domain Name System (DNS) for storage of data associated with E.164 numbers, and for resolving those numbers into URIs that can be used (for example) in telephony call setup. This document also describes how the DNS can be used to identify the services associated with an E.164 number. This document obsoletes RFC 3761. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6116"/>
          <seriesInfo name="DOI" value="10.17487/RFC6116"/>
        </reference>
        <reference anchor="RFC6303">
          <front>
            <title>Locally Served DNS Zones</title>
            <author fullname="M. Andrews" initials="M." surname="Andrews"/>
            <date month="July" year="2011"/>
            <abstract>
              <t>Experience with the Domain Name System (DNS) has shown that there are a number of DNS zones that all iterative resolvers and recursive nameservers should automatically serve, unless configured otherwise. RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This document extends the practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space and other well-known zones with similar characteristics. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="163"/>
          <seriesInfo name="RFC" value="6303"/>
          <seriesInfo name="DOI" value="10.17487/RFC6303"/>
        </reference>
        <reference anchor="RFC6840">
          <front>
            <title>Clarifications and Implementation Notes for DNS Security (DNSSEC)</title>
            <author fullname="S. Weiler" initials="S." role="editor" surname="Weiler"/>
            <author fullname="D. Blacka" initials="D." role="editor" surname="Blacka"/>
            <date month="February" year="2013"/>
            <abstract>
              <t>This document is a collection of technical clarifications to the DNS Security (DNSSEC) document set. It is meant to serve as a resource to implementors as well as a collection of DNSSEC errata that existed at the time of writing.</t>
              <t>This document updates the core DNSSEC documents (RFC 4033, RFC 4034, and RFC 4035) as well as the NSEC3 specification (RFC 5155). It also defines NSEC3 and SHA-2 (RFC 4509 and RFC 5702) as core parts of the DNSSEC specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6840"/>
          <seriesInfo name="DOI" value="10.17487/RFC6840"/>
        </reference>
        <reference anchor="RFC7116">
          <front>
            <title>Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries</title>
            <author fullname="K. Scott" initials="K." surname="Scott"/>
            <author fullname="M. Blanchet" initials="M." surname="Blanchet"/>
            <date month="February" year="2014"/>
            <abstract>
              <t>The DTNRG Research Group has defined the experimental Licklider Transmission Protocol (LTP) and the Compressed Bundle Header Encoding (CBHE) mechanism for the InterPlanetary Network ('ipn' URI scheme). Moreover, RFC 5050 defines values for the Bundle Protocol administrative record type. All of these fields are subject to a registry. For the purpose of its research work, the group has created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official management. This document describes the necessary IANA actions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7116"/>
          <seriesInfo name="DOI" value="10.17487/RFC7116"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8375">
          <front>
            <title>Special-Use Domain 'home.arpa.'</title>
            <author fullname="P. Pfister" initials="P." surname="Pfister"/>
            <author fullname="T. Lemon" initials="T." surname="Lemon"/>
            <date month="May" year="2018"/>
            <abstract>
              <t>This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.' and designates this domain as a special-use domain name. 'home.arpa.' is designated for non-unique use in residential home networks. The Home Networking Control Protocol (HNCP) is updated to use the 'home.arpa.' domain instead of '.home'.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8375"/>
          <seriesInfo name="DOI" value="10.17487/RFC8375"/>
        </reference>
        <reference anchor="RFC8767">
          <front>
            <title>Serving Stale Data to Improve DNS Resiliency</title>
            <author fullname="D. Lawrence" initials="D." surname="Lawrence"/>
            <author fullname="W. Kumari" initials="W." surname="Kumari"/>
            <author fullname="P. Sood" initials="P." surname="Sood"/>
            <date month="March" year="2020"/>
            <abstract>
              <t>This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector. This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8767"/>
          <seriesInfo name="DOI" value="10.17487/RFC8767"/>
        </reference>
        <reference anchor="RFC9076">
          <front>
            <title>DNS Privacy Considerations</title>
            <author fullname="T. Wicinski" initials="T." role="editor" surname="Wicinski"/>
            <date month="July" year="2021"/>
            <abstract>
              <t>This document describes the privacy issues associated with the use of the DNS by Internet users. It provides general observations about typical current privacy practices. It is intended to be an analysis of the present situation and does not prescribe solutions. This document obsoletes RFC 7626.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9076"/>
          <seriesInfo name="DOI" value="10.17487/RFC9076"/>
        </reference>
        <reference anchor="RFC9171">
          <front>
            <title>Bundle Protocol Version 7</title>
            <author fullname="S. Burleigh" initials="S." surname="Burleigh"/>
            <author fullname="K. Fall" initials="K." surname="Fall"/>
            <author fullname="E. Birrane, III" initials="E." surname="Birrane, III"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document presents a specification for the Bundle Protocol, adapted from the experimental Bundle Protocol specification developed by the Delay-Tolerant Networking Research Group of the Internet Research Task Force and documented in RFC 5050.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9171"/>
          <seriesInfo name="DOI" value="10.17487/RFC9171"/>
        </reference>
        <reference anchor="BIND-ARM" target="https://bind9.readthedocs.io/en/latest/chapter3.html">
          <front>
            <title>BIND 9 Administrator Reference Manual</title>
            <author>
              <organization>Internet Systems Consortium</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="IANA-NS-REQS" target="https://www.iana.org/help/nameserver-requirements">
          <front>
            <title>Technical requirements for authoritative name servers</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8196XLbSJrg/3wKrFwRZXWQtC7r8uzM0JLcrVhZVkmqmu2Z
mGiDZErCGgQ4AGiZpXI/yzzLPNl+Zx4AKLu6J2K3IrotkkAeX373lcPh0DRZ
k9vjZOP2wSbZohil1SJN/rUsbJIWs+T86jI5vbxJPixslTZZWdQbJp1MKvsZ
XsEfZ2WTjK+vxhtmmjb2vqxWx0ndzIyZldMincPIsyq9a4b203DWFEOYYYgz
DLd2TL2czLO6hkGb1QIePD+7fZckL5I0r0sYPStmdmHh/4pmY5Bs2FnWlFWW
5vjhfPwW/ikr+Ov69t2GKZbzia2OzQzWcGymsExb1Mv6OGmqpTWw1l2TVjaF
UTfMY1l9uq/K5QI+ndo8Xb06zepqucDdJbdlDhstmuTSNvhgVtxvmE92BX/P
jk0yTE5vL/Gft1f4/wAA+u7yxny2xRKmTpLfN3SS8N438M95muXwJ8DpnzPb
3I3Kip5Iq+kDfP3QNIv6+NUrfAq/yj7bkT72Cr94NanKx9q+gvdf4Xv3WfOw
nMCb9lOeFfA9HUR4CvhUDiCrm2B8fnrEb4+ysue9V71nOnpo5vmGMemyeSgr
hBYMnyR3yzxnTDirsk/J/8LR6QdYd1pkvxJaHSfjNF/B8Sa3dvpQlHl5n9l6
kFxcnNCzlmFjP9GW//keP46m5dyYoqzmMMRnAv71u5Ptrd09+XPn4HBH/tzd
PtA/97Z2X8uf+/vu26PdfX3taG9/S/88eH2If96eXJ1cHNM32wd7xmTFXXva
o+1DnXZ3S//c397e1z93t3b1z8M9neDAP3C4veP+3D3QJR4e7B/oYrYO9AFY
xTb++fb88nQ4vn5/TEBSUsZvk6NkPJtnRVY3QLhAKdf2zla2mNrkfVosgYzo
FXdW9N8QzwQIsWhsVdgmuVnVjZ3XyQkQVFk12XJODxKVJXdAp3yQTVrdW0Ah
xaAJkO7RCOht1jxY4AM1YpEtXjGqvZo+pAuYYJfwBQY4H1+Oh5c3w+uzn27i
jRAuZNM0Tyr7H8ussnNgBnUCsJeFZw2dQYL4ldS2+myr+rmNwUzftYPHx8dR
lhYp0daDzRevcAaeYBiuxRgzHA6TdIJgnjbG3D5kNTDF6RJ/pmXDlusEAJFM
ASLECco7x2kHwGUTwKYqhQGW02ZZWWInNN0ihdPCzeLbyGyLcgZMGjlidpfB
VnEk/O3tspjlNrmqyqaclnny8u3V5sicpdOH5B1Q3yr5CQ4cX5kllzjEJbHL
5CGtk5TY+yStBYgyIqK3uRyNR36hjw+AP8k4yXg34zwvp4RZ525BJDIu9Qmc
yvBUowRefHuVjO8RKlPYM8ClWiUTWwBMHuDxtOH5dbuVnQLLrfmXFFk6gP4e
8XcIfBWmmmX1tPxMgwC6ATNN6oWd4jKAbdRL2Drs7ub6F5QSN7+cvDUyIiwF
RF3tZxB4rviMOvOABFqUGRz1AKh+mi9pqgqZO8zDqwOwpDN4rclqgDDuAE4a
GDQ8mCYzOP+soIMfMbLMsxmcljEvkNCqcgbHDj8i6vSfZPL0JCT/9SvsbLEA
UqxhpfP5EomDUCorkoLFSm3cokDA/h87bZKmhFXAgul4Zk4iMSQQFZOfr8+T
evoAOG14MuB7MJlDtRoPD7GvpjGQELIpfHgEIZGw8EXAjgvj0SIF0X5f1CHG
1QNWKoAM3c+AC+4dE6ASLBqB6H+U5a7FuxbKwQBA0oCzhMtwEM9Rwst3P11e
AsmYFpZ+KspHXCFpOv4gad/lsqHf+ZiRimYliKXCwM7KaQYcZsbwyeC00tYu
nKblCX1RlZ8zgrDBs4VZamBLDQ5PCEiI5bEetwyi9FNNU6ee1+P6mtKkrYMg
dgWzM1eA7RL5o54XMYCB+RiS/ehj8vLpyc06nAPQ8q9fN79B0OZbBN1DaC9P
Ljb9/oxS9czegcLQJVtHccnJhSdS4V8mPCzimrAK+CllypVFTKd2Aa8wzbFY
KYvHtJoZ+BP/hfkBJ+hoHdyBuZVEPmnO2Jw1RJQ5UklZAIoBNGYZShggyS9N
8lAuahMBsbL1Mm9qBuN5g0MWJQIFAAraIx+5cAA3x6y0tcHHZiUCrwFpkyzy
tChwkYxU7jz4FeQRxV12DzJlBiiUZ9OVqW2OHGEBZ8SkPE8/0RnJdgHc0wxV
8ho2frWcwEuMmPgd/g5rzbN5hsiNFJpn99kk76dK2rVDw+GsqIfhULz9S8R/
An0vYf9qK0BlWOfZF7BAMkRi0AZ+rtfMyGwPxfSMz2KyMvYLnM0UNIpVCA98
OSfUh0UuaKOELXg4TZURS4YTGgA/pEfz1ZDHxWUbZN4niMEFPUeQPEVEzegz
83IwG5JHwtWN9z/f3KLdgv8mlx/ob1B3fj6/PjvFv2/+NL64cH8YeeLmTx9+
vjj1f/k3Tz68f392ecovw7dJ9JXZeD/+8wZjzsaHq9vzD5fjiw2UEU2knSCw
4BAnwI5Q41tUFo81rZF6plU2gQ/wztuTq//6z+09kEL/A5Xb7e0jkAz84RCU
YfgAmkHBsxHM+SNQ4cqki4VNKxwFIAiEsQCFLUcpUCf1Q/lYJKhTADj/8G8I
mX8/Tv5hMl1s7/2jfIEbjr5UmEVfEsy633ReZiD2fNUzjYNm9H0L0vF6x3+O
Pivcgy//4Z/Q9kmG24f/9I+mrSoua1uL6gWYTVIFzgSU77uqnCeBVD42pg/3
jw3YUMnuznACzGJZIMun8wOjHIUhMrxAnMcaHP6KhmYtb6WxcHx6urFEEMnu
aAfZqFsLkkLw6O9bQyr6bKGaV4PssrzDlQRKQTz/bmf+b8t1XNYtTTGfqFBA
YVCsVyYiCKDum00fYF3B6lFy0vrj5Y22WwtE1hycMwzyCGYLKVIshoEWXvat
YxAuYXNAPNJ+SeeLHG2Wl0cHh4cHR4MdBMEN62PhKRTfA3/R42Avchg4cLid
1x1oi7bIJ41qoxzfj/DDj4EeyZKNBFVWBJsl2Mp6YbYeFOvAD/aiOuqyJgbF
ovJMhD6akP70Xp6dn26imIIpN/A9+LwRTtDdU0yIonD00eIxKwNOWVLEwi9J
2VF7xql3BPPKAmutyXQVODCce9QqmKBt1+gkYt5MHf7GeglrL6gNMeiDbcBs
rJ2RsjkQFYo8T/AJZDKo8jWZNcvcio4OtnE+SaefYEsP6ecMFFfTwmRvbxGo
yEXyec9ZY7C/ZrqY5kP5gnd3cjHUfQRrasNxQGoaWfYgn1omKqyvYYJE68rp
i4mbGcfNRKlQo48Ql4+kJFdmWemkiDmNqISoZNFucMZI7yHppk5Q0BzulgXr
CDCxqrhuil/xIAAAavEPyzvnJWM4kPqA6icepHeuJk8vpvw9vuLmq79Glsmi
XCzJl0JK3juvvJ2rWwoQ5C3C6+W787ebJEGM6j78Kx0xCpaSTKS6XFZTUrLP
WZtHHyw7LGwCYyCQEKaG3kHgCGBJlJNWUQt5qe6AMH/xIvHo/B5xHDbYxvoQ
5Z0QJGYhvoi2Lg8Dv7WwUZIZ7DbxNphgiAcW6RGLtKrZoe00HdMeWnkMHKaw
DbQQSoYsoGEggoWpi0NAlkzSq14Bw/uCK/cMZy9iOM5WPXn74Ro0rWlJE0Rv
7LfErOj3bDcQb0OjG7B82qsKDGLhhRPGEoKZar/ZjWTgtkOmczlHNHtIeZuf
03xpWS+PFYO2avDGERJ755oMVUAVCMiWvImapxOboyxfZweM2bUUiPbLgRvf
e6/wsM0E+In561//GvmvRvQN+8RgmSyJxowdE+tZtMoX5Idg19DCdNVk/zS1
cZIVjaU5MAOCyQCwF58Y35ycnwNjukeoqaMgtykdM8INSeM2gqR6zGRSejfZ
2NqQc6dFsG2DBuAinc1wmcXM6Fc1mDgN4jYMBUzwczYDdUjWMGJrJMYAtTmB
MBqlMyYdoHvU1YUaxMWDp1UjgIku5+kCCYJWjF+2ZKL5zdHSb63z+c38NhwO
6X/w1Ed47Jj1GECf3b3XH+GFjzsj+SrwQXSf3vr2s9v7u4d7blj+tNX75Nbo
O559Oma/9P/cOGMtjPZGbJaM2I2vDGjaKKiaVlR3BBPxn5l6ygYEevejqL30
NwBtZM7+Y5kBcrADWfBS5AOrrXQKyLiZDd6ToNTTwPlHrNM4/tSGByJ/Z+cD
ZU2meSyHNrdz9SU0D5W17htkXCAQmHHpkoRlhjxhf7TXo2rJKlHV8Py7ZtXk
eT9A6IC9qgBCIJvQE9B1MOIw6x0GAbvzbiWeX+lJlFr2CyQP8CQG2FbmWV8B
6OgTJHXnWUBBSk4DHGyOL/e5EhAkl0tPcrEG3jInaHsXOArtWqk0ZsV7bVaM
PiPalrq60Q82Lxsbe6fHLamJ5i4AkYRAV9ls2usuydVq0u762v6p2BAF6E/T
OiAX9H8CfTXCbtK7BhmWCm6JF77cGmxtulBDsA5CAQM/7+0c7R3tH+wcvWZ7
oHdd77xVNVA8xs0Q20sNced+GZsy6+6IWrSkiiH9pnaO57kdoLUOrms9Bi7t
OtmiGfzGQCpj9KtkXRzQbm5TElPLYgYTsnLXi/hvnAW5pdYSqTopnC5CfWQC
i2nUVmFQOwT1+CGbZBLcCsgCn3WgNsIYanICFas4hiUvzDJQJ2GBKx+5AXxj
BVLtCq8kvhU9/+lFbGC0DTlvn+gYT0/0F+zAozIdNMaJRKPlAAiGjnGjTcsM
XGe/kHbxF4yGT8ibPPoLrG3Uo4BE+IZj+1EcVRHWewMfjsd87IzdI/oAW/wO
K3uf1Q0iDVLUhn99w5n9NCkiFLyTYFQp2Xv9ep+5mHiciW2wKWnYeegAR3bj
bEn+u4i6A67e2iCfc76Chf5c5NknibcVbFOZymL8luVqhjGtIWg6FZtUpLsv
9iUWSUtxC0gKa2e4VAP8Ab3ThMVXt9fAi8tPywV6SOCAA0OXD7ROgrMeJF66
LKoMY8uAjo82u39oBgSdATmiOVQcDCbMzeMIWdFJuljkK1aTYK3Oljd/AK2z
sI8OJz1ARb2X8DIyrGWdonPdYycaaOgfQ7jy3pJywgo1MIHO44NgdBejgAdh
fhjExSnQAUt7QHDDpobiIHA+ABGHMP69le2RveIJhaITCYcxcONoYRDbTskR
tZwisO6WOS2OV9610kDewBiwgjIXhSbWHinuz0v0YSA4EkCiQuKcAFUYwuEy
chKv4vpzoB2DCYSrueUDhSc2RhukPk/JtnaWkJKLhmk+YwIOApqcpuI3wMgf
MnMHEhHttY3wgRzkLaR4I3xaPtZCbzh3Vhn0kvMIMDo9OJzmtXoWdXQR8Ond
HQIiSJ3KV4YxhCPT6inIAk8BuUnkkTY2rotcDeD0pxzjFofGi0TUYnRiCIer
RSXWj845QJ4qWGNerpBVHwMq3LEeBTKMw6EpxgbZLWNK2FZFVtlDSsEs1stg
csIFOSAAyAcCpB+4Jh1siba/qS1gAuqMHAIkdypagyiQKJeMRq3J2IkDiu6x
UdtVqBxSaJZepdysxnIuRxTlIBLjbWm8FrfVq/AKcxefm8/5ECb0EOeBAO49
Pc3TIr0HmAx9zK1Ki3tLx4WardOv6GvGXC/lj1rKB2IAqql16HkWhdnYL1PQ
xhqHeJLooicTuc7YtKmjFZMFvCLXgoQ8LXvN4lyYIJPjg7gAQtcT6HnAIW7O
TgI/328sPsHyDHw7z9ihYouquN3ehIclLdE7/ACP0DdQkXG4xuYMBDaMAAbf
sKxAPeKX1hmq+tIuvpQvQXAN85R0N3hpt/elHjvU79RZoZHTzNk2TH8L8qyy
V4HPc6XnyHwDyNNoOoVaVoi/j6UQj/JtOISP9M0wHRHZDhm/R4IuIzI1jTwz
WfPMQHMfGK9jqmaun+eGjNBwXy6bgdeUcURDiFzyVXwGBtAhh6rOT1lPt/5V
zoRA3kjIiMyfvSA9c5oP/GDATJ3XcprVdIacaGPtYsi8DHNCyac+zfKswQwl
w/MMVH5ROD+tiDCZcYlDQGClZqpz+CBfgSNRFGDi0E9vOScpxzQ+dqNH3l+X
JeEYxY81UZ+IFOFRwg81rQGpk9+bg4popymz1ZPL8fszNnxYnl5f15acyLjO
aWm/AJtTRZpMf1g54DciJQmXoh6yxpgiv2XB9hYEXXvNOB3zkZYOwNp3AgOZ
Hz5cn//x/DLpxTPzw+3tRbK7v7VljCBtAs+OMQFw+2hntAU69fZW9BP8l+xs
bW0fzyaHx8fux0n3ve3op9Z726T7A+G+kMF5A4g1TMnXhIZj2dc17wtJ+YWX
q8n42DnxrjV3rYgjuXCOmLotoqZ1upHzNTR5vCwMML0Hqm1uFAK0Y59sIyBw
ku2tZJuVsWc5xe8YYQ0f6VnEzt+9iLUjfP8idv/uRawdYd0iyNQM3Dkk6olN
qdnRlJyk2OOEhZPfHj1jxX2XLfrGmJ0RIpjNUIVoQHQEGDdwbmWxp9B4+C5R
4h9bL01oXzSBGnIAOLXlku0BDoIMy5kJsNjdEfo/xFz2plFNqSriSJixnuVU
/DeODXKQVafLJE2SJ2TJC/oRJozZjDRUFjuom4IufJdVdQNL2Bup7SPRAMrV
smpyviEy/QaMaG+oUyngP3rOJm7fkJ99fENANa9HwKEbO0eNLnU4InYVJxQm
H/8tfPPfjxFwHwFodCR+Fv6eDFUWYDwuCL8MM38yji82FLH91lEmL6NJt9dN
us3fb/KsMAWwsVSFFyoFrM6xTy9ZWOtSXkg14Nw4lw8IQskL9yH/SN5dGBik
VFHfqVcF3ufkwVHMqd96Tn3BVvq1Zd+HJWd6ubzHhZDoNOYcCM2mMxSuEYk0
z/Jwed3x7jDlURUjfkIMGThCHEBMKKJkER8M9h9rgzP8t/B9nvgl5dZ3nhAF
r//Mk801PPi/d8jdv3tIYrG92hLRLkPZ60Poz2ItNFkD5W/qLOuWqMKBN/Kd
QqYPKN813hpaDSHixE4NtkTtFT+WISmpLU6pQatdHc9Y+UAscElMR710FC13
amZlwTIs+sGsmVqRpkNzN2q71C6YPpeQLlDfgpm0e5rW6JXr2HbH9/zozMqZ
V0smPpKZW5LLqTDTBzG75SWCw8c1nE8Dx/xSLfHWrsbOjOeG4XAuB/hWcnaS
pxcMoaEcrRiH3lcpvME5KyddxZt8lmcovhL2ovbKOPtlQVOTnIOHtNqIM50C
r1hsb1Lokt9hTEw+w+ljHFpFa0nVYsrCUXZMwU7CUyhWmrrdGlR9eFIRlORl
OiOP3w06mGEq9BCwa4jAw96olueL3eCkSkhRxicw6FBPQToOzeuz89NOIEnf
UZd+5A/IcBQeQepFeiLhmEXr8tWdOM8a4e3kKMWfXGqZshcxcin/KB+isBuy
46VZsauOfb2yVtYKEQDiukFHyefMPsa2oMucpnkQCFQjholQoVORFhE4BySW
CmNSYgEIUOeqD4bAKRH0FZY/uAXKetRGQYuXpZUvtaFzHPR5DQYmcYk2DCdn
c7WQxY3bMdJZzeg1zjEOjBHo6cp5P3ETJ96OxUSnlmXbpj1Ko2rHCjqmejop
sciQ4gbCBPMsrdUq11MPjOpWDqdPJsLSSCFBZIaskQRpoOqXZ9WGJ0OvSiPr
kqCsyxp1Uzo3Hbz2vZEqtxtUw3r9Y4F3VZbqwx6jECASrvjdPggMWOCHb4Cr
J1ZASjyokAXFDOZLGJ0isX3RCfoV1oEZihhu4/OLuOKbJAy2qhsWq1MderFn
+8RXzSQXWDWDeOaDAuL661TGkQut4FWfXLjUUMSdnsRQ8/sSQ6NcTQnaGOdq
ZZU8dUshdoP1eF7P5cS6vf0tnxznqn/ucSOYqgYge0+OelGs+QM6++YWeSpi
J6xigrS7Ghj133vBHK8elkW6dhQ8USokQJkwS7bL34Nl8HYYNS6lhhLQwmAs
nnUETynq1pPBA8zbGb32aRsEjM0B1fv0xaGWhYtCdfOX20GJIMwGm+MDJ6uB
cATwgWwhKWPC2sKo5kjyy9ACXkmWAGVjSAounjmNQvmePpUV2DpyQ+DowsjA
zpGUZR10bm2jDDpL+eQoDsMpJykieVT3i5lGxgd36PibbLrM0woObrasqIDJ
1TcOJHtUnyeBz8EwsyYUNlkJbdPZtTNYrzn6RdB5B+AncRgmtGp4LExppdgn
yjwR6O4sNHArUVtvbJtwRZzIQXIP47dTerZL4d1sa6xcaoULx5yeCpNQFhIm
IGYzLh8s6kcMnOnRpPkj6KeqRneXGAJNFAVdiVIwY/gQyaeVui7hTV8m55Vn
dEZElAz6r51+qqkysxMpD9KI/GBhNSDt2f+ESvjE9uYUI979DcWBOL4sxtMK
KxRCtFGGcc0+NwQmkPaj1g8HS3zEJFmeO3Bc0OJ4JRSp1NGNaJn01gQny4EP
g7iUqkUsWsiomcJK/Fa7W4ec/YIp00tnrwKzDqP0BiwPymAEvePyf59+eD8+
v9R0eU4a0Qz8wFqrm3KxsDPMlYBVT/JV4N7jJEHUyZCRDzywSDJjEdGH0/Ht
OJqDfqpdNgrGaIrSSVbHRynuaJlPY6LH2fUv78bnFwDbbG5hH1KYJm43b1sK
/eqUkk0Bx5CwzsDKji/f6T3d2hWyoJ40QUXchf0Vhp3Iv20l04mHLNZLTTwR
xTQpo5OJVpEg4Faq7rBbFwwFtllxUVOSOyH9eL8/14x0NujeNPBmFIpzegSl
G7W4Tn9RiBEaIRbYl6gih41k3soX6YDJr1RggWTjSTJint0KBx9QDmpBJeZX
Vir5pQZ3btH6zuq5FEZ0JCvQm3XVZOoK1AA50xg7FzPrezUo/xfVprJUWcGu
DVwIWnRTO0PYswA60V4C8ISTr8kpi7ugwczTC83IMOaqrDPSyfClwt6zgsZJ
qTwa2yGc7KBrRc0t4tV1mBUVcBDix2uTRiSKjBaKEKm6Wm5vL1zwMSoIX1Af
BPSwYzIIGziDsH1DFPVXPbvT04HGF7f6LLsjHwQS1km5WHGNiIqOoinXKQFA
Acuc2UCd5ZRDw2XSwIUA/KCYYB1fZKbF5fAOT9DY5UjLwqah+QLrw8xtE7oX
1LWMm7m9QIdKVq26OJeRFjfNSypoMd7TPUMyDiQGd31Ag01R8w0McgcAeKBI
htuw4ayhmloBVaGU15jAiJQ3edmVDjCbB4mkFdZRgZQ41RnLEb1XpE5kxRJm
J8fOHe8xQqC2XoGowQNNRZusjU4c+sZ8lw6PPZQt5tsicBS8qcp8xDme2FoH
haEWLCXI+SQCU9VB9jaAWLL9gdmkb6JqfNWM8d1AuWPaqNekXKGM8EdMWZWC
q8yysLwkpfwhfgRA8QuzOvKBkUpENHR9fXP+R9bjUFnCjPcysipeBxWp2PiI
4hiqorWmkdYRIDa5xF9YOCwU2dsSPhQN+dVmBAfTmmY3noZrjCyo5pjOFHD0
z24nmGMiJQxe/DSpKqaYxUYl9ZbyCZ+eJot06N/++tX4o8OVAjbMckk48o85
Sc/M9IIz8Ml+w2Jhbb+BinwrO590Tm89+BhqKjn+cMBNKsLVF4toqwn0H7dK
EHzBU72cNJha8nxBgYncbknQyYBCWWXgN291ABEplEYtoNAPyqBC1zHKQlK8
61YzJemjNBBt3K3AkwYQnCB2VGwJg2glhVbI9VulmCkGc5ZIDVM3rvcocJ4n
91LAXia4ZGoasyHHN5Tjw41jwkO9IfnOlSi62G2LxNQtlVVRtZZmDXZbr7jF
kTs6RcaSkVBvKnTewAqijMoge891kkCK8EFPmSqewbBiySZVKo4zal9GLlBM
YwtcLlSFGRAdUWwBe0VhrSqda7NCAkiQXnXDpXMS+iUZ3ponPFEao5moO8td
nnFdJe+PLUScxvhpOmtMFdb8EkUsJera7r1hGLZAPw9xjf+Bur/oCDeJ8gPn
2Jb+fLi3FbEA5sB+cQ655yXsohArIZhUcxmjhaBws3gGSFfU8goxM2An5XS6
rOpjKmfg4exMQcKtoQSbX3YZ1iYVl0ZeAPK9qB5bx5m7oxYHcoW5YiC6OkSP
guIvcBKZQc0iVG0ZfpsYF+XMiYDVzi8DaUYTsGzGTuO3AkMRJYYWFUkVAmVt
m4YSmTG2MkFi9y1jjDh87GdshShsUPJBMN4FqgDqMwDIkIVzCiD2hvBBaBP1
t6tVbXN4FtmmJZNEzK1AY+RGayx1cAkSEcfQREFFlrECQT7AgKmD2rKwA0OH
QsZN3oYKpT0AuK40muF+EcqjvHwiUeOPkWW0rlaaCKCuGDAXrTBD5Ym0QRyC
X5lFycFxsCIJGWQSS1CYo0ZXXVM6PkXmkixEEeh+CQdThHxTlVMvIrLCAH5T
tK1hq/2+yH7VDD7HGEUqv5fU5SAX+pp1u6cX69OayVr0byAwHsocK7A4wRkY
xdq+RGHhcrfoaqz11TKS91ly6SsGJRH+gr/HrVZlceUyei40TCMttsIGWwNX
FtNpH8E6lDYsEG+Rzxw3tcQzw9MmlAD6umd+TCzY5ff5B0dm7NND85VLzFlS
/Y2PqkiNDMci+CglGENJJ12NhoqQS03n5p4jCDc4RDrt86JVUhVVQ0m4kapL
XBGBFJyFO+/v/nR0sHe4d0i0Q38euVh/EAF0hV4c8UfKobSuVmomaQ/tHI3e
FBiZ9fxSAMefRw40a3JI+L2j1ntH336P8iy6OTrfN+lz+ST/L7Ilo/V/x+b/
v1h1b3qlGrE+xzJ0m0mEnw6JI/ymlWG5rDELIsiz7Omgsq7QEMOnNHSr2vD2
QakZFvix/cxHR8xhjmdTfnOW70PRW9SeBrHTC+y5MCOICTNMRebMm5D4WwlC
oY7s2rXoPtCo7OklpJHUVhmy4+ruJKRUIuPyB82L00wbyqkTh7ayO0oKIfbe
y/25sQXOuwSxw+DDChFkUfyRCkZI/2Cv/BQ91jkqQ/cPXAIWVadKA78YgrWm
zHNiCyf/A8fUEdmr4AtUBqadk8KmC2X/EL7UnBnE7iufREV7H6g+gA60ZP2m
Hkkf83qLrFc9dqeyOBND1GViiYESaeNFnBQZ6BGGwuwRHOW4tUlHq9uIJj/K
7FmtXWaLTIpYpTBV9WHueuPCkYAPH1TKUVaSGnakp4qeo3vylSouDbS3+wo3
SeEcGVUZmH6zItQKbqltBDZHhqMwMOpyKpTALSZwBdOHDMBPlj6VszjpyRuK
Hg7kuHT6cS0Q0soFNaLcFVxUkN3CUQ7JU1EFImQuqGmCTp1KIFd25xJIdElR
YgY8ZPO7OErepmlNF2IHvzuP0NZW3uK7DStX1NmiGfZ6uQZZV3eKc67RadLH
VrO6hV2CB6MYPNIILhrQA4YjX4BZ6HdkhQ7ZWyJtmWpV7qbLhjRWPqkhOkn1
eOL8F2lpkASj4dicK7OmQCd5Hvg4ryqbs4DC9BQoy4uzm7W6MvUCSTE8Xdgv
A1+p1S31c73HgiQs4byu4IvQfUgTt1xhJmplEG8hMIDEBTONshboxGnBI6Ou
Q+kvqt4/MrA6jT1iZVrxgZvoPKarqJ0fCefLqN8M6OOSPh958MTlE7QHF9fd
r0z+c1Swcci5tozx7QqassyD+BcO/vGHP55dnl2Pb88+ihFCRu6doQ7yT0/a
Xh4LSHE/EqWheEbD8SXPz1udDbKaR8mKxdLFd6RT1mPZsjE0ye279G23aFF6
h6JI/yCD/vD9+kmwa7Dr04JKqtB+UYXDb+8cTa8Zl8+zbchmqJmnDUfUmpIT
HTlJWQ1higFhhw5OrqFzz1Q2cRzE0JnQ+YTthSmhBhB3SRUs7WwasJrH3vWm
DpigGdwVu3WeXnSLGXjvEoSBNQ9h3Ozz+grxrPgsZSlwckpxJo2nJ7eulGUK
LYW+Qd9XT4MHcNC1nXoOe3LR84IGtDCP1axJaZVM1Xg5sDNK6xUdz7R9qRzr
FcEWOCcDEHCrc4H/N+K4pvk9EHUBSzcqMssgLUPj1Thc/xAxB/EbkMpS7fUe
V/NzUCwK5eBzyyL6TsL1dRTV/LFeAyVxH85Tij/NMwK1uPYFIK3gkVvVHJQG
dBQOwlb1xCYV6u38r1Yi1MmFS75FfKOcW8Qp6rNyvy6ySLzM+TF64p0c+mhA
Z9esdFf3M4iijeKSoTfT6SfrvM6OBqSf/u4+Nkq+pxxu0iSAZ99nRRtptUPh
PW2eZc+N0djC2iSjICU6SBJ0KYJvzNnlz+8phs2t7eZ4g0xSTvBhnjj0v/sE
1O3tfVaxPogLqlYxLpl2AlunG1FbC5c2EbfRIoeZNFzWeu8unxDSZYuaPKE+
AYEiIM4ciIM06ptEhj2fo6LJAJWmJ1LPzQUmLHMw6xBD0Qsu2nC7CWfUZ7W4
Z4ZZPciGnR+aNF7NyGbO70zRQNpSovKABZR0ZMSkBpfXSun8NNcbHFBPMcwj
1hSmIGuCKyECBHb5sDUmwIe3YLgpw8RVnZKLAP/QSV/2vfuRH9ARcLWmsM1O
T9WE73Rw36/vgSrdG5yKRzSJ9xms1SdFNPPGo7MnYVIP2ceIrMILBR/iLr0B
FeQ5BozJIUZWBGvgmTlsY79IwYJo9YEXW4oyJJsp9Pg6VgbaYrNEyP0SBja4
wgk1yRmGUztxwG7mMVcNYiYnSBBQ/KSRqwt9UVgU9SAttQiB4Ayv2Acep5zH
6ejtXzel5ijYxiToCAFMuBX2Msb/yC0ygwiGZyLCGlhnJij4MQZGCmdFz+b8
N62jlChc0hOFA/D9i+bdGk3NkKsawgjTZOUS2/TVgaI+h/M0aQJ5W2EpqpH5
DJ8ahqnlDhkOgrUkV2CD7I2OWskSkYmy1/oxakgdYZOt+bPFzojyVzIp75ea
wV3MLKeAppTJiI205TnNg9Icdckn9dFTROEwt4gjzWU7NM55e4KBJlAQoqCq
+JC0Hi5C6CgAbgLnHsqIsA1TYLXKeEKG3DemduHQkenZaJB1juXHOqjfMAbq
+CwnS3ScpBwqh+W+z3hBjoxquQspFfALUFzjLjTESKFTeynlU5G1kFrV8RsF
o5Pe2XBOrztZNAi78CfvGteFUTRMdCOn5ZAbUKrHfPbbI0U9WpwJy9KWBd5o
UzByxxqmMBlHD75fNgcA0bgJIsSJ1yFbaahpR+uRej3KDdc8CYd7miPtmx8r
RL6n8kGUU5yWot6UHlSQEY9DmHiVnftS1ij7TIs+jo45si2EE5l95z6Se0Ph
62TBOOEvuvlKHJvXD6r6UqZepNfiVS7PXy8T5DNiG2LShZyGHm/CuYBIo9OY
fMCHI5TwHJgjB6hvYYrKMGDEuLzuZUGM3Zz6+tnxe5q0KV06RJK1WplR8Lrt
aglcOEFq2V3phYU4bNpB56CYakjFVMkVdgY4F8sS82nbxqbUAYcGSKu4QYsO
A1SKTciVkcTfPqWXBsQphUtKJGkQiQfyT2qbR59vrZayThfosWaK5gGt0Q6x
NGvGTRDiNpwsNMKZ9oOZTJzZHSbbkY6P40npafvOC2+E+xLo2vr+jUwIaxsi
eu8Dd2NyuZJZ1Mf3PCjYRsXTR5A2j9VJ7Mdmr/N3FSsOuJszNvrXls1hVQd3
S1UvtPbs8NWC32yRNdDGsGidiOfbCaggo1Rbg5Scjdxwfn2g/rv8My5bbbEy
BCMagHJP3DAHystbWBj7ewHVtJewIMGmtN5k77xb9fD8NAkrvoM0A73gigQR
Pv6nsuYqOTEOby9uJOPwL+JxRjW7qFtWKa5kN1yJrxMOMC+8ehA/uiqRHF2u
UrH24Iv2ixnXMrPf+ezm5i/nl+e3oCPU1Ory5TpioHtvnoEjPvqNUzddXxdI
Zbk0DUVUy+Lv+K+ou25rjy7kFVWnt66JxCBZbbol5xyTU5PeeRo4PyktKPOJ
cNtB3BCtrwNSsj49N41OjW+L66ZBN2EmljtSvcim69abMV+/4mQn4N+a9uSu
MuuWwLAr6LPFxKuwVMuzlgFHYd21fpl2knG3ILLZzzdCBv1I8UFfimZ+auee
9a2BEmzUdeytfnbVYOIL43DYkS7KJqzE2UF6Ia8Gw6beJesULHXBEKOg3aZY
cKf5YXjZbDs8kgg8iRGnTU2tKOdZk91rsYh6HJyWGJX2YdP4arVgC/XGkE+N
Ck4xxO88TOwIwMaQj5T+71wvCi5NeEOtp9XeIshu5/ZKGCSKsv5inUDS/3zm
X1Z5jKPkvt7gDuPZtZWYI7rml3Mtwqnka6r9l6/RBpZCQk0wmjEjL3y8WtsZ
wIHRoYNZlE2zcknuBziygeHuF2gh04t4JLK3QTJfUny5U5JDhuJA7vrjIoxO
eQdwmihoVKsxPqGWCOjzQgcFahJB42xgfoNvzNjnWzXsA3BFR77Kqos+XIdA
CQdLCw+7nHQd1ft8+FK+8/Hbbt1xIRe5UM4ikW43RQQviMYwV0Op5m+5VtPV
FpZ4kx3aoy57nu6WIgVhgy4M6dziG+R+cyiA787Bm0RjveVSUk5YsnIAM7zb
Rh08hB2xph/cxhm6WPi+ASoAkkfjOzKxS7+7oVbvFa7VnAq77mgpGhVw2u39
PfafcUogeYcHvhScdmy4zagEP3DdZyN4L2mAESwe6NI06WXvM1xnPgMSl9Z2
fr68HF/dXvOtSVQF0BMKO+m5WxkV+D7nIwYHNI+BjxW7z6z80XfwxazHF1pQ
C1mQxkP8kKDGhnzkZtHEaDtH2aqf1HSkIBBq+mesKtdcqCzuS9pbfCdseOs0
5Z5RHUHjO/FFHU6cAooQEeSvObucQxoMADTt4mmiO5ECd05csIt3JyXP3w7a
M3QQ7ne9jF3NmbORo2IWytJl2cmh1+Di7RmHqdf7DxjUnISCUWGaSpNGZVQp
Iui6wv+Wu8RctX8dH8dafzv1TUfXUZgZHt9DxuxW/GssBjKtQWkXuohBz9gg
A/jIinNomjS871a8cdGsjN0S4JW4Vxya4ewxwlcn+rFIea3332tDbUP+Krh7
4jqooEINcF1xVfemdv6x9zaLvkgXRcIBj+HnwnPw7hm4y2NczDdcB5mWRpA5
WE9wRVD73jHQbOKKcgoR+uiV03+krYnY3KgwCEilQDRz7Q2Mu2+8tiBRQZtW
jIvW6hqkcOcQ9h3D/hd5Ou0PCJrIacXZid+CExnrHUU9utN9QKEsCmaHHYBq
uhqQujaFqV66B3UBUYQtSqoK2gnEjw6kmC9O0ULpivE19PsLa2kCVZVXGgPD
hdh4vZpU5AN8uO5nV51Ix0oXt/YTuDqRkgHvVWab15Z91QL1+7ycpLlJ5H6V
QPcI0xU5g5TaGQR3WPGB+T7Rri2ZcekyrtKcy8X0gvg1NW5tP5FR4RDeaCPT
Bt5/4Rtz8ZFRv5AqqzFK9ADUJOikSpl4ZbvDNFRHhTetk6/RRQLAxtJL26ge
h1ljfH1idMuVdu053D14/fXrG9MtZeNfOnfBdosi6YwDxt/v8GR2GkoQV5Hj
TBzj0tMkXNebnvyveEvR0wsvhvHaIuCNGz4XbQO2XgEyLkrK3O6/DYnv52Jp
Z+/SZd4EFRrPXxPoa6M6V0wZZhiEQ2tn5YhAo5fIIF/kED0nkpANp7d/KOA5
X1Ju0QRVLdwtyUx3/dXEGk9N3+JcQaNgUifDGc24b5rxn9kOwqH9vWHeA0Bl
jJ7DGK5Hz5pYyclXfGdhy99NUwTFXmIjpjXX014Ox6en16Px9dVYJKwK5IVc
rqbpAGzG6I0v20fbcG4muGld543cZS5oLGWcHXmSSLUEC5PwakfWgvpOnO7j
cpdihJrmugvhkm2n1eBNd7vtm9Ja1w07/300xs7W0cH26x0dyezsH+7tvt57
/TqROzK4i6Ouoef2uXUlZwdkRL2JruHoXrHdhlxPMHM9ffDlBvlKygtRWSSX
fzHVfv+udFqkoJBwkKL+8pn1yV2xri+xXiIeXx4hNK5ZkFwbQNHzlpnCVyc4
Lu2DBKpP+Dp69jnxnWsNWnpzsVRDJOZaQYnGmRaJaDoiXWPeuA52/1JWn1Ch
+SMc9yJ5iTFh6mJS4jvcuiNSEUnWGADJJjcTepT37+l9du9pXnGY/BDkhPZW
tAmDo5bW04eyrFnIN+j+L+XgicO5/tPr7jyMyuTwfh7/oK+rRK34mftggNQo
Rm37a12A1LYOdg/2tg939ozS3M723sHe4e7+3kHycuvL3hb/50hy68vBO/5v
E4EYrt/A+jGtpr0lujXV39To0A3FebGilnArE3EiJ5+3d/bJQ1iXYVgxqOj1
1wU1mqsdhTLGoj8hw42sTElkDF0urPcZDkhoLQt3GaxKQE6+d+udVmZ+19El
4wHFtFVwib5mVG/cGAcSJpBhybdkmAmtlMtI2Y3HBIE1cXwfhJwTWqZXaAUl
1U4SSySBN8sGnN8rUsVVaCuHyknHRyDOEHcjUsc8Tisb+0kC29dxFg4/YO6Z
c6po3n/bcG9icAi7wJKZlVl7d+lYgb7xI7z6Y3IzBeWVrnrtv5ox6GXxcj05
UnA/2H2fB0Kyf6SxNXyFQS1Og9XsJtY7qRXvXYp9cxWY4b2zZOSFgIh72XTg
FCaxuyvFJ+FRcDPENXdQZ4EUwUNsiLK5OxG2pyFKxEkJ8O5eNnRqcdMQp8m4
zjjwWXORi8CzwNMIIp7l2T31Fernbr5c2C2O+qcFajhMYTLtecVH2E5tBtwH
raUmo1N9voFa+o2mKX3Xa93hVfZYV7RWgLwMHW2k4X/dJCP4++QFB4XXiQwZ
almER+bUot4B36CNvmbFrohbRcTRweHR3q4Gb5mgvc6F1UwCLcZUd9Xcs6Qj
eRxaOzNrd9ARZ1QTFRtyrEFOl6sxQ4M9rkr0/gp0rkuQuBt+RK/A3bJq+No6
54/w9QFe/QluWnO+SUbzHtJvSo8k4ZXgrRu9XlAYi3FrLNBIXRyLvh+m4ffA
cq+VRWKXCCpFGyTLxYz+paNHNSnBQhjJdkZO6vN8uYegsc8RGx1zi264L3/U
jsOoEF5JCJa5SzUEEPuMnACExOiZabq8cBN32A+sXYpSMYf5G/k3h11jctXp
5DjRkVFbTOwwPmsN7wetLHZhVyzUdhRe89UEZwSL36JxPrqUS1grwoCJbR6t
bZUSEtDiUk3m5y8oiB6sOWgVQU7V4LdhcMuYNqCWSkS9ryTwm7QFaFYH14r5
8lJsOxquVJt0uhP2t5lSNg7fvslusr4ogGTVBI2tgn7wZIUIM78H3VIsCoyv
OqxlFtjJMUfR1wLfN5Z6t0TlEe87YD+BpLAGO+CpnrnLcZOypVwRZZf1hHXt
YeVn6/gHBp53wZ+AQik/I3iOZ5FGU+YbxbhYE63SitNbOQ2AG5X0c3yvJRqP
3+0Or5UzVkVl8c1/4+YroSbBfazrGAu1GLsFNc5JlNR9unY1xGNXKoEELb1o
ozpA7q38RcgHwHkdMLxTF9XwEKC+ZViyFGHV84EesRfjeqoqYMiA1QOj3JiZ
IrHjFgNeG2XB1oj9jP9rWEuj+Ss8sZyMWyvWkz9TFlyyuxjtyID34jGRbwL4
zSe7Yi+sCBbHnINtxEFRcggpeGyBuZmaHN+Sq319XMm3xn6otcueaB85pHq/
jDgUE0cVRE9tle97fdU/KhBcW0+Ddq4vSiUnvxBMFHVzwZ9OhUpUkqKVzhL8
4wZoLW0gqO7AMceeLq9ZMHkFISr1uH0I3TOh8CX/4TqVLExWJa20kXkGiXYN
JfRW6ebkoVPg66jdUyiPkZ+uwenNtYFVF70Nkn25pTZ2XUCjV9pwlpTm72Wl
o0b2YtL9Yr56LGyQGqS/4hr8yO2iR9JYArL1xoPV/g7SwV/aLAGg8Z3h5c3w
+uynG6TdKui6hhcg8G0npKBgOVHbfGspX+0VBT2hRub/AkrVj+xGoAAA

-->

</rfc>
