<?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 sortfefs="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-kazuho-quic-delegated-stateless-reset-02" category="std" consensus="true" tocInclude="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>Delegating QUIC Stateless Resets</title>
    <seriesInfo name="Internet-Draft" value="draft-kazuho-quic-delegated-stateless-reset-02"/>
    <author fullname="奥 一穂" asciiFullname="Kazuho Oku">
      <organization>Fastly</organization>
      <address>
        <email>kazuhooku@gmail.com</email>
      </address>
    </author>
    <author fullname="Stefano Duo">
      <organization>Google</organization>
      <address>
        <email>stefanoduo@google.com</email>
      </address>
    </author>
    <author fullname="Joseph Beshay">
      <organization>Meta</organization>
      <address>
        <email>jbeshay@meta.com</email>
      </address>
    </author>
    <author fullname="Matt Joras">
      <organization>Meta</organization>
      <address>
        <email>mjoras@meta.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <workgroup>quic</workgroup>
    <keyword>internet-draft</keyword>
    <abstract>
      <?line 36?>

<t>This document specifies how a QUIC endpoint can delegate sending Stateless
Resets to a component that outlives its connection state. It also defines a
frame for clients using zero-length Connection IDs to advertise a Stateless
Reset Token and a transport parameter for servers to indicate support for
receiving the frame.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    QUIC Working Group mailing list (quic@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/quic/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/kazuho/draft-kazuho-quic-delegated-stateless-reset"/>.</t>
    </note>
  </front>
  <middle>
    <?line 45?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Stateless reset (<xref section="10.3" sectionFormat="of" target="RFC9000"/>) allows an endpoint that has lost
connection state to signal to its peer that a connection can no longer be
continued. Nothing a Stateless Reset carries is protected by the connection's
keys or tied to its packet number spaces: the signal is authenticated solely by
the 128-bit Stateless Reset Token it ends with, which the receiver matches
against the tokens it retains.</t>
      <t>QUIC uses that property to avoid retaining state. An endpoint
associates a Stateless Reset Token with each Connection ID it issues, delivering
the token to the peer either in the stateless_reset_token transport parameter or
in a NEW_CONNECTION_ID frame. When such an endpoint later receives a packet that
it cannot associate with any active connection, it recomputes the token from the
Destination Connection ID carried in that packet -- typically by applying a
static key to the Connection ID (<xref section="10.3.2" sectionFormat="of" target="RFC9000"/>) -- and emits a
Stateless Reset carrying that token. Because the token is derived from the
Connection ID, the resetting endpoint need not retain any per-connection state.</t>
      <t>The same property permits a different arrangement, and it is the subject of
this document: the entity that sends a Stateless Reset need not be the endpoint
that ran the connection.</t>
      <t>The ability to send a Stateless Reset is valuable precisely when connection
state has been lost involuntarily -- for example, when an application exits or
is terminated by the operating system. After the application is gone, the peer
may buffer data that will never be delivered and continue to send packets on
the connection until its idle timeout expires. It can also delay fallback
delivery, such as a push notification or a secondary connection. At scale,
abandoned connections consume memory and connection-table capacity. To cover
these scenarios, an endpoint can delegate the termination of the connection to
a component that outlives its own connection state, and that component can
reset the peer long after the endpoint is gone (<xref target="delegation"/>).</t>
      <t>Delegation is optional. A delegate, such as an operating system, system service,
or application helper, needs to survive the loss of connection state and retain
access to the connection's network path.
A mobile operating system could withdraw an application's network access before
the application can send a CONNECTION_CLOSE frame. Once the connection has been
abandoned, a delegate that retains network access can reset the peer
(<xref target="proactive"/>).
If a reset cannot be delivered, the
peer relies on the usual QUIC termination and timeout mechanisms.</t>
      <t>A CONNECTION_CLOSE packet could be recorded for a delegate to send, but such a
packet is difficult to manage. It is protected under the
connection's packet-protection keys that endpoints periodically rotate, and it
carries a packet number that must fall within a dynamic range the peer will accept;
thus, the recorded packet would need constant refreshing to remain usable.
Moreover, because the packet is encrypted, a delegate that does not trust the
endpoint cannot verify that it only closes the connection.</t>
      <t>In contrast, a Stateless Reset does not depend on packet-protection keys or
packet numbers, and its contents can be generated or verified by the delegate
(<xref target="division-of-labor"/>). The delegate retains the token and the information
needed to match and route packets (<xref target="delegation"/>).</t>
      <t>A delegated Stateless Reset can also be better formed than one sent by an
endpoint that has lost its state: the delegate can remember a Connection ID that
the peer has issued and place it where a 1-RTT packet carries the Destination
Connection ID, so that the Stateless Reset reaches the intended peer in a
load-balanced deployment (<xref target="constructing"/>).</t>
      <t>In <xref target="RFC9000"/>, Stateless Reset Tokens are issued alongside Connection IDs.
An endpoint that uses zero-length Connection IDs cannot issue one in a
NEW_CONNECTION_ID frame (<xref section="5.1.1" sectionFormat="of" target="RFC9000"/>). Only a server can provide a
token for its handshake Connection ID in the stateless_reset_token transport
parameter; clients cannot because client transport parameters are not
confidential.</t>
      <t>Zero-length Connection IDs are common for clients. A client that identifies connections
solely by the 5-tuple has no need to issue Connection IDs and can reduce
per-packet overhead by using zero-length Connection IDs. To allow such clients
to issue Stateless Reset Tokens and delegate them, this document defines a
frame for advertising a token and a transport parameter through which servers
indicate support for receiving that frame (<xref target="advertising"/>).
Servers can advertise a token in the existing stateless_reset_token transport
parameter; the new frame is limited to clients that use zero-length Connection
IDs.</t>
      <t>The mechanisms in this document apply to QUIC versions 1 and 2 (<xref target="RFC9369"/>),
which use the same Stateless Reset format and short-header fields.</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?>

</section>
    <section anchor="delegation">
      <name>Delegating a Stateless Reset</name>
      <t>An endpoint can delegate the sending of a Stateless Reset to a component that
outlives its connection state. The delegate retains a registration containing:</t>
      <ul spacing="normal">
        <li>
          <t>Information the endpoint uses to match incoming datagrams to the connection,
such as endpoint-issued Connection IDs or routing information
(<xref section="5.2" sectionFormat="of" target="RFC9000"/>).</t>
        </li>
        <li>
          <t>A return path and a peer-issued Connection ID that the peer currently accepts
(<xref target="constructing"/>).</t>
        </li>
        <li>
          <t>A Stateless Reset Token that the endpoint has advertised, or will advertise,
to the peer (<xref target="division-of-labor"/>).</t>
        </li>
      </ul>
      <t>The delegate retains the token rather than recomputing it from a Connection ID.
It needs no packet-protection keys or packet numbers.</t>
      <t>Both clients and servers can delegate resets, regardless of the length of their
Connection IDs. Tokens are advertised in the server-only stateless_reset_token
transport parameter or in NEW_CONNECTION_ID frames. A client using zero-length
Connection IDs can advertise a token for the whole connection in RESET_TOKEN
frames (<xref target="advertising"/>).</t>
      <t>Registration can precede token advertisement, but the peer recognizes a reset
only after learning the token and associating it with the reset's source
address (<xref section="10.3.1" sectionFormat="of" target="RFC9000"/>). For tokens associated with Connection
IDs, the peer also needs to have used and not retired the ID. A reset carrying
any other token is indistinguishable from a packet that cannot be decrypted and
is discarded. A delegate <bcp14>MAY</bcp14> track when the peer starts using a Connection ID,
and send a Stateless Reset carrying its token only once that happens.</t>
      <t>The endpoint updates a registration when its matching information, peer-issued
Connection ID, or path changes. A reset sent with stale routing information
might be dropped.</t>
      <t>Tokens associated with endpoint-issued Connection IDs remain bound to those
IDs when the path or peer-issued Connection ID changes. A token advertised
using RESET_TOKEN remains fixed for the connection's lifetime
(<xref target="reset-token-frame"/>).</t>
      <t>A connection can have registrations for multiple paths. Closing a socket or
losing a path does not authorize resetting a connection that remains active
on another path (<xref target="proactive"/>). A delegate <bcp14>MUST NOT</bcp14> use a canceled or expired
registration to send resets.</t>
      <t>Once the endpoint has lost or abandoned connection state,
the delegate can send a Stateless Reset proactively (<xref target="proactive"/>), and
thereafter responds to datagrams matching the registration by sending it again,
but does so only if the Stateless Reset is smaller than the datagram that
triggered it, as required by <xref section="10.3.3" sectionFormat="of" target="RFC9000"/>.</t>
      <t>The delegate limits how long it retains a registration
after the endpoint loses or abandons connection state. A retained
registration applies only to the old connection. It <bcp14>MUST NOT</bcp14> prevent delivery
to a new connection that reuses the same routing information.</t>
      <t>This document does not define an interface between an endpoint and a delegate.</t>
      <t>Except as described in <xref target="constructing"/> and <xref target="proactive"/>, the requirements of
<xref section="10.3" sectionFormat="of" target="RFC9000"/> and <xref section="10.3.3" sectionFormat="of" target="RFC9000"/> governing the
construction and sending of a Stateless Reset apply unchanged.</t>
      <section anchor="division-of-labor">
        <name>Token Generation and Packet Construction</name>
        <t>An endpoint and its delegate can divide the work of generating a Stateless
Reset Token and constructing a Stateless Reset according to their trust
relationship. When the delegate trusts the endpoint, such as when the delegate
is an application helper, the endpoint can generate the token itself and
provide it to the delegate as part of the registration (<xref target="delegation"/>).</t>
        <t>When the endpoint and the delegate cross a privilege boundary, such as when the
delegate is an operating system that can withdraw the endpoint's network
access, the delegate can instead generate the token (<xref target="fig-delegation-flow"/>).
When the endpoint registers a new connection or a new Connection ID it issues,
the delegate forms and retains a Stateless Reset datagram (<xref target="constructing"/>)
and returns the Stateless Reset Token to the endpoint to advertise to its peer.</t>
        <figure anchor="fig-delegation-flow">
          <name>Delegating a Stateless Reset with a Delegate-Generated Token</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="672" width="544" viewBox="0 0 544 672" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,32 L 8,656" fill="none" stroke="black"/>
                <path d="M 32,256 L 32,368" fill="none" stroke="black"/>
                <path d="M 80,80 L 80,248" fill="none" stroke="black"/>
                <path d="M 80,288 L 80,360" fill="none" stroke="black"/>
                <path d="M 200,448 L 200,576" fill="none" stroke="black"/>
                <path d="M 264,80 L 264,192" fill="none" stroke="black"/>
                <path d="M 264,288 L 264,360" fill="none" stroke="black"/>
                <path d="M 264,376 L 264,440" fill="none" stroke="black"/>
                <path d="M 264,480 L 264,568" fill="none" stroke="black"/>
                <path d="M 264,584 L 264,624" fill="none" stroke="black"/>
                <path d="M 448,256 L 448,368" fill="none" stroke="black"/>
                <path d="M 472,80 L 472,440" fill="none" stroke="black"/>
                <path d="M 472,480 L 472,568" fill="none" stroke="black"/>
                <path d="M 472,584 L 472,624" fill="none" stroke="black"/>
                <path d="M 512,448 L 512,576" fill="none" stroke="black"/>
                <path d="M 536,32 L 536,656" fill="none" stroke="black"/>
                <path d="M 8,32 L 536,32" fill="none" stroke="black"/>
                <path d="M 88,96 L 128,96" fill="none" stroke="black"/>
                <path d="M 216,96 L 256,96" fill="none" stroke="black"/>
                <path d="M 88,176 L 112,176" fill="none" stroke="black"/>
                <path d="M 224,176 L 256,176" fill="none" stroke="black"/>
                <path d="M 88,208 L 200,208" fill="none" stroke="black"/>
                <path d="M 344,208 L 464,208" fill="none" stroke="black"/>
                <path d="M 32,256 L 448,256" fill="none" stroke="black"/>
                <path d="M 88,304 L 120,304" fill="none" stroke="black"/>
                <path d="M 192,304 L 256,304" fill="none" stroke="black"/>
                <path d="M 32,368 L 448,368" fill="none" stroke="black"/>
                <path d="M 272,400 L 296,400" fill="none" stroke="black"/>
                <path d="M 440,400 L 464,400" fill="none" stroke="black"/>
                <path d="M 200,448 L 512,448" fill="none" stroke="black"/>
                <path d="M 272,496 L 288,496" fill="none" stroke="black"/>
                <path d="M 448,496 L 464,496" fill="none" stroke="black"/>
                <path d="M 272,528 L 296,528" fill="none" stroke="black"/>
                <path d="M 440,528 L 464,528" fill="none" stroke="black"/>
                <path d="M 200,576 L 512,576" fill="none" stroke="black"/>
                <path d="M 8,656 L 536,656" fill="none" stroke="black"/>
                <polygon class="arrowhead" points="472,528 460,522.4 460,533.6" fill="black" transform="rotate(0,464,528)"/>
                <polygon class="arrowhead" points="472,400 460,394.4 460,405.6" fill="black" transform="rotate(0,464,400)"/>
                <polygon class="arrowhead" points="472,208 460,202.4 460,213.6" fill="black" transform="rotate(0,464,208)"/>
                <polygon class="arrowhead" points="280,496 268,490.4 268,501.6" fill="black" transform="rotate(180,272,496)"/>
                <polygon class="arrowhead" points="264,304 252,298.4 252,309.6" fill="black" transform="rotate(0,256,304)"/>
                <polygon class="arrowhead" points="264,96 252,90.4 252,101.6" fill="black" transform="rotate(0,256,96)"/>
                <polygon class="arrowhead" points="96,176 84,170.4 84,181.6" fill="black" transform="rotate(180,88,176)"/>
                <g class="text">
                  <text x="76" y="68">Endpoint</text>
                  <text x="268" y="68">Delegate</text>
                  <text x="468" y="68">Peer</text>
                  <text x="172" y="100">Register</text>
                  <text x="144" y="116">(Peer</text>
                  <text x="188" y="116">CID,</text>
                  <text x="152" y="132">Path,</text>
                  <text x="200" y="132">etc.)</text>
                  <text x="316" y="148">(Generates</text>
                  <text x="384" y="148">Reset</text>
                  <text x="432" y="148">Token</text>
                  <text x="288" y="164">&amp;</text>
                  <text x="320" y="164">Reset</text>
                  <text x="376" y="164">Packet)</text>
                  <text x="144" y="180">Reset</text>
                  <text x="192" y="180">Token</text>
                  <text x="248" y="212">Advertise</text>
                  <text x="312" y="212">Token</text>
                  <text x="188" y="228">(RESET_TOKEN</text>
                  <text x="252" y="228">or</text>
                  <text x="340" y="228">NEW_CONNECTION_ID)</text>
                  <text x="264" y="244">|</text>
                  <text x="84" y="276">Optional</text>
                  <text x="136" y="276">(if</text>
                  <text x="172" y="276">path</text>
                  <text x="204" y="276">or</text>
                  <text x="236" y="276">Peer</text>
                  <text x="272" y="276">CID</text>
                  <text x="328" y="276">changes):</text>
                  <text x="156" y="308">Update</text>
                  <text x="120" y="324">(Peer</text>
                  <text x="164" y="324">CID,</text>
                  <text x="208" y="324">Path)</text>
                  <text x="300" y="324">(Keeps</text>
                  <text x="352" y="324">Reset</text>
                  <text x="404" y="324">Token;</text>
                  <text x="316" y="340">Rebuilds</text>
                  <text x="376" y="340">Reset</text>
                  <text x="312" y="356">Packet)</text>
                  <text x="80" y="388">|</text>
                  <text x="52" y="404">[State</text>
                  <text x="104" y="404">Lost]</text>
                  <text x="344" y="404">Proactive</text>
                  <text x="408" y="404">Reset</text>
                  <text x="324" y="420">(Usually</text>
                  <text x="408" y="420">sufficient)</text>
                  <text x="252" y="468">Optional</text>
                  <text x="304" y="468">(if</text>
                  <text x="340" y="468">more</text>
                  <text x="392" y="468">packets</text>
                  <text x="460" y="468">arrive):</text>
                  <text x="332" y="500">Incoming</text>
                  <text x="404" y="500">Datagram</text>
                  <text x="344" y="532">Stateless</text>
                  <text x="408" y="532">Reset</text>
                  <text x="304" y="548">(If</text>
                  <text x="352" y="548">smaller</text>
                  <text x="404" y="548">than</text>
                  <text x="440" y="548">Rx)</text>
                  <text x="312" y="612">(Discards</text>
                  <text x="376" y="612">Reset</text>
                  <text x="288" y="628">&amp;</text>
                  <text x="352" y="628">Registration)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
+-----------------------------------------------------------------+
|                                                                 |
|    Endpoint                Delegate                   Peer      |
|        |                      |                         |       |
|        |------ Register ----->|                         |       |
|        |     (Peer CID,       |                         |       |
|        |      Path, etc.)     |                         |       |
|        |                      | (Generates Reset Token  |       |
|        |                      |  & Reset Packet)        |       |
|        |<--- Reset Token -----|                         |       |
|        |                      |                         |       |
|        |--------------- Advertise Token --------------->|       |
|        |       (RESET_TOKEN or NEW_CONNECTION_ID)       |       |
|        |                      |                         |       |
|  +---------------------------------------------------+  |       |
|  |  Optional (if path or Peer CID changes):          |  |       |
|  |     |                      |                      |  |       |
|  |     |----- Update -------->|                      |  |       |
|  |     |  (Peer CID, Path)    | (Keeps Reset Token;  |  |       |
|  |     |                      |  Rebuilds Reset      |  |       |
|  |     |                      |  Packet)             |  |       |
|  +---------------------------------------------------+  |       |
|        |                      |                         |       |
|  [State Lost]                 |---- Proactive Reset --->|       |
|                               |   (Usually sufficient)  |       |
|                               |                         |       |
|                       +--------------------------------------+  |
|                       |  Optional (if more packets arrive):  |  |
|                       |       |                         |    |  |
|                       |       |<-- Incoming Datagram ---|    |  |
|                       |       |                         |    |  |
|                       |       |---- Stateless Reset --->|    |  |
|                       |       |   (If smaller than Rx)  |    |  |
|                       |       |                         |    |  |
|                       +--------------------------------------+  |
|                               |                         |       |
|                               | (Discards Reset         |       |
|                               |  & Registration)        |       |
|                                                                 |
+-----------------------------------------------------------------+
]]></artwork>
          </artset>
        </figure>
        <t>In this division of labor (<xref target="fig-division-of-labor"/>), it is possible to deny
