<?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.29 (Ruby 3.4.4) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-madhavan-aipref-displaybasedpref-01" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.30.2 -->
  <front>
    <title abbrev="displaybasedpref">A Vocabulary for Controlling Usage of Content Collected by Search and AI Crawlers</title>
    <seriesInfo name="Internet-Draft" value="draft-madhavan-aipref-displaybasedpref-01"/>
    <author fullname="K. Madhavan">
      <organization>Microsoft Corporation</organization>
      <address>
        <email>krishna.madhavan@microsoft.com</email>
      </address>
    </author>
    <author fullname="F. Canel">
      <organization>Microsoft Corporation</organization>
      <address>
        <email>fabrice.canel@microsoft.com</email>
      </address>
    </author>
    <author fullname="J. Gimbel">
      <organization>Microsoft Corporation</organization>
      <address>
        <email>jordangimbel@microsoft.com</email>
      </address>
    </author>
    <author fullname="S. Cooper">
      <organization>Microsoft Corporation</organization>
      <address>
        <email>sonia.cooper@skype.net</email>
      </address>
    </author>
    <date year="2025" month="September" day="21"/>
    <area>Web and Internet Transport</area>
    <workgroup>AI Preferences</workgroup>
    <keyword>crawler</keyword>
    <keyword>display-based preferences</keyword>
    <keyword>AI</keyword>
    <abstract>
      <?line 51?>

