<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-kelley-rep-namespaces-00" category="std" consensus="true" submissionType="IETF" updates="9309" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="REP Namespaces">Namespaces for the Robots Exclusion Protocol</title>
    <seriesInfo name="Internet-Draft" value="draft-kelley-rep-namespaces-00"/>
    <author fullname="Kevin Kelley">
      <organization>Anthropic</organization>
      <address>
        <email>kelleyk-ietf@kelleyk.net</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <keyword>robots.txt</keyword>
    <keyword>crawler</keyword>
    <keyword>product token</keyword>
    <keyword>namespaced label</keyword>
    <keyword>policy token</keyword>
    <keyword>usage preferences</keyword>
    <abstract>
      <?line 56?>

<t>This document updates RFC 9309, the Robots Exclusion Protocol, so that
a <em>selector</em> (<tt>User-Agent:</tt> line) in a robots.txt group can carry a
<em>label</em> that is optionally qualified by a <em>namespace</em>.  The product
tokens of that standard are described here as unqualified labels;
labels qualified by a namespace are written <tt>__&lt;namespace&gt;_&lt;label&gt;</tt>. It
reserves the sequence <tt>__</tt> for that purpose, establishes a registry of
namespaces, and specifies how namespaced labels are matched. It also
defines terminology for existing parts of robots.txt files. Existing
robots.txt files are interpreted as before, and deployed parsers
ignore namespaced labels.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/kelleyk/draft-kelley-rep-namespaces"/>.</t>
    </note>
  </front>
  <middle>
    <?line 69?>

<section anchor="introduction">
      <name>Introduction</name>
      <t><xref target="ROBOTS"/> originated as a mechanism that allowed service operators to
provide machine-readable traffic-management signals to automated
clients; in other words, it allowed websites to direct robots to paths
that they wanted those robots to visit, and away from paths that they
did not.</t>
      <t>Because <xref target="ROBOTS"/> is the only widely-deployed standard that provides
machine-readable signals to automated clients, it has come to be used
to communicate a variety of other things as well. More such uses are
under active consideration, notably in the IETF AI Preferences
(AIPREF) Working Group <xref target="AIPREF"/>. This is understandable, but it also
leads to ambiguity and confusion.</t>
      <t>In addition, because <xref target="ROBOTS"/> was a de facto standard for decades
before the RFC was written, the parsers actually deployed predate it,
diverge from it, and diverge from one another.  For example, some
merge groups that name the same product token and some do not, some
match product tokens by prefix or substring rather than exactly, some
match line names by prefix, and some end a group at a blank
line.</t>
      <t>Changing the format safely is therefore difficult.  Any extension has
to be ignored by every one of those parsers, has to leave unchanged
how every one of them reads the lines that are already there, and has
to mean the same thing to every consumer that does implement it,
without relying on any behavior the deployed parsers disagree about.</t>
      <t>In <xref target="ROBOTS"/>, a group consists of one or more <tt>User-Agent:</tt> lines,
which this document names <em>selectors</em>, followed by one or more rules
(<tt>Allow:</tt> and <tt>Disallow:</tt> lines).  A selector may either be a wildcard
or contain a product token, which is a name that the robot chooses for
itself and that "<bcp14>SHOULD</bcp14> be a substring of the identification string
that the crawler sends to the service" (<xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>).</t>
      <t>This document updates <xref target="ROBOTS"/> to generalize non-wildcard selectors
so that each carries a <em>label</em> that is optionally qualified by a
<em>namespace</em>.  An unqualified label is in the default namespace; it is
exactly the product token of <xref target="ROBOTS"/> and keeps its existing
meaning. A <em>namespaced label</em> is written <tt>__&lt;namespace&gt;_&lt;label&gt;</tt>.</t>
      <t>Each namespace is registered with IANA, and the specification that
registered it defines what labels the namespace contains and their
semantics (<xref target="labels"/>).</t>
      <t>A namespaced label stays within the alphabet that <xref target="ROBOTS"/> allows
for product tokens (<tt>a-z</tt>, <tt>A-Z</tt>, <tt>_</tt>, <tt>-</tt>). This document therefore
introduces no new directive names and no new characters; the path
language, longest-match precedence, and group structure defined by
<xref target="ROBOTS"/> are not changed.</t>
      <t>As a result, the wide variety of existing parsers deployed across the
Internet will continue to interpret traffic-management signals as they
did previously, and will ignore selectors for a namespaced label as
they would any selector for a product token they do not recognize.  In
addition, a group's selectors can freely combine namespaced labels
from one or more namespaces with product tokens.  This avoids
unnecessary duplication in robots.txt files, which are
size-constrained.</t>
      <t>Equally importantly, people who author robots.txt files, and people
who build software that consumes them, keep the semantics they already
know: a group for a namespaced label is written, read, and evaluated
like any other group, so the mental model they already have carries
over unchanged.</t>
      <section anchor="motivation">
        <name>Motivation</name>
        <t>The immediate need for namespaced labels comes from the AIPREF
Working Group, which is defining a vocabulary of
usage preferences <xref target="VOCAB"/> and means of associating those preferences
with content <xref target="ATTACH"/>, including in robots.txt.</t>
        <t>The goal of that work is to allow a service operator to bind usage
preferences (e.g., "no AI training") to paths.</t>
        <t>Such a preference is about use, not a traffic-management signal; the
two are intentionally separate. Ordinary rules for a crawler's own
product token still govern fetching, and nothing about the preference
changes that signaling; the two types of signals are independent and
orthogonal.</t>
        <t>The Working Group's attachment needs could be addressed by registering
a <tt>usage</tt> namespace, with labels corresponding to the vocabulary terms
it standardizes.</t>
        <t>A label used this way is an example of a <em>policy token</em>
          <xref target="policy-tokens"/>.</t>
      </section>
      <section anchor="example">
        <name>Example</name>
        <t>This section is not normative. It uses the <tt>example</tt> namespace, which
is reserved for documentation (<xref target="iana"/>), and treats it as though a
specification had defined labels <tt>foo</tt> and <tt>bar</tt> in it.</t>
        <artwork><![CDATA[
User-Agent: *
Disallow: /private/

User-Agent: ExampleBot
Disallow: /search/

User-Agent: __example_foo
Disallow: /articles/
]]></artwork>
        <t>The first two groups are ordinary: the crawler <tt>ExampleBot</tt> obeys the
second, and other crawlers the first. The third group's selector
carries the namespaced label <tt>__example_foo</tt>. A consumer that
implements the namespace looks that label up exactly as a crawler
looks up its product token, and finds <tt>/articles/</tt> disallowed and
every other path allowed; what "allowed" and "disallowed" express is
defined by the namespace's specification (<xref target="defining"/>). Had the file
no third group, that specification would also decide whether the first
group is consulted instead (<xref target="matching"/>). A parser that does not
implement this document sees a group for a product token that no
crawler uses, and ignores it.</t>
        <artwork><![CDATA[
User-Agent: ExampleBot
User-Agent: __example_bar
Disallow: /drafts/

User-Agent: Example__Bot
Disallow: /
]]></artwork>
        <t>Here the first group has two selectors and matches both the product
token <tt>ExampleBot</tt> and the namespaced label <tt>__example_bar</tt>
(<xref target="mixed"/>). The second group's selector is invalid, because its value
contains <tt>__</tt> and is not a well-formed namespaced label. It matches no
label, so <tt>Disallow: /</tt> applies to nothing, but it still begins a new
group: that rule is not added to the group before it (<xref target="reserved"/>).</t>
      </section>
    </section>
    <section anchor="conventions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>This document uses the ABNF of <xref target="RFC5234"/>, including its core rule
ALPHA, and the rule <tt>identifier</tt> from <xref section="2.2" sectionFormat="of" target="ROBOTS"/>.</t>
      <dl>
        <dt>service operator:</dt>
        <dd>
          <t>An entity that operates a service, such as a website, and publishes
a robots.txt file for it. <xref target="ROBOTS"/> calls this party a "service
owner".</t>
        </dd>
        <dt>consumer:</dt>
        <dd>
          <t>An entity that interprets signals that a service operator expresses
in robots.txt by looking up a product token or namespaced label.
Consumers are often crawlers or other types of robots.</t>
        </dd>
        <dt>parser:</dt>
        <dd>
          <t>In the sense of <xref target="ROBOTS"/>; software that parses robots.txt files
and matches labels (e.g. product tokens) and paths against their
rules.</t>
        </dd>
        <dt>identification string:</dt>
        <dd>
          <t>In the sense of <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>; the string a crawler
sends to identify itself. In the case of HTTP, the <tt>User-Agent</tt>
header field (<xref section="10.1.5" sectionFormat="of" target="HTTP"/>).</t>
        </dd>
        <dt>selector:</dt>
        <dd>
          <t>A <tt>User-Agent:</tt> line (<xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>; <tt>startgroupline</tt>
in the grammar of <xref section="2.2" sectionFormat="of" target="ROBOTS"/>). A selector carries a
label or the value <tt>*</tt>.</t>
        </dd>
        <dt>wildcard selector:</dt>
        <dd>
          <t>A selector that carries the value <tt>*</tt> (i.e., <tt>User-Agent: *</tt>).
<xref target="ROBOTS"/> calls this 'a user-agent line with the "*" value'.</t>
        </dd>
        <dt>wildcard fallback:</dt>
        <dd>
          <t>The behavior of <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> under which a consumer
that finds no group matching a label obeys the group(s) with a
wildcard selector instead. The fallback applies only when no other
group matches the label; the rules of a wildcard selector's group are
never combined with those of a group that does match it. A group
whose selectors include both <tt>*</tt> and the label in question matches
that label through the latter, and is not a use of the fallback.</t>
        </dd>
        <dt>robot:</dt>
        <dd>
          <t>An automated client operated by a single party and whose behavior is
