<?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-03" 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-03"/>
    <author fullname="Erik Kline">
      <organization>Aalyria Technologies, LLC</organization>
      <address>
        <email>ek.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="20"/>
    <area/>
    <workgroup>Delay/Disruption Tolerant Networking</workgroup>
    <keyword>DTN</keyword>
    <keyword>BP</keyword>
    <keyword>IPN</keyword>
    <keyword>DNS</keyword>
    <abstract>
      <?line 71?>

<t>This document requests the creation of ipn.arpa, an infrastructure DNS
namespace for the Bundle Protocol (BP).  It maps a Fully Qualified
Node Number to the DNS base name <tt>N.A.ipn.arpa.</tt>, where N is the Node
Number and A is the Allocator Identifier.  A BP Agent can use that
name to discover a convergence-layer endpoint at the destination or
at a relay.  This document specifies an SRV binding for version 4 of
the TCP Convergence-Layer Protocol (TCPCLv4).</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
subject to delay and disruption.  In the ipn URI scheme <xref target="RFC9758"/>,
IANA assigns Allocator Identifiers, and Allocators assign Node Numbers.
An Allocator can hold more than one identifier.  The pair of Allocator
Identifier and Node Number forms 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.  The FQNN determines the DNS base name
(<xref target="discovery-model"/>); the convergence-layer (CL) discovery binding
determines which name and record type to query.</t>
      <t>Discovery is optional.  It supplies candidate next hops, not routes
or contact plans.  The BP Agent makes forwarding decisions under its
configured policy.  Not all FQNNs have public discovery data
(<xref target="publication-restrictions"/>).</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 pair (Allocator Identifier, Node Number), for example (978879,2)
(<xref section="3.3.1" sectionFormat="of" target="RFC9758"/>).</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 name at or beneath the DNS base name that a BP Agent queries
first under a discovery binding.  Alias and service targets can be
elsewhere.</t>
        </dd>
        <dt>ipn.arpa operator:</dt>
        <dd>
          <t>The entity that provisions and operates 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 can use DNS discovery alongside configuration and other
sources to populate its forwarding information base.</t>
      <section anchor="discovery-model">
        <name>Discovery Model</name>
        <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"/>.  In the
two-field text form, the omitted Allocator Identifier is zero; the
DNS name still includes the label <tt>0</tt> (<xref section="4" sectionFormat="of" target="RFC9758"/>).
In the two-element CBOR scheme-specific part, the first integer
encodes both the Allocator Identifier and the Node Number
(<xref section="6.2" sectionFormat="of" target="RFC9758"/>).</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.
Zero is the single digit <tt>0</tt>.  Neither label is padded or split.</t>
        <t>The Service Number is not part of the DNS base name.  URIs with the
same FQNN give the same name, regardless of the Service Number or
the encoding of the FQNN (<xref section="6.4" sectionFormat="of" target="RFC9758"/>):</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 last two rows are usable in locally served instances, not for
public discovery.  The same local scope applies to discovery for
Experimental Use Allocator Identifiers (<xref target="publication-restrictions"/>,
<xref target="locally-served"/>).</t>
        <t>A BP Agent <bcp14>MUST NOT</bcp14> perform DNS discovery for the Null ipn URI or a
LocalNode ipn URI.  Neither identifies a remote destination.  The BP
Agent tests the interpreted pair (A,N), not the Node Number alone:</t>
        <ul spacing="normal">
          <li>
            <t>(0,0): <tt>ipn:0.0.0</tt> is the Null ipn URI (<xref section="3.1" sectionFormat="of" target="RFC9758"/>).
A URI with this FQNN and a nonzero Service Number is invalid;
<xref section="3.4.1" sectionFormat="of" target="RFC9758"/> requires processors to treat it as Null.</t>
          </li>
          <li>
            <t>(0,4294967295): a LocalNode ipn URI identifies a resource on the
local node (<xref section="3.4.2" sectionFormat="of" target="RFC9758"/>).  <xref section="5.4" sectionFormat="of" target="RFC9758"/>
prohibits publication of LocalNode ipn EIDs in node identification
directories, including DNS.</t>
          </li>
        </ul>
        <t>Neither special case applies under a nonzero Allocator Identifier.</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>The BP Agent constructs this name directly from the FQNN.  It needs no
preliminary PTR lookup as used in in-addr.arpa or ip6.arpa.</t>
        <t>The registered service name for TCP port 4556 is <tt>dtn-bundle</tt>
(<xref section="8.1" sectionFormat="of" target="TCPCL"/>).  The BP Agent uses priority and weight to
select an SRV record under <xref target="RFC2782"/>, then uses its Target and Port.
The Port need not be 4556.  A Target of <tt>.</tt> indicates that the
specified service is unavailable at that domain.</t>
        <t>Without a usable SRV record, this binding supplies no new candidate.
After an unsuccessful SRV lookup, the BP Agent <bcp14>MUST NOT</bcp14> fall back to
resolving the DNS base name for addresses and connecting to TCP port
4556 as part of this binding.  This exception to the suggested usage
in <xref target="RFC2782"/> does not affect other bindings, independently obtained
forwarding information, or retained results (<xref target="other-cls"/>,
<xref target="discovery-results"/>, <xref target="caching"/>).</t>
      </section>
      <section anchor="examples">
        <name>Examples</name>
        <t>In this deployment, a fictional space agency offers one public ingress
service for three destinations.  Its Allocator Identifier, 978879,
and the identifiers in <xref target="managing-allocator-ranges"/> come from the
Example Range in <xref section="9.1" sectionFormat="of" target="RFC9758"/>.  The zone excerpts omit
routine SOA, NS, 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 agency chose the destination names independently of the Node
Numbers.  Its two ingress relays are separate BP nodes with their own
Node IDs.  Both have onward routes to all three destinations through
the agency's cislunar and deep-space ground facilities.</t>
        <t>Examples A and B are alternative configurations of the allocator's
zone (<xref target="dns-constraints"/>).  Both use these relay addresses:</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>For a bundle destined for <tt>ipn:978879.2.345</tt>, the BP Agent queries
for SRV at <tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt> and orders the two
relay candidates according to <xref target="RFC2782"/>.  If it selects
<tt>relay-a.space-agency.example.</tt>, it resolves that target and attempts
a TCPCLv4 connection to <tt>[2001:db8::10]:4556</tt> or <tt>192.0.2.10:4556</tt>.
If it cannot reach that relay, it can try the other.  The BP Agent
transfers the bundle over a session that its policy accepts
(<xref target="forwarding-policy"/>).</t>
        </section>
        <section anchor="example-b-service-lookup-redirected-through-a-cname">
          <name>Example B: Service Lookup Redirected through a CNAME</name>
          <t>Instead of publishing an SRV RRset at each service name, the agency
makes each name an alias for the same SRV owner:</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.  DNS resolution
follows the CNAME to the shared SRV RRset.  The agency can now change
the relay selection for all three destinations in one place.</t>
        </section>
        <section anchor="shared-ingress">
          <name>Shared Ingress Behavior</name>
          <t>Equal SRV priorities and weights give roughly balanced relay selection
across connection attempts (<xref target="RFC2782"/>).  They neither guarantee equal
traffic volume nor indicate current relay load.</t>
          <t>The three destinations share relay endpoints, not identities.  Each
bundle keeps its destination EID.  After accepting it, the relay uses
the agency's routes and contact arrangements.  A connection to the
relay does not imply that a spacecraft is currently reachable.</t>
          <t>The agency uses one public DNS view and needs no internal DNS
