<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ovalles-ai-terms-01" 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-01"/>
    <author fullname="Damien Ovalles">
      <organization>AIPayGen</organization>
      <address>
        <email>djautomd@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Web and Internet Transport</area>
    <keyword>AI</keyword>
    <keyword>crawlers</keyword>
    <keyword>robots.txt</keyword>
    <keyword>well-known</keyword>
    <keyword>payment</keyword>
    <abstract>
      <?line 63?>

<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. It also defines an <tt>AI-Purpose</tt> request header with which a client declares the use it intends, a way to point to the terms from any HTTP response, and how a paid access produces a receipt that records the use. AI Terms is designed to sit alongside the Robots Exclusion Protocol and the usage-preference vocabulary of the IETF AI Preferences work, adding the pieces those leave out: price, payment binding, purpose declaration by the client, and a record of licensed use.</t>
    </abstract>
  </front>
  <middle>
    <?line 67?>

<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. Automated AI systems now access web content for several distinct purposes: indexing for AI search, fetching a page live to answer a person, collecting content to train models, and acting as autonomous agents. Sites increasingly want different treatment per purpose, and some want to permit a purpose in exchange for payment rather than refuse it.</t>
      <t>The IETF AI Preferences working group <xref target="AIPREF"/> is defining a vocabulary for expressing usage preferences <xref target="I-D.ietf-aipref-vocab"/> and ways to attach them to content <xref target="I-D.ietf-aipref-attach"/>; its charter excludes technical enforcement, client authentication, and auditing. 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 explicitly excluding licensing, compensation and payment. None defines how an automated client pays for a use, declares the use it intends, or receives a record of a paid use. This document is intended to fill that gap and to be complementary to all three. It addresses four things:</t>
      <ol spacing="normal" type="1"><li>
          <t><strong>Terms per use, including a price.</strong> A use can be <tt>allow</tt>, <tt>paid</tt> (with a price and unit) or <tt>deny</tt>.</t>
        </li>
        <li>
          <t><strong>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, <tt>AI-Purpose</tt>, in which the client states its intended use and so accepts that use's terms.</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>A reference implementation is deployed and serves terms for every site using it <xref target="REFIMPL"/>.</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>
    <section anchor="uses">
      <name>Uses</name>
      <t>This document defines four uses. Every access by an automated AI system falls under exactly one of them.</t>
      <dl>
        <dt>search:</dt>
        <dd>
          <t>Indexing content in order to show links or excerpts in AI-powered search results.</t>
        </dd>
        <dt>answer:</dt>
        <dd>
          <t>Fetching content in real time to answer a question asked by a person.</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>
      <t>These uses refine the categories of the AI Preferences vocabulary <xref target="I-D.ietf-aipref-vocab"/> (AI Training, AI Use, Search) as follows: <tt>search</tt> corresponds to Search, <tt>training</tt> to AI Training, and <tt>answer</tt> and <tt>agent</tt> are two kinds of AI Use. The split of AI Use into answer and agent exists because sites commonly want to treat a person's live question differently from an autonomous agent's task; the author welcomes the working group's view on whether that split belongs in the vocabulary instead (see <xref target="relation"/>).</t>
    </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.</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 per use (<tt>search</tt>, <tt>answer</tt>, <tt>training</tt>, <tt>agent</tt>), each a Use Terms object (<xref target="use-terms"/>).</t>
          </dd>
          <dt>default (string, <bcp14>REQUIRED</bcp14>):</dt>
          <dd>
            <t><tt>allow</tt>, <tt>paid</tt> or <tt>deny</tt>, applied to an automated AI client that declares no use or whose identity check fails.</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 (<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 any use is <tt>paid</tt>):</dt>
          <dd>
            <t><tt>protocol</tt>, <tt>version</tt>, <tt>endpoint</tt> and protocol-specific members (<xref target="payment"/>).</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.</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.</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> (decimal string), <tt>currency</tt> (ISO 4217 code; <tt>USD</tt> in this version) and <tt>per</tt> (<tt>page</tt> or <tt>request</tt>).</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>
        </dl>
        <t>A client <bcp14>MUST NOT</bcp14> use content for a use whose access is <tt>deny</tt>. A client <bcp14>MUST NOT</bcp14> use content for a use whose access is <tt>paid</tt> unless it has paid for the access.</t>
      </section>
      <section anchor="paths">
        <name>Paths</name>
        <t>Each entry has <tt>match</tt> (a path pattern in which <tt>*</tt> matches any sequence of characters within one path segment), <tt>uses</tt> (a partial set of Use Terms) and optionally <tt>payment</tt>. The entry with the most literal characters in <tt>match</tt> that matches the request path applies; its <tt>uses</tt> replace the top-level terms for the uses it lists.</t>
      </section>
      <section anchor="example">
        <name>Example</name>
        <sourcecode type="json"><![CDATA[
{
  "ai_terms": "0.1",
  "site": "https://example.com",
  "updated": "2026-11-16",
  "uses": {
    "search":   { "access": "allow", "attribution": "required" },
    "answer":   { "access": "allow", "attribution": "required" },
    "training": { "access": "paid",
                  "price": { "amount": "0.002", "currency": "USD",
                             "per": "page" } },
    "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" }
}
]]></sourcecode>
      </section>
    </section>
    <section anchor="discovery">
      <name>Discovery</name>
      <t>In addition to the well-known URI, a server <bcp14>MAY</bcp14> reference the terms from any response with a <tt>Link</tt> header field <xref target="RFC8288"/> using the relation type <tt>ai-terms</tt>:</t>
      <artwork><![CDATA[
Link: <https://example.com/.well-known/ai-terms>; rel="ai-terms"
]]></artwork>
      <t>A server <bcp14>SHOULD</bcp14> include this link in HTTP 402 (Payment Required) responses <xref target="RFC9110"/> to automated clients, so that a client refused for payment can find the full terms.</t>
      <t>A site <bcp14>MAY</bcp14> add a line <tt>AI-Terms: &lt;URL&gt;</tt> to its robots.txt. Section 2.2.4 of <xref target="RFC9309"/> allows records beyond the protocol's own; crawlers that do not interpret this one are unaffected by it.</t>
    </section>
    <section anchor="declaring-the-purpose-the-ai-purpose-header-field">
      <name>Declaring the Purpose: the AI-Purpose Header Field</name>
      <t><tt>AI-Purpose</tt> is a request header field whose value is one of the use tokens defined in this document:</t>
      <artwork><![CDATA[
AI-Purpose = "search" / "answer" / "training" / "agent"
]]></artwork>
      <t>An automated AI client <bcp14>SHOULD</bcp14> send <tt>AI-Purpose</tt> with each request to a site that publishes AI Terms. By sending it, the client declares the use it intends and accepts the terms for that use. A server <bcp14>MAY</bcp14> record the declaration and <bcp14>MAY</bcp14> echo it in the response. Using content for a use other than the declared one is a breach of the published 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 that fails every listed check is treated as unidentified, and the <tt>default</tt> terms apply to it.</t>
    </section>
    <section anchor="payment">
      <name>Payment</name>
      <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; the client retries with a signed authorization in the <tt>PAYMENT-SIGNATURE</tt> request header, and the content is returned only after the payment is verified. Settlement transfers the stated amount from the client's wallet to the site's.</t>
      <t>Other payment protocols can be bound by defining their <tt>payment</tt> members in a future revision.</t>
    </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 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 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.</t>
        </dd>
        <dt>AI Preferences <xref target="I-D.ietf-aipref-vocab"/> <xref target="I-D.ietf-aipref-attach"/>:</dt>
        <dd>
          <t>The vocabulary expresses whether a usage category is permitted, and the attachment draft carries that in a Content-Usage header field and robots.txt rule. A site can keep expressing preferences that way; AI Terms adds a price and payment binding for categories the site permits for a fee, client-side purpose declaration, and receipts. Where both are present for the same content, a <tt>deny</tt> expressed through either <bcp14>SHOULD</bcp14> be honored.</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 and has publisher backing; AI Terms is deliberately smaller: one JSON document with a directly actionable price per use, 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, the more restrictive <bcp14>SHOULD</bcp14> be followed. A mapping between the RSL payment types and the uses in this document 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-considerations">
      <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 for allowed ones.</t>
      <t>A client can misstate its identity or purpose. Identity verification limits the former; receipts and independent detection of copied content make the latter visible.</t>
      <t>A malicious or compromised terms document 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.</t>
      <t>Terms referenced from another origin <bcp14>MUST</bcp14> be fetched over HTTPS. Clients <bcp14>SHOULD</bcp14> cache terms for a bounded time and respect HTTP caching headers.</t>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>The <tt>AI-Purpose</tt> header reveals the client's intended use to the server; this is its purpose. Receipts may link a payer's account or wallet to the content it accessed; operators that consider this sensitive should use payment accounts dedicated to automated access.</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>Reference: 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's origin content.</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>Reference: this document</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="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>
        <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>
      </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/>
            </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/>
            </author>
            <date year="2026" month="November"/>
          </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="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.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="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="TOOLS" target="https://github.com/Damien829/pay-per-crawl/tree/main/spec">
          <front>
            <title>AI Terms JSON Schema, test vectors and readers</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 325?>