controlled, directly or indirectly, by that party.  Crawlers are
classic examples of robots; browsers and other agents acting on
behalf of a user are not.</t>
        </dd>
        <dt>rule:</dt>
        <dd>
          <t>As in <xref section="2.1" sectionFormat="of" target="ROBOTS"/>; an <tt>Allow:</tt> or <tt>Disallow:</tt> line.</t>
        </dd>
        <dt>group:</dt>
        <dd>
          <t>One or more selectors followed by one or more rules (<xref section="2.1" sectionFormat="of" target="ROBOTS"/>). The selectors within a group are disjunctive; in other
words, a group <em>matches</em> a label if any of its selectors does
(<xref target="mixed"/>).</t>
        </dd>
        <dt>label:</dt>
        <dd>
          <t>A name within a namespace; what a selector carries, other than <tt>*</tt>
(<xref target="syntax"/>). Every label belongs to exactly one namespace: an
unqualified label, which is a product token, belongs to the default
namespace, and a qualified label to the namespace that qualifies it.
The qualifier is not part of the label. Labels <bcp14>MUST NOT</bcp14> contain the
sequence <tt>__</tt>.</t>
        </dd>
        <dt>namespace:</dt>
        <dd>
          <t>A set of labels defined by one specification. The <em>default
namespace</em> is the set of unqualified labels; it is defined by
<xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>, has no name, and is not registered.
Every other namespace has a registered name that qualifies its
labels, and the specification that registers it defines the labels
in it and their meaning (<xref target="defining"/>, <xref target="iana"/>).</t>
        </dd>
        <dt>product token:</dt>
        <dd>
          <t>In the sense of <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>; the name that a crawler
chooses for itself and uses to find the groups that apply to it. In
the terms of this document, a product token is an unqualified label,
which is to say a label in the default namespace: "product token",
"unqualified label", and "label in the default namespace" all name
the same thing. This document does not change what a product token
means or the alphabet it is drawn from (letters, <tt>_</tt>, <tt>-</tt>); it gives
the <tt>product-token</tt> grammar rule that same meaning (<xref target="syntax"/>).</t>
        </dd>
        <dt>namespaced label:</dt>
        <dd>
          <t>A label in a namespace other than the default namespace, written
together with the namespace that qualifies it as
<tt>__&lt;namespace&gt;_&lt;label&gt;</tt>; the <tt>namespaced-label</tt> rule of <xref target="syntax"/>.
The term names the whole qualified value; the label itself is the
part that follows the namespace (<tt>ns-label</tt>).</t>
        </dd>
        <dt>invalid selector:</dt>
        <dd>
          <t>A selector whose value is not a <tt>selector-value</tt> (<xref target="syntax"/>).</t>
        </dd>
        <dt>policy token:</dt>
        <dd>
          <t>A label, whether a product token or a namespaced label, that a
consumer looks up regardless of whether it appears in the
identification string of any outbound request. Existing examples
describe how content will be used rather than whether it may be
fetched (<xref target="policy-tokens"/>).</t>
        </dd>
        <dt>proprietary policy token:</dt>
        <dd>
          <t>A policy token that is a product token documented by a single
consumer. Some service operators already include these in their
robots.txt files. The consumer that defines a proprietary policy
token <bcp14>SHOULD</bcp14> clearly and publicly describe how it interacts with
other mechanisms that consumer supports (<xref target="policy-tokens"/>).</t>
        </dd>
      </dl>
    </section>
    <section anchor="labels">
      <name>Labels and Namespaces</name>
      <t>This section updates Sections <xref target="ROBOTS" section="2.1" sectionFormat="bare"/>, <xref target="ROBOTS" section="2.2" sectionFormat="bare"/>, and <xref target="ROBOTS" section="2.2.1" sectionFormat="bare"/> of <xref target="ROBOTS"/>.</t>
      <t>A group is one or more selectors followed by one or more rules. A
selector carries either the value <tt>*</tt> or a label, and every label
belongs to a namespace. An unqualified label belongs to the <em>default
namespace</em> and is a product token exactly as <xref target="ROBOTS"/> describes; the
default namespace is defined by <xref target="ROBOTS"/> and nothing in this
document changes it. A qualified label belongs to the registered
namespace that qualifies it.</t>
      <section anchor="syntax">
        <name>Syntax</name>
        <t>The grammar of <xref section="2.2" sectionFormat="of" target="ROBOTS"/> uses the rule name
<tt>product-token</tt> for the whole value of a <tt>User-Agent:</tt> line, including
the value <tt>*</tt>, although its prose uses "product token" only for the
name of a crawler. This document brings the grammar into line with the
prose: the value of a selector is a wildcard, a product token, or a
namespaced label, and <tt>product-token</tt> names only the second of those.</t>
        <t>The <tt>startgroupline</tt> and <tt>product-token</tt> rules of <xref section="2.2" sectionFormat="of" target="ROBOTS"/> are replaced by the following rules; its <tt>identifier</tt> rule is
unchanged.</t>
        <sourcecode type="abnf"><![CDATA[
startgroupline   = *WS "user-agent" *WS ":" *WS
                   ( selector-value / invalid-value ) EOL

selector-value   = "*" / product-token / namespaced-label
invalid-value    = identifier  ; that is not a selector-value

product-token    = word *( "_" word )
word             = 1*( ALPHA / "-" )

namespaced-label = "__" namespace "_" ns-label
namespace        = ALPHA [ *( ALPHA / "-" ) ALPHA ]
ns-label         = ns-word *( "_" ns-word )
ns-word          = ALPHA [ *( ALPHA / "-" ) ALPHA ]
]]></sourcecode>
        <t>A selector whose value is a <tt>selector-value</tt> is valid: <tt>*</tt> makes it a
wildcard selector, a <tt>product-token</tt> is a product token in the sense
of <xref target="ROBOTS"/>, and a <tt>namespaced-label</tt> is a namespaced label in the
named namespace, whose <tt>ns-label</tt> part is the label. A selector
whose value is an <tt>invalid-value</tt> is an <em>invalid selector</em>; it begins
or continues a group exactly as any other <tt>startgroupline</tt> does, and
matches no label (<xref target="reserved"/>).</t>
        <t>The set of lines that <tt>startgroupline</tt> accepts is unchanged: every
<tt>selector-value</tt> is an <tt>identifier</tt> or <tt>*</tt>. The invalid values are the
<tt>identifier</tt>s that contain <tt>__</tt> other than as a well-formed
<tt>namespaced-label</tt>, or that begin or end with <tt>_</tt>. The grammar of
<xref target="ROBOTS"/> admitted these as product tokens and this document does
not; no product token in use is known to be among them
(<xref target="deployment"/>).</t>
        <t>No namespace and no label contains <tt>__</tt>, and a namespace contains no
<tt>_</tt> at all, so the leading <tt>__</tt> unambiguously introduces a
namespace and the first <tt>_</tt> after it unambiguously ends it. Namespaces
and labels, product tokens included, are compared case-insensitively.</t>
        <t>For reference, the complete formal syntax of <xref section="2.2" sectionFormat="of" target="ROBOTS"/>
as amended by this document is reproduced below.</t>
        <figure>
          <name>Formal syntax of RFC 9309 as amended</name>
          <sourcecode type="abnf"><![CDATA[
robotstxt = *(group / emptyline)
group = startgroupline                ; We start with a user-agent
                                      ; line
       *(startgroupline / emptyline)  ; ... and possibly more
                                      ; user-agent lines
       *(rule / emptyline)            ; followed by rules relevant
                                      ; for the preceding
                                      ; user-agent lines

; Changed by this document: the value was product-token, which
; was defined as identifier / "*".
startgroupline = *WS "user-agent" *WS ":" *WS
                 ( selector-value / invalid-value ) EOL

rule = *WS ("allow" / "disallow") *WS ":"
      *WS (path-pattern / empty-pattern) EOL

; parser implementors: define additional lines you need (for
; example, Sitemaps).

path-pattern = "/" *UTF8-char-noctl   ; valid URI path pattern
empty-pattern = *WS

identifier = 1*(%x2D / %x41-5A / %x5F / %x61-7A)

; Changed or added by this document. A startgroupline that
; carries an invalid-value is an invalid selector; it still
; delimits a group, and matches no label.
selector-value   = "*" / product-token / namespaced-label
invalid-value    = identifier  ; that is not a selector-value
product-token    = word *( "_" word )
word             = 1*( ALPHA / "-" )
namespaced-label = "__" namespace "_" ns-label
namespace        = ALPHA [ *( ALPHA / "-" ) ALPHA ]
ns-label         = ns-word *( "_" ns-word )
ns-word          = ALPHA [ *( ALPHA / "-" ) ALPHA ]

comment = "#" *(UTF8-char-noctl / WS / "#")
emptyline = EOL
EOL = *WS [comment] NL ; end-of-line may have
                       ; optional trailing comment
NL = %x0D / %x0A / %x0D.0A
WS = %x20 / %x09

; UTF8 derived from RFC 3629, but excluding control characters

UTF8-char-noctl = UTF8-1-noctl / UTF8-2 / UTF8-3 / UTF8-4
UTF8-1-noctl = %x21 / %x22 / %x24-7F ; excluding control, space, "#"
UTF8-2 = %xC2-DF UTF8-tail
UTF8-3 = %xE0 %xA0-BF UTF8-tail / %xE1-EC 2UTF8-tail /
         %xED %x80-9F UTF8-tail / %xEE-EF 2UTF8-tail
UTF8-4 = %xF0 %x90-BF 2UTF8-tail / %xF1-F3 3UTF8-tail /
         %xF4 %x80-8F 2UTF8-tail

UTF8-tail = %x80-BF
]]></sourcecode>
        </figure>
      </section>
      <section anchor="mixed">
        <name>Groups with Multiple Selectors</name>
        <t>A single group <bcp14>MAY</bcp14> have several selectors (<xref section="2.2" sectionFormat="of" target="ROBOTS"/>),