an endpoint the use of the Stateless Reset as a means of conveying
information of its own. The Stateless Reset Token and the other bytes that the
delegate generates (<xref target="constructing"/>) are outside the endpoint's control, and the
peer's Connection ID, which the endpoint supplies, is also the value that
it places in the Destination Connection ID field of the packets it sends. A
delegate can therefore monitor the packets that the endpoint sends
after the registration, and send the Stateless Reset only if those packets
carried that Connection ID. The Stateless Reset then carries no Connection ID
other than the one that the endpoint's own packets were already carrying to
the peer.</t>
        <figure anchor="fig-division-of-labor">
          <name>Division of labor between endpoint and delegate</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="432" width="560" viewBox="0 0 560 432" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,32 L 8,416" fill="none" stroke="black"/>
                <path d="M 40,96 L 40,384" fill="none" stroke="black"/>
                <path d="M 72,96 L 72,128" fill="none" stroke="black"/>
                <path d="M 104,96 L 104,128" fill="none" stroke="black"/>
                <path d="M 296,96 L 296,384" fill="none" stroke="black"/>
                <path d="M 552,32 L 552,416" fill="none" stroke="black"/>
                <path d="M 8,32 L 552,32" fill="none" stroke="black"/>
                <path d="M 40,96 L 296,96" fill="none" stroke="black"/>
                <path d="M 312,112 L 344,112" fill="none" stroke="black"/>
                <path d="M 40,128 L 296,128" fill="none" stroke="black"/>
                <path d="M 312,192 L 344,192" fill="none" stroke="black"/>
                <path d="M 40,224 L 296,224" fill="none" stroke="black"/>
                <path d="M 312,256 L 344,256" fill="none" stroke="black"/>
                <path d="M 40,304 L 296,304" fill="none" stroke="black"/>
                <path d="M 312,336 L 344,336" fill="none" stroke="black"/>
                <path d="M 40,384 L 296,384" fill="none" stroke="black"/>
                <path d="M 8,416 L 552,416" fill="none" stroke="black"/>
                <polygon class="arrowhead" points="320,336 308,330.4 308,341.6" fill="black" transform="rotate(180,312,336)"/>
                <polygon class="arrowhead" points="320,256 308,250.4 308,261.6" fill="black" transform="rotate(180,312,256)"/>
                <polygon class="arrowhead" points="320,192 308,186.4 308,197.6" fill="black" transform="rotate(180,312,192)"/>
                <polygon class="arrowhead" points="320,112 308,106.4 308,117.6" fill="black" transform="rotate(180,312,112)"/>
                <g class="text">
                  <text x="72" y="68">Stateless</text>
                  <text x="136" y="68">Reset</text>
                  <text x="188" y="68">Packet</text>
                  <text x="244" y="68">Layout</text>
                  <text x="380" y="68">Source</text>
                  <text x="416" y="68">/</text>
                  <text x="452" y="68">Origin</text>
                  <text x="56" y="116">0</text>
                  <text x="88" y="116">1</text>
                  <text x="168" y="116">Unpredictable</text>
                  <text x="236" y="116">(6</text>
                  <text x="272" y="116">bits)</text>
                  <text x="388" y="116">Delegate</text>
                  <text x="452" y="116">(First</text>
                  <text x="508" y="116">Byte):</text>
                  <text x="380" y="132">0:</text>
                  <text x="416" y="132">Short</text>
                  <text x="468" y="132">Header</text>
                  <text x="516" y="132">Form</text>
                  <text x="380" y="148">1:</text>
                  <text x="416" y="148">Fixed</text>
                  <text x="456" y="148">Bit</text>
                  <text x="96" y="164">Destination</text>
                  <text x="188" y="164">Connection</text>
                  <text x="244" y="164">ID</text>
                  <text x="376" y="164">6</text>
                  <text x="412" y="164">random</text>
                  <text x="460" y="164">bits</text>
                  <text x="88" y="180">(variable</text>
                  <text x="160" y="180">length)</text>
                  <text x="388" y="196">Endpoint</text>
                  <text x="384" y="212">(Peer's</text>
                  <text x="444" y="212">active</text>
                  <text x="492" y="212">CID)</text>
                  <text x="104" y="260">Unpredictable</text>
                  <text x="192" y="260">Payload</text>
                  <text x="388" y="260">Delegate</text>
                  <text x="456" y="260">(Random</text>
                  <text x="516" y="260">bytes)</text>
                  <text x="60" y="276">(4</text>
                  <text x="100" y="276">bytes)</text>
                  <text x="88" y="340">Stateless</text>
                  <text x="152" y="340">Reset</text>
                  <text x="200" y="340">Token</text>
                  <text x="388" y="340">Delegate</text>
                  <text x="456" y="340">(Random</text>
                  <text x="516" y="340">token)</text>
                  <text x="64" y="356">(16</text>
                  <text x="108" y="356">bytes)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
