<?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 tocindent="yes"?>
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-httpapi-idempotency-key-header-09" category="std" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>The Idempotency-Key HTTP Header Field</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-httpapi-idempotency-key-header-09"/>
    <author initials="J." surname="Jena" fullname="Jayadeba Jena">
      <organization/>
      <address>
        <email>jayadebaj@gmail.com</email>
      </address>
    </author>
    <author initials="S." surname="Dalal" fullname="Sanjay Dalal">
      <organization/>
      <address>
        <email>sanjay.dalal@cal.berkeley.edu</email>
        <uri>https://github.com/sdatspun2</uri>
      </address>
    </author>
    <author initials="D." surname="Tishkin" fullname="Dmitrii Tishkin">
      <organization/>
      <address>
        <email>me@dmi03.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="21"/>
    <abstract>
      <?line 41?>

<t>The HTTP Idempotency-Key request header field can be used to make non-idempotent HTTP methods such as <tt>POST</tt> or <tt>PATCH</tt> fault-tolerant.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        HTTPAPI Working Group mailing list (<eref target="mailto:httpapi@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/httpapi/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/httpapi/"/>.
        Working Group information can be found at <eref target="https://ietf-wg-httpapi.github.io/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ietf-wg-httpapi/idempotency"/>.</t>
    </note>
  </front>
  <middle>
    <?line 45?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>In mathematics and computer science, an idempotent operation is one that can be applied multiple times without changing the result beyond the initial application. It does not matter if the operation is called only once or tens of times over.</t>
      <t>Idempotency is important in building fault-tolerant HTTP APIs. An HTTP request method is considered <tt>idempotent</tt> if the intended effect on the server of multiple identical requests with that method is the same as the effect for a single such request. Per <xref target="RFC9110"/>, the methods <tt>OPTIONS</tt>, <tt>HEAD</tt>, <tt>GET</tt>, <tt>PUT</tt> and <tt>DELETE</tt> are idempotent while methods <tt>POST</tt> and <tt>PATCH</tt> are not.</t>
      <t>Let's say a client of an HTTP API wants to create (or update) a resource using a <tt>POST</tt> method. Repeating the request multiple times can result in duplication or incorrect updates. Consider a scenario where the client sent a <tt>POST</tt> request to the server, but the request timed out. The client is left uncertain about the status of the resource. It doesn't know if the resource was created or updated, or if the server even completed processing the request. Furthermore, the client does not know if it can safely retry the request.</t>
      <section anchor="notational-conventions">
        <name>Notational Conventions</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>The term "resource" is to be interpreted as defined in Section 3.1 of <xref target="RFC9110"/>, that is, identified by a URI.</t>
      </section>
    </section>
    <section anchor="the-idempotency-key-http-request-header-field">
      <name>The Idempotency-Key HTTP Request Header Field</name>
      <t>An idempotency key is a unique value generated by the client which the resource uses to recognize subsequent retries of the same request. The <tt>Idempotency-Key</tt> HTTP request header field carries this value.</t>
      <section anchor="syntax">
        <name>Syntax</name>
        <t><tt>Idempotency-Key</tt> is an Item Structured Header Field <xref target="RFC9651"/>. Its value <bcp14>MUST</bcp14> be a String (Section 3.3.3 of <xref target="RFC9651"/>).</t>
      </section>
      <section anchor="uniqueness-of-idempotency-key">
        <name>Uniqueness of Idempotency Key</name>
        <t>The idempotency key <bcp14>MUST</bcp14> be unique and <bcp14>MUST NOT</bcp14> be reused with another request with a different request payload.</t>
        <t>An idempotency key is an opaque value. A resource <bcp14>MAY</bcp14> define what makes a key unique, and clients sending requests to that resource need to generate keys accordingly. Unless the resource defines otherwise, two keys are considered the same only if their values match exactly.</t>
        <t>For example, a resource could require keys that combine a tenant identifier with a request number that is unique within that tenant:</t>
        <artwork><![CDATA[
Idempotency-Key: "tenant-4821:1007"
]]></artwork>
        <t>Such keys are predictable; see <xref target="security-considerations"/> for how a resource can prevent keys from being guessed.</t>
        <t>It is <bcp14>RECOMMENDED</bcp14> that a UUID <xref target="RFC9562"/> or a similar random identifier be used as an idempotency key.</t>
        <t>The following example shows an idempotency key whose value is a UUID <xref target="RFC9562"/>:</t>
        <artwork><![CDATA[
Idempotency-Key: "8e03978e-40d5-43e8-bc93-6894a57f9324"
]]></artwork>
      </section>
      <section anchor="idempotency-key-validity-and-expiry">
        <name>Idempotency Key Validity and Expiry</name>
        <t>The resource <bcp14>MAY</bcp14> require time based idempotency keys to be able to purge or delete a key upon its expiry. The resource <bcp14>SHOULD</bcp14> define such expiration policy and publish it in the documentation.</t>
      </section>
      <section anchor="idempotency-fingerprint">
        <name>Idempotency Fingerprint</name>
        <t>A resource <bcp14>MAY</bcp14> compute a fingerprint of the request payload and store it together with the idempotency key, in order to detect a key being reused with a different request. A resource that does so <bcp14>SHOULD</bcp14> document it.</t>
        <t>When a request arrives with an idempotency key that has been seen before, a resource that uses fingerprints handles it as follows:</t>
        <ul spacing="normal">
          <li>
            <t>If the fingerprint matches, the request is a duplicate and is handled as described in <xref target="idempotency-enforcement"/>.</t>
          </li>
          <li>
            <t>If the fingerprint does not match, the resource fails the request as described in <xref target="error-handling"/> and does not return the result of the original request.</t>
          </li>
        </ul>
        <t>A resource that does not use fingerprints cannot detect a key reused with a different payload, and handles such a request as a duplicate.</t>
        <t>Requests that carry different idempotency keys are distinct requests and are each processed, even if their fingerprints match.</t>
        <t>How the fingerprint is computed is up to the resource; for example:</t>
        <ul spacing="normal">
          <li>
            <t>Checksum of the entire request payload.</t>
          </li>
          <li>
            <t>Checksum of selected element(s) in the request payload.</t>
          </li>
          <li>
            <t>Field value match for each field in the request payload.</t>
          </li>
          <li>
            <t>Field value match for selected element(s) in the request payload.</t>
          </li>
          <li>
            <t>Request digest/signature.</t>
          </li>
        </ul>
        <t>If the fingerprint covers only part of the payload, requests that differ only outside that part are treated as the same request.</t>
      </section>
      <section anchor="responsibilities">
        <name>Responsibilities</name>
        <section anchor="client">
          <name>Client</name>
          <t>Clients of HTTP API requiring idempotency <bcp14>SHOULD</bcp14> understand the idempotency related requirements as published by the server and use an appropriate algorithm to generate idempotency keys.</t>
          <t>Clients <bcp14>MAY</bcp14> choose to send an Idempotency-Key field with any valid value to indicate the user's intent is to only perform this action once. Without a priori knowledge, a general client cannot assume the server will respect this request.</t>
          <t>For each request, a client <bcp14>SHOULD</bcp14>:</t>
          <ul spacing="normal">
            <li>
              <t>Send a unique idempotency key in the HTTP <tt>Idempotency-Key</tt> request header field.</t>
            </li>
          </ul>
        </section>
        <section anchor="resource">
          <name>Resource</name>
          <t>Resources <bcp14>SHOULD</bcp14> document their idempotency-related behavior, including any expiration policy. A resource is responsible for managing the lifecycle of the idempotency key.</t>
          <t>For each request, a server <bcp14>SHOULD</bcp14>:</t>
          <ul spacing="normal">
            <li>
              <t>Identify idempotency key from the HTTP <tt>Idempotency-Key</tt> request header field.</t>
            </li>
            <li>
              <t>Generate idempotency fingerprint if required.</t>
            </li>
            <li>
              <t>Enforce idempotency (see below)</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="idempotency-enforcement">
        <name>Idempotency Enforcement</name>
        <ul spacing="normal">
          <li>
            <t>First time request (idempotency key and fingerprint has not been seen)  </t>
            <t>
The resource <bcp14>SHOULD</bcp14> process the request normally and respond with an appropriate response and status code.</t>
          </li>
          <li>
            <t>Duplicate request (idempotency key and fingerprint has been seen)  </t>
            <t>
Retry  </t>
            <t>
The request was retried after the original request completed. The resource <bcp14>SHOULD</bcp14> respond with a response consistent with the request being completed according to the user's intent.  </t>
            <t>
Concurrent Request  </t>
            <t>
The request was retried before the original request completed. The resource <bcp14>SHOULD</bcp14> respond with a resource conflict error. See Error Scenarios for details.</t>
          </li>
        </ul>
      </section>
      <section anchor="error-handling">
        <name>Error Handling</name>
        <t>If the <tt>Idempotency-Key</tt> request header is missing for a documented idempotent operation requiring this header, the resource <bcp14>SHOULD</bcp14> reply with an HTTP <tt>400</tt> status code with body containing a link pointing to relevant documentation. The following example shows an error response describing the problem using <xref target="RFC9457"/>.</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 400 Bad Request
    Content-Type: application/problem+json
    Content-Language: en
    {
      "type": "https://developer.example.com/idempotency",
      "title": "Idempotency-Key is missing",
      "detail": "This operation is idempotent and it requires correct
       usage of Idempotency Key."
    }
]]></sourcecode>
        <t>Alternately, using the HTTP header <tt>Link</tt>, the client can be informed about the error as shown below.</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 400 Bad Request
    Link: <https://developer.example.com/idempotency>;
      rel="describedby"; type="text/html"
]]></sourcecode>
        <t>If there is an attempt to reuse an idempotency key with a different request payload, the resource <bcp14>SHOULD</bcp14> reply with an HTTP <tt>422</tt> status code with body containing a link pointing to relevant documentation. The status code <tt>422</tt> is defined in Section 15.5.21 of <xref target="RFC9110"/>.</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 422 Unprocessable Content
    Content-Type: application/problem+json
    Content-Language: en
    {
      "type": "https://developer.example.com/idempotency",
      "title": "Idempotency-Key is already used",
      "detail": "This operation is idempotent and it requires
      correct usage of Idempotency Key. Idempotency Key must not be
      reused across different payloads of this operation."
    }
]]></sourcecode>
        <t>The server can also inform the client by using the HTTP header <tt>Link</tt> as shown below.</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 422 Unprocessable Content
    Link: <https://developer.example.com/idempotency>;
    rel="describedby"; type="text/html"
]]></sourcecode>
        <t>If the request is retried, while the original request is still being processed, the resource <bcp14>SHOULD</bcp14> reply with an HTTP <tt>409</tt> status code with body containing problem description.</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 409 Conflict
    Content-Type: application/problem+json
    Content-Language: en
    {
      "type": "https://developer.example.com/idempotency",
      "title": "A request is outstanding for this Idempotency-Key",
      "detail": "A request with the same Idempotency-Key for the
      same operation is being processed or is outstanding."
    }
]]></sourcecode>
        <t>Or, alternately using the HTTP header <tt>Link</tt> pointing to the relevant documentation</t>
        <sourcecode type="http-message"><![CDATA[
    HTTP/1.1 409 Conflict
    Link: <https://developer.example.com/idempotency>;
    rel="describedby"; type="text/html"
]]></sourcecode>
        <t>Error scenarios above describe the status of failed idempotent requests after the resource processes them. Clients <bcp14>MUST</bcp14> correct the requests (with the exception of 409 where no correction is required) before performing a retry operation, or the resource <bcp14>MUST</bcp14> fail the request and return one of the above errors.</t>
        <t>For other 4xx/5xx errors, such as 401, 403, 500, 502, 503, 504, 429, or any other HTTP error code that is not listed here, the client <bcp14>SHOULD</bcp14> act appropriately by following the resource's documentation.</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="the-idempotency-key-http-request-header-field-1">
        <name>The Idempotency-Key HTTP Request Header Field</name>
        <t>The Idempotency-Key field name should be added to the "Hypertext Transfer Protocol (HTTP) Field Name Registry".</t>
        <dl>
          <dt>Field Name:</dt>
          <dd>
            <t>Idempotency-Key</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>permanent</t>
          </dd>
          <dt>Specification document:</dt>
          <dd>
            <t>This specification, Section 2</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>Note to RFC Editor: Please remove this section before publication.</t>
      <t>This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in <xref target="RFC7942"/>.  The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs.  Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors.  This is not intended as, and must not be construed to be, a catalog of available implementations or their features.  Readers are advised to note that
