<?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.31 (Ruby 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-nandakumar-agentproto-pace-http-00" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="PACE HTTP Binding">PACE Binding over HTTP</title>
    <seriesInfo name="Internet-Draft" value="draft-nandakumar-agentproto-pace-http-00"/>
    <author initials="S." surname="Nandakumar" fullname="Suhas Nandakumar">
      <organization>Cisco</organization>
      <address>
        <email>snandaku@cisco.com</email>
      </address>
    </author>
    <author initials="C." surname="Jennings" fullname="Cullen Jennings">
      <organization>Cisco Systems</organization>
      <address>
        <email>fluffy@cisco.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Applications and Real-Time</area>
    <workgroup>Agent Communication Protocols</workgroup>
    <keyword>agent-to-agent</keyword>
    <keyword>agent-to-tool</keyword>
    <keyword>HTTP</keyword>
    <keyword>AI agents</keyword>
    <keyword>dialog management</keyword>
    <abstract>
      <?line 138?>

<t>This document specifies how the dialog management of the Protocol for
Agent Communication Exchange (PACE) is carried over HTTP. It maps PACE
control operations onto HTTP resources, methods, and an event stream,
and defines a header field that ties application requests to a dialog.
The binding uses HTTP semantics only, so it works over HTTP/1.1,
HTTP/2, and HTTP/3. Protocols that already run over HTTP, such as A2A
and MCP, join a dialog without changes to their transports or
messages. An optional track resource carries dialog content that no
application protocol carries, such as authorization checkpoints. The
document also describes where Oblivious HTTP can hide a participant's
network address from the dialog host, and how the binding relates to
A-SIP.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://suhasHere.github.io/draft-nandakumar-agentproto-pace-http/draft-nandakumar-agentproto-pace-http.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-nandakumar-agentproto-pace-http/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Agent Communication Protocols Working Group mailing list (<eref target="mailto:agentproto@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/agentproto/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/agentproto/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/suhasHere/draft-nandakumar-agentproto-pace-http"/>.</t>
    </note>
  </front>
  <middle>
    <?line 153?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>PACE <xref target="PACE"/> separates agentic dialog management from the transport
that carries it. Its dialog management protocol
(<xref section="3" sectionFormat="of" target="PACE"/>) defines the dialog context (identifier,
generation, state, controller, and participants), sixteen control
operations, and the rules that participants and intermediaries follow
when they propagate the context. <xref target="PACE"/> also binds that protocol to
Media over QUIC Transport (MOQT) <xref target="MoQ-TRANSPORT"/>.</t>
      <t>Most deployed agent protocols run over HTTP. A2A <xref target="A2A"/> uses JSON-RPC
over HTTP with Server-Sent Events for streaming, and MCP <xref target="MCP"/> uses
its Streamable HTTP transport. These applications, and the HTTP
infrastructure in front of them (load balancers, API gateways, reverse
proxies, and authorization servers), need dialog management that does
not require a new transport. This document defines that binding.</t>
      <t>With it, an application gets the PACE dialog model without changing
its HTTP stack:</t>
      <ul spacing="normal">
        <li>
          <t>A dialog identifier that is stable across HTTP connections, HTTP
versions, intermediaries, and application protocols.</t>
        </li>
        <li>
          <t>One authoritative controller and a generation-ordered dialog
context, so participants agree on who is in the dialog and whether it
is still active.</t>
        </li>
        <li>
          <t>Cancellation, revocation, and termination as explicit dialog
operations, independent of whether an HTTP request or connection
happens to be open.</t>
        </li>
        <li>
          <t>Recovery after a lost connection, by resuming an event stream.</t>
        </li>
      </ul>
      <t>The dialog context and control messages are exactly those of <xref target="PACE"/>.
This document adds no control operations, control message members, or
states. It defines how the existing ones are carried over HTTP. One
dialog can use this binding and the MOQT binding at the same time
(<xref target="interworking"/>).</t>
      <section anchor="scope">
        <name>Scope</name>
        <t>This document specifies the HTTP resources that host a dialog
(<xref target="resources"/>), the mapping of control operations onto them
(<xref target="operations"/>), an event stream that delivers control messages
(<xref target="event-stream"/>), invitations (<xref target="invitations"/>), a header field that
ties application requests to a dialog (<xref target="content"/>), an optional track
resource (<xref target="tracks"/>), interworking with the MOQT binding
(<xref target="interworking"/>), and the effect of HTTP versions (<xref target="http-versions"/>),
Oblivious HTTP (<xref target="ohttp"/>), and A-SIP (<xref target="asip"/>).</t>
        <t>Dialog content, such as chat, model output, tool calls, and media, is
carried by the application protocol (<xref target="content"/>), except for the
content of a track resource (<xref target="tracks"/>). This document does not
define real-time media over HTTP. A dialog that needs it carries media
over MOQT under the same dialog identifier.</t>
      </section>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

</section>
      <section anchor="terminology">
        <name>Terminology</name>
        <t>This document uses the terms dialog, dialog context, dialog-id,
participant, principal, invitee, controller, intermediary, dialog
host, propagation relationship, flow, log, and log position as defined
in
<xref section="1.3" sectionFormat="of" target="PACE"/>. It uses the HTTP terms client, server, origin
server, intermediary, resource, and representation as defined in
<xref target="RFC9110"/>. Where the two meanings of "intermediary" could be
confused, this document says "PACE intermediary" or "HTTP
intermediary".</t>
        <dl>
          <dt>Dialog host:</dt>
          <dd>
            <t>As defined in <xref section="1.3" sectionFormat="of" target="PACE"/>. In this binding, it is the
HTTP origin server that hosts a dialog's resources: it keeps the
dialog's control log, accepts control messages from participants,
and delivers them on event streams. It is not the source of dialog
context, unless it is also the controller (<xref target="hosting"/>).</t>
          </dd>
          <dt>Control log:</dt>
          <dd>
            <t>The ordered sequence of control messages that the dialog host has
accepted for a dialog.</t>
          </dd>
          <dt>Control log position:</dt>
          <dd>
            <t>An unsigned integer that the dialog host assigns to each control log
entry, starting at 1 and increasing by one per entry. It orders the
control log and is the resumption point of an event stream
(<xref target="resumption"/>). It is neither a dialog generation nor a log
position of the dialog log (<xref section="3.11" sectionFormat="of" target="PACE"/>), which orders
dialog content. In this binding, dialog log entries are objects on a
track resource (<xref target="log-over-http"/>).</t>
          </dd>
          <dt>Dialog URI:</dt>
          <dd>
            <t>The URI of the dialog resource on the dialog host
(<xref target="dialog-resource"/>).</t>
          </dd>
          <dt>Inbox:</dt>
          <dd>
            <t>An HTTP resource at which an agent receives invitations
(<xref target="invitations"/>).</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="architecture">
      <name>Architecture</name>
      <figure anchor="_figure-arch">
        <name>PACE HTTP Binding Layering</name>
        <artwork><![CDATA[
┌────────────────────────────────────────────────────────────────────┐
│  Application Protocols (A2A, MCP, AutoGen, Poppy, ...)             │
├────────────────────────────────────────────────────────────────────┤
│  PACE Dialog Management: dialog-id | lifecycle | propagation       │
│  ([PACE], Section 3)                                               │
└────────────────────────────────────────────────────────────────────┘
╔════════════════════════════════╗  ┌────────────────────────────────┐
║ PACE HTTP Binding              ║  │ PACE MOQT Binding              │
║ dialog resources | control log ║  │ namespaces | ctrl tracks       │
║ event stream | inboxes         ║  │ content tracks | priority      │
║ PACE-Dialog header field       ║  │ ([PACE], Section 4)            │
╠════════════════════════════════╣  ├────────────────────────────────┤
║ HTTP versions | priority       ║  │ MOQT: pub/sub | relays |       │
║ MOQT interworking gateway      ║<>│ caching                        │
╚════════════════════════════════╝  ├────────────────────────────────┤
┌────────────────────────────────┐  │ WebTransport over HTTP/3,      │
│ HTTP Semantics                 │  │ or native QUIC                 │
├──────────┬──────────┬──────────┤  └────────────────────────────────┘
│ HTTP/1.1 │ HTTP/2   │ HTTP/3   │
│ TLS/TCP  │ TLS/TCP  │ QUIC     │
└──────────┴──────────┴──────────┘

  ╔══╗ defined in this document     ┌──┐ defined elsewhere
  ╚══╝                              └──┘
]]></artwork>
      </figure>
      <t>The parts drawn with double lines are defined in this document. The
dialog management protocol and the MOQT binding are defined in
<xref target="PACE"/>. Both bindings carry the same dialog context and control
messages, and a gateway can join HTTP and MOQT participants in one
dialog (<xref target="interworking"/>).</t>
      <t>The binding uses only HTTP semantics <xref target="RFC9110"/>, so the same
resources and messages work over HTTP/1.1 <xref target="RFC9112"/>, HTTP/2
<xref target="RFC9113"/>, and HTTP/3 <xref target="RFC9114"/>. <xref target="http-versions"/> describes how
each version affects dialog control.</t>
      <section anchor="roles">
        <name>Roles</name>
        <t>In the MOQT binding, every participant is a MOQT endpoint and a relay
fans messages out. HTTP is client/server, so this binding adds a
dialog host, which takes the relay's place for control messages:</t>
        <ul spacing="normal">
          <li>
            <t>Each participant is an HTTP client of the dialog host. It POSTs its
control messages to the dialog URI and receives every participant's
control messages on the dialog host's event stream.</t>
          </li>
          <li>
            <t>The dialog host stores accepted control messages in the control log
and delivers them to every authorized participant.</t>
          </li>
          <li>
            <t>The controller remains the only source of dialog state
(<xref section="3.3.2" sectionFormat="of" target="PACE"/>). The dialog host does not commit, merge,
or change dialog state; it forwards the controller's messages
unchanged.</t>
          </li>
        </ul>
        <t>A participant that is also the dialog host appends its control
messages to the control log directly, without HTTP requests.</t>
      </section>
      <section anchor="hosting">
        <name>Hosting Models</name>
        <t>Any HTTP origin that implements this document can host a dialog. Three
models are common:</t>
        <dl>
          <dt>Controller-hosted:</dt>
          <dd>
            <t>The controller is the dialog host, and other participants are its
HTTP clients. This suits an agent that opens dialogs with many
clients.</t>
          </dd>
          <dt>Invitee-hosted:</dt>
          <dd>
            <t>The controller is an HTTP client of the first invitee, which hosts
the dialog. This is the usual case for A2A and MCP, where a client
agent opens a dialog with a remote agent or tool server. POSTing OPEN
to the invitee's dialog collection is also the invitation
(<xref target="invitation-by-open"/>). A-SIP <xref target="ASIP"/> dialogs are invitee-hosted: the
principal is the controller, and the agent hosts the dialog
(<xref target="asip"/>).</t>
          </dd>
          <dt>Hub-hosted:</dt>
          <dd>
            <t>A dialog host that is not a participant, such as an agent platform
or gateway, hosts the dialog for all participants. This suits
multi-party dialogs whose participants do not serve HTTP.</t>
          </dd>
        </dl>
        <t>The hosting model does not change the dialog. In every model, the
controller is the participant named in <tt>controller_id</tt>, only the
controller assigns generations, and participants authenticate the
controller through key-bound presentations in the <tt>credentials</tt> member
of its control messages (<xref section="7.1.4" sectionFormat="of" target="PACE"/>), not through the
identity of the dialog host.</t>
        <t>The choice of host matters when participants act for principals whose
interests conflict, such as a consumer's agent and a brand's agent
disputing a charge (<xref target="DIALOG-UC"/>, UC1; <xref target="dialog-host-trust"/>). In
such a dialog, the participant that is not the host <bcp14>SHOULD</bcp14> be the
controller, or the dialog <bcp14>SHOULD</bcp14> be hub-hosted by a party both trust.</t>
        <figure anchor="_figure-hosting">
          <name>Invitee-hosted and Hub-hosted Dialogs</name>
          <artwork><![CDATA[
   Invitee-hosted                         Hub-hosted

 +-------+  POST OPEN, UPDATE   +-------+     +-------+      +-------+
 |   A   |--------------------->|   B   |     |   A   |      |   B   |
 | ctrl- |<---------------------| dialog|     +-------+      +-------+
 | ler   |  event stream (SSE)  |  host |       |   ^          |   ^
 +-------+                      +-------+  POST |   | SSE POST |   | SSE
                                                v   |          v   |
                                              +---------------------+
                                              |     dialog host     |
                                              +---------------------+
]]></artwork>
        </figure>
      </section>
    </section>
    <section anchor="resources">
      <name>Dialog Resources</name>
      <t>A dialog host exposes a small set of resources. This section defines
them, how clients find them, and how control messages are
represented.</t>
      <section anchor="uris">
        <name>URIs and Discovery</name>
        <t>This document does not define fixed paths (<xref target="RFC8820"/>). Three URIs
are needed before a client has a dialog, so an agent advertises them
in its Agent Card (<xref section="7.2.3" sectionFormat="of" target="PACE"/>), or a deployment
configures them:</t>
        <dl>
          <dt>dialogs:</dt>
          <dd>
            <t>The dialog collection, to which a controller POSTs OPEN
(<xref target="opening"/>).</t>
          </dd>
          <dt>inbox:</dt>
          <dd>
            <t>The inbox, at which the agent receives invitations (<xref target="inbox"/>).</t>
          </dd>
          <dt>inbox_type:</dt>
          <dd>
            <t><tt>push</tt> or <tt>pull</tt>: whether senders POST invitations to the inbox, or
the agent GETs them from it (<xref target="inbox"/>). Present with <tt>inbox</tt>.</t>
          </dd>
          <dt>join:</dt>
          <dd>
            <t>The join URI, at which a client resolves a join code to a dialog
(<xref target="join-code"/>). Present only if the dialog host accepts join codes.</t>
          </dd>
        </dl>
        <t>The dialog host returns every other URI, such as a dialog URI or a
track resource, in its responses. An Agent Card that advertises this
binding includes:</t>
        <sourcecode type="json"><![CDATA[
{
  "pace": {
    "bindings": ["http", "moqt"],
    "http": {
      "dialogs": "https://agent-b.example/pace/dialogs",
      "inbox": "https://agent-b.example/pace/inbox",
      "inbox_type": "push",
      "join": "https://agent-b.example/pace/join"
    },
    "moqt": {
      "relay": "moqt://relay.example:4443"
    }
  }
}
]]></sourcecode>
        <t>This document defines the member names under <tt>pace</tt>. PACE does not
define a card format (<xref section="7.2.3" sectionFormat="of" target="PACE"/>), so how these members
are placed in a particular format, such as an A2A Agent Card extension
or an SD-Card claim, is left to that format.</t>
        <t>The example URIs in this document follow the pattern below. The
pattern is illustrative only; clients <bcp14>MUST</bcp14> use the URIs the dialog
host returns.</t>
        <table anchor="_table-resources">
          <name>PACE HTTP Resources</name>
          <thead>
            <tr>
              <th align="left">Resource</th>
              <th align="left">Example URI</th>
              <th align="left">Methods</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Dialog collection</td>
              <td align="left">
                <tt>/pace/dialogs</tt></td>
              <td align="left">POST</td>
            </tr>
            <tr>
              <td align="left">Dialog</td>
              <td align="left">
                <tt>/pace/dialogs/{dialog-id}</tt></td>
              <td align="left">GET, POST</td>
            </tr>
            <tr>
              <td align="left">Track resource</td>
              <td align="left">
                <tt>/pace/dialogs/{dialog-id}/tracks</tt></td>
              <td align="left">GET, POST</td>
            </tr>
            <tr>
              <td align="left">Inbox</td>
              <td align="left">
                <tt>/pace/inbox</tt></td>
              <td align="left">POST (push), GET (pull)</td>
            </tr>
            <tr>
              <td align="left">Join URI</td>
              <td align="left">
                <tt>/pace/join</tt></td>
              <td align="left">POST</td>
            </tr>
          </tbody>
        </table>
        <t>A dialog host <bcp14>MUST</bcp14> respond to other methods with 405 (Method Not
Allowed), with an <tt>Allow</tt> header field (<xref target="RFC9110"/>).</t>
        <t>A dialog URI is an address, not a capability. Knowing a dialog URI
<bcp14>MUST NOT</bcp14> grant access to the dialog; the dialog host authorizes every
request (<xref target="authorization"/>).</t>
      </section>
      <section anchor="media-types">
        <name>Media Types</name>
        <t>A control message (<xref section="3.10" sectionFormat="of" target="PACE"/>) is sent over HTTP as one
JSON object with the media type <tt>application/pace+json</tt>
(<xref target="iana-media-type"/>). The object is exactly the PACE control message,
with no envelope.</t>
        <t>A control message is an I-JSON message <xref target="RFC7493"/>. A dialog host and
every receiver <bcp14>MUST</bcp14> reject one with duplicate member names, invalid
Unicode, or numbers that I-JSON does not allow, because two parsers
that resolve such input differently would act on different messages
under one valid signature (<xref target="json-parsing"/>).</t>
        <t>This binding moves a control message between several serializations:
the POST body, the single-line <tt>data</tt> of an event (<xref target="event-stream"/>),
and the payload of a MOQT object (<xref target="interworking"/>). A control message
is therefore its JSON value, not its octets:</t>
        <ul spacing="normal">
          <li>
            <t>Wherever this document requires a message to be forwarded
unmodified, the value is preserved: the same members, at every
level, with the same values. Whitespace, member order, and string
escaping can change.</t>
          </li>
          <li>
            <t>Two messages are identical when their JCS <xref target="RFC8785"/> forms are
equal.</t>
          </li>
          <li>
            <t>Hashes and signatures over a message, or over an object it carries,
are computed over a JCS form, so they survive re-serialization. Every
key-bound presentation in <tt>credentials</tt>, whether a Workload Proof
Token, a Key Binding JWT, or a PACE presentation JWT, binds itself to
its control message with the message hash claim <tt>mth</tt>, which
<xref target="WPT-MSG"/> defines. PACE computes <tt>mth</tt> under its <tt>pace</tt>
canonicalization profile: over the JCS form of the message without
its <tt>credentials</tt> member (<xref section="7.1.4" sectionFormat="of" target="PACE"/>). The detached JWS
<tt>signature</tt> of a checkpoint covers the JCS form of the checkpoint
object without its <tt>signature</tt> member <xref target="PACE-AUTHZ"/>.</t>
          </li>
        </ul>
        <t>Control messages are not compressed (<xref section="4.2.3" sectionFormat="of" target="PACE"/>). A
dialog host <bcp14>MAY</bcp14> apply HTTP content coding to a response, but the
decoded representation is the unmodified control message.</t>
      </section>
      <section anchor="dialog-collection">
        <name>The Dialog Collection</name>
        <t>A POST of an OPEN to the dialog collection creates a dialog resource
(<xref target="opening"/>). The dialog collection rejects any other control message
type with 400 (Bad Request) and <tt>pace_reason</tt> <tt>unsupported-operation</tt>.</t>
      </section>
      <section anchor="dialog-resource">
        <name>The Dialog Resource</name>
        <t>The dialog resource represents one dialog. It supports:</t>
        <dl>
          <dt>POST:</dt>
          <dd>
            <t>Appends a control message to the control log (<xref target="operations"/>).</t>
          </dd>
          <dt>GET with <tt>Accept: application/pace+json</tt>:</dt>
          <dd>
            <t>Returns the latest context-carrying control message from the
controller (<xref target="snapshot"/>).</t>
          </dd>
          <dt>GET with <tt>Accept: text/event-stream</tt>:</dt>
          <dd>
            <t>Opens an event stream of the control log (<xref target="event-stream"/>).</t>
          </dd>
        </dl>
        <t>The dialog resource exists from the time OPEN is accepted until the
dialog host discards it after termination (<xref target="termination"/>).</t>
      </section>
    </section>
    <section anchor="operations">
      <name>Control Operations over HTTP</name>
      <t>A participant needs to send control messages to every other
participant and to learn the outcome. This section defines how a
participant POSTs a control message, how the dialog host reports its
processing, and how each PACE operation maps onto that.</t>
      <section anchor="sending">
        <name>Sending a Control Message</name>
        <t>A participant POSTs one control message per request to the dialog URI
with <tt>Content-Type: application/pace+json</tt>. The dialog host processes
the request as follows. Each step names the response when the step
fails; <xref target="_table-status"/> lists every status code with its <tt>pace_reason</tt>.</t>
        <ol spacing="normal" type="1"><li>
            <t>Authenticate the HTTP client and check that it may send this
message to this dialog (<xref target="authorization"/>). The HTTP client
identity <bcp14>MUST</bcp14> correspond to the <tt>sender_id</tt> of the message; a client
<bcp14>MUST NOT</bcp14> send control messages on behalf of another participant.
Failure: 401 (no or invalid HTTP authentication), 403 (the sender
is not authorized, or has been revoked), 404 (no such dialog, or the
client may not learn of it), or 503 (authorization cannot be
determined).</t>
          </li>
          <li>
            <t>Validate the message as a PACE control message
(<xref section="3.10" sectionFormat="of" target="PACE"/>): required members, member types,
version, size, and I-JSON (<xref target="media-types"/>). Failure: 400 (the
message is malformed, or its version or <tt>type</tt> is not supported),
413 (the message is too large), or 415 (the body is not
<tt>application/pace+json</tt>).</t>
          </li>
          <li>
            <t>If the message is a duplicate, respond as <xref target="retries"/> describes.</t>
          </li>
          <li>
            <t>Check that the dialog has not been terminated or expired, except
for a STATE needed to complete synchronization (<xref target="termination"/>).
Failure: 410 (the dialog has been terminated or has expired).</t>
          </li>
          <li>
            <t>If the message is an UPDATE, REVOKE, or TERMINATE from the
controller, check that its generation is exactly one more than the
generation of the latest such message in the control log. Failure:
409 with <tt>pace_reason</tt> <tt>stale-generation</tt>.</t>
          </li>
          <li>
            <t>Append the message to the control log, assign it the next control
log position, and deliver it on every open event stream for the
dialog. Respond with 202 (Accepted), or 201 (Created) for OPEN, with
the assigned position in the <tt>PACE-Log-Position</tt> header field
(<xref target="iana-fields"/>).</t>
          </li>
        </ol>
        <t>A dialog host <bcp14>MUST NOT</bcp14> modify a control message. It <bcp14>MUST NOT</bcp14>
reorder control log entries after assigning positions, and it <bcp14>MUST</bcp14>
deliver entries to each event stream in control log position order.
<xref target="dialog-host-trust"/> describes what participants can detect when a
dialog host breaks these rules.</t>
        <t>A 202 (Accepted) response means only that the message is in the
control log. It does not mean that any participant has received or
applied it. Participants learn the outcome from later messages on the
event stream: the controller's UPDATE commits an ACCEPT, REJECT,
JOIN_REQUEST, LEAVE, or DECLARE (<xref section="3.3.2" sectionFormat="of" target="PACE"/>); CANCEL_ACK
answers a CANCEL; and ERROR reports a refusal.</t>
      </section>
      <section anchor="status-codes">
        <name>Status Codes</name>
        <t>HTTP status codes report the dialog host's processing of a request.
They are distinct from PACE ERROR messages, which a participant sends
when it does not apply an operation (<xref section="3.8" sectionFormat="of" target="PACE"/>). A dialog
host that rejects a request responds with a problem details object
<xref target="RFC9457"/> (<tt>application/problem+json</tt>). When a PACE reason
(<xref section="3.8.1" sectionFormat="of" target="PACE"/>) applies, the object carries it in the
<tt>pace_reason</tt> extension member, and carries the <tt>message_id</tt> of the
rejected message, if any, in <tt>pace_message_id</tt>.</t>
        <table anchor="_table-status">
          <name>Dialog Host Status Codes</name>
          <thead>
            <tr>
              <th align="left">Status</th>
              <th align="left">Condition</th>
              <th align="left">pace_reason</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">201 (Created)</td>
              <td align="left">OPEN accepted; dialog resource created</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">202 (Accepted)</td>
              <td align="left">Message appended to the control log</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">400 (Bad Request)</td>
              <td align="left">Unparsable, not I-JSON, missing a required member, or reused <tt>message_id</tt> (<xref target="retries"/>)</td>
              <td align="left">
                <tt>malformed</tt></td>
            </tr>
            <tr>
              <td align="left">400 (Bad Request)</td>
              <td align="left">Unsupported control-message version</td>
              <td align="left">
                <tt>unsupported-version</tt></td>
            </tr>
            <tr>
              <td align="left">400 (Bad Request)</td>
              <td align="left">Unrecognized <tt>type</tt>, or not OPEN at the dialog collection</td>
              <td align="left">
                <tt>unsupported-operation</tt></td>
            </tr>
            <tr>
              <td align="left">403 (Forbidden)</td>
              <td align="left">Sender not authorized, or invalid join code</td>
              <td align="left">
                <tt>unauthorized</tt></td>
            </tr>
            <tr>
              <td align="left">403 (Forbidden)</td>
              <td align="left">Sender has been revoked</td>
              <td align="left">
                <tt>participant-revoked</tt></td>
            </tr>
            <tr>
              <td align="left">403 (Forbidden)</td>
              <td align="left">Inbox sender has opted out (<xref target="refusing"/>)</td>
              <td align="left">
                <tt>unwanted-contact</tt></td>
            </tr>
            <tr>
              <td align="left">404 (Not Found)</td>
              <td align="left">No such dialog, or the client may not learn of it</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">409 (Conflict)</td>
              <td align="left">OPEN for a dialog-id that already exists</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">409 (Conflict)</td>
              <td align="left">Controller generation is not the next one</td>
              <td align="left">
                <tt>stale-generation</tt></td>
            </tr>
            <tr>
              <td align="left">409 (Conflict)</td>
              <td align="left">Track object out of order or changed (<xref target="tracks"/>)</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">410 (Gone)</td>
              <td align="left">The dialog has been terminated or has expired</td>
              <td align="left">
                <tt>dialog-terminated</tt></td>
            </tr>
            <tr>
              <td align="left">425 (Too Early)</td>
              <td align="left">Message received in early data (<xref target="early-data"/>)</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">429 (Too Many Requests)</td>
              <td align="left">Contact limits or join code attempt limits exceeded (<xref target="refusing"/>, <xref target="join-code"/>)</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">503 (Service Unavailable)</td>
              <td align="left">Authorization cannot be determined</td>
              <td align="left">
                <tt>authorization-unavailable</tt></td>
            </tr>
          </tbody>
        </table>
        <t>Other status codes have their meanings from <xref target="RFC9110"/>; for example,
401 when HTTP authentication is missing or invalid, 413 when a message
exceeds the dialog host's limit, and 415 when the body is not
<tt>application/pace+json</tt>.</t>
        <t>For example, a dialog host rejects a controller's UPDATE whose
generation is not the next one:</t>
        <sourcecode type="http-message"><![CDATA[
HTTP/1.1 409 Conflict
Content-Type: application/problem+json

{
  "type":
    "https://iana.org/assignments/pace/errors#stale-generation",
  "title": "Generation is not the next expected generation",
  "status": 409,
  "pace_reason": "stale-generation",
  "pace_message_id": "1b9d6bcd-bbfd-4b2d-9b5d-ab8dfbbd4bed"
}
]]></sourcecode>
        <t>A refusal by a participant is a dialog-level answer, not an HTTP
error, even when that participant is the dialog host. For example, a
controller-hosted dialog that refuses a JOIN_REQUEST accepts the
request with 202 and appends the controller's ERROR
(<xref section="3.3.2" sectionFormat="of" target="PACE"/>). The outcome is then visible to every
participant that tracks the control log, whatever the hosting model.</t>
      </section>
      <section anchor="retries">
        <name>Retries and Duplicates</name>
        <t>POST is not idempotent, but PACE control messages are: each carries a
unique <tt>message_id</tt>, and reprocessing a duplicate <bcp14>MUST NOT</bcp14> repeat its
side effects (<xref section="3.3.3" sectionFormat="of" target="PACE"/>).</t>
        <ul spacing="normal">
          <li>
            <t>A client that does not receive a response <bcp14>MAY</bcp14> repeat the POST with
the identical message (<xref target="media-types"/>); it need not send the same
octets.</t>
          </li>
          <li>
            <t>A dialog host that receives a message whose <tt>sender_id</tt> and
<tt>message_id</tt> match a control log entry <bcp14>MUST NOT</bcp14> append it again, and
<bcp14>MUST</bcp14> respond as it did to the original, including the original
<tt>PACE-Log-Position</tt>.</t>
          </li>
          <li>
            <t>A message that reuses a <tt>message_id</tt> and is not identical is
rejected with 400 (Bad Request) and <tt>pace_reason</tt> <tt>malformed</tt>.</t>
          </li>
        </ul>
      </section>
      <section anchor="opening">
        <name>Opening a Dialog</name>
        <t>The controller opens a dialog by POSTing OPEN
(<xref section="3.3" sectionFormat="of" target="PACE"/>) to the dialog collection of the dialog
host. The controller generates the dialog-id (<xref section="3.2" sectionFormat="of" target="PACE"/>);
the dialog host does not assign it. In the following example, agent-a,
the controller, opens an invitee-hosted dialog (<xref target="hosting"/>) with
agent-b, which hosts it at agent-b.example:</t>
        <sourcecode type="http-message"><![CDATA[
POST /pace/dialogs HTTP/1.1
Host: agent-b.example
Authorization: DPoP eyJhbGciOi...
DPoP: eyJ0eXAiOiJkcG9wK2p3dCIs...
Content-Type: application/pace+json
Accept: application/pace+json, text/event-stream

{
  "version": 1,
  "type": "OPEN",
  "dialog_id": "550e8400-e29b-41d4-a716-446655440000",
  "generation": 0,
  "sender_id": "agent-a",
  "message_id": "6f1c7c6e-3a3e-4b5e-9c55-0b8b4b1d0e11",
  "context": {
    "dialog_id": "550e8400-e29b-41d4-a716-446655440000",
    "generation": 0,
    "controller_id": "agent-a",
    "state": "pending",
    "participants": [
      {"participant_id": "agent-a", "state": "active"},
      {"participant_id": "agent-b", "state": "invited"}
    ]
  },
  "parameters": {"supported_protocols": ["a2a"]},
  "credentials": "eyJ...",
  "nonce": "q0v8pS2l7yY3mY0b1i4o9A"
}
]]></sourcecode>
        <t><tt>parameters</tt>, <tt>credentials</tt>, and <tt>nonce</tt> are control message members
(<xref section="3.10" sectionFormat="of" target="PACE"/>). <tt>parameters</tt> carries the dialog parameters
that the controller proposes (<xref section="3.5" sectionFormat="of" target="PACE"/>); <tt>credentials</tt>
carries agent-a's credential with its presentation for agent-b, which
has no nonce yet (<xref section="7.1.4.2" sectionFormat="of" target="PACE"/>); and <tt>nonce</tt> is the
value to which agent-b binds its presentation in ACCEPT. The HTTP
request itself is authorized with a DPoP-bound access token
<xref target="RFC9449"/>.</t>
        <t>On success the dialog host responds with 201 (Created) and a
<tt>Location</tt> header field giving the dialog URI. Dialog URIs are
opaque (<xref target="uris"/>), so the controller checks the dialog itself: it <bcp14>MUST</bcp14>
verify that the first entry of the dialog's event stream is its own
OPEN, unchanged, and otherwise treats the dialog host as untrusted
(<xref target="dialog-host-trust"/>). If the request's
<tt>Accept</tt> header field includes <tt>text/event-stream</tt>, the dialog host
<bcp14>MAY</bcp14> send the event stream for the new dialog as the response content,
starting with the OPEN at control log position 1 (<xref target="event-stream"/>).
This saves the controller a separate GET. Otherwise the response
content is empty or a representation of the OPEN. For example,
agent-b answers agent-a's OPEN above with the event stream, whose
first entry is that OPEN:</t>
        <sourcecode type="http-message"><![CDATA[
HTTP/1.1 201 Created
Location: /pace/dialogs/550e8400-e29b-41d4-a716-446655440000
PACE-Log-Position: 1
Content-Type: text/event-stream
Cache-Control: no-store

id: 1
event: OPEN
data: {"version":1,"type":"OPEN","dialog_id":"550e8400-...",...}

]]></sourcecode>
        <t>A dialog host <bcp14>MUST</bcp14> reject an OPEN whose <tt>dialog_id</tt> already exists
with 409 (Conflict), unless it is a duplicate (<xref target="retries"/>). Since
dialog-ids are random UUIDs, a collision indicates a faulty or
malicious sender. The controller can open the dialog again with a new
dialog-id.</t>
        <t>The dialog host makes the dialog visible to each invitee listed in the
OPEN context, and to no one else. An invitee that hosts the dialog
already has the OPEN. Any other invitee learns of the dialog from an
invitation that the dialog host sends to the invitee's inbox: an HTTP
resource, advertised in the invitee's Agent Card (<xref target="uris"/>), at which
an agent receives invitations (<xref target="inbox"/>).</t>
      </section>
      <section anchor="accepting-or-rejecting">
        <name>Accepting or Rejecting</name>
        <t>Each invitee (<xref section="1.3" sectionFormat="of" target="PACE"/>), such as <tt>agent-b</tt> in the
example above, answers with ACCEPT or REJECT, with <tt>in_reply_to</tt>
naming the OPEN, or the UPDATE, that invited it. An ACCEPT carries three control message members (<xref section="3.10" sectionFormat="of" target="PACE"/>): <tt>parameters</tt>, the dialog parameters the invitee accepts
(<xref section="3.5" sectionFormat="of" target="PACE"/>); <tt>credentials</tt>, its credential with a
presentation bound to the controller's nonce from the OPEN
(<xref section="7.1.4" sectionFormat="of" target="PACE"/>); and <tt>nonce</tt>, a fresh value to which the
controller binds its next presentation.</t>
        <t>How the invitee gets the OPEN and sends its answer depends on the
hosting model (<xref target="hosting"/>):</t>
        <ul spacing="normal">
          <li>
            <t>In an invitee-hosted dialog, the invitee is the dialog host. It
received the OPEN as the controller's POST, and appends its answer
to the control log directly.</t>
          </li>
          <li>
            <t>Otherwise, the invitee is an HTTP client of the dialog host. It
learns of the dialog from an invitation (<xref target="invitations"/>), reads the
OPEN from the event stream or a snapshot (<xref target="snapshot"/>), and POSTs
its answer to the dialog URI.</t>
          </li>
        </ul>
        <t>An <tt>active</tt> participant answers a parameter proposal in an UPDATE,
and acknowledges a SEGMENT, in the same way (<xref section="3.3.2" sectionFormat="of" target="PACE"/>,
<xref section="3.7.1" sectionFormat="of" target="PACE"/>).</t>
        <t>The controller reads the answer on its event stream and commits it
with an UPDATE at the next generation, marking the invitee <tt>active</tt> or
<tt>rejected</tt>. The dialog becomes <tt>active</tt> with the first such UPDATE
that marks an invitee <tt>active</tt> (<xref section="3.3.2" sectionFormat="of" target="PACE"/>).</t>
        <t>Before an invitee accepts, the dialog host <bcp14>MUST NOT</bcp14> deliver it any
dialog content and <bcp14>MUST</bcp14> limit its event stream to the controller's
control messages and its own (<xref target="visibility"/>).</t>
      </section>
      <section anchor="joining">
        <name>Joining a Dialog</name>
        <t>A prospective participant that knows a dialog URI asks to join by
POSTing JOIN_REQUEST to it. The dialog host accepts the request from a
client that is not a participant only as <xref target="authorization"/> allows.
The prospective participant <bcp14>MAY</bcp14> then GET the event stream, which the
dialog host limits as for an invitee (<xref target="visibility"/>).</t>
        <t>The controller admits the joiner with an UPDATE that sets its state to
<tt>invited</tt>. The joiner then sends ACCEPT, and the controller's next
UPDATE marks it <tt>active</tt>. A controller that declines sends ERROR
<tt>policy-rejected</tt> (<xref section="3.3.2" sectionFormat="of" target="PACE"/>), and the dialog host
then ends the joiner's event stream.</t>
        <t>Other participants see the JOIN_REQUEST on the event stream and <bcp14>MUST</bcp14>
ignore it, as in <xref section="4.3.2" sectionFormat="of" target="PACE"/>. A joiner therefore
discloses in its credentials only claims that every participant may
see.</t>
      </section>
      <section anchor="join-code">
        <name>Joining with a Join Code</name>
        <t>A participant on a channel that cannot carry the dialog URI, such as
a PSTN call, can join from another channel with a join code
(<xref section="3.4.6" sectionFormat="of" target="PACE"/>). The controller issues the code to an
existing participant, and the code is conveyed over the call. A client
that has the code but not the dialog URI resolves the code first:</t>
        <ol spacing="normal" type="1"><li>
            <t>The client POSTs <tt>{"join_code": "..."}</tt>, with
<tt>Content-Type: application/json</tt>, to the join URI, which the
agent advertises in its Agent Card (<xref target="uris"/>) or in a Link header
field with the relation type <tt>pace-join</tt> (<xref target="iana-link"/>).</t>
          </li>
          <li>
            <t>The dialog host responds with 200 (OK) and
<tt>{"dialog_id": "...", "dialog_uri": "..."}</tt>. Resolving does not use
up the code.</t>
          </li>
          <li>
            <t>The client POSTs JOIN_REQUEST, carrying <tt>join_code</tt>, to the dialog
URI. The dialog host responds with 202, as for any control message.</t>
          </li>
        </ol>
        <t>The dialog host accepts both requests from an otherwise unauthorized
client. For both, it:</t>
        <ul spacing="normal">
          <li>
            <t><bcp14>MUST</bcp14> accept each code in one JOIN_REQUEST only, and <bcp14>MUST</bcp14> reject a
code that is unknown, expired, or already used with 403 (Forbidden)
and <tt>pace_reason</tt> <tt>unauthorized</tt>, without saying which; and</t>
          </li>
          <li>
            <t><bcp14>MUST</bcp14> limit attempts per client, per code, and per dialog, and
respond with 429 (Too Many Requests) <xref target="RFC6585"/> beyond the limit,
because codes read aloud are short.</t>
          </li>
        </ul>
        <t>The dialog host makes these checks before it appends a JOIN_REQUEST,
so that guesses reach neither the controller nor the other
participants. They add to the controller's own checks
(<xref section="3.4.6" sectionFormat="of" target="PACE"/>), and the controller still decides
admission. The code authorizes only the JOIN_REQUEST; later requests
use the client's own credentials (<xref target="authorization"/>).</t>
      </section>
      <section anchor="updating-declaring-revoking-and-leaving">
        <name>Updating, Declaring, Revoking, and Leaving</name>
        <t>The controller POSTs UPDATE, REVOKE, and TERMINATE, each with the
complete context at the next generation (<xref section="3.3.3" sectionFormat="of" target="PACE"/>).
Because the dialog host checks generation continuity (<xref target="sending"/>),
two concurrent state changes from the controller cannot both be
appended: the second receives 409 (Conflict), and the controller
resends after reading the control log.</t>
        <t>A participant leaves by POSTing LEAVE. The controller commits it with
an UPDATE marking the participant <tt>left</tt>, and <bcp14>SHOULD</bcp14> send TERMINATE if
it is then the only active participant (<xref section="3.3" sectionFormat="of" target="PACE"/>).</t>
        <t>Any <tt>active</tt> participant POSTs DECLARE to state its own descriptors,
such as its kind, consent, or posture, or its observations of others
(<xref section="3.4.2" sectionFormat="of" target="PACE"/>). The controller commits it with UPDATE. The
dialog host <bcp14>MUST NOT</bcp14> withhold a DECLARE from the event stream, even
when the dialog host is the controller, so that every participant can
check the committed values against it.</t>
        <t>The controller POSTs SEGMENT to start or end a segment
(<xref section="3.7.1" sectionFormat="of" target="PACE"/>). From a SEGMENT with <tt>phase</tt> <tt>start</tt> to the
matching SEGMENT with <tt>phase</tt> <tt>end</tt>, the dialog host applies the
segment rules of <xref target="visibility"/>.</t>
        <t>When the dialog host appends a REVOKE (<xref section="3.4.7" sectionFormat="of" target="PACE"/>), it
<bcp14>MUST</bcp14>:</t>
        <ul spacing="normal">
          <li>
            <t>stop delivering control messages and content for the dialog to the
revoked participant, after delivering the REVOKE itself as the last
event on its stream, and then end that stream;</t>
          </li>
          <li>
            <t>stop forwarding requests to the revoked participant, and cancel any
request it holds only to propagate the dialog to it; and</t>
          </li>
          <li>
            <t>reject later requests from the revoked participant for the dialog
with 403 (Forbidden) and <tt>pace_reason</tt> <tt>participant-revoked</tt>.</t>
          </li>
        </ul>
      </section>
      <section anchor="snapshot">
        <name>State Requests and Snapshots</name>
        <t>A GET on the dialog URI with <tt>Accept: application/pace+json</tt> returns a
snapshot: the latest context-carrying control message from the
controller, that is, the OPEN, UPDATE, REVOKE, TERMINATE, or STATE
with the highest generation in the control log. The dialog host
returns it unmodified, with the <tt>PACE-Log-Position</tt> of that entry and
an <tt>ETag</tt> that changes whenever the snapshot changes. A client <bcp14>MAY</bcp14> use
a conditional GET with <tt>If-None-Match</tt> to poll for changes.</t>
        <t>The snapshot is a copy of a controller message, not a message from
the dialog host. A participant that applies it <bcp14>MUST</bcp14> verify the origin
and integrity of the controller's presentation in <tt>credentials</tt>
(<xref section="7.1.4.3" sectionFormat="of" target="PACE"/>) and apply the generation rules of
<xref section="3.3.3" sectionFormat="of" target="PACE"/>, as for the same message on the event
stream, so it need not trust the dialog host to leave it unchanged.
Verification does not show that the snapshot is current: a dialog host
can return an older message of the controller. A participant ignores
a snapshot whose generation is lower than the latest it has accepted,
and uses STATE_REQUEST when it needs the latest state.</t>
        <t>A snapshot does not replace STATE_REQUEST. A participant that needs a
fresh context bound to its own nonce, for example after a gap in
generations or when it resumes after a disconnection
(<xref section="3.9" sectionFormat="of" target="PACE"/>), POSTs STATE_REQUEST with its
<tt>last_accepted_generation</tt>, <tt>nonce</tt>, and <tt>credentials</tt>, and the
controller answers by POSTing STATE (<xref section="7.1.4.1" sectionFormat="of" target="PACE"/>).</t>
        <t>Snapshot responses <bcp14>MUST</bcp14> carry <tt>Cache-Control: private, no-cache</tt>, so
that shared HTTP caches do not store them and private caches revalidate
before reuse (<xref target="RFC9111"/>).</t>
      </section>
      <section anchor="cancel-over-http">
        <name>Cancellation</name>
        <t>CANCEL (<xref section="3.6.1" sectionFormat="of" target="PACE"/>) asks the participants doing some
work to stop it, without ending the dialog. A participant sends it by
POSTing it to the dialog URI, like any other control message. Besides
the members every control message has, CANCEL carries:</t>
        <dl>
          <dt>scope:</dt>
          <dd>
            <t>Which work to stop, as <xref section="3.6.1" sectionFormat="of" target="PACE"/> defines:
<tt>operation</tt>, one application request the sender made; <tt>dialog</tt>, all
work the sender started in this dialog, including work delegated
from it; or <tt>subtree</tt>, the work in the dialogs delegated from this
one.</t>
          </dd>
          <dt>target:</dt>
          <dd>
            <t>With scope <tt>operation</tt> only: the application request to stop. Over
MOQT, a request is named by its track; over HTTP, it is named by its
protocol and request identifier, as an object with these members:
</t>
            <dl>
              <dt>protocol:</dt>
              <dd>
                <t>The protocol identifier of <xref section="8" sectionFormat="of" target="PACE"/>, such as <tt>mcp</tt>,
<tt>a2a</tt>, or <tt>ext</tt>.</t>
              </dd>
              <dt>request_id:</dt>
              <dd>
                <t>The application's identifier for the request, such as the JSON-RPC
<tt>id</tt> or the A2A task identifier.</t>
              </dd>
              <dt>uri:</dt>
              <dd>
                <t>Optional. The target URI of the application request.</t>
              </dd>
            </dl>
          </dd>
        </dl>
        <t>For example, agent-a asks agent-b to stop the MCP tool call <tt>t1</tt> that
it made to <tt>https://tools.example/mcp</tt>:</t>
        <sourcecode type="json"><![CDATA[
{
  "version": 1,
  "type": "CANCEL",
  "dialog_id": "550e8400-e29b-41d4-a716-446655440000",
  "generation": 1,
  "sender_id": "agent-a",
  "message_id": "0c5b7c1e-9f2a-4d3b-8e6f-2a1b3c4d5e6f",
  "scope": "operation",
  "target": {
    "protocol": "mcp",
    "request_id": "t1",
    "uri": "https://tools.example/mcp"
  },
  "credentials": "eyJ..."
}
]]></sourcecode>
        <t>An ERROR that rejects an application operation uses the same form
(<xref section="3.8.1" sectionFormat="of" target="PACE"/>).</t>
        <t>Each receiver doing the affected work applies the cancellation through
the application protocol's own mechanism and POSTs CANCEL_ACK.</t>
        <t>Closing an HTTP connection, resetting an HTTP/2 or HTTP/3 stream, or
abandoning an application request <bcp14>MUST NOT</bcp14> be treated as CANCEL.
Conversely, a CANCEL does not by itself close any HTTP request; the
application protocol ends its own responses when the work stops.
CANCEL travels on its own HTTP request, so it does not wait behind
streamed application responses. <xref target="priority"/> describes how to keep it
ahead of content.</t>
      </section>
      <section anchor="termination">
        <name>Termination and Expiry</name>
        <t>The controller ends the dialog by POSTing TERMINATE. After appending
it, the dialog host:</t>
        <ul spacing="normal">
          <li>
            <t>delivers TERMINATE on every open event stream and then ends each
stream;</t>
          </li>
          <li>
            <t>responds to later POSTs for the dialog with 410 (Gone) and
<tt>pace_reason</tt> <tt>dialog-terminated</tt>, except a duplicate TERMINATE,
which receives its original response, and a STATE needed to complete
synchronization (<xref section="3.6.2" sectionFormat="of" target="PACE"/>); and</t>
          </li>
          <li>
            <t>answers snapshot GETs with the TERMINATE for a retention period of
its choosing, after which it <bcp14>MAY</bcp14> respond with 404 (Not Found) or 410
(Gone).</t>
          </li>
        </ul>
        <t>When <tt>expires_at</tt> passes, the dialog host treats the dialog as
terminated in the same way, without appending a message. Expiry does
not create a generation (<xref section="3.6.2" sectionFormat="of" target="PACE"/>).</t>
      </section>
      <section anchor="summary-of-the-mapping">
        <name>Summary of the Mapping</name>
        <t>Every control message except OPEN is POSTed to the dialog URI, and
every control message is delivered on the event stream. Some are also
delivered elsewhere, as the last column shows.</t>
        <table anchor="_table-mapping">
          <name>PACE Operations over HTTP</name>
          <thead>
            <tr>
              <th align="left">PACE Operation</th>
              <th align="left">Sent by</th>
              <th align="left">Also delivered</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">OPEN (to the dialog collection)</td>
              <td align="left">Controller</td>
              <td align="left">As an invitation to each invitee's inbox, unless it hosts the dialog (<xref target="inbox"/>)</td>
            </tr>
            <tr>
              <td align="left">ACCEPT, REJECT</td>
              <td align="left">Invitee or participant</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">UPDATE</td>
              <td align="left">Controller</td>
              <td align="left">As an invitation to the inbox of each invitee it adds</td>
            </tr>
            <tr>
              <td align="left">JOIN_REQUEST</td>
              <td align="left">Prospective participant</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">LEAVE, DECLARE, STATE_REQUEST</td>
              <td align="left">Participant</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">SEGMENT, REVOKE</td>
              <td align="left">Controller</td>
              <td align="left"> </td>
            </tr>
            <tr>
              <td align="left">TERMINATE</td>
              <td align="left">Controller</td>
              <td align="left">Then every stream ends</td>
            </tr>
            <tr>
              <td align="left">STATE</td>
              <td align="left">Controller</td>
              <td align="left">Snapshot (<xref target="snapshot"/>)</td>
            </tr>
            <tr>
              <td align="left">CANCEL, CANCEL_ACK, LOG_STATUS, ERROR</td>
              <td align="left">Any participant</td>
              <td align="left"> </td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section anchor="event-stream">
      <name>Event Stream</name>
      <t>Participants need every control message pushed to them as soon as it
is accepted, and need to catch up after a lost connection. The event
stream does both with Server-Sent Events <xref target="SSE"/>.</t>
      <section anchor="format">
        <name>Format</name>
        <t>A participant receives the control log by sending GET to the dialog
URI with <tt>Accept: text/event-stream</tt>. The dialog host responds with
200 (OK) and an SSE stream. Each control log entry is one event:</t>
        <ul spacing="normal">
          <li>
            <t><tt>id</tt> is the entry's control log position, in decimal.</t>
          </li>
          <li>
            <t><tt>event</tt> is the control message <tt>type</tt>.</t>
          </li>
          <li>
            <t><tt>data</tt> is the control message, serialized as JSON on a single line.
The dialog host need not reproduce the octets the sender POSTed, but
it <bcp14>MUST</bcp14> preserve the message's value (<xref target="media-types"/>).</t>
          </li>
        </ul>
        <t>For example, the controller's UPDATE at generation 1 is the third
entry of the control log, and a participant's CANCEL the fourth:</t>
        <artwork><![CDATA[
id: 3
event: UPDATE
data: {"version":1,"type":"UPDATE","generation":1,...}

id: 4
event: CANCEL
data: {"version":1,"type":"CANCEL","scope":"operation",...}

]]></artwork>
        <t>The dialog host <bcp14>MAY</bcp14> send SSE comment lines to keep idle connections
open, and <bcp14>MAY</bcp14> send a <tt>retry</tt> field. Comments carry no dialog
semantics; in particular, they do not count as activity for the
dialog's idle timeout (<xref section="3.5.2" sectionFormat="of" target="PACE"/>).</t>
        <t>Event stream responses <bcp14>MUST</bcp14> carry <tt>Cache-Control: no-store</tt>.</t>
        <t>A participant <bcp14>MUST</bcp14> process events in control log position order.
Control log positions only order the log. The participant applies
controller operations by generation (<xref section="3.3.3" sectionFormat="of" target="PACE"/>), and
treats a generation gap as a reason to send STATE_REQUEST. A receiver
that does not recognize an event type <bcp14>MUST</bcp14> handle it as
<xref section="3.10" sectionFormat="of" target="PACE"/> requires for an unrecognized <tt>type</tt>.</t>
      </section>
      <section anchor="starting-position">
        <name>Starting Position</name>
        <t>An event stream starts at control log position 1 by default, so a new
participant sees the complete control log, including the OPEN and
every committed change. A dialog host <bcp14>MAY</bcp14> compact a long control log.
If it does, it <bcp14>MUST</bcp14> keep, at a minimum, the latest context-carrying
controller message and every later entry, and a stream that requests a
compacted range starts at the oldest retained entry. A participant
that receives a stream whose first entry is not the one it requested
<bcp14>MUST</bcp14> send STATE_REQUEST before acting on state that may have changed
(<xref section="3.9" sectionFormat="of" target="PACE"/>).</t>
      </section>
      <section anchor="resumption">
        <name>Resumption</name>
        <t>A participant that loses its event stream reconnects with GET and the
<tt>Last-Event-ID</tt> header field set to the last control log position it
processed, as <xref target="SSE"/> defines. The dialog host resumes the stream with
the next entry, or with the oldest retained entry if those entries
were compacted. The participant then:</t>
        <ol spacing="normal" type="1"><li>
            <t>sends STATE_REQUEST, as <xref section="3.9" sectionFormat="of" target="PACE"/> requires after any
reconnection, and applies the controller's STATE only after
authenticating the controller and checking its generation; and</t>
          </li>
          <li>
            <t>if it reads or publishes on a track resource, POSTs LOG_STATUS and
resumes each track after its accepted position (<xref target="log-over-http"/>).</t>
          </li>
        </ol>
        <t>The participant learns which application requests completed while it
was away through the application protocol, such as A2A <tt>GetTask</tt>, not
from the control log (<xref section="3.9" sectionFormat="of" target="PACE"/>).</t>
      </section>
      <section anchor="polling">
        <name>Polling</name>
        <t>Some clients cannot hold a response open, such as clients behind
proxies that buffer responses and clients that use Oblivious HTTP
(<xref target="ohttp"/>). Such a client polls:</t>
        <ul spacing="normal">
          <li>
            <t>It sends the event stream GET with <tt>Last-Event-ID</tt> and the <tt>wait</tt>
preference <xref target="RFC7240"/>, for example <tt>Prefer: wait=30</tt>.</t>
          </li>
          <li>
            <t>A dialog host that honors the preference sends the entries that
follow <tt>Last-Event-ID</tt> and then ends the response. If there are
none, it waits up to the requested number of seconds for one before
ending the response. It includes <tt>Preference-Applied: wait</tt>.</t>
          </li>
          <li>
            <t>The client sends its next poll with the last control log position it
received.</t>
          </li>
          <li>
            <t>A dialog host that does not honor the preference sends an ordinary
stream.</t>
          </li>
        </ul>
        <t>Polling does not change which entries a client receives or their
order. A track resource (<xref target="tracks"/>) and a pull inbox (<xref target="inbox"/>) are
polled in the same way.</t>
      </section>
      <section anchor="visibility">
        <name>Visibility</name>
        <t>The dialog host delivers to each client only what that client may
see. A participant's state is the one in the latest committed
controller context in the control log, not the one implied by the
participant's own requests.</t>
        <table anchor="_table-visibility">
          <name>Event Stream Visibility</name>
          <thead>
            <tr>
              <th align="left">Client state</th>
              <th align="left">Delivered on the event stream</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Invited or prospective (not yet <tt>active</tt>)</td>
              <td align="left">Controller's control messages, and the client's own</td>
            </tr>
            <tr>
              <td align="left">
                <tt>active</tt></td>
              <td align="left">All control messages</td>
            </tr>
            <tr>
              <td align="left">
                <tt>left</tt>, <tt>rejected</tt></td>
              <td align="left">The committing UPDATE, then the stream ends</td>
            </tr>
            <tr>
              <td align="left">
                <tt>revoked</tt></td>
              <td align="left">The REVOKE, then the stream ends</td>
            </tr>
          </tbody>
        </table>
        <t>Every <tt>active</tt> participant receives every control message, whatever
its <tt>access</tt> or the segments in progress, so that each participant
sees the whole lifecycle. Content is restricted further, by three
rules. They apply to content on the track resource and to
application requests that the dialog host relays.</t>
        <dl>
          <dt>Only what <tt>access</tt> allows:</dt>
          <dd>
            <t>A participant with an <tt>access</tt> descriptor
(<xref section="3.4.1" sectionFormat="of" target="PACE"/>) receives only the flows and modalities in
its <tt>receive</tt> list, and may publish only those in its <tt>send</tt> list.
Without <tt>access</tt>, it receives and publishes every flow.</t>
          </dd>
          <dt>Segment content stays in the segment:</dt>
          <dd>
            <t>The content of a segment is exchanged in the segment's own dialog,
which only the participants the segment names can read. The others
see only the SEGMENT control messages, which tell them that the
segment took place.</t>
          </dd>
          <dt>Nothing new before a segment is acknowledged:</dt>
          <dd>
            <t>A participant that a segment does not name receives no content
published after the SEGMENT until its ACCEPT naming the SEGMENT is in
the control log (<xref section="3.7.1" sectionFormat="of" target="PACE"/>), so it has seen the
SEGMENT before later content reaches it.</t>
          </dd>
        </dl>
        <t>The dialog host enforces these rules for content it hosts or relays.
Each participant applies them to content that the application protocol
carries directly (<xref target="content"/>). These rules protect content only from
other participants, and only as far as the dialog host follows them.
Participants that do not trust each other to honor a segment, or that
do not trust the dialog host, protect content end to end
(<xref target="dialog-host-trust"/>).</t>
      </section>
    </section>
    <section anchor="invitations">
      <name>Invitations and Discovery</name>
      <t>When a controller opens a dialog, the invitee may not know that the
dialog exists, or where it is hosted. It needs the dialog URI to read
the OPEN and answer it. This binding gives it that URI in one of two
ways:</t>
      <ul spacing="normal">
        <li>
          <t>When the invitee hosts the dialog, the OPEN POSTed to it is the
invitation (<xref target="invitation-by-open"/>).</t>
        </li>
        <li>
          <t>Otherwise, the invitee receives an invitation, carrying the dialog
URI, at its inbox (<xref target="inbox"/>).</t>
        </li>
      </ul>
      <t>An invitee can refuse an invitation and limit later contact from the
same sender (<xref target="refusing"/>). The same inbox also receives contacts
outside any dialog, such as offers, and a follow-up dialog delivers
updates to an agent that is offline (<xref target="follow-up"/>).</t>
      <section anchor="invitation-by-open">
        <name>Invitation by OPEN</name>
        <t>In an invitee-hosted dialog, the controller POSTs OPEN to the
invitee's dialog collection (<xref target="opening"/>). That OPEN is the
invitation: the invitee holds the dialog and needs nothing more.
Participants that the controller invites later, with UPDATE, receive
an inbox invitation.</t>
      </section>
      <section anchor="inbox">
        <name>Inbox Invitations</name>
        <t>An inbox is an HTTP resource at which an agent receives invitations.
The party that hosts the dialog sends each invitation: the dialog host,
which in a controller-hosted dialog is the controller.</t>
        <dl>
          <dt>The invitation:</dt>
          <dd>
            <t>A JSON object with the media type <tt>application/pace-invitation+json</tt>
(<xref target="iana-media-type"/>) and these members:
</t>
            <dl>
              <dt>dialog_id:</dt>
              <dd>
                <t>The dialog identifier.</t>
              </dd>
              <dt>controller_id:</dt>
              <dd>
                <t>The controller's participant identifier.</t>
              </dd>
              <dt>invitee_id:</dt>
              <dd>
                <t>The invitee's participant identifier.</t>
              </dd>
              <dt>dialog_uri:</dt>
              <dd>
                <t>The dialog URI on the dialog host.</t>
              </dd>
              <dt>expires_at:</dt>
              <dd>
                <t>Optional. The time after which the invitation is void.</t>
              </dd>
              <dt>purpose, basis:</dt>
              <dd>
                <t>Optional. Copies of the <tt>purpose</tt> and <tt>basis</tt> parameters of the
OPEN (<xref section="3.5.1" sectionFormat="of" target="PACE"/>), so that the invitee can screen
the invitation before it reads the dialog.</t>
              </dd>
              <dt>related_dialogs:</dt>
              <dd>
                <t>Optional. A copy of the <tt>related_dialogs</tt> member of the dialog
context (<xref section="3.2" sectionFormat="of" target="PACE"/>), for example naming the dialog
that a follow-up continues.</t>
              </dd>
            </dl>
          </dd>
          <dt>What it proves:</dt>
          <dd>
            <t>Nothing. Like the MOQT invitation (<xref section="4.1.3" sectionFormat="of" target="PACE"/>), an
invitation only points to the dialog. It carries no dialog context
and grants no access. The invitee reads the OPEN or UPDATE that
invites it from the dialog URI and decides on that. The copied
members are hints: where they differ from the control messages, the
control messages apply, and the invitee <bcp14>SHOULD</bcp14> reject the
invitation.</t>
          </dd>
          <dt>Push and pull inboxes:</dt>
          <dd>
            <t>An agent advertises its inbox URI in its Agent Card (<xref target="uris"/>), and
whether the inbox is push or pull, in <tt>inbox_type</tt>:
</t>
            <ul spacing="normal">
              <li>
                <t>A push inbox is on an HTTP server that the invitee operates. The
sender POSTs the invitation to it, and the inbox responds with 202
(Accepted). The inbox authenticates the sender (<xref target="refusing"/>) and
<bcp14>SHOULD</bcp14> accept invitations only from agents the invitee is willing
to hear from, as following does in the MOQT binding
(<xref section="7.2.2" sectionFormat="of" target="PACE"/>).</t>
              </li>
              <li>
                <t>A pull inbox is on a server that the invitee can reach but does
not operate, such as its dialog host or platform. This suits agents
that cannot accept inbound HTTP connections, such as agents on user
devices. The invitee GETs the inbox with <tt>Accept:
text/event-stream</tt> and receives each invitation as an SSE event of
type <tt>invitation</tt>, with an <tt>id</tt> that the inbox server assigns for
resumption (<xref target="resumption"/>). The inbox server delivers to each
authenticated client only the invitations naming it as
<tt>invitee_id</tt>.</t>
              </li>
            </ul>
          </dd>
          <dt>Offline invitees:</dt>
          <dd>
            <t>An invitee that comes online late GETs its pull inbox without
<tt>Last-Event-ID</tt> to receive pending invitations, and ignores those
whose <tt>expires_at</tt> has passed.</t>
          </dd>
        </dl>
      </section>
      <section anchor="refusing">
        <name>Refusing Contact</name>
        <t>An invitee needs to refuse unwanted contact, and to limit later
contact from the same sender.</t>
        <dl>
          <dt>Refusing:</dt>
          <dd>
            <t>The invitee POSTs REJECT to the dialog URI. The REJECT <bcp14>MAY</bcp14> carry a
<tt>result</tt>, such as reason <tt>unwanted-contact</tt> or <tt>no-stated-purpose</tt>,
and <tt>contact_limits</tt> (<xref section="3.6.3" sectionFormat="of" target="PACE"/>), for example an
opt-out from later contacts by the same sender.</t>
          </dd>
          <dt>Purpose and basis:</dt>
          <dd>
            <t>A contact that no subscription or existing dialog covers <bcp14>SHOULD</bcp14>
carry <tt>purpose</tt> and <tt>basis</tt>, and an invitee <bcp14>MAY</bcp14> refuse one that does
not (<xref section="3.5.1" sectionFormat="of" target="PACE"/>; <xref target="DIALOG-UC"/>, UC3-4).</t>
          </dd>
          <dt>Applying limits:</dt>
          <dd>
            <t>An inbox applies the limits it has recorded to the sender it
authenticates; limits with scope <tt>sender</tt> apply across dialogs. For a
sender that has exceeded them, the inbox:
</t>
            <ul spacing="normal">
              <li>
                <t>responds to a push invitation with 429 (Too Many Requests)
<xref target="RFC6585"/>, with a <tt>Retry-After</tt> field when <tt>retry_after</tt> was
given, or, after an opt-out, with 403 (Forbidden) and
<tt>pace_reason</tt> <tt>unwanted-contact</tt>; and</t>
              </li>
              <li>
                <t>does not deliver such an invitation on a pull inbox.</t>
              </li>
            </ul>
          </dd>
          <dt>Unauthenticated senders:</dt>
          <dd>
            <t>Limits cannot be tied to a sender that is not authenticated
(<xref section="3.6.3" sectionFormat="of" target="PACE"/>). An inbox <bcp14>SHOULD NOT</bcp14> accept push
invitations from senders it cannot authenticate; one that does can
limit them only per channel or address.</t>
          </dd>
        </dl>
      </section>
      <section anchor="follow-up">
        <name>Follow-up and Offline Delivery</name>
        <t>A participant can want updates after a dialog ends, such as a consumer
agent waiting for a refund (<xref target="DIALOG-UC"/>, UC3), even while it is
offline.</t>
        <dl>
          <dt>Opening the follow-up:</dt>
          <dd>
            <t>The participant opens a follow-up dialog as its controller, with a
<tt>related_dialogs</tt> entry of relation <tt>follow-up</tt> naming the original
dialog (<xref section="3.2" sectionFormat="of" target="PACE"/>). As controller, it sets the dialog's
<tt>expires_at</tt> and ends it with TERMINATE. A related dialog is not a
delegated one, so it survives the end of the original.</t>
          </dd>
          <dt>Receiving updates:</dt>
          <dd>
            <t>The other party publishes each update on the track resource. An
offline subscriber receives the updates when it next reads the track
resource from its last position (<xref target="resumption"/>), so it needs no push
endpoint. Each update is delivered at least once, and the subscriber
discards duplicates by group and object ID, as for any replay of the
dialog log (<xref section="3.11.2" sectionFormat="of" target="PACE"/>). The dialog host keeps
updates for at least the <tt>log_retention</tt> that the subscriber
proposed. A <tt>deferred</tt> <tt>result</tt> in the original dialog can give the
time of the next update in <tt>next_update_at</tt>, so the subscriber need
not poll more often.</t>
          </dd>
          <dt>Contact without a dialog:</dt>
          <dd>
            <t>A party that contacts a principal with no follow-up dialog, such as
with a renewal offer, sends an invitation to the principal's agent's
inbox, with <tt>purpose</tt> and <tt>basis</tt> (<xref target="refusing"/>).</t>
          </dd>
        </dl>
      </section>
      <section anchor="agent-cards">
        <name>Agent Cards</name>
        <t>An agent publishes its Agent Card at an HTTPS URI, such as the A2A
well-known Agent Card URI, and receivers verify it as
<xref section="7.2.3" sectionFormat="of" target="PACE"/> requires. Agent Card responses <bcp14>MAY</bcp14> be cached
according to their HTTP cache headers; a card that is specific to a
requester <bcp14>MUST</bcp14> be served with <tt>Cache-Control: private</tt>.</t>
      </section>
    </section>
    <section anchor="content">
      <name>Correlating Application Requests</name>
      <t>Dialog content is carried by the application protocol over its own
HTTP transport, such as A2A JSON-RPC over HTTP or MCP Streamable
HTTP. Those messages carry the dialog reference in their own extension
points (<xref section="8.1" sectionFormat="of" target="PACE"/>), which HTTP intermediaries do not
parse. This binding adds an HTTP header field so that intermediaries
and servers can correlate a request to a dialog without parsing its
content.</t>
      <section anchor="pace-dialog-header">
        <name>The PACE-Dialog Header Field</name>
        <t><tt>PACE-Dialog</tt> is a Dictionary Structured Field <xref target="RFC9651"/> with
these members:</t>
        <dl>
          <dt>id:</dt>
          <dd>
            <t>Required. A String carrying the canonical textual form of the
dialog-id.</t>
          </dd>
          <dt>gen:</dt>
          <dd>
            <t>Optional. An Integer carrying the latest generation the sender
knows.</t>
          </dd>
          <dt>uri:</dt>
          <dd>
            <t>Optional. A String carrying the dialog URI.</t>
          </dd>
        </dl>
        <t>Receivers ignore members they do not recognize. For example, agent-a
sends an A2A request to agent-b in the dialog, at generation 3, and
names the dialog both in <tt>PACE-Dialog</tt> and in the A2A message
metadata:</t>
        <sourcecode type="http-message"><![CDATA[
POST /a2a HTTP/1.1
Host: agent-b.example
Content-Type: application/json
PACE-Dialog: id="550e8400-e29b-41d4-a716-446655440000", gen=3

{"jsonrpc":"2.0","method":"SendMessage","id":"r1","params":{
 "message":{..., "metadata":{"org.ietf.agentproto/dialog-context":
 {"dialog_id":"550e8400-e29b-41d4-a716-446655440000",
  "generation":3}}}}}
]]></sourcecode>
        <t>A client <bcp14>SHOULD</bcp14> send <tt>PACE-Dialog</tt> on every application HTTP request
that belongs to a dialog, in addition to the dialog reference in the
application message. When both are present, they <bcp14>MUST</bcp14> name the same
dialog-id; a receiver <bcp14>MUST</bcp14> reject a request in which they differ, with
400 (Bad Request). A server <bcp14>MAY</bcp14> send <tt>PACE-Dialog</tt> on responses.</t>
        <t>Like every dialog reference, <tt>PACE-Dialog</tt> is a correlation value. It
<bcp14>MUST NOT</bcp14> be treated as a credential, and a server <bcp14>MUST</bcp14> authorize the
request independently of it (<xref section="3.2" sectionFormat="of" target="PACE"/>). A server that
receives a request naming a dialog in which the client is not an
<tt>active</tt> participant <bcp14>SHOULD</bcp14> reject it with 403 (Forbidden).</t>
        <t>The field gives HTTP intermediaries one place to apply dialog-level
policy, such as routing all requests of a dialog to the same backend,
rate limiting per dialog, or rejecting requests for a terminated
dialog, and to record the dialog-id for audit. An HTTP intermediary
<bcp14>MUST NOT</bcp14> add, change, or remove <tt>PACE-Dialog</tt>.</t>
      </section>
      <section anchor="application-protocols-over-http">
        <name>Application Protocols over HTTP</name>
        <t>This binding does not change the HTTP transport, message format, or
semantics of any application protocol. An MCP client and server keep
Streamable HTTP, JSON-RPC, and MCP session handling; an A2A client and
server keep their JSON-RPC or HTTP+JSON binding. PACE support is added
beside them:</t>
        <ul spacing="normal">
          <li>
            <t>Application requests carry the dialog reference in the protocol's
existing extension point, such as MCP <tt>_meta</tt> or A2A message
<tt>metadata</tt> (<xref section="8.1" sectionFormat="of" target="PACE"/>), and <bcp14>SHOULD</bcp14> carry the
<tt>PACE-Dialog</tt> header field. Implementations that do not support
PACE ignore both.</t>
          </li>
          <li>
            <t>PACE control messages go to the dialog URI, not to the application
endpoint (<xref target="operations"/>). A PACE component next to the application
client or server sends and receives them; the application protocol
does not see them.</t>
          </li>
          <li>
            <t>A PACE CANCEL is applied through the protocol's own cancellation,
so the application sees its native cancel (<xref target="cancel-over-http"/>).</t>
          </li>
        </ul>
        <table anchor="_table-app">
          <name>Application Protocols over HTTP</name>
          <thead>
            <tr>
              <th align="left">Protocol</th>
              <th align="left">HTTP transport</th>
              <th align="left">Dialog reference</th>
              <th align="left">Cancellation</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">MCP</td>
              <td align="left">Streamable HTTP</td>
              <td align="left">
                <tt>_meta</tt>, and <tt>PACE-Dialog</tt></td>
              <td align="left">PACE CANCEL applied as <tt>notifications/cancelled</tt></td>
            </tr>
            <tr>
              <td align="left">A2A</td>
              <td align="left">JSON-RPC or HTTP+JSON</td>
              <td align="left">Message <tt>metadata</tt>, and <tt>PACE-Dialog</tt></td>
              <td align="left">PACE CANCEL applied as <tt>CancelTask</tt></td>
            </tr>
            <tr>
              <td align="left">Other</td>
              <td align="left">Protocol's own</td>
              <td align="left">Protocol's extension point, and <tt>PACE-Dialog</tt></td>
              <td align="left">Protocol's own</td>
            </tr>
          </tbody>
        </table>
        <t>PACE dialog-ids are distinct from application session and context
identifiers, such as the MCP session identifier (<tt>Mcp-Session-Id</tt>) or
the A2A <tt>contextId</tt>. A dialog-id <bcp14>MUST NOT</bcp14> be used as one of them
(<xref section="8.1" sectionFormat="of" target="PACE"/>). A dialog can contain one MCP session or A2A
context, or span several, for example when an application reconnects.</t>
        <t>An application server need not be the dialog host or implement PACE.
A server that does not implement PACE works unchanged but does not
enforce dialog membership. One that does, even when another origin
hosts the dialog, tracks the control log or snapshot to know the
participant set and state.</t>
      </section>
    </section>
    <section anchor="tracks">
      <name>Dialog Tracks</name>
      <t>Some dialog content has no application protocol to carry it:</t>
      <ul spacing="normal">
        <li>
          <t>flows defined by PACE extensions, such as the <tt>checkpoint</tt> flow of
<xref target="PACE-AUTHZ"/>;</t>
        </li>
        <li>
          <t>content tracks, such as <tt>chat</tt> or <tt>progress</tt>, that MOQT participants
publish in a dialog that also has HTTP participants
(<xref target="interworking"/>); and</t>
        </li>
        <li>
          <t>content of a hub-hosted dialog whose participants share no
application protocol.</t>
        </li>
      </ul>
      <t>For such content, a dialog host <bcp14>MAY</bcp14> offer a track resource. It holds
the objects that participants publish on named tracks, in the sense of
the MOQT binding (<xref section="4.1.2" sectionFormat="of" target="PACE"/>), and delivers them on an
event stream. A dialog host that hosts dialogs using PACE
Authorization <bcp14>MUST</bcp14> offer a track resource, because it is the only way
HTTP participants send and receive checkpoint objects (requests,
responses, commitments, and assertions), which <xref target="PACE-AUTHZ"/> carries
as a reliable flow named <tt>checkpoint</tt> at the Urgent Signals tier. In
this binding, that flow is each participant's track named <tt>checkpoint</tt>
on the track resource.</t>
      <t>A dialog host that offers a track resource advertises its URI in a
Link header field <xref target="RFC8288"/> with the relation type <tt>pace-tracks</tt>
(<xref target="iana-link"/>) on the 201 response to OPEN and on snapshot responses:</t>
      <sourcecode type="http-message"><![CDATA[
HTTP/1.1 201 Created
Location: /pace/dialogs/550e8400-e29b-41d4-a716-446655440000
Link: </pace/dialogs/550e8400-e29b-41d4-a716-446655440000/tracks>;
      rel="pace-tracks"
]]></sourcecode>
      <t>Track payloads pass through the dialog host, which can read them
unless participants protect them end to end; <xref target="dialog-host-trust"/>
requires this when the dialog host is untrusted.</t>
      <t>Track payloads pass through the dialog host, which can read them
unless participants protect them end to end; <xref target="dialog-host-trust"/>
requires this when the dialog host is untrusted.</t>
      <t>Clients <bcp14>MUST</bcp14> use the advertised URI. Only <tt>active</tt> participants may
publish to or read from a track resource, and an extension that
defines a track can restrict access further. The dialog host
authorizes track requests as it does control messages
(<xref target="authorization"/>), and stops accepting them when the dialog
terminates (<xref target="termination"/>). Track responses <bcp14>MUST</bcp14> carry
<tt>Cache-Control: no-store</tt>.</t>
      <t>Real-time media is not carried on a track resource; a dialog that
needs it uses MOQT (<xref target="webtransport"/>).</t>
      <section anchor="the-pace-track-header-field">
        <name>The PACE-Track Header Field</name>
        <t><tt>PACE-Track</tt> (<xref target="iana-fields"/>) identifies an object or a position on
a track resource. It is a Dictionary Structured Field <xref target="RFC9651"/> with
these members:</t>
        <dl>
          <dt>name:</dt>
          <dd>
            <t>A String carrying the track name. Required.</t>
          </dd>
          <dt>g:</dt>
          <dd>
            <t>An Integer carrying the group ID. Required on POST.</t>
          </dd>
          <dt>o:</dt>
          <dd>
            <t>An Integer carrying the object ID within the group. Required on
POST.</t>
          </dd>
          <dt>sender:</dt>
          <dd>
            <t>A String carrying the publisher's participant identifier. Used only
on GET, to read one publisher's track from a position
(<xref target="log-over-http"/>).</t>
          </dd>
        </dl>
      </section>
      <section anchor="publishing-an-object">
        <name>Publishing an Object</name>
        <t>A participant publishes one object per POST to the track resource.
The request content is the object's payload, <tt>Content-Type</tt> is its
media type, and <tt>PACE-Track</tt> identifies it. For example, a participant
of a dialog hosted at hub.example publishes a checkpoint request as
object 0 of group 4 on its <tt>checkpoint</tt> track:</t>
        <sourcecode type="http-message"><![CDATA[
POST /dialogs/550e8400-e29b-41d4-a716-446655440000/tracks HTTP/1.1
Host: hub.example
Content-Type: application/json
PACE-Track: name="checkpoint", g=4, o=0

{"type":"request", ...,
 "signature":"eyJhbGciOiJFUzI1NiJ9..9XUavKNq..."}
]]></sourcecode>
        <t>The publisher of an object is the authenticated HTTP client; a client
cannot publish on another participant's track. The dialog host
responds with 204 (No Content) when it stores the object.</t>
        <ul spacing="normal">
          <li>
            <t>Each publisher's objects on a track <bcp14>MUST</bcp14> be in increasing order of
group ID, and of object ID within a group. A POST that goes
backwards receives 409 (Conflict).</t>
          </li>
          <li>
            <t>A POST that repeats a stored object with identical content receives
204 again; one that repeats it with different content receives 409
(Conflict). Content with a JSON media type (<tt>application/json</tt> or a
<tt>+json</tt> suffix) is identical as defined in <xref target="media-types"/>. Other
content is identical when its octets are equal.</t>
          </li>
          <li>
            <t>A JSON payload must be I-JSON; the dialog host rejects one that is
not with 400 (Bad Request).</t>
          </li>
        </ul>
        <t>Other status codes are as in <xref target="_table-status"/>.</t>
      </section>
      <section anchor="reading-objects">
        <name>Reading Objects</name>
        <t>A participant reads the track resource with GET and
<tt>Accept: text/event-stream</tt>. To receive one track, it <bcp14>MAY</bcp14> include
<tt>PACE-Track</tt> with only <tt>name</tt>; to receive one publisher's track from a
position, it includes <tt>name</tt>, <tt>sender</tt>, <tt>g</tt>, and <tt>o</tt>
(<xref target="log-over-http"/>). Otherwise it receives every track it may read.
Each object is one event:</t>
        <ul spacing="normal">
          <li>
            <t><tt>id</tt> is the object's position in the track resource, which the
dialog host assigns. Track resource positions are distinct from
control log positions and from log positions.</t>
          </li>
          <li>
            <t><tt>event</tt> is <tt>object</tt>.</t>
          </li>
          <li>
            <t><tt>data</tt> is a JSON object on a single line with the members <tt>sender</tt>
(the publisher's participant identifier), <tt>track</tt>, <tt>g</tt>, <tt>o</tt>, and
<tt>content_type</tt>. A JSON payload is in <tt>json</tt>, as a JSON value that the
dialog host preserves as it does a control message
(<xref target="media-types"/>). Any other payload is in <tt>data</tt>, base64url-encoded
without padding (<xref section="5" sectionFormat="of" target="RFC4648"/>), with its octets
preserved exactly.</t>
          </li>
        </ul>
        <t>For example, the checkpoint request that agent-b published as object 0
of group 4 is the twelfth object of the track resource:</t>
        <artwork><![CDATA[
id: 12
event: object
data: {"sender":"agent-b","track":"checkpoint","g":4,"o":0,...}

]]></artwork>
        <t>Because the dialog host re-serializes JSON payloads, signatures over
them are computed over their JCS form, as for checkpoints
(<xref target="media-types"/>). A publisher whose payload is signed over its exact
octets uses a non-JSON media type, so that the octets travel in <tt>data</tt>.</t>
        <t>Resumption with <tt>Last-Event-ID</tt> and polling work as for the event
stream (<xref target="resumption"/>, <xref target="polling"/>). The dialog host chooses how long
it retains objects, but no less than the dialog's <tt>log_retention</tt>
parameter (<xref section="3.5" sectionFormat="of" target="PACE"/>) when it is set. A client that
resumes from a position that the dialog host no longer retains starts
at the oldest retained object, and learns what it missed from the
application or the publisher.</t>
      </section>
      <section anchor="log-over-http">
        <name>Log Replay and Rehydration</name>
        <t>The dialog log of <xref section="3.11" sectionFormat="of" target="PACE"/> maps onto track resources
as follows:</t>
        <ul spacing="normal">
          <li>
            <t>A flow is one publisher's track on the track resource. In the
<tt>positions</tt> of LOG_STATUS, <tt>flow</tt> has the form the MOQT binding uses
(<xref section="4.2.4" sectionFormat="of" target="PACE"/>), with an empty <tt>namespace</tt> and the track
<tt>name</tt> as <tt>track</tt>.</t>
          </li>
          <li>
            <t>A log entry is an object. Its log position is its group and object
ID, encoded in <tt>accepted</tt> as <tt>{"group": G, "object": O}</tt>.</t>
          </li>
          <li>
            <t>All flows on a track resource are <tt>reliable</tt>.</t>
          </li>
        </ul>
        <t>A receiver retrieves the entries of a flow from a given position with
a GET on the track resource whose <tt>PACE-Track</tt> carries <tt>name</tt>,
<tt>sender</tt>, <tt>g</tt>, and <tt>o</tt>. The dialog host starts the stream at the first
object of that publisher's track after that group and object ID, and
continues it live. A new client instance rehydrates the log in the
same way.</t>
        <t>The dialog host stores the objects it accepted, so a publisher whose
POST received 204 (No Content) has made that entry available. After
LOG_STATUS, a publisher re-POSTs, with identical content, only those
entries above the reported accepted positions that the dialog host no
longer holds; the dialog host accepts them as repeats.</t>
        <t>Application requests carried over the application protocol's own HTTP
transport (<xref target="content"/>) are not dialog log entries in this binding.
Their replay and completion status remain those of the application
protocol, such as A2A <tt>GetTask</tt> or MCP Streamable HTTP resumption, and
LOG_STATUS does not list them.</t>
      </section>
    </section>
    <section anchor="interworking">
      <name>Interworking with the MOQT Binding</name>
      <t>One dialog can have both HTTP and MOQT participants, such as a browser
that carries voice over MOQT and a tool server that uses MCP over HTTP.
The dialog keeps one dialog-id, controller, and generation sequence
(<xref section="3.9" sectionFormat="of" target="PACE"/>). A gateway, which is a PACE intermediary,
joins the two:</t>
      <ul spacing="normal">
        <li>
          <t>It is the dialog host for the HTTP participants. It publishes each
HTTP participant's control messages, unmodified, as objects on a
<tt>ctrl</tt> track under <tt>("pace","dialogs",{dialog-id},{participant-id})</tt>,
where participant-id is that participant's <tt>sender_id</tt>. The relay
must authorize the gateway to publish under these identifiers.</t>
        </li>
        <li>
          <t>It holds SUBSCRIBE_TRACKS on <tt>("pace","dialogs",{dialog-id})</tt> and
appends every <tt>ctrl</tt> object it receives to the control log, so HTTP
participants see MOQT participants' control messages on their event
streams.</t>
        </li>
        <li>
          <t>If it offers a track resource (<xref target="tracks"/>), it publishes each HTTP
participant's objects on the named track under the same namespace,
with the same group and object IDs. It delivers to HTTP participants,
on the track resource, the objects of other tracks it receives
through SUBSCRIBE_TRACKS, except real-time media tracks. Both bindings
use group and object IDs as log positions, so LOG_STATUS passes
between them unchanged, and the gateway serves FETCH for the objects
it published (<xref target="log-over-http"/>, <xref section="4.2.4" sectionFormat="of" target="PACE"/>).</t>
        </li>
        <li>
          <t>It <bcp14>MUST NOT</bcp14> change dialog-id, generation, sender, or message
content in either direction, and <bcp14>MUST</bcp14> preserve the controller's
generation order. Message content is the JSON value
(<xref target="media-types"/>). A gateway <bcp14>SHOULD</bcp14> publish the JCS <xref target="RFC8785"/> form
of a message as the MOQT object payload, so that a repeated message
yields identical objects whichever HTTP serialization it arrived in.</t>
        </li>
        <li>
          <t>It applies relay authorization on the MOQT side
(<xref section="9.2.2" sectionFormat="of" target="PACE"/>) and HTTP authorization on the HTTP side
(<xref target="authorization"/>) for the same participant set.</t>
        </li>
      </ul>
      <t>Because the gateway forwards messages unchanged, participants
authenticate one another end to end through <tt>credentials</tt>, whichever
binding each uses. A CANCEL with scope <tt>operation</tt> names its target in
the form of the binding the sender uses for the targeted work: a track
for MOQT (<xref section="4.3.6" sectionFormat="of" target="PACE"/>), or an application request for
HTTP (<xref target="cancel-over-http"/>).</t>
    </section>
    <section anchor="http-versions">
      <name>HTTP Versions and WebTransport</name>
      <t>The binding works over any HTTP version, but versions differ in how
well they meet the transport requirements of <xref section="2.1" sectionFormat="of" target="PACE"/>,
in particular that dialog control overtakes queued content.</t>
      <dl>
        <dt>HTTP/1.1:</dt>
        <dd>
          <t>A connection carries one request at a time, and an event stream
occupies its connection while it is open. A participant therefore
uses at least two connections: one for its event stream, and one for
its POSTs and application requests. A CANCEL sent on a connection
that is busy with a streamed application response waits behind it,
so a participant <bcp14>SHOULD</bcp14> keep a separate connection available for
control messages. HTTP/1.1 pipelining <bcp14>MUST NOT</bcp14> be used for control
messages.</t>
        </dd>
        <dt>HTTP/2:</dt>
        <dd>
          <t>The event stream, control POSTs, and application requests are
concurrent streams on one connection, so a CANCEL does not wait for
other responses to finish. TCP still delivers all streams in order,
so a lost packet delays every stream on the connection, including
control messages.</t>
        </dd>
        <dt>HTTP/3:</dt>
        <dd>
          <t>Each request is on its own QUIC stream, so a loss on an application
response does not delay control messages on other streams. QUIC also
provides connection migration and 0-RTT (<xref target="early-data"/>). HTTP/3
best meets the low-latency and interruption requirements of
<xref target="PACE"/>, and clients <bcp14>SHOULD</bcp14> prefer it when the dialog host supports
it.</t>
        </dd>
      </dl>
      <section anchor="priority">
        <name>Priority</name>
        <t>Dialog control is meant to overtake queued content
(<xref section="5.3" sectionFormat="of" target="PACE"/>). With the Extensible Prioritization Scheme
<xref target="RFC9218"/>, clients and dialog hosts:</t>
        <ul spacing="normal">
          <li>
            <t><bcp14>SHOULD</bcp14> send control POSTs and event stream requests with urgency 0
(<tt>Priority: u=0</tt>), and <bcp14>SHOULD NOT</bcp14> mark them incremental;</t>
          </li>
          <li>
            <t><bcp14>SHOULD</bcp14> send application requests and responses at urgency 1 or
greater, using lower urgency (higher values) for bulk transfers; and</t>
          </li>
          <li>
            <t><bcp14>SHOULD</bcp14> set the response priority of event streams to urgency 0.</t>
          </li>
        </ul>
        <t>The tiers of <xref section="5.3" sectionFormat="of" target="PACE"/> map onto urgency as follows. Track
resource requests and responses (<xref target="tracks"/>) use the urgency of the
track's tier; for example, the <tt>checkpoint</tt> flow uses Urgent Signals
and therefore urgency 1.</t>
        <table anchor="_table-urgency">
          <name>PACE Priority Tiers and HTTP Urgency</name>
          <thead>
            <tr>
              <th align="left">PACE tier</th>
              <th align="left">Urgency</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Dialog Control</td>
              <td align="left">0</td>
            </tr>
            <tr>
              <td align="left">Urgent Signals</td>
              <td align="left">1</td>
            </tr>
            <tr>
              <td align="left">Real-time Media, Interactive</td>
              <td align="left">2</td>
            </tr>
            <tr>
              <td align="left">Standard Operations</td>
              <td align="left">3</td>
            </tr>
            <tr>
              <td align="left">Discovery</td>
              <td align="left">4</td>
            </tr>
            <tr>
              <td align="left">Background</td>
              <td align="left">5</td>
            </tr>
            <tr>
              <td align="left">Bulk Transfer</td>
              <td align="left">6 or 7</td>
            </tr>
          </tbody>
        </table>
        <t>A server applies priority signals according to its own policy and the
requester's authorization, so a client cannot raise its traffic above
what the server allows. This matches the subscriber-priority model of
the MOQT binding.</t>
      </section>
      <section anchor="webtransport">
        <name>WebTransport and the MOQT Binding</name>
        <t>An application that needs real-time media, independent streams, or
relay fan-out uses the MOQT binding (<xref section="4" sectionFormat="of" target="PACE"/>). The MOQT
binding runs over WebTransport over HTTP/3 <xref target="WEBTRANS-H3"/> or over
native QUIC (<xref section="4.2.1" sectionFormat="of" target="PACE"/>). A WebTransport session is
established with an extended CONNECT request to an HTTP origin, so
the same origin can offer both bindings, and one dialog can use both
(<xref target="interworking"/>).</t>
        <t>The extended CONNECT request that establishes the WebTransport session
<bcp14>SHOULD</bcp14> carry <tt>PACE-Dialog</tt> when the session is opened for one dialog,
so that the origin can authorize and route it.</t>
      </section>
    </section>
    <section anchor="authorization">
      <name>Authorization</name>
      <t>Two questions are answered separately, as in the MOQT binding:</t>
      <table anchor="_table-authz-layers">
        <name>Two Layers of Authorization</name>
        <thead>
          <tr>
            <th align="left">Question</th>
            <th align="left">Who answers it</th>
            <th align="left">How</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">May this HTTP client make this request?</td>
            <td align="left">The dialog host</td>
            <td align="left">HTTP authentication of the client (hop by hop)</td>
          </tr>
          <tr>
            <td align="left">Who sent this control message, and may they?</td>
            <td align="left">Every participant</td>
            <td align="left">
              <tt>credentials</tt> in the control message (end to end)</td>
          </tr>
        </tbody>
      </table>
      <t>The dialog host needs the first to decide what to accept and deliver.
Participants need the second so that they do not have to trust the
dialog host.</t>
      <dl>
        <dt>Authenticating clients:</dt>
        <dd>
          <t>The dialog host authenticates each HTTP client, for example with an
OAuth 2.1 access token <xref target="OAUTH-2.1"/> in the <tt>Authorization</tt> header
field, or with a TLS client certificate. Access tokens <bcp14>SHOULD</bcp14> be
sender-constrained with DPoP <xref target="RFC9449"/>, so that a token read from a
log or intercepted by an HTTP intermediary cannot be used by another
client. This takes the place of relay authorization in the MOQT
binding (<xref section="9.2.2" sectionFormat="of" target="PACE"/>), which binds the same tokens with
DPoP for MOQT <xref target="MoQ-C4M"/>, so a participant that uses both bindings
can use one key.</t>
        </dd>
        <dt>Authenticating senders:</dt>
        <dd>
          <t>Participants authenticate one another, and check authorization and
delegation chains, through the <tt>credentials</tt> member of control
messages (<xref section="7.1" sectionFormat="of" target="PACE"/>, <xref section="9.1" sectionFormat="of" target="PACE"/>). The
dialog host forwards them unchanged and need not understand them.
HTTP authentication identifies a client only to the dialog host, so a
participant <bcp14>MUST NOT</bcp14> treat the dialog host's acceptance of a message
as proof of who sent it, unless the dialog host is itself the
participant checking. A DPoP proof covers one HTTP request and is
not forwarded. HTTP Message Signatures <xref target="RFC9421"/> with
<tt>Content-Digest</tt> <xref target="RFC9530"/> <bcp14>MAY</bcp14> give the dialog host a signature
over a request, but they cover its octets, which the event stream
does not preserve (<xref target="media-types"/>). Neither replaces the
presentations in <tt>credentials</tt>, which bind the control message
itself with <tt>mth</tt> (<xref section="7.1.4" sectionFormat="of" target="PACE"/>).</t>
        </dd>
        <dt>Who may POST what:</dt>
        <dd>
          <t>The dialog host derives each client's permissions from the latest
committed controller context:
</t>
          <table anchor="_table-authz-post">
            <name>What Each Client May POST</name>
            <thead>
              <tr>
                <th align="left">Client</th>
                <th align="left">May POST</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Controller</td>
                <td align="left">Any control message</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>active</tt> participant</td>
                <td align="left">Any control message except OPEN, UPDATE, REVOKE, TERMINATE, STATE, and SEGMENT. The dialog host <bcp14>MUST</bcp14> accept its DECLARE, whatever its <tt>access</tt>.</td>
              </tr>
              <tr>
                <td align="left">Alternate controller</td>
                <td align="left">Also an UPDATE that names itself as controller, to take over (<xref section="3.7.4" sectionFormat="of" target="PACE"/>)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>invited</tt> participant</td>
                <td align="left">ACCEPT, REJECT, and ERROR</td>
              </tr>
              <tr>
                <td align="left">Not in the dialog</td>
                <td align="left">JOIN_REQUEST, if the dialog host's policy allows it, or if it carries a <tt>join_code</tt> (<xref target="join-code"/>) or names a <tt>sponsor</tt> (<xref section="3.4.5" sectionFormat="of" target="PACE"/>)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>left</tt> participant</td>
                <td align="left">JOIN_REQUEST</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>rejected</tt> or <tt>revoked</tt> participant</td>
                <td align="left">Nothing</td>
              </tr>
            </tbody>
          </table>
          <t>The dialog host rejects any other request with 403 (Forbidden), or
<bcp14>MAY</bcp14> respond with 404 (Not Found) to a client that has no
relationship with the dialog, so as not to reveal that it exists. If
it cannot determine authorization, it responds with 503 (Service
Unavailable) and <tt>pace_reason</tt> <tt>authorization-unavailable</tt>.
Participants make the same check themselves, for the sender they
verify (<xref section="7.1.4.3" sectionFormat="of" target="PACE"/>).</t>
        </dd>
        <dt>No list of dialogs:</dt>
        <dd>
          <t>A dialog host <bcp14>MUST NOT</bcp14> offer a resource that lists the dialogs it
hosts to clients that are not authorized to see all of them, just as
the MOQT binding restricts short prefix subscriptions
(<xref section="9.2.2" sectionFormat="of" target="PACE"/>).</t>
        </dd>
      </dl>
      <section anchor="anonymous-authorization">
        <name>Anonymous Authorization</name>
        <t>A hop-by-hop credential identifies the participant to the dialog host,
and links its requests across dialogs. Where the dialog host needs to
know only that a request comes from a member of the dialog, it <bcp14>SHOULD</bcp14>
authorize with holder-bound Privacy Pass tokens <xref target="RFC9576"/> instead,
as the MOQT binding does at relays (<xref section="9.2.3" sectionFormat="of" target="PACE"/>,
<xref section="9.3" sectionFormat="of" target="PACE"/>):</t>
        <ol spacing="normal" type="1"><li>
            <t>The dialog host challenges with the PrivateToken authentication
scheme <xref target="RFC9577"/>. The controller's domain issues membership tokens
to admitted participants, under public metadata derived from the
dialog-id <xref target="PP-AGENTS"/>.</t>
          </li>
          <li>
            <t>The participant presents a holder-bound token with a redemption
proof in the <tt>proof</tt> auth-param <xref target="PP-AGENTS"/>. The proof covers the
method and target URI, and, for a control message, the message
itself with <tt>mth</tt>.</t>
          </li>
          <li>
            <t>Each token is redeemed once. Every request, including each poll of
the event stream, consumes one; a participant that reads the event
stream as one long response uses one per stream.</t>
          </li>
        </ol>
        <t>The dialog host then knows only that the client is a member. It
cannot tell the controller from the others, so operations reserved to
the controller still require the controller's own credential in
<tt>credentials</tt>. Combined with Oblivious HTTP (<xref target="ohttp"/>), the dialog
host learns neither which participant acted nor its network address,
while participants still identify one another through <tt>credentials</tt>.</t>
      </section>
    </section>
    <section anchor="ohttp">
      <name>Oblivious HTTP</name>
      <t>TODO: how Oblivious HTTP <xref target="RFC9458"/> can hide a participant's network
address from the dialog host, where it applies, and where it does not.</t>
    </section>
    <section anchor="asip">
      <name>Relationship to A-SIP</name>
      <t>A-SIP <xref target="ASIP"/> defines a web API between a principal and an agent,
with MOQT for real-time media and offline notification. It has the
shape of the invitee-hosted model of this binding (<xref target="hosting"/>):</t>
      <table anchor="_table-asip">
        <name>A-SIP and the PACE HTTP Binding</name>
        <thead>
          <tr>
            <th align="left">A-SIP</th>
            <th align="left">PACE HTTP binding</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">GET agent URI (capabilities)</td>
            <td align="left">GET Agent Card, which advertises the dialog collection (<xref target="uris"/>)</td>
          </tr>
          <tr>
            <td align="left">POST agent URI (create dialog)</td>
            <td align="left">POST OPEN to the dialog collection (<xref target="opening"/>)</td>
          </tr>
          <tr>
            <td align="left">Dialog context resource</td>
            <td align="left">Dialog snapshot (<xref target="snapshot"/>)</td>
          </tr>
          <tr>
            <td align="left">Log, with catch-up</td>
            <td align="left">Event stream with <tt>Last-Event-ID</tt> (<xref target="resumption"/>)</td>
          </tr>
          <tr>
            <td align="left">Chat over the web API</td>
            <td align="left">The application protocol, or the track resource (<xref target="tracks"/>)</td>
          </tr>
          <tr>
            <td align="left">Voice and video over MOQT, muxed or relayed</td>
            <td align="left">The MOQT binding over WebTransport on the same origin, or through a relay (<xref target="webtransport"/>)</td>
          </tr>
          <tr>
            <td align="left">:pause, :resume</td>
            <td align="left">Idle dialog, and resynchronization with STATE_REQUEST</td>
          </tr>
        </tbody>
      </table>
      <t>An A-SIP dialog is a two-party PACE dialog whose controller is the
principal and whose dialog host is the agent. PACE adds what A-SIP
leaves open:</t>
      <ul spacing="normal">
        <li>
          <t>multi-party dialogs;</t>
        </li>
        <li>
          <t>delegation to further agents, with linked dialogs;</t>
        </li>
        <li>
          <t>cancellation that reports its outcome;</t>
        </li>
        <li>
          <t>controller transfer; and</t>
        </li>
        <li>
          <t>control messages authenticated end to end, which stay verifiable
through dialog hosts and relays.</t>
        </li>
      </ul>
      <t>An A-SIP dialog resource could be represented by PACE dialog context,
so that A-SIP and PACE clients can share a dialog.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations of <xref target="PACE"/> and of HTTP <xref target="RFC9110"/>
apply.</t>
      <section anchor="dialog-host-trust">
        <name>Dialog Host Trust</name>
        <t>A dialog host plays the part of a delivery service: every message of a
dialog passes through it, so participants rely on it to deliver
messages, and it sees who talks to whom and when. This binding does
not rely on it for anything else:</t>
        <table anchor="_table-host-trust">
          <name>What Participants Rely on the Dialog Host For</name>
          <thead>
            <tr>
              <th align="left">Property</th>
              <th align="left">Relies on the dialog host?</th>
              <th align="left">Protection</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Integrity and origin of control messages and checkpoints</td>
              <td align="left">No</td>
              <td align="left">Key-bound presentations, signatures, and generations; changes are detected</td>
            </tr>
            <tr>
              <td align="left">Confidentiality of content</td>
              <td align="left">No, when content is protected end to end</td>
              <td align="left">End-to-end protection of track resource payloads and segment content (<xref section="9.2.1" sectionFormat="of" target="PACE"/>)</td>
            </tr>
            <tr>
              <td align="left">Delivery, timeliness, and ordering</td>
              <td align="left">Yes, within limits</td>
              <td align="left">Generations, sender checks, expiry, and the choice of host (<xref target="hosting"/>)</td>
            </tr>
            <tr>
              <td align="left">Metadata: participants, timing, and volume</td>
              <td align="left">Yes</td>
              <td align="left">Inherent to hosting; Oblivious HTTP hides network addresses (<xref target="ohttp"/>)</td>
            </tr>
          </tbody>
        </table>
        <t>A participant <bcp14>SHOULD</bcp14> treat a dialog host it does not operate as
untrusted, and the rest of this section says what that requires. A
dialog host sees every control message of the dialogs it hosts,
including participant identifiers and credentials. It can delay,
drop, or withhold messages, but it cannot forge or change them without
detection:</t>
        <ul spacing="normal">
          <li>
            <t>participants authenticate the controller and one another through
key-bound presentations whose <tt>mth</tt> covers the message
(<xref section="7.1.4" sectionFormat="of" target="PACE"/>);</t>
          </li>
          <li>
            <t>checkpoints carry their own detached signatures <xref target="PACE-AUTHZ"/>; and</t>
          </li>
          <li>
            <t>participants apply the generation rules to every controller message,
so a dropped, reordered, or replayed UPDATE, REVOKE, or TERMINATE
shows as a gap or a stale generation (<xref section="3.3.3" sectionFormat="of" target="PACE"/>).</t>
          </li>
        </ul>
        <t>Every control message carries a presentation, which a sender may omit
only where every party that forwards it is trusted
(<xref section="7.1.4.3" sectionFormat="of" target="PACE"/>). The dialog host forwards every message,
so a participant that treats it as untrusted does not omit them, and
rejects messages without one. For OPEN and JOIN_REQUEST, which are
sent before the sender has a nonce, the presentation is the
nonce-less form of <xref section="7.1.4.2" sectionFormat="of" target="PACE"/>. The same section of
PACE defines the sender binding, role check, and replay rules that
let participants detect a forged or replayed message, such as a
TERMINATE the controller did not send.</t>
        <t>A participant <bcp14>SHOULD</bcp14> check that each message it sent appears unchanged
on its event stream at the control log position given in the 202
(Accepted) or 201 (Created) response. A receiver discards a message
that fails verification and does not act on it. A participant that
detects a modified, misplaced, or missing message treats the dialog
host as untrusted: it leaves the dialog, or continues through another
dialog host or the MOQT binding (<xref target="interworking"/>). It cannot report
the dialog host through the dialog host itself.</t>
        <t>Some misbehavior cannot be detected from the control log: dropping a
message, reordering messages from participants other than the
controller, and delivering different messages to different
participants. Their effect on dialog state is limited, because only
the controller's messages change it and each carries the complete
context; a participant learns of a dropped message of its own only
when no commit, CANCEL_ACK, or reply follows.</t>
        <t>A dialog host that withholds a REVOKE or TERMINATE can keep a
participant acting on stale state until the dialog expires or the
participant reaches the controller another way. When the dialog host
is untrusted, the controller sets <tt>expires_at</tt>, and participants use
short-lived credentials.</t>
        <t>The visibility rules of <xref target="visibility"/> decide what the dialog host
delivers to each participant, but a dialog host could ignore them.
When the dialog host is untrusted, participants <bcp14>MUST</bcp14> protect the
payloads they publish on the track resource, and the content of
segments, end to end (<xref section="9.2.1" sectionFormat="of" target="PACE"/>), as PACE requires for
MOQT relays that are not trusted with content. The visibility rules
then limit only what each participant learns about the dialog, not
whether it can read content.</t>
        <t><tt>credentials</tt> pass through the dialog host and are visible to every
participant that reads the control log. Participants <bcp14>SHOULD</bcp14> use
credentials bound to a key, with the key-bound presentations of
<xref section="7.1.4" sectionFormat="of" target="PACE"/>, and sender-constrained tokens <xref target="RFC9449"/>,
so that credentials read from the log cannot be replayed. A
credential bound to no key, such as a bearer token, can be replayed by
any reader of the control log.</t>
        <t>In a dialog between parties of conflicting interests (<xref target="DIALOG-UC"/>),
the dialog host is often one of them, such as a brand that hosts
dialogs opened by consumer agents. It can delay or withhold the other
side's messages, such as a DECLARE that raises posture, a REJECT with
<tt>contact_limits</tt>, or a CANCEL, and it learns the timing and metadata
of every exchange. It cannot change what a participant declared, nor
approve on the other principal's behalf <xref target="PACE-AUTHZ"/>. A participant
that cannot accept these risks chooses the host as <xref target="hosting"/>
describes and keeps its own record of what it sent.</t>
      </section>
      <section anchor="json-parsing">
        <name>JSON Parsing</name>
        <t>A dialog host authorizes a message as it parses it, and each
participant parses it again. If the parsers disagree, the dialog host
can admit a message that a participant reads differently. For
example, with a duplicate <tt>sender_id</tt> or <tt>amount</tt> member, one parser
can keep the first value and another the last. A signature over the
JCS form of one reading then verifies for a participant that acts on
another. Requiring I-JSON (<xref target="media-types"/>) at the dialog host and at
every receiver removes the ambiguity. The generation is at most
2^53 - 1 (<xref section="3.10" sectionFormat="of" target="PACE"/>). Amounts, account numbers, and
other values that need exact decimal or 64-bit precision are carried
as strings, as in <xref target="PACE-AUTHZ"/>, because a JSON number can change
value when it is parsed.</t>
      </section>
      <section anchor="early-data">
        <name>Early Data</name>
        <t>TLS 1.3 early data, used by HTTP/1.1 and HTTP/2 over TLS and by HTTP/3
0-RTT, can be replayed. Clients <bcp14>MUST NOT</bcp14> send in early data a control
message that changes state or cancels work (OPEN, ACCEPT, UPDATE,
JOIN_REQUEST, LEAVE, DECLARE, SEGMENT, REVOKE, TERMINATE, CANCEL), a
STATE_REQUEST (<xref section="11" sectionFormat="of" target="PACE"/>), or a join code. A dialog host
that receives such a request in early data <bcp14>MUST NOT</bcp14> process it before
the TLS handshake completes: it either waits for the handshake to
complete or responds with 425 (Too Early) <xref target="RFC8470"/>.</t>
      </section>
      <section anchor="caching">
        <name>Caching</name>
        <t>Control messages, snapshots, event streams, track objects, and
invitations are specific to the requester's authorization. Dialog
hosts <bcp14>MUST</bcp14> mark them as this document specifies so that shared caches
do not store them, and HTTP intermediaries <bcp14>MUST NOT</bcp14> serve a cached
snapshot or event stream to a different client. Responses of a pull
inbox and of a join URI also carry <tt>Cache-Control: no-store</tt>.</t>
      </section>
      <section anchor="resource-exhaustion">
        <name>Resource Exhaustion</name>
        <t>Event streams are long-lived. A dialog host <bcp14>SHOULD</bcp14> limit the number of
concurrent event streams per client and per dialog, the size of
control messages (<xref section="3.10" sectionFormat="of" target="PACE"/>), and the retained control
log, and <bcp14>SHOULD</bcp14> apply rate limits to POSTs per sender. A dialog host
<bcp14>SHOULD NOT</bcp14> retain the control log of a terminated dialog beyond its
retention period (<xref target="termination"/>).</t>
      </section>
      <section anchor="privacy">
        <name>Privacy</name>
        <t>The privacy considerations of <xref section="9.3" sectionFormat="of" target="PACE"/> apply. In this
binding, HTTP intermediaries see request URIs, which contain dialog
URIs, and the <tt>PACE-Dialog</tt> header field. Deployments that need to
limit linkage <bcp14>SHOULD</bcp14> use fresh dialog-ids per dialog, pairwise or
per-dialog participant identifiers, and dialog URIs that do not encode
participant or task information. Access logs that record <tt>PACE-Dialog</tt>
are subject to the same retention limits as other identifiers.</t>
        <t>The dialog host also sees each participant's network address
(<xref target="ohttp"/>).</t>
      </section>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="iana-media-type">
        <name>Media Types</name>
        <t>This document requests registration of the following media types in
the "Media Types" registry.</t>
        <section anchor="applicationpacejson">
          <name>application/pace+json</name>
          <dl>
            <dt>Type name:</dt>
            <dd>
              <t>application</t>
            </dd>
            <dt>Subtype name:</dt>
            <dd>
              <t>pace+json</t>
            </dd>
            <dt>Required parameters:</dt>
            <dd>
              <t>N/A</t>
            </dd>
            <dt>Optional parameters:</dt>
            <dd>
              <t>N/A</t>
            </dd>
            <dt>Encoding considerations:</dt>
            <dd>
              <t>binary (I-JSON <xref target="RFC7493"/>, UTF-8)</t>
            </dd>
            <dt>Security considerations:</dt>
            <dd>
              <t>See the Security Considerations of this document and of <xref target="PACE"/>.</t>
            </dd>
            <dt>Interoperability considerations:</dt>
            <dd>
              <t>Receivers reject duplicate member names. Signatures and hashes over
the content are computed over a JCS <xref target="RFC8785"/> form, not over its
octets (<xref target="media-types"/>).</t>
            </dd>
            <dt>Published specification:</dt>
            <dd>
              <t>This document</t>
            </dd>
            <dt>Applications that use this media type:</dt>
            <dd>
              <t>Agents, tools, and dialog hosts that implement the PACE HTTP binding.</t>
            </dd>
            <dt>Fragment identifier considerations:</dt>
            <dd>
              <t>Same as for <tt>application/json</tt> <xref target="RFC8259"/>.</t>
            </dd>
            <dt>Additional information:</dt>
            <dd>
              <t>Deprecated alias names for this type: N/A. Magic number(s): N/A.
File extension(s): N/A. Macintosh file type code(s): N/A.</t>
            </dd>
            <dt>Person and email address to contact for further information:</dt>
            <dd>
              <t>Suhas Nandakumar <eref target="mailto:snandaku@cisco.com">snandaku@cisco.com</eref></t>
            </dd>
            <dt>Intended usage:</dt>
            <dd>
              <t>COMMON</t>
            </dd>
            <dt>Restrictions on usage:</dt>
            <dd>
              <t>N/A</t>
            </dd>
            <dt>Author:</dt>
            <dd>
              <t>Suhas Nandakumar</t>
            </dd>
            <dt>Change controller:</dt>
            <dd>
              <t>IETF</t>
            </dd>
          </dl>
        </section>
        <section anchor="applicationpace-invitationjson">
          <name>application/pace-invitation+json</name>
          <t>Registered with the same template as <tt>application/pace+json</tt>, except:</t>
          <dl>
            <dt>Subtype name:</dt>
            <dd>
              <t>pace-invitation+json</t>
            </dd>
            <dt>Applications that use this media type:</dt>
            <dd>
              <t>Agents and dialog hosts that deliver PACE invitations over HTTP.</t>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="iana-fields">
        <name>HTTP Field Names</name>
        <t>This document requests registration of the following fields in the
"Hypertext Transfer Protocol (HTTP) Field Name Registry":</t>
        <table>
          <name>HTTP Field Name Registrations</name>
          <thead>
            <tr>
              <th align="left">Field Name</th>
              <th align="left">Status</th>
              <th align="left">Structured Type</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">PACE-Dialog</td>
              <td align="left">permanent</td>
              <td align="left">Dictionary</td>
              <td align="left">
                <xref target="pace-dialog-header"/> of this document</td>
            </tr>
            <tr>
              <td align="left">PACE-Log-Position</td>
              <td align="left">permanent</td>
              <td align="left">Item</td>
              <td align="left">
                <xref target="sending"/> of this document</td>
            </tr>
            <tr>
              <td align="left">PACE-Track</td>
              <td align="left">permanent</td>
              <td align="left">Dictionary</td>
              <td align="left">
                <xref target="tracks"/> of this document</td>
            </tr>
          </tbody>
        </table>
        <t><tt>PACE-Log-Position</tt> is an Item Structured Field whose value is an
Integer: the control log position of the entry that the response
concerns.</t>
      </section>
      <section anchor="iana-link">
        <name>Link Relation Types</name>
        <t>This document requests registration of the following entries in the
"Link Relation Types" registry <xref target="RFC8288"/>:</t>
        <dl>
          <dt>Relation Name:</dt>
          <dd>
            <t>pace-tracks</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Refers to the track resource of a PACE dialog.</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t><xref target="tracks"/> of this document</t>
          </dd>
          <dt>Relation Name:</dt>
          <dd>
            <t>pace-join</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Refers to the resource at which a PACE join code is resolved to a
dialog.</t>
          </dd>
          <dt>Reference:</dt>
          <dd>
            <t><xref target="join-code"/> of this document</t>
          </dd>
        </dl>
      </section>
      <section anchor="problem-types">
        <name>Problem Types</name>
        <t>This document requests that IANA create a "PACE Problem Types"
registry in the "Protocol for Agent Communication Exchange (PACE)"
group, with the Specification Required policy. It has one entry for
each ERROR reason of <xref section="3.8.1" sectionFormat="of" target="PACE"/>, with the reason, a
title, and a reference. The problem type URI of an entry has the form
<tt>https://iana.org/assignments/pace/errors#{reason}</tt>.</t>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t>JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t>This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <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="RFC9111">
          <front>
            <title>HTTP Caching</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.</t>
              <t>This document obsoletes RFC 7234.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="98"/>
          <seriesInfo name="RFC" value="9111"/>
          <seriesInfo name="DOI" value="10.17487/RFC9111"/>
        </reference>
        <reference anchor="RFC9218">
          <front>
            <title>Extensible Prioritization Scheme for HTTP</title>
            <author fullname="K. Oku" initials="K." surname="Oku"/>
            <author fullname="L. Pardue" initials="L." surname="Pardue"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>This document describes a scheme that allows an HTTP client to communicate its preferences for how the upstream server prioritizes responses to its requests, and also allows a server to hint to a downstream intermediary how its responses should be prioritized when they are forwarded. This document defines the Priority header field for communicating the initial priority in an HTTP version-independent manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing responses. These share a common format structure that is designed to provide future extensibility.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9218"/>
          <seriesInfo name="DOI" value="10.17487/RFC9218"/>
        </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>
        <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="RFC8470">
          <front>
            <title>Using Early Data in HTTP</title>
            <author fullname="M. Thomson" initials="M." surname="Thomson"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="W. Tarreau" initials="W." surname="Tarreau"/>
            <date month="September" year="2018"/>
            <abstract>
              <t>Using TLS early data creates an exposure to the possibility of a replay attack. This document defines mechanisms that allow clients to communicate with servers about HTTP requests that are sent in early data. Techniques are described that use these mechanisms to mitigate the risk of replay.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8470"/>
          <seriesInfo name="DOI" value="10.17487/RFC8470"/>
        </reference>
        <reference anchor="RFC4648">
          <front>
            <title>The Base16, Base32, and Base64 Data Encodings</title>
            <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
            <date month="October" year="2006"/>
            <abstract>
              <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4648"/>
          <seriesInfo name="DOI" value="10.17487/RFC4648"/>
        </reference>
        <reference anchor="RFC8288">
          <front>
            <title>Web Linking</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="October" year="2017"/>
            <abstract>
              <t>This specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types").</t>
              <t>It also defines the serialisation of such links in HTTP headers with the Link header field.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8288"/>
          <seriesInfo name="DOI" value="10.17487/RFC8288"/>
        </reference>
        <reference anchor="RFC7493">
          <front>
            <title>The I-JSON Message Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="March" year="2015"/>
            <abstract>
              <t>I-JSON (short for "Internet JSON") is a restricted profile of JSON designed to maximize interoperability and increase confidence that software can process it successfully with predictable results.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7493"/>
          <seriesInfo name="DOI" value="10.17487/RFC7493"/>
        </reference>
        <reference anchor="RFC8785">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author fullname="A. Rundgren" initials="A." surname="Rundgren"/>
            <author fullname="B. Jordan" initials="B." surname="Jordan"/>
            <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>Cryptographic operations like hashing and signing need the data to be expressed in an invariant format so that the operations are reliably repeatable. One way to address this is to create a canonical representation of the data. Canonicalization also permits data to be exchanged in its original form on the "wire" while cryptographic operations performed on the canonicalized counterpart of the data in the producer and consumer endpoints generate consistent results.</t>
              <t>This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>
        <reference anchor="PACE">
          <front>
            <title>PACE: Protocol for Agent Communication Exchange</title>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Cullen Fluffy Jennings" initials="C. F." surname="Jennings">
              <organization>Cisco Systems</organization>
            </author>
            <date day="16" month="November" year="2026"/>
            <abstract>
              <t>   This document defines the Protocol for Agent Communication Exchange
   (PACE), an agentic dialog management protocol with a binding to Media
   over QUIC Transport (MOQT).  A dialog is the correlated sequence of
   interactions between two or more participants over the course of a
   task.  PACE defines a transport-independent dialog context and
   control operations to establish, modify, and terminate dialogs and to
   revoke propagation relationships.  It specifies how that context
   stays coherent across intermediaries, trust boundaries, modality
   changes, and interruptions, and how it is carried over MOQT.  PACE
   does not interpret or define dialog content.  Over MOQT, a dialog can
   combine text, audio, video, and request/response exchanges in point-
   to-point, point-to-multipoint, and multi-party topologies.
   Application-layer agent protocols such as A2A, MCP, and AutoGen keep
   their own message formats and carry the dialog context through their
   own extension points.  Delegation between agents and approval of
   individual agent actions are specified in a companion document.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nandakumar-agentproto-pace-01"/>
        </reference>
        <reference anchor="SSE" target="https://html.spec.whatwg.org/multipage/server-sent-events.html">
          <front>
            <title>HTML Living Standard: Server-sent events</title>
            <author>
              <organization>WHATWG</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="DIALOG-UC">
          <front>
            <title>Agentic Dialog Use Cases</title>
            <author initials="F." surname="Siyavud">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
        </reference>
        <reference anchor="RFC6585">
          <front>
            <title>Additional HTTP Status Codes</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <date month="April" year="2012"/>
            <abstract>
              <t>This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety of common situations. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6585"/>
          <seriesInfo name="DOI" value="10.17487/RFC6585"/>
        </reference>
        <reference anchor="OAUTH-2.1">
          <front>
            <title>The OAuth 2.1 Authorization Framework</title>
            <author fullname="Dick Hardt" initials="D." surname="Hardt">
              <organization>Hellō</organization>
            </author>
            <author fullname="Aaron Parecki" initials="A." surname="Parecki">
              <organization>Okta</organization>
            </author>
            <author fullname="Torsten Lodderstedt" initials="T." surname="Lodderstedt">
              <organization>SPRIND</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   The OAuth 2.1 authorization framework enables an application to
   obtain limited access to a protected resource, either on behalf of a
   resource owner by orchestrating an approval interaction between the
   resource owner and an authorization service, or by allowing the
   application to obtain access on its own behalf.  This specification
   replaces and obsoletes the OAuth 2.0 Authorization Framework
   described in RFC 6749 and the Bearer Token Usage in RFC 6750.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-v2-1-17"/>
        </reference>
        <reference anchor="RFC7240">
          <front>
            <title>Prefer Header for HTTP</title>
            <author fullname="J. Snell" initials="J." surname="Snell"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>This specification defines an HTTP header field that can be used by a client to request that certain behaviors be employed by a server while processing a request.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7240"/>
          <seriesInfo name="DOI" value="10.17487/RFC7240"/>
        </reference>
        <reference anchor="RFC8820">
          <front>
            <title>URI Design and Ownership</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="June" year="2020"/>
            <abstract>
              <t>Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of substructure in URIs is often problematic.</t>
              <t>This document provides guidance on the specification of URI substructure in standards.</t>
              <t>This document obsoletes RFC 7320 and updates RFC 3986.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="190"/>
          <seriesInfo name="RFC" value="8820"/>
          <seriesInfo name="DOI" value="10.17487/RFC8820"/>
        </reference>
        <reference anchor="RFC9112">
          <front>
            <title>HTTP/1.1</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 specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns.</t>
              <t>This document obsoletes portions of RFC 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="99"/>
          <seriesInfo name="RFC" value="9112"/>
          <seriesInfo name="DOI" value="10.17487/RFC9112"/>
        </reference>
        <reference anchor="RFC9113">
          <front>
            <title>HTTP/2</title>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <author fullname="C. Benfield" initials="C." role="editor" surname="Benfield"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced latency by introducing field compression and allowing multiple concurrent exchanges on the same connection.</t>
              <t>This document obsoletes RFCs 7540 and 8740.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9113"/>
          <seriesInfo name="DOI" value="10.17487/RFC9113"/>
        </reference>
        <reference anchor="RFC9114">
          <front>
            <title>HTTP/3</title>
            <author fullname="M. Bishop" initials="M." role="editor" surname="Bishop"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9114"/>
          <seriesInfo name="DOI" value="10.17487/RFC9114"/>
        </reference>
        <reference anchor="RFC9421">
          <front>
            <title>HTTP Message Signatures</title>
            <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/>
            <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
            <author fullname="M. Sporny" initials="M." surname="Sporny"/>
            <date month="February" year="2024"/>
            <abstract>
              <t>This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9421"/>
          <seriesInfo name="DOI" value="10.17487/RFC9421"/>
        </reference>
        <reference anchor="RFC9530">
          <front>
            <title>Digest Fields</title>
            <author fullname="R. Polli" initials="R." surname="Polli"/>
            <author fullname="L. Pardue" initials="L." surname="Pardue"/>
            <date month="February" year="2024"/>
            <abstract>
              <t>This document defines HTTP fields that support integrity digests. The Content-Digest field can be used for the integrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digest and Want-Repr-Digest can be used to indicate a sender's interest and preferences for receiving the respective Integrity fields.</t>
              <t>This document obsoletes RFC 3230 and the Digest and Want-Digest HTTP fields.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9530"/>
          <seriesInfo name="DOI" value="10.17487/RFC9530"/>
        </reference>
        <reference anchor="RFC9449">
          <front>
            <title>OAuth 2.0 Demonstrating Proof of Possession (DPoP)</title>
            <author fullname="D. Fett" initials="D." surname="Fett"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="D. Waite" initials="D." surname="Waite"/>
            <date month="September" year="2023"/>
            <abstract>
              <t>This document describes a mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level. This mechanism allows for the detection of replay attacks with access and refresh tokens.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9449"/>
          <seriesInfo name="DOI" value="10.17487/RFC9449"/>
        </reference>
        <reference anchor="RFC9458">
          <front>
            <title>Oblivious HTTP</title>
            <author fullname="M. Thomson" initials="M." surname="Thomson"/>
            <author fullname="C. A. Wood" initials="C. A." surname="Wood"/>
            <date month="January" year="2024"/>
            <abstract>
              <t>This document describes Oblivious HTTP, a protocol for forwarding encrypted HTTP messages. Oblivious HTTP allows a client to make multiple requests to an origin server without that server being able to link those requests to the client or to identify the requests as having come from the same client, while placing only limited trust in the nodes used to forward the messages.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9458"/>
          <seriesInfo name="DOI" value="10.17487/RFC9458"/>
        </reference>
        <reference anchor="RFC9576">
          <front>
            <title>The Privacy Pass Architecture</title>
            <author fullname="A. Davidson" initials="A." surname="Davidson"/>
            <author fullname="J. Iyengar" initials="J." surname="Iyengar"/>
            <author fullname="C. A. Wood" initials="C. A." surname="Wood"/>
            <date month="June" year="2024"/>
            <abstract>
              <t>This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recommendations for each deployment model, to help ensure that the desired security and privacy goals are fulfilled.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9576"/>
          <seriesInfo name="DOI" value="10.17487/RFC9576"/>
        </reference>
        <reference anchor="RFC9577">
          <front>
            <title>The Privacy Pass HTTP Authentication Scheme</title>
            <author fullname="T. Pauly" initials="T." surname="Pauly"/>
            <author fullname="S. Valdez" initials="S." surname="Valdez"/>
            <author fullname="C. A. Wood" initials="C. A." surname="Wood"/>
            <date month="June" year="2024"/>
            <abstract>
              <t>This document defines an HTTP authentication scheme for Privacy Pass, a privacy-preserving authentication mechanism used for authorization. The authentication scheme specified in this document can be used by Clients to redeem Privacy Pass tokens with an Origin. It can also be used by Origins to challenge Clients to present Privacy Pass tokens.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9577"/>
          <seriesInfo name="DOI" value="10.17487/RFC9577"/>
        </reference>
        <reference anchor="PP-AGENTS" target="https://datatracker.ietf.org/doc/draft-nandakumar-privacypass-delegated-agents/">
          <front>
            <title>Privacy Pass for Delegated Agents: Delegation Attestation and Holder-Bound Tokens</title>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <author initials="C." surname="Jennings">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nandakumar-privacypass-delegated-agents-00"/>
        </reference>
        <reference anchor="ASIP">
          <front>
            <title>The Agentic Session Initiation Protocol (A-SIP)</title>
            <author fullname="Jonathan Rosenberg" initials="J." surname="Rosenberg">
              <organization>jdrosen.net</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   The Agentic Session Initiation Protocol (A-SIP) is used for the
   establishment and lifecycle maintenance of agentic dialogs.  It also
   enables and content exchange between a principal and an AI Agent over
   the Internet.  A-SIP can be used between a user agent and AI Agent,
   between AI Agents, or between an AI Agent and a tool with agentic-
   like properties.  A-SIP is built ontop of HTTP/3, web transport and
   Media Over Quic Transport (MOQT), leveraging a modern, public-cloud
   friendly protocol stack.  Its usage of MOQT is optional, needed only
   when real-time media is exchanged.  This allows asynchronous agent
   interactions to be done entirely using HTTP/3, so simple cases remain
   simple.  Despite the name, A-SIP has no technical relationship with
   SIP (RFC3261).  This document is not yet a fully fleshed out
   protocol, and is meant to solicit feedback on this general direction
   of work.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-rosenberg-agentproto-asip-00"/>
        </reference>
        <reference anchor="MoQ-C4M">
          <front>
            <title>Authorization scheme for MOQT using Common Access Tokens</title>
            <author fullname="Chris Lemmons" initials="C." surname="Lemmons">
              <organization>Comcast</organization>
            </author>
            <author fullname="Gwendal Simon" initials="G." surname="Simon">
              <organization>Synamedia</organization>
            </author>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Will Law" initials="W." surname="Law">
              <organization>Akamai</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   A token-based authorization scheme for use with Media Over QUIC
   Transport.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-c4m-02"/>
        </reference>
        <reference anchor="MoQ-TRANSPORT" target="https://datatracker.ietf.org/doc/draft-ietf-moq-transport/">
          <front>
            <title>Media over QUIC Transport</title>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <author initials="V." surname="Vasiliev">
              <organization/>
            </author>
            <author initials="I." surname="Swett" role="editor">
              <organization/>
            </author>
            <author initials="A." surname="Frindell" role="editor">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-transport-23"/>
        </reference>
        <reference anchor="WEBTRANS-H3">
          <front>
            <title>WebTransport over HTTP/3</title>
            <author fullname="Alan Frindell" initials="A." surname="Frindell">
              <organization>Meta</organization>
            </author>
            <author fullname="Eric Kinnear" initials="E." surname="Kinnear">
              <organization>Apple Inc.</organization>
            </author>
            <author fullname="Victor Vasiliev" initials="V." surname="Vasiliev">
              <organization>Google</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   WebTransport over HTTP/3 is a binding of the WebTransport protocol
   framework [OVERVIEW] to HTTP/3 [HTTP3].  It provides support for
   unidirectional streams, bidirectional streams, and datagrams, all
   multiplexed within the same HTTP/3 connection.  WebTransport enables
   application clients constrained by the Web security model to
   communicate with a remote application server using a secure
   multiplexed transport.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-webtrans-http3-17"/>
        </reference>
        <reference anchor="A2A" target="https://a2a-protocol.org/latest/">
          <front>
            <title>Agent-to-Agent Protocol Specification</title>
            <author>
              <organization>Linux Foundation</organization>
            </author>
            <date year="2025"/>
          </front>
          <seriesInfo name="Version" value="1.0"/>
        </reference>
        <reference anchor="MCP" target="https://modelcontextprotocol.io/specification/2026-07-28">
          <front>
            <title>Model Context Protocol Specification</title>
            <author>
              <organization>Linux Foundation</organization>
            </author>
            <date year="2026" month="July"/>
          </front>
          <seriesInfo name="Version" value="2026-07-28"/>
        </reference>
        <reference anchor="PACE-AUTHZ" target="https://datatracker.ietf.org/doc/draft-nandakumar-agentproto-pace-authz/">
          <front>
            <title>PACE Authorization: Delegation and Action Approval</title>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <author initials="C." surname="Jennings">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nandakumar-agentproto-pace-authz-00"/>
        </reference>
        <reference anchor="WPT-MSG" target="https://datatracker.ietf.org/doc/draft-nandakumar-wimse-wpt-message-binding/">
          <front>
            <title>Message Binding for Workload Proof Tokens</title>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <author initials="C." surname="Jennings">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nandakumar-wimse-wpt-message-binding-00"/>
        </reference>
      </references>
    </references>
    <?line 2118?>

<section anchor="examples">
      <name>Example Flows</name>
      <t>The examples below use the conventions of the examples in <xref target="PACE"/>.
<tt>D</tt> is the dialog-id <tt>550e8400-e29b-41d4-a716-446655440000</tt>, <tt>{D}</tt> in
a URI is that dialog-id, and control messages are abbreviated to their
type and key members. HTTP authentication fields are omitted.</t>
      <section anchor="delegating-a-task-with-a2a">
        <name>Delegating a Task with A2A</name>
        <t>Agent A (controller) delegates a task to Agent B over A2A. B hosts the
dialog (invitee-hosted).</t>
        <artwork><![CDATA[
 A (controller)                                   B (dialog host)
  |                                                       |
  |-- POST /pace/dialogs  OPEN gen 0 (B invited) -------->|
  |<- 201 Location: /pace/dialogs/{D}, text/event-stream -|
  |<========= SSE id:1 OPEN ==============================|
  |                               B appends ACCEPT        |
  |<========= SSE id:2 ACCEPT ============================|
  |-- POST /pace/dialogs/{D}  UPDATE gen 1 (B active) --->|
  |<- 202 PACE-Log-Position: 3 ---------------------------|
  |<========= SSE id:3 UPDATE ============================|
  |                                                       |
  |-- POST /a2a  SendMessage  PACE-Dialog: id=D, gen=1 -->|
  |<- 200 text/event-stream (A2A task updates) -----------|
  |                                                       |
  |-- POST /pace/dialogs/{D}  TERMINATE gen 2 ----------->|
  |<- 202 ------------------------------------------------|
  |<========= SSE id:4 TERMINATE, stream ends ============|
]]></artwork>
        <t>The A2A request and its streamed response use A2A's own HTTP
transport. The PACE control messages use the dialog URI. Both carry
the same dialog-id.</t>
      </section>
      <section anchor="calling-an-mcp-tool-from-a-hub-hosted-dialog">
        <name>Calling an MCP Tool from a Hub-hosted Dialog</name>
        <t>Agent A opens a dialog on a hub, H, and adds an MCP tool server,
<tt>fs-tool</tt>, which receives invitations in a push inbox.</t>
        <ol spacing="normal" type="1"><li>
            <t>A POSTs OPEN (gen 0, <tt>fs-tool</tt> invited) to H's dialog collection.
H responds 201 with the dialog URI.</t>
          </li>
          <li>
            <t>H POSTs an invitation to <tt>fs-tool</tt>'s inbox:
<tt>{"dialog_id":"550e...","controller_id":"agent-a",
"invitee_id":"fs-tool","dialog_uri":"https://hub.example/pace/dialogs/550e..."}</tt>.</t>
          </li>
          <li>
            <t><tt>fs-tool</tt> GETs the dialog URI as an event stream, reads OPEN, and
POSTs ACCEPT. A POSTs UPDATE (gen 1, <tt>fs-tool</tt> active).</t>
          </li>
          <li>
            <t>A sends an MCP <tt>tools/call</tt> to <tt>fs-tool</tt> over Streamable HTTP, with
<tt>PACE-Dialog: id="550e...", gen=1</tt> and the dialog reference in
<tt>_meta</tt>. <tt>fs-tool</tt> checks on its event stream that A is an
<tt>active</tt> participant, and answers.</t>
          </li>
        </ol>
      </section>
      <section anchor="interrupting-a-long-running-call">
        <name>Interrupting a Long-Running Call</name>
        <t>A has a streamed MCP call <tt>g1</tt> in progress at <tt>code-tool</tt> over HTTP/3
when its user cuts in.</t>
        <ol spacing="normal" type="1"><li>
            <t>A POSTs CANCEL to the dialog URI with <tt>Priority: u=0</tt>, scope
<tt>operation</tt>, and target
<tt>{"protocol":"mcp","request_id":"g1"}</tt>. On HTTP/3, the request is on
its own QUIC stream, so it is not delayed by the streamed MCP
response or by a loss on it.</t>
          </li>
          <li>
            <t>The dialog host appends CANCEL and delivers it on <tt>code-tool</tt>'s
event stream, which <tt>code-tool</tt> holds at urgency 0.</t>
          </li>
          <li>
            <t><tt>code-tool</tt> applies the CANCEL as MCP <tt>notifications/cancelled</tt>,
ends the MCP response with a JSON-RPC error, and POSTs CANCEL_ACK
with outcome <tt>stopped</tt>.</t>
          </li>
        </ol>
        <t>Resetting the HTTP/3 stream of the MCP response would not have
cancelled the work (<xref target="cancel-over-http"/>).</t>
      </section>
      <section anchor="recovering-after-a-lost-connection">
        <name>Recovering after a Lost Connection</name>
        <t>B's network changes while it is a participant in <tt>D</tt>. Its last
processed event was control log position 7, and its last accepted
generation is 3.</t>
        <ol spacing="normal" type="1"><li>
            <t>B reconnects and GETs the dialog URI with
<tt>Accept: text/event-stream</tt> and <tt>Last-Event-ID: 7</tt>. The dialog host
resumes with entries 8 and 9: an UPDATE (gen 4) adding Agent C, and
C's ACCEPT.</t>
          </li>
          <li>
            <t>B POSTs STATE_REQUEST with <tt>last_accepted_generation</tt> 3 and a
nonce. The controller POSTs STATE (gen 4), which B receives on the
stream, authenticates, and applies.</t>
          </li>
          <li>
            <t>B uses A2A <tt>GetTask</tt> to learn whether the task it was working on
received new input while it was away, and does not infer that from
the control log.</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIACF0+2oAA9y93XIbSZYmeO9PEUtdpNQFQCJFKSWqsrqZFDNTWfphiVTl
1LT1JAJAkIwSEIGKAEihKbWtzfVe9Jp127SN7ZqN2fblXu4T7KP0k+z5dT/u
EWAqq6prZlbWXUkAER4e/nP8/HznO8Ph0K3K1bw4yHZODo+Os6/LalZWF1l9
VTTZd2dnJzsun0ya4kovwO/0qh03zVfFRd1sDrJ2NXNuVk+rfAGNzZr8fDWs
8mqWv18v8maYXxTVatnUq3q4zKfF8HK1Wg4fPHDterIo27asq9VmCTe+OD77
xlXrxaRoDty0rtqiatftQbZq1oWDTjx0eVPk0JnD5XJewuPhzjaD52Rvi3w+
PCsXxY67rpv3F029XuJ1+ODsqF4s1pVcn51gP6b1vN1x74sNXD07cNkwoz4O
oYf0R/TNqq7n+AW+Pf738AX/1uKHWZnP64tskVfw3QJvdVdFtS6g0ewzu5Fl
/Po7P0DXcfy/xfvw+0VezuH7MH5/Uxar81HdXOCveTO9hF9xNNuD+/fxYvyq
vCpGetl9/OL+pKmv2+J+aOY+3n5Rri7XE2igXV/m7XdFU9z/rJnDe+cw9e3K
PNy3MeJmR2X9ea193lWjy9VivuNcvl5d1g1OGHQiy3i97Zziw7PXvokd+hFe
P6/Kv6fhhouOynZa8y+FjGsrT/2bKf42mtaLnaTlo/V8XlTZ90VVwcS02xvO
Tjftqli08QPO5+vz841t3lV1s4A7r2iBvP3maG9396n8+WT3y339c++Rfvt0
d/dB+HNX/9zbfaJ/7j/6Uv98/EgveLL/pd62/3j/iW/3if755f7Th/rtl08e
4Z+4x2EXDp+Ptk8HXHZ6enxAr6nC47uzVy+zl+UVrt3TFd4Kmyo7LRqQI8MW
135xhfuFB8fPIfwb4mAeZD98d3j2w7fcZt5cFLCydGHhxI/aZTEdXV/mq+sL
WtWL9XxVLqFn99vwkCE/hJaKc2V1bkf6+YvDl2++Hb47intOO7OcZs95F79r
i+wobwvp6QxW+UG292Dv8XB3t6fvZQXC6ZtRdlpu8qv1jAfz8SMezDeH786+
G+6NdnlEcUcOa7x/eLU33JU52NvXSXryZM9M817482H4c9/P+J5fB48e+tv2
95+GJeFXx6MvH4c/aaGcnAwPvz1+fXYaj8VJU17l0012krdtBoOXPS/mxQUM
wSyjYYJ3lW9Qfh2uUALw3yiBv6vnM5iIr+s1fDir34Po/hmDeDoy29f+cDTy
m4++hvkuixYnl+/PshfVqmiqYjV8joKk5/RZ8nst4bWGM30lXtYtnkJ9qw46
na+afPq+aIIshQOuK61ua/0+tH14+uKEV0BTwyqFo+3Cbqm8LZdw1av6N8Oj
/VdmqSzqPwyn+wv57ezt4evTkzdvz+Ipe1XA8cPH9W/evTjKzpq8apd1s/pz
DP1vR9lvoXvzsriyX7+A9X5drFYy/E2NPYF+rOro7sNR9k0DmkIxn2+78nPn
0o/HSl9vuPfwj5m2bkM4Qz8cf03DO/zuoRn/62JCV9Hxg0873DvskR2oH/Dx
rgd6dgrCqjyXcz6ZiEfbJODLslp/yL7B3UP3bRmg3xZNy6fO7ujBTu8Y5Hv5
cCl9offnsxrf9NXRSbJ+apgfUExg2D985hs8Hj748s/1EtLccO9J75sssHdT
7px/I9ArWtu9+1EjeIINUfD+x0S2ofZ6SD32B7cRZijADqcs15bwqKt8/j+I
8EqVIXz83//pUqu3WdoMJ2fDV6ffpmKmbeEObx/g4YC66rzOZ7hq6vP/sST+
dbloi+H1cjVccM+HE+75nz5wW5u+79xwCEbDpMWGwAo4uyzbDNpYo1GQyZot
2uyyvs5Wl0XXcMhgGPEHvw1hmF2f6XD8YXqZVzAfd3FZ38vgOdO8gVGaBctt
lL1YQdvLlrYEGlMrkL9ZvSwaMZvgm5oNuqZo63UzLdpBtihgombwB+6IvGK9
Dcw7MLsWA4dfzorzsoLXyLPLIocTP4OXms+g4/kK1gv+EGwzaPkPa5A9bQaP
yuWNRzAyRSajlq1B2eJetKA0oy6GPZtvBllbZ+UqQ2uuDa91f3e0O3D01x53
kv5+OAr2FHcln0OXZ5usWVfhbmh0Pb3MwFYAYU5vAxJxkP2+Livfvewa7Jd6
vcp4jKnrMCtlk/lDA/rTOJn+dpQdwhOW+Lr5PKNF5AdUpqXVpkmWwXhSD6va
2aFSAaf3hL7mVmxBt4rp+yX0GDTdDEbS+SWWz2HIZkU7bcoJPPP6Eqyx7M1k
Dnp5vZZBnsKcXpazAl53mTcw2qBFV6svWgfbCYc6y2cz6D3of029sMv0sm5X
POC6fnUGm4IOGBgndzgEZWfEG2FRzmbzwrk7uF2berYm8eocSeKbG/zPp08w
6dANuj0XTby7LXxX/AQ4GkAd3HKFi73tuVPH1N29uTktWL4/xG3GT7/nF7N5
UTlvsrswStAhWN3NwEHfZN/AtICoKAaZ7Kg5/EzDYoazvQdXlR9WBViOcpkL
G48vxyc263khy9XeTb+XKOMWqN7RO57Dk+prB3Na4a0bfDWwf6An1JJ0ehQG
lhYDTpE+QJcXTNNWrTG7++rNb87uQSuRzvnpE8zpK1gAMF7Leb0BOUOz5Rtt
4202wu0FjcD/Qk9oh39/+ub18O3JkfMX0T5TG/EUWzsm840OFxY4sLp4sGCX
Yp+OTqQ5V8J1p3RNPpkX3J5fHbQtwJAzu8sMOjlx4DRpcngILMo1bBLY/rDI
vAReZHfpZJvk87yagrIyyA5PXmQ42tf5Bj41IBabtnDw/h9oq5K0jLYp26W4
EqoCxqu7NmlWZjW8TFWvSFCWDW7LqriOX8WeImG9ws2yAWFufsChLGl/RuIX
zjhe27TptA+k80VSDlqhIWU5vAIRduDcX2WHekvYCvxk6BJchSOfT8GqUdlS
VxVvMhgR9pVlV6zqwRfxgpYh65F/7Qie/KYqdDxXZMKb7cZ3ZmFLDusGziE/
yPBU2Q50hsQ766IpCjhfQDjW+BZlZbc+Ngw7DL5pYDShHXrPcj6H18ROYM+O
cEXM5yILYCHUU/mbFhi8YlmJTtlmxQd8PzjFfM+sGEDjaFlUMzn69ckwh3Iq
09kJZ40ZWWjiEkYNVC08lyYFNlhhv94WU9xamwz0FWwkm+N+DTcOsskGz6U1
7qr0ZB85OpMTCYgvpHqDnnZZDou0+ADjMd/A0IFFi11XqTNKlB44TFo457Ku
9jFIW4b/otsXfoCzlURsSyqMrng9dYoPJUwJ+qgr6U2P6gPLx+nLwKuCyIB7
oWN6ZKksQGkXvlzRd22+gKvLRYGHBi3aa/bKwnkB43TnTnY6hffYrt+pkAlq
FW8aPEG9loGN+9+h5QHdBvrakt7tvGfIWGFD8YQ3h+/p7mRCRboUcPbDmHZm
ERugy4d8OTVRVlflSh5Fr+4/8hO6+p77LH0PGxPFR7saq0vOq0twJX3TSofC
4PNpkc5ZzxQFQV+cn8PSx7Gk2VBJhA+h+IN+gTe5RE3CAcaLfIOk2eDX6K/h
lfA80umCugYSFT6xlAUJu1zDJ4wgwFKcz0XwkRyEN2ydrt7JhjrdqxEmA1h8
mBbLFZ2TcItTpRJeNE/1TzugnbMEzh7YnCvHWwxuyudDXPjcu+g416lkxRUO
NNS6vAJG1/PJTrMD5j+dFLKZOocIb6O3fOQt6NB/CafQGpYmC6L3oOBgYKYF
0/Pd6dnOgP+bvX5Df789BrXl7fFz/Pv0u8OXL/0fTq44/e7Nu5fPw1/hzqM3
r14dv37ON8O3WfSV23l1+LsdnqOdNydnL968Pny5w8dEJNhA7rD8peW3bAr0
kuatU/UbFbjs66OT//e/7e6DePxfxNEP+gt/QFc/fEB9jp+GNo98RP0OTYMi
b7AVWDUw0kvYjLR64EgCWQhaPMZa4JT+WxyZvzvIfjmZLnf3fyVf4AtHX+qY
RV/SmHW/6dzMg9jzVc9j/GhG3ycjHff38HfRZx138+Uv/3qOS3S4++Svf+Vo
9ZzRSVvDwtqkopgUTrIX4Bo1CwbJ6aafh+Vs4IyOMIBtV1b491xEYpEo+0aR
2Wgrjs0jVcpZFLKS0F6Wy0F2Dtr7IKN+4GxjR5Z1W6qiwFtwBnqpC5bK7sjY
KnQY+jdjhZdebzovWfyQwonHZwn6nNOPcW9VMHAvmgIWLkZO8qQfGfVDYk/4
7B/IlqQxva5hv+fknsHe7dgH7MBAreFwmJBUOofuzgbJzmlBgRZ3XHwnSLMd
0c3N10HO4ggfuIPs0PYy2z5aVXTkD1BelTR4oELR8PFAybiFI7r1B9cXbTjC
D/D+90Wx1Cb8JXq28txOUTR3D1y2Ya0qOsD4LblT5Iwmu6OOj3FWgUoS0yxP
WazDe3Z13XU1R8Od35PMP7UMRW/Gg68m5YkPsKPQcxxYFLyqSbd4jlf8pM67
sKsndg2AVoreOn5/aAAPp+DwsY/y654mE5Szqi0veDZXxYXORNp83uJVpFcU
OZyzZtThsTBiuLpBbWxWosrtihU9hXFs8Ts4YEFlzEBt4stpaOl9dUpNm3wz
7zVSmpd8IqPbhQ7aeJ7gZtbn5EI6bWXmipK1en2dYLfArLKijq/gpYE4AeVq
0Z+882K0u2v8FwM4MUoYDX4NvypVJ+nZBaZZHIVSdOh68nt4AqqYWY5whI4W
gZISD/ihaEVhX757+0JXD/yZdN83UVfplPKYiRDW67jlF9Wk/iDLI9KkcWL5
jdHQJRdEU0wL2ECtVV+56ViBRZ0jO0R0xKpgo//mTm4+fnLuH/7hH9y//dP/
9m//9L/+/+j//hFe6T9nmQHMGE/p3cO9wwH7QA/Xq/pb1D5O6uUS9tJoNLqX
2X/QDDT1f/z3fp8/7//9K48OHUeynl95F81BUBGyj9m8BHNiM50X8Lc95+3o
QFN3/xYb+7tB5rdsPIw//Y+b+qf/3kPz5/2/f3H/9s//9G///I//zv/3X3D4
/gI7GHbVP//vWQcSl0wkXIKzydeRZdR/HU44XJvIzBYWmj2SfHMITWoxakdX
rBoxo9ukucgf8BHkIwjVou32zgcluBFc3SX63TZxcxRZVV3MegKS5jobYP9e
92X/27//Uvi/8Fl/AXH1rzQ6sYshHcMwOrgKDrLlenK/XU/gOrQSNnhDPNi0
WCL/hziffXO//BXNHehCnfWUDvZ//fcf7P/zLzfYf5HtzZP1QzEJoZEQgnw4
sIL6P/Pcn/roZc8k8P+AtlexM5uiLv1y/ycH8f/+ky/4V3zWX+B8+Rc/Ohi1
zfyHPRkUHkwzkGcvT++fHZ3wr9EHP2CfeTj+P3/yBf/iHO4zf2b9F2t1xiYt
98svy3/0VxbztqAoLDX1X81mue2feb1/IZ305iC7c15egJI6RI2VURlfdQHZ
2ct8UzSIzP7EbjS0N1tER1xX7D+d1WsM2sxL9Z1veyeJLG8NqG7xoEctOh8V
yL6u4eFyFWMVNh33YE/UwcfYBxrzESGITn0K2tPrU4QQ+xGFeuDXOoQBen35
HRwCOeESMILxg1A8SfvtwjnNHl2xjimKHuEVfBN72ARvAe9eeYjfBRyDv3Yf
x63jqTbh/cv62pEpLL9mOfm7I6wBjKH4Wut50aJh1Zm0AeoJMB1m7Mh/wBcV
1YxtXh5/Oq3cOYjE8L71GlYLjVmpzqj76nyi4bJxF4wH5c5YgWrBrvL3hZrb
8Iwv2mw5Bw2H/AipA4Jik8f46mmnZUFwLxJTFJ9GRvnJm9MzdJO0xuQPvo3a
3oMGLTvKxMjsjNUXva10rd0v2iTg9lfZWeLiaFd1g4tJXSidViVYGbs+uj4k
dJFwJFAC0kUETtBHG8dQg3D1ioeftkDqZmLMA5vVwRXxcLRnfBGjzgtpgAEe
tVhgdHpRNBcFOr5wUhnBZNt/hr4rmPDrvJm1ifPqi7Di4P51xbfPYHUfRqtA
w9Pe/xU5kTBwSqGLtiNidOatxj0rYeJXiEXSaLkNzLa8tb5jl1pGUEoQF3fU
xwZdqzaRq5E7t1jOJegRHyMEzbExQhzRpijcglumWCeMJHrO1KE2R48M3FPM
1AdjprVs0xGQUAM5pOK4OIIgaEeYDdRKxKhdlwRKEY8LvUVNIWhuuuXDBQTm
BjeD3IvShrznt3awf8uelw2Mg/e+s4gg5yw6p/w7Sf/kPdftOsdISctSAyEo
HuHFWKhcHoPbhl6F3yJCfpGUW9SrQi9pOHjHIm1E0gOn+83J8WvsDK8a6eoX
RvrCG/JGsasx+KRSH9Vwshlid2gncbTx5gax4yj0ZZhpluJBFdelj1noYKTo
JIot0guxjzsMInckhDW/W0/MjB1GG0h3F27qCEBmwGq6TEB+rzADg7e7nNyD
zuPZUzyfR+vRLjy4n7I9hnjBJiw5wh5Ei3hWU8dopjhwyUe8bEgJyQapxBLI
LqcXlYhOunTgw6vxhrLyBm1xUp/G4bofy9l4wII0aUC92MEH3HbBYyS3CQsn
6C7bwuqyqdcXlxghHU4o1cKGcPwZMZ42BYVbYeWNBVrhYHOVfbEJI9S/HO2O
9iMHM0ce+KHYF47iwkT0nK483NPLuuTDg9bMIl+t8Gwi6Fr8nlMOYvvFK7PK
ESCCEWAUaV5O7frC71qQmHgk8Epj3WQCltpMvwMVo12uORaAE91ckBfbJwGh
0vXuaPdZ5j3Q2Nfhqlm3K3beV46f6MOH6czbvbCSVZZJVHSSztsg42C9Dle4
7tJvN4xQ8KbaZBNUmKk3I/ZLZ4h6tjt/q/kQ9i9YML8Y8r9fZCS4SGrBm588
Pzw7hmvNz51P4aMj98Qh/P/HYd+/X+HPX+PPdJ+/OPMf6Ucn3qph9vGXve18
lNH5+JO9wZ1ALUc+rrunp8f36GuaC/Wp4H//Uxgf+ujS5tN/6cB9pDvhAclH
d7st1/13FUbGf/yZjfxi2PfvFz+zFe6Ele7Zn7Evid2qIlhM12Qpk/kT9gE7
GVu0Yu+oV/6tN7Zu7gTcFGp/9g2KD8u6JWx6u8AzpS1IpfA36Lki0k6wZQ7V
5gEhzER5AQWEz8xFgDz3IeGcj6CTKgraIFgMbA8+x5RPOktu7qybsv2UohT8
OSTwm/PyAynqq0uSyJIRKIo1ohaxacx/JvwNiosChGdQajACa8QVKBz+KM5n
0JFVKeCBBchXOggktQC07fgI2LOR9HskunJB/lJ+MwplmlZuDrRROZRVxevo
QAiA0sCdVQDZFBNVikFtlbfOS40CnpHiBB8GIf4X9Jm+ACCrVnCHaelHyrGG
5sbLdXs5xreCv+bz8YFHXrYIxoSjira4bc5redQJyl4LHfj2+EwsLwrygw1j
n56d8AJh5XJM34+hT+i+0JcjVwZMr3k/P6u4dudXtKbpsiloJhZdxwOHPw3x
p+iRpIKUnXPaoxR8g20MAKWLmmK1bio1edlmoD6Gk9hYybhGXBw2RuwJrTP4
Yom5/JwqYVYdJ2rYxVm2Tn0FoBPM1zOy9kGY/L4FlfkGXnYHAx87B9kNCaod
dSrBN39LuegI61rUf1jt/N2Ar6Av9Xr4LGt1x+Suc6L/ZFR8yNE4u4+PuK/X
DfRGmrqfvI2vim+ipYd34soLv+Hw/2R7dBHd8UleiN7OvBA5TLAd/AGaoc/a
yMH+/v5Dud/h/38i0ZzKIpMGwcoiB5kEyTfGnoxHgiJPYIM5+vMI8AGa3u2C
BGSSwHhbj/cliUa+HlKj1apYz/NG2oxsC7TqzAoqPqzAgkNzqibg9OnzIX0/
neflAvGVoCqcr3j/5itpUBa7jBCL7I5TlxMuROtDDbYCgQvfsGdUv0Lrcz5f
Y8oXOfZxxz3zpwgB8Rh8LI8xZpfdZNCjj/6Ig5P5OHQNPr3inCw4m1H/8v8P
tzzvGJsfs3G0fMfwDWss4fL0mvuqA5ezT3g9CLRBuOksxoLcdvN9DiF22yBA
R7iVhaD27C7uClgdcAv+PZ/fo3u+F6EYbsOtYN4H1QtKQhgaoHXqGvd6w05H
WaDZYdk0wxXCIk4S4Fhc7z94lN3l4c9ew5I/xDVRzO4NxFUAZh99NY4joneN
z/jeyDwXX4edHpJmNRBTepov80k5B7tqlP26qq/ZcAl3OcV0ZhcNGh8owdvE
W/msK+fVAShS3GlKARr8NlvFQ9s5M+gMxBUqWgTCG6LwYlUrhezHwKQHNrGK
tKzKRM1w/6I/HhOBBG4UMN0MOMYHZWODgKZp/wWK/jEhvfMqH4Y+eZ+jtFa2
JjFBUl6SHg8cPbKqs6K6gt28LEZ978VT9GJIfdUvaU6RMwMd8/FKAn3P8TEp
ykiji4s6hrAzDr+s+dViIUsw03xezty7qsTTmDQuZsERsJ10xauM+ZzgpJNi
mpN4uaY0lxbFKV0vSgMLzrICSxj6e34ORnWFw3NNIM2cuhZ+CA5WlvrYbepX
hk6LnDBTqGrAdKAvpjVhFOPiX9SsrKRjOilW15gP1+JA5eRPgxGU9QeHPE0Z
buxJPduwtY1PgN1NyN8xZuiOI+hdTw6DU1fXMt9QBhdh4imSIYukJw6UdRaA
Y0dPwwo2qjA0/DAY64J3LH5XT1fFioMRBI9lFKk9QySpC4dDh4FB4+LkLmbk
y17UM4TFz/it6Sm4BMmyaK7EycexMp8kk69kS2dwwl2hr8pvJrqQWmkRuAuG
FoFFBrroCCzIdg2MHGZRgB3dIsK84nQZdoxRnIDAvibzh70/U5g/zUQsm+z7
o1PeHUgj8+kTnbJsHkHDf1jnc2zqu7y9lFCZX06S1+tHhxY+f1X5Xe3TDAgx
yz5wWNCa8JPT4/GRGp3bwLJvrvA0BsMzWmYjTDGkMet3n7Efz3jOBiEpK8l3
hzYo4x3zYn4Nj9QQ7Pc/nInBRPInap1+45RMWD/F/BxzMbM+n5yVjPwFGHeX
rNVk48XqcixOcbj95kZS9ik6SHrcSIUfDVTLd4guh09jfQ599XlVY1a5DhDG
d89LTPmvrySDQ0dX/X22h/V6Jf3v8zfe5leUYFGxyqeXMJPf/3AKDY39wuCN
blKdM7Kl294ehavQ1RxOFozXUN9Ms9IzjkwzTwQltx71GPcausI5bIvIRt5P
VFuQIS5SLQ5/R5k8G58YSQgrEO7kBKkpyMBGEayINTkQQZ9G4d9B5Wt0w4uJ
dLHwyY3jKfrdUVAHb+6IdhZURDrJSdKyMEXrOwl7Gn0S4dOUnZ2i01xsrvfb
/XIC4rZXEzIVtXToi7L1ILv7dT6jxCDQUu6RsKC1+iOCuEELyMbrql0vEY9T
zIY+BW7cGQKvS/sB8AjjyNL1aq0fdNJSQkBglcnzUNDjqFFQROKI3VOuJ4iY
5upBX1HTZXfAIVniB1m/0oPPeitmODbLRC6KlBgSjoKEdtILTZgPoWmB/7dV
vmwv69W2bmCz9+2hSl14w1GyJMNQd1/8qsmJPOofbUriNBwDlHVGC7E0AfA1
yJM5bw0bVS7bKQWI4WTgXFebdIsJb+Gj4r51e78xyZReMb25Y+YnjSdzrhtM
K/qGeuECxj9i84g46lbD6Zw3HJMBeQTSpOj3QZJhnEcNsHOss8YGKYGIGJJM
TIEBMxDiaB347Hm8npAidCr4l2V2EEkqJasYc1sLQWr4MVPul5s7Lf/WGSPu
KG6bdCEuCVzANkcHWcG6+PiIhePwjCgQ+zdCF1sg78jOW/+MXIkS4AgkgEi7
KpbiypBUDhK6XnuhC9x5Xs5bjAWxOYlghDWCbea0SnmC+Ut2v11zun0bCycY
wN0RcQzZ4F0U3iZsEx5XEj3C6NiGlxb5vrIsliSljyf3WWw0KKZ5vN2H58gA
mdaNMXApMMg+TgxRJif6Mxsez7y92b/ua/SGXOagwtAh0kEUjLCNb2BY4dQ9
AMm+m90Fo6tu1NQRkzCMFbwSWNX7Dx5md2laqJf0QmLxeCwLqVfo656gOYEJ
+O/JIt9/sE8PIZtHveCSIpspLIHGG9vjbUkRUfZwP8JHJ0wreYWXTuh+0FVI
rsCzRm4PmdHgNXSOddLIK9pneGIL263lA7UUZkHBF02FjG9y/AnMC5lF/l7y
98QshIatpY4rwwz9AxpRu7RgSBcwdTUm2dG741JWFBm6xbGdsY68P2/vUTf2
d2WKTGurGuQcxlh5KPd3H/ElaMpJM3jrFtMexvMhnLSxekkQNG8vD7yfJkdA
XlNQ5pKFw43c/ig7ClvLysecX4TWix4OaD40GC/CUdeUauwkJ66dnmGAVAIt
q5rUwDmsgKzdVNPLplb2z77zJlr5uzz8ti89/bhkrgjsCzTwqHc0KgnbDrK3
x7998+tjGuqz47evXrzGvpozPwJ/ROLGIg+svwRl96KmDM+80lbMpSIpRP+g
Hea71gGlhdVH6+XBU1EyYkUO5CmI2vAMEJ+PR6JZRe/eVakGgqNA+Yk/VQgb
VTwXPNImGQ4sQA5vqBXigcprrNGcB2mh+t9bWXb0BnsP9rK7h6Kd8FLfQ8l2
RDry7B41wBF2vB7boShRKwmOPsVPQRpkhLwE5fREfon9iCI0yO1FX7SJOzG4
MVFSk32w6SoMpMXqVa4pyP6P9DafCcjUIdRfVAK0wwJSKbkZp6Opt2lOZjSY
ZRU9IqQ34tNHrhd3EZFXpaRI6JlAIYzWHZ7eEYw0m8BD37cSWiBeJRqoeMrC
+Y8ZzK1CdERcmM3GE+SiRf3ChGzxdoleVTF0FneyOAFxZzPDF4Y2VmCU29fp
6IW8g3GLNSmQ1NmRPegiIwXPwTBLDpMcHR2fnKGo+P746Gzgvn/z4vWPSAFw
fArfvjw+/C3Lj+fHRy8P3x7fhut8lh0dvj46fvnj4dGvHYzaNdrhuXz5jBbG
8du3b956FRRt2/N1mwv0+JQVpyMMM6ISSR8pVonatjIOqW7VSjM9+Nmg1rJ3
QJQ+opPbMPacqGGmwhhG5zB3LeDINbpq5wyVjZaptUozyWzAE1uJysFomJ7E
DoAoriNeWDF+vX4qp1irSEN4JVA4F+QIARVUvBeCDd9/9CVsibvxqck36MGJ
jsdKVQ4WrS7u48imC7N2jcOwCm7zwKKmyz6W1D7EJioJywK9i+SYDK9RKh2/
ezELVkuJiuKGgsL8AHMXxb9koXxEy2NWajQr6ks3AhYL4I9sRKoF+axjeLI7
A9M5+eZIOnz0tg4DhYtZnz3Pt3adFR+zdxW6xdGEYCcxq2egypW8avNUzaMt
2BRIkxAP4l2j42DLY6+vjW95utfUtL9KUemVu4+xA0W+vq1NkGU1HAaIIWe1
kIMT8HY80tFGjeOQ/a4aeRYokd/UzaScgb2CTzolhb9P1VeLIaAfqO1w1U80
mZoKvKj87h/K19ta4dBlG9qqyTeBzkWaJZB07ALjbl3niAUa4gSAaqWNgmXy
Gt6MiHHxwte9ZsotNopfdU9htQsm0i93y7WAucoR/6W4WrbcH2DkiWaoqEbS
rVA9/NijsvW3yQFjkS44TvAGrHN42P8sIibSzqGu/C08ixr5OTozdk5eP1wj
vdsDW+QM7JPjvJlv7B73pzQsqwJ/RNranHxY+GmIn0zn9p5yO6/wxJct0uoQ
YihtXtLhCz0LKxVRAoul/w2tDLIoopUzyGL8jjyRDFKkR0Qw7bsqv8LqDiBb
8PfDfjvVGKk4JJE1O1yHJsZR9FxOXwmdiwP1O0KzmqMb4+dvGCVlT+vL/KqQ
MJBnhaHT14TAn9EKFbjFwKE3gA7bHh8A2aYiLsPeH5DVyVqft6h5MDspDqAo
0GjzMYWmqPf1WHN0iy0KB9E3pq/B7S1ONj3Q+9Qvxi7fvo0YzERJXfoePksM
N5LuI3eLV8yoAI4hUQwvCnAnBBOh1cAFQEidp4QThlEUTVM37Z10NxMuaYdW
AYKJvt3+HrDr+GxPb+aVsYNeh6cDxWrJ4Y1t9j8yUQbwwt3J09njyXQ2nEzO
Z8P9yd5s+HTyaDbMJ09m55PJbH9SzHYUynSo+mYAUEeJbCIZKEyasQIrsAte
go4GhPLgKl0ssfHRk0kDRm60TgzWW2GsM0OZRj2kMIrVxD0QjzUm1hG9qSkE
mUXVlwxFeq27RW0XaITYFvwCVXZVtiVmgKrf2nUQ7cIC0DG50SArNCgYZVQo
m5vYkIh9Vb8No3VZkeHwiS6mcgaCsWbiPAyA9TnNKAp3IHw/om/mbl2VMFCR
vhTYrLyFYJxHwUKGKwr2g7gWOZALyZhMhjGK7DEPqpzMnrM1Y85WOkFMMI8C
f/IUD2gQXwABSH343EBoYt8dJcERZSznsog3hDJOM8EcjCw3q7U3BAkb4Aac
JWOdvohVyWJtc5GvLDDXuwQ2YeR4HVLI5SIv2avishhClZMNMSu91sxZb8yj
hlhOin2a77EfXRcIv5z3/vCLyeaJui0UTbKaZFzJie6Nj8+PKwYFm5fzGw5t
wjPlQKQoUcXhj7M4jS3JIgMpFCWJxavLmmNbo65Rbo1jeZM8VKRoxF2Nyl/0
tMiOd2nMKFi66k4TwqhCoij4CkHEETo1H7hYFg309askNc1ELgLrGG8GAbpG
iX20tlZZgoHtOS9pT0UQRJ9o7VBrOUjbcGnZh5P6JCs2319Ovp2Wb8rRaOTw
qwP87kHxHw7hu+/fT799ev3rveXD2dGLFq/4jCiVuzWYO+gGV+X0FisMzr3d
QTjNkX7y+DWfkPyecjY+evSgeAJreljsPZ0M93dn+8P8y93Hw/39x48fPdqH
Xx484NvMQXuQPeATWgXBjlYVG+Z8cXwAPz7fnX45fVwMH+YPCziAHxXDp9NH
j4YPJk8m+5Pd2YNid5fvk2B0QGT/cZ3t7a4077Pq0k6LysHQag5O6vfWdYjY
cAFL39gf0hZNa8z3vPNp8JP3TaL7eAvMdj7RfX/nBLWNd4MAxzw4HKgdbxj/
6FmvCcCe7+U7f8d3GEANNgxrE5YhD3lVVwSB3/nDg6sny9O9+Zeb3z1c/O7B
ZLfcr58eesVoHJ4KR2QCbCIZSC2NBVXVS8fstketRpl9QOQRkq0ffnbey2pE
GLJoUbpO9IxHke8x6rXzWgBPGbIv+p9DVDaCz5BxHMkbxwGhjF4+2xSrDlAp
8X/aoRIKSQbphaQWfkAAd3VgZeyQDSFbr+4JEqxsbbq+uAdRLAlMzQN+3xdK
zbm//5SwS28qdCbwzx1UgPU3xr4yUi/d+KXwlycQ5gsu5hZH7Ee+TBplOTWF
q5c5KmMwgJTjJCD/ZJ4pBBV1jl/6wEcUQARi6MIvEs7/Zh0kOgsTGgXy1aPR
fV05Drx4ZgCT6n5dIkYW37s7QjnmOFD4oZi5u1uzQc8zAzP4onWCmEkGTVNW
snEXSDNIH+1QV/T6XV8gikoByB15AmBQ1mnnOS89ZFAdc73hl91ekA4jUvKr
IrU0MJNOKnQgPn+UvQkDarrjOagxprhYYnZwQ2pxtA1kJrF/sfmkCkHmwwt+
f/PLTOorg4mMatKI2W1XTCmoabz3NoMb94NsB6fb4CBWLe5/zgHmOkosHOWJ
xtA9/I8Q+jgUB9wBSKMhEYA4V87wdrr2gDVIdEXhseE1hd2BaAmiJNhDN5y5
dGDA/wi1ZX/6A3npFAYo5oJvbZy4EZ0o1NbjlxLPGsMrcmNjlUQQoc6rqgyy
xKztepG9e/fiOYYZSQsuW5aaMzEi8+w8X89pVTlQ1OEYRqJ21mU6ivGUIzZx
YQc0WlSqwq4KnehJfFt4Khr51hrNOQHqSc8leJByJxUkfwIZr6C/EPRSFUQE
RclveqthGzaKvg72pex23imHHjvpH4yO4TbJwCevW165kLfYRUIQzQw7FFLe
Cs629D4RQxSt+Xn6puamOIPUHwGaxehuZWlNkjTB6GKhKr6/t7Q0EZ7uju2o
391C+Xwv5ImNRZ6MdW401YsEycCLGVoQfDLTEzlY6jM1wTpczjc/ruqxq6gY
jZ8U77FXSAbjK1j5IzvqUI98oxdhEu8WNasHHOQ8OCjW43r1Kzsv6lVyn6tW
DRiCnmhSuYuEN6shq/Rw/6IVPcpjOVObN4V+R/oU7vhzeMxllmhUq5j2IihW
5IG0PUPKEgFE6gD4sjd8emDKgef94bnPuPKKD7DHFCGRyUoJHi+qrQbuIHp0
n6fwxYp8EhJuCP3qceuhcTuIPH+hz4Ftpo+jiKrm6OHc6dNnMWNRLsl2yWL2
bl99EBRdyqTNYSldETFsmHQKwSEnmGR+c4KTSl6BzFYHO4rgjgr2OZlp4yzG
3SpEwW8PsTTQPVQZIBVlC+XT91V9PS9m5G/MTo+/fXX8+mygso6SaZBybrur
deDsT19GEfdRx1nkh0nfreYk6WiQmAOP0RzlymmyoQQacuOLt4XJFjlThdq5
90MER+dY/WIxnnZSoIu4DZd6RYuVKpKq/Gg24/A51uET7rzNH+3c10JYUKWS
qqMbB8ejQW4hvZR3lbG6SfxOeCmFfLrj2COuXNfJTI5NMiLwBei0p1RMfy5h
KmriDPw9f8VY6KbG6j+UANzxp+PqSnLl8/Y9HcAUJ5xsnHoLo9DAqqZzJFVO
TMTAo0p4fzrro+7jaGK4EwEoEygx5xO2XJhx29uguUIxBEwb6FPDVWzb7krg
M+eqbmbmewY62Sj5jG7FJ+FAwTfJNqAXbQsGvTODHCZUjeUYlkUu91LP+RRQ
bJTmCsaHGWwqJw/gdQ7rSte3SRWca6GCWTFlOk1unOMy42UNWupm6DfcbTsj
9MRah9RhH/vht+iQCEpENsLJtQXbZtFqEkLCjpAh67u8qDjPkarLREU19uO+
4gCEAeX8SKRams7JjyN8D0a34DVHeWtilHXZJhf5xkGn460mujolgWP8WbYc
x8jTBAQkvyRkQVXMMykNSSHxwDQatp9XE12enZyevaayTINAKSqnnWQrSaPS
HR/Zj3Wr/dHjTuQtog1r196yFvaOyvlCZhGNWliUMzq4oZmrYqPJjvQLdHfk
Q1IskS9z0zyG0zRea6SOJxLxF5J4P6CshbOAPuFsjvEN0VP8iBeiqxFtyU/j
AGy9JW2DAukDlb2B2yRIiCzrEtP0ctKIRcFQABj/l2X1XlwuhNUmr4s/rrTi
jiSSU11j5gxQFC3s1PckbPa6kjX1lT3I7r759T0JdOF4RI5tsq29sxv6GQaJ
UMMw1Di3PsSybum110s//IR674x7DNT0GV5jPxlhZD3/C7vmfup99gZBDG96
cgi3nTRERebruqkuGBxrFoolZxB7d/BGNC1IgaZTmpvUAi6zQjh6U1GFhJv+
ZFcPBeWyzQp/vK0rPFmrQcDwE48gG9CEqBNfRQToEsLUTlKhQZMFss82p7Gn
dUtWi74HaxsC7mkpy0mrMNHflMNPtH5oaYiVwAupsYDybaAi8u8+fkTJ1JNi
U4tMYFwLNKJ5/wqYzUGNndfrGTlUQJduVre5NdpCPbITTXD31kaMTxi4VohT
LtaUbIXPgrnTmjaJr7ASo7iTC8eFijdIetFrQaLmxV26Ta72ndhSnhMO4RKG
wqHO0LaU6X2mUs6QYCglY/SSzwRzrUvcKWELT6l2z5xpW9kz3i2x7D2m3T0H
rSBv6M+3iC/0uXgvi/yKfBrJGcG7P83wwDt8iseAN46KO+dzUjxzdq9dcDu6
4WulkEhWi6wQ0ww+pazWmFuGVpvkAiLpAtJPwK/TddOweoGamFbP9lZg7KIj
wBqxghdO0bbCcwDmiKVcTr2N3UXgyBsw0/wF3A9qBlkEf6o1gK2L7ZtwPeHi
uw5Fb4hJ9NproNbgsi2PkXRIYmzC9EiO/pCtU547X49MsgBIOe+q3VvRAyPm
F+61gXk1Kbgfs1dpTtTK4TSL5apu2oFTpxn+CG8zo2J3LQkz5OaExbBuCp8m
Vk+Qk0JzaM95r3e2bReItH08ZTAjxvnYBsSrLmtkLPGv1OtbYAiXr5Edrece
WlyVbV2NFNan07ypQvqLDh8m1WBvMoXuulYLj7x4EWTkG2IRLoiltC0uiEPv
7i0+g+wbOmR9K5I+BUpewYlTzWosctQRdgfXYP/F8NBu5EnTAKgB6ZDUIqda
vtYww+LSfeMZDgyWVVmyAr6MBHe5IgIj0gTaVb1Us74neb31BQCYhSuiTZWX
zjyWO9adafubpvFO6Z6EWXNNpKf6Y7x4xAGja0jkCxlfYmPSL8+070Legg+w
5W5ZA+3rFqVLYNXojBmyQ+g3w2Wt51Kd1HQP71yuVP0QbSg+scJu6Hl+MoTw
+D69qE8r6gPJh5SewusrLObEi0cpPurRQ4mL3oKYDh+Nkc9hP/AMhLnTFg9k
9n4mDYLd9aI/DowvPz11zYkLY0epoM4bGZflxSU+3eJ8e1IgE+3L6bvAnFvC
H99sXy4geWFzjWriAkDCseOz/GIsVq6csSjxPDbT+1bl12ArkgsHDRGC+nGK
TT7PAg3Ei/Pha9DHh69QqJCIWcKocQ0GaYwFnn9GyWDo5UYIW4Ig9Hk/7Iey
c5IC0bCHHb+ZyiiBCGQeIqD4Qcf1HVfFRWPoqCO98lZun06MIsbmaXl6fqSZ
bRWUbqta5Q0t70DWt7duGKcCp60jyCehDjrylpkkrgpeQL76wW9xVBQ7743N
lhkitKC5mSzR0Q5iYLtD5wevULLt5rMwgd2BTaeL3UfoTvFP4jhyDIVH5jzy
mVV2E5fCWytJWOyTJ7Qn7TtvFWp2XuUx/5qMjLKIdDv/dAPQ5SIiUVO9q42b
zR3HolSh9jEvVZwoaDWw6QyaM5td5EuseWOY3VF4aLepNGjIsCUSk7qqeP3E
ysDT6OQUfSIeCwE6uTGeYz/q2P1oMnMGJsCGkr2L/VolzPQSNTHaMOfAd3ZJ
Et5QwR9YXoV6glxv4wTlsGzKK8rnr+oh1i7DDrY1O7HayxxzeThOhb8FRv8V
56YX7LSURvQiOJuEi8GJQUt44cDCuOsNtCM6hsVLdHOHT2VT19Q5TmuNtZnH
SRJl+75TBwC7imPW1ovCUQUgUv1AW0CvqjoUhFsl7O10LWqY0kYFyh7qlEE2
L98X21mVRtnXRUsWMd6nMWZWdNNTErbfQLJ5NVYNehosT2ZL/oG8dvaVBhxD
2DI+SmiD6SjjkPY3IEePrW7veWEule4D7KlZ8UzhJ7hO54gR52eHq0gBtjWr
xMESQOZ0B+iBxQVhezIlZn5G7BbtegKStxC9mK4trYLShltVhSBUObwArKIV
8lxQIeofcBvSONkXJWWO9ZTet+UxHGVvrsiHidyEA5MhjIEbKikBG5HCH5iO
8SywFWkda3sR1f8wdbl8W7TlQdFoBsKem/BuBhbeA2cawaljYmrfbGiKTQSd
/Cf21PPwi8V0OWbk7DjfyzlldAwCFdVHr/7+WM7Cg8xQIRYlPE2PUbkpPITc
OKdvXg/fnhzxoyj7mK9GluAV7FPTEj163ZT8zDdLVn5YUeM5teWLe6aukxrG
GDUWBwpg012Pbbw6OuHSMeixz8arXdbaHLH+cBhgrNlaeF3riZ9x/FLa620o
cd65fz6c+O7Pwok/mD6afDndLYZPz/fy4f7s4WT4pHh8PtzLdycPp/uzR/BB
csNwo+AtfqtIwhmNfYCP65IjQuvpUvHcYdHgD6td/V4871vHccdDsPsB1T6J
rBKqgDhzv4pWQiACWAuXPqt3VObmlrz7kUCYPDssHxa00CgFCb3VKIeMYS4m
o0Y0uAKLS9emjpZ4KRcFaoZluwhACsPegDyH85rToyrPTFgpRT8qy6uV+fX+
Hu4nqUun2ipyWkwQs1fJlX1SzrtuJgK8LSg9iLtCyRS4nAty9OvZ47U2Fmpo
rVNYkU45W3eLeI5d3yhkHjGDgxEUEu8RokHGDQqGjDwWBOxVQYFKf6N9mKrn
vnfXOR7PxWUJ5hiPSTFLxsCz3d/caBnYtHIfbv73RYHqgcsxoIWrRZweQmZo
SO2IYwPDHFhMwtINddxPPmDczUXyVi0oHayFLiVnwqGOkhgc5KrxdeWC4/IW
+hzrOGnJVw3bLvhOfDwKTRnyX/D6TFw87J0IqeCSrxa7JrrJ3krhFOFPgyGP
agQpMgGISLnanIhmyDi5ltA2+id8oS4BlNWEOpkD8OaqW3sDhSpGeNPfcDgJ
ahpXAa1rsO5qXBrKEntZ10LrRzPIr1SuJO3QRpYSygFi5XoAzfCoqldvzMGz
9sd8hQ5kDPF0vYVd5HwOemXIxU+QUkHd9Qss2P8jXce4nxyF6Ek8oAG1JWLx
OIURoQNqvVjkITfgFTyJgaK9Gq6sDOWXxGUXqD2sUh14vHsYwWUzYCi+C6YY
ZaeYZovxN6z15sLFvgbswDofEea8XlRkqTP7PyXAen5Kpq8gWfgxO8TqcaHF
LgkKvdndbdmECc8DtBfAW3K6xMBmRQNbZHenbJsB7xJdQcw4RMQZjPSpI3yK
kBtIAOUzOra6lLorONkR/BrDljMuixBHkD8iRXMvhokfLvRHEksYJNb1R8vT
JHd4VKB4k5N+U5kEv4uTH88ui8pzSJKgJPlIzZ71XH/aj42kG/jMGpgzfZC9
fPPtj9jQu9OBqDAfCTKevncgfFjwdomKJfQxo3IBpmNa5qfc9Zs7Ue6IcxGn
Ffmw+jcQ1njwm26BW6Gt8WQjfKMhfWUJTA2h3KXM5PXS+03mNTt+RWlh9d26
0/igpsgiCcJTKts4pM1Eb0Km6+kxRTZAknxDFUHS0KA/JRK/Lu5HiXwyDC5C
YnQd2900oJ/AaTiLO6GCJqfHXsQcM24iTdIumXuVE0bw2CZLSAJedMkXbXRb
4MYrKwqdL5iifUxNjJNYmZ9C5v+hC5mMv/+6gaf2Z6WPCz4geof5/Kn6NLIk
pgPhPaCUyD9bTzkMwinv1gHAApx4A+hgZHVT6fIzdnlQX+DFGVfepchMrLmO
7zhgbc3BtKvvvLosGzgrbIJaTFBIakRUJ1j1XLz2vF43q0s28Sjf56Hm+wjO
9paMH75iZxCZbbuS54Nt7Wtb/MDb2lLjUa0za5yZxKF0pnzmGq5ODI/i7mIU
pNdrZ/PCbNTWob4osB69O8/GmB60GTOQawRycMGFcdl5WNW6s3w17me4ZEOF
IJq3jboJp6DrUEYfhcQxKKCMjj55kLqFbNPC32TyI1I149jqtp/l3NQUrnEH
aiALlNgpeKO2P0WQeNTzm0QKmUyJVAkNNUUAeDYirXc3EFyjBPs8bAirQ6L8
ReoZurpzprVDfdyzY3fc7Grvug5vBnOKBU5xQuzRKIH9inOEh3vrtuUeh8oa
Aited4nKfKiS0yM1rEamfmS3kD+xvSVjEoZsVlAGGpfVowyy2G3rjwoDyfHC
IGa/0JwUr2kqukDKbiTMHrhbsFmkmMLzz8Q5CdTy4lzN04EXhbgDKQsL9O6y
KhfrxeC2wKldKZ7JuNKTnG01EnUq1xRdz64SjQI76SaWMKDKumFgSY7PZ0yB
uMqJoIpaTBzgLuUxkSdxPCnJ8VSMKx5+pe9IMeNaSd0V6QsmTjnFrFLMOOc0
bJjLSkJr22MySnfTrhdLiSM0/kMHmkyNCzo6zU7AJUsCUoxB1Cg0NDN+CVbC
kGTQ8MXzJM8Yy1qK6iHGRM+6Bb1KSdJn6rI/PbZFQno0kbUypevAo07iQWWy
COomGK+9s8o1B3HKhCLWXRdSuIXWR1dmod+AkcgcAokmrhNweNonCURFJIRF
GNpSKYAj15o96FkJZ/gVNkHoZENKFiPJOFYmLO4cnrEoOTb590Y4ArQmMdkH
LaD1ZF5SARzShNJCiewJCZq8oo51Rsju4Zv4NSmpQusk+CmHNYtukRDP8nkV
Ce4NkQjCXND13rVejM3wIhLG7hoFPuZBmVrQvZ7I4KFHJ/z422J1lrfvx4QD
cCkYUKtG3LbTTjAhuMKcmyX/BXuMjG2tsidoQkGI+Qx5Vji0M3qxeO6gtx94
NcD2nKyxApY542mC5Qa6AsOJb2AGryjxmBJksayHjnF2urYlO7GfXBfqhU+3
TfwFBnSRbHSFN47R0TimqExB9bmmWoJsb/8BRltsEHp8QhcdkHfyq4cPxlsY
oi7rqpZkUdOs6aIyOmOcItMaiFu6aNJTdOiUKaEppPxTBcKZziXsWEvwd0VK
ibSWQmc47Yz85DMdhTrLa8RphbipedLK8C2c+LcZHjLjMo8FDcSZB/OaPFDO
I0V4i5dlt8rSkMG5ZWy9ekOD3D/GOal3ZZVTESqfxaNLPC1Nz1tUJ8WUhJXz
kR9TNo51RuhVLFhilk2xSdbzuThUrAsHpwtHo+vP4134W48JhI1oAIJd48A7
jdWrpDmnKGGvGZSCupbnOqXkn1gP+ELzucTcoiM+wo14tckqL4rb6AKyBrG2
sGBS7gmBe1z8YA4dsCQkz9yRLB3q0Mfs+W1+QOucc+oDI7pSm1Z3FzuDxDMK
3o1ddMZcD8TVHvZsUen4DA8ARkfhvAunpGsEkBwyQIViVYYRF19IZfelUWJv
1Tgw5dK9CpfbckPwN4Xloi6nyKcUlhY6nNiF24tq9uu+18UUKAodlWZhxhwf
EhacK9ldMBcXXH3TY4BxoVpF1Kv0oHqSz+K8mG6m82KUHQWqE2gDtiZpvOdo
0GOgndZUUxSOSegl8YGBZLXHtcrSSbYrk0a43jO5l8uBSv22xAGkm8u/N+d0
UrmqaBR95VK9MKDBXZbCeCPgS5A7mkdxPqfkVuj2op7lMIWE2Ku0KJzcMCam
DF7CqGeLMqTNoJ4o2V9EVMiXo4foBwkkaFcHrFOpdYBQIK9X8ZrADiEoSUDN
OtywdzetF2z8oxbf9lNyHuDZXBtDuYrj+2TrCerEB5b8mESoIHOflCFiqF0u
OrDA5zPK2vRNKJa7KwUkh66Yz9mPqquCWuDHrOr6PRdUhoF4DQ/AzY1MQr5e
vHlJk/0+6y4VBmL66/3xhG8S5qHyyxq1FZmQmdbmMq/D9bwoy4+pMQyrhl5T
yvq5VUmM8fIaokUcYVsUWr9EW5TXZjNWJ5vymMgm68mUKiq4Y+qTpRjwSSBY
3foaDyH6dt6Cx4kEsQbHwm59v5H7tGfPcKa0DvjicqfmUvgu4U3E4O+FClxP
ANtOPSY5QDQD/DxvNBplX1xqZ1GXR7FrX1Qcg1AlkckPWtWi9Pi1IgQpoEVG
9yQPHHReoWC8JfxnKxkXxiReGBYZIpxFOCUJgJs7lpdCwpwRMDlm64yZMpR5
HTdF2FvSY6ZAGgisk/PmyjZjMhDSR6uUkBojAvA6uN+d9f0o9wNn+JvquRcS
m+aHU7loTpFEJ/N1DWbYxlecjch4OgG6AHA3AU+fc4QSegubx3CyQbp+zmrb
yilipLBpyWSsmrhIJtFVJmjo6J7M5aENs3xEtuQkFojDxomXYSvnWusDX4kU
VgkRxNT8LGvpd346xmjDK0hLrYOzhniBEXGio6gGZI02YqseMN4pQ7BnZKZV
63VrzAFkR7hnP9KcVWiDihlD73wD3s4Naxp1CJo4u5j9tDj3k2Q0nXwkU+PT
hSBvl3e2U9MzD2Fzf6/wpMWLbx4vfA3i0Xlxycw6TdEnU5L+costz/HAJogN
dMIcvTxOY+iODiF+a4UDjiCuMllidFNgwwmK10rdIbcRVo28K2Wj5nQSFG89
9CVLh8qKPSfAjVgyJby5nYw1OalMw3Rg/+yC6sPQgtRWD2WmourqanMkMFGP
MgzwTe1yjLaMuFvDxXGKhk0kiG+XxRXdGxbvLTeGpPxODwni2clmo7sCFKYX
IooVSi3qZhVNBc7WVU10cqgDNchrCrZA3pZt2tpRvSwLT7E0lovZqzKmO8aW
2Evq6SDYkWEecdCqowj5TWUFKij4oBhRI0m/Qwp4ICYSbDpjdXEjzn4UZHT6
Loc+94feJbnal1uO6awzqVCHlvpWturYv2UURdOIqKdBFkuKMqUp/SAFNkHD
uCrIDBJdeJS9ROw8tkWF4eNzMBCfpORyeRUfmqRLUdnpNsYBkCqgepyPYeor
CwPBRcOIiVqYXUd2eZu5oDmHkTCcN35rkKLgXaqWYIhK3lFKfCY0gJqFC2sP
PcuaEoCApUt8hQPRaVYUTy3JIdrx1gY7ZGWLC5vUTbRzg69CX0dyoCV5MVU/
0AG2bi/FnlPvFM/ZYdXDFOKVCNGPtvKGKOmCFnFfeSwRbFdEpLBrfj7nqlT0
048UPCRBh24+usrfQ2oInx2ENWi6241DrWL50zI1qIU23X6kk9kBwwd1mDuo
mVCoStcKaTKm3GwEkkiKE0lAQadCmDgsG6O3HnjEY0rBEjtDTkreeTUGpHiF
DELVXe/DFIuZ9peotvwONploL4m464B7/6QM+NahFlMahDFS3hCiEB+CCrzM
QlDfcI1YUwcnHoQVIre1IPOagir07kG8SHDBjxenhCXY6TY8R8aOIeIUS4Kd
iCV8kh1OENAw5RFsiJ/egQ5Jbof6wGIlQxI8EJAhWc3n3AypAOE6oTchBxDC
hMygcp0rGmouCEBGL7USApy8rny481O0GOXu1ANMTdiFOot8wvGWaFXYMwKA
Mzu8JoBR/TeiRcu3KicialVmtIPm8cK5sBcLM3dYYAJURXxxEuJYefMgUwyr
6aKUw+S8R/ZgkZQh8lwLqUWXBMFqZxo15h3pi0Zh7Fg2aWQF+bLjYgppYTG1
VTzBrLGIXGoRZcYigufrw9Xxpc9iwSS4zS7Tovh66VcCIxD2Bfl4xrgQ5uhX
1tUvgJCeOmiYAUT4GJz+oSo9A+Xjket+ZL64cYoAfrhVM6BTuV6uhugnNBU0
1aYTH38yFCf8fHq2KGkHwu2WTzUlFGu0Tdg1yriczFN2+SOdljnLVDwPGRbU
p9INFNCno86QbZpctO99CMmxANuu5mGd8ucvDl+++Xb47ggDge+OHg73yYrG
0xe7x6Po9wWdEyb8LaR8pa9WiuEjD4iW84NCXtHp8kxvvDaJb3z1WItlTpu6
VUHbMg1U7vwR6LnKfCE09DQNgvyRY9emCuR6BHtJdxt1EskLQ5+k0i4bY32i
zZAyH8ZKHEYQeIKg/ZjzD9cictAPU6GrZ+BxBbrKBlsJFFhYpdRSyU54Jlf+
VXCnKscl76LI6UHnX5BYMMnvqliS8tDSZL/k6Qnl4FYlT2seTYCpqO6bST3/
8ZYbhXUk+gPm9siZiNMT6XPCRyEdw2Wmh6h54rN41RPlSibSjDymrF4bCj5c
SrMZhm0UuatqP+4sPRQkOoeOwOBiSUE5qDjgtGTqrAlp2ezpg7VnjnQixFkv
QMKyLoqBZdxmmq5xjirB3e6uvOdrijGIAosTiQsIjzGpMERxFO2qyuaI3VAc
lh2fk6g1lt1CmJuzHlvMg1U9Td7Ytzi2FpYpzxSw/v1W2ggh+/b5pTByhjPk
C9xQ0aFI0DLJc6b+2swktTiNF4SWDnbGZ+USqICd/u26ufJIbfQei62pL0Hn
Hh7k+HYy3TrIwUu+sYGknCDneGV/mA53Ax46suLkkJgQgsTAxnVtBeaCD9bI
pjaZEI59UJKj3DIMwWJ6In3L8kWQ/Sj7D96djFGBicsLRHkrOWF/UPklFgM1
OsIL0Iy3cIpBy7NQww0ho00tG008TS+eR3SCxLSwCc4Kmb3O4tnd7eGGsno5
Qhdxxejo0QO03+RkQNeOT5EyCmz0GlJaZoYrajxDFEaDgWvVWNRA8QlgeqCD
YEDRL29BTh9ZUDR9Oqqwd/Dzj/wZV7Wve2KWA06RHOcENEEXKDQHXcdMTNE1
fLKU9CFE4Taqyoomg+WiywqFgmBWYPJTmRDITTM9+ZqiKq7hFnJgDwIQpZtm
45v/QuwY2ruSCiS8Un3eqsTZzlT+3h5vSbFlyRl2WWKz574a42nE0Ur9Otw7
dNfFfD4kxkd7m2ZteaRxqzwxKX4Yzc2HPbDBkW3OoLxBO5sIw8TMwUlXM+ET
j1TZGJYKgWaCepSjAjjzhyzCPZCchU5grfcDy4LgqZOCrSXJ19vCk0EgZjAW
GpbZ0IFDEzT0BEw3dzRE6NzzmCG7bMUVpWiX3rAj5/xoJR16N5BPVYtFqmJA
n6bchywhPJgx1Z3RHAj4oAZwa9dtEXxDHS7eAI7i3QijitPr6407ca4ZAfIk
8XeyK5Z6gUxADbmvOX5KYUeE9iBWLIqxUdKYunFiXK24T+O2HBcQaGh5oYSY
ynwUhreBtCyTwopbGh8uEFEtkCO5vTAIxPckk/Udd+Ib6sTNHXLSa+yTfoJ5
HZsbxsy79LykUcFESBj89RSJ+mbaCnGfPH60C2tdQbyRH7+keP9bKUiOchLa
IBYtG8GD160rKqyI/oh1TmRQi1TOcx2Vi4IiEsY7XGUvkJ+JGB9NowLhMhkF
we6ANokxHdoj/33sbe7rYlQU4K2XA0JqrY7OlckT8akCaRFX5jlwXkTigrcT
LCQPEVvIIEkReshORwZ7mP5RShoeHNE8MoeVSjlf23hRrHJK29lW/jDfy3+q
6uHtBM3OdOMgK2dffSZfBL7qVw+du9nBVprldOdgZ28EP+xAny9rrD+Eddel
yDZ8TSWJml34i4Ia7c7BjfMsEvBhNBoN8DO/MHyxUzcXo7JYnY/ojUhESTmm
ofjQsdbxTX/No59FdvHwE/7T4kjik7KEnfFk+dx3K0ItWQCnL0wKzNJorUgg
/zLIndIet1vEYAT/8mnTFO+nNYQueyE2k/QnOlAIk6OejlDf6BnJKKGdiAiV
A01MFUJa6vsXou9O6VTchOLl82lcnUEKDAjOUayFRy1930HWI9NUtuLLU+oe
FSbZwieRG1pen5sivSO+aaX+pXEN78vFX+C+Oams5S1xKPPCFHsxuSnanphO
Xvzb8dRFpWZM5XqRjXGARO2ixMUg8V9fn69oe08+tKuZ9gwXILllZDVQBWzH
pQmMzw6OKur/fB7QhgSGi0g32YM2AaMFhm7gqCIcmetEYW94rgkTJaWbDEUl
2cqBNcAZWmzxttaNrYKAtWzppvVM6imlL7sJywK21kBA09KBBVaMi9aX6KVm
c51o7c2gzDgXqQopIBu7l2pHntmQMomJIMWnK9I4VptenYveCRUnWSJByyAj
yAV9SoifVPWSLMojjEER2TXnzEF/n+mhFZp0pklRsoIKx+/8C0IQyCuPmIhA
CpTSnoTFN3MT4hMj1wzhjw5780Z+SsUzfDUUcRd3qlf5OJ4a1ia+5PhHPBzI
g2yPSKphzYfG+DYV0XAw++65LBE9VgsEgYPn50KJI2PsmwwMtEDjJFoGCmYE
S/VXMb+o+8gmCBVXpyq5seQFjdP4Gksoi+QJCxCwhClFq7S3FY2wNLqoVKuZ
RW6KxbOtRgGqd55RkouKLDj3gToh6cxlK75l3LwhNSghJrJkRngMt50ucxIl
ZWbkBJIXylzEP6Y0fWRkfvT7N/uYbEpE6acL8GNM/peQaAheH9fbxyzZefCN
rEEhU4yWzsdoNHQokAUNxs1zc7b3ZQQIPo90GbCUP27ZitAPTbn3S/znPZpf
lRKv6GlcJiaMmKYP2C86m7D3gUkDBuUPz1d4/08IWYT5U8+9pGcgwozEgQaw
4rXBgs5TQ39YuQD6aWN3gZWMhknu7vjVdDk85R+GL2ZjZMVxqnmPpdkXs3HI
wMUzyKoeVFYibz0gEzaE2yp6TCIvG40VpkjSvbaHLNacPJ5Or3aJkB1UmlCt
sdEu8iV2OLc0i5SBlPG40db3zAqTLtE/8rqrvKOuj1yk8QQZEF9GXFpt4KL1
MXiyuwVCrU8SK+yyROJD6/f3HnJ6L3bICr1vD6CVUpkiRAo2jiOmnClIP8DY
3SLJ0JYDVthi76iAOOM2b+5InpTkFlrMTsUxq6rud50QTQkeLFLphHMiOMmW
nC40Wn53JYt1TImktOPGdCsH7m9uaOMdvjv77j9++oT0WR4+Tv00ZIsw/hJf
1bSWsbBcE/zCgsADPp+xh6rgEY4KIbH4niTykrsIrQuKF845e/mU2yrKnrhc
TxIQI8fE4/pUSPMKo4nhxT61iIk56PWk8UHMVkyWB3kzO5m0BL0iMCptbPZV
ywEedSKkoAiTpg6rz/WgFNJzl8JYUoxYt5BXQD9wGAuV/pgqqjcxs/UAFdhU
5DbCVt2hLTTCwqj/1Qe+KowHeUvKXb5xnTkVAo6gDGRhHfphu6uK3cB5k24g
KWOUSyU2V9siNAt+9h65ePkqGM4JacS8pLOVVjuPfrQLxJ//riHH7CmoWFh0
ZYXozuxF5VZGQZeFTi2VbSeL6wvhT+15iusP7aRFkql5hn53RjzFpAkaLXem
SpVYa+SNe7L35Il44+jRfeWqeBkSN7ktWKWBKKxY7ROcQfD4fAKU9R0i5r9I
7Wt82YPslz//zvv8rr96RmFzgpp+tWMGYUe4Z2jMl/lmXmPoDNE0kaIZpZPw
6tMUKz6ghcMs3v6SdkJbNOScILSiJ+fEeY4BWnvb6ov4OvKj/1l7fSQ57yRm
tCqQqf9McCBKNezzYrSUzKuSFfpWcy0eUec68koAMUHv5HwhZqfw1/OwcJ6l
YGU12bJbZcHUetKnKTtJ61k8U/vM9dRzGoi2UC+VZ0HczYt0IAMTIkUqLDsn
xTf1pTv0Qe42+qC3RT4fUviRkfziP9JQTg+JxLP4PHccHy5XTFVLRxh077qY
eCvJx+p8OII7a6MRGnegX0IdPZJqlFTuFWzLL02+nkBoVLnec/pPj2GgWOd4
aV9gIIj+UYhzOHchuKje0ATHuV88D3fgWKPPHe6sb7vTx8Wpq6JGUHNRW+g4
4NY43rG9+xorvSVLInvXFpzUh3gEqsw60Hwz9gOaNng4ZC/q5LBu10MagsQb
fLPQ/L6h90uRNJbXxI/BUtDO6phIz9izy1C71sQpwyjSG5PoHMSFJslJjOG0
kN9i7VRZpWZNlqs0xhNleVs3pyiuqIytfRTFvGBuVSTtft46eWlip+Lls69k
wpFaQ6OwNaDzR5ycaQDIdPuzgj80Wge0Qb7aCT3FGM9X+2CIfvUAwzzCFCcv
DD9iwMZlOwgQznG3wo/F5vvLybfT8k35/Tfv/v7F7uvy+6ej0dP/8C6/+vXr
P1BVzEAk59ckO0d10cgCiMFtpmb5M89/4QROZnR4NR17dL++UjwxvJ6YcjWt
/57H65AstqtyhNYdp/mabaXKshHJGuDH1IQK+W1JnWfWNrLuVMpIUu55V3jk
KjoOZSdREUaGh6IP/powOltq5ImTzt/XFEshcaN3mkXZYrxZMMIbcqO5VXgU
Dg5VOzNwPW1NoxQcMLLZ9rZbKGBCxzx5gpb3RXeXyVW7O06XKlm2BGiTolDt
+vy8/HCPBIHveh4MbipfHHE9jtj9JfkqImzCvTLfrRJNonUKi50pMSW9TqRR
tsAkZpjZF0P8+llHn1LeeD9YpeJ5JaCThtO0gjP6JdaommDKDrEISyFm9q3x
z8pZ+lYKHLJIbrvkpRHGLNgrlmTM3c5RGuDv9CrYzkCJpoV1J9YMqG2yN8co
UMbPLIT+tqPIGTZSy+hDrQw8wBj+ulAnaE32UefQCqnKEU0EBx/5kSUTvRH/
AmfsB+mznUM1HEqeD6jPeIwrHNtlIekURhvkCQm8jh33p8muskxE7MBnnLv9
OqFvHXOXE7LWPMoVTSlZbfIoYyZ07HEPf55GAnrzmAZF5wvmSpOwxrL7OMFq
lG4tIn7IxlI8Ove9Zf5Ww3NhB1Y5XyP9Pk81fFZyEv5X4kjWUyPqgvjbJ3lb
PN5fN/NhUeG+nAmkjpE9s9QZ9AjlOOir+4/3nzA2Sao0iVxhJi/BfMExjeQO
vSS0XSWD/XMCPjEEG3r4ZA+c0T2Uofa6mJ+v/AIXFGO8Yg0B7e6essbyDZ41
ltcAHPLSgZ3BDjUC31idYedi52B/sFPvHDywzLHbyss2INOUJbiNFgK6NlW1
4JiBI7MrFwLB9coUQ8do5tEphV49HDX0iiy7zrQbBUS9k3768cnaPNE14jw5
ORjIkMqR0myYnFtx4q0SFlNhibCiyKrzaVRbud+E5E7qgYTyCBHJdQIKHmCl
CSHH6wPVUt0AKTyB2BRXKmOj118GUjY+I7eDr9KmGO4Udut8hnKSqWL5glST
woEtVqYOoSApmNswsUjCONo3wI5Bxwljzf1mclG3hVyU34rPC893yAnBWCE6
VHaK4TbK26YrhM/bl9CLtwxwxvbeFpebWaM1xOJjKCKToeDEeRbjnw0GdZEv
8dhBKynaluQoFS4WDrZ7D2f/SboFpv5CqXDG/pygopKWMX6MLXOi2uqSQQxZ
x+eNKz/OENkf7Y32YyimZBViSXRRAlr05gVGQ0W889FOsQs+K1jRmltCc28X
oKegTcj42N2aQtKhZdSoRVjTvlOGTH7YzQ7dsnOQfTvIdvgm+PDmE3cAC11S
6KbHuULSZ6yea+Z39qgqTCAqi5CDwGx9ZFrStMkCp5Si8BZcStqWR021NU4n
tEqWJpWLcuT6laPu/hciXgpsSK0W3jbEqOvsEZGvetaXUjmhDdKbCFAxDR/l
3uMewwgI7neknVIEVAW9wEB8I9tHk9EYMbVSAhdmHOy+QWKM0WNC0YCWE8Ui
wc6WtbI2dg09XPNciMsUWb3KyznOsRTJcXav2CfAAUZ5k4MtVtTAsJs5z+A4
qYWfHoyomorYdUhctzC9VbUTAUjhra7pwQ1J1InS+shMk7TAXqhOaU7S26pK
ETAqgCsiRqqMg3krK/P0dbVAn0KLcFbLRnNFOJZPRLOlcDGvsduLnO6rW596
YYEtP0Ez2wWje6YXOS15tRqqXR/fRtY5AbkQxVSIdwbVmMTi1yIWkVzGBEWR
hS9EjvOK+aQJs0l9INRWGpK1aWaTBsSPsqXrXr+qS9g0NE10M6Mcqa6cjdKz
lxfe3KMsRnYTUVoNnR4e2TCIEreIkyKgmFtcJ7Bbb6HBhu2N2Vhc8Yf5bPAl
GBZlUHoD9/u6rFQprZUXt+yjH2sCws4OErmL4wwtkPbpZb20mbbYch57a8gm
WTVzcc3BpeigGd+lIBRotOKS2xnc+DH7NLixVbHhi3tjpgBE7oz4J37DOPD8
hTeqKJc9O5MwIPpvybcQIVZ1fKkQszi71pLHiY5wg4AZ8aAyD9Ppu69Pj96+
+Pr4x7O3h0e/PsW3vf217o3FSNOy7mw0y/CojWzrotQpDINkMEmKLI00F91l
/0UXJVdrEghrukqPy69GIN1tcVjLcktehCSZr9ur2G+Hb2JQAGGMGfPqVZmB
JlX5n3pOQ16slgKhs5wH7K3v8yDYAw79gmSfiru3jFxzGk1MJ9sXQmuSEBK3
Msq+RoEkIpky7dr+98DtEvkYaIaN4OR6YeiQLMDY5KDYIgCCQoKhLmMx1b85
Pjv6zm92eVuX2Ymb9UQlBtl29VOWv8dqCVzXyLog2waSaUJQq+Ah8L5BUGFL
GnamYNQjo6fIjCWyQq9uEJ/Cx6wwviTIEfwaWzwTfsQEuOpjqngz2LsMJ/gS
E9y59mTG6qYv3tCGw0pjMhpPUUs1Fw0BxjoMwobiekab0bVIAr7wKV9quwv3
FbQGh9UVad0yFco3QNIti8Kruvape4gqjk2LpwkxDA0+H6B9rXB/fCtpIDeu
w55Awkaxg0JHHW5h/7qXTWZRR8goG63gAscSiAjReb9RkxrcfkSdWlmceEyF
Iw8V1GmpFkyNYc4uovrAXLq2rJw330Rr0mZXPreKlQQdEL5TKo8eqFR1+LNG
i8N2ezh6HFl7XHWlr/QnUsbQnGwF7t7hOfstlyNij+YPxeTMK5g3dyhAJvWK
WjGq9X0Yd0hqjq8MKpeyE0PvUxor2NGX9TVlkOKLb2Bai5VKX3mkYCWYITqy
2fcsqHPgovJDvJMMVrCRVMpV/h5GGgZkLZQtnPqnATvPNiL8QV7ZwyXkQ4u4
R1F+B6SEQZHhlp9O18uy8CQA2pihGyDugG7Be1BWhFmffVo+v/q6tqxGB9Qf
XBBp6RJlky2EIQh/ZxoZX2ojMTjMmm6Z+Yf9tPIsl2m8BKaw3Wh86NYCq1JT
gCs6II0W48qjCK9KUEp/wOQg9FutbGWqYPLJu6SKycjHWbNluYRznVgbOrBg
5QduCDjvb5ZJ31POgXgU9VliSm4bPCmmAFdP100TGiDtBWfBFjuhIUhr6lLV
Wn4/FlABkQJi6hzeqb0EdRRxyasS9onXXzArSB9WysHmB5qq8S0xJYg0HuTY
jgod1p6H3/fO10LqG2kZrIc4WFIw2VdFr0N93t+8e3Hkh1A7ouRscRaEXyuW
bCXvcMfzQEokjrVOfgoV8yQ6gSti0zPrZlFeNIGZ9sHw7RnJzCJv5pshenzp
LOcXIiUJ3gMlj7o9roeYB1tNN5IEChZTs176eTfSyOOBUQmytUlUPaAsBwrI
9oG8JGWFVSyBdkhZYkw21grFUeo4jk2JByAJjNoLtUSmWfPwUUIZ84NqyscM
8MIdJs/VI/wUTsBF4Rjns7f7BN9P342gtOEt2BFqczOjvZNJvSpbXEn2DomS
NYJJYaipBO5YX/8gW3/1YBwnCeGeXuTNe9ZmKX5PqUDzZ8nz+zdqZVkE0C6X
B+9mtPkuCHIJuidDfGEV4LEs19y9LC9wCZJq2LLqMlnP3/M5dc4cA4S69v1Y
iTdJVrlOJtVKvbKCAubQj4H41xBRmxx20Ryif5rd03pncEtLKNN5G2zLCEQF
SFTP0uYki5wu+IIRvs9sugObQ12EPB1aMTzYia3BB1sY9VBaF1vPPvJt8Etc
p0NWvtbc+5g94Cq1MQT5I8wifh3Aea9Qcx+wr4gRkXDRHtd2XUGXkA7CVFb9
mD3M+HFKV/4x26dvvoYhQCMM3uJj9oi/wpk/k5mHbx+j0vVllHKjr2kLufqt
fUbT65VnefEdIkNSmj9R0v2yaeVNI8ILFbucOKpWXSC0QLYQq3WLTBa/r4B1
mpzj8uRSPkdWDHKGumtP3yJd0uWFjsMFln9VWkvPqzL03V3UMySG6qL0WcpF
SqUao4kHLwJEdvJnmAiOkJSJOT2wacS6yyj5ky2e87wiSjpaq52AitWtO3Q4
eKU3Cpq1VuSN3sZ7+e4/hO37w/HXYPy/Ph1+9xC2LVZPQrtC8ujoHEtCN2me
UtS2z51qHcxvrha5D/CgOMcIy9Gb16+RFNAyJFRKCYIpPLgQnLe9+DtyjHIG
w8Q6IoJGaRyoKDDwKtfNPxEZtr0z5NP33ec56HtNFyWHxvlu/jgNQ0Iatah7
obcDFwWAw5sGfx7JRVgRhRzCWZzZcXMntlzh9UAZp3fxABEuGkCcb6zGEtdu
L9vqAcq938jdIDx+uKwzLUNfYn7kdyBHu4XEX1GBt7K1wDvYhUSXTPVuqEN/
LQWArJLxMZjoYhCTjS6lcbmhu5f1EhOi4D9czhp71XJAuOw4b0O9GDTa8Jlc
Giiuax1Z1WnhJ/WH3A3m+L04ZxG6+/egh23IVcdSFMf9JX8D3Y9maaen3FWo
+cDlKVe1UC9LrataefJMbtCop2w2LzMsgGbBBJ6zhGIJFCmWOhrOdAKDPHHF
QtGi1OqIAkURY7B3kMotSb4h73lQXN7gA8gYFgz+qn5fIEDtDSb5DOEHkDwy
/ONo0DS7Ghoh2HioH5lnZy9P/TmBSQaULouxN/MMr+ZOCs8kiUQgIHM51k9t
PT+pTwQwvr//FBXJ4OjirppUBGQa5MRBkioSgZtsvPyy8QvDp0iGHl1WK6KQ
Oi/HFVv9BCAg/gXh2kvdX2a7ol3QPRJSD5jGV/DSNjizZHQokJzxAHjnzc3N
q/o3w6P9VzISeeIB0IjRJHEGq9RF0fa+2HQXlqGbjNbwNk+YGCyowiXDwAEH
IfUjJ8glAjsGmc2Tibd3oJPvWtoxt7T12WR2ZHfT4zZBlHnfX+zMznxVelwK
FCDAcPZM4oVZr/SzuREx43HEBsBJQDhJcZAi+BiI8iS95QvNTKGouvX/YhyH
soUwgnCOwXCWssg0LnlFqY3ImIpirrxOEVumlDpFRYFWGbcs5Lc415YDh61Z
hb3KcCLBFF2kHvHTAPGSTbvnszyygPl/XsLMgtrP1zx6+ACuQQiqcvTFgi0A
x9DNQdqk9oo9gyRQp4HrjIBaBraZeti808C7/Xu89a8lXEBhbakapWA/TyGB
aJQe/y9tvb4ji31qOB8MFFusLsfJCk8CIA4PUzwtCfWAZ0+f8Id1G9jDfSnB
JSYttew09eTRzNJFbhpfobpTapEIe32JRFYgqAMf8XuvWWRRfUOsVFh1fDB8
S3/lv/4bJNCFSZADXyRGqxJ6UtEBV/gVI5+LgnUhMswXJCzvsDaeHx+9PHx7
HIoKZrao4Eg6eziHc6LKV1EJG/y6JV3YFG0ILnuc1DxmTUV5gEoWrcyk0pmd
ZR0i5pCedcaIqqoNhKybX/j47ds3b+W+17UvjSmv/jH7/s2L16HOcnneI2XU
7uPaYCVzFHB9Y/Vb59kYg/w/IvSK1il+GuInSl5t5O3hMnIM1E3C8L0fAwfl
NaloZfKOtr96XShqiVnwvkplfKNWwsN7UgVwSam+rP5R3RByPsqi1iWNyl/W
UzObA2S5RxOrHOyjcBqwF4i5vykLRS8jbNIq+wZdAPeYOsyAJYWAwGU+aRi5
FEIw2pN/1lneKrMMDESBxH2Ce+TyZVihl2OtotbMCk5ZLFIjvtRMYs2UeYTv
cgpisJyifHpXec85x+gS5uuoueE6XD3G8zJSHsTCEL2GlQU8WGGvXCGIw8fw
lMW6QMCEMH2mUjF2Q2IJREb2wJcCfeDwS2f340mrufXer8X128uYiqJldnRh
qKjjWtEKiPKmH5keiIJAX7rQhgyy369bKXDQ8Q5ouityJaCliv7d8kPERp/A
MVONUbiuqrraLLBidcfW1F+GqdV5iNYZ1hpDWy2cWFaXIQXXapNdbcZxsbbq
PQengnMw4Yf/QWvO9JlUtSMqD8HR5Zayjss7CLCyr8gQLV/h5Q82OC1jxMiA
BcGFPE6QZxWE20kezA1RNr58TBZNuwK7YeDyHi8OZxtoFdZ0Ph7asKH9ya5P
rnmfChVQOuFgqFCr9Vv8hBlhz8iWiRVNTKBvyZXu+/4lpj2dJRgF6DCB6+Co
R5xmIGWRN3dc2SWfyXEf49QYFUNQhGmmvESiUBg4dWZIQTFscTI8/BZO3FNM
XtobdcjNRU3CsyGaGLbZPIXxrGD0HjbP6qfamvRpTCMyJFB68lB+otVYpZfM
V8l+QQ6iK5vwQNjqOg6J1WVhFLSuhjZyD4V+m7tPLpNZUSwoSxch2ezC8Eqp
j4YJdUVNEsJJma5OrJAB86BxP+sz6ELelyKoPNqX1XQEkIZYAdl/hCf3Ua8e
4C2uM2ZkNRvR+HQI88criZga5VTRCrVWL/KaJRe9pdMq8JtlPjlmxU5DcyfH
JCUq1oHeMMGYEVWVi3RtzDpcTIKr4A2s4KsSxaLiFGoBJwyMBCH+Ic0dqETH
Z6U9qvJK1Z8riZFXxYrzNrhQARX6m6f8N/QyIk83EWqkFypCzsKkzzd3ak03
ePP8zQEldqSXsFn16Anxr1TZJRW2TEBw0l8n/e0UE1N+Cql2KvEC1iz9t2ol
UUffWv0EhMnh8PQF9jdvS6rDwB9vDuE/0LFA9nBdTLLDkxceS2bJzgX+QAlI
MKQ4hySHz5lgIkK5cUItM/NbAjZmBmIp7trLfOnRxUkdTY0pZBa6jIsEf2ff
MzlX+U0kuEQjrtfGoSXKt6QwEvLD3J3my5yKnZcY4eOfAwO5moWGWcbMRlyo
U2qckSOVTC77FAozyn34GLrAVAH9qdqfmYmKaa0+rxP5XzzlDNyrf+vNL/EQ
prmaYhQHKerJgxsitL0pUGm5A2rriFh4FKmuS4Wd0H249YEm8twCFKWGf0vg
alwzGN6vA8x6kC3WH1BqS4HnYiaPixSAnrhMFfRYDYLUYWPn4hDsMnFQdw6W
iEUbZAecGwWPfDGbG6JpDq1uqik0V6k2R8NIJq6xi4yF05aBl4/WrEbCwsqV
cNgOB8D4KiWzJbztdT3kigSGtk8SVGztVt5d8cblqxJfEz6elqvQjRIlO/nL
6eEOxC7VmV8ipbj7K5iM+aqULojyiOF44zxEFAuzwkgJNll8qIR6OjK6yVJR
6sFJ+Aj2Ca1XqFwq45q8mQbgLetZXPgwoi0I4Qbd0FiAng0WyiAy+F2LcZAZ
5oLinanwy3har+cz9EdDx1l9MkRzs2jThsBUmHumEBWThaqDEiObEmGQGAdt
dU0h1iMQ5bA15JBm/aDVH6fRjwwlEOyAEBuYo2h398GnT5Rtt2HzRIQIkldk
ZxTWuLnT5TFKGbmWpGurDSJExVr0p2Xr9EBgSOoowos0XsKoZT/8JbteoxMa
ZmDDeCOO5lDjLuQUkIdzxYSl6Fxd5fP3ZAfCh4WejVVSdYBqezH7vG9dqqew
Y6KYt8WB0JqCVrRCcACcpqWHxtth+Gvh4hTZ3Y3kEUcNTRLNBEckg+PcrFx1
z0u1BfSUwP/8utiIJh45Mm1ybpo00j4T3LWksxcr8sqwBK+r81JUGsGnKCga
HzjgUKvBSQvXVbSZ8ACpZsNVPSyoX/718bROMuuVeYtZlakmvW8+MdR2Y9fT
R19DakDwS1QlWo1PI/yNzvjsd4WIGBhXqYsGp3kYDIWZ8+Ai0SWWQDLFUaeX
nNlzzus60jCoG6+0CEBiiEGniPqOjq16zgcFdAePi+qSqTiwQCe39ixVDC8J
yJZoqhw/UT04OkDCXoxcZJED562saXwvu62/qZudTvUtCedxUCNmdjTapJbw
RB+J5ygLo4c+Eq+ltTKbLYoGQZTkHtSL2FMbLeWNyxIidSlHTgQukVcTAWKw
1PqZD2QjBb1dqgBXDDgcuBnsah/6RFPXJClhbCJ45EAqYE8aQzq+8KUqeVeV
NZ+Ly60huMSCUnBFYmlgtY3+ja7ppxR4CIZzTKmwLRpBp6eRKZ54W0q8wEtQ
YR2b6Z8wnspBG78gkdljL0yqRbOeM4g1mlB8ZzXbFa2KM7DENdQUtI+LmXDF
L1nBSyMI8JsPImAbl2gEU6LeBQLjGsIn5/OoN5FX+2HqijzuXXPBiW5nwJsC
KkcwtlODnHHM6knWV+EREWKZ+/ClkIDytnG3+0g7/iffSnSMki7R43egjcz5
uIZO0GxkrenHqZfqMfcnkJJqwPpksi7PahkHJ2Q8msJRNFMqlxu/8GUu/Aya
SWXHU7VT+nlIQVDNlkgHx3hSeWykeKgeNkJeLbar6YBnJYXpFT+2au2U8ipr
FdkP5kXCSMsbm8r8NRdqecjK9A4onyvq/MpMd/qsnAljezUbbRG96mFHiBT6
nXQlklJTkZ1f5I1Je3GCvo4QtuoI6qGpkWT3UllL91yoXo1vhuyjd4V+9J53
SXH5P8mq94XoQlibV3hezqXKl5p9hKzR1ZYztQ3VjOisVRGf1KhPC12ULUVu
WRxQILS68GMiqzt1DNmlfkAp72yyWBe0ZARwVrw3AQU7knBwd5zLPZA3OVFY
iaQqBKnnfAvFqHgqR0JuDa84KS5z0AkaA27x+lqn7PscSwSR9CQuQOeXowhS
M1ziQopWtp44TCni0qxj0a+5rK5SifnmUAHXby2jN5fTxmxR+JGnXF6YKL5x
t5NWhrOqxMhElNjxHoYCZXzclgxh4Ai5iGa+iXLVC6VqT32w4ipkg4SPGqtW
KIqWOkHablVLaH0g6Ro/Hh792h9JGw+17uUkVi0ClzIfWNF5RZoHJ724xF1J
jotKji4eLFjJ5dwuGinXKQszaoEKrvshMQoGTzPSN3CxomQNOss1O0hvp6Kh
tkoor41oHcEUOgqIDecUcrDKFhumV2VbknNNRS0J9/AteRwNNi/pYVq33D6e
lbRYW2U7XEqAMBCo782z+M2jd5KkUs/r67zhQlgVQ3HYdWcZU8KTsDuxddDe
CHbTLQYPAUjpPPN0wZgmRKJI4lpRVFNPd/bsSWZb1jf4jkIHXNFXVBY9b3q2
TT6p16tIemIZAdgntKpYOWYIX0ini8Fht3Esswu5kU7OC68vuluiKEb8jWJz
R45RXJCmC5lGrmCZgFY9CLG7bTo2zNdWJVoYiLtwxyhKyVhH7+SxvQl4R0Lz
MKRaZL1qFmgZmciJfwEQTfQGhpsCpgmlOD58QJNhmskmG8dVYPNZiMTa8XPu
hSk4oE5+GnzeplPhiKR6iXjuUbw4Lqp8b9A58BCQjQVVbUmOmFKD94hS7Du1
7ATGPdn44s7iN4zttshg87Erh14vc3TYJwpwSBZTTj58xJeAkTMgWY3YHAa6
pVXvOa1WDgPvZpINQvu/5EpjiIsW54DjTB/Q0osPfIBZNUGOtGuOntu1DnJw
npMJBNILvXJNfeXrHQstnikHi/rC/Dwx0hINS3lLuNY3Q6lWRFTRlO371rOQ
4RNUhzJODxC/nODBpjQzluipKeXBCM3IcJa20GqalE5/IrU2b+4gg+BQSm92
vIeGIDxKly+5WmfB+CY9/yPp4H9nRlQE0qgbssVDAxTW/KIpikHnXKFEAAyq
m2euulPCksdrO/MNWUPOJ0NJMNwXZrZUIoR8yhewf1cKkx1wcJd657w6sPJA
dSZW5NiaqmgFFZ+mmndqmfu4i1OmPSKmoETlXBPMK1HICy301hGrOXNtOHmW
cmLj/Uym2oVWZt0jmru7coWE0T0DF5Z7k7DCYlJerOEU4lPJ2OYlgTUWOCN7
/+nRw2yY7SbFqR/EaTE0nOj5m07xr6xaE2CCzVgeMk7Vy3yeEDMGkpaxyKlm
/eP94aQknMO05BpGjZr8M0SVtET93WoiR7zDgu4qbJjcBS4oRHvb8TQaqj2a
8RlvjWNMRs2eI1Dj5o7JTAV16eVptjt6mNGXGX458PB2n++syWP393gV4E34
nV7z0FHaa+c8GGVRJQEEVlHKJHJr+OcFgIWLNoX6kFk1ZRNlWsCBRv7Ku4z2
VKij+Gxc7Cl4eXz42+NBwHAK6rMXHMrSFvUgFwfRzNLYjTUmWuGIcCS+3qSe
ixMtQohy+GAIiczRCPjRAelLCQ+lujXooMPhxtJ+7SXi49T+aMncVEACpcAr
Pi5cvKqdXs8GhQXy7e89yu6e1TUvj3tCJ7L/5QMlGMbCBJii7Y6SaMHAh3yl
cpNJfRMqQqWTxD0SSoxzSMBWxGYn7pYUwpF4kaUIFI1TSMrNpaTFrJ6uybEv
7eJwiyJEIa0ZF+iGQ19q961UUR+EvMikeqZZsIj3zrUEuA91103sBZEqr54D
WxJC3voUWDIIl+v53FEldY2MyQrCcD2VXpL8s1tqQhDzs8Q3jj9cglggRJQ7
jhJ9cZwR6MNGUlpsSDRX1spxCkSggCZq2AXi1GHEB5kalbbWJ/m+EFnH98eR
pe2y1brxhbBTRYEPdEtP2ecbqo2SccYp30spaoinSbwFTSo3P6DjqKIJCNVI
g2K6qUnrap3nOsXnlPWsp7iHptIjglC47QVO2BcY7QUA8vsJVWfZOu9B7Fub
iCFVQQLrxmcuaGk58U/xTzrCtxW6fA7yut4sAnaVM9Fqx+sDY+eUrOHNHbAn
ilZj1lS3z66GZV4y/TZoLfD90EdcewMmA5vij33ObJ1NpvGMFDAUcnn7HkaF
S62SnJBMMdLpVfKiphi9tiPhs2YmJFvONkyyLK5c3VURt1oHFUc7lsNI3ZJT
SWjNmcAaMwsevj7sxNVhJVEyeYYVG7AeHdVZCQrRJ6lM62Wex9Q2xUWJxqFN
uGTXEfvllKS4VZKgHfOgHb2dY/J3olIRiOcm1n14NrLza7kVS7HhTteTlf3R
3OTLnniyYIJev75/6JxWde/77RjnnrIYo0HC32F/YEreXdEZ6eT6cv/pQ1SV
3p19M3xyD3rUD0/A20+5jOk2eIMPKPpRFmGtsAayY6GvFJsUZ0f3KaEIvRR0
Diq7YJUpHWJks6DwQZc5V1K5otRC69jpkl/nvURgXFVWE5yII4i4qLtpS86d
eK41PZa5CBhlDZkxiAhEZZMxkwMRhOjyIlC9IG+QnTLe31rMMbdlJGMQUkjd
/6bJOWBvqnf2zCVuYCHI7ikbISXXHj2lWTuU2usED/XiA5t5jhgahu3k8xKz
JyhVhVUqjBlRBRVYl6PsVX4BugufmHfbe/wtDPI3iPH0Zaz8L3D9FCR4DQLz
HK+gbYJSLdzrTmCVSAQDiU/nKjQoq4C9A9QVxTYlnT9dY8zrNTJNvF+DgpT9
EvQU+vA3U+SYGMGi+RWvWcqSX+PJjDcevXn16s1rYiSnVANe/VW4gDYipw30
PQhUQ3YtBB8uXvbi+OybfjkyDLqglw4oeCifPSZVXBWwQjjyH0+sFy1jJTk8
6Jc/3Yf9zCW8ZemKg1g5ToNya0hXUZLTeuYaVq9pNYk4l7JZf6QoPxdyPg6j
7Hy3QZQQAjM9SYgviHwXe3DPdCF7K2J+hyBG5gdiKkHm3Y+2ABfJe8Qf+fLJ
vfWSzSELV2MaYV4xpsfU9fqI7PQ4KwruIh0EiSpSaeubfAmXnWgsMW74BSwP
ahJVP3Ic3dIO19u4tWcKCO1r5eZAIS/JjOpw8vQjxGXc6fdYeMypw53aZgyv
YOOdrnNSVexge1BVVkRBTNUeiK/RU1LgiwZrgRBpPRahVDR2rFVQUck/chEW
ltsZVmHPY4JOYeteHuCOl8te273KE+Dc88JnN/Ehei6hmB4gL6nvBu5ItRVk
qeLNt0zrtm6gNfYTnQhs8CsPzqBOeF8AZ3y09ZzzGCije1sPTYpkTyfJsqgn
cFLyoG6dLloHpFIK6DvPlAjI3L7j/JyINbTjhQWeLwJBrxeLdaVh9WNxKGd3
sb17O45YYk1Y49TqDaHIHeeLesA91dWhJYuBJdKXOSmVMwXTCglP4tx9Uy0V
r0Y3DW1JIcvLfIF3n+hDL01HAtrWXGOMn2+LHLgxquTtwf37uCVGdXNxn6v0
kDXE1UyLpqmb9s4NPxrLBDiQe1R/C/X4YyHJ+IbyYm/uiKNW+Sr1IxiVQlql
O/uKbY7Wb2i90vv/UGcZPx/HJNmYUDX+nPpwWA/g5vknpENxOZel1QMsEOLm
hkItgEERBzyZNMVVSRoRL/yycTSe7JbfaOLYqJf0QE4pbKnmPDJB+wpWG+MX
GXK189Ri7XPHq+8wuxu0iXsK7iZPPdl9mE1CF37N5y3cOoK/fZ1whVTcjTM6
UNfFWjRp+z/97+vsrtEB7lGy8R/3T7LhOQ0jKpWbMdoJ3ivD2mCSjTK7lw3l
36/o3l8OCTOzrVIvzPagW8gr48z7X36l/7LTU9BbZge7/NCvbv338TPe92tP
GM4O2eh9u8/d08t+8rm9Y4WvmWlSPY7YLo4Y8wXQgJmx2usqEgfZQz+qPf+2
9PmhPvBPHavPWxv5Xp6BeVrNlCnD6lgH0KGvnhOZ9Ve7WfS+D3qm/y6WRqCt
8/+1djWtbQNB9K5fsbgHN6C45APS+ha7pS4UGkLulmM7qQ+VTWRRSv989d7M
7M7KSqHQqy2tdmd2Zj9m5r32sIElnYX+eP9Ln091lPJQoKZL/9lMR39Rx7/o
6Npf6OvgOStzHUUKSsglgythWZ5CzfoCSTw5SIIxiaS5p060x3dF0mSCrgvt
bzznRGdsl+5C/NQtV+BxeADDg1Y4L9pHK0/Te/HoMhHHblJknbC639vHMix0
hdwwCZ5NOtKIsqiemnP8EKFIYsjCH2xIRXlouyMsL68nLFe+1QtYOpG3dF0g
EtL2kgsD9v3Yqr1dqRnOzGGRghLwbD0oA0oN9cKLiO/p+oWW4/fGjfRtilar
38pvsNxtRtMRVkvQj5aj5PnlH2EzW42QHRxGumLIX9pwpEpYti+77mfbLzia
1VPSc3KdSh1wEsjnTw9Nb2zMFah7Fb4SAJYAl6Aj6eDFaybBq0ei6C+86NUX
ToprxnBpA6r8ipcy79bdLKsy+cli2iNMKQ2KJ7tIpf9JQhU/lAieYp2SHRp3
rNeulkhWqLxEpCbCMH3zeAqLlfRMhLcH8GAMEZt4dmI9XyJ+LjcYXxEBuW9r
YjXDsohssGo8pjSkAnGE6vmC0HHd5vGZly9dDyrszL2ANOAZ2UI7K38J6xaJ
z3VuFoq9nBdaQudS8JiDz5aC7s6RJoD30pWl67S22sZuJv5YH7rJqQ5M5uzz
BaZd+FZrP0sfXxP4ZK1YH0RQlshxhEeWMDAdlRMWGojOEdC0vxzyMkANL08z
yW17oDJx+Z4MdoKYJAmaLAo9mxDf5LWhWY9Hj2cLc3OPGK4pRmBfFnacytcE
wxpYC7jdkMVF1gxm4s7vHMx44qo9v7+bBx4LRENe4cjeRCPChCplhKEChfyh
a1/Y/7ZH45E38E5Dyn4a+C7TCw38r4h95ZMSDH8VYh+hQlZt0BxI3wWjaHDG
i5jrxcxFKyzs7tHj8zwOYFh9rJSQbdUcC41abw15+WeCNcovLm7KuMzixUh6
VeTZGVdiRzPGcNhLuYgb8p/RPb1OYyugNFl98TTcnNKj6bwmtgKVZ3cc79nC
h6mDcqLLvT4Lyv+px+borufj6KxhDTOdIHligbgBCGJpglgmQVTdLpXeDe3V
+3iydcmyrlHrkBnKLC3je2P/S5j9HvnRoc0Def0KvSUkRM6nddxLAlqwVEze
xjAMJwo3iixxMJFtDcxvu/rQHtOEwtMr0kVlCfu7+slIrJT4diB78E24XQOF
opv+kt8qyAfFH28ACmrCdAEA

-->

</rfc>
