<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-httpbis-no-vary-search-11" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="No-Vary-Search">The No-Vary-Search HTTP Caching Extension</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-no-vary-search-11"/>
    <author fullname="Domenic Denicola">
      <organization>Google LLC</organization>
      <address>
        <email>d@domenic.me</email>
      </address>
    </author>
    <author fullname="Jeremy Roman">
      <organization>Google LLC</organization>
      <address>
        <email>jbroman@chromium.org</email>
      </address>
    </author>
    <author fullname="Nidhi Jaju" role="editor">
      <organization>Google LLC</organization>
      <address>
        <email>nidhijaju@chromium.org</email>
      </address>
    </author>
    <date year="2026" month="November" day="17"/>
    <area>Web and Internet Transport</area>
    <workgroup>HyperText Transfer Protocol</workgroup>
    <keyword>http</keyword>
    <keyword>caching</keyword>
    <abstract>
      <?line 108?>

<t>This specification defines an extension to HTTP Caching, changing how the URI query component impacts caching. It introduces the <tt>"No-Vary-Search"</tt> response header field, which allows origin servers to signal to caches that certain parts of the query component do not semantically affect the served response and can be ignored for cache matching purposes.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-httpbis-no-vary-search/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        HTTP Working Group mailing list (<eref target="mailto:ietf-http-wg@w3.org"/>),
        which is archived at <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
        Working Group information can be found at <eref target="https://httpwg.org/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/httpwg/http-extensions/labels/no-vary-search"/>.</t>
    </note>
  </front>
  <middle>
    <?line 112?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>HTTP caching <xref target="HTTP-CACHING"/> is based on reusing resources which match across a number of cache keys, with the most important one being the presented target URI (<xref section="7.1" sectionFormat="of" target="HTTP"/>). However, sometimes multiple URIs can represent the same resource. This leads to caches not always being as helpful as they could be: if the cache contains a response under one URI, but the response is then requested under another, the cached version will be ignored.</t>
      <t>The "No-Vary-Search" response header field defines a caching extension, as described in <xref section="4" sectionFormat="of" target="HTTP-CACHING"/>, that tackles a specific subset of this general problem, for when different URIs that differ only in their query component identify the same resource. It allows resources to declare that some or all parts of the query component do not semantically affect the served response, and thus can be ignored for cache matching purposes. This is achieved by interpreting the query component as a sequence of parameters encoded using the <tt>application/x-www-form-urlencoded</tt> format <xref target="WHATWG-URL"/>. For example, if the order of the parameters within the query component does not affect which resource is identified, this is indicated using</t>
      <sourcecode type="http-message"><![CDATA[
No-Vary-Search: key-order
]]></sourcecode>
      <t>If specific query parameters (e.g., ones indicating something for analytics) do not semantically affect the served resource, this is indicated using</t>
      <sourcecode type="http-message"><![CDATA[
No-Vary-Search: params=("utm_source" "utm_medium" "utm_campaign")
]]></sourcecode>
      <t>And if the resource instead wants to take an allowlist-based approach, where only certain known query parameters semantically affect the served response, they can use</t>
      <sourcecode type="http-message"><![CDATA[
No-Vary-Search: except=("productId")
]]></sourcecode>
      <t>Note that "cache busting", the practice of changing a part of the query component to create a distinct cache key and force retrieval of a newer response, can be made ineffective by the <tt>"No-Vary-Search"</tt> response header field.</t>
      <t><xref target="header-definition"/> defines the new <tt>"No-Vary-Search"</tt> response header field, using the <xref target="STRUCTURED-FIELDS"/> framework. <xref target="data-model"/> and <xref target="parsing"/> illustrate the data model for how the field value can be represented in specifications, and the process for parsing the raw output from the structured field parser into that data model. <xref target="comparing"/> gives the key algorithm for comparing if two URLs are equivalent under the influence of the header field; notably, it leans on the decomposition of the query component into keys and values given by the <eref target="https://url.spec.whatwg.org/#concept-urlencoded">application/x-www-form-urlencoded</eref> format specified in <xref target="WHATWG-URL"/>. (As such, this header field is not useful for URLs whose query component does not follow that format.) Finally, <xref target="caching"/> explains how to extend <xref section="4" sectionFormat="of" target="HTTP-CACHING"/> to take this new equivalence into account.</t>
      <t>From a deployment perspective, this extension is implemented by HTTP caches, including browser caches, content delivery networks, and forward proxies. Origin servers send the <tt>"No-Vary-Search"</tt> response header field to provide instructions to these caches. Caches that implement this extension use these instructions to determine when a previously stored response can be safely reused for a new request, even if the query components of the target URIs differ.</t>
    </section>
    <section anchor="conventions-and-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?>

<t>In this document, the terms "URI" and "URL" are used interchangeably, depending on context. "URI" is used in the context of <xref target="URI"/>, <xref target="HTTP"/>, and <xref target="HTTP-CACHING"/>, whereas "URL" is used in the context of the algorithms specified in <xref target="WHATWG-URL"/>.</t>
      <t>The term "query parameters" in this document refers to the keys and values resulting from parsing a URL's query component using the <eref target="https://url.spec.whatwg.org/#concept-urlencoded">application/x-www-form-urlencoded</eref> format <xref target="WHATWG-URL"/>.</t>
      <t>This document also adopts some conventions and notation typical in WHATWG and W3C usage, especially as it relates to algorithms. See <xref target="WHATWG-INFRA"/>, and in particular:</t>
      <ul spacing="normal">
        <li>
          <t>its definition of lists, including the list literal notation « 1, 2, 3 ».</t>
        </li>
        <li>
          <t>its definition of strings, including their representation as code units.</t>
        </li>
      </ul>
      <t>(Other concepts used are called out using inline references.)</t>
    </section>
    <section anchor="header-definition">
      <name>HTTP header field definition</name>
      <t>The <tt>"No-Vary-Search"</tt> response header field is a structured field <xref target="STRUCTURED-FIELDS"/> whose value <bcp14>MUST</bcp14> be a dictionary (<xref section="3.2" sectionFormat="of" target="STRUCTURED-FIELDS"/>).</t>
      <t>It has the following constraints:</t>
      <ul spacing="normal">
        <li>
          <t>If present, the <tt>key-order</tt> entry's value <bcp14>MUST</bcp14> be a boolean (<xref section="3.3.6" sectionFormat="of" target="STRUCTURED-FIELDS"/>).</t>
        </li>
        <li>
          <t>If present, the <tt>params</tt> entry's value <bcp14>MUST</bcp14> be an inner list of strings (<xref section="3.1.1" sectionFormat="of" target="STRUCTURED-FIELDS"/>).</t>
        </li>
        <li>
          <t>If present, the <tt>except</tt> entry's value <bcp14>MUST</bcp14> be an inner list of strings (<xref section="3.1.1" sectionFormat="of" target="STRUCTURED-FIELDS"/>).</t>
        </li>
        <li>
          <t>The <tt>except</tt> entry <bcp14>MUST NOT</bcp14> be present if the <tt>params</tt> entry is also present.</t>
        </li>
      </ul>
      <t>The dictionary <bcp14>MAY</bcp14> contain entries whose keys are not one of <tt>key-order</tt>, <tt>params</tt>, and <tt>except</tt>, but their meaning is not defined by this specification. Implementations of this specification will ignore such entries (but future documents might assign meaning to such entries). Future extensions to this dictionary <bcp14>MUST NOT</bcp14> restrict the set of URIs that are considered equivalent; they can only expand it. If a future extension requires restricting equivalence, it <bcp14>MUST</bcp14> be deployed as a new HTTP header field to ensure safety.</t>
      <t>The <tt>"No-Vary-Search"</tt> response header field is set by origin servers. Intermediaries <bcp14>MUST NOT</bcp14> insert, delete, or modify the field's value unless they are acting as the origin server for that response.</t>
      <aside>
        <t>A parsing algorithm is defined in <xref target="obtain-a-url-variation-config"/>.</t>
      </aside>
    </section>
    <section anchor="data-model">
      <name>Data model</name>
      <t>A <em>URL variation config</em> consists of the following:</t>
      <dl newline="true">
        <dt>no-vary params</dt>
        <dd>
          <t>either the special value <strong>wildcard</strong> or a list of strings</t>
        </dd>
        <dt>vary params</dt>
        <dd>
          <t>either the special value <strong>wildcard</strong> or a list of strings</t>
        </dd>
        <dt>vary on key order</dt>
        <dd>
          <t>a boolean</t>
        </dd>
      </dl>
      <t><iref item="default URL variation config" primary="true"/>
The <em><iref item="default URL variation config"/>default URL variation config</em> is a URL variation config whose no-vary params is an empty list, vary params is <strong>wildcard</strong>, and vary on key order is true.</t>
      <t>The <iref item="obtain a URL variation config"/><xref target="obtain-a-url-variation-config" format="none">obtain a URL variation config</xref> algorithm (<xref target="obtain-a-url-variation-config"/>) ensures that all URL variation configs obey the following constraints:</t>
      <ul spacing="normal">
        <li>
          <t>vary params is a list if and only if the no-vary params is <strong>wildcard</strong>; and</t>
        </li>
        <li>
          <t>no-vary params is a list if and only if the vary params is <strong>wildcard</strong>.</t>
        </li>
      </ul>
    </section>
    <section anchor="parsing">
      <name>Parsing</name>
      <section anchor="parse-a-url-variation-config">
        <name>Parse a URL variation config</name>
        <t><iref item="parse a URL variation config" primary="true"/>
