<?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-tiptop-ipn-allocator-prefixes-01" category="exp" consensus="true" submissionType="IETF" updates="4291" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="IPN Allocator Prefixes">IPv6 Prefixes Derived from IPN Allocator Identifiers</title>
    <seriesInfo name="Internet-Draft" value="draft-ek-tiptop-ipn-allocator-prefixes-01"/>
    <author fullname="Erik Kline">
      <organization>Aalyria Technologies Inc.</organization>
      <address>
        <email>ek.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <keyword>IPv6 prefixes</keyword>
    <keyword>IPN Allocators</keyword>
    <keyword>DTN</keyword>
    <abstract>
      <?line 71?>

<t>This document requests an IPv6 /16 prefix for use by IPN Allocators.
It defines a method to derive an IPv6 /48 prefix from a 32-bit IPN Allocator Identifier.
Use of the derived prefix is optional.
The method reuses the existing IPN Allocator registry.
It does not encode physical location or define a routing mechanism.
The preferred /16 prefix is 5f01::/16.
This document also updates RFC 4291 to permit other interface identifier lengths within the allocated block.</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-ipn-allocator-prefixes/draft-ek-tiptop-ipn-allocator-prefixes.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ek-tiptop-ipn-allocator-prefixes/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ekline/draft-ipn-allocator-prefixes"/>.</t>
    </note>
  </front>
  <middle>
    <?line 82?>

<section anchor="intro">
      <name>Introduction</name>
      <t>An IPN Allocator Identifier <xref target="RFC9758"/> identifies an authority that assigns IPN Node Numbers.
This document associates an optional IPv6 prefix with that authority.
The association does not describe network topology.
It does not identify a next hop or establish a route.</t>
      <t>An Allocator can use the derived prefix to assign IPv6 addresses within networks under its administration.
The method reuses the existing "'ipn' Scheme URI Allocator Identifiers" registry <xref target="IANA-IPN"/>.
It does not require a new per-identifier registry.</t>
      <section anchor="scope">
        <name>Scope</name>
        <t>This document defines an address assignment mechanism.
The mechanism applies to terrestrial networks and to space networks.
This document also updates <xref target="RFC4291"/> for addresses within the common prefix (<xref target="update-4291"/>).</t>
        <t>This document does not define:</t>
        <ul spacing="compact">
          <li>
            <t>a conversion between an IPN endpoint identifier and an IPv6 address;</t>
          </li>
          <li>
            <t>an encoding of an IPN Node Number or Service Number in an IPv6 address;</t>
          </li>
          <li>
            <t>a Bundle Protocol <xref target="RFC9171"/> convergence layer;</t>
          </li>
          <li>
            <t>a method to carry IPv6 packets in bundles;</t>
          </li>
          <li>
            <t>a routing protocol or an automatic route discovery mechanism; or</t>
          </li>
          <li>
            <t>a requirement to use IPv6 in all Delay-Tolerant Networking (DTN) deployments.</t>
          </li>
        </ul>
      </section>
      <section anchor="motivation">
        <name>Motivation</name>
        <t>An Allocator already manages a namespace for IPN Node Numbers.
A corresponding IPv6 prefix can simplify address administration for networks that use both IPN identifiers and IPv6 addresses.</t>
        <t>Physical location does not determine network connectivity or transit policy.
This document does not assign prefixes to celestial bodies.</t>
        <t>An Allocator can retain its derived prefix when its equipment changes location.
Continued reachability depends on the available routes and applicable routing policy.
This document makes no routing scalability guarantee.
It does not define a mobility mechanism.</t>
      </section>
      <section anchor="experiment">
        <name>Experiment Scope</name>
        <t>This document specifies an experiment.
The experiment evaluates these questions:</t>
        <ul spacing="compact">
          <li>
            <t>whether registry-derived prefixes simplify address administration;</t>
          </li>
          <li>
            <t>whether participating implementations support the intended address structures;</t>
          </li>
          <li>
            <t>whether routing and filtering permit the intended connectivity; and</t>
          </li>
          <li>
            <t>whether changes in Allocator control can occur without conflicting assignments.</t>
          </li>
        </ul>
        <t>This document encourages operators and implementers to publish reports of their deployment experience.
The experiment makes no claim of automatic route aggregation or improved routing scalability.</t>
      </section>
    </section>
    <section anchor="conventions">
      <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 terms "Node Number" and "Service Number" as defined in <xref target="RFC9758"/>.
This document also uses the terms that follow.</t>
      <dl>
        <dt>Allocator:</dt>
        <dd>
          <t>An organization or other authority that assigns IPN Node Numbers (<xref section="3.2" sectionFormat="of" target="RFC9758"/>).</t>
        </dd>
        <dt>Allocator Identifier:</dt>
        <dd>
          <t>An unsigned 32-bit integer A that identifies an Allocator (<xref section="3.2" sectionFormat="of" target="RFC9758"/>).
"The Allocator of A" is the Allocator that the IANA registry <xref target="IANA-IPN"/> currently lists for A.</t>
        </dd>
        <dt>Common prefix:</dt>
        <dd>
          <t>The IPv6 /16 prefix that this document requests.
The preferred value is 5f01::/16.</t>
        </dd>
        <dt>Derived prefix:</dt>
        <dd>
          <t>The IPv6 /48 prefix P(A) associated with one Allocator Identifier A.</t>
        </dd>
        <dt>Eligible identifier:</dt>
        <dd>
          <t>An Allocator Identifier that this document permits for ordinary use.
<xref target="eligibility"/> gives the rules.</t>
        </dd>
      </dl>
      <t>An Allocator can hold more than one Allocator Identifier (<xref section="3.2" sectionFormat="of" target="RFC9758"/>).
Each Allocator Identifier is associated with only one Allocator.
This document provides one derived prefix for each eligible identifier.
Thus, one Allocator can have more than one derived prefix.</t>
    </section>
    <section anchor="construction">
      <name>Prefix Construction</name>
      <section anchor="common-prefix">
        <name>Common Prefix</name>
        <t>This document requests 5f01::/16 as the common prefix.
Until IANA allocates the common prefix, 5f01::/16 is requested and unassigned for this purpose.
Until then, an Allocator <bcp14>MUST NOT</bcp14> treat an eligible identifier as permission to use 5f01::/16.
The allocation requires IETF Review (<xref target="iana-space"/>).</t>
        <t>The first instance of the 6bone experimental network used 5f00::/8 for IPv6 testing <xref target="RFC1897"/> <xref target="RFC3701"/>.
That block was later returned to IANA for future allocation <xref target="RFC5156"/>.
<xref target="RFC9602"/> then assigned 5f00::/16 for Segment Routing over IPv6 (SRv6) Segment Identifiers (SIDs).</t>
        <t>Allocating 5f01::/16 extends the allocation adjacent to 5f00::/16.
Within the remaining 5f00::/8 space, this choice avoids splitting a larger aligned block.
The mechanism does not depend on the specific /16 value or on SRv6.</t>
        <t>Note to the RFC Editor:
If IANA allocates a /16 other than 5f01::/16, replace "5f01" with the allocated value throughout this document.
This replacement includes the derived prefixes, the examples, and the IANA entries.
Also revise the rationale in this section and the filter text in <xref target="routing"/>.
Then remove this note.</t>
      </section>
      <section anchor="layout">
        <name>Address Layout</name>
        <t>This document numbers the 128 bits of an IPv6 address from 0 to 127.
Bit 0 is the most significant bit.</t>
        <table anchor="tab-layout">
          <name>Layout of an Address in a Derived Prefix</name>
          <thead>
            <tr>
              <th align="left">Bits</th>
              <th align="right">Length</th>
              <th align="left">Field</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0-15</td>
              <td align="right">16 bits</td>
              <td align="left">Common prefix</td>
            </tr>
            <tr>
              <td align="left">16-47</td>
              <td align="right">32 bits</td>
              <td align="left">Allocator Identifier</td>
            </tr>
            <tr>
              <td align="left">48-127</td>
              <td align="right">80 bits</td>
              <td align="left">Allocator-controlled address space</td>
            </tr>
          </tbody>
        </table>
        <t>The requirements that follow apply to each party that constructs a derived prefix.
