<?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.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-morrison-alter-uri-scheme-06" category="info" version="3">
  <!-- xml2rfc v2v3 conversion 3.32.0 -->
  <front>
    <title abbrev="alter URI Scheme">The 'alter' URI Scheme for Dispatchable ~handle References</title>
    <seriesInfo name="Internet-Draft" value="draft-morrison-alter-uri-scheme-06"/>
    <author fullname="Blake Morrison">
      <organization>Alter Meridian Pty Ltd</organization>
      <address>
        <email>blake@truealter.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <abstract>
      

<t>This document defines the <tt>alter</tt> URI scheme as a dispatchable
reference syntax for <tt>~handle</tt> identity references published in
the DNS records defined in the companion specification for
discovering Model Context Protocol servers through DNS TXT records.
An <tt>alter:</tt> URI binds a
textual <tt>~handle</tt> reference to a resolution and verification
procedure that retrieves the handle's envelope from a publishing
zone, validates the envelope's signature chain, and dispatches the
result to an operating-system URI handler.  The reference may be
scoped to an organisation, narrowed to a named facet of the
identity, and addressed to a typed action surface.  The scheme is
the addressing form of
the <tt>~handle@org:facet/action</tt> reference; its resolution semantics
are those of that companion specification, reused without
modification.</t>
      <t>The scheme is provider-neutral and introduces no new cryptographic
primitive.  A handler given an <tt>alter:</tt> URI verifies the handle's
envelope before acting on it, and where the URI addresses an action,
verification precedes any side effect.  IANA provisionally
registered the <tt>alter</tt> scheme under Section 4 of RFC 7595 on
5 October 2026.</t>
    </abstract>
  </front>
  <middle>
    

<section anchor="introduction">
      <name>Introduction</name>
      <t>The <tt>~handle</tt> identity primitive defined in <xref target="MCPDNS"/> binds a textual
identifier of the Sovereign or Bot tier (<xref target="IDCOMMITS"/> Section 3) to a
cryptographic principal published in an <tt>_alter.&lt;domain&gt;</tt> DNS TXT
record.  An Instrument-tier handle, such as <tt>~cc-example-model</tt>,
names an instrument whose acts are attributed to the Sovereign that
operates it, and has no envelope of its own (<xref target="MCPDNS"/> Section 2).  A
handle reference written in running text, such as <tt>~alice</tt> or
<tt>~example.com</tt>, is interpretable to a human reader, and a machine
cannot dispatch it as it stands.</t>
      <t>This document defines the <tt>alter</tt> URI scheme as the dispatchable
form of a handle reference.  An <tt>alter:</tt> URI binds a <tt>~handle</tt> to
the resolution procedure of <xref target="MCPDNS"/> and to a URI handler registered
with the host operating system.  It carries three optional
addressing components, an organisational scope, a facet, and an
action-path.  A handler that receives <tt>alter:~alice</tt> retrieves and
verifies the envelope, then decides what to do with it (open an
inbox, show a profile card, initiate an Accord ceremony per
<xref target="IDACCORD"/>, dispatch to a per-surface MCP tool).</t>
      <t>For example, <tt>alter:~carol@acme.example:security/verify</tt> names the <tt>verify</tt>
action under the <tt>security</tt> facet of <tt>~carol</tt> at <tt>acme.example</tt>, in
one string.  Every component beyond the handle is <bcp14>OPTIONAL</bcp14>; a bare
<tt>alter:~alice</tt> remains valid.</t>
      <t>This document specifies the addressing syntax, the dispatch and
verification obligations of a handler, and the operating-system
registration entries a handler installs.  It does not specify the
resolution semantics of any facet or action surface.  What a given
facet or action means, and how a resolver computes its answer, are
owned by the specification that defines that surface.  This document also carries the registration template
submitted to IANA under <xref target="RFC7595"/> Section 7.2; the DNS record format
is specified in <xref target="MCPDNS"/>.</t>
      <section anchor="requirements-language">
        <name>Requirements Language</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>
        

</section>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <dl>
        <dt><tt>~handle</tt></dt>
        <dd>
          <t>A textual identity reference defined in <xref target="MCPDNS"/> and tiered in
<xref target="IDCOMMITS"/>.  Handles begin with the tilde character U+007E.</t>
        </dd>
        <dt>Envelope</dt>
        <dd>
          <t>The signed identity record retrieved from the <tt>_alter.&lt;domain&gt;</tt>
DNS TXT record of the publishing zone, as specified in <xref target="MCPDNS"/>
Section 7.</t>
        </dd>
        <dt>Organisational scope</dt>
        <dd>
          <t>An optional DNS-named organisation qualifying a handle, written
after an <tt>@</tt> separator, e.g. <tt>~carol@acme.example</tt>.  The scope
identifies the publishing zone under which the handle's envelope
is resolved.  Because a handle carries no zone of its own, a
reference with no scope names no zone (Section 3.4).
<tt>org-scope</tt> selects the publishing zone consulted in the
resolution procedure of Section 3.4; it carries no claim about
which context, tenancy, or organisational capacity the presenting
principal is presently acting under.  A resolver, facet, or
action-path definition <bcp14>MUST NOT</bcp14> infer the principal's acting
context from the presence, absence, or value of <tt>org-scope</tt>.
Where a reference needs to carry acting context, it does so via a
<tt>context</tt> artefact reference (see Context Artefact Type below) or
via a facet or action-path defined for that purpose by the
surface that owns it, never via <tt>org-scope</tt>.</t>
        </dd>
        <dt>Facet</dt>
        <dd>
          <t>An optional named aspect of an identity, written after a <tt>:</tt>
separator, e.g. <tt>:security</tt>.  A facet narrows a reference to one
addressable face of the identity.  What a facet denotes, and how a
resolver answers it, are defined by the surface specification that
owns the facet.  An identity-pronoun
reference axis <xref target="IDPRONOUNS"/> is one example of the kind of
specification that could own such a facet.</t>
        </dd>
        <dt>Action-path</dt>
        <dd>
          <t>An optional typed surface addressed under a handle (and facet, if
present), expressed as the path component of the URI, e.g.
<tt>verify</tt>, <tt>decisions/123</tt>, <tt>billing/invoices</tt>.  An action-path names
an operation or resource surface; its semantics are owned by the
specification that defines it.</t>
        </dd>
        <dt>Artefact type</dt>
        <dd>
          <t>A lowercase-alphabetic label identifying a member of a typed
artefact genus, carried as the first path segment of an
artefact-ref-form URI, e.g. <tt>context</tt> in
<tt>alter:context/9f2a-freelance-b</tt>.  An
artefact type names a member of a genus whose extent is owned by
the specification defining that genus; this document defines only
the shape of the reference.</t>
        </dd>
        <dt>Artefact reference</dt>
        <dd>
          <t>An opaque reference to one member of the genus named by an
artefact type, carried as the second path segment of an
artefact-ref-form URI, e.g. <tt>9f2a-freelance-b</tt> in
<tt>alter:context/9f2a-freelance-b</tt>.  What an artefact reference denotes, and
how a resolver dereferences it, are defined by the surface
specification that owns the artefact type.</t>
        </dd>
        <dt>Handler</dt>
        <dd>
          <t>An operating-system component registered to receive <tt>alter:</tt>
URIs and dispatch to a resolver.  Examples include xdg-mime
associations <xref target="XDG-MIME"/> on Linux, LaunchServices URL handlers
<xref target="LSHANDLERS"/> on macOS and iOS, registry entries under HKCR on
Windows, and intent filters on Android.</t>
        </dd>
      </dl>
    </section>
    <section anchor="scheme-definition">
      <name>Scheme Definition</name>
      <section anchor="scheme-name">
        <name>Scheme Name</name>
        <t><tt>alter</tt></t>
      </section>
      <section anchor="status">
        <name>Status</name>
        <t>Provisional.  IANA provisionally registered the <tt>alter</tt> scheme
under <xref target="RFC7595"/> Section 4 on 5 October 2026.</t>
      </section>
      <section anchor="uri-scheme-syntax">
        <name>URI Scheme Syntax</name>
        <t>The <tt>alter</tt> URI scheme's generic syntax conforms to <xref target="RFC3986"/>.  The
scheme carries two disjoint reference forms under one scheme name.
The grammar uses the ABNF of <xref target="RFC5234"/>.  ALPHA, DIGIT and HEXDIG are
its core rules, and <tt>unreserved</tt>, <tt>pct-encoded</tt>, <tt>sub-delims</tt>,
<tt>pchar</tt>, <tt>query</tt> and <tt>fragment</tt> repeat the productions of <xref target="RFC3986"/>.</t>
        <artwork><![CDATA[
alter-URI          = "alter:" ( handle-ref-form
                                / artefact-ref-form )

handle-ref-form     = handle-ref [ "@" org-scope ]
                        [ ":" facet ] [ "/" action-path ]
                        [ "?" query ] [ "#" fragment ]

artefact-ref-form   = artefact-type [ "/" artefact-ref ]
                        [ "?" query ] [ "#" fragment ]

handle-ref   = "~" handle-name

handle-name  = sovereign-name / bot-name / instrument-name

sovereign-name
             = ALPHA *( ALPHA / DIGIT / "-" / "." )
                 ; Sovereign tier.

bot-name     = ALPHA *( ALPHA / DIGIT / "-" / "." ) ".bot"

instrument-name
             = "cc-" 1*( ALPHA / DIGIT / "-" / "." )
                 ; Instrument tier.

artefact-type
             = 1*LOWER
                 ; the artefact genus member name; lowercase only

artefact-ref = ref-segment *( "/" ref-segment )
                 ; opaque within the genus named by artefact-type

ref-segment  = 1*( unreserved / pct-encoded )
                 ; "~" is unreserved in RFC 3986 (its section 2.3), and
                 ; any other octet is available via pct-encoded.
                 ; A ref-segment MUST NOT be "." or "..", and cannot
                 ; be empty, so "//" and a trailing "/" are both
                 ; malformed.  See Ref-Segment Traversal under
                 ; Security Considerations

org-scope    = domain-label *( "." domain-label )
                 ; the organisational zone qualifying the handle

domain-label = ALPHA / ( ALPHA *( ALPHA / DIGIT / "-" )
                         ( ALPHA / DIGIT ) )

facet        = facet-label *( "." facet-label )
                 ; a named aspect of the identity surface

facet-label  = ALPHA *( ALPHA / DIGIT / "-" )

action-path  = action-segment *( "/" action-segment )
action-segment
             = 1*( unreserved / pct-encoded / sub-delims
                   / ":" / "@" )

query        = *( pchar / "/" / "?" )
fragment     = *( pchar / "/" / "?" )

pchar        = unreserved / pct-encoded / sub-delims / ":" / "@"
unreserved   = ALPHA / DIGIT / "-" / "." / "_" / "~"
pct-encoded  = "%" HEXDIG HEXDIG
sub-delims   = "!" / "$" / "&" / "'" / "(" / ")"
                 / "*" / "+" / "," / ";" / "="
LOWER        = %x61-7A
                 ; a-z
]]></artwork>
        <t>The two alternatives of <tt>alter-URI</tt> are unambiguous because they are
discriminated by the single octet immediately following the scheme
separator <tt>alter:</tt>.  U+007E TILDE (<tt>~</tt>) introduces a
<tt>handle-ref-form</tt> reference; a lowercase ALPHA introduces an
<tt>artefact-ref-form</tt> reference; no other leading octet is valid, and
a URI beginning with any other octet <bcp14>MUST</bcp14> be rejected.  The
<tt>artefact-type</tt> is restricted to <tt>1*LOWER</tt> because the tilde
character is reserved as the handle prefix under this scheme and
<bcp14>MUST NOT</bcp14> begin an <tt>artefact-type</tt>.  A parser that inspects only this
first octet can determine which grammar governs the remainder of the
URI without backtracking.</t>
        <t>The <tt>handle-name</tt> ABNF carries the three tiers of <xref target="IDCOMMITS"/>
Section 3 using the lexical markers of <xref target="MCPDNS"/> Section 2, a
trailing <tt>.bot</tt> for the Bot tier and a leading <tt>cc-</tt> for the
Instrument tier, without restating tier-level invariants; an
<tt>alter:</tt> URI carries a single handle and the parser determines the
tier from the lexical form.</t>
        <t>The four identity-bearing components of <tt>handle-ref-form</tt> are parsed
left to right and each is bounded by its introducing delimiter: the
handle follows the scheme separator, an <tt>@</tt> introduces the
organisational scope, the first <tt>:</tt> after the handle (or scope)
introduces the facet, and the first <tt>/</tt> introduces the action-path.
A <tt>:</tt> appearing after the first <tt>/</tt> is a literal action-segment
character, because the facet, if present, is fully consumed before
any <tt>/</tt>.  An <tt>@</tt> appearing after the first <tt>/</tt> is also a literal
action-segment character and never introduces
an <tt>org-scope</tt>, since an <tt>org-scope</tt> can only follow <tt>handle-ref</tt>
directly.  Every component after <tt>handle-ref</tt>
is <bcp14>OPTIONAL</bcp14> and any combination <bcp14>MAY</bcp14> be omitted.</t>
        <t>The host-component slot of a generic URI is not used.  All
identity-bearing material is carried in the path-like productions
immediately after the scheme separator; the <tt>@</tt> in <tt>org-scope</tt> is a
component delimiter within that material and <bcp14>MUST NOT</bcp14> be read as the
userinfo <tt>@</tt> of an <xref target="RFC3986"/> authority.</t>
        <t>This document admits one member to the <tt>artefact-type</tt> genus,
<tt>context</tt> (Section 3.8).  Any other member is admitted by the
specification that defines what it addresses (Section 3.9).  The
genus is a set of reference shapes and governs no storage or
transport format.</t>
      </section>
      <section anchor="scheme-semantics">
        <name>Scheme Semantics</name>
        <t>Operations on an <tt>alter:</tt> URI in <tt>handle-ref-form</tt> are
retrieval-and-verify by default.  Submitting an <tt>alter:</tt> URI in
<tt>handle-ref-form</tt> to a handler <bcp14>MUST</bcp14> perform the resolution and
verification procedure specified in <xref target="MCPDNS"/> Section 12.3 before any
content, directive, or action derived from the resulting envelope is
acted upon.  Specifically, the handler <bcp14>MUST</bcp14>:</t>
        <ol spacing="normal" type="1"><li>
            <t>Parse the URI per the ABNF above, isolating the handle, and any
organisational scope, facet, and action-path.</t>
          </li>
          <li>
            <t>Take the publishing zone from <tt>org-scope</tt>.  Where <tt>org-scope</tt> is