overrides.  Its records expose the advertised FQNNs, their association
with the ingress service, and the relay addresses, but not the internal
routes or contacts (<xref target="privacy"/>).</t>
        </section>
      </section>
      <section anchor="dns-constraints">
        <name>DNS Constraints</name>
        <t>A CNAME redirects only its owner name (<xref section="3.6.2" sectionFormat="of" target="RFC1034"/>).
In Example B the CNAME is at the full service name.  A CNAME at
<tt>2.978879.ipn.arpa.</tt> would not redirect the SRV lookup.  A CNAME
record and an SRV RRset cannot coexist at the same owner name.</t>
        <t>The SRV lookup can follow a CNAME or DNAME.  In contrast, an SRV
Target other than <tt>.</tt> must have address records at that name, without
CNAME or DNAME redirection (<xref target="RFC2782"/>; <xref section="5.1" sectionFormat="of" target="RFC6672"/>).</t>
      </section>
      <section anchor="other-cls">
        <name>Other Convergence Layers</name>
        <t>Other CLs can define bindings that use the same DNS base name.  For
SVCB, <xref target="RFC9460"/> and the applicable binding govern AliasMode,
ServiceMode, parameter compatibility, endpoint selection, and fallback.
SRV rules do not carry over: in ServiceMode, an SVCB TargetName of
<tt>.</tt> denotes the record's owner name in the response, not service
unavailability (<xref section="2.5.2" sectionFormat="of" target="RFC9460"/>).</t>
        <t>A BP Agent need not query for every CL it supports.  This document
specifies no order in which to try them.</t>
      </section>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <section anchor="discovery-results">
        <name>Discovery Results and Failures</name>
        <t>Discovery succeeds when a BP Agent obtains usable connection
information.  A valid DNS answer need not contain a usable candidate:
the discovery binding and the record-type specification determine
compatibility and candidate selection (<xref target="tcpcl-binding"/>,
<xref target="other-cls"/>).  A candidate is an endpoint at the destination or at a
relay.  Discovery does not guarantee current reachability, acceptance
of a session or bundle, or eventual delivery.</t>
        <t>Negative answers concern the name at the end of any alias chain
(<xref section="2" sectionFormat="of" target="RFC2308"/>):</t>
        <dl>
          <dt>NXDOMAIN:</dt>
          <dd>
            <t>That name does not exist.</t>
          </dd>
          <dt>NODATA:</dt>
          <dd>
            <t>That name exists, but has no RRset of the requested type.  The
response code is NOERROR; the answer can still contain aliases.</t>
          </dd>
        </dl>
        <t>A SERVFAIL response, a timeout, or another resolution failure gives no
answer about service availability.  None of these outcomes makes the
FQNN invalid.  Absence of one CL's records does not rule out another
CL's service.</t>
        <t>An unsuccessful lookup does not invalidate independently obtained
forwarding information or require deletion of a bundle.  The BP
Agent's existing policies govern retries and route precedence.</t>
      </section>
      <section anchor="caching">
        <name>Caching and Operation During Disruption</name>
        <t>Resolvers cache positive answers (<xref target="RFC1034"/>), negative answers
(<xref target="RFC2308"/>), and resolution failures (<xref target="RFC9520"/>).  A negative
answer to a refresh is a completed lookup, not a resolution failure.</t>
        <t>A BP Agent need not repeat discovery for each bundle.  For a retained
candidate, the first TTL to expire among the RRsets used to obtain it
limits its freshness.  These can include alias, service, and address
RRsets.  Copying the candidate into a forwarding table does not
refresh it.  TTL expiry does not require closing an established CL
session or deleting a bundle; refreshed data informs later connections.</t>
        <t>If the BP Agent cannot refresh an expired result, explicit operational
policy governs its continued use.  Endpoints, aliases, or administrative
control may have changed.  This differs from a resolver serving stale
DNS data under <xref target="RFC8767"/>.</t>
        <t>TTL expiry also differs from signature expiry.  DNSSEC validation
checks the RRSIG validity period (<xref section="5.3.1" sectionFormat="of" target="RFC4035"/>); the
signature expiration time limits the TTL of authenticated data
(<xref section="5.3.3" sectionFormat="of" target="RFC4035"/>).  Retaining a candidate does not extend
that validity period (<xref target="bpa-validation"/>).</t>
      </section>
      <section anchor="locally-served">
        <name>Locally Served Namespaces</name>
        <t>Local discovery under <tt>0.ipn.arpa.</tt> or an Experimental Use allocator
subtree (<xref target="publication-restrictions"/>) requires explicit DNS
configuration.  A resolver can serve the local zone itself or send
queries to a configured server for that subtree.  This document
requests neither automatic resolver behavior nor additions to the
IANA "Locally-Served DNS Zones" registry <xref target="RFC6303"/>.</t>
        <t>The signed public hierarchy can authenticate the absence of a name in
public DNS, but not 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"/>; for nested anchors, see
<xref section="5.10" sectionFormat="of" target="RFC6840"/>).  The trust configuration belongs where
validation takes place: at the trusted resolver (<xref target="bpa-validation"/>)
or at a BP Agent that validates independently.</t>
        <t>A deployment can accept unsigned local data under explicit policy;
that is not successful DNSSEC validation.  Administrators should scope
local resolution and trust settings to the relevant subtrees, not to
all of ipn.arpa.  Queries should stay within that scope even when local
resolution fails.  Public fallback cannot supply the local data and
can disclose the queried identifiers (<xref target="RFC6303"/>; <xref target="privacy"/>).</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"/>).  Each identifier has a separate name
under <tt>ipn.arpa.</tt>; DNS has no numeric-range syntax.  An agency that
wants to keep discovery records in its existing zone can request one
parent-side DNAME per identifier (<xref target="provisioning-alternatives"/>).</t>
        <t>For example, the agency in <xref target="examples"/> also holds identifiers 974848
and 974849.  The <tt>ipn.arpa.</tt> operator publishes:</t>
        <sourcecode type="dns"><![CDATA[
$ORIGIN ipn.arpa.
$TTL 3600
974848 IN DNAME 974848.space-agency.example.
974849 IN DNAME 974849.space-agency.example.
]]></sourcecode>
        <t>The agency publishes both sets of records in its existing
<tt>space-agency.example.</tt> zone.  Neither DNAME target needs to be a
zone cut.  The relay names below are relative to the agency's zone
(<xref target="relay-addresses"/>).</t>
        <sourcecode type="dns"><![CDATA[
$ORIGIN space-agency.example.
$TTL 3600
; ipn:974848.2.345
_dtn-bundle._tcp.2.974848 IN SRV 10 1 4556 relay-a
_dtn-bundle._tcp.2.974848 IN SRV 10 1 4556 relay-b
; ipn:974849.2.345
_dtn-bundle._tcp.2.974849 IN SRV 10 1 4556 relay-a
_dtn-bundle._tcp.2.974849 IN SRV 10 1 4556 relay-b
]]></sourcecode>
        <t>For <tt>ipn:974848.2.345</tt>, the BP Agent queries for SRV at
<tt>_dtn-bundle._tcp.2.974848.ipn.arpa.</tt> (<xref target="tcpcl-binding"/>).  DNS
substitutes <tt>974848.space-agency.example.</tt> for the matching suffix and
continues the lookup at
<tt>_dtn-bundle._tcp.2.974848.space-agency.example.</tt>.  A DNAME redirects
descendants of its owner; it does not redirect the owner itself
(<xref target="RFC6672"/>).</t>
        <t>Distinct target names keep node 2 in each allocator space distinct,
even though both use the same relays.  Using the allocator number as a
label is a convenience.  If both DNAMEs had the same target, both
queries would reach the same SRV owner.</t>
        <t>Tools such as BIND's <tt>$GENERATE</tt> directive <xref target="BIND-ARM"/> can abbreviate