other implementations may exist.</t>
      <t>According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".</t>
      <t>Organization: Stripe</t>
      <ul spacing="normal">
        <li>
          <t>Description: Stripe uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference:  https://stripe.com/docs/idempotency</t>
        </li>
      </ul>
      <t>Organization: Adyen</t>
      <ul spacing="normal">
        <li>
          <t>Description: Adyen uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://docs.adyen.com/development-resources/api-idempotency/</t>
        </li>
      </ul>
      <t>Organization: Dwolla</t>
      <ul spacing="normal">
        <li>
          <t>Description: Dwolla uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://docs.dwolla.com/</t>
        </li>
      </ul>
      <t>Organization: Interledger</t>
      <ul spacing="normal">
        <li>
          <t>Description: Interledger uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://github.com/interledger/</t>
        </li>
      </ul>
      <t>Organization: WorldPay</t>
      <ul spacing="normal">
        <li>
          <t>Description: WorldPay uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://developer.worldpay.com/docs/wpg/idempotency</t>
        </li>
      </ul>
      <t>Organization: Yandex</t>
      <ul spacing="normal">
        <li>
          <t>Description: Yandex uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://cloud.yandex.com/docs/api-design-guide/concepts/idempotency</t>
        </li>
      </ul>
      <t>Organization: http4s.org</t>
      <ul spacing="normal">
        <li>
          <t>Description: Http4s is a minimal, idiomatic Scala interface for HTTP services.</t>
        </li>
        <li>
          <t>Reference: https://github.com/http4s/http4s</t>
        </li>
      </ul>
      <t>Organization: Finastra</t>
      <ul spacing="normal">
        <li>
          <t>Description: Finastra uses custom HTTP header named <tt>Idempotency-Key</tt></t>
        </li>
        <li>
          <t>Reference: https://developer.fusionfabric.cloud/</t>
        </li>
      </ul>
      <t>Organization: Datatrans</t>
      <ul spacing="normal">
        <li>
          <t>Description: Datatrans focuses on the technical processing of payments, including hosting smart payment forms and correctly routing payment information.</t>
        </li>
        <li>
          <t>Reference: https://docs.datatrans.ch/docs/api-endpoints</t>
        </li>
      </ul>
      <section anchor="implementing-the-concept">
        <name>Implementing the Concept</name>
        <t>This is a list of implementations that implement the general concept, but do so using different mechanisms:</t>
        <t>Organization: Django</t>
        <ul spacing="normal">
          <li>
            <t>Description: Django uses custom HTTP header named <tt>HTTP_IDEMPOTENCY_KEY</tt></t>
          </li>
          <li>
            <t>Reference:  https://pypi.org/project/django-idempotency-key</t>
          </li>
        </ul>
        <t>Organization: Chargebee</t>
        <ul spacing="normal">
          <li>
            <t>Description: Chargebee uses custom HTTP header named <tt>chargebee-idempotency-key</tt></t>
          </li>
          <li>
            <t>Reference: https://apidocs.chargebee.com/docs/api/idempotency</t>
          </li>
        </ul>
        <t>Organization: Twilio</t>
        <ul spacing="normal">
          <li>
            <t>Description: Twilio uses custom HTTP header named <tt>I-Twilio-Idempotency-Token</tt> in webhooks</t>
          </li>
          <li>
            <t>Reference: https://www.twilio.com/docs/usage/webhooks/webhooks-connection-overrides</t>
          </li>
        </ul>
        <t>Organization: PayPal</t>
        <ul spacing="normal">
          <li>
            <t>Description: PayPal uses custom HTTP header named <tt>PayPal-Request-Id</tt></t>
          </li>
          <li>
            <t>Reference:  https://developer.paypal.com/docs/business/develop/idempotency</t>
          </li>
        </ul>
        <t>Organization: RazorPay</t>
        <ul spacing="normal">
          <li>
            <t>Description: RazorPay uses custom HTTP header named <tt>X-Payout-Idempotency</tt></t>
          </li>
          <li>
            <t>Reference: https://razorpay.com/docs/razorpayx/api/idempotency/</t>
          </li>
        </ul>
        <t>Organization: OpenBanking</t>
        <ul spacing="normal">
          <li>
            <t>Description: OpenBanking uses custom HTTP header called <tt>x-idempotency-key</tt></t>
          </li>
          <li>
            <t>Reference: https://openbankinguk.github.io/read-write-api-site3/v3.1.6/profiles/read-write-data-api-profile.html#request-headers</t>
          </li>
        </ul>
        <t>Organization: Square</t>
        <ul spacing="normal">
          <li>
            <t>Description: To make an idempotent API call, Square recommends adding a property named <tt>idempotency_key</tt> with a unique value in the request body.</t>
          </li>
          <li>
            <t>Reference: https://developer.squareup.com/docs/build-basics/using-rest-api</t>
          </li>
        </ul>
        <t>Organization: Google Standard Payments</t>
        <ul spacing="normal">
          <li>
            <t>Description: Google Standard Payments API uses a property named <tt>requestId</tt> in request body in order to provide idempotency in various use cases.</t>
          </li>
          <li>
            <t>Reference: https://developers.google.com/standard-payments/payment-processor-service-api/rest/v1/TopLevel/capture</t>
          </li>
        </ul>
        <t>Organization: BBVA</t>
        <ul spacing="normal">
          <li>
            <t>Description: BBVA Open Platform uses custom HTTP header called <tt>X-Unique-Transaction-ID</tt></t>
          </li>
          <li>
            <t>Reference: https://bbvaopenplatform.com/apiReference/APIbasics/content/x-unique-transaction-id</t>
          </li>
        </ul>
        <t>Organization: WebEngage</t>
        <ul spacing="normal">
          <li>
            <t>Description: WebEngage uses custom HTTP header called <tt>x-request-id</tt> to identify webhook POST requests uniquely to achieve events idempotency.</t>
          </li>
          <li>
            <t>Reference: https://docs.webengage.com/docs/webhooks</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This section is meant to inform developers, information providers,