The derived prefix <bcp14>MUST</bcp14> contain the complete 32-bit Allocator Identifier immediately after the common prefix.
The identifier <bcp14>MUST</bcp14> appear in network byte order.
Leading zero bits are significant in this binary field.
The lengths of the decimal text form and of the Concise Binary Object Representation (CBOR) <xref target="RFC8949"/> encoding have no effect on the field.
A 16-bit common prefix and a 32-bit Allocator Identifier produce a /48.</t>
      </section>
      <section anchor="derivation">
        <name>Derivation</name>
        <t>For an Allocator Identifier A, define two 16-bit values:</t>
        <ul spacing="compact">
          <li>
            <t>H = floor(A / 65536), the 16 most significant bits of A</t>
          </li>
          <li>
            <t>L = A modulo 65536, the 16 least significant bits of A</t>
          </li>
        </ul>
        <t>With the requested common prefix, the derived prefix is:</t>
        <artwork><![CDATA[
P(A) = 5f01:H:L::/48
]]></artwork>
        <t>H and L are written as hexadecimal fields of the IPv6 text form (<xref section="2.2" sectionFormat="of" target="RFC4291"/>).
The examples in this document use the recommended text form (<xref section="4" sectionFormat="of" target="RFC5952"/>).</t>
      </section>
      <section anchor="allocator-space">
        <name>Allocator-Controlled Address Space</name>
        <t>Bits 48 to 127 of each address in P(A) are under the control of the Allocator of A.
The Allocator controls address assignment and prefix delegation within P(A).
These activities remain subject to this document and applicable IPv6 specifications.
This document does not require a particular structure or encoding in these 80 bits.</t>
        <dl>
          <dt>Assignment:</dt>
          <dd>
            <t>The Allocator can assign prefixes of any length within P(A).
Ordinary /64 subnets remain permitted.</t>
          </dd>
          <dt>Routing and forwarding:</dt>
          <dd>
            <t>IPv6 forwarding processes support prefixes of any length <xref target="RFC7608"/>.
Routing policy determines which prefix lengths operators advertise and accept.
Forwarding support does not establish support for host address configuration.</t>
          </dd>
          <dt>Host interface addresses:</dt>
          <dd>
            <t><xref target="update-4291"/> permits interface identifiers other than 64 bits within the common prefix.
Host and link support for other lengths varies (<xref target="slaac"/>).</t>
          </dd>
        </dl>
      </section>
      <section anchor="update-4291">
        <name>Update to RFC 4291</name>
        <t>For addresses within the common prefix, this document removes the requirement for a 64-bit interface identifier.
This exception updates Sections 2.5.1 and 2.5.4 of <xref target="RFC4291"/>.
It applies only to the common prefix allocated by this document.</t>
        <t><xref section="2.5.1" sectionFormat="of" target="RFC4291"/>, as updated by <xref section="5" sectionFormat="of" target="RFC7136"/>, requires 64-bit interface identifiers for unicast addresses that do not start with binary 000.
<xref section="2.5.4" sectionFormat="of" target="RFC4291"/> states the same constraint for Global Unicast addresses.
This document adds the text that follows after each of these two statements:</t>
        <ul empty="true">
          <li>
            <t>This requirement does not apply to addresses within the IPv6 block allocated for IPv6 Prefixes Derived from IPN Allocator Identifiers (RFC XXXX).
In that block, an interface identifier can have any length that the subnet prefix permits.</t>
          </li>
        </ul>
        <t>Note to the RFC Editor:
Replace "RFC XXXX" with the number of this document, then remove this note.</t>
        <t>All other text of Section 2.5.1, as updated by <xref target="RFC7136"/>, still applies.
For example, a 64-bit interface identifier derived from an IEEE MAC-layer address still uses the Modified EUI-64 format.</t>
        <t><xref target="RFC9602"/> is a limited precedent for this exception.
Its discussion of <xref target="RFC4291"/> concerns SRv6 SIDs that are not assigned to host interfaces.</t>
      </section>
      <section anchor="slaac">
        <name>Address Configuration</name>
        <t>This exception does not change SLAAC or link-specific address configuration procedures.
Operators must select address structures that their hosts and links support.</t>
        <t>In Stateless Address Autoconfiguration (SLAAC), a host forms an address from an advertised prefix and an interface identifier.
A link-type specification defines the length of that interface identifier.
Many link-type specifications define a length of 64 bits (<xref section="4.1" sectionFormat="of" target="RFC7421"/>).
The host ignores the prefix for address formation if the two lengths do not sum to 128 bits (<xref section="5.5.3" sectionFormat="of" target="RFC4862"/>, item (d)).
Thus, SLAAC on such links forms addresses only from /64 prefixes.
This document does not define a new SLAAC mechanism.</t>
      </section>
    </section>
    <section anchor="eligibility">
      <name>Eligibility and Optional Use</name>
      <t>The current IANA "'ipn' Scheme URI Allocator Identifiers" registry <xref target="IANA-IPN"/> determines eligibility.
The rules that follow apply to each Allocator Identifier A.</t>
      <ol spacing="compact" type="1"><li>
          <t>Ordinary assignment:
A current ordinary assignment of A permits the Allocator of A to assign addresses and delegate prefixes from P(A).
An ordinary assignment is a registry entry that assigns A to a named Allocator, alone or in a range.
Rules 3 to 7 take precedence over this rule.</t>
        </li>
        <li>
          <t>Optional use:
The Allocator of A decides whether to use P(A).
This document does not require a second registration for each identifier.</t>
        </li>
        <li>
          <t>Unassigned identifiers:
An unassigned identifier does not permit use of its derived prefix.</t>
        </li>
        <li>
          <t>Reserved identifiers:
A reserved identifier does not permit ordinary use.
The reserved identifiers include 0x80000000 to 0xFFFFFFFF.</t>
        </li>
        <li>
          <t>Experimental identifiers:
Identifiers in the Experimental Use range (0x40000000 to 0x7FFFFFFF) do not confer exclusive control of globally unique IPv6 prefixes.
This document does not specify operational use of their derived prefixes.</t>
        </li>
        <li>
          <t>Example Range:
The IPN Example Range (974848 to 978943) is for documentation (<xref section="9.1" sectionFormat="of" target="RFC9758"/>).
Its derived prefixes are not for operational deployment.</t>
        </li>
        <li>
          <t>Allocator Identifier zero:
Allocator Identifier zero does not permit ordinary use under this specification.
<xref target="default-allocator"/> gives the reason.</t>
        </li>
      </ol>
      <t>An Allocator Identifier is an eligible identifier only if rule 1 applies and rules 3 to 7 do not exclude it.
No other text in this document makes an Allocator Identifier eligible.</t>
      <t>A party <bcp14>MUST NOT</bcp14> assign addresses or delegate prefixes from P(A) unless A is eligible and the party has authority from the Allocator of A.
These eligibility rules govern address assignment and prefix delegation.
They do not require a router to query the IPN registry when forwarding a packet.</t>
      <section anchor="default-allocator">
        <name>The Default Allocator</name>
        <t><xref target="RFC9758"/> assigns Allocator Identifier zero to the Default Allocator (<xref section="3.2.2" sectionFormat="of" target="RFC9758"/>).
The Default Allocator serves multiple independent organizations.
Assignment of a Node Number by the Default Allocator does not assign control of the derived /48.
This document reserves P(0), which is 5f01::/48, for future specification.
This document does not define a subdivision of P(0).</t>
      </section>
    </section>
    <section anchor="examples">
      <name>Examples</name>
      <t>The examples in this section are illustrations.
They use the requested common prefix 5f01::/16 and identifiers from the IPN Example Range.
They do not represent operational IPv6 assignments.</t>
      <table anchor="tab-examples">
        <name>Example Derived Prefixes</name>
        <thead>
          <tr>
            <th align="right">Allocator Identifier</th>
            <th align="left">Hexadecimal value</th>
            <th align="left">Derived prefix</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="right">974848</td>
            <td align="left">0x000EE000</td>
            <td align="left">5f01:e:e000::/48</td>
          </tr>
          <tr>
            <td align="right">974849</td>
            <td align="left">0x000EE001</td>
            <td align="left">5f01:e:e001::/48</td>
          </tr>
          <tr>
            <td align="right">978943</td>
            <td align="left">0x000EEFFF</td>
            <td align="left">5f01:e:efff::/48</td>
          </tr>
        </tbody>
      </table>
      <t>For A = 974849, H is 14 (0xe) and L is 57345 (0xe001).