absent, the reference names no zone, and the handler proceeds
only if it holds an association between the handle and a zone
established out of band; otherwise the reference is
unresolvable.  A zone is never derived from the spelling of the
handle (Section 6.9).</t>
          </li>
          <li>
            <t>Retrieve and DNSSEC-validate <xref target="RFC4033"/> the <tt>_alter.&lt;zone&gt;</tt> TXT
record, as <xref target="MCPDNS"/> Section 12.3 specifies.</t>
          </li>
          <li>
            <t>Select the record whose handle matches, and verify the envelope
signature against the published Ed25519 key, per <xref target="MCPDNS"/>
Section 12.3.  An envelope that procedure does not treat as
verified is unverified.</t>
          </li>
          <li>
            <t>If a facet or action-path is present, forward it verbatim, with
the verified handle, as the specification that defines that facet
or action surface directs.  The envelope names no resolver.  The
fields of <xref target="MCPDNS"/> Section 7 carry no endpoint, and the procedure
of <xref target="MCPDNS"/> Section 12.3 recognises the handle without reading a
facet or action-path.</t>
          </li>
        </ol>
        <t>Envelope retrieval in Step 3 is a DNS query.  <xref target="MCPDNS"/> defines no
other surface from which an envelope is retrieved, and neither does
this document; where the <tt>_alter.&lt;zone&gt;</tt> TXT record is absent, the
reference is unresolvable.</t>
        <t>An Instrument-tier handle names an instrument whose acts are
attributed to the Sovereign that operates it.  It has no standing
as an independent handle and no envelope of its own (<xref target="MCPDNS"/>
Section 2; <xref target="MCPDNS"/> Section 7.3.2).  A handler <bcp14>MUST NOT</bcp14> treat a
<tt>handle-ref-form</tt> reference whose handle is Instrument-tier as
naming an independent principal: it <bcp14>MUST NOT</bcp14> accept a record
published for that handle as the instrument's envelope, and <bcp14>MUST
NOT</bcp14> dispatch a facet or action-path under it on the instrument's
authority.  Authority for anything done with an instrument is the
operating Sovereign's, verified under the Sovereign's own handle.</t>
        <t>The facet and action-path are addressing information only.  What a
facet denotes, how a resolver answers an action and what a
dereference yields belong to the surface specification that defines
the facet or action.  A conforming handler treats the facet and
action-path as opaque, verified-then-forwarded tokens.</t>
        <t>Where an action-path names an operation with a side effect, the
verification of Step 4 is a precondition to that side effect:
handlers <bcp14>MUST NOT</bcp14> perform, initiate, or authorise any action
addressed by an <tt>alter:</tt> URI until the envelope has been retrieved
and verified.  Handlers <bcp14>SHOULD</bcp14> treat any verification failure as a
hard error and <bcp14>SHOULD NOT</bcp14> fall back to unverified retrieval or to
executing the addressed action.</t>
        <t>An <tt>alter:</tt> URI in <tt>artefact-ref-form</tt> addresses a typed artefact
and names no <tt>~handle</tt>.  The resolution procedure of Steps 1-5 above is
defined entirely in terms of DNS zone resolution for a handle and
does not apply to it.  This document does not define how an
<tt>artefact-type</tt> is resolved to a genus, how an <tt>artefact-ref</tt> is
dereferenced to content, or what a handler does upon receiving one.
The specification that defines the artefact genus named by
<tt>artefact-type</tt> owns those semantics, as a surface specification
owns facet and action-path semantics.  A conforming
handler that receives an <tt>artefact-ref-form</tt> URI and has no such
specification registered <bcp14>MUST</bcp14> treat it as unresolvable and <bcp14>MUST NOT</bcp14>
attempt handle resolution against it.</t>
      </section>
      <section anchor="encoding-considerations">
        <name>Encoding Considerations</name>
        <t><tt>alter</tt> URIs are ASCII per <xref target="RFC3986"/>; characters outside the
unreserved set <bcp14>MUST</bcp14> be percent-encoded.  The IRI form per <xref target="RFC3987"/>
is supported for action-paths that contain non-ASCII characters;
the <tt>handle-ref</tt>, <tt>org-scope</tt>, and <tt>facet</tt> productions <bcp14>MUST</bcp14> be ASCII,
as the DNS labels of <xref target="MCPDNS"/> are.  The tilde
character U+007E is reserved as the handle prefix and is treated as
a literal, not as an unreserved-character escape.</t>
      </section>
      <section anchor="applications-and-protocols-that-use-this-scheme">
        <name>Applications and Protocols That Use This Scheme</name>
        <t>No software outside the author's own company runs the resolution
procedure of Section 3.4 today.  Every implementation that handles
the scheme at this revision belongs to Alter Meridian Pty Ltd, and
none of them performs Steps 3 and 4 of that procedure on an <tt>alter:</tt>
URI.  Section 9 records each one.  They are:</t>
        <ul spacing="normal">
          <li>
            <t>A command-line client by the present author accepts <tt>alter:</tt> URIs
supplied to it as input.  It does not register as an
operating-system handler for the scheme and does not run the
resolution procedure of Section 3.4.</t>
          </li>
          <li>
            <t>The author's own service parses both reference forms with one
shared grammar and refuses a string that the grammar and its table
of forms do not hold.  For a <tt>handle-ref-form</tt> URI it then looks
the handle up in the service's own database of handles.  That
lookup retrieves no <tt>_alter.&lt;zone&gt;</tt> record, validates no DNSSEC
chain and verifies no envelope signature, and is therefore outside
the procedure of Section 3.4.</t>
          </li>
          <li>
            <t>The same service queries the <tt>_alter.&lt;domain&gt;</tt> TXT record when a
company claims a handle on its domain.  That is a DNS retrieval of
the record that Step 3 names.  It runs when a handle is claimed,
and dereferencing an <tt>alter:</tt> URI does not trigger it.</t>
          </li>
          <li>
            <t>The service's agent-facing tools parse an <tt>artefact-ref-form</tt> URI
and resolve nothing.</t>
          </li>
        </ul>
        <t>Any agent runtime, client, or operating-system component that
resolves <tt>~handle</tt> references can register a handler for the
scheme.  The author knows of no such handler outside Alter Meridian
Pty Ltd at this revision.  Section 10 states the resolution path and
what a deployment outside the author's company would look like.</t>
      </section>
      <section anchor="interoperability-considerations">
        <name>Interoperability Considerations</name>
        <t>Each target platform has its own URI handler registry:</t>
        <ul spacing="normal">
          <li>
            <t>Linux desktops: xdg-mime associations <xref target="XDG-MIME"/>.</t>
          </li>
          <li>
            <t>macOS: <tt>CFBundleURLSchemes</tt> entries in an application's
<tt>Info.plist</tt> <xref target="LSHANDLERS"/>.</t>
          </li>
          <li>
            <t>Windows: <tt>HKEY_CLASSES_ROOT\alter</tt> with <tt>URL Protocol</tt> and
<tt>shell\open\command</tt> subkeys.</t>
          </li>
          <li>
            <t>Android: <tt>&lt;intent-filter&gt;</tt> with <tt>&lt;data android:scheme="alter"&gt;</tt>.</t>
          </li>
          <li>
            <t>iOS: <tt>CFBundleURLSchemes</tt> entries in an application's
<tt>Info.plist</tt> <xref target="LSHANDLERS"/>.</t>
          </li>
        </ul>
        <t>Where multiple applications register a handler for <tt>alter:</tt>, the
operating system's default-application policy applies.  No special
arbitration mechanism is defined by this document.</t>
        <t>Browsers <bcp14>MAY</bcp14> treat <tt>alter:</tt> URIs as opaque external schemes and
delegate dispatch to the operating-system handler.  Clients <bcp14>SHOULD
NOT</bcp14> attempt direct retrieval of <tt>alter:</tt> URIs over HTTP; the
resolution procedure of <xref target="MCPDNS"/> Section 12.3 retrieves the envelope
by a DNS query and defines no HTTP retrieval of it.</t>
        <t>The <tt>alter</tt> scheme does not displace any existing scheme and does
not contradict the path-handling rules of <xref target="RFC3986"/>.  It coexists
with <tt>https:</tt>, <tt>mailto:</tt>, and other schemes that an operating
system may dispatch on the same surface.</t>
      </section>
      <section anchor="context-artefact-type">
        <name>Context Artefact Type</name>
        <t><tt>context</tt> is a member of the <tt>artefact-type</tt> genus (Section 3.3),
naming the reference shape for a context artefact.  A context
artefact is an object the presenting principal holds, distinct from
an organisational scope or a facet.  This document
specifies the reference shape only; it assigns no meaning to what a
context artefact carries, in the same way it assigns no meaning to
an artefact reference generally.</t>
        <artwork><![CDATA[
context-ref-form      = "context" "/" context-ref
                           [ "?" query ] [ "#" fragment ]

context-ref            = personal-context / opaque-context-ref

personal-context       = "personal"
                           ; RESERVED.  Denotes the presenting
                           ; principal's own organisation-free
                           ; default context, as a positive,
                           ; present value rather than the
                           ; absence of one.

opaque-context-ref     = 1*( ALPHA / DIGIT / "." / "_" / "-" )
                           ; opaque within the context genus,
                           ; using a character class that itself
                           ; excludes "~".  MUST NOT carry
                           ; the handle or the organisational
                           ; domain of its holder; a reference
                           ; that carries either is
                           ; non-conforming.
]]></artwork>
        <t><tt>context-ref-form</tt> is <tt>artefact-ref-form</tt> with <tt>artefact-type</tt> =
<tt>"context"</tt>; it introduces no third alternative to <tt>alter-URI</tt> and
no change to the discriminator rule of Section 3.3.  Worked forms:
<tt>alter:context/personal</tt>, <tt>alter:context/9f2a-freelance-b</tt>.  The
RESERVED <tt>personal</tt> literal is the one exception to full opacity
within this genus: because it is identical across every principal
rather than an opaque per-context identifier, resolving it never
distinguishes one principal's personal context from another's, and
it reveals only that a personal-context resolution was attempted.</t>
        <t>A <tt>context</tt> artefact reference is an address authored by its holder,
naming which context artefact is meant.  Determining which context
is presently acting for a given session or request is out of scope,
as the resolution meaning of a facet or an action-path is; see
Context Reference Confusion in Section 6.</t>
      </section>
      <section anchor="artefact-type-genus-membership">
        <name>Artefact Type Genus Membership</name>
        <t>Beyond <tt>context</tt> (Section 3.8), this document admits no member to
the <tt>artefact-type</tt> genus and establishes no registry of
<tt>artefact-type</tt> names.  A specification that defines a kind of
artefact <bcp14>MAY</bcp14> admit a member by naming its <tt>artefact-type</tt>, stating
what an <tt>artefact-ref</tt> under it denotes and how one is dereferenced,
and stating any sub-grammar it imposes on <tt>artefact-ref</tt>, following
the pattern of Section 3.8.  A member that needs no sub-grammar
conforms to <tt>artefact-ref-form</tt> as specified, with <tt>artefact-ref</tt>
opaque within the member.</t>
        <t><tt>artefact-ref</tt> is a sequence of <tt>ref-segment</tt>s so that a member can
place a scoping name ahead of the reference it scopes, for example
<tt>alter:example/scope-a/item-7</tt>, without folding the two into one
segment that only the emitter could read.</t>
      </section>
      <section anchor="security-considerations">
        <name>Security Considerations</name>
        <t>See Section 6 below.</t>
      </section>
      <section anchor="author-change-controller">
        <name>Author / Change Controller</name>
        <t>Blake Morrison, Alter Meridian Pty Ltd, blake@truealter.com.
Change control transfers to the IETF if this scheme is later
specified by an IETF Stream document.</t>
      </section>
      <section anchor="references">
        <name>References</name>
        <t><xref target="MCPDNS"/>, <xref target="IDCOMMITS"/>, <xref target="RFC3986"/>, <xref target="RFC7595"/>.</t>
      </section>
    </section>
    <section anchor="operating-system-handler-registration">
      <name>Operating-System Handler Registration</name>
      <t>These subsections are non-normative.  Each sketches the registration
entries that a conforming handler installs on one platform.
Implementations are responsible for the platform-specific syntax;
this document does not prescribe handler binaries or invocation
shapes.</t>
      <section anchor="linux-desktops">
        <name>Linux desktops</name>
        <t>A <tt>.desktop</tt> file with <tt>MimeType=x-scheme-handler/alter;</tt> and an
<tt>Exec=</tt> line invoking the platform resolver.</t>
      </section>
      <section anchor="macos">
        <name>macOS</name>
        <t>A <tt>CFBundleURLTypes</tt> entry with <tt>CFBundleURLSchemes=("alter")</tt> and
a <tt>CFBundleURLName</tt> of <tt>Identity Handle Reference</tt> in the
application's <tt>Info.plist</tt>.</t>
      </section>
      <section anchor="windows">
        <name>Windows</name>
        <t>Registry entries under <tt>HKEY_CLASSES_ROOT\alter</tt>:</t>
        <ul spacing="normal">
          <li>
            <t>A default value of <tt>URL:Identity Handle Reference</tt>.</t>
          </li>
          <li>
            <t>A <tt>URL Protocol</tt> value of empty string.</t>
          </li>
          <li>
            <t>A <tt>shell\open\command</tt> subkey with the handler invocation.</t>
          </li>
        </ul>
      </section>
      <section anchor="android">
        <name>Android</name>
        <t>An <tt>&lt;intent-filter&gt;</tt> declaring
<tt>&lt;data android:scheme="alter"/&gt;</tt> on an <tt>Activity</tt> capable of
performing the resolution procedure of <xref target="MCPDNS"/> Section 12.3.</t>
      </section>
      <section anchor="ios">
        <name>iOS</name>
        <t>A <tt>CFBundleURLTypes</tt> entry with <tt>CFBundleURLSchemes=("alter")</tt> in
the application's <tt>Info.plist</tt> <xref target="LSHANDLERS"/>.  Associated domains and
universal links serve <tt>https:</tt> URLs and do not register a custom
scheme.  An application that only opens <tt>alter:</tt> URIs, and handles
none, lists <tt>alter</tt> under <tt>LSApplicationQueriesSchemes</tt> if it needs
to test whether a handler is installed.</t>
      </section>
    </section>
    <section anchor="addressing-examples">
      <name>Addressing Examples</name>
      <t>The following non-normative examples illustrate the addressing
syntax.  Facet and action semantics are out of scope; each surface
is defined by the specification that owns it.</t>
      <artwork><![CDATA[
alter:~alice
alter:~example.com/decisions/123
alter:~bob/inbox
alter:~carol@acme.example
alter:~carol@acme.example:security
alter:~carol@acme.example:security/verify
alter:~example.com:billing/invoices
]]></artwork>
      <t>The first form addresses an envelope; the second and third address