and users of known security concerns specific to the idempotency keys.</t>
      <t>Resources that do not implement strong idempotency keys, such as UUIDs, or have appropriate controls to validate the idempotency keys, could be victim to various forms of security attacks from malicious clients:</t>
      <ul spacing="normal">
        <li>
          <t>Injection attacks - When the resource does not validate the idempotency key in the client request and performs an idempotent cache lookup, there can be security attacks (primarily in the form of injection), compromising the server.</t>
        </li>
        <li>
          <t>Data leaks - When an idempotency implementation allows low entropy keys, attackers <bcp14>MAY</bcp14> determine other keys and use them to fetch existing idempotent cache entries, belonging to other clients.</t>
        </li>
      </ul>
      <t>To prevent such situations, the specification recommends the following best practices for idempotency key implementation in the resource.</t>
      <ul spacing="normal">
        <li>
          <t>Establish a fixed format for the idempotency key and publish the key’s specification.</t>
        </li>
        <li>
          <t>Always validate the key as per its published specification before processing any request.</t>
        </li>
        <li>
          <t>On the resource, implement a unique composite key as the idempotent cache lookup key. For example, a composite key <bcp14>MAY</bcp14> be implemented by combining the idempotency key sent by the client with other client specific attributes known only to the resource.</t>
        </li>
      </ul>
    </section>
    <section anchor="examples">
      <name>Examples</name>
      <t>The first example shows an idempotency-key header field with key value using UUID version 4 scheme:</t>
      <artwork><![CDATA[
Idempotency-Key: "8e03978e-40d5-43e8-bc93-6894a57f9324"
]]></artwork>
      <t>The second example shows an idempotency-key header field with key value using a random string generator:</t>
      <artwork><![CDATA[
Idempotency-Key: "clkyoesmbgybucifusbbtdsbohtyuuwz"
]]></artwork>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC9110">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC9651">
          <front>
            <title>Structured Field Values for HTTP</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="P-H. Kamp" surname="P-H. Kamp"/>
            <date month="September" year="2024"/>
            <abstract>
              <t>This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields.</t>
              <t>This document obsoletes RFC 8941.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9651"/>
          <seriesInfo name="DOI" value="10.17487/RFC9651"/>
        </reference>
        <reference anchor="RFC9562">
          <front>
            <title>Universally Unique IDentifiers (UUIDs)</title>
            <author fullname="K. Davis" initials="K." surname="Davis"/>
            <author fullname="B. Peabody" initials="B." surname="Peabody"/>
            <author fullname="P. Leach" initials="P." surname="Leach"/>
            <date month="May" year="2024"/>
            <abstract>
              <t>This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing System (NCS), later
