<?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 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ovalles-ai-terms-03" category="info" submissionType="IETF" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="AI Terms">AI Terms: Per-Use Terms, Payment and Receipts for Automated AI Access to Web Content</title>
    <seriesInfo name="Internet-Draft" value="draft-ovalles-ai-terms-03"/>
    <author fullname="Damien Ovalles">
      <organization>AIPayGen</organization>
      <address>
        <email>djautomd@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <area>Web and Internet Transport</area>
    <keyword>AI</keyword>
    <keyword>crawlers</keyword>
    <keyword>robots.txt</keyword>
    <keyword>well-known</keyword>
    <keyword>payment</keyword>
    <keyword>aipref</keyword>
    <abstract>
      <?line 91?>

<t>This document defines AI Terms: a JSON document published at the well-known URI <tt>/.well-known/ai-terms</tt> in which a website states, for each of four uses of its content by automated AI systems (search, answer, training and agent), whether the use is allowed, allowed for a price, or not allowed. Each use corresponds to one category of the IETF AI Preferences vocabulary, and the document defines how a site's terms are written, conservatively, as AI Preferences statements (the Content-Usage header field and robots.txt rule) for clients that read only those. AI Terms extends the AI Preferences work with what it leaves out: a price and a free allowance, a payment binding (HTTP 402, with x402 as the first), a purpose declaration by the client (the AI-Purpose header field), a description of a paid page that the payment depends on, and a receipt that records the use.</t>
    </abstract>
  </front>
  <middle>
    <?line 95?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The Robots Exclusion Protocol <xref target="RFC9309"/> lets a site say whether a named crawler may fetch a path. The IETF AI Preferences working group <xref target="AIPREF"/> defines a vocabulary for how content may be used by automated processing, including AI training <xref target="I-D.ietf-aipref-vocab"/>, and ways to attach those preferences to content <xref target="I-D.ietf-aipref-attach"/>. Its charter excludes technical enforcement, client authentication and auditing.</t>
      <t>Sites increasingly want to permit a use in exchange for payment rather than only allow or refuse it, and want a record of what was paid for. AI Terms builds on the AI Preferences vocabulary to add that. It is an extension of that work, not an alternative to it: every AI Terms use corresponds to one AI Preferences category (<xref target="aipref"/>), a site's terms can always be written as AI Preferences statements that grant no more than the terms (<xref target="signals"/>), and a site can keep stating its preferences the AI Preferences way. AI Terms adds five things:</t>
      <ol spacing="normal" type="1"><li>
          <t><strong>A price per use.</strong> A use can be <tt>allow</tt>, <tt>paid</tt> (with a price and unit) or <tt>deny</tt>, with an optional free allowance for verified clients.</t>
        </li>
        <li>
          <t><strong>A payment binding.</strong> For paid uses, the terms name a payment protocol and endpoint. This document uses HTTP 402 with the x402 protocol <xref target="X402"/> as the first binding.</t>
        </li>
        <li>
          <t><strong>Purpose declaration by the client.</strong> A request header field, <tt>AI-Purpose</tt>, in which the client states its intended use and so accepts that use's terms.</t>
        </li>
        <li>
          <t><strong>Description before payment.</strong> A quote for a paid page can describe the page, and a payment answering such a quote is settled only if the page delivered is the page described (<xref target="describe"/>).</t>
        </li>
        <li>
          <t><strong>Receipts.</strong> A paid response carries proof of payment and the declared purpose, giving both parties a record of licensed use.</t>
        </li>
      </ol>
      <t>Individual drafts cover neighbouring ground: <xref target="I-D.car-ai-txt-wellknown"/> declares usage policy and links to a licensing or pricing page, and <xref target="I-D.reilly-aipref-compliance"/> defines verifiable compliance records while excluding licensing, compensation and payment. <xref target="relation"/> describes how AI Terms relates to them and to Really Simple Licensing <xref target="RSL"/>.</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>
        <?line -18?>