To <em><iref item="parse a URL variation config"/><xref target="parse-a-url-variation-config" format="none">parse a URL variation config</xref></em> given <em>value</em>:</t>
        <ol spacing="normal" type="1"><li>
            <t>If <em>value</em> is null, then return the <iref item="default URL variation config"/>default URL variation config.</t>
          </li>
          <li>
            <t>Let <em>result</em> be a new URL variation config.</t>
          </li>
          <li>
            <t>Set <em>result</em>'s vary on key order to true.</t>
          </li>
          <li>
            <t>If <em>value</em>["<tt>key-order</tt>"] exists:
            </t>
            <ol spacing="normal" type="1"><li>
                <t>Let <em>keyOrderValue</em> be the <tt>item_or_inner_list</tt> component of the tuple <em>value</em>["<tt>key-order</tt>"] (ignoring any parameters).</t>
              </li>
              <li>
                <t>If <em>keyOrderValue</em> is not a boolean, then return the <iref item="default URL variation config"/>default URL variation config.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s vary on key order to the boolean negation of <em>keyOrderValue</em>.</t>
              </li>
            </ol>
          </li>
          <li>
            <t>If both <em>value</em>["<tt>params</tt>"] and <em>value</em>["<tt>except</tt>"] exist, then return the <iref item="default URL variation config"/>default URL variation config.</t>
          </li>
          <li>
            <t>If neither <em>value</em>["<tt>params</tt>"] nor <em>value</em>["<tt>except</tt>"] exists:
            </t>
            <ol spacing="normal" type="1"><li>
                <t>Set <em>result</em>'s no-vary params to an empty list.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s vary params to <strong>wildcard</strong>.</t>
              </li>
            </ol>
          </li>
          <li>
            <t>If <em>value</em>["<tt>params</tt>"] exists:
            </t>
            <ol spacing="normal" type="1"><li>
                <t>Let <em>paramsValue</em> be the <tt>item_or_inner_list</tt> component of the tuple <em>value</em>["<tt>params</tt>"] (ignoring any parameters).</t>
              </li>
              <li>
                <t>If <em>paramsValue</em> is not an inner list, then return the <iref item="default URL variation config"/>default URL variation config.</t>
              </li>
              <li>
                <t>Let <em>paramsList</em> be a list containing the <tt>bare_item</tt> component of each tuple in <em>paramsValue</em> (ignoring any parameters).</t>
              </li>
              <li>
                <t>If any item in <em>paramsList</em> is not a string, then return the <iref item="default URL variation config"/>default URL variation config.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s no-vary params to the result of applying <iref item="parse a key"/><xref target="parse-a-key" format="none">parse a key</xref> (<xref target="parse-a-key"/>) to each item in <em>paramsList</em>.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s vary params to <strong>wildcard</strong>.</t>
              </li>
            </ol>
          </li>
          <li>
            <t>Otherwise, if <em>value</em>["<tt>except</tt>"] exists:
            </t>
            <ol spacing="normal" type="1"><li>
                <t>Let <em>exceptValue</em> be the <tt>item_or_inner_list</tt> component of the tuple <em>value</em>["<tt>except</tt>"] (ignoring any parameters).</t>
              </li>
              <li>
                <t>If <em>exceptValue</em> is not an inner list, then return the <iref item="default URL variation config"/>default URL variation config.</t>
              </li>
              <li>
                <t>Let <em>exceptList</em> be a list containing the <tt>bare_item</tt> component of each tuple in <em>exceptValue</em> (ignoring any parameters).</t>
              </li>
              <li>
                <t>If any item in <em>exceptList</em> is not a string, then return the <iref item="default URL variation config"/>default URL variation config.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s vary params to the result of applying <iref item="parse a key"/><xref target="parse-a-key" format="none">parse a key</xref> (<xref target="parse-a-key"/>) to each item in <em>exceptList</em>.</t>
              </li>
              <li>
                <t>Set <em>result</em>'s no-vary params to <strong>wildcard</strong>.</t>
              </li>
            </ol>
          </li>
          <li>
            <t>Return <em>result</em>.</t>
          </li>
        </ol>
        <aside>
          <t>In general, this algorithm is strict and tends to return the <iref item="default URL variation config"/>default URL variation config whenever it sees something it doesn't recognize. This is because the <iref item="default URL variation config"/>default URL variation config behavior will just cause fewer cache hits, which is an acceptable fallback behavior.</t>
        </aside>
        <aside>
          <t>The input to this algorithm is generally obtained by parsing a structured field (<xref section="4.2" sectionFormat="of" target="STRUCTURED-FIELDS"/>) using field_type "dictionary".</t>
        </aside>
      </section>
      <section anchor="obtain-a-url-variation-config">
        <name>Obtain a URL variation config</name>
        <t><iref item="obtain a URL variation config" primary="true"/>
To <em><iref item="obtain a URL variation config"/><xref target="obtain-a-url-variation-config" format="none">obtain a URL variation config</xref></em> given an HTTP response (<xref section="3.4" sectionFormat="of" target="HTTP"/>) <em>response</em>:</t>
        <ol spacing="normal" type="1"><li>
            <t>Let <em>fieldValue</em> be the result of parsing the <tt>"No-Vary-Search"</tt> response header field from <em>response</em> as a Dictionary (<xref section="4.2" sectionFormat="of" target="STRUCTURED-FIELDS"/>). If parsing fails or the field is absent, let <em>fieldValue</em> be null.</t>
          </li>
          <li>
            <t>Return the result of parsing a URL variation config (<xref target="parse-a-url-variation-config"/>) given <em>fieldValue</em>. <iref item="parse a URL variation config"/></t>
          </li>
        </ol>
        <section anchor="examples">
          <name>Examples</name>
          <t>The following illustrates how various inputs are parsed, in terms of their impact on the resulting no-vary params and vary params:</t>
          <table>
            <thead>
              <tr>
                <th align="left">Input</th>
                <th align="left">Result</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: key-order</tt></td>
                <td align="left">no-vary params: (empty list)<br/>vary params: <strong>wildcard</strong><br/>vary on key order: false</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: key-order=?1</tt></td>
                <td align="left">no-vary params: (empty list)<br/>vary params: <strong>wildcard</strong><br/>vary on key order: false</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=("a")</tt></td>
                <td align="left">no-vary params: « "<tt>a</tt>" »<br/>vary params: <strong>wildcard</strong></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except=("x")</tt></td>
                <td align="left">no-vary params: <strong>wildcard</strong><br/>vary params: « "<tt>x</tt>" »</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=()</tt></td>
                <td align="left">no-vary params: (empty list)<br/>vary params: <strong>wildcard</strong></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except=()</tt></td>
                <td align="left">no-vary params: <strong>wildcard</strong><br/>vary params: (empty list)</td>
              </tr>
            </tbody>
          </table>
          <t>The following inputs are all invalid and will cause the <iref item="default URL variation config"/>default URL variation config to be returned:</t>
          <table>
            <thead>
              <tr>
                <th align="left">Input</th>
                <th align="left">Explanation</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: key-order="not a boolean"</tt></td>
                <td align="left">
                  <tt>key-order</tt> expects a boolean, not a string</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params="not an inner list"</tt></td>
                <td align="left">
                  <tt>params</tt> expects an inner list, not a string</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=(not-a-string)</tt></td>
                <td align="left">
                  <tt>params</tt> items must be strings (tokens are invalid)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=?0</tt></td>
                <td align="left">
                  <tt>params</tt> expects an inner list, not a boolean</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=?1</tt></td>
                <td align="left">
                  <tt>params</tt> expects an inner list, not a boolean</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=?1, except=("x")</tt></td>
                <td align="left">
                  <tt>params</tt> and <tt>except</tt> cannot both be present</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=("a"), except=("x")</tt></td>
                <td align="left">
                  <tt>params</tt> and <tt>except</tt> cannot both be present</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=(), except=()</tt></td>
                <td align="left">
                  <tt>params</tt> and <tt>except</tt> cannot both be present</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except="not an inner list"</tt></td>
                <td align="left">
                  <tt>except</tt> expects an inner list, not a string</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except=(not-a-string)</tt></td>
                <td align="left">
                  <tt>except</tt> items must be strings (tokens are invalid)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except=?1</tt></td>
                <td align="left">
                  <tt>except</tt> expects an inner list, not a boolean</td>
              </tr>
            </tbody>
          </table>
          <t>The following inputs are valid, but somewhat unconventional. They are shown alongside their more conventional form.</t>
          <table>
            <thead>
              <tr>
                <th align="left">Input</th>
                <th align="left">Conventional form</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: key-order=?1</tt></td>
                <td align="left">
                  <tt>No-Vary-Search: key-order</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: except=("x")</tt>, key-order</td>
                <td align="left">
                  <tt>No-Vary-Search: key-order, except=("x")</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: params=()</tt></td>
                <td align="left">(omit the header field)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>No-Vary-Search: key-order=?0</tt></td>
                <td align="left">(omit the header field)</td>
              </tr>
            </tbody>
          </table>
        </section>
      </section>
      <section anchor="parse-a-key">
        <name>Parse a key</name>
        <t><iref item="parse a key" primary="true"/>