The complete Example Range contains 4096 (2^12) identifiers, from 0x000EE000 to 0x000EEFFF.
The 12 least significant bits of 0x000EE000 are zero.
Thus, the range maps to a prefix of length 48 - 12 = 36:</t>
      <artwork><![CDATA[
5f01:e:e000::/36
]]></artwork>
    </section>
    <section anchor="routing">
      <name>Routing and Operational Considerations</name>
      <t>This document specifies address assignment only.
The principles that follow apply to derived prefixes:</t>
      <ul spacing="compact">
        <li>
          <t>A derived prefix does not establish connectivity.</t>
        </li>
        <li>
          <t>An address assignment does not require another network to accept a route.</t>
        </li>
        <li>
          <t>A shared Allocator does not imply a shared routing domain.</t>
        </li>
        <li>
          <t>An Allocator can operate disconnected networks.</t>
        </li>
        <li>
          <t>Routing policy determines permitted route advertisements and transit.</t>
        </li>
        <li>
          <t>A prefix does not indicate contact times, delay, or available capacity.</t>
        </li>
        <li>
          <t>Ordinary IPv6 addresses remain available through other assignment mechanisms.</t>
        </li>
      </ul>
      <t>An Allocator Identifier alone provides no evidence of reachability.
Operators determine reachability through their routing mechanisms and policies.</t>
      <t>This document does not define an inherent administrative domain boundary for the common prefix.
Operators <bcp14>MAY</bcp14> exchange routes and traffic for derived prefixes between administrative domains.
Such exchange is subject to agreement between the operators and to their routing policies.
This design does not guarantee acceptance of derived prefixes on the public Internet.</t>
      <t>Existing filters can reject traffic from this block.
Operators need to check filters for unallocated IPv6 space and former 6bone space <xref target="RFC5156"/>.
A filter that matches only the SRv6 block 5f00::/16 <xref target="RFC9602"/> does not match 5f01::/16.
Broader filters, such as a filter for 5f00::/8, can match both blocks.</t>
      <t>If the IPN registry withdraws or reassigns A, the previous Allocator of A loses its authority over P(A) under this document.</t>
      <t>An Allocator <bcp14>MUST NOT</bcp14> retain authority over P(A) solely because it previously held A.
A change to the contact information of a registry entry alone does not reassign the Allocator Identifier.
Registry changes do not automatically update deployed addresses, routes, filters, or authorization records.
The previous and new Allocators need to coordinate these updates to prevent simultaneous use of P(A).</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>An address in a derived prefix exposes the associated Allocator Identifier.
The Allocator Identifier is public information in the IANA registry.
An observer can use it to associate traffic with the Allocator.</t>
      <t>An Allocator Identifier is not proof of identity.
An attacker can configure an address in the derived prefix of another Allocator.
The arithmetic mapping does not authenticate packets or authorize route advertisements.
Registry information does not, by itself, authenticate a route origin.</t>
      <t>Route leaks and unauthorized route advertisements remain possible.
An operator that accepts a route for a derived prefix needs to verify the origin under its own policy.
This document does not create Resource Public Key Infrastructure (RPKI) <xref target="RFC6480"/> certificates.
It does not create Route Origin Authorizations (ROAs) or a new trust anchor.</t>
      <t>After reassignment, stale filters can block traffic for the new Allocator of A.
Stale authorization can let the previous Allocator of A continue to originate routes.</t>
      <t>More than one party can use the same experimental identifier.
For this reason, rule 5 in <xref target="eligibility"/> excludes these identifiers from ordinary use.</t>
      <t>Interface identifiers shorter than 64 bits reduce the address space that an attacker needs to scan (<xref section="5" sectionFormat="of" target="RFC7421"/>).</t>
      <t>IPv6 prefix eligibility can create new incentives to request IPN Allocator Identifiers or large identifier ranges.
An aligned range of 2^k identifiers maps to an aggregate of length 48 - k.
The existing IPN assignment procedures were not designed solely to distribute IPv6 address space.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="iana-space">
        <name>IPv6 Address Space Registry</name>
        <t>IANA is requested to allocate a /16 address block for "IPv6 Prefixes Derived from IPN Allocator Identifiers".
The preferred address block is 5f01::/16.</t>
        <t>This block is in 5f00::/8, the former 6bone testing block (<xref target="common-prefix"/>), within 4000::/3.
The "IPv6 Address Space" registry <xref target="IANA-IPV6-SPACE"/> lists 4000::/3 as "Reserved by IETF".
Allocations from this space require IETF Review <xref target="RFC9812"/>.</t>
        <t>A 16-bit common prefix and a 32-bit identifier produce a /48.
A smaller block cannot preserve this complete mapping.</t>
        <t>IANA is requested to update the "IPv6 Address Space" registry entry for 4000::/3 to reference this document.</t>
      </section>
      <section anchor="iana-special">
        <name>IPv6 Special-Purpose Address Space Registry</name>
        <t>IANA is requested to add the entry that follows to the "IPv6 Special-Purpose Address Space" registry <xref target="IANA-IPV6-SPECIAL"/>.
<xref target="RFC6890"/> and <xref target="RFC8190"/> define the fields.</t>
        <dl spacing="compact">
          <dt>Address Block:</dt>
          <dd>
            <t>5f01::/16</t>
          </dd>
          <dt>Name:</dt>
          <dd>
            <t>IPv6 Prefixes Derived from IPN Allocator Identifiers</t>
          </dd>
          <dt>RFC:</dt>
          <dd>
            <t>This document</t>
          </dd>
          <dt>Allocation Date:</dt>
          <dd>
            <t>The date that IANA allocates the common prefix</t>
          </dd>
          <dt>Termination Date:</dt>
          <dd>
            <t>N/A</t>
          </dd>
          <dt>Source:</dt>
          <dd>
            <t>True</t>
          </dd>
          <dt>Destination:</dt>
          <dd>
            <t>True</t>
          </dd>
          <dt>Forwardable:</dt>
          <dd>
            <t>True</t>
          </dd>
          <dt>Globally Reachable:</dt>
          <dd>
            <t>True</t>
          </dd>
          <dt>Reserved-by-Protocol:</dt>
          <dd>
            <t>False</t>
          </dd>
        </dl>
        <t>These values are deliberate initial design choices.
They permit ordinary IPv6 forwarding across administrative boundaries.
"Globally Reachable" indicates that a router can forward these datagrams beyond an administrative domain <xref target="RFC8190"/>.
It does not guarantee a route.</t>
        <t>The parent entry does not make every derived prefix eligible.
IANA is requested to add this note to the parent entry:
"Address assignment and prefix delegation within this block are subject to the eligibility rules in Section 4 of this document."</t>
      </section>
      <section anchor="iana-exceptions">
        <name>More-Specific Entries</name>
        <t>Some derived prefixes are not for ordinary use.
IANA is requested to add the more-specific entries in <xref target="tab-exceptions"/>.
These entries take precedence over the parent entry.</t>
        <table anchor="tab-exceptions">
          <name>Proposed More-Specific Entries</name>
          <thead>
            <tr>
              <th align="left">Address Block</th>
              <th align="left">Name</th>
              <th align="left">IPN Identifiers</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">5f01::/48</td>
              <td align="left">Reserved (IPN Default Allocator)</td>
              <td align="left">0</td>
            </tr>
            <tr>
              <td align="left">5f01:e:e000::/36</td>
              <td align="left">Documentation (IPN Example Range)</td>
              <td align="left">0xEE000-0xEEFFF</td>
            </tr>
            <tr>
              <td align="left">5f01:4000::/18</td>
              <td align="left">Reserved (IPN Experimental Use range)</td>
              <td align="left">0x40000000-0x7FFFFFFF</td>
            </tr>
            <tr>
              <td align="left">5f01:8000::/17</td>
              <td align="left">Reserved (IPN Reserved range)</td>
              <td align="left">0x80000000-0xFFFFFFFF</td>
            </tr>
          </tbody>
        </table>
        <t>Each entry uses the values that follow for the other fields:</t>
        <dl spacing="compact">
          <dt>RFC:</dt>
          <dd>
            <t>This document</t>
          </dd>
          <dt>Allocation Date:</dt>
          <dd>
            <t>The date that IANA allocates the common prefix</t>
          </dd>
          <dt>Termination Date:</dt>
          <dd>
            <t>N/A</t>
          </dd>
          <dt>Source, Destination, Forwardable, Globally Reachable, and Reserved-by-Protocol:</dt>
          <dd>
            <t>False</t>
          </dd>
        </dl>
        <t>These values match the Documentation entry for 3fff::/20 and rules 4 to 7 of <xref target="eligibility"/>.