+-------------------------------------------------------------------+
|                                                                   |
|   Stateless Reset Packet Layout           Source / Origin         |
|                                                                   |
|   +---+---+-----------------------+                               |
|   | 0 | 1 | Unpredictable (6 bits)| <---- Delegate (First Byte):  |
|   +---+---+-----------------------+         0: Short Header Form  |
|   |                               |         1: Fixed Bit          |
|   | Destination Connection ID     |         6 random bits         |
|   | (variable length)             |                               |
|   |                               | <---- Endpoint                |
|   |                               |       (Peer's active CID)     |
|   +-------------------------------+                               |
|   |                               |                               |
|   | Unpredictable Payload         | <---- Delegate (Random bytes) |
|   | (4 bytes)                     |                               |
|   |                               |                               |
|   +-------------------------------+                               |
|   |                               |                               |
|   | Stateless Reset Token         | <---- Delegate (Random token) |
|   | (16 bytes)                    |                               |
|   |                               |                               |
|   +-------------------------------+                               |
|                                                                   |
+-------------------------------------------------------------------+
]]></artwork>
          </artset>
        </figure>
      </section>
    </section>
    <section anchor="constructing">
      <name>Constructing a Routable Stateless Reset</name>
      <t>When constructing a Stateless Reset, the endpoint or its delegate <bcp14>SHOULD</bcp14> place a