and those selectors <bcp14>MAY</bcp14> carry labels from the same or different
namespaces, including the default namespace (i.e., they may be product
tokens rather than namespaced labels).</t>
        <t>As in <xref target="ROBOTS"/>, selectors in a group are disjunctive; in other
words, the group matches a label if any one of its selectors does.
This is a consequence of the need to be backwards-compatible with
deployed software: a parser that does not implement this document
applies a group to the product tokens it names exactly as <xref target="ROBOTS"/>
specifies, whatever else the group's selectors carry. Accordingly, no
specification defining a namespace can alter whether a group matches a
product token or what its rules mean for one.</t>
        <t>A specification defining a namespace <bcp14>MAY</bcp14> describe other behavior among
its own labels, or between its labels and those of another namespace,
when they appear together in a group or across groups. A specification
that does so <bcp14>MUST</bcp14> specifically account for consumers that do not
implement this document, for consumers that implement only some of the
namespaces involved, and for the disjunctive reading that such
consumers will apply to whatever they do recognize, and <bcp14>MUST</bcp14> show that
the file means something acceptable to its author under each of those
readings. It <bcp14>SHOULD NOT</bcp14> make the meaning of its labels depend on which
product tokens share their group, since that would scope the namespace
by crawler through group membership and invite service operators to
add product tokens to a group, creating crawl rules they did not
intend.</t>
      </section>
      <section anchor="reserved">
        <name>Reserved Selector Values</name>
        <t>Every <tt>identifier</tt> that contains the sequence <tt>__</tt> at any position, or
that begins or ends with <tt>_</tt>, is reserved to this document and to the
namespaces registered under it. Such a value is not a product token;
it either parses as a <tt>namespaced-label</tt> or makes its selector an
invalid selector (<xref target="syntax"/>).</t>
        <t>The reservation covers <tt>__</tt> at any position, not only as a prefix,
because some deployed parsers match more flexibly than <xref target="ROBOTS"/>
specifies.  Specifically, they treat a selector as matching when the
value it carries is a prefix of, or a substring of, the crawler's
product token or its whole identification string. Were only the prefix
reserved, a crawler could name itself <tt>Foo__example_foo</tt>, and under
substring matching the group for the namespaced label <tt>__example_foo</tt>
would be applied to that crawler.  Reserving the sequence everywhere
makes accidental matches implausible without requiring any deployed
parser to change.</t>
        <t>The reservation cannot help where a parser matches in the other
direction, treating a selector as matching when the crawler's product
token is a prefix or a substring of the value the selector carries.
Under such a parser, a crawler named <tt>example</tt> or <tt>foo</tt> would match a
selector carrying <tt>__example_foo</tt>.  Because of substring matching, a
namespace name <bcp14>SHOULD</bcp14> be compared against a corpus of known or likely
product tokens before it is registered (<xref target="expert-guidance"/>), and so
<bcp14>SHOULD</bcp14> each label before it is defined in a namespace (<xref target="defining"/>).</t>
        <t>No label contains <tt>__</tt>, whichever namespace it is in. In particular, a
product token <bcp14>MUST NOT</bcp14> contain <tt>__</tt>, the label in a namespaced label
(its <tt>ns-label</tt> part) <bcp14>MUST NOT</bcp14> contain <tt>__</tt>, and a namespace <bcp14>MUST NOT</bcp14>
contain <tt>_</tt> at all. Using <tt>-</tt> as the word separator in both namespaces
and labels is <bcp14>RECOMMENDED</bcp14>.</t>
        <t>A crawler <bcp14>SHOULD NOT</bcp14> send an identification string that contains <tt>__</tt>.</t>
        <t>A consumer <bcp14>MUST NOT</bcp14> document a proprietary policy token that contains
<tt>__</tt> (<xref target="policy-tokens"/>).</t>
        <t>A consumer <bcp14>MUST</bcp14> treat an invalid selector as matching no label, and
<bcp14>MUST</bcp14> otherwise process it as it would any other selector; it still
begins or continues a group, and the rules that follow it belong to
that group.</t>
        <t>A consumer <bcp14>MUST</bcp14> likewise treat a selector carrying a well-formed
namespaced label as matching no label when it does not recognize the
namespace or does not implement it.</t>
        <t>Service operators <bcp14>MUST NOT</bcp14> publish robots.txt files that contain
invalid selectors.</t>
      </section>
    </section>
    <section anchor="defining">
      <name>Defining a Namespace</name>
      <t>The default namespace is defined by <xref target="ROBOTS"/> and is outside the
scope of this section: its labels are product tokens, the wildcard
fallback applies to them, and allowed and disallowed mean what
<xref section="2.2.2" sectionFormat="of" target="ROBOTS"/> says. Every other namespace identifies a
specification, recorded in the registry of <xref target="iana"/>, and every label
in it is defined by, and only by, that specification. Beyond the
syntax of <xref target="syntax"/> and the exact matching of <xref target="matching"/>, which
hold for every namespace, that specification decides the remaining
questions, including whether the wildcard fallback applies to its
labels. This section lists them.</t>
      <dl>
        <dt>Label syntax:</dt>
        <dd>
          <t>The specification <bcp14>MUST</bcp14> define the syntax of labels within its
namespace, within the <tt>ns-label</tt> rule of <xref target="syntax"/>, and <bcp14>MAY</bcp14>
establish a registry of labels. Because of substring matching, each
label <bcp14>SHOULD</bcp14> be compared against a corpus of known or likely product
tokens before it is defined or registered, and <bcp14>SHOULD</bcp14> neither be one
nor contain one (<xref target="reserved"/>).</t>
        </dd>
        <dt>Wildcard fallback:</dt>
        <dd>
          <t>The specification <bcp14>MUST</bcp14> state whether the wildcard fallback applies to
labels in its namespace (<xref target="matching"/>): always ("yes"), never ("no"),
or under conditions the specification sets out
("specification-defined"). Where it applies, it is the fallback of
<xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> and nothing more: a consumer that finds
no group matching the namespaced label obeys the group(s) with a
wildcard selector, exactly as a crawler whose product token matches
no group does, and a consumer that does find a matching group does
not consult wildcard groups at all. Where it does not apply, a
consumer that finds no matching group has been given no signal (see
"No matching selector" below). Nearly every robots.txt file published
today has a group with a wildcard selector, written with crawling in
mind and without knowledge of any namespace. A namespace whose labels
express something the authors of those groups cannot have intended
<bcp14>SHOULD</bcp14> specify that the wildcard fallback does not apply to its
labels, so that a file written without knowledge of the namespace
says nothing in it; the <tt>usage</tt> namespace anticipated in
<xref target="motivation"/> is expected to take this position. A namespace <bcp14>MAY</bcp14>
instead specify that the wildcard fallback does apply, where reading
existing wildcard groups under it is the intended effect; its
specification <bcp14>SHOULD</bcp14> then explain why that reading is safe for files
written before it existed. A namespace whose answer depends on the
label, on the content of the file, or on anything else <bcp14>MUST</bcp14> set out
those conditions completely, such that two consumers reading the
same file reach the same answer.</t>
        </dd>
        <dt>Allowed and disallowed:</dt>
        <dd>
          <t>The specification <bcp14>MUST</bcp14> define what is expressed when lookup finds a
path allowed, and when it finds a path disallowed, in the group(s)
that match a namespaced label in its namespace (<xref target="matching"/>).</t>
        </dd>
        <dt>No matching selector:</dt>
        <dd>
          <t>The specification <bcp14>MAY</bcp14> define what is expressed when no selector
matches such a namespaced label (<xref target="matching"/>).  If it does not,
then the robots.txt file expresses nothing in the context of that
specification.</t>
        </dd>
        <dt>No matching rule:</dt>
        <dd>
          <t>The specification <bcp14>MAY</bcp14> define what, if anything, is expressed when a
selector matches such a namespaced label but no rule in the matching
group(s) matches the path.  If it does not, then per <xref target="ROBOTS"/>, the
expression is equivalent to an <tt>Allow:</tt> rule.</t>
        </dd>
        <dt>Interaction with other labels:</dt>
        <dd>
          <t>The specification <bcp14>MAY</bcp14> describe behavior other than disjunction among
its own labels or between its labels and those of other namespaces,
within the limits of <xref target="mixed"/>: it <bcp14>MUST</bcp14> account for consumers that
do not implement this document or that implement only some of the
namespaces involved, it <bcp14>MUST NOT</bcp14> alter whether a group matches a
product token or what a group's rules mean for one, and it <bcp14>SHOULD
NOT</bcp14> make the meaning of its labels depend on which product tokens
share their group.</t>
        </dd>
        <dt>Relationship to rules for product tokens:</dt>
        <dd>
          <t>The specification <bcp14>SHOULD</bcp14> state how rules under its labels relate to
rules under a consumer's own product token(s). For a namespace used
for policy tokens, <xref target="policy-tokens"/> supplies that statement.</t>
        </dd>
      </dl>
      <t>This document registers no namespace for use. It reserves the
namespace <tt>example</tt> for documentation (<xref target="iana"/>).</t>
    </section>
    <section anchor="matching">
      <name>Matching Namespaced Labels</name>
      <t>This section updates <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>.</t>
      <t>To determine what has been expressed for a given path under a