action surfaces under an envelope; the fourth scopes a handle to an
organisation; the fifth adds a facet; the sixth adds a typed action
under that facet; the seventh addresses a facet-scoped surface.  The
first three, and the seventh, carry no <tt>org-scope</tt>.  A handler
resolves them only through a zone association held out of band
(Section 3.4).  No example addresses an Instrument-tier handle, for
the reason given in Section 3.4.</t>
    </section>
    <section anchor="security-considerations-1">
      <name>Security Considerations</name>
      <section anchor="verification-mandate">
        <name>Verification Mandate</name>
        <t>The verification mandate of <xref target="MCPDNS"/> Section 12.3 is the security
floor of this scheme.  Handlers that accept an <tt>alter:</tt> URI without
verifying the envelope's signature against the DNSSEC-validated
publishing record violate the scheme's invariants.  An attacker
who induces a handler to perform unverified retrieval can
substitute an envelope.  Implementations <bcp14>MUST</bcp14> treat envelope
verification as a precondition to any side effect (writing files,
sending requests, dispatching a sub-handler, or performing an
addressed action).</t>
      </section>
      <section anchor="action-address-confusion">
        <name>Action-Address Confusion</name>
        <t>Because an <tt>alter:</tt> URI <bcp14>MAY</bcp14> address a typed action, a handler that
acts on the action-path before verifying the envelope exposes a
confused-deputy surface: an attacker-supplied URI could name a
privileged action under a handle the attacker does not control.
The Step-4 verification <bcp14>MUST</bcp14> complete, binding the resolved envelope
to the addressed handle, before any action-path is dispatched.  A
handler <bcp14>MUST NOT</bcp14> infer authority from the URI's textual form alone.</t>
      </section>
      <section anchor="context-reference-confusion">
        <name>Context Reference Confusion</name>
        <t>A <tt>context</tt> artefact reference (Section 3.8) is a claim for a
handler to verify and confers no authority by itself.  A handler that treats the mere presence
of a <tt>context</tt> artefact reference in an inbound request as
sufficient to act under that context, without a separate admission
step re-deriving the verdict against the principal's actual
holdings, reproduces on the context axis the confused-deputy
surface described in Action-Address Confusion above.</t>
        <t>A context artefact is held privately and reveals nothing about any
other context the same principal holds.  The resolution procedure for a
<tt>context</tt> artefact reference <bcp14>MUST NOT</bcp14> expose, to any party other
than the presenting principal's own bound credential, the
existence, name, or count of any other context the same principal
holds.  An unresolvable <tt>context-ref</tt> and a <tt>context-ref</tt> the
resolver declines to answer <bcp14>MUST</bcp14> be indistinguishable; a resolver
that distinguishes them creates an existence oracle over the
principal's context set.</t>
        <t>This document specifies no resolution path for a <tt>context</tt> artefact
reference other than resolution by its holder, using the holder's
own bound credential.  It neither describes nor forbids resolution
by any other party.</t>
      </section>
      <section anchor="handler-substitution">
        <name>Handler Substitution</name>
        <t>The operating-system's default-application policy is the
trust-anchor for which binary handles <tt>alter:</tt> URIs.  Users
configuring the default handler <bcp14>MUST</bcp14> treat handler selection with
the same caution they apply to default browsers or default mail
clients.  A malicious handler could parse an <tt>alter:</tt> URI, present
a forged envelope to the user, and act on attacker-supplied data
without performing verification.  This document defines no manifest
against which a handler binary could be checked.</t>
      </section>
      <section anchor="path-component-privacy">
        <name>Path-Component Privacy</name>
        <t>An organisational scope, facet, or action-path included in an
<tt>alter:</tt> URI is part of the URI's textual form and may be logged by
the operating-system handler registry, browser history, terminal
scrollback, and chat-client indexers.  Surface owners that consider
a facet or action identifier (e.g. a decision identifier, a thread
identifier) sensitive <bcp14>SHOULD</bcp14> provide indirected forms (opaque
tokens, ephemeral identifiers) and <bcp14>SHOULD NOT</bcp14> recommend embedding
sensitive identifiers in the URI.</t>
      </section>
      <section anchor="ref-segment-traversal">
        <name>Ref-Segment Traversal</name>
        <t>An <tt>artefact-ref</tt> is a sequence of named segments and has no
filesystem meaning.  A <tt>ref-segment</tt> <bcp14>MUST NOT</bcp14> be <tt>.</tt> or <tt>..</tt>, and <bcp14>MUST NOT</bcp14> be
empty.  An <tt>artefact-ref</tt> of <tt>../secret</tt>, one of <tt>/etc/passwd</tt>
(whose first segment is empty), and an <tt>artefact-ref-form</tt> URI
ending in <tt>/</tt> are therefore all malformed and <bcp14>MUST</bcp14> be rejected.
Implementations <bcp14>MUST</bcp14> reject them on the textual form, before any
resolution is attempted, and <bcp14>MUST NOT</bcp14>
normalise a navigation segment away and resolve what remains: a
resolver that receives an already-normalised reference cannot tell
that a traversal was ever requested.  The percent-encoded spellings
of these segments are covered by the same rule, because
<tt>pct-encoded</tt> decoding happens before a segment is compared.</t>
      </section>
      <section anchor="cross-scheme-confusion">
        <name>Cross-Scheme Confusion</name>
        <t>A URI in which the scheme separator <tt>alter:</tt> is followed by <tt>//</tt>,
the introducer of an <xref target="RFC3986"/> authority component, is malformed and
<bcp14>MUST</bcp14> be rejected.  Implementations <bcp14>MUST NOT</bcp14> silently coerce such a
URI to the same URI without the double slash; divergent parsers
risk confusing a third-party authority component with a handle
reference.  The <tt>@</tt> of an <tt>org-scope</tt> <bcp14>MUST
NOT</bcp14> be parsed as an <xref target="RFC3986"/> userinfo delimiter; there is no
authority component in an <tt>alter:</tt> URI.</t>
      </section>
      <section anchor="form-confusion">
        <name>Form Confusion</name>
        <t>The two forms defined in Section 3.3 share one scheme prefix and
are discriminated solely by the octet following the scheme
separator.  A parser that accepts a leading tilde character inside
an <tt>artefact-type</tt> production, or that treats an <tt>artefact-ref-form</tt>
URI as containing a <tt>handle-ref</tt> when no tilde is present, breaks
the partition between the two forms and creates a parser-divergence
surface: two conforming implementations could disagree about which
form a given URI carries, and an attacker could craft a URI that one
implementation resolves as a handle reference and another resolves
as an artefact reference.  Implementations <bcp14>MUST</bcp14> reject any URI in
which the octet following <tt>alter:</tt> is neither U+007E TILDE nor a
lowercase ALPHA.  Implementations <bcp14>MUST NOT</bcp14> attempt
<tt>handle-ref-form</tt> parsing on a URI beginning with a lowercase ALPHA,
and <bcp14>MUST NOT</bcp14> attempt <tt>artefact-ref-form</tt> parsing on a URI beginning
with U+007E.  A handler that dispatches based on a partial or
best-effort match of either form, rather than a full match against
the discriminator rule of Section 3.3, is non-conforming.</t>
      </section>
      <section anchor="handle-domain-confusion">
        <name>Handle-Domain Confusion</name>
        <t><tt>handle-name</tt> admits U+002E FULL STOP, because the tier productions
it mirrors from <xref target="MCPDNS"/> use a trailing <tt>.bot</tt> label to carry the
bot tier lexically.  A <tt>handle-name</tt> may therefore be spelled so
that it resembles a DNS domain name.  <tt>alter:~example.com</tt> is a
well-formed handle reference naming a principal whose handle is
<tt>example.com</tt>, and nothing in this scheme connects it to the
<tt>example.com</tt> zone.</t>
        <t>Implementations <bcp14>MUST NOT</bcp14> derive DNS meaning from the lexical form of
a <tt>handle-name</tt>, <bcp14>MUST NOT</bcp14> resolve a handle through DNS on the basis
of its spelling, and <bcp14>MUST NOT</bcp14> treat a handle ending in a public
suffix as evidence of any relationship to the corresponding domain.
An association between a domain and a handle is established out of
band and is never inferred from the handle's characters.  A surface
that renders a handle to a person <bcp14>MUST</bcp14> retain the leading tilde,
because a handle stripped of its tilde and placed where a reader
expects a domain cannot be distinguished from one.  Only a trailing
<tt>.bot</tt> label carries meaning under <xref target="IDCOMMITS"/>; no other label
within a <tt>handle-name</tt> carries any.</t>
      </section>
      <section anchor="iri-considerations">
        <name>IRI Considerations</name>
        <t>When an <tt>alter:</tt> URI is presented in IRI form per <xref target="RFC3987"/> with
non-ASCII characters in the action-path, implementations <bcp14>MUST</bcp14>
apply the conversion procedure of <xref target="RFC3987"/> Section 3.1 before
performing the resolution procedure.  Non-ASCII characters in the
<tt>handle-ref</tt>, <tt>org-scope</tt>, or <tt>facet</tt> <bcp14>MUST</bcp14> be rejected; those
productions are restricted to the ASCII forms above.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>Provisional registration of the <tt>alter</tt> URI scheme in the Uniform
Resource Identifier (URI) Schemes registry was requested of IANA on
30 September 2026, under <xref target="RFC7595"/> Section 4 and the procedure of
<xref target="RFC7595"/> Section 7.2, and IANA registered the scheme as Provisional
on 5 October 2026, citing revision 03 of this document.  <xref target="MCPDNS"/>
Section 11 and <xref target="MCPDNS"/> Section 16.2 cross-reference the
registration.  The template submitted is:</t>
      <ul spacing="normal">
        <li>
          <t>URI scheme name: <tt>alter</tt></t>
        </li>
        <li>
          <t>Status: Provisional</t>
        </li>
        <li>
          <t>URI scheme syntax: As specified in Section 3.3 above.</t>
        </li>
        <li>
          <t>URI scheme semantics: As specified in Section 3.4 above.</t>
        </li>
        <li>
          <t>Encoding considerations: As specified in Section 3.5 above.</t>
        </li>
        <li>
          <t>Applications/protocols that use this URI scheme name: As
specified in Section 3.6 above.</t>
        </li>
        <li>
          <t>Interoperability considerations: As specified in Section 3.7
above.</t>
        </li>
        <li>
          <t>Security considerations: As specified in Section 6 above.</t>
        </li>
        <li>
          <t>Contact: Blake Morrison <eref target="mailto:blake@truealter.com">blake@truealter.com</eref>, Alter Meridian
Pty Ltd.</t>
        </li>
        <li>
          <t>Author/Change controller: Blake Morrison, Alter Meridian Pty
Ltd.  Change control transfers to the IETF if this scheme is
later specified by an IETF Stream document.</t>
        </li>
        <li>
          <t>References: This document; <xref target="MCPDNS"/>; <xref target="IDCOMMITS"/>.</t>
        </li>
      </ul>
    </section>
    <section anchor="related-work">
      <name>Related Work</name>
      <t>Schemes for persistent identification of network resources existed
before this one.  Each is summarised here from its own
specification.  The summary is not a claim that the <tt>alter</tt> scheme
could not be written in any of them.</t>
      <dl>
        <dt>URN:</dt>
        <dd>
          <t>A URN is a URI assigned under the "urn" scheme and a particular URN
namespace, "with the intent that the URN will be a persistent,
location-independent resource identifier" (<xref target="RFC8141"/> Section 1).
Resolution of URNs "is more flexible and varied" than resolution of
locators (<xref target="RFC8141"/> Section 1.2.1), and <xref target="RFC8141"/> leaves the
resolution procedure to the namespace and to resolution services.
An <tt>alter:</tt> reference could be carried in a URN namespace.  This
document defines a scheme of its own.  An operating-system
handler registry keys on the scheme name.  A handler for <tt>urn:</tt>
would have to dispatch again on the namespace identifier before it
reached anything specific to handles.  A reference with an
<tt>org-scope</tt> also names the zone that publishes the key, and the
verification procedure of Section 3.4 follows that name.  That name
is a location in the sense that <xref target="RFC8141"/> sets location-independence
against.</t>
        </dd>
        <dt>Handle System:</dt>
        <dd>
          <t>The Handle System is "a distributed information system designed to