Connection ID that the peer currently accepts in the position in which a 1-RTT
packet carries the Destination Connection ID field.</t>
      <t>If the peer uses a zero-length Connection ID, the Destination Connection ID
field is empty.</t>
      <t><xref section="10.3" sectionFormat="of" target="RFC9000"/> calls for unpredictable bits, rather than the
Destination Connection ID, because an endpoint that has lost its state cannot
recover a Connection ID that its peer accepts, observing that the resulting packet
"could be incorrectly routed" where the Connection ID is critical for routing toward
the peer, as in load-balanced deployments. Because a delegate retains state, it can
send a Stateless Reset that reaches the peer and is less distinguishable from a valid
packet.</t>
      <t>To maintain indistinguishability from a valid 1-RTT packet, the endpoint or
delegate <bcp14>MUST</bcp14> include at least 4 unpredictable bytes following the Destination
Connection ID. Doing so satisfies both the 21-byte minimum size requirement of
<xref section="10.3" sectionFormat="of" target="RFC9000"/>, when zero-length Connection IDs are used, and provides
the 4-byte offset required by <xref section="5.4.2" sectionFormat="of" target="RFC9001"/>.</t>
      <figure anchor="fig-reset-format">
        <name>Routable Stateless Reset Format</name>
        <artwork><![CDATA[
Stateless Reset {
  Fixed Bits (2) = 1,
  Unpredictable Bits (6),
  Destination Connection ID (0..160),
  Unpredictable Bits (32..),
  Stateless Reset Token (128),
}
]]></artwork>
      </figure>
    </section>
    <section anchor="proactive">
      <name>Sending a Stateless Reset Proactively</name>
      <t>An endpoint that retains the state necessary to send a CONNECTION_CLOSE frame
<bcp14>MUST</bcp14> use CONNECTION_CLOSE instead of a Stateless Reset, as required by
<xref section="11" sectionFormat="of" target="RFC9000"/>.</t>
      <t>Once the endpoint that delegated the Stateless Reset has lost or abandoned its
connection state, a delegate <bcp14>MAY</bcp14> send a single Stateless Reset proactively,
without waiting to receive a datagram from the peer. <xref section="10.3" sectionFormat="of" target="RFC9000"/>
describes a Stateless Reset only as a response to a received packet because an
endpoint that has lost its state learns of the connection's existence only from
one; an endpoint or delegate that retains the token knows which connections it
may need to reset before any packet arrives.</t>
      <t>A delegate <bcp14>MUST NOT</bcp14> send a Stateless Reset unless the endpoint has lost or
abandoned its connection state. Loss of one path does not by itself imply
abandonment. Once delegated teardown begins, the endpoint <bcp14>MUST NOT</bcp14> resume that
connection.</t>
    </section>
    <section anchor="advertising">
      <name>Advertising a Token with Zero-Length Connection IDs</name>
      <t>The RESET_TOKEN frame lets a client using zero-length Connection IDs advertise
a Stateless Reset Token. Servers indicate support with the reset_token
transport parameter. The token is bound to the connection and can be delegated
as described in <xref target="delegation"/>.</t>
      <section anchor="reset-token-tp">
        <name>The reset_token Transport Parameter</name>
        <t>A server that is willing to accept RESET_TOKEN frames
(<xref target="reset-token-frame"/>) from its client advertises the reset_token transport
parameter (0x-TBD).</t>
        <t>The reset_token transport parameter has a zero-length value; its presence alone
conveys that willingness. A client <bcp14>MUST NOT</bcp14> send this transport parameter.
Receipt of this parameter from a client, or receipt of a non-zero value, <bcp14>MUST</bcp14> be
treated as a connection error of type TRANSPORT_PARAMETER_ERROR.</t>
      </section>
      <section anchor="reset-token-frame">
        <name>The RESET_TOKEN Frame</name>
        <t>The RESET_TOKEN frame (type 0x-TBD) carries a Stateless Reset Token that a