In each name, the first word gives the IPv6 status, and the parenthetical identifies the IPN identifiers.
For example, 5f01:4000::/18 is reserved IPv6 space and does not permit IPv6 experimental deployment.</t>
        <t>A later change to the IPN registry does not remove an IPv6 exclusion specified by this document.
Use of an excluded IPv6 block requires a separate specification and the applicable IANA updates.</t>
        <t>IANA does not record individual derived prefixes.
An ordinary assignment in an eligible range becomes usable without a second per-identifier registration (<xref target="eligibility"/>).
This document does not request entries for currently unassigned identifiers.</t>
        <t>Editor's Note:
The author requests IANA and community review of the entries in this section (<xref target="open-issues"/>).</t>
      </section>
      <section anchor="iana-ipn">
        <name>'ipn' Scheme URI Allocator Identifiers Registry</name>
        <t>This document makes no changes to the "'ipn' Scheme URI Allocator Identifiers" registry <xref target="IANA-IPN"/>.
It makes no changes to the registration procedures of that registry.</t>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC4291">
          <front>
            <title>IP Version 6 Addressing Architecture</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <date month="February" year="2006"/>
            <abstract>
              <t>This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.</t>
              <t>This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4291"/>
          <seriesInfo name="DOI" value="10.17487/RFC4291"/>
        </reference>
        <reference anchor="RFC7136">
          <front>
            <title>Significance of IPv6 Interface Identifiers</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="S. Jiang" initials="S." surname="Jiang"/>
            <date month="February" year="2014"/>
            <abstract>
              <t>The IPv6 addressing architecture includes a unicast interface identifier that is used in the creation of many IPv6 addresses. Interface identifiers are formed by a variety of methods. This document clarifies that the bits in an interface identifier have no meaning and that the entire identifier should be treated as an opaque value. In particular, RFC 4291 defines a method by which the Universal and Group bits of an IEEE link-layer address are mapped into an IPv6 unicast interface identifier. This document clarifies that those two bits are significant only in the process of deriving interface identifiers from an IEEE link-layer address, and it updates RFC 4291 accordingly.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7136"/>
          <seriesInfo name="DOI" value="10.17487/RFC7136"/>
        </reference>
        <reference anchor="RFC6890">
          <front>
            <title>Special-Purpose IP Address Registries</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="L. Vegoda" initials="L." surname="Vegoda"/>
            <author fullname="R. Bonica" initials="R." role="editor" surname="Bonica"/>
            <author fullname="B. Haberman" initials="B." surname="Haberman"/>
            <date month="April" year="2013"/>
            <abstract>
              <t>This memo reiterates the assignment of an IPv4 address block (192.0.0.0/24) to IANA. It also instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries. Upon restructuring, the aforementioned registries will record all special-purpose address blocks, maintaining a common set of information regarding each address block.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="153"/>
          <seriesInfo name="RFC" value="6890"/>
          <seriesInfo name="DOI" value="10.17487/RFC6890"/>
        </reference>
        <reference anchor="RFC8190">
          <front>
            <title>Updates to the Special-Purpose IP Address Registries</title>
            <author fullname="R. Bonica" initials="R." surname="Bonica"/>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Haberman" initials="B." surname="Haberman"/>
            <author fullname="L. Vegoda" initials="L." surname="Vegoda"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>This memo updates the IANA IPv4 and IPv6 Special-Purpose Address Registries to address issues raised by the definition of a "global" prefix. It also corrects several errors in registry entries to ensure the integrity of the IANA Special-Purpose Address Registries.</t>
              <t>This memo updates RFC 6890.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="153"/>
          <seriesInfo name="RFC" value="8190"/>
          <seriesInfo name="DOI" value="10.17487/RFC8190"/>
        </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="IANA-IPN" target="https://www.iana.org/assignments/uri-schemes">
          <front>
            <title>'ipn' Scheme URI Allocator Identifiers</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </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="RFC1897">
          <front>
            <title>IPv6 Testing Address Allocation</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="January" year="1996"/>
            <abstract>
              <t>This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. This document specifies an Experimental protocol for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1897"/>
          <seriesInfo name="DOI" value="10.17487/RFC1897"/>
        </reference>
        <reference anchor="RFC3701">
          <front>
            <title>6bone (IPv6 Testing Address Allocation) Phaseout</title>
            <author fullname="R. Fink" initials="R." surname="Fink"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="March" year="2004"/>
            <abstract>
              <t>The 6bone was established in 1996 by the IETF as an IPv6 Testbed network to enable various IPv6 testing as well as to assist in the transitioning of IPv6 into the Internet. It operates under the IPv6 address allocation 3FFE::/16 from RFC 2471. As IPv6 is beginning its production deployment it is appropriate to plan for the phaseout of the 6bone. This document establishes a plan for a multi-year phaseout of the 6bone and its address allocation on the assumption that the IETF is the appropriate place to determine this. This document obsoletes RFC 2471, "IPv6 Testing Address Allocation", December, 1998. RFC 2471 will become historic. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3701"/>
          <seriesInfo name="DOI" value="10.17487/RFC3701"/>
        </reference>
        <reference anchor="RFC4862">
          <front>
            <title>IPv6 Stateless Address Autoconfiguration</title>
            <author fullname="S. Thomson" initials="S." surname="Thomson"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="T. Jinmei" initials="T." surname="Jinmei"/>
            <date month="September" year="2007"/>
            <abstract>
              <t>This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4862"/>
          <seriesInfo name="DOI" value="10.17487/RFC4862"/>
        </reference>
        <reference anchor="RFC5156">
          <front>
            <title>Special-Use IPv6 Addresses</title>
            <author fullname="M. Blanchet" initials="M." surname="Blanchet"/>
            <date month="April" year="2008"/>
            <abstract>
              <t>This document is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5156"/>
          <seriesInfo name="DOI" value="10.17487/RFC5156"/>
        </reference>
        <reference anchor="RFC5952">
          <front>
            <title>A Recommendation for IPv6 Address Text Representation</title>
            <author fullname="S. Kawamura" initials="S." surname="Kawamura"/>
            <author fullname="M. Kawashima" initials="M." surname="Kawashima"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5952"/>
          <seriesInfo name="DOI" value="10.17487/RFC5952"/>
        </reference>
        <reference anchor="RFC6480">
          <front>
            <title>An Infrastructure to Support Secure Internet Routing</title>
            <author fullname="M. Lepinski" initials="M." surname="Lepinski"/>
            <author fullname="S. Kent" initials="S." surname="Kent"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>This document describes an architecture for an infrastructure to support improved security of Internet routing. The foundation of this architecture is a Resource Public Key Infrastructure (RPKI) that represents the allocation hierarchy of IP address space and Autonomous System (AS) numbers; and a distributed repository system for storing and disseminating the data objects that comprise the RPKI, as well as other signed objects necessary for improved routing security. As an initial application of this architecture, the document describes how a legitimate holder of IP address space can explicitly and verifiably authorize one or more ASes to originate routes to that address space. Such verifiable authorizations could be used, for example, to more securely construct BGP route filters. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6480"/>
          <seriesInfo name="DOI" value="10.17487/RFC6480"/>
        </reference>
        <reference anchor="RFC7421">
          <front>
            <title>Analysis of the 64-bit Boundary in IPv6 Addressing</title>
            <author fullname="B. Carpenter" initials="B." role="editor" surname="Carpenter"/>
            <author fullname="T. Chown" initials="T." surname="Chown"/>
            <author fullname="F. Gont" initials="F." surname="Gont"/>
            <author fullname="S. Jiang" initials="S." surname="Jiang"/>
            <author fullname="A. Petrescu" initials="A." surname="Petrescu"/>
            <author fullname="A. Yourtchenko" initials="A." surname="Yourtchenko"/>
            <date month="January" year="2015"/>
            <abstract>
              <t>The IPv6 unicast addressing format includes a separation between the prefix used to route packets to a subnet and the interface identifier used to specify a given interface connected to that subnet. Currently, the interface identifier is defined as 64 bits long for almost every case, leaving 64 bits for the subnet prefix. This document describes the advantages of this fixed boundary and analyzes the issues that would be involved in treating it as a variable boundary.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7421"/>
          <seriesInfo name="DOI" value="10.17487/RFC7421"/>
        </reference>
        <reference anchor="RFC7608">
          <front>
            <title>IPv6 Prefix Length Recommendation for Forwarding</title>
            <author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
            <author fullname="A. Petrescu" initials="A." surname="Petrescu"/>
            <author fullname="F. Baker" initials="F." surname="Baker"/>
            <date month="July" year="2015"/>
            <abstract>
              <t>IPv6 prefix length, as in IPv4, is a parameter conveyed and used in IPv6 routing and forwarding processes in accordance with the Classless Inter-domain Routing (CIDR) architecture. The length of an IPv6 prefix may be any number from zero to 128, although subnets using stateless address autoconfiguration (SLAAC) for address allocation conventionally use a /64 prefix. Hardware and software implementations of routing and forwarding should therefore impose no rules on prefix length, but implement longest-match-first on prefixes of any valid length.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="198"/>
          <seriesInfo name="RFC" value="7608"/>
          <seriesInfo name="DOI" value="10.17487/RFC7608"/>
        </reference>
        <reference anchor="RFC8949">
          <front>
            <title>Concise Binary Object Representation (CBOR)</title>
            <author fullname="C. Bormann" initials="C." surname="Bormann"/>
            <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
            <date month="December" year="2020"/>
            <abstract>
              <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
              <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="94"/>
          <seriesInfo name="RFC" value="8949"/>
          <seriesInfo name="DOI" value="10.17487/RFC8949"/>
        </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="RFC9602">
          <front>
            <title>Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture</title>
            <author fullname="S. Krishnan" initials="S." surname="Krishnan"/>
            <date month="October" year="2024"/>
            <abstract>
              <t>Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data plane. Thus, Segment Identifiers (SIDs) used by SRv6 can resemble IPv6 addresses and behave like them while exhibiting slightly different behaviors in some situations. This document explores the characteristics of SRv6 SIDs and focuses on the relationship of SRv6 SIDs to the IPv6 Addressing Architecture. This document allocates and makes a dedicated prefix available for SRv6 SIDs.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9602"/>
          <seriesInfo name="DOI" value="10.17487/RFC9602"/>
        </reference>
        <reference anchor="RFC9812">
          <front>
            <title>Clarification of IPv6 Address Allocation Policy</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="S. Krishnan" initials="S." surname="Krishnan"/>
            <author fullname="D. Farmer" initials="D." surname="Farmer"/>
            <date month="October" year="2025"/>
            <abstract>
              <t>This document specifies the approval process for changes to the "IPv6