namespaced label, a consumer looks up the path and label combination
as it would the combination of a path and a product token under
Sections <xref target="ROBOTS" section="2.2.1" sectionFormat="bare"/> and <xref target="ROBOTS" section="2.2.2" sectionFormat="bare"/> of <xref target="ROBOTS"/>, subject to the following.</t>
      <t>Consumers <bcp14>MUST</bcp14> match namespaced labels exactly, apart from case,
regardless of their matching behavior for product tokens.  Prefix
matches and substring matches <bcp14>MUST NOT</bcp14> be applied.</t>
      <t>If there is more than one group matching the label, the matching
groups' rules are combined as <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> specifies.</t>
      <t>If no group in the file matches the namespaced label, the namespace's
specification decides whether the wildcard fallback applies
(<xref target="defining"/>). Where it applies and the file has a wildcard selector,
the consumer obeys the group(s) with a wildcard selector as <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> specifies for a product token that matches no group,
and evaluates the path against their rules as described below. Where
it does not apply, or the file has no wildcard selector, no signal has
been provided, and the namespace's specification gives that outcome
its meaning (<xref target="defining"/>).</t>
      <t>A consumer <bcp14>MUST NOT</bcp14> consult a wildcard selector's group for a
namespaced label in any other circumstance. In particular, it <bcp14>MUST NOT</bcp14>
apply the wildcard fallback where the namespace's specification does
not provide for it, and it <bcp14>MUST NOT</bcp14> combine the rules of a wildcard
selector's group with those of a group that matches the label.</t>
      <t>If the lookup finds that the path is disallowed, or finds that it is
allowed, what has been expressed is likewise defined by the
namespace's specification. Path evaluation itself is exactly that of
<xref section="2.2.2" sectionFormat="of" target="ROBOTS"/>, including longest-match precedence, the
special characters of <xref section="2.2.3" sectionFormat="of" target="ROBOTS"/>, and the use of the
<tt>allow</tt> rule when an <tt>allow</tt> and a <tt>disallow</tt> rule are equivalent.</t>
      <t>Implementers are cautioned that general-purpose robots.txt parsers
apply the wildcard fallback to any label they find no other match for,
and that several match by prefix or substring. A consumer built on
such a parser <bcp14>MUST</bcp14> configure or wrap it to comply with this section.</t>
    </section>
    <section anchor="policy-tokens">
      <name>Policy Tokens</name>
      <t>This section updates <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/>.</t>
      <t>A policy token is a label, whether a product token or a namespaced
label, whose RFC 9309 signals a consumer looks up regardless of
whether it appears in the identification string of any outbound
request (<xref target="conventions"/>). The recommendation in <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> that a product token be a substring of the identification
string applies to a product token that names a crawler; it does not
apply to a policy token.</t>
      <t>Some crawler operators already publish policy tokens, e.g. ones that
control how content is used rather than which crawler can fetch it.
These vendor-specific policy tokens are called <em>proprietary policy
tokens</em>.</t>
      <t>Consumers <bcp14>SHOULD</bcp14> interpret a proprietary policy token as they would in
the absence of this document. A consumer that documents a proprietary
policy token <bcp14>SHOULD</bcp14> document whether the wildcard fallback applies to
it, how its rules relate to rules for that consumer's crawler product
tokens, and how they relate to any namespaces the consumer implements.</t>
      <section anchor="independence">
        <name>Independence from Crawler Rules</name>
        <t>Consumers <bcp14>MUST</bcp14> interpret the RFC 9309 signals being expressed based on
their own product token(s) exactly as they would in the absence of
this document. That is, <tt>ExampleBot</tt> still checks whether there are
rules for <tt>ExampleBot</tt>; if there are, they still have the meaning
described in <xref target="ROBOTS"/>.</t>
        <t>Signals expressed through product tokens and through namespaced labels
may coexist in the same robots.txt file, but they are independent and
orthogonal unless the specification governing a namespace says
otherwise (<xref target="defining"/>).</t>
      </section>
    </section>
    <section anchor="deployment">
      <name>Deployment Considerations</name>
      <t>A parser that implements only <xref target="ROBOTS"/> reads a namespaced label as
it would any product token, finds that it matches no crawler it is
asked about, and ignores the group as it would any group for a
product token it does not recognize; where the group also has selectors
carrying product tokens, it applies the group to those exactly as
written. No deployed file changes meaning, because no deployed file is
known to use a reserved value: a survey of widely fetched robots.txt
files conducted for this document found no selector value that
contains <tt>__</tt> or begins or ends with <tt>_</tt>.</t>
      <t>The constraints in <xref target="reserved"/> on crawler product tokens and
identification strings cost existing crawlers nothing for the same
reason: none is known to use <tt>__</tt> today. They exist to keep it that
way.</t>
      <t>Service operators, and tools that check robots.txt files for them,
<bcp14>SHOULD</bcp14> flag a namespaced label whose namespace is not registered, and
<bcp14>SHOULD</bcp14> flag an invalid selector (<xref target="syntax"/>), as these match nothing
for any conforming consumer.</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>The security considerations of <xref section="3" sectionFormat="of" target="ROBOTS"/> apply to this
mechanism.</t>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>This document does not introduce any new privacy considerations.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="rep-namespaces-registry">
        <name>REP Namespaces Registry</name>
        <t>IANA is requested to create a new registry titled "REP Namespaces" in
a new "Robots Exclusion Protocol (REP)" registry group.</t>
        <t>The registration policy is Specification Required (<xref section="4.6" sectionFormat="of" target="RFC8126"/>).</t>
        <t>Each registration consists of:</t>
        <dl>
          <dt>Namespace:</dt>
          <dd>
            <t>The <tt>namespace</tt> string, conforming to <xref target="syntax"/>. Namespaces are
compared case-insensitively and recorded in lowercase.</t>
          </dd>
          <dt>Label syntax:</dt>
          <dd>
            <t>The syntax of labels within this namespace, within the <tt>ns-label</tt>
rule of <xref target="syntax"/>, or a reference to the registry that enumerates
permitted labels.</t>
          </dd>
          <dt>Wildcard fallback:</dt>
          <dd>
            <t>One of "yes", "no", or "specification-defined": whether the wildcard
fallback of <xref section="2.2.1" sectionFormat="of" target="ROBOTS"/> applies to labels in this
namespace when no other group matches them (<xref target="defining"/>). For
"specification-defined", the referenced specification <bcp14>MUST</bcp14> be
consulted.</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>The specification that defines the namespace as <xref target="defining"/>
requires.</t>
          </dd>
          <dt>Change controller:</dt>
          <dd>
            <t>The party to whom IANA refers requests to change the registration.
For registrations made by IETF Stream documents, the IETF
(iesg@ietf.org); otherwise, the person or organization that made the
registration, or a successor it designates.</t>
          </dd>
        </dl>
        <t>The default namespace (<xref target="conventions"/>) has no name and no entry in
this registry.</t>
        <t>The registry initially contains one entry, which reserves the
namespace <tt>example</tt> for use in documentation and examples:</t>
        <dl>
          <dt>Namespace:</dt>
          <dd>
            <t>example</t>
          </dd>
          <dt>Label syntax:</dt>
          <dd>
            <t>Reserved; any <tt>ns-label</tt>.</t>
          </dd>
          <dt>Wildcard fallback:</dt>
          <dd>
            <t>Reserved; not applicable.</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>This document.</t>
          </dd>
          <dt>Change controller:</dt>
          <dd>
            <t>IETF (iesg@ietf.org)</t>
          </dd>
        </dl>
        <t>The <tt>example</tt> namespace has no defined labels and expresses nothing. A
consumer treats a selector that carries one of its labels as it does a
selector for any namespace it does not implement (<xref target="reserved"/>).</t>
        <t>The first registration of a namespace for use is expected to be
<tt>usage</tt>, made by the AI Preferences Working Group's attachment work
(<xref target="motivation"/>).</t>
        <section anchor="expert-guidance">
          <name>Guidance for Designated Experts</name>
          <t><xref section="4.6" sectionFormat="of" target="RFC8126"/> asks that a registry using Specification
Required give its designated experts clear review criteria. The
expert(s) review a request against the following:</t>
          <ul spacing="normal">
            <li>
              <t>The referenced specification is permanent and readily available,
and defines the namespace as <xref target="defining"/> requires, addressing each
item listed there rather than leaving any to implementers'
discretion.</t>
            </li>
            <li>
              <t>The namespace name conforms to the <tt>namespace</tt> rule of <xref target="syntax"/>,
is recorded in lowercase, and is neither identical to nor
confusingly similar to a registered namespace.</t>
            </li>
            <li>
              <t>The namespace name has been compared against a corpus of known or
likely product tokens, and neither is one nor contains one
(<xref target="reserved"/>).</t>
            </li>
            <li>
              <t>The label syntax stays within the <tt>ns-label</tt> rule of <xref target="syntax"/>.</t>
            </li>
            <li>
              <t>The "Wildcard fallback" field agrees with the specification, and,
for "specification-defined", the specification sets out the
conditions completely, such that two consumers reading the same
file reach the same answer (<xref target="defining"/>).</t>
            </li>
            <li>
              <t>Where the specification describes interaction with other labels, it
meets the requirements of <xref target="mixed"/>.</t>
            </li>
          </ul>
          <t>The expert(s) do not assess the merits of what a namespace's labels