client associates with the connection rather than with any Connection ID.</t>
        <figure anchor="reset-token-format">
          <name>RESET_TOKEN Frame Format</name>
          <artwork><![CDATA[
RESET_TOKEN Frame {
  Type (i) = 0x-TBD,
  Stateless Reset Token (128),
}
]]></artwork>
        </figure>
        <t>The frame contains the following field:</t>
        <dl>
          <dt>Stateless Reset Token:</dt>
          <dd>
            <t>A 128-bit value that the sender will use to construct a Stateless Reset
(<xref section="10.3" sectionFormat="of" target="RFC9000"/>) for this connection. The token <bcp14>MUST</bcp14> be
generated so that it is hard to guess, as required by <xref section="10.3" sectionFormat="of" target="RFC9000"/>.</t>
          </dd>
        </dl>
        <t>RESET_TOKEN frames are ack-eliciting; a sender that detects the loss of a
RESET_TOKEN frame retransmits the token it carried. A RESET_TOKEN frame <bcp14>MUST</bcp14>
only be sent in a 1-RTT packet.</t>
        <t>A client <bcp14>MUST NOT</bcp14> send a RESET_TOKEN frame unless the server advertised the
reset_token transport parameter.</t>
        <t>Only a client that uses a zero-length Connection ID may send a RESET_TOKEN
frame; the mechanism substitutes for the tokens that a Connection ID-issuing
client sends in NEW_CONNECTION_ID frames. A client that uses a non-zero-length
Connection ID <bcp14>MUST NOT</bcp14> send a RESET_TOKEN frame. A server that receives a
RESET_TOKEN frame from such a client <bcp14>MUST</bcp14> treat this as a connection error of
type PROTOCOL_VIOLATION.</t>
        <t>An endpoint that has not advertised the reset_token transport parameter treats a
received RESET_TOKEN frame as a frame of unknown type, which is a connection
error of type FRAME_ENCODING_ERROR (<xref section="12.4" sectionFormat="of" target="RFC9000"/>). A server <bcp14>MUST
NOT</bcp14> send a RESET_TOKEN frame. Because a client cannot advertise the transport
parameter, it treats a RESET_TOKEN frame from a server as a frame of unknown
type.</t>
        <t>A server that receives a RESET_TOKEN frame recognizes the contained value as
a Stateless Reset Token for this connection and thereafter processes it exactly
as a token received in a NEW_CONNECTION_ID frame, following the requirements of
<xref section="10.3" sectionFormat="of" target="RFC9000"/> for retaining the token and for detecting a
Stateless Reset that carries it, except that this token is immediately usable
and is not subject to the rule that excludes tokens for unused Connection IDs.</t>
        <t>A client uses a single Stateless Reset Token for the lifetime of a
connection. It <bcp14>MAY</bcp14> send more than one RESET_TOKEN frame -- for example, to
retransmit a frame that was lost -- but every RESET_TOKEN frame it sends on a
connection <bcp14>MUST</bcp14> carry the same token value. A server that receives a
RESET_TOKEN frame carrying a token value different from one it received earlier
on the same connection <bcp14>MUST</bcp14> treat this as a connection error of type
PROTOCOL_VIOLATION. Receipt of the same value more than once is idempotent. The
token <bcp14>MUST NOT</bcp14> be used for another connection or for a Connection ID.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Knowledge of a Stateless Reset Token allows an entity to terminate the
connection. A token <bcp14>MUST</bcp14> be difficult to guess and <bcp14>MUST NOT</bcp14> be reused. A sender
can generate a token using a cryptographically secure random number generator.</t>
      <t>Giving a delegate access to the token creates another opportunity for
disclosure, even if it can already terminate the connection. The endpoint needs
to consider this exposure when selecting a delegate.</t>
      <t>The token and routing information <bcp14>MUST</bcp14> have confidentiality and integrity in
transit and at rest. The delegate <bcp14>MUST</bcp14> restrict registration creation, update,
cancellation, and access to the endpoint and entities authorized to act for it.</t>
      <t>Removing a registration does not revoke a token retained by the delegate. A
token associated with a Connection ID is invalidated when the peer retires that
ID (<xref section="10.3" sectionFormat="of" target="RFC9000"/>). A token advertised using RESET_TOKEN remains
valid for the connection's lifetime (<xref target="reset-token-frame"/>).</t>
      <t>A delegate can retain multiple registrations for a connection, such as one for
each path. Implementations <bcp14>SHOULD</bcp14> limit the number of registrations to avoid
resource exhaustion.</t>
      <t>A RESET_TOKEN frame is protected by 1-RTT packet protection. A Stateless Reset
reveals its token to an on-path observer. This does not create a new termination
capability because the peer enters the draining state after accepting the
reset. The token cannot be used for another connection.</t>
      <t>A delegate sends using the source and destination addresses of a path on which
the endpoint recently received packets from the peer. This allows the peer to
apply the remote-address check in <xref section="10.3.1" sectionFormat="of" target="RFC9000"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC9000">
        <front>
          <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
          <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
          <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
          <date month="May" year="2021"/>
          <abstract>
            <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9000"/>
        <seriesInfo name="DOI" value="10.17487/RFC9000"/>
      </reference>
      <reference anchor="RFC9369">
        <front>
          <title>QUIC Version 2</title>
          <author fullname="M. Duke" initials="M." surname="Duke"/>
          <date month="May" year="2023"/>
          <abstract>
            <t>This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC.</t>
            <t>Note that "version 2" is an informal name for this proposal that indicates it is the second version of QUIC to be published as a Standards Track document. The protocol specified here uses a version number other than 2 in the wire image, in order to minimize ossification risks.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9369"/>
        <seriesInfo name="DOI" value="10.17487/RFC9369"/>
      </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="RFC9001">
        <front>
          <title>Using TLS to Secure QUIC</title>
          <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
          <author fullname="S. Turner" initials="S." role="editor" surname="Turner"/>
          <date month="May" year="2021"/>
          <abstract>
            <t>This document describes how Transport Layer Security (TLS) is used to secure QUIC.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9001"/>
        <seriesInfo name="DOI" value="10.17487/RFC9001"/>
      </reference>
    </references>
    <?line 486?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9U87XLcRnL/5ykmVFVMxrsbUZYVm7J9pkjKZiyJDEXl6uJy