To <em><iref item="parse a key"/><xref target="parse-a-key" format="none">parse a key</xref></em> given an ASCII string <em>keyString</em>:</t>
        <ol spacing="normal" type="1"><li>
            <t>Let <em>keyBytes</em> be the <eref target="https://infra.spec.whatwg.org/#isomorphic-encode">isomorphic encoding</eref> <xref target="WHATWG-INFRA"/> of <em>keyString</em>.</t>
          </li>
          <li>
            <t>Replace any 0x2B (+) in <em>keyBytes</em> with 0x20 (SP).</t>
          </li>
          <li>
            <t>Let <em>keyBytesDecoded</em> be the <eref target="https://url.spec.whatwg.org/#percent-decode">percent-decoding</eref> <xref target="WHATWG-URL"/> of <em>keyBytes</em>.</t>
          </li>
          <li>
            <t>Let <em>keyStringDecoded</em> be the <eref target="https://encoding.spec.whatwg.org/#utf-8-decode-without-bom">UTF-8 decoding without BOM</eref> <xref target="WHATWG-ENCODING"/> of <em>keyBytesDecoded</em>.</t>
          </li>
          <li>
            <t>Return <em>keyStringDecoded</em>.</t>
          </li>
        </ol>
        <section anchor="examples-1">
          <name>Examples</name>
          <t>The <iref item="parse a key"/><xref target="parse-a-key" format="none">parse a key</xref> algorithm allows encoding non-ASCII key strings in the ASCII structured header field format, similar to how the <eref target="https://url.spec.whatwg.org/#concept-urlencoded">application/x-www-form-urlencoded</eref> format <xref target="WHATWG-URL"/> allows encoding an entire entry list of keys and values in a URI (which is restricted to ASCII characters). For example:</t>
          <sourcecode type="http-message"><![CDATA[
No-Vary-Search: params=("%C3%A9+%E6%B0%97")
]]></sourcecode>
          <t>Notice that while the input string <tt>"%C3%A9+%E6%B0%97"</tt> consists entirely of ASCII characters (as required at the HTTP layer), the percent-decoding step used by the cache produces a non-ASCII result. This will result in a URL variation config whose no-vary params are « "<tt>é 気</tt>" ». Note that the "<tt>+</tt>" character in the encoded string is mapped to a space (SP). As explained in a later example, the canonicalization process during equivalence testing means this will treat as equivalent URIs such as:</t>
          <ul spacing="normal">
            <li>
              <t><tt>https://example.com/?é 気=1</tt></t>
            </li>
            <li>
              <t><tt>https://example.com/?é+気=2</tt></t>
            </li>
            <li>
              <t><tt>https://example.com/?%C3%A9%20気=3</tt></t>
            </li>
            <li>
              <t><tt>https://example.com/?%C3%A9+%E6%B0%97=4</tt></t>
            </li>
          </ul>
          <t>and so on, since they all are <eref target="https://url.spec.whatwg.org/#concept-urlencoded-parser">parsed</eref> <xref target="WHATWG-URL"/> to having the same key "<tt>é 気</tt>".</t>
        </section>
      </section>
    </section>
    <section anchor="comparing">
      <name>Comparing</name>
      <t><iref item="equivalent modulo variation config" primary="true"/>
Two <eref target="https://url.spec.whatwg.org/#concept-url">URLs</eref> <xref target="WHATWG-URL"/> <em>urlA</em> and <em>urlB</em> are <em>equivalent modulo variation config</em> given a URL variation config <em>variationConfig</em> if the following algorithm returns true:</t>
      <ol spacing="normal" type="1"><li>
          <t>If the scheme, host, port, or path of <em>urlA</em> and <em>urlB</em> differ, then return false.</t>
        </li>
        <li>
          <t>If <em>variationConfig</em> is equivalent to the <iref item="default URL variation config"/>default URL variation config, then:  </t>
          <ol spacing="normal" type="1"><li>
              <t>If <em>urlA</em>'s query equals <em>urlB</em>'s query, then return true.</t>
            </li>
            <li>
              <t>Return false.</t>
            </li>
          </ol>
          <t>