in the Open Software Foundation's (OSF's) Distributed Computing
Environment (DCE), and then in Microsoft Windows platforms.</t>
              <t>This specification is derived from the OSF DCE specification with the
kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have
been incorporated into this document. This document obsoletes RFC
4122.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9562"/>
          <seriesInfo name="DOI" value="10.17487/RFC9562"/>
        </reference>
        <reference anchor="RFC9457">
          <front>
            <title>Problem Details for HTTP APIs</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <author fullname="S. Dalal" initials="S." surname="Dalal"/>
            <date month="July" year="2023"/>
            <abstract>
              <t>This document defines a "problem detail" to carry machine-readable details of errors in HTTP response content to avoid the need to define new error response formats for HTTP APIs.</t>
              <t>This document obsoletes RFC 7807.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9457"/>
          <seriesInfo name="DOI" value="10.17487/RFC9457"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
      </references>
    </references>
    <?line 404?>

<section anchor="changes">
      <name>Changes from Draft-08</name>
      <t>This revision has made the following changes:</t>
      <ul spacing="normal">
        <li>
          <t>Clarified how resources define idempotency key uniqueness</t>
        </li>
        <li>
          <t>Relaxed the requirement to document idempotency behavior from <bcp14>MUST</bcp14> to <bcp14>SHOULD</bcp14></t>
        </li>
        <li>
          <t>Clarified optional request fingerprints and duplicate-request handling</t>
        </li>
      </ul>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors would like to thank Mark Nottingham for his support for this Internet Draft. We would like to acknowledge that this draft is inspired by Idempotency related patterns described in API documentation of <eref target="https://github.com/paypal/api-standards/blob/master/patterns.md#idempotency">PayPal</eref> and <eref target="https://stripe.com/docs/idempotency">Stripe</eref> as well as Internet Draft on <eref target="https://tools.ietf.org/html/draft-nottingham-http-poe-00">POST Once Exactly</eref> authored by Mark Nottingham.</t>
      <t>The authors take all responsibility for errors and omissions.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9U82XLbxpbv+Ioe+iF2hgAlWY4tZblRJDlWrheNJN/cVCoV