Address Space" registry. It also updates RFC 7249.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="242"/>
          <seriesInfo name="RFC" value="9812"/>
          <seriesInfo name="DOI" value="10.17487/RFC9812"/>
        </reference>
        <reference anchor="IANA-IPV6-SPACE" target="https://www.iana.org/assignments/ipv6-address-space">
          <front>
            <title>IPv6 Address Space</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="IANA-IPV6-SPECIAL" target="https://www.iana.org/assignments/iana-ipv6-special-registry">
          <front>
            <title>IPv6 Special-Purpose Address Space</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
    </references>
    <?line 576?>

<section anchor="open-issues" removeInRFC="true">
      <name>Open Issues</name>
      <t>The issues that follow need review.
Each item gives the current working choice.</t>
      <dl>
        <dt>Intended publication status:</dt>
        <dd>
          <t>The working choice is Experimental (<xref target="experiment"/>).
An Experimental document that updates <xref target="RFC4291"/> can require review of this choice.</t>
        </dd>
        <dt>Allocation lifetime:</dt>
        <dd>
          <t>This draft requests an allocation without a scheduled termination date.
Publication status and allocation lifetime are separate choices.
Review can choose a different lifetime.</t>
        </dd>
        <dt>Acceptance and interoperability of the RFC 4291 exception:</dt>
        <dd>
          <t>The working choice updates RFC 4291 for the common prefix (<xref target="update-4291"/>).
Review needs to decide whether to accept this exception.
Review also needs to assess interoperability with hosts and links that assume 64-bit interface identifiers.</t>
        </dd>
        <dt>Routing scope and registry properties:</dt>
        <dd>
          <t>The working choice permits routing between administrative domains, subject to agreement and routing policy.
The parent entry sets "Globally Reachable" to True.
An alternative is a limited-domain design, such as the design for 5f00::/16.</t>
        </dd>
        <dt>Registry treatment of excluded identifiers:</dt>
        <dd>
          <t>The working choice is the set of more-specific entries in <xref target="iana-exceptions"/>.
Unassigned identifiers receive no entries.</t>
        </dd>
        <dt>Effects on IPN assignment policy:</dt>
        <dd>
          <t>The working choice makes no change to IPN assignment procedures.
The Designated Experts for the IPN registry need to review the incentives in <xref target="security"/>.</t>
        </dd>
        <dt>Routing authorization and reassignment procedures:</dt>
        <dd>
          <t>The working choice ties authority to the current IPN registry assignment.
This document defines no new authorization mechanism.
The source of routing authorization for derived prefixes needs review.</t>
        </dd>
      </dl>
    </section>
    <section anchor="changes" removeInRFC="true">
      <name>Changes Since -00</name>
      <ul spacing="compact">
        <li>
          <t>Added "Updates: 4291" and specified the interface identifier exception as an update to RFC 4291, as updated by RFC 7136.</t>
        </li>
        <li>
          <t>Separated assignment, forwarding, and host address configuration in <xref target="allocator-space"/>.</t>
        </li>
        <li>
          <t>Added <xref target="slaac"/> on SLAAC and link-type constraints.</t>
        </li>
        <li>
          <t>Added the Experiment Scope subsection.</t>
        </li>
        <li>
          <t>Limited the authorization requirement to address assignment and prefix delegation.</t>
        </li>
        <li>
          <t>Stated that forwarding does not require registry queries.</t>
        </li>
        <li>
          <t>Completed the fields of the more-specific IANA entries and clarified their names.</t>
        </li>
        <li>
          <t>Stated that later IPN registry changes do not remove IPv6 exclusions.</t>
        </li>
        <li>
          <t>Removed the claim that former 6bone use makes the block suitable for an experiment.</t>
        </li>
        <li>
          <t>Separated allocation lifetime from publication status in the Open Issues appendix.</t>
        </li>
        <li>
          <t>Revised the filter, reachability, and reassignment text.</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8U823LbyJXv+Ipe+iHSlEiLuksTT0LL8lgVW9JK8s5ObW2q