In this case, even URL pairs that might appear the same after running the <eref target="https://url.spec.whatwg.org/#concept-urlencoded-parser">application/x-www-form-urlencoded parser</eref> <xref target="WHATWG-URL"/> on their queries, such as <tt>https://example.com/a</tt> and <tt>https://example.com/a?</tt>, or <tt>https://example.com/foo?a=b&amp;&amp;&amp;c</tt> and <tt>https://example.com/foo?a=b&amp;c=</tt>, will be treated as inequivalent.</t>
        </li>
        <li>
          <t>Let <em>searchParamsA</em> and <em>searchParamsB</em> be empty lists.</t>
        </li>
        <li>
          <t>If <em>urlA</em>'s query is not null, then set <em>searchParamsA</em> to the result of running the <eref target="https://url.spec.whatwg.org/#concept-urlencoded-parser">application/x-www-form-urlencoded parser</eref> <xref target="WHATWG-URL"/> given the <eref target="https://infra.spec.whatwg.org/#isomorphic-encode">isomorphic encoding</eref> <xref target="WHATWG-INFRA"/> of <em>urlA</em>'s query.</t>
        </li>
        <li>
          <t>If <em>urlB</em>'s query is not null, then set <em>searchParamsB</em> to the result of running the <eref target="https://url.spec.whatwg.org/#concept-urlencoded-parser">application/x-www-form-urlencoded parser</eref> <xref target="WHATWG-URL"/> given the <eref target="https://infra.spec.whatwg.org/#isomorphic-encode">isomorphic encoding</eref> <xref target="WHATWG-INFRA"/> of <em>urlB</em>'s query.</t>
        </li>
        <li>
          <t>If <em>variationConfig</em>'s no-vary params is a list, then:  </t>
          <ol spacing="normal" type="1"><li>
              <t>Set <em>searchParamsA</em> to a list containing those items <em>pair</em> in <em>searchParamsA</em> where <em>variationConfig</em>'s no-vary params does not contain <em>pair</em>[0].</t>
            </li>
            <li>
              <t>Set <em>searchParamsB</em> to a list containing those items <em>pair</em> in <em>searchParamsB</em> where <em>variationConfig</em>'s no-vary params does not contain <em>pair</em>[0].</t>
            </li>
          </ol>
        </li>
        <li>
          <t>Otherwise, if <em>variationConfig</em>'s vary params is a list, then:  </t>
          <ol spacing="normal" type="1"><li>
              <t>Set <em>searchParamsA</em> to a list containing those items <em>pair</em> in <em>searchParamsA</em> where <em>variationConfig</em>'s vary params contains <em>pair</em>[0].</t>
            </li>
            <li>
              <t>Set <em>searchParamsB</em> to a list containing those items <em>pair</em> in <em>searchParamsB</em> where <em>variationConfig</em>'s vary params contains <em>pair</em>[0].</t>
            </li>
          </ol>
        </li>
        <li>
          <t>If <em>variationConfig</em>'s vary on key order is false, then:  </t>
          <ol spacing="normal" type="1"><li>
              <t>Let <em>keyLessThan</em> be an algorithm taking as inputs two pairs (<em>keyA</em>, <em>valueA</em>) and (<em>keyB</em>, <em>valueB</em>), which returns whether <em>keyA</em> is <eref target="https://infra.spec.whatwg.org/#code-unit-less-than">code unit less than</eref> <xref target="WHATWG-INFRA"/> <em>keyB</em>.</t>
            </li>
            <li>
              <t>Set <em>searchParamsA</em> to the result of <eref target="https://infra.spec.whatwg.org/#list-sort-in-ascending-order">sorting</eref> <xref target="WHATWG-INFRA"/> <em>searchParamsA</em> in ascending order with <em>keyLessThan</em>.</t>
            </li>
            <li>
              <t>Set <em>searchParamsB</em> to the result of <eref target="https://infra.spec.whatwg.org/#list-sort-in-ascending-order">sorting</eref> <xref target="WHATWG-INFRA"/> <em>searchParamsB</em> in ascending order with <em>keyLessThan</em>.</t>
            </li>
          </ol>
        </li>
        <li>
          <t>If <em>searchParamsA</em>'s size is not equal to <em>searchParamsB</em>'s size, then return false.</t>
        </li>
        <li>
          <t>Let <em>i</em> be 0.</t>
        </li>
        <li>
          <t>While <em>i</em> &lt; <em>searchParamsA</em>'s size:  </t>
          <ol spacing="normal" type="1"><li>
              <t>If <em>searchParamsA</em>[<em>i</em>][0] does not equal <em>searchParamsB</em>[<em>i</em>][0], then return false.</t>
            </li>
            <li>
              <t>If <em>searchParamsA</em>[<em>i</em>][1] does not equal <em>searchParamsB</em>[<em>i</em>][1], then return false.</t>
            </li>
            <li>
              <t>Set <em>i</em> to <em>i</em> + 1.</t>
            </li>
          </ol>
        </li>
        <li>
          <t>Return true.</t>
        </li>
      </ol>
      <section anchor="examples-2">
        <name>Examples</name>
        <t>Due to how the application/x-www-form-urlencoded parser canonicalizes query strings, there are some cases where query strings which do not appear obviously equivalent, will end up being treated as equivalent after parsing.</t>
        <t>So, for example, given any non-default value for the <tt>"No-Vary-Search"</tt> response header field, such as <tt>No-Vary-Search: key-order</tt>, we will have the following equivalences:</t>
        <table>
          <thead>
            <tr>
              <th align="left">First Query</th>
              <th align="left">Second Query</th>
              <th align="left">Explanation</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">null</td>
              <td align="left">
                <tt>?</tt></td>
              <td align="left">A null query is parsed the same as an empty string</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=x</tt></td>
              <td align="left">
                <tt>?%61=%78</tt></td>
              <td align="left">Parsing performs percent-decoding</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=é</tt></td>
              <td align="left">
                <tt>?a=%C3%A9</tt></td>
              <td align="left">Parsing performs percent-decoding</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=%f6</tt></td>
              <td align="left">
                <tt>?a=%ef%bf%bd</tt></td>
              <td align="left">An invalid UTF-8 sequence and the literal U+FFFD character are both parsed as U+FFFD (�)</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=x&amp;&amp;&amp;&amp;</tt></td>
              <td align="left">
                <tt>?a=x</tt></td>
              <td align="left">Parsing splits on <tt>&amp;</tt> and discards empty strings</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=</tt></td>
              <td align="left">
                <tt>?a</tt></td>
              <td align="left">Both parse as having an empty string value for <tt>a</tt></td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=%20</tt></td>
              <td align="left">
                <tt>?a= &amp;</tt></td>
              <td align="left">
                <tt>%20</tt> is parsed as U+0020 SPACE</td>
            </tr>
            <tr>
              <td align="left">
                <tt>?a=+</tt></td>
              <td align="left">
                <tt>?a= &amp;</tt></td>
              <td align="left">
                <tt>+</tt> is parsed as U+0020 SPACE</td>
            </tr>
          </tbody>
        </table>
        <t>Note that no Unicode normalization is performed during this comparison. For example, a query string of <tt>?a=%C3%A9</tt> (using the NFC encoding of <tt>é</tt>) and <tt>?a=e%CC%81</tt> (using the NFD encoding of <tt>é</tt>) will not be treated as equivalent.</t>
      </section>
    </section>
    <section anchor="caching">
      <name>Caching</name>
      <t>To reuse a stored response, <xref section="4" sectionFormat="of" target="HTTP-CACHING"/> requires that the presented target URI and that of the stored response match. If a cache implements the <tt>No-Vary-Search</tt> extension, this matching requirement is also satisfied if the URIs are equivalent modulo URL variation config (<xref target="comparing"/>) given the stored response's <tt>No-Vary-Search</tt> header.</t>
      <t>Note that while <xref section="5.2.3" sectionFormat="of" target="HTTP-CACHING"/> defines cache extensions as <tt>Cache-Control</tt> directives, the <tt>"No-Vary-Search"</tt> response header field is defined as a standalone header. This design choice leverages Structured Fields (<xref target="STRUCTURED-FIELDS"/>) to provide a robust parsing model without overloading the existing, complex <tt>Cache-Control</tt> parsing logic.</t>
      <t>The <tt>"No-Vary-Search"</tt> response header field operates in addition to content negotiation and the <tt>Vary</tt> header field (see <xref section="4.1" sectionFormat="of" target="HTTP-CACHING"/>).</t>
      <t>This document does not alter the requirements for cache invalidation (see <xref section="4.4" sectionFormat="of" target="HTTP-CACHING"/>). A cache <bcp14>MAY</bcp14> invalidate stored responses for URIs that are equivalent modulo URL variation config, but is not required to do so. Therefore, state-changing requests might not invalidate all conceptually equivalent responses.</t>
      <t>Cache implementations <bcp14>MAY</bcp14> fail to reuse a stored response whose target URI matches <em>only</em> modulo URL variation config, if the cache has a stored response with a more recent <tt>Date</tt> header field which:</t>
      <ul spacing="normal">
        <li>
          <t>has a target URI which is equal to the presented target URI, excluding the query, and</t>
        </li>
        <li>
          <t>has a non-empty value for the <tt>"No-Vary-Search"</tt> response header field, and</t>
        </li>
        <li>
          <t>has a <tt>"No-Vary-Search"</tt> response header field value different from the stored response being considered for reuse.</t>
        </li>
      </ul>
      <t>When a cache has multiple stored responses with conflicting <tt>"No-Vary-Search"</tt> values, preferring the response with the most recent <tt>Date</tt> header field helps ensure caches converge on the origin's latest caching policy.</t>
      <aside>
        <t>Caches aren't required to reuse stored responses, generally. However, the above expressly empowers caches to, if it is advantageous for performance or other reasons, search a smaller number of stored responses.</t>
        <t>That is, because caches might store more than one response for a given target URI path and authority, they need a way to efficiently look up the <tt>"No-Vary-Search"</tt> response header field value without accessing all cached responses. Such a cache might take steps like the following to identify a stored response in a performant way, before checking the other conditions in <xref section="4" sectionFormat="of" target="HTTP-CACHING"/>:</t>
        <ol spacing="normal" type="1"><li>
            <t>Let exactMatch be cache[presentedTargetURI]. If it is a stored response that can be reused, return it.</t>
          </li>
          <li>
            <t>Let targetPath be presentedTargetURI, with query parameters removed.</t>
          </li>
          <li>
            <t>Let lastNVS be mostRecentNVS[targetPath]. If it does not exist, return null.</t>
          </li>
          <li>
            <t>Let simplifiedURL be the result of simplifying presentedTargetURI according to lastNVS (by removing query parameters which are not significant, and <eref target="https://infra.spec.whatwg.org/#list-sort-in-ascending-order">sorting</eref> <xref target="WHATWG-INFRA"/> parameters in ascending order by key, if key order is to be ignored).</t>
          </li>
          <li>
            <t>Let nvsMatch be cache[simplifiedURL]. If it does not exist, return null. (It is assumed that this was written when storing in the cache, in addition to the exact URL.)</t>
          </li>
          <li>
            <t>Let variationConfig be obtained (<xref target="obtain-a-url-variation-config"/>) from nvsMatch.</t>
          </li>
          <li>
            <t>If nvsMatch's target URI and presentedTargetURI are not equivalent modulo URL variation config (<xref target="comparing"/>) given variationConfig, then return null.</t>
          </li>
          <li>
            <t>If nvsMatch is a stored response that can be reused, return it. Otherwise, return null.</t>
          </li>
        </ol>
      </aside>
      <t>To aid cache implementation efficiency, servers <bcp14>SHOULD NOT</bcp14> send different non-empty values for the <tt>"No-Vary-Search"</tt> response header field in response to requests for a given target URI path and authority over time, unless there is a need to update how they handle the query component. Doing so would cause cache implementations that use a strategy like the above to miss some stored responses that could otherwise have been reused.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The main risk to be aware of is a cache returning a response that was originally fetched from a URL different from the one requested. In a web browser, this could cause the user to see a response fetched from a URL different from the one displayed when they hovered a link, or the URL displayed in the URL bar.</t>
      <t>For shared caches, such as CDNs or forward proxies, returning a response for a different URL carries the risk of cross-user state leakage. If a server incorrectly declares that a query parameter does not affect the response, but that parameter actually dictates user-specific or sensitive content, the shared cache might serve one user's personalized response to another user. However, because the origin strictly controls the <tt>"No-Vary-Search"</tt> response header field, it is the origin's responsibility to ensure that ignored parameters are safe to disregard for all users.</t>
      <t>The <tt>"No-Vary-Search"</tt> response header field alters the algorithm that caches use for URI identifier comparison. As discussed in <xref target="RFC6943"/>, altering identifier comparison logic can lead to security issues, primarily through "false positives" where two identifiers are incorrectly deemed equivalent.</t>
      <t>Because URL query parsing replaces invalid percent-encoded UTF-8 sequences with <tt>U+FFFD</tt>, lossy decoding can map distinct query strings onto the same cache key (for example, <tt>?a=%f6</tt> and <tt>?a=%ef%bf%bd</tt>). Origins should not rely on invalid percent-encoded sequences being distinguishable, as this is a concrete example of the false positives warned about in <xref target="RFC6943"/>.</t>
      <t>Incorrect configuration of this field can exacerbate cache poisoning or data leakage risks by causing such false positives. Origin servers <bcp14>MUST NOT</bcp14> declare a parameter as no-vary if doing so would bypass server processing required for safe response reuse. This includes parameters used for authorization, user identification, signature verification, user consent, routing, auditing, revocation, or any other security-sensitive operations.</t>
      <t>However, since the impact is limited to query parameters, this does not cross the relevant security boundary, which is the origin (<xref target="ORIGIN"/>). (See also the <eref target="https://url.spec.whatwg.org/#concept-url-host">host</eref> from <eref target="https://url.spec.whatwg.org/#url-rendering-simplification">the perspective of web browser security UI</eref> <xref target="WHATWG-URL"/>). Indeed, origins already have complete control over how they present URLs and response bodies, including on the client side via technology such as <eref target="https://html.spec.whatwg.org/multipage/nav-history-apis.html#dom-history-replacestate">history.replaceState()</eref> <xref target="HTML"/> or service workers.</t>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>This proposal is adjacent to the highly-privacy-relevant space of <eref target="https://privacycg.github.io/nav-tracking-mitigations/#terminology">navigational tracking</eref>, which often uses query parameters to pass along user identifiers. If an origin were to encode user identifiers in its URI, this proposal can reduce user tracking by private caches, since preventing server processing of such user IDs bypasses the server in favor of the cache. It does not interfere with <eref target="https://privacycg.github.io/nav-tracking-mitigations/#deployed-mitigations">existing navigational tracking mitigations</eref>, or any known future ones being contemplated. <xref target="NAV-TRACKING-MITIGATIONS"/></t>
      <t>However, this tracking reduction does not fully apply to shared caches (such as content delivery networks and forward proxies), which still receive the requests containing the identifiers. Furthermore, an errant configuration that incorrectly ignores parameters related to user identity or private state could expose cached content meant for one user to another. While this mistake can occur with standard caching, the <tt>"No-Vary-Search"</tt> response header field increases the surface area for such misconfigurations, making it critical that origins accurately classify their query parameters.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="http-field-names">
        <name>HTTP Field Names</name>
        <t>IANA is requested to enter the following into the Hypertext Transfer Protocol (HTTP) Field Name Registry (<eref target="https://www.iana.org/assignments/http-fields/http-fields.xhtml">https://www.iana.org/assignments/http-fields/http-fields.xhtml</eref>):</t>
        <dl>
          <dt>Field Name:</dt>
          <dd>
            <t><tt>No-Vary-Search</tt></t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>permanent</t>
          </dd>
          <dt>Structured Type:</dt>
          <dd>
            <t>Dictionary</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t>this document</t>
          </dd>
          <dt>Comments:</dt>
          <dd>
            <t>(none)</t>
          </dd>
        </dl>
      </section>
      <section anchor="no-vary-search-dictionary-keys-registry">
        <name>No-Vary-Search Dictionary Keys Registry</name>
        <t>IANA is requested to create a new registry, "No-Vary-Search Dictionary Keys", in a new "Hypertext Transfer Protocol (HTTP) No-Vary-Search" registry group, at <eref target="https://www.iana.org/assignments/no-vary-search/">https://www.iana.org/assignments/no-vary-search/</eref>.</t>
        <t>The registration policy is "IETF Review" (see Section 4.8 of <xref target="RFC8126"/>).</t>
        <t>A registration request <bcp14>MUST</bcp14> include the following fields:</t>
        <ul spacing="normal">
          <li>
            <t>Key: the dictionary key for the <tt>"No-Vary-Search"</tt> response header field</t>
          </li>
          <li>
            <t>Description: a brief description of the key's purpose</t>
          </li>
          <li>
            <t>Reference: a pointer to the specification that defines the key</t>
          </li>
        </ul>
        <t>The initial contents of this registry are:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Key</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>key-order</tt></td>
              <td align="left">Indicates if query parameter order affects caching</td>
              <td align="left">this document</td>
            </tr>
            <tr>
              <td align="left">
                <tt>params</tt></td>
              <td align="left">A list of query parameters that do not affect caching</td>
              <td align="left">this document</td>
            </tr>
            <tr>
              <td align="left">
                <tt>except</tt></td>
              <td align="left">A list of query parameters that affect caching</td>
              <td align="left">this document</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="URI">
          <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="HTTP">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="HTTP-CACHING">
          <front>
            <title>HTTP Caching</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 defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.</t>
              <t>This document obsoletes RFC 7234.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="98"/>
          <seriesInfo name="RFC" value="9111"/>
          <seriesInfo name="DOI" value="10.17487/RFC9111"/>
        </reference>
        <reference anchor="STRUCTURED-FIELDS">
          <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="WHATWG-ENCODING" target="https://encoding.spec.whatwg.org/">
          <front>
            <title>Encoding Living Standard</title>
            <author initials="A." surname="van Kesteren" fullname="Anne van Kesteren">
              <organization>Apple Inc.</organization>
            </author>
            <date year="2026" month="May" day="21"/>
          </front>
          <annotation>WHATWG</annotation>
        </reference>
        <reference anchor="WHATWG-INFRA" target="https://infra.spec.whatwg.org/">
          <front>
            <title>Infra Living Standard</title>
            <author initials="A." surname="van Kesteren" fullname="Anne van Kesteren">
              <organization>Apple Inc.</organization>
            </author>
            <author initials="D." surname="Denicola" fullname="Domenic Denicola">
              <organization>Google LLC</organization>
            </author>
            <date year="2026" month="July" day="17"/>
          </front>
          <annotation>WHATWG</annotation>
        </reference>
        <reference anchor="WHATWG-URL" target="https://url.spec.whatwg.org/">
          <front>
            <title>URL Living Standard</title>
            <author initials="A." surname="van Kesteren" fullname="Anne van Kesteren">
              <organization>Apple Inc.</organization>
            </author>
            <date year="2026" month="July" day="06"/>
          </front>
          <annotation>WHATWG</annotation>
        </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="HTML" target="https://html.spec.whatwg.org/">
          <front>
            <title>HTML Living Standard</title>
            <author initials="A." surname="van Kesteren" fullname="Anne van Kesteren">
              <organization>Apple Inc.</organization>
            </author>
            <date year="2026" month="August" day="11"/>
          </front>
          <annotation>WHATWG</annotation>
        </reference>
        <reference anchor="NAV-TRACKING-MITIGATIONS" target="https://privacycg.github.io/nav-tracking-mitigations/">
          <front>
            <title>Navigational-Tracking Mitigations</title>
            <author initials="P." surname="Snyder" fullname="Pete Snyder">
              <organization>Brave Software, Inc.</organization>
            </author>
            <author initials="J." surname="Yasskin" fullname="Jeffrey Yasskin">
              <organization>Google LLC</organization>
            </author>
            <date>n.d.</date>
          </front>
          <annotation>W3C Privacy CG</annotation>
        </reference>
        <reference anchor="ORIGIN">
          <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="RFC6943">
          <front>
            <title>Issues in Identifier Comparison for Security Purposes</title>
            <author fullname="D. Thaler" initials="D." role="editor" surname="Thaler"/>
            <date month="May" year="2013"/>
            <abstract>
              <t>Identifiers such as hostnames, URIs, IP addresses, and email addresses are often used in security contexts to identify security principals and resources. In such contexts, an identifier presented via some protocol is often compared using some policy to make security decisions such as whether the security principal may access the resource, what level of authentication or encryption is required, etc. If the parties involved in a security decision use different algorithms to compare identifiers, then failure scenarios ranging from denial of service to elevation of privilege can result. This document provides a discussion of these issues that designers should consider when defining identifiers and protocols, and when constructing architectures that use multiple protocols.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6943"/>
          <seriesInfo name="DOI" value="10.17487/RFC6943"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
      </references>
    </references>
    <?line 511?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>This document benefited from valuable reviews and suggestions by:</t>
      <ul spacing="normal">
        <li>
          <t>Adam Rice</t>
        </li>
        <li>
          <t>Julian Reschke</t>
        </li>
        <li>
          <t>Kevin McNee</t>
        </li>
        <li>
          <t>Liviu Tinta</t>
        </li>
        <li>
          <t>Mark Nottingham</t>
        </li>
        <li>
          <t>Martin Thomson</t>
        </li>
        <li>
          <t>Valentin Gosu</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+V9y5LbRrbgnl+Rlwq5iyOSUklqWa62rK6HZJdbKulWlezo
kB1kkkiSsECAgwSqii1rIuYrZjvbG3cz+7vz3c53zHfMeeQLIMhiydK4I0bh
sEQAmXny5HnnyZO9Xq9VxEWi9sT5TImTrPeDzJe9MyXz8Ux8d37+WhzK8SxO
p+LZVaFSHWdpS45GubrYq33dGstCTbN8uSd0EbVaUTZO5Rw6jnI5KXqxKia9
WVEsRrHupVnvAltqatnb3W3pcjSPNXZfLBfQ6PjZ+fNWWs5HKt9rRdDzXmuc
pRogKPWeKPJStQCCBy2ZK7kn2j+qkZBpJI7TQuWpKsR5LlO9yPKi3brM8nfT
PCsX8N130Hl+rq7MBxOVi9d5VmTjLGm33qklfBvttURPIKT495hn37pQaQkw
CGF6QtTALwb2RxgBUfQtvoOnswznjV3ovbt38e/LaT/Lp3fh3VzGyZ5w2Ohd
Tv96+QBfwjtEhm+XxLrQfX55dx9exRdK331djpJ4fDfsALvN1SLzTadxMStH
/XE2N6PTXz1ll1DfTeRIJfpudSGgnwRQrQvAVAP09T6uXdj+rJgDXhmaHixv
qXo08J6oDdySZTHLckQ9ACHEpEwSpp4jwGUaj8UR/j9LJL0GaGQa/0MWAMee
+DbLpokSL14c0kvFKI7+GnHT/lytdvu9ytV8KU6zuUy37vKXUY7f/3U8g7/j
cs7LVu/6JI5msfhe/lLSizxD7lJRXGT51iOl2Mcv0EV1rFaa5XNoeEGk+Ob0
eE+cPj988NXjR/ATSZJ+f7W7e8/87h3uH353fPKtfb4Lz8/OT98cnr85fXbU
e3787MXRGb989Gd8+eN3++c/ftt7dnL46gjbIVCFzKeq8NSl0nEWAb339UKN
+5czWXjyFkaaPDPfiBfxBf51VgB7yjzCT9xa05+e+Rv+xCnw9n5fXMhU/A3I
ENYo9W8Zu/tpqtZ8ACDA+8UC0Hmcjvs0VAoo5jnhTxIk4v69+4969/7cux9M
+Pjk+el+42zjdJLLTVM9xg/+4Hk29H/Ur/JM0HcjT/muqyS5AYVf9na/9Ch8
c/qiEYFlnmxCHzT75yWSL3v3HrVaQAIh3313/rJ5pijuNk0VG/7zzvVxj8TD
yf4PvfPT/cO/Afv3Xh6fH3+7f3786uSsccaLPL6Q4+V42jcqJ87upvKiV+Ry
jCqxN4+LeEqiToeYOJEX5rFMeufmY/HSf3w9Wl73xVm6jFReR8hrVaiVV4SK
g1xewKtsUlyC3dDdxD3f98XfpdYAVr3779Vkkqvl6uu1vPPgEIwMwpM4RKy/
Oj3+9viEpO6jh39+2Gr1ej0hRxqRVrRa57NYC6SieBKPCRsiUpM4VRr6E07/
iiKrGGhdMZ7JdIp4nGWXogBzDhSE+K+lypcCLIFFlqq0EPF8AaNoa9j0xTE8
S4s8i8oxjIDNhu2qZdcegnkBxhSYX2KmJOBVTGKVRF1xOYvBTJRJkl1qmH8M
owut8guVawRPx1NYX/wXjka9y0KMVV5I+HAhc4Ajm9CYdTCjDEyEAjoDfVsA
GpJkKeRkosYFfU6DRB4stP3GgJ2REjBmlsM7YFkeFkyugk3YRZkvMq10n1E+
j6MoUa3WLTQbCQGI7FaLsGrwI96/D/Xohw8CFmckNQwAS5CrUuNHAEdW5og/
xgiNKOQ4zzQsmmA7FqfKAIGhqQF5wDE0mXmmaV3AWoXJQr8K5oHd4ssF9A0I
gfGY92hRd96/P1MErfiyv4sdI5AfPnT64rvsUgH+u0KDkC/iOcA0L5MiRiEA
TTWhCaxF7paRCXTtptAXRH8JrLMOVg4XQyaXcqkNbFIDLSQLMHvwn9ANrl6Z
RPAazFteVJ4t2O243ogIt15lilSEMwWYumJUMiTufUxdIqBAGBpnzy0kwDHD
2bnuI4HUhpi4jJMkIIA+cpISdVpuJmXPYW7hHaN1cYKR0uM8HsFwQLke+w8t
7j2BdJnKC5BpCXVoWVmAj6NhAYniYYJTlaoc2GORZ6NEzbtEsZc46ygGSs9x
eWjFqD9+BigDRgAQYP5xvsrcEfw/niyblvW4sIzqqRXWN1LjBIQhD4I0A3yM
H35K9uwSf4J+0DdhUiZE+A8XRGF/I5w66Dgg3sLyRx0ySShHsknHCsGHeQAi
ChRJZLgiLWnbeihBOxope/eqd3l52UNV3wObxXw8FKz7YdG9nfPhQ188B9DV
lZwDY3UtwYP3yHxOnOsHRlbnRWvApOUuRh8LELtEOH2zqLGKukw4+F8aIdR2
Lq3Wf4M/5J8Bw2s5Va0q2e+hzOkRePRpq3U88YTJMAXw7qj+tN9F/nRDIcZI
pNAi4bpJkO1LWHzd2Z4caFK/ZxoEpH6y0y6L+YC7awv6MQcXq5ybH2NYFwlE
1u6Y6e4DAZpF8rhNQbLISFwC0MQLhXyHqoT5BN3vHkt6IJI8AypEhQd8yUxo
1di7NLtMV1G4NWuw6IRRS622QIC6GqtFAQhYsMY6jtwcT7LC8HGbeWpUaly3
dtdoElD8MTOFMxUk8fk6Nkf5nytYIPguirEzmIXTYcTVQAljxGmRA4+CNIOe
QOGpS+ADP0fD9XMQuIB1RdgAYxoZ+iYGB4j09+/5QY8Edox8CzrZSm/sDMa+
gQXjRQEI9bpjDD1PcEExgtSHD8Balr05SIUE3uDk378H7GEPaBckSYkmHK2B
QstaCvqWmMWaZKxtAFGlslhxypiVS8Xy01Z04vJlILI19WZGZXKWlyIriwWo
0EmezZnIihxIoyQJSwNiA5g0SM/MqBMHHk4MV1zmPI8phpmoF1riZAp2XTGb
s6i23xEvXWbovIG8BZYAgQsWboJEw5oaOwC/KXFyGB+EuP8Ligw5SpYgPQu0
N8BCyFhGgk5CEtS0vOtok+aClhRhiDCqCfjUktXba4X7zzubnNRbYLkgswUN
OlYbmFWy9kBVNezsA/+XKC9I0FUMjZilPTA7mk6IVMLh5Qx03nrlMMlQJPHS
MQT9jngepyhduriAbLTA8qmrRULWFlFcxmZMtNlkcbKPwEUGcstJYhJeyzFY
d2kBHPgciQzEgVok2XKOUC5A3i2Yo82MvZOCQh5V5JzpG1bGWdcKiBsESlJS
nGiUg2micvcGrUZCgUqgX8BKqgrkQ8MRgATw4SLkiqsYjYVXVe9DK8M224oC
xAF0dhFHrBhy9gZYLwBExtyEkQ4DX8bNrT5vWF/TrN5ZhPphDuKKbT2JFv5F
nJUa9IQuyCpyABoJoeVEwVv0NozNRCLWWsddoZDq40Y+cSacdx+0MSb76Poc
ZukF2hcIHSL2yMlVzQY0SgEMi2vRfvnm7ByUCf0tTl7Rv0+f/eubYxCZ+O+z
7/ZfvHD/aJkvzr579ebFkf+Xb3n46uXLZydH3BieisqjVvvl/t/bvNztV68x
CLH/os3GL+A6ysYlYZ6s14ysSmscos7WrYrNfnD4+rf/ufsQGOFfwO++v7v7
FdA9/3i8++VD+IHLwaORfuefqJ1bIEeAdrAXNIzHchEXMtHkF+gZan+0CgCb
/+UtYubnPfH1aLzYffiNeYATrjy0OKs8JJytPllpzEhseNQwjMNm5XkN01V4
9/9e+W3xHjz8+mmC1Nvbffz0mxYYkrX1YGMDaRwoBqitzQsIUq5NS0U0TCtF
RohiFQDiBDgWBQEwD/H+VdE37aFz04jdPn6LdP3+PXyALhd76fgvVst1l4zs
NqkNGOs7xJ9O5emNUp65A+cp2nXrr4FKczUxURGjWit6CzgenXS0rFG8Wv0u
UTn8Sa/oBW+1fE4d1zDhCt8lGvRClC1AxpDjOK6JEtTvpHKK5QINYUQK90iv
MS5Woo0L8osQzaayRnMgV7QRhejyy9EXZ0p5qChkb5fcxJPicQne7B6wIvSi
hTcScXFpQy3UOYhAfAj/K8gVdxD/9u9ityvud8UD8dt/9Bt7A6kOfdT7i3Nv
z3FXMCFEK5hF0AcgcecVRjCEwbuhRGQMdBUwrFTa9Y1TYjSiHNTEut9BiU0K
dDV4wYC9v7VqHzOlbq0IY/Kg6xZks3nMZgubsyTqRuwqkLqDscJI1YP+fcRb
QzcdQMtxIWYcSDLGDmIAt3zBpAZpoWlNwWk1uGUpM3Re7RCc+yJfAq/UgRll
GRqXVUge9B+th6VhHHY71w4CyjdNAYFETJ42qmPucqRu6zHZ0/usY56vjCOs
wsIxbJDQWBZVLBCdoAgwXxmBGKw96BIb/KMmsbJ2Los/oHm0bTEKCDAGa9l1
QzFzWxBdoBC4bA5rSkzCBjJ7gBGb/vX4eV8cWzuNvSoXg6uG2SmCyKEpst8d
1Ds47qREfnDyT4t5PJ1hwAnD3A4eDHsHTTt98Zzb+Y1zVgIoSgNcWbQDMqGh
CxbQ0vooIMkJ6AKsVGRN73X9xccRyHoBN4DEIijRY/TIJzUgyHaMc1Y9NCDF
PL3ZT16ZJTY29smqMqbnqhBCXyPVOAiaq8Wyf3Oxg9OFBaxuJPQ5qQPDO5IW
w6EKLGuVF2g7JKB1uxi4BI/Whj+pV8c2ZZqg80xIQiRKnrCROJURycAmbFtA
Me6wJxHpH1rfiH2vnp1zHGtHgWQpZCOk+p5EtYqJDjERWA+WbhJPSZfeEkc+
QvD+VhBaaLX2xQB3RV07we0GvPTa2/ROUu4hhOJCL+RYPWnfa39omQQLEzBr
7QkVk94hsmJta1AzGADdR2PwpgYDCv7WRUqr9Yl7ghmhV8HhyD0vo0E57uz8
CyBSgjEkmlDQ6XSIqgabPhqwCmt6ZeRPFTn0OYio+aJYEsRdUXsbTqxr7Lba
PGjLIi/ZDdgE3c97zBhMIuvg9KS1cy01dQzjWRkBQqypT6CakVpeo2HraOEV
BAXg/CKjDFZRGCLpL/g9dNeA6LU9buiO+OW14br3t2zQDZ7yY7UOjfytWoc6
XKvFhvbg9WzsgAl2Uw9EsJkYbPpmYMJWA+KiAazDLklt85tUXJkkXbslBpLc
xsnWk1kfO3kBAnXAvsWArSGU3Ws/Pws+J8lZp3FUXETjFQB/etsOlHf7Z9Ay
KKR4495CAR+8wvc/8JxGHCUdguE9H2T5gGyZAZLGMPBzbOiixN3LdaPtkMYm
eZyGTlinbwFAUGvjG7PBiZ6bItf0vBXGMBJvjNBUcX4DzqwGkkXqKCtm4VyN
JQQTRYYJXhijyOL7I8gDRkuNMG8cENC6YUC/wDUs1JgefbhQum5Enm9T5f8V
gvNQNlEbv/0ktOYH2o7QKkNbMguN9Y8ktWBeL6AXw88kTI2R7TY1R2DhDHC2
tfkpCYYpTxA0TxXSrSaHr7DfoDnD4tiJFf2n4aZVOjLbd9gR7jMtFsmStoyN
cEW22+E9GZTY8BOVIxqmOPEmwD+WFsmHv4w1b/1uwyO0fPz2k5ClH2g7sqwM
/anJkjv/RGRZgfTmZBnC8lnI8rPQZAD19uywQpanPDPbqOq3HKc25cTs0lTc
F+N10m6jSjn3Z0tEUagck47QZdRK6SBRIOZNrPRP6E2Ns2ka/0P5zI6RGkuz
U7J5hJGayYsY82PQRf+lROqilhPaaeYt6VmM4T1OoGCTXo4Rq3IElDUBs3gk
x+9cV1XknNN2JW6iWue8gh2DODBW2RbnSIMP066Ey4IozMP1cS8T6KMmAzxL
INo+JtDuk337aqOf8P7WZucALdyNngaauBu7YBt3Yx/WyN34kbVyYVkoeOCi
AJWAldudROwM7DfGJiZZQ8iqilDPfuHG+NaRBwq5+7E4yHHUGMPcsJYkiez4
ExknmBEZ7PkjSY04vJc0zAMt/JCHm+e1hgoCAbPORTQuRjBqX8DCXue7AAXe
Es84zclsCHrn0ac88HYzdpCVmhmJA3zUf9Sl/RDaEmJ9FucmEdVu+fsNkJqY
c842/wZC+BUkGTLqtX9+BVwSAj/xn19bv/a2/HNn2w9v+AdAEMO1KV7DKhaq
GN0TO94W73w9yr+pvAx1insZujR7KEqBZjaD8OTp7vCPAcFliMl2ZxMIv/27
aA/lsC1++4+NEGxBDatAuCytq81ANE61AuEVQfhRQFhMBBD8vsX4eDxcB8JG
PITwXQNCXUB5QYRRsTgF+zmOSKaQIbGl9cHZBWwNqegmIsjO9xlm5aTc6dat
thczRih8BlHypF0Jk7SHOJvKttsVpv7oMJISmtybycNQaHvFGYFxfg32m+wY
VX+laZyNjAANQENyA0uRwTBojGO2PBiXI+X304rsnUqZiAwBdTYO8/TesIkE
tpuNDRRdP5tQwH7WYbqr0iwYJtyfw+0n7J9CWMH+4TZrg+K6PtJnGCYYw8mk
TziM6XsdQbut1t9J0HYKawjaDvN7CdoMs47StppNndLAuV0rowkW3uRFDxLT
VESZ+rQSmaDraHbwOPNKJhnMCZP2zLZwloeJKJJSLOf9G4tsM8fDek/Xt7mp
1KY/H2Mn3sAAq67bdnZjdU7XmDhd38lWIzXIlPUjNdsxlTntZPO4WEkx3mQt
XIe9JiH+sSOF21RoxPpdKQwHhZtQ8Dvcc4Kf1S0meFDfUYJHgWu9f3Z4fGxF
CO4wnNE/0YGu7MUcLMFpcw702xj4LcsXs3gs7OlunzfWfAL6lm/T48yxzkpu
lt3mMED0DRCnCqyhsaK43b2r+wdi506HomAeMDocB+/uiZ2z151+E/RHitLV
/CQWKh8Ds/Ywfbw6g8bMt8rnIfCU7mZBZ3jqAPCEViB4c/6891jY8WkSmM51
8Oqlh2Xt6flbZTHpPTbg9Ezb3iibB6DZc/k1+CwgHsEcB1yBtN/k0IehSh/1
MofFLLggztMeUxd+Z5WJSaF0ZGejYNUAC+UTdoWO53EiaVPMnof4f5e/uDIh
SVlJMWbFUD6TzVWo52aaiNax2HGhRZszoyjthSc/nkk8YEOx6fBw2N5NTjXd
Pnxwe/+rO7efPbp9cO/2V1+GZ3vw6A5t8AMYiTIHLFClGW4frrYe+owRnioG
MCcrAIsdqW1CEHhHLN4oSJfIpco75vxQjb1gXLXg9EVz4ILDsAt7llgGNMPx
HRP5Jd/LBLfWhzYbUzVQ85Nf/J//Jv7P//of5Bz3hT/5hGC0h3fguZuepVF7
+s+gC+CYY2I3LSGe0kSJRMJG7Gt7jILzeSSVRQmO+/FkYXaY1mpKebgDOlGZ
13KpBNZUwWdzOuVSOBwUeLgK443B8RlK9qIUMskpGUMnOXh4KuvylOf/ZHe4
4Ys7+MX99V8wvdy+fw+/e3Ddd56unjwctlrIIToTeD5WxzRJssxgVrhGrNFu
zrw9Pqm0Io1RZMgLG9qlo60ohjwdmMMM9nzS+1v+TBOr0ADFcyDQJGsOY19m
IMZPX+jtIV+BdQAP9we8XQ//PBgQRgbXA+D0eDNDDNyTQ5vnVEsDC8Q3Rys4
J8lllBDugEfnQMPAXSCS8dA5Zc4tJChc1CkrwPNhkereGcXf+kGiSh2wCkmb
XbJNMRbunqwUt2VJkLjsd+gPBjVA2ae1HT3OvzJdnFZBxaf2rMJY4s4tnZpB
YBYyzk3ylMnp5AMfjtTkBNk/L1O3mXm93jJn7j4ZB2Thoe8Yj0gZIdHMtNI4
s43vng5pzRtfTrLsqXwy+uKLL8YburBfjZ8Mu+7kPYkzzhIF0enWv+83b7jc
02uS5ZbKwmcHZEv5eJ/2NFalBrOzG+RF6Yb+V7Zn/9glZO7+7AZ3BVMVBB7c
CIEH/x8j8KABgXUpt7on7/Ib6+LsrJk4mxIl0OjhwM0A5dKAHKNaUz6GvgVA
7gCpzcPnPn96e+/n/nrgDj4euINPBlxTls1Kj/9cyA+hcVVP/lCMXw/Retpu
THEmbVpHsPWKX4D5ez6T6cAcUPHWSCHfmXR7E+7Dw+Osdnew5f6ga5Kb9gcd
Ugv0+MA9Phh0uq42Bls2MGtOXaT2CNxbd9BKmGx/mV4rFMjbxjY9bNPDNg1i
gaHZsIJN2uatButqG8FEtSbw4x6mYegxH4XkUFQTMLWB0UWxjcxSUfyksibX
Ut8fAPvB9rAbOq3OHKhUx/9QVpmRiUiJUdVBzGdrTVii35io9h4/+ZFcbHz2
9Zoxq6Zq9ZOf3kLLn5HBvIxj2GqA+Q+bYbt2hN1tR9jdPMKZwQDiDv66A89a
YTIKG9aVyNFRqcJAzra2QOg3K2uMuLOUBUkyCu/TiVKw07URb5UvjSgwdWeM
uZ6N7Dl6b3sa4xSrAZQLW1bLm6mBk8I2vkm0gcmeZVyRyTn9Nsa6pLCGdWb4
5MvEpPpsX3jEGe/ro/EAu2LwZ1i3rurpBeEFTop5DsK0EP9KWPoVFhTEfWR+
ik+1Bb26TfFxCS4YfEfL04fVh0+r8fZfxT5/4axVDigEPllwaMdumVFQH/yS
q6Hv9/aj3Se3v3zsnthjJAuVI4Xq1bhWIx6o3//8t6Bj+YTjIsNP0PHtyaNh
0K+a3B7Bf9GQEJG6xAWOL7vqVrY0jD2+/ObO8+fPj4LIFzISbV8a5AHOzDc7
X9y6mkwm0V86Hmng8n0xtDBYFFbnpoHJC6rTMvyCvcMo1pi2oSsrocO5DV0v
8Kuyyr+KAwccFZTjCE99WT2LDbG9w9n9ewHOxBfDoN8hvfRUQxO/d+/+PXH2
ev/wWcNK+H7vVNa41u+dm/ZK+z8+Pplm4g0WXY0wspnPffQw1pZwoGMTQuRY
BcexNB5jrdQckxWRSEdoA5rc8TUCTp4f+qg3fgZkzEYWNlC3Dw9vP96ttTiq
tlD/+79DE5JFtCWumoUoB+Fs5cRbtipNCzesqHoJbW9Xapx0rylN486puvBu
Y0VEZgXp8uXrlVSovJw5C8thale6xRS9rMrhYVj/j9bBFagzEFENBHsGWsMi
ai4UweNTFLdWGMlE/dZlcAZFmDqBp1ubyZ9WVMbQaJZ+SGe8R+BR++f+/f6D
BvTaylmMk+CMMqomqnTTA4+gyLNkCKyec5Uf3b1Zgm1wOpbL81Ht2wQPfhvQ
eV8gUnSUejzLcK8jwZRyOQXgzvy+0nPskA+5N+VTB0V8pMgzLIDmcmf5qK3d
k8ug8ySTrg4EHdegMwK4Dom6Wpm+7SfJpvH4pqebM2BuypNFezeKuFgDllcz
ZY5SNc0KQxJWrA+x42G1nx2twmV96Kt/+kXtrJTq8EUGk8Kc3A2oWAdlGI2m
YUBWBmtgUNwuMW3xvL9rv0K42hS7Co+yb8ccnBFibHy3TYWllIDxMkoJyRV0
DrIEKKtQPVfdzhRIskf1sX0AIBXz4dhTSbn9ATgOasDlYVVemBICOFtM8+aD
Eo2yzWxhBWKKhAigYoAHXwebJ10pojozjFPrHz0lyUkvwJsI+PAIplYjGjKW
aS+JuwkAcluazndaJ2IpZSMonGLi73zOl/tFu5g198daxWFvW/MWD+aLpgZl
8KroYvM/qJ+AANLawSr/yNW4PLpd2dwVQia04zIlpm5CA6i8edxFVAJYuavW
V1k6fELVfzcsHlbZ1ba0gqnGSwlOsDA2e57rF4Bq4OsbXA3bRQYQLqsnXUz5
MmA/PpTj2YmpuD7brj/8ElQXJpdvBEIUd0rhW/K65gt4nWtX7TkjIo5ZTUYX
EnhnqvCAANUwZGtHUnlAcN4oloNFmqjqIXuxSPJzLIuTBzWU6wD2W9/QAR4s
xwYt7ZkiAwRzPrVhPsEAD9UccUvBBdWMxvWsQTtiKIu5DnlcLE2xzlShIhOX
cknnuCaTeBzD6gEGkix7h37mjbQjk6/VS3hkSZvqEoktceznKs7Ib7RFc2ly
VLoPN+Nh/eN3dUcRQHRlgVclCO1uu6UocFKIwgml0c0U12UnEitM1SLWXfra
Osh7tCwmugJG67h4SVWxR2ZpfnrrpMw5IR1w/tPPZKIZilkBlsuH26qZJR0s
MfGMGGxPNxov4mtZydsMhjG1t1dqtoI6BIqOgp4SqYuTH86oeCnw6SmxKTz4
6a0fwwPtQzF8INvAxkd7XJ8aNQlVFUO5v3KEybzmQ4QroFMhxjwyC2vB2xkt
GXh8vjItU6XdlNtBE4tK3mBwBMn7c0X6AggagnwA8Tu1JAFRraGRBfWhOwHa
0gtdJ6AKJrdbBrFzzMSldTlXkfUqMCEDRP4lcDmYY1yZEamPE1S9Hu7W7Tc2
HfEgE4DQ73hwawF1hNodHdympAcpMTtngwY8r2+egKyveT9NtGKW/Hf5ILWJ
VMOIAWkHwH0M94abPZXO0XeUcVT32hhyK3zHy64r/emrIXIVUG8Y1OwTfWMD
BVffzyfz9uXWKoT8DoF1+btBTaJcMcpIs0C/5YIMVBNbXYI5kkYm5atWCrAv
jjIKzGTiksrvB8pvxWSlFbCWKroj06XXGKzNYXC8h4vDryuGDy8hjZPZ5eLg
5Eip1KwqBQFAMZQ030NjbcmgpOgcN/vyWL8z3C7xOg6UfbF2qo1pgM88VkkI
GZUNHjLaJ6ogHTnhurRI2Q2mICt8c5kAlpRCBa5Gtuxs18ZaPAqxVam5hAf6
QQEY2w8ZxXqBOXQRixReTCQBsiCSOH3XtadEuRf7uRE6pCEkuvYY+tEziQ1t
iVwbQj48OqGzprWauN1mHDKphlcMvIAecyqtRZoI1wVLhOPlFT3CAHlVWKL5
HdhvJohiamXFKagjDAvASpirBKx/V1dEK6XuQ3vYlnaTRdAAxCo7Zngomrxn
BKfn6tYjSjBeQbXEjSfNpmmIKWsCIsC0KNjJnyjcpjGvP/5HRUpl9pIJ+i4w
ecPD6rZgGGWBYjF4DhLc9P4UNnQqFrz5Mh7FCbKPr6rG9YbNvQmBbpWm4ho5
xLHO1RRpYGJuccA56JsGKyhKwHAFW7gsvsmoLg0doYxz1xPklVDlvqbQcKm1
rYn2FO+7+erhAyrZiSOQcm1qzSEW0hV4DwlzoJEndIsc+VXxHL5OMPM0z8rp
TLT5UCjXDb9Qum02jnCr2Q9jz72EZKvmlVp6gK4Ds9bIHI6MzVUvlLuuXUze
RvntNlc1Rm+cxSGH3YddmJrWS58ijnOcy4Wvrl/d5spSY2PQloevvL9T2Zly
Owg2pus3EDq2MjaVKkbpxkGUhLb2183BQ88uM0M3LWPgqxHFnk0WKwvsLB1j
0WULkKtOV10PENw5hQBH6OfUSAIrgNo1MfZImbtSSTQW0+aY7kCCFchHKJRM
ynGGZMPGJZe2N8KKpJlGYxPXkxQlCs0aZCvVw12JQXs7igylkk9kAeM1qqrf
0XIhUX2ydDQpwUHUmDmT+NXxHkcgTFEMKiardMjhvuo3WxG8Y9Bl7WQpe2we
0p1LVOsRAAie08d8hSaaxLAEFOyUJdqy+K9cXWT2Y7rdY2l8Pst6PS9rOZqJ
Ch3Wzd84ZNOA7dl+vEconscmTb7ulxid67OA6LYkVgqJwmiB53ogGbwtbRmU
9wjEMBiufKcWhSN3sEowReUpUQzzXLdPQOvh58b6fmuy3m1xe6TEwGbw0L05
vmYA7BiUbUQyr2fdFsZ2PckNC0nAl2gdZ4ZzZZKDGFyypcXh6UJZncMWpTMV
7SlFvpkhDaNfIHGqNfdN9GicYPhC0Cm6i1iKQo1naQYyeOlMjLewUmAMLvtG
/J2hOt7p+Gk3Xn3HETRgQ7oTznTRk4tY082gt6Js7p5auYodd6iC90vKes2J
l3A/AKv/szK75e9TW7EucR8tz4C1sd40hp1+keMgB3kGtkCy7Jl763qe0ij9
H/Ne0uBqOmHvsfMTvdGNd7e41D/h0uUvZRN0MUvtsh8CVsf9C5QfdKyxyuBc
ChWLHVmyv1Rc+Z6l9srXKGJxs5YCHkUFMXwHGJ7SMCauvYEPi9rgBK1k1Zar
8ZIC7Bll3Ypsw6gFEgr1dXykjRQ0BqWzFEHsXmTueiTqn66lchKAqsKjWcpK
863dkxGNayICTH/s+tjCtuHTjpN/fLWPKZ1LlyG5CHIBfiQGWyO8PmXdlYkf
PgTSkVbAwU7YJ/Xm7/goqf45FpAiiyc09sWO5cS192I0XYvhaA7QSEduxiq+
sAEn47rWqnRVyO15maMKmNPeCirePEdmqepnNkwDg4qNVF2NrBGyyLf1ZIru
cO4Ijr0MdsHUFd4BZsOfds54fIbuP3FmfGCu26Qt3qwFwsGoKNVDHoOYZorS
5tJNGyC/6T4m2jnS0XWZT+gUIzxjrY5LBCNX0AMcNOfkxxhVXExXQpmtaive
EUCYO/oRCZaT5grG7n43j0eSfcf7J/srgg9zs+jEFm2QihNoAE/p01h7z5fF
hd0DDA9hG/lIF2QXjRdkix0coBOMIE7VFBCNJZK+tvx3eXnZj2UqSQFwbWza
Y+TbowmPlX/3r1AVfNPZAxfXdbzX2lvZ5W61UOmUGt8BjHOJ4Q986PaGz/Ey
bnjrSze1Wqe2eD6+qNzI0GodZnMCDV/tpEBSVO6ofgl6UAjqb3gy0M55DXbd
fVl8QQt/261fQ1jvtc2BRWrU3mINVi81NAtB15N38Qzf9StSvYP77jfGTTR9
mUNttIOEs2zjleww+4tYXbZ5a9hvDD/m2zie0m0q9x/xHvR+tSuDJjaujZ1b
I0MmCdqpBKzs0dugSDp6PjcN2UFXR3QPzAJ7oWLTeawm5kLHhfcwyLHCsADf
PwjtPO2g/Z/FzDfGH6sUjucrtYJLyOjg9jntpwPHy8SKMF953q0YiA/K34MJ
B4lGAcxr0ooaU408zC6lKUi7E5Vf2/+pt+NUqaBsABZX4Jv8NPpE9cAPB/c5
6uNunmV4q5ekUL+2FofgLEB7LHfVViKkZ2FEyXbd2K8tV7FVv7UOHX7r/dJF
slhXECXz/hgthkRFU2Kw1vs93rVU0RMOTrQ/1DMzRioFsilsMBHj0lSuMCc+
Y6Wuy+kUD5BiCHe0JO7Yj+RcnIJVDP/+vkyAvbHW2Xj2ThHrXIAweTk+UfgL
75suxTlQr4RfL2X+Do/Lolk1k3N+Aj/A+8zm4EPDgx8oCAKPvs102fq/2Col
yyKCAAA=

-->

</rfc>