</section>
      <section anchor="terminology">
        <name>Terminology</name>
        <dl>
          <dt>Site:</dt>
          <dd>
            <t>The origin <xref target="RFC6454"/> whose content the terms govern.</t>
          </dd>
          <dt>Client:</dt>
          <dd>
            <t>An automated AI system, or the software acting for it, that requests content from a site.</t>
          </dd>
          <dt>Settling party:</dt>
          <dd>
            <t>The party that settles a payment for content: the site itself, or a gateway acting for it.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="uses">
      <name>Uses</name>
      <t>This document defines four uses. Each access by an automated AI system is made for one of them, and the client declares which (<xref target="purpose"/>).</t>
      <dl>
        <dt>search:</dt>
        <dd>
          <t>Indexing content in order to show links to it, or excerpts of it, in AI-powered search results.</t>
        </dd>
        <dt>answer:</dt>
        <dd>
          <t>Using content, fetched in real time or taken from an index, as input to a generative AI model that answers a question asked by a person. A summary of the content shown in AI search results is an answer use.</t>
        </dd>
        <dt>training:</dt>
        <dd>
          <t>Collecting content to train or fine-tune machine-learning models.</t>
        </dd>
        <dt>agent:</dt>
        <dd>
          <t>An autonomous software agent reading content or invoking endpoints to complete a task.</t>
        </dd>
      </dl>
      <section anchor="aipref">
        <name>Relation to the AI Preferences Vocabulary</name>
        <t>Each use corresponds to one category of the AI Preferences vocabulary <xref target="I-D.ietf-aipref-vocab"/>. The correspondence is not exact, and the notes say where the two differ; <xref target="derive"/> writes terms as preferences so that the preferences never grant more than the terms. (Sections 3 and 4 of <xref target="I-D.ietf-aipref-vocab"/> do not yet have working group consensus; this mapping follows its -08 text and will follow its changes.)</t>
        <table>
          <name>Uses and AI Preferences categories</name>
          <thead>
            <tr>
              <th align="left">AI Terms use</th>
              <th align="left">AI Preferences category</th>
              <th align="left">Notes</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>training</tt></td>
              <td align="left">AI Training (<tt>train-ai</tt>)</td>
              <td align="left">AI Training covers generative models only; <tt>training</tt> also covers training models used for other tasks.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>answer</tt></td>
              <td align="left">AI Use (<tt>ai-use</tt>)</td>
              <td align="left">Includes summaries of the content shown in AI search results.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>agent</tt></td>
              <td align="left">AI Use (<tt>ai-use</tt>)</td>
              <td align="left">An agent that does not give the content to a generative AI model makes no AI Use; its terms still apply.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>search</tt></td>
              <td align="left">Search (<tt>search</tt>)</td>
              <td align="left">Search excludes generating summaries, which AI Terms counts as <tt>answer</tt>. Search covers every search application, not only AI-powered ones, and allows training models used only within the search application.</td>
            </tr>
          </tbody>
        </table>
        <t>The <tt>training</tt> use also corresponds to the cross-vendor robots.txt policy token <tt>__usage_ai-training</tt> proposed in <xref target="I-D.kelley-aipref-training-preference-signal"/>, which expresses the AI Training preference per path; <xref target="robots"/> writes it from a site's terms. AI Terms uses that token rather than defining one of its own.</t>
        <t>No use spans two categories. AI Use is split into <tt>answer</tt> and <tt>agent</tt> because sites commonly want to treat a person's live question differently from an autonomous agent's task. If the AI Preferences vocabulary gains categories for these, a later revision will map them. Extensions to that vocabulary are made by standards-track RFCs (<xref section="4.4" sectionFormat="of" target="I-D.ietf-aipref-vocab"/>), which this document is not; it only asks whether the split would be useful there.</t>
      </section>
    </section>
    <section anchor="the-ai-terms-document">
      <name>The AI Terms Document</name>
      <section anchor="location-and-format">
        <name>Location and Format</name>
        <t>A site publishes its terms as a JSON <xref target="RFC8259"/> object at the well-known URI <xref target="RFC8615"/> <tt>/.well-known/ai-terms</tt>, served with media type <tt>application/json</tt> and UTF-8 encoding. The document <bcp14>MAY</bcp14> instead be hosted elsewhere and referenced as described in <xref target="discovery"/>; such a reference <bcp14>MUST</bcp14> use HTTPS.</t>
      </section>
      <section anchor="members">
        <name>Members</name>
        <dl>
          <dt>ai_terms (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t>The version of this specification, <tt>"0.1"</tt> for this document.</t>
          </dd>
          <dt>site (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t>The origin the terms apply to, serialized as in <xref target="RFC6454"/>, for example <tt>https://example.com</tt>.</t>
          </dd>
          <dt>updated (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t>Date of the last change, <tt>YYYY-MM-DD</tt>.</t>
          </dd>
          <dt>uses (object, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t>One member for each of the four uses (<tt>search</tt>, <tt>answer</tt>, <tt>training</tt>, <tt>agent</tt>), each a Use Terms object (<xref target="use-terms"/>). A document that lacks one is invalid; a reader that meets one anyway applies <tt>default</tt> to the missing use.</t>
          </dd>
          <dt>default (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t><tt>allow</tt>, <tt>paid</tt> or <tt>deny</tt>. It applies to a request that declares no use (<xref target="purpose"/>), to a request whose client fails the site's identity checks (<xref target="identity"/>), and to a use for which no valid terms are found (<xref target="paths"/>). When <tt>default</tt> is <tt>paid</tt>, the price is the one the 402 response states (<xref target="payment"/>); since the terms then state no price to compare with, a client <bcp14>SHOULD NOT</bcp14> pay such a quote without a price ceiling of its own.</t>
          </dd>
          <dt>paths (array, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t>Overrides for parts of the site (<xref target="paths"/>).</t>
          </dd>
          <dt>identity (object, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t><tt>verify</tt>, an array of identity methods the site applies, and <tt>unverified</tt>, what applies to a client that fails them (<xref target="identity"/>).</t>
          </dd>
          <dt>purpose_header (string, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t><tt>"AI-Purpose"</tt> in this version.</t>
          </dd>
          <dt>payment (object, <bcp14>REQUIRED</bcp14> if a top-level use or <tt>default</tt> is <tt>paid</tt>, or a <tt>paths</tt> entry lists a use whose access is <tt>paid</tt> and carries no <tt>payment</tt> of its own):</dt>
          <dd>
            <t><tt>protocol</tt>, <tt>version</tt>, <tt>endpoint</tt> and protocol-specific members (<xref target="payment"/>).</t>
          </dd>
          <dt>preview (object, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t>Whether quotes for paid pages describe the page and whether delivery is checked against the description (<xref target="describe"/>).</t>
          </dd>
          <dt>receipts (string, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t>A description of the receipt a paid access returns.</t>
          </dd>
          <dt>report_only (boolean, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t><tt>true</tt> if the site currently measures automated access without charging and has not yet chosen terms. No AI Preferences statement is derived from such a document (<xref target="derive"/>).</t>
          </dd>
          <dt>contact (object, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t><tt>licensing</tt>, a URL for bulk or custom licensing.</t>
          </dd>
        </dl>
        <t>Unknown members <bcp14>MUST</bcp14> be ignored. A document is valid when it meets the requirements of this section. A JSON Schema <xref target="JSON-SCHEMA"/> for them is published as an aid <xref target="TOOLS"/>; it cannot express every rule (for example that a <tt>paid</tt> use needs a way to pay). A client <bcp14>SHOULD</bcp14> treat a document that is not valid, or whose <tt>ai_terms</tt> major version it does not implement, as absent; the one exception is a missing use, to which it applies <tt>default</tt>.</t>
      </section>
      <section anchor="use-terms">
        <name>Use Terms</name>
        <dl>
          <dt>access (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t><tt>allow</tt>, <tt>paid</tt> or <tt>deny</tt>.</t>
          </dd>
          <dt>price (object, <bcp14>REQUIRED</bcp14> when access is <tt>paid</tt>):</dt>
          <dd>
            <t><tt>amount</tt> (a decimal string greater than zero), <tt>currency</tt> (an <xref target="ISO4217"/> code; <tt>USD</tt> in this version) and <tt>per</tt>: <tt>page</tt> (each page delivered) or <tt>request</tt> (each request answered).</t>
          </dd>
          <dt>attribution (string, <bcp14>OPTIONAL</bcp14>):</dt>
          <dd>
            <t><tt>required</tt>, <tt>requested</tt> or <tt>none</tt>: whether the client is to cite and link the source when content is shown to a person.</t>
          </dd>
          <dt>free (object, <bcp14>OPTIONAL</bcp14>, on a use whose access is <tt>paid</tt> or <tt>deny</tt>):</dt>
          <dd>
            <t>A free allowance: <tt>requests</tt> (an integer from 1 to 1,000,000,000) and <tt>per</tt> (<tt>hour</tt> or <tt>day</tt>). See <xref target="allowance"/>.</t>
          </dd>
        </dl>
        <t>The terms state that content is not to be used for a use whose access is <tt>deny</tt>, and is used for a use whose access is <tt>paid</tt> only after payment, beyond any free allowance (<xref target="allowance"/>). A use whose value is not an object with a valid <tt>access</tt> is treated as not listed.</t>
      </section>
      <section anchor="allowance">
        <name>Free Allowance</name>
        <t>A use whose access is <tt>paid</tt> or <tt>deny</tt> <bcp14>MAY</bcp14> carry a <tt>free</tt> member, for example <tt>{ "requests": 100, "per": "day" }</tt>. The site answers up to <tt>requests</tt> requests for that use from each client whose identity it has verified (<xref target="identity"/>), in each UTC hour or UTC day, with the content, without payment; after that, the use's access applies for the rest of the window. Only requests answered with the content count toward the allowance. A client whose identity is not verified gets no allowance. Attribution applies to requests made within the allowance. On a use whose access is <tt>allow</tt>, <tt>free</tt> has no meaning and <bcp14>MUST</bcp14> be ignored.</t>
        <t>The allowance is a pacing signal: a client that reads steadily can stay within it, and only a burst meets the price or the refusal. A site counts requests per verified client identity, per use and per window. A site that counts approximately, for example on several servers that each keep their own count, <bcp14>MAY</bcp14> grant more than the stated allowance and <bcp14>SHOULD NOT</bcp14> grant less.</t>
      </section>
      <section anchor="paths">
        <name>Paths</name>
        <t>Each entry of <tt>paths</tt> has <tt>match</tt> (a path pattern starting with <tt>/</tt>), <tt>uses</tt> (Use Terms for one or more uses) and optionally <tt>payment</tt> (the payment for the prices it sets).</t>
        <t>In <tt>match</tt>, <tt>*</tt> matches any sequence of zero or more characters other than <tt>/</tt>, and every other character matches itself. A pattern matches a request when it matches the whole path component of the request target, without the query, after both are normalized as in <xref section="6.2.2" sectionFormat="of" target="RFC3986"/>: hexadecimal digits in percent-encodings are compared in upper case, percent-encoded unreserved characters are decoded, characters outside the set allowed in a path (for example non-ASCII characters) are percent-encoded as UTF-8, and dot-segments are removed from the request path (<xref section="5.2.4" sectionFormat="of" target="RFC3986"/>). An encoded slash (<tt>%2F</tt>) is not a segment separator. Patterns <bcp14>MUST NOT</bcp14> contain dot-segments.</t>
        <t>The terms for a use on a path are found for each use separately: among the entries that match the path and list that use with a valid Use Terms object, the one with the most characters in the normalized <tt>match</tt> other than <tt>*</tt> applies; if two have the same number, the first in the array applies. If no matching entry lists the use, the top-level <tt>uses</tt> member for that use applies, and if it is missing or invalid, <tt>default</tt> applies. Because <tt>*</tt> does not cross <tt>/</tt>, an entry applies at one depth; a subtree at several depths needs one entry per depth.</t>
        <t>An implementation <bcp14>MUST</bcp14> match patterns in time linear in the length of the pattern and the path (for example segment by segment, since <tt>*</tt> never crosses <tt>/</tt>). It <bcp14>MAY</bcp14> ignore patterns longer than 512 characters, after normalization, or containing more than 16 <tt>*</tt> characters.</t>
      </section>
      <section anchor="example">
        <name>Example</name>
        <sourcecode type="json"><![CDATA[
{
  "ai_terms": "0.1",
  "site": "https://example.com",
  "updated": "2026-11-18",
  "uses": {
    "search":   { "access": "allow", "attribution": "required" },
    "answer":   { "access": "allow", "attribution": "required" },
    "training": { "access": "paid",
                  "price": { "amount": "0.002", "currency": "USD",
                             "per": "page" },
                  "free": { "requests": 100, "per": "day" } },
    "agent":    { "access": "paid",
                  "price": { "amount": "0.002", "currency": "USD",
                             "per": "page" } }
  },
  "default": "paid",
  "identity": { "verify": ["published-ip-ranges"] },
  "purpose_header": "AI-Purpose",
  "payment": { "protocol": "x402", "version": 2,
               "endpoint": "https://pay.example/g/abc123def456",
               "network": "eip155:8453", "asset": "USDC" },
  "preview": { "shows": ["title", "description", "excerpt", "words"],
               "delivery": "per-quote",
               "described_quote":
                 "https://pay.example/g/abc123def456{+path}" }
}
]]></sourcecode>
        <t>The AI Preferences statement these terms imply for every path (<xref target="derive"/>) is <tt>train-ai=n</tt>: training is paid, so <tt>n</tt>; answer is allowed but agent is paid, so nothing is stated for AI Use; and Search is not stated, because a Search preference would also allow training for search, which these terms price.</t>
      </section>
    </section>
    <section anchor="discovery">
      <name>Discovery</name>
      <t>In addition to the well-known URI, a server <bcp14>MAY</bcp14> reference terms from any response with a <tt>Link</tt> header field <xref target="RFC8288"/> using the relation type <tt>ai-terms</tt>. The target <bcp14>MUST</bcp14> be an <tt>https</tt> URI and <bcp14>MAY</bcp14> be on another origin, for example a document that a rightsholder or a registry publishes for the site's content:</t>
      <artwork><![CDATA[
Link: <https://example.com/.well-known/ai-terms>; rel="ai-terms"
]]></artwork>
      <t>A server <bcp14>MUST</bcp14> include this link in every HTTP 402 (Payment Required) response <xref target="RFC9110"/> that it sends because of its AI Terms, so that a client refused for payment can find the terms it is being asked to pay under. A server <bcp14>SHOULD</bcp14> include it in other responses to automated clients, in particular successful ones, so that a client or archive that stores response header fields keeps the pointer with the content.</t>
      <t>A document's <tt>site</tt> names the origin whose content it covers, wherever the document is hosted. A client <bcp14>MUST</bcp14> ignore a document whose <tt>site</tt> is not the origin of the content it is deciding about: the origin of the well-known URI it fetched, of the robots.txt that named it, or of the response whose <tt>Link</tt> field referenced it. A document hosted on another origin (by a rightsholder, a registry or a provider that generates terms) thus applies only when the site's own responses or its robots.txt reference it, and only to that site's content.</t>
      <t>A document referenced by a <tt>Link</tt> field applies to the target resource of the request the response answers (its path and query), whatever the response's status. For that resource it replaces the site-wide document entirely: its <tt>paths</tt> are matched against the request path, and its <tt>default</tt>, <tt>identity</tt> and <tt>free</tt> members apply; a free allowance it states is counted separately. Only <tt>Link</tt> header fields of a final response count, not those of a 1xx response or link elements in content. A link with an <tt>anchor</tt> parameter is ignored, and if a response carries more than one <tt>ai-terms</tt> link, the client ignores them all. If the linked document cannot be retrieved or is not valid, the client applies the site-wide document; a site that depends on stricter linked terms enforces them at the server (<xref target="security"/>). Every redirect followed while retrieving a linked document <bcp14>MUST</bcp14> use <tt>https</tt>, and a linked document is cached by its URI.</t>
      <t>An <tt>AI-Terms</tt> record in the origin's robots.txt names a site-wide document, as the well-known URI does; if the well-known URI yields a valid document, that document is used and the record is ignored. Responses from a payment endpoint or a <tt>described_quote</tt> URI on another origin never establish terms: such a settling party may link the terms as a pointer, and the client checks the linked document against the terms it obtained for the site.</t>
      <t>A header field travels only with the response. Content copied to another host loses the link, and this document defines no way to name a work independently of the origin that serves it (see <xref target="open-issues"/>).</t>
      <t>A site <bcp14>SHOULD</bcp14> keep the terms document and <tt>/robots.txt</tt> free to fetch for every client, whatever its terms for other paths: they are how a client learns the rules and the price, and a client that is refused <tt>/robots.txt</tt> may treat the site as having no rules at all (<xref section="2.3.1.3" sectionFormat="of" target="RFC9309"/>).</t>
      <t>A site <bcp14>MAY</bcp14> add a line <tt>AI-Terms: &lt;URL&gt;</tt> to its robots.txt. <xref section="2.2.4" sectionFormat="of" target="RFC9309"/> allows records beyond the protocol's own; crawlers that do not interpret this one are unaffected by it.</t>
    </section>
    <section anchor="signals">
      <name>Writing AI Terms as AI Preferences</name>
      <t>Most automated clients do not read AI Terms. Some are starting to read AI Preferences: at least one operator documents that, since 2026-10-30, it has begun recognizing a "no AI training" preference based on the AI Preferences drafts <xref target="ANTHROPIC-CRAWL"/>. This section defines how a site's AI Terms are written as AI Preferences statements and as robots.txt rules. The statements are a conservative approximation: they never grant more than the terms, and they cannot express what the vocabulary has no category for, such as a price or training models that are not generative.</t>
      <section anchor="derive">
        <name>Deriving Preferences</name>
        <t>The AI Preferences statement implied by a site's terms for a path is derived from the access that applies to each use on that path (<xref target="paths"/>):</t>
        <dl>
          <dt>AI Training (<tt>train-ai</tt>):</dt>
          <dd>
            <t><tt>y</tt> if <tt>training</tt> is <tt>allow</tt>; <tt>n</tt> if it is <tt>paid</tt> or <tt>deny</tt>.</t>
          </dd>
          <dt>AI Use (<tt>ai-use</tt>):</dt>
          <dd>
            <t><tt>y</tt> if <tt>answer</tt> and <tt>agent</tt> are both <tt>allow</tt>; <tt>n</tt> if neither is <tt>allow</tt>; otherwise no preference is stated.</t>
          </dd>
          <dt>Search (<tt>search</tt>):</dt>
          <dd>
            <t><tt>y</tt> if <tt>search</tt> and <tt>training</tt> are both <tt>allow</tt>; otherwise no preference is stated. A Search preference of <tt>y</tt> also allows training models used only within the search application, and overrides the other categories (<xref section="4.3" sectionFormat="of" target="I-D.ietf-aipref-vocab"/>), so it is not stated where training is priced or refused. AI Terms governs AI-powered search only, and the Search category covers every search application, so a price or a refusal for AI-powered search is not a reason to state <tt>search=n</tt>.</t>
          </dd>
        </dl>
        <t>A <tt>paid</tt> use is written as <tt>n</tt> because an AI Preferences statement carries no price and no identity: a client that reads only the preference cannot pay, and must not make the use for free. A client that pays under the AI Terms is licensed by its payment (<xref target="payment"/>), not by the preference. A free allowance (<xref target="allowance"/>) does not change the derived value: it applies only to verified clients, and a preference applies to everyone.</t>
        <t>The statement is serialized as in <xref section="6" sectionFormat="of" target="I-D.ietf-aipref-vocab"/>, a Dictionary <xref target="RFC9651"/> with the categories in the order above, for example <tt>train-ai=n, ai-use=y</tt>. Because <tt>train-ai</tt> is always stated, the statement is never empty. No statement is derived from a document whose <tt>report_only</tt> is <tt>true</tt>: its operator has not chosen terms.</t>
        <t>The derivation uses the terms for each use, not <tt>default</tt>. A preference describes uses, and a client that acts on one is making a particular use, which is what declaring it would state (<xref target="purpose"/>); <tt>default</tt> governs clients that do not say what they are doing. A site whose <tt>default</tt> is more restrictive than its terms for a use, and which wants clients that read only preferences to meet that <tt>default</tt>, writes the more restrictive terms for that use.</t>
      </section>
      <section anchor="header">
        <name>The Content-Usage Header Field</name>
        <t>A server that publishes AI Terms <bcp14>SHOULD</bcp14> send the <tt>Content-Usage</tt> header field <xref target="I-D.ietf-aipref-attach"/> with the statement derived for the request path on successful responses to automated clients. The field describes the content of the message, and a 402 response carries a price, not the page, so a 402 response does not carry it for the page; the <tt>Link</tt> field (<xref target="discovery"/>) points to the terms instead. A server that already sends its own <tt>Content-Usage</tt> field for a response combines it with the derived statement as <xref section="5.1" sectionFormat="of" target="I-D.ietf-aipref-vocab"/> combines preferences: for each category, <tt>n</tt> in either gives <tt>n</tt>.</t>
        <t>For a response that carries an <tt>ai-terms</tt> link, the statement is derived from the linked document (<xref target="discovery"/>). robots.txt rules (<xref target="robots"/>) are derived from the site-wide document only; where the two differ, <xref target="both"/> makes the more restrictive apply.</t>
        <t>A successful response to a paid request carries the same statement as an unpaid one. The payment licenses the client that paid; the receipt (<xref target="receipts"/>), not the preference, records that. An archive that stores the paid response together with its header fields keeps the site's preference for everyone else.</t>
      </section>
      <section anchor="robots">
        <name>robots.txt Rules</name>
        <t>A site <bcp14>MAY</bcp14> add rules derived from its terms to its robots.txt:</t>
        <ol spacing="normal" type="1"><li>
            <t><tt>Content-Usage</tt> rules (<xref target="I-D.ietf-aipref-attach"/>): the statement derived from the top-level terms, and a rule for each <tt>paths</tt> entry with the entry's pattern as the rule's path, its characters that robots.txt reads specially (<tt>$</tt>, <tt>#</tt> and others outside the path set) percent-encoded. A rule's value is the derived statement where that is no looser than the terms on every path the rule reaches, and otherwise the most restrictive value the terms give any such path.</t>
          </li>
          <li>
            <t>A group for the product tokens whose operators document them as collecting content for AI training or as controlling its use for AI training (for example GPTBot, ClaudeBot, CCBot, Google-Extended and Applebot-Extended), with <tt>Disallow</tt> for the paths where <tt>training</tt> is <tt>paid</tt> or <tt>deny</tt>. Search crawlers and fetchers acting for a person are not in this group; their uses are not training.</t>
          </li>
          <li>
            <t>A group for the policy token <tt>__usage_ai-training</tt> (<xref target="I-D.kelley-aipref-training-preference-signal"/>), with <tt>Disallow</tt> for the paths where <tt>training</tt> is <tt>paid</tt> or <tt>deny</tt> and <tt>Allow</tt> where it is <tt>allow</tt>, including <tt>Allow: /</tt> when training is allowed everywhere, since a missing group states no preference. The group holds only these rules: it states a preference, not crawl rules, so a site's own <tt>Disallow</tt> rules and <tt>Content-Usage</tt> rules do not belong in it, and it is kept apart from groups that name crawlers. No group is written for a document whose <tt>report_only</tt> is <tt>true</tt>.</t>
          </li>
        </ol>
        <t>A robots.txt path pattern cannot express every AI Terms pattern exactly: in robots.txt, <tt>*</tt> also matches <tt>/</tt>, a pattern matches a prefix of the path and query, and the longest pattern wins rather than the one with the most literal characters. A site or generator that writes these rules <bcp14>MUST NOT</bcp14> write a rule that, for any path it applies to under <xref target="RFC9309"/> and <xref target="I-D.ietf-aipref-attach"/>, states a preference less restrictive than the terms (where <tt>n</tt> is more restrictive than no statement, and no statement more restrictive than <tt>y</tt>), or allows a training-only crawler a path where <tt>training</tt> is not <tt>allow</tt>, or states a preference in favour of training through the policy token on such a path. Where a rule cannot be exact, it errs toward the more restrictive value. Because readers differ on which of two rules of equal length applies, a generator <bcp14>MUST</bcp14> assume that the less restrictive one does. It <bcp14>MUST NOT</bcp14> copy into the training group a site's own <tt>Allow</tt> rule that reaches a path where <tt>training</tt> is not <tt>allow</tt>. The <tt>Content-Usage</tt> header field (<xref target="header"/>) is computed per path and is exact.</t>
        <t>Because a crawler named in a group of its own reads only that group (<xref section="2.2.1" sectionFormat="of" target="RFC9309"/>), the site's own rules and the <tt>Content-Usage</tt> rules need to appear in every group of the file to reach every crawler. No preference is implied for a disallowed path (<xref target="I-D.ietf-aipref-attach"/>), so a group that disallows every path needs no <tt>Content-Usage</tt> rules.</t>
        <t>The <tt>Disallow</tt> rules stop training-only crawlers before they see a 402. That is the intent for crawlers that cannot pay: they are kept from taking for free what the terms sell. A crawler that can pay finds the price in the AI Terms document, which the <tt>AI-Terms</tt> record points to; a site that expects such crawlers can leave their product tokens out of the group. A site that prefers every crawler to meet the 402 can omit these rules and keep the <tt>Content-Usage</tt> rules alone.</t>
        <t>An example for the terms in <xref target="example"/>, where <tt>training</tt> is paid site-wide, with a site's own <tt>Disallow: /admin</tt> kept in both groups (some training tokens left out for brevity):</t>
        <artwork><![CDATA[
User-agent: *
Disallow: /admin
Content-Usage: train-ai=n

User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: Google-Extended
User-agent: Applebot-Extended
Disallow: /admin
Disallow: /

User-agent: __usage_ai-training
Disallow: /

AI-Terms: https://example.com/.well-known/ai-terms
]]></artwork>
      </section>
      <section anchor="both">
        <name>Reading Both</name>
        <t>A client that reads a site's AI Terms and also its AI Preferences statements combines them as follows. Only statements attached by the site's origin are considered here: its robots.txt and the <tt>Content-Usage</tt> field of its own responses. A statement attached by anyone else, including one embedded in the content, is not overridden by a payment under the AI Terms, and is combined as <xref target="I-D.ietf-aipref-vocab"/> says.</t>
        <t>The access that applies under the AI Terms is the result, with three qualifications. First, an <tt>n</tt> from any statement attached by the site's origin, for the category of a use the AI Terms <tt>allow</tt>, denies that use, as <xref section="5.1" sectionFormat="of" target="I-D.ietf-aipref-vocab"/> requires. A robots.txt rule derived from terms can be stricter than the terms (<xref target="robots"/>), so a site that wants such uses honoured uses patterns robots.txt can express exactly. Second, an AI Preferences <tt>y</tt> never makes a <tt>paid</tt> or <tt>deny</tt> use allowed. Third, an <tt>n</tt> for the category of a use the AI Terms make <tt>paid</tt> is the derived statement: a payment made under the AI Terms is offered by the site as a specific arrangement in the sense of <xref section="5.2" sectionFormat="of" target="I-D.ietf-aipref-vocab"/>, which can take precedence over it, so it does not stop a client that pays from making the use. Likewise, content a client receives within a free allowance (<xref target="allowance"/>) may be used for that use. A site that does not want a use made by any client, paying or not, states <tt>deny</tt> with no <tt>free</tt> allowance.</t>
        <t>In the other direction, a site that publishes only AI Preferences statements has no AI Terms: <tt>y</tt> and <tt>n</tt> do not become <tt>allow</tt> and <tt>deny</tt> terms, and no price is implied.</t>
      </section>
    </section>
    <section anchor="purpose">
      <name>Declaring the Purpose: the AI-Purpose Header Field</name>
      <t><tt>AI-Purpose</tt> is a request header field. Its value is a Token <xref target="RFC9651"/> naming one of the uses defined in this document:</t>
      <artwork><![CDATA[
AI-Purpose = "search" / "answer" / "training" / "agent"
]]></artwork>
      <t>Senders <bcp14>MUST</bcp14> send one of these tokens, in lower case and with no parameters. A recipient ignores any other value, treating the request as if it carried no <tt>AI-Purpose</tt>; it <bcp14>MAY</bcp14> accept a value that differs only in case.</t>
      <t>An automated AI client <bcp14>SHOULD</bcp14> send <tt>AI-Purpose</tt> with each request to a site that publishes AI Terms. The field states the use the client intends, and the terms for that use apply to the request. A server <bcp14>MAY</bcp14> record the declaration and <bcp14>MAY</bcp14> echo it in the response. A request without the field gets the <tt>default</tt> terms.</t>
    </section>
    <section anchor="identity">
      <name>Identity</name>
      <t>A client's claimed identity (for example a user-agent product token) is not by itself evidence of who operates it. The <tt>identity.verify</tt> member lists the methods a site applies:</t>
      <dl>
        <dt>published-ip-ranges:</dt>
        <dd>
          <t>The request's source address is within the address ranges the claimed operator publishes for that client.</t>
        </dd>
        <dt>web-bot-auth:</dt>
        <dd>
          <t>The request carries an HTTP message signature verifiable with a key the claimed operator publishes, as defined in <xref target="I-D.ietf-webbotauth-httpsig-protocol"/>.</t>
        </dd>
      </dl>
      <t>A client fails a check when it claims an identity whose operator publishes the means to check it (address ranges or keys) and the check does not confirm it. The <tt>identity.unverified</tt> member says what applies to a client that fails every listed check:</t>
      <dl>
        <dt>treated-as-unidentified:</dt>
        <dd>
          <t>The <tt>default</tt> terms apply to it. This is the value when the member is absent or has any other value.</t>
        </dd>
        <dt>treated-as-claimed:</dt>
        <dd>
          <t>The terms for the use its claimed identity is documented for (for example <tt>training</tt> for a product token its operator documents as a training crawler) apply to it, or <tt>default</tt> when no use is documented; it earns no free allowance.</t>
        </dd>
      </dl>
      <t>In both cases a failed check never earns a free allowance. A client that claims no identity the site can check is not verified (it earns no free allowance) but has not failed, and the terms for its declared use apply. When <tt>identity</tt> is absent, the site verifies no client: none fails a check, and none earns a free allowance.</t>
    </section>
    <section anchor="payment">
      <name>Payment</name>
      <t><tt>payment.endpoint</tt> is an absolute <tt>https</tt> URI with no query or fragment. The content at path P (with its query) is paid for at the endpoint with any trailing <tt>/</tt> removed, followed by P; a site that answers 402 itself <bcp14>MAY</bcp14> give its own origin. A settling party <bcp14>MUST</bcp14> ensure that P cannot reach a path outside the site's: it normalizes P as in <xref target="paths"/> and then removes dot-segments (<xref section="5.2.4" sectionFormat="of" target="RFC3986"/>), and it does not decode an encoded slash or backslash into a separator.</t>
      <t>When the applicable access is <tt>paid</tt>, a server answers a request that carries no valid payment with status 402 and the payment requirements of the protocol named in <tt>payment.protocol</tt>. For the x402 binding <xref target="X402"/>, the requirements are carried in the <tt>PAYMENT-REQUIRED</tt> response header field; the client retries with a signed authorization in the <tt>PAYMENT-SIGNATURE</tt> request header field, and the content is returned only after the payment is verified. With the <tt>exact</tt> scheme on EVM networks, settlement transfers the stated amount from the client's wallet to the payee named in the payment requirements. The x402 binding settles in the asset named in <tt>payment.asset</tt>, a stablecoin denominated in the price's currency; a client compares a requirement's amount with the price by converting the asset's atomic units with its decimals, counting one unit of the asset as one unit of the currency, and <bcp14>SHOULD</bcp14> refuse a requirement that asks for more than the price. A client <bcp14>MUST</bcp14> check that a requirement's network and asset identify the asset the terms name, by network and contract address rather than by symbol, and <bcp14>MUST</bcp14> take the asset's decimals from its own knowledge of that asset, not from the quote.</t>
      <t>A client <bcp14>SHOULD</bcp14> pay only at an endpoint named by the site's well-known document, or by a linked document (<xref target="discovery"/>) whose endpoint the well-known document also names, in its own <tt>payment</tt> member or in a <tt>paths</tt> entry. A linked document that names any other endpoint, or a higher price than the well-known document for the same use, makes a claim that the site's operator has not confirmed in its site-wide terms; a client that pays under it does so only within its own limits. Terms that the site neither publishes nor references say nothing about whether it authorized anyone to sell its content (<xref target="security"/>).</t>
      <t>Other payment protocols can be bound by defining their <tt>payment</tt> members in a future revision.</t>
      <section anchor="describe">
        <name>Describing Content Before Payment</name>
        <t>A payment of this kind cannot be taken back, so a client needs to know what it is buying before it pays, and a site should not be paid for something else. This section defines how a quote describes a page and how the delivery is held to that description. It applies to quotes made by a settling party that is not the site: when a site settles its own payments, it holds every key the check depends on and could describe one page and deliver another, so such a site <bcp14>MUST NOT</bcp14> send <tt>delivery</tt> set to <tt>must-match</tt>. A client cannot itself tell whether the settling party is independent of the site; it relies on the terms it obtained from the site's origin naming that party (<xref target="payment"/>).</t>
        <t>A quote (the 402 response) for a paid page <bcp14>SHOULD</bcp14> describe the page. For the x402 binding <xref target="X402V2"/>, the description is carried as the extension named <tt>ai-terms</tt> in the quote's <tt>extensions</tt> object. As that protocol requires of every extension, its value has two members: <tt>info</tt>, the description, and <tt>schema</tt>, a JSON Schema for it. <tt>info</tt> is an object with these members:</t>
        <dl>
          <dt>title (string, at most 120 characters, or null):</dt>
          <dd>
            <t>The page's title.</t>
          </dd>
          <dt>description (string, at most 300 characters, or null):</dt>
          <dd>
            <t>The page's own summary, when it has one.</t>
          </dd>
          <dt>excerpt (string, at most 200 characters, or null):</dt>
          <dd>
            <t>The opening of the page's main text; null when the site's snippet controls forbid showing it.</t>
          </dd>
          <dt>words (integer):</dt>
          <dd>
            <t>The length of the page's main text in words.</t>
          </dd>
          <dt>delivery (string):</dt>
          <dd>
            <t><tt>must-match</tt> when the quote is held to this description, as defined below; <tt>not-checked</tt> otherwise.</t>
          </dd>
        </dl>
        <t>Unknown members <bcp14>MUST</bcp14> be ignored. A site's snippet controls (<tt>nosnippet</tt>, <tt>max-snippet</tt>) apply to the text shown.</t>
        <t>A quote that describes a page commits to it. The commitment is an integrity-protected value, bound to the request URI and limited in time, that travels with the payment, so that the delivery is checked against what that client was shown and not against a later reading of the page. For the x402 binding, the settling party places the commitment in the <tt>extra</tt> member of each payment requirement it offers; a version 2 client includes the requirement it accepted, <tt>extra</tt> included, in its payment payload, and the settling party reads the commitment from there. The name and format of the commitment are private to the settling party, and a client treats <tt>extra</tt> as opaque.</t>
        <t>A payment answering a described quote <bcp14>MUST NOT</bcp14> be settled unless the main text delivered is at least half as long as the main text described and the settling party's comparison accepts it. The comparison <bcp14>SHOULD</bcp14> reject content that shares less than half of the described main text; how it measures shared text is an implementation matter, and <xref target="impl"/> gives the method and measurements of one implementation. The main text is the page's main region when it marks one (for HTML, a single <tt>main</tt> or <tt>article</tt> element), otherwise its visible text. A page that is empty, much shorter, or mostly different text is not a delivery, whatever its HTTP status.</t>
        <t>A description taken after the payment request is received <bcp14>MUST NOT</bcp14> be used to judge that payment's delivery: a site that serves the same wrong content to every request would then match itself.</t>
        <t>A settling party that describes pages <bcp14>MUST NOT</bcp14> settle a payment for a page when the payment carries no valid commitment, unless the quote that payment answers was not held to a description (see below). It answers such a payment with a fresh described quote instead.</t>
        <t>The description in a quote is not itself authenticated: a site that builds its own quotes could claim <tt>must-match</tt> for a page the settling party never described. A client <bcp14>SHOULD</bcp14> therefore return the quote's <tt>ai-terms</tt> extension with its payment, as the x402 version 2 specification provides for extensions, and a settling party <bcp14>MUST NOT</bcp14> settle a payment that returns a description with <tt>delivery</tt> set to <tt>must-match</tt> unless the payment also carries a valid commitment. A client that does not return the extension is not protected against such a claim.</t>
        <t>The request made to describe a page and the request made to deliver it <bcp14>SHOULD</bcp14> be indistinguishable to the site, so that a site cannot show one page to be described and another to be paid for.</t>
        <t>A quote is held to a description only if it carries one, with <tt>delivery</tt> set to <tt>must-match</tt>. Any other quote is not checked: it is paid when the page is returned successfully, or answered with a fresh described quote. Such a quote <bcp14>SHOULD</bcp14> carry an <tt>ai-terms</tt> extension whose <tt>info</tt> has <tt>delivery</tt> set to <tt>not-checked</tt> and, when a described quote can be had elsewhere, a <tt>described_quote</tt> member saying where, in the form defined for the terms document below. A client that wants the check <bcp14>MUST</bcp14> treat a quote with no <tt>ai-terms</tt> extension, or one whose <tt>delivery</tt> is not <tt>must-match</tt>, as not checked, and asks for a described quote instead.</t>
        <t>The <tt>preview</tt> member of the terms document declares which of these a site does:</t>
        <dl>
          <dt>shows (array of strings):</dt>
          <dd>
            <t>What a description contains: any of <tt>title</tt>, <tt>description</tt>, <tt>excerpt</tt>, <tt>words</tt>.</t>
          </dd>
          <dt>delivery (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t><tt>must-match</tt>: every quote describes the page and is held to it. <tt>per-quote</tt>: each quote says which applies; quotes obtained from <tt>described_quote</tt> describe the page and are held to it, and any other quote is paid when the page is returned successfully. <tt>not-checked</tt>: pages are not described and deliveries are not compared.</t>
          </dd>
          <dt>described_quote (string, with <tt>per-quote</tt>):</dt>
          <dd>
            <t>Where a client asks for a described quote: a URI Template <xref target="RFC6570"/> with one variable, <tt>path</tt>, the path and query of the page starting with a slash, for example <tt>https://pay.example/g/abc123def456{+path}</tt>.</t>
          </dd>
        </dl>
        <t>This mechanism does not judge whether a page is good, accurate or worth its price. It holds the site to the page it showed.</t>
      </section>
    </section>
    <section anchor="receipts">
      <name>Receipts</name>
      <t>A successful paid response <bcp14>SHOULD</bcp14> carry:</t>
      <ul spacing="normal">
        <li>
          <t>the payment protocol's proof of settlement (for x402, the <tt>PAYMENT-RESPONSE</tt> header field identifying the settled transaction), and</t>
        </li>
        <li>
          <t>the <tt>AI-Purpose</tt> header field echoing the declared use.</t>
        </li>
      </ul>
      <t>Together with the request URI and time, this forms a record of licensed use. The site can show which automated client accessed which content, for which use, and what was paid; the client's operator can show that it licensed the content it used. A receipt shows that a payment was made for a request; it does not show that the content was later used only for the declared use. A future revision may define a signed receipt object independent of the payment protocol; the compliance records and transparency receipts of <xref target="I-D.reilly-aipref-compliance"/> are a candidate format to reuse rather than reinvent.</t>
    </section>
    <section anchor="relation">
      <name>Relation to Other Work</name>
      <dl>
        <dt>Robots Exclusion Protocol:</dt>
        <dd>
          <t>Unchanged. A disallowed path remains disallowed; AI Terms governs the use and price of content that is fetched. <xref target="robots"/> defines robots.txt rules derived from AI Terms.</t>
        </dd>
        <dt>AI Preferences <xref target="I-D.ietf-aipref-vocab"/> <xref target="I-D.ietf-aipref-attach"/>:</dt>
        <dd>
          <t>AI Terms is an extension of this work. Its uses refine the vocabulary's categories (<xref target="aipref"/>), its terms are written as AI Preferences statements and as the robots.txt training policy token of <xref target="I-D.kelley-aipref-training-preference-signal"/> (<xref target="signals"/>), and <xref target="both"/> says how a client combines the two. It adds what the working group's charter leaves out: a price and payment binding for uses a site permits for a fee, client-side purpose declaration, a check that a paid page is the page described, and receipts.</t>
        </dd>
        <dt>AI.TXT <xref target="I-D.car-ai-txt-wellknown"/>:</dt>
        <dd>
          <t>Declares usage policy per category and per agent, with a Training-Fee member that links to a pricing page. AI Terms adds a machine-actionable price and payment binding, client purpose declaration and receipts. If preferred, the Use Terms, payment and purpose members of this document could be defined as an extension of the ai.json format instead of a separate well-known URI; the author is open to that.</t>
        </dd>
        <dt>Verifiable Compliance Records:</dt>
        <dd>
          <t><xref target="I-D.reilly-aipref-compliance"/> records what a processor observed and decided, and excludes payment. AI Terms receipts record paid uses; the two can coexist, and a later revision may reuse its record format.</t>
        </dd>
        <dt>Really Simple Licensing <xref target="RSL"/>:</dt>
        <dd>
          <t>RSL 1.0 expresses licensing terms as an XML document discovered through a <tt>License:</tt> line in robots.txt, a <tt>Link</tt> header field with <tt>rel="license"</tt>, or markup. It defines payment types including per-crawl and per-use, a license server protocol based on OAuth 2.0, and can advertise x402 as an accepted payment method. RSL is the more complete licensing framework, has publisher backing, and can also state amounts and answer with 402. AI Terms is deliberately smaller: a lightweight x402 profile that works alongside RSL, with one JSON document of per-use access, no license server, a purpose declaration by the client and a receipt on each paid response. The two can be published side by side, and a site with an RSL license can point to it from <tt>contact.licensing</tt>. Where both are present and disagree, a client should follow the more restrictive, counting a refusal as more restrictive than a requirement for a license, and either as more restrictive than a price. A mapping between RSL payment types and AI Terms uses is future work, and the author would welcome doing it with the RSL community.</t>
        </dd>
        <dt>Web Bot Auth <xref target="I-D.ietf-webbotauth-httpsig-protocol"/>:</dt>
        <dd>
          <t>Used as an identity method (<xref target="identity"/>).</t>
        </dd>
        <dt>x402:</dt>
        <dd>
          <t>Used as the first payment binding (<xref target="payment"/>).</t>
        </dd>
      </dl>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>Terms are statements, not enforcement. Sites that require them to hold <bcp14>SHOULD</bcp14> enforce them at the server or edge, for example by answering 402 for paid uses and verifying identity before granting an allowance. A site whose <tt>default</tt> is <tt>allow</tt> gives every use to a client that declares none; a site that prices a use and wants that price paid sets <tt>default</tt> to <tt>paid</tt> or <tt>deny</tt>.</t>
      <dl>
        <dt>Integrity and origin of the terms:</dt>
        <dd>
          <t>Terms referenced from another origin <bcp14>MUST</bcp14> be fetched over HTTPS. A document's terms apply to the origin named in <tt>site</tt>, and only when retrieved for that origin (<xref target="discovery"/>). Anyone can publish a document naming any site and a payment endpoint of their own, and a gateway can answer 402 for content it does not own. A client <bcp14>SHOULD</bcp14> therefore pay only at an endpoint named by terms obtained as <xref target="discovery"/> describes (<xref target="payment"/>), and a settling party that sells content on a site's behalf <bcp14>SHOULD</bcp14> verify that the site's operator controls the site, for example by finding its terms, or another token it issued, served from the site's origin. Whoever can set header fields on a response can link terms for it, including a payment endpoint. A host that lets several parties set header fields under one origin <bcp14>SHOULD</bcp14> remove <tt>ai-terms</tt> links that its tenants set, unless it intends their terms, including their payment endpoint, to govern their content, as <xref target="discovery"/> provides; clients limit the exposure by paying only at endpoints the site-wide terms name (<xref target="payment"/>).</t>
        </dd>
        <dt>Spending:</dt>
        <dd>
          <t>A malicious or compromised terms document, or a quote, can state any price. Clients <bcp14>MUST</bcp14> apply their own spending limits per request and per period and <bcp14>MUST NOT</bcp14> pay without such limits. A client <bcp14>SHOULD</bcp14> compare the price in a 402 with the price in the terms and refuse a quote that asks for more.</t>
        </dd>
        <dt>Identity and allowances:</dt>
        <dd>
          <t>A client can misstate its identity or purpose. Identity verification limits the former. This protocol cannot detect a client that declares a cheaper use than the one it makes (for example <tt>search</tt> to get content it trains on); only a paid access leaves a receipt, and independent detection of copied content is the only check. A free allowance is counted per verified identity (<xref target="allowance"/>), so claiming a well-known client's name does not earn its allowance. Published address ranges change; a site <bcp14>SHOULD</bcp14> refresh them regularly, since a stale list can refuse a genuine client or accept one whose address was reassigned.</t>
        </dd>
        <dt>Derived signals:</dt>
        <dd>
          <t>A robots.txt rule or <tt>Content-Usage</tt> value that is looser than the terms would grant uses the site did not grant. <xref target="robots"/> therefore requires derived rules to be no less restrictive than the terms on any path they reach. Values copied from a remote source (for example a gateway's quote) into response header fields <bcp14>MUST</bcp14> be checked against the syntax of the field before being sent, so that a compromised source cannot inject other header fields.</t>
        </dd>
        <dt>Resource use:</dt>
        <dd>
          <t>A terms document is parsed by clients and its patterns are matched on every request. Clients <bcp14>SHOULD</bcp14> bound the size of the document they accept (for example 64 KiB) and the number of <tt>paths</tt> entries they consider. Pattern matching <bcp14>MUST NOT</bcp14> backtrack (<xref target="paths"/>): a pattern made of many <tt>*</tt> characters separated by single letters makes naive regular-expression matching take exponential time.</t>
        </dd>
        <dt>Delivery check:</dt>
        <dd>
          <t>The delivery check of <xref target="describe"/> compares text, not meaning. A site can describe and deliver the same poor page and be paid for it, and a delivered page may differ from the described one by up to about half of its main text. The check does not cover a quote that carries no description. A description is only as good as the settling party: the protection in <xref target="describe"/> against a forged description depends on the client returning the quote's extension with its payment. A client that needs the check <bcp14>MUST</bcp14> look for the description in the quote it pays (<xref target="describe"/>), not only at the terms document. The commitment <bcp14>MUST</bcp14> be integrity-protected with a key the site cannot obtain from the quote, bound to the request URI and short-lived; otherwise a site or a third party could substitute a description after the fact.</t>
        </dd>
        <dt>Disclosure:</dt>
        <dd>
          <t>A description discloses part of a paid page without payment. Sites decide how much through <tt>preview.shows</tt> and their snippet controls.</t>
        </dd>
        <dt>Caching and replay:</dt>
        <dd>
          <t>Clients <bcp14>SHOULD</bcp14> cache terms for a bounded time and respect HTTP caching header fields. A 402 response and a paid response <bcp14>MUST</bcp14> carry <tt>Cache-Control: private</tt> or <tt>no-store</tt>, so that a shared cache does not serve a price or a paid page to another client. A response served within a free allowance or after an identity check <bcp14>SHOULD</bcp14> also be marked <tt>private</tt>, and a response whose status depends on <tt>AI-Purpose</tt> <bcp14>SHOULD</bcp14> carry <tt>Vary: AI-Purpose</tt>. A shared cache in front of the server answers every client alike, so a site that needs per-client terms enforces them in front of such a cache. A settling party <bcp14>MUST NOT</bcp14> settle the same payment twice (with the <tt>exact</tt> scheme on EVM networks, authorizations carry a nonce for this) and <bcp14>SHOULD</bcp14> accept a payment only for the request URI it was quoted for.</t>
        </dd>
      </dl>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>The <tt>AI-Purpose</tt> header field reveals the client's intended use to the server; this is its purpose.</t>
      <t>Payment links a payer to the content it bought. With x402 on a public blockchain, the transfer itself (payer and payee addresses, amount and time) is public, while the URI bought is known to the site and the settling party; the site's records connect the two. Operators that consider this sensitive should use payment accounts dedicated to automated access.</t>
      <t>Verifying identity by address and counting allowances require the site to process client addresses and identities. Sites should keep only what counting needs, for no longer than the window it needs.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="well-known-uri">
        <name>Well-Known URI</name>
        <t>IANA is requested to register the following in the "Well-Known URIs" registry <xref target="RFC8615"/>:</t>
        <ul spacing="normal">
          <li>
            <t>URI Suffix: ai-terms</t>
          </li>
          <li>
            <t>Change Controller: IETF</t>
          </li>
          <li>
            <t>Specification Document(s): this document</t>
          </li>
          <li>
            <t>Status: provisional</t>
          </li>
          <li>
            <t>Related Information: none</t>
          </li>
        </ul>
      </section>
      <section anchor="link-relation-type">
        <name>Link Relation Type</name>
        <t>IANA is requested to register the following in the "Link Relation Types" registry <xref target="RFC8288"/>:</t>
        <ul spacing="normal">
          <li>
            <t>Relation Name: ai-terms</t>
          </li>
          <li>
            <t>Description: Refers to a document stating the terms under which automated AI systems may use the context resource.</t>
          </li>
          <li>
            <t>Reference: this document</t>
          </li>
        </ul>
      </section>
      <section anchor="http-field-name">
        <name>HTTP Field Name</name>
        <t>IANA is requested to register the following in the "Hypertext Transfer Protocol (HTTP) Field Name Registry" <xref target="RFC9110"/>:</t>
        <ul spacing="normal">
          <li>
            <t>Field Name: AI-Purpose</t>
          </li>
          <li>
            <t>Status: provisional</t>
          </li>
          <li>
            <t>Structured Type: Item</t>
          </li>
          <li>
            <t>Reference: this document</t>
          </li>
          <li>
            <t>Comments: a request header field naming the use the client intends</t>
          </li>
        </ul>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8615">
          <front>
            <title>Well-Known Uniform Resource Identifiers (URIs)</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="May" year="2019"/>
            <abstract>
              <t>This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes.</t>
              <t>In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space. It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8615"/>
          <seriesInfo name="DOI" value="10.17487/RFC8615"/>
        </reference>
        <reference anchor="RFC8288">
          <front>
            <title>Web Linking</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="October" year="2017"/>
            <abstract>
              <t>This specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types").</t>
              <t>It also defines the serialisation of such links in HTTP headers with the Link header field.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8288"/>
          <seriesInfo name="DOI" value="10.17487/RFC8288"/>
        </reference>
        <reference anchor="RFC9110">
          <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="RFC9309">
          <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>
        <reference anchor="RFC8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="RFC6570">
          <front>
            <title>URI Template</title>
            <author fullname="J. Gregorio" initials="J." surname="Gregorio"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="M. Hadley" initials="M." surname="Hadley"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="D. Orchard" initials="D." surname="Orchard"/>
            <date month="March" year="2012"/>
            <abstract>
              <t>A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI reference, along with guidelines for the use of URI Templates on the Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6570"/>
          <seriesInfo name="DOI" value="10.17487/RFC6570"/>
        </reference>
        <reference anchor="RFC9651">
          <front>
            <title>Structured Field Values for HTTP</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="P-H. Kamp" surname="P-H. Kamp"/>
            <date month="September" year="2024"/>
            <abstract>
              <t>This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields.</t>
              <t>This document obsoletes RFC 8941.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9651"/>
          <seriesInfo name="DOI" value="10.17487/RFC9651"/>
        </reference>
        <reference anchor="RFC3986">
          <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="RFC6454">
          <front>
            <title>The Web Origin Concept</title>
            <author fullname="A. Barth" initials="A." surname="Barth"/>
            <date month="December" year="2011"/>
            <abstract>
              <t>This document defines the concept of an "origin", which is often used as the scope of authority or privilege by user agents. Typically, user agents isolate content retrieved from different origins to prevent malicious web site operators from interfering with the operation of benign web sites. In addition to outlining the principles that underlie the concept of origin, this document details how to determine the origin of a URI and how to serialize an origin into a string. It also defines an HTTP header field, named "Origin", that indicates which origins are associated with an HTTP request. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6454"/>
          <seriesInfo name="DOI" value="10.17487/RFC6454"/>
        </reference>
        <reference anchor="X402V2" target="https://github.com/coinbase/x402/blob/main/specs/x402-specification-v2.md">
          <front>
            <title>x402 protocol specification, version 2</title>
            <author>
              <organization>x402 Foundation</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="I-D.ietf-aipref-vocab">
          <front>
            <title>A Vocabulary For Expressing AI Usage Preferences</title>
            <author fullname="Paul Keller" initials="P." surname="Keller">
              <organization>Open Future</organization>
            </author>
            <author fullname="Martin Thomson" initials="M." surname="Thomson">
              <organization>Mozilla</organization>
            </author>
            <date day="13" month="September" year="2026"/>
            <abstract>
              <t>   This document defines a vocabulary for expressing preferences
   regarding how digital assets are used by automated processing
   systems.  This vocabulary allows for the declaration of restrictions
   or permissions for use of digital assets by such systems.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-vocab-08"/>
        </reference>
        <reference anchor="I-D.ietf-aipref-attach">
          <front>
            <title>Associating AI Usage Preferences with Content in HTTP</title>
            <author fullname="Gary Illyes" initials="G." surname="Illyes">
              <organization>Google</organization>
            </author>
            <author fullname="Martin Thomson" initials="M." surname="Thomson">
              <organization>Mozilla</organization>
            </author>
            <date day="18" month="August" year="2026"/>
            <abstract>
              <t>   Methods are defined for associating usage preferences with content
   that is obtained using the HTTP protocol.  This document defines
   attachment methods using the Robots Exclusion Protocol and HTTP
   header fields.

   This document updates RFC 9309 to allow for the inclusion of usage
   preferences.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-attach-05"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="X402" target="https://www.x402.org">
          <front>
            <title>x402: an open payment protocol over HTTP 402</title>
            <author>
              <organization>x402 Foundation</organization>
            </author>
            <date>n.d.</date>
          </front>
        </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>n.d.</date>
          </front>
        </reference>
        <reference anchor="I-D.car-ai-txt-wellknown">
          <front>
            <title>AI.TXT: A Declaration File for AI Usage Preferences, Licensing, and Policy</title>
            <author fullname="Kayla Cardillo" initials="K." surname="Cardillo">
              <organization>Independent</organization>
            </author>
            <date day="12" month="June" year="2026"/>
            <abstract>
              <t>   This document requests registration of two Well-Known URIs under the
   "/.well-known/" path: "ai.txt" and "ai.json".  These URIs define a
   structured, machine-readable file in which a site operator can
   declare AI usage preferences (training, scraping, indexing, caching),
   licensing terms, required attribution, and per-agent rules.

   "ai.txt" is positioned as a structured attachment surface for AI
   usage preferences in addition to robots.txt and HTTP-header carriage
   proposed by the IETF AIPREF working group.  As the AIPREF vocabulary
   stabilizes, "ai.txt" can carry those preferences in a typed, single-
   file form alongside the broader licensing, attribution, and policy
   declarations defined in this document.

   This format is complementary to "robots.txt" [ROBOTS].  Where
   "robots.txt" can block crawling entirely, "ai.txt" expresses nuanced
   policies such as "you may crawl but not train on this content" -- a
   distinction that "robots.txt" alone cannot express.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-car-ai-txt-wellknown-00"/>
        </reference>
        <reference anchor="I-D.kelley-aipref-training-preference-signal">
          <front>
            <title>Machine-Readable Training Preference Signal</title>
            <author fullname="Kevin Kelley" initials="K." surname="Kelley">
              <organization>Anthropic</organization>
            </author>
            <date day="16" month="November" year="2026"/>
            <abstract>
              <t>   This document describes how a service operator binds usage
   preferences (e.g., "no AI training") to paths by writing ordinary
   robots.txt groups keyed by a per-purpose policy token in the User-
   Agent line.  It introduces no new directive names and no new grammar:
   the path language, longest-match precedence, and group structure of
   robots.txt are not changed.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-kelley-aipref-training-preference-signal-01"/>
        </reference>
        <reference anchor="I-D.reilly-aipref-compliance">
          <front>
            <title>Verifiable Compliance Records for AI Usage Preferences</title>
            <author fullname="Lawrence John Reilly Jr" initials="L. J. R." surname="Reilly">
              <organization>Independent</organization>
            </author>
            <date day="1" month="August" year="2026"/>
            <abstract>
              <t>   Work in the AI Preferences (AIPREF) Working Group defines a
   vocabulary for expressing preferences about how digital assets may be
   used by automated processing systems, together with mechanisms for
   attaching those preferences to content.  Neither component provides a
   way for a processing entity to demonstrate that it observed an
   expressed preference, nor for a publisher or auditor to verify such a
   demonstration after the fact.

   This document defines the AI Usage Compliance Record (AUCR), a
   structure that binds a retrieved asset, the preference expression in
   force at the moment of retrieval, and the usage category the
   processing entity assigned to that asset.  It defines an aggregation
   scheme that allows a processing entity to attest to very large
   numbers of records with a single signature, a proof mechanism that
   allows an individual publisher to audit only the records concerning
   its own assets, and a discovery mechanism for locating attestations
   and verification keys.  The mechanism is deliberately confined to
   evidence: it makes claims of compliance falsifiable and non-
   repudiable, and takes no position on the legal effect of any
   preference or any record.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-reilly-aipref-compliance-00"/>
        </reference>
        <reference anchor="I-D.ietf-webbotauth-httpsig-protocol">
          <front>
            <title>HTTP Message Signatures for automated traffic</title>
            <author fullname="Thibault Meunier" initials="T." surname="Meunier">
              <organization>Cloudflare</organization>
            </author>
            <author fullname="Sandor Major" initials="S." surname="Major">
              <organization>Google</organization>
            </author>
            <date day="29" month="October" year="2026"/>
            <abstract>
              <t>   This document describes a protocol for identifying automated traffic
   using [HTTP-MESSAGE-SIGNATURES].  The goal is to allow automated HTTP
   clients to cryptographically sign outbound requests, allowing HTTP
   servers to verify their identity with confidence.

   It defines the Signature-Agent header field for in-band key
   discovery, a key directory format based on JWKS, and a well-known URI
   at which that directory is served.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-webbotauth-httpsig-protocol-01"/>
        </reference>
        <reference anchor="RFC7942">
          <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="ISO4217">
          <front>
            <title>Codes for the representation of currencies</title>
            <author>
              <organization>International Organization for Standardization</organization>
            </author>
            <date>n.d.</date>
          </front>
          <seriesInfo name="ISO" value="4217:2015"/>
        </reference>
        <reference anchor="JSON-SCHEMA" target="https://json-schema.org/draft/2020-12/json-schema-core">
          <front>
            <title>JSON Schema: A Media Type for Describing JSON Documents</title>
            <author>
              <organization>JSON Schema</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="RSL" target="https://rslstandard.org/rsl">
          <front>
            <title>Really Simple Licensing (RSL) 1.0 Specification</title>
            <author>
              <organization>RSL Collective</organization>
            </author>
            <date year="2025" month="December" day="10"/>
          </front>
        </reference>
        <reference anchor="ANTHROPIC-CRAWL" target="https://support.claude.com/en/articles/8896518">
          <front>
            <title>Does Anthropic crawl data from the web, and how can site owners block the crawler?</title>
            <author>
              <organization>Anthropic</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="TOOLS" target="https://github.com/Damien829/pay-per-crawl">
          <front>
            <title>AI Terms JSON Schema, test vectors, readers and site integrations</title>
            <author>
              <organization>AIPayGen</organization>
            </author>
            <date year="2026" month="November"/>
          </front>
        </reference>
        <reference anchor="REFIMPL" target="https://aipaygen.com/ai-terms">
          <front>
            <title>AI Terms reference implementation</title>
            <author>
              <organization>AIPayGen</organization>
            </author>
            <date year="2026" month="November"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 576?>

<section anchor="impl">
      <name>Implementation Status</name>
      <t>Note to the RFC Editor: please remove this section before publication.</t>
      <t>This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in <xref target="RFC7942"/>. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.</t>
      <section anchor="aipaygen-gateway-and-site-integrations">
        <name>AIPayGen gateway and site integrations</name>
        <dl>
          <dt>Organization:</dt>
          <dd>
            <t>AIPayGen (the author's).</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Server side: generates the AI Terms document for each site from its settings, serves a site's own document at <tt>/.well-known/ai-terms</tt>, sends <tt>Link: rel="ai-terms"</tt> on every 402 it sends, verifies client identity against published IP ranges and, for agents that sign their requests, by Web Bot Auth (<xref target="I-D.ietf-webbotauth-httpsig-protocol"/>: an Ed25519 HTTP message signature covering <tt>@authority</tt> and <tt>signature-agent</tt>, with <tt>created</tt> and <tt>expires</tt>, checked against the key in the agent's published key directory), settles with x402 and echoes <tt>AI-Purpose</tt> on paid responses. It derives AI Preferences statements as in <xref target="signals"/>: the gateway sends <tt>Content-Usage</tt> on paid responses and serves robots.txt rules for each site; the author's own site sends <tt>Link</tt> on every 200 and 402 response, <tt>Content-Usage</tt> on every 200 response, and writes its robots.txt from its own terms. The robots.txt rules include the <tt>__usage_ai-training</tt> policy token group of <xref target="I-D.kelley-aipref-training-preference-signal"/>, as <xref target="robots"/> describes, in the rules served for each site and in the author's own robots.txt. The robots.txt generator computes, for each rule, the strictest value the terms give any path the rule reaches, by exhaustive search over the product of the patterns' automata, so that no rule is looser than the terms. A site that only measures traffic (<tt>report_only</tt>) gets no derived preferences until its operator chooses terms. For pages bought through a quote the gateway made, the 402 describes the page (title, description, a 200-character excerpt, word count) and the payment is settled only if the delivered page is at least half the described length and shares enough of its main text, measured as an estimated Jaccard similarity of at least 0.38 between bottom-k MinHash sketches (k = 64) of the four-word shingles of the first 1,500 words of each main text. In the author's trials with one article, deliveries keeping half or less of the described text were refused in every trial; acceptance began at about 52 percent and was complete at 60 percent. The description is sent as the <tt>ai-terms</tt> extension and, for older clients, a second time under a vendor key. The commitment expires after 15 minutes. A payment for a page that carries neither a valid commitment nor a valid not-checked marker is answered with a described quote and not settled, and so is one that carries the marker but returns a description claiming <tt>must-match</tt>. The quote that a site's own install fetches from the gateway and answers with is not held to a description: it says so in an <tt>ai-terms</tt> extension with <tt>delivery</tt> set to <tt>not-checked</tt>, and in a marker in each requirement's <tt>extra</tt>; installs that rebuild the quote themselves pass on only the marker. Responses that refuse or fail a payment carry a vendor header field saying whether anything was charged: nothing, or unknown when a settlement call broke off. The free allowance is applied by the Cloudflare Workers, Express, Next.js, Netlify, Vercel and Django integrations, counted per process, and by the WordPress plugin since its version 2.4.0; the gateway publishes the allowance in the terms it generates but does not itself count or grant it. Client side: an agent tool that, before paying for a page, reads the document a <tt>Link</tt> field in the page's response points to (any <tt>https</tt> host whose name is not private; redirects are not followed) or, when the response links none, the site's well-known document; a link it cannot read counts as no terms. It refuses a use the document denies or prices above the caller's limit, and sends <tt>AI-Purpose: agent</tt>. It pays only the requirements in the page's own 402 response, within the caller's limit, and never pays an endpoint that terms name, so terms can only make it refuse. It applies a document only when its <tt>site</tt> is the page's origin (<xref target="discovery"/>), whether the document was linked, found at the well-known URI, or linked from the gateway's quote for one of its routes.</t>
          </dd>
          <dt>Maturity:</dt>
          <dd>
            <t>Running in production on one site and offered to others; early.</t>
          </dd>
          <dt>Coverage:</dt>
          <dd>
            <t>This document except: signed-request identity (<xref target="identity"/>) as a basis for the free allowance or for terms (Web Bot Auth signatures are verified, and a public endpoint shows any client the verdict for its own request, but they are used only to label and count clients; the site integrations grant allowances by published IP ranges, and generated documents list only <tt>published-ip-ranges</tt>); choosing terms by <tt>AI-Purpose</tt> (<xref target="purpose"/>), for which crawler class is used instead (see Description); the free allowance (<xref target="allowance"/>) in the gateway and in the Nginx, Apache and Caddy integrations; and the free allowance on a use whose access is <tt>deny</tt>, which no integration applies yet. <tt>Content-Usage</tt> is sent by the gateway (so also through the Caddy integration, which relays it) and by the Cloudflare Workers, Express, Next.js, Netlify, Vercel and Django integrations (on pages they serve to AI crawlers), not by the Nginx, Apache and WordPress integrations, which send only the <tt>Link</tt>, on their 402s. The gateway publishes <tt>preview.delivery</tt> as <tt>per-quote</tt>. The gateway's own responses link the route's document, whose <tt>site</tt> is the merchant's origin, as a payment-endpoint pointer; the author's own site's document does not describe the gateway's paths. The documents the site integrations link name the route's upstream origin, so they apply only to pages served from exactly that origin (not, for example, its <tt>www</tt> variant). The integrations choose the terms for a request by the crawler's class, from its user agent and published addresses, not from <tt>AI-Purpose</tt>, which the gateway only records and echoes. A client that claims a crawler's name from an address its operator does not publish is answered as that crawler without a free allowance, and the documents the implementation generates say so (<tt>identity.unverified</tt> is <tt>treated-as-claimed</tt>); in a site's "training" mode, search and on-demand crawlers are therefore let in free by name. The WordPress plugin's own 402s carry the <tt>Link</tt> (since 2.5.1), but 402s it relays from the gateway for a paid retry do not yet. A new route that sells a site's pages must name the site's origin, so that the endpoint rule of <xref target="payment"/> holds exactly. A route for an API, or a page route created before that rule, can have a base path; its document still names the whole origin and the endpoint rule does not hold for it (clients buy at the route's own URL), and no robots.txt rules are generated for it.</t>
          </dd>
          <dt>Licensing:</dt>
          <dd>
            <t>The site integrations (WordPress, Cloudflare Workers, Nginx, Apache, Caddy, Next.js, Netlify, Vercel, Express, Django) are open source <xref target="TOOLS"/>: GPL-2.0-or-later for the WordPress plugin, MIT for the others. The gateway is not.</t>
          </dd>
          <dt>Contact:</dt>
          <dd>
            <t>The author.</t>
          </dd>
        </dl>
      </section>
      <section anchor="python-reader">
        <name>Python reader</name>
        <dl>
          <dt>Organization:</dt>
          <dd>
            <t>The author.</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A single-file reader using only the Python standard library: fetches a document, resolves the terms for a use and path (<xref target="paths"/>), derives the AI Preferences statement for a path (<xref target="derive"/>), checks a price against a client limit, and validates a document.</t>
          </dd>
          <dt>Maturity:</dt>
          <dd>
            <t>New; written from this document's text.</t>
          </dd>
          <dt>Coverage:</dt>
          <dd>
            <t>Document parsing, <xref target="use-terms"/>, <xref target="paths"/> (matching segment by segment, without backtracking) and <xref target="derive"/>. No payment, no robots.txt generation, and no delivery check.</t>
          </dd>
          <dt>Licensing:</dt>
          <dd>
            <t>MIT <xref target="TOOLS"/>.</t>
          </dd>
        </dl>
      </section>
      <section anchor="interoperability-aids">
        <name>Interoperability aids</name>
        <t>A JSON Schema for the document and a set of test vectors are published <xref target="TOOLS"/>: 26 validity cases, 24 path-resolution cases for <xref target="paths"/>, 8 AI Preferences derivation cases for <xref target="derive"/>, and 5 robots.txt cases (23 checks of what an RFC 9309 reader concludes from generated rules) for <xref target="robots"/>. Both implementations above pass every case they cover; the robots.txt cases apply only to the gateway, which generates robots.txt. The two implementations share an author, so they are not independent; reports from others are welcome and will be listed.</t>
      </section>
    </section>
    <section anchor="field">
      <name>Field Observations</name>
      <t>Note to the RFC Editor: please remove this section before publication.</t>
      <t>These are measurements from one site, the author's own <xref target="REFIMPL"/>, read once from its public counter (the path <tt>/ai-crawlers/live.json</tt> on that site) at 2026-11-18T22:16:48Z. They describe one small site over three days and are not a survey. The site's pages are free to every AI use; only its marketplace listings (third-party APIs, servers and agents) are priced, at USD 0.001 a page, and AI crawlers that request a listing get a 402 with x402 payment requirements and a <tt>Link</tt> to the site's AI Terms.</t>
      <table>
        <name>The author's site, 2026-11-16 to 2026-11-18</name>
        <thead>
          <tr>
            <th align="left">Measure</th>
            <th align="left">Value</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Counting began</td>
            <td align="left">2026-11-16</td>
          </tr>
          <tr>
            <td align="left">Requests from AI crawlers (by user agent, and by published address where the operator publishes one)</td>
            <td align="left">6,731</td>
          </tr>
          <tr>
            <td align="left">Of those, answered with a 402 quote</td>
            <td align="left">3,231</td>
          </tr>
          <tr>
            <td align="left">Payments by crawlers</td>
            <td align="left">0</td>
          </tr>
          <tr>
            <td align="left">Requests identified as fake (a crawler's name from an address its operator does not publish) or disguised (a browser's name from an address an AI operator publishes)</td>
            <td align="left">90</td>
          </tr>
          <tr>
            <td align="left">Distinct crawler labels</td>
            <td align="left">25</td>
          </tr>
        </tbody>
      </table>
      <t>The crawlers with the most requests were GoogleOther (3,442), Amazonbot (800), GPTBot (717), meta-externalagent (646), ClaudeBot (468) and ElevenlabsCrawler (466). Anthropic's and Mistral's crawlers are checked by address only from 2026-11-17, when their address lists were first used; earlier requests were counted by name.</t>
      <t>With the caution that one small site allows: crawlers that collect in bulk appear to treat a 402 as a failed fetch and move on. None paid. This is why <xref target="signals"/> writes the terms into the signals such crawlers already read: robots.txt rules, which they follow, and the AI Preferences statement, which at least one operator has begun to recognize for training <xref target="ANTHROPIC-CRAWL"/>. The counter also records which address-verified crawlers fetch robots.txt, <tt>/llms.txt</tt> and <tt>/.well-known/ai-terms</tt>; at the time of the reading it held no such reads, so this document reports none.</t>
    </section>
    <section anchor="open-issues">
      <name>Open Issues</name>
      <t>Note to the RFC Editor: please remove this section before publication.</t>
      <t>Questions the author would like the working group's and readers' views on:</t>
      <dl>
        <dt>Naming a work:</dt>
        <dd>
          <t>The document covers an origin (<tt>site</tt>). Terms that travel with a work across hosts, for embedded metadata or a registry lookup, would need to name the work instead, for example by a URI or an identifier. An optional member doing so would change what a document covers: a reader of this version would ignore it and apply the terms to the whole of <tt>site</tt> when it finds the document at the well-known URI or through robots.txt (a linked document is already limited to one resource). It is therefore left out of this version, and adding it would come with a new major version of <tt>ai_terms</tt>. It would preferably be aligned with any asset-identification mechanism the AI Preferences work adopts rather than defined separately.</t>
        </dd>
        <dt>Subtrees:</dt>
        <dd>
          <t><tt>*</tt> never crosses <tt>/</tt>, so terms for a whole subtree need one <tt>paths</tt> entry per depth. A form such as <tt>**</tt> would change the matching of this version.</t>
        </dd>
        <dt>Delegation:</dt>
        <dd>
          <t>A site cannot yet say in its site-wide document which hosts may publish terms, or name payment endpoints, for its content; <xref target="payment"/> limits payment to endpoints that document names. A list of delegated hosts would let a rightsholder's or a registry's document be confirmed rather than only linked.</t>
        </dd>
        <dt>A priced use as an AI Preferences statement:</dt>
        <dd>
          <t><xref target="derive"/> writes a <tt>paid</tt> use as <tt>n</tt>. Whether that reading is acceptable, against <xref section="5.1" sectionFormat="of" target="I-D.ietf-aipref-vocab"/> and <xref section="5.2" sectionFormat="of" target="I-D.ietf-aipref-vocab"/>, is asked of the working group.</t>
        </dd>
        <dt>The payment asset:</dt>
        <dd>
          <t><tt>payment.asset</tt> is a symbol; clients check the asset by network and contract address themselves (<xref target="payment"/>). A later version could carry the address, for example as a CAIP-19 identifier.</t>
        </dd>
      </dl>
    </section>
    <section numbered="false" anchor="changes-from-02">
      <name>Changes from -02</name>
      <ul spacing="normal">
        <li>
          <t>Uses are mapped normatively onto the AI Preferences vocabulary (<xref target="aipref"/>); a summary in AI search results is an <tt>answer</tt> use.</t>
        </li>
        <li>
          <t>New section: writing AI Terms as AI Preferences statements: the derivation, the <tt>Content-Usage</tt> header field, robots.txt rules (including the <tt>__usage_ai-training</tt> policy token) that are never looser than the terms, and how a client reads both (<xref target="signals"/>).</t>
        </li>
        <li>
          <t>Paths: each use is resolved separately; ties go to the first entry; <tt>*</tt> may match nothing; paths and patterns are compared after normalization, without the query; an invalid use value counts as not listed; matching must not backtrack (<xref target="paths"/>). The -02 text was ambiguous on these points; the new text matches the published implementations and test vectors, but a reader that followed -02 another way may resolve some documents differently.</t>
        </li>
        <li>
          <t>Clarifications of format 0.1 (the document format is unchanged): <tt>payment.endpoint</tt> is an absolute <tt>https</tt> URI, and content at path P is paid for at the endpoint followed by P (<xref target="payment"/>); every 402 sent because of the terms carries <tt>Link: rel="ai-terms"</tt> (<xref target="discovery"/>); a document applies only to the origin named in its <tt>site</tt>, and only when retrieved as <xref target="discovery"/> describes; what <tt>default</tt> applies to, and what a <tt>paid</tt> default costs; <tt>report_only</tt> derives no preferences.</t>
        </li>
        <li>
          <t>A site that settles its own payments does not claim <tt>must-match</tt> (<xref target="describe"/>).</t>
        </li>
        <li>
          <t><tt>AI-Purpose</tt> is a Structured Field Token; unknown values are ignored (<xref target="purpose"/>).</t>
        </li>
        <li>
          <t><tt>identity.unverified</tt> says whether a client that fails identity checks gets <tt>default</tt> or the terms of the identity it claims (<xref target="identity"/>).</t>
        </li>
        <li>
          <t>Security and Privacy Considerations expanded: origin of the terms and of the payment endpoint, derived signals, header injection, resource use, caching and replay, undetectable purpose misdeclaration, public settlement data.</t>
        </li>
        <li>
          <t>Implementation Status: AI Preferences derivation, <tt>Content-Usage</tt>, robots.txt generation, <tt>Link</tt> on every 402, and the WordPress plugin's free allowance (since 2.4.0).</t>
        </li>
        <li>
          <t>Discovery: a <tt>Link</tt> target may be on another origin (a rightsholder's or a registry's); a linked document governs the resource the response answers and replaces the site-wide document for it; rules for several links, <tt>anchor</tt>, unreachable targets and redirects; a client pays only at endpoints the site-wide document names unless it accepts an unconfirmed claim within its limits (<xref target="discovery"/>, <xref target="payment"/>).</t>
        </li>
        <li>
          <t>New appendices: Field Observations (<xref target="field"/>) and Open Issues (<xref target="open-issues"/>).</t>
        </li>
      </ul>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thanks to the site owners and developers whose public discussion of AI crawler access shaped the uses, the free allowance, the delivery check and the receipt design.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAEBX/moAA8196XYbV5LmfzxFDjVzRHoAiqQWy2C7u1labHZrYYt0uWvm
9DESQBJMC8hEZSZEoWj1s8yzzJNNxBcRd8lM0Krq+jE+VTYI5HKXuLF+ETEa
jQZN3iyzcbJ3dp5cZdWqHicXWTX6qc7kz2FykW5XWdEkaTFPPmSzLF83dXJd
VsnZpilXaZPNE7r3bDbL6jppyuTnbJq8KIuG7tkbpNNplX0KHr83mJezIl3R
K+dVet2Myk/pcpnVozQfNXzB6OjxYEZPXZTVdpzkxXU5qDfTVV7XOT10u6Yb
z19dvR7k62qcNNWmbk6Ojr47OhmkVZaO8XYe6TkNoCqyJrmq0qJel1Uz+Jht
b8tqPh4kIxox/3tWpbfLrKr5c1VOy6Y+bD43/NdttlyOPhblbcF/rWUJ+GNK
782uB3VDL/klXZYFjWeb1YN009yUFT97kNA/15vlUmb5Ml3lWZG8l2nix7Ja
pEX+l7ShGY1pKLTCP2QFfspWab6kpfk15cWd//OC/z6clatBUVa02PmnjN6R
fHj94vmz46f28eT5c/343fHxkX18fPSdu+CpfXz29Ft3wbOnx/rx8XfPn9kF
T54+4Y///uTo5I8nY4zKaOQzfZesq7IpZ+UyqdfZLL/OZ5jHMPlEC0kfkpM9
3OMWBP+MeNLjBA94XW6KOW6Sh6fVImvGyU3TrOvxo0eLvLnZTHnOj2ZlXkzT
OnvE9z2aLsvpI1qP4hG/ucaXo2gQo08nh6s5PfV89PIwz5rrkWzX6FM5S6fj
nh/SpklnN+MB01mwvjz57tTHRFlJuabdVILwa1HS7JMfr64uErruv7gAt7e3
h3zdId1BFxB9fHj1Oh4NnaYLGn5WZQUdu2RfZnOQ/FxWH/NikfxQlZt1MrtJ
KzoF9wwHJ6lvDDS8tKnS2ceswnrxWB7dLh7Jix6l03LTPNL1nKUVTu/nZsTH
BqfG1vojfZFtbbXpiXlB4xut3eBHdb4o0qVdX2X5cumuJxpYL/OULov27jab
0lnlCY0w3pwfKBuhRPztd0+wf+eX75+cHH8bL96Lcp4JB2tusqTK6FU1bSY2
JCmvk9mm4qHlWX3fyoG/4J50mbwPTjSefMn8Ia3m+h3urbOKnsmUZs+i4Y0T
DPDk6Pgpffkvl+/fjS5f/Pjq7Vk8Zv4huZzdEH8gjpG8zeZ5mlwRN8TbXmb1
rMqnvPO48GU52zB93jeB4Im9FPBrTeepxu/YfHDrRydHJ0ej45PwV9qlKuNl
v3wTj/lDRixvm1zmtIlZ8iafZUXNQ9ynKw+S48Oj5DI8vPeMlW4gkUKUNOMD
2jvcql7WuuYYLv2N64iQaSw07Kc07NHxER+od1c/fnh/cf5i9OLD2c+tQb8s
iTbOiuamKtf5TCQEPyRNrqtyBYoh8htCxtyUt8mMWEKdN1lCRE8MMCEmNfuI
y1S4/NM983Lv6Z1SvVmz3DqcLdPNPANDzIpHdKTzGUmSR8+fMwN/TrdevX//
5rLDICBuw20eJk1WN8SnZ01ZkWAneTnnIfNUMIWcaHpRYTPuo5xIYN3DvUXy
PT/57hGxy9GatAosSbwtz0bHx0w8r16fv714s2MSjlskoKWVnda/dZDEXtLt
IiswTFM8esY1Iv2I/5Wk05q5YTMYXN3kdTLX85XMs+u8YIJxylMqK+6uWG+m
y7y+ISUpbZR6TLNIfvpwnkweHfpv3FgmtBfJ7U0+u6EHEr1he4i+aQOHOPEZ
SS3mVdflpko2NQ2B/shJMZuJ5pVMt0ka6mf1tm4yWsr9Okur2Q0TcH2bVUQT
ypNBBiktSnMwpFdnNFZhkPT0hOZMZ7m8zeZD+4BhpCQB6VwPac2Tomzst8Pk
FY+P7yTmQOx1XRZzKIekLyWm3fGQ+QUshJKWRIPA3izTaitHja/rrDqfvxSk
+5AeDkohJTC5rfKG1mDIa0E89xOk+pIfVLdfgyUFp0z2+RWqt5L6SyuR3OCA
JNd5tpxjFF5HTKrNMjvAGsyWOR7Q3NAO85miSRLbI5qss0NHGUn2mZ7Mi0Cv
aY2CtNKPyS0dHFp3ekbeJMss/cR7umnGtsayP8SFskyWmcXikH9VXYTY/xzs
1dSQoTwTKkcqL77Oq5r3l+7aVGsaIK0lsRc580wzYFyYkCzI2fnoQq8MVwOP
mEPqrE1s8kjyOf2LVg5rwffb4ObZGrNnRVEmUokpYctGdKKLQ1RzKKdulc/n
y2wweMDStirnmxlkKZ3BLPmArUhefZ4tN1A7L0wVu7tT5ffLF1pHukZIJKnT
raPrNGHlfG48OlnRb9dZg+O2Tpubw+RqB2Heqoa1gIZ1dyfaGb3KiDINaBf0
ASmhp5LfM8UU5/EJJf2F7Sd68pCOPs0JW0nvdsfz7q5Xqf3yRRb0Nt3igIlC
K9SXrIOB0282iu6j5K4vXw6Tc+YhojcSyfJA+N5sdlOQmF4mGevJMxyZoREK
81/6r4px2V4af0Ojpo28pLWveU50NHh+dDSIdBseD4mEFRF7Kiym4PfdpMVC
dBqjHKJN4USse/PBAvEzw6GB48bGVoDHoqTEBInDdEuUD7qkZwancbrJlyDH
vvMYbCCv6HwOIuW1ASMs5CzXSvcgYCaLobBAWoGl6oafMn5AToc4I/tg61+/
gzO2xuEY5f7dnWzUly84eRHLm+GN2P+pY3738zoMmSQ9LVhRJivS32R9eS3k
ofRGUcxreSWOLI4Rv+5jlq3xPCZMljoRofUwuHQbrD0tKKnfWJwbekA9HgyO
D5NvvjlTRkdkASbwzTek6WKl6JU0tQl2fjJMJryhk2Qf7C1kj5sibw6YNCbz
rNhOlAHCaFNFPWafIDTaGdJBmRkIIz8cnOhoYsbK43kNwiRqYpE7DNaL2UnA
i51dyKMixrcmQ7ZhphIqDxDbxqxlqPzA2Mi+u2NblPhLyMHdkAaPeagXv8fL
ZSmr7M8bVgBDRk6L6Vn8ZOjVjkAQiN6BfWYNsZhnmL/ojXQ+ZrNsbURF3xth
Hg6e8OBeBlJiml0zrekqyaj+vCmbzJQJJ0B4y0W+TDMVJIvM6HDtPFKswjAN
1huwbnkWrXGdNaRCqiTOr90T6JlLIryKfsrr8Ft505zp3v4gwj8cPOUpmNdL
BoxByskFbVZs1fGGES+g/60Ddxm0FmwKs3hZ5GGyyD/xmEl+3dDVpM5Dani+
tYSlJItMDPSctvpTPt8Q9cIGYx2PvQ1Fli9uyA6vTBwV87Gy9j6LHCIKQ2H2
w7Nel/SmLQa6zIuPIj707fxMpnU6WvzRr768YJeZHshBOVbpdMmczn53gp6I
jH4QAcMvcG8d4mr67IWJkQu9u8qW+B7vkW0SNTAwFZagVpoLrf5KtqFMdtmi
pCxcviG5R0rGA7roz5u8Uh75hiTRhqYt6sbHbMs8nka+9/any6u9ofw3efce
nz+8+refzj+8esmfL388e/PGfRjoFZc/vv/pzUv/yd/54v3bt6/evZSb6dsk
+mqw9/bsT3uy9nvvL67O3787e7PH57SJmAkrvjTPqVhxFe0LqxVpPfC0Tff8
4cXF//0/x09o2v+NlKST42NWkuSP58ffPqE/SENSFQ1nR/6kldwO0vWaTAd+
Ci0l0f06b0g8QKuub9icITHN9PrN/+aV+Y9x8g/T2fr4yT/qFzzh6Etbs+hL
rFn3m87Nsog9X/W8xq1m9H1rpePxnv0p+tvWPfjyH/6JzkyWjI6f/9M/DkA9
TH95US7LxVa0nvFgDDWyrPIFrRr0UvauYpVLaACij3kxsuCTXdAivgDr5Sec
FX2GHCwuvq8ur5tb3nyyTpmgmZGyRqRqNTi+twrhwxBBzqoZc0k53lWzteHi
D7lf2GgdsFwYPPKwsbwfjoOmzpbXGFOaLGikJPDjAfEBS35igXf3gOXel12W
tDNo1YZMJa7AynLvQjAfX5E8w3tYhxKjcuXNRpVijvmJfCNGrwwZfH4gZjGv
AfHb7DOP3BaN9o5OPuugJSjdc0te6BJ6Mp24Rm1wCFESqmuyhJnvy5NZYmyW
rF0MRGzxq36qg/cMxQKRg0rK8jJp8lWGfU4/kkYne1fQrzQ+HLu8WG8a4dpk
t2eVaJy0NKuS5JxsobyshnAkUgBPrT+q+cGqVl0WpJuRBF2tUm+T29zlZGNC
rYmoKizPV1FlxgrPzfx1wUIyT+YreE6826NmQxu2om3mP8jmrWDpYPRYqEV8
BopyVW7qgOQXMBBInQnfwvRWfCphpZnqpeYPM/+G9bSG1sB4vkgUFRhtzfWP
3hS4e6A6+GDw13g3dtsWOy06sT79s8XzVcO8yD7TufLETV+xai+mbSWqUnNb
JvP8ml55mrA6UxFVMM+pYImpnyTW2esyMNmD7wu2W9RS6DETDpP9ywxGeZ08
xpie8LR3ToyOOyaxzUgLTYlWY2sa/pqi3tSnItxWJHKEhbDCLhro6Og5vfuz
6Fe3pIXor+L8gvlYHx4MBr/FxtZvO22r35J3WMPfBr+NRiP3f3rAxMh5Irdf
mSm+L7/Q5CYHrZ+gmtXhcRRqhjQ9DR9JsrO0y52RrxfDPwCGJrYvUSutNcYk
501HxFHa/QlpenQDhnJeqMUuxzkXv+DXHWh7AR+qXc/ng7gQkUXUMmdfOe/n
Qoy5LDzp/TxpRayM79Gnn2LbhCSJOdFu0pYvtzoUGR+P5VJGum9fHfjvnJPC
XgdzQGc/VG7vaGFGanID8reVPLQH6V6Ipa5Lw6NxAU6eKZSigLnTia/VLBEa
7d1KUaVyNndFaHaezjO+G4vn+/s9CEp+aD/RcmTqi+ilAUHBJBOiipiSxCLK
uh59InbIfhPvxVQToClZwEx++QWGwS9sOrjHkmHDUhJSSQ7218b02DUly599
5hhb7Z0D7rz4m2D2s++NmZYM0TOtPFJdnIUZnXG1QGUuodcIqgUMGlEPmOTo
EBD/f1di1eo10QLYpl/gQ6N/tiZpm1gNoMV05493x87KNJuleA7GSmJmJRue
mszLWBCrsKXBswnqxbGwanoQ3WIyPpB2eAfPmEVWcv57QmVBCxsSisU5a/iK
2TZix9mnHN4r8E/istCYSOEyt5bSDY06eDJLXGhapDlYqK0eIUjMIVf4jFQa
JE8OIQh2iIGDoXMyhCqgSDhmCeroI64XRSJkH27LzXKuXtTrDas5Ync8gNR0
FGExUEj5N2XgnHyNSP9gcCbKq0Vo6oAXpbUFcqC1M36CiLGc/krz2xHIkQuf
HT+lC3cEdYYcAv6UzcXXs0IMlxEtREieEyC0KvT109Xr0XPSYWYlnD2Yn1st
slGIJEkFTrEYZFCwXkwsJxNNAPEKIxG2BJPIEiTFIK/B8rZfvpyaA8WfRphs
TNTsoLoUXelttpoyWmaQ5r+om7BuKhjtZswdmBVhaBCIH5yhCCwy2Ts6PN6b
KHUGVMCqOO/K7ierOeWNJogMolgsb54u87/IfGObS+Nmn1N4ACYWCtQvOBI4
oXdv1nPYF/2vf5k2ZmDQUaobVThoOn+if0Zv345evsRTmBvtC7m0HvGeNV6s
YxTHg2vPxfKcnBs6hjMMWP3QOA8dJDwgTRxey4iUDiM9SgiPLRxS8R3p4GQv
6dzWYIk5L9UnWrf5KUgA3kFcs8o4fsLXpMUWNh3TKQ1wQjw1JaVhYgIG+Cxi
sWIH6K87VrHtx3X+WnjY7RVQIcxlKeqGWXCFsO3IhBvGN6iBLabfdZova2et
Ei/N5xyvICuXzC1eBXqSfeXc3Xgcv4a3SdgVvRfLFMQar9nthpGQwJGF/vmG
ZalbIFpdmedQtetclHn+g1eW/8seX+dRVHcrngmjm55KBzTnU+mJnkMucikP
S56qNg5ioMRhmOHrCnjfCFvysbuULy03jXOkz7IcToFIUmJ6yX5aVel2mJg/
RCiajnqVG6SGvQdO6ZSTHCzOYOCW3h2P6GETuA3Zdc9SkN+GcdhNKxIG5dzv
pVGLbNlkU5gzn33/MH9DatLFADE5mli1dp8nK1T1izrKHRXHI93zjvO9iXPI
Kd/DkonLpMMH2CFNjL9ck8n7iXRiJjI5A12SgUdlgvWbkCRoSA6TsEJQk28T
MlcfibsNi2GOaaKOiQ5lEuypzMHCDHwYdeT80cxmeZJd5LB2ysBaNMpTZs0i
u92xtz+rKAfZGbWow7/uevvFwtN71G+/5Uni0DKLh67TqJfdRxnaPvxBZajV
/p08a0eyBRYm4WkNSugSV1mzqYoaz2Rszi9QVPanZbnM0qJNIU21ySYWfpDg
GaBlrOmtsrTeMDPzPi19h51HjsIuDJhxk9bOcp7xphemAr8rdwb6eLHE/J+L
Zqnn3gmCfe8e4HVi6y2dNbuOpvPR8+kknecNtpC0w49MprNNTRPxjnx63k+F
qEdGLtAp2EO9KMqKUSJnkfInvJU9zqwCiuyRrQjc8k6fEE2TnxFAnEjgBxA6
0sRU+4WbMIDiiOsq53AGwFOsAtE7Z2khPhaYK2oKMtIj2Q+VB3Gs2WHjc1hk
2ZzPJMtIDmynW0jcmPuaHRDLYfXrYPI473KmJ6ZjTUjp/lXClFCo8sDudmgo
uAPTKcMYT51kYbek0DS76kIRDWEpMi1vukJdtD2vUsBlq6oEKX9Cpn+tbGfu
wOKlyw6x420epk9bsb0+IcHD0j9fpctEXpsseDHNwvtLVpUktieK3NzyDbBW
Bf5JdEAqdHaaTH66fNlh1QciO8g6mzBHJM5Dt0OtiiOGElhWBcMuMX1DtDS6
iN2WDQ1xuhFe1C87lKSZw9sTM12tgraOBhLaPUpGuXgxIfY0ZqchgE01y2QZ
nc/agjIQfOrmHQwQ/u4c7yHjIO4VKG4blWHGYfSxm0QtKw8gIWu4zHSOeQzH
w6OjI/t/sOKk6hKzq/QNKb2A/TEZ7Z17OqJzV07xEZ0HRyeYLJ8GCX8539mO
CSkygEeQ1797tU4f5uh1kzlYypBetS3Z7VNs26CC/WjwYAT+2XTON86Zy8gE
UdcVyiAscCIDgCIApiEsi+9g4U+cEwf0Nb/2zL327oF/Kxu3X7OdsCJZU+Bg
wITnMVFu3TKX7pI92+K9cXJM+5js0f7R5z3atb3ky0TMU1HKNOawWfOeBLTh
4lHClgUvIFSC06SELqN2Sl/eQPw5nEZbW2fkEN/909WLhImJp8ef56yqOliF
i7KYfNWdPNWN5eEMDYBGNoIumjFHDxen0646wm1ezMvbQ7LpiDzc3IwVdF4t
zkdaktu0Eu+927BAWLQnr+LBJr9gqUg6XXhrwG8CfdcNCE6bwPsY3Pp+57l3
fFyIQvQP1locVrQtzeWQ+mOQS9wQ+AEF+bd0cDY1+UBzAIdWEFDqJnWeUgN2
yekjRYORL14tEHHituV6U6dLRLKgaImf160BOxdbQB+3xkNDHIm2S59tY/Vh
ymzEc7wmdfhzzhobQ0rDQ0LLX7PKwEKK/TyVeiRBnIBM0UjzirVvedoQx68v
ugImNw8Wk0cWGHFyz5I2S1jBBcyzuwdiaGmASswFolWzH3gTJzRy9qnvC9CR
/8VgNX5jBd85qHbyiH0LE3ZG0KVeE3BB1koGzBcINzeEFW2VNzf2QwionSDs
G1y6NW3lARAuNix65zes8HActAZvrXkHeQVoHizm3atZPSZllVe59L5eGrgQ
jehu8ou71D1ZAtaHQPPI/N07AxeCKqL6C078DSn6snBsadNSFI23GNRXAbC5
5zP8G/0CJDM4DYA/bKQjpSt2V5kD9dnhyeEJP1mTs758GSc3RGimBc3zheCx
mF5nDFk2N6H4JdQPAFffZs00PUtZ74uuZohRwckvcEoGC8pPoDfxFcNooTdN
TadGYxgO7g1MiKxKpCeTKjM6u3xxfh484wAPbw+Dpg9np+zdvGxGdbYQhZ8v
J+W/dEZMuNbyTr9sT2nZnkTLxuK3SOw99TKtOYz0P05eTw6cFE70ZfTfNePn
GCl6IXShRgufOVhHNNNwdJFm4tWI0q2H9xE5bx8iBfIiYiHEE1clHTueFR/Y
3OIYIDs1hgFinEP4e7EZqQxt/9/QWQFOCq1KcVjaZqo0CIjQeEN4nug4qkw5
hSV7W0rkFiTAoMdiI+qCByeamIH3Rm9G5IIFCL9BIvPel6FCV/GUzi+i7Cfw
lrq5R26fnJ0awIGohSMIADGovFfFjeQPGq7huTlTChEyYx86OhOmaYOVnJM1
dcMu0nozbaDyNY7h47da7UAYX3jCGq4L+okIhcgwzl4R0pJ9Xhu58eIx7IPR
RYK2grM5KxaNcxQbzzIQQPfkGUFzqEY+DtWDyJOWqD5mnGHOB/C8IqIAYe6H
syTaNFp4enwS0I9xM6MfdewrPsgFQU2qHT/Dq/39Irhe6YDvHujQSXj953/+
Z8JBkMHdIEn2zA5mVZNjBkP+ksUyf9HjxZcL1I/P12gyz+j4uf5Ek6bv75Dv
syeOdvo7SUjHFQWI7wJrY0ReYM3x92a5kco7lCeIvvdfeYI59nlU4RNYWd8b
al5T+M8eZKheDhNZVufo6IRfaGYwf0kWb+8joqeJIs/mrhtU6xLWAuV995sB
flU4QIFF+f9hTskXuhxD21N+EI1lz1RBeb34oOnz/95zPqNRvh5VQJfs/Yc+
KXYT7yFhzXmE5QpRfeSp5kbd02xinpW6IOirk86E9swLGxI6PfFQif3R4lE6
nR2fPKYZPXn6rLsie0XWMMCG78/y9fHTp+PnT54+BknSyW90KV/s2XzEeyuj
Ze9BjSUAJoFvCryk/Kei3vgjkLF7/9EdgbltsdpZNYLrt2ekLjT5i1wx7u7u
VyzB3f9kTviF5jP4wlxEhPNO7yii4iq7mTNLuo4ojqZYOPcojCKD/XxfTMYe
6ZFLhsmQUVSTYnJqmDifNEe2S6PAmfBikjs3+gBV+FFWQZExUPkFKKKKilw0
dHiD1H4PUBQSHQcORBJl3DD52Zb85zD+bgFw+hBFf2lxYWLKPkYMLT2dc1qP
B8vFIXBkpsDwgSjxY1L1SLANWx/pUg1m8iYvPk7ibDsNuz9//uULCfxcFaTK
gfUkam6BdfE9iOLt7FLWXkAzE8TnYbLSsKainhWi5EgwObbj2h5aMgnyxU1D
J2I5xy0wEhakujChOPSA2TcaYzSULOTZgKc4Tv6hR171QgX+8ZTn+v2e/b0n
5Hzm1pfnKHlimTgz4Q1kTwh2zmWV7Fv1DsW2zw/88kui3PHxEa1xo4mHNbL0
jMA0XGSYiqHDCTo7XnKw5lHGFtvx17nqJnq8QPjTDL4DwE/FS072By0pDG2Z
mNq4NrVc0LfYKhu3BPNc1ESzduAGQjbFjOEqHOpgkcMAEcFodYbO+0iHQaBr
rMqR3p/VfnlCeqxhv6vfoQTCvuPeYRXPUQ4RwIQJYYLMII32CnAhxn5z1AHA
s6EgOD+pzzcMjAi2I/ARyfaLqhZQq0YO5L3mFPUvbiEBc40PzXLAZ1HSYdxz
fQvnwlAswSkPneXrAWVYScmtVHC0s47t0Msg5czLYQ9gKnkTRYUU1dI5sMk+
4MvhuRyGp1JTk8tPucMyKDzQELAH9O3Gu/dcskN4hHnKnuqAY6+jHGCflh66
qgw7FTOCiDzCKWMm0XoETrzG8zUaiTj62/6GcHXN9bqPrDwzHOF+OJCQuKMw
u+ehSJ8NWUavzcZy78r583qZWmIfz2l0yz4ANxXWnCpYsvxO8zUJWkzw7GGg
NrTc1XxrgtATGWymiynGLnRKK9bntJMHDdalaWoK8gTy3qxs9dH2SJpaUpeJ
X5EV57O6xD0nB6gUTpgmx58/+0toqcBzs6VGJnMXfWESxm+WfjihMd6U1YQZ
FJ2NRpQDdZw6IzbtZpV5+4ltSi/w8PhhFBzCwxTRQOvioIJ8ZTb326Uxzilv
Bbsb2K9SVq0wZPBgR4y9u39qaaGK0LEsb4Tp4HLT94sc0PRhG2ajniSwfk45
zUjNVxhG8kqir9mcqGvWKMyb3epIHdPBg3N15ujAa6oAWOJg+zqmlRQkOt2C
DonBiaXOWZFXstSamKeWuPCfhxEfEBaf9izP0NI2W0yU3Q6nhgxo/bYVsjTP
jn+UYq792CF5zQlgw6x9eP2D410KnjUJbZaFwkta2rfoS12eK24DOrwpVB7Z
0rGBCuoomQiZ7i5CGYAqVXp20nMUidVHsSH7cOpEOWUfg2oeRpvgsZEeSdrv
J4Pfe4lt5+zQCj7QyV3nopXYpFn0JMvSQMty4GTQfXlLRWnBf00FRlEHztXh
IyGYD2XcDsAI/1H1SZzh+zXCnlxeapTXNTFJAWVoDEIVIwsj6EL4NWJW+cjT
5EQYJA1Hyhp4y0bWO5AFHvXqMw7AxKEMCO5XKm3oViFRR6EZm6Ui1Z1n385a
GOjJa6coxoNkKhFYhEd01exgZEKiJdXnw9Mc+nlPDh8fHh8+Vk+vFHsIFov1
fE7bx4nP/GEmDfynD2/+cSK5W+EZPkzCh3snstaRUHC/Za9q7FfmLFa9qAun
rqScnVbBaVhKphAPAJUcPSnS62t6qfEfmF8/V6icEKTLdzL57x5Ybv5g8JbJ
tKMN24tRjsSedJhclit5s4v2IE6YthMNxrzktM21OD6JJuEVd+RWa7RUXIri
YDsaPT4aWqx2mi02BZZrUeR/ESa9J1kfztkVWq1c5G2+oxqDJj3f3bXqNkme
lIcC9ZeF8ctYfWVxBJBv3a71Umt8O7gOyndYYyYIDqKyH47P76RQOUa4baOP
bi0hK8DgaxjWJS/RiR0qA64dgJMZYisLRSwfhJyaIC9HfLAv2cfBF8c0pq6P
33GisOMkNy02qkthKf3NTQeHhvCAFoxsoTRdiKRUDmmeGMOQkkG9KxcL0Jot
EHdBXoyPZp+ye8aHC3ogSp2cp/CRfakfvKaI57VfUWQ5OGn4dvDW27xWyK63
Hsz/g5zcVqZTOAJLiMIIglSyziB+/02konadRxwr3k4C79HfnM+k5pCDBkPu
STDWp6ZECSOP708YqUvdNe8Is5TH0A/HB2Dui8PMgxQhya2ue1JzeTpeIbF0
MDtjv5sXVpfh0UsNi6DOvPbLXNCR6+GIK00gTbq73xcgxBBdSLcEnIsJzHkA
i90nMwAA+wop9IfZV/1oDK1dFaaBGmNap7pKq03dYBKczWfRO0yXlY7AT6EH
eFuLn8e4u+wHnFZa6ULVbweZDnHFYoZN26M67MDQ2sCrILgnZYUEKCx8CDis
cQh/NNu9XQ/GVR3xCxLyKyYLEpIaCY6wtz3pKC6+fw+1syfjZY7rJE1Ya7Vy
OpzzOflT5AwTXuF0StTawm55rzU9GXzte861cGFQx0DFY41KQuZqbtpzUiNg
tW62wB7vBht3HVMBZnqi/vQNYx0BSTcdw5DOEcpZFhePFwfwxvRyL2tMcgi9
eDArgzz81vmyIVLCp6uspjPkvFhqDNG46C+BcxFvUfysCmpJTpF6SOqEl2Md
ZamcBvFo40dR/TjV2yShW+S/aODzEilgquDqgoYZA9AtGJ3Gdrc6NYuWcp/K
yAVYz6PnFMV6VwW7VvUwRl7JJYG3xpLKgS9oD8C91+L2om/wVsaF9n4Uk+21
uP4fiAX3JfB3CyNxrnbHQ9QqYq81xjCJntuJKewqe+bPlSdnR8sOYRZATtjB
4R3M93umRXGUIXjqCz2xaheu6HFBlaMoKciYuSu4aL5dqcwDERTd4Hkf0J15
gL+iOwQkHjkd96OMwIPE100I7G7JNwz89XJilkw0Ww0eaIJJZy/kNdcqIp2j
bTWF0p43fhNs6f1mpHUSgnyO7+Ge/pHr0KBxHMLk+lA0tSJRRY1z2CFciUhf
x4MU/J/tQNHvh9vNCPt8Gq3VPuyYG3yFZUEfKCCr9cweX6xUGegrBTGkBWQd
kRZIcvB7j6xk3+PgdclbseRS/koOgy2KQwNFW0ZLtSlwPQtILS4jEl4lfx26
gFRb4DTEJsjA4YXQBB6nDcSqwDCoH8l1+rhKQU9kR4g/LN7VlAtB2YP0mHB3
BX3UsgkEifOoAO2zNOYW7OMH7OPdA93GjndC9jnaVs+uOx4KqZLXPlSOVnax
toPxLr5mZOQBV4FBmkraizs1cQqaO6n482HtEUneLSTf3gytMIfBzkTIhEEU
gIA5tQzo0f3Jf+cowAOxcmAzxMBDMOA6aw7aKEJmS/pmh7LvZyd2QCz9JlmW
JE+rlmnOXD5AA9jEeMQMCB36AcLSagxjFx4oGYh/JCplANe6EdTXDcoNnmkF
FI+RRbVTKWZQq7g3FakO49PsRueIR6fYjkIJnHXELE2CURVdbIUbTXEPr4yQ
ZD9cXP2hbIbJCxShlo8v8J8fynKxzEYoGjBXR/QZ8Y+MttZ9e6AI/MnLvBbj
NJBDjJiTrWiZ6528YLPJzLnG75IoJP/hC01ZqovzdViuD5YXfCXXHGu7wt6M
Woqdffj9+hj7f21RjL/LkogL4ExulxvUqWHAfV9FVi4bJ48mGuEMDGYDqIDO
8Rzz6vmEMVkSDa9F/gTh6fI7R2G9+Virb3gcRObSiGUL6JKrq+NC1WGCyGuw
Pt7N3M//VGueZgxXTILUAVmTjxkncrL+LlwPA659rNrRFSwamU5gcwthfZ0x
A9kZFlgJMfa96YVOl7WrUOEJ4dQieJIg4+GZMUC6gFV7EOy8zPnnAC0aRIG9
nwPQTlFocf8tFw4J66Y0vQjiJe0QI14DJKdZJbRO6ls0nd+bB0YQHk+N30zQ
iD8ZK10ov80jv6A4EMLazr4aZZ/cG/ZRHTImukaSZ8/7evaKe0yqIjB6h+ZU
8bKl/6bJlhMqeHriVkvdKRzhyFghanWY9rEAWLV2uhnL1TM/Ipnr9BNyoK79
OecmA5vFTZejiRnji17/LJVDZEt8oFhrjtGGZBVLcJ/A1Jks5J33LViLAdFB
+X1id5aCJBeKoD9InSSSUpSzB3cH5ASySeuazmDiSpV1thMw7RJw8yZE7q+3
Ur4HO23LIgc95jlnnuE4c9hO1VdsjDDEe61Qkhdq3wqokDM1NigBrnE3S03E
qhM/+YND+xmRKL6GkwxkDj6tP/biocozX7AfR7eO48DZMFRx8ZAorNfPcxnq
DovAlQUVfuZG1MDqXWYaY+KEJAlAyizAa2PXtMUSlOEq++el0RjATiVXpYe8
WxwpencdqnACz+eKCH1TUi9TR+6Q+bDuP661VTSGm4YDuLDCmQpEteQ1yL0+
FgcHvVs1iLRCVoluLo4nc6v6eJDmwWZLpLsZUdgjAatj+F2YJZe7yNpVFDcO
kKA9kAfnAohRHiS/MvaRgXW4KfGr0bZAlayWCsuZUEoU2KU4uU7ooI4pJHA6
SYkUfkXJFeNDecJU6qLi/aSKNl2C6zC11jQu82uQJLEEhC/D3lMOy9GZ3FZa
vFdhIVUrna9yEiLYTXo6ojOqduzXHIX1zFnWZ5ldN1gk1FRgJHazPVDw6E9k
m4ykGGbyzaD9lkE0Z8Ulw907iO4UTT76yin18bcv2t+0VP3ot47K3x1g8EU8
pB6FOr7YB+6/FjkrQFkU9pSyoH/gpb97AN8HK2fdkEdPrLhQCLWiX3dEip2n
ycwwLVSpaLMwVgxGJYGOkNcKEkQS9gq2cDlQxMQ3bmMNdzFjESqRAFBnJE6Y
d8cEIyAVy5wWoZ2A71bTbD7PHNzJZU2rnNOIHtkgWkBW/Tnd+I5LsddVmosT
b5fXrk63xoD7IsP98SPF8myWjUv0Zk7JyoSrNcawRk5LQ14XK3YOh96/OJ3t
GTpmEZZ2lUS/aEBOOaPVcWl84nD/K9yXmh6E7Ws5BVu+G9f9YZp5uF23j4Pz
IgYmlmrn8P6DjcMkvikLUh2l8LyzRyIqnKH5hZovYqewcU5UAhhj+6xwMFkC
RuJzTLt2rFSt1K5BVzd5Nfcb9XXLjiCkPneXx2cckCrS4fvpqUQlxogMBFjh
Kh9xUiOZTeLnteB3IQDRKA313vieCF1eTC7tzNJvlkmV31IQWRbvdl586CBp
N64KStAQlQZiD5M3+ceMXVJD5wwK8PqzDI5ujd53gLTtGGrYsSYK5UTy241T
m7DwJlmtSD5qBjqjMasvqmAXkpowSgo4waycCeTXlylA7olHEAggVEAGoQ7h
wkNapHUX21YQje/ZNTF/SjHxroQZS2k90vKrjDJwkrrIutddJYPGxQJ50JoR
NlZqc/2UWkEvCxIOBmFHDqmi0Ne5Q1r1OEdnmlzBpAujxWQnBGVPlTxqxUnN
Oz0EVNsIhvi9y49MHrlER/7oQVyPLNVPBO8lqwBW6glhOf92ONxZ2UGuBh95
yUrXUs6y+Q4hLQyQjt06wjczNQkZYOpDgQ/6BCEtx1MrzEcCFNiqcFlR7Ql+
eDQvEbDtxogZxqqSEaO601q1x6j+fFzcCXONdg4ziooENeUOgvUIPR8q1LNh
6IogTiJNWDxyrCfQ6mpihqsShO0kPwtKvvBL3zjG8qSy2U2p+TdNBJn1jWTC
Cgcy6IUV5wgKRGoA/0FybjVN7h64+i1eI+NMiWWaw7J1NQLjtKyNUx1j68Jl
8guMJFtekyGRzw3SdEsTEd854oxqo9tLDrXioOWZ+5R0KzaYRqUGx1wfsJMU
asVJdWk4p0ISKNL5vNKaKmEJFv1WbtbNlck7IEQ7s4zNO+nmMxjcZtMR69zc
eqv16jBQiTQwDStLDZaG5HvYmkWtGG5vcv8ghlJB1nGOQJO7px0rajc5nVtq
LqaC9Xb1NfBODNftexzvCFZCtiWVAsXyGIZOt5aTbqEJaWESTAtX+pB4WVzn
1aqHFoICkkYPrJh+VS1JsV2lQJO8ccwdEVC+aZTWo00hr+Gn2561jok/trl1
i1KNRtiTS1DSseVW9C1R4EyLOx5GA9DNtXeHXEO7PDY9ZzAQEKoCRKcyMJKt
IWRwMmNoj4cPp6EH1Oz9g3D6w7gkJmaudV+jEYGTCyCdfo6VGVEcYHszD+d3
8lbZ9hiWCTe3FaE2ik2pNMDPeRWRFTklxla1pv3dgztAUrChnWRcfSydV9D1
kHKs3crM+mQpRwvem2fjEMywdJThoixZfBJNmWHzr38tmHtbIikXGRJoHmkq
1prJFwzVriDTulxumizKwDURjzgEeoBU6UI6O10FaBjD/F5ogzdeAElgc24Y
UFqjEWhNZdFcqy3ICvHNyaOJVY4Z+vQhkhEXsT/LcubYxaTiA3WZ2KFsVrWY
giJBozwXKDrctMICyhfm16u0NLMAhsLKObAuERlzxVdqus8wgop0NloodBJ1
XBfn/qo3LvzlmJ7U85HiJmExHHY3cSlo/AEneRrUwRkMfjaeo5hXlhrtgnJB
5rfvNxPVbg7AqJLWZNYYtk3yD7EBvqaJtn/sFP/0ORfeEe4I0RW0tWRG7adn
zVGtnd7QKUbu4fDCqLqoYnpycfant6/eXY2sVuWkPz34NFTPJDOt9g7CBZwf
aFJsLcLbz788/+Hd2dVPH15NenX9IFvKlzyUWrSGxrYidn7lcl8yj7iFxfAm
MNsnCXp3A2X/6o9vE60UwVFYtHwScAGJ0/pa3NW+JBlKc3j0iFPeboldZI2p
nDQI4iBuf3btqJz8aIes55RpSlypomej8b0QHuejEXFzaaasKMnkwUDtrWyg
sW6p9UNOvezWGllGqzomLv0nc3RxTzHypgwFZ/3AWRsYA19PVkE+Q/fJ2kOJ
tFRXPZRsUrPE+CojZJlcWnd+sNEOw8Jv2u80Gq1yMO6UcG2V0ZwLSGo6tNLG
RVBZYYNo3koFmgHDQ1ONZRuM1ksn3pQhL0t4HwAmXETY62Q+oszliLarabkc
+gqCjWHIbTVt3Twiihkwe3lJQi4y13IV1wuOwFEj8hdDlVOXjmMickwa4YAq
NISuYq9fkI7pwyTMJbc9GaRt1KRoru75/Nie54lzGWmjQ4EraATBVc5TBa+U
fnsx/MrSi8NxOCxDqAPaMLSM+E2+QG6f1Io3IukbnsupZHAEPJjmv4MalLgA
rDlKO+Bt0bDlGPLsPFYRtHOa9PiyxCdnMqsuozQTW6JlvsrBN7QKfpg6aDk3
3l4oJBPEOYGIDKzoCuoduDK7eeM4NKBMcJBzagatTtRXvZWlPBi8l1e2Gr86
x+wUxd+IdlwXGgmPtbe6lo2+3sBCsw4tlqAF1DDfbPmqf5C4o1fKXMVzJn4b
jRXL/pijILzF86WfHEt9dQnrVkh4lGbN5OB6kXPhjg3cdhrszGW/oq7A9Q0g
7/oCp6RxqEuWGwjJ+/L1pBmBB0invgg8XyBuCl8E/gbZvVppIahM1O4hocXm
nTOyrb+FNbiNkMZaklqnZgJJKVAXt5ZkR6CexPRzRrRYmz4XXvjiJsB/g+G7
+em8LPUYm2JZ1QCMGpBBnEy2DBPUYOQKu5yQM5LifQG71w1XlbZhSo666cQL
gS4gLls57OBwKlUgNEkmDJuGadghKtmHttQFqYec39PuGWAdgPctymsa1kGn
KbAy806ngHt1vT86bS+s8o/Mf9H1FLPqe3qLUAhA3qpKYJxc2MVdSr9JuUVa
dWVGTje1OA7gLaAPd5tgYsWkZ47JUBjlAmMy6YrrctIZsXa4gNqWQu8Jy95r
k029WY2wsLS0uF/tJYMBinr56uRcb5LBXccnR1GJP3bUb5bLA98bdIEET74b
fV6CrgvtZz0++qpn8ZHS5pND5xO6EZ2IXqFVxrqPP/mdx3MivbYxafzbVlzB
k/sHnuLqTsmXusjX66wxnCy0qikH/okHCWaWvW/Amu9rlXP3xnaRxviFaK3N
N2LdlJHprCTJMzjFflyupbVneHndIgzvmGME5C3noJKlqG0yJh6i/HUtGXat
xD49Vb9kgPYq/TyyPw9ifzOmi/LzwfkOGHXA3rlZWt7U3uVlX5kJY9XkWeDC
rSj58ur8F+kau7ldtS+oCmoJ5KtMC2hYRQiv3VtF97AJ5n39RhSI4/yxZPpY
tX1xpPiSFb7jmoARAtroZ1rDPtYc1N8JF6cwg46m5DXG60R7F3SsLfBrhDZY
/bJ+Eic+rKCNFFuWMXQjhEnYj2Kv06vnTn91GlC6XZZpYLK2JiOYi9ZcTHpU
CimWGhpSNXeVerPI34EqwkgHzGz/4xe1U/vYD1q74TN/Wad/3oix0G0onwbd
0oR+nRCemkrA1ZOXglTIgnMetZh3dRRuUpLBqRRUNZET3mMv61+1h7VaqznA
7diNOjwx9pMzFcH6fYNpzoK5gbGrI6ZzhSHpyvoBBBzyBm1VfasaPGGu3EyO
ZlzQdgXIgDWK5x+/fNHEKh9QkRRieaZz6yDZMnqYTC1gn3WHrXK5L0BKrVB3
pR3N4KH+8ertG4kQFwt2VPMtgjxAIucym1jtJkbmGo8U0UzKN/u5+MVSJHzh
00WQ+0oWEStodOorzBi2d81FXlw7RzdsSfc2jtKqvIIQjdbfQoWwQKSKnt71
7BijgxMI8fx5RJ4I1tOh+HUzt3HrrTCvZRzjyAeqdWic0XdblXHjZu2FY5E/
aLNwTkr9Yi2oLimbXQXb831p9hRotHySAnSG6XyLINrhCwu2nIieHwzDsxgI
nPhk12DVvB8mTdMk1mGyTGSoVES2uxxIOvBZwkle33T4hOVIWspyoHMWzsxR
qlDVnC1P9rMw0GUe78t0ky+DnEq1ZsSYEFs8UhuC1ethvRLvcAPu6VDEHPha
MN3sXIzVXq8Qe13ZebucFFXeBqHmZUzU/tEq82nettOmnUXZ42LvJRYF8aEn
V2srJcXmXlMpJBlHJ2ig65Jt22TWjgo573qwXn5xdJe91mJqgdITNlAJxU4W
DFUaqDNyAju46b1ObMfcbSJrc6RL1Oxx3OTEs6dLLyKJsMJSmBa+AsSI2b2z
S6WZTiyXrDSW/GZGfqDjBWpqvBsCpQgQGeDTw6/ZJU7nNIdWdHhULRurjwLD
CVjGIouc5D6flWt9lBaosDYtO07zYXIZtkrUFdaGOcWOIyH5QWKJoeVGd36R
fp4yeE49Dm1uol6kmzRo7cpCrVuzzYer0cVDLlQdkbUoZyPE0Gfn8wPba9O3
IAS9U0M8ttrHzLePBLymZy2kAGgR1CuwhbC0iWCjh0kabaxyA3Ntd9cm5rQT
LV8dasI903RNRH0iCkxjPQt8oMk8RvVrbXfJ14iZVmsbQ+niFpC3VrznulmF
dFyBhTwZ2j7hMnRWFHOWP8IYnPRYg+2WasEajVUOt51ljuQVc2unED4BV3ib
b2fbQO5WYEM+u/EdHlS+xF6dLq3192pEoTj3Yt2+7tn9Kw7qYXxSxqo9WOpm
zJ10GfPgAuuC4lwVbg5+rYUF+TWyVpVS3UtrYO4kQpbWbG9ekVbIpp52HH76
7ZFVlWDy/0TaObPhoTjyrRVslJgX2oatbjyphGp3dDD+3XroE5wQzmfLuBBO
Xq+83BIV0dyCqduORVnyAZzNNlUqmX1EribqJax0bt5P5393sb+FFGS9AaqX
wQMfrAPn3QOXy9+qMhBn5oecls7jKBLSQc09+ljCiAniltD+Wf8YtoO4lxfv
312+aiVkWYzLonpm3CH8mcJVLeF0HUUE8ouexJA5e0oI2eD1jyoN9HkrzEWR
g9JWEpUEQo9m5wolbeosaLSGjlk38NXjGLdKj2icPrNqLw7M71saB/VgUnFk
+AIMLrTrwjvufVYu3I0rik0DgjhX/CZqOAg/VaXDqdGp+uWtJggW5DTGPbu3
hW/gO8Wx4suRmViLFp5rRMURFQCaRRT64LwNUz2mPX7wNumdmj+CGCdw01aB
AlvJlMOMp5htE9d8FghxBs1VWU68zUDh/hkM+RCuQw/JuX+JuT+QQYd8yiCY
So8pPgkckA+YVcYvE4lI/cwRWT5u8gMdtw/A8SevPs+WGyzFhU6GOd5PhRTJ
kq6srdQ7MtRZvAXfn3brqjWKIpOWwblgLyMPBJO2lA7ncpuWl+DiQJ0SKFG6
g8PIokpfVKpwZ1LJ7oxBtLEMkP/IazANzsJmHNQWmDVw05VQDc/Tl2Rkz0xU
0U5eJI0JXTWPv7b4JBhEUFXdkHJx9q4R1NfXHkD4UmuHGkjI1YWBQhBVeg0T
nDhKIUbxfB4Up+Q1csm0D6XSB8o+cyog0v7GVrRIKEMPkgVp+NhKPQZhacRq
4BAWnnCdcRIDBjMCfkpR8iFieegQpY6/WMAo8Bl5wS2ztmMJcjq8+vcrXUuS
OCPWZD83I46Mw1su5PLSNEfkrNlWrH1Jw21i/QOBUXYpglarcvQ6c8hNDJWD
+Aon5QUSi5c9wz4RbQ788SrlplnZSKQRDLqdK2rr1bdU8cy5QrjQSGWl3lwb
sWHgOZm7R1nUwA6ILyoOhwQMxmvL9eoeKRpvfsidnYyvqQYviT1Wrb1VD1s4
rQTnkaOzzgoL/NLm/dFjmV94bvxBuDFv2+/yXOPct0o9VclCkw2XqXbGE+1y
ls+NeLLP6io3NJLfMcfuLYeWiZEJ/NQOkcBFy+xzXpuS7KIEgYwShp/7J8ma
0ZQ/ZCiUcwl/afLGGm6z6nn5RmiVPiTHh0eWq5XVvi93UIy7SP797ZvANFIg
C8S5VAxAYwKI+PFEaim3ilL0d28RnRodTFRD2JOaBeyi5dzfc1842/lytmug
viwbkTVyqQ+ip2okuorpHAY4dAFXV0P4/RkRS3JyeCSry8udzoHbqtUvpf2/
NajhM8Pgnz7E6uVBhSyQS9ZkwSJec5YK874hTHxDnAiWUuKU9mr2KEkpQMGV
KZOXHkFYKaSMh9KITZlpJq0LknrFyLpqjKkvbprbjP8tE6HJS4o9tDdG8CHZ
eQFeSdMYehsE4WJfKOzallSVxCHKIEVLi+IiPUxkug3UQ6sWZRpUYeGnQJvX
9jxK+uw6cp3YMVCGhSGnOgCUWOsE3gsbFrLbBVeF1BSxTrVr/aFvT2+FLFyj
TT4ENlbWYRZVBlLSKSh4RSDCftuDwhIBhs/Xd013VQiJEXoiyXQOyj8Ep3TP
Axx0b0W2uWBvaOMzWY/4yKDukhEPRCnrWaL1CoWa71CZqDjvicsixQ2FJaPy
e/wKdnkyIJGLwf2cTTmLOsGx+tq8D+iUtZMEDjSvMaC4hzO9hMk5vAduK7ST
bGsMbQDJA05ABSCL0VFIopbEX66TblAtssCcIubVLUEPalMKYeSXWrAmdaFT
HsqKKY6tXTNM9R75Le5jwTb6fNEqwoo8SAsu8smVhkkqG7BDkoeEzbDFUsAV
iodL2+U4QWFXLVBLW5TQm7iMNlbAL/Jfm07D6P8YFa9telOn05sv0H7TighZ
2L4Fzs1uWe1zi+BLybSovZB0kWAIhcpP1xhHE7WjHhSGV1A7QvJlOYZ2GfYN
cjXII1iChyQplhiNkoLGPbcCtreuKC7tynoOtWs2nglMEGxJOFoS1IlS6BMy
zaUr+jwwfn0LDiyDtIU2DrggAuVuEpAfIiiMZgIj2xnJDLS4J5bz++BXbRyr
Tj9kqwczDfyMrcLMveEajSculx40WRqY7iFXTEHcWUcpRO8t/Dag1KFPfPSi
dayulS04Y0u9+xaqkCykBC01uO2eqHT9cDUWHKU0R2VPR9a0WwUJb3c1WQtt
cRIk64QFFbq7zduExiKi//PZsQ6yKC/MxmDnrYKLlbbbIEQX5Oe0kHY10tqc
M7wchWT4Zz4+mrv8USU7XTM/avm6PfIhnyIx9fUK503q0IuF905dZWFAcTQ6
RvoEi6bp1mWDK23aq9q9hjzavMP7L9lNQ8+AOZ9wKs0sLze1dKFd0ThWObxT
raI3kMjw3w6t63wjZRlV7r7QcUvVKWEirnd7rS9VLDIsPpd4rBYg/T9XqIML
X661tT3jjhEBNCxz++iq21psV6vfI/V9WzkJeQjHFONOcwSCGHiUHcDc2MSL
lDlReVLLGnrsKOr/YWHQadxuQj4mlMJDn9EriSYa3dVlscATl3qC+9lp6hpw
nGccFt0lkWDUp2vx8SVRQbq8UTx6nIlo3RGYULMm5JRwifDxPThVahPhpXlM
6qtwWqwmTwVeQBmqGrLaKyhIxZGBcV0o9kP0VKYPmpLxjFx+oM90jssuIEaL
8LDwkcAkdl5ZHAgnAzhzDxsVKAgXTs1uJciKq8/Je59fghgodJoqW7B/i4Ol
Vg+SiGGZSRPyGfyPSmqLrNiwaRj0VZSseh/5s/ez45b7HojflWjxpVXqEKeU
0GC77AmrEq2yN0G6PvcR6C3fKnqudF5x9eIlypcLTA+/Rb7IEAGh+F3zQopP
UmLfbCv9TilBeFt86dit5AMeJn/kkddGRFopn1k5h+QkZ7yV9q7awMNaDvWB
ZOnt6FNpClIbtIi5b8lScnUhxVRXFVNac9YRDjKNeKiOzUDlBTzl2iorHAEc
FHoxrbrsaCsIiyhgpY0fTEZYL0BXdyZsIehK8bpaBsaiDfUgSFDs8F9cvYuw
UO7WyDJa3mdPkn/N/+BTxaWdPWK4Qc6N1rjeujJNdLjCspu8eB6Blc4+cg7U
x6htTRJW6pxjhCsmkLgruvOCzcUqBnSN9AT8JkyvSJna9HyO1MOj6DsZCVKq
WNAWzF1It+DYEg6bBpo1O11gy/PoW/Equ2ySLz5LjuFsYjBxBn7YjYC5gcer
BAkNDk62LmHuaKA4zBBxgeIAN4kLEaeRspFOWfPBV2YttEBc7a/UVB6DMzIN
OdigAiTb+f/ItghlZAAti5JJYkBerkVBUgmQmp0aK8Bjlc+liQwk9QYr6sHB
tACLbB69IkgbCZwsEh232KIhsnbDsNo4Ds3siXEcxDU/BmGzCKjmYXSa7SPN
sG0OWobdNLcuzqID5XZA8x4wd6sIRQhKEqOkleD3O7hvgDJHTEzzsBNS6orU
puy9hm+W7RXxXdebaU2SeIOStOFiePjltdTj5P7YS+iwwtui3ZPf4NasGvFr
+3CEKX9uk8TZIK5lRF4AKjXnqyFaDhE9nRiLIi20jc2nUb1I5eyLErheplse
XYtJotll1A8EC5lJ9FnvZaheI7jUmT40ZvA056jVhBm2YfxeUk2Bk5rw0LLR
Cxnr2FDb4iEoyhGq808iVJrgjGW0PhTMlpuLJbVSg4LGjVokBdFnHY0afbtq
XvGzsMuho0oOii4cnLjTDP5rzg2yObhi+XF3Y81nD85yBBqIYGSTP6YMxg1+
B18Nl0AOQJCUFafah30daaT5x6xT6U3OP1zqyhV62rGGrzGEIr9/V9WDAJLp
Gb25Jm95k/ZvvzbtPEqPrw1hx26pmRXrzLWgi22JVW5yyY4hCiDkCbkABsA6
DLH4ILngLZy1fYaKJdsJ8eAG3ekybFvxsFaDWstzuGQE3qNTiZPlguA1u2kw
sLxNMdgxB8FVtnAUU2YEjabvw+MPFwS8TbNkuixnH0l34BqFYMGasG+44n15
rAYJM6eGo5qP5Lgb8kRqa+CxQ+2wi3ggLZ+MAXXUYYAEUNId2QqnoWfFwms0
q4IZiwslv3ftDEQC6z7IinFRvRxqtTrneWldSHI2k0AKrbmApuPGO2LWWXCw
5VLdOmNE0zLVters4NDv63BNGhV0p8wWUrRWeXjORRuFpeugUZdWXYuYor4M
x1E8WWg+QcZYYL3ckuUpmRe4Tmpnnb0765DqgwfJz2wY/qvFSsm25+vy2uhf
VkbaopsUQ5Qjlzr5/MVe/Ix6L3Ft1AFme/7s+Cn78wcjkMPl5vo6/zxOXMHV
UfJC2qsph0es6vzV1Wv65TKCfb9U5WC/RleSIIDMl4JnjsV5xEpNuqRvgWuh
WZwXEv5EX012VmP2HHr00Jer7Tr721ag+5zuKpw8f66r4C58RxwvWoiXXhUY
02VSO6MMncIsGUyNEx4s3r02gOvsnKw1GjHqW259BThmDZ99f/ZDDEc95u01
5RWCGJcSgzzav215fqQFqfDeK+MwBh1K9vkNB8EraDyybntai/D4+EgXzl8U
yrude3/ZVJtZg4KkvCVEVLQe9014xBAABHbGSX/RRJ+PvKuqHo1zNIIJh2MX
5zfJOLl+Hac2DQbvSo96pKkmr+Y5MTSaB+d8ZeagbcKkd7W3hdVKopOiM+0K
38vIKRIkkIX3xilS3YI4Lg90q2+Nzp9p6qzrcQC4rBuXlEgXc5SmIpE8eskd
d139XhdXBzaCbkqXgSGWa8nJb797ciIdeWNbgg2y1qCt7qRNOA8kKJ8WsmbV
YcFcxPILWUuuNXlkJrw3xx8L2L80D20UTI+g8RArvpBdKJyRx49c5m7SbH1z
8OBTPufuA61cNkSQnfLJP27ZQ03ySsK6GgXnIR4mrzcV657sYEUgPbumXbZW
yJm4jBvXXFLuzD1LswC1Fn/WcD5nlW7Wrr0uFgMafz7dsNz0FeKsx7T04alb
XTqnUl2a+5PMxX+F2HfapMtSFuJTmi8BoenQV6UWx3WG0oH1Iepqo8ATQxXn
n3LNNfOrLFp4+0nMxQB5kZIWZ+ekAv1AK2OhLhhueWMGoom499UiLVQtFMye
3rfvA9oP6wM4NzzvpQsvRUdmeTm2NhLqAuxUwfdtrjACV3eGtRqG/Q8tPS4q
9+6LuTTJpLcWORs1MACAkRknAMTYj3sT79SSymNy8dBXbTPO5Pz16jjw8Inz
C3PpIokENt0ic3Fa9qrqBio3rFGwJ4ro7391SJ/to1fzk6dPj7/bVVoSrhUU
X/tnVekbK67rLpISnhOD3s+kQqFelX1es9eVfu3zYLKLwApDLUT59ovBP0pt
4LLaHlgpK830/mzFxRikzTWHQxWfT2BovtaKUKoQP78HrakV2xykUnw/RtO6
+S3XdedlQvtCYR0MbESaIRbOSidIiRJHZQFVcYUEfnRorA/7huMv95ch4i/d
e1qV6KOyTI0vW9sZuqaIi/3X2zsrgrO6xiF/LahVI5ABnljD1S7/Sft4aOg3
OuwS6emuq59NZ3a+KY32blFVXmr9bpaZNYRESXai3J1N4Hb0lZsyq7xJiX/D
ANIm1eZQtQKbvr0T3OUPTXtMvSulkBY7O0MkcRFvGCou2ZtW/Jornu9Pwk5X
B1LiF25SCYuEXWLZvFnGNT/ptMEfpu97rX7g2sxKjzQ0b6w/P+wnl7VkEu7J
dtpHmtWwVQ6DKXnkXOqJplwNUX1DbDDv7g+K5Vneh+UqNt43nnk8cZzQHzul
rX8RfJDwmWcFJtf2Sg9tmR1QlrZaFP9/IeOVuyvV+SrnIuKNlL23tx4dPn7u
sGBEkbTjo4/J27z4kcs31h8z6QG2/zH5Pnn25MDFeshaGGH+9Q1iCrWPAjHG
6nj4lE6/1DWxChKBD/28dUAa7mtde2yhJtQPwxwstn3hO4RbvpJ4WafaAKwK
zsPUcOLcNxLCS07VzwM/3TRbpNBixeH/9MQ6QCo+qfZITbro2ZH93NVKxcPQ
mAO/N4/TSdRyOXduxVpKXXLDA9GjxXzjchqsG7IM6ri+VaSpj/H4aUImCHMN
qSzQSXuP4xEGFeykIqO2mX0dZMmJj1JqA7dSXNsJlFatRClfmD43HpAqCtFA
eJn0yVy3tj/p2kWs4wTeq5soJz/Soli0p8ulArpq7+kPFUOXvY8wxz0Z/NJu
EA3MS4AmduXo7sg7DrMNDQUA/L0saeHrufuqiVpS5NSm4tCDyN0PIinsZK2z
5SdEB2rtMS7IEn0Da9eulbQ8BDF2rpVLKnrg7DQHqZJdZOP6FGAhnWIrJdhw
QIgvLThpWsvgAQuz0aJAVvXMp9LNeGumFclnrhyj5ek70IbUGyk8lxfLcjO/
ZhQHkpBQnemVhCmHyTtmKL/iQ7MkU2iY/JEPqaC8X/5KymwZmQDDCDihtp9s
jb6O3jG/gENvvdwwPErwCqjjYfUHDp8cHp1GZBXXFA+m0ypw5k0HJntvD4qH
FWND30OgDHIXl1bDg9nVQkw/ss6lyeHUofIs/0UO/jAojeNti7hJd+6TZuFa
1aiD79W9j5CyFl0G0kwiEgCLuHoECF6c0v2iLvuEWauSTIKjGvokXfci8VcX
yN0PfLw9NSRPEymWKSn/VhBZ5W8tqd6mFJwboRvcNFoC7aZTVg6SOhWvSgby
zFggAXKk/Et0Ya/ej2ULJngPQpnu1EX1f+O15bnEinNQvr/vvVJcA88PQZbi
eAjqpdZl0LlHVC4O1+e2BlEBw8Bz6BGqTNmCXW0VxenHqQ6jqn++jSnnUKKK
KEs5DqdaRleUfgMGodVG27zZECkiJaXPhxgLEG+DwVu290iFQUrKpijUqaga
rBSGwI1OFbcOPETK0vr5lJFN6En+gifEHc6AWwizj1jDWzdjzeYcufI4Abgq
AJtL8flpWue++n03IIhfpIVSZC07K1YOjSG5LBCokRm3/ZL46lvg4G1005xM
A1feXdp2YdBDsJnGugH69FZakGU6VT4pbEc1Eh9tiRinsqQgrjHd9nkOZOTG
5nxJ2VqQXnj5pKfjxeTgVJR7n1NEL4jMaoa/aFcbJkOfdWwN/khfkDLiqvlJ
Nhiq8ATunIPTvj1qNyrSoxmqDfrVOzoUn4fJ2RrBVP7hRTqfb6PVOnUWQZsU
CuVJCmTzlc8BbrdeTkUktdz53WZNt2e7KZ8qv2zE+xyzXcJ08+1aOyO1F3Je
75Yl1EEoC/+uojfZh6tiYdgnCcA36JxkbR8VCKKv7660F86xUJdJaIMg5cYi
6YYKfcmBeVffQldqO3CEV+K41Iqv4xDdaEa9064Etw27fgMRFnbERD5FxGBX
tFBkOTdBU7i09urYyJ13/Fvivj2OmodhIRJfmD8opuHHC+CYWi7uSPafdEwG
Ej6c0WZdc6WWlRsxSIsZC/DMxlVkg0NYvDZ2S6LcB/TrCoBzkt08ub29nUh5
C7KqZbTR0MT8D1SqKNffpZIJNUkLICZV52Pilj+qQkkiagvRmtVBBfCQ+YSd
TY16MOUwUV98gTtafaTBsLC4mo/iW/rEvU10Oy0TJLS/UotxK98zIFAbieJT
teItb4UmvE7KBa1pW/f7O9hIV/J2/xdm3HmQkBE081qV7HBRh5OkxYzm2Qoi
x/q8KjBdUbJc8h+4kQx4PF4noYK2Vu5VKkN3+CNPrA8q+8nh08PjAxGBuFDq
Drs+d+FeBrWBOWNna43bwHHPSBu7lYOQBOkobspC8xIgsWPT6vkYFgN1p1vQ
yNdJkIVgFaCtGeKZvlZamSdnF+fDxNv28pt6vH3z4LRRv+EMZRkBc+KwG5jA
qYS/fAQ5Xy611DvUNRqAywwx8olH7GgTGWyidST7hrudbhyGz1iH6H5vDlyb
u45vl6nA6wxafngwcMnIBi7tMqt9RxnDXnEVyZChCMDdsisQbyLBDjA0JIkr
CPnu7ur9+zeX7Jz/4eLN6OTwaFRWI8m4Nv2vTa3D5O35lftVNNFYEoktBbUU
6ac2YeH5EuS6IMO7lJbcWdWNZUWXt8JXZ4r9HSG9V55AzNCly/Cw9PF1Q5vE
LsNlPq2AJTNfShpINUYMLK3EY8iKXckO7bFtgOWhi39ozKw3BuLOodwst+Bu
uFFqX/vBgV6V1QamE3xY2szeAUhj6+FddnvqKmgoMwhMgIcCT25ZCYY3Adgc
zo67O5quuIM4buB77ew78LQ22AH8Wj4OHb92yG6u2azFM2zK0s/cqiDGZ0ZP
iivjXbi6fZYy0jo6TH2OboWYEJ2HuJnmS0QDc0YrnHXqgMf+A8vQg+sVwQjE
x+QEe3EaHJKTZ7IhAEGmkLAnT7DDIxDRRlx9aKjF73OLOEyet+kEi5N2brA1
k9V4GneY5cv2Tx4bAaGBn2QuMsSCW9bbeZiVVrIYFOH5EXjUgb7M4kKH0gq6
HZgWbwIccgqkTGtt6A4T+lQ5Y2uEsRIVSCZTPLyQboeSOBG+PQrEC6BcgCEE
ypp6ZoJsJHbccERGpy3cSUrMaE433OEsJqaZNqQDiEzwN+9R1sKlSMOx9HfF
sqCcXpXFNX5lqIUlcXbU47u7D69en7+9eMNUAU+RQD9NEVTDWpyBlYT/wXUm
HG437eQRHyqUGJmIGYEgOOfMpFwx/uTZ6Ph4dPz86uRkfPxs/OT5/8KObOO+
DCi4oGBxCbqxdjMXz87c7Qgdqw0pzVtfj8tpFnwJVCJXOJfOBXEezT6TWBDJ
uwaVvQ2TUvOs8mo+EowtqQ6GPKj0zQjtH1jt6xncDk3y0+XL5Ojw6OjYORK1
JIDT2Vw6eyY1yRUDw1lyQVqhVJTo67slXESVtQD/GfRMp53/LXkrO578JllO
yW+D30ajEf5Pv74w+KPEcX7zG/KMr0w+KETB1Xty49+fbgNLwHl/O9aAlL0U
md1tHkl7e0BvfTb89vExXvieo1GlRLvjSAmvhLi2fkseD0/0ekXtwtHhxvZb
chSP3nd5REt4du7t/9dsCfbGcmoBl3Olp9LTplV5W+9+mnTi7i4BT/87Ge5L
0MDM2yTwLvF0Tp7SBXdjafLw/d5VeFLl8Ab7RsTgj9XeF4FPu7Vx8G90bDAI
isT7fihL0m+kVtn+4+GTJyekNJyt0r+UBbHLZP/50RF98cPFFbve9r89/vaA
o6ZNOuIoTlWkS7EK9589eXbAmmRKggCXPnn2XGTzqyWdvYLmVb/QOdJvz5C3
zy6WdT57KKT9lvGKKZcTjKwcC6gFkGHBmPNqu1l/6/3keeUulC6ymKhEWNnD
Jb7M3KcL6xUW4TADajBw7dpmqYhbDdBHzAlmYz1uHfMZI3BRxI40++VHFlT0
VpxardtqFXCsGSbURYGMMYvntKd3Ugc4n3uM2e3NNkS6GDgkCJYUjjPgGskh
8Cu6ZK4u9f/HHYMiMNe3GoXwxvAu5dNuctFx+KDDXlTEaTaFIFxn5aLgzECo
SFZP7e7u7N3Vjx/eX5y/GL34cPbzG4MwmpyBQ85XiMLbZItHLonXTVEWMiyP
NHm0XK7wWeFN/Tix0zY0U4ITqRY2kFhnoU2BECVSBSH0gptSUEjjlAcMsC+S
c657wHKeTaIRqiDUf0dp/29MxtAkvETXxFtORBELtVUiTtKMgCJ8mLAPj8/V
mMaUWrYz3eCyE32JMZWDziUlLrqDuBcYunsYG5eudLOqrGsEwwyos5pmc4ZK
Mj8hwyNN1CmlgG9OjNushzoPBuED4WieAjxVndXdKi8AyZdBLhHRSMU8hygT
1duWVgNOKu/QPsp7JCnbypC15i2AZmi9Bte14KbcLQ1c0KuDhbWVLNCzqTut
voJr825a5wSuodEOPPYFgwQPKt7p4ATvd/vi5f7AWxsWDukUmYOuS4V98a86
Z9J1wxUD21PU4MrcjoOuF2u6utHs7lmlv5aVWxWeZJr/IucLr5K7BK6UTpdc
XYezpVAA1DWPRVPBkW2c4qZ93dwebiQ0Ni9R8y0oz2lQbEvoRQzrcjMlLiy1
FjjxV4KGIFD2aT+aBPFBsaxly2q5T2iRVzFMTpYihGQeNDcoPcDFviV/ix75
Db0loi9BG6ix21poyREm7Sx0Q/hkzG0GcEW3p58PKoJD4qgB8WvOUF+YpQiz
xFzFj6GLhWny02nkY7NCG5ZcVka1QlCH3xfdEYeuBK+u2c7m+TCyGqNS3gTN
t+JCavUN8D1w/QVM4GFUGj1oaBjuMdQBIX3pIwOlXFwqpoX1Si4pTGhmsMnS
1Gon6QMmhZQysxc2XibUhotCVWlzroQtgY959rsKo4rrIugffM/FQ7yt5uOt
kili6Fp+3eVm8QECecedWvEQ7f7p68JY3U5rLvp7zUQDCE1cCoZ3HB49O//a
IsN5mvUJMb+GFvTi7PxidPxdyK1ZekpSkxojo6MTUomlNkA2/37vmvSCjNXd
ERcss1IFpGnNpaUzAzfhHlDG26IDXz42qhiLghzSCo3PGOcAiSueRr5ZNlao
diLWykRKS4/YN2ZCegxS4r3xJUTvATALXNk7abRgditeGXci7riC96PSQV+B
9D0QWoYdDf7Xi00Vph+VoxV8DKr6RXVseREumB9qfXttEq8uz5AFnyaosbQo
TSKKcg4uegqOvALutEFIFwipU4nEmY/Ul6aw4vKK67NW3halVZdhA/hXxo9H
KzPB6/EIBRUc4mEaddacegbtkzj6ikqIrkrEqThKpufVNF9sUAMJi+nQQeLH
YkGJa6WwhsJHnB3dcY6xBh54DSU241QR7KPrrD4Cwl7SPwS+u7U9QCPQIKjl
miSxVByx9ebrB8HlpwVij4iN7Ud6iVWOZbCxVqw+CJjN1zSiHzreooqOtpu/
r7t81D4+5j2nQRKHxPUzstpqp8cb2kdwlDtSQVqYndNQAzQwQehsbNey85ig
3fXsdtd1OxWt05fx8w1Ug+rwTjzpZbSENdNVBBB3UYOiDKHhvMsh1nxXU9Wg
SEe3u1FcgoIfGcFNIGGCpEFxd14xyzl1GMdPUn6HD7D2PIxhKnhqbzRV+2VY
p4QwYsyGdN0qHVALUt6vadR2RWnD3ZK7sHO7MubIl7fknehPW2eMccrZX+O+
6oqKrFKoWLuu2zwuwTQ0fi8lfsDMqqCgz9BVhfClJoaAQXM1D6lNbeWi8zqq
060+3ABfysYXT7E3z3K8O5rQSWMZ7gq3tJNi0BbCHAs9Qeo2ysgi008Oj7AZ
L+38jAOPKGNqG/C7qSCG4qKV+7+nah4YWjI0ocK6+m4DmhCNabBotxHWJbJH
Mxf9+jTIKrLCg8B0DlmrmJHxPuG9RCaK9I3C1OwVChcNund7POU9Bfxi7Tyo
RGiNDIlREzd3KrYc/aDxt+r/MZMcJnExQFGEWAkr5owTHffFO+gREvD4Ij7C
0EdCv4VOEi0uezaz1vNgUP1q4BVJoo916BpnrmZ7M6eVXrJfqlZwkR4Ensym
NnPVO7wNZVbfpGvtrbFBHK6LT7M+wVEJJyNvK8pMTJPO9uHg/wG+XQlD7wMB
AA==

-->

</rfc>