<section anchor="implementation-status">
      <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 402 responses, verifies client identity against published IP ranges, settles with x402 and echoes <tt>AI-Purpose</tt> on paid responses. Client side: an agent tool that reads a site's document before paying, refuses a use the site denies or prices above the caller's limit, and sends <tt>AI-Purpose: agent</tt>.</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>All of this document except signed-request identity (<xref target="identity"/>), which is not yet implemented.</t>
          </dd>
          <dt>Licensing:</dt>
          <dd>
            <t>The site integrations (WordPress, Cloudflare Workers, Nginx, Apache, Next.js, Express, Django) are open source <xref target="REFIMPL"/>. 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"/>), 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"/> and <xref target="paths"/>. No payment.</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 (validity cases, and path-resolution cases for <xref target="paths"/>) are published <xref target="TOOLS"/>. Both implementations above pass all vectors. They share an author, so they are not independent implementations; reports from others are welcome and will be listed.</t>
      </section>
    </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 and the receipt design.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA81c7XbbRpL9j6fopX9EyiGpj9gZh85kVmPZE+3altaSN5Mz
Z07YBJoUYhDgoAHJXB3Ps+yz7JNt3arqBkBJzu7sn82ZSUgQaHRXV9269dGa
TCZJkzeFm5nRyZm5cvXaz8yFqycfvJOvY3Nht2tXNsaWmXnvUpdvGm+WVW1O
2qZa28Zlhp49SVPnvWkq85NbmJdV2dAzo8QuFrW76Q0/SrIqLe2aXpnVdtlM
qhtbFM5PbD5pcMPk8ChJadRVVW9nJi+XVeLbxTr3PqdBtxt68OzV1esk39Qz
09Stb44PD787PE5s7eyM346ZntEE6tI15qq2pd9UdZN8dNvbqs5miZnQjPHv
tLa3has9PtfVomr8tPnU4NutK4rJx7K6LfFtIyJIfEND/2KLqqRZbJ1PbNtc
VzVGTAz9s2yLQtZ2ate5K825LI5/rOqVLfP/sA2tY0YTILn+yZX8k1vbvCCB
/Goh0uyfV/g+Tat1UlY1iTi/cfQO8/71y+Ojo+/04/Oj3z0NH789ehY+Hj9/
rh+/Ozo6DB+/OYyPHT+jj5Brb+Q/Pz08nvFUgjp8whWSpKk2tA4VgNnUVVOl
VWGqG1ebH6+uLgzdN5Inbb1yzcxcN83Gzw4Obm9vpxhlSgunG2jB71+9Hr6E
lOKidktXu5K0x+xZ2lS33Dc/VfXHvFyZP9VVuzHpta1pMx9+S2Yb29Q2/ejq
ae6aJd52cLs6kKEO7KJqmwN+ku6kdx4fHn87OTqiK2eTU35iIrdObqrULmYP
/GCbxqbX4ZfU1qyrn5oJlIR1JPxWu7wotuE52r9NkVta2mDUW7cgTYPmTHgR
+WoSxKpb9LvvnvJuvL98M5TXe0fqtDWXOQ3szJs8daWHnPbozn1zND00lxuX
5ss8ZS0TiUUd5X8m0MMZhiYjJd1MoQIPSrb2Beu7rTMWKn0fyvHZ5Oh4cnRI
F6/Oz99c3ttatnfzL5fn78xlek06PjaN8425oZdWtWczJZvNyAC/MNOBoezO
cZU31+0ClnIgFvf8+LsDUtbJhjCMrfugqZ07IHsqDzzJ5kFNIL08e3vx5pEF
RAU1LHbYwW9J94tzJu2w25UredYB9R6Y14TAGf8yduGh4U2SXF3n3hB+tmyM
mVvmJZlNh9xWpB3v2LSLIvfXhNC2Mc2168Ga+fD+zMwPpt2VOJc5oa65vc7T
axqQtNXnjTOkCrR5YwZ+R+ZgqiV9bmvTepoCfcnJK6QC+2axNbbvHPzWN45E
ueedrdPrMW29v3U16UNNGwMNhi5YEkqzP6ZXO5przROm0Q2tmdS+unXZOHzg
aViCIzKBMcnclFUTfpuaM3z2VRQQodj85Gxy0dabyrs57ejfWijiNSufuSUl
iutNi1xkmxbkUHw3iYakQovLSAYkFbuFq9tUdA0fcBfLzizrak0v3Ao40gib
qvRuzAu8rm4xaZvTWsVdkuFnLaDP0q3sWmko2iv6Qp4qvn0a9xjCyBxhRklC
oBfT3hj4o5XPM8e3v2c/Zl59SosWLpMQVjEbU5ABSdKTTafXjHwtrXeLjcQt
8LBmB53Jd36kdWQZ9gs3bXKXsoRIqKZw9sYZAttZ2JXgMxZ5iUfogshfZcs2
BE3BUCJ1kZLV1WMuBUMcLRVCEGtY51lWuCR5AhfP4sNAsI0vrf3uTr3g5880
1QYCF7WmjQz6Zg18dxZYgVnTb0vXsFpsbHM9HTKeoNQldlW2k4wl2gA01Dty
k7YwWe6bvEybIAIPYpO5T5AkMykaTS2DX8gWQe9ckVwJnrHRYjG4SnBZlWN6
j6A33RpeCUWEQZl1lbnCqzjlHuvZJMtqXbVeTM1PyZOQUdNcUsJheBJyLrcW
6p8ved9pTPqlETCh1+v8ZWRfrZ3cDlMg7YQuxl2mabhP5LpLWgTWGNSBNl6M
m6yStEtsayr795jaYQEr5gJ3d8IjaBvZEpYKH30dZoj6RPrt2TmyuptNb8i7
uwd9P42JZZFtM48Vtw/1XONrEPL9h+XGz59fCAYKW8HiizaDfbj0uiSPXBgH
0pWyBxkHoIH/oP+qx9Yta7Mcm0ZIRqZzk2ctdAhsGRAL5lW6fHVN1KYOkimz
mc7sIX5CK4uApuKoyLS2/LYiLz/KgtXcMCY2jMwYH6GGMi95wWMkh18igEtT
JBJiF0RSut8jqBHU0g+0Q/Q6crZbFRXeFScw5gfps8AE3q4KNDXviH7HVzGm
lj13o3LdYBfFS7RQ2C8COt3G8HsTkFjhR8GaEXjoe3OvTwsML0kkgtwruxGg
rcxCVy+UoWaPYfk+oiTipbIMWuq8uNIGhu9nSXI0NV9/LXgPq+MFkJGqkNTv
Tb/+2pzwUlISAL1szg5wPjZzzHpu9tix6d08qbbMm32sdp65cjufJsd40cUQ
qDHuazZYWTrJp3NvQEgWy048gNFJGuwQd2XFDCHECuJtMSBig26AuzvEIDBB
2aJlXvtuSsk3PNHfciAikqF7Hw98/7jjNt1jSm7YfOOuQrCCcozuCHp5g+n6
V16kMU2eYlohKJa3s9iC36etqevcsaMnfaL/bXrRNGagepl10Loii6ddJk92
TXfXTb6jlDs+8eRRgioIuSmqLQggluLqG+cDUQFKkqFuxRG2bPY58E3p8OfP
NPqTJxTz/63Nax7WmzeE5y0BguA1RdTAZ7Lp0dsPl1ejsfzXvDvnz+9f/duH
s/evTvH58seTN2/ih0TvuPzx/MOb0+5T9+TL87dvX707lYfpqhlcSkZvT34e
CSqNzi+uzs7fnbwZYW+bgeqRZNUSsa81IRYgwvqEgDmt8wV9oWf++PLiv/7z
6Ckt/Z80xCY9lC8IsukLUQTF5qostvqVtm+b2M2GPDdGgWmndpM3ll2vN/4a
PJucHbbp679AMn+dme8X6ebo6Q96AQseXAwyG1xkmd2/cu9hEeIDlx54TZTm
4PqOpIfzPfl58D3IvXfx+z+QN3FmcvT8Dz8k4GgfyPYfi1ti+DA1r1gRlUUh
eigfCiDMkmRMHqzM2L8Ss6G9gDMQ1romMQuNmiUzuE4hWMFx0xaRqoJ6VLw1
6viYLKSkG2z89LLJhqIIWKSMBVtuC7LuJBEOhsFfB5bWG5yIEmF7vh7SNYYi
dmH+I42JtSmFowFD+IMhX36Bz9EcIbJJ09Ji1xavdhNi3DWTH2F7mB9YHcY6
Kftkz1fL5haWwL9zyN1/SwXtvamYZAUI98J4ACcN8L6h2QtH807wvOZNFBCV
bF0ucSCu7FC4Hjd7nHrtIcRReYwxwgeA4SXvwT7MaVnBvRF1nsvGzGmCtQBt
xvO9VAo9D2Kd4+pgWFjwXPZmrl8gk7kAxW1lSAoZL0MmAFdGQQIxlaa7CCzp
djgErqRFxPJJe11q4Ts8U2uS4Vogw4YNJT4ddYA8CRP8qCWReNMjGkre4+1w
P7QfL1jUkn9AYE+vUnozoMx0903ubslOeoE1TUEWtXAcPApyDiLBvCSTsxli
dkfbVruCncrnz/twCyyXGJSeqmmzv3hTpR1pe81ZRngp9jIhISG+VhwRIhPJ
W3CQhvwkqUO1+JWs4ZG8hdz47dEzuvGRHMZYvF0mfIPCupy0eLsBS9qAePIU
D36lPRBF+HD1evKc9D+tmHDw+iJiEfJFeZAvoYAXuERG524B75rJUn2HfzED
/3J3RwEgE/ctogTfckjZuW12BNAZkKRL8bpv3XqBzHRi819ETnu+qVmJg4vY
h6ljnjQwR7tsfYS0vp8EJHsYHU6PRnP2+AP3CLzErjw+Mln1SlVDN4uEByJL
j7abjOH54adP6bcAB4UlNiahIM3mZ/pn8vbt5PR0jlEAJnuy2ztDnAPsWAyB
BZu9YPvjaMZ9ex8He94fS5LKmljICBq1d3dHI4mWiDKTP7KE8I8sZJdVR/Y8
ZmHkEgDsOiwllmxpMfQoK14EzJVzJnmGyK/Zkmxc+pG8W84wjlwDkuF1bbdj
E7ysiIS2us4z5zWkrpuIubKTd3f8tCwsjh/lOxhszmEaL4Rmj7dxHi88tCaw
qDQHxYPLcj1eEm6S9yh1/UXzaVGOw7eNOho+mkeqprrLyxZmfE8ZTL7kjJrm
AmUfZMwQPmB7dCR8DG5MTDvcNAl2oVrlRVz8VllIHcpbDy/hRM1600RrczFv
N0zsEdFs69LzmCg+/cJOYG9RVeS2y13RNHXr5lhmlHXa1uoF1s76FtrT6VfI
NhGyVS1bVr3iKCmBT7dp89iGx/Aae05I+obViAD/I5QybT29oYvBabwPpYBu
EBgjFdj0qqyIIglUdSZ296QzLUIumeb/0qygCRyw3tcD0O6w+B1FsOQesd97
ZGz5moiYvJRwYC6iTLf049nluXl6fPQ7csuZe2HmHy5P72nivvCCDRjC3hzJ
D5mcRpVz6IltaPRFy2rwiLbXEjVlWKE+6nSZJVHW+WyQ5la4yIV3sbFpZkZU
gpgySYTXHxlnCDA4cxMp5UkYK0QXkiHoJSU5IaII1BOmCN/8w8/LNrZlwRco
+iYvyBYhbifcKypzwRB390TAKkleAazpBcQ78Nyc9BwEb08Sr/gXqrld7D7/
em74Hs7uUwgLCcOVklHCHMgGoK6wENBnciQ8jnertdQY5vA7+gIKsaEwjile
VGbRg4ptnatuc4WKuZADmW3MZqyJE9CGNZzv7U2BXh9Ww84gzFqgQxIVPDdF
V0ki6vQIOwqbCstuqg1R/htX9OJ3zWWxvAuwT5Huq08WzD1J/v73vxtQnOQu
MWYUmMRoZpgRjHERaIMLoTrl5FkUp+QGdfO4RytTk6Nv9Sd6NV2/4+LVSDwz
fTfmjl7Gu42n2NARxfesBteDhYzM57GMIB79/zJCYAKYVX8EKOJorEW6/j8j
xhq9nTFEpHN4eIwXBuzARQKLB4cYjMbTHwE1aFLdwkBKeF3/P6ZFt/PURkp9
BnMZBecurxeSQJ//MorlxEm+mdSgc370Vx1pyAFGXECN7l7uEPORUYNPHmmr
AValAEyXju8taBRcel9XacSp6uvB6sAu0qPjb2hFT599e18io9I1iIvwPPnr
o2fPZs+fPvuGtcqT7asoX5J8ks8wHAQ5p4G2E1R1FD5JzkqugzH+a/VvGKHA
vXL8UXPs0FH9BwqFMVeo6dr5G4L9eShOLnNXZCEyev6cAh7J1Al+SEwWApsQ
+8zY8hOMMzPfP2DZD4ZMP7zAgL8fhe8jkcJJWIhmkiQP7cRnsociiIvZ3b2Q
TNasYbYf1+e1CHd0dEirgNfaydn7MZKtjJKxDisVomxQQUK6e5lr/hQtNyEb
G6JMiJz2hwsaBP3I/2qB/HviPD9wWgAo27X8TM2l4zqiOZ4eT5/CEfQrhgxA
PhYwFm5b6euDHlOUTbJ8ETuKlPlXXJiOuUcRGtwR8g1taSnYTxtJC3ERjFSO
g4Www2pAM82qBIMyP4pyvIZyJMmguJ1LtnhQ4RYlEpd9Y4uWeXSXOGOH3lQf
ifZpci67l0pVnerN4fcR8s1BxG58jCDM1xn6VJUeDpJUsbwD7+ovhQ2C47iw
HuY6vMcs3y6dEFIRU/PHLY8k2exxn119oQSkldKQ5ncDHytJf1CjgUlzPr5L
4Xc5D/zs0utKxldLFRuYEr/o5946PlV1VdFBWQC7xFu6qEPbBetd7OwIuv/E
nIXI7e5JjM86QkgaSkPmKHB3caGUShkXZB71RJJZ0pjQiFbsYwZQZFZT74ql
cTcYRAgX6RW6xGqtoQg9moeXTDXKDKE88xShTBpg2kF4OUM8ec/PhISEKsJX
PnBiLaFhhsr2mGvqVXlYlUAWLzMFnETlidusVaQkuXWLCWHDBNm1nVfHko5V
2FvTi1BSRVOGpajP9cufiukolHx5EmPJGkXj6yVKv9AwxjWak0G2gbMIWtmB
rAGvnF5AcIHkoySo2lI2iKAhG8dq1FwJwXwn3RPQKaA7mLvEzUnyE6ISFrok
1rDs3big5w8FKPogJaJXqZYVECqP5V6RIAp0rWcPE6Ya+wn65algHaGqKA0d
4OChehwzBlMucsZCpFYaYx1yHBl6HByYLdPMgl3PL05+fvvq3dUkxKjzzp0L
9r7oIxC5AF6kaoW28UgKVztD7418efandydXH96/2u1b6natFxJK3sFpncou
Gw0wg7TyUJxHn9SlaxqpF6LOUPqlOC5t9qKJMfMUptKtgmzvFl2tsfEJ1vsV
IOicMWy3NuxDfXqBNgVgSGzboPvzugusYpoB1TTy7GxMNUGNZoiexP5jdvUt
KxkRgJ2aq/oTbNWW0GQyEEDPYcearO/kwIgIhRjv7u/lxfm7y1eRl6n1bIOn
ljEyEaRlLrHPO6TvHzi2gVuGqwijRNiX2u5VtZIcQQwzgwogC87bT3AyFk+N
ht4vVIqlksG5JdoOLoBpz9tu64QYL1Ln/Ltql7T+yaU2tADdwnRvNdJ/MVSS
iHHxfWzoHKrqvAbKy142g5vd2XluxBJo7IwmpN00q4t2qg0K92UTQWBnx3V6
9/tRWI7cJW45qjIxDcg08Dd6XriwhjVmOQJlI33VsI3awbEP+53y8kY8DHQ5
sPfKiOWg7ZmgNZZakuTRhjY4pQ+l5NRZZhSehN5ITifU6CkHn4vXX3T1mhUC
mbIjQpIlzTV/EqqPvFteOtI417dT1nu8lvd4j1QsWXSFJm3VAizGRjxpUgrH
ADAL6S9r+s5KxpSSMpqjog+RmQND9BzC5AOPNzA7rtnEAMDUbSEUL1jIR+c2
/TayfgNZI2q/7YmUGIcf9NrstD+y9fQqpTHTKwsLvUpL50Jr2IRbOh9omhxr
vUm7TsxPXIPifhEoI2YcuCW/BS070YitZvqi2CHLumpXxLRzlr7CJ9e5Qpb3
5Gx69eerL3aYcdHnwSYzFG/iVrJosMcrno56wlChnbx2sebDQu41p/X70ab3
BB+q4gK9TEIe3YvYfPdQR+pQtmdL3fgamgdx9k7G9Ht5wlDBhYVaXKwhplVb
cPUwkDzLFNJ9apBt7+oJNp8iZRdwJJQduRvNuw2muZttGFSCcy9HNhoJpWnz
/r2joy879Hsv6Idt+02M6zr3pHZdV/AQ9LJqoVVWiACp9ywYaGx/jG17vYZ6
hVf1VLHRTNaBMjwMMK24oh6aggkTXT30CQKweTeSyIyW/NhBCQrqL9+IruIE
BE5MdPDTdT92henS/Pntm17riiaBelbDCRv2Z7O55BvQCxKBZfxIRocVf84J
F3WHozk3Iq5t/bHdcHtgaJQJeoY0jzd7XSdgPOUQzGpCAgHtCC42kO5IiBfW
Mzk05yekLuZ4eijyhcBtRrc2uVdGLMuXoNh1NiRR25Tll2sgV9Wu6xbpxLis
CXqQdJPud9AEDXdqmkiKHoUXO53tRb7gQJI2z6/BMusZh8DDcw2KGhlRc+4B
umf0sWuSwomhKMa9FuVH+wi7PnThGKVkIQY0UwhVUNZFPyRn4F5s+b9BfRnr
Zd4lyy5MC0/HcwS5su25FvKmXcXuUZxn0yMvv6qdG3f7Qb9SsMHHe3qQLk00
QhnWFLBxp6Frbp3GcJjZUN26UwPO32+wAz8QtqbHA4Jv1rYUBj1tTqGntMcw
0lm8Di0yaEzdkt3i9N4fq8awcv5PQ2DmQj4i6k4B+365mo+29Z7p2k13ffZu
ffgJ0oRtjcGJWWB7RXvQ4iaQUWvwtJZ8JpImva7v0HCvZzw4towN5tcViUp3
Sp+R37QHRk0ZGZsMjRT93A23zCGuxqxhvMt+Ay/viqRheAOCgJhyKGkkI/P9
XALUEocusRhpjA1PVfEYwLRLOUlQqY0/Rc6MhuVKiIwgOGI+ptIn6xlBRhrq
6Wm1QXAdGOjafnTaQIL6nwH0k43zNAkciA6gJwq8irCHzCb3IR/Wc7sIPngR
yLVL47R5KflmqXFqjoNDUThUv9H0oS5jw25Hwq7AXuj/eSVeL9ZJN3YbS/Lc
4iPPT4Nu9BqENPcvOT/tsQmldaXb3QnLy26+MbJNBylKK6G1k3BQGQyaHRrJ
UKVWmhXFAUmy8KLOb2z6gB4/EquS4yWf6nsg+dVOs3TIBrCavhCcyKXRK+pL
PD8M983FA+4ldzUNRp6G0w2AjUF+oRchhtD0RYwu1ZhSXYY2QAEzGfko7gQC
YX6Rrcl74G0yaKw28Ox0V0hG9eTdyT0JPXlifgL9+tdAv5KE7+Psixb6Jfxb
If1Wqx3Aztj6BGhHwzH8SO/nHsnY3cbpC8T6l+1ymX+amXhecGJeytkahDh1
JZ6SD0ZPSMqqabMhWtNPl5xIwxmtSoiULfiBgpd+Fk4F44Qy2hSkoQ/7FKPV
K/IK/9iK749zf9Vc4uJVxxvf8YHq3sJPuyacmaxVI4Ro9DD4kFIRM5Ge4d2E
R+8UFxSStTgoHGJCJ0lmJDPESFUVp18SMkTGZsfVGZ7+PyavH0lCNU/kSrNz
3Xm2Pbxhv/cKmo8IctQvs7Eku5tmvRrSF5ThsYXh+B14G5vG8KiBDJUk76om
IgHNwrzKcjJSekXhLJIhbl3duGCkgvsLtwRfYfokDmSqHePhjv5pSM0Ek7OQ
8Gd45OF+BjhEW8zvdnsjg2tl2MThjMqz3oTgLfwRgckp8gvCbuhyJNEcCtFD
OJ41bPjUU9yfP2sn6bBvbHfSgVaFBe+cLrLe515myifk6Pac8SuVWEjjMeFn
9GUVchZ6ZoyGoPlQNHshu1BWoYDGzjWPi4aLzLsjZzvHSZh+ZpWTWhB+3KJh
nDBYcqdKoTHFqXnd1vBuoKLMwt2Sdlm6ghYgm/CyjPDCS/jJvIOfwG5JAPza
JiQafatNl/Q2FgZMkptCaB568kirVVGEVo9CrluSItex2MY92u70pNaYc3iN
LSoRxI3NC44n7ulXrVRh6bjY4+HU2K1KJjC7ERZS9aQsfn53JCAOR7jStBPO
jJsVQRPOF/OJHUQNWMcqup/z/p+RSLqz5mav491febDVPk7SjZfCH+HLZmbl
Si3YNf1G7oig8Zg3z4D5ClQOWW6cURuHs0RWs//MnLpjN82X2rJRb51Lc8Kw
4WAOmwJ7jS0D41Ct8LFFLjBOu0J+s3/G/exC631jzcZroeVTKBsh004XB/QG
qtYP63xgWyoohMArUdWqCMTdZr2Vx1UHILNbzjFJ64LX+m7M99H8+aSEHLDE
7wuBRISCcON8JmCdK9youLopz2Q+6JN8Cw0kWXA6oy1LdR6beCraVNL85kNH
YcWnC1g9WSn9C9rlukDo9RKEk4ZmnSqK+wksnJLZNJp/nwRG3NWSB2HWWH2t
muLWNZ3+c0Yx5mRCRvieqpu9nwj1L4BlY9qTqs2WSC5ylpxmPjbvyCN/GpuT
DegwfSVPOf2Vrr+SjM7YnP5K6lDts2FyTkxrxv0jbvzuYHIyWxYGh99hbmJV
2rq4pc+l/uGK++Y4uH3HApFdLleFmyxxAFZG0HYeLtdxx4cMH/7yBqnCorb4
SzgSF/gezRkzQSlu3G7Lgu2S+igF9JrCx1IL7mWq1Ypiw01P9bgOyxhh+0cG
+lr3zt2+MLc1EvNlqBP2dIYPSn5qdrTrNP55ClvLWd9BS74eNdYp47hvzCHu
qM3bM6Sk+Y+PhMOK7LE5NljkBcNEnnG1sPdnSGJmvMMrSdFIB+jgb5TssRC4
R98yHgWpTlj20gLMP/GonaQlRROxqZsm8hvX95yBgMCGPD2fI9TXs3ZuKYhh
11KqYmmbFP2Ay+LpuoB6Z2SE3mhA14YzsXp+MGRluI6H88sLpw0DHPucpIDu
wmXcMuuTu1nZIrXtst+PlhQJutFn0DSr+fmIbwT3Tv+4S4Z2VWyG194j4Xic
RW19SHqjEUj/4oK2DdB6N66XdQpJpZCPkz+AMU3+G3p4WNq/SgAA

-->

</rfc>