qbDA7O6YWGAPA5BaS3al8iT5cz/yBvmdZ0kqr5H+mBnMANglZalSCet8IrGL
np7+7p7uGY/HotZ1rg7kzrHK1TypdTGX//Dq9Ei+rJMaHhkjL5RRtdkRKTyY
l9X6QJo6E1mZFskS3syqZFaPr5JfmkU5/nOj03HGoFQ2Ng7IuEIg4/sPxM38
QOK3hF5VB7KuGlM/uH//S/jkSq1vyio7kLqoVVXA1wm0ACBF9jrJywJWWysj
VvpA/liX6Uiasqpnambgt/Wygl9+EklTL8rqQMixkPAza/Kc8KS/pDw4kP/1
l7/I//z3f/7vf/sX+ywxqQaQP9AW5NlVQ8/LCjB9mpg6X9Pfapno/EDyRsur
5ts5Ppik5bK3FhBPzZKilMdN2cL6riznuQphGf5a1pTfzunDYWh/Xxq1Wsgn
yiySdQvvuaqTENrPU/rCt0t4PgzoeVLXAK1KzGYoy5/x8xaIKMpqCXJxDSQU
upgFf00mEyHG47FMpqaukrQW4nKhjQTRaJaqqKVZqVTPtDJyUd7IhAVLFdmq
BBbLNCmkExVp4DHKnhc7wWIn6xJeBERWwH54qV4ktSybOgcUjNTwhbQsCpXW
uiwkidtEntYyyU0JwGe6gG8lYlbB/iXgLtNcAxgjG4Or/aKqcpyrYl4v5FEL
5/SY182uVVVrowCDDl7ysrxShQTBhM9g74VZgSjKVYILgfTSWkZVAIBAadhd
SvtsVvRN+FxUKlX6GvGoF4AdvgoEJYoudZaBrIh78rSoK5AQQkyIVitJoeTu
27cvLdL79yefyXIm/+ri6dGX9+/f//XXPSBDXt4AAYqW6kTARWJkXppadImH
uBo9L5KcsAZCrRTshl5KQlIj80DAQSnn8PlUISQwHo3KJvJFWS9wV0nXiMBb
VYXiAEKyqsoaYKlMTte0/xb4JwZtgQH5lLWGLzhMkvQKYBTNcgpLGvhTmQN6
1WIMUFH7gb9E6wzMQ67yNSwg8Fv7D74YT3XdQ4pZCR8AjYy80fViJG8WOl0Q
bGYSLAhiny7A+iTzRBempg9rfBXFEL5W42PgHwl5Y2CXRDXY5wqkaE0CdV3q
zH4VCWTl9bBlj0iMKVMNj80A+RhTxFCqJO2ILGKhjWkUWENQK8QZ1hAeTUQA
/yCGKoAB/+iC6efWeU1S9dp+f0CsQWrhnUS+OPnj66OzFy9Oji5Pz168htVZ
fOUfgfwg5IBcKHR5gi9bUuLOLC+RQkKTKShKkDC3ed5jUqwlWBV4JRCOEVMb
LUJTE5Hd/mZVucQ/xbEyIIoJ0SUmEctfxvtG5jAaoHD1egVCk5O0yGS1ytck
weh8QJokyKOjXwyxo4CTB6iCgQaidQQjoZYowYkYUog1WwBAh/YxAUOfJiBA
wdbQqAI7rwF1v8sIj5GVVYBJLtxTvlDwDtKWpY5oCvI47llNtN0gCWgnvcjC
/zPeMtOzmarQAAPCCeg82vcRbY3EjsWomf4MMIECIHWBH2AlRbVENcCNGlK1
voB7bKfKvmPVgt6ChTuWwmKdTHWuWcUQ8gBgwOY6yZtkmuP2wCsZNAw3KKwt
NMEmEI3jVMEnaCFBVK7LvCnqpNLwBrATLbt6kyxXuRoxBEALJQaNDtJTvUGa
oaYAWZCCRRKYOSQth1lmDf5/Ceo/q8nEqggKvDwHlzfyOiuWCQhng3yQWVIn
TMkbnedAtmsywk7vYTXkjDPJni4s7oBbIWI6StigzsnKavA7YHaXCpwsbGWl
QajIpaLFt241B0xmoCxTgCfsmuuRVXtS78YskI/g/O12gGgJIAFLZkm1Dlko
D0EeQPXUSCRTQBs2nQWfk4M3IEdyqZYQfbqd2Y/HNfE0TWBvIAITsJHwKeCD
OwQdMqkqgHWlGUUGKYo9SM8sowjXWUfMgIBiexBS3hS9QITVg77bvgoLC3bd
3hajD5WJFwKPo5UANDEWVQANNgWE/tj/jd8qV/hbkgMp/aYCbhQ9mRvZfylC
0SlQHtkTCN9C5fDKiPSR4hfTwBevmVSgFgZp1IsdcLtsZkSSpqh81mSGrh1g
1hDmX4Ew1ouJOJTLErS3rxfwUpNn5AggDbjpKFkAxy41VaCYSnTVCBltbULg
r46enb08cS7rrEhVl+HOBrQiOUIr2EpM4l1+FxFcMeawAA6CTWVXRgw8nQG0
ynqAwho8r7yk84Jko4JnChWWgDWmgTCHAoxQXknMrMYuVbpICm2WGIoc9vds
PR4Td0rhDeRc6FdIQ9sdsskYgcWprSgJ+y5adnAHOm1ydFkQGBXJnMPuKK5r
ioxFWkT8Zyhj+z3En4I9IqmTfQw7QWkz65Lhq16fNAStNopMOiEhgVhCQknG
iUSHgpVsDekPOHFyXK3ekelEpq3qxyA3jXFO1FLEAr8hUpFnQksEySiyfgbc
oyAXCFBh6gQ21KApmojnIIdogYB2gSNviaeKtFqv6iGRykrYFooD5cVEu9Bk
4ScY1s2sGwXXWxZAnxRU0oZCkW88JaMEcZxBX91zin61TK1QRYAVG5gDziwi
tXG8IOtcU0aFcg8CNVcFKjJQCwSKkNWt83O7RY3IIPUxaMHL2ThPpmWFmiEv
g295DWsDIbaoSvpEFFwZsoazBArR2QyBLijv7wYsaGsps4EsxXo62M4UAipO
55aKjDlY04LS1ZoixUIMZ1ZEGzKLB9HOrXkAX4YSm3SiSYqHvYAiLIro2Z2v
csh4kOcQdFSYk+6PLy4vvUZbpcC3gwC4Gyaa0oaa8LXuvitMKiwIrMEUpAWK
84RE5GWSjadJnoC9zFBm8nJNaT6QlzSjwiy1mDOBQfbevvWB8Gg4lwEdhp24
PaIjNDrrhNhgyA67+SulV1uSd6srBJj4RRvYkLSEMfznk/3JfhzCo4MAHUts
Ok8MBP24RkQTYVMPkHVkOIhHZhbJVTdLuFueJXye9djXKbx7YEvCj4dSMyYl
fBet7QyQg4gOQgIh/mkzmfANCE2WZRHWRjCMcOuQlSFYVMYJwjLhk2va2ufj
uoGImGS2KNlcYt5OHOguixEcqUHWpOjoqrEVYjSbC5WQvbitQkOhHhU42D9Z
7IVfdZPEFVkU+i3R7IdVq6GykSsFcVmjvqX4Uy/A/swXtopgy0BiqAYkwxoQ
0NoLZLAg6dNLW0si2xTUpWx+yPIFmYepfWHhboKG7xXqxq4MdMg15HzMPSeE
Tuc2cEOQklIm1oYfjFNIV8qqESwFMLgbCu/3iZAPcNNUuvrs0Zew45Fg4jn3
SYlpl6PsA+h9s4B9jVF20FprlWeIkriHaF6j/JaW9cfIXc0iTChjao91ZyN3
nr96ebkz4n/lizP6/eIE0L04OcbfX35/+OyZ/0XYb7z8/uzVs+P2t/bNo7Pn
z09eHPPL8FRGj8TO88M/7bAn3Tk7R5t0+GxngG4VhWNTNsoVpK/InsRA5mXS
Sk+5nvHk6Pw//nX/oWQqPtjfByraP77Y/7uH8AfmqrwaBQ38J9B2LYAzKmEr
DyER5FK6Bv83wuwB6HqD+UCFFYK/+REp89OB/GqarvYffmMf4Iajh45m0UOi
Wf9J72Um4sCjgWU8NaPnHUrH+B7+Kfrb0T14+NUfctB/Od7/4g/fCJKh4Gyk
H0W9vRfEFiLyVb0s01W5y9kAoIFKt7il0j0YLWFmMddYkecMCAI0rjceAAfl
aRs5xekmlyxdEKULwARRxVLDHGzDQDI3EtJnmQ7M2DrzjslHSwd7QYBh6CZj
39spnk0A3UPcVlMVlC5ak4shyeA6bWhDUUvaVFiyQudNUb7h9XqxCq4yXGr1
8DyV0L95+wsRfOnyCPcMiRJWWjdFumx8toS6wL4FJzWFr3cS/WquAXZiR0gq
a5uvg//dGMfHKRPayCdl7Z0nm9LA1QT44WnMCEUrqTIilC2TWHfAf+lK9L20
D/RawvmIiNYak0EadFpiuAqN728I58L4pRdDiH6gOOBO0TEjdjeLMo/KArDq
xcnLk8vXl2c/nLzg+MAMuWtxEakghYzg6TOfx7g1uY6KSbaXGGT2vNC/KOOK
BILowyWiHCx14c6MgkDEls6thFD93JeEIes2ZVNBrJVkWYW865atezHvUySB
5ZyrynM1puP42wIl50y+ZLRIrrFiYZMXW4LWleIEDgSWdDssggssTpcs9a7s
jUETxTSNhsAaS31W+IMThKiGYnNrXFRQpcIA+AyPpdqUT4IXwGgoveICrt8B
iGDlDwc7CjYSrByD9WVfx9d0ZInIE89Kri1RYghOtnBxUmt1V5k97ImMNqGF
sMgad8zmKLSA3QSPVBw1eoHVDtNSmVJWYiDsEug4ZI+Xer5gOlYloJshtsNC
cIu9tyWRadkUGZvD0igUl4DgiCViu9GaB1voaE0mmEWBMtolDQR/b2w5q1d6
zPVMYaEMyw/ckEBwx6THri7QOeQkMQ55Ywj2sslrjQkPbgNQPIKkn4UG6ESp
TCX8I9qqr7ZwhwLod3BeE52t2uoib4erhoLKfKwbBK1bUoyk28ZkFDwnuIsU
PqKCDBf0MxEJmzseYBsPRPAV0cjtUVkDc6GBKr2teIteqWODvnjcQUc6W6EQ
FQFVii0eoAUhERuVNhrxisFWLtgO5I4uzgJLSMe1I4EWljgAJoo0U88GayBg
MswSomDneWlDdlFbnqn0fE5nLLqmELlSf27IrsHCHbP6WWRWuz6fMi3ujaAz
gPYYuWMOxMDpAJf8WnYMhYeHFl6X4VQgp7Jy7o81yzyLTmUgmvByBL7rmjNj
PuoRFKpi1tiX2sZVIiljGzAyk26XSFCGxMQbK/2U6Myw3DVV9Y3iMza/dY4C
HRkB3skbDO+QF1FK1A316MVI2FzFlxi4pAionIl+T4VnoQWxhclyjkUM56FF
i4Et1G9NAThFbgq2fGh+792zoeh3XFd1YM7Z/R2F4CET6UWacULiiraRiuJL
Ges7nWMAZraI20l4eq0vIXmHdpNiJd0WySk45Lo2CGPOpnShV7ZlIDIc9C0T
yXt7nnXT/Tq6+c4RrDu/ijQG9+qq0+HZem1UPiOj48p6unZa4VFK8OCiql3Q
G6nTQHnZ7ykifWwdKzxHA+dQAf3hmWJvmYQnqW6vwr+lBw/0fBjUnpeFi7en
ZfZgbtSvSWNPC1beBigE+5vp+bjd43iWlze00f4+mTJUj+xaCDphwmeb+lZi
94EWwwSHikMNA9409/M6Yd+E5NEMmvrLsCumrS+HfV9BDxQw9bfffpNJYq7n
4tPxh/58Kt7JD/15xzBOHOqdn2NHyP7POQa7IQz6dcMqm9eP8aBfeXfywkqB
pD+/eT8Y9P+7hOMRhrS/Bw/+5zzBZi5Vp5O93w2j/81da4tVLEnvBUP+tX2X
DfneNjy+Yoq2KxFRP85e3gdGR4TlodeTAK3255steOyGkTvYhV4uv7cFjw/a
y+9R3U87MOB/Z7bnQu5CIOlSGSeyLnPZO4iQ6MJ4771sgMHceEWZpGfCJp3b
iEegcKg2e/x49welVpGcP37/vVyoaaPzzIH5XfTo6MkgjI/BWw95Ax4bfiIY
P5Krkc8gYfqp/03i1rkLQi1NNujLltV2X2E3CNbNGmzGwHrX3uBebsH4lr0M
/tyR0J9ug9FVomVZtSf2eJh9rVB/3t0C4y57uRsMMLPy1JW9j11gMbaW9n8P
D5KPbrDi5ePOeOyezuJU9uLN3nvh8QF7+Rjy0cVnC6Z3gLF7zIXAyAa9Jwzy
2W3cv81n/+6fdx8ltoRIVbw9kPcGwnZJAz9f72w90+L2ax9Bjr/zTT3kAnZ+
pf4OPqa0KSdmRpRy+nRh4NRjZLuFV5D6aCzmYklHFWsRTyhQ3dilWr2sEvOA
pUoK14R4rah4HJQY8APblclnZMOhv0vJuKw2XdeuZz/KuOY+2OvnGHSqUTa1
cQl0kHFR51WZuy5QbuiD5516bTtp4AmA/QFYnxlRtpcbzlCwf5lrydgxT81A
xh2jbO54p6NwR0pnXbXtwJ7IQxElgVR1wz5KsMaFrm0N1b3WPw0jKEF1KkyL
R77cMcjGtghXGr+EcA36tFR8vjXIyJo6uG3rU1HGr4iyPUEjPheqv4dPuHnX
7fGGWqvyClLhddCdX/qurI+cB36cTNDZni55bJXoWbLG3tD25yWdBsm/lWeV
noMMxVA+Di5IG/ff4L7vBOWdvA//7cN/r4pVpTKdcsP37iM5BRXfeycxOxq3
ye7uU12ZWj4Bbabw4T1xuX8gX2IrifyeW0megk1pcbkFY//b/oF8SscQT3RA
dgdls7bGUB5hx2pWLmmnPSi710mliRZ8tNkLje9E3dt2xNTdVGJ4P7pQhvGJ
O9LAVGMvgHKbLt1VXu6Gy21QYmk7T9bY/RhA6UrdheUUOpG9lkcP3ZMPweVj
7Oj/FnWH/XELZQN1qRwZUHf/0Rby/v+j7of+fIzYsRc9dqM4Hz/24j53VBOV
vF14gSEjd+OFJwYX4JZIwfpNVVGkZQvq288bOuV+25Lr4xvbRMZd1El8bH5b
45CLsyBu1a4RhAM324UttndhDwVl2CM9a9ekc7Nkc7/raDtMwYEejhcsV/Ua
gG87xcKxCj7HbiI7h45mFHUe1dvmKdsJh40Txm0fvO3SwKlnPCEb7H1vJ44t
4UeynNKQkh+R5J4WPH2HR0x1sePHWbBtDXiX1jQ10kDGsmPb5eve6CbQKq00
zgrn3Iprzyrr8gYSRR/w0RmvxmnA4fZ30w5sJv1+LjsJxjOuYsNpuD06bbvv
mQQF8ZO+t6EJBnICnVnZo14NiU0DNOjZaZzhAcnwtWh8oKc7Iu4mALrmDTa8
19iABGx92JUcyp5mJfZju1P5jWMIE3lc0uFVKQ18bKi3fFralqUH+2OEJpe6
0MtmKQ23Svgz2luOaO1Q5pbpAEzaGureo7EKPvQzxPCHvHQ5m/FAxNDJ/ueT
h9ypaCft9+lkH41mz4oJ2caBkD8+2JNfy33sEIzDC/700R5+stlq7N6fTPYf
3d/b9P5nDyYT+nDYu+7uP/gCPv41Mu/cBWP7qK1l32iUn9LX0JLfky/tMXZf
mM+D1o6399rDdtEf4wibHtlGwHYBEk6ItrO8w3N7guQSta73uTvKHDpi73Zs
hJK03+3W6PfB8JSWnxwaSmyHW2U0Jrf9AdG4Jc1uGLuGBsgf9MyMBFZoMKe7
SXTtx9BovB6BuuKlGxbnzFVu0RrfTD50ysrth7YdcQVOWHGzsl3Rj8q13uDW
qSjuYzT9WVvID2iMQSHtaWHchAAiPo68DFB3eByzPbe+KvDyC/bT4UCxrmmW
2s2ocHscz4/yfDzvhmvQJhoWa3tiNpjypqA/NjVPiUgiBlp2ntnhWqxVxG1j
YINsq4JervK1g4QW0c6wBnIJxM2wrDFVkN6bjnX3e0BHurQ1pWhwEBT8MJp4
CW6eoHmiZ4OG9e29sA+Wu53Cgz6eMcmpwL+xRbdnrd0po9hwIcZEuuGY3oRN
3Aa7uaOYi0u+6TRoW4zaf93g0jSgteh3HYXNIETMewQ+HMW59Dic+67mt/fC
nsR6hRbTDZ1xcGSo19yqO0dIffqaTd2NbA1I7Jj0nrKmS6OhUSHwP2/Gl0+O
Xev6bVeFUKd8xFiqYD7mGA/fRpmla50EV3FthdHusQA2B63cseJR6XmIkeIC
bdLKNupoE17Jw8EPw6NG2ar9bgI6VowRW0ZzxAtOFYiLSnjgJu7SVFUFIHCZ
9UrJy4vDFy/Pzy4uX58fXhw+P7k8uXh9cnFxdhEIQMiqp6QKMcuZUZvUZpfW
sTyQ7Qz0lsmFRDhOt7fKeJUIthIG/P7mlc50AYUNAzuAeOMSEdvVGNwweu8R
hET7j8OQ3lpt/IEUYqrY6RaW4Db8pGzoQPQiMsLiQByAXLnrgNq6unQjOm44
vGFH59POPrXjCZaeV92zfcjaRL2VrbFxQiaDuWk3ostHJQuw5IjEvKG+ra39
phgZyyiC6VsHHsRIr8Yq1ynFDo9pttUO61N4gzMjTFF310PSh4QOFxWQeljD
djp3yw4qb/8t3DHPM0ztGDXN6IfJCLdhD6l9MgAw8LjWWAZjJpi+3mKoKM6j
Ad9w6PW2dFxiBNHHiUdCeKrSz0LixTgQ1NcNp0hVSy1r8TqpMHXD45GWRYhv
y7nbxEuIvLNog7Mvt1MWoYbup72+aUAYyLhy22LEOrKerAGbDKggw3Z+cXZ5
dnT27PU/np49O8T9TQYyBh4vrjssvtUXERaIuI9Y+zsg9PhXEPimwOixIOPu
Dul0vAERe4CnaPZfn7w4Ojs+ffEdG//IODyYPOxO2XgCk1ZsZ0ZbZLD0dZdm
td2KKFZ9x03VB0eBgY1bv+iUZ4gMxKJJNx4J7vMasg5+isl6G+5Et/Y2MZvC
uSGT6c5Q3UgApEKYJ9JcJF7GhPUeQZjb2TnH5m2XlY065Yr3aQPn0W13j1s8
ijWj1ITm7ugKscFqj78JDyIRxe3r1gVp0waiermELB9fX9vrRYStCiHn3X1b
NlCtmtz6MQCI1RrjjAwX+mgWq3u1gghm5YiTG5LPkDXKD9Kwa+iODbhMljp6
/JUZfRHpXqZVl6L1KV4KOSZ0KRS8g6MceOHVegCkO9nGu0xCxNgY0XluO5zA
ZCZ5fC9b54+FkxBEcEcaaRRdO1G3oggpGRC6Enbu1tjoJULwDtaSjI0YsJYy
inztAoxZyIiUesh1pparsqbcEaIREUQjaIWmdnKPrj6wY0dxIzdfF9SNEakw
lDYV1hqx1A/L2KEpIX4AQ5KrbK6GRx9sS0ZwYWVtr3Tzd6jJOrpLqJ0Ls1FU
fC0RBUykkOG2aEAlY3ZjyCOiqQDHUDcASMOE5bxKVgt7FZHB7Sl3MGsvHrLv
lxhLfMe3OQSVnfguLF4gpaTCeOKWlK82BRVpsfqqDV7qA0uNUNYL7JTQ7mYa
bk6IyNILL6MLAOlSjNTyg8VLvVkReC6WGsDVnaoEczWXkV0bmOVh0tKIXHjr
CO6C7FRRqzkJg7Zpt7bTO6gXpu4MsBMwfF7p1A0SuAlapBc1lfDA5EjwVFse
tJrEdI5OoUiYKF1ys3cZp9C1vbqFJnaXpWVdtLQvwFTqGmgR+Bjr0Dp3G2FT
jSVaZ2aye+JB461Ui+fvRKOoPCzLAaLoXzTZjyS6I5Jy44ik4Pr/1hFJuW1E
snOZEZ03+IHI/qxkaMfa2Ra0jyjqdJMpXQYnT9EPoP+1L9sjO5qTI1StvsHe
41Xc3aoY63Nri3qzgGjJlrOG8pDuFbTRZUrt3PykfzeAwGm4JDfBrC+uj8Z1
zJ3gU3YlKN406GYFiJXezsAEF7gJvL3QntBEV4bRTa0FDdOQhFXhvbF2HpzL
QG7cjFgWJpjtaPQWgx4zlR0oSw85EqYon+a2hxN2lFxxfmh74O2xqOiMBKV8
mtqpF5tufZrIZV2AJwDevcg3x1CMtgTOjN0Ye7pQ6RUX3baMs0/oHuXDF4c9
n3T55NheuExXWWLZM72yforiQPH2gGVOZV/vzIDpdJB9eXZ8hjm082gT8T/m
p39LSl0AAA==

-->

</rfc>