express; that is for the review process of the specification itself.
They <bcp14>MAY</bcp14> ask for a different name where the requested one is likely
to mislead, and <bcp14>SHOULD</bcp14> decline a request whose specification does not
meet the criteria above, explaining which it fails.</t>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC5234">
          <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="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="ROBOTS">
          <front>
            <title>Robots Exclusion Protocol</title>
            <author fullname="M. Koster" initials="M." surname="Koster"/>
            <author fullname="G. Illyes" initials="G." surname="Illyes"/>
            <author fullname="H. Zeller" initials="H." surname="Zeller"/>
            <author fullname="L. Sassman" initials="L." surname="Sassman"/>
            <date month="September" year="2022"/>
            <abstract>
              <t>This document specifies and extends the "Robots Exclusion Protocol" method originally defined by Martijn Koster in 1994 for service owners to control how content served by their services may be accessed, if at all, by automatic clients known as crawlers. Specifically, it adds definition language for the protocol, instructions for handling errors, and instructions for caching.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9309"/>
          <seriesInfo name="DOI" value="10.17487/RFC9309"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="HTTP">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="AIPREF" target="https://datatracker.ietf.org/wg/aipref/about/">
          <front>
            <title>AI Preferences (aipref) Working Group Charter</title>
            <author>
              <organization>IETF</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="VOCAB" target="https://datatracker.ietf.org/doc/draft-ietf-aipref-vocab/">
          <front>
            <title>A Vocabulary For Expressing AI Usage Preferences</title>
            <author fullname="Paul Keller">
              <organization/>
            </author>
            <author fullname="Martin Thomson">
              <organization/>
            </author>
            <date year="2026" month="September" day="13"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-vocab-08"/>
        </reference>
        <reference anchor="ATTACH" target="https://datatracker.ietf.org/doc/draft-ietf-aipref-attach/">
          <front>
            <title>Associating AI Usage Preferences with Content in HTTP</title>
            <author fullname="Gary Illyes">
              <organization/>
            </author>
            <author fullname="Martin Thomson">
              <organization/>
            </author>
            <date year="2026" month="August" day="18"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-attach-05"/>
        </reference>
      </references>
    </references>
    <?line 830?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>This work was informed by conversations with many members of the AI