<t>This document proposes a standardized vocabulary to express preferences for usage of digital content collected by Search and AI crawlers. This vocabulary allows for the creation of structured declarations about restrictions or permissions for use of content retrieved by such systems.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://kmadhavan-msft.github.io/i-d-ietf-aipref-displaybasedpref/draft-madhavan-aipref-displaybasedpref.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-madhavan-aipref-displaybasedpref/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        AI Preferences Working Group mailing list (<eref target="mailto:ai-control@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/ai-control/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/ai-control/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/kmadhavan-msft/i-d-ietf-aipref-displaybasedpref"/>.</t>
    </note>
  </front>
  <middle>
    <?line 55?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>This document defines a common vocabulary of terms for search and AI systems that process digital content. The primary purpose of this vocabulary is to enable machine-readable expressions of preferences about using digital content collected by Search and AI crawlers.</t>
      <t>The terms defined by the vocabulary can be used to describe, in a standardized way, the types of uses that a declaring party may wish to explicitly restrict or allow. Preferences are then expressed as a grant or denial of permission concerning each of the types of use defined in the vocabulary. This ensures that preferences can be communicated, processed, and stored in a consistent and interoperable manner.</t>
      <t>The vocabulary or the preferences that might be expressed do not proscribe how automated processing systems obtain or act on preferences. Separate documents will describe how preferences might be associated with digital content. It is designed to ensure that preference information can be exchanged between different systems and consistently understood. A reader will also find that this document identifies existing implementations of certain vocabulary elements, helping readers connect these concepts to current preferences supported by most search engines and AI solutions. The authors anticipate removing the references to existing implementations in the final version.</t>
      <t>Expressing preferences is without prejudice to applicable laws including the applicability of exceptions and limitations to copyright.</t>
    </section>
    <section anchor="definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<dl>
        <dt>This document uses the following terms:</dt>
        <dd>
          <t/>
        </dd>
        <dt>Crawler:</dt>
        <dd>
          <t>A crawler is an automated program that scans the web, collecting content (web pages, images, documents etc.) or availability status per URI scanned.</t>
        </dd>
      </dl>
    </section>
    <section anchor="statement-of-preference">
      <name>Statements of Preference</name>
      <t>The vocabulary is a set of categories, each of which is defined to cover a class of usage for digital content. The section on <xref target="vocabulary"/> defines these categories in more detail.</t>
      <t>A statement of preference is made about a specific digital content. Statements of preferences can assign preferences to each of the categories of use in the vocabulary.</t>
      <t>A statement of preferences can express preferences about some, all, or none of the categories from the vocabulary. This can mean that no preference is expressed for a given usage category.</t>
      <t>In the absence of a statement of preference, no preference is set.</t>
      <section anchor="conformance">
        <name>Conformance</name>
        <t>TODO Conformance</t>
      </section>
      <section anchor="applicability">
        <name>Applicability and Effect</name>
        <t>This specification provides a set of definitions for different categories of use based on expressed display preferences.</t>
        <t>This specification does not provide any enforcement mechanism for those preferences, and conformance to it does not encompass whether preferences are actually respected during data processing.</t>
        <t>Preferences do not themselves create rights or prohibitions, either in the positive or the negative. Other mechanisms—technical, legal, contractual, or otherwise—might enforce stated preferences and thereby determine the consequences of following or not following a stated preference.</t>
        <t>An entity that receives usage preferences <bcp14>MAY</bcp14> choose to respect those preferences it has discovered, according to an understanding of how the asset is used, how that usage corresponds to the usage categories where preferences have been stated, and the applicable legal context.</t>
        <t>Usage preferences can be ignored due to express agreements between relevant parties, explicit provisions of law, or the exercise of discretion in situations where widely recognized priorities justify doing so. Priorities that could justify ignoring preferences include - but are not limited to - free expression, safety, education, scholarship, research, preservation, interoperability, and accessibility.</t>
        <t>Because enforcement is not provided by this specification, the consequences of ignoring preferences could vary depending upon how a given legal jurisdiction recognizes preferences.</t>
      </section>
    </section>
    <section anchor="vocabulary">
      <name>Vocabulary Definition</name>
      <t>The following definitions apply to content collected by search and AI crawlers. It does not include user-initiated access of content. All these categories apply independently of each other with the most restrictive taking precedence in case all/some categories are present.</t>
      <section anchor="indexing">
        <name>Indexing and Retrieval</name>
        <t>The act of allowing or disallowing content collected by web crawlers from being indexed or retrieved for purposes of display. Such preference mechanism can also be applied for cases where digital content is not accessible. In existing implementations, access preferences are typically expressed via the NOINDEX statement set in HTTP header or meta tags.</t>
      </section>
      <section anchor="display-text">
        <name>Display text</name>
        <t>The act of allowing or disallowing a reproduction of text content collected by a web crawler, except for the title if specified, from the whole or parts of the content to display portions of that content. In existing implementations preference on which text can be used for caption are expressed via the NOSNIPPET statement set in http header, HTML meta tags, or HTML tags properties (data-nosnippet).</t>
      </section>
      <section anchor="display-text-length">
        <name>Display text length</name>
        <t>The act of limiting the number of characters as a textual display from content collected by a web crawler. In existing implementations quotation length preferences are expressed via the max-snippet statement set in http header or HTML robots meta tags.</t>
      </section>
      <section anchor="exact-text-match">
        <name>Exact text match</name>
        <t>The act of limiting text content to only an exact match if displaying text content from the document. If this preference is present, text content must be quoted as is or use avoided and an explicit link back to the source of the document used in that instance. One example of existing implementation of text quotation preferences is notranslate.</t>
      </section>
      <section anchor="image-preview">
        <name>Image preview</name>
        <t>The act of limiting usage and size of images. In existing implementations image preview preferences are typically expressed via the max-image-preview statement set in http header or HTML meta tags.</t>
      </section>
      <section anchor="video-preview">
        <name>Video preview</name>
        <t>The act of limiting usage and length of videos. In existing implementations video preview preferences are typically expressed via the max-video-preview statement set in http header or HTML robots meta tags.</t>
      </section>
      <section anchor="gen-ai-training">
        <name>Generative AI training</name>
        <t>The act of using content in training general purpose AI models that have the intent to generate text, images or other forms of synthetic content, or the act of training more specialized AI models that have the purpose of generating text, images or other forms of synthetic content. In existing implementations preferences are communicated via robots.txt or via http header or HTML robots meta tags.</t>
      </section>
    </section>
    <section anchor="usage">
      <name>Usage</name>
      <t>The vocabulary is used by referencing the terms defined in the section on <xref target="vocabulary"/>, directly or via mappings, in accordance with how they are defined in this document.</t>
      <section anchor="more-specific-instructions">
        <name>More specific instructions</name>
        <dl>
          <dt>A recipient of a statement of preferences that follows this model might receive more specific instructions in two ways:</dt>
          <dd>
            <t>Extensions to the vocabulary might define more specific categories of usage. Preferences about more specific categories override those of any more general category.</t>
          </dd>
          <dt/>
          <dd>
            <t>Statements of preferences are general purpose, machine-readable statements that cannot override contractual agreements or more specific statements.</t>
          </dd>
        </dl>
        <t>For instance, a statement of preferences might indicate that the use of a digital content is disallowed for Generative AI Training. If arrangements, such as legal or business agreements, exist that explicitly permit the use of that digital content, those arrangements are likely to apply, unless the terms of the arrangement explicitly say otherwise.</t>
      </section>
      <section anchor="usage-category-labels">
        <name>Usage category labels</name>
        <t>Each usage category in the <xref target="vocabulary"/> is mapped to a short textual label. The <xref target="label-table">table below</xref> tabulates this mapping.</t>
        <table anchor="label-table">
          <name>Usage Category Labels</name>
          <thead>
            <tr>
              <th align="left">Category</th>
              <th align="left">Label</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Indexing and retrieval</td>
              <td align="left">index</td>
              <td align="left">
                <xref target="indexing"/></td>
            </tr>
            <tr>
              <td align="left">Display text</td>
              <td align="left">display-text</td>
              <td align="left">
                <xref target="display-text"/></td>
            </tr>
            <tr>
              <td align="left">Display text length</td>
              <td align="left">max-text-length</td>
              <td align="left">
                <xref target="display-text-length"/></td>
            </tr>
            <tr>
              <td align="left">Exact text match</td>
              <td align="left">match-text</td>
              <td align="left">
                <xref target="exact-text-match"/></td>
            </tr>
            <tr>
              <td align="left">Image preview</td>
              <td align="left">max-image-preview</td>
              <td align="left">
                <xref target="image-preview"/></td>
            </tr>
            <tr>
              <td align="left">Video preview</td>
              <td align="left">max-video-preview</td>
              <td align="left">
                <xref target="video-preview"/></td>
            </tr>
            <tr>
              <td align="left">Generative AI training</td>
              <td align="left">train-genAI</td>
              <td align="left">
                <xref target="gen-ai-training"/></td>
            </tr>
          </tbody>
        </table>
        <t>An important note about this process and format is that, if the same key appears multiple times, only the last value is taken. This means that duplicating the same key could result in unexpected outcomes.</t>
      </section>
      <section anchor="consulting-a-preference-expression">
        <name>Consulting a Preference Expression</name>
        <dl>
          <dt>A single preference expression can be evaluated for a usage category as follows:</dt>
          <dd>
            <t>If the expression contains an explicit preference, that is the result.</t>
          </dd>
          <dt/>
          <dd>
            <t>Otherwise, no preference is expressed.</t>
          </dd>
        </dl>
      </section>
      <section anchor="combining-preferences">
        <name>Combining Preferences</name>
        <t>The application might have multiple preference expressions, obtained using different methods.</t>
        <t>If multiple preference expressions are active, all preference expressions are consulted as described in the section on <xref target="legaleffect">Applicability and Legal Effect</xref>. This might result in conflicting answers.</t>
        <dl>
          <dt>Absent some other means of resolving conflicts, the following process applies to each usage category:</dt>
          <dd>
            <t>If any preference expression indicates that the usage is restricted, the result is that the usage is restricted.</t>
          </dd>
          <dt/>
          <dd>
            <t>Otherwise, if any preference allows the usage, the result is that the usage is allowed.</t>
          </dd>
          <dt/>
          <dd>
            <t>Otherwise, no preference is set.</t>
          </dd>
        </dl>
        <t>This process ensures that the most restrictive preference applies.</t>
      </section>
    </section>
    <section anchor="legaleffect">
      <name>Applicability and Legal Effect</name>
      <t>TODO</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
    <section anchor="explain">
      <name>Addendum - Explanatory Note</name>
      <table anchor="explanatory-table">
        <name>Search and AI Tool Behavior Examples</name>
        <thead>
          <tr>
            <th align="left">Category</th>
            <th align="left">Search Experience if preference set to disallowed</th>
            <th align="left">AI Tool Experiences (such as Chat experience) if preference set to disallowed</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">
              <strong>Indexing and Retrieval</strong></td>
            <td align="left">Content is not used or linked in response to a user search query.</td>
            <td align="left">Content may not be used or linked in response to a user query.<br/><br/>Eg: Response in Copilot to the query, “Tell me what the mayor of SF said last night at city hall?” may not retrieve and use a relevant SF Chronicle article to inform a user response if this preference is set to not allowed.<br/></td>
          </tr>
          <tr>
            <td align="left">
              <strong>Display Text</strong></td>
            <td align="left">When content is shown in response to a user query, only the title (if specified) and URL.</td>
            <td align="left">Content cannot be used as a direct input to generate an AI experience (such as an AI summary or overview) in response to a user query. When content is shown in response to a user query, only the title (if specified) and URL may be displayed.<br/><br/>Eg: Response in Copilot to the query, “Tell me what the mayor of SF said last night at city hall?” may only display the title and URL to a SF Chronicle article if that article is delivered in the response and it will not serve as a direct input for grounding, provided the whole document is set to no display.<br/></td>
          </tr>
          <tr>
            <td align="left">
              <strong>Display Text Length</strong></td>
            <td align="left">Any display that includes a portion of the content must comply with the specified character limit.</td>
            <td align="left">Any display that includes a portion of the content must comply with the specified character limit.<br/><br/>Eg: Response in Copilot to the query, “Tell me what the mayor of SF said last night at city hall?” may use a SF Chronicle article for grounding purposes to generate a response, but any passage of the article that is included as part of that response must comply with any established character limit. The response may go beyond the passage from the content and include other statements or information – whether observations derived from examining the article or not.<br/></td>
          </tr>
          <tr>
            <td align="left">
              <strong>Exact Text Match</strong></td>
            <td align="left">Any display that includes a portion of the content must only present the designated portions of the content.</td>
            <td align="left">Any display that includes a portion of the content must comply with the specified character limit.<br/><br/>Eg: Response in Copilot to the query, “Tell me what the mayor of SF said last night at city hall?” may use a SF Chronicle article for grounding purposes to generate a response, but any passage of the article that is included as part of that response must only include characters from the designated portion of the content.<br/></td>
          </tr>
          <tr>
            <td align="left">
              <strong>Generative AI Training</strong></td>
            <td align="left">Any text included cannot be used for training of Generative AI models.</td>
            <td align="left">Any text included cannot be used for training of Generative AI models.<br/></td>
          </tr>
        </tbody>
      </table>
    </section>
  </middle>
  <back>
    <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>
    </references>
    <?line 227?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1bX3PcRnJ/30+BrF4k1e4yyrkqF5bPNk1RNhNR1EnUOVeu