provide an efficient, extensible, and secured global name service"
(<xref target="RFC3650"/> Section 1).  A handle is a naming authority, called its
prefix, and a local name (<xref target="RFC3650"/> Section 3), and a Local Handle
Service and its namespaces "must be registered with the Global
Handle Registry" (<xref target="RFC3650"/> Section 4).  In an <tt>alter:</tt> reference
the authority is a DNS zone that publishes one signed record, with
no registry beyond DNS.  <xref target="RFC3650"/> Section 6.1 records that "it is
therefore generally considered inappropriate to use DNS as a
general-purpose naming service".  The scheme here uses DNS to
publish one small record per handle, and defines no naming service.</t>
        </dd>
        <dt>ARK:</dt>
        <dd>
          <t>An ARK has the general form <tt>[https://NMA/]ark:[/]NAAN/Name[Qualifiers]</tt>,
where the Name Assigning Authority Number "identifies the
organization that originally assigned the Name of the object", and
an organisation "may request a NAAN from the ARK Maintenance
Agency" (<xref target="ARK"/> Section 2.3).  A founding principle of ARKs is that
"persistence is purely a matter of service" (<xref target="ARK"/> Abstract).  An
<tt>alter:</tt> reference carries no assigning-authority number and is not
made actionable by prepending a URL; Section 3.7 tells clients not
to retrieve it over HTTP.</t>
        </dd>
        <dt>PURL:</dt>
        <dd>
          <t>A PURL is a persistent URL: "PURLs are persistent URLs, they
provide permanent addresses for resources on the web" (<xref target="PURL-ADMIN"/>).
<xref target="ARK"/> Section 1 credits the scheme with "the advantage of working
with unmodified web browsers".  An <tt>alter:</tt> URI is dispatched to an
operating-system handler, and its resolution is a DNS query.</t>
        </dd>
      </dl>
      <t>This document adds a verification mandate to that field.  A handler <bcp14>MUST</bcp14> retrieve the <tt>_alter.&lt;zone&gt;</tt> record, validate it under
DNSSEC and verify the envelope signature before it acts on anything
derived from the reference (Sections 3.4 and 6.1).  The summaries
above make no claim about whether any of those schemes has an
equivalent.</t>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>[RFC EDITOR: remove this section, and the reference to RFC 7942,
before publication as an RFC.]</t>
      <t>This section records the status of known implementations of the
scheme defined by this specification at the time of posting of this
Internet-Draft, and follows the shape of <xref target="RFC7942"/>.  Listing an
implementation here does not imply endorsement by anyone.  No effort
has been spent to verify the information beyond the author's own
reading of the code.  Other implementations may exist.</t>
      <t>All three implementations below are written and run by Alter Meridian
Pty Ltd, and none of them runs the resolution procedure of
Section 3.4 on an <tt>alter:</tt> URI.</t>
      <dl>
        <dt>Command-line client:</dt>
        <dd>
          <t>Organisation: Alter Meridian Pty Ltd.  Description: accepts
<tt>alter:</tt> URIs supplied to it as input.  Maturity: the author's own
tool.  Coverage: input acceptance only.  It does not register as
an operating-system handler and does not run Section 3.4.
Licensing: Apache-2.0, published on npm as <tt>@truealter/cli</tt>.
Contact: blake@truealter.com.  Last updated: 2026-11.</t>
        </dd>
        <dt>Address parser and handle lookup in the author's service:</dt>
        <dd>
          <t>Organisation: Alter Meridian Pty Ltd.  Description: one shared
parser for both reference forms, with a table of the forms the
service accepts, and a lookup that resolves a <tt>handle-ref-form</tt>
handle to the service's own bound record.  Maturity: part of the
service's code.  Coverage: Section 3.3 syntax and the
reject rules of Section 6; of Section 3.4 only Step 1.  The lookup
reads the service's own database in place of the <tt>_alter.&lt;zone&gt;</tt>
record.
Version compatibility: written against revision 03 of this
document; the grammar is unchanged through this revision.
Interoperability: a conformance check over the author's own
sources tests emitted URIs against the same grammar.  Licensing:
proprietary and not released.  Contact: blake@truealter.com.  Last
updated: 2026-11.</t>
        </dd>
        <dt>DNS claim check in the author's tooling:</dt>
        <dd>
          <t>Organisation: Alter Meridian Pty Ltd.  Description: a service route
that queries the <tt>_alter.&lt;domain&gt;</tt> TXT record when a company claims
a handle on its domain.  Maturity: the author's
own tooling.  Coverage: it does not perform Step 4 of Section 3.4 on an
<tt>alter:</tt> URI, and retrieves the record named in Step 3 for a
claim.  Licensing:
proprietary and not released.  Contact: blake@truealter.com.  Last
updated: 2026-11.</t>
        </dd>
      </dl>
    </section>
    <section anchor="open-issues">
      <name>Open Issues</name>
      <t>This section is removed before publication as an RFC.</t>
      <ol spacing="normal" type="1"><li>
          <t><em>Resolution path.</em>  The resolution path of the scheme is the DNS
path of Section 3.4: parse, take the zone from <tt>org-scope</tt>,
retrieve and DNSSEC-validate the <tt>_alter.&lt;zone&gt;</tt> TXT record,
verify the envelope signature, and forward any facet or
action-path.  It is specified and has no running implementation
outside Alter Meridian Pty Ltd.  Section 3.6 records what the
author's own software does today, and that does not include
Steps 3 and 4 on an <tt>alter:</tt> URI.</t>
        </li>
        <li>
          <t><em>Outside deployment.</em>  A deployment outside the author's company
has two parts.  A zone publisher that is not Alter Meridian Pty
Ltd publishes a signed record at <tt>_alter.&lt;zone&gt;</tt> for a handle it
controls.  A client or operating-system handler that is not
Alter Meridian software then receives an <tt>alter:</tt> URI naming that
handle and zone, retrieves and validates the record, verifies the
envelope, and only then acts.  Until a handler of that kind
exists, the author intends to keep the registration Provisional
under <xref target="RFC7595"/> Section 4.</t>
        </li>
        <li>
          <t><em>Artefact references.</em>  This document defines no resolution for
<tt>artefact-ref-form</tt> (Section 3.4), and the author knows of no
resolver for it.  The tools recorded in Section 3.6 parse the form
and resolve nothing.</t>
        </li>
      </ol>
    </section>
    <section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>The scheme builds on the <tt>~handle</tt> identity primitive defined in
<xref target="MCPDNS"/> and the tier taxonomy of <xref target="IDCOMMITS"/>.  The lexical choice
of tilde for the handle prefix is informed by <xref target="POSIX-TILDE"/> and by
the long-standing shell convention that the tilde denotes a named
principal.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <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" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <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>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5234" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
            <author fullname="P. Overell" initials="P." surname="Overell"/>
            <date month="January" year="2008"/>
            <abstract>
              <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC7595" target="https://www.rfc-editor.org/info/rfc7595" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7595.xml">
          <front>
            <title>Guidelines and Registration Procedures for URI Schemes</title>
            <author fullname="D. Thaler" initials="D." role="editor" surname="Thaler"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <author fullname="T. Hardie" initials="T." surname="Hardie"/>
            <date month="June" year="2015"/>
            <abstract>
              <t>This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="35"/>
          <seriesInfo name="RFC" value="7595"/>
          <seriesInfo name="DOI" value="10.17487/RFC7595"/>
        </reference>
        <reference anchor="RFC3987" target="https://www.rfc-editor.org/info/rfc3987" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml">
          <front>
            <title>Internationalized Resource Identifiers (IRIs)</title>
            <author fullname="M. Duerst" initials="M." surname="Duerst"/>
            <author fullname="M. Suignard" initials="M." surname="Suignard"/>
            <date month="January" year="2005"/>
            <abstract>
              <t>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement of the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources.</t>
              <t>The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3987"/>
          <seriesInfo name="DOI" value="10.17487/RFC3987"/>
        </reference>
        <reference anchor="RFC4033" target="https://www.rfc-editor.org/info/rfc4033" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4033.xml">
          <front>
            <title>DNS Security Introduction and Requirements</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>The Domain Name System Security Extensions (DNSSEC) add data origin authentication and data integrity to the Domain Name System. This document introduces these extensions and describes their capabilities and limitations. This document also discusses the services that the DNS security extensions do and do not provide. Last, this document describes the interrelationships between the documents that collectively describe DNSSEC. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4033"/>
          <seriesInfo name="DOI" value="10.17487/RFC4033"/>
        </reference>
        <reference anchor="MCPDNS" target="https://datatracker.ietf.org/doc/draft-morrison-mcp-dns-discovery/">
          <front>
            <title>Discovery of Model Context Protocol Servers via DNS TXT Records</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-mcp-dns-discovery-10"/>
        </reference>
        <reference anchor="IDCOMMITS" target="https://datatracker.ietf.org/doc/draft-morrison-identity-attributed-commits/">
          <front>
            <title>Identity-Attributed Git Commits via Tier-Structured Trailers</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-identity-attributed-commits-05"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="IDACCORD" target="https://datatracker.ietf.org/doc/draft-morrison-identity-accord/">
          <front>
            <title>Identity Accord Protocol</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-identity-accord-04"/>
        </reference>
        <reference anchor="IDPRONOUNS" target="https://datatracker.ietf.org/doc/draft-morrison-identity-pronouns/">
          <front>
            <title>Identity Pronouns: A Reference-Axis Extension to ~handle Identity Systems</title>
            <author fullname="Blake Morrison">
              <organization>Alter Meridian Pty Ltd</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-morrison-identity-pronouns-05"/>
        </reference>
        <reference anchor="POSIX-TILDE" target="https://pubs.opengroup.org/onlinepubs/9699919799/">
          <front>
            <title>IEEE Std 1003.1-2017, Shell Command Language, Section 2.6.1 Tilde Expansion</title>
            <author>
              <organization/>
            </author>
            <date year="2017"/>
          </front>
        </reference>
        <reference anchor="XDG-MIME" target="https://specifications.freedesktop.org/shared-mime-info-spec/latest/">
          <front>
            <title>Shared MIME-info Database Specification</title>
            <author>
              <organization/>
            </author>
            <date year="2024"/>
          </front>
        </reference>
        <reference anchor="LSHANDLERS" target="https://developer.apple.com/documentation/bundleresources/information-property-list/cfbundleurltypes">
          <front>
            <title>CFBundleURLTypes (Information Property List)</title>
            <author>
              <organization/>
            </author>
            <date year="2024"/>
          </front>
        </reference>
        <reference anchor="RFC7942" target="https://www.rfc-editor.org/info/rfc7942" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7942.xml">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
        <reference anchor="RFC8141" target="https://www.rfc-editor.org/info/rfc8141" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8141.xml">
          <front>
            <title>Uniform Resource Names (URNs)</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <date month="April" year="2017"/>
            <abstract>
              <t>A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance. With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and it describes procedures for registering namespace identifiers with the Internet Assigned Numbers Authority (IANA). This document obsoletes both RFCs 2141 and 3406.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8141"/>
          <seriesInfo name="DOI" value="10.17487/RFC8141"/>
        </reference>
        <reference anchor="RFC3650" target="https://www.rfc-editor.org/info/rfc3650" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3650.xml">
          <front>
            <title>Handle System Overview</title>
            <author fullname="S. Sun" initials="S." surname="Sun"/>
            <author fullname="L. Lannom" initials="L." surname="Lannom"/>
            <author fullname="B. Boesch" initials="B." surname="Boesch"/>
            <date month="November" year="2003"/>
            <abstract>
              <t>This document provides an overview of the Handle System in terms of its namespace and service architecture, as well as its relationship to other Internet services such as DNS, LDAP/X.500, and URNs. The Handle System is a general-purpose global name service that allows secured name resolution and administration over networks such as the Internet. The Handle System manages handles, which are unique names for digital objects and other Internet resources.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3650"/>
          <seriesInfo name="DOI" value="10.17487/RFC3650"/>
        </reference>
        <reference anchor="ARK" target="https://datatracker.ietf.org/doc/draft-kunze-ark/">
          <front>
            <title>The ARK Identifier Scheme</title>
            <author fullname="John Kunze">
              <organization/>
            </author>
            <author fullname="Emmanuelle Bermes">
              <organization/>
            </author>
            <date year="2026" month="October" day="23"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-kunze-ark-44"/>
        </reference>
        <reference anchor="PURL-ADMIN" target="https://purl.archive.org/">
          <front>
            <title>PURL Administration</title>
            <author>
              <organization>Internet Archive</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
      </references>
    

<section anchor="change-log">
      <name>Change Log</name>
      <section anchor="draft-morrison-alter-uri-scheme-06">
        <name>draft-morrison-alter-uri-scheme-06</name>
        <ul spacing="normal">
          <li>
            <t>Tighten the prose.</t>
          </li>
          <li>
            <t>State in Section 3.6 what resolves today: the implementations that
handle the scheme are all the author's company's own, and none runs
the procedure of Section 3.4 on an <tt>alter:</tt> URI.</t>
          </li>
          <li>
            <t>Add Related Work (Section 8), comparing URN, the Handle System,
ARK and PURL, and an Implementation Status section (Section 9) in
the shape of RFC 7942.</t>
          </li>
          <li>
            <t>Add Open Issues (Section 10), stating the resolution path and what
a deployment outside the author's company would look like.</t>
          </li>
          <li>
            <t>Record the licence of each listed implementation in Section 9.</t>
          </li>
          <li>
            <t>Open Issue 3 says that the author knows of no resolver for
<tt>artefact-ref-form</tt>, as Section 3.6 records, where it pointed at a
resolver that Section 9 does not list.</t>
          </li>
          <li>
            <t>The comment on <tt>opaque-context-ref</tt> in Section 3.8 says that a
context reference <bcp14>MUST NOT</bcp14> carry the handle or the organisational
domain of its holder.  It previously said that a reference <bcp14>MUST NOT</bcp14> lexically
embed a handle-name or a domain-label.  The worked example
<tt>9f2a-freelance-b</tt> fails that condition, as does any reference
containing a letter.  No other requirement changes.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-05">
        <name>draft-morrison-alter-uri-scheme-05</name>
        <ul spacing="normal">
          <li>
            <t>Rewrite the prose and pin each citation
of another Internet-Draft to its latest posted revision.  The
grammar, the examples and every requirement are unchanged.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-04">
        <name>draft-morrison-alter-uri-scheme-04</name>
        <ul spacing="normal">
          <li>
            <t>Correct the section references into <xref target="MCPDNS"/>: the envelope record
is <xref target="MCPDNS"/> Section 7, and the resolution and verification
procedure is <xref target="MCPDNS"/> Section 12.3.  Revision 03 cited Sections 5
and 8 of that document for them.</t>
          </li>
          <li>
            <t>State that a handle carries no zone of its own.  Step 2 of
Section 3.4 takes the zone from <tt>org-scope</tt>, or from an
association held out of band, and otherwise treats the reference
as unresolvable; it no longer points at a handle-to-zone procedure
in <xref target="MCPDNS"/>, because that document defines none.  Note this in the <tt>org-scope</tt>
definition and under the Addressing Examples.</t>
          </li>
          <li>
            <t>Remove the statement that <xref target="MCPDNS"/> falls back to an HTTPS
well-known surface for envelope retrieval.  <xref target="MCPDNS"/> defines no
such fallback, and the statement contradicted Section 3.7.  Drop
the [RFC8615] reference, since nothing else cited it.</t>
          </li>
          <li>
            <t>State that an Instrument-tier handle is not an independent handle
and has no envelope of its own, as <xref target="MCPDNS"/> Section 2 states, and
that a handler <bcp14>MUST NOT</bcp14> treat one as naming an independent
principal.  Correct the Introduction to match, remove the
Instrument-tier addressing example, and attribute the <tt>cc-</tt> prefix
in the ABNF comments to <xref target="MCPDNS"/> rather than <xref target="IDCOMMITS"/>.  The
grammar is unchanged.</t>
          </li>
          <li>
            <t>Correct the <xref target="RFC7595"/> section references: provisional
registration is <xref target="RFC7595"/> Section 4, the registration procedure is
<xref target="RFC7595"/> Section 7.2, and the requirements for permanent
registration are <xref target="RFC7595"/> Section 3.</t>
          </li>
          <li>
            <t>Record in the Abstract, Status and IANA Considerations that
provisional registration was requested on 30 September 2026 and
that IANA registered the scheme as Provisional on 5 October 2026.</t>
          </li>
          <li>
            <t>Correct the iOS registration text: a custom scheme is registered
with <tt>CFBundleURLTypes</tt> in <tt>Info.plist</tt>, as on macOS; associated
domains and universal links serve <tt>https:</tt> URLs.</t>
          </li>
          <li>
            <t>Describe the one command-line client that accepts <tt>alter:</tt> URIs
as it is: it does not register as an operating-system handler and
does not run the resolution procedure.  Remove the statement that
it registers itself as the default handler.</t>
          </li>
          <li>
            <t>Reduce the Artefact Type Genus Membership subsection to the rule
for admitting a member, and remove the list of members that named
one implementation's own artefact kinds and file titles.  Replace
the examples that used them in Terminology and under Ref-Segment
Traversal with generic ones.</t>
          </li>
          <li>
            <t>Replace the closing paragraph of Context Reference Confusion: this
document specifies no resolution path for a <tt>context</tt> artefact
reference other than its holder's, and neither describes nor
forbids resolution by another party.</t>
          </li>
          <li>
            <t>Remove a <bcp14>SHOULD</bcp14> that depended on a handler manifest no
specification defines.</t>
          </li>
          <li>
            <t>Replace the hand-typed BCP 14 paragraph with the standard
boilerplate, use a neutral handle in the examples, remove a
statement of the document's own contribution from the Abstract,
and name in words the documents the Abstract relies on, where it
had cited them by tag.</t>
          </li>
          <li>
            <t>Describe the malformed forms under Ref-Segment Traversal and
Cross-Scheme Confusion without spelling each as a complete URI.
The requirements are unchanged.</t>
          </li>
          <li>
            <t>Shorten the Abstract, Introduction, Status and Scheme Semantics
prose.  No requirement changes.</t>
          </li>
          <li>
            <t>Correct step 5 of Scheme Semantics, where a facet or action-path
was dispatched to a resolver named by the envelope.  The envelope
names none; the step now defers to the specification that defines
the facet or action surface.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-03">
        <name>draft-morrison-alter-uri-scheme-03</name>
        <ul spacing="normal">
          <li>
            <t>Add a Handle-Domain Confusion security consideration.  Because
<tt>handle-name</tt> admits "." in order to carry the <tt>.bot</tt> tier suffix of
<xref target="IDCOMMITS"/>, a handle may be spelled to resemble a DNS domain.  State that no
DNS meaning follows from a handle's lexical form, that a domain's
association with a handle is established out of band, and that a
rendering surface <bcp14>MUST</bcp14> retain the leading tilde.</t>
          </li>
          <li>
            <t>Partition the scheme into two disjoint reference forms carried
under one scheme name: <tt>handle-ref-form</tt>, unchanged from revision
02, and a new <tt>artefact-ref-form</tt>,
<tt>alter:&lt;artefact-type&gt;/&lt;artefact-ref&gt;</tt>, addressing a typed artefact
rather than a <tt>~handle</tt>.</t>
          </li>
          <li>
            <t>Add a discriminator rule: the octet immediately following the
scheme separator selects the form, U+007E TILDE for a handle
reference and a lowercase ALPHA for an artefact reference.  No
other leading octet is valid, and the tilde <bcp14>MUST NOT</bcp14> begin an
artefact type.</t>
          </li>
          <li>
            <t>Add Artefact type and Artefact reference to Terminology, defining
the shape of the reference only, and state that this document
assigns artefact resolution no meaning.</t>
          </li>
          <li>
            <t>Make <tt>artefact-ref</tt> a sequence of <tt>ref-segment</tt>s separated by "/",
so that a scoping name can precede the reference it scopes, and
widen each segment to <tt>1*( unreserved / pct-encoded )</tt> so that a
<tt>~handle</tt> or its percent-encoded form can be carried.  Make the
<tt>artefact-ref</tt> component <bcp14>OPTIONAL</bcp14> so that a bare artefact type is
expressible.</t>
          </li>
          <li>
            <t>Add Form Confusion and Ref-Segment Traversal security
considerations.  A <tt>ref-segment</tt> <bcp14>MUST NOT</bcp14> be "." or "..", and is
rejected on its textual form, after <tt>pct-encoded</tt> decoding, before
any resolution.</t>
          </li>
          <li>
            <t>Add <tt>context</tt> as a member of the <tt>artefact-type</tt> genus, with a
Context Artefact Type subsection specifying <tt>context-ref-form</tt> and
the RESERVED <tt>personal</tt> literal, and a Context Reference Confusion
security consideration.  Define <tt>org-scope</tt> as a DNS zone qualifier
that carries no acting context.</t>
          </li>
          <li>
            <t>Add an Artefact Type Genus Membership subsection listing further
members of the genus.</t>
          </li>
          <li>
            <t>Repoint the informative Apple reference to the current
CFBundleURLTypes page.  The mechanism cited is unchanged.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-02">
        <name>draft-morrison-alter-uri-scheme-02</name>
        <ul spacing="normal">
          <li>
            <t>Broaden the addressing syntax to the full <tt>~handle@org:facet/action</tt>
reference: add the <tt>org-scope</tt>, <tt>facet</tt>, and <tt>action-path</tt>
productions and their left-to-right parsing rules.  Every added
component is <bcp14>OPTIONAL</bcp14>; a bare <tt>alter:~handle</tt> is unchanged.</t>
          </li>
          <li>
            <t>State explicitly that facet and action-path are addressing
information only, with resolution semantics owned by the surface
specification and out of scope here.</t>
          </li>
          <li>
            <t>Add an Action-Address Confusion security consideration and extend
the verification mandate to cover addressed actions.</t>
          </li>
          <li>
            <t>Correct the registration Status to Provisional, the registration
this document actually requests.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-01">
        <name>draft-morrison-alter-uri-scheme-01</name>
        <ul spacing="normal">
          <li>
            <t>Editorial and reference alignment.</t>
          </li>
        </ul>
      </section>
      <section anchor="draft-morrison-alter-uri-scheme-00">
        <name>draft-morrison-alter-uri-scheme-00</name>
        <ul spacing="normal">
          <li>
            <t>Initial submission.  Upgrades the provisional registration
recorded in <xref target="MCPDNS"/> Section 11.</t>
          </li>
        </ul>
      </section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA819e3Pb1rXv//tT7KPec2L3EKQlv2IqSaPYSqNb23IlpY9x
PSVIghRqEGAB0LJy5uSz3M9yP9ldz/0AQNlpz9xpZiJLJLCfa6/nb62dJIlp
87bIpvbg6jqzX6RFm9Vf2B8vzuzl4jrbZHZV1fZF3mzTdnGdzovM/nydlkv4
9yJbZXVWLrLmwKTzeZ19gEbo/eD1A7OsFmW6gQ6Wdbpqk01V13lTlQk9mezq
PGnoyeTBE7NI22xd1bdTm5eryuTbemrbete0Rw8ePHtwZEy6a6+remqsTeB/
a1e7ouDWvyvS95l9Ja3Tl1W9Tsv8p7TNq3JqT2hkr7I6X+Zpad+0t/Zlu6QH
s02aF1M7xya+hf4yGtt4UW2MKat6Ay18yLDTi++fHx0ePpNfvzx8+kh+ffjs
yyfy6+Ojh/rp08fPHvsHnsqvjx48fIi/vnr+5sXryymNQPcAFnpRfcjqW1ut
YDLLrLDPq7LNPrb2TV211aIq7GVWwxON/ZCnFhqwV3+6gr1YVPUSNgIb84v0
ySX6BYvUpvU6a6f2um23zXQyWaZt2tbp4j2sVJ61qzG0NIHNnnT2ebPYJsuy
SZY6tQk110AfWYPbrAM9g3nWZdYmL7CBHr302kkOH9CbMBCY3NGDoyfw59mL
5+evXp1dddb1bJmV8PttctK2dT7ftdnS/jZvYXE3m7zltbzKgR4vYfsX7a6G
769qoApY6H/FRc11PqmbT7LgufyDy3tHi8mDx92FNthycDDOXpw8f35+8WJ4
1e3JAsnTkfC/9orSWP/pVaRWkgePhkj0zcX56/Mfu2ffrRYsU1ntygbm6Zls
cvIxb+zpxzYrG1gD21aOEbsXL2+bNtv8axPsVib3zy6wtjNAnNa+Ob88+1Ny
dfbyxWlnjU9PT+1lu7SHDx48HB8mRw8On47s5XVWFMQLYEHty7Rc79J1Bp9n
C1wQezR+Mj4E/lAsM9iBbUo7cDC4HtvdvBlX26xc19VuS6tRlUVeZvjF5NmT
Z8+eHT57+uzZJBr04VP4808vfpu8OnvVGfHldYrMCL9IcJ3sC1jxedpk9nKb
LfJVvqBNGx5NEz7SjFd1li2z5n1b8cgaajvZ5CB9se0En58UMKimjQd4hHT8
8vKHk9cvXp5edAj3+fff7ZAQf7x4eXW7zRp770y5AyweUPM2q5GE8qa9PzzO
ZfYhK/CxcbrdFhlKXiSi3QY2m1qZzKmHOmuqXQ0axyT3PSApUA9JAT1MFit+
dlcXLY6mPw+UzM8eHTkp/uhQhfSTxw/w15OL38UzRNUIPpSTtgJB4dSb/lFL
5N/w0P3v6rq0v9uVP2V3PHSK9LcDUszsd1m9kaH/whP3HjtJ0vr9Lztg7rXk
UZdlgZxNjh7iqYINTk5evDp7Ha8Ofm5Plpu8hPWvA3KM1yXmMToMe1IvrkGK
7DlNdTFO+QGaZ08OJUli0zl2u2iNuboGHqmEY5fZCg5eY1vYvRmpdDPSTFnf
tGljU7sMNFtTK7O1zS0Q3kfSfWfCZmdWeY91zzUWjjVQ3TWc0Lw02BFqZDVr
YzIA/IrGAFQNvAPPRHQusRejWk1ervfpfY3ofe01sJb1tdP9pLexOSllmlOe
5zwvYRCpwWZ2aRHMxE8UxEhq8VgVOxoLMkAchg7OwOFaZEtQiKDftIVHQTuA
08qryu190dis5ANsV3W1gRZlWWA25qeqBFb6IS1y3Dd+Tx+HN5t8XaaocFnY
hLwc0Qh0V/hx2JdmV7Q01tLiWYehleukIXFHU+WB1GNr8aj66W3SWzvPDKzt
FvZBGiA6bGh6I1umdV3dyJcWD+LSrtIFECZo4Ni57jqPLF0uYTSNPo8cBj5k
MdHsanxTBiFUljdEFvIebi8yLmicPtYt+RYGNaVuJ9xYsEfHFjXUYI8asFdg
SIvGpLQtFQgDGizszx4aG8H7Oxz1TQ7P71qzqZbuyzEenGDAFvb8A0y7Tsps
ByeroJnnZVtXyx0SfVnZMruxi/p221brOt1e5wsglByURTyowEB1Q+waPkCq
iimTKaxDRMYR0TyDNcpoWWG9YC55y6t/c53RjDNqRfeiwfZ52UYmJF6YSLZA
iQcP3AKlgfjOVisQ6jDEs5PXJzxRFOZpUdwCma2BgWUobkOWIesCQgXZvqgE
j3DFQWRYtPFgiOaxPV+01RweQcY0Zs60yZcwNWN+heyOVo/OFC33AF9xSxhy
jrdsJ77T42zlOAthkjBiUrWXyEEyOFBA4/a7Ck4MfnnvrTOK3rnxP7xPBGyi
PcQBlIt8Czse8jXavr+yTfzVsgJjufxmpuzHMPvBTS9hlsCJifkm1DXPcAQn
Y3GN/Hb282KRZB/TDQh50OmAzc1GBs8cbWHu3oaNRqKGPYUvkBK81QajjqeK
ZG+YKUAzSinXKZGpIylYITxF1U0J66Er6vS7+zh8I+q05x43dd6Cvo1LUO/K
EokRFz+cD7C1BWwhcPDZzzIx1F5mIzxHOco4oMGW/CbEMK53cHahixSISTgK
MCkQcGVmFmlZwqYp84MBYx/ws2nhwWb8y+UbfhNJOOE9OJDOZHkDh+RHQKlt
RVwr4EVePECrbmFxXjTdgDdbf7wMciE++1XTeo5umaPj6QROBoyZWQRorfBM
S8fUBIwUeR0Il7JtRl2+DhRMPB++YG4ua10a5hMJLMl1xKhEui2yHIWbrINu
r5d68LSJuJdS2Aj/KmFPFjkynBtsDpZgWRHLxV28h2YBDiEv59VHIKLr6gZF
ZV2tctgJmO8SqKYEBgCUjBMSq3kBS7apgIHBMpm3amm/G3lCoaWGbxORQOha
gg+r4j7QzPfAC4QyR25e0FlVfJsuNtlYvps22WIH9H47oendziyfSyIu+UgW
T1ghfaNvzbzQnHHrMzi10F/QBR6K0sCOAUGjogPrf0q+LreRwPlvq3IZiAU8
Rudvrs7OX5+8PIZZzoEdmN7uIEtqWMfonRKRgzKVgHxYxxtFhyTYXxEhFfDB
NdtP4cGRw4vvdhUSkSOsCAN9tETG7kVicyBvGibzZUUCVcd5qwpPT9hT70AF
ss51X+v4I9JcyiLXdB/bZGC2Cm8kuqM+YKq0+jvmnUjfzQ1NDpYZmCUw3DkN
qaOy0mnx/Af+CJWfcPnToqmCs5zZaHVgubZob5pmN98gsyW+QbKZieytuFE9
s346Pjq2saZt2RY00K/udiQ6gSZ+9St7kf19lwOtIMNwRj7L4vfZrb0hlf3g
1Y+XVwcj/te+PqffL05//+PZxekL/B1s4Jcv3S9Gnrj84fzHly/8b/5NlLyn
r1/wy/CpjT4yB69O/nzA23KgdH7ABkO0ijXJj3nmZQrqnY0BXrMA0cjz/e75
m//7fw4f2f/6r38TT/V//7f8gb5q+AMUKFGxq7K4lT9hMW8NGN5ZWpO0LwrY
sG0ORIoE0xCjKi2qXrCQv36LK/Nuar+aL7aHj76RD3DC0Ye6ZtGHtGb9T3ov
8yIOfDTQjVvN6PPOSsfjPflz9Leue/DhV79Bn41NDr/8zTcG9bcrMMjzsiqq
9a0xTiAadNGpedU3DwfVOGIbOWmZObrfAu0MDs8P1HADO72Gl5ycbMn3BEIc
7VwMsPzngwdPT2E7TkX8wEhIhweNCBv2Q6HzofJryfYZce6uQgdDiS1K1Sq9
LWfZlkv3HDNowR9SY84H5DEuWOmEOXaYsMkVCm/7d1hOYIXYY+p0SFHGoJN0
hUuASum3oJ1nW1iUtgKelY1BpMwGZNvMmWQ4BGud5twMTVA4zw0oxNfDVi42
0SgDRdX3u2yR7lBhVamlDA9UUGrSq5+wfPB6oGPiFsNjNDaRufrWPaetjx+B
KLd2BsuU0JM48SJD/XhoBguQVmAxO9cD9TisswVdoKEZjnxRpDkY83O0F62s
x4K9EsA0sjItF2AVg4jpaF7APNIFUh8NDTrG1S7X0Ia3L8jKpG+ADYmhR+tO
SpnKppEqb6BfWxuobnyychq5sh+MGYpa4vqBTePG4XUZuj8CPIAFUvRcfoHJ
gBaxo5UJFhvX/o9ke6bB1pVZBhKjZfHmZuFWKBfhDvIPw0u47TP5EnSjus1g
bm3Q3L0G9Fz1+pzo9+hRBW5QVDf3eRWora4WECxKRuKQhfJ2V2/RkGIZDi+r
gkjfAjWywVRmqAdgw9GczffYSefI8nFNkQG0rJJY7yFRg0lOqJ1Nka30jqjT
NWe02zwXdsQ00QrD2gI549az2kZ2FE1AeJN27bUfbgw+rkClCfQdPQIfiHWg
kiPGYu3ZtKo6skh9lQcaoUXDp6gjtpq6QYnogKcYt3nrgz7vkPbxkApz0qm8
z1Eqr3C9+qrWotoVS7Je2fSU3o058dvf2Sh2TelcvN+KuZvjVPdwheSU5Ss6
o3Qs78NmfdzKO2JKEpF5ZV0GDjYebywSuFgKYGmgJYSulWZyePQQP5jnBQjV
9SQvP1SgtzczXryQgIn94XY7N19Fvgz1++t02CXmVWPcxFBbHV5E1VdzWjg9
YLhOJMfhiGX1Im2yJC22YC5n0LQt4F8V7SqRNtlmzk4XcQDiiLW5dVbugO6Y
jbqVW+U1GLo0xyZbb2T10jJ4MwGSScg+dwsa8AtSFcTukQ8nz1ZHaYIxnSLF
AOGcFzQcDI5OZEo8bBqleFkyjCm2RJWyhNBEX+VnjosuEFxLauC4o6XqAqNu
qW1cp1tH4t7ZEKy/+1DpN/37LuvxgGD02BKPn3kRbHnam3VvB4DloGX5y7eg
t8qfvRfMkcohXh/yJ2isY5HBAfURhruZ1DClOyYVrQmsOquXtS51x5Puj3bo
Cq3ULeK8Q9ApLFATueqDSMIHkuKnzN7QC7YodqC9flyuKdSIC9401SIXq/qt
Bj7foav3ZV7uwCh/me7KxTVCXZBVWIwwif2M/OGtD0XSS5t0cX7JXurzy5Ga
mLfO+Gae98Pvnl9YCnn/EXgtyJqROrZxyqscJ4fEC2uzrCtyJfxKUVAvnL5B
tqR8+hoI0Ig7YsZftGm7a4x54z3Lg85me6ez2ewzfh/h8HquZug3AGxdkl9D
nMw9tyBoRHB4gEsvNMgFJIw0T5rMW8EyvWON2Ygr0dnvNxVu+N+qvAypmV/n
MZN7h9/C4zmmYazrdLMB63LXiMp98t3r78ljKIAp7O/k5ZsfTkb2xdlvz65o
Y344/RP8Qa4IZPcLjAnUu0LF+mxXoqiqQQVH8bKF8wujqZb8Z7ObJ8usyDfN
bGTgSzCd8GPgLfXtjN9f1SnxAfQggfHbilKobvpGB8gLYszPP/9sGLWGy+n+
+1pQb9MDe0+I1DESYz/x32SA+dw3ptOM9OM/tW/twbcH1mlr9t3enuBJGBmr
Re/wr8lBJHPvfPM3B5ZWjN/8FbQjawavmf7IcZDuUxI+0l/w5D/RYTB/Wvaf
D3RJSjqIwR/4faMxAv5kYudVq7/6WIO8Gz8cD/Frpk3763vyy0SodGIPkgP8
OT6AXevN5zgMU4DJDzTkhvD57cJPeOsAMVfxmDtjPFgs4KXDXz5IH7XRUUZ7
2O3n8Ncvz/94ejHUUiRyWEaL3MYBH3sVi1WEiIKgZaQjlc0wDaSc8KPBwYu+
gGa0hNm7ukE0FxM2SJO5Zz0fgVUK2Mhwh0h1eRO+BP1iJBDZhL3Hiqnihh7e
VxHfawd9uRWMF1jmos1I/0o/pHlBNg7aYsFIxkMNnESL46zgeUY7DVrzwXgs
rkWOLA01Ak9nmy3abmCmHkzwrFJMqkXwI2p7fHwzPDvXQw1s0gKPPrlBLjNC
BSeXMqarOkXEAhgjJBsGD4hYgmj4YoCWdX4QoJ61EdGxlyphdRxpA6YYfTa4
V+Sej50T5B8JHEzewWNM1ODX7hjdu/uYDvSs/3VfuI+8nVmx/Pc1c+Z4YuFH
g/NKe2Z4aAw73dCEDX2K28DIQrGAnJz/7JzIzqf3TfxBn1vcccAm1ovpoVWc
kOyakKyD8bFkcE1DyyTX8YEJPfYbfMxJjDufMvyha+yzxhgOyARv2IBa+kwX
fv6Vfv58YMKWkWf/+4GqOfyPCTqjB/6N3vxf9PM/6OcX9PMe/RQ8XXfRfk1f
/if9HNHPY/r59YEh3u2n/e8fnxwmT08GiSz5iVQe0uBQ8yMtpyTML+lGM6cM
zYhF7IAo5/l6V+3Qf80eUYwtkAaHACeEN8D7gREDJxA9IMwAN0DSGPsE7XhV
FSAr9HyKUuz8SM4QAZ7DnnBLWE97b/bz7H6IVEnNrKNKRcCaNJBIvH/huyVo
9l0VJ3q9rISDF1m6JKiKcnIKRTLr5yA4+fPJfCaHb5f5E/eeo9n7NzjQxExR
/Z5FwmsmXmewaRYSKZuJMJ6FC87RAuOjBfwak2oagm7Q2bPKP7qALgbQBDwA
Iw9EylpQIPF4yHsHe9Jo/Bw0lC05pSm6hO0Z9nzwLEEMgRnbUiglE4eymgZr
1JRKDREiH146c9/gCgpyyc7TxXvCP2IEWaycQPGbsW0RRhwZQYCqDav0PuBi
nPcbTBOltiL7CMZ0AZKtfq+v9BAj6MZ3MnKGCtpM3K6ZR96wKFXimIF+5h4y
HaVr5OaHG8xoCPw8KRAaCwv7Ia3ztGybY6bLAKahU031OMneanxaNsgtPGPq
aIDOFa5zRhKXRV1Vu9p7NudZWseYC+IAvcOFfIA6XJoiWxEEos7X1y2NJksR
1QLMoUKCIy6A6pKeOWyfWF+Ok6NRylSYHTQBMwidyhIJCo4uvjoMB/HOuBks
H/upg/NwD3aHnrxv4uZCFEnQxqTbbWhajc0J90KhVfIduv6C93HnCpwyAu1i
WeqO8Cg6385dq85aQhshkPiWQz+k+hKIziCngW4E3vPt54wGI/ZuSB3xHsQg
cSk4cuCXwOBe+BjCCElyQWCWMHSFfIA4BO9rSEYzEBQ1HLLidgAdwgOOng7g
IYLwoRfmKGcoOHTyZ+SrFYMLhLQRdZT4Zpuiap1blDwjeKxyhmUgahIXryhM
7zBsQFjBqaRolrobxQjB/U+K/H3kUDChiPOr36Vo1luZpKN1w80xftzurHjr
B3iwGxQuR2gVIOhM2L/ZIS4cswmwF47iOE+HwLYxqtLF0qRLypYK/LECx+sK
KvaCG++/DkKZXxLazglAaQjnthQIiDjx73DhE7wK8XEOAhp08Oy+iE+2BOmA
NYxNChDe6JhmF6aKHozCwvKnazQakLuDNKvqVtAl49Dxd+kguOZcAxXkOuwi
XXEHh5ikkZB8WiTwbcJhE5w4zDDdFRhYumRIDJ3UXqsDeg3jCwVkRBsPIyO3
TAez18M4+YDwYFzfSb1DMGgdOLe8NbS7yH34zIJeOAoQRyC/8whywDBunI+D
ZYKCkJIuswOaxjnrlgMrGwWMmSc0NeZwbN+geHEg4K0cIpL66bzCMeQwVRGh
rgUFAGJgYg9UMAQKhlz8aGyvMGdqKNJOkwujphoojs8tdkpB5nYUR0LiiL+X
Lzpt2ppsSQ0Qy8wRSQAcrFgy7Nl70mFn2pssK0N5xhrITxxEtahZKKwXVQ04
EHN44phP4k0uy+oHxwMnQ6cqPqBnglQ+mjnyx0yiFfE+AxFRpE+1N2hCxatS
0hM8pObh2F4IMoVGCsR2efo80VwBYkmYLfsuRqxg99/MCHxsrYBVCJUyTLAO
ADg2j8bwFcImZJ4Ec+EomIxww2kHI58IcRvBPLFHn7KQrhF42IaUAQtxujx6
/PjwGaLKRkSfAUAmGhoLZXcYOGTvzqJDBrY1OqdT2gvBni7ZBaV/jc3jsT1b
7cMFeLDFCJnZTQqzBiKCt+dAORvWPbF1nIfrwZ2b5rMAgNQzH64ONFHYQyMo
HDdfR/pB1OiK6QUGgAQ+pHo/FbgFobuXWwxF+GPjVo8GMvA2UQRu/BrOf5SA
ECjgrK+nNJCB9QxgV9axcWSYl222BVOCBA5iqchfAZNyo9AFKyvDwk9XiM4O
G0RpGbJHD90aicKV04tIHCaKvh4H2REDR0WpHQfnGZEJz3p80I3ZC+i3n4bs
m09B9m0A2WckrED2CeyOiJ1UelhmW9ho7CJgap/C9jvL7uh4gITg6DHmP5aX
qCjJYbvLbxBzDFi37irBUYUVEsEdTsDhkqZ4/lyf6WKRbVsKn+IeGc9KHJJH
p84U65c9QKWNnMaHqNQA0jzMFNjmh2FUZa9N41VAWCT9nUYDErQl8bdEISDO
jJAOcjG/HKjf7fsXwFYdd/EY8uB72kOeqlqhNPSOSOacEI/kDpJBSUi62Lvp
oIE6cXbFAbn0IUkyoleDILy9ZXaEMCxUKqpPwIT0nBtnrPnFJ6qTkCuO3eUf
IN0Fpib7jsI5NxLr8IuYwNNlIhydDtr7rMQ8EcGqDYBrYmgNb1+YGcVcIUbA
r5ixPWLGhjlVFZzQVrLQGf3tW5gaDdR7AhdF1Kc3sJ7IhNWQMilDNR6oRLiO
WO/dgc5dRPKYuMYctR7HKI3PYSTT7QcdjkCI5YRDl9E0V2lekExHI+saRWRW
1xWbuR58DI8VBfmgcO5eAgeCAI9sZbKP2WLndFA/K6EC08vWzEP3WmAr+CQ3
zTaUh2ieToY6TLLLgdyD94StbOxh8piVZVTxFFmC1m2NpimakhmG9OF5lGOk
7wUNEh8IuLFxqgqmb9/iyhBT76Qr6UPcHx/Gco+Pk5C1bNIIooofj9doxsN3
B5XecFZJVctZdoeMhoCmhkBaOL1QQAp3Kji9uKbGF3vjF+wNSggHUBtxsvEg
xzD0wjCfcw10uIZxXCPKWuouj5AQ5Ur6nDhEEHZs6wCMQmeWjwjnn4VKQeRT
QBGPsUOfSuYtTNGLc7GaTzHigYvdjfIF+BRG8Z1cPj9jo875I469z6lBs4V4
DTkxfACmCXzo8PICRbHGTvk8nMEikDEctP30HaWM7LZo5ou0DZa/Uexl2cJ0
YOnKhIfnx3PMWbyBR2oU+78YaIKbO4ugJTpYanBkRK7jYaNoXaz6wsLILLqe
fYl+fNLBTzinhveVE0ecg2/EB5eox69o4vvImkVK4DHYyBM431pOghrV7PQG
hgdr9SNQPZ169pMY8xrorVq1N4TQ9HsnvF8kPict32KSpQYAlJTMPrA6nPRl
6p2EOWLNXLmIUGdiKaxhjZajHHXGUCwR6YR9Gq56wkGcUkD80NRGpVkjvPQh
LcQjl4IdjDjyB2EUY+wNwGeuTAC5xZEN0R5TuGxqTEInnkqSJJSMsihySpGL
cPWykKJCNpFIaQjwjTvGjFHyScvtru3knun5ZzJAlHMXGqgMR2McPkwUtLL7
BckGY5jgVZcQGsb7cQShIcxBD2ZGOgs7NLh+iQsh4WDg6R0LS84x5C1pAwwa
HQXUtCghlqxEbnhZ0SzQtQLL8z3JuL4VQKKaWixtUVXvGwG6ynnbbdUDLHOR
mS21agt0J3RJ202YcmwHXvRZpijPOyacujl8IQV4iB0mmNuAtROC4g1ZnP3s
PBYjxwlQQyRHnpxKmcantqtJN25qZN9qkK2fIB4YnZhnRva0nnRKLfFJkZzj
3wiiQxbG29GBbrWScUrDtLtidpMqxIRNjIQ7Dcw06hQMaQKYLwOU7ZCLNfC+
5Os1WUpuDdzOpmsUNMDeidIqZINEundIYulcVBzs4ZoDmegRp/Zw9C0MdCQn
nlNs9mN1KTFB2muGinw0FHDxZ7x7mAXlKSJGGMr7EgNuQASiMbiXlIvH7NII
u+xx2IDjHT5A415rgIQ8guwbYLOiroHBXFS3DNEekhlKRTeUFYGnx2KohUUU
FZah5ZrnxRCy6BTZLVeasZh8SlrBddo4J0I/ab2+JYZM2GQrFZSaqUM078Mz
I8EQNHlqZ0GRJJaNzczBkzm4nnrZ+gVylRlWURpvsajRLEI8Y7OCYIaGf/jd
6Z//+vzlCXCCy79enJ9f/UV0KmKUM0ROq5CeCRZt1mDBq79gPvpfRMTMEOXy
PrttsHHBP0PjXzE4OmFw9Dfa6FfIzrAxeozJ52tGwR58M8Mm8v/5SYtVu8EY
AubNpKEusoe69UiPOj4JPkRfNBpuSYLG7LaCX2+5feIoqMSgvozR0Hqea/Ly
JgO2W+bNBplLBM8PzB4Y93eY10T28MmfRbWOxLQ37SkXo+aQBC0XW1dZka3R
Hx5i7duBzPOgDM5zYh1q85JDSNV19sZGTLUzHnTI2B+urt4ci4/wE+UeOs7V
sEKQ85ujNe+dosKA1RtKncUjItMhhLCLxuGtSFiMglKbgBNkH2H3aWNjvcTg
k6jA1+kyF7c/hWZppfAFApTHSG8uP1FRmw3XqphxRSrU7rFWaFtNRbcXN67s
VisZH25jjGwM1iFyuycONxalkjZPrGsw+c8EUdQ8zuPZG3kNo6EP74/UGxkH
dzg1h215zY3UxtTexA8dSpe6x4oIf9MIik/uDFI7KTZF1SngiwXnW5o99TnI
DeRS6SJ/gYkLN3THjX6+Y1ZpUbshKsIaByyJ1YnXnZeCZUZOS8NNuElv97Zk
hhN4CCmAUUrJC5COYsQ+gbL5iwMCHwZP3ZUZ8CkcfNBMDLYEsmtwcROd90QY
SxL2bHqPudHqNwOwwhAaeHF6eXrxh9MXsGcv2LfaIYe7Xw/Tc1HghpRBSVR3
vy4822faknNlWzVUO2n0qb7ZbuI0Xzil1+xGUdPljlclSxhPHjmNTH9tZR0H
QfghEvRu2PAwrl03S7AVd77NaLY0QOuA8tsIgwI9JyvuJMBjYKiUtNUgaBV2
2XlyKfZ296uBNSTGYnzyP7G5ZAJoTAd5SVYfh0nBn+o89TnsEivLB7HF/h10
7Hjf2phBr7PuiSbuO6TUs4DosOGvzcwd/Rnxqbh+GuwqmC8BopbQnCGglrwO
uIHlOlOBH4BoMSt2V3TMNIwo/7Gq37Mva9NMTSdNUc/3bPQ5CYwYjNWjbmfu
XYdWYztSkpnR/yAhAUSiIQFjEQDjKDhvmHSnDsuWk0hhWNWC0G91BUSakUfH
MQkTHtLUZYhivSM9Er4U2kgsKwoLtYxQMCyK1juMqTF6KeRAOq+4QEBakmj/
QnI0c2T+H7K0cNhWslR6nDTQlW6QLbHORcizk7vT/1m4irtfbB2PkeSD4CR5
VIzBhgIaJVdLfJnhnr2nzVDpBdYCuFhfg1E1zbuGlW44N5jxIgyVUX9lMFuV
mFWMQig7QIRjaD4zqui46sao+qx21C3G0R1KhJ2OUS2E35KC84qUoOY634J+
zUWj9oDNRrYdwrCRkBcIm9mvSBFs1cFmBK0g2aXVquf8Vx/EyV3RhNTl+ruN
Q8uABub1O9h42ey8bbqjG1kBCYvJ3IuLuOiuxD5dIQSB7oRBkxFFkhR1TKUS
d/NE/WV4SDdYRYLwbXE3Iw/UN6JaI0OLmdKXtB662DhcLpxBjgXXjwnTUAcD
YUHVmVGX6RIWtC8yudOxMb2oEUEC4WmR57MglWpGJTvkgMuwF2lpxNqgI4AL
RWl86TWiKrv57VS0D09KQ4AbLfWg3Fj+nNAjSToBdrpJns48BhxWdakKO2Ze
gOzgShiKwmUEBTMizOBC3GQtVSIQvyJgxX3JVZio5Q4ZVxeRo8bOn4l9znIH
D2oNWwxM1MSFw0d7/eUD1yiMjbS34PYsgStXVM2WJdvZ6dX3iG0LcxDgN6wN
VhuPSuSYMD18iZb0JrSzqcaX+ryMUfN0FCL+R97OG/n8asr0PnfWNNdR18Ax
NOorlpFNiqG93Vyy/DhuhTqEuyoCoxLoZGreZ66IbVT3zKgTRKhsAA+gVeIs
YRoy56kam7Mo1MHdAyPe4h5TfRTRuvSNRFmRJHwfm3Y4LotSgYqJuUEgjJrG
WeGAPlQSsWTsLK947BMjKTeWv2aWChvyUX2VbzLk319/1Ps+pJMJUcnxTPCZ
Znb6MVt8jUoGciro9L2eBOesc3gxGgF52KjjbiFydjbdygj6zqiv74nP6v5M
UnXCh15TNgkyB1dgnynCU9lM6ytFbqzIicVjFHedMRfDpQn2evEkEKQmjy9O
BAOc7h8XefG6zj/3MmV8ahFGfnK/R9AXIfOkqZQgTIP9gAxp6HkMlxmYHtiT
udNtOIFHJV6GNW0+UE1JrCQ1JyXXSNDNuzF+gU+Kh5n/D1CJFPnev92xzxIE
n3iGs6VYNuzS25W5ZMYCmb9vuLa38zJhuQuprlF14nN2sWvaauNd9ieRDzUQ
DLiXnXiglsblsGhJgGMcdeOcbEKNLy+DQO/vOcrjHLiMQCYZbpB7o4J4c52R
jh5UuWyUhWVcSOPE47W0NIgmGmmuX8REVWhCO0WxI86ZhVga9q4hQ8NoXQc+
0a0NFCivxxxv1RzZrut2EAcilbLCGhBSfVT/CGr/TqLKR/rAvJpPqPCrftAv
U7f/G1cw6zMekfqtAwObdisw+fROTgAi5hpV1Vb37bGENKmGDoNtyX7lZ7Uu
rKypMrXe+5hShqgW0ox8aI7Kskf5WvJ4vsK40JKKEJNJIcPIP/rPwwrsRkGF
CkfWYYNZw284KBVnRktd+Khwu2QsUtKgBxZLGyMPPo5B/w5J6iNxhBUQHY0r
9jMSP8LsA9uNsPgmrvlHsQctFBbtzL5S23iZADPIFLQ0MekCm4piueYO3RA4
5R9CXNwraBgrtBKdRIi5DX+zPxSQu9JLTLyroqrEce20vBCgx9qQgGE78Vgt
XM/UrWJg8CKBEJXfSSlw2Fpy/XMM+UOO2SJZAGv4ogkSLoXHti1duQH2Fqrj
kiHs0ZuVS7YZxASi/YAqI0jrHRd31pFjtKGj0AUQLBc+iRY+HcJhdkrc23tY
jI9s+xxL5oDpQLBqtekbXz+aXYVoi7naxrBNgcBNQ1gmH7X7IvrZuBfe7q14
NMqlJGZnH9nSFSdHdHpH4XpiTDvlTGJm+oEXQTKQhikBq9aRsUrOfwSDLJNl
tt35sghT8krIfiYOIEOptGRAsWGHFxp8gKVb+wseOqXzaFzSjteixcRhTCFC
E5JH8bGh7cUQdpEhEBarrEdazQeCYsq+i3nkl1/PuU/D6qZ6uMszlkFV+7pb
JjP1qG7N24EVAMrXcrYsDAr2dAfBqQGfzSd9W5FDhq1vLi5KficTnCJJuUG2
i9uHXAF4rR8su8OyYtUv3h4gqDcYKNbynoZcUnf73koGsVNisvN6pQ2c2RXs
G+Gu8IjBS4GIcfEHNdtTzeHMyJlDbjTTIDqlzhJKk9KNhmlSPDJKIIqLluIV
D9fsB2jQq7lV73EVhwOovqR8EJK7cdk3YYnofQeW0cDkpRzyKpKYwgMhuau0
SuwOFQQL14mlBDuOiWozLsrWiRDehVNmsrhzyxw583kfKQuE9W8ltdRoWGcw
TimxJ97yRZ2RLYVwSLTnKPbLJWGRGxBDBOagNQM1d3X/HI3O8aSMEbRhXEFs
3s5nLuTOyXWLgiHIlaQrOOgo8g3n18a2j4PcBsMex8jxTQrJgiCgrNzpJGF2
6QLNrA+ckmHCRdI5Nll7R219zeIKAD3sU+5vYpBzVHnHfvB27PIOKjPwJ180
ZmjjOGzv8qOE6HFkBAWZ58vwEh3CI7h9JKJhNqdOn0uV1ur06aEt7kaPSBoM
3V6apOXimochvnhyrNyqKRZbaVjUBOEiJL/y9a7W6asTIOLorCfoR1wUWlM7
jKNLkMVizWS3HqSvDc4VoFLV7jOEORgGoLFDe4P2To61XbQzlpYB4M1PYqRH
zqQ463Ug0tTjhynoLtmWTP+eSEZ3gVHmGugjoTjtpxl4VAkoqPkKOLlRNisZ
drF/61YmMscC6xmMQLynbxAn8tzB7N4g91vckpfjzvzhbvIll7+Ui3Ti0h05
4QXDSro9AQzrw5dY2aJarznl4C7sjwtPjHRbLSxPW+EHHBEC5gRnA4xuzGKR
+mDALBLBF2O+2kcgBspAZwmCdWFrj4Ync8H00sqCKJy9R7VTU6umcBShS8m4
SpfBDUb3gXJLjt9rso1cQkVsrqaiOILTvcd+fsPZTiObbVFnr10Ffmyvud/N
20FteQMEAoS4AVlIGYa+z+BNRYYgWlt9yv2KZpK/c3dUgXNExGffBDkYhnRy
gQZx4IzOWBSGiIo3zMZ4yRD8M575PD/50pA/Ty/wiYaEnsLxeAIWGNgi8KbA
2GeTrF1MtmCI3ixn5h7nM7LdqxEGmAw1e18T5/cCWsWuwPylCReA8eBiTJZy
FeL8uMNKRz1/Nj3BX6sNzYGQ4FyE+m+IT8uDkGu8TnyRc0HZZrAxH+RSFzff
FEFAITL3hlNryGcHJoMXyb2cm7RAar5NXA/LQE+RS51AbSqMePtbVxYPQ8SU
Qy8qp8tW6eSwuJT6xjCroOQiJSu8O49yKL0LC3k+wgNc3RgT1UfFc8kJOddY
DqZs3HKG+08w21rZ4XOMzSdS/yJS/SV7zV+Y0C1o4kUDlqkhdx+PdTaZzEbE
zhw6ot5fjsRjnqneTURXZqCC1iBh4ZFp4PRR9HtRZVxVHKUCVZnS3E5cwLDq
FMnfaocaXFOkzfUx6Faw5ITX5gJLjanz5r1o4WxSk5MsYY10YBaafinlB8Or
uAj46EqzhLUkXH7vXAstSe6OXzBX3MUViDnmI8k1bczQUPJe6RLe9e9RCAW7
fSURSUmZ8PebBCAUzssIKwH7LCS6sjCuBQfHCm0KIV2uFHZ3/bde3THNfvHF
troXpuQktUy/hlmQlTWyVWxKDjM9opO00bww3uowBYwzDxDkQ4MIqy/MoeH3
jcTK6zbv1e3wa5uydsvKusw2UaJbZMZ5M/CVIICYd6ielRtY8nSNZdDYTKOz
yrfBKewjKCXmWL7zbnAjC7wqVm51k0BDZjqZV879mQYe3uA2BGqYtW59VDL9
+0bevjMswgH1d6mG43lPl35C1qPGQVQzsCRbs1MH8C7uIQJmoEIAbpLcWDlc
9a9bbpCRF92WByXt/rYZoSw3AvW8IsFVqph/tOQGiPgoV9mAjQSCYbXCSkcb
xievFDnHojbCXzG4ix8Utdp8FjRtxNwnhtp5iyt5wcC/gNfEZf0Et4PzPDq1
3//48qW9vDp/M+pUPuSaOb7iFkwqxzzuhv1czlHN1/V0S/hxqVR3pQtacHOt
5ic18qi8wEmn5iCq6F7rmUsNHGJuRjCXlKG5mReZZjUJ0pGqpLv7BKJLJLng
1w20lIik650nrTMReFc61SnMLL6XkrLGxWejuDwt816VJZVvzFsRhPHLFL6A
Tdt7NLgUEM1O8WCDJQYJ+xQv4ci3ohpY4Gj1Nx6LMgi0nJMyRPWWRTvqaMaS
6K+teD1V7idesHvvoyUtDE0AVtspFTUreHLX+VaVgkVVM85iyfUvKFcN7YCh
Ikyp7i+7eHwWWr8Ik5mnElVzNZXIR1uHRZXcJVQ++ZhxZhLHFK0UvZOd0JqA
FJV1Ui4zb0ggKkdm3r3DCvEBW3TPyyqzNMNhEhJKb+NNLd9marKPXPvTzVxU
33kW+aFkTpzveo7hMX8MTXQMFcarpCSXIngwT1iBFd9QrGmHtHyFzFKcPJgM
3o17/fF64KJiL7tZyxnOImdny1B+uBqTgUNg1JPQpNKJU4b9uGge9KENrjvP
VQ+1zONnwCMomLh3iKE46yaxowYvOexdNRs1S2A3JsxtF0BSUKYWh8T9im4j
zuZf8c0Y3a0ILs+IYFM+56V32a0a7WVO1y5c6IVBZ4FPAh6/L4npjXOTkA3m
zC/sgYYE8ufhA1hoMCQ3etPGaO+dlI9cnDjcMTN4eSUzKeqkcweIv7c3WADT
u/BjZBcc2HNJ7A8euqCqg8P5qlOuFNLhIXXdj9U+GR9Zgl4nwbU75IX2a68F
COTCTusv7MwbAikFm4Gnbqq7BF/xpSjTaFrRC4zjmNqTzs2CoVEhNBO/pyiP
u1595F91dSgWEcXd9fZj/3ZY/GCydYUPiPOyApI3/WU4afwdPd3Gn/jGe2mr
nz/Ep5hTrO24uP7nvh+MAUN8wBSmNoZ62q8GIJ3fdAGgMAiBgNJakY05iWGf
BZb1/TSMFFrCVqz9x0CjmFCPsFH7ebDRJACNTmNfsi8ddhxd04mM6wIVBGga
0y2MUa6y4sB5Q4EVn5fgKymVoB7AG1ZvNGskCrM04oGhubBwPJVyyc0OAdLk
VyKJS/JTkpXjQi56zyW9cKslbDXY6kohdC4bkqg3i+rgznOKj3DNC5jyjxev
p3RPGvzCrk62g+XKUV/P62BXlwdhIqaYG4tdkdb4NmwQ4eS3KcbXDhy+UC5i
csPEjm5yLLeUiRbDyzqikgk84yQsr+auifPu3AN77y1df/voMGB4dJnmhZeR
MEvorLEH6FbCXVihtqoFbxAJki0PenEqKkZAA0HzYqif8dH4UByo/lvQuwQe
tK9ShpC3WySWLlGETWoQNDiRsJJU4Hh0QQ1fmTilNXXtSuwEmuhFT1LdQF9c
jx3MvduubS/ygIUvXZg6vAsqNE4pOxsohW4T40T+65TToHzlujWlgpWd1Qji
DHJo8paWMkXQg3UV6hzuGdr0NTdOwkJ+XL6uc7MqFcD2t58TZkuu09Q0EPyc
ynuK3Dc2xnjsrVrjK5ljHkQqVRfkd75XNnXE7UuJlI0MwZNRk8G2DBwDypAT
y9zd+GYZ0j6Va4KjD7HPg5R0dK3YGBbUkzDFMpOD3lZ0SSQHZzCKrAiJEd8k
SCB0XhgCfmGBlqKay9WhSriYYEon5uGTxw+ik+mJhBdDLVx1WiIEj0xrIEu+
rhJMOPFY0XpIRwOtP9Rghn1Jz/EyGKxQwQVNUqkN42gNVmaza1rWeJ2y5jjW
b2lixnoANp+Ag6HeCc53FtsYYVZj60pcoPh2xU+GyI9cq7wdWhdGSriG+Ulz
zouCRlAb7I3nCVgPWoKI2j+gfDweiXgyXJqzUyeIOsBYAV2lzgk2V5Hyg0Ol
0nlWX0r09lnZQd15dxkzMQaSaFSyB1tg4uJ58iw3GEISpN42wDl2CgjEfSCO
5eJ3U77mEH6jsBuurwyNbbjZW8ZbTyavX51M3qX1++nbybvXJyevJ4j9f/t7
uiUIY4LvZihzfH1V/Bqh3bAF2KuvkPl6R9bCQXzDtNGK0z+FmOI6X+d8F6AT
oq5tMXQ41f5A75DqJNEDbaa3Hq1kceTeYYDTfpWSTE2ZwE7QcUy0Cd8Fd1mM
H/KpWyGiIsDIsAsPnm0YzUC1ig6cHOacRdhkQgShS7Dl6I1utHZ0MkcjYtHe
1/tJh6SVv3Y61XVN/GkoeV3VR0J3WW3SpRrWhKyZY84oMUH2iP148fI41JIp
BtdIUR1thKSqlKDGWqha+QIo6A2mWJDGg79J8Uuv2+G39uANQ/XrrPNVQzii
24BVwvdgrHAGouJ4V8Hdtk5i3mRzXDpsOTl58ers9TtSV+JNOyTkS95Gd2IQ
XzpgvOAHMIyokv3KosLJOfn0wK7cgBFEejF05cAfB+NYkxD3h0cTCk57f3Gw
keOfnYhsUAy5f6MAobgHccVaXJSKQfer9bp9I5X2E+WycHP5EjJGBPtaWXF9
7wBG7HQLq0BU1SzMQGn7LtSxYcsTegE+ez9SzHMMeVDxzQ2aQvFN6z6VQrVv
qiQp9sU1F2iDI5/DzCTtrROqcHeQIsu3py/Ors4vphjJrj6IeSGZax7dHt22
i289ffboaKQmCTtLPfSYrrsbv5Ot1MvuvCjJKJd0R1VVsIxU2fN4SWF4LenS
KZ0TJ2CIMYAVsfA9kCitqy0P0orsZrCqkhcYnOIpRdfF6AXE5IyBaWFWzkup
FgNL2QlfEYt3WF78ElO1lqDg00NsSd6yfYbQfIqbGFeEFobOUNGAtEJlSkSy
F/WMQjRac1z4Pkbp0TtKhNBdPGT6ZDSilCsKy9cbdZ+ipE5iTO5SdgQ37Ahe
N1y7S2MDQanDgYqMsYsr1G2roRjy834JQ2Sq54Ecm+5JJaUsdowqbfkpifKG
AoTKFe2vcfgKTzLIj2l/xS3Va0MnA/J84JRTfkt6SSkWwLWk91RKjO4p7+Ow
0m5pxCgDA2lwgcpyuYbpb9FySY7GD0bBNQLwaLnd4HRm3vUygSWc4evOVzOU
bgutp6AS7LaU8zAlt2FyeIgEI8BfiZ77fDAtQqgOa10rEeb/6J6RDkdlGlEU
cqco9YZKO440StpK0h+NRJLC+VJ31dOZErzWT0OXEIjGn/vFG52t6mAeUY1G
RX8jH4uIJ8Do+UEQNJaOqaegCATBtyt7A1Gi1q7glNPDj7tGIiUNUVXDQxEc
PEM2cpXHDteXhP3jRHX1lceC0eiFGUhDf5AwAwF92pwdj1PPMAQ1OeBnDlwG
nGPlqgVg8hcXLVm6uF1cENDYnrNz6nOg6eARDtPBkbsHV/UlzDxsJPl9KZXU
Ajw9YXhkXOPwvLFSBkpu1qZSioyPdpGlfNvTZxwuaGTgeKGiw8Kcp9A9Tchz
aAj/IAd0JwAWtmWjEWj+F9bh7FThRD62rw7nMANFHfCm1MnEPDTMJ5eMKKke
3yNy8bxEsGFG4IUV5GTojKX0l2xwioDlOfz/2l4qElDas6bZcfZqoP8QiaOO
pVev7dGb6A6jX1/EYPnxr/vZEAgelkPsCyK0nNOGBY30gWBRp8xiwfbQ+4oG
Lyka8b05d9y8M6RSezoauZto9inPqofxXTNIawoWppuQgrtUSLzmYWzCw2RR
bJZ9TBPd7TJYhTQ4N2GQRVXTG/Es0xiiusNaoppolypLq3KcBgQtUG66xicu
/Tyk+RzBNp/LMH1FU9zpk8+tcMpXJzUE8UIh1Pjrl1RP0Js3eYSDwRSqy+qd
R2nsOkIFu7vVUYF/cq5qEEYq0TNUfKgubQQ+crZ6d2BuwdvrTIvxawH7wP50
dQvJ9RDe/8K3ZXlOwX56LY3s+cbIF0SWjY+vS9EaKlSniFIv6IoJnyKgVb2x
ZA+9TlUhR8F2cdxiSVGp91m2ld6DsHUY97R2fxQZiOYhEM1JDwjXMH/Yk+YQ
38yAPQwByKLEYm/69cv9MnMQsDNSgtzlkEmFY17Yfihz6+5loxC83VfoGLNG
sbsiW67pUEsdAGFy811OVz+x5PTljN3t1luEmRFq38NPja+VL/MiyBYoYFVZ
bW47176qUiWIpMU1ZsMTspogLlpAJS6hTwUNBIYFJtTbN+eXZ39KCEPIvUpi
BtaTT/QSI0t1NRjSUXrfHw+wIMYg5ZlYwPnMK1ioJEnophFcMgmFvqzWBGBZ
orGbbCSImnDdOJDUWlvlwRMMyV/hzauZpsBVDQeIW3KHxHt3E6nOxABZ5HfN
SjmKQQasBvoE7T/ExpjLBuYlmpWfKDg+yFMTrCIRhV49WWOlL0as47r/ePGa
z2gU6kDBhX5RHAj61xzQddCD4kS76+MZXi4tA3eOBfWX6PACFcG/efjgvqvZ
1TOopfw17QJpY/9wAWwMZkthdKBEVInYEqCSFwUFmrtXJQSU8AyJLhg/yLcm
vW08zQ7UBg85hRnkPFSfc0Acj8ShDioj3eKWkShKTcB9uLy7uzDBCeKCvR9c
jp3zeiiFbNavyDmLSf3LYEZckF7r9vUSSx0E9FPVLIdKVrJes0Wjp9o1IGOa
NBd1Ih3qzIFLoT1KUHIiiDBsXCeXO0oI6yY87IarPWoFEdiAXiFHutnIZ29x
xQDaFFpPRjv6MFQEay8ydOqzr0tB23/f5XWmdwEDU5JCUJ9kSY8NkSdal5ln
SQwohOUjEl3kTsUjICb3Gfv42M3DtcGalhyCpMy4evNXJOjF8mMu4GrJYG9c
XzKcCN9eL2brZ07nkSHETF1rMWTvCHV196lum4qmaawry11vFPLt31AX+mbD
i1sjTzlbOsI+h5qRSyYvAgMeVhhWyzmpH8t9BF86RcdpGCIGN15otOFtSmHI
5ifxGXqkAFlpRwyRiG5tAcMkCKv3LBMkdKm/iSO7o1JKUH+bby716f8hOXdu
MKJSrDBilNIIFUfG09hgWklbJaxgB1dJBpfhhnjzcLW8Pia+4Vac7eICCCaJ
LAOfzt2mevDMQJUk5urivWffeuaLALo9X1G1OL2ZDGQahrHQUCT8OPvh3XWT
WJOwd4XlnpsqLedHYfs+YzQeia+w7mkLQ27ovwBTXCQmYReeHILG6zZILwhX
QHpWwMIyifJ9GyHh7b2OUnFOQ7dFCn2LQTlwZ+TwzbFHclWFhl4j0u9dF8lV
fRxUIRoHHVJV6mzEMc4k6Y0Vw4qzKkY+VJORq6xzt6QnEGFqosTofZtMbYtF
MhPNlemXiAvvSBZxSeaKm3aY4tFTlD0zjdx74w7/8wZNnxNOOQzqbKDIPELO
1TeG9KLk4MGQ2Rk78JKD1/KrjsE7YB5HYLsDQPbfb+xhoE7pAkoke6QaooPy
xhBmVZO3+4DMHdAxdNYFG4d099lgYdsDC3c3KT+/jEeC2s/U1ZULPE2+Pw0c
D1TOw6TfoPodnSWK4C7OL48d+6YmgvJ39jPK3+HAX2g9SlK7ymzwPqwoAbB7
/RXd6oII5cgxGV93dWcIhwYe32+1D1y/l0fjAfSdNlLARi9q61R1YKLDTFim
uDtrHwdlSDWkgeEF6JA8OEt3f7zUsVX/qhso7hryQv46gKXhxKlUcGQsiLvM
ZeqhU4R3lCp9gnnOGLuLjGIQwved8qVI6SUHF4F4rqgiQVVU69tAEAYZ99DE
lU+XRiokCE++wNGJaOR4B8VNi4o4I+aJAsvakn/0jsJF024w4x+saGIDlT6o
aeLNASkjPlyehLerU6CEI81ReRKnBqTuKlMuK02SRjL7lHa19oVI8CikLsK9
u3r4asIVub57/sYePgrW0UHeyLORkuI6r2DTa0oHGEk+XZntWsRXqWAuIwJw
og0tL39GxMmte+AuBSxZopFfy6GalAOLXCfjCJPPHfZAm2mi59H9T4VsS292
kh9jKeoGUSQiENJ1j/X4THMORvaoNKBR5hnDyfIum1wT1tjooUxZLQjGjg6N
BgQSrGOjgGp0jbdWdgVTqFNEYkoGc6kpEyyeGgEyDJp1XnRQEavH5KLpNDNy
aWBDt0yj6Eh7ICJv4OstqpFpNI7viTfW3XJbaiFKHA5otEjJQT7AHTcxMyfq
ViyJbt/5pMX30IiHJ92Xs+pKHcbZFzAhKYeHBvpQViteDoIuhHrJZdC870Ey
4kj3k3RFMqqimtbOJpNSMZp9yphxyjqNkk7JQHOKNXGIKGdT8DNsiPnUwzCF
c6QqMbf4RdMx16LaBsN5j4EZ5/wxnMFInlOxVe5MW0QafeMS6cNQGVreGDYB
0vsbGnldsIHC4o3644NyBZK/1IUPjILQNi2N+hygjQdHCkYos5tBL5gPdX4V
VSD4ZvJV+PQ3qER5Hb936bPtpGP7e58dcfZTsdn1wKnxOaj/y5zruEVlFpAn
dwt3cD2pxnn1R3HufBgnioSg4jKibHe5P3440f81EqHkcioYisfbcGDHK/bs
OQ8K4KxziSW7lnHRdEFOwg+pkX6ABU9KoIuMxEAn0GTk7I3cCxQ9Eqi7P05R
Hh6fCrpWKpi2E/L+qikc7SuM2nYq+Nx9T4GUGyQWejA5GBE6Qk9mdFEBXgGJ
JUMz8SUP3lXAwusGQy1SJVnvG6jsDC81Cq5cntigooy9P/MdI6W7sA3Fj5pe
QRsCBuCYfIIKwQ3eq93bWQZfqeT8zdXZ+euTl8FE5xR8iLaZtLrs45bOEbA/
JYa4nglt3bAcd0VrbSeT7hOFmpCTw5wPxuMDvWzVYX9YRyPQblTLCOQOVt0e
rNCjlY5I37kNaEdnFKijn3k7nOKsBEXWu3EutCpYpFKV1YEbkdRGzewd1wQp
Y7yrgKjdLzlf8G3xUYJOlBvxd4Xpq7kcYsn5ehsZuWOR5S+wqwrBiq6wdjV1
osaSrDGtqejSJGnaEPQJ2i7mjXYwtmSs7EC3Ig7RtatB716rFuQvmRS3WPOL
PdVHqLd8V1fpUrTFQL4ISk2GRLU99Ox+Cys+JY1pwurSLGTxU2yl69kcaZ64
XHweaIIz1jd9kjgz8xzZPQy/rZIao5WuzgnB5Nz13tAXieqgYFHjOMGxsgCt
oeFCxh1vFes8wBWwkmGrtzitOrXjuWwfsRRfad5GMF7m+3SKopw8rTmPBfN8
MS6p0NC1wsh9HRSmJ+xxSKL7SrUOHxUObWAGlp7JfaB6KhZmuxWdm66rKHIT
iSEBbwfupr6LjnqO8P1UyLZwaSqfGyw6RJo9XeaghORsVYXaRQEC1V/68snG
HhhKsM6p5A0lrjcSKvpxC+bt0l1fOOytM4qZZMxDP8pyODb/DxN9HbJJyQAA

-->

</rfc>