mkBTRAQCDC6SGNn5lnzLftmeS18BUHZ2dmv1IhJEd58+fe6XHg6HUZ3WmToR
g/OrhwNxVapZ+qQq8U6V6YNKxKwsFuL86kJMsqyIZV2U4jxReZ3OUlVWg0hO
p6V6oOH+O2aeQQTf1V1Rrk6EelpGzTKB79WJ2Ns5HkdRUsS5XMDqSSln9VDd
D+t0WRfLYbrMh9LMNlzq2Ybb46hqpou0qtIir1dLGHl+dvs+ypvFVJUnEU5+
EsVFXqm8amCZumxUBODtRq+ELJWE9y9u4fNjUd7flUWzPBG351e3l1fRvVrB
w+QkEkNBqDCL8gNvc/Tk3e1F9KDyBpZ7JUQ4FTxg2H6BVdL8TvyMP+PjhUwz
AIr2+MdU1bNRUd7hD7KM5ydiXtfL6uT1a/UkF8tMjeJi8fqXnyOYP63nzRSw
rO6zNFevGV39SBrA+xkiuYb37Yw0bsTzjNLixRlef99pjOb1IhtEkWzqeVEi
4mBlIWZNlvGhDs7K9F78CVce0E+wWZmnf5M1nB78PJHZqkyluFXxPC+y4i4F
wjvP4xG/rRhbsOcRouqPd/gdcQJr5kW5gGkeAP1CXL8/RXLSHw/Huwf648HR
8bb+eDS2H48P94/w4/nkYjKEkz2h1Qwb/A42+ztxE8/VQonP1+frCB/H2J0L
vbsTmpTnk+Wdqt2ZPj4+jlKZSzzx1xII+C5fwHTV66ZMhxUtV0VRms9aOxsf
HR/qj7uH22aTe0cHO/rj/njf7Hf/eN88Pdg7Mvs93NuxuDnYPjIIOd47NggZ
H5oXjg+2zQzHR+MdD03/djC8uZqcnoXYIk6ZJEmpqkrcLGWs/hcxky4fDoaS
Jx9WOHkLnLPT88nHHoBulipOZTa8asplUan/OwDh4ZCgrPSKpbpLq7pcRdFo
NIqi4XAo5BQeyLiOott5WgkQeQ2OFqX6awNMWgmZs8B5PTZCRwARiAYAn65a
omcUndcigXdyYBUpFgp2kYi6gGcor91ce0d2LpTgUuzuDKdpvVaUj6LPsF4x
E/Vc6ckSMwNAXSyRZ2U2gk0os2ypAMaKRqgn2DaKunB+gw4Gu4CX86IWKo+L
RInlfFWlscwEvQ3TwzHovQG8IDJpwgUIBxAa1YKXRpBUWQJwHroAwP0Z8MYJ
PBu10CyzqhBa7SBZk+ZBjC1VuQCEFAB+KdK8VuUMqEOkFiUiU/ldPa/EI0jN
NKd9aikIy0/hwz0cMZ3xIk2STEUgyc/zuiySJqb9PL9K8evXKJrkazEvnp+1
UPr61a1OZMFEmtYrWFvCVoj0KprpAjF4QWqv6my5qgqgxponMUfnazXakp7U
rMH4NWMRfHtgiariMp0qkasaNSegb4nyunWuGvgVnF6unmoxL5Z4pEDkcpql
1VyfqhoRPhwuYoASqb2H9OCceNcMvRYGyp6JBqgSTZ7gMSI7JYs0R6qjTXyT
YL9X4FtahvMymuPr1xAByNJpqWj/j0hgQ4+aHC8AnbyCBYulAgqp8P/XtnCw
LJ6bPQsneNo8Yb8KuVxmSDuAthq5BNYDqeSwJHMSFiRL7dMXOYaIE1kGiBOl
UucEEJmgkxdAL/rMNp6fefSQx22OOrtzhIXbPImiHwBnYLY9AKaR8qYAmlI5
i7MLEBjJsgBW8pkTtyJDsviR5slZvuDZgjjTM3jsgiR5o8qHNLZP0rx/KvEW
yCpTYM0WdREXmWZVUJeADQb3DhZTYG+tVKnHOJkcy7JcabaT8b0C4oSVpjSn
WcGIuaVZAnFMnF+gGRAzx4gkBTqB5VbusH+EV/UcTHaEWlgWWYkWxW1lGZjy
AN7wtshUKeGNCz52XHQDrNhNOIRlVqxIo42i5xOiDvj1zQCOFT7Wg69MsZ8K
MEukFmwL++Vri5tlBnZ2AoCCcrwjLYXWIJMcUlBXek0Al0isyyJPWIc4QYWy
oUrBGia5YlghYHGa1ZI4CTXSnSDZaTFHNMwAoSQB4rzqKCKPQGtUE7kTfXDs
uQLx/oBiGRYGIPIK9AgIxDRetXnJTqSlmLGdiTwUkEGN/DkFciVIOmKxVLWE
Y0S51pKMj3PFz/Hwl7QYEgZi3GxjFJ2Cl5SCk4KiT8LP0zRDsOHEgaVAq2ul
9gCGNYhoxcTGWCJREtunRKO9W1zIe9qjfa0CVJqV7hqJRKdUKCitll8U+kVP
pBGxnT2B+ExpASMplX3UEZdkfhmt6d5j8ei+C/Ugs4bkGuwbaIQsMMBURSII
UErGgJHUwxDlMOoblPijP8tSlsC/6VISUnAgcSi9CDM1y2VR1oR/ND5AfSV2
VpgPLIim1FLCwqURjMczSzOgTDoVtmOCiXwi/RHf96cxZJIGxFagpZIR0RVx
3JQk32FB/GUG584rO+N3ragITwZlcVOSIIBTLMmIpQ1YhCBbojnWsI1QKsRL
pU3RtPTEkz5JlLidk7VUGGcyXZDkb4lQeXcHB2sNTVi/LPBwe8iWaFCcooDP
+bgQ4ndItCl/f34Vu19p00rcqxXGFYCvBp8+39wOtvi/uLikz9dn//r5/Prs
HX6++TD5+NF+iPQbNx8uP3985z65kaeXnz6dXbzjwfBUBI+iwafJr/ALAjm4
vLo9v7yYfBwIUs6BYgfTBDA9ZUIpgarRkJVVZOy7BMe8Pb36r3+M90DX/Qso
u53x+BiUHX85Gh/uwRcUPbxakWcr/RUOaxWB0FCyNIonlsu0BmsC3gWanheP
uQD6Q/Pvh/9AzPznifj9NF6O937SD3DDwUODs+Ah4az7pDOYkdjzqGcZi83g
eQvTIbyTX4PvBu/ew9//AUMfYjg++sNPUZsxrCWKCgZIxlOJAz7J0EgZIBJZ
btIxeV5DvwEXzk9qcVYAvz+injF8fxKdiEkeBGaQOdgp+k73Aw2+G8Uez+5o
B3nPgrbpL+bZ03rdJscpYUPaO0W6vIOVJ7xi6A25eV5eUIgBsqN7HX6fDNBJ
rIPHtAQ+QnO+37wXIAhLgAGoHIQTSCU0NSawp1Pf4sXN4IptL14v0Of0I5Sh
O4uaSbU82ehdoIDCdZyHf7Ux2XROX8LOXZGrfncTwT/L0rsUVXvaPpHeIT0b
Ya3DCAGZl+YSUAc0hxt7flY0P8lSQOId7IGRXzZZv50zL7IEjAEUUHPUQOuA
f/nkz8DG6R+XVj0IglMNFmrzESoIQFBFb7XML9w3mlRCdVGJ8zQg9cJd0Dbl
g2ptM5yXNQ9Hz1EBsSXAJnfsff1KRpKmQv06voHfdYC2o4ptwMlSGIqUjv82
ij7DPjLmChPv6Hlvy5sHltGzo0IB4dXkLC0wg0CsBm8sORpn5q+1FvFQZHQA
GNUKBU7eh10EmqiPkgDG4QniPzZOgy9o76iiTIG4Vg8p+OZARxS8I7fEuKjg
n6RlhVKoqiW6dTocdjDFg3LGhvOocekE196GtY+0ewPMidF3tClISGMEl1So
DuGywIb9UQhJPMJ+MF6PdifYfIgy2BNhH+ebNWgI+huiiTDqixOxGjjY3oEV
EKPC4l1DBaczI4/3jojgWls76EwyrBs31w8Hm/YFL+YBP52/qzwRjgPdoaun
mryIOsS3TP4COGVX1MIwin5x4YISI/u5nowxR+ewxXQSzwtUe/KhSGH2Cgzu
mo1PQFOJ2kFmvEMdggtDIJ6PgU6O8XG0hxCTfGZZi5IrF7h72OFFUZNxhO9i
lPAsSUk9ns/ajCBpCtaQxMUWI1tovGbo5w7w2cBE2fywIS9dz8HqvCPzOhCr
WgLpaeg80jzOmkQzYNsh2dKxLEoXVWyTWY0Go0tyKydoD5RA+DrGxs6KRK7S
JmKlZaoZz94FkPFTzbaGNpKZdBUy1QIoiAcDspX22kyg/aNc4d6eX2X0oSOK
cm054FrjnSMxTdnib0VhOHa9jecy3jkcRW/BRNg2inxRAKsireOxYmADJgEw
voi3OJkQX8RHit/ip/epAv3y4t+X6MtQ/9kPJ/bTS38wUmwPx/u0JpAGbeaL
CEyEtWvCgOHeIY7c3TEjezVYd+Te0RCwAu8fbXdGDrU/l/leJYVgvqDf9qqW
0yGfDWdO3gz0kfEhmHNEQ96mglnNDLS34wWdAuuSAgcrPDJSj+gFa/vR6i/k
obbau+3Gfkkb4D6kCzMCmQOfamuxX9MvFipBNQ9AyBlRcVfD4WqeRqGVnO9i
hPt0VaOUSFCjf1SSYlN/U2XB2EZvyic/w0tTtoVmSHK8kskj2OxKnC5AhxB3
YbqPXSn+EXR+jHz6lme5nP4FWBO0FkBemeiB2Dh9e3m9yYoA83gg+23Mk0wM
8IPVbIYjtfjT0EyQ3BB1YcSW4j0vYnVJSQ2M2IDdqZmd6MLEAxP7BejjPQcx
+83PLRP9ASQbcEgqchDmg3gjZllRlBsT8Voc7O/vHmyymAPW6uN5wusEh36E
oRN4J2mygkfagZmSa0euiWP8YoS3s2xa9k9vqgw28fe//z0im/wN64YPJx9B
P+wd0Q/RB0L3R6KfR/CualLa4Bk/SUMZdFqWXrRFYYjFM4F3rAlsI+23nj7o
RgBMlqVUuBWOFfXOvKfnxYwym0ck3q14OXXiJUiuAiW4QgE2rqKIBDK4KyzG
cWYSDdIJGfZgACGcxmGO5YCURkLozfE+O9Grqi9ZgtjWp5OozESAdPYCF6bJ
ADGSA2bobbKFIqqG2Y/sgsDDDgOkdELGwuAA39pAsMsRcYCwAaPGBfwoX2ZY
mcUeQKYFPBpidl/GGQwdjHaYmcT5SkugcNNCXBq/7fXBHu41xwyF3jr7d0D0
sOi1H3csykeJ4+4QANq4e4RiIubskIlvroGERBdWI6BFIaxVyhFmF3WvxOM8
RS3C52cFqYskJmDH1igw6UjiWC1rnPC9g8lA4tLPNh9pfkIDeY6ixZAPxjzT
u8akEKMPRVV7OWKbPEActLJd1jPuSylXvt0ISCchtC6RhvughXFrWZrfB/Dy
RAYjDxJNPeTgKpMydiz7mWBDCra57+dXPsBaWn8zrbfViWSgBVhZCWkSUJQk
hL3ZeE4bB5oz1BOeFbKiSTVq2VOBWNsfjWnX+IlEkZeGpEyCSXSSE6/N9pZO
c5n6VdvIjnwRimv5QpSilQwTjXXv7uv3sMII37Oe5Qu75QhJk4NccPSltMWU
FESQQI9wqOQsaONhe3t71AJyLwASxxivvJILpY0rmeoT+DkrpqBIPrfX7YQK
k8RECZ9q34yrtPFEkpplcMUqm1Ymsw9U3U9COyyOAFzKyxiCvcRFooM9YHdU
1oH+J+sQxQZS97/DH9D9T+I8563Q9BRj6K3vsBEZTzDZoCDLQ0NNmqlfcBSv
jetnIPHcv1wnnmchIW6xx97jS8EmjaTAc4GBAb12SdSjyqpOYbRmkBFxtzYI
tl5mTGvLcMUQuGJnZ2fi0+R0SOltLzuFC9j48idQVjA8EWefz4cg07iAjZjM
hSYw/gYyDHDItlKsEiMs6kAaIHdXlO5uOL4TMj/SeaxKEBLotwuMT+jgdKm8
PCvHUOaB1K5aPuqpL+OxEIMEZ9SWTpacOW0mbj5OJqeoplEiD21YoVdzsD5M
MJE3ii6t0lo0aIuCLRLXPSk/S4IpK6XKyn+rVWEnQOI3yIgZDjZbmjRYQ+AD
sEHgbuLJEzbwcIKqEnPWVpEmgVPQzznoSND2scw1NHxs5UptHR+me7lOG3wi
7uufrXKZYjeX0Zu+uWplOBY7WkOYCeAuL0oNkBe8tQjgekuYJGVLE2WcUatG
QDcLNl6POivvAz/uGtF8dLCDHAhEDsZ0srlpAsGaZtCgBGnKR6lPwopG0mR0
GmiN2RrblytndKURzx+m0MWZi8HTWV6aOjAs9Ht+5Yfo2aPXuQ4OHv22sijf
gvMW4lOhJMALIYO1WYvxyJms0jOEhQC3z0BfdN8gl8HaZV1vwqsyc+eBKNP+
gnJWLB2QsZ85c9ZdjoSdxQuG4VoZNF6R6mISBwswaYaB5oITqKJEeUPrXBPG
dnHUoajlvbIiFIPUD0oLUUQsoGln5M4apDThp5sQozBEQhY2lwXoQLrd3Df9
lwqcyDwxG3WlOHSIPodHuyOwRKxk9oyjE43Fpu9Xt6YucWi4QrVbDANL7I3E
NVgo5UPfAqLs/tSZvZ3FEhzl6s5pQrJi++lom/8QedtP7/UfgLM/8ipY4Bza
IJ0H0xFNBu8jj9L5i43tp71glUO9yqaRTijx0VJ7AqgqLAL2XOc7sgOBucAC
/Wujws6Gl46ZxfBKu1qWmPyyjDAUDZs+wE2TpSGuEXZLeWi3Bb+IjePDvSMO
CRwfHh3v7W4i1yD1GFC0/nKS9tjKeC/TK847xKAqawyQn+RtwJWSALSHo35J
gxE+Jpt1v75IOjaEgWF1X5cRuM/PILhlk9WunyJMkCpZ4atrYlLrErRptS5Z
RmoFNBvKBjG2fhNKt9KXKpqWiIiAtDGUflH4NmgnlsQVN+vCfAYWNGZ1ENhm
9zqyluq+14pawChbObhNu0eTquC552AQu3IFGromagQn5GkkjYQ7FKK9pba9
0SOaaGVw5iQiFRqRJAVeI6HPtG91ARXtefESqQtDtWmKvPKO6cMDHYOrbZox
1jVXjVu9spZitcPSnTxMqHdT6v0gkVBEQzar0yXlkTjbxgrY1ZJg8ilQwzKo
xJ2u1kDVLptsBQMNw1Msup3k1rBdbWyD2cvhI1dVsXe05WdVWwz6LVsLfMIk
fUiNX4JLaFvLRFyxSpE/aqOqE4u1qTZYHvyoxqjOShOVC9H2Rp395H0eqiVL
9R1x26ZXnUwIZCPn3fz6vmhNJuqL+ODFqjmh+UWEpSphQi34602q9TzDFFf4
p3XGF1CCoA3PzlAlmnwY40WdqG3KKONr/eOP/fHjvvHj9eNRU7nxoIS742ez
mRlvEm2WBnSqzZxNmFhT1UAH4ybijYZ1S3xA4h3voRmgNnXmAMn5cHdvnx4C
vJpNbXosVLU6g1aJve3jA7Gx8+fxzqZPN1s6y+pwSmaG2SHPPd55IYXiDUWq
RoFjPB9ONyMYC7ms2OzVFAIDtU8HyBriCm8Edu5RliQ8zd0DTp0Ap/mx6EuP
fLFWBjaleQn40GSsXygV7kp71JamzwisvHS51lNp2xyUu5q000E9MWe/NHdE
g3r1TtfezlkZuxYcHe72umoQgmouS9+r8NpzFgi7NG+YutekwIC/ASVMJ7CA
0O0HBDcMdH0jMGR95N5mEEz9rYkwcMqY9DfXzmvI2zgDpYKSWVMwpmHAOq4w
fZjJ1RY1StjC9ViitaQxap3EVs+QTm24UboMw5Q79jTYrC9zXmeKsQ9nS8cw
E4ufdDmRX4bvh4Rcn0FQqG8AZJO70xLHWCTUc//ANxQYRnOwApcCv65wHVwG
JgIxLcB6pex10Zs3dwB/mvyKxiLHxLy2AZhwhvEwMuXbdrlt6+lbHOC/wfCI
nRWVpUvAybtScYDZzILwhTXlbOV4mHKoYcwosiYsXmx3gmYlU/TVAVxn0alG
PcYeP7AWyWo7M21kXDFT6aYNBtqggvUylgZwwZLDYq44UhnPVXxv5+CMgYuK
6/QiZZ44BbcAQuOqNH4clIRNbPkOCq6FrGF2kymBTVDglAPvrkTMj9Va9NBQ
v7LubVlIdG40oFscz0LT2yyJoJuiri1CBk9CzTi0KJLp+azHNE7reVLKR/IG
0A3SJu2WCdw9pEVTtYMYWYGMTeUY1vqngIh2HKwr5iV/Jr0lh7rTpm+aqsiw
mmSqYonWWVpbcODpHCuLJtTExGRrs1EstGxHN9uMncAQywtP3GuTN3Rf/Ebd
azOBaeTQdp1teGCHnxN/7PK6KiAUoMyuW+4YC1vr/TdTMxljI4NtuWXcI/Fh
uNG1IzsCLtgHrpXOFJmkHnZ2wHjSvCn6CzJXOJeOJXC0CRU7eCEN4b2jySv9
Cwtd6ZcmtdSteloWJi3hlfv2o/F2DYIFlaoSo/tnZ9JWfq34CAEqpuRxuDbW
tNYBRV7fygGbDvIKjl/y6CnAUBaAJQx60U81LynrGt1GXtIE/JUf1tfQtvBD
OXhWdkHRMwwFBM8XCrtlwFBbsl1gfLAG01Q162LTyOiRjOpV8B6d+mg0s26h
8wd8q7LZVriCNmdgBfDSc11+gLkEqRtYQTSaldfYFqaGoQBWohjEJLeaQkdi
Sd5XdjHOWrfQhcRNFAyTYyyMFA5B5bUbY1fLN3r/YqxmVhifLJoSpPUVU9ef
wCU7z2eldNUfG9dXfzrXhV14gwMmvHBj5KKqKmyiM9PSBi4ZronPxpgWvZxU
m3RYxLmwENUTxHMmvhmXHTvLB9OHWBjqqzPWFb5ip5ymLwh0eOWGxoaiBGcA
r+RFKR7rNkXENSMYN8ZiCsD8FBTMc8DH7xmnBLjqD7dyApTD4xRb2+JQ2D7X
tYaNCjr6ZboDO851GCKOznvz/RVsvm7XeIDBjeVzJJiCckymRo+lLdFVuMWN
nuoDk+GK/D5ZP6ZFUoGJA08JHBmE7oGlsY4rvJBLx9wmFlr7YUTy4SoWPrr6
mt06gGnnz/cBAqynl9ueO9X29u5NpZp3bYRnf7u8qXhUOpjLxhssrNUxOmEo
X9Ip0n9QNkyoZbVC8rqjUrD2n1souheYCCu3+D1bxkZTBZ0OuEltpemycAMB
8wzyyv/sXqX2ZRfhvK0uoVtrW+Ivae5ZYFT76duLpjOBXwfyCntGvmLMjIs0
9rTvzaD03fTSk/szt8QAM3HDlJkFrcSBzdDgvSZnt+8HI9tZgOfiDGXmDeP6
+o0bbKgejXfQ0v2uelaPiltVrOAsL+D8MBBJ2AC+YZ3LYOpuBBNV0XpxtIYQ
tL1VfxNXbPYhaVjcEFvO0DGLVcdctVT64q02PVRLb6+l24TD51520hT+aAP2
e67SWUcBdDGPbU/Ba5gwSg2nwiXLY/puyoBNeTLVN+rp3+KBYHWdpfMousBL
pUzR4T/JUGBFvD/lkkkPu5FHfuId3R3GRZX6KGX9zS4o4D5y3MM5Ll5PouiG
tD1NibeQRe+I9fjyK/tQFypiOMI9/Nlk7a45GOD/ZnhoOF0Nzb0U+Ot7mVVq
fU826jOusqYYXQL6YsqxHepppuQYh9qp+8ZEo9sJrnbBp4zLotUG/6BMGIEc
70F3MwMb2jHFOyZzgppLz651MJwEeP5ygcGDVcElKf2xC4+0QjvJ8/JtpOyW
M0eKOtSRfj2n9x64gq7aaHsXNqX1AkfpGi7DRP4aJ9Fg8p0JJlcoZyU7tRv4
9ch9eSwYElRwh7JkYO7xKNXwxhQunXGXkBEbtvAJExg3xaLbcxRmVwOL6EVJ
g22Prl5KNyexFcZBcrvwV5uo0y+tKXkI0csJC19+cGAexUZ/+03QUEOywzeD
bKPNd2Ur+juDXugYsgkpB4FVjxsISycrtmne2+6Bn1uC2mFzzMuE+fRObmjT
TPpEEfwh/neJDTup1lXjox5I+ysXNmlSU7swdIULbtIjPelhz6T2W+mgNJAe
uUnfu0ldusVQkkm4gJxE5ZX0kz4KSOocZklgCxu1uPTD/8b5YR+atdbJ/59u
2RKeTtkSni7ZEl2xy+2Bv11/cESPErcBbTnDZpeTYDvbXp3BHtcZUDln4HWN
sJaRaoawHkqbrNSHi5dpeLURHAaFxRqv05ElwFxR2Mu/MMAEGD3PpFUM26Jr
klua5loR13a9B/0cOJxBZclE9/OGAcEg2unF+6j41zQ+6iIeLBXUeaq++nV9
VR/ddUMea+KXU9uydCzRAvwgvYU1mgZ5fgsL0qIO2hkT1wMSw4GktR/SpKH9
tqt/1tXC5UFlCjuNU2w/UhgEpLXNTTO2pKz/5jRbERSQz+aLnTbo6RotgpTp
7nPoLTnDrXNB9+8qgZXeJxwdo4iGa6Bnxs05Nd/kpH/ZPdEFCp52C5L+AHyx
VPkwrSqYyXVpfF+xZcfGh1Gd/Ka7CEdHh405/9vvuVs3dXA+nutu6n79m+9A
+4mpjO/RN78EVIhzQgXsyEcMyCFmjDQvZ/GbAV7jaxpP+ZVALFMUmk9AXwJB
JbhOdJjiUHPxGRu5OoRDXXAc8eUtsIwx8jocg2Ii0HdIj+5iKq5KA14I3rGH
w5eT9Vytx2kjdnd9UrLt8KNAn2TpTGE21GkdvLE3uFLU68j3+AtOP2ky6vpz
mgXBQbCvOjhgT7q7LlujRrhYl0EYL50iUPMCHUYpknQ246SjGY6bcQk3qmPB
UBqFaLU9qxnJNi1Zpb7mWDo3fPZmMPvuJrRA28gbV8b6hbE6095uVbBD6cYd
O15imqXq7okSAO2SflMYDATyYh+R14dHV0ayajW8uqSFsHdxDX5M9bPJjL6c
it3qz7zSkq3L4PQ9Nr4vVWGCoNfvg9nQi9U8IjHGnPPCfoPIUHt07JG6LCNn
NMhL9fKMFAKzkpFuDjHVZlY7BuW369iaQsmKBr7gq7S9JOpf7K9uRr2pUt2O
bS5jiM6oMZtyyu2oJ6F0DYAt4Ut3hKwLmppTeUfIohwYySN9X0/HGjFZPC15
8HcvaEzbtkm4r35DaBDpZ4LsBWjNnqjX1rtlqgiEdQCim5Y313dZal5QvDuE
yuuKYKToJAwWY/Ruo7dygXnbqBi6HU7rwBvElBhub+P9O/xsrfr6Af1TmHbw
2b8Gn6/7cvYeo7+nP8s1JUkS8U2nt7PdGIbPsS+MymJutLxOhJ/vccEcNqrX
98EyIbTbu7+O3L5s9yldrEJNKUbQcXOP61KsvGFh9bu+7xEEkLaa6M2Punes
nrcTTK3bT7+/hhdRUkuelGwJG9XqFF9ZMsS6XmbjH/CCD4oMmytT/J79UID4
17Gw3ZjJ0h52WvINqR2I2IsI2KCV8tfeQ+g66MIs+olh4zsRzS5dMgATaCxX
8C32Hqomrckqn/ElDv5tmiER9ZgFFITtmlImHe0bfHjdBvgTTxrYB2o9Y0Si
WtgKCqG2usIFi9LXFWf9N3xtGuHXYgAA

-->

</rfc>