e5gFZnfHBDBrDLDLPVFV/g7JY1J1n+U+ij/J/bp7Bhhgl6SsS5yXuK6OiwHQ
09N/f90NTafTUW3qXB8n45PkDzZV8yZX1S5Z2Co5tWVd2Tw35TJ559RSJ3bB
i7qs8TfPdVrrLJnvkrdaVekqUWWWnJwnp5Xa5rpy45Gazyu9Ae3MuHWudnPl
dLau9GI8SlWtl7baHSemXNjRKLNpqQrwkVVqUU8Lla3URpVTZej56ZDA9B+f
jVwzL4xzBhzt1njz/OzqRZI8SlTuLPY0ZabXGv9X1uNJMtaZqW1lVE4X5ydf
4w/OOD5/c/ViPCqbYq6r41EGro5HqS2dLl3jjpO6avQIJ/jNSFVagep3es7n
PIcYqlLXyVWlSre2VT0ebW11vaxssyZpnievwaeudJlqiOJa73A7Ox4l0yQV
AdFPf64pHyxZd2/QzZPz0UaXDThKkrvoJokcfvwdNidNfUMP0nqhTI51Zaap
KPIro+vFzFZLuksKw91VXa/d8dERPUxLZqNn4bEjWjiaV3br9FFH5oheX5p6
1cxB4LrVVOEW9ZGZZlN6/y690bs5hOzqaPM+jZnQnhn7ILWjjzOW2aou8vFo
pJp6ZStSAbhIkkWT52Jz43+bJReeyJjv4fiqNH9WNazrOLkwaWWdXZDZV9A1
L/NzWqR8XRm3KtUscPJVEd6YpbYYHdjxxSw5VaXOP2m7hZpXJtWzlCg8vNe/
zpJvDAz80zb7AWaryiUTeHivtziXtWtdfdJezpZGgTQR+Mpdw7Jn8LHRqLRV
gYc3cIURxYvuajqdJmru6kqleO5qZVyCUNIUFKPWlV1bp12iElfDaVWVmT/D
zTZdnKttom9gI87FzsfhrwkhLzOwSJUnqQ996d2hz3u2myXMSbSRynP4EROu
VxoPaj480QfzTVo3FQhmOsXTfAdcz21TJ+CthrJlCW9DMj7qBTaZycBcpfG0
3ghzrgFrbudqXbiZyKowWZbr0egRRbDKZg1TTt4/MtHlh4EgM70wJcsRWi/w
eHQw7I1IWAgzricNvzMOrFgZKYl5IE2SlMZNUxCxdVORxpjoQIC4ImWVap5r
xDaEqlJPIcWMF7wSRUiLni5FjI2j4PgpqiSr0v6MIgh+mrQYsQdXTOaatJER
n5l2aWXmeoL0NjS/rdpN+HWK3MxuQ0bKUlLeBIjZtarqHY66S7aILt5Uc5Mi
X+9asyCTYNuaxXkB4V3TFmUQDLZVpL8lshW/g7SIXMiyag2KxJIiq9HmGhIW
NfT5bEWAc/VF4G2eEmelW6V3LHkJkQU1paH8n02CVdBPkrtDihbaZGqlM47V
RLcMJVyKC94AylJXXjexNYp7xfsyI4VZrmravpNHZpPSsl2KqpKV3SZIEbYg
1gJnJItgx3ZeK7BGEifBl/E2M5jPmlxXt27joLc8b02B6ceMtTwp52xqeNct
ct++i5zXZP4gZJal2JdIeSjkpI2NpEyRt75JVwjfZLS63mqYRGYW/HzdHozk
24kb1tUANlVQhs1myUlCXqYrOQ2BqwQWkMnedS9OGAJbZmFwOH0DYiQ8U6xz
TXd9VKNYpSsWZKQ3Lc+4SbLS+Zrek00d8VXCRUmtTouFrmuOBWlTVRLmO5m6
Zk1YTFy0sK4OIUkjg3EI86HJ5g3zI/FHkAHdreFfa9JipQu7IUbInmJzsnef
zfsExAPtbcA9VmGjZz44kU9HlIxjdVN0wvIPTYaUTuTVmryczTxXW6Ka5rjp
WQl3TW5qjr5QMCQiGQOHy01hAj8kJLveVWRoM4r5QO8bUlF4+Dk5s5Hr94+y
7uqDeBZQa0Kw1SXji3dvrwg609/k1SX/fnP2+3fnb86e0++33568fNn+GPkn
3n57+e7l8+5X9+bp5cXF2avn8jJWk97SaHxx8sexBIXx5eur88tXJy/HIuDY
4jjOWbJzjg+QY82hbhS8joPJ16ev//qXZ58l79//w5sXp//07Nm/fPjgL377
7J8/w8UWsVJ2syXsXy4h7t0I8oYFcUiC+adqTa4JO0U4dfDoEgZbaQj36fck
mT8dJ5/P0/Wzz77wC3Tg3mKQWW+RZba/sveyCPHA0oFtWmn21geS7vN78sfe
dZB7tPj5lygHdTJ99tsvvxgN8ZZPY3AASxmJLZbS5vHIl4TAa8eIJz61kgMg
RvVCLvJTIZHFIX4Jta2eT0KmJpoheT/GDSTJpYY2AB/4bxd7dZ3OnnCs3lBt
4/0FibhuHOW85N2bc94EEZV94y1uSRAir+qSKRzDhVtTu5h2LvxhmH0MQ00U
hRTkpMA1xFVIptuVwQ/T4Qh2UAQKSnc50oAkWcKdhKYOQiWnBbHhf993W//p
8aPu4kkL2HzQbFkhMy6QYvEAInCOc58k7eH6wInYRDmjPX7CudY6RWxP99nq
S26Y83EspK1+SrY9fBHx50HGPri4h1PZ5hCMF9adLYDD4L1c8Ze21Ac2XlS2
OAxoiHihVSlmWdqBjDpAQSoDwkJdUnolhiYHuD+XE6FU4RfBgLrrPJP9TWBT
ZKMcwDnDi12m3RVs8fL5ZXyfnz/pZQuKb2dI/kin7x/1EskH78tByQIh4JAb
5PTIqqMU4U00YIl9JUpPw8YY1FfmPeB0cOfMgo6HZ8QCWAdIoLOlIrFCE6wx
rvAlFVUNEdVJwDSttGBzpu7o4ilbrMnlEOuhmapvOHARYLwGRsNQey1FQtYw
MM9UrSJ8iBPE0NvjStAsnM43ZJ5U7AFEUBqWGq6yKzMXMSI6GN7f2zzqH0O1
bYCypV5yrTtLLvmx9uDu55/+s8YFYWmYdo7n8gk7ZSWss7lbegn1g8bTAji9
FMX6sv6xGdbhCuAJEYIKg1KLp1BL7MdGHoN+uwjPLlVHC2qfMnkvzADAo96J
G1U61YZkI44SM4EslKQrSwqFzrzw9zVM2lwpqicdh1AuIdIUYIXzjqXU4mEs
jsWcLhiCsxs6smfjuF6b+GVVB7e1FW1ry4xDFb3Q82ey8S2JqcfPSkFpcwLY
cv5JEGcP0JGWJHLekEu/2zu+h+0ImVwKZY2OmxRqWWkfagOcr4CdN1TVUb0o
6caXieI8bVEMMDkJVqVvdJUa5/sbgEqa3Q42COtrPHyUM27hfuwFqV2WXMCi
WocQaK/khwZIeAFrsVwoWapC25ss0tQ2edY+x8faA8IMcIEqknkjkI4sioGs
5MgpwrOOi/xJ4tRC16ijddZIyMASrAZx263MekJ2w8CfSkz8rDb+oaiM5MAn
WoLhEGFZglq+1qmiEBZHHNMLSL4HMAxck4PecvDUIpgN4QZpVNMDDaxOClGf
SMRgfkDgcZl0gTpNuEEcfRR38Dtoj1jfJTUP7Dt3jSM6GepOQMmB/oi7o9V1
HoXVoEoIr5oyXQ4FIt+oT4WyEmh6D54IA1HnPpcSh8EChz8ukEnGXNy1zTG4
Xq2uvYhTnflqGLSxAaL4EYGA3k7ivY544Ux5jv1uOH7hfG+kiwbJU2NMbnjJ
cem/kJ6Lj39woPbyoOQIqAZ5CdKYa64fiTTlyCrq21E+830w592TciZgFnXz
IlzQpUCGWVSYz32w8WTo9MGNh60vb87B8nMkmPPyztJ2ElQ4zJL1bk35B3rq
svzGKFbRq8tz1Bj/HuEcjrpl8u3V1WvUTdxVsJTSkE9rtXSiieceJFCIpKrU
j0jo8uN0oCDNddfb5A7lTX1YNSpWzsQX022blmdjiVkEJ6eo3iLFLcINp2kK
vK7FlH4XagIGtGOrtvfhY2Jo7Nwt8VjTOISUDnKOqNUoWubyn9VxSAlvX52/
fn12ta8Gmr94NUygk4uXnSY4UfASXXEnXXN2SR4T+pmW1pUGlXH95IDOcl0u
4aV91U1lta9BjvGhsyFDOA4SK0UYhryFu5b0PgBNK1BWwcPqvF++PzZWfgZ+
h6a9L8tC3Uz9ue+VZiu8ys4tTGNg4Gc3dHwWFQrflCSlaUnkxEt3iSm2Y1gY
Nyu4+KEnhZhpQ8beG63phjIZEvKd9n694SPjpP96gSROlkeSk4ayYThLmVJt
LGdFzqZlB0FyU16jEkivA5JytqnStgKLewe+p6xImgTaUsK8JelBkeqk13VQ
ma2LdzodNNoQ6mhOS6NHH+4LD7w2Rm8pytP11F/fIX0BgdynRvblxM5th/vt
zPR2+iXxk8ytx9fHGd3A2v4AvdjopIRe7Eef1PsGbvJ7D5x109vrl561x9nf
42Df6FJXXDURUoHmDc803j9aahoST8NK//QyImrzY9m9uGR6eTueAtHCAhV7
iMvInw5hWseUN2rNZhnaU209RmG74HTgdiUWapOGfVuE7plqeeC2DachlTMK
v4uJaIbmuQhx4Jfw8bG5STQbD3VYpaKXWX3DwyZa+Vjtyacme4MdX6tRjA97
h7zRH835Mvpj2mQTBEqgRQaZwmQB9ASyTsZ2XE1y84BRpy8ed3zi3nZRE1QM
8KJVFjXMKJxVAkYc9bGwp1kb3/e5sw3k9SpI3ckurHA/OPIldGQYw72Yua2l
gaPj1uvZDVTrwmhgMMEUqnKuAdFhbwcKGowbudF290uozyvq4kgVT6cud/J4
cK2oVXZ8T0NRRa94Q5/sT4Nd977gLVUS1m3ZiJokcUVNULR3hI4O2HphqzYx
Te5TmwgS2J79IczJdJjUq0NQPMBXD+n6AezKxwDO1qqqaJznp2U84UciljIR
b84pivU7BRPxY2EkGiHz4LfHGj8x4G7ilRbvy2rIzbWWapGrtknSlDlt3Lmk
z/HRm/H2DkCu7U6J27zrdU2TXM0R3kajMyr/+h3V4OZ3t8C5fQ2kxg0ERbOa
qm6BJFOWfvr3NZsMru0WJPjOlNeeICYRtVoH75PoAF5vk9PAyG3ykl7B3zct
grod3R5P2//a3/HiFM/0a86qrTlvpTDE3+9D8QnOws8nRL4PuG+TGGnTe/E1
3o0vD7zvk/wtZ+EIrA8p+eUBQb8qdPew7a38bTkbIl0QGy4JpT5Cuz2Ahkg+
8QIJKb4WOn38c3sAaYBOb4EsKb4WOneAilv5OUVUwjJIDTAGiA1WiNz74yQ2
NSk0fzcWB2htiy3LjT9w+xQ5GCZMjT7EsjCW8dhdPq0hK5L5P38tA2eeUDXA
6VAVMs2VcSZsuclrs+adC+oZciVBT+YKoQJW2HAhUKtrXfpBCA1BfEDNGu5o
tqVbS16aWsB2IE8+2pTweKnOwC5ggnbtIIOekXI9GradtT0+nvjgfh73R6Me
YPuBAzHLwEMGMINAoVxIoZwCzxe+/9mRQZyDYlyvbImnMVKSOP8hAHHNSeoy
xK4D85oW34bDFnOxlihpeuy59pIEJ5I4GMi16jl4dNIXf4uCQ4cPm8IcBmBq
ZTOSMo76AJkw54BN84DsvsdSUZjUfb3p+hBu7c+cXnJ2kskTxVi61Hz1JNiW
hzTBbmhykxuZ98LqtvIh1glNz2Sg5wGs2CQSDV61+cYDeH7VTQaz6NZNuEPW
TSH7BhOshBDKYbsLmd3FqZ1I4ByhIUmNos5egjve9ezQnsze9iqAQP/+w9Q9
nHjQVGW0eBXHkd4nXAd7rTFnIk2G7vdrHvVXpHkZWPKHiCevTjgeIOb6bx+H
XxbQoAec85NKwK1smGW6zJoimVLgyFWpavL5VxQgqamCJVN+GORr/50fXtBI
uCyG3uCbyk3p3gVIdssozNo8eskljwP4OvXAyt958jC9GB/0UMHH/vdJLwno
ePr0cKv76VOc87TfHeaSC1GVujji7DIYk9mc4jZ/mAv82GiamXc06MtFIhJ6
lQ/REQKfz6ujL/j/zpbH4M4/hldO7drktg6lCz8+SX7+6b+uNEJXQQ3ZYK9q
Z7mR+PYFUpPJJKmVHGOoHCDrXEEZX/7803+3bIYOPEuFW1rdaA10TleVRYWb
E56t+S9NlHm+HA7QnskcbKp5O+Cuu3dOPmciWgmI7Ao4iHXxHX2/GdUI8rnR
PbKLsrg0rh/HnesnfLB3b17GOvKVUVARd1ulKMZG66bfy0CChB90ht55gNxx
TVH4jzCp1BLodJ+u/9eOyEqd6wCLg6R/bbNiXkPTuuM5MMlnO2haxtdi7TWl
3NzwmDuk3FZE/HVsLZ9nkjJp2qkPqJLgEf0zEp40TrpBZjfL6D7kjKy1HUDd
ZawI8oT/2WZPyvjAqh0IEjN+DDIclHBXmT7GoO/uwnSvVWk3C5Du5OxX2eT/
xFok5hy0h57quulgzzlbg5jIGJ0AhHLhHzFIIe4Dlwe0Xmzs9jTDalsArWnt
iY0/w3FUsxi3OqSdq9gy6VRLmkrurP8UInDUTiKCguQTbxkeC7SLmjjceem+
bP75p/9ov9qx83a4Tz5SGR6hEnUaGwjojs8un6v0bFlKVrbkCyo//y5DZpf3
4xOZcPBX2/JBTG8OqLtW6/+b9K9s0qylYG7RtLEbkO1pbai02IIOt+taO+LW
R8vZIOXyqDk0E7BHn5Z0+Gf/Y4QC19R/0B1i7nch+v8QhnHv1xplqcEOZzKM
46bESP5JEU33GIyn16Xd5jpbstdiD5no6ux344XKnR57zP83szU9TXY6AAA=

-->

</rfc>