repetitive zone-file entries.  They produce ordinary DNS records.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="forwarding-policy">
        <name>Authentication and Forwarding Policy</name>
        <t>DNSSEC authenticates DNS data (<xref target="dnssec"/>), not the live session peer.
The CL specification and configured security policy govern peer
authentication (<xref target="cl-peer-identity"/>).</t>
        <t>A BP Agent uses DNS-derived forwarding information according to its
configured forwarding policy.  That 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
bundle transfers to an endpoint an attacker selects.  DNSSEC
<xref target="RFC9364"/> provides data origin authentication and integrity, not a
guarantee of service availability (see also <xref section="7.1" sectionFormat="of" target="RFC6116"/>
on ENUM).</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 includes every RRset used for discovery,
even outside ipn.arpa: aliases and redirections (CNAME, DNAME, or SVCB
AliasMode), service and connection parameters (such as SRV or SVCB
ServiceMode), and addresses.</t>
        <t>Signing ipn.arpa (<xref target="creation-of-ipn-arpa"/>) does not authenticate data
in delegated zones or external target namespaces.  Likewise, validating
a service RRset does not authenticate address RRsets supplied with it.
A CNAME synthesized from a validated DNAME needs no signature of its
own.  The validator checks the substitution
(<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"/> distinguishes secure, insecure, bogus, and
indeterminate RRsets.  Insecure means the validator has established
that no chain of trust reaches the RRset from any configured trust
anchor, for example through proof of an unsigned delegation.  An
insecure RRset can still have signatures.  Missing signatures where
a secure chain requires them can make the result bogus.  If the
validator cannot determine whether to expect signatures, the status
is indeterminate.</t>
          <t>A BP Agent may not know the resolver's validation result.  A missing
authentication indication does not establish that an RRset is insecure.
The BP Agent's configured policy governs acceptance of insecure results
and results whose status it does not know.</t>
          <t>A known validation failure is a failure of that discovery path
(<xref target="discovery-results"/>).  It should not trigger automatic acceptance
of the same data through an unvalidated path.  The BP Agent can still
retrieve DNSSEC data for independent validation.  For local trust
configuration, see <xref target="locally-served"/>.</t>
        </section>
      </section>
      <section anchor="cl-peer-identity">
        <name>Convergence-Layer Peer Identity</name>
        <t>For TCPCLv4, <xref section="4.4" sectionFormat="of" target="TCPCL"/> specifies session security.  In
Example A (<xref target="examples"/>), three identifiers have different roles:</t>
        <ul spacing="normal">
          <li>
            <t><tt>_dtn-bundle._tcp.2.978879.ipn.arpa.</tt> is the SRV query name.  It
comes from the destination FQNN.</t>
          </li>
          <li>
            <t>If the BP Agent selects <tt>relay-a.space-agency.example.</tt>, it resolves
that SRV Target to establish the TCP connection.  When policy calls
for network-level authentication, that host name is the DNS-ID
reference identifier (<xref section="4.4.4.2" sectionFormat="of" target="TCPCL"/>).  If the TLS
client sends the server_name extension, it uses the relay host name,
not the query name (<xref section="4.4.3" sectionFormat="of" target="TCPCL"/>).</t>
          </li>
          <li>
            <t>The relay can supply its own Node ID in SESS_INIT.  The DNS-ID check
does not authenticate that Node ID, and discovery supplies no
expected peer Node ID.  <xref section="4.6" sectionFormat="of" target="TCPCL"/> specifies how to
handle absent, unexpected, or unauthenticated peer Node IDs.</t>
          </li>
        </ul>
        <t>The bundle's destination EID remains <tt>ipn:978879.2.345</tt>.</t>
      </section>
      <section anchor="privacy">
        <name>Privacy</name>
        <t>Public records can associate destination identifiers with services,
relays, and addresses (<xref target="shared-ingress"/>).  Queries 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"/>
discusses resolver selection and encrypted DNS transports;
<xref target="locally-served"/> covers containment of local queries.</t>
      </section>
      <section anchor="resource-consumption">
        <name>Resource Consumption</name>
        <t>Traffic for many distinct FQNNs can consume resolver, memory, and
connection resources.  Implementations <bcp14>SHOULD</bcp14> bound outstanding
discovery work, retained discovery state, and connection attempts,
for example with resolver, queue, and connection limits.</t>
      </section>
    </section>
    <section anchor="iab-considerations">
      <name>IAB Considerations</name>
      <t>This document requests IAB approval for ipn.arpa as an infrastructure
namespace under <xref section="3" sectionFormat="of" target="RFC3172"/>.  The two 32-bit components
of an FQNN, the Allocator Identifier and Node Number, determine the
DNS base name for discovery (<xref target="discovery-model"/>).  The precedent is
e164.arpa: an ENUM client derives a name from an E.164 telephone
number and queries it for NAPTR records <xref target="RFC6116"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="creation-of-ipn-arpa">
        <name>Creation of ipn.arpa</name>
        <t>Following IAB approval under <xref section="3" sectionFormat="of" target="RFC3172"/>, IANA is
requested to add ipn.arpa to the arpa domain for names derived from
FQNNs (<xref target="discovery-model"/>).</t>
        <t>IANA is requested to arrange ongoing administration, including request
processing (<xref target="allocator-dns-provisioning"/>), as approved by the IAB.
The ipn.arpa operator provisions and operates the zone; IANA need not
operate the authoritative servers itself.</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.  For the
recommendation to operators of delegated zones and other namespaces,
see <xref target="dnssec"/>.</t>
      </section>
      <section anchor="publication-restrictions">
        <name>Publication Restrictions</name>
        <t>This document excludes two sets of names from public DNS discovery.
The restrictions do not change any allocation or its Bundle Protocol
semantics under <xref target="RFC9758"/>.  At or beneath each restricted name,
they cover discovery records, NS delegations to servers that publish
such records, and CNAME or DNAME redirections that expose discovery
data elsewhere in the global DNS.</t>
        <t>The public ipn.arpa zone omits these allocator names and their
descendants.  Queries for them receive ordinary DNS negative answers
with normal DNSSEC processing.  For home.arpa, an insecure
public delegation accommodates validators without local trust
configuration (<xref section="6.2" sectionFormat="of" target="RFC8375"/>; <xref section="7" sectionFormat="of" target="RFC8375"/>);
this document requests no such delegation.  See <xref target="locally-served"/>
for local resolution and trust configuration.</t>
        <section anchor="allocator-zero">
          <name>Allocator Identifier Zero</name>
          <t>Allocator Identifier zero denotes the Default Allocator
(<xref section="3.2.2" sectionFormat="of" target="RFC9758"/>).  Public DNS discovery for its FQNNs is
outside this document's scope.  A populated <tt>0.ipn.arpa.</tt> zone
<bcp14>MUST NOT</bcp14> be published in the public ipn.arpa hierarchy.  Local
resolvers or servers <bcp14>MAY</bcp14> serve it authoritatively, as with the reverse
zones for <xref target="RFC1918"/> private address space
(<xref section="4.1" sectionFormat="of" target="RFC6303"/>).</t>
          <t>The restriction covers assigned Node Numbers as well as Private Use
Node Numbers 1 through 16383 (<xref section="3.4.3" sectionFormat="of" target="RFC9758"/>) and 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"/>).
Public support would require administration and delegation procedures
for existing assignments and a way to handle private ranges and
locally served 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.  Independent experiments can reuse these identifiers
(<xref section="4.2" sectionFormat="of" target="RFC8126"/>), so no single public mapping can
represent them all.</t>
          <t>For each Experimental Use Allocator Identifier A, a populated subtree
beneath <tt>A.ipn.arpa.</tt> <bcp14>MUST NOT</bcp14> be published in the public ipn.arpa
hierarchy.  Local DNS resolvers or servers <bcp14>MAY</bcp14> serve names beneath
<tt>A.ipn.arpa.</tt> 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 each provisioning request for <tt>A.ipn.arpa.</tt> to the entry
for Allocator Identifier A in the "'ipn' Scheme URI Allocator
Identifiers" registry
(<xref section="9.1" sectionFormat="of" target="RFC9758"/>).  They determine the request interface,
storage format, and presentation of provisioning information.</t>
        <t>A requester can seek DNS provisioning at assignment or later.  An
allocator assignment remains valid and usable without a DNS entry.
Only Allocator Identifiers assigned for operational use are eligible
for public provisioning.  This excludes Allocator Identifier zero
(<xref target="allocator-zero"/>), Experimental Use Allocator Identifiers
(<xref target="experimental-allocators"/>), unassigned or reserved identifiers,
and the Example Range, 974848 through 978943
(<xref section="9.1" sectionFormat="of" target="RFC9758"/>).</t>
        <t>The allocator's authorized DNS administrators manage node-level records
and further delegations.  Neither IANA nor the ipn.arpa operator needs
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>A requester chooses one parent-zone configuration for <tt>A.ipn.arpa.</tt>:</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 parent-side DNAME cannot coexist with a delegation NS RRset or its
DS records at the same name (<xref section="2.3" sectionFormat="of" target="RFC6672"/>).</t>
          <t>One request can cover several identifiers in the requester's
allocation.  It specifies the configuration for each identifier;
each allocator name has its own parent-zone records.</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 child-zone
operator coordinates signing-key changes that affect a parent DS
record with updates to that record.  Support for DS does not require
every delegated zone to be signed.</t>
          <t>DS records apply to NS delegations, not parent-side DNAMEs.  The
ipn.arpa operator signs a DNAME as data in ipn.arpa.  Authentication
of data at its target depends on the target namespace's own chain of
trust.</t>
        </section>
        <section anchor="request-validation">
          <name>Request Validation and Allocation Review</name>
          <t><xref section="9.1" sectionFormat="of" target="RFC9758"/> governs numeric assignments, including
Expert Review.  The ipn.arpa operator checks DNS provisioning requests
under its published technical procedures.  IANA's requirements for
delegations <xref target="IANA-NS-REQS"/> provide background for NS requests;
<xref target="RFC6672"/> specifies the DNS requirements for DNAME redirection.</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="RFC9520">
          <front>
            <title>Negative Caching of DNS Resolution Failures</title>
            <author fullname="D. Wessels" initials="D." surname="Wessels"/>
            <author fullname="W. Carroll" initials="W." surname="Carroll"/>
            <author fullname="M. Thomas" initials="M." surname="Thomas"/>
            <date month="December" year="2023"/>
            <abstract>
              <t>In the DNS, resolvers employ caching to reduce both latency for end users and load on authoritative name servers. The process of resolution may result in one of three types of responses: (1) a response containing the requested data, (2) a response indicating the requested data does not exist, or (3) a non-response due to a resolution failure in which the resolver does not receive any useful information regarding the data's existence. This document concerns itself only with the third type.</t>
              <t>RFC 2308 specifies requirements for DNS negative caching. There, caching of TYPE 2 responses is mandatory and caching of TYPE 3 responses is optional. This document updates RFC 2308 to require negative caching for DNS resolution failures.</t>
              <t>RFC 4035 allows DNSSEC validation failure caching. This document updates RFC 4035 to require caching for DNSSEC validation failures.</t>
              <t>RFC 4697 prohibits aggressive requerying for NS records at a failed zone's parent zone. This document updates RFC 4697 to expand this requirement to all query types and to all ancestor zones.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9520"/>
          <seriesInfo name="DOI" value="10.17487/RFC9520"/>
        </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:
H4sIAAAAAAAAA61d63Iby3H+P08xoVwl0QVAvIk35QaRlMMKRcmkjh0nlTIX
wJLYaLEL7y5I8dDys+RZ8mTpr7vnsoulrBPnVNkCgcVcevr6dU9jOByaJmvy
9NhufJ6nNlsWo6RaJvbfyyK1STGz558u7enltf24TKukycqi3jDJZFKl9/QV
fDgrGzu++jTeMNOkSe/K6vHY1s3MmFk5LZIFjTyrkttmmH4ZzppiSDMMMcNw
a9fUq8kiq2satHlc0oPnZ5/fW/vCJnld0uhZMUuXKf1f0WwM7EY6y5qyypIc
f5yP39E/ZUWvrj6/3zDFajFJq2MzozUcmyktMy3qVX1sm2qVGlrrrkmqNKFR
N8xDWX25q8rVkv46TfPk8fVpVlerJXZnP5c5bbRo7GXa4MGsuNswX9JHej07
NnZoTz9f4p93n/D/RAB+7/La3KfFiqa29pcNba3sfQMvF0mW00ui0z9naXM7
Kit+Iqmmc3p73jTL+vj1azyFt7L7dOQee403Xk+q8qFOX9P3X+N7d1kzX03o
m+mXPCvofT6I+BTwVE4kq5tofHl6JN8eZWXP9173nulo3izyDWOSVTMvK1CL
hrf2dpXnwglnVfbF/itG5w9o3UmR/cxsdWzHSf5Ix2s/p9N5UeblXZbWA3tx
ccLPpkKb9Atv+Z/v8OdoWi6MKcpqQUPcM/Gv3p9sb+3u6cudg8Mdfbm7feBe
7m3tvtGX+/v+3aPdffe1o739Lffy4M0hXn4++XRycczvbB/sGZMVt91pj7YP
3bS7W+7l/vb2vnu5u7XrXh7uuQkOwgOH2zv+5e6BW+Lhwf6BW8zWgXuAVrHt
Xr7Z4cHenV+eDsdXH46ZXk6q8a49suPZIiuyuiEZJqG5Sm/TKi2mqf2QFCuS
KP6KPzb+b4jjIZksmrQq0sZeP9ZNuqjtCclWWTXZasEPssDZWxJZOdMmqe5S
4ibHTBOS4qMRid6smaekEmowVFq8Fq57PZ0nS5pgl1mHBjgfX46Hl9fDq7Pf
Xrc3wmyRTZPcVumfVlmVLkgv1JaOQReeNXwcFqxm67S6T6v6exujmX5oBw8P
D6MsKRIWs3maL19jBplgGK/FGDMcDm0yAZmnjTGf51lN+nG6wse8bNpybYkQ
dkoUYaVQ3nqlOyCFa4mxqoQGWE2bVZWyZuHplgmdFjaLb79bFbM8tZ+qsimn
ZW5fvfu0OSLiNaRBlrVN7HsSuUf7Wzra7DZLZ+aynKX2knWkbUoeA0p9ktRK
r5vL0XjkFjK6GdiHOXGIvbSZrBcDGB0AZmHsPhjneTllpjqHosZ0FS1lTArS
ju+w7yntakXzNPOk4b1gBbOsnpb3GMySsqYXd2DHIWlMeo90/rLM6KtJw3PM
iGxZofSqDL2bEDXpWZqoTeN6mU6xhBqkvL76nQX7kZ5lyoEhMMQeEd1gXBJq
sLOf/YJnD1Rlob/f2xzJwS6yGVHdmBcQiqqc0RHRcDjm/hOxT08qqd++2Xq1
XJLY1LTdxWIFRubtZIUtxBrUMIf/lU4bJg92x4SeefuBAy6YHnRO9qerc1tP
58R5Og0pqm/fBgZsbRMyqndF3Xs49UAO0H1U69M24pF6ZMZF9G0c4bzMZ3ZR
VnyQdA7kH2TxiYMKyySrwNH+mybMy7PGfAgF2sOrrWdevf/t5SXo3+GnL0X5
gCNmByTijgeyWeWq4c9x7Amz+awka1EY2mc5zUjaZ/yczeg0ErdS3YF3gILQ
LavynnZKzxqcHc1Sk4poMLxwKXjL8bMcGlm4LzVPnQS9i/U1pfEzKt1Zdejs
2C3thxQifSut1+XUvHp68lMNF0Sp/Nu3zbeiUtbk6NXJxWa0MpUFE03wMM+m
c9EAWHeVTsnNYY8EXEj6qnok4p/6IUjWSmbGJBd9A7bOIW90KrMMqpT4+WtD
3LIkRivINyRviDS9AReRn0d60S7zpHA79qe6SL6krM0fkooldkaSDHGtLYkW
bYZOC37dbXZHenFGpM+zKRTAJc1BNGXa1XaekAVYrib0YbRzWlcC0skHfBSk
uelUMhbhmmhI2yTBZm1Q8HtMkNP0lo6P/xY5J0/QwhWs7caHn64/wxXFv/by
I78ms/XT+dXZKV5f/8v44sK/MPrE9b98/OniNLwK3zz5+OHD2eWpfJneta23
zMaH8R82RHY3Pn76fP7xcnyxAf3RtDRgUvHRTYiVYbmXVQp+T2o69XpaZRP6
g77z7uTT//z39h6pjr+Dv7K9fUQqSv44JP+G/iD9X8hsZUHiKX8Smz2aZLlM
kwqjgOzTZEmGN4dWqW09Lx9IU5DlIHL++j9Amf88tn8/mS639/5R38CGW286
mrXeZJqtv7P2ZSFiz1s903hqtt7vULq93vEfWn87ukdv/v0/wZ21w+3Df/pH
0zX5ZPZEiG9LknrWSBA94vOqXMR6+5g0XI+uPjbkFtvdneEko8EKqAs+P4qz
YMjJoAYd3DXHbG6tKhmwQFuxPj1dp8z8dne0A53t1wJRiB79ZWsgxYmvZoVT
SQ20AdlbC3UdVteaf3dt/r9uE7Asb3Je9RFvEH9rc8BqOv2aLJZkp18dHRwe
HhwNdjZpYe21jLbXVnNNvl42bRGk+BFS1Po9Gljo0p3szdpUatqF6LDxSsmX
9MHLyOiL9mWNmrGuEtsBeU2srpdm6zntzpQWe3EOBfErdAUNQXr5TL0weOXB
ir86Oz/dhB2gKTfwPfp7I55gfU9tmZhBpfaLBUlBy9q5M8abbKMmaUFu8zxY
aaZ5lZKWqzkaUDoIndcNZcuWqTl0k6jrOPVuOXsO/mlwD3yekwshfbQNmo0t
pfgMg9iK0l/kPkxTEkLaZLXKU3W/KNzIJ8n0C22JTFZG/od53pdVXxW+qHdo
aX/NdDnNh/qG7O7kYuj2Ea3JbVHsfAPYxFFyPRJgkibBMGMYWgQt7zar6kat
cbLuV4CV8iwRw+lYX4Ipdg9oThokpTDrQS2EP8aSwaWycgsFtzWPshR2v2pv
keVRJYof4OeyUOFygdWwvPW4hNCGrfs0XUIdRXCWfXoxlffxldK//23N6UQQ
02aKJC+Lu5pk3jrPRLiHF0oLrExdrqopVluSx7JcIeplvzNydDyUQF/EMWCp
L2zg0w9gXlpll52NeZfewh8H2sUBY/B4cZKD+BTZ8i6TqhZHz/sGphtfOVVA
PKLSbZMp+JmltIyNlg9IDAUwQ+JUChBY3WM/7CzYcpE18D/69DOUyM9pVbL3
aryM01LIrciKab6a6THnyYQocLN1E+uZva6e0eAIa0lzjsjtybuPV6owg1wQ
FRpZnTC06m9DjnOJGSelykXvokE9FxCrejXRqvZ7jOl7GqF3rPFaTHQ56JFI
nJ2ZkBSbv/zlL6YVqPM75iwhJ55mvdTQnA+bPECvGJ1WhxbKHT3VeDALkm/t
7Rkc70WS2/skXxETrVh1ja9Pzs+J8+/AvC7KytOE2QKnmFLM+O/0r8MFdCr+
Bo4OnnqaQSZ0enpumcxmNCERpaYgohmJi922tngOYQRODXtcIw8NTPwqi2JO
qkEztoZ3gIN4MXhLZKJK70juSA/XbrTOfBS0NqyCiBuwOX2KB2wddIcB6Xj+
7KXnz50j/LP583A45P/RUzf02LF4IKOd0e7emxv6ws3OSN8KMIxdf3rrrz+7
vb97uOeHlb+2ep/cGv3As0/HgsH9w8aZek/Y2zvs7RIGb+ObnFuekDCR9FmA
0ByHrOpkkrMzCOaHR8eoGdQPhdCkczVEJH1hujGbxod8cvxtkmNSzjbReDPC
kNg4m7OvpLoziD09+1PdL761/W4UODBPT7rUoSxVJHjcUaSIGWg26LkeN4HV
wwpKLOjSxFxgXJZ1fTuSiJbXWKWLsmkpZR8rG1lD42HEOMZTT3hwuSlU7Wgp
NlZQIr+2r7YGW5vHjgW2wFMO5ouX3XJV17xiqw6qyh0NEHmgRVlAKfTIclaQ
Xslmb+n78fB7nQkcyFs7/wlAFZBLmHfSV9BnWOxI97O3c7R3tH+wc/SGNpbY
NWJ3SSx2GZ65OHDCYhy7vGqvq6vP43W/6SgBGoiWO88m0JIRm+Gh9pLIrtYM
/vEbujZ5mAaZ0c6nSHZBQsQUQhURqyE2U6Zhg5YgAq+DWDjvzB1ALzzLDoZz
KIOj8U5dy6cXbc+y68EHx9SN8fTEr+jYgiQwXwCCFXe4Nuw5ICNDjymwG/z/
5xxXNnB/RJJpwgjr6I+0tlGPDWyBSd4jqoUzWQcLUUkJcfDtdLp480WazmBn
DMlSni1I7mgFnz5fEV+UX1ZLcBvHRhkQ2yGZrUodV3hJ+7oOXgPZl6wmoUyD
D8yzQzEAbwYIbPfevNmHMNyEjd3EXsShSIMSdbOLlTGssKwy5DwEcHxIs7s5
kGNTk+8zbRz8raGIcEV0AOxmFDIQePUzu+k81Cda4Ii3gldMGVYn5E9g2Yzt
6+O0xBsyEWCTqfrkcrDGsUggQgbeTO6RuoRN4Ofo/wSaJdr9Xn2KxFmNsPyB
HKKLfDzkWJS0uoeAPI7M+LZhFw3B+WoKtXG7ynkkOUfxrtZ1OaIxy+EYURDK
Ib9nd3fNFeNsE50+jZxKPEKsVqTiepN6cids+ISTOnJbwg5c1iL9iqhDYGFx
U1Z3d6TaiWpEg7vUELfFQjMrU/GFkttbnDFHGG5QVhQ+X05cXk7g3aUz0x9q
cPKcDAc/A4W4yhu2jjzqcJqrOQxRhz4D5qEwi1xOH3WSNlHXANGUYiwIoM4d
Opku8/IRygNBya3YW5h0BtgTYNa0YNoVKXkE2eoM0ASgtHE8JMa1SlvGsWYJ
7s91DKziPMa57VnkCjB5F0mR3NFEQ4/LD6ukoGMggk9LHLlqC+O8nyt8LF92
8nrUsV4qsIhK+ZSrJS0QsZABGg688PrjeGAvrwUMIB67PjtxinIER5JtKXmR
UWT2HZ9S/UqHam1v0sNaWWFDRGunCAUqdvSe8R8DLoYRKFwclhUZM/nSc06n
+9IuvpSTlFfDPGGNQ1/a7f1Sj08ZnajzKJUxpvOyTtcSgQy2dHn+tpusdNwB
v1TZSVKH4qHWKQkoYnLSCQVHfy6MQCLroRAglGw1DfMOcSHnF8oCAqWZDQgv
1Mc6Y+KtcnU353hC9vKSDiGrmUaS3UvT5VCkAGUjDAxNM4qFMsRTxkuVRIrv
eM1Jjoy85LpbsIOPaDwrv6wN8yDAsKIeilkkiW9qsSq8JcnNUpwohAn6Tayv
pW+aX328Ov/N+aUI7FD2MlJBH5lfff58YXf3t7aM4SGGiaVnx0imbx9RyEJh
y/ZW6yP6z+5sbW0fzyaHx8f+w8n697ZbH3W+t822n5jphQ7uVbNy1xXvaCxv
2ysRMLDXi6Cz7PjY+6n6hENdx4GQXBGlbBm9y+T1MCyHk8HlEcgZwXnEFj1U
7UpITNA132cbhMAk21t2WzwJ3fyo/3R+fITJMyOsD7HzNy/i2RF+fBG7f/Mi
nh3huUWwqwk8J7Eyjp4smVCc9Xpg3/E4HJiKhzEveUA366TpUZmMKFYzmC0F
uUQugvdT9+B04jhABd4iZhLfsDY33yUTrTlrrHhB3qcL/mHSNOmC7JlJvPvv
fCDxZG7+I5bs/zwGWW/gbdwEZSBvjoysi/bAmWIWFYX0aYED/YyCvkdBE+Ga
dJxhQwqtqG8dYfRUtLSkTsUGSmoGMRlnjUGpFFsgvRi8o6F86FyaoB/eBf1w
IeHAVSrBRDpzOp4mO7kcfziDz0MeXDKDLmY3pp4zLCv++NVVnXJZC281DhCE
UeQojCTD+RnNzZPSAbTu4AWGRTAg2ShkpP4fVAov377iEqi1J9R09jOM3XxG
vP9/h9z9m4f0gaI6Fno+ijLX8wRRWzgmBHvw2x4KVvP/F3P43BKd3pGN/KD+
6iPKD433jDaLKeI1VE3OVB14TGLxhC2it5ckgnBFWUWsGLKQQF6+J0fkQpoO
UVV6nWeXAAGhEG4On5r9JNFqoqkguhxx9btXmVQhLXPam4rstUx3rlR5p8k1
ikpkIUOlF3kAZ39aJRIbaiSdaUQnsXQt6DELN3mWkyQHYDnrrs8k06qs61gF
OgUJr8vrYI3hHyliFfTmbpWgFpj2lGIhUGO3AD/uiaQAq4EsaFxtp6uqkgpC
zJ2XyUzBhh6i8D71SVdHpzCrxD7sWlqLnIFRbfmFvFDBAWIH++z8FMG+hNSs
MCVVIJpKZgCA0HZv1SnW0JjrfZKKIypX6DTu2AvEVjKaD3Az4rNHl4lk3p2i
3hgggtKCPmZzAahg1BJqxjSiIBKcep+lD7wkh/MIcIoQFAWWsBYVSrw0WHDu
W/p16SKPZEbPNBkwIC40GmiM4GrKwAoudPCBhur3gU8adRzsAZmrxmO1bklG
SRgqpgS1rrL7JJgn3tdJcOiRIOy4+MCtRRgrtVe1FPOoVqNzZevSAjxDAgt1
1C6x5k1hJOGoAVAYD6hxbMz4lOWppDG9geNDucoFWHKL896zYDVhDKMoFnsf
sR1Vv2Fapl+z2leLst4K23NZJT8wax1RWM5qg9aneCEpTZAdRbgDnc44vIsl
l8sfgXstVjQpB4R6op5xHLolhl3TZaY9ld836B6rirctgNkBC6hU92f/kRcS
la5aLl0FEwT4xhh97ELS71Kx4PEiWaEGf0K0bl6NHF1z/buTdwPN+u7tbwG7
VWZmyHnKWJ2D5u4gSYWUASBtPXClM/wHwDAaGPpkWi6WJDQThLrk5/mCX69X
21USI8NRFconSEkw10xJqzyyn3cMQ9CaB6dGy1aY8pL54dbgyEgDlq54QA7r
ZUsUNO6jw1ziConoTeVs4/FLXnUsNjujNyFPwFTqZI08iir2lONCRslPLtgx
1+Lgbj2zCVA76Sz2/7FEqdrkbAg7xguubvAlDaTVoBhIoSku0CkouFKwDxR+
TxtaVYzbrSN9cbUM46lQnqgEjCsLBGesHWwbdLuJ0EYWZk78SFVsUT+A5I4q
GkAH8NdHNcdSoNCtNYk0Kg5xyBWr7QoeX+VqWswmlskXqwZHY72gBvBnhIZu
iu3yX5UaqO/XquPdxLha9UBNb+mCGxCMPJs1lQwxvHA9DLFXiGhQwsPGm3Hc
FEWrcGdmaZ7dS9HuZXonGJEQm12UKaSziSqBJNPNwUpSPGqQQdNnRZyOcKyN
ey2S6b78t9OPH8bnl1Kwo5ou7Ir1Mdbw8XT8edx+iD9T0zdPmLFFmyt4pdck
UimgEreJvFonknbKGbPaXn48u7r6eCW1z8pQUHNSP+I5CjtiLG1sr8+ufvd+
fH4RiXdim2yRknJmMiaFaPjg2JIGYvlgZ5ATRDpTMkGywtm8WC9wSXKR6nZo
wfQggORaS5zh7jC6q5lQcNWkZiVOX5ESs5fBlHiaQvtZzpDIKg0/pivA/jpZ
DzV2waeS6Zhzf0miQPIEnIwFe6Uun+kQkE5y+mUtJyzl8WQgoLzULlRpUzkv
m50ccr1TcqqxeTFsJ5JW4Ce8PrOnq4rTn+Eq3dMLl4Aw5kqQCnA4vUdjlnXW
YnwxrurOkErvCIZR4yvMPdBC+C4HuGFw28rpAjeSYwogwfTVW3p6zuqB7VzO
2XmXgOL8Tc/4z9iLig4KabJWgQEDA576Ake5VI7xCiqucUJESqsjhxbHmCxK
zW6x5Glukz4XViCLZJAEbSQm4O0UiKv5pGvWzq5ASwRs0HZ11R0yMjp97aRc
PrqEWqRACyZYxHYNK3/HssaTksNG2gKvP9Keji+neVkrykKqI5GofkaCZCJ9
KczLJXJCu7furFD0lDSJcn3NNyKryJJBfZzftpE8j1nJEjEzE9fl0gb4G+zf
hAwM+fYKQIlACH2hqrJixVk/nOdZiNpUe4lyim6S3MOo4Q5STkrlUXxQiaFn
3oXIJJ3G6avEwXmVHBSyqE2SS9Udbz3KEOPC4bdvcJsDxXEjtz0kisUSvqIm
jwgmgDSWqhl4ACSO0y+1ctr1+W/kM1hh1OqUs1bdcFR6jRua7l6L6cykF2ky
1AUJk3J5LK0VSmmFvHbDYfPMX/uIp9htT0HLvkpdGVwSMWdkyxpSlYa95Z7l
T5bJMOzYe+gXWvB0LQVPl+42ERytToWRkdKgSMblMG5adVhsnuxakZPPReD2
WAM04PvXXEJdjWdPRMCtPBLrNs8wbFOxUinF5KVy1oNIn+a3XL0HAim0LUow
uqgjFyUVuUzg6/I611xdfz3SISR0liVM0DSsxRVLMzxCWibTPJuACHz1bUMp
P1TKg8ORuqk3tDSD6Mtsjuu4wuZcrciljwoZzDMS2Go6F4Aq5ilxNoK5TlzY
YALaEKJ6oUOeSXmAkE5MRfCH3f0605omcSuK6M3wQou08mFTIQ4lF3FetkpR
D1zkyBt9yydQiGclD7PaTk0r2txyXzrc2wqVJzJFu8Z5knLxs1wUNUEESInD
zWFU7tj5mDxAOgsn2Sc5Rv3loGSD0HGCo+W3sMEMhQVyVOwth6sZQqBIwXmm
Fz38VsRaS0wj52lNleHA4ivUfNcJCAZXJRqZKLLqHJ8w1cgENhJvlw4DSu/R
BUAFQcE5uRkYXwemKX+rMuXmahKpq8o0pSElkfD+JSzjZZiOcwED/Em40986
UOvFpTSPkWAzqWjthgEDUki5A8BEvGetAopXkSABtehCVB+0tiKqzeDiCSjB
5+suzDN3T8mIceVFfL80Lu00LRxrZ61iUTDPaAMcfiShBoAvWKruDZr3LasQ
jVQK0lWkTWWptn4kPfxVrtAo+si3rh4SAHJ03gBWI71ehewy7Jb3kyWJnBQu
9kEUYGhRtNAh3y4QwGgZV4pWggnq3QghpK8LqEPhuYL9cXpJald8mc43se6g
cd063qODvcO9Qy6d4ZdHqg1uYrOkNzdCLqUnTdKXhZLBkbeQzcnfz6RdZfrO
w0ffy9H2Znm4sp8dXuKMZw7D3PQnRfmQopJdWYjmRQVWlmuXiZRcTFcu1yGg
r5SrQGk+WIfQcxSiasED6HyVhc62U9EgJ/pLE1BvrWSkmbacke5J1Y3CWfRm
03/5VybxxEd/ZeKjXz7xs1+ZhAz9TXfnz+TibcjFm/5cPA8R8Xzf1Sv2fuGD
ERM1DN/ffI+jb3wmlzwcCXnr1e1t9lWUr0YEevtFS1C/u7z+WdjNaKPNchGY
jCjrKJgblwx4CyQyCq0iVF4QUnH4NFwOePQpC87UFwkIp7Pq4+rmHYgYh6zh
6ruUPM30mwPDJgwo+d1cpLSFS0vBFi561C6KDEMVWt2O+/n+Zol2lSgyhha4
/oGHZVrglvgsjC7LHvAD3ouV9ISrSOgm3OE1lmVew2WYY2p0WSHZvfnVb84u
z67Gn89utNwYEv705FqzoKYQbgr3T0InAoP4vhG4AoI/vM1yvv5WSZaOU4ZL
7jWRWi7uQGGyJF9dseALCjKmKy4F7oF9x8GtdH7J+xBwf5Jw9OnFehkE38WE
ExQ7ptLUgL0EqSmr06mAKprEAvzoQcplClJBB55cdNBZzQ+GIEF30IqPeYDY
MVaclkQPnww1ofm4BrdzDpBWOiRaZPdSnNMHbbUqZjoNBqKv+F4DjGLqEhF4
L4EwN1GkQhOb9TDUOwCLZLmUWt2o1wezl+7ftHrbuHK+kGg5ufDJPxwN5/xw
BKzy7lpzxfsU30IFui9VDa2jyeConqZsA9z8PHmPjCJwJZEP+qW4Hy2UiMV9
wwzmk7LK7rJWFOXOny/eVQxzc7RkAhhOO+/DVu0rCljEXYninJAj297e//bN
IHd9+dMH8MRHdU/quBan3RdCNTEpjUUKDCWrFy4NJDEdgyTaVEC3ZtdFQ1FR
KWqnYeN7GwhOieQkFZBehtf5WcQHLg72Fx4lLySQOONyrfYiqirLVcOOobNK
xw4qUvTSZxbJSee040BUHyNJyI0Zn6PbHARSR/XsEF+XrqNBnKJjFahDRDm3
zRbwx3j7NYVgLG/uju7zl3OjyvY4CGb4JisYuLtjSYKK5MQ4QBlO38c2h/EV
oudF9iV9yADvu/iN3LpwG19I2z+lS+QqLqpXDXy/mJHPqMP1J5cy+xkHJBCb
i1NnanF9rUEAsMTcGrIh6htGEECAyrwXAQjtGYQsTge/sL8L0ffk0atBhFmd
INuY8KFc7IyqJIJcKLfrhed2JEwcqNc4FeKSonwtgnOBfqC8j/lpy793uUO9
yIbLNlytEY2PHbQSMfeo49esrIAHmvwzENeCDD4rb8HM6WVNw9S3jwF3sB2l
GiEee6OjDiJIFI0/bn+oHsvdSuIJ1topJN29mpR3K7nhbwBWSAYSjOWh8HN9
lrRNohXDgQkQZUYAtqATxEFtlSFuSepwVXCzsGDxGNtUftYI1NPufuGOi7QZ
Uk63emPGXf9laVPMA1lcXbCvudAUG6POnrextw+Z9DkIbyo6lCipdCMeg0Tu
mkdEasyd8SpvhI7it+GgW0gZhNYndzGBVGVwdgP2LcwubEP0bFa1yQQ/8kfS
9hhgzTEwN5aKmY28uog3ZXnsVi9ks133RIu2OAPtIWR3pFrSVLgCw9qzzqhV
hfeyjg+ykzMIKWHWJ+54NGlvNH3FGf4HvjkhBGh599gmEwAvWtLnEp7sRLs/
vGHzGmKZkLP8qvd6kHaiU8yKHUNyAe5aiG47re0dbLbHXpmAKYNSxYzdi3Ce
GY2kFu+9vvKWPcIM23AeYsQIQG1D4IyM2vXLwJqlXO8ZR+6oYlEN3Ok1D1Vi
Ui2YHthYxexFV/2iu5XOiXauIesOfwlpDHMaIJzNgdYCxvgNC6gkbVjZljmj
M7/+wZLzLNxnCDcy+WyNtZLR9jcp46oHvlWJabopM3Ua7S8pP0d/VHAeVqFV
WJD0SKCkjV9wW5yZUanB+XHzEka/udPeMCdGyTvO20DmIYHROoXMt18bnp9y
AYLrmdnG4KKDdLeFo3ubSoPPF9cgGlm7dokt50b+qHURTVrUvJIs6hwl6JFf
1oCGcbFWOJXuOnZbq8BZBCCKZUZwX1fdrJecuI7q7Pr6j+eX559V1GT74p3g
YnKv18SU00EGrmuhrxvytzXR/YVVNKQZAqNfaV2p3hvt98vDHIoZY5DRR5zC
WRgK21eFG5Sd21XRDr7iiWrN9gjnv1wrd8XVe65lWr/HIYL/SQBuEnAHdRuj
0LqDEzm+d40G251VItFkf1Id0nogBUJ1x4fGoXaqlpmlXFJAgrr7FBrM3VrF
2L75jC0n2gZVK8ZahcJxmkUTd0bwDi6CJhKGlK4/dhf/sLLk/SRa8yIB4NYB
AjCc/oq3EKWdXZ0VRicxqh6XjabnOOLk+re3Pf0XLDNS7Sp6ONdDDCKqW+Ea
OZ0rd6sfMMhq4SpF3GV/ro3Vt3HBUAuuoRgWcJ0cGqWdBEFe+UYa+aGLdFFW
jwMH07lQyc3BPgvUGKdohdDqTE/4eh8CtybRPozhrjxppUG4jRtJT8OFHJ3A
zIXtAxN7dcxTYaVEmtX6VyVlLs0Oz8fv1hCjZ1rW4tFkidMnot9KbyCJ6rjf
U6drbdSx1tUVdNuPoR2zvyeLy5naYA4FMxTkoZuu+KU4jEH7Ml63HU/U5GIQ
eYaNdhVq394OtO3vEKaNTLUuCT6aSbf391yULdCC0+QCL9UuDaxeuD0b0Tds
Qyy/nAPNL0LfXIcvZtI29HKMJgNOdwiwyiDGSA7octyH6Z30NA+G09EXXcPx
cE0WWqf4/ZMZyOS0+6ger4RyipqvaeYCr+Uev1hZxn898kY0MSJRz7Vk05ls
e6ZKs33FXcm1Ga1GqjG6ol8zUaM1mimkFVEWHyfKpMirVkrQbBOJFYk64oWv
tSX7bg8yYBJvhVquasvoA0KeVnNqp5AFS1d7tD4hdybgrrwBh2p3O9PwXeE3
rAoHoFW0nXjRedT+tDSX9V5yEFxfv1ggJ+DuZJQeN6NBuvhLMDABdhkYcZgd
JKz2MmqBchUVosCAPlej0tVB6VfXCYy0hEveCY+xvPUBGCNtxRHN6MrGuUpK
i12ZQ7Q6DL5Qp4kzbYkMAzkSdVwe5W/4j1uN9NhyuhnBBuysNcDvpdH1WhoY
9/+jaJvxVsce0vlOIEvD2Jv/Eqj//E0C/areXPFzGo6HfO89B3De5eVE7sAo
J/ZyWumqrOpW3oWPQKGYrIrTSpGTommuBdafQgBaSYy1Uky2YdzQ39dgBLFW
jp1T6BH3S5f41zeQ8gRldH9BeoZF1UMIUfuy56K/dp8vV/2Mnvzt2xkHrU82
UU3Saz2BAa7Y/4qgleveAJMt+neqSdqFWoL+9RpG7sX29CKoQbQD+tbfZpYb
uLXuRpymtwlwmNDIu1Ncsd4V6VMfkHirkiUGgKyJA65blEIdMypZGFdxbRJn
nQI4zov7ji2T1Of1Z224PjCvL+MCJhwqY1jAysrL2ofxH7TATVI5QVvnj2wo
/L0ueNtVnRpRg9ibVBYfbR9y2oNCgghDZsVoWpGZR2+5ZGbTtwzyeso5u75r
b9yUndeS5jn+/aST/UTLaT2z7bU9mrntdrtZddq/ev/JtcuwO1tHB9tvdvwo
O/uHe7tv9t68wTKlpA4bd/PTy7gm0aAm8Zk6nAN2bN622qasNUtULtILMT4N
K2W+nWbq0kDDizsrihlwP3WLtbomarOu3ckeKAwmZauBpDs3KT9iz77Trg7K
k5siN75c4/fy+y32N/ixF/tKSj/QuY0dCunLGTcAYzfZ0E43pcOp/v6L/FiM
hnJT9fRik+YIgQ53z4tuJtfo52VZSwUmavBsGVeJ+TvtP9QlD118woOhRgvm
+fm2NwgwGXxNn/npAbu9dbB7sLd9uLNnPINt7x3sHe7u7x3YV1tf97bkP89/
W18P3st/myBil9kYFQsIX1i1i49Dd5Osv1QsdHjD76+wc1iXkrbhDpZ6GJq6
5VJN31dTTFvCbejeu8L8HyKxHePySdB1WgxonDtxE/8ah/0las+sqb1wWft5
1efKk3h2057dVxymWnAokVmgtTh7YZuY71Pkcbfs0Jo7rgGA79C05gxLuVQU
G0Serhd6yZXIDy/wMcRz+MI6btLR2pzKM0ouHllvPNOpVQmwIY24r+WXN9BY
sO+3LqJi45jVuvLiL4W3gla/WL4QfEtGhJxrGj+54wh2kTTiBCoP+kiwteH4
7h1wfkc/V8+dfuFTan0HqQmvK8EmfA9CskB9v1rh4TK52Ic16fW9B9/MDZMw
bUfmI64e96sFb+64y3Z0jxHSi+NP8+wuo5H5hJTh47VHLdUkWHhWV5pWbMhO
EUT+x/SiYdC9XzFilFXhd8K3ply70+jHV3wnslY7sYHWP3q1d3RweLS3+33m
We9GpN7LzwqsJe2KZS65TbkoSyFw15qR79quKo7poogkKneU+FZr1tZFlHPd
Bk2u3aFwIuw+m+FWYvuXZdgOXSmPj3XFiQfr+P1hEr/Pl7zcjyeV8ttJ6Ey8
lGtOTGpYXm6oFuocTn2VlHSRKIxjo2ewpCpdq8vhe5LtmzfORXzUWgsVrCFp
1FDfFJwRscGi4nzvWiNxqC8Kp1XKpURGNFhg/s8aR7tztETbTadRMMxWnXJ+
xftW3EsRZWn0j+bktNo5ipTjrryRv5VIGXnpf82plhsCzUOaFu0wVxvedcJW
5YqW0RhH9cyMuD9X69zRb+oFcQsIqaF2TbqiCG/NEOBSa7xO14o+DOwzGZzw
ErxLzKar04pjB+Rp/M+EcdgeNX5geVF1d5c7mBaPBJ7V3zCohyK2UDhab9kl
3l9Z6i3/lsaf/G9paMlMtAOZ6judEKW8br0ivdOAQW+oRIdNJNXLvfIDPpFI
xt0aujmsHR+nhDqXj0WwjILNS16B/p9UTKevYxOT42VtWhx83v1thXXWSNs3
Bd6aTv0qLxjVGi6FFnNaVJqJUr1r31UOI596MC3oIL6fhGK+1mF/HxvUuKCd
7KoiLUnMNjBORYqmYh3Z0YoB3Au74/h2ZFCD3qeNv8VNuBvtHCgTq36YzrN8
xsQwftnTUqAfBAe11IYN8WtKXhNyaYR0Nk2UnrRY1/yDeUu2o/NymzB8BjAl
hEnYYPeCqJGiujaQqfX6Yq8hVxFvOn3WRugGrhN9Wwx01+s/Z2HlV9gSlZak
dtdM4zs+7QJdZD3kEo40LHPCyhFOrf2q16repImFh32NVBa2LW1UIxb9/psg
s6z0g/FtFYx9J9xzFSneToRIOwLopTN7o9N0f2ct8IcUwK2ZLsdaxv8MWBQC
Nf5HIYM1GsmvSL6s23VfiKBjtPXpKf6tyVC2yn2AXTNOpGiu/RLemqj0vaND
TvW51g9T9ti5/wXQ9nfycncAAA==

-->

</rfc>