NYEm2RaIxkUDohiXU/Mb8zbfMp8yXzJn6cZKSfGNp2qmUqFJoJfTZ99aYRgG
sUl0Nt8XVTkLnwVBqctU7YuLhRIniVrmplRZvA7/qtbixcXFqXihZKIK8Vyr
NAkSE2dyCcOTQs7KUCtYY1GWucx1qFuzr9Q6XNDEcGsviGWp5qZY7wtbJoHO
i31RFpUtd7a29rZ2AlvKLPlVpiaDhdfKBrneFz+XJh4L+NBZorJyLKwpykLN
LHxbL92XstAxvIrNMpfuyxIGwyudpTpTvwTBtcoqtR8IMS9Mle/TmQ5OT+BB
uc5hvx9NcQXoEN/ja3i6MHg8PJPdn0zogKu5P2M01+WimkbaTGDoUuqUh8Kr
b3FoZIo5vChUbpo13ByArb/cpIWyIJBVuTAFghrC/wKOYPfFD5H4QWWSHjDm
f5BrwOtUNs8VA/LOvXj37Rwf4IZBd7HzSBzJVKat1c5lBvNaj91ilp5HCT7/
NpZpNFXFlUrVOlJJRQOrQm88o01kafMq2+ltfhSJC20XgOzW9kdLDTTUnTcO
gqX6Nlnqrcd8jiAzxVKW+hpoGehs1voVhGEo5BSYAXggCJCRiXH73Fyof1TK
loL5UsyQoUUsMzFVorIqAWYDkl4pkZmsYeaSF1sqIE5iha3ihZBWXJ6+Ob+4
FKaAbwcXhy8uxUxWaRmWJlWFzMqIwVrqJElVEDwQJ1lZmKSKS22yIDjJYKty
ofAQsRXA/8TEVQmA2VgDzGoMT0ULDJPDwjhbaCtAVES5kKWHX+Z5quEIS4BB
5ym81EtlxQrIYioYtZDZHLkctgQ8WBgFs9YGtsUnOtOllimvEtMmkTgpRWJg
jcyUCCtCpmc0vAMJ8EYKG5ssXcNHrBAlAC+AOHNAmGtVADpa5MB5Gn4UIPgl
7C6mlU5RKfWQyKgHabWROMj4l6ciE4QgMJkFPBUAxWWDr0sPrc7gZwIv1Wym
YsBjRo+tKgAuhLLGmUZFA+dP/SaMQEZ0sx/NBu5FNsDvbl1gSSGFhVPAUsQm
bpVInMJG79//y9nzw73t7a0PH8Y0z7PU5ZvTi5M3r88vx+LyxfHBEf77/fEF
/nP6FngMmePy6Pjl8cUx/ChUmylWC522VmKmpAmOK3E8UBDw/1KVnwH/grBL
EQOzIEvNkMc8ksUKUG5RCuJCgcYWD+FEVQ7irB7BHGAbUxUxygpSSvrdePNI
nKkcZjVM5sjUZUhkV8d/QPakqvkN2UZnsSkKxCXvClQ/dLRFzMag7wpt4MxA
a9rEHcPiRw2P3xnO0dB5DCxWdgBDeIBtKyDPRbMUkDdVMwAAOBm4E2CUU+Nm
gpkqK+ZrliJCRy0o2WeluMrMyvNdja8V8AljNBE1RpMxnXjW5kUFtorUQKpw
bF6YWFnbw2gknlcF/C6WplDjNhpqafVQaFYPVs5UiuqvLNadlUB1PnggxGtT
EgmA7wHd1ygDgHVWpGDHxcoUwFujV2/PL0Zj/le8fkPfz47/7e3J2fERfj9/
cfDyZf0lcCPOX7x5+/Ko+dbMPHzz6tXx6yOeDE9F51EwenXw02hMvDxiATl4
OUKmKRdAJPBDqiWRHVnBoApEOS/yglAnbZAoGxd6Cj9gzneHp//1n9u7Tgh3
trf3PnxwP55tP92FH8BUGe9Gmox/ArLWAShFJZE5BWg6QGiuS5mChwFUtQuz
ygSyI+Dy858RM7/si6+mcb69+417gAfuPPQ46zwknA2fDCYzEjc82rBNjc3O
8x6mu/Ae/NT57fHeevjVX9CvEuH2s798EzCPANqXYuTZfUQqcgNFRKJmMJXo
ca7IDorH0TbKU183ShTEsdPHM7RrU9Rab89OIjSlt7qqZ062Oy5rcNAyo2B7
kKUBRAkyrmG4uJYpfM5VhkaNt2oJFSjYeNGVZ/AV6ISgqcw807+htp9a3BrG
o5RpVWsJshO15CLglz3IL7tmreecFLQYsTzBGZHInq+zUt4EwXAtPFgGGkkt
xTm42HFZoVls48Mj+4sn2x8+oPJyKwtiVnQlcCYqnYcNleC/Fp1o6iOnPt4S
FjNQVDiibeQBIGaQPvb9To4AKHReUvBxocgbI9MrQZ+BfNXo4Yci0WBzC8Y3
v8jlOjUyiW4lN1iYXNb0Bn+iISiwvWNOIDeaenACkUFwKsPImoFZwqK9IWel
9hLI1MiyWTFT7E56rsKlYMUY7BvOTNcR4C1FnHU4i4EAROKZV9qifl8ZNxkU
XcvTqZmL1BXbEV3w4Sz6a8C16gYcYtgrCJ6DrYFfaFnGbVMemwo4As+hCwck
e5VmOUV0SHTlyEfzolh4EnjEZ9USQgMvtJ6mOIh0NTzlJfYDcu57HLsvRvw6
3H22s72/vbX1dBQE5+g91acGDZJAmCenqfoScK+ADa2KIfwo16HHCBkwC3oc
vTDQyp1DAu1hDTRsvOisMEtgNCThHM4AzIbuKYHf0owMPGidtydHnvOffLED
ezhHb6lTsAvgpyawXAtBPpyQtuPBMy9GLBIzk6ZmhRA4spAt2TQBWNJYr6VI
bw0AuhW1z9TW472nz1S4u5U8CXcfq2fhNN57HH7xbG9XPnk623u8szsiKe7J
rfibTHUCCCa+P77JdeFkuSM0nnHQlxJTiYfuQe9NARIPv+ZVMacQIVHo5Hgh
yzGWAEFStBMrynonZ+CchJJnTePYb8wNuJAMZ15NU4gj0e/R7OR7N4FDmsFJ
nwMB0EKBoQK90T2bC8cAwlkzqnH+OlqHdrelQd8cHc+5IqXlgoeBAsTsBOAA
VTKgJAE8xKXDBHNlRwMOlV1HeRGXkutnTY0q7x1pdPJ+BF+mJbBoU65dbLiJ
32jBBTDvVME8ix9TNSNnU/a2JUvYQo+FeRnEuxbRACswl1vgz8/FCWOujUzS
UsqOOyglFveBARsH7dd1bkTLsXv/vp11UpgXiBUeHWzb5k3bMW28GHcV8Ezq
1HbAGW6oisIUIQEEy4I6QBDrVcH+V0XWjrMdy5hCQwTexJZRh+MaKuIigNcu
WkGF4fMOq9zGJI4n2WR5enDaon2qFpIBlLPalHFSoYBQoVlyINSolhNtIdqL
y8YM4ob4RknYzEUvGOhQXFObqM7BiAiw/wtQ2X1KUWhPQkgsUOU+pPNY+5K0
vVOgxGSHCxVf2WrpkY46uRiIa9QbaUEXxbgL/Iu889A+8gpkw0z2olgfs50l
KPDM7LV97NSP2977uImewz8Tq+eZRC8PTdiQ22NMvlh2EnJZ1NxYM0nRITyT
3CVzqhJNK7+guRRruUBWtvIg3XjyTNkcrfJUp7oE7xUfPhCH5DsFwaHzoQCO
Ou/AZgQVX5vRnC6rMtCTlCEeqNJCpQSLM0OU+UXAnB1ofHkXX+MaKFqg9CCo
KwygiFRMOgfhLBfLjsfW5/mogZ3Mw8KgWYYZ6A2S092LSJgZnJZdI9W1pz3M
0uBCkoJD+ACo4jPLmarSxU9MMlVgppMDAMneOCbZIvGjy+xJEDQN4FPQDxpy
TmqaT5H6IMapD2mB4VUbIyudokKyOaoV2qSh5XPP1e7RuMkbMWlI4s7p9N7t
GzjezMZE6WGwsinmiZhdzpyIo2bib3Zg3FidtPW/Z4ipWshrwAoa2jityFlH
Ggzcho4lpdM73k0VieZSZrLOm6Z6puJ1DK+cEA1du004c6hu4eyEfcX1AF3k
mH40wj4X329i2o4qnXkhofHHbCc7wx+iZz1VYK8fBQNH6bgxrOL9g9tMbkAq
rnDJtRrah/1johy2oUNnA/mzdjgeoUO7yQd0RqWjG6kwkKa8LBOwFruOnDvi
KuetUTIvNgnlbsRR7XF8FNhdkM8wxdbA7kJWaV1WAARlVlKsNHQHmrzfZu+3
e7DmLBQAWc4Fe3fTL8nOZJNQrONPb0g7eidCwA9Bu1QFGX1naO46DvuFn+g8
PiLNZkCIUpCbFYF+UeIYv4pzl/+1JJngCqGv5mwOj3jhfDJg0Z6TVtvGe2UK
lMBSc9KVE/pe3bRjm3YxpjFepD95mZ5bWZ85x9SiY02W8d2trcs2M/LrqUnW
iArMQHOyHY5xBUoLSOXoB7pOXUtyaNsxjrgnuiTENOzjfFuv4kBYQPUtXYrf
xZi7T56iNx38/vvvVO8LlyCCcq4o6MRTTLajbQEHEd9BKOTZBl8CNyG2wguq
tLaqSxO30b++sybrDH0ps3kFi++D70Yv3tOnECMs144gqPUlxwTcyhTpELlD
coW1oe9oXE/FEjfO7dvohtrNYOYsHH2BBO0Uu1ocQIFJ6dUqEo9KF24VwKCc
qw0ZsWhEIz4gNiECSEEfgP+mUggKqzrVT6zhGPLyJVD+spPodzU/roKiXNcl
CqZunZkmdf5PUQ433Rdf/WFcf/OlOziw5dejOmKarkdfUp3961GpbsrJolym
Iz46C2ShXHIOC4zLvGTOdk7aIBNyT/LvI6RuZ+fTS117Pd5Bb0x6bz+JnkQ7
g8T3/XTa2RFvM2cCKaHihOb/jazJFKIHwDEGrn9W4NzsumJ4m7wNUlvLipwG
NI81z3K+Li4M+BaDSNol89ugdaX4onGoUTRlao0TzrbUTtd3SvhHS+2d3PBP
yu9HSm87aeN8grErSW/0CWCYLTHkYM+klSL44+Zy7w8IrjdjfJLcJf/u04J7
iEFyPv5vCtRBG48YnWNQ7B0V4s+eyG0SsWaR2l2kGH4QvdKaXkK40tAWzB4F
qZjdgaorIm/AJZKNsbtbEtoKlxljk9L9aIL+b8sEO6G2dlPBLF/XHpbqtRBg
prHrUjZptDpIqCXC45kin2Uk6kwEls28CmwJpBUPa/Kqm1jlnDmYEVK4fyIz
fqKjqA8QH3m33iUf2BJy90DNAtS90AGRQMFTddOnFJNRShRbllzgzJghZ8W6
qJnLfLs3N5MnNzfu1bjuttrd2h7Dx+OxeLK1hR87+EE/d+HFzh7BgyE+r0NM
xc4QaQlfnUK1n2K4lFDVvuNVOa0jMcHaRI3Aq9N1y6Fun/kzOygwYKPXweuD
um9Ful6KBx9dtd40nFNK2DmHpgJLd1haSRIuNiJooxfAmgVyprgoZGYxm3da
mNLEJhUPcbtHLgv5Glc5U3PARrEeIRXqx/vBfn/rIDgn1sVXsMFSZpTNO89V
rGe+hccjAweRKbft1+PaAdphPKHM1bgTvH4QvDYlJcjALxLHiS5NsS9OUyUt
4n2JfEOqzrq1PK9iyi/2VLhoj8AyPTawdOUP02UZNqG1YKir9rnHmPfeKI/Y
P5CQLHOU7ICZubGktby3cILtD5kqwyPslR37UgbXyXA67gOTZNovMfwFDv90
b3cHC/TENy1Dhsv3wfZdMbaR5rrrDVApLaYICNaT44vnOByLbQmcxVIurNYu
mn7MC9d2RE2+1lHDAiyOEBnRaOHOn+r63CiBmNm81kkFx+rCSSLXFDnw5RoM
ZQKSzpkll61FGHtdTqCs1AwI3U665JQDNALcLsylcauf6wulQynLYbtrF5Oc
u7CVa5WE3Qgb6DcA7qsSlZFgxnWqokaitEy+lu9ImZeyqBjFU0q7Al/I1DAm
rkEVkls24LHCF0IUJe5x0zMSfa6ryORau27UGs8Bq7X+UkuJOU3NxaR2cgeF
BxloDO4DnofyvBJ1GIjDtVYr2gzTL677mZqjrWeWObbmNe0GjFAsVToBt75I
eM1mbaoyEBQqLhRVlnHWKVFj1z2DYJJ/jKoctk8U9YnOKBtOOFI3oFR0wymU
alNgbWV81dprKRPesEYEt8mRsAI6UBMsuRoiuJ7fFI1abDk8NAachKg2B3GJ
Y00tB3A61JFvirnM9G/0fp/6ZHIVBKE4auTTP+biaAwMY5YdJwfVdzJMRMEq
Z4oCjxj8x7qx2tJi5JoA9m23Y7wLzkGyBrezDw09/XPA1B4TABBJXI/hYQcK
yRB6k2gnvZsAkz6URyuwpXIAJj/+hHAmtCAB2geBFDPVSooBHK13nwaYdvd/
s/YAph9NkSancj0AyL/4RKipnd4VrgsRbsNaq3x+F3v9BEKpbgbw8eNPA12c
miqJ1rRiAxdyFBhA0ErhvAIAJzGWwPLyTmHAJXct3cfoQ/yCXnGjAXi3eilT
7DXUhprxxXksgRGJVjMZcx2IToQqTAOLR/cSmjd3//Qhew4hMd5VGMDlX3xq
Ss8qtPIzOS10HBGKh0IJhqtEf3Eol/4N4CEmwFz/fKniRUbN8q0+ZfSC5Lq+
guNrbwvnGdkllpHdCETs0l99oEAEm5QhgqTA0o1p6eNb0M7C7qGM4kXDNGC7
KZSEU3FFy1sN78gfMiM5h5EYAp2ZTS4WRxD+Ic2ui6y8CreYJwb7cDi8bTJJ
S4U3MLRdYi9MD/XvZDY3Q7zT4/tYAR/9enJ0/Or0zcXx68Offv3r8U+3WZJ8
nWuUB0xfvANsTxLaon9tqw/f4UIWcwUu1wDE+s19UMZ+YH+vW1gXaEdUred1
dMFdUn8Bjo4eIpMf3ytXIY8L2wJ2Ya5UdomO8UpNF8Zc2c0wr1arqKTpDbCU
k5z4efUXbFrM2FMPsT2jgAMNtARo/FOZDk7Cj+87CY8KXWAJ57mNJxolAQKX
y7SBfYosDFLth9yF9TP5myk22S7/4j54/x7CIJD8NuZv4Y0Cl+yYLf/kps8c
Ay33BkKG72SGvt8A1Na7W6F1V50ub/4gHwNisymvWV21rg5iEjxcFbpUIaop
C18eT64fR9vRFyicM52CH9UahNqNRrqXESadHrgUi7tmOWCg839UEE0MRcHd
ceveLcMuHDzd2E2joBmvUkLcLBPun6BoVRXl2lOthYRfEQm+PtPpq+81MmGm
9jZFXvOiJRiqvM2NOk1CiJw1iRXAgx5niUjpn/t7Y/AC1jmmIWWRoMSQPRpg
4raBhAxigeGR3TFAoPBg7UN1WjphGkY5nQIWvL/GvGBlKdqIIY6+zZOoMWGj
OQHJ9yodoKG3sBP3JXQG2BShc1EQLxNE0OR6e3Jh8pe44CSWOYZGfYR9993f
DgbIwYckExDyy5JKGfdJxd9DvgoQUuKJm5XCk6NbZGM6vZYoH7lbno4IYNdD
J0AGR/CY0+uTm5BZKyxbO+gkGPjSanqczTEhPHCm/Zs/IONevjQQGxu2fNOO
U+MCb5s1+VaGDDwYDKHjhVaY4LwmfmpxwV0+DKyrCLaWR+5NDubLzl3Pey+3
KN4/uK0bvpcIw2K3kpw0ceWphtPGveQJMTA8DlzTXNHKmvn92PMpsiYvVgfb
w+a5po/L9brWSSD2qMDzNb0OQJzZ5ICx7d1SnpdyAe3OHkrhYAYA00HYZ+cb
64arxT5tCnJS6iXPYLFkf5T6Qd35ZFnK+MpdGIAwQcc00N0D4V6u7J1Drx8c
Cmq47l7s8Emvu6DzutLlo9spdJeKtz21HQOnKZECi1T52JXTXXPA4AwPAVfg
fuu03oc4AF1df4RHfJMeDqvr8gzXNbFpDCMBkSrZHLFXou9l+yjdZAXmnBSS
J/ckYIiQo/jiDd4fw85+znFxf7Hr1MRqB5Jopvg+i8s0DlCAG2jsJMfaqbvp
bNyCjlqYFjb1PRBiKjC8FYsKFwK62d2WCSw7PTVTajnAy+YYDVJ8OKBkFxW6
yw7UcHZs8UYLXlfAGwY3oHNY/HzlbbBm+4ZDyVcz//vf/6OXk0ZCHaQrubZd
VqMFLPIRpX6bDtnumX02vYnoMKNb94R+Lt50TzJuCXBt+JGHDDo1ftfOabpc
S32Tonc9qbsAMsm0m/Kbrt0NJc+lfVzZVjrZX+RD56TNEY3SAoakBDAQkxUc
9d72ms25uHPMULrbsTNqdrzrBg96h907fQQHPmX/iCNFutKDndpIhF1hAUFY
hvlz13q4LSHGLrtPAKL0N50s3w50jdL4BytuATNOr9ag95bT+XpaAaYrO52W
iZ2aRbmuqtVvI/4TCZjjRdQe4t8oUE7ZUskk3HoG1i3m596aYf6a0ISVgDoh
3EinG87XAVJQeHR/dEGZb2+B3FWiPtdU9VVG6rNP5Y27aNdqMG+nwTsL+J5j
hp+qoaW/kNMBxeTusrVX8J0LEXSZxPeihnVzomtkRDwdxL7Vm/3a9/t8BU8l
X49mMrVq9IFpz39PxIoVmbxUXyl3UTG7Eq9kcYUXv1GdLuSSr81pro5gmaVp
KXBFLKZIBB5Ubz1Zg1OXhLDtCUdzHcrmWFWmcsuG3v2c/rJE1rtlgy54p7SK
dupnDmt/ebgh48bhK2V9vJ8MUUNqppOltLDBxO8TLZN2//IjQvjPnLJvVr4j
6/4INdpKYT2ljx1Mjf1MbuEbLHAc8/XLZtXSgI8S+b8TQ60DE/47OllNCfrT
MGFuVLi19ciRkLHXI1nUJXJJQZ3r5q+vX3AfB1fT+XI7tTvC+yj4H7TuGasL
SAAA

-->

</rfc>