Preferences (AIPREF) Working Group and other members of the IETF
community.  Thank you all, and please reach out to the author so that
your name can be listed here.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA919e2/bSJbv//Up6ioYtG1ISpyke7rt6dl1J/Z0sHlt4kxj
djCIKKlkcU2RahZlRROkP8v9LPeT7XnVi6SUpHeBBW4DM7Ekslh16tQ5v/Pk
aDRSTd4U5kwPXmYrY9fZzFi9qGrdLI1+U02rxurLD7NiY/Oq1K/rqqlmVTFQ
2XRamzu47c3lax1uHahZ1pibqt6dadvM1byalfDjmZ7X2aIZ3ZqiMLtRbdaj
0t8zevBAbdZzuM+e6R8ePfhB2c10lVt8YrNbw83PLq+vFDzskbqns9pk8Nhf
zFRn5Vw/KxtTl6bR13VW2nVVNwN1a3bbqp6fKa1HuqY1jJsPDX2c1dm2MDX9
va6r+WbW6Ka6NSV94yc110U2NQVfVhX5bBddtbHZjYG7zcLUpoQVqGzTLKua
H7jYFAWvefBv5i4v9b/Rogfwo9ZVfZOV+T+zBtZ2pi/KZllX63xGv5lVlhdn
mml0O8pNs/hX+TCGFSpVVvUK7rwz+KA3V08enp7+IH9++/DRY/nz+9OH3/k/
/8jfvvrp1fXbM/yK6KvychGP9fP19Wv+9fT0AXy+ePb6zeXVGc3KscfFM9h9
v2J9lOVIgGP9S1Xf5uWN/ktdbdb6yTKrYUN4sU1W35jmTC+bZm3P7t+HLc6a
OpvdmnqMqxsDNe5vb+7zUPezabVp7tOdgZ743wjJJlyAn5FVzvQiK6yBz399
9eTip9Zc9V+rWTbdFFm901fAzJcf4AnAUDBPWMc72r9oNV8xXWDo+8zL+NWI
pz66w8fx1K2pc2ORwG76jkVHT/E+dxQ6t48efN+79sBPr7NNwdxU9/z6AigP
3Ha9rFa2KiNCPXzw8LvRgx9Gp49wa6+vL5783CKXtdUsB27YQx69zZulfgKn
0ZSNhmcgv/y3aZY1TTZb/n6i8f2jB99+hmp/QSZ4VhQ7OKdfTbXvR6ffKzUa
jXQ2tbgwOIbXy9xqWNNmheQQyYWnh4TX8LDkHGpbwRVZozJ9Yk1hZk1Vn+ij
yTugwejiBoY8m+giL80xUjqL5Je+oSM2y0r4Xw2LytQJSakTGlDDrKo1CpYM
Fqt/3WRFvshBkk3hSn3iRdvJWMNyjZN+iuQa3LrgUWwDYjWr5yho9dzYWZ1P
YZAl8ILOrN6UYWB6uD1X/G/7if6BNNK2zhtgHz15//5P/pc/v/8T3fvnyVg/
axQcUVPfAS2Rgtb8ukHuwzsmopFgeutNva6sGWoDE50WuV3C9UAlc5PD/uxg
GSpoliGpCLs2M5yX1ctq2xHxlqYHsnC2NHOchga5Uqm5WcAewFRMvcrLqqhu
djQJ8wGegwdlDYxDVIs2aJEXxo5h1/ka1f6JHpUjZwMHNzADIOjUwLCGZzo3
66LawfcwOJDCqvwGZL7pznnMPLnK5/PCKNCKcFx4O2H7lfr4kSX+p08gOfOb
vMzkYZlemdkSNJBdMTmBVaot/IaEz4HY1drUGXAkLLxSwCF3+RyJM1sCMUBt
Z3OgudFwEBaLfDZaZSWICjoGFqYKhIPb8ChWK3yimhU5/GbPkZMr2NRao16G
bcnDk7dmanM8QHDnPK/hPAhF8Yt11iytopnC7Tu9zUpcCRx1a6LL7nIYgkmY
bTPYqLpa8b3a36vm+VyXVQOk+8nMsg0MEJEpZ6arSjg5W1hzsRv5zfAnghmQ
iWJVhyp9JNBCAlryEnZgVq0MXjE1ACOARPAnfLXalDkCJ9iguwxEYYOMLCRr
4Ck3FndvC6J/rF8gR9jNbIkDEEupTTmHC0E4gT6H4UoLE6wJYwxxyTC7HW4B
rhCVqE51uTpifd/W5R8/8vefPo01ybwcjz+MzASBJQ/1dNPwZsKRKYAQvPrV
NL/Z5LAI3BGYz4JkIFD+GUi0+TznmU2727AlHgWWW8BiqkB5PHlzuBzpzgeG
pSzIXLxFhAuLXjk7SI4NScJwqmqDshomPARuuDOguphVHPMkX1YlbEdJewAS
84rOfrZa46otbKJa0aUkk4XN8Jiy7MI/EnTJggj3fl7hlrgxUOykV1qUnqjg
8g9weGGjUe/gpsCGMjuA/IeZzJpil4yCOoMlRRhhGJ5r8HCICsGDr6dFVt4q
vAs2BnBbeYNPwekzNoRVLAwyDh2Nmqk+z/Hgb4oGSHJR7mAiQHdScMDcivma
hRZpAQP03BElSb3gqZXtGdJpgBuAa4BpNyWKpRs4ECijW7eZla6Zt2ByBYtl
El6okgr8acdT5OXKTFYmK8Nu0CnC5/HYeEhAf4tSmVcwZI57S7IM+QMhD8BR
eHCxwzsr3MIdLG+Z3eViHrXFNVAHoFNtYFYIZZnfA3cPPf3piFpWH7TKWq+Q
ul0QYGEmyxx2t0lAB2+zxw/2ZAibJgJ1ukvGrDcFHvHJBf4MoyKFJk9hovKZ
nnKM26ndcCDwYetyYrcpyqRtXswBcswV/AZzbzJCJgnbDjXPM7ei+r3kZTmt
Z8uqsmxbqryBRy1oKnTV4O3Pr949f8oPCxzPm69BmJUNKPAZSTTNP3ql4Cw6
mH3J4ofRA+mzgT76+PGtIbWoH44fjk9xULchx+N9YC4SSTAg7AeI0yL/J5yv
qhw5anh6WSWYThvQCQTOckIlXwzPVArPLsouzsL7RYYDNgFLoAmw4BxlcG6V
iAUWg4n4gVVHa0LC3xoDcgt2wkMahScG/h0DK5y0IccJPv9zIE6pSyRAQH5w
DyMzgwKBzIhnFy8vhrL1xmEz2VrCxdENsCqHw7ZIQgFseGN4hjCkdWPmtbJg
SgPLzCxuP9/Eu33RgVKoY3Zs4Qh1s2K9hF8a3rWYanhirEJd1JLYR5Ns9M/J
UE8uRv+B/7zH/xtNjkVvevbychQMcMZrsLISFILZCvZBBc6HG1cjP4FoRMsD
JMy5aLhmCaC7vNkA+hrqogLBaZuRUyYGFoeKnanMEgcODcx3Q5AeCYpsF8NE
FKUlnVKSwkgqhtUWGI31KsKiGJ3ESJilnxOH2ayuLG2T8u4ZODQFbVVebggA
eRh8CE1mNmA3uBYk78ai2sOF0YgCkP1JJKSQdXcZVQIByGpTzEmSe2HHd6TH
ha5lTQ00mFU3JRz+MVqlKuAXkebf2OjxaJwtQAMUqGIABpU94F15eOFkdLBY
+Iyk7EX2GsrVuyqfWwB7JeywtWjWzjfrwh0eYN+2veGEMmJECysYoeIBciMD
4GH9lQESaL6qBqhFiGJtKtCDcGMlNnXPqEh+vk7hddMNSERAGYtmm9Ui+EXB
0v6thiRtRDC7o0k0FvWtbktQRl4/7tnEPEJ6eBtPxNxlxYbMjSK/NbS3DJxp
LLG3wYgBvsoKoDeA++TZgBcQNbPQVhXAg4BGgEj37gHihnPJRP54b+U/fELt
ATJutTLzHHFlaQxD1a6NibDfMq7EyTCwVgnejjQonVH8AcyB4MgC07bjeQT5
RP4vEeoowQlVZJFLR3BXBPiJyWbizwGYTz4hBCh5OSs2c7wp4aYxr/SmAgI6
PwFYcreEDSsWjKi5W0Yk2Tk5TIumreJpH5nxzXioByDhwBghloSnDo690QeP
fIs2ThZNnMAFIiu0fMiygZ/3Sg+SlarZVt7qLr32tQaEFmzZWL+qYblIXcJJ
wnkCKeBkV9tSpaIBZB7InRvkEzjqpkEj8GYo4ppRJs+RlbCbu2KOEuTKM4Rr
WaDjJNHTTVvnZR/NGoQq4BpcFTwB8Bds5g0uQrYk4SCYLzvFGCMCNyLjocBD
YDWfowuUAYfTsaj1Mz2h/ZkEth2yGPK8W8Od66qcC4TGKUd8iS4SC5jOm2sg
aSwpWz62aOcyfkXbHPewdKYUsao+iT3sJ6CW+POIxR+Yn3QKL+WWj/fk5k+C
3qzgu9wSS3gvOTlzyEbGCU/krnSZeOIUoRRyPYmlKfqajzxAiBx4CwCEwBaQ
Go0lqxdHrjY3wKUqBTLLbO4VrVBxsqgqQd/TrJ7gAcvxYP32228qgv36RHlw
ru+va5Q15r5KLhFK/FQ18bXWZDX6U5NL37+XZb+Hx8dXo9tzBhx/nyZAvLTI
wbInXhSjFjmwkvNxlmDtSZjCRFdTs2NtDzsBXMJkYhksN/AW0APG5HwEdqjn
Hf2pHHROEJ4T/5NkMROEqYkZp7wF14aIRVXdyskTllw7E5q9Yi4qxBfCr4iL
W/YNLgp2FM7UJFBvQjafWF54QsV0pcWjIHN+rnNGsAP5OKDhBuHmAUyIYhSI
4wNGSxeCpEr4DHjT6QoEuPrnbC6UBtVcVjGZhyJ5kvsFDhWgI+fw/Rz1vhE3
g+yXYpWcWyZ2gU4tQNsNqE58PIFO9/gLwYKRVQ0nMuxLy4q1hqykWOe3YRh6
VSrl2A4PM28E4z7bf4Si89F/FuAAxmeBYgu2/5C9f986ZnxefjbiguJDw0sg
jwYcnwAHSSeTa9lqUKbL2DJjx3t6lJxZdIj3UXoopHz+wcyJ7NeEq/DodU4U
W42AkPJ5cLghcyNoAqXkbCdyshNhrehVdDaO0BMEc2hPhySrWxfsD31JSGsS
UQoGXAM8Zdeu6EbvMWQ1OgU9VJLHwGyZ0c5401Eb+7nM56hAWO8wpcUHCOMA
IZzsZhPvHgaq7ljX8wY8pRPCnz/em4VfBcDdkl1Qw8EevHj39now5H/1y1f0
95vLf3/37M3lU/z77c8Xz5/7P5Rcwd6L8Fe488mrFy8uXz7lm+FbnXylBi8u
/jZghh68en397NXLi+cDtvLjc0Kgml1rSexAhfAM3PPTk9f/7/+ePgY8938k
NgygkD9gHBi9q0snx9jPvRSX6U7BRoH2oIATmmnZOgesjEcNOGkJGIjCP0Dc
k78jZf5xpv80na1PH/9ZvsAFJ186miVfEs2633RuZiL2fNXzGE/N5PsWpdP5
Xvwt+ezoHn35p38hX+ro9Pt/+bPquIgcoLj46eWV+FU4/t4C0A0hJ3bAqYvn
r3+O3B7E3hPn2DIAB8g0SHxVsacKSN8G12cK8wc0jtDs+NDwTyRT5eohBwpI
x0mgRay3jcTOlE5jjKg5SBaDZI2dHzNgDMt8iZEvDPAN5CEwBLCIqQcwS6eQ
e2bnedeGSAl5cbt2g6hCml1q1oJGRB2NBEY/dtvL1TW9xjDEE5mUIJoFurA8
MIF7JM7iALg8TilWZriUZ+JJBjhqUl/aecvupXtsx2ZGMke6QDAhWUEta/+Y
94eCV9kNCudGvFqabRSYWK9HtH+ee52fbHmIpzWL8mK8H1WestPsrh270WcZ
D45ZAOwaivzWExhhCdgACAqMXcxjB+zpg/Hp+Ft3K4trp6iIYXoc4AcduOd6
AjZH3ZBSwKsnzDCsKLLVCmRamwqpAzj2enu/LQzCWlf8/KQr9eQEHZwd5y9P
3A/Czo8Ixvqb9VE+NmDzThK0PzlGDu0/aN9kKG3qUYbXMjXILsNhBycDHvqb
eFILuHmazW5xUqjafLjiMC9wWM85izyqhonRchj1lmIXaAf54EohkzMA+IIj
4GGaJxKyQy8HHhm2uAl7qOA1Ez6PDiYMEj1XqEoPPveylH0e3YcBEpKIV41i
qkR07hxzc0fMyoodypcG7MoOVRSEF/wbrocuDwiPBb5hdIe77ES8uKxK/evG
WCK7zN9RlS/ABDC0IPmWBkTkMMVhG+uiYJ5YsOMkX0TItoPNTg9IHgZmPRXG
SW10nNISPGvkOCMEgnVVFAZgInuiYRtos9ynIVsjLOKa3RjEqhOhTNxZkVmb
z5xpH4nScz2tqy0HZb1lSExNUVoOr8EIOKViwXuBjO+80rhe2GRaLgVBYlZu
CYQMELULdcH825EuGIphJoz1KvLAxg7kA3G0VBqdouZLpAkjcTeUBBWywINo
Lf7npiQ/f8iKQLbivAh36Ynwyok/Y/mCPZsLAhbhGciocH9sDyjG4yyYKBTn
JxJFjLZO96bSb+izDpCSJxMe2+7ATvhAS7wkA5cnBf+rMDcBw6piTlexx/sM
5gwDdGJZSbCwZWZHY0axLjy8wW1DiR66HSCTO4LZT9zqrmJbkVOf3He1O2bI
0u6UiYXznFW0g7c+7ol+Dp1mJwHFw5JFHdBwouYjcx7Jk5jgzDMnPcs8cUkp
MlhP5hWH/eKQjj4k5jnmjkEleEYiZkLMDUl0GfkwAjWXWUi0ouhciPLGNLZO
e9pDUT4/jo2DfJ78AvzyJgT1tEQnU5/HUHvvHAK2mJV+Fx4Ka4ohURS71lHs
mk2BivRjUH8O1oJC2xGMahA5kdQ37CtlTouMimEHybKXtHtwSAPJ0cEEmWwX
JMSe4PCZHiRjD3CQQWdoZ4ceHmxABiJ+lAWF5Ip2sNO5fySm6AROO+laQhZ1
GnsVxoYdKNk0OioMKkcbRVeJ/W9AklqZy0TGZsfxxENAsrbY+4WzjRgpyLXo
CAtB+CR7csQJjZGI7KXS0MWpcGLVDXvUPHQ7IKDQqNf7wuvMoZMwzxH9MOH1
EXe79ThBh+wm8WQK4S6rwkRykwDkeQxXmLlZ8MAYJBcZA5JabDtWjyallVkg
CcXTtA8bM/BgQOzxzcT9PKIfJu1tiWMD0ZYMvaeyxwjsxg7F+5kx1GGfsXf2
giwC0Fig8xWo6MbN6QybrHZ5FyiT+gwvAiyomzfNtAIkDeMR5guJoB4TwRDO
Z0PJqC4Gt2VnGIdK4kSvaDKYlDPFSVDQyZBl1QqUiAxcY4weIzNd2sXf+LSU
NgXdEU4RZES6sX6LKWXdpFEXUnWoGOaO/sYyWLCdZFlk01Y2lmgDmlZrLXSg
cI7iEZoVsEHFLvg0ZpTwF5E4F88DwBNGZAjaiKY+FdYmIWvMuVtjQNzuofA9
hw3woVHVzMd7kmrSikuFpCJRPhax4xBVEMvcji6i4Jn3u1dfj1PBYlEdu1Yy
ulKjlE6LHBGOpnt4pyIoFp2ocX96Ugu3eUQT4RkBHG12iyIxkR3sNpFzXlRH
xqbAp53d5EKx4ktVXiu5MCxbdZ9ZRAA76iCqxPDkW5JZwAQivCRk/gVeiOBS
JEFOyrWtylxFFktw3j6yk7oek8gJqZK9hg0uJF4p4S1r+NktgMBGuDySVs7P
EkDUVvTTmhKUY6cLnLgqdVgoetxZxH00ZBynCPZ7Bw8NiU87KppZtk0r1ne0
hiZERlwCqgTO246j3pG8a6G9dypJnKrNuqBJSbyOjybl7OIA50TuxNsr4Q0V
J5r89ttvOpuWC5XOTGv9oz755S1ANu8LGvAXZ/SvFLUk/x3pVKvq+y4KJJ+P
9eWr58H7Jt/io9CxdF8nhIDPbdCh0uHozrBArc+9cmEtnz7II3UZn25HE1if
HOnB+wH/fazon/i/H/UpXEHOdJjUYDSAi1R7briI9zBIOLI4pAMq0Un2g/KA
f9ftseXTP5S7OZoIfBXP2H08Vu4v/RXjU0xxP1LqQUk5hfDy+RlJ8VV2K/ix
66DEw9Rm7B4pnEemkkpc3M7e7kGePts3zdMqveCYJ6CYVhUgI8PLPLL7Yn+s
ahOhhDMUc91Evj1pw84Tsgw4tuhSljHtMASb4+C/zxfriAS0YGjxKsQ6ZYmd
sON1MNSjDPWulJnNzLqRUgo5+2esdFXfHtOiI8GBLq2TCaMmt2y6mmMbSPb4
+oBsyHdBUd7IeJG4kA/0qu4WD7VzahM98ZMpxXUKlhjPJGi5JKd0vkIjaC4o
MLPttFm27ds2owKJcY6U7vAnxa6txlzBUgKi2ariooWVIr8AZqDiSLwpL6u4
Co0Tann/ksC3Y/CenOKyUhOMjFO9ks8lxEoXFO9Ez03J9S6UmqqjxN5IX3lP
CKcL0JCLhnF9ej8FXxCcBGCp8GbnUmmRUIA2aswap72CI4WO4MyaEcwfazPQ
11jsgBpYwuLz0ThwgzeAYS0lH4Vm7HIQrShkmhXmpIm+i/ePMql4ivgzoKlt
rNkY/SP4B5V2xEfxvjardbOjikfJNflRd1Rg8t+5/sXwJRJniMIkfdqw579z
OqXu4pOj1gPjSeHF4/GYTYzK2hyrqRBqf/GjWkEcGx5LOCB9WHxjjPEZi9Qg
Iu6yr1imA46cFo6Y8HfPWp3rJyyxOhsf47ptOOijuDQEbsefHGaHPyPAcB9x
x7gNfb4W+Hwp7CGy8+BHnJGFmMdnYw2O3WPkEXQhhmRHawrRlG7P3GcZ99zl
P/mMJ7DUzmTJvvINzhmriF214ZzhIyyKOQ/1ZW/zxqyytSV7Pn4sIJv7sPZ3
11ffj7AqYFRWoMdou1gXvHvzjNPO5A6VTJPXHOLHMFNCVH/48PApLOkPHx6f
jr69oL++vaJ/vjsd/fHiON56BOLzvsNPujvdP8rKOw+B1bK1HXn8nd+7c58f
BPfOTZGvED9nLo0tjqM7eT7+X0Oy/4NA9v8DHKuwlhUlBkz9HjDqUZtT72s4
Svfxx2PlpR5cjccH/ieH8u8yzD/0y+ewAaBsRtViRJeiFwwT9veJsXNfZEVZ
5ZhjrWU09RLH/8OHB8zrD5jRHzwdP7hQ8FD86eED/u4H5HicO/BfnVNeMDqh
sd700XcPf+AsNvPB5fpI9DQq1FGqvfIfabzRqScEfXzo/njk/niskutoVqc0
q4cP+Z/Hoz9eIVXajwd4wjgbqKtkdLz9ycPR0yseHEBNoeR5+NPlA/i/iwej
n6Lf6SGXp6PLJ/ph9GUgOPz6FP7v+wejHzq3XY4ur6Lb+FmP6VlX+Kwf6FkP
07uuTkdXj/SjPQ+7eswP+z4ZWIWrf+Tff7oiM+rjGfe1+HFw1cY0rkWDDhBm
8ImcN3/hwA2hiReboskx0fyt97V9vMfBVbLROJzOSOXFxd+4fMQihMeH+XuO
9medDBXDwTSTAMfivg4SNvTVIhS1wLz0fEHorUlaHISUs95YhEs7wTw/8SG3
Wz/EDudO6cox14LlaSVrnADxBQFuCW+HBE4nwNvhbS757Ya4x8pVoHN6igu/
SsyWtChbBJggsQX7144IDTc5luaT3zcU9EvGFhYc9SUs6z0Jy8olqfhUkSpO
6PWY3NXn9jo2lW9HMaSQGKWkAJ1NoE6rogxYAnTrbEap+DeYiQFWSRpSjQqG
IiMGLbyiocQeFyppUV91QicUpUP6M96kImrEkBXlTlzoL3guMrJ3wbO16ZNN
yF7D+l9MGfRGTYVXNFuDZl7js+PCIaEASysejYXRrlJP0ld9qC3iSXwmlyNy
cJZQSrwGFbYerDsK9/vfsVQILPZqUzZEhJlPJJSbDqW3D/tuCdeSf5Iq85mH
ozONiKgq7oxUUjgIHx0tKn/jI49RzQ2g6/AgCib58LPnsUZqGn09I4/OK8ZI
CaE1Vz0gcVmcoBQ1keeC239UtE1SHsi5Y1T57HysSqZnKVE8JO+Sn4rW4mKw
cth9ogQWO2GtPVsMrYNll+LjyENxX146lzzXMthZtTZplFIBUnUVBC7dSs6B
WU2BYst8zbGJ8g6Ad38vFMC87XNOYRGZxwyLgkgX44Pk8DDFue2IogI0KSh8
46qNnIrRf2Ufzsd73qukFKdhJO6f2JvT1yYH/RQlxsqs1KiCXRGcN1a8N9a7
b4Y6rn0icZYknpcu7z7mzigFhPce3RVSrNcK7iYUO8caMQlCSZosOaB6/IrU
g4BdmlEtQ1Z2IsztaPE1RW1wPSygZlinZ/cQB+dIxzCzUmeYfxgqVyXB3Tra
LR44J5AibYvCfCBnACnOPgk/1vptJEtECVMBWRz7yGzIqXRCTQklQzJpHiYJ
x4YjIkmzBHHpuNrFrmxHYnIAqTeOPda/YFWLD5zws1xXJgrKuGPEVYUUGZKU
gclVVaX1WSxeiENUmKZfaMACTr59ruBLbX0tI+lh4U08ES4wJSfLje8PBzlY
t1jEoJivQJoRDbAiWJQhimbYeI8XuPvHr5ucM6TL0EhGOdBQSTixj/GyEtlr
aYq13nLzLIc1/APZ484IScr/kS0bJ0s+wyJRmWpaUpRwSptLIk9NE2UrOjYb
q3d0pq0U39KU461nr36opkSPNJU28u7w+cjS6PNOnKVp+Z52fZiw6LXDIMPE
f0qsFrqEeEeny5BHVFivNxSsY/8wPBrrwYtdW4uE2qG0OwVIEvMBRH4zutnk
8wzYxpd82krJs0nNuVhxNI7zarUShVr1eeSR7nVAk74jNR0FuBuu3qLE+zWV
HGLB7bAD2zo5ijxmkoXcDdOoIwpLptGY432DtT3k7jIVLnNu8rF+R50WJ6OJ
NHBgN4gUXVNWMedLl30+blx0VLxDqNMxXwQlLDU0Kvek5KSKUpI0o3pRv8qg
63qyTeI8GTeYIl3SnxnSfoBI+q6LKznPzonFoSa6kWTCNqey/WpGVaFUbpw3
UQcLBsQ9XrOg7DuRr7QEyca5XRwzKyieUjFqoFt61oUHi2bXUWX+tKdxpZ5+
HN31s2DLIzvMQ9UUgpAt3LXVKBPjbQe8+a2WmqdODlKyvx2EYSnj52kwdHxg
BtCaP9ysAL4ySQVzezYNNmuj9TF0dbmhkj10llhEddvYdK1ZpD9Tp5yC0dtK
zm+oU47LlsnGQzNBpemxaZKKzXZ2vCc12ENU266EH9Ie1nMWjSGnhtpZ+Nzd
buoRJ/8m1IsqF6e7vmrmMSiUXcXsreJIlgOInvfJMA8MSBeFQmYXrwCkxMYX
TywKZPdUUnP5tKTxYCdfZAvlaj8SN01cYt2p3Il3DpOppd+jTjLKCmoehhsL
zPmc2xjRGl3dTzo3OgEShCCd72kjfCX1AZy83eoCIdsW6YluuqlYkhd/g9t9
X860K6drXPk5pY8K1tdf/T6F79GQ7lX5jqMoGuq0P69AnleG3mcVBQnLqO9Z
xTVpafT/l30FWD0bAfRpzBczgc+m53x4m4KLqPr+DI73FltZHQ12xg4AuXC1
09GgrOATZj06Wx3zoaQeupudb7FAE8QSFn4Mkp9GQrnBMVgKBGk5RbYgX1bu
Mzn8KqrF4XqEJFMPTaqzqPhMh9Iz2oF28VmvxfBVlWjD3h4QkqWSIqxQuuUn
4pNDOnMm1UQ1AVmYbriJBmlcN4UwLdd0QzCUp7DXdOTSGaY5zGl9XutpS2ov
C9PHJHkqqOPCW31kDbL14GV0i6PKgMP2sMcvObWWpV+7RNgVEM/plM0pKhMc
oxKW7yG5ayHHLYiQ5JymiZUARDJJLkHrC891YeY3xmVYxzmo0UHgHfOFI66R
RvBdUWkBeatsaEQp9HaGGnrx2UdDaxJRwAdACt/6z2q6P05uhyIY1xswY8LF
BOgsMvVbaVK6cS5r3kgRQLtjj6amWvk64/YcdO6iTlXU4Batm1kjZjM74rCa
W9whKUlZlrs+H19KBeFQtnfFB0gbImnwbV537iMnORz9tVksYKrnQslUQMnO
NEtKHQabPUf0IpNzflFUltmCK9ldAbajfNAGNDHs+tzlpqy0W1OLRxKzSTVX
AAhSr8QCl/x9V6CZY/SevOXIr7xt5NtnyY/5YSRZmQMjOewScain64b6fWbc
iyf4dYPPl1ljJZ7amoxSHyjimSNq74V7n4cIW4l3uyr8OQNzLJdAbw0Jm4yK
Q0J7G2nJJwBeruErwqOHoTabhbMrhRWnQW8m4SGdxwZ1R4TtWSKFJQ6tsAyt
W1AciZtGPCGdubWb3+hni1hcD7koSUBvS3r6Bgdporow1IfGdVlrM39rwa4q
9rOLHUqATXqwdJeeUU2jb/96eOUY/AZacRIzz9tNyRVro+aN67WRE7okYgKB
pZbEFpm/ZYLS2Av9cGCXUZClSop8cRbUaZdrPKirEeoWtlFYCB+ikcSpQqV8
iIX6gAseZwpcaZ2Grr4kctUylizV8AVgLektbINwCS/afHwi9wefsJKoOhSs
9HmbB0JOEdiPg07u6Wg0fy6AqLvVV1Lo50KZ3UCilJ66yBCM8fWxoZYdjOzb
jg4BV7wxBe01hXiaKmryl97ezyAOAxBgxwgZ3+60lp9ajU8xDNbjSwIw5E6C
6UOPsOvyVVqtxj3hNc8wckFZrHNtOZyoTImtBHlvQ0Pb3GlqHEptyzgfFp8B
j6MQXfzmhcjPEry8h9rikYPkhZNJL4O0kDKpj/e8nPxcZVRvKdQ1Nifj9zCI
6PbANkgxbh/GQJfUjmxBX81ITwmgk1Ha+yGlTQTHiGPXm+TNut+4jsXf206r
5/hHUvqFK3RlX4mPBVX/9D8N3auTQhLs0O6PP51NVpndRqO+M3xGyfWUQ4LZ
wEOVVjnyOfGaxIu/7tkAsf2aI0H+1KNLPLXdTeRnCwEalMv0qJo8YSvu25+x
Ed1jz/lSzUihMFT8Rg6WZDlPXQrpIesyhOFoGt5yE8HLUe5IR/XVjCbN9zpJ
F+zy+SJTXrVb9bUt6ChFvHDF9l37STVxueRec7en7UpMLHWAWPsb8UVJl+xL
VnH7XRudobhtkds4G71MhhPDmQSqx8St6pQS8MQeUzLYs9jxn+SBvJxjHtzc
+3snUuU4rwxAOTbopbyU3jYDfc59iZGQEX+o9cyit3SNYjLeiT/La5Ct2D8V
bdtWuCdSx0pszF5OY7Pr8KJdgYWjlLQ08Bo5Whl3rw6hgqTDjuos80AznU7j
Hi8XUqPCm5fERblNTAcy5PxV3O/e/7hPK8AYPlaRNtVUe2k01q/x8cLXhD99
VXxosI9cszjkMI89vvs7tJOrGp+exdmj3VYVj9KhHXeH5kBqQsQQ7yxjekDJ
8qUUcDl6ylUoTAOwxk1xUNH1SptlG5yCkfc0yIsQRvISptiscW8sOsSghNxd
7xhKhSAvmWv0JDptgWLOvxrCJVbyb/2vRkk6wWIzcoS6KolgM2Pjq2jymw21
tdXbOsM+r5rfwLOmF/80yyT4QsjmNeOwa3Ylf7yXwrDfhWhadfi5z4P84q4G
yl+O++ATW33v6M91OVB7uxx8WY8DJT0OUEzGHTVdEySM+mDS9dz3pu9SJBTR
Nj2tQb7oZSDK9a8LQZP+HrL8SgXn4z2PrVDl/XZZsi0YTERbyfmFu10OXECx
hdSpqV/lagCVSw6P+z1g+V+31QOaNT7DJpPu4hTWvKYKOqDyvKpHTlqlz5Xz
ii289ElP4wS+6iRBkmLghFcxHAiCy6sYBATnJSGRbGpDGm6rFqTtFOdfWm0d
kvYebj7ecvniIAlqMG72YEOhFNtkkc2XdHkAse9onaZDy0uEKCHS7KKBEg+0
1QkSC62nOcPvmW/cPpPXSUm3NP2GpvPxXh5d8akD76O3Yyx7zvfUcFcRp+em
Gf4/JbMi5OqzNeNgR7KROt1I1drIa/aVDdNGxdy+F7T67DYBwDVpFRVoHt91
jl4of5Fkw/FI5H6PjP+0tW3wDuGhFBqE1bukzt7yUv6p+xIOTIWfVeQB9rXP
6D5tueq41INmerghP1h6JFu7ETV+V0A7Sxpd+yrkeXTgJuYcuGpW6mDq3+lm
KfHAV7qSOomy2KMu6OTwiZIO+C1a/a9HSVJLWs0XUuAV2QHuBAkcs7doleHb
D9Iu3d5C6eSwxBC5Ve/blwdyHoFcGRB7lyPyCy9j8jko7VSJyNgKA5CpjUo0
nA8lkYKxflmFDFCyRlz7EGHT0FO7bF8J9PCFynhBFvJsKfvujLQbfKboOL9z
0Lf2iV5azCkqGCrYUPCGBVns31lQ06HIee3T+0T7hA7f5K7szQSWFEb/gphG
Sj5CnBtdby2JGZ20/p60OHHbhACQ77rr3N4u9xOPHmaNW8x4KdE9EBd6I/1o
/hRpJISx40HxV3q3TM59qtQ22/VlAQlkrirXdZhEVzcVSOazGrqEv0WR3fSd
GAZeSaJP2kiPs7mSUXrywOL05aGIZmucd4eJRG+cwsOC8LVCN9hN6MSEggKA
1abGPssdMWHll0+uQYFcOEsvTMyNR2mI3oEjaqPjWyYxMsa3U8x6HrvmHz61
PZEhactVybNSNVstt7RmRo/BN4Z1n0HOR86mT95Art9I0gmYM3gjJXkSVuXI
J2Xq43HEp/oEFSoZm3feZo44h68c7H2jrz6Cm44HYSznfL4O2U58JgTrwIze
JgriDWUZm6RX8uPxdwSR+X3erBLo5WrJiNGLBM+U8hN37uyQWT+RAzmMmQio
EbWMi2koHV33txOg4xSndqEhXuN1+zKS9uQckSj7XMqR+NXbSUdkE4W3AyVN
m2ox0k2JxwRtMgxVoBOZWlJINtKezJ1XXIZGiTT0kqIBPWxPOsxZL05FL35I
hDmcBhOsl5DrQ+dNJ3HpqClytyXyqvMykCsKY+6Z9FBoJcSb98WDp77nG771
g8Ipcnl/vCTp3pb4odj7GGaHG8pMb93LR03oQewDuNyzmIqYAEHTcaYZ+yNt
Qw5+vPcSK+W3tsbfYdYpNmve8Xtw32L+6irYJkwUec/8EWzJzb+6l5gfn4ek
XHnPLMyjIsMcfgah+M+ICPQUjrDFj/dFGzPM6SXPG3pFEdA2RInr/grOto0d
93F1fU3g13rHdpnPa693qRjC3+EAU12bBwaobOlm15X3i4JBG+7rl8aEyB8s
rQ7b8ki+70oHVwx1TrogHPp9hzNc7zzGwH9TCgK3+DO2Y/ZwGbFBa6elQVj3
fVGO7K03O/GqWwF97MAXLGB+ZVSUJ520iY+qXt2Q1uPfqJTC4YCkRKAnEbq3
ORF3nkm0B/lpOwHBdqoQSAFJNxr604P8n75E+tCbyPBVcfTGmighiUwcrLyW
Wgt6+lN3FuagZ7EUw9LbvtKiDKXaWlJ7LQmEcy96irJPN1SOkOhc5XUuhgGI
9PPwcCMPp+6SGt87iW/hBORk6jwj+Kn4ErSr5efMyaQ4/BEieHAcTsQztkfk
Yi4W6KesdJV3lO+DqvYuywt63ba8ReKLRKwXsEP36jdyGXB6LfYXoSxi7s6E
2VqRJwpfyexqnjCdLfIKf4N5BzmY5oZFLK+pVacjEMO3UYxhSI8ex/nYfjAR
mlRLSi5bGbOs4HcK1aygFrTDmNyQr4BUNTvzWq2qOXGwf8Y+dPBFecaYBpZk
GuvYc+Snygc7yh22kk7cPp88pSKSi9230h7Mv3ZDDDoCcyBv4aDXUtvQg7iV
pA/zHkrawUG80J8qLJru96ezsfmnD6SzdfwjJxJA7c7KNw71fV97c4LQHUDt
p03jsvbpvIjnJErHEQEaTrwk3mQo7614rWpJ4pHklzi6JA4nURGhn4yzfUWA
uEofcXS3hAO/gkWR5YuJSyDoJFLru0JIr39PlmD2iD0t9XD4bvTcFv4Fqs7r
ambUYSUIMnnXRSeASF5zJBz7QEUuouPnzgxdTiZXOlCrcjCuQYIhvhmNRtSg
Ac26i5lLfSWSq49nANWneFx/HAD7WjNw9iO9ahR7R+WlvJBsSvgFS3sF1tH2
rlBgSU23I+PFMxVrqSN+8+pxqq6i11K0bicsiKGMDQCnHb2JNytvqXMTNYSj
pmBASuv4lo4Diz2pj5f8XwX31CIfM4puiPzlV2v9F/CsE3GKiwAA

-->

</rfc>
