<?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-01" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="PACE">PACE: Protocol for Agent Communication Exchange</title>
    <seriesInfo name="Internet-Draft" value="draft-nandakumar-agentproto-pace-01"/>
    <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>MOQT</keyword>
    <keyword>AI agents</keyword>
    <keyword>dialog management</keyword>
    <keyword>real-time communication</keyword>
    <abstract>
      <?line 205?>

<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>
    <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/draft-nandakumar-agentproto-pace.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-nandakumar-agentproto-pace/"/>.
      </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"/>.</t>
    </note>
  </front>
  <middle>
    <?line 224?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>AI agents are autonomous software systems that work with users, other
agents, and tools to complete tasks. The exchanges between them form
dialogs. A dialog is the correlated
sequence of interactions between two or more participants over the
course of a task. For dialogs to work across platforms and vendors,
participants need a common way to correlate a dialog and maintain its
lifecycle across multiple hops, intermediaries, trust boundaries, and
changes of modality or network attachment, without sharing the
content of the dialog itself.</t>
      <t>This document defines the Protocol for Agent Communication Exchange
(PACE). PACE has two parts:</t>
      <ul spacing="normal">
        <li>
          <t>A transport-independent agentic dialog management protocol
(<xref target="dialog-management"/>): the dialog context, the control operations
that manage its lifecycle, and the rules participants and
intermediaries follow when propagating it.</t>
        </li>
        <li>
          <t>A binding of that protocol to Media over QUIC Transport (MOQT)
<xref target="MoQ-TRANSPORT"/> (<xref target="moqt-binding"/>, <xref target="dialog-over-moqt"/>), which
carries the dialog context on MOQT tracks and uses MOQT relays for
fan-out, prioritization, and multiplexing of dialog control
alongside text, audio, video, and request/response exchanges.</t>
        </li>
      </ul>
      <t>In terms of the Agent Communication Protocol architecture <xref target="ARCH"/>, the
first part realizes the Agentic Dialog Management block
(<xref section="6.1" sectionFormat="of" target="ARCH"/>), and the second is the MOQT profile corresponding
to <xref section="9.1" sectionFormat="of" target="ARCH"/>.</t>
      <t>The dialog context consists of identifiers and lifecycle state only.
Content exchanged with AI models, such as conversation memory,
retrieved documents, or prompts, is not part of it.
The content is opaque to PACE, the MOQT binding carries it on content
tracks without interpreting it. PACE
does not replace application-layer agent protocols. A2A, MCP, AutoGen, and
similar protocols keep their native messages and carry the dialog
context through their own extension points (<xref target="protocol-bindings"/>).</t>
      <section anchor="scope">
        <name>Scope and Goals</name>
        <t>Agent interactions are increasingly live dialogs rather than one-shot
requests. A user speaks while an agent answers, cuts in, and expects
the agent to stop. Voice and video run alongside chat, streaming model
output, and tool calls. Several agents and people work on the same
task, and the task can outlast a single connection or network. In
natural spoken conversation, people take turns within a few hundred
milliseconds <xref target="STIVERS"/>, so an interruption has to take effect ahead of output
that is already queued. PACE is designed for these dialogs.</t>
        <t>PACE addresses the following goals.</t>
        <ul spacing="normal">
          <li>
            <t>Dialog correlation: A dialog identifier that stays stable across hops,
intermediaries, trust boundaries, modality changes, and time. Defined
by the dialog context: identifier, generation, state, controller, and
participants (<xref target="dialog-context"/>).</t>
          </li>
          <li>
            <t>Multi-modal exchange: Real-time media, chat, streaming model output,
and request/response operations in one dialog. Each modality keeps its
own latency and reliability, and none of them delays the others, even
when they share one transport session (<xref target="data-exchange"/>).</t>
          </li>
          <li>
            <t>Multi-party exchange: Point-to-point, point-to-multipoint, and
multi-party dialogs among agents and people. Relays fan out each
message, so a sender publishes once however many participants there
are, and late joiners catch up from relay caches (<xref target="topologies"/>).</t>
          </li>
          <li>
            <t>Low-latency interaction: Dialog control, including interruption and
cancellation, takes effect within the latency of natural conversation
and ahead of queued content, so that agents can hold an interactive
voice conversation (<xref target="data-exchange"/>).</t>
          </li>
          <li>
            <t>Dialog lifecycle: Opening, updating, and terminating dialogs, and
revoking propagation relationships, with the controller as the single
authoritative source of state (<xref target="lifecycle"/>).</t>
          </li>
          <li>
            <t>Resilience: Recovery from path and intermediary failures, resumption
after interruption, and defined behavior when a participant or the
controller is unreachable (<xref target="propagation"/>, <xref target="dialog-recovery"/>).</t>
          </li>
          <li>
            <t>Transport independence: A dialog model that any transport can carry.
This document specifies a MOQT binding: namespaces, tracks, operation
mapping, and delivery (<xref target="moqt-binding"/>).</t>
          </li>
          <li>
            <t>Application protocol reuse: MCP, the Personal Agent Protocol, AutoGen,
and A2A keep their native messages and carry the dialog context
(<xref target="protocol-bindings"/>).</t>
          </li>
          <li>
            <t>Identity and authorization reuse: Agent identity separate from user
identity, delegated authorization, and selective disclosure, without
mandating a token format (<xref target="identity-discovery"/>, <xref target="authorization"/>).</t>
          </li>
          <li>
            <t>Privacy: Mitigations for linkage through persistent dialog and
participant identifiers (<xref target="privacy"/>).</t>
          </li>
        </ul>
        <t>PACE does not define trust frameworks,
authorization protocols, or audit data structures; deployments use
existing mechanisms, and auditing systems can use dialog identifiers.
The authority agents exercise in a dialog, delegating work and
approving single actions, is specified in PACE Authorization
<xref target="PACE-AUTHZ"/>.
Dialog content, model behavior, planning, and task semantics are also
out of scope.</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>
        <dl>
          <dt>Dialog:</dt>
          <dd>
            <t>The correlated sequence of interactions between two or more
participants over the course of a task. A dialog can outlast any
single message exchange, MOQT session, or transport connection. A
two-party dialog is an agentic dialog <xref target="ARCH"/>, which
composes larger topologies by cascading two-party dialogs; PACE
supports both cascaded and multi-party dialogs (<xref target="topologies"/>).</t>
          </dd>
          <dt>Dialog context:</dt>
          <dd>
            <t>The identifiers and lifecycle state needed to correlate and
maintain a dialog (<xref target="dialog-context"/>). The dialog context does not
include content exchanged with AI models, such as conversation
memory, retrieved documents, prompts, or media payloads. It
corresponds to the meta-data of the <xref target="ARCH"/> dialog context.</t>
          </dd>
          <dt>Log:</dt>
          <dd>
            <t>The content of a dialog: the inputs and outputs its participants
exchange, as an ordered sequence of log entries per flow
(<xref target="dialog-log"/>). It corresponds to the log of the <xref target="ARCH"/> dialog
context. Entry content is opaque to PACE; entry metadata is not.</t>
          </dd>
          <dt>Flow:</dt>
          <dd>
            <t>An ordered sequence of log entries that one participant sends in a
dialog, with a single output class and delivery class, such as one
participant's chat or audio. A binding defines how flows are named;
in the MOQT binding, a flow is a track (<xref target="log-over-moqt"/>).</t>
          </dd>
          <dt>Log position:</dt>
          <dd>
            <t>A value that orders the entries of one flow. Positions increase
with each entry but need not be contiguous.</t>
          </dd>
          <dt>Dialog identifier (dialog-id):</dt>
          <dd>
            <t>A UUID that names a dialog for its whole lifetime.</t>
          </dd>
          <dt>Participant:</dt>
          <dd>
            <t>A user-facing client, agent, tool, or service that takes part in a
dialog and processes its dialog context. Each participant has a
participant identifier that is unique within the dialog. In the
MOQT binding, the participant identifier is the agent-id field of
the participant's tracks in the dialog namespace (<xref target="namespace"/>). A participant plays the
principal or agent role of <xref target="ARCH"/>; the controller is usually the
principal's client.</t>
          </dd>
          <dt>Principal:</dt>
          <dd>
            <t>The user, workload, or organization on whose behalf a dialog runs
and from whom an agent's authority derives, corresponding to the
principal role of <xref target="ARCH"/>. A principal takes part through a
participant, usually its client, or through an agent that acts for
it; in a credential, the principal is the subject, not the agent
presenting it (<xref target="identity-discovery"/>).</t>
          </dd>
          <dt>Invitee:</dt>
          <dd>
            <t>A participant in state <tt>invited</tt>: named in OPEN, or added by UPDATE,
that has not yet answered with ACCEPT or REJECT
(<xref target="participant-states"/>).</t>
          </dd>
          <dt>Controller:</dt>
          <dd>
            <t>The participant named by <tt>controller_id</tt> in the dialog context:
initially the participant that opened the dialog, later an alternate
controller that took over (<xref target="controller-transfer"/>). The controller
is the authoritative source of the dialog context and the only
participant that changes the participant set, expiration,
generation, or terminal state.</t>
          </dd>
          <dt>Intermediary:</dt>
          <dd>
            <t>An entity that forwards dialog context between participants without
being the source of it. A MOQT relay that forwards PACE tracks is an
intermediary, and so is a gateway that transforms one modality into
another.</t>
          </dd>
          <dt>Dialog host:</dt>
          <dd>
            <t>An intermediary that keeps a dialog's control messages and delivers
them to its participants, in a binding where participants do not
exchange them directly, such as a binding over HTTP. Unlike a relay,
which forwards messages as they arrive, a dialog host stores them and
serves them on request. A participant can also be the dialog host.</t>
          </dd>
          <dt>Propagation relationship:</dt>
          <dd>
            <t>The authorization and forwarding relationship that allows a
participant or intermediary to receive or forward a dialog's
context. PACE signals the creation and revocation of such
relationships; the deployment's authorization mechanism enforces
them.</t>
          </dd>
          <dt>Participant descriptor:</dt>
          <dd>
            <t>Optional members of a participant's entry in the dialog context that
say what kind of party it is, whom it acts for, how it was
authenticated and by whom, what it may receive, and what it has
consented to (<xref target="participant-descriptors"/>).</t>
          </dd>
          <dt>Posture:</dt>
          <dd>
            <t>Whether a participant treats the dialog as cooperative or
adversarial (<xref target="posture"/>). Posture describes incentives, not
hostility <xref target="DIALOG-UC"/>.</t>
          </dd>
          <dt>Segment:</dt>
          <dd>
            <t>A span of a dialog whose content reaches only named participants,
while the others learn that it happened and its result
(<xref target="segments"/>).</t>
          </dd>
          <dt>MOQT session:</dt>
          <dd>
            <t>A transport-level session established with MOQT SETUP. A MOQT
session is not a dialog: one dialog can span several MOQT sessions,
and one MOQT session can carry several dialogs.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="architecture-overview">
      <name>Architecture Overview</name>
      <t>The PACE architecture layers as follows:</t>
      <figure anchor="_figure-arch">
        <name>PACE Architecture</name>
        <artwork><![CDATA[
┌─────────────────────────────────────────────────────────┐
│  Application Protocols (A2A, MCP, AutoGen, Poppy, ...)  │
├─────────────────────────────────────────────────────────┤
│  PACE Dialog Management: dialog-id │ lifecycle │        │
│  propagation                                            │
├─────────────────────────────────────────────────────────┤
│  PACE MOQT Binding: namespaces │ control tracks │       │
│  media and operation tracks │ priority                  │
├─────────────────────────────────────────────────────────┤
│  MOQT: Pub/Sub │ Namespace Routing │ Relay Caching      │
├─────────────────────────────────────────────────────────┤
│  QUIC / WebTransport: TLS 1.3 │ Mux │ Migration         │
└─────────────────────────────────────────────────────────┘
]]></artwork>
      </figure>
      <t>Identity, authentication, authorization, and encryption are building
blocks used across these layers. PACE integrates them
(<xref target="identity-discovery"/>, <xref target="authorization"/>) but does not define new
ones.</t>
      <section anchor="transport-requirements">
        <name>Transport Requirements</name>
        <t>Live dialogs (<xref target="scope"/>) place the following requirements on the
transport that carries them. They refine the transport aspects of
<xref section="8" sectionFormat="of" target="ARCH"/> for live, multi-modal dialogs.</t>
        <ul spacing="normal">
          <li>
            <t>Low latency: Each flow reaches participants within the latency its
modality needs: under 100 ms for real-time media, and under a second
for chat and streaming model output (<xref target="data-exchange"/>). A loss or a
backlog on one flow does not add delay to another.</t>
          </li>
          <li>
            <t>Push delivery: Content, new participants, new flows, and new dialogs
reach participants as soon as they are published, without polling.</t>
          </li>
          <li>
            <t>Interruption: Dialog control, such as an interruption or a
cancellation, reaches its receiver ahead of content that is already
queued. Real-time content that is too late to be useful is dropped
instead of being delivered late.</t>
          </li>
          <li>
            <t>Concurrent flows: Real-time media, chat, streaming model output, tool
calls, and bulk transfers share one dialog and one connection, each
with its own priority and reliability.</t>
          </li>
          <li>
            <t>Fan-out: One message reaches every participant without the sender
sending a copy to each. Participants that join late or reconnect can
catch up.</t>
          </li>
          <li>
            <t>Continuity: A dialog survives connection migration, network changes,
reconnection, and intermediaries.</t>
          </li>
          <li>
            <t>Scale and control: Dialogs scale through intermediaries across
regions, and each intermediary enforces who may send and receive.</t>
          </li>
        </ul>
        <t>Request/response mechanisms might not meet these requirements. When a
dialog's flows share one ordered connection, a cancellation waits
behind output that has already been sent, and one lost packet stalls
every flow. Delivery to several participants, and learning about new
ones, are left to the application.</t>
      </section>
      <section anchor="why-moqt">
        <name>Why MOQT?</name>
        <t>This document specifies a MOQT binding for exchanging dialogs. Other
documents can bind the same dialogs to HTTP for agents that cannot use
MOQT. Media
over QUIC Transport (MOQT) <xref target="MoQ-TRANSPORT"/> is a publish/subscribe
protocol over QUIC <xref target="RFC9000"/>. It meets each requirement in
<xref target="transport-requirements"/> with a transport mechanism, so agent
protocols do not need to rebuild them.</t>
        <ul spacing="normal">
          <li>
            <t>Low latency: Objects are sent as soon as they are produced, on QUIC
streams or datagrams alike, and relays forward them as they arrive,
without waiting for the rest of a group. Each track has its own
streams, so a loss on one flow does not hold up the others. Datagrams
are not retransmitted, so real-time media keeps flowing under
congestion instead of waiting for lost data.</t>
          </li>
          <li>
            <t>Push delivery: Agents publish and subscribe directly, with no polling
and no long-lived HTTP connections. Content reaches subscribers as
soon as it is published. SUBSCRIBE_TRACKS on a namespace prefix
delivers all current and future tracks under that prefix, so new
participants and flows appear without a separate signaling channel. Output
that arrives minutes or hours after its input reaches the subscriber
without a webhook or a client-side HTTP server.</t>
          </li>
          <li>
            <t>Interruption: Publisher priority (per subgroup or datagram) and
subscriber priority (per subscription) let dialog control overtake
queued lower-priority data, so a cancellation reaches the agent ahead
of output already in flight. Per-track delivery timeouts let the
publisher mark time-sensitive objects: objects that miss the deadline,
such as a voice frame whose playout window has passed, are dropped at
the relay instead of wasting bandwidth and queue depth.</t>
          </li>
          <li>
            <t>Concurrent flows: One MOQT session carries sub-100ms media, sub-second
chat, and best-effort bulk transfers at the same time, in one
congestion control context. Objects can be delivered over QUIC
datagrams, which suit real-time audio and video where lower latency
matters more than retransmission, or over QUIC streams, which suit
agent chat, operations, and bulk transfers that need ordered, reliable
delivery.</t>
          </li>
          <li>
            <t>Fan-out: A single PUBLISH reaches every subscriber through the relay,
so multi-agent collaboration does not need application-level broadcast
code, and the publisher keeps no per-subscriber state. Relay caches
let late-joining or reconnecting agents catch up without the publisher
retransmitting.</t>
          </li>
          <li>
            <t>Continuity: QUIC provides connection migration (for example, from
Wi-Fi to cellular) and 0-RTT resumption. A dialog is not tied to a
MOQT session: one dialog can span several sessions (<xref target="terminology"/>).
An agent namespace is not tied to a host either, so the principal and
the agent can each move between hosts over a dialog's lifetime and a
new client instance catches up from relay caches.</t>
          </li>
          <li>
            <t>Scale and control: Relays handle NAT traversal, load balancing, and
fan-out without direct peer-to-peer connections, and they can be
stacked hierarchically to spread load across regions without an
all-to-all mesh. Namespace-level access control maps onto agent
authorization scopes: the relay decides who may publish or subscribe
to each namespace. QUIC provides TLS 1.3 for every hop.</t>
          </li>
        </ul>
        <t>Where UDP is blocked, the same MOQT binding can run over QMux
<xref target="QMUX"/>, which provides QUIC stream and datagram operations over TLS
over TCP. Agents keep one protocol stack instead of falling back to a
separate one, at the cost of TCP head-of-line blocking and reliable,
ordered datagrams.</t>
      </section>
    </section>
    <section anchor="dialog-management">
      <name>Agentic Dialog Management</name>
      <t>This section defines the dialog context, its lifecycle, and the rules
for propagating it. The mapping of this protocol onto MOQT is defined
in <xref target="moqt-binding"/>.</t>
      <section anchor="dialog-overview">
        <name>Overview</name>
        <t>A dialog has one controller, which holds the authoritative dialog
context: the dialog's identifier, its state, its participants and
their states, and a generation number. Other participants read that
context and send requests; only the controller changes it.</t>
        <t>Every change works the same way. A participant sends a request, such
as ACCEPT to answer an invitation, LEAVE, or DECLARE to state what
kind of party it is. The controller decides whether to apply it and,
if it does, publishes UPDATE with the complete new context at the next
generation. Receivers replace their copy of the context with each
UPDATE instead of merging changes, and use the generation to detect a
missed or stale update (<xref target="generations"/>).</t>
        <t>The dialog is <tt>pending</tt> until an invitee accepts, then <tt>active</tt>, and
finally <tt>terminated</tt> (<xref target="lifecycle"/>). Each participant has its own
state: <tt>invited</tt>, then <tt>active</tt>, and then <tt>left</tt>, <tt>rejected</tt>, or
<tt>revoked</tt> (<xref target="participant-states"/>). A participant leaving does not by
itself end the dialog.</t>
        <t>A two-party dialog opens as follows:</t>
        <figure anchor="_figure-dialog-overview">
          <name>Opening a Two-Party Dialog</name>
          <artwork><![CDATA[
  A (controller)                                         B
    |  OPEN    gen 0, pending, A active, B invited        |
    |---------------------------------------------------->|
    |  ACCEPT  in_reply_to: the OPEN                      |
    |<----------------------------------------------------|
    |  UPDATE  gen 1, active, A active, B active          |
    |---------------------------------------------------->|
    |                                                     |
    |      content: entries of the dialog log             |
    |<===================================================>|
]]></artwork>
        </figure>
        <t>The rest of this section defines, in order: the dialog context
(<xref target="dialog-context"/>); the dialog and participant states, the control
operations, and how the controller commits changes (<xref target="lifecycle"/>);
what participants declare and how they are admitted and removed
(<xref target="participants"/>); negotiated parameters (<xref target="dialog-parameters"/>);
stopping work and ending dialogs (<xref target="ending"/>); segments, delegated
dialogs, and controller changes (<xref target="delegated-work"/>); errors
(<xref target="errors"/>); recovery after an interruption (<xref target="propagation"/>); the
encoding of control messages (<xref target="control-encoding"/>); and the dialog log
(<xref target="dialog-log"/>).</t>
      </section>
      <section anchor="dialog-context">
        <name>Dialog Context</name>
        <t>A dialog context contains the following fields:</t>
        <ul spacing="normal">
          <li>
            <t><tt>dialog_id</tt>: A UUID version 4 <xref target="RFC9562"/>. The controller generates it
when opening the dialog. It remains unchanged for the lifetime of the
dialog, including when the dialog crosses an intermediary, changes
modality, or resumes after a connection loss.</t>
          </li>
          <li>
            <t><tt>generation</tt>: An unsigned integer identifying the current controller
state. The initial generation is 0. The controller increments it by
one for each committed change to the dialog context, including a
change in a participant's state.</t>
          </li>
          <li>
            <t><tt>state</tt>: One of <tt>pending</tt>, <tt>active</tt>, or <tt>terminated</tt>.</t>
          </li>
          <li>
            <t><tt>controller_id</tt>: The participant identifier of the controller.</t>
          </li>
          <li>
            <t><tt>participants</tt>: The set of participant identifiers in the dialog, each
with a state: <tt>invited</tt>, <tt>active</tt>, <tt>left</tt>, <tt>rejected</tt>, or <tt>revoked</tt>.</t>
          </li>
          <li>
            <t><tt>expires_at</tt>: An optional absolute time in RFC 3339 date-time format.
When present, participants treat the dialog as terminated at that
time.</t>
          </li>
          <li>
            <t><tt>parent_dialog_ids</tt>: An optional list of dialog-ids, set by the
controller in OPEN when the dialog is opened to carry out work
delegated from another dialog. The first entry is the dialog that
triggered this one, followed by that dialog's own parents, so the list
traces the delegation chain back to the originating dialog (<xref section="6.2.1" sectionFormat="of" target="ARCH"/>). It does not change after OPEN.  </t>
            <t>
A controller that opens a delegated dialog with participants in
another trust domain <bcp14>MAY</bcp14> omit <tt>parent_dialog_ids</tt>, or list only the
entries those participants may learn, so that parent dialog-ids are
not disclosed across the boundary. It then keeps the link to the
parent dialogs locally and applies lifecycle propagation
(<xref target="lifecycle-propagation"/>) and cancellation (<xref target="cancellation"/>) from
that local link. Participants of such a dialog cannot detect a
cycle in the dialog lineage; they rely on the delegation chain in
<tt>credentials</tt> for cycle detection (<xref target="delegation"/>).</t>
          </li>
          <li>
            <t><tt>related_dialogs</tt>: An optional list of objects, each with a
<tt>dialog_id</tt> and a <tt>relation</tt>, set by the controller in OPEN and
unchanged after it. <tt>relation</tt> is <tt>follow-up</tt> (the dialog carries
updates on the outcome of the named dialog after it ended),
<tt>resumes</tt> (the dialog continues a relationship established in the
named dialog), or <tt>continues</tt> (the dialog carries on the same task
on another channel). Unlike <tt>parent_dialog_ids</tt>, a related dialog is
not delegated work: lifecycle propagation (<xref target="lifecycle-propagation"/>)
and cancellation do not follow this link, so a follow-up outlives the
dialog it follows. A controller <bcp14>MAY</bcp14> withhold entries across a trust
boundary, as for <tt>parent_dialog_ids</tt>.</t>
          </li>
          <li>
            <t><tt>alternate_controller_id</tt>: An optional participant identifier of an
active participant that may take over as controller
(<xref target="controller-transfer"/>).</t>
          </li>
        </ul>
        <t>The context is encoded as a JSON object:</t>
        <sourcecode type="json"><![CDATA[
{
  "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"}
  ],
  "expires_at": "2026-10-23T12:00:00Z"
}
]]></sourcecode>
        <t>The <tt>expires_at</tt> member is omitted when the dialog has no configured
expiration, <tt>parent_dialog_ids</tt> is omitted when the dialog was not
opened from another dialog or when the controller withholds it
(above), <tt>related_dialogs</tt> is omitted when there are none, and
<tt>alternate_controller_id</tt> is omitted
when no alternate is designated. A context snapshot <bcp14>MUST</bcp14> contain every other
member,
including participants whose states are <tt>left</tt>, <tt>rejected</tt>, or
<tt>revoked</tt>. A controller <bcp14>MUST NOT</bcp14> remove a participant from a later
snapshot; it changes that participant's state instead. The controller
<bcp14>MUST</bcp14> appear in the participant set with state <tt>active</tt>.</t>
        <t>The identity of the principal on whose behalf a delegated dialog runs
travels in the <tt>credentials</tt> member as a delegation chain
(<xref target="delegation"/>), not in the dialog context.</t>
        <t>These identifiers are correlation values. They <bcp14>MUST NOT</bcp14> be treated as
credentials or bearer authorization. Knowing a parent dialog-id does
not grant access to the parent dialog. A participant identifier <bcp14>MUST NOT</bcp14>
encode personal or task information.</t>
      </section>
      <section anchor="lifecycle">
        <name>Lifecycle and Control Operations</name>
        <t>The dialog lifecycle has three states:</t>
        <figure anchor="_figure-dialog-states">
          <name>Dialog State Machine</name>
          <artwork><![CDATA[
                  OPEN (controller, generation 0)
                                |
                                v
                         +-------------+
              UPDATE +-->|   PENDING   |------------------+
                     |   +-------------+                  |
                     |      |      |                      |
                     +------+      | UPDATE committing    | TERMINATE
                                   | an invitee's ACCEPT  | or expiry
                                   v                      v
                         +-------------+            +------------+
      UPDATE, REVOKE +-->|   ACTIVE    |----------->| TERMINATED |
                     |   +-------------+ TERMINATE  |  (final)   |
                     |      |            or expiry  +------------+
                     +------+

]]></artwork>
        </figure>
        <dl>
          <dt>pending:</dt>
          <dd>
            <t>The controller has opened the dialog, but no invitee has accepted.</t>
          </dd>
          <dt>active:</dt>
          <dd>
            <t>At least one invitee has accepted, and the dialog has not been
terminated or expired. The context can be modified with UPDATE and
REVOKE.</t>
          </dd>
          <dt>terminated:</dt>
          <dd>
            <t>The controller has terminated the dialog, or its expiration time
has passed. This state is final.</t>
          </dd>
        </dl>
        <t>Only the controller causes transitions. UPDATE, REVOKE and
TERMINATE each advance the generation by one. ACCEPT, REJECT,
JOIN_REQUEST, LEAVE and DECLARE are requests the controller commits with
UPDATE. Interruptions, cancellations, and segments do not change the state.</t>
        <t>An interruption, such as a lost connection or relay failure, does not
change the dialog state. Participants recover the current context as
described in <xref target="propagation"/>. A participant's own state is tracked
separately from the dialog state: joining or leaving does not by itself
terminate the dialog. When the controller commits a LEAVE that leaves
it as the only active participant, it <bcp14>SHOULD</bcp14> publish TERMINATE. This
lets an agent that is not the controller end a two-party dialog.</t>
        <t>The control operations below cover the lifecycle functions of
<xref section="6.1.2" sectionFormat="of" target="ARCH"/>. Initiation is OPEN, and termination is
TERMINATE, expiry, or a LEAVE that ends a two-party dialog. Suspension
needs no operation: a dialog persists through idle periods with no
transport connection, and a binding can pause individual flows.
Resumption is STATE_REQUEST, which recovers the dialog context,
followed by LOG_STATUS, which establishes what each receiver has
accepted so that missed input and output are replayed without
duplication (<xref target="log-replay"/>), and cancellation is CANCEL
(<xref target="cancellation"/>).</t>
        <t>PACE defines the following control operations:</t>
        <table anchor="_table-control-ops">
          <name>Control Operations</name>
          <thead>
            <tr>
              <th align="left">Operation</th>
              <th align="left">Sender</th>
              <th align="left">Generation</th>
              <th align="left">Effect</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">OPEN</td>
              <td align="left">Controller</td>
              <td align="left">0</td>
              <td align="left">Creates a pending dialog and identifies invitees.</td>
            </tr>
            <tr>
              <td align="left">ACCEPT</td>
              <td align="left">Participant or invitee</td>
              <td align="left">Current</td>
              <td align="left">Accepts an invitation or a parameter proposal.</td>
            </tr>
            <tr>
              <td align="left">REJECT</td>
              <td align="left">Participant or invitee</td>
              <td align="left">Current</td>
              <td align="left">Rejects an invitation or a parameter proposal.</td>
            </tr>
            <tr>
              <td align="left">UPDATE</td>
              <td align="left">Controller</td>
              <td align="left">Next</td>
              <td align="left">Replaces the participant set, expiration, or controller.</td>
            </tr>
            <tr>
              <td align="left">JOIN_REQUEST</td>
              <td align="left">Prospective participant</td>
              <td align="left">Latest known, or 0</td>
              <td align="left">Requests admission to an existing dialog.</td>
            </tr>
            <tr>
              <td align="left">LEAVE</td>
              <td align="left">Participant</td>
              <td align="left">Current</td>
              <td align="left">Leaves the dialog. The controller records the participant as left.</td>
            </tr>
            <tr>
              <td align="left">DECLARE</td>
              <td align="left">Participant</td>
              <td align="left">Current</td>
              <td align="left">Declares the sender's own descriptors, or its observations of others (<xref target="declare"/>).</td>
            </tr>
            <tr>
              <td align="left">REVOKE</td>
              <td align="left">Controller</td>
              <td align="left">Next</td>
              <td align="left">Revokes a participant's propagation relationship.</td>
            </tr>
            <tr>
              <td align="left">TERMINATE</td>
              <td align="left">Controller</td>
              <td align="left">Next</td>
              <td align="left">Ends the dialog.</td>
            </tr>
            <tr>
              <td align="left">SEGMENT</td>
              <td align="left">Controller</td>
              <td align="left">Current</td>
              <td align="left">Starts or ends a segment (<xref target="segments"/>).</td>
            </tr>
            <tr>
              <td align="left">CANCEL</td>
              <td align="left">Any participant</td>
              <td align="left">Current</td>
              <td align="left">Asks receivers to stop work started by the sender's earlier input (<xref target="cancellation"/>).</td>
            </tr>
            <tr>
              <td align="left">CANCEL_ACK</td>
              <td align="left">Any participant</td>
              <td align="left">Current</td>
              <td align="left">Reports the outcome of a CANCEL.</td>
            </tr>
            <tr>
              <td align="left">STATE_REQUEST</td>
              <td align="left">Participant</td>
              <td align="left">Current</td>
              <td align="left">Requests the current context after a gap or reconnection.</td>
            </tr>
            <tr>
              <td align="left">STATE</td>
              <td align="left">Controller</td>
              <td align="left">Current</td>
              <td align="left">Supplies a complete context snapshot.</td>
            </tr>
            <tr>
              <td align="left">LOG_STATUS</td>
              <td align="left">Any participant</td>
              <td align="left">Current</td>
              <td align="left">Reports accepted log positions, or answers such a report (<xref target="log-replay"/>).</td>
            </tr>
            <tr>
              <td align="left">ERROR</td>
              <td align="left">Any participant</td>
              <td align="left">Current</td>
              <td align="left">Reports that an operation was not applied, and why.</td>
            </tr>
          </tbody>
        </table>
        <section anchor="participant-states">
          <name>Participant States</name>
          <t>Each entry in <tt>participants</tt> has its own state, separate from the
dialog state. The controller sets it, in the same UPDATE, REVOKE, or
OPEN that commits the change:</t>
          <figure anchor="_figure-participant-states">
            <name>Participant State Machine</name>
            <artwork><![CDATA[
     named in OPEN, or added by UPDATE
     (an invitation or an admitted JOIN_REQUEST)
                      |
                      v
               +-------------+  REJECT committed   +------------+
               |   invited   |-------------------->|  rejected  |
               +-------------+                     +------------+
                      |
                      | ACCEPT committed
                      v
               +-------------+  LEAVE committed    +------------+
               |   active    |-------------------->|    left    |
               +-------------+                     +------------+
                      |
                      | REVOKE
                      v
               +-------------+
               |   revoked   |
               +-------------+
]]></artwork>
          </figure>
          <t>A participant in state <tt>left</tt>, <tt>rejected</tt>, or <tt>revoked</tt> stays in every
later snapshot with that state (<xref target="dialog-context"/>). Admission
(<xref target="guests"/>, <xref target="sponsored-admission"/>, <xref target="joining-codes"/>) and revocation
(<xref target="revoking-a-participant"/>) are defined in <xref target="participants"/>.</t>
        </section>
        <section anchor="committing">
          <name>Committing Participant Changes</name>
          <t>Only the controller changes the dialog context. Other participants
send requests and responses, and the controller commits the result.</t>
          <ul spacing="normal">
            <li>
              <t>OPEN includes at least one invitee.</t>
            </li>
            <li>
              <t>ACCEPT and REJECT answer a proposal from the controller, named by
<tt>in_reply_to</tt>: an invitation in OPEN or UPDATE, or a parameter
change carried in <tt>parameters</tt> on UPDATE. After the controller
commits an invitee's answer, its state is <tt>active</tt> or <tt>rejected</tt>. A
participant that rejects a parameter change remains in the dialog;
the controller then withdraws the change in a later UPDATE or
revokes the participant.</t>
            </li>
            <li>
              <t>JOIN_REQUEST does not add a participant. The controller admits the
requester by sending UPDATE with the requester's state set to
<tt>invited</tt>, or refuses it with ERROR <tt>policy-rejected</tt>.</t>
            </li>
            <li>
              <t>ACCEPT, REJECT, JOIN_REQUEST, and LEAVE do not modify the context by
themselves. The controller commits each resulting change by
publishing UPDATE with the complete context at the next generation.</t>
            </li>
            <li>
              <t>The dialog becomes <tt>active</tt> when the controller publishes such an
UPDATE after at least one invitee has accepted.</t>
            </li>
          </ul>
        </section>
        <section anchor="generations">
          <name>Generations and Ordering</name>
          <t>UPDATE, REVOKE, and TERMINATE carry the next generation and a complete
context, so a receiver replaces its state as a whole instead of merging
partial updates. Other operations carry the current generation
(<xref target="_table-control-ops"/>).</t>
          <ul spacing="normal">
            <li>
              <t>The controller <bcp14>MUST</bcp14> serialize its state-changing operations and <bcp14>MUST
NOT</bcp14> reuse a generation for different state.</t>
            </li>
            <li>
              <t>A receiver <bcp14>MUST</bcp14> reject a controller operation whose generation is
lower than the latest generation it accepted, with ERROR
<tt>stale-generation</tt>.</t>
            </li>
            <li>
              <t>If a receiver sees a generation greater than the next expected one,
it <bcp14>MUST</bcp14> send STATE_REQUEST and <bcp14>MUST NOT</bcp14> infer the missing changes.</t>
            </li>
            <li>
              <t>A prospective participant does not yet track the dialog, so its
JOIN_REQUEST carries the latest generation it knows, or 0. The
controller does not reject a JOIN_REQUEST as stale.</t>
            </li>
            <li>
              <t>Receivers use the message identifier and generation to detect
duplicates and stale messages. Reprocessing a duplicate operation
<bcp14>MUST NOT</bcp14> repeat its side effects.</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="participants">
        <name>Participants</name>
        <t>This section defines what participants declare about themselves and
others, and how they are admitted and removed. Each change is a
request that the controller commits with UPDATE (<xref target="committing"/>).</t>
        <section anchor="participant-descriptors">
          <name>Participant Descriptors</name>
          <t>In a dialog between a person and their own agent, the participants
know who each other is. Many dialogs PACE carries are not like that
<xref target="DIALOG-UC"/>. A consumer's agent negotiates with a brand's agent; a
person on a phone call talks to a voice agent through a gateway; a
recorder or a transcriber joins a meeting. Before a participant shares
information or agrees to something, it needs answers to questions
such as:</t>
          <ul spacing="normal">
            <li>
              <t>Is the other party a person or software?</t>
            </li>
            <li>
              <t>For whom does it act, and what may it commit to?</t>
            </li>
            <li>
              <t>How strongly was it authenticated, and by whom?</t>
            </li>
            <li>
              <t>Has it agreed to be recorded, or to have its input processed?</t>
            </li>
            <li>
              <t>Is it here to cooperate, or to bargain?</t>
            </li>
          </ul>
          <t>Policies, and in some places laws, on AI disclosure, recording
consent, and delegated authority depend on these answers.
Participant descriptors carry them in the dialog context, so that
every participant sees the same answers and knows who gave each one.</t>
          <t>Each entry in <tt>participants</tt> <bcp14>MAY</bcp14> carry the members below. They come
from three sources: the participant itself, other participants, and
the controller. The source matters, because a participant's statement
about itself is not the same as another participant's observation of
it.</t>
          <table anchor="_table-descriptors">
            <name>Participant Descriptors</name>
            <thead>
              <tr>
                <th align="left">Member</th>
                <th align="left">Set by</th>
                <th align="left">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>kind</tt></td>
                <td align="left">The participant</td>
                <td align="left">
                  <tt>human</tt>, <tt>agent</tt>, <tt>tool</tt>, <tt>transformer</tt>, <tt>recorder</tt>, or <tt>gateway</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>acts_for</tt></td>
                <td align="left">The participant</td>
                <td align="left">Opaque pseudonym of its principal</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>commit_scope</tt></td>
                <td align="left">The participant</td>
                <td align="left">RAR <tt>authorization_details</tt> <xref target="RFC9396"/>: what it may commit to</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>consent</tt></td>
                <td align="left">The participant</td>
                <td align="left">
                  <tt>{"recording": s, "processing": s}</tt>; s is <tt>granted</tt>, <tt>refused</tt>, or <tt>withdrawn</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>posture</tt></td>
                <td align="left">The participant</td>
                <td align="left">
                  <tt>cooperative</tt> or <tt>adversarial</tt> (<xref target="posture"/>)</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>detected_kind</tt></td>
                <td align="left">Other participants</td>
                <td align="left">List of <tt>{"kind", "by", "how"}</tt>; <tt>by</tt> is the observing participant, <tt>how</tt> is <tt>stated</tt> (the subject said so) or <tt>inferred</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>observed_consent</tt></td>
                <td align="left">Other participants</td>
                <td align="left">List of <tt>{"recording", "processing", "by", "how"}</tt>, for a participant that cannot declare its own, such as a person on a call</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>assurance</tt></td>
                <td align="left">Other participants</td>
                <td align="left">List of <tt>{"level", "by", "method", "at"}</tt></td>
              </tr>
              <tr>
                <td align="left">
                  <tt>access</tt></td>
                <td align="left">Controller</td>
                <td align="left">
                  <tt>{"send": [...], "receive": [...]}</tt>, naming modalities or flows</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>declaration_ref</tt></td>
                <td align="left">Controller</td>
                <td align="left">
                  <tt>message_id</tt> of the DECLARE whose values were committed</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>sponsor</tt></td>
                <td align="left">Controller</td>
                <td align="left">Participant that sponsored this participant's admission (<xref target="sponsored-admission"/>)</td>
              </tr>
            </tbody>
          </table>
          <dl>
            <dt>Declared members:</dt>
            <dd>
              <t>The controller copies them verbatim from the participant's latest
DECLARE and names that DECLARE in <tt>declaration_ref</tt>. Any participant
can check the copy against the DECLARE the sender published, which
is authenticated by the sender's key-bound presentation
(<xref target="key-binding"/>). A controller <bcp14>MUST NOT</bcp14> alter them. A participant
that finds a mismatch <bcp14>MUST</bcp14> disregard the controller's copy.</t>
            </dd>
            <dt>Observed members:</dt>
            <dd>
              <t>Each entry names the participant that made it, in <tt>by</tt>, so that
every participant decides for itself whether to rely on it. This is
what separates a participant's claim to be a person (<tt>kind</tt>) from
another participant's detection of automation (<tt>detected_kind</tt>).</t>
            </dd>
            <dt><tt>assurance</tt>:</dt>
            <dd>
              <t>How strongly a participant was authenticated. <tt>level</tt> is <tt>none</tt> (a
guest, not authenticated), <tt>asserted</tt> (identity claimed but not
verified), <tt>authenticated</tt>, or <tt>delegated</tt> (authenticated, with
verified authority from a principal). <tt>method</tt> is a value from the
PACE Assurance Methods registry (<xref target="iana"/>): <tt>credential</tt>, a
key-bound presentation (<xref target="key-binding"/>) of a credential mechanism
(<xref target="identity-formats"/>); <tt>cimd</tt>, a key-bound presentation checked
against a key from an OAuth Client ID Metadata Document <xref target="CIMD"/>;
<tt>resumed</tt>, keys pinned in an earlier dialog named in
<tt>related_dialogs</tt> with relation <tt>resumes</tt>; or <tt>join-code</tt>
(<xref target="joining-codes"/>). Other documents can register further methods,
such as those for telephony.</t>
            </dd>
            <dt><tt>access</tt>:</dt>
            <dd>
              <t>What the participant may send and receive, such as audio but not
screen share. It differs from the <tt>supported_modalities</tt> parameter,
which states what a participant can handle. Absent <tt>access</tt>, a
participant may send and receive every flow. Relays and dialog hosts
enforce it (<xref target="relay-authorization"/>).</t>
            </dd>
          </dl>
          <t>An example entry, for a consumer's agent as seen in a dialog with a
brand's agent:</t>
          <sourcecode type="json"><![CDATA[
{"participant_id": "p-7c1e", "state": "active",
 "kind": "agent", "acts_for": "u-4f9a",
 "detected_kind": [{"kind": "agent", "by": "brand-agent"}],
 "assurance": [{"level": "delegated", "by": "brand-agent",
                "method": "credential",
                "at": "2026-11-13T10:02:11Z"}],
 "posture": "adversarial",
 "declaration_ref": "9b2f6c1e-0d4a-4e8b-a7c3-5f1d2e3a4b6c"}
]]></sourcecode>
        </section>
        <section anchor="declare">
          <name>Declarations</name>
          <t>A participant states its own descriptors, and what it observed about
others, with DECLARE. DECLARE is a separate operation, rather than a
field the controller fills in, because the controller may act for the
other side. A brand's agent that controls a dialog should not be able
to say that the consumer's agent consented to recording, or that the
consumer's agent is a person. With DECLARE, the statement comes from
the participant and is signed by it; the controller only copies it,
and anyone can check the copy.</t>
          <t>The <tt>declaration</tt> member of DECLARE is an object with any of these
members:</t>
          <dl>
            <dt>Own descriptors:</dt>
            <dd>
              <t><tt>kind</tt>, <tt>acts_for</tt>, <tt>commit_scope</tt>, <tt>consent</tt>, and <tt>posture</tt>. Each
replaces the sender's previously declared value.</t>
            </dd>
            <dt><tt>sponsored</tt>:</dt>
            <dd>
              <t>A list of participant identifiers whose admission the sender
sponsors (<xref target="sponsored-admission"/>).</t>
            </dd>
            <dt><tt>observations</tt>:</dt>
            <dd>
              <t>A list of objects, each with <tt>subject</tt> (a participant identifier),
one or more of <tt>detected_kind</tt>, <tt>assurance</tt>, and <tt>consent</tt>, and
optionally <tt>how</tt> (<tt>stated</tt> or <tt>inferred</tt>). Each states what the
sender concluded about that participant, or what the participant
said when it cannot declare for itself, such as a person on a call
who agrees to be recorded.</t>
            </dd>
            <dt><tt>disclosure</tt>:</dt>
            <dd>
              <t>A record that the sender disclosed that it is an AI, with <tt>at</tt> (the
time), <tt>to</tt> (the participant identifiers it was made to), and
<tt>entry</tt> (the entry reference of the log entry that carried it). It
records what the sender said, not that it was understood.</t>
            </dd>
          </dl>
          <t>The controller commits a DECLARE with UPDATE at the next generation.
In that UPDATE, it:</t>
          <ol spacing="normal" type="1"><li>
              <t>copies the sender's own values into the sender's entry and sets
<tt>declaration_ref</tt>; and</t>
            </li>
            <li>
              <t>appends each observation to the subject's <tt>detected_kind</tt>,
<tt>assurance</tt>, or <tt>observed_consent</tt>, with <tt>by</tt> set to the sender. An
observed consent never replaces a participant's own <tt>consent</tt>
declaration.</t>
            </li>
          </ol>
          <t>The controller <bcp14>MUST</bcp14> commit a well-formed DECLARE from an active
participant without undue delay. It <bcp14>MUST NOT</bcp14> refuse a declaration of
<tt>kind</tt>, a raise of <tt>posture</tt>, or a <tt>consent</tt> value of <tt>refused</tt> or
<tt>withdrawn</tt>. A participant must be able to say what it is, to become
more cautious, and to refuse recording, without the agreement of a
controller that may act for its adversary. A controller <bcp14>MAY</bcp14> refuse other declarations with ERROR
<tt>policy-rejected</tt>.</t>
        </section>
        <section anchor="posture">
          <name>Posture</name>
          <t>Many agent dialogs are between parties whose interests differ: a
buyer's agent and a seller's agent, or a customer's agent and a
support agent handling a dispute. In such a dialog, an agent should
not share everything it knows about its principal, and should not rely
on the other side's statements without checking them. Posture lets a
participant say which kind of dialog it considers this to be, so that
every participant applies the matching policy and knows that the
others have been told. Posture describes incentives, not hostility.</t>
          <t>A participant declares its posture with DECLARE:</t>
          <ul spacing="normal">
            <li>
              <t>The dialog's effective posture is <tt>adversarial</tt> if any active
participant declares it, and <tt>cooperative</tt> otherwise.</t>
            </li>
            <li>
              <t>Each participant decides from its own policy what posture means for
it, such as whether a routine exchange may proceed without a
per-action approval (<xref target="delegation-approval"/>).</t>
            </li>
            <li>
              <t>A counterpart's declaration of <tt>cooperative</tt> <bcp14>MUST NOT</bcp14> lower the
assurance, approvals, or records that a participant's policy
requires.</t>
            </li>
          </ul>
          <t>A participant can raise its posture at any point, for example when an
order-status inquiry turns into a refund dispute. The controller
commits the change like any declaration and cannot refuse it
(<xref target="declare"/>), so every participant learns of it. Context shared
before the change stays shared; after it, participants <bcp14>SHOULD</bcp14> stop
sharing context they would not give an adversary, and each applies its
adversarial policy to later exchanges.</t>
        </section>
        <section anchor="guests">
          <name>Guests and Assurance Upgrade</name>
          <t>A controller <bcp14>MAY</bcp14> admit a participant that has not authenticated, such
as a caller on a channel that carries no credential, and records its
<tt>assurance</tt> level as <tt>none</tt>. The deployment's policy limits what a
guest may do, such as receiving general information only. The
participant raises its level later in the same dialog by presenting
<tt>credentials</tt> on a later control message, such as a DECLARE; the
controller, or another participant that verifies them, records a new
<tt>assurance</tt> entry. No new dialog is needed. A participant that
requires a higher level for an operation rejects it with ERROR
<tt>insufficient-assurance</tt>, stating what it needs (<xref target="error-reasons"/>); a
participant that cannot or will not upgrade answers with ERROR
<tt>upgrade-declined</tt>, and the dialog continues at the current level.</t>
        </section>
        <section anchor="sponsored-admission">
          <name>Sponsored Admission</name>
          <t>In a dialog between parties of different principals, the controller
acts for one side, and the other side still needs to bring in its own
principal or a person who takes over from its agent. A JOIN_REQUEST
<bcp14>MAY</bcp14> carry <tt>sponsor</tt>, the identifier of an active participant. If that
participant has listed the requester in the <tt>sponsored</tt> member of its
latest committed declaration, the controller <bcp14>MUST</bcp14> admit the requester,
subject only to authenticating it and to <tt>max_participants</tt>, and <bcp14>MUST
NOT</bcp14> give it <tt>access</tt> narrower than the sponsor's. The controller sets
<tt>sponsor</tt> in the requester's entry. A principal takes over from its
agent by joining as the agent's sponsored participant, after which the
agent sends LEAVE.</t>
        </section>
        <section anchor="joining-codes">
          <name>Join Codes</name>
          <t>A participant on a channel that cannot carry the dialog identifier,
such as a voice call over the PSTN, can bind a new channel to the same
dialog with a join code: a short-lived, single-use value that the
controller issues to an existing participant and that is conveyed in
the call. A JOIN_REQUEST <bcp14>MAY</bcp14> carry <tt>join_code</tt>. If it is valid, the
controller admits the requester as the sponsored participant of the
participant to which the code was issued, records an <tt>assurance</tt>
entry with <tt>method</tt> <tt>join-code</tt>, and invalidates the code. A code
<bcp14>MUST</bcp14> have at least the entropy its lifetime and the controller's rate
limit on attempts require, and a controller <bcp14>MUST</bcp14> limit attempts per
dialog. A requester that does not know the dialog-id redeems the code
at an endpoint that resolves it, such as one that a binding over HTTP
provides. Other documents can define encodings for voice and DTMF.</t>
        </section>
        <section anchor="revoking-a-participant">
          <name>Revoking a Participant</name>
          <t>REVOKE is controller-authoritative. It carries the complete context at
the next generation, sets the target participant's state to <tt>revoked</tt>,
and ends that participant's propagation relationship. A participant or
intermediary that receives REVOKE:</t>
          <ul spacing="normal">
            <li>
              <t><bcp14>MUST</bcp14> stop forwarding the dialog's context to the target.</t>
            </li>
            <li>
              <t><bcp14>MUST</bcp14> cancel subscriptions that it holds only to propagate the dialog
to the target.</t>
            </li>
          </ul>
          <t>The revoked participant <bcp14>MUST</bcp14> stop acting under the authorization it
held in the dialog. It <bcp14>MUST</bcp14> send TERMINATE in each delegated dialog it
controls whose <tt>parent_dialog_ids</tt> include the dialog, so that work
it delegated under that authorization stops as well
(<xref target="lifecycle-propagation"/>). Revocation of the participant's
credential itself is a function of the credential mechanism
(<xref target="identity-formats"/>).</t>
        </section>
      </section>
      <section anchor="dialog-parameters">
        <name>Dialog Parameters</name>
        <t>Dialog parameters are negotiated in the <tt>parameters</tt> member of OPEN,
ACCEPT, UPDATE, and JOIN_REQUEST (<xref target="control-encoding"/>). They describe
how the dialog is conducted and are not part of the dialog context:</t>
        <ul spacing="normal">
          <li>
            <t><tt>dialog_type</tt>: Short-lived (bounded duration) or long-lived
(indefinite)</t>
          </li>
          <li>
            <t><tt>idle_timeout</tt>: Maximum idle duration before the controller
terminates the dialog</t>
          </li>
          <li>
            <t><tt>max_participants</tt>: Maximum number of participants in the dialog</t>
          </li>
          <li>
            <t><tt>supported_modalities</tt>: Data modalities the participant can handle</t>
          </li>
          <li>
            <t><tt>supported_protocols</tt>: Application protocols offered (A2A, MCP, etc.)</t>
          </li>
          <li>
            <t><tt>content_encoding</tt>: Compression applied to content payloads (for
example, <tt>gzip</tt>); absent means none (<xref target="message-serialization"/>)</t>
          </li>
          <li>
            <t><tt>liveness_interval</tt>: Maximum interval, in seconds, between liveness
signals from a participant doing work in the dialog (<xref target="liveness"/>)</t>
          </li>
          <li>
            <t><tt>controller_capable</tt>: Whether the participant can act as controller
if designated as alternate (<xref target="controller-transfer"/>)</t>
          </li>
          <li>
            <t><tt>log_retention</tt>: Minimum time, in seconds, for which a participant
retains entries of its <tt>reliable</tt> flows that a consumer has not yet
accepted (<xref target="log-replay"/>)</t>
          </li>
          <li>
            <t><tt>purpose</tt>: On OPEN and JOIN_REQUEST, a short statement of why the
sender opens or joins the dialog, such as a delivery update or a
notetaker for a meeting</t>
          </li>
          <li>
            <t><tt>basis</tt>: On OPEN and JOIN_REQUEST, why the sender considers itself
entitled to make contact, from the PACE Contact Basis registry
(<xref target="contact-basis"/>)</t>
          </li>
        </ul>
        <t>Parameters are negotiated by proposal and acceptance:</t>
        <ul spacing="normal">
          <li>
            <t>The controller proposes values in OPEN, or in UPDATE for a change.</t>
          </li>
          <li>
            <t>Each invitee or participant accepts with ACCEPT, stating the values
it supports. A participant that cannot accept a proposal sends
REJECT.</t>
          </li>
          <li>
            <t>For list-valued parameters, such as <tt>supported_modalities</tt> and
<tt>supported_protocols</tt>, the accepted values <bcp14>MUST</bcp14> be a subset of the
proposed ones, and they are the participant's active set. Accepting
no value of <tt>supported_modalities</tt> is a rejection.</t>
          </li>
          <li>
            <t>For scalar parameters, the accepted value <bcp14>MAY</bcp14> lower a limit
(<tt>max_participants</tt>, <tt>idle_timeout</tt>, <tt>liveness_interval</tt>) but <bcp14>MUST
NOT</bcp14> raise it. <tt>log_retention</tt> is a minimum, so the accepted value
<bcp14>MAY</bcp14> raise it but <bcp14>MUST NOT</bcp14> lower it.</t>
          </li>
          <li>
            <t><tt>purpose</tt> and <tt>basis</tt> are not negotiated.</t>
          </li>
          <li>
            <t>The controller's committing UPDATE carries the resulting values in
<tt>parameters</tt>, and those values are in effect from that generation.</t>
          </li>
        </ul>
        <section anchor="contact-basis">
          <name>Contact Purpose and Basis</name>
          <t>An agent can open a dialog with a party that did not ask for it, such
as a person's agent or an organization's inbox. The recipient needs to
decide whether to engage before any content is exchanged, as a person
screens a call or an email <xref target="DIALOG-UC"/>. <tt>purpose</tt> says what the
contact is about, and <tt>basis</tt> says why the sender considers itself
entitled to make it. With <tt>contact_limits</tt> (<xref target="results"/>), they let a
recipient refuse a contact, say why, and limit later ones.</t>
          <t><tt>basis</tt> takes one of these values:</t>
          <dl>
            <dt><tt>subscription</tt>:</dt>
            <dd>
              <t>The recipient asked for contacts of this kind, such as updates on an
order or a delivery.</t>
            </dd>
            <dt><tt>existing-relationship</tt>:</dt>
            <dd>
              <t>The sender and the recipient's principal have an ongoing
relationship, such as a customer account, and the contact concerns
it.</t>
            </dd>
            <dt><tt>contract</tt>:</dt>
            <dd>
              <t>The contact is needed to carry out an agreement to which the
recipient's principal is a party, such as arranging the delivery of
something it bought.</t>
            </dd>
            <dt><tt>legal-obligation</tt>:</dt>
            <dd>
              <t>Law or regulation requires the sender to make the contact, such as a
product safety recall.</t>
            </dd>
            <dt><tt>consent</tt>:</dt>
            <dd>
              <t>The recipient's principal agreed to contacts of this kind from this
sender, outside any subscription.</t>
            </dd>
            <dt><tt>none</tt>:</dt>
            <dd>
              <t>The sender claims no basis: the contact is unsolicited, and says so.</t>
            </dd>
          </dl>
          <t><tt>purpose</tt> and <tt>basis</tt> are the sender's assertions, and the recipient
checks them. A recipient can check <tt>subscription</tt>, and often
<tt>existing-relationship</tt> and <tt>consent</tt>, against its own records. It
cannot in general check <tt>contract</tt> or <tt>legal-obligation</tt>; it records
them and weighs them with the sender's <tt>assurance</tt>
(<xref target="participant-descriptors"/>). A recipient can refuse a contact whose
basis it cannot confirm, or that states no <tt>purpose</tt> or <tt>basis</tt>, with
REJECT and a <tt>result</tt> reason such as <tt>unwanted-contact</tt> or
<tt>no-stated-purpose</tt> (<xref target="results"/>). The values describe the sender's
reason for making contact; they are not claims of a legal basis for
processing personal data under any jurisdiction.</t>
        </section>
        <section anchor="dialog-lifetime">
          <name>Dialog Lifetime</name>
          <t>Short-lived dialogs carry an <tt>expires_at</tt> in the dialog context and end
when it passes. Long-lived dialogs omit <tt>expires_at</tt> and continue
across idle periods and interruptions until the controller terminates
them. When <tt>idle_timeout</tt> is set and the dialog has been idle for that
long, with no content or control sent by any participant, the
controller <bcp14>SHOULD</bcp14> publish TERMINATE.</t>
        </section>
      </section>
      <section anchor="ending">
        <name>Stopping Work and Ending Dialogs</name>
        <t>CANCEL stops work without ending the dialog (<xref target="cancellation"/>);
TERMINATE and expiry end it (<xref target="termination"/>); and results say how a
participant regards the outcome (<xref target="results"/>).</t>
        <section anchor="cancellation">
          <name>Cancellation</name>
          <t>A principal that interrupts an agent, a policy decision, or a failed
subtask can require work to stop at once. PACE carries cancellation as
a dialog control operation rather than relying on connection teardown,
so a binding can deliver it ahead of queued content. The MOQT binding
sends it on the <tt>ctrl</tt> track at critical priority (<xref target="cancel-over-moqt"/>).</t>
          <t>CANCEL does not change the dialog context and does not end the dialog.
Its <tt>scope</tt> member selects the work to stop:</t>
          <dl>
            <dt>operation:</dt>
            <dd>
              <t>A single operation the sender started, named in <tt>target</tt>.</t>
            </dd>
            <dt>subtree:</dt>
            <dd>
              <t>All work the receivers carry out in delegated dialogs whose
<tt>parent_dialog_ids</tt> include this dialog. A receiver that controls
such a dialog sends CANCEL with scope <tt>dialog</tt> in it, so cancellation
propagates down the delegation chain and dependent subtasks do not
continue after the parent work is withdrawn.</t>
            </dd>
            <dt>dialog:</dt>
            <dd>
              <t>All work the sender started in this dialog, together with its
subtree.</t>
            </dd>
          </dl>
          <t>A receiver applies CANCEL through the application protocol's own
cancellation where one exists, such as MCP <tt>notifications/cancelled</tt>
or A2A <tt>CancelTask</tt>, so the application sees its native cancel. CANCEL
is idempotent: a receiver that has already acted on a CANCEL reports
the same outcome again and does not repeat side effects.</t>
          <t>Each receiver doing affected work answers with CANCEL_ACK, giving one
of these outcomes:</t>
          <ul spacing="normal">
            <li>
              <t><tt>stopped</tt>: the work stopped before completing.</t>
            </li>
            <li>
              <t><tt>completed</tt>: the work had already completed.</t>
            </li>
            <li>
              <t><tt>partially-reversed</tt>: the work stopped, and some but not all of the
actions it took were rolled back.</t>
            </li>
            <li>
              <t><tt>irreversible</tt>: the work stopped, but an action it took could not be
rolled back.</t>
            </li>
            <li>
              <t><tt>unknown</tt>: the receiver cannot determine whether the work, or work
it delegated, stopped.</t>
            </li>
          </ul>
          <t>CANCEL_ACK <bcp14>MAY</bcp14> also carry <tt>compensation</tt>, an object with a
<tt>description</tt> and an opaque <tt>reference</tt>, for what the receiver offers
in place of an action it could not reverse, such as a refund or a
credit. The terms under which work can be cancelled before it commits
are stated in a commitment (<xref target="delegation-approval"/>).</t>
          <t>When CANCEL reaches delegated dialogs (scope <tt>subtree</tt> or <tt>dialog</tt>), a
receiver that controls such dialogs sends its own CANCEL_ACK only
after it has received a CANCEL_ACK from each participant doing work in
them, or after a locally configured timeout. Its outcome is the least
favorable among its own and those it received, in the order
<tt>completed</tt>, <tt>stopped</tt>, <tt>partially-reversed</tt>, <tt>irreversible</tt>,
<tt>unknown</tt>; a delegated participant that did not answer before the
timeout counts as <tt>unknown</tt>. The initiator of a CANCEL therefore
learns whether the cancellation took effect along the whole chain, or
that this could not be determined.</t>
          <t>Such a receiver <bcp14>MAY</bcp14> also report each delegate's outcome in <tt>details</tt>,
a list of objects with <tt>delegate</tt>, <tt>outcome</tt>, and optionally
<tt>dialog_id</tt> and <tt>compensation</tt>. <tt>delegate</tt> is the delegate's
participant identifier, or an opaque label where the receiver withheld
the delegated dialog from the initiator (<xref target="dialog-context"/>); in that
case <tt>dialog_id</tt> is omitted. A delegate that did not answer is listed
with <tt>unknown</tt>.</t>
        </section>
        <section anchor="termination">
          <name>Termination and Expiry</name>
          <t>TERMINATE is final.</t>
          <ul spacing="normal">
            <li>
              <t>After TERMINATE, a receiver <bcp14>MUST</bcp14> reject later operations for the
dialog with ERROR <tt>dialog-terminated</tt>, except a duplicate TERMINATE
or a STATE needed to complete synchronization.</t>
            </li>
            <li>
              <t>Expiration has the same effect as TERMINATE. Each participant
evaluates it locally from <tt>expires_at</tt>, and it does not create a new
generation.</t>
            </li>
            <li>
              <t>A controller <bcp14>SHOULD</bcp14> publish TERMINATE before the expiration time when
it can.</t>
            </li>
            <li>
              <t>Resuming a transport connection does not reopen a terminated or
expired dialog.</t>
            </li>
          </ul>
        </section>
        <section anchor="results">
          <name>Results and Contact Limits</name>
          <t>ERROR reports that an operation failed. A dialog that ends normally
can still end without what a participant wanted: a refund declined,
an agreement not reached, a contact refused. TERMINATE, LEAVE, and
REJECT <bcp14>MAY</bcp14> carry <tt>result</tt>, which states how the sender regards the
dialog's outcome:</t>
          <sourcecode type="json"><![CDATA[
"result": {
  "category": "deferred",
  "reason": "policy",
  "next_update_at": "2026-11-20T09:00:00Z",
  "recourse": "https://brand.example/disputes",
  "parts": [{"label": "pickup", "category": "completed",
             "compensable": false},
            {"label": "refund", "category": "deferred",
             "compensable": true}],
  "sources": ["a1b2c3d4-..."],
  "commitments": ["6f1c0e9a-..."]
}
]]></sourcecode>
          <ul spacing="normal">
            <li>
              <t><tt>category</tt>: <bcp14>REQUIRED</bcp14>. One of <tt>completed</tt>, <tt>declined</tt>, <tt>deferred</tt>,
<tt>partial</tt>, <tt>transferred</tt>, <tt>failed</tt>, or <tt>abandoned</tt>.</t>
            </li>
            <li>
              <t><tt>reason</tt>: <bcp14>OPTIONAL</bcp14>. A value from the PACE Result Reasons registry
(<xref target="iana"/>), such as <tt>ineligible</tt>, <tt>suspected-fraud</tt>, or
<tt>no-stated-purpose</tt>.</t>
            </li>
            <li>
              <t><tt>retry_after</tt>: <bcp14>OPTIONAL</bcp14>. The time before which the recipient
should not ask again.</t>
            </li>
            <li>
              <t><tt>recourse</tt>: <bcp14>OPTIONAL</bcp14>. A URI at which the recipient can pursue the
matter, such as an appeal or a human channel.</t>
            </li>
            <li>
              <t><tt>next_update_at</tt>: <bcp14>OPTIONAL</bcp14>. For <tt>deferred</tt>, when the sender expects
to report next, so that a waiting participant does not poll.</t>
            </li>
            <li>
              <t><tt>parts</tt>: <bcp14>OPTIONAL</bcp14>. For <tt>partial</tt>, the outcome of each part, and
whether a part that took effect can be compensated.</t>
            </li>
            <li>
              <t><tt>sources</tt> and <tt>commitments</tt>: <bcp14>OPTIONAL</bcp14>. Identifiers of attested
assertions and commitments (<xref target="delegation-approval"/>) on which the result rests,
so that each fact keeps its source.</t>
            </li>
          </ul>
          <t><tt>result</tt> is the sender's statement. It does not change the dialog
state beyond the operation it accompanies, and a participant that
needs to rely on it checks the assertions and commitments it cites.</t>
          <t>REJECT, LEAVE, and TERMINATE <bcp14>MAY</bcp14> also carry <tt>contact_limits</tt>, which
asks the recipient to limit further contact:</t>
          <ul spacing="normal">
            <li>
              <t><tt>retry_after</tt>: The time before which the recipient does not contact
the sender again.</t>
            </li>
            <li>
              <t><tt>max_contacts</tt> and <tt>period</tt>: At most <tt>max_contacts</tt> contacts in
any <tt>period</tt> seconds.</t>
            </li>
            <li>
              <t><tt>scope</tt>: <tt>dialog</tt>, for dialogs related to this one, or <tt>sender</tt>,
for any dialog from the same sender.</t>
            </li>
            <li>
              <t><tt>opt_out</tt>: When true, the sender refuses further contact of this
kind altogether; later contacts are refused with ERROR
<tt>unwanted-contact</tt>.</t>
            </li>
          </ul>
          <t>Limits apply to the recipient as identified by its <tt>credentials</tt>.
They cannot be tied to a participant that has not authenticated
(<xref target="guests"/>). They are enforced by the sender's own policy; a
recipient that ignores them is refused.</t>
        </section>
      </section>
      <section anchor="delegated-work">
        <name>Segments, Delegated Dialogs, and Controller Changes</name>
        <t>These rules apply to dialogs whose content some participants may not
see (<xref target="segments"/>), dialogs opened to carry out work delegated from
another dialog (<xref target="lifecycle-propagation"/>, <xref target="liveness"/>), and dialogs
whose controller changes (<xref target="controller-transfer"/>).</t>
        <section anchor="segments">
          <name>Segments</name>
          <t>Part of a dialog sometimes has to reach only some participants: card
details entered for a payment tool, an off-the-record span in a
meeting, or a challenge that only the person behind an agent may
answer <xref target="DIALOG-UC"/>. A dialog has one visibility scope
(<xref target="topologies"/>), so the content of such a segment is exchanged in a
separate dialog whose <tt>parent_dialog_ids</tt> names this one, and whose
participants are only those who may see it. This dialog, the parent,
carries only the segment's start, end, and result.</t>
          <t>The controller announces a segment with SEGMENT. Its <tt>segment</tt>
member has:</t>
          <ul spacing="normal">
            <li>
              <t><tt>segment_id</tt>: A UUID version 4.</t>
            </li>
            <li>
              <t><tt>kind</tt>: <tt>masked</tt>, for content delivered only to the named
participants, such as payment data, or <tt>off-the-record</tt>, for a span
that agents and recorders do not receive.</t>
            </li>
            <li>
              <t><tt>phase</tt>: <tt>start</tt> or <tt>end</tt>.</t>
            </li>
            <li>
              <t><tt>participants</tt>: The participants that receive the segment's
content.</t>
            </li>
            <li>
              <t><tt>dialog_id</tt>: <bcp14>OPTIONAL</bcp14>. The dialog that carries the content. The
controller <bcp14>MAY</bcp14> withhold it from participants not listed.</t>
            </li>
            <li>
              <t><tt>result</tt> and <tt>reference</tt>: <bcp14>OPTIONAL</bcp14>, on <tt>end</tt>. The segment's result
(<xref target="results"/>) and an opaque reference to it, such as a payment
reference, that does not expose its content.</t>
            </li>
          </ul>
          <t>Each participant not listed in <tt>participants</tt> <bcp14>MUST</bcp14> acknowledge a
SEGMENT with ACCEPT naming it in <tt>in_reply_to</tt>. A <tt>recorder</tt> records
the gap, so its record shows that a segment happened, its kind, and
its result. For <tt>off-the-record</tt>, the controller <bcp14>MUST NOT</bcp14> admit to the
segment dialog any participant whose <tt>kind</tt> is <tt>agent</tt> or <tt>recorder</tt>,
and the segment's participants exchange its content only in the
segment dialog. Until a participant has acknowledged, it might not know
that a gap is intended; the controller <bcp14>MAY</bcp14> revoke a participant that
does not acknowledge, and a dialog host withholds later content from
it.</t>
          <t>Because the segment dialog is a delegated dialog of this one, it ends
when this one ends (<xref target="lifecycle-propagation"/>). With end-to-end
protection (<xref target="e2e-protection"/>), it has its own keys, so participants
of this dialog that are not in the segment cannot read its content
even through the relays they share.</t>
        </section>
        <section anchor="lifecycle-propagation">
          <name>Lifecycle Propagation Along Delegation Chains</name>
          <t>A delegated dialog carries out work for the dialogs listed in its
<tt>parent_dialog_ids</tt>. Its lifecycle follows theirs:</t>
          <ul spacing="normal">
            <li>
              <t>When a dialog terminates or expires, each participant that controls
a delegated dialog whose <tt>parent_dialog_ids</tt> include it <bcp14>MUST</bcp14> send
TERMINATE in that delegated dialog. Termination therefore reaches
the end of the delegation chain, as CANCEL with scope <tt>subtree</tt> does
(<xref target="cancellation"/>).</t>
            </li>
            <li>
              <t>When a participant is revoked, it terminates the delegated dialogs
it controls under that participation (<xref target="revoking-a-participant"/>).</t>
            </li>
            <li>
              <t>A controller that terminates a delegated dialog for one of these
reasons and needs to know whether work below it stopped first sends
CANCEL with scope <tt>dialog</tt> and waits for the CANCEL_ACK outcomes
(<xref target="cancellation"/>).</t>
            </li>
          </ul>
          <t>These rules use only the linkage in <tt>parent_dialog_ids</tt>, or the
controller's local link when it withheld that member
(<xref target="dialog-context"/>). A participant
that cannot reach a delegated dialog's other participants still
terminates it; they observe the termination when they resynchronize.</t>
        </section>
        <section anchor="liveness">
          <name>Liveness</name>
          <t>When the <tt>liveness_interval</tt> parameter is set, a participant that is
doing work in the dialog for another participant publishes a liveness
signal at least once per interval, even when it has no other output.
In the MOQT binding, the signal is an object on its <tt>progress</tt> track
(<xref target="dialog-namespace"/>); any other object the participant publishes in
the dialog also counts.</t>
          <t>If a delegating participant receives no liveness signal from a
delegated participant for two consecutive intervals, it treats that
participant as unavailable: it halts the affected work, sends CANCEL
for it, and <bcp14>MAY</bcp14> ask the controller to revoke the participant.
Unavailability is not revocation; it can be a transient failure, and
the participant can resume (<xref target="propagation"/>).</t>
        </section>
        <section anchor="controller-transfer">
          <name>Controller Transfer</name>
          <t>A dialog's controller can change in two ways. In both, the new
controller is the participant named in <tt>alternate_controller_id</tt>,
which the controller sets with UPDATE and which <bcp14>MUST</bcp14> name an <tt>active</tt>
participant that set <tt>controller_capable</tt> in its ACCEPT <tt>parameters</tt>.</t>
          <ul spacing="normal">
            <li>
              <t>Hand-off: The controller publishes UPDATE at the next generation
with <tt>controller_id</tt> set to the alternate. From that generation, the
alternate is the controller and the former controller is an ordinary
participant.</t>
            </li>
            <li>
              <t>Takeover: If the controller is unreachable (<xref target="propagation"/>) for
longer than the deployment's takeover time, the alternate publishes
UPDATE at the next generation after the last one it accepted, with
itself as <tt>controller_id</tt>, and with <tt>credentials</tt> showing that it is
authorized to control the dialog, such as a delegation from the
principal that authorized the original controller.</t>
            </li>
          </ul>
          <t>Participants accept a takeover UPDATE only from the participant named
in <tt>alternate_controller_id</tt> in the context they hold, and only after
verifying its credentials. If a participant receives two different
contexts for the same generation, one from the former controller and
one a takeover by the alternate, it <bcp14>MUST</bcp14> accept the takeover. A
participant that has already accepted a later generation from the
former controller rejects the takeover with ERROR <tt>stale-generation</tt>;
an alternate that receives this withdraws, resynchronizes with
STATE_REQUEST, and does not act as controller. A former controller
that sees an accepted context naming another controller <bcp14>MUST</bcp14> stop
publishing state-changing operations and resynchronize with
STATE_REQUEST.</t>
          <t>Controller transfer keeps the dialog-id and generation sequence, so a
dialog continues through the failure of a controller, including an
application-level mediator that controls it, rather than being
replaced.</t>
          <t>Editor's note: Takeover by an alternate trades availability for the
risk of a brief split between controllers. Deployments that cannot
tolerate this omit <tt>alternate_controller_id</tt>.</t>
        </section>
      </section>
      <section anchor="errors">
        <name>Authorization and Errors</name>
        <t>Before applying an operation, a participant <bcp14>MUST</bcp14> authenticate its
sender and check authorization using the deployment's mechanisms
(<xref target="authorization"/>). A valid state-changing operation needs no separate
acknowledgment. An ERROR names the rejected control message in
<tt>in_reply_to</tt>, or the rejected application operation in <tt>target</tt>
(<xref target="error-reasons"/>), and gives a reason.</t>
        <ul spacing="normal">
          <li>
            <t>A message that cannot be parsed, or that lacks a required member
(<xref target="control-encoding"/>), is rejected with ERROR <tt>malformed</tt>.</t>
          </li>
          <li>
            <t>If the sender's credential is missing or fails verification, the
participant <bcp14>MUST</bcp14> reject the operation with <tt>unauthenticated</tt>, or
with <tt>credential-invalid</tt> when the credential is revoked or expired.</t>
          </li>
          <li>
            <t>If authorization fails or cannot be determined, the participant <bcp14>MUST</bcp14>
reject the operation with ERROR, giving <tt>unauthorized</tt> or
<tt>authorization-unavailable</tt> as the reason, or <tt>scope-exceeded</tt> when
the operation exceeds the scope delegated to the sender.</t>
          </li>
          <li>
            <t>A participant that does not understand the control-message version
or an operation <bcp14>MUST NOT</bcp14> reinterpret it. It responds with ERROR,
giving <tt>unsupported-version</tt> or <tt>unsupported-operation</tt>.</t>
          </li>
        </ul>
        <t>Reasons are precise enough for the sender to decide what to do next,
but an ERROR <bcp14>MUST NOT</bcp14> reveal policy details beyond the reason.</t>
        <section anchor="error-reasons">
          <name>Error Reasons</name>
          <t>The <tt>reason</tt> member of ERROR takes one of the values below. They
distinguish validation, authentication, authorization, policy, state,
and processing failures from transport failures, which MOQT reports
separately (<xref section="6.1.5" sectionFormat="of" target="ARCH"/>).</t>
          <table anchor="_table-error-reasons">
            <name>ERROR Reasons</name>
            <thead>
              <tr>
                <th align="left">Reason</th>
                <th align="left">Meaning</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>malformed</tt></td>
                <td align="left">The message cannot be parsed or lacks a required member.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>unsupported-version</tt></td>
                <td align="left">The control-message version is not supported.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>unsupported-operation</tt></td>
                <td align="left">The operation type is not supported.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>stale-generation</tt></td>
                <td align="left">The generation is older than the latest accepted.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>unauthenticated</tt></td>
                <td align="left">The sender's credential is missing or fails verification.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>credential-invalid</tt></td>
                <td align="left">The sender's credential is revoked, expired, or otherwise invalid.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>unauthorized</tt></td>
                <td align="left">The sender is not authorized for the operation.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>authorization-unavailable</tt></td>
                <td align="left">Authorization could not be determined at this time.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>scope-exceeded</tt></td>
                <td align="left">The operation exceeds or contradicts the scope delegated to the sender.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>policy-rejected</tt></td>
                <td align="left">Local policy refuses the operation, such as a join.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>delegation-cycle</tt></td>
                <td align="left">The delegation chain or dialog lineage contains a cycle (<xref target="delegation"/>).</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>dialog-terminated</tt></td>
                <td align="left">The dialog is terminated or expired.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>participant-revoked</tt></td>
                <td align="left">The sender has been revoked from the dialog.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>validation-failed</tt></td>
                <td align="left">The operation was refused because it could cause unintended or irreversible effects.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>insufficient-assurance</tt></td>
                <td align="left">The sender's assurance is below what the operation needs; ERROR carries <tt>required_assurance</tt> (<xref target="guests"/>).</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>upgrade-declined</tt></td>
                <td align="left">The sender cannot or will not raise its assurance; the dialog continues at the current level.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>unwanted-contact</tt></td>
                <td align="left">The recipient refuses contact from the sender (<xref target="results"/>).</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>translation-failed</tt></td>
                <td align="left">A mediator could not translate the operation or its result between protocols.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>timeout</tt></td>
                <td align="left">The operation, or a step it depends on, did not complete in time.</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>internal-error</tt></td>
                <td align="left">The receiver failed while processing the operation.</td>
              </tr>
            </tbody>
          </table>
          <t>The first group of reasons applies to control messages. A participant
that rejects an application operation, such as a mediator that
refuses or cannot translate a tool call, also <bcp14>MAY</bcp14> publish ERROR with
<tt>target</tt> naming the operation, in the form CANCEL uses
(<xref target="cancel-over-moqt"/>), and <bcp14>SHOULD</bcp14> also answer in the application
protocol where that protocol has a matching error.</t>
          <t>Errors that the application protocol reports for its own operations,
such as a failed tool call (an MCP error result) or a failed task (an
A2A task in the <tt>failed</tt> state), stay in that protocol. A participant
can therefore tell a transport failure (MOQT), a dialog failure
(PACE ERROR), and a tool or agent processing failure (application
protocol) apart by where each is reported.</t>
        </section>
      </section>
      <section anchor="propagation">
        <name>Propagation and Continuity</name>
        <ul spacing="normal">
          <li>
            <t>Correlation across hops: An intermediary <bcp14>MUST</bcp14> preserve the dialog
identifier, generation, and lifecycle operation when forwarding dialog
context. It <bcp14>MUST NOT</bcp14> create a new dialog identifier or change the
dialog state. This document defines no identifier-alias mechanism; a
deployment that needs aliases requires a separate mechanism that
securely correlates the alias with the original dialog.</t>
          </li>
          <li>
            <t>Trust boundaries: A participant forwarding dialog context into another
trust domain does so only within a propagation relationship that the
deployment's authorization mechanism permits. Authorization to forward
or subscribe at the transport layer does not by itself make an entity
a participant.</t>
          </li>
          <li>
            <t>Modality changes: Transforming a modality, such as converting audio to
text, does not create a new dialog. Participants and intermediaries
<bcp14>MUST</bcp14> keep the same dialog identifier and current lifecycle state
across the transformation.</t>
          </li>
          <li>
            <t>Continuity over time: After a connection loss, a participant <bcp14>MAY</bcp14>
reconnect, over a new transport session if necessary, using the
existing dialog identifier. It <bcp14>MUST</bcp14> obtain the current context from
the controller with STATE_REQUEST before acting on state that may have
changed while it was disconnected, and it uses LOG_STATUS to
establish which log entries were accepted (<xref target="log-replay"/>).
Acceptance of an entry does not imply that the application operation
it carries completed; entries a receiver has not accepted are
replayed, and entries it has accepted are not.</t>
          </li>
          <li>
            <t>Unreachability: If the controller is unreachable, participants <bcp14>MUST</bcp14>
suspend actions that depend on an unconfirmed context change. Each
participant remains at the last generation it accepted until the
controller is reachable again, an alternate controller takes over
(<xref target="controller-transfer"/>), or the dialog expires. Participants <bcp14>MUST NOT</bcp14> create
a replacement dialog solely because a path or intermediary failed. If
an invitee or participant is unreachable, the controller <bcp14>MAY</bcp14> revoke it
or let the dialog expire, according to deployment policy.</t>
          </li>
        </ul>
      </section>
      <section anchor="control-encoding">
        <name>Control Message Encoding</name>
        <t>A PACE control message is a UTF-8 encoded JSON object <xref target="RFC8259"/>.
Every control message contains these members:</t>
        <ul spacing="normal">
          <li>
            <t><tt>version</tt>: The integer 1.</t>
          </li>
          <li>
            <t><tt>type</tt>: One of the operations in <xref target="lifecycle"/>.</t>
          </li>
          <li>
            <t><tt>dialog_id</tt>: The canonical textual form of the dialog's UUID.</t>
          </li>
          <li>
            <t><tt>generation</tt>: A non-negative integer no greater than 2^53 - 1.</t>
          </li>
          <li>
            <t><tt>sender_id</tt>: The sender's participant identifier.</t>
          </li>
          <li>
            <t><tt>message_id</tt>: A UUID version 4 unique to this message.</t>
          </li>
        </ul>
        <t>Control messages also carry the following type-specific members:</t>
        <ul spacing="normal">
          <li>
            <t><tt>context</tt>: The complete dialog context, encoded as the JSON object
defined in <xref target="dialog-context"/>.</t>
          </li>
          <li>
            <t><tt>in_reply_to</tt>: The <tt>message_id</tt> of the control message this message
answers: the OPEN, UPDATE, or SEGMENT that an ACCEPT or REJECT
answers; the STATE_REQUEST or LOG_STATUS that a STATE or LOG_STATUS
answers; the CANCEL that a CANCEL_ACK answers; or the message that
an ERROR rejects.</t>
          </li>
          <li>
            <t><tt>target_id</tt>: The participant identifier whose propagation relationship
is revoked.</t>
          </li>
          <li>
            <t><tt>declaration</tt>: The sender's declaration (<xref target="declare"/>).</t>
          </li>
          <li>
            <t><tt>segment</tt>: The segment being started or ended (<xref target="segments"/>).</t>
          </li>
          <li>
            <t><tt>scope</tt>: The cancellation scope: <tt>operation</tt>, <tt>subtree</tt>, or <tt>dialog</tt>
(<xref target="cancellation"/>).</t>
          </li>
          <li>
            <t><tt>target</tt>: The operation to cancel when <tt>scope</tt> is <tt>operation</tt>, or the
application operation an ERROR rejects. Its form is defined by the
transport binding (<xref target="cancel-over-moqt"/>).</t>
          </li>
          <li>
            <t><tt>outcome</tt>: One of <tt>stopped</tt>, <tt>completed</tt>, <tt>partially-reversed</tt>,
<tt>irreversible</tt>, or <tt>unknown</tt>.</t>
          </li>
          <li>
            <t><tt>last_accepted_generation</tt>: The highest generation the sender has
accepted from the controller, or -1 if it has accepted none.</t>
          </li>
          <li>
            <t><tt>reason</tt>: One of the values in <xref target="_table-error-reasons"/>.</t>
          </li>
          <li>
            <t><tt>positions</tt>: A list of objects, each with <tt>sender_id</tt>, <tt>flow</tt>, and
<tt>accepted</tt>, giving the accepted position for one flow
(<xref target="log-acceptance"/>). The forms of <tt>flow</tt> and <tt>accepted</tt> are
defined by the binding.</t>
          </li>
        </ul>
        <t>Each type requires the members listed below:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Type</th>
              <th align="left">Required type-specific members</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">OPEN</td>
              <td align="left">
                <tt>context</tt></td>
            </tr>
            <tr>
              <td align="left">ACCEPT</td>
              <td align="left">
                <tt>in_reply_to</tt></td>
            </tr>
            <tr>
              <td align="left">REJECT</td>
              <td align="left">
                <tt>in_reply_to</tt>; <tt>reason</tt> optional</td>
            </tr>
            <tr>
              <td align="left">UPDATE</td>
              <td align="left">
                <tt>context</tt></td>
            </tr>
            <tr>
              <td align="left">JOIN_REQUEST</td>
              <td align="left">none</td>
            </tr>
            <tr>
              <td align="left">LEAVE</td>
              <td align="left">none</td>
            </tr>
            <tr>
              <td align="left">DECLARE</td>
              <td align="left">
                <tt>declaration</tt></td>
            </tr>
            <tr>
              <td align="left">REVOKE</td>
              <td align="left">
                <tt>target_id</tt>, <tt>context</tt></td>
            </tr>
            <tr>
              <td align="left">TERMINATE</td>
              <td align="left">
                <tt>context</tt></td>
            </tr>
            <tr>
              <td align="left">SEGMENT</td>
              <td align="left">
                <tt>segment</tt></td>
            </tr>
            <tr>
              <td align="left">STATE_REQUEST</td>
              <td align="left">
                <tt>last_accepted_generation</tt></td>
            </tr>
            <tr>
              <td align="left">STATE</td>
              <td align="left">
                <tt>context</tt>; <tt>in_reply_to</tt> when answering a STATE_REQUEST</td>
            </tr>
            <tr>
              <td align="left">LOG_STATUS</td>
              <td align="left">
                <tt>positions</tt>; <tt>in_reply_to</tt> when answering a LOG_STATUS</td>
            </tr>
            <tr>
              <td align="left">CANCEL</td>
              <td align="left">
                <tt>scope</tt>; <tt>target</tt> when <tt>scope</tt> is <tt>operation</tt></td>
            </tr>
            <tr>
              <td align="left">CANCEL_ACK</td>
              <td align="left">
                <tt>in_reply_to</tt>, <tt>outcome</tt></td>
            </tr>
            <tr>
              <td align="left">ERROR</td>
              <td align="left">
                <tt>reason</tt>; <tt>in_reply_to</tt> or <tt>target</tt></td>
            </tr>
          </tbody>
        </table>
        <t>For OPEN, <tt>context</tt> has generation 0 and state <tt>pending</tt>, and carries
<tt>parent_dialog_ids</tt> when the dialog is delegated. For UPDATE,
REVOKE, and TERMINATE, <tt>context</tt> has the next generation, and a
TERMINATE context has state <tt>terminated</tt>. An UPDATE that adds a
participant sets that participant's state to <tt>invited</tt>; the
participant becomes <tt>active</tt> only after it accepts and the controller
publishes a later UPDATE.</t>
        <t>Further optional members are defined for some types:</t>
        <ul spacing="normal">
          <li>
            <t><tt>result</tt> and <tt>contact_limits</tt>: On TERMINATE, LEAVE, and REJECT
(<xref target="results"/>).</t>
          </li>
          <li>
            <t><tt>required_assurance</tt>: On ERROR with reason <tt>insufficient-assurance</tt>,
an object with <tt>level</tt> (<xref target="participant-descriptors"/>) and optionally
<tt>acr_values</tt> and <tt>max_age</tt> with their OpenID Connect meanings, for
the authentication of the sender's principal.</t>
          </li>
          <li>
            <t><tt>sponsor</tt> and <tt>join_code</tt>: On JOIN_REQUEST
(<xref target="sponsored-admission"/>, <xref target="joining-codes"/>).</t>
          </li>
          <li>
            <t><tt>compensation</tt> and <tt>details</tt>: On CANCEL_ACK (<xref target="cancellation"/>).</t>
          </li>
        </ul>
        <t>Three optional members carry information that is not part of the dialog
context:</t>
        <ul spacing="normal">
          <li>
            <t><tt>parameters</tt>: On OPEN, ACCEPT, UPDATE, and JOIN_REQUEST, the dialog
parameters being proposed or accepted, such as modalities and
application protocols (<xref target="dialog-parameters"/>).</t>
          </li>
          <li>
            <t><tt>credentials</tt>: On any message, an identity assertion or
authorization proof in a format selected by the deployment
(<xref target="identity-formats"/>). A participant
refreshes its credentials before they expire by including new ones
on a later message.</t>
          </li>
          <li>
            <t><tt>nonce</tt>: On OPEN, ACCEPT, UPDATE, JOIN_REQUEST, STATE_REQUEST, and
STATE, a fresh random value, with at least 128 bits of entropy and
base64url-encoded, to which the recipient binds the presentation in
its next <tt>credentials</tt> (<xref target="key-binding"/>).</t>
          </li>
        </ul>
        <t>JSON member order is insignificant. Receivers <bcp14>MUST</bcp14> ignore unrecognized
optional members, <bcp14>MUST</bcp14> reject an unrecognized <tt>type</tt>, and <bcp14>MUST</bcp14> reject
messages with missing required members, invalid member types, or an
unsupported version. Receivers <bcp14>MUST</bcp14> limit the size of a control message
to a locally configured maximum. A participant <bcp14>MUST NOT</bcp14> include
application content in a control message.</t>
      </section>
      <section anchor="dialog-log">
        <name>Dialog Log</name>
        <t>The dialog context tells participants which dialog they are in and
what state it is in. The log tells them what has been said in it.
PACE does not interpret log content, but it defines the metadata of
each log entry, so that participants can agree on what was exchanged
when they resume, recover, or start a new client instance
(<xref section="4.2.10" sectionFormat="of" target="ARCH"/>).</t>
        <section anchor="log-entries">
          <name>Log Entries</name>
          <t>Each log entry has the following metadata:</t>
          <ul spacing="normal">
            <li>
              <t><tt>sender_id</tt>: The participant identifier of the sender.</t>
            </li>
            <li>
              <t><tt>flow</tt>: The flow that carries the entry. Its form is defined by the
binding.</t>
            </li>
            <li>
              <t><tt>position</tt>: The entry's log position in that flow. Its form is
defined by the binding. A sender <bcp14>MUST</bcp14> assign positions that increase
with each entry it sends on a flow and <bcp14>MUST NOT</bcp14> reuse a position for
different content.</t>
            </li>
            <li>
              <t><tt>timestamp</tt>: Optionally, the time at which the sender produced the
entry. Receivers <bcp14>MUST NOT</bcp14> rely on timestamps from different senders
being comparable.</t>
            </li>
            <li>
              <t><tt>source_id</tt>: Optionally, for an entry that renders another
participant's input, such as a translation or a transcription, the
participant identifier of the participant whose input it renders.</t>
            </li>
            <li>
              <t><tt>derived_from</tt>: Optionally, the entry references of the entries it
was derived from.</t>
            </li>
          </ul>
          <t><tt>sender_id</tt>, <tt>flow</tt>, and <tt>position</tt> together form an entry
reference, which names one entry for the lifetime of the dialog.</t>
          <t>A transformer, such as an interpreter or a speech-to-text gateway,
is a participant (<xref target="participant-descriptors"/>). It publishes each
rendering on a flow of its own, so that different participants receive
different renderings of the same exchange by choosing which flow to
consume, and records are kept with the original apart from its
renderings. Its renderings carry <tt>source_id</tt> and <tt>derived_from</tt>, so
they are attributed to the speaker as derived content and not
mistaken for the speaker's own words. Content a transformer sends that
renders no input, such as a note of its own, carries neither member and
is attributed to the transformer. PACE cannot check that a rendering
is faithful; it keeps each rendering linked to its source.</t>
          <t>Each flow has an output class and a delivery class, fixed for the
life of the flow and defined by the binding's flow naming:</t>
          <ul spacing="normal">
            <li>
              <t>Output class (<xref section="4.2.11" sectionFormat="of" target="ARCH"/>): <tt>input</tt>, for content a
participant sends in the principal role; <tt>response</tt>;
<tt>information</tt>, such as tool calls, sub-agent invocations, and
reasoning summaries; or <tt>progress</tt>, such as token counts, elapsed
time, and liveness signals.</t>
            </li>
            <li>
              <t>Delivery class: <tt>reliable</tt>, for content that every receiver needs,
such as chat, operations, and their results; or <tt>loss-tolerant</tt>, for
real-time media whose value expires, such as audio and video frames.</t>
            </li>
          </ul>
          <t>Entries in a <tt>reliable</tt> flow are delivered in position order. Entries
in a <tt>loss-tolerant</tt> flow can be lost, and later entries do not
depend on earlier ones.</t>
        </section>
        <section anchor="log-acceptance">
          <name>Acceptance</name>
          <t>A receiver accepts an entry when it takes responsibility for it:
from then on it either processes the entry or reports an ERROR for
it. The accepted position of a flow, for one receiver, is the
highest position in that flow up to which the receiver has accepted
every entry it needs to.</t>
          <ul spacing="normal">
            <li>
              <t>A receiver <bcp14>MUST</bcp14> record an entry as accepted before it, or the agent
it serves, begins to act on the entry, and <bcp14>MUST</bcp14> keep that record
for as long as it can resume the dialog. A receiver that fails after
acting on an entry therefore never reports it as unaccepted.</t>
            </li>
            <li>
              <t>A receiver <bcp14>MUST</bcp14> discard an entry at or below its accepted position
for that flow as a duplicate, without repeating its side effects.</t>
            </li>
            <li>
              <t>For a <tt>loss-tolerant</tt> flow, the accepted position is the highest
position received; earlier lost entries are not recovered.</t>
            </li>
          </ul>
          <t>Acceptance is not completion. An accepted request can still be in
progress, fail, or be cancelled (<xref target="cancellation"/>); the application
protocol reports those outcomes.</t>
        </section>
        <section anchor="log-replay">
          <name>Log Status and Replay</name>
          <t>After a gap, reconnection, or failover, participants exchange their
accepted positions with LOG_STATUS so that each sender knows what to
make available again, and each receiver knows what to retrieve. This
answers whether a sender needs to replay its input
(<xref section="6.1.2" sectionFormat="of" target="ARCH"/>) without inferring it from transport state.</t>
          <ul spacing="normal">
            <li>
              <t>A participant that resumes a dialog first resynchronizes the dialog
context with STATE_REQUEST (<xref target="propagation"/>). It then sends
LOG_STATUS without <tt>in_reply_to</tt>, listing in <tt>positions</tt> its
accepted position for each flow it consumes.</t>
            </li>
            <li>
              <t>Each participant that receives such a LOG_STATUS and consumes flows
of the sender answers with LOG_STATUS, with <tt>in_reply_to</tt> naming
it, listing its accepted positions for the sender's flows only.</t>
            </li>
            <li>
              <t>For each <tt>reliable</tt> flow it sends, the resuming participant makes
every entry above the lowest accepted position reported for that
flow available to the receivers again, at the same positions and
with the same content, as the binding defines. It <bcp14>MUST NOT</bcp14>
re-send an entry with new content at an existing position, and
<bcp14>MUST NOT</bcp14> send again as new entries the content of entries a
receiver has already accepted.</t>
            </li>
            <li>
              <t>The resuming participant retrieves entries above its own accepted
positions in other participants' flows, as the binding defines.</t>
            </li>
            <li>
              <t>Entries in <tt>loss-tolerant</tt> flows are not replayed.</t>
            </li>
          </ul>
          <t>A sender retains each entry of a <tt>reliable</tt> flow until every
participant consuming that flow reports an accepted position at or
above it, or for the <tt>log_retention</tt> time (<xref target="dialog-parameters"/>),
whichever comes first. A receiver whose accepted position falls below
what the sender still retains cannot recover the missing entries; it
<bcp14>SHOULD</bcp14> report this to the application and <bcp14>MAY</bcp14> request the current
state through the application protocol.</t>
          <t>A new client instance of a participant (<xref target="device-handover"/>) uses the
same procedure to rehydrate the log: it retrieves the entries it
needs to show, in each flow, from the positions it chooses. A binding
<bcp14>MUST</bcp14> define how a participant retrieves entries by flow and position
range, or <bcp14>MUST</bcp14> state that it does not support rehydration.</t>
          <t>LOG_STATUS does not change the dialog context and does not advance
the generation. A participant <bcp14>MUST NOT</bcp14> include log content in it.</t>
        </section>
      </section>
    </section>
    <section anchor="moqt-binding">
      <name>MOQT Binding</name>
      <t>This section specifies how the dialog management protocol of
<xref target="dialog-management"/> is carried over MOQT.</t>
      <section anchor="namespace">
        <name>Namespace Organization</name>
        <t>PACE uses MOQT's hierarchical namespace for routing, isolation, and
multiplexing. In MOQT, content is addressed by a Track Namespace (an
ordered set of up to 32 fields, compared as byte sequences
<xref target="MoQ-TRANSPORT"/>) together with a Track Name. PACE organizes
communication into two namespace scopes: an agent namespace for each
agent's identity and invitations, and a dialog namespace for all of a
dialog's traffic.</t>
        <section anchor="agent-namespace">
          <name>Agent Namespace</name>
          <artwork><![CDATA[
  ("pace", "agents", {agent-id}) -- {track}
]]></artwork>
          <t>This is an agent's persistent identity on the relay network. Each agent
publishes the following tracks:</t>
          <ul spacing="normal">
            <li>
              <t><tt>"card"</tt> — Agent Card containing capabilities, identity claims,
authentication schemes, and MOQT connectivity information
(<xref target="agent-card"/>)</t>
            </li>
            <li>
              <t><tt>("pace", "agents", {agent-id}, "invites") -- {invitee-id}</tt> — One
track per agent it invites to dialogs (<xref target="invitations"/>)</t>
            </li>
          </ul>
          <t>The common prefix <tt>("pace", "agents")</tt> enables SUBSCRIBE_NAMESPACE-based
discovery of all agents on the network. An agent follows another by
subscribing to its card and to the invitation track named by the
follower's own agent-id. See <xref target="agent-discovery"/> for the complete
discovery flow.</t>
        </section>
        <section anchor="dialog-namespace">
          <name>Dialog Namespace</name>
          <artwork><![CDATA[
  ("pace", "dialogs", {dialog-id}, {agent-id}) -- {track}
]]></artwork>
          <t>The dialog-id is the dialog identifier (<xref target="dialog-context"/>). The
controller mints it when it opens the dialog. Each participant
publishes its tracks for the dialog under its own agent-id field
within the dialog's namespace; the agent-id is the participant
identifier used in the dialog context. Each participant issues
SUBSCRIBE_TRACKS on the dialog prefix <tt>("pace", "dialogs",
{dialog-id})</tt>, so it receives every participant's tracks, including
those of participants added later, as PUBLISH messages forwarded by
the relay.</t>
          <t>Each participant in a dialog publishes the following tracks:</t>
          <ul spacing="normal">
            <li>
              <t><tt>"ctrl"</tt> — Dialog control messages (<xref target="control-encoding"/>)</t>
            </li>
            <li>
              <t><tt>"chat"</tt> — Chat messages and streaming LLM output</t>
            </li>
            <li>
              <t><tt>"audio"</tt> — Real-time audio stream</t>
            </li>
            <li>
              <t><tt>"video"</tt> — Real-time video stream</t>
            </li>
            <li>
              <t><tt>"progress"</tt> — Progress output, such as token counts, elapsed time,
and liveness signals (<xref target="liveness"/>), kept apart from the response</t>
            </li>
            <li>
              <t><tt>"ops/{req-id}"</tt> — Request/response operations (one track per request)</t>
            </li>
          </ul>
          <t>Only the <tt>ctrl</tt> track carries the dialog context. The other tracks
carry dialog content and are outside the dialog context. In the terms
of <xref section="4.2.11" sectionFormat="of" target="ARCH"/>, <tt>chat</tt>, <tt>audio</tt>, and <tt>video</tt> carry
response output, operation and protocol binding tracks carry
information output, and <tt>progress</tt> carries progress output. Extensions
define further tracks, such as the <tt>checkpoint</tt> track of PACE
Authorization (<xref target="delegation-approval"/>).</t>
          <t>Protocol bindings extend the dialog namespace with additional
namespace fields, so that multiple protocols can operate concurrently
within a single dialog without track name collisions:</t>
          <artwork><![CDATA[
("pace", "dialogs", {dialog-id}, {agent-id}, {proto}, {category},
 ...) -- {id}
]]></artwork>
          <ul spacing="normal">
            <li>
              <t><tt>{proto}</tt> is the protocol identifier of the binding: <tt>"mcp"</tt>,
<tt>"poppy"</tt>, <tt>"a2a"</tt>, or <tt>"ext"</tt> followed by a further field naming
another protocol (<xref target="protocol-bindings"/>).</t>
            </li>
            <li>
              <t><tt>{category}</tt> is the operation or primitive type (e.g., <tt>request</tt>,
<tt>response</tt>, <tt>task</tt> for A2A; <tt>tools</tt>, <tt>resources</tt>, <tt>prompts</tt> for MCP).</t>
            </li>
            <li>
              <t><tt>{id}</tt>, the track name, is the request, task, tool or resource
identifier. A binding <bcp14>MAY</bcp14> define further namespace fields between
<tt>{category}</tt> and the track name.</t>
            </li>
          </ul>
          <t>For example, in a dialog whose dialog-id is
<tt>550e8400-e29b-41d4-a716-446655440000</tt> (written <tt>D</tt> below), the
following Full Track Names are used:</t>
          <artwork><![CDATA[
A2A: "agent-a" sends request "r1" (in a dialog with "agent-b")
  ("pace","dialogs",D,"agent-a","a2a","request") -- "r1"

A2A: "agent-b" publishes updates for task "t1"
  ("pace","dialogs",D,"agent-b","a2a","task") -- "t1"

MCP: client "agent-a" calls tool "read_file" on "fs-server"
  ("pace","dialogs",D,"agent-a","mcp","tools","read_file")
      -- "request"

MCP: "fs-server" publishes the result of that call
  ("pace","dialogs",D,"fs-server","mcp","tools","read_file")
      -- "response"
]]></artwork>
          <t>The MCP tracks above are the <tt>request</tt> and <tt>response</tt> tracks of
<tt>(mcp, {server-id}, clients, {client-id}, tools, {tool-name})</tt> in MCP
over MOQT <xref target="MCP-MOQT"/>, with the leading
<tt>(mcp, {server-id}, clients, {client-id})</tt> fields replaced by the
dialog namespace and the publisher's agent-id (<xref target="mcp-binding"/>).</t>
          <t>See <xref target="example-workflows"/> for concrete examples of agent-to-agent,
agent-to-tool, and multi-agent collaboration workflows.</t>
        </section>
        <section anchor="invitations">
          <name>Invitations</name>
          <artwork><![CDATA[
  ("pace", "agents", {controller-id}, "invites") -- {invitee-id}
]]></artwork>
          <t>An agent learns a dialog's dialog-id before it can subscribe to the
dialog. A controller tells an invitee that follows it
(<xref target="agent-discovery"/>) by publishing on a track under its own agent
namespace, named by the invitee's agent-id. Each object, in its own
group, is a JSON object with these members:</t>
          <ul spacing="normal">
            <li>
              <t><tt>dialog_id</tt> — The dialog identifier</t>
            </li>
            <li>
              <t><tt>controller_id</tt> — The controller's agent-id</t>
            </li>
            <li>
              <t><tt>expires_at</tt> — Optional; the time after which the invitation is
void</t>
            </li>
          </ul>
          <t>An invitation only points to the dialog. The dialog context, including
the OPEN or UPDATE that invites the agent, stays on the controller's
<tt>ctrl</tt> track, which the invitee reads before deciding. Relay
authorization (<xref target="relay-authorization"/>) forwards each invitation track
only to the invitee it names, so other followers of the controller do
not see it. An invitee that comes online late catches up on pending
invitations with a join fetch and ignores those whose <tt>expires_at</tt> has
passed.</t>
          <t>An agent that does not follow the controller learns the dialog-id out
of band, for example through the application protocol's own channel
(<xref target="poppy-binding"/>).</t>
          <t>Editor's note: This document does not define how to invite an agent
that neither follows the controller nor can be reached out of band, or
how to advertise a dialog for others to join. These are left for
future work.</t>
        </section>
      </section>
      <section anchor="transport-binding">
        <name>Transport Binding</name>
        <section anchor="connection-establishment">
          <name>Connection Establishment</name>
          <t>Agents <bcp14>MUST</bcp14> establish either a native QUIC connection or a WebTransport
<xref target="WEBTRANS-H3"/> session as defined in <xref target="MoQ-TRANSPORT"/>. For native QUIC
connections, agents <bcp14>MUST</bcp14> use the ALPN value "moqt". For WebTransport,
the protocol is negotiated using the "WT-Available-Protocols" mechanism
as specified in <xref target="MoQ-TRANSPORT"/>.</t>
          <t>Upon establishing the MOQT session via the SETUP message exchange
defined in <xref target="MoQ-TRANSPORT"/>, an agent performs the bootstrap sequence
to make itself discoverable:</t>
          <ol spacing="normal" type="1"><li>
              <t>Announce: PUBLISH_NAMESPACE on <tt>("pace", "agents", {agent-id})</tt></t>
            </li>
            <li>
              <t>Publish Agent Card: PUBLISH on track <tt>"card"</tt> under its namespace</t>
            </li>
            <li>
              <t>Discover peers: SUBSCRIBE_NAMESPACE on <tt>("pace", "agents")</tt> to
learn about other agents on the network</t>
            </li>
          </ol>
          <t>See <xref target="agent-discovery"/> for the full discovery flow that follows
bootstrap.</t>
        </section>
        <section anchor="track-organization">
          <name>Track Organization</name>
          <t>Each agent publishes only under its own agent-id: its card and
invitations under <tt>("pace","agents",{agent-id})</tt>, and its dialog
tracks under <tt>("pace","dialogs",{dialog-id},{agent-id})</tt>. A
participant issues SUBSCRIBE_TRACKS on the dialog prefix to receive
the tracks of all participants. The relay handles fan-out to all
subscribers via prefix matching. This publishing model ensures clear
ownership and enables relay caching.</t>
          <t>Namespace structure and track names are defined in <xref target="namespace"/>.</t>
        </section>
        <section anchor="message-serialization">
          <name>Message Serialization</name>
          <t>Each PACE object payload is one protocol message, with no PACE
header: a control message (<xref target="control-encoding"/>) on <tt>ctrl</tt> tracks, an
invitation on invitation tracks, and the protocol's native message on
binding tracks. The
track namespace identifies the protocol, and MOQT carries the length.</t>
          <t>Payloads are uncompressed unless the participants agree on a
<tt>content_encoding</tt> dialog parameter (<xref target="dialog-parameters"/>). It
applies to binding tracks only, never to <tt>ctrl</tt> or invitation tracks.</t>
        </section>
        <section anchor="log-over-moqt">
          <name>Log Mapping</name>
          <t>The log of <xref target="dialog-log"/> maps onto MOQT without additional headers:</t>
          <ul spacing="normal">
            <li>
              <t>A flow is a track the participant publishes in the dialog, other
than <tt>ctrl</tt> and invitation tracks. In <tt>positions</tt>, <tt>flow</tt> takes the
form used by CANCEL <tt>target</tt> (<xref target="cancel-over-moqt"/>): <tt>namespace</tt>,
listing the namespace fields that follow
<tt>("pace","dialogs",{dialog-id},{agent-id})</tt>, and <tt>track</tt>.</t>
            </li>
            <li>
              <t>A log entry is an object, and its position is the object's Location.
<tt>accepted</tt> is encoded as <tt>{"group": G, "object": O}</tt>.</t>
            </li>
            <li>
              <t>The output class follows from the track name (<xref target="dialog-namespace"/>).
The delivery class is <tt>loss-tolerant</tt> for tracks sent with Datagram
Delivery Mode or a finite delivery timeout, and <tt>reliable</tt>
otherwise.</t>
            </li>
            <li>
              <t>Timestamps are not carried; a protocol binding that needs them
carries them in its native messages.</t>
            </li>
            <li>
              <t>A transformer publishes renderings under the namespace fields
<tt>("render", {source-id}, {source-track})</tt> after its own agent-id,
where <tt>{source-track}</tt> is a track the source publishes directly
under its dialog namespace, such as <tt>audio</tt> or <tt>chat</tt>,
with the rendering's label, such as a language tag, as the track
name. The <tt>{source-id}</tt> field gives <tt>source_id</tt>, and an object in
group G is derived from group G of the source track, which gives
<tt>derived_from</tt> at the granularity of a group.</t>
            </li>
          </ul>
          <t>A publisher makes entries available again by continuing to serve
them with FETCH; a relay's cache can serve them as well, but the
publisher does not rely on it. A receiver retrieves entries above its
accepted position with FETCH from the next Location, or with a join
fetch when it resumes a subscription (<xref target="dialog-recovery"/>). A
publisher that restarted without its earlier objects cannot make them
available again; it starts each track at a new group, and receivers
treat the missing range as described in <xref target="log-replay"/>.</t>
        </section>
      </section>
      <section anchor="dialog-over-moqt">
        <name>Dialog Operations over MOQT</name>
        <t>This section specifies how the operations of <xref target="dialog-management"/> are
carried over MOQT. Each control message is one MOQT object on the
sender's <tt>ctrl</tt> track under
<tt>("pace","dialogs",{dialog-id},{agent-id})</tt>. MOQT control messages
(PUBLISH, SUBSCRIBE, their responses, PUBLISH_DONE) establish and end
the subscriptions that carry those objects. They are not dialog
operations: PUBLISH_OK accepts a MOQT subscription, not a dialog, and a
participant <bcp14>MUST NOT</bcp14> infer acceptance, rejection, or termination of a
dialog from a MOQT response or cancellation alone.</t>
        <t>The <tt>ctrl</tt> track <bcp14>MUST</bcp14> use Subgroup Delivery Mode and <bcp14>MUST NOT</bcp14> use
Datagram Delivery Mode or a finite delivery timeout. A participant
publishes control objects in increasing Object ID order, and the
controller publishes state-changing operations in increasing
generation order. Because <tt>ctrl</tt> is a track of its own, a CANCEL,
ERROR, or TERMINATE is not lost or delayed when a content track fails
or falls behind.</t>
        <section anchor="opening">
          <name>Opening a Dialog</name>
          <t>Prerequisite: B learns the dialog-id from A's invitation, which
requires that B follows A (<xref target="agent-discovery"/>), or out of band. A
does not need B's prefix: all participants' tracks are under the
dialog prefix.</t>
          <t>Below, PUBLISH, SUBSCRIBE, and SUBSCRIBE_TRACKS are MOQT messages;
OPEN, ACCEPT, and UPDATE are PACE control messages sent as objects on
the sender's <tt>ctrl</tt> track. Agent A (controller) opens a dialog with
Agent B (invitee):</t>
          <ol spacing="normal" type="1"><li>
              <t>A generates a dialog-id (UUID version 4) and issues
SUBSCRIBE_TRACKS on <tt>("pace","dialogs",{dialog-id})</tt>, which covers
all participants' tracks, including future ones.</t>
            </li>
            <li>
              <t>A issues PUBLISH for
<tt>("pace","dialogs",{dialog-id},"agent-a") -- "ctrl"</tt> and sends OPEN
on it, listing B as <tt>invited</tt>, with <tt>parameters</tt>
(<xref target="dialog-parameters"/>) and <tt>credentials</tt>.</t>
            </li>
            <li>
              <t>A sends an invitation on
<tt>("pace","agents","agent-a","invites") -- "agent-b"</tt>
(<xref target="invitations"/>), which B subscribed to when it started following
A.</t>
            </li>
            <li>
              <t>B issues SUBSCRIBE with FILL_PARAMETERS on A's <tt>ctrl</tt> track, reads
OPEN, and decides. Until it accepts, B subscribes to nothing else,
so it receives no dialog content.</t>
            </li>
            <li>
              <t>B issues PUBLISH for
<tt>("pace","dialogs",{dialog-id},"agent-b") -- "ctrl"</tt> and sends
ACCEPT (or REJECT) on it, with its parameters and credentials. On
accepting, B issues SUBSCRIBE_TRACKS on the dialog prefix, which
also covers A's <tt>ctrl</tt> track.</t>
            </li>
            <li>
              <t>The relay forwards B's PUBLISH to A through A's SUBSCRIBE_TRACKS
from step 1, and A reads ACCEPT.</t>
            </li>
            <li>
              <t>A sends UPDATE (generation 1) on its <tt>ctrl</tt> track, marking B and
the dialog <tt>active</tt>. If B rejected, the UPDATE marks B <tt>rejected</tt>,
and B ends its <tt>ctrl</tt> track with PUBLISH_DONE.</t>
            </li>
          </ol>
          <t>Tracks either agent publishes later reach every participant through
its SUBSCRIBE_TRACKS on the dialog prefix. Multi-party dialogs follow
the same pattern, and existing participants receive a new
participant's tracks without subscribing again.</t>
        </section>
        <section anchor="joining">
          <name>Joining a Dialog</name>
          <t>An agent that knows a dialog's dialog-id but was not invited asks to
join by issuing PUBLISH for its own <tt>ctrl</tt> track,
<tt>("pace","dialogs",{dialog-id},{joiner-id}) -- "ctrl"</tt>, and sending
JOIN_REQUEST as the first object on it. The relay forwards the
PUBLISH to every participant holding SUBSCRIBE_TRACKS on the dialog
prefix, not only the controller. Only the controller acts on
JOIN_REQUEST; other participants <bcp14>MUST</bcp14> ignore it, and <bcp14>MAY</bcp14> decline a
PUBLISH for a track whose agent-id is not in the dialog context. A
joiner therefore discloses in its credentials only claims it is
willing for every participant to see. The controller validates the
credentials and decides whether to admit the joiner. The joiner
subscribes to the controller's <tt>ctrl</tt> track with FILL_PARAMETERS, so
it receives the current dialog state as well as the answer. To
admit it, the controller invites the joiner with UPDATE, the joiner
answers with ACCEPT and subscribes to the dialog prefix, and the
controller's next UPDATE marks it <tt>active</tt>. A controller that declines
answers with ERROR <tt>policy-rejected</tt>, and the joiner then ends its
<tt>ctrl</tt> track with PUBLISH_DONE. Before admission, the joiner's
authorization covers only publishing its own <tt>ctrl</tt> track and reading
the controller's (<xref target="relay-authorization"/>). A joiner with a <tt>sponsor</tt>
or a <tt>join_code</tt> follows the same steps; the controller admits it as
<xref target="sponsored-admission"/> and <xref target="joining-codes"/> require.</t>
          <section anchor="moqt-setup-extensions">
            <name>MOQT Setup Extensions</name>
            <t>MOQT Setup Options are exchanged hop by hop.
PACE defines one Setup Option, which lets a PACE-aware relay or a
directly connected peer learn that the endpoint implements PACE:</t>
            <table>
              <thead>
                <tr>
                  <th align="left">Setup Option</th>
                  <th align="left">ID</th>
                  <th align="left">Description</th>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td align="left">pace-version</td>
                  <td align="left">0x50414301</td>
                  <td align="left">Highest PACE control-message version supported</td>
                </tr>
              </tbody>
            </table>
            <t>The <tt>version</tt> member of each control message remains authoritative.</t>
          </section>
        </section>
        <section anchor="idle-detection">
          <name>Idle Detection</name>
          <t>In this binding, a dialog is idle (<xref target="dialog-lifetime"/>) while no
participant publishes an object on any of its tracks.</t>
        </section>
        <section anchor="updating-a-dialog">
          <name>Updating a Dialog</name>
          <t>The controller changes the participant set or the expiration by
publishing UPDATE on its <tt>ctrl</tt> track with the complete context at the
next generation. Participants request changes with JOIN_REQUEST or
LEAVE; only the controller commits them. Parameter changes, such as
adding a modality, are proposed in <tt>parameters</tt> on UPDATE, and each
participant answers with ACCEPT or REJECT (<xref target="lifecycle"/>). An UPDATE
that adds a participant is followed by an invitation to it
(<xref target="invitations"/>).</t>
          <t>A participant sends DECLARE on its own <tt>ctrl</tt> track; because every
participant subscribes to the dialog prefix, each sees the DECLARE as
well as the controller's committing UPDATE, and can compare them
(<xref target="participant-descriptors"/>). The controller sends SEGMENT on its
<tt>ctrl</tt> track, opens the segment dialog with a dialog-id of its own,
and invites only the segment's participants to it; relays authorize
that dialog's namespace for them alone (<xref target="relay-authorization"/>).</t>
          <t>Participants <bcp14>MAY</bcp14> use MOQT's REQUEST_UPDATE message
to change per-subscription parameters, such as pausing delivery with
FORWARD=0, resuming with FORWARD=1, or changing priorities and
filters, without tearing down the subscription. REQUEST_UPDATE is the
right tool for track-level changes that do not need dialog-wide
agreement; pausing a video track while chat and ctrl keep flowing is
a typical case. Pausing a subscription does not stop the publisher
from producing objects and is not a cancellation.</t>
        </section>
        <section anchor="dialog-recovery">
          <name>Recovery</name>
          <t>PACE recovers from network and intermediary failures in several ways:</t>
          <ul spacing="normal">
            <li>
              <t>QUIC Connection Migration: QUIC's connection ID lets a MOQT session
survive network path changes (such as WiFi to cellular). The dialog
state is unaffected.</t>
            </li>
            <li>
              <t>Relay Caching: Relays may cache recent objects, so a reconnecting
agent can pick up what it missed without the peer retransmitting.
Relays are not required to cache, and they never become the
authoritative source of the dialog context.</t>
            </li>
            <li>
              <t>Dialog Resumption: After losing its MOQT session, which it detects
through the QUIC idle timeout or a subscription timeout, an agent
reconnects
(to the same relay or an alternate one), re-issues PUBLISH_NAMESPACE
on its agent namespace, its follow subscriptions
(<xref target="agent-discovery"/>), and SUBSCRIBE_TRACKS on the dialog prefix,
which includes the controller's <tt>ctrl</tt> track, and sends STATE_REQUEST with its last
accepted generation. It applies the controller's STATE only after
authenticating the controller and checking that the generation is not
older than its last accepted one (<xref target="generations"/>). It then sends
LOG_STATUS (<xref target="log-replay"/>) and fetches, on each content track, the
objects after the accepted position it holds.</t>
            </li>
            <li>
              <t>Join Fetch for Mid-Dialog Catch-Up: An agent joining a dialog in
progress, or recovering after a disconnect, uses the fill fetch
mechanism from <xref target="MoQ-TRANSPORT"/>. The subscriber issues SUBSCRIBE with
FILL_PARAMETERS on the chat or operation track; the publisher opens a
unidirectional fill fetch stream carrying the historical range
(typically the latest complete group) before live objects resume on
the subscription. "Catch up on prior content, then follow live"
happens atomically, without a separate FETCH roundtrip. For the dialog
context itself, STATE is authoritative; a fetched old <tt>ctrl</tt> object
cannot establish the current lifecycle state by itself.</t>
            </li>
            <li>
              <t>Bounded Historical Fetch: To retrieve a specific range of past objects
deterministically, for example replaying a task's output history,
agents use FETCH with explicit Start and End Locations. The publisher
confirms the actual End Location in FETCH_OK.</t>
            </li>
            <li>
              <t>Unreachable Controller: If the controller's <tt>ctrl</tt> track cannot be
resubscribed, participants follow the unreachability rules in
<xref target="propagation"/>: they suspend context-dependent actions and do not
create a replacement dialog. If the context names an
<tt>alternate_controller_id</tt>, the alternate can take over
(<xref target="controller-transfer"/>); its <tt>ctrl</tt> track already reaches every
participant through their subscription to the dialog prefix. A slow
subscriber whose subscription ends with PUBLISH_DONE
(TOO_FAR_BEHIND) resubscribes and resynchronizes with STATE_REQUEST.</t>
            </li>
            <li>
              <t>Mediator Failover: A relay is never authoritative, so an agent whose
relay fails reconnects through another relay without changing the
dialog. An application-level mediator that is a participant is
replaced by the controller with REVOKE and UPDATE; one that is the
controller is replaced by controller transfer.</t>
            </li>
          </ul>
          <section anchor="device-handover">
            <name>Moving to Another Device</name>
            <t>A participant, such as a user's client, can continue a dialog on
another device under the same agent-id. Two instances <bcp14>MUST NOT</bcp14> publish
the same track at the same time.</t>
            <ol spacing="normal" type="1"><li>
                <t>The new instance obtains the participant's credentials and key,
connects to a relay, and subscribes to the dialog prefix.</t>
              </li>
              <li>
                <t>The old instance, if reachable, ends its dialog tracks with
PUBLISH_DONE and its subscription to the dialog prefix.</t>
              </li>
              <li>
                <t>If the participant is not the controller, the new instance resumes
with STATE_REQUEST and a key-bound presentation (<xref target="key-binding"/>).
If it is the controller, the new instance first recovers its own
last control objects with FETCH on its <tt>ctrl</tt> track, and publishes
no state-changing operation until it holds the latest generation.</t>
              </li>
              <li>
                <t>The new instance publishes its tracks, starting each content track
at a new group, and uses join fetch on content tracks to restore
the history it shows to the user.</t>
              </li>
            </ol>
            <t>If the old instance is unreachable and later returns, it sees the new
instance's objects on its own tracks, stops publishing, and
resynchronizes.</t>
          </section>
        </section>
        <section anchor="cancel-over-moqt">
          <name>Cancellation</name>
          <t>A participant sends CANCEL (<xref target="cancellation"/>) as an object on its
<tt>ctrl</tt> track at critical priority (0-15). Scopes <tt>dialog</tt> and
<tt>subtree</tt> need no <tt>target</tt>. For scope <tt>subtree</tt>, a receiver that
controls a delegated dialog whose <tt>parent_dialog_ids</tt> include this
dialog sends CANCEL with scope <tt>dialog</tt> on its own <tt>ctrl</tt> track in
that delegated dialog. For scope <tt>operation</tt>, <tt>target</tt> names a track
the sender publishes in the dialog and, optionally, a group on it:</t>
          <sourcecode type="json"><![CDATA[
{
  "namespace": ["mcp", "tools", "search"],
  "track": "request",
  "group": 3
}
]]></sourcecode>
          <t><tt>namespace</tt> lists the namespace fields that follow
<tt>("pace","dialogs",{dialog-id},{agent-id})</tt>. Without <tt>group</tt>, all work
started by objects on the track is cancelled. An ERROR that rejects an
application operation (<xref target="error-reasons"/>) uses the same form, with an
additional <tt>publisher</tt> member giving the agent-id that published the
operation, since the rejecting participant is not its publisher. Each receiver doing the
affected work publishes CANCEL_ACK on its own <tt>ctrl</tt> track and stops
publishing objects for that work, ending a track that carried only
that work with PUBLISH_DONE.</t>
          <t>Pausing delivery with REQUEST_UPDATE (FORWARD=0), unsubscribing, or
closing a MOQT session does not cancel work.</t>
        </section>
        <section anchor="termination-and-revocation">
          <name>Termination and Revocation</name>
          <t>The controller ends the dialog by sending TERMINATE on its <tt>ctrl</tt>
track (<xref target="termination"/>). Upon termination, pending operations are
cancelled, each participant terminates the delegated dialogs it
controls (<xref target="lifecycle-propagation"/>), and dialog resources are
released after a configurable grace period.</t>
          <t>After TERMINATE, or when <tt>expires_at</tt> passes, each participant <bcp14>SHOULD</bcp14>
send PUBLISH_DONE on every dialog track it was publishing (ctrl,
chat, audio, video, and any operation tracks), and ends its
subscription to the dialog prefix. PUBLISH_DONE signals that no
further objects will be delivered on the track, allowing subscribers
and relays to release state without waiting for timeouts. Neither
PUBLISH_DONE nor STOP_SENDING substitutes for TERMINATE.</t>
          <t>A participant leaves by sending LEAVE on its <tt>ctrl</tt> track. The
controller commits it with UPDATE, marking the participant <tt>left</tt>,
and <bcp14>SHOULD</bcp14> send TERMINATE if only the controller remains active
(<xref target="lifecycle"/>). The leaver then ends its tracks with PUBLISH_DONE and
its subscription to the dialog prefix.</t>
          <t>When the controller sends REVOKE, every participant stops forwarding
dialog context to the revoked participant and cancels any
subscriptions held only on its behalf (<xref target="lifecycle"/>). The revoked
participant ends its tracks with PUBLISH_DONE, and participants <bcp14>MAY</bcp14>
decline its later PUBLISHes. The deployment
also withdraws the revoked participant's authorization at the relay,
for example by letting its <xref target="MoQ-C4M"/> token expire or by refusing
revalidation, so that the relay stops delivering the participant's
subscriptions to the dialog's tracks.</t>
          <t>When an agent is leaving the network entirely (not just a single
dialog), it cancels its PUBLISH_NAMESPACE for
<tt>("pace","agents",{agent-id})</tt>. Relays then send NAMESPACE_DONE to
agents with matching SUBSCRIBE_NAMESPACE subscriptions.</t>
        </section>
      </section>
    </section>
    <section anchor="data-exchange">
      <name>Multi-Modal Data Exchange</name>
      <t>Over the MOQT binding, a dialog can carry several data modalities
concurrently, each with appropriate quality of service. This content
is outside the dialog context; a change of modality does not change
the dialog (<xref target="propagation"/>).</t>
      <section anchor="modality-types">
        <name>Modality Types</name>
        <t>PACE defines the following data modality classes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Modality</th>
              <th align="left">Latency</th>
              <th align="left">Examples</th>
              <th align="left">Delivery</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Real-time</td>
              <td align="left">&lt; 100ms</td>
              <td align="left">Voice, video, screen share</td>
              <td align="left">Continuous stream</td>
            </tr>
            <tr>
              <td align="left">Semi-real-time</td>
              <td align="left">&lt; 1s</td>
              <td align="left">Chat messages, streaming LLM output</td>
              <td align="left">Ordered objects</td>
            </tr>
            <tr>
              <td align="left">Non-real-time</td>
              <td align="left">Best effort</td>
              <td align="left">Tool calls, file transfers, documents</td>
              <td align="left">Reliable delivery</td>
            </tr>
          </tbody>
        </table>
        <t>These classes correspond to the low-latency loss-tolerant, reliable
ordered, and high-throughput reliable delivery semantics of
<xref section="8.1" sectionFormat="of" target="ARCH"/>.</t>
      </section>
      <section anchor="channels">
        <name>Channel Architecture</name>
        <t>Each modality maps to dedicated MOQT tracks within the dialog
namespace (<xref target="dialog-namespace"/>). Different modalities are
isolated by track name while sharing the dialog context and
authorization.</t>
        <t>Within a track, a MOQT group is a synchronization point. The objects
in a group carry what belongs together at that point, such as one
message, one request and its incremental results, or one phase of an
operation, and relays carry them together. A publisher starts a new
group at each point where a receiver can begin consuming the track
without earlier objects, so a subscriber that joins or recovers starts
at a group boundary (<xref target="dialog-recovery"/>).</t>
      </section>
      <section anchor="priority-and-quality-of-service">
        <name>Priority and Quality of Service</name>
        <t>MOQT's 0-255 priority scale enables differentiated treatment of messages
based on urgency and modality. PACE defines the following tiers of
subscriber priority:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Priority Range</th>
              <th align="left">Category</th>
              <th align="left">Use</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0-15</td>
              <td align="left">Dialog Control</td>
              <td align="left">All control messages on the <tt>ctrl</tt> track, including CANCEL, ERROR, and REVOKE</td>
            </tr>
            <tr>
              <td align="left">16-31</td>
              <td align="left">Urgent Signals</td>
              <td align="left">Signals that must preempt content, such as authorization checkpoints (<xref target="delegation-approval"/>) or a request for a human</td>
            </tr>
            <tr>
              <td align="left">32-63</td>
              <td align="left">Real-time Media</td>
              <td align="left">Voice/video frames</td>
            </tr>
            <tr>
              <td align="left">64-95</td>
              <td align="left">Interactive</td>
              <td align="left">Chat messages, streaming LLM tokens</td>
            </tr>
            <tr>
              <td align="left">96-127</td>
              <td align="left">Standard Operations</td>
              <td align="left">Tool calls, request/response</td>
            </tr>
            <tr>
              <td align="left">128-159</td>
              <td align="left">Discovery</td>
              <td align="left">Agent Cards, invitations</td>
            </tr>
            <tr>
              <td align="left">160-191</td>
              <td align="left">Background</td>
              <td align="left">Telemetry, non-critical notifications</td>
            </tr>
            <tr>
              <td align="left">192-255</td>
              <td align="left">Bulk Transfer</td>
              <td align="left">File transfers, documents</td>
            </tr>
          </tbody>
        </table>
        <t>MOQT relays forward Publisher Priority unchanged, so PACE applies
policy through subscriber priority, which MOQT applies before publisher
priority. A subscriber sets the subscriber priority of each
subscription according to its policy for that peer and track, and can
change it with REQUEST_UPDATE, so a publisher cannot raise the urgency
of its traffic beyond what its subscribers allow. A subscriber <bcp14>MUST</bcp14>
subscribe to a <tt>ctrl</tt> track with a subscriber priority in the Dialog
Control tier.</t>
      </section>
      <section anchor="request-response">
        <name>Request/Response Pattern</name>
        <t>Request/response interactions use coordinated publish operations.
Agent A publishes a request object on its own track
<tt>("pace","dialogs",{dialog-id},"agent-a") -- "ops/{req-id}"</tt>. Agent B,
which has subscribed to the dialog prefix, receives the request,
processes it, and publishes the response on its own corresponding track
<tt>("pace","dialogs",{dialog-id},"agent-b") -- "ops/{req-id}"</tt>. Agent A
receives the response through its own subscription to the dialog
prefix.</t>
        <t>For a detailed example of request/response over MOQT tracks, see
<xref target="MCP-MOQT"/> which defines this pattern for MCP tool invocations.</t>
      </section>
      <section anchor="streaming">
        <name>Streaming Pattern</name>
        <t>Long-running operations produce incremental results as MOQT objects.
The publisher starts a new group at each synchronization point
(<xref target="channels"/>), such as a phase transition (initialization, progress,
completion), and the objects in a group carry the incremental data for
that phase.</t>
        <t>Late-joining subscribers catch up mid-operation with a join fetch, and
retrieve a specific range with a bounded fetch (<xref target="dialog-recovery"/>).</t>
        <t>Upon operation completion, the publisher sends PUBLISH_DONE on the
operation track to signal end-of-stream. Receivers treat PUBLISH_DONE
as the authoritative completion marker; publishers <bcp14>MUST NOT</bcp14> emit
further objects on that track after PUBLISH_DONE.</t>
        <t>To cancel an in-progress streaming operation, the requester publishes
CANCEL on its <tt>ctrl</tt> track (<xref target="cancel-over-moqt"/>), or the application
protocol's own cancel message on its request or operation track. The
publisher then stops the operation and sends PUBLISH_DONE to end the
stream. REQUEST_UPDATE with
FORWARD=0 only pauses delivery to that subscriber; it does not cancel
the operation.</t>
      </section>
      <section anchor="real-time-media-exchange">
        <name>Real-Time Media Exchange</name>
        <t>Audio and video streams use dedicated tracks (<tt>"audio"</tt>, <tt>"video"</tt>)
with ascending group order and high priority (32-63),
ensuring media frames preempt lower-priority data under congestion.</t>
      </section>
    </section>
    <section anchor="topologies">
      <name>Communication Topologies</name>
      <t>PACE supports multiple communication topologies through MOQT's relay
fan-out:</t>
      <ul spacing="normal">
        <li>
          <t>Point-to-Point: Two agents publish and subscribe to each other's
dialog tracks. Used for tool invocation, task delegation, and
bilateral collaboration.</t>
        </li>
        <li>
          <t>Point-to-Multipoint (Fan-Out): One agent publishes; multiple agents
subscribe. The relay handles fan-out without the publisher maintaining
per-subscriber state. Used for broadcast notifications and shared
context distribution.</t>
        </li>
        <li>
          <t>Multi-Party: All participants publish on their own tracks and
subscribe to the dialog prefix. The controller adds a participant
with UPDATE; existing participants see the new participant in the
context and receive its tracks through their existing subscription.</t>
        </li>
        <li>
          <t>Hierarchical Teams: A coordinator creates child PACE dialogs to
delegate subtasks. Each level operates as a separate dialog with
narrowed authorization scope, and each child's <tt>parent_dialog_ids</tt>
links it to the dialogs above it (<xref target="dialog-context"/>). Delegation
chains (<xref target="delegation"/>) maintain an auditable path from the
original user authorization, and CANCEL with scope <tt>subtree</tt> stops the
work below a level (<xref target="cancellation"/>).</t>
        </li>
      </ul>
      <t>A dialog has one visibility scope: every participant subscribes to the
dialog prefix and can receive every other participant's tracks. When
participants must not see each other's traffic, such as tools from
different administrative domains used by one agent, or a subset of
agents that needs a private exchange, the agent <bcp14>SHOULD</bcp14> open a separate
delegated dialog for each, linked by <tt>parent_dialog_ids</tt>, rather than
adding them to one dialog. When the other participants need to know
that such an exchange happened and its result, as for a masked payment
or an off-the-record span, the controller announces it as a segment
(<xref target="segments"/>).</t>
    </section>
    <section anchor="identity-discovery">
      <name>Agent Identity and Discovery</name>
      <section anchor="agent-identity-model">
        <name>Agent Identity Model</name>
        <t>PACE treats the agent as an authenticated party distinct from the
principal it represents. Separating the two makes it possible to revoke an
agent without affecting the user, scope an agent to a subset of what
the user is allowed to do, and audit what the agent did on its own
versus what the user initiated.</t>
        <t>PACE does not define a new identity token format or claim set. The
credential an agent presents in the <tt>credentials</tt> member of the
control message it uses to open, accept, or join a dialog
(<xref target="control-encoding"/>) identifies:</t>
        <ul spacing="normal">
          <li>
            <t>the agent, by its participant identifier in the dialog or by an
identifier that the protocol binding relates to it, such as the
Poppy <tt>client_id</tt> (<xref target="poppy-binding"/>);</t>
          </li>
          <li>
            <t>the user, workload, or organization the agent acts for; and</t>
          </li>
          <li>
            <t>when the agent acts for another agent, the delegation chain
(<xref target="delegation"/>).</t>
          </li>
        </ul>
        <t>In JWT-based formats, these map to the registered claims <tt>sub</tt>, <tt>iss</tt>,
<tt>iat</tt>, and <tt>exp</tt> <xref target="RFC7519"/> and to the <tt>act</tt> (actor) claim
<xref target="RFC8693"/> for delegation. <tt>sub</tt> identifies the principal: the user,
workload, or organization on whose behalf the work is done, not the
agent presenting the credential. The acting agent is identified by
<tt>client_id</tt> or by the outermost <tt>act</tt>, and the meaning and validation
of <tt>act</tt> chains follow the OAuth Actor Profile <xref target="ACTOR-PROFILE"/>. Other
formats carry the equivalent information in their own fields. Other
documents can profile how a person's sign-in with OpenID Connect,
cross-domain grants, and out-of-band approval relate to these
credentials; an ID Token is not a PACE credential. The token format and the trust
framework are chosen by the deployment.</t>
        <section anchor="identity-formats">
          <name>Credential Mechanisms</name>
          <t>Agents present credentials using existing mechanisms. The mechanism in
use is advertised in the Agent Card (<xref target="agent-card"/>) and indicated in
the <tt>credentials</tt> member of control messages; it is not negotiated in
MOQT SETUP, which is hop by hop (<xref target="moqt-setup-extensions"/>).</t>
          <table>
            <thead>
              <tr>
                <th align="left">Mechanism</th>
                <th align="left">Identity</th>
                <th align="left">Authorization</th>
                <th align="left">Reference</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">JWT</td>
                <td align="left">Agent and principal claims</td>
                <td align="left">Scope claims</td>
                <td align="left">
                  <xref target="RFC7519"/></td>
              </tr>
              <tr>
                <td align="left">SD-JWT</td>
                <td align="left">Selectively disclosed claims</td>
                <td align="left">Selectively disclosed scope claims</td>
                <td align="left">
                  <xref target="RFC9901"/></td>
              </tr>
              <tr>
                <td align="left">SD-Card</td>
                <td align="left">Attested agent metadata, key-bound presentation</td>
                <td align="left">Disclosure per discovery context</td>
                <td align="left">
                  <xref target="SD-CARD"/></td>
              </tr>
              <tr>
                <td align="left">OAuth 2.1 access token (JWT or opaque)</td>
                <td align="left">Token claims</td>
                <td align="left">Delegated user authorization</td>
                <td align="left">
                  <xref target="OAUTH-2.1"/></td>
              </tr>
              <tr>
                <td align="left">GNAP</td>
                <td align="left"> </td>
                <td align="left">Fine-grained, continuous grants</td>
                <td align="left">
                  <xref target="RFC9635"/></td>
              </tr>
              <tr>
                <td align="left">WIMSE workload credentials</td>
                <td align="left">Workload identity</td>
                <td align="left">With deployment policy</td>
                <td align="left">
                  <xref target="WIMSE-CREDS"/></td>
              </tr>
              <tr>
                <td align="left">WIMSE Workload Proof Token with message binding</td>
                <td align="left">Proof of possession bound to the control message</td>
                <td align="left">Binds the tokens presented with it</td>
                <td align="left">
                  <xref target="WIMSE-WPT"/>, <xref target="WPT-MSG"/></td>
              </tr>
              <tr>
                <td align="left">mTLS client certificate</td>
                <td align="left">Infrastructure-anchored identity</td>
                <td align="left">With deployment policy</td>
                <td align="left">
                  <xref target="RFC9846"/></td>
              </tr>
              <tr>
                <td align="left">OAuth Client ID Metadata Document</td>
                <td align="left">Agent keys published at its own HTTPS <tt>client_id</tt> URL</td>
                <td align="left">With deployment policy</td>
                <td align="left">
                  <xref target="CIMD"/></td>
              </tr>
              <tr>
                <td align="left">Common Access Token (CAT)</td>
                <td align="left"> </td>
                <td align="left">Relay-level namespace authorization</td>
                <td align="left">
                  <xref target="MoQ-C4M"/></td>
              </tr>
            </tbody>
          </table>
          <t>WIMSE workload credentials and mTLS need trust anchors configured in
advance. Agents with no prior relationship, such as a person's agent
contacting a business for the first time, can instead identify
themselves by an HTTPS URL at which they publish a client metadata
document with their keys <xref target="CIMD"/>; a verifier fetches it and checks a
key-bound presentation (<xref target="key-binding"/>) against those keys. This
shows that the agent controls the URL's domain, not who operates it
or whom it acts for.</t>
          <t>A deployment profile <bcp14>MUST</bcp14> pick at least one mechanism for identity and
one for authorization; one mechanism can provide both. Receivers <bcp14>MUST</bcp14>
verify a credential's signature, issuer, and expiration before acting
on its claims, and validate authorization using the rules of the
mechanism in use.</t>
        </section>
        <section anchor="delegation">
          <name>Delegation Chains</name>
          <t>When an agent acts on behalf of another agent, its credential carries
the delegation chain, such as nested <tt>act</tt> claims <xref target="RFC8693"/>, tracing
the authorization path (for example, User → Coordinator → Researcher
→ Tool). Where an authorization server issues each hop's token, the
chain is that server's assertion, with the semantics of
<xref target="ACTOR-PROFILE"/>. Where agents in different trust domains delegate
to each other without an authorization server, the chain is a
sequence of Delegation Tokens <xref target="DELEGATION-TOKENS"/> in which each hop
is signed by its delegator <xref target="AGENT-DELEGATION"/>. PACE carries the credential in OPEN and identifies the
delegated dialog's parents in <tt>parent_dialog_ids</tt>; it does not define
delegation semantics. How a delegation credential is bound to the
delegated dialog, how authority narrows at each hop, which credential
formats suit which deployments, how cycles are rejected (with ERROR
<tt>delegation-cycle</tt>), and how revocation of a delegation terminates the
dialogs that depend on it are specified in PACE Authorization
(<xref target="delegation-approval"/>).</t>
        </section>
        <section anchor="selective-disclosure">
          <name>Selective Disclosure</name>
          <t>Different peers need different claims: a tool may need only the
agent identifier and its authorization, not the delegation chain or
the principal. Agents <bcp14>SHOULD</bcp14> disclose only what each peer requires,
using the selective disclosure of the mechanism in use
(<xref target="identity-formats"/>). For agent metadata, SD-Card <xref target="SD-CARD"/> lets
an agent disclose issuer-attested claims per peer, and an Agent Card
(<xref target="agent-card"/>) can be an SD-Card.</t>
          <t>Selective disclosure does not make agents anonymous: an SD-Card's
<tt>sub</tt> is always disclosed and stable, so its presentations can be
linked (<xref section="3.1" sectionFormat="of" target="SD-CARD"/>). Identifier linkage is addressed
in <xref target="privacy"/>.</t>
        </section>
        <section anchor="key-binding">
          <name>Key-Bound Presentation</name>
          <t>A presentation proves possession only when it is bound to the
verifier and to a fresh value from it, such as an SD-Card Key Binding
JWT (<xref section="6" sectionFormat="of" target="SD-CARD"/>). A verifier sends a <tt>nonce</tt> in its
control message (<xref target="control-encoding"/>), and the peer's next control
message carries, in its <tt>credentials</tt> member, a presentation bound to
that nonce, with the verifier's agent-id as audience.</t>
          <t>A presentation also binds the control message that carries it, so
that a copy of it in another message does not verify. It does so with
the <tt>mth</tt> claim of <xref target="WPT-MSG"/>, computed under the <tt>pace</tt>
canonicalization profile below. Each presentation carries <tt>aud</tt> (the
verifier's agent-id), <tt>mth</tt>, and <tt>nonce</tt> (the verifier's nonce),
except that a first message has no nonce to carry (<xref target="first-message"/>).
PACE supports three presentation types, one for each kind of
credential, and a verifier tells them apart by the JOSE <tt>typ</tt> header:</t>
          <table anchor="_table-presentations">
            <name>Presentation Types</name>
            <thead>
              <tr>
                <th align="left">Presentation type</th>
                <th align="left">typ</th>
                <th align="left">Used with</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Workload Proof Token <xref target="WIMSE-WPT"/></td>
                <td align="left">
                  <tt>wpt+jwt</tt></td>
                <td align="left">WIMSE workload credentials</td>
              </tr>
              <tr>
                <td align="left">Key Binding JWT <xref target="RFC9901"/></td>
                <td align="left">
                  <tt>kb+jwt</tt></td>
                <td align="left">SD-JWT and SD-Card credentials</td>
              </tr>
              <tr>
                <td align="left">PACE presentation JWT (<xref target="presentation-jwt"/>)</td>
                <td align="left">
                  <tt>pace-presentation+jwt</tt></td>
                <td align="left">Other credentials bound to a key</td>
              </tr>
            </tbody>
          </table>
          <t>A Workload Proof Token is carried in the message as <xref target="WPT-MSG"/>
describes; a Key Binding JWT carries <tt>mth</tt> as an additional claim. The
PACE presentation JWT covers credentials whose key a <tt>cnf</tt> claim
<xref target="RFC7800"/> confirms, such as a DPoP-bound access token or a JWT; keys
published in a Client ID Metadata Document <xref target="CIMD"/>; and the key of an
mTLS client certificate, which cannot be proven to a peer over TLS
because relays terminate it.</t>
          <t>A participant that verifies key-bound presentations <bcp14>MUST</bcp14> support the
PACE presentation JWT, which works with any credential bound to a key.
It supports the other types as the credential mechanisms of its
deployment require (<xref target="identity-formats"/>).</t>
          <t>A credential bound to no key, such as a bearer token, cannot be bound
to a presentation. A verifier relies on it only as far as its
credential mechanism and the deployment's policy allow.</t>
          <t>The <tt>pace</tt> profile applies the <tt>json-jcs</tt> profile of <xref target="WPT-MSG"/> to a
PACE control message, with <tt>credentials</tt> as the credential member: the
<tt>mth</tt> hash is computed over the JCS <xref target="RFC8785"/> form of the control
message with its <tt>credentials</tt> member removed. A presentation can
therefore travel inside the message it binds, and a copy of it in
another message does not verify.</t>
          <section anchor="presentation-jwt">
            <name>PACE Presentation JWT</name>
            <t>Some credentials are bound to a key but have no proof that a PACE peer
can check. A DPoP proof <xref target="RFC9449"/> covers an HTTP request, not a
control message. An mTLS client certificate is proven in the TLS
handshake, which ends at the first relay. A JWT with a <tt>cnf</tt> claim, or
a key published in a Client ID Metadata Document, has no presentation
of its own. Without a proof, a peer cannot tell the credential's
holder from anyone who copied it.</t>
            <t>A participant that presents such a credential therefore sends a PACE
presentation JWT with it, in the same <tt>credentials</tt> member, in each
control message that carries the credential. A participant whose
credential has its own presentation, a Workload Proof Token or a Key
Binding JWT, uses that instead.</t>
            <t>A PACE presentation JWT is a JWT <xref target="RFC7519"/>, signed with JWS
<xref target="RFC7515"/> by the private key that the credential it accompanies
confirms. Its <tt>alg</tt> <bcp14>MUST</bcp14> be an asymmetric digital signature algorithm,
and <bcp14>MUST NOT</bcp14> be <tt>none</tt> or a MAC algorithm. Its JOSE header carries:</t>
            <ul spacing="normal">
              <li>
                <t><tt>typ</tt>: <bcp14>REQUIRED</bcp14>. <tt>pace-presentation+jwt</tt>.</t>
              </li>
              <li>
                <t><tt>jwk</tt> or <tt>x5c</tt>: The public key as a JWK when the credential
confirms only a key thumbprint, or the certificate chain for an
mTLS client certificate. Omitted when the credential carries the key
itself.</t>
              </li>
            </ul>
            <t>Its claims are:</t>
            <ul spacing="normal">
              <li>
                <t><tt>aud</tt>: <bcp14>REQUIRED</bcp14>. The verifier's agent-id, or an array of the
agent-ids of several verifiers <xref target="RFC7519"/>.</t>
              </li>
              <li>
                <t><tt>nonce</tt>: The verifier's <tt>nonce</tt>. <bcp14>REQUIRED</bcp14>, except in a presentation
sent before the sender has one (<xref target="first-message"/>).</t>
              </li>
              <li>
                <t><tt>iat</tt> and <tt>jti</tt>: <bcp14>REQUIRED</bcp14>.</t>
              </li>
              <li>
                <t><tt>ath</tt>: <bcp14>REQUIRED</bcp14>. The base64url-encoded SHA-256 hash <xref target="RFC6234"/> of
the ASCII encoding of the credential it accompanies.</t>
              </li>
              <li>
                <t><tt>mth</tt>: <bcp14>REQUIRED</bcp14>. The message hash of <xref target="WPT-MSG"/>, under the <tt>pace</tt>
profile.</t>
              </li>
            </ul>
            <t>A verifier checks a presentation at one of two levels:</t>
            <dl>
              <dt>Origin and integrity:</dt>
              <dd>
                <t>The signature, with the key that the credential confirms, after
checking a <tt>jwk</tt> or <tt>x5c</tt> against the credential's thumbprint or
certificate; <tt>typ</tt>; <tt>ath</tt>; and <tt>mth</tt>. These show who sent the message
and that it is unchanged. Any participant that reads the message can
check them, and they are enough to detect a forged or modified
message (<xref target="control-security"/>).</t>
              </dd>
              <dt>Authentication of the sender:</dt>
              <dd>
                <t>In addition, that <tt>aud</tt> contains the verifier's own agent-id and that
<tt>nonce</tt> is the nonce the verifier sent. Only the verifier the
presentation is addressed to can check these.</t>
              </dd>
            </dl>
            <t>A verifier rejects a presentation that fails a check it applies, and
one whose <tt>jti</tt> it has already accepted in the dialog on a different
message.</t>
            <t>When a dialog opens (<xref target="opening"/>), OPEN carries the controller's
nonce, ACCEPT carries the invitee's bound presentation and its own
nonce, and the controller's UPDATE carries its presentation bound to
that nonce. Joining uses JOIN_REQUEST, UPDATE, and ACCEPT the same
way (<xref target="joining"/>). A participant that requires a key-bound
presentation and does not receive a valid one <bcp14>MUST NOT</bcp14> treat the peer
as authenticated.</t>
            <t>Resumption uses STATE_REQUEST and STATE the same way. A participant
resuming a dialog sends STATE_REQUEST with a <tt>nonce</tt> and a
presentation in <tt>credentials</tt>; if it holds a nonce from the
controller's last message, the presentation is bound to it. The
controller's STATE carries a presentation bound to the STATE_REQUEST
nonce. The controller thereby verifies that the resuming party is the
participant whose exchange was interrupted, and the participant
verifies the controller. The controller answers with ERROR instead of
STATE when the dialog is terminated (<tt>dialog-terminated</tt>), the
participant is revoked (<tt>participant-revoked</tt>), or the check fails
(<tt>unauthenticated</tt>, <tt>unauthorized</tt>) or cannot be completed
(<tt>authorization-unavailable</tt>). A controller that resumes sends its own
nonce in its next control message and requires each participant's
next control message to carry a presentation bound to it.</t>
          </section>
          <section anchor="first-message">
            <name>The First Message</name>
            <t>OPEN and JOIN_REQUEST are sent before the sender has a nonce from its
peer, so the presentation they carry cannot be bound to one. Without
a presentation, an intermediary could change their content, such as
the dialog-id, <tt>purpose</tt>, or <tt>basis</tt>, and the change would show only
when the peer's later message failed to match.</t>
            <t>The sender of OPEN or JOIN_REQUEST therefore includes a presentation
with <tt>mth</tt> over the message and without <tt>nonce</tt>. Its <tt>aud</tt> is the
invitee's agent-id, or, for an OPEN with several invitees, an array of
their agent-ids; a presentation type whose <tt>aud</tt> takes one value is
included once per invitee. Such a presentation proves who sent the
message and that it is unchanged, but not that it is fresh: the
receiver relies on <tt>iat</tt> and <tt>jti</tt> until the sender's next
presentation, bound to the receiver's nonce, proves freshness. A
receiver <bcp14>MUST NOT</bcp14> treat the sender as authenticated until that bound
presentation verifies.</t>
          </section>
          <section anchor="control-security">
            <name>Control Message Security</name>
            <t>Relays and dialog hosts forward every control message, and relays
terminate TLS. Without protection in the message itself, they could
forge a message, for example a TERMINATE in the controller's name or a
CANCEL that stops a participant's work, or replay one. This section
says how participants detect both.</t>
            <dl>
              <dt>Presentation on every message:</dt>
              <dd>
                <t>Every control message carries a key-bound presentation in
<tt>credentials</tt>. A sender <bcp14>MAY</bcp14> omit it only where every party that
forwards the message to its receivers is trusted, for example inside
one trust domain with no relay. A receiver that does not trust the
path rejects a control message without a valid presentation, with
ERROR <tt>unauthenticated</tt> (<xref target="error-reasons"/>). A message without a
presentation has none of the protections below.</t>
              </dd>
              <dt>Several receivers:</dt>
              <dd>
                <t>A message that several participants receive, such as the
controller's UPDATE, carries a presentation whose <tt>aud</tt> is the array
of those participants. Its <tt>nonce</tt>, if any, binds it to the one
participant whose nonce it answers; the others check its origin and
integrity.</t>
              </dd>
              <dt>Sender binding:</dt>
              <dd>
                <t>A receiver <bcp14>MUST</bcp14> check that the credential of the presentation
identifies the participant named in <tt>sender_id</tt>. For UPDATE, REVOKE,
TERMINATE, SEGMENT, and STATE, that participant <bcp14>MUST</bcp14> be the
controller named in <tt>controller_id</tt>, or an alternate taking over as
<xref target="controller-transfer"/> allows.</t>
              </dd>
              <dt>Role check:</dt>
              <dd>
                <t>A receiver <bcp14>MUST</bcp14> reject, with ERROR <tt>unauthorized</tt>, an operation that
the verified sender may not send, according to the Sender column of
<xref target="_table-control-ops"/>.</t>
              </dd>
              <dt>Replay:</dt>
              <dd>
                <t>A message copied from another dialog fails <tt>mth</tt>, which covers its
<tt>dialog_id</tt>. An older controller message fails the generation rules
(<xref target="generations"/>). The same message delivered again, such as a
TERMINATE redelivered after a reconnection, has the same
<tt>message_id</tt>; the receiver processes it once and does not repeat its
side effects. A receiver keeps the <tt>message_id</tt> and presentation
<tt>jti</tt> values it has accepted for at least the dialog's
<tt>log_retention</tt> (<xref target="dialog-parameters"/>). After that, it rejects a
presentation whose <tt>iat</tt> is older than the period for which it keeps
them, unless the dialog log delivers the message at a position the
receiver has not yet accepted (<xref target="log-replay"/>).</t>
              </dd>
            </dl>
            <ul empty="true">
              <li>
                <t><strong>Editor's note:</strong> A host or relay cannot forge controller messages,
but a dishonest controller could sign two different messages at the
same generation and send each to different participants. Controller
messages could carry <tt>prev</tt>, a hash of the previous generation's
context, so that participants comparing their chains, through the
controller or out of band, detect such a fork. Feedback is welcome
on whether this is needed.</t>
              </li>
            </ul>
          </section>
        </section>
        <section anchor="records">
          <name>Records and Provenance</name>
          <t>Relays forward control messages unchanged, but transport security
authenticates only the adjacent hop, and PACE defines no audit data
structures. A deployment that requires control messages and content to
be attributable end to end, with records that parties other than the
operator can check, adds an evidence mechanism of its choice; PACE
does not mandate one and its messages are unchanged by it. What such a
mechanism records for delegations and approvals is described in
PACE Authorization (<xref target="delegation-approval"/>); TRAIL <xref target="TRAIL"/> is one example of such a mechanism.</t>
        </section>
      </section>
      <section anchor="agent-discovery">
        <name>Agent Discovery</name>
        <t>Agent discovery uses MOQT's namespace operations to find agents and
follow their activity. Discovery operates on the Agent Namespace scope
defined in <xref target="namespace"/>. Each agent is identified by a globally unique
agent-id (UUID), verifiable via the Agent Card (see <xref target="agent-card"/>).</t>
        <section anchor="phase-1-discovering-agents-on-the-network">
          <name>Phase 1: Discovering Agents on the Network</name>
          <ol spacing="normal" type="1"><li>
              <t>Each agent announces its presence by issuing PUBLISH_NAMESPACE on
<tt>("pace","agents",{agent-id})</tt>.</t>
            </li>
            <li>
              <t>Agents discover peers by issuing SUBSCRIBE_NAMESPACE on the common
prefix <tt>("pace","agents")</tt>.</t>
            </li>
            <li>
              <t>The relay sends NAMESPACE messages to subscribers for each matching
PUBLISH_NAMESPACE, enabling agents to learn about each other without
prior knowledge.</t>
            </li>
          </ol>
          <t>If an agent-id is known out-of-band (e.g., from a registry or URL),
agents <bcp14>MAY</bcp14> skip Phase 1 and proceed directly to Phase 2.</t>
        </section>
        <section anchor="phase-2-following-an-agent">
          <name>Phase 2: Following an Agent</name>
          <t>Once Agent B knows Agent A's agent-id, B follows A with two
subscriptions:</t>
          <ol spacing="normal" type="1"><li>
              <t>B issues SUBSCRIBE on <tt>("pace","agents","agent-a") -- "card"</tt> and
reads A's Agent Card (<xref target="agent-card"/>).</t>
            </li>
            <li>
              <t>B issues SUBSCRIBE on
<tt>("pace","agents","agent-a","invites") -- "agent-b"</tt>. When A
invites B to a dialog, the invitation arrives on this track
(<xref target="invitations"/>), and B then subscribes to the dialog.</t>
            </li>
          </ol>
          <t>Following is B's choice: B follows the agents from which it is willing
to receive invitations. Following does not show B any of A's dialogs.
A follows B the same way when it expects invitations from B.</t>
        </section>
        <section anchor="agent-card">
          <name>Agent Card</name>
          <t>Each agent publishes an Agent Card on track <tt>"card"</tt> under its namespace
<tt>("pace","agents",{agent-id})</tt>. When capabilities change, the agent
publishes a new object (incrementing the MOQT group).</t>
          <t>All Agent Cards <bcp14>MUST</bcp14> include:</t>
          <ul spacing="normal">
            <li>
              <t>Agent identifier (UUID) and display name</t>
            </li>
            <li>
              <t>Supported modalities and protocols</t>
            </li>
            <li>
              <t>Authentication schemes</t>
            </li>
            <li>
              <t>Identity claims (issuer, public key, expiration)</t>
            </li>
          </ul>
          <t>PACE does not define a card format. An Agent Card is the agent's
application protocol metadata in a signed form, such as an A2A Agent
Card (<xref target="a2a-binding"/>) or an SD-Card <xref target="SD-CARD"/>, which lets the agent
disclose different claims to different peers. The card names the
agent's namespace <tt>("pace","agents",{agent-id})</tt>, and receivers <bcp14>MUST</bcp14>
check that it equals the namespace on which the card was published.</t>
          <t>The <tt>"card"</tt> track reaches every subscriber through relays, so a card
on it is not bound to any one verifier. It shows that its claims are
signed and unmodified, but not that the publisher is the agent.
Receivers <bcp14>MUST</bcp14> verify the card's signature and expiration before
acting on its claims, and a participant that relies on the agent's
identity <bcp14>MUST</bcp14> obtain a key-bound presentation in <tt>credentials</tt>
(<xref target="key-binding"/>).</t>
          <t>Every subscriber sees the card, so an agent that uses pairwise or
per-dialog agent-ids (<xref target="privacy"/>) publishes a separate card, with a
separate key, for each agent-id; otherwise the card links them.</t>
        </section>
      </section>
    </section>
    <section anchor="protocol-bindings">
      <name>Protocol Bindings</name>
      <t>PACE manages dialog identifiers, lifecycle, and context propagation.
Application-layer agent protocols keep their native message formats
and semantics, and carry the dialog context through their own
extension points (<xref target="carrying-dialog-context"/>). PACE does not change
those protocols; any standardized mapping is coordinated with their
maintainers.</t>
      <t>Over the MOQT binding, an application protocol's messages also need a
place on MOQT tracks. This section defines that placement for MCP,
the Personal Agent Protocol (Poppy), A2A, and a generic
JSON-RPC baseline for custom protocols. Each binding runs inside a
PACE dialog, using the dialog namespace (<xref target="dialog-namespace"/>)
and the channel architecture (<xref target="data-exchange"/>). Multiple bindings
can coexist in a single dialog, each under its own protocol namespace
field, so one agent can speak A2A to a peer and MCP to a tool in the
same dialog.</t>
      <section anchor="carrying-dialog-context">
        <name>Carrying Dialog Context in Application Protocols</name>
        <t>An application message joins a dialog by carrying a dialog reference
in the protocol's own extension point, whether or not the protocol
runs over MOQT. The reference is this object, under the metadata key
<tt>org.ietf.agentproto/dialog-context</tt>:</t>
        <sourcecode type="json"><![CDATA[
{
  "dialog_id": "550e8400-e29b-41d4-a716-446655440000",
  "generation": 3
}
]]></sourcecode>
        <t><tt>generation</tt> is the latest generation the sender knows. The
controller's <tt>ctrl</tt> track stays authoritative; a receiver that needs
the full context sends STATE_REQUEST.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Protocol</th>
              <th align="left">Carried in</th>
              <th align="left">Keep distinct from</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">MCP</td>
              <td align="left">
                <tt>_meta</tt></td>
              <td align="left">JSON-RPC request IDs and the <xref target="MCP-MOQT"/> client ID</td>
            </tr>
            <tr>
              <td align="left">Poppy</td>
              <td align="left">Track namespace (<xref target="poppy-binding"/>)</td>
              <td align="left">Conversation ID</td>
            </tr>
            <tr>
              <td align="left">AutoGen</td>
              <td align="left">Message <tt>metadata</tt></td>
              <td align="left">Conversation ID</td>
            </tr>
            <tr>
              <td align="left">A2A</td>
              <td align="left">Message <tt>metadata</tt></td>
              <td align="left">
                <tt>contextId</tt>, <tt>taskId</tt></td>
            </tr>
          </tbody>
        </table>
        <t>A dialog-id <bcp14>MUST NOT</bcp14> be used as a task, request, content, or session
identifier, or as a credential.</t>
      </section>
      <section anchor="binding-architecture">
        <name>Binding Architecture</name>
        <t>A binding specifies:</t>
        <ul spacing="normal">
          <li>
            <t>Protocol identifier: the namespace field that follows the
dialog-id.</t>
          </li>
          <li>
            <t>Namespace pattern: how operations map to namespace fields and track
names within the agent's dialog namespace.</t>
          </li>
          <li>
            <t>Message serialization: how native messages are encoded in MOQT
object payloads. Bindings <bcp14>SHOULD</bcp14> use the native wire format as the
object payload (<xref target="message-serialization"/>).</t>
          </li>
          <li>
            <t>Dialog reference: where messages carry the dialog reference
(<xref target="carrying-dialog-context"/>).</t>
          </li>
          <li>
            <t>Priority: which PACE priority tier its tracks use (<xref target="data-exchange"/>).</t>
          </li>
          <li>
            <t>Identity and authorization: how the protocol's own identity and
authorization constructs (if any) relate to the credential
mechanisms (<xref target="identity-formats"/>) in this document.</t>
          </li>
        </ul>
        <t>A complete mapping of each protocol operation to MOQT primitives
belongs in a protocol-specific document, such as <xref target="MCP-MOQT"/> for MCP.</t>
        <t>Protocols use distinct protocol namespace fields within PACE dialogs.
In the tables of this section, a pattern such as
<tt>("a2a", "task") -- {task-id}</tt> gives the namespace fields that follow
<tt>("pace", "dialogs", {dialog-id}, {agent-id})</tt>, then the track name.</t>
        <t>In the examples, D is the dialog-id.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Binding</th>
              <th align="left">Protocol Fields</th>
              <th align="left">Example Full Track Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">MCP</td>
              <td align="left">
                <tt>"mcp"</tt></td>
              <td align="left">
                <tt>("pace","dialogs",D,"fs","mcp","tools","read") -- "response"</tt></td>
            </tr>
            <tr>
              <td align="left">Poppy</td>
              <td align="left">
                <tt>"poppy"</tt></td>
              <td align="left">
                <tt>("pace","dialogs",D,"acme","poppy","conversation") -- "events"</tt></td>
            </tr>
            <tr>
              <td align="left">A2A</td>
              <td align="left">
                <tt>"a2a"</tt></td>
              <td align="left">
                <tt>("pace","dialogs",D,"agent-a","a2a","task") -- "t1"</tt></td>
            </tr>
            <tr>
              <td align="left">Generic</td>
              <td align="left">
                <tt>"ext", {proto}</tt></td>
              <td align="left">
                <tt>("pace","dialogs",D,"agent-a","ext","proto","rpc") -- "call"</tt></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="mcp-binding">
        <name>MCP Binding</name>
        <t>The Model Context Protocol <xref target="MCP"/> binding enables tool and resource
access for agents. Within a PACE dialog, MCP tracks add an <tt>"mcp"</tt>
namespace field after the dialog-id, under the namespace of the agent
that publishes the track:</t>
        <artwork><![CDATA[
Namespace: ("pace", "dialogs", {dialog-id}, {agent-id}, "mcp",
            {category}, ...)
Tracks:    {track-name}
]]></artwork>
        <t>The complete MCP over MOQT specification, covering track structure,
operation mapping, message serialization, Agent Skills, and relay
support, is defined in <xref target="MCP-MOQT"/>. PACE adopts its track semantics.
The mapping is mechanical: the leading
<tt>(mcp, {server-id}, clients, {client-id})</tt> or <tt>(mcp, {server-id})</tt>
fields of an MCP over MOQT namespace are replaced by <tt>("pace",
"dialogs", {dialog-id}, {agent-id}, "mcp")</tt>, and the remaining
namespace fields and the track name are kept unchanged. For example,
with <tt>{cli}</tt> and <tt>{srv}</tt> the agent-ids of the MCP client and server:</t>
        <table>
          <name>MCP over MOQT Tracks within PACE</name>
          <thead>
            <tr>
              <th align="left">Track</th>
              <th align="left">MCP over MOQT</th>
              <th align="left">Within PACE</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Tool request</td>
              <td align="left">
                <tt>(mcp, {server-id}, clients, {client-id}, tools, {tool-name}) -- request</tt></td>
              <td align="left">
                <tt>("pace","dialogs",{dialog-id},{cli},"mcp","tools",{tool-name}) -- "request"</tt></td>
            </tr>
            <tr>
              <td align="left">Tool response</td>
              <td align="left">
                <tt>(mcp, {server-id}, clients, {client-id}, tools, {tool-name}) -- response</tt></td>
              <td align="left">
                <tt>("pace","dialogs",{dialog-id},{srv},"mcp","tools",{tool-name}) -- "response"</tt></td>
            </tr>
            <tr>
              <td align="left">Resource</td>
              <td align="left">
                <tt>(mcp, {server-id}, resources) -- {resource-uri}</tt></td>
              <td align="left">
                <tt>("pace","dialogs",{dialog-id},{srv},"mcp","resources") -- {resource-uri}</tt></td>
            </tr>
          </tbody>
        </table>
        <t>MCP needs no handshake of its own, and MCP over MOQT client IDs are
not used within PACE: PACE supplies the dialog-id, and peers learn
each other's MCP tracks through SUBSCRIBE_TRACKS on the dialog
prefix.</t>
        <t>MCP messages keep their native JSON-RPC format as the object payload
(<xref target="message-serialization"/>) and carry the dialog reference in <tt>_meta</tt>
(<xref target="carrying-dialog-context"/>). Key operations map as follows:</t>
        <table>
          <thead>
            <tr>
              <th align="left">MCP Operation</th>
              <th align="left">MOQT</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>tools/call</tt></td>
              <td align="left">Request object in a new group on the client's <tt>("mcp","tools",{tool-name}) -- "request"</tt> track; the result in the same group on the server's matching <tt>"response"</tt> track</td>
            </tr>
            <tr>
              <td align="left">Progress and partial results</td>
              <td align="left">Further objects in that group on the <tt>"response"</tt> track (<xref target="streaming"/>)</td>
            </tr>
            <tr>
              <td align="left">
                <tt>resources/read</tt></td>
              <td align="left">FETCH or SUBSCRIBE on the server's <tt>("mcp","resources") -- {resource-uri}</tt> track</td>
            </tr>
            <tr>
              <td align="left">
                <tt>notifications/cancelled</tt></td>
              <td align="left">Applied from PACE CANCEL (<xref target="cancellation"/>)</td>
            </tr>
          </tbody>
        </table>
        <t>MCP tracks use the PACE priority tiers (<xref target="data-exchange"/>) as
<xref target="MCP-MOQT"/> assigns them: control, tool, prompt, task and skill
execution tracks use Standard Operations, catalog and skill content tracks
Discovery, and resource tracks Bulk Transfer.</t>
        <t>An MCP server that holds an MCP SD-Card returns a key-bound
presentation to the client that requests one
(<xref section="8.2.4" sectionFormat="of" target="SD-CARD"/>). That presentation is specific to the
requesting client, and SD-Card requires the response carrying it to
have a private <tt>cacheScope</tt>. Within PACE, relay authorization keeps
the response track within the dialog (<xref target="relay-authorization"/>). The
nonce and audience prevent replay of the presentation, but other
participants of the dialog can read the claims it discloses, so the
server discloses only claims that every participant may see.</t>
        <t>When a Key Binding JWT carries an <tt>interaction_id</tt>, an agent includes
it in the MCP requests it makes for that interaction
(<xref section="8.5" sectionFormat="of" target="SD-CARD"/>). Agents <bcp14>MAY</bcp14> use the dialog-id as the
<tt>interaction_id</tt>, so that presentations and messages correlate on the
same identifier.</t>
      </section>
      <section anchor="poppy-binding">
        <name>Personal Agent Protocol Binding</name>
        <t>The Personal Agent Protocol (Poppy) <xref target="POPPY"/> lets a person's own
agent (the Personal Agent) sign in to a Company and talk to the
Company's agent (the Company Agent). Poppy defines discovery through a
<tt>poppy.json</tt> document, OAuth-based identity with pairwise user
identifiers, API access through OpenAPI and MCP, and a Conversations
protocol over HTTPS.</t>
        <t>This binding carries Poppy Conversations over PACE. Poppy discovery,
OAuth sign-in, web browsing, feedback and excluded-task documents are
unchanged and continue to use HTTPS. Poppy APIs of type <tt>mcp</tt> can use
the MCP binding (<xref target="mcp-binding"/>) when the Company offers MCP over
MOQT.</t>
        <section anchor="roles-and-discovery">
          <name>Roles and Discovery</name>
          <t>The Personal Agent is the PACE dialog initiator and the Company Agent
is the responder. A Company that offers this binding lists it in the
<tt>agent.protocols</tt> array of its <tt>poppy.json</tt>. Poppy ignores protocol
types it does not recognize, so the entry can sit alongside the
default <tt>poppy</tt> HTTPS entry:</t>
          <sourcecode type="json"><![CDATA[
{
  "agent": {
    "protocols": [
      { "type": "poppy", "endpoint": "https://acme.example/agent" },
      {
        "type": "pace",
        "binding": "poppy",
        "endpoint": "https://acme.example/poppy/pace",
        "relayEndpoint": "moqt://relay.acme.example:4443",
        "namespace": ["pace", "agents", "acme"]
      }
    ]
  }
}
]]></sourcecode>
          <t>The <tt>pace</tt> protocol type is not defined by Poppy Draft 0.3. Until Poppy
defines it, the entry is carried as a Poppy extension named under a
domain the publisher controls, as Poppy's extension rules require.
The Personal Agent <bcp14>MUST</bcp14> apply Poppy's <tt>poppy.json</tt> validation (domain
match and issuer checks) before using the entry. <tt>namespace</tt> is the
Company Agent's agent namespace, and <tt>endpoint</tt> is the HTTPS URL at
which the Personal Agent starts a conversation (see below).</t>
          <t>A Company that holds a Company SD-Card (<xref section="8.3" sectionFormat="of" target="SD-CARD"/>)
carries the <tt>agent</tt> member of its <tt>poppy.json</tt> in the SD-Card's
selectively disclosable <tt>agent</tt> claim. It can therefore leave the
<tt>pace</tt> entry out of its public <tt>poppy.json</tt> and disclose it only to
the Personal Agents it chooses. A disclosed <tt>pace</tt> entry that also
appears in <tt>poppy.json</tt> <bcp14>MUST</bcp14> match it, as SD-Card's consistency rules
require.</t>
        </section>
        <section anchor="namespace-structure">
          <name>Namespace Structure</name>
          <artwork><![CDATA[
Namespace: ("pace", "dialogs", {dialog-id}, {agent-id}, "poppy",
            "conversation")
Tracks:    "messages" | "requests" | "events" | "deltas"
]]></artwork>
          <table>
            <thead>
              <tr>
                <th align="left">Publisher</th>
                <th align="left">Track</th>
                <th align="left">Content</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Personal Agent</td>
                <td align="left">
                  <tt>messages</tt></td>
                <td align="left">Poppy messages sent by the Personal Agent</td>
              </tr>
              <tr>
                <td align="left">Personal Agent</td>
                <td align="left">
                  <tt>requests</tt></td>
                <td align="left">Conversation requests: handoff to a human</td>
              </tr>
              <tr>
                <td align="left">Company Agent</td>
                <td align="left">
                  <tt>events</tt></td>
                <td align="left">Poppy events: <tt>message</tt>, <tt>state</tt>, <tt>authorization</tt>, <tt>user_requested</tt>, <tt>direct_opened</tt>, <tt>direct_closed</tt></td>
              </tr>
              <tr>
                <td align="left">Company Agent</td>
                <td align="left">
                  <tt>deltas</tt></td>
                <td align="left">Non-durable <tt>text-delta</tt> events</td>
              </tr>
            </tbody>
          </table>
          <t>The Company Agent's <tt>{agent-id}</tt> is the one in the namespace advertised
in <tt>poppy.json</tt>. The Personal Agent's <tt>{agent-id}</tt> <bcp14>MUST</bcp14> be pairwise: it
<bcp14>MUST</bcp14> differ for each Company, <bcp14>MUST NOT</bcp14> be derived from the person's
identity, and <bcp14>SHOULD NOT</bcp14> equal the Poppy User ID. A Personal Agent <bcp14>MAY</bcp14>
use a fresh <tt>{agent-id}</tt> for each dialog. This preserves Poppy's
property that a Company knows a person only by an opaque identifier
that differs at every Company. It also stops relays, which always see
namespaces, from linking a person's conversations across Companies.
Personal Agents do not publish an Agent Card or answer agent discovery
(<xref target="agent-discovery"/>), and the Company does not follow them.</t>
        </section>
        <section anchor="starting-a-conversation">
          <name>Starting a Conversation</name>
          <t>The Company does not follow the Personal Agent, so the Personal Agent
gives it the dialog-id over HTTPS (<xref target="invitations"/>):</t>
          <ol spacing="normal" type="1"><li>
              <t>The Personal Agent generates a dialog-id and sends a POST request
to <tt>endpoint</tt> with the Poppy-Session header, as for every endpoint
a Poppy extension defines, and the body <tt>{"dialog_id": "&lt;D&gt;",
"agent_id": "&lt;pairwise agent-id&gt;"}</tt>.</t>
            </li>
            <li>
              <t>The Company verifies the Session JWT, issues SUBSCRIBE_TRACKS on
<tt>("pace","dialogs",D)</tt>, and responds with a token <xref target="MoQ-C4M"/>
that authorizes the Personal Agent for that dialog only
(<xref target="relay-authorization"/>).</t>
            </li>
            <li>
              <t>The Personal Agent connects to <tt>relayEndpoint</tt>, subscribes to the
dialog prefix, and publishes OPEN on its <tt>ctrl</tt> track, with itself
as controller and the Company Agent invited (<xref target="opening"/>). The
dialog continues as in <xref target="opening"/> from step 5.</t>
            </li>
          </ol>
        </section>
        <section anchor="operation-mapping">
          <name>Operation Mapping</name>
          <t>Poppy messages and events keep their native JSON format as the object
payload (<xref target="message-serialization"/>). The dialog reference is not
carried in them, because the dialog-id is in every track namespace.</t>
          <table>
            <thead>
              <tr>
                <th align="left">Poppy Conversations</th>
                <th align="left">PACE / MOQT</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Start a conversation</td>
                <td align="left">The dialog-id handoff over HTTPS, then OPEN with the Personal Agent as controller (see above). The Poppy conversation ID is assigned as in Poppy and is distinct from the dialog-id</td>
              </tr>
              <tr>
                <td align="left">Send a message</td>
                <td align="left">One object per message, in a new group, on the <tt>messages</tt> track</td>
              </tr>
              <tr>
                <td align="left">Read events, resume from a cursor</td>
                <td align="left">SUBSCRIBE to the <tt>events</tt> track, with FILL_PARAMETERS or FETCH from the Location after the last event received</td>
              </tr>
              <tr>
                <td align="left">Request a human</td>
                <td align="left">A <tt>handoff</tt> object on the <tt>requests</tt> track</td>
              </tr>
              <tr>
                <td align="left">Direct Conversation</td>
                <td align="left">A new dialog whose <tt>parent_dialog_ids</tt> starts with the parent dialog-id</td>
              </tr>
              <tr>
                <td align="left">Close</td>
                <td align="left">TERMINATE</td>
              </tr>
            </tbody>
          </table>
          <t>Each event is one object in its own group, so an event's MOQT Location
serves as the Poppy cursor. The <tt>messages</tt>, <tt>requests</tt>, and <tt>events</tt>
tracks are durable and <bcp14>MUST NOT</bcp14> use a finite delivery timeout; the
<tt>deltas</tt> track <bcp14>SHOULD</bcp14> use OBJECT_DELIVERY_TIMEOUT. The Company Agent
<bcp14>MUST</bcp14> treat a repeated message <tt>id</tt> from the same User as a duplicate,
as Poppy requires. Handoff requests use the Urgent Signals priority
tier, and messages and events the Interactive tier (<xref target="data-exchange"/>).</t>
        </section>
        <section anchor="identity-and-authorization">
          <name>Identity and Authorization</name>
          <t>This binding reuses Poppy identity and authorization unchanged.
Sign-in, token refresh, and client metadata stay on HTTPS.</t>
          <ul spacing="normal">
            <li>
              <t>Credentials: The Personal Agent is identified by its Poppy
<tt>client_id</tt>, and the person only by the pairwise Poppy User ID. It
sends its Poppy Session JWT, and its access token when signed in, in
the <tt>credentials</tt> member of OPEN, and new ones on its next control
message after a refresh or sign-in (<xref target="control-encoding"/>).</t>
            </li>
            <li>
              <t>Ownership: The conversation belongs to the <tt>client_id</tt> and User ID
that opened it. The Company <bcp14>MUST</bcp14> reject control messages from any
other client, User, or account, and <bcp14>MUST</bcp14> authorize subscriptions to
the conversation's <tt>events</tt> and <tt>deltas</tt> tracks only for that owner.
The relay enforces this (<xref target="relay-authorization"/>): the only
participant token the Company issues for <tt>("pace","dialogs",D)</tt> is
the owner's.</t>
            </li>
            <li>
              <t>Signing in: When the Company Agent needs account access, it publishes
an <tt>authorization</tt> event; the Personal Agent signs in over HTTPS and
continues the same dialog with new credentials. Because tokens pass
through relays, the Personal Agent <bcp14>SHOULD</bcp14> use DPoP-bound tokens where
the Company supports them: with DPoP proofs <xref target="RFC9449"/> for its HTTPS
requests, and with DPoP proofs for MOQT <xref target="MoQ-C4M"/> for its
SUBSCRIBE and PUBLISH actions on the dialog's tracks
(<xref target="relay-authorization"/>). A token carried in the <tt>credentials</tt>
member of a control message is accompanied by a proof bound to that
message (<xref target="key-binding"/>).</t>
            </li>
            <li>
              <t>Personal Agent SD-Card: A Personal Agent presents its SD-Card with
the Poppy SD-Card extension over HTTPS, unchanged
(<xref section="8.3.5" sectionFormat="of" target="SD-CARD"/>). The SD-Card's <tt>sub</tt> and <tt>cnf</tt> key
identify the Personal Agent, and so the person, to every Company
that verifies it (<xref section="8.3.7" sectionFormat="of" target="SD-CARD"/>). Pairwise
<tt>{agent-id}</tt> values do not hide that link, so a Personal Agent
<bcp14>SHOULD</bcp14> present its SD-Card only to Companies with which the person
has, or is setting up, a relationship. Where the Company only needs
to know that the Personal Agent is attested, it <bcp14>SHOULD</bcp14> accept a
Privacy Pass token <xref target="RFC9576"/> instead.</t>
            </li>
          </ul>
          <t>Editor's note: A Poppy Session JWT is bound to an HTTP method and URL
(<tt>htm</tt>, <tt>htu</tt>). How these claims apply to a PACE control message is to
be agreed with the Poppy authors. The same question applies to the
Poppy SD-Card extension, whose Key Binding JWT nonce is the <tt>jti</tt> of
the Session JWT. A Personal Agent's <tt>credentials</tt> in this binding are
a Session JWT, not an SD-Card presentation, so whether the Company
sends a <tt>nonce</tt> (<xref target="key-binding"/>) and how the Personal Agent answers
it is also to be agreed.</t>
        </section>
      </section>
      <section anchor="a2a-binding">
        <name>A2A Binding</name>
        <t>The Agent-to-Agent Protocol <xref target="A2A"/> binding places A2A messages on
tracks under each agent's dialog namespace, using the <tt>"a2a"</tt> protocol
namespace field:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Track Pattern</th>
              <th align="left">Content</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>("a2a", "request") -- {request-id}</tt></td>
              <td align="left">A2A JSON-RPC requests</td>
            </tr>
            <tr>
              <td align="left">
                <tt>("a2a", "response") -- {request-id}</tt></td>
              <td align="left">A2A JSON-RPC responses</td>
            </tr>
            <tr>
              <td align="left">
                <tt>("a2a", "task") -- {task-id}</tt></td>
              <td align="left">Task status and artifact updates</td>
            </tr>
          </tbody>
        </table>
        <t>A2A messages keep their native JSON-RPC 2.0 format as the object
payload (<xref target="message-serialization"/>) and carry the dialog reference in
the message <tt>metadata</tt> (<xref target="carrying-dialog-context"/>). Key operations
map as follows:</t>
        <table>
          <thead>
            <tr>
              <th align="left">A2A Operation</th>
              <th align="left">MOQT</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>SendMessage</tt></td>
              <td align="left">Request object on the client's <tt>request</tt> track; the response on the server's <tt>response</tt> track with the same request-id</td>
            </tr>
            <tr>
              <td align="left">
                <tt>SendStreamingMessage</tt></td>
              <td align="left">Response objects on the <tt>response</tt> track, ended by PUBLISH_DONE (<xref target="streaming"/>)</td>
            </tr>
            <tr>
              <td align="left">
                <tt>GetTask</tt></td>
              <td align="left">FETCH on the server's <tt>("a2a","task") -- {task-id}</tt> track</td>
            </tr>
            <tr>
              <td align="left">
                <tt>SubscribeToTask</tt></td>
              <td align="left">SUBSCRIBE on that task track, with FILL_PARAMETERS to catch up</td>
            </tr>
            <tr>
              <td align="left">
                <tt>CancelTask</tt></td>
              <td align="left">Applied from PACE CANCEL (<xref target="cancellation"/>)</td>
            </tr>
          </tbody>
        </table>
        <t>A response that creates a task carries the A2A task-id, which names
the server's task track. A2A tracks use the Interactive priority tier
for requests and responses and the Standard Operations tier for task
updates (<xref target="data-exchange"/>). An A2A agent advertises PACE support
through A2A's own Agent Card extension mechanism, pointing to its PACE
Agent Card (<xref target="agent-card"/>).</t>
        <t>An A2A agent that holds an A2A SD-Card (<xref section="8.4" sectionFormat="of" target="SD-CARD"/>)
publishes it as its PACE Agent Card. Its <tt>supportedInterfaces</tt> claim
is disclosed per element and its <tt>capabilities</tt> claim selectively,
so the agent can disclose its PACE interface and extension only in
the discovery contexts it chooses. The SD-Card A2A extension, which
carries a key-bound presentation in the metadata of the first Message
or Task in a context, works unchanged over these tracks because A2A
messages keep their native format. An A2A <tt>contextId</tt> is used within
one dialog, so the agent presents its SD-Card at most once per
<tt>contextId</tt> in that dialog.</t>
        <t>A complete mapping of A2A operations to MOQT is left to a separate
document coordinated with the A2A maintainers, as <xref target="MCP-MOQT"/> does
for MCP.</t>
      </section>
      <section anchor="jsonrpc-binding">
        <name>Generic Binding</name>
        <t>A protocol without its own binding uses the <tt>"ext"</tt> protocol namespace
field followed by a field naming the protocol:</t>
        <artwork><![CDATA[
Namespace: ("pace", "dialogs", {dialog-id}, {agent-id}, "ext",
            {protocol-name}, ...)
Tracks:    {identifier}
]]></artwork>
        <t>The protocol's native messages are the object payloads
(<xref target="message-serialization"/>), and they carry the dialog reference in
the protocol's own extension point (<xref target="carrying-dialog-context"/>). The
protocol defines its own namespace fields and track names below
<tt>{protocol-name}</tt>.</t>
      </section>
    </section>
    <section anchor="authorization">
      <name>Authorization and Security</name>
      <section anchor="authorization-model">
        <name>Authorization Model</name>
        <t>Access in PACE is granted through authorization proofs scoped to the
operations an agent may perform. PACE does not define a new
authorization protocol or scope syntax. The scope representation,
token format, issuance mechanism, and verification policy come from
the mechanism the deployment selects (<xref target="identity-formats"/>).</t>
        <section anchor="delegated-authz">
          <name>Delegated Authorization</name>
          <t>Authorization proofs travel in the <tt>credentials</tt> member of control
messages: OPEN, ACCEPT, and JOIN_REQUEST, and UPDATE when the
controller presents its own (<xref target="key-binding"/>). Proofs are refreshed
before they expire by sending new credentials on a later control
message; long-lived dialogs <bcp14>SHOULD</bcp14> renew the proof in place rather
than terminating the dialog. Revoking an agent's authorization ends
its propagation relationship through REVOKE (<xref target="lifecycle"/>), and the
revoked agent terminates the dialogs it delegated under it
(<xref target="lifecycle-propagation"/>).</t>
        </section>
        <section anchor="delegation-approval">
          <name>Delegation and Action Approval</name>
          <t>PACE Authorization <xref target="PACE-AUTHZ"/> specifies the authority agents
exercise in PACE dialogs: delegation credentials bound to the
delegated dialog, narrowing of authority at each hop, authorization
checkpoints through which an agent asks for approval of one action,
approval tokens that cover only that action, and optional evidence of
approvals. It reuses existing OAuth, WIMSE, and agent-protocol work
and states how each fits. A PACE deployment that delegates across
agents, or that requires approval of individual actions, uses it.</t>
        </section>
      </section>
      <section anchor="transport-security">
        <name>Transport Security</name>
        <t>All PACE traffic is encrypted under TLS 1.3 because QUIC requires it.
MOQT relays terminate QUIC and TLS on each hop, so transport-layer
authentication identifies only the adjacent hop. PACE therefore
authenticates participants at the application layer, through the
<tt>credentials</tt> member of control messages, as <xref section="7.2" sectionFormat="of" target="ARCH"/>
requires when intermediaries terminate TLS.
Identity assertions and authorization proofs are signed and
short-lived. MOQT Common Access Tokens <xref target="MoQ-C4M"/> handle
namespace-level authorization at the relay.</t>
        <section anchor="e2e-protection">
          <name>End-to-End Protection</name>
          <t>TLS protects each hop, but relays terminate it. To keep content
confidential and integrity-protected from relays, participants protect
object payloads with End-to-End Secure Objects <xref target="MOQ-SECURE-OBJECTS"/>.
A deployment that does not trust its relays with content <bcp14>MUST</bcp14> protect
every content track this way, and <bcp14>SHOULD</bcp14> protect <tt>ctrl</tt> objects,
and those of extension tracks such as <tt>checkpoint</tt> (<xref target="delegation-approval"/>),
too; relays do not need to read any PACE payload
(<xref target="relay-authorization"/>).</t>
          <t>Keys are scoped to a dialog. How they are established and distributed
to participants is chosen by the deployment. One way is an MLS <xref target="RFC9420"/>
group per dialog whose commits the controller carries in its control
messages. Where a key establishment mechanism requires <tt>ctrl</tt> objects
to be readable by participants before they join, as MLS does,
<tt>ctrl</tt> objects are left unencrypted and
remain authenticated by the presentations bound to each message
(<xref target="key-binding"/>). When the controller commits a participant's
departure or revocation, the keys <bcp14>MUST</bcp14> be rotated so that the
departed participant cannot read later content, and when a
participant is added, they <bcp14>SHOULD</bcp14> be rotated so that it cannot read
earlier content it was not given.</t>
        </section>
        <section anchor="relay-authorization">
          <name>Relay Authorization</name>
          <t>Relays do not interpret PACE. They enforce, per namespace and track,
who may publish and who may subscribe, using the agent's token, for
example a Common Access Token <xref target="MoQ-C4M"/>. Because relays see these
tokens, they <bcp14>SHOULD</bcp14> be bound to the agent's key and presented with a
DPoP proof for each MOQT action, as <xref target="MoQ-C4M"/> defines for MOQT; the
proof names the action, Track Namespace, and Track Name in place of
the HTTP method and URI. A DPoP proof authorizes the MOQT action at
the relay. It does not cover the content of the objects published, so
credentials inside control messages are bound to the message with
<tt>mth</tt> (<xref target="key-binding"/>). The access each agent
needs follows from following (<xref target="agent-discovery"/>), invitations
(<xref target="invitations"/>), opening (<xref target="opening"/>), and joining (<xref target="joining"/>),
and each agent publishes only under its own agent-id
(<xref target="track-organization"/>). Where a participant's <tt>access</tt>
(<xref target="participant-descriptors"/>) limits what it may send or receive, its
token covers only those tracks, so the relay enforces the limit; a
participant not in a segment holds no token for the segment dialog
(<xref target="segments"/>). The controller, or its authorization server,
grants an agent access to a dialog on invitation or admission and
withdraws it when the agent leaves or is revoked.</t>
          <t>Because each PACE subscription covers one track or one dialog prefix,
the relay checks it once, when it is made. Relays <bcp14>MUST</bcp14> refuse
subscriptions to a prefix of <tt>("pace","dialogs")</tt> shorter than a
dialog-id unless explicitly authorized, since they would reveal every
dialog on the relay. How tokens reach agents is deployment-specific;
the Poppy binding returns them over HTTPS (<xref target="poppy-binding"/>).</t>
        </section>
        <section anchor="anonymous-relay-authorization">
          <name>Anonymous Relay Authorization</name>
          <t>An access token tells every relay which agent is subscribing or
publishing, and its bytes link the agent's requests across dialogs.
Where relays need to know only that a request comes from a member of a
dialog, deployments <bcp14>MAY</bcp14> authorize with Privacy Pass tokens <xref target="RFC9576"/>
carried in MOQT as <xref target="MOQ-PP"/> defines, instead of or in addition to
access tokens:</t>
          <ul spacing="normal">
            <li>
              <t>The controller's domain issues membership tokens to the
participants it has admitted, under public metadata derived from the
dialog-id, and stops issuing when a participant leaves or is revoked
<xref target="PP-AGENTS"/>.</t>
            </li>
            <li>
              <t>Each token's scope, in its <tt>origin_info</tt>, covers the dialog's
namespace and the actions the participant needs (<xref target="MOQ-PP"/>).</t>
            </li>
            <li>
              <t>Tokens <bcp14>SHOULD</bcp14> be holder-bound, with a redemption proof that names the
MOQT request (<xref target="PP-AGENTS"/>), so that a relay or another party that
sees a token cannot present it with another request. Unbound Privacy
Pass tokens are bearer tokens, and relays see them.</t>
            </li>
            <li>
              <t>Subscriptions are kept authorized with fresh tokens before they
expire (<xref target="MOQ-PP"/>). A participant whose tokens stop being issued
loses access within the lifetime of the tokens it holds.</t>
            </li>
          </ul>
          <t>The relay then learns that a member of the dialog made the request,
not which member. Participants still identify one another through
<tt>credentials</tt> in control messages; these tokens hide participants only
from the relays. A binding over HTTP can apply the same tokens to
dialog hosts.</t>
        </section>
      </section>
      <section anchor="privacy">
        <name>Privacy Considerations</name>
        <t>PACE dialog and participant identifiers (dialog-ids and agent-ids)
can persist across
intermediaries and trust boundaries. If several parties see them in
the clear, they can be used to correlate interactions that would
otherwise look unrelated. This is a known risk for any dialog
management protocol. Deployments mitigate it as follows:</t>
        <ul spacing="normal">
          <li>
            <t>Identity claims and agent metadata are disclosed selectively
(<xref target="selective-disclosure"/>): agents reveal only what each peer
needs. Selective disclosure does not hide the agent's identity
(<xref target="agent-card"/>).</t>
          </li>
          <li>
            <t>Authorization proofs are narrowed to the minimum scope and
refreshed before expiration so intermediaries cannot replay broad
grants.</t>
          </li>
          <li>
            <t>Agents acting for an individual person <bcp14>SHOULD</bcp14> use pairwise or
per-dialog agent-ids in their dialog namespaces, so that relays
cannot link that person's dialogs with different peers. The Poppy
binding requires this (<xref target="poppy-binding"/>).</t>
          </li>
          <li>
            <t>Dialog-ids <bcp14>SHOULD</bcp14> be fresh per dialog. Reusing a dialog-id across
unrelated interactions re-introduces the linkage risk the identifier
is supposed to avoid.</t>
          </li>
          <li>
            <t>Relays and dialog hosts that need to know only that a request comes
from a dialog member <bcp14>SHOULD</bcp14> authorize with holder-bound Privacy Pass
tokens (<xref target="anonymous-relay-authorization"/>), so that they do not learn
which participant acted.</t>
          </li>
          <li>
            <t>Payload content <bcp14>SHOULD</bcp14> remain encrypted end-to-end with respect to
relays unless the relay is explicitly trusted (<xref target="e2e-protection"/>).</t>
          </li>
          <li>
            <t>Long-lived dialogs <bcp14>SHOULD</bcp14> rotate keys periodically; QUIC provides
the key material lifecycle.</t>
          </li>
          <li>
            <t>Participant descriptors (<xref target="participant-descriptors"/>) reach every
participant. <tt>kind</tt>, <tt>assurance</tt>, and <tt>consent</tt> can reveal that a
person is present and how they authenticated, and <tt>acts_for</tt> can
link dialogs. Participants <bcp14>SHOULD</bcp14> declare only the descriptors the
dialog needs, <tt>acts_for</tt> <bcp14>MUST</bcp14> be an opaque value that differs per
counterpart unless the principal chooses otherwise. <tt>method</tt> in
<tt>assurance</tt> names a registered method, never an identifier.
<tt>related_dialogs</tt>, like <tt>parent_dialog_ids</tt>, links dialogs and is
withheld where the link should not cross a boundary.</t>
          </li>
          <li>
            <t>Agent Cards <bcp14>SHOULD</bcp14> advertise only what discovery requires. Relays
and every subscriber to the <tt>"card"</tt> track see it. Finer capability
details can be disclosed in a key-bound presentation after a dialog
begins (<xref target="agent-card"/>).</t>
          </li>
        </ul>
        <t>Relay operators <bcp14>MUST NOT</bcp14> retain content past operational need. Agents
<bcp14>SHOULD</bcp14> send only what the task requires.</t>
      </section>
    </section>
    <section anchor="scalability">
      <name>Scalability and Reliability</name>
      <t>PACE inherits MOQT's relay architecture for geographic distribution
and load management:</t>
      <ul spacing="normal">
        <li>
          <t>Multiple subscribers to the same track result in a single upstream
subscription, which reduces origin load.</t>
        </li>
        <li>
          <t>Edge relays cache content close to subscribers, which cuts
round-trip latency.</t>
        </li>
        <li>
          <t>Relay failures stay localized; other paths keep operating.</t>
        </li>
      </ul>
      <section anchor="failure-modes-and-recovery">
        <name>Failure Modes and Recovery</name>
        <t>Agent network loss and relay failure are recovered as described in
<xref target="dialog-recovery"/>. An unreachable participant or controller is
handled by the rules in <xref target="propagation"/>, and a dialog that outlasts its
expiration or idle timeout ends as described in <xref target="dialog-lifetime"/>.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The threats described in <xref section="10" sectionFormat="of" target="ARCH"/> apply to PACE.</t>
      <t>QUIC and TLS 1.3 0-RTT data can be replayed. Participants <bcp14>MUST NOT</bcp14>
send control messages that change state or cancel work (OPEN, ACCEPT,
UPDATE, JOIN_REQUEST, LEAVE, DECLARE, REVOKE, TERMINATE, SEGMENT,
CANCEL) or STATE_REQUEST in 0-RTT data.</t>
      <t>In a dialog between parties of different principals, the controller
acts for one of them. Participant descriptors that a participant
declares are verifiable against its own DECLARE, so the controller
cannot misstate them; descriptors that others observe are attributed,
so each participant weighs them by who made them. The controller can
still delay commits or refuse admissions other than those this
document requires it to accept; a participant that relies on a fair
controller in an adversarial dialog can be the controller itself, or
use a dialog host that neither party operates.</t>
      <t>A participant's <tt>kind</tt>, including <tt>human</tt>, is its own claim. Detection
of automation by others is recorded separately, and neither is proof.
Policies that grant more to people than to agents rely on
authentication, not on <tt>kind</tt>.</t>
      <t><tt>result</tt> and <tt>contact_limits</tt> are statements by their sender, not
evidence; a participant relies on the assertions and commitments they
cite, as PACE Authorization describes (<xref target="delegation-approval"/>). A join code is a bearer secret for the short time
it is valid: it is single use, rate limited, and admits the redeemer
only as the sponsored participant of the party it was issued to.</t>
      <t>A segment hides content from participants of this dialog only when
its content is exchanged in a separate dialog with its own keys
(<xref target="segments"/>, <xref target="e2e-protection"/>); a participant of the segment can
still disclose what it received.</t>
      <t>Relays can read and modify payloads that are not protected end to end
(<xref target="e2e-protection"/>), and they see control messages unless those are
protected too. A deployment that adds an evidence mechanism
(<xref target="records"/>) lets participants detect modification by relays even
when payloads are not encrypted.</t>
      <t>Without key-bound presentations at resumption (<xref target="key-binding"/>), a
captured STATE_REQUEST or STATE could be replayed to impersonate a
participant or the controller.</t>
      <t>Work in a delegated dialog that continued after its parent was
terminated or its authorization revoked would act without authority.
Lifecycle propagation (<xref target="lifecycle-propagation"/>) prevents this when
every controller in the chain is reachable; a controller that is not
leaves its delegated dialogs running until they expire, so delegated
dialogs <bcp14>SHOULD</bcp14> carry an <tt>expires_at</tt> no later than their parent's.
Enforcement outside the agent, such as a hold applied at an
enforcement point in front of the participant (for example, a TRAIL
edge <xref target="TRAIL"/>), stops a participant whether or not the participant
or its controller is reachable.</t>
      <t>Controller takeover (<xref target="controller-transfer"/>) lets the alternate
change the participant set. Participants accept it only from the
designated alternate with verified credentials.</t>
      <t>Threats specific to delegation and action approval, such as approval
spoofing by an intermediate agent and confused deputies, are
addressed in PACE Authorization (<xref target="delegation-approval"/>).</t>
      <t>TODO: further considerations.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document asks IANA to create the following registries in a new
"Protocol for Agent Communication Exchange (PACE)" group, each with
the Specification Required policy <xref target="RFC8126"/>. Each entry has a
value, a description, and a reference.</t>
      <t>PACE Result Reasons (<xref target="results"/>), with initial values <tt>policy</tt>,
<tt>ineligible</tt>, <tt>suspected-fraud</tt>, <tt>no-stated-purpose</tt>,
<tt>unwanted-contact</tt>, <tt>insufficient-assurance</tt>, <tt>upgrade-declined</tt>,
<tt>principal-declined</tt>, <tt>agreement-reached</tt>, <tt>no-agreement</tt>,
<tt>superseded</tt>, and <tt>consent-withdrawn</tt>, each referencing this document.</t>
      <t>PACE Contact Basis (<xref target="contact-basis"/>), with initial values
<tt>subscription</tt>, <tt>existing-relationship</tt>, <tt>contract</tt>,
<tt>legal-obligation</tt>, <tt>consent</tt>, and <tt>none</tt>, each referencing this
document.</t>
      <t>PACE Assurance Methods (<xref target="participant-descriptors"/>), with initial
values <tt>credential</tt>, <tt>cimd</tt>, <tt>resumed</tt>, and <tt>join-code</tt>, each
referencing this document. Other documents can register further
values, such as STIR/SHAKEN attestation levels for telephony.</t>
      <t>This document also asks IANA to register the following entry in the
"Setup Options" registry of <xref target="MoQ-TRANSPORT"/>:</t>
      <table>
        <thead>
          <tr>
            <th align="right">Type</th>
            <th align="left">Name</th>
            <th align="left">Specification</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="right">0x50414301</td>
            <td align="left">pace-version</td>
            <td align="left">
              <xref target="moqt-setup-extensions"/></td>
          </tr>
        </tbody>
      </table>
      <t>This document also asks IANA to register the following entry in the
"WIMSE Message Canonicalization Profiles" registry of <xref target="WPT-MSG"/>:</t>
      <ul spacing="normal">
        <li>
          <t>Profile Name: <tt>pace</tt></t>
        </li>
        <li>
          <t>Description: JCS of a PACE control message with its <tt>credentials</tt>
member removed</t>
        </li>
        <li>
          <t>Reference: <xref target="key-binding"/></t>
        </li>
      </ul>
      <t>This document also asks IANA to register <tt>application/pace-presentation+jwt</tt>
in the "Media Types" registry, for the <tt>typ</tt> header of PACE
presentation JWTs:</t>
      <ul spacing="normal">
        <li>
          <t>Type name: application</t>
        </li>
        <li>
          <t>Subtype name: pace-presentation+jwt</t>
        </li>
        <li>
          <t>Required parameters: n/a</t>
        </li>
        <li>
          <t>Optional parameters: n/a</t>
        </li>
        <li>
          <t>Encoding considerations: binary; a PACE presentation JWT is a JWT, a
sequence of base64url-encoded values separated by period characters</t>
        </li>
        <li>
          <t>Security considerations: <xref target="key-binding"/> of this document</t>
        </li>
        <li>
          <t>Interoperability considerations: n/a</t>
        </li>
        <li>
          <t>Published specification: this document</t>
        </li>
        <li>
          <t>Applications that use this media type: PACE participants</t>
        </li>
        <li>
          <t>Fragment identifier considerations: n/a</t>
        </li>
        <li>
          <t>Additional information: Magic number(s): n/a; File extension(s):
n/a; Macintosh file type code(s): n/a</t>
        </li>
        <li>
          <t>Person and email address to contact for further information: Suhas
Nandakumar, snandaku@cisco.com</t>
        </li>
        <li>
          <t>Intended usage: COMMON</t>
        </li>
        <li>
          <t>Restrictions on usage: none</t>
        </li>
        <li>
          <t>Author: Suhas Nandakumar, snandaku@cisco.com</t>
        </li>
        <li>
          <t>Change controller: IETF</t>
        </li>
      </ul>
      <t>TODO: registries for control operations, ERROR reasons, and dialog
parameters.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC6234">
          <front>
            <title>US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)</title>
            <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <date month="May" year="2011"/>
            <abstract>
              <t>Federal Information Processing Standard, FIPS</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6234"/>
          <seriesInfo name="DOI" value="10.17487/RFC6234"/>
        </reference>
        <reference anchor="RFC7515">
          <front>
            <title>JSON Web Signature (JWS)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7515"/>
          <seriesInfo name="DOI" value="10.17487/RFC7515"/>
        </reference>
        <reference anchor="RFC7519">
          <front>
            <title>JSON Web Token (JWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7519"/>
          <seriesInfo name="DOI" value="10.17487/RFC7519"/>
        </reference>
        <reference anchor="RFC7800">
          <front>
            <title>Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <date month="April" year="2016"/>
            <abstract>
              <t>This specification describes how to declare in a JSON Web Token (JWT) that the presenter of the JWT possesses a particular proof-of- possession key and how the recipient can cryptographically confirm proof of possession of the key by the presenter. Being able to prove possession of a key is also sometimes described as the presenter being a holder-of-key.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7800"/>
          <seriesInfo name="DOI" value="10.17487/RFC7800"/>
        </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="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>
        <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="RFC9000">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="RFC9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="July" year="2026"/>
            <abstract>
              <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t>This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9846"/>
          <seriesInfo name="DOI" value="10.17487/RFC9846"/>
        </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="RFC9562">
          <front>
            <title>Universally Unique IDentifiers (UUIDs)</title>
            <author fullname="K. Davis" initials="K." surname="Davis"/>
            <author fullname="B. Peabody" initials="B." surname="Peabody"/>
            <author fullname="P. Leach" initials="P." surname="Leach"/>
            <date month="May" year="2024"/>
            <abstract>
              <t>This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing System (NCS), later
in the Open Software Foundation's (OSF's) Distributed Computing
Environment (DCE), and then in Microsoft Windows platforms.</t>
              <t>This specification is derived from the OSF DCE specification with the
kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have
been incorporated into this document. This document obsoletes RFC
4122.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9562"/>
          <seriesInfo name="DOI" value="10.17487/RFC9562"/>
        </reference>
        <reference anchor="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="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC9420">
          <front>
            <title>The Messaging Layer Security (MLS) Protocol</title>
            <author fullname="R. Barnes" initials="R." surname="Barnes"/>
            <author fullname="B. Beurdouche" initials="B." surname="Beurdouche"/>
            <author fullname="R. Robert" initials="R." surname="Robert"/>
            <author fullname="J. Millican" initials="J." surname="Millican"/>
            <author fullname="E. Omara" initials="E." surname="Omara"/>
            <author fullname="K. Cohn-Gordon" initials="K." surname="Cohn-Gordon"/>
            <date month="July" year="2023"/>
            <abstract>
              <t>Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicating endpoints, and not to any servers involved in delivering messages. Establishing keys to provide such protections is challenging for group chat settings, in which more than two clients need to agree on a key but may not be online at the same time. In this document, we specify a key establishment protocol that provides efficient asynchronous group key establishment with forward secrecy (FS) and post-compromise security (PCS) for groups in size ranging from two to thousands.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9420"/>
          <seriesInfo name="DOI" value="10.17487/RFC9420"/>
        </reference>
        <reference anchor="ARCH">
          <front>
            <title>Architecture for AI Agent Communications on the Internet</title>
            <author fullname="Jonathan Rosenberg" initials="J." surname="Rosenberg">
              <organization>jdrosen.net</organization>
            </author>
            <author fullname="Zaheduzzaman Sarker" initials="Z." surname="Sarker">
              <organization>Nokia</organization>
            </author>
            <author fullname="Tirumaleswar Reddy.K" initials="T." surname="Reddy.K">
              <organization>Nokia</organization>
            </author>
            <author fullname="Kehan Yao" initials="K." surname="Yao">
              <organization>China Mobile</organization>
            </author>
            <author fullname="Dapeng Liu" initials="D." surname="Liu">
              <organization>Alibaba</organization>
            </author>
            <author fullname="Suresh Krishnan" initials="S." surname="Krishnan">
              <organization>Cisco</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   This document defines the terminology and architecture for AI agent
   communications protocols over the Internet.  It provides the
   foundational architectural elements for the Agent Communications
   Protocol (ACP) - also known as agentproto - a new protocol to be
   developed in the IETF.  ACP enables communication between user agent
   clients and AI agents, between AI Agents and other AI Agents, or
   between AI Agents and tools.  All three of these interaction patterns
   - and the many use cases therein - require a session-like protocol
   which handles lifecycle management, including creation, modification,
   deletion and so on - along with the exchange of input and output.
   These session-like associations can be extremely long lived - running
   for hours or even days - and span multiple IP hosts used by the both
   the principal and by the agent.  They can also be highly intermittent
   with asynchronous responses.  All of these mean a new type of
   protocol is needed.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-manyfolks-agentproto-arch-00"/>
        </reference>
        <reference anchor="QMUX">
          <front>
            <title>QMux</title>
            <author fullname="Kazuho Oku" initials="K." surname="Oku">
              <organization>Fastly</organization>
            </author>
            <author fullname="Lucas Pardue" initials="L." surname="Pardue">
              <organization>Cloudflare</organization>
            </author>
            <author fullname="Jana Iyengar" initials="J." surname="Iyengar">
              <organization>Netflix</organization>
            </author>
            <author fullname="Eric Kinnear" initials="E." surname="Kinnear">
              <organization>Apple</organization>
            </author>
            <date day="6" month="July" year="2026"/>
            <abstract>
              <t>   This document specifies QMux version 1.  QMux version 1 provides,
   over bi-directional streams such as TLS, the same set of stream and
   datagram operations that applications rely upon in QUIC version 1.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the QUIC Working Group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/quic/.

   Source for this draft and an issue tracker can be found at
   https://github.com/quicwg/qmux.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-quic-qmux-02"/>
        </reference>
        <reference anchor="WIMSE-CREDS">
          <front>
            <title>WIMSE Workload Credentials</title>
            <author fullname="Brian Campbell" initials="B." surname="Campbell">
              <organization>Ping Identity</organization>
            </author>
            <author fullname="Joseph A. Salowey" initials="J. A." surname="Salowey">
              <organization>Palo Alto Networks</organization>
            </author>
            <author fullname="Arndt Schwenkschuster" initials="A." surname="Schwenkschuster">
              <organization>Defakto Security</organization>
            </author>
            <author fullname="Yaron Sheffer" initials="Y." surname="Sheffer">
              <organization>Independent</organization>
            </author>
            <author fullname="Yaroslav Rosomakho" initials="Y." surname="Rosomakho">
              <organization>Zscaler</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   The WIMSE architecture defines authentication and authorization for
   software workloads in a variety of runtime environments, from the
   most basic ones up to complex multi-service, multi-cloud, multi-
   tenant deployments.

   This document defines the credentials that workloads use to represent
   their identity.  They can be used in various protocols to
   authenticate workloads to each other.  To use these credentials,
   workloads must provide proof of possession of the associated private
   key material, which is covered in other documents.  This document
   focuses on the credentials alone, independent of the proof-of-
   possession mechanism.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-wimse-workload-creds-03"/>
        </reference>
        <reference anchor="WIMSE-WPT">
          <front>
            <title>WIMSE Workload Proof Token</title>
            <author fullname="Brian Campbell" initials="B." surname="Campbell">
              <organization>Ping Identity</organization>
            </author>
            <author fullname="Arndt Schwenkschuster" initials="A." surname="Schwenkschuster">
              <organization>Defakto Security</organization>
            </author>
            <date day="27" month="August" year="2026"/>
            <abstract>
              <t>   The WIMSE architecture defines authentication and authorization for
   software workloads in a variety of runtime environments, from basic
   deployments to complex multi-service, multi-cloud, multi-tenant
   systems.  This document specifies the Workload Proof Token (WPT), a
   mechanism for workloads to prove possession of the private key
   associated with a Workload Identity Token (WIT).  The WPT is a signed
   JWT that binds the workload's authentication to a specific HTTP
   request, providing application-layer proof of possession for
   workload-to-workload communication.  This specification is designed
   to work alongside the WIT credential format defined in draft-ietf-
   wimse-workload-creds and can be combined with other WIMSE protocols
   in multi-hop call chains.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-wimse-wpt-02"/>
        </reference>
        <reference anchor="ACTOR-PROFILE">
          <front>
            <title>OAuth Actor Profile for Delegation</title>
            <author fullname="Karl McGuinness" initials="K." surname="McGuinness">
              <organization>Independent</organization>
            </author>
            <date day="8" month="October" year="2026"/>
            <abstract>
              <t>   This document defines a common representation of delegated actors in
   OAuth JSON Web Token (JWT) assertion grants, JWT access tokens, and
   Transaction Tokens.  It profiles the act claim defined by OAuth 2.0
   Token Exchange, requires issuer-scoped actor identifiers, and uses
   the sub_profile claim to classify actor entity types.  It specifies
   token processing, delegation-chain propagation, sender-constraint
   handling, and discovery metadata, so that issuers and resource
   servers in different trust domains interpret delegated actors
   consistently.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-mcguinness-oauth-actor-profile-01"/>
        </reference>
        <reference anchor="DELEGATION-TOKENS">
          <front>
            <title>Verifiable Attenuated Delegation for AI Agent Chains</title>
            <author fullname="Rafael Asor" initials="R." surname="Asor">
              <organization>Attenu</organization>
            </author>
            <date day="27" month="October" year="2026"/>
            <abstract>
              <t>   AI agents increasingly delegate tasks to other agents.  Each
   delegation should convey only a subset of the delegating party's
   authority, that subset should be bounded in scope, magnitude, and
   time, and any enforcement point should be able to verify -- offline,
   with no call to an authorization server -- that a token presented at
   hop N carries authority no greater than the token at hop N-1, back to
   a trusted root, and that every hop acts under the same accountable
   principal.  OAuth 2.0 Token Exchange (RFC 8693) models two-party
   delegation and records prior actors in a nested "act" claim, but that
   claim is informational only and cannot enforce attenuation across a
   chain of depth two or more.  This document defines the Agent
   Delegation Chain: a profile of OAuth 2.0 JWT access tokens (RFC 9068)
   that carries authority as Rich Authorization Requests (RFC 9396),
   binds the chain to one principal and names the agent acting at each
   hop, links each delegation to its parent by a cryptographic byte-
   commitment, and specifies a deterministic offline verification
   algorithm that enforces monotonic attenuation, bounded depth,
   monotonic expiry, and principal invariance.  It reuses existing JOSE,
   proof-of-possession (RFC 9449), and status-list machinery (the OAuth
   Status List draft) and introduces no new cryptography.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-asor-wimse-agent-delegation-chain-03"/>
        </reference>
        <reference anchor="AGENT-DELEGATION" target="https://datatracker.ietf.org/doc/draft-nandakumar-wimse-delegator-bound-chains/">
          <front>
            <title>Delegator-Bound Delegation Chains for AI Agents</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-delegator-bound-chains-00"/>
        </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="RFC8693">
          <front>
            <title>OAuth 2.0 Token Exchange</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="A. Nadalin" initials="A." surname="Nadalin"/>
            <author fullname="B. Campbell" initials="B." role="editor" surname="Campbell"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="C. Mortimore" initials="C." surname="Mortimore"/>
            <date month="January" year="2020"/>
            <abstract>
              <t>This specification defines a protocol for an HTTP- and JSON-based Security Token Service (STS) by defining how to request and obtain security tokens from OAuth 2.0 authorization servers, including security tokens employing impersonation and delegation.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8693"/>
          <seriesInfo name="DOI" value="10.17487/RFC8693"/>
        </reference>
        <reference anchor="RFC9635">
          <front>
            <title>Grant Negotiation and Authorization Protocol (GNAP)</title>
            <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
            <author fullname="F. Imbault" initials="F." surname="Imbault"/>
            <date month="October" year="2024"/>
            <abstract>
              <t>The Grant Negotiation and Authorization Protocol (GNAP) defines a mechanism for delegating authorization to a piece of software and conveying the results and artifacts of that delegation to the software. This delegation can include access to a set of APIs as well as subject information passed directly to the software.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9635"/>
          <seriesInfo name="DOI" value="10.17487/RFC9635"/>
        </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="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="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="MOQ-PP">
          <front>
            <title>Privacy Pass Authentication for Media over QUIC (MoQ)</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</organization>
            </author>
            <author fullname="Thibault Meunier" initials="T." surname="Meunier">
              <organization>Cloudflare Inc.</organization>
            </author>
            <date day="1" month="November" year="2026"/>
            <abstract>
              <t>   This document specifies the use of Privacy Pass architecture and
   issuance protocols for authorization in Media over QUIC (MoQ)
   transport protocol.  It defines how Privacy Pass tokens can be
   integrated with MoQ's authorization framework to provide privacy-
   preserving authentication for subscriptions, fetches, publications,
   and relay operations while supporting fine-grained access control
   through prefix-based track namespace and track name matching rules.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-privacy-pass-auth-04"/>
        </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="RFC9901">
          <front>
            <title>Selective Disclosure for JSON Web Tokens</title>
            <author fullname="D. Fett" initials="D." surname="Fett"/>
            <author fullname="K. Yasuda" initials="K." surname="Yasuda"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <date month="November" year="2025"/>
            <abstract>
              <t>This specification defines a mechanism for the selective disclosure
of individual elements of a JSON data structure used as the payload
of a JSON Web Signature (JWS). The primary use case is the selective
disclosure of JSON Web Token (JWT) claims.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9901"/>
          <seriesInfo name="DOI" value="10.17487/RFC9901"/>
        </reference>
        <reference anchor="MOQ-SECURE-OBJECTS">
          <front>
            <title>End-to-End Secure Objects for Media over QUIC Transport</title>
            <author fullname="Cullen Fluffy Jennings" initials="C. F." surname="Jennings">
              <organization>Cisco</organization>
            </author>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Richard Barnes" initials="R." surname="Barnes">
              <organization>Cisco</organization>
            </author>
            <date day="6" month="July" year="2026"/>
            <abstract>
              <t>   This document specifies an end-to-end authenticated encryption scheme
   for application objects transmitted via Media over QUIC (MoQ)
   Transport.  The scheme enables original publishers that share a
   symmetric key with end subscribers, to ensuring that MoQ relays are
   unable to decrypt object contents.  Additionally, subscribers can
   verify the integrity and authenticity of received objects, confirming
   that the content has not been modified in transit.  Additionally it
   allows MoQ parameters to be protected so the publisher can select if
   they are readable and/or modifiable by relays.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-secure-objects-01"/>
        </reference>
        <reference anchor="TRAIL">
          <front>
            <title>TRAIL: Tamper-evident Records for Agent Interactions and Liveness</title>
            <author fullname="Kareem Nassar" initials="K." surname="Nassar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Cullen Fluffy Jennings" initials="C. F." surname="Jennings">
              <organization>Cisco</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   AI agents call other agents and tools across organizational
   boundaries, but the records of what they did are kept by the
   operators whose conduct the records describe, and the parties
   overseeing them learn of problems only afterwards.  TRAIL makes this
   communication auditable and revocable by parties other than the
   operator.  An enforcement point outside the agent and its sandbox,
   the edge, signs each call as a COSE Action Record, which the receiver
   keeps, and appends it to a tamper-evident trail that witnesses
   countersign.  Authorities read the trails and publish rules that the
   edge enforces on every call: require approval, refuse an action, stop
   an agent, or cap how many agents run across machines.  The edge lets
   traffic through only while it holds current state from each authority
   and a recent witness countersignature, so an authority that goes
   silent, or a trail that nobody is witnessing, stops the agent.  TRAIL
   defines bindings to HTTP and to Media over QUIC Transport (MOQT) that
   produce the same evidence; over MOQT, holds reach edges as soon as
   they are published.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nassar-agentproto-trail-00"/>
        </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="POPPY" target="https://personalagentprotocol.org/docs/0.3/spec">
          <front>
            <title>Personal Agent Protocol (Poppy) Specification</title>
            <author>
              <organization>Sierra</organization>
            </author>
            <author>
              <organization>Meta</organization>
            </author>
            <date year="2026"/>
          </front>
          <seriesInfo name="Version" value="Draft 0.3"/>
        </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="AutoGen" target="https://arxiv.org/abs/2308.08155">
          <front>
            <title>AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation</title>
            <author initials="Q." surname="Wu">
              <organization/>
            </author>
            <author initials="G." surname="Banber">
              <organization/>
            </author>
            <author initials="Y." surname="Zhang">
              <organization/>
            </author>
            <author initials="Y." surname="Wu">
              <organization/>
            </author>
            <author initials="B." surname="Li">
              <organization/>
            </author>
            <author initials="E." surname="Zhu">
              <organization/>
            </author>
            <author initials="A." surname="Awadallah">
              <organization/>
            </author>
            <date year="2023"/>
          </front>
          <seriesInfo name="arXiv" value="2308.08155"/>
        </reference>
        <reference anchor="MoQ-C4M" target="https://datatracker.ietf.org/doc/draft-ietf-moq-c4m/">
          <front>
            <title>Authorization scheme for MOQT using Common Access Tokens</title>
            <author initials="W." surname="Law">
              <organization/>
            </author>
            <author initials="C." surname="Lemmons">
              <organization/>
            </author>
            <author initials="G." surname="Simon">
              <organization/>
            </author>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-c4m-02"/>
        </reference>
        <reference anchor="MCP-MOQT">
          <front>
            <title>Model Context Protocol and Agent Skills over Media over QUIC Transport</title>
            <author fullname="Cullen Fluffy Jennings" initials="C. F." surname="Jennings">
              <organization>Cisco</organization>
            </author>
            <author fullname="Ian Swett" initials="I." surname="Swett">
              <organization>Google</organization>
            </author>
            <author fullname="Jonathan Rosenberg" initials="J." surname="Rosenberg">
              <organization>Five9</organization>
            </author>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <date day="1" month="November" year="2026"/>
            <abstract>
              <t>   This document defines how to use Media over QUIC Transport (MOQT) as
   the underlying transport protocol for the Model Context Protocol
   (MCP).  MCP enables integration between language model applications
   and external data sources and tools.  MOQT provides publish-subscribe
   delivery over QUIC and WebTransport with native prioritization, relay
   caching, and multiplexing.

   This specification maps MCP messages onto MOQT objects and tracks.
   It covers MCP's tools, resources, prompts, multi round-trip requests,
   and the Tasks extension, and it uses MOQT relays to cache content
   that MCP marks as public across clients and to let a response outlive
   the connection that carried its request.

   The document also describes Agent Skills, composed instructions that
   extend AI capabilities beyond atomic tool operations, using
   progressive loading aligned with MOQT's object-based delivery.  The
   same tracks can run standalone or inside a dialog of the Protocol for
   Agent Communication Exchange (PACE).

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-jennings-agentproto-mcp-over-moqt-01"/>
        </reference>
        <reference anchor="RFC9396">
          <front>
            <title>OAuth 2.0 Rich Authorization Requests</title>
            <author fullname="T. Lodderstedt" initials="T." surname="Lodderstedt"/>
            <author fullname="J. Richer" initials="J." surname="Richer"/>
            <author fullname="B. Campbell" initials="B." surname="Campbell"/>
            <date month="May" year="2023"/>
            <abstract>
              <t>This document specifies a new parameter authorization_details that is used to carry fine-grained authorization data in OAuth messages.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9396"/>
          <seriesInfo name="DOI" value="10.17487/RFC9396"/>
        </reference>
        <reference anchor="CIMD">
          <front>
            <title>OAuth Client ID Metadata Document</title>
            <author fullname="Aaron Parecki" initials="A." surname="Parecki">
              <organization>Okta</organization>
            </author>
            <author fullname="Emelia Smith" initials="E." surname="Smith">
              <organization>independent</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   This specification defines a mechanism through which an OAuth client
   can identify itself to authorization servers, without prior dynamic
   client registration or other existing registration.  This is through
   the usage of a URL as a client_id in an OAuth flow, where the URL
   refers to a document containing the necessary client metadata,
   enabling the authorization server to fetch the metadata about the
   client as needed.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-client-id-metadata-document-03"/>
        </reference>
        <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="STIVERS">
          <front>
            <title>Universals and cultural variation in turn-taking in conversation</title>
            <author initials="T." surname="Stivers">
              <organization/>
            </author>
            <author initials="N. J." surname="Enfield">
              <organization/>
            </author>
            <author initials="P." surname="Brown">
              <organization/>
            </author>
            <author initials="C." surname="Englert">
              <organization/>
            </author>
            <author initials="M." surname="Hayashi">
              <organization/>
            </author>
            <author initials="T." surname="Heinemann">
              <organization/>
            </author>
            <author initials="G." surname="Hoymann">
              <organization/>
            </author>
            <author initials="F." surname="Rossano">
              <organization/>
            </author>
            <author initials="J. P." surname="de Ruiter">
              <organization/>
            </author>
            <author initials="K." surname="Yoon">
              <organization/>
            </author>
            <author initials="S. C." surname="Levinson">
              <organization/>
            </author>
            <date year="2009" month="June"/>
          </front>
          <seriesInfo name="DOI" value="10.1073/pnas.0903616106"/>
          <refcontent>Proceedings of the National Academy of Sciences, vol. 106, no. 26, pp. 10587-10592</refcontent>
        </reference>
        <reference anchor="SD-CARD" target="https://datatracker.ietf.org/doc/draft-nandakumar-agent-sd-card/">
          <front>
            <title>Agent SD-Card: Selective Disclosure of Agent Metadata for Discovery and Authentication</title>
            <author initials="S." surname="Nandakumar">
              <organization/>
            </author>
            <author initials="C." surname="Jennings">
              <organization/>
            </author>
            <date year="2026" month="October"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-nandakumar-agent-sd-card-00"/>
        </reference>
      </references>
    </references>
    <?line 3590?>

<section anchor="example-workflows">
      <name>Example Workflows</name>
      <t>The examples below share these conventions:</t>
      <ul spacing="normal">
        <li>
          <t><tt>D1</tt> to <tt>D7</tt> stand for dialog-ids (UUIDs). <tt>A</tt>, <tt>B</tt>, and <tt>C</tt> are
agents with agent-ids <tt>agent-a</tt>, <tt>agent-b</tt>, and <tt>agent-c</tt>; other
agents are named in the example that introduces them.</t>
        </li>
        <li>
          <t>Before each example, every agent follows the others
(<xref target="agent-discovery"/>). Each invitee learns the dialog-id from an
invitation (<xref target="invitations"/>), and every participant holds
SUBSCRIBE_TRACKS on the dialog prefix. The relay therefore forwards
every new dialog track to the participants, and the steps do not
repeat the invitations or relay hops.</t>
        </li>
        <li>
          <t>Each example lists the tracks by publisher, then the steps. <tt>gen</tt>
is the dialog generation after a controller operation.</t>
        </li>
        <li>
          <t>JSON-RPC messages are shown without the dialog reference
(<xref target="carrying-dialog-context"/>) and, for MCP, without the per-request
<tt>_meta</tt> fields of <xref target="MCP"/>; real messages carry both.</t>
        </li>
      </ul>
      <section anchor="delegating-a-task-with-a2a">
        <name>Delegating a Task with A2A</name>
        <t>A asks B to do a task. This example shows the complete dialog
lifecycle; the later examples abbreviate it.</t>
        <artwork><![CDATA[
A publishes:
  ("pace","dialogs",D1,"agent-a") -- "ctrl"        OPEN, UPDATE,
                                                   TERMINATE
  ("pace","dialogs",D1,"agent-a","a2a","request") -- "r1"
                                                   task request
B publishes:
  ("pace","dialogs",D1,"agent-b") -- "ctrl"        ACCEPT
  ("pace","dialogs",D1,"agent-b","a2a","response") -- "r1"
                                                   task result
]]></artwork>
        <ol spacing="normal" type="1"><li>
            <t>A publishes OPEN on its <tt>ctrl</tt> track (gen 0, B <tt>invited</tt>) and an
invitation on <tt>("pace","agents","agent-a","invites") -- "agent-b"</tt>.</t>
          </li>
          <li>
            <t>B reads OPEN on A's <tt>ctrl</tt> track and publishes ACCEPT on its own
<tt>ctrl</tt> track.</t>
          </li>
          <li>
            <t>A publishes UPDATE (gen 1, B <tt>active</tt>). The dialog is active.</t>
          </li>
          <li>
            <t>A publishes the A2A request on its <tt>request</tt> track <tt>r1</tt>:
<tt>{"jsonrpc":"2.0","method":"SendMessage","params":{...},"id":"r1"}</tt>,
with the dialog reference in the message <tt>metadata</tt>
(<xref target="carrying-dialog-context"/>).</t>
          </li>
          <li>
            <t>B publishes the result on its <tt>response</tt> track <tt>r1</tt>.</t>
          </li>
          <li>
            <t>A publishes TERMINATE (gen 2). B could instead have sent LEAVE.</t>
          </li>
        </ol>
      </section>
      <section anchor="calling-an-mcp-tool">
        <name>Calling an MCP Tool</name>
        <t>A reads a file through an MCP server, <tt>fs-tool</tt>.</t>
        <artwork><![CDATA[
A publishes:
  ("pace","dialogs",D2,"agent-a") -- "ctrl"
  ("pace","dialogs",D2,"agent-a","mcp","tools","readFile")
      -- "request"                                 tools/call
fs-tool publishes:
  ("pace","dialogs",D2,"fs-tool") -- "ctrl"
  ("pace","dialogs",D2,"fs-tool","mcp","tools","readFile")
      -- "response"                                result
]]></artwork>
        <ol spacing="normal" type="1"><li>
            <t>A opens the dialog with fs-tool (OPEN, ACCEPT, UPDATE).</t>
          </li>
          <li>
            <t>A publishes the call as Object 0 of a new group, say Group 7, on
its <tt>readFile</tt> request track:
<tt>{"jsonrpc":"2.0","method":"tools/call","params":{"name":"readFile",
"arguments":{"path":"/data/report.csv"}},"id":"t1"}</tt>.</t>
          </li>
          <li>
            <t>fs-tool publishes the result as the final object in Group 7 of its
<tt>readFile</tt> response track:
<tt>{"jsonrpc":"2.0","id":"t1","result":{"resultType":"complete",
"content":[...]}}</tt>. The JSON-RPC <tt>id</tt> pairs the response with the
request; the matching Group ID helps relays and recovery
(<xref target="MCP-MOQT"/>).</t>
          </li>
          <li>
            <t>A makes further calls as new groups, or terminates the dialog.</t>
          </li>
        </ol>
      </section>
      <section anchor="long-running-tool-call-with-progress">
        <name>Long-Running Tool Call with Progress</name>
        <t>A asks <tt>code-tool</tt> to generate code. The call takes a while, so
code-tool reports progress while it works and sends the code in the
final result.</t>
        <artwork><![CDATA[
A publishes:
  ("pace","dialogs",D3,"agent-a") -- "ctrl"
  ("pace","dialogs",D3,"agent-a","mcp","tools","generateCode")
      -- "request"                                 tools/call,
                                                   cancellation
code-tool publishes:
  ("pace","dialogs",D3,"code-tool") -- "ctrl"
  ("pace","dialogs",D3,"code-tool","mcp","tools","generateCode")
      -- "response"                                progress, result
]]></artwork>
        <ol spacing="normal" type="1"><li>
            <t>A opens the dialog with code-tool (OPEN, ACCEPT, UPDATE).</t>
          </li>
          <li>
            <t>A publishes the call as Object 0 of Group 5 on its <tt>generateCode</tt>
request track, asking for progress with a <tt>progressToken</tt>:
<tt>{"jsonrpc":"2.0","id":"g1","method":"tools/call","params":
{"name":"generateCode","arguments":{"language":"python"},
"_meta":{"progressToken":"g1"}}}</tt>.</t>
          </li>
          <li>
            <t>code-tool publishes Group 5 of its <tt>generateCode</tt> response track as
shown in the table below. It sends the progress notifications in
one subgroup and the result in another, so that each is on its own
QUIC stream and a large result does not delay the progress
updates (<xref target="MCP-MOQT"/>). A receives each object as soon as it
arrives, orders them by Object ID, and knows the call is complete
when the result arrives.</t>
          </li>
          <li>
            <t>To cancel instead, A publishes <tt>notifications/cancelled</tt> as the next
object in Group 5 of its request track (<xref target="MCP-MOQT"/>). code-tool
stops and ends Group 5 of its response track with a JSON-RPC
error.</t>
          </li>
        </ol>
        <t>The table lists the objects in code-tool's reply, in Object ID order,
and the subgroup that carries each.</t>
        <table>
          <name>Objects in code-tool's Reply to the Group 5 Call</name>
          <thead>
            <tr>
              <th align="left">Object</th>
              <th align="left">Subgroup</th>
              <th align="left">Content</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">0</td>
              <td align="left">
                <tt>notifications/progress</tt>: progress 0 of 3, "Planning modules"</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">0</td>
              <td align="left">
                <tt>notifications/progress</tt>: progress 1 of 3, "Generated parser"</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">0</td>
              <td align="left">
                <tt>notifications/progress</tt>: progress 2 of 3, "Generated tests"</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">1</td>
              <td align="left">
                <tt>tools/call</tt> result with the generated code (142 lines)</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="interrupting-a-voice-agent">
        <name>Interrupting a Voice Agent</name>
        <t>A user's client, <tt>U</tt> (agent-id <tt>user-u</tt>), talks to a voice agent, <tt>V</tt>
(agent-id <tt>agent-v</tt>). V answers by voice while a tool call it made to
<tt>search-tool</tt> is still running. The user cuts in, and V has to stop
speaking and cancel the tool call at once.</t>
        <artwork><![CDATA[
U publishes:
  ("pace","dialogs",D4,"user-u") -- "ctrl"         ACCEPT
  ("pace","dialogs",D4,"user-u") -- "audio"        microphone
V publishes:
  ("pace","dialogs",D4,"agent-v") -- "ctrl"        OPEN, UPDATE,
                                                   CANCEL
  ("pace","dialogs",D4,"agent-v") -- "audio"       speech
  ("pace","dialogs",D4,"agent-v") -- "chat"        reply text
  ("pace","dialogs",D4,"agent-v","mcp","tools","search")
      -- "request"                                 tools/call
search-tool publishes:
  ("pace","dialogs",D4,"search-tool") -- "ctrl"    ACCEPT,
                                                   CANCEL_ACK
  ("pace","dialogs",D4,"search-tool","mcp","tools","search")
      -- "response"                                results
]]></artwork>
        <ol spacing="normal" type="1"><li>
            <t>V opens the dialog with U (OPEN, ACCEPT, UPDATE) and adds
search-tool the same way.</t>
          </li>
          <li>
            <t>V answers the user. It publishes speech on its <tt>audio</tt> track as
datagrams at media priority (32-63), with a short
OBJECT_DELIVERY_TIMEOUT, and the reply text on <tt>chat</tt> at interactive
priority (64-95). Its call to search-tool, Group 3 of the <tt>search</tt>
request track, is still running.</t>
          </li>
          <li>
            <t>The user starts speaking. U publishes microphone audio on its
<tt>audio</tt> track, and the relay forwards each frame to V as it
arrives. The dialog does not change.</t>
          </li>
          <li>
            <t>V detects the user's speech and stops producing speech and text. It
publishes CANCEL on its <tt>ctrl</tt> track at critical priority (0-15),
with scope <tt>operation</tt> and a <tt>target</tt> naming Group 3 of its
<tt>search</tt> request track (<xref target="cancel-over-moqt"/>). The cancellation is
sent ahead of any <tt>chat</tt> objects V has already queued, and a loss on
the audio datagrams does not delay it.</t>
          </li>
          <li>
            <t>Speech objects that the relay has not delivered within their
delivery timeout are dropped at the relay, so the user does not
hear the rest of the old answer after cutting in.</t>
          </li>
          <li>
            <t>search-tool applies the CANCEL as MCP <tt>notifications/cancelled</tt>,
stops, publishes no further objects in Group 3, and publishes
CANCEL_ACK with outcome <tt>stopped</tt> on its <tt>ctrl</tt> track. V
listens to the rest of the user's audio and answers in new groups
on its <tt>audio</tt> and <tt>chat</tt> tracks.</t>
          </li>
        </ol>
        <t>The dialog, its generation, and the MOQT sessions stay the same
throughout: an interruption changes the content of a dialog, not the
dialog. If the dialog's flows shared one ordered connection, the
cancellation in step 4 would wait behind the output V had already
sent.</t>
      </section>
      <section anchor="collaborating-in-a-multi-party-dialog">
        <name>Collaborating in a Multi-Party Dialog</name>
        <t>A coordinates research by B, a web researcher, and C, a data analyst.</t>
        <artwork><![CDATA[
A publishes:
  ("pace","dialogs",D5,"agent-a") -- "ctrl"        OPEN, UPDATE,
                                                   TERMINATE
  ("pace","dialogs",D5,"agent-a") -- "chat"        assignments
B publishes:
  ("pace","dialogs",D5,"agent-b") -- "ctrl"        ACCEPT
  ("pace","dialogs",D5,"agent-b") -- "chat"        status
  ("pace","dialogs",D5,"agent-b","a2a","task") -- "research-1"
                                                   findings
C publishes:
  ("pace","dialogs",D5,"agent-c") -- "ctrl"        ACCEPT
  ("pace","dialogs",D5,"agent-c") -- "chat"        status
  ("pace","dialogs",D5,"agent-c","a2a","task") -- "analysis-1"
                                                   results
]]></artwork>
        <t>Because each participant subscribes to the dialog prefix, every agent
receives every other agent's tracks in <tt>D5</tt>; no per-track
subscriptions are needed.</t>
        <ol spacing="normal" type="1"><li>
            <t>A publishes OPEN (gen 0, B and C <tt>invited</tt>). B and C each publish
ACCEPT, and A commits both in one UPDATE (gen 1).</t>
          </li>
          <li>
            <t>A posts assignments on <tt>chat</tt>. The relay delivers each object once
to B and once to C.</t>
          </li>
          <li>
            <t>B publishes findings on <tt>research-1</tt> as they arrive, one group per
research phase.</t>
          </li>
          <li>
            <t>C reads B's findings as they arrive and publishes its analysis on
<tt>analysis-1</tt>.</t>
          </li>
          <li>
            <t>A follows both tracks, posts a summary on <tt>chat</tt>, and publishes
TERMINATE (gen 2). Each agent then ends its dialog tracks with
PUBLISH_DONE.</t>
          </li>
        </ol>
      </section>
      <section anchor="group-chat-with-an-autogen-runtime">
        <name>Group Chat with an AutoGen Runtime</name>
        <t>An AutoGen <xref target="AutoGen"/> runtime, R, hosts a group chat with a human, H,
and a remote agent, B. AutoGen has no binding of its own, so R uses the
generic binding (<xref target="jsonrpc-binding"/>) with <tt>"autogen"</tt> as the protocol
name, and each AutoGen message carries the dialog reference in its
<tt>metadata</tt> (<xref target="carrying-dialog-context"/>).</t>
        <artwork><![CDATA[
R publishes:
  ("pace","dialogs",D6,"runtime-r") -- "ctrl"      OPEN, UPDATE,
                                                   TERMINATE
  ("pace","dialogs",D6,"runtime-r","ext","autogen") -- "conv1"
                                                   R's agents' turns
H publishes:
  ("pace","dialogs",D6,"user-h") -- "ctrl"         ACCEPT
  ("pace","dialogs",D6,"user-h") -- "chat"         human input
B publishes:
  ("pace","dialogs",D6,"agent-b") -- "ctrl"        ACCEPT
  ("pace","dialogs",D6,"agent-b","ext","autogen") -- "conv1"
                                                   B's turns
]]></artwork>
        <ol spacing="normal" type="1"><li>
            <t>R opens <tt>D6</tt> (gen 0, H and B <tt>invited</tt>), and commits both ACCEPTs in
one UPDATE (gen 1).</t>
          </li>
          <li>
            <t>R's group chat manager picks the next speaker, as AutoGen does. The
speaker's message goes out once on its publisher's <tt>conv1</tt> track,
and the relay delivers it to every other participant.</t>
          </li>
          <li>
            <t>When the manager asks the human, H answers on <tt>chat</tt>.</t>
          </li>
          <li>
            <t>For a nested chat, R opens a child dialog <tt>D7</tt> whose
<tt>parent_dialog_ids</tt> is <tt>[D6]</tt>, and posts its result back in <tt>D6</tt>.</t>
          </li>
          <li>
            <t>R publishes TERMINATE (gen 2) when the chat ends.</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAEtf+2oAA9y9zXYbSZIuuI+niKEWJWUDECkplZlU367LpJiZrNJfiVTl
rb6nRwgCQTJKAAIdAZCJltTnnruexSx6MYtZzGKeZB6ln2TMPjNzNw8EJGV1
nenuyVOVKQEID/8xt3/7bDgcZqtqNSsP871XR8cnh/mrpl7Vk3qWX9ZNfnRV
Llb5cT2frxfVpFhV9SI/+WVyXSyuyr2suLhoyht9ci+j78urutkc5u1qmmXT
erIo5jTwtCkuV8NFsZgW79bzohkWPOqS3zNcFpNyuH+QteuLedW2NP5qs6Rn
Tk/Of8gW6/lF2Rxmk3rRlot23R7mq2ZdZvTKh1nRlAW9+mi5nOnM2pxekb8u
i9nwvJrT/G7r5t1VU6+X/LueldhS273sXbmhX08Ps3yYY3pDmhz+kHyyqusZ
f/D85R/O+b9Hp/Jdy3+ZVsWsvsrnxYI+m+ujDU9nRdPJJ/7dWXZTLtYlvS//
whnmuezM3s+0qmpxlf/Iz/Hn86Ka0edxV/9rVa4uR3Vzxd8WzeSavr1erZbt
4f37/GP+qLopR/az+/zB/Yumvm3L+3GY+/z4VbW6Xl/QAO36umh/Kpvy/ufO
kx+bES20K/fe8PhIRhxV9WcH+uwPRter+Wwvy4r16rpu+PDo1XkuZLd3xq/M
X4Sn9/AlrbdYVP+E/aUfHVftpJZvSt3IVl/4Xyf83YjOba8z8vF6NisX+e/K
xYJOot09cH62aVflvE1fcDlbX15u/PDZom7m9OQNKOL1D8ePHzx8pH/85uuD
r+Mfv7M/fru/r3/89ptv8YOfX50Pn5/9eIh32aV+XrYt7Vr+fbWYMtXwrWYK
mtXFlMmrvszP63d0u2SKUzq3w/zB/oPHw4MDfBL2lv4Z5tWCLuHZyO2q/+J4
FPYEH7dlU5Vttbis5fk8P12symZRroZP+Wh7eMNtNW/L4e1yNZzLzIcXMvPh
/r4srGiuSnrSCItmXKyaYvKubCJBE+/ZJp6dQ9+XfXxwEHb324NvbPu/2w8b
/d23jx7bDx58bb/97uvHD/iPz+s/DM9fH704e/Xy9Xn3EIg35PVN2eR/eHN6
nJ83xaJd1s3qr7HpfxzlfyzaalaVN/7j01F+dluuVrrxTc0zoXms6uTpo1H+
Q0PbUM5mu375pafIuz+c1/84XNnyhg8e/iVntj3Q/Szj96d35LtHD3AyR6+P
f6L1Dp+OiPVuLuvZu9YzCmZu9Ks/PH/z3+RXGP4f19Vk+I/z9S98cU6fn50M
j1+fPD1zv1By0bsynDTltA0/pru2/dMlb/bR8fnL18NXr1/+cPrsRKc1uVpX
iwUR3bDmkx0WE9rbIU3vspqV9MzTk2cnPx6dn758MTx/+fuTFzqNoq2NakUC
0SmVV2AwQ5LB1YJf9+PJi/NhHCAlvKfyAA3zfb0m4fg0DJAf8wCtSPlTEfT/
sXjANMz9gucuK27/Wmygf3TmBC+P3pz/NHwwOnAHLMd282B4oNf/8XcPjQof
PxTue/I9bv/wp4eeMsoLEPGQ5/nQ6PZR5B3fgKOQPjF89co9x9S/bKqbYrIh
SUeEwxOgH756NcSJn6Xn/Ep+mr+in+JI9aDLqZ7soT/6oxULZ/kzq0w/1bNp
aSTyH0oa6BZgB6a2JLkMfwVK+NToKhO++27/wA7o7OT4zeuT4cvvf3dyfH7W
Oay2nKybclhf/LmcsDqYEzGcPpMfLegFqfJC86uY37LiPGR6+/vOedLn+RH2
OmgU7gD50I4mcpZLGvGmmP0HObCuas+v/6d/+0n1DstH9Orlq1d/6uxd2bT1
opip8RLsmbuv6uVycy8/W5aT6lI17O629ewZTYr2rCqbpvCfPC9XxY5d+iPN
QI6M15Hvj/ql4FInGhdH07Q9aO/TY/dbmisz+QdH6RqPzCDprPFTa/t619qe
VYv1L/kPfPvFNvnMqvYORvt7vSsqHhTDZCFiBvBBPT9+1dGJarpyZO4QRf3y
hSt4PNz/5q+1CB1u+ODb3pXMeXYTmVxYEZksrZ/e/WQQuq71j+Wic1D6YX6y
KC5mrIC/oBGH9FH+7NnzPLFeb0hHfL6eraqhmYIL0hjbvp14uOtu/2GU/7z2
H/w4yr8vFmRG+w//NMr/nm34zmfpk9+PaFP9Byf8VPITUh6PbotpMZsV1zs2
vGj+W8UuggcP978d7X978PXXO0in+aW6EWP0or0ff62K9fGj51sbG5lj3k6u
yeKG5GPTPF+3vNVsSzOLnExI9fr1gu1n2oDitsMgn5U8ZtvZ4rNqriS3k8f+
ai168mg+3H/wb9KfaQi9e0PeFpFGf1YW75nqfLIcsnnCT61U8j38DqrJ8enz
p1ua0ISsDWJA1ZRMqVXB0xnS69fi9Mifnh49e/nj8M1xD9OqJvlT8ZO8acv8
uGjLX3MkP/BWb4qb9ZQ+PTs//ePJ644m9GZR4dLMxBs0ofu0bkgY3BRNJbRS
LXL6aDFcFXCj0F8nOy/a/nfD/T6ZgMmc02RWeJv/9AUJ0RFd98uqnE39F6/o
Jjb17aJDUCeLq1nZrPynz0f5T8WmaK+rzut+KqtFSUbOokN+P9Wb7qe0U69r
UjsWtf+UZkbTmJb563W1SnnC70dDuuB/qrfoGER/Q3/byVSfvjw9zA/2Rwf7
3zy8vyRtZ7T/3f7DxwePD3TzmvISvHSxgq5aT8qS7e42ry/z1XVJV4W3nkX2
pJiW8w1/fjYhEqOLO8hviPXS8I8H+aIe5Q/ov8slf/D1t98M6d/fPeAzO3s6
PD56/bSH4vBV0UxpMaRBTfjEiATbyaxuSWPjV8nPnisli/7Mvhk62o3oWnT4
oN1+qXSw/++mag1bMl1ocX8lFcuGI3t7OBzmxIr54VWWnV9XbW5XnAjokgix
xdl9sb84u8ta7b0B7ag4TYkVbLlMcxO2+W21us6LXF00+arO4UXJerwo+V3m
bvdIGNmAlcxtUjdNOYMZ1Jb/uGZ6ovPOKt7aYiJS96Jc3ZYkjle3NWkS+bwm
mlgWDc2uWhZkCIjbRkZbNy0IpshWRftuBPU9bEaRR78HO1SWJf2LN0umpMoE
0xM7tFcNrbEmFVCFP62PbTLSEdrrAc1iWl1uBiA+muu8WtAiMhlJGBv9vilv
SKTxji0LNQywWh7vulq2o/x0lavCQvO7rm9pGcUqs5nQ6zYtzeu6bHiexaQh
hpFjc+a81UyRA/a4t6scRrJ8ktHkilm12uRyrq1ME8816yVeLx/xG6sVHwbR
FD07lb3kwxplsnc1TWxRr+TpZVOu+AxkR5ONW6xG+Ut7mEYPXxYLWs/8gn/P
i6Kv1tOqJqZRTctaptHw0ZMW2pR0OAs6wVIpkhebLetKVGn8gXiL/X3Oqph+
yMPg70MmjQ3t/rKm19N2jDKnww1nxYbmCOoOlNzm7XpCpNyyGj9gYTwwpsKq
Yf6uLJcZ0VfV5CQdcvVN5uLtUilG27cBDXaIaXXd1Oura/c4fUpaDtMCpk5E
4OxGo3UxcTF0ofaj3ItpRfu2pr/JEuyOFHQnjJD4pGn/adPpevCgxhVGwjPm
1XQ6K7PsDnOwpp6uJxLvCKESjEa8sl7U83pNu1Nfrm7xBvGVg0hz9rsJD1gT
bySCqmmNTSZD6MWoeXPpIvBcZuWKKIBuJa34/NqfcbjgpCJiV+0efYpfZI5f
5H8Zv8gcv8iFX/zAxK2XmOaNNeq1W9JreXJyKjfEO2padZaMvCCxKVvPau1t
sZHF65zjpQC1FjRr+j9dwDabVZflZDOZlfY2oW36+3W9pN387J0XrqUbSgsK
LIAWRDJKFrJaFZNrpoQBDq5eE4u5pueZe2M7cI9N5tvOr9pydjn6a0oY5csc
/OFD4i1sD7PsKzrufg79eWlEsvXu+/fy/TB+//HjvcOeazlQYuoyeRoFtC0D
8NLzcDJK0vRcs57RwpOD593PO6dEuzGbEYO9Jc0kygBWaOkm8lpNcmK/CydZ
TZT2BSRUlNLb3r9PAhofP/IOsHlgUZOPHwd52JNgPNCW0PFfV/C5C9tv+zgX
HRssNSgnQvR00Vv5kAl6A0cmDXJZLIZES8SZm4osvpXafI4pEyH/oit1b2lw
bPRX0rFIGPwF4oGo8nQB+Rs01U8FaRFqJbV6smK98v17jkvwJjHxX1YN3Sg+
VESEq3/SXenYRM8j6V3M6sm7jPb8rBRP3+PRAZRVjHov0ktb0mqnxsKwfxpZ
EN7Aq+Lzyujc42jf+dFw/baOiMPuVbvC2iu+KMz+GzmryFHYkUxMbjHbjLJj
veK2g1Ph4MT64U8hPmKi0JtcJPKIi24GGYl/Ipcbesz4APP9hpczX/KfK1EW
sI08KaL0c71p/Fr6mq4BnSaTOPOAQdwSuw1GkhVIUJ/MlAqNbQVtRO8TBsuC
stKUxK1JNBSfk/wjJ/JV3Asrbas5h+GdjsBaQC5ifIEglykC/RpA1tEA8t0a
AN9be4/d3ZYoiA79zh0ys4g/4RU/1mw0v7/T8icfSWBjLYnsYyldLSZEwexf
mW2IDG7KINGIy11D9JGCXy/KYXtdrzK9XRC2LMlZjyh4q6+ZQM0UoD+0txDz
k/WK1TIh7/KXJbzpvG75HR1sS8rXKP9jXU1k3rjKxDUX7q4T+dFdJ+OlLOZ8
hiC/jI52uV5F5YF2dcaHdEY015jSI/u9LGsWjxBs9ULuWTEvoffHq8d/YxU0
p5FnBV3wIsfGgCQXetOiiCSFfJHR6cIhQdfyXZn6Hgb22lVBej07KYQkoXBd
lrf5NQnkhpQTIh6yE3DvW77T4ghhXtPWvKdeFxc5WMuY5SVdW5rmdVlM+QbJ
jmSQD3R7ihlt2HST05Gty6nKURbLZJpeLehesgSmhbfh0ImI8KNiShNrW+Vq
Ipp446+YqEYsfJ8ac2nMSDl0+ldgLyKrxDSBPRR0FqgqW2KwT1npN1A4CYe1
YVYsWJxe9GnUh24qg5zoQWX3QPjcwCTLjL8WsZxI6qgl6IC4aF+pXxcTC9zx
UHKVkByE9Qz66VZPidfeK6+cFVnh5umaRvkJKWRxN5jFtNAHczAKVhoXk40O
OquKi4p/J7u14HFE6M3p/CGPebughtOO0pVhdxC0D/poA1WvxNuDkkWiCSld
2BX2EdrKk00RiypuyqsvNMjo7d4kC8Yx6cZX21d5RJstSoVc17wsoKIol5Wb
QxMmjZDY8hp2OOu6bAKQHcscgvW2TXrcvBkcwKely7ZBEf8zzZEFJYkG2v/1
Mr8kASZKDX024XFpR6INqdvxrL4d2pk4tnsYrw5Ij9X1yWw9Feelu+iyJ8SO
JuVsplTLt761a6+8hI/R3kMnbAzJcyIltcAnhCGYuMRm4Z7qNjMLvK5n08B7
CrjZaJQbsOlE2u8gBl1kUCwO85ekn9MiB7SDU6i2qT+E16+HbvQAjwh/vtMn
IqaJ189nLLaFtoV3Z+bJq1YiiFuy48QQFF2HFhBmqZN/XSIBh3aeL7V6DnHq
y4LdWOYfEbZFXxXVjJREmg79az1f2p5f0m+SQ5UlizU0JdvzurghJViuXeFp
MRfOzAQQ10Wse71omNLBSEURsI1J9PdGJ63rifZAtJN4bYFhC2MSGqBLEa88
kwKUlRHHwBObLrqiikQnO0RaXcuBXbBzVsUGkavxJSVNK5w/vbjC/m7ZI5i6
c8dEk6cpSfc4FEUMJmV/jDhqaXoBSH37tZqZSRIxGfsVr6/yU0iZlTDfIoll
6VxV/bLftSUdNlMfqIo1KRaF+u0gD+kL6WCyY23we0+D3zvY6NjehVwwdlRA
KxHnEy/AXjGcmkdc6CZ5jS5Ks1Bon8lKu1KRxCrDrFq8Y4vXlFWOfJNl4byj
W6I0sTiwkRhb9NbUd6juQtEDLhuiJVa2SFdI9zXo2rAp2A5c5fD3k7hdw2Zr
n9BYy1m9genBm5yRYdliZ+Ylc6uqnas2gef5C/NaMeGv23Jbo2nFSDGesjGm
Wf5SNhPS4sSfJo+Fg+SRxatCGyM+OrxMtEvVx2EQJX657byR7P37mGTClp4T
JmDlcpONswzYEbVYRGbLGm7LMSc6GHXdzdqaVWkwRLYVxJB4TWpJ1ZSydc+I
sa9pnWJXviP1gLOr23zv+Zuz872B/Dd/8RJ/fn3yhzenr0+e8p/Pfjp69iz8
IdNfnP308s2zp/FP8cnjl8+fn7x4Kg/Tp3nyUbb3/OhPe7KSvZevOD/u6Nke
IoAJZ+JlkYp8UUbLj29Sm5HiO2mqC9nc749f/T//18EjIv7/RbNFP37Uv3C+
KP2F2bK8je1h/StrR3yEZdHgqGdsdyxJuDAlkuQhM4mUMVYkWE/+77wz/3CY
/+3FZHnw6O/0A15w8qHtWfIh9mz7k62HZRN7Pup5TdjN5PPOTqfzPfpT8nfb
d/fh3/52xjd2ePDtb/8uA/WcQ6izPrQhE3QV/0aGqFDsYXaYn++M6XzWR9tV
1PuiOuqlPXLBhWjZLTY0hN4/89GbCjMQeabqLviLk4jBFKSh2QV4WycqKwyv
rZBYdB8FZ1o9X9ZsYc04xte4GASbMpOinRQSKeuMT1wN7gua/XrJM6Lfkxav
TzCdd4Ibpklv66gJ8yBjSY/kc84h9luX046zWhR481IH33WvAZX3eKeM/cMi
ZH04+oF+nfsJRgAcUHmvAyp4n5iS4DddFhtOCUaADQdjXjYxtK+ZQDgjgoWL
+g3tODuroC195kk7eMhtP8S9XC2Wa7VmxBaEGZcQNM0jUmMBiiKOS0wlvSb8
bnoFXGAkhfNLstMT5zb9Hzt+uupbFz/evyJVPHlN+Qm9YLPbK/cEM9jkljqi
bj3aix9oNrwZR5+fPFRPtja9zsDmG4xgzswziaqBZL26sn/5ZMaZsok6iY8i
idDYKc/4TQvz3JSHeuR87Bau4Ignb6lISlZrp09AoFuOSI5h8i9x+0XphWHR
8aULgZAN3FawBXlz8ptixrspk5nyrePRbWfYrUP7woOPyJiWB1vz2/GisCNs
FehBXNCGILbE2tSF0GF1ta7XbbzyzkNzV0mlmt6T+bx5c/pUpgNFPl5m1v2Y
UG/JOCzBFuCEIQUubqsMwQrt8LKYwEWL5KKBcMQBPHW4fPSTG7Ym8SYxbOEJ
Ts5bTH5OMYE3it/euXLiFfFkwx6yYqf6mZt3bL2omIqdFW1+ltOF2l7pCfNP
doyp3npJuqimObKFOAabd58islPvdPLSaDMx2YS/4O4eJW9dmu+GV9gQGdDH
M1AxLAwu92Casfv8pGsc88rbNaktm+4gfCNwVnyi9qExMz7RQW7lEzhAXyHF
XlUiC5K8rHrOIsdjT26r5hdsHfrVPAhIemVUpIn06eqy09jHOZRXJavtLhJ7
FL51tGQWSoccBmELmKCMQGFy6+/NkS0m8WRl0atq9UQD5sTN+PiLmRJGeL3S
QrtG7vgAtzAQB5ZRtvwkYhG7bLJ7CFbdVKuylBuVEN5CJfG4wk+mY7G5oda+
fHXyQkyiKUtp0iXevHp6dH4ysHAlXw+e06Y0P32QrMfHJ6/O+dnXJ5wUrzZv
fPMQr1Xl4TjQlNGIn6PMh94+jrT3tpqOO2QfVA/mqhVvp9BlMpawxmXJPpP4
7ABerwZnNePkKs6pSfwlwlnq+p2oh7SW+KUUI12WTVBI4nc8Gb3QOzxHPRFQ
CyKwqdBhPpiHhdu7i2tLopHyl2Wlnml61vupmSjFQzaTQwdhRN+Tyld1K+BN
RKm3BZtnnRmaGp0oztFtcFFqaN+tk4NlRy6I23kB7FNjZyx/U3+++p7bWqQi
OzRubQzZfmRIsHgLXm16vAa7gGc6CiziLStda+J6w2DiCjeW85s2BOsT146q
BhK3L+fMWLpq10Aut+kBt2zGpfs1rVVLNfVMXepkK09Ws01UOOIoIL6fzs9f
jfI3i1n1jlM7sJsDeNzJHIg7Gifcih+e45s3pUuR4o3goFkjtDRX1ZulqX0C
rxOiCl3hMcFlaWEbOxrmMcH0+92sdr9TBww4usybV+kfULY5E9WpcxvqpnOC
nPo2KfmC0Vc6ojtMr4qC4Dh4xbFNCDZSgsJs2F+srkJ2ZqxhZyX+YpGG0SsU
5c8/Wexa/UJ0o2gqpHYotaRaTi6ehOWqBvN7udSEV7I8LliBg8qfSn3RzXq5
n+Tx0RkW7GRgeq4W8NOLAYecu4EIzipKo4El5N0WrTq5NalVjcCLDZ4ZyJgV
J6psbKvlZtoX14XuMgsmMe06jD+uV7k/aaLsY+PV/3xdIlKcOrA56LVKckVg
qKkfGIfNs57CcGvoF3iljAqerG/IzWkDnZdXCB1BLiETLqJcpAqENHUkQJyV
V3zAIjxJl1p4M0xVFTNp4FJHdIiEjwiuhCnINZ2VLmKWz8qiWaguyRu4FPGE
0AAtm+MAM3UatzIV3TjvWpDZxSymGRmrsxBmCwmkJp/x6NnJ+ZtXxpVx8eXX
mkwRLc3a5VzS8rEHrYbG/SRa847zA/6L6PwPz8Uw8Z38yKfHcDLnTVXeiodQ
Ysj+e+RTgKtJMJkzuP75n/85+9d/+d/+9V/+x3+e//3vNOP/mSdRiQDqkN/t
SQ9BldogH41G9/KcnqXn/89/70X8qv/937JiHOlWWtNhHoxHXpxzFeEh+UdW
/T/zJIz3K/75z75ruFPfbwfHsEemqagWFbct7Jo4qXBBLYbmf61pdJv/X+2b
lDe9Wl/cP1tfYJkvgn38mtRVVjj4UyQB5MfEvvmT/+yrRu7m/fzn8iIEbEnx
enaWH4weYrnP17/If6urJr1Gsup/+fdeyK/63/8BCfD+ML9zWV1xtTVLDCn2
+S9aMu1EyN5HMnxCgLRISngGfWHScjFpNppKQRLoYl3NkDeJTEyEA6eWiyQ5
UCKjLE2KVAPeZNWps18RO4UDrhvOXJBsJAHbSnQtBuSTONv7O1EXaNwXtPRn
PjWPlQqk9dHLJHcxTdPyz2q+WxYjGGKOxlzeOexfVg0l8Hrtc36KFjl77MuK
2abfxlxTDQizRjl3SVFRUUAijCWoHIq3Dp5S07q2zNFOTotkOAUDkT2b7WG+
RmbPwf5+PpegdNNNvkIOMn5VaFItZx/TLyeS5jDdkZjVm9FC+taMKYX9Kmwr
E/uF83wRnLPxxIvpVFKsWI8OhuxXxM7a6+CfPsyPLWRLpNExQvkT+J01eYv+
qhsKg6bj8IRa1dZM58FoLEPS0zSm7y+JQGi1SFhwSSnbGUnBhu3kHurq05wk
O0dRe2FdNDHVyHTsTk4ijWJZia8dpFb621VdSwaWBHPpxl6u4V+bkiKxLCWJ
vl3pm8R/oftbSu4WL5X2ebJuUBOFPf21eXq5oIRJdqkcyMV69i43B1LrcuWc
05r/GmOFA0tQgyLPW8VR4iC7Ozl7PO0fJE+ejMtFjFDaXpcIcXhzy85YUsiZ
7GEbiAeCi0yWIEd+njhcmvRGu805brLXuEo6cdRj5SHxTXeTpO+aJunSh9o1
Kf/sfnB5snOTUYNQUmL5myBivzedhCrUYX2Vn9GOS06wEqYRKu04vjJvbaeS
Qpg6XnIVq9dwaxLHg1n4bA3CNubt0qMAGRP3et3NzoyJI7zC6xVu/LwsVypE
POsdsWnM0Yzgl5JgUqQXC4slm5HcL7LumQFelNdVCBdGP65l+F6wX68trbaN
h57VqFCYvCuRf0u0mwnVSCTpqcXJOAVbrbuUCSH0y1YuKOiiRlRJhNgAHGZW
Xq4skuhy50XC/Xy9gRb3224p0K60MbBmZbkuF3CUv0SlWIjgwirlZ0IWt6/B
YjcbRtKsHJV1Cz4lTgBCseJnS097qmXgwVSeer9dX4hPIgspaXGw9+8VZozj
EqdCHK2QnyMOrlV8/36HuP9oUc4ohwPdSWorYgmx3EC8khL1gz8N2o45rjoi
+KWA2kgZIPJl+sQHav1YetAXvC5mJ2CQEIIsIOl+c30bezSt9MbqfODCE+9k
6sdUDsjExIRt545CKbpn4qQBhKIG9iSUyrSuTDPOQ5N8RS73CWLksK6Xzm1D
dG8TlzRfLQDBPs+r1YoX3NZdZUIdzJeqXq2VvdKtJXamKARBDvl14RLyXvXI
f0FyMpoShcToyvmTQQmL2oS3+mroA66OGPJgU6H6yENomccd11YYGU4Y3kM9
cCnoDcrCKD978/3Z8evT70/eEvkf//6Mt7Zw4cklq4kMs2budEmBUgkLp/Aa
Lh+1UUUF05I1fhQbzJykk8KDR8VjLNlVRihFzJYU1y+iynQbFuWM2IPUPGhw
S8iMefNizbo7ncE1ZwRZLi6qUZiF2sZoqE43x5Fnkd+WF9cIHrEGqRAZKEfB
dsPh3mzrUq90K5so3e9yaga9BHTtb889c96HCWw/JH5XGvoeMdyk/LxRtsPx
zqBPEVnclsDC0qAqvUovSiJW/Pq1ZodVNq4lsDqSIF1INbicsbAbcabtUK5k
SLTga1JzDstMhCCfa9iDeUFyn38xZMjXShy/wn8O7Q9aRVm16i2md3I+2QAb
Y8EUyTxHOqh6bzkQDj5CsoBuPbMIhv7iG8wXW3XEvFhpEF4CWMlFlVzQCzqE
22qqid3YRg4RrK77tceX225SMaXosIZkkLBmIGolfxAsD9ExoT0SzxiWl5fM
1juaZLGKUo13baAlICmzscMPYRHj6BCNpdOBg1TK8siyNQeNpletHKdDFowr
wZLgF8jJZAdSvIhJ0kxRKI3asMA9Y7ZcFIaBVcdXMgcDwcmOxHKXXt1a8lBY
rqmuNFBFGZn9RoSJwnxkyUGv3nz/7PTsp47W7C6bq7aLETm6K2LJ6iyJ75L2
o/6WIFukeNtXDMJ3f9HUxXRChIUTm7o64HgnRJgwS6fL5GYj4V31aUlhCY3C
t4q3f8gqOsKJTkGvYm1MqE7xlkB4KbThIOXUCPS6PE4LecnTHXp8flc0tIKr
8wdI5qBRf66GP1TIBSTWsp4VDXhavj98fX7uqiHS4nykRFSiqxSWZ2MxkU8G
LixmgWxGl1bKoZWcg8NyaFFcdd8m8dOyYnVAC1988obw48gUeQKllF3dlCGC
zmNozqkLOltClCSU0zBst4vcANth9ivHRDvcV0a0w+jRSie6a1P66sURqqwF
FWmQA/j3opjR4JblHYusAy2IOkEEx+y7HvJ/vb4QqHSjLARKFtsO0/y6oo1n
P9xEcjPIXFiyWJA3qwNNLa0oPFH+MpsBdnuGOPz1KPpw9bIUguQVgvXFkhW5
VR1SZYoOKhjxivbQMfMpmRJTZ8CZLlU38ZbzcYrdG6li1CF387GCwMEkrmuy
drOfwQLfPH3FZAS/IfOfwKE7lcgLVK0K73u+/oXUewapDTm/8XWOM0pignJm
X/qHYWheYqWcH3PITy46CliQKmm2B47KS7bLAroi3FRyx4IGRQ8OTMxMatG4
afSchf+wvhwikxtLBW8Jfgm68plZq0GSSBxwZ837+zvbEAtqDrbKXTwwRBd1
4VOACtmlFJJ7mATkKGhtkSTpsGYbDDQmLJwYKmClbJSka7fqSMxXi2fGNdT6
CZdSh7wJSSxNqkjlrNn06EshSsu9PdoEMRBfq8qL1xrVbpIK7rhUMEk+lpaw
uLyhXLD21XhOn8blTZCDpKgo1qK2TyQU3skcDCg7nCtyIkm2kgKDAp14L26L
TTfxRFJ5C3uDuBgzBtGRnDN4SjkXTXyON9VKfUfPTo7+eAKl4unJ8bOj1ydS
M86kzNkLWU+qRDedy7EJSVTgl5Hkxs9p7YOs4kwnyPaBKxaVvDlfYai4NODr
tndylRZcIhb3n6W4eELbAC8gJwZHnGaQ2RghgTfTV7qrPC+bK7N3Qu0zFybx
AO7AaU3TcoVq8IxVMShMcPyUUnCJxNL4gGYjuEx8uhbjpTgMx2S1rapZOIuy
BK9G2jzHXfKxVISORd5ccnYabec4YFtNx1tllf15umbU40QPY0Jj33v0I3Y7
0QfjpmSlF7+tm2ws8Fny4v6UxQ5JzsoCRVhBpbvYZAJfk5cLn2g44hu/VebB
+Yg9CQ2khOR3I+3d++Io9/cZ//tDjgRO/iOdVb7PGAKafnyUy2YM8u/1VKb2
7Ad5dvgX/PN3H+y9ehNp7LdMspu3q1r4k01o+x999m//kheH9yrNY70Hg7BI
v1z509Z7/23r/Qv+SZ4NEIguU9+JMf5/3179l1//D825EyntyCQLmmqJNfHZ
cyLXVyBXEct7H+Wum5Nt1SOExdhkGd+HgpT1lfI8SfK7FtOU56twcmIk61p7
gmKXipl6PkdatoqbDiN5kiFrLU3KLCcz1DLGEcWLWUzFqaeKDCvx0yxlEC2W
sSiv6lWF1DlWlOblSgtVdcnxQ0yBQUuWvqgz10iLi9CWVsb8JLcMMFfYa6hl
A6/reynL7w4g5vwajFQ2Td20vAT5Ez60am91cnWjdt06cTm1jAz62hCltvJl
Y6700H6HB4uEMzKRZ1vFRlCgVBs0QOigRhntOC3KARSt0MQgDWajlkIQv8by
BOeRh0KVG4GAzh+p4/3rxw/Y8d5RAVTwQXvJFOei1tuSlH6wR2SOWawXVnZm
Hupg4MlNd0VJEcLBEDTC4tg+KmMoNWRG6zm70PZATHsymUvzVxbeEmdHN5uI
4yjFx0iIXi8UzwVJC+zmFEVyY6szD1aS4q7uhnMUpCH13usTxB72t3YRRUcS
hakgL3PxurPZxNJdri5fIsuNrvs1+7BdhXjG+LfVYitnVhPeacn401icb7T7
QVEZOBWBZuE1EDyXFh9slym4Gh6nlMkTGMBzCn2+LVemcfZVtycpvmnct8i3
9Zw4/37NJg+aDeaDSoGyfVus5OxrSz0uLtp6tl6J35AnQZchf/jw4XeAthUX
n+AAsKfkZ4GZKyVmmIKgcOJuJ283bqsovOJURfGX7BEN8zZczrYzNdKnVxHN
bUg/GGATL6wEKSEx0Te69whlh1IBUmtSKhwcxBjFD6h4CXCqaNJFuNV8agLZ
plnYicFpy2mqqyvYtxCOMJSFC0khCzyRwVZD+B7rboMbideJgZDdJ77sANaJ
jiTBIkdIil6YIp/kER+Oxnk8epBgxIE7BW1Vb43wCd4y4rusfHbrX1RPdVtk
OdBMkcnJV4tYeaH4C9OamWH+/OhPeU1Xu++sQaRyxItQVBbrOuGq929hRw3i
yhF3RgZ19MHCmx1onD8lGBdJspbBQ22wJTALxKkqp7B454rG/NAt8VBxYylW
6oznGJNWnZiU1O3w1TCVoAoV4uIpLDDd3/k36iHFCvFeTK2TfaGFCgkErqSN
qTFHtwNzSysH2E1DgvqJqDpNSUtSXLMtksOpjmO9WjuWLCiMKq8xHJ/wqCKA
jLU0X497173WOI7wOuV0/M4ordVBMbZijLFnAH3XX9yYUQRb+G7kxoDFKjd0
uF6S4edFjcRkeAwYv5YGx0yDpFQo4pJsf2N0+hJW5srpPQ4GjFUed0YXx3nZ
aiVPqHvxKfuVVZH6d9wTlh4G6J21h6gDiAHkbLiZGvq8F8qJei+lziyurmrt
RgVOwNzzsJ/+P0X9GoNO6F8zEBTFFByUqV1Dj+GUAMBQaaVSUKB4z9WMHqUs
jBkPExRC+cZUlBEUwqM4HU/ZwUDs8aZvR0DPoVDwbVcx8HS9W0EQv7ZYo1sV
fszYAMsngYE2Vbd2Vx9mEfXyF0TjoXEDsYTW+Luzly/0homL4c+M3P+eRtwL
q9s7zPe+/nq//PbR/v6wfPDdxfDRwfTRsPjm4PHw0aPHj7/++hF9s7+/xyS9
F7U8em4fHyW7sWfdJ4eFPAClhT9VrUs+9UydvvzvsG/f+4+7Y7mRZA/3Pg4+
89RF8pRqTWTM5vk/YBJRHeLvFb5/+ODh+cGDw/19+t/f72UfYT1jk736pMVa
0CxUa+0qHVIqy0cjdvc0c4WafUT2qcFupe42UzWmR1HJDQqswxTtAsB4uVtc
EH3dG2wz576Xsw2MLJeFeNCznVfAPZ3haVp4+G1EjeQ32h0F6vyiWDIyaA5c
GzXhNIgiGN+yzYMsKv1pxi80BPEVYK6fc/B1OYTi6ah536lCk12WSuHM5vqE
+U2sx029CWZ2mBN2qzgYL4wAQKvtel4RgVqireq93vIAAKbyx1XwbxfQdzU2
lNIj9jcLZkYq2JWkC6fwBUUg60r4gUL195hoMtu2gwXTRLgeHhW4Fa0mj4dj
4MpStiAEccnNjqn7gjaN5+fjeqP89wux9IstRRDqbsbTvGoKINgjYqgKdPLr
rnvXMW6bm7g8ytw6daG4mhGxQjNKy158FhHWSdBppTsjGFp47v2d6JNKvOhR
mAKo9bopjbiDg7j7DxQe5zP2QKX5/r2eJ/q8kp/652b3L/4m8Y7+TeeH6pv9
G/ab0l9pok9PX/yY9/peu8/a7LZf8sVL+ND3ny989m+Sl32wpaiLQsuFPuTn
J6+fn76gbz67ifh5jIj8JsSu6GMkRpBk2HzJKDc7Pv7iQ9r5lR2BIj7kr0/+
+PL38fiOjhlZGAtJPOJxE55+6iS6swhP4eu7iAJxvOOLDlP+Cfu2YyH9+/A3
2Q5/uEoR9YarC/IMfPg5asRQRaRajIdpUlmCeO42zgQAdeoQCkPiNcJhJAqz
TBg8SnkRVGoFyKjv14Ou/9SwODh/m03F6GaxnSmdAIKTVFK80FGmssJgpW0x
muTQaWJxtB1Lda/zy1WUn6jqwNPD1dYhxW4kWKAqKEnn5rOnV77sCxsX6AQA
jbfS9NQOgfLEIzXBiiymN8iX6YQ5L9jOLUd69QYKVDLIfvfy9MVbRtE7OTvX
oDH22oLGLLssur0r4MBbqRHYUZLUyZA0ztZpDYZTnPpm+kQ4iADUcZR64j04
BDKDU1hxyWlRLNlBRERzA1u9hbhuX6Vh/UkEwXP+XgSpO9CHnYBAR3Sqdysc
rjScmoYckpli4XYndJi7FLWe6Ko2B4l0mXjef+5RfO1kCj1RcaXQyKQUVCvD
+YXbadso48SJXIEQLTEoEJkQcDYrVxGtL9QdGWKPmwkqQ7aCwM506/R/uijZ
DI4nEtWCy/VCYQ2TkrrHo4PRA9fCgQiQffLmixdUnwQvGV/Ea6MgMhJFSDZM
Uy+2Jp+frdul9BbIUFXHTC6s4TC6pBTftQ35khUnotGnVT1tLUE964NItMwU
nyS1ZH6Qu+ZEyKsdZa9DsiAv+Oyc1hRvtGTVKI33pgtl3lf77OWPb3mEN2f2
aPTMtAJ7oQUZWq/GCBjGpYNbUvMoJGE8ovUpM+H8Y2XADKAzXUdIAEV+k9+E
7h6Jv4SWeHz04vjkWbbtOQyQuC45KsbDtqmNNMsPUTklCXsmuOcf8h8j5/yQ
nwhs+IeMpX/yf36cldAPpurO8PQ+fwBdHsUvSYhTarZMx25N3BFv59FUM/rg
WZQAv4hQpHGVRX1AP8/lqk0Tf4SIQ9QVnqm6JRmD4YXrf9nwr0utdvny4VWc
dnaDO71iPKTzfB7Iid/hgkkY2Yspnn5To7y26076kD9Dp938HVlGMtI+Xq0C
jMPaknuOvKk8wBrbzeZ3CQdI98hvzDPw0YQHd3QEvm7NdHulRYvaL3mNSdjd
L3oq0XlNEANpqohxqDJB7agvuLLCsiAvDW8FxivGQSREqADKw65jYm9BuxVS
3AUlL0NGJaR/1JPFNN0xfujs5MfnJy/Ou4/EDSANlGFa68ZYsaoOXXAYjCZc
ge9F2p0gvTPtu1hs21obFclGaPltFrJyG06m9wxYhQstcu5yHff6t0fHv//M
FOgeAHy241QvdATdGs/FP0EirxPVrKu9aCj8qlimye/sOwhv+cT2rzXQU8QU
vq77Sq9MEBtfuPggMmYO1VMRyaUFjkV3mlLqCzuSQd578vr1y9dfvN+oXndg
IOpY1HjW1KCdNjw220houzK0dI56GQykbb8Gm0d37txJzulMjKr3d3qy6rLs
JOKOkmKZhst9hp8ls6bA9xwESHXaDgtqS+QaDMxNhZBIaj3AOwjxJcWeqjOC
kqQHiXO8fBYmUX52d1taLGIykefiu9wzu5wyW1b+lm2vwi3mUnzONmaLOiYE
9mbFsflv7tSeuX3WP/PZOXxm1UEjCKv6i7dHxJrfnS/YnphAuHN7cqln7lvE
/wfbI6T8F25K34rVW/4Fy+n6UravecBk6XIF71XZBVH6maQW7Q1lMYNMMD1D
VEGTr4tVbNaylYRI5qvpQ6xMX0GSCDQLivbrppwOg8okX6ilOmR/cGsB/Ygf
yONY95lh4bcEvwUqnfRwEWs6SSccCQ89jp5Gv3HHGnd4fye6Ij/u8Jw4yNCO
f74nsT9LUvh1QYJaEAt8+qzrleSFrmcr1IqDlSoGOyoSt3xa6Msi95mHVYZl
+ftBmY5eAu/bNmBYDq67VOPxYUdDt0wAIhbj96nSHjPHrB2xCiBN1BxzSMXc
OUfQIdK5IPFIHQzerSsLcSUYSDTQOI4Sr9KytADYigQ3ZnM4E0PnatmFSdjl
idacJbk75QLUP22KWy/NJE9OrokaKrWU94nC21HW+awSqyOBqUm04y3hC4Fn
kXolLPr4YhOARbolEuFHIYrG4TAgurqUNyhxl2sB9JaHRQMaL2uyoTfDuL+B
0oKrL09dfUyAIhLUDSe9tpP6ChAbfTBvy9lNuV0fYlSgLgG+CbHkQp5WB1Lf
mrd0SlcS4lyX6MMUL/JFyRqzo6u+wG+sRREtkn3E5usVpfhzHmflRdEPIIzh
JWd582Le3/ElIVnWVa34x9Eois2ROotTN49thVUWafZH8LI0ZjvHqwVnqADK
b1e9SL9k4iSaxGNszzna4pTMbIizYi6+pfyKf+WrLg0gRkiWZ4VurnGCwwBI
4l7Kq+UH6Dgk8sweraT+6hKtoS8vpRd7yGM9inuBFwqhS5qvzcQp9ogHJ0m5
XBCMimyUXsOzKJ4C/6uVCzjE28V3EPVAQ5c/DPyCS39GbQlLyY13BReQeyUO
X5p5lgCbQR/Hle0hbU5q99l2YbOqxaVyYgjkWNok+7Pc4RIJbIthywWBwMcs
2lpxwhJe5xsW9+4T+1fEXJNk5zQX1XWI1WNKRi9aqa+SjnFmi1ttlkE2uTg0
70NfyRbnQan3UKGqpW7LsvG5mkx7IEiYPPw6aavmMiGWJXBpaYKMVyH9AhV6
LgkaJEZdu6s48xMFFxdaaa6sFZEc6yn5RdUYWhdmso3holWIiCj9RKzGWCEy
q4IqpQUIqQ37NDqaOoasBzZGf+gicmgp9i40X8BUKO3La+0sUnHbZkxSKEiG
NJH0Hq5JfM6N9SwNFe5do06DoUEuH5KRUzBjyXfhNEQWq1rgbvUqrWWWXzQ0
P/v+CW2jzhrwLctrlKlyKTZR1rtWSuEFU8NiH9r5wGDan+AkJqgHEs0LDn7F
KmD9mdkEgxsxmkD+fXnJiBBp9g2ArtrMpVdIo4qGeQw7rUgEMt7fFWI1EoMw
vwl9DTJghptp3AxFIKeuc6mWfYYj4pLH+nJ1S6/9LUNCIKGKlFDcZMHOdsjX
nLBXmceAXsiP/ESn1xK1oR/yrQDkJNDaA4+tjSf0R7yqqULV6cZJnwz66Lq4
KR34jDU0mf5W1sMI0qU0LTOE7NIevSiaK9IYf8uQ23TpK1Pm2cJin5tK1FkB
Rrbg9ki+LaDMhGWpwnuHrotpg0H032AXvyafskCTkxjtAD53snfen0UUEryz
bbw6iJng0bFD56mBJ+MGXfGuyTVacDj1k74mzhSNyoABsSMOpylKrHBlapMg
LQdtDhRQIDFeEaccOBJLUNGylCeJOqk9ExQeZcD6XSFaQU9uGXt8M+GdWnHq
oo6yIW3IDexEZqN7nAOIqMX+kD+XvC+O/CDS+iH/I5oKdWI99MsxF0yPOfHl
uhtzGF+v58UCJSnMEvgPDH2I/1q3hrIRW174gtryyjHG8GWyQtu+pd/2v+Sl
9I5atuV6Wi82c+ky0bpEOAwid/ItIB/6B3p9RPZCkkj2lqRpUXEanFSCPfzu
8cePhwn6fbjq9hZciR3b8X4vXJ69w5zOdC8KYf7g4/hJjr4XYySnSTWPGDbm
5TADbqF7o/j2O17o0PHFznTo+OMUHl+GE/WhnL61Q+0p9/+QP9M0fVoQ/44z
ai82/G8Sznu8iPHFZmw1MUJfnSxNWhf9VhLuQcBTzVvXJjdEsxWHTe9h1tDw
Gv4NJikj0iTdbn9unnHj013vTH0gUH89zVasiELUFPVB+/wLLx0hF4V2W+Ka
HBb5kkkCxCROiUVZjd0tVjQ3uww89XE3OEFPs57MadOj0egf6BnVv+0TXtsi
gJFyeWAlaGaCkKanz6sT0iey236J6o/I7tV8U4vWiWkhGZw5twByHlUMrp6z
rUFfdbc6uNgk6T/lVjFQeXeHM+5eEqTw0qXH6ejUOHY5amBxaty+J82J+Ieh
HHOl6AXt1jz6pdLJioVAinRIGmKgPbRAw0rtY5Y93b0fdWM3WS7tE65LtVQA
/FCwKG9XyVHEIF2C2attIqu209mjG9Z7V26GqH+wcj5XvoTvYjvlHYnTyPLG
FnUSgax4iawAhC3p0OZAmcKjpGU0pEM0Xb8i2u8sN5wNpjffn4+T4ba1vaUU
09LCPsydoiaR92DfGr6H9qdjeeqgPqw4ShBiqlasaEgFC0Zth4npdKu5KnOB
WdwV4Rkqu/oldCyp4nDoelWr5nu3w67ZTnEMhzcnUT5TtsaqaEIII3atEwMS
rswJ/sSTuezqSgBW4OLzD3DJACfvNcK+QyY6lsqEhSxH3mHaYCQX4gk/hEq1
oDzyG1PdGDl0cQSnXWomfpDzRI5jYZljAVeVNoghLKjNE45sg0jH4R8L1lS7
kobhVbEoiLIPfRo81z7R0/33YvtWSNA6Ph6RVuUOBdR3sWGk4n48qeZTFFnt
eA3uPaJcduXxU6v6yF9yV+f8WMDBTp/y4qR55lPDyX3//vj0+dOPH5/EKjR+
Iw1CTLZaaOwB8GQS11fd2yKc8linQgS2YkjgD8VtT3CsbNMhIDKWlXdjJOZ9
S6F45Tjo48t1g6/lUFsP3yhVoCijJ9JhY3QD4hfhKD2E1Nb3NN+HyexkOPAK
I9WSaAAKMtucUioL/1sb2f1YO+bSjkShOo4++tiPS+NeYBLpPeQlCxIbMcsL
wOfaOgZbra76FpB7FGaFdoNFFltxofurgFNri0Ckhg63m7Rzhqki8glTNY1o
y2HAzireHt+cVys1E8+BrzHrqcpaDr+ZHJR9pVy0eaJeWu0WNCG1BfjD9fDR
5XeoKNtLGCGrPO+3HyWliv6KuQkS495HLvnaCxxTnhMl7JDHVKbU//BgK7Zq
Chv9MN7+vt/52rKD4cHD84P9w/0HhwcHf69TUrUc048au6400RP4J99dPLh8
TJs43J8+KoaPym8vhsU3k4fDry8Ppg/Kh8Wji8eTPa1ZYz/W0zgEO68sC6ob
cVWStXSLJLXK9/oydVx8d8FZB1pQlWQUVZ3Wo+8GZ+Mgp/9em0u4yKTdacdV
d1nNUKYUbeHOD/h2EIEYvIZMBR5L9OL1VGmpHXjWdaRtr+v1LDS6BSgou5VC
k0F5YXoTJr7NWTA0tP2nPJRtPVRFm2GU/+z2ahATvucyOis1UBC20ubYa9Pm
itWBfOit7qzIZVallfSfDHGVxUa8d111UtOPvTIaSsBIqvlDXGgJqd75hRWg
tWUWlLPsZUo3zJdF4xk4q37QMc4H0YwWQgtGrrh2ETp0KZNBcSV5eVPV63a2
MTttKjoAi4ZgK4ylR5qVmu8C3RB7xuVFXvs2CDJYu9sI4Vf6xMPOW3sK3Mdq
+rIKtGNWKCAXlH+By2WzMdUBB97k1O1LdpNH0LJkBliDFX432OCJtW0Qa152
iSKl1gUNjKD+NLjtU7f+QOpPtwUxD8EGPkKU1ZZ1HdXuTxnYkK21c/46Nylv
f3Ra6ubLl/Ei6yoiHoQ13xP6PjpVJjbm2t67snIuXLkHP5Y6LHaCtoiGDbtj
Vd+zvR9DqOqzYrUQF+egXuwDO9M25htzPWgywuqeNpS3NNrbzkp4T609sKyE
pwC89HZV19O0uiCthwh2vC//2RF3PtU+hRbbrVjIH4ycbZxm5apXgDuxdjJI
sUqpfYGSsm0HAyEqezBCgSxbjeK+dU5LG1SuD43avRIY198KpvItJ5IdNruu
JMfAzZWtcR4myDp9ivYmCUN3rT5efbh/PIBb3vZpaMUzPIqMFj+bwUYoY9WR
afuiImWJPadIuXTcgBufFQJm4oJ4l+I/dnNgj69x5IJkcNUqGpJyXE2RiX5N
san4J+aXRCl1dEt2q2bnDPqiojRXUXob7tlA7i0c6eBoJNdXzMM1v6i2WTux
6uGocfkhJtnoyrpQNV4hAJmrMrXpAYXQF2n5vFeRXMS7J59EQoPaWvT9HfOo
ZhnicyLsLUqHtmG+aXJpggZVXUizEiPjkNXo9cbr20iIIKY4ix/q8Uxoj+t5
97eZGif6GWwMjfZW7XLNubF0kROsmEEsXRJFCJXS0l0GVgZiayHOnYeIQ7TC
tZQtqlHsLckMKyUoZD5wEVGeoY0oxtg8NmyVoqqE2oWM2LIyvNYI/MHEWk2l
qqdSyfCpyJHB9iDMw+4oOKtx0C5+FFQ5rR9ABA5tclb1bPoF3WVjb9lRV9We
WkEDtlIH8gr0YZYk+zDrRAgeSQ36e+SUef9+dQm9THlFvuuNQUvwsQJe4y1x
A05F2MJZDe6xBg2EFbtKNkxC+zqleVksYqP7KMxvQ4PfBr0Xy9j8Gqjb7J+P
lVBiBZfNsBAvGJ1XU99If9+IPzC0jxVqiC/4mm8Vz/w3bYfrddYbmKTlwvB+
BZExCK9sB1YwIGUsXWuetVDsg+a3MTTI1mnDyQFW648bSfi09rrie+2Q8UVL
KhaClo0M2jUTF49OKsK6WahoLcDDYPnr/U7lS7adyS4pAkgkcNujtWVye8EV
K0HrDPUyuE7bNwkoXK31eTeoRvCPaXYhAX33csnUla+fBLCkDnqcFlxyOUrG
P7WKNWlzXRLFBVZzxdcBefXK5l2jLrvknNTje0Qr2a5qzYA0Qmwt0S0mv0bP
4ZvlVcOK3fs7mhvMR9yRJ8hN6QslWYl2x9Fp+NWi3MJy4z8LNJPXBAVBJjgY
rFOSkCQvzwedFBffHLpCEkm7ct2AWSVpMCDpDMvCXZzW8dqKw4kPQLTBWZ4k
YpClKTlPfskgdGFsMhfZZl99YekxG/N4cnJBCkNSxxTVDrKotxCUWT4xizuk
CKPcYsu1LpuqnmUJ6QzCRhboKOS3EsrqKH9Ru/aJCLMTqxIIm+7YmbEA7hJR
XfHrZQ8upf4jJuZZfm+SvZqRKdauLy85R4PxjpwGy0xAwEFFk5JMFwNxJfWk
aAWR+0lHbvpgJhtn1WwGYlwrRVvehJ+Ffjfk688p6uMt1AEHX7ZKUiexXL1J
ZyGuF7Lr6QL1mc/9aVOmMEHWWyJk0DtSWGDmdtbWHhYzKwRx2lEPyVkkz3T/
WFMAf2GQO8URd3g6TTRC2fBkZC5tqxAEIXQnJgWf15fFTJIQBZXZdrHAeorO
R5xNCWLyx8g8hH0JCrQQU6kNxCe6O5z/hpmDZi3G4Kxj/N0tFLEojCx5zSCz
OL0gNNZJ+1zREFV/H8+LX94miTWDmO3KEhdMu4pO73xBO5VmpOpifrOdaA2z
MYaWdfU+aVxv7ZHLB+k5uEyUXmJBhjhQuE5WrKwG4k38GyKzRBFlpqO6MwxV
JJEr7f+Ou2Eec9iDSD4Ng3S1gz62j+sac5GM98TuDlm3rxUyEAJYwKuz8xeD
2OewkIYD9o46sOIs8eNLD0+eJZfuk0rfrKQ93ED7IQ3XFvJPHJ0BepEYlnhm
fEVx14FpGAn04E25kUgTyJBW0L1JLicLwaW3CC7hiojbhiZTSUMVP5FYduBu
ih5w78EaHnPCOet4ztgUSebjNU6d2Fh4V0MmDg5xLFhs0oXFLPEO07bW0Bhc
DNRpKeBgsDVCar65jjj+by1NQpugrdA5O9ozSHeQFt35+RLoHhBNhqfQvfTy
QPj1khtmBlSsuIkCYWtZzchUjQTKcFssxMt5XFcmtaZ0QaDo5lrd0tZI9vU2
Qr0oTcE2sAfQM/fKy6zzTX8EUTtkG864SAHNTWUIl/PnP+i9fK0lWfQSnxby
/s6OWq0s0xrxyoMxDpOWLPC6+ETxnnqOrMevNpDaVP5mVTRXZT+IHLNUK3UT
b365MFPkSwvTOwynyZIutnokiC22WrcB+1Oy8bksXBtypljnv2mjXl67ZYzs
USkPT1oQtsFTKXCEJk5s7h7RJcu742oDAqlL9EuKMy2kpZn1jCw7HaDIrrnm
SFOSbRrdZgi1xmqVSlt3beHoVStjN+bP6YVyFG+5e1MELAbsdOWhVF2by07X
qhVXXLMVXc5m2SdQVUcg70kwebcSlByYnksbLQKiTEAw78tl6M9kSLD6X8XG
BwGuP5bTcb6VwsHE3yF1PbZOMHXGF+FFfQYl15mVc5k3mu9EIjT6Ww9oDq+5
a7LrhHfpBZ+uJ1ZeYEn1vIOdzhxK9klHgdVmyfDyZ1Fq5neR1sFUs5Ybj+zG
2HWVkySI0zHzqlblPR6McXHeaj9MGu158Us1X88FLsdGyb1h7WsRAyySL/jk
UbdUsjiytHnqBMY6xYWAz+9LfDhEM1yfX9iNkMRkh3SQ0HiYgXNjD8TQbIu1
/ktAqd89enA0yJ8fvxrk5WoyumeY/HzZ7HRpkGPiuY2201QYA0mGly62y2LD
3eZatCDk5AhrQji++qdqOWazSVIxxIPFtjOTkdqcQyvrCvjFNAk+wgV9/xbM
lCS6Py/9COln0sATGd1i2NiTHBVDO9o25DYl9UqhPUiaGw8OICPoVBwO66RY
sud9zAkxmsDWcyTsI+/CC1eXDqAVqmXAbt2JPIx9IOJvSt7lCu0knhM18x6E
7qNh/Ze1qc7JSuE6k74dhs+sKd1j6xw31qxV1Q8suB5cK5sSzf4MS6OLkYEW
A+tmSYwaHSACQni3FFSUXheM5yav1wZJr1E3wcOvrYQl4e5BKw/NbbV1FhuT
gp5dsjnSaJaNVr/wBC+Ktmo/OT2diYvGqttbYdEAms85ryD9OQNJA06XS1ZC
ChNy4o7l4/x7fmfIh4sY0/TdEPPhzcte7WTXcOForTZ4Jk6Axf5hT4Wk/LRs
Y3wwgmhUVmlt6UdwygVvtFWm1qlDR3uKicJtcsF8JbxaeZMUFyr3afs8N2Zz
yYC+BB22XWagGiOtCWJbfIjBfbufSAA7EsU0JtzHB8UWDySsWwStBBmkrEWV
wVDJbTNRPenbbxYqGTpp1OJnoBFGCpclncAXtYvw9c+5Eoz6Pytejm5AS+Za
0SRr354/zDfxsBdiYTCJ9XkIUsE36OOu95Cp54tm1aU+6vIgmfJc+FDorZFO
jasdOQioY4SxXVCgWo0845CoidzSoBzEuzDaonfoxwHBwdBjnZ0QC8XDhWDq
cLqPnatLtUc1wkLDQXatizRer+gRcsdfyfwxktx3Bo7wdxxJgLFbLfO3boqf
lslpBxPxvjPusQRavTNbHGYhMqmOz+aKlEgRn9ymcnFR/yK+HbI7qmUlkXVx
yWUSbfIJ2OXiigthVe/h6IXJdca6Vwf+dODTRjJJ5jT3us6DoRNmeac4Mp5w
y+GJW+/Z4A2sNO45SChAf/tpjrzFj5lakfw11tHfih9+LDmaTA8twi24y9y5
GTWUukUhoh/YuoRFNe4hNrx4zZkrcFKMzlZdYIsyZG0pPR1yqpQz0MZWAhHf
SuesLaz0tW3o/8ax2Mj0XKMMAA24ys/YZjsbm2do6I3U8F7dytCr1abxG1/h
Jf4RDkFc1cLI/FheDluonK8/hwdTHBM+Xk5qIj1HhATPDzeYvhn7ahAlBPH9
px2EEEK3tATvNZLMnZ7pV5Y4snFTbRqFCYBCYepDzWI9VLmCU3GVLSbKluNs
WF/MqqsinN2z4lZCllfrmfkCNCjhKNXo0W2Em4qIF7aFiMAuyxXnLME9J7uD
zJAtOklWGGtZe2nG+BYKKWRKA95LeOj5fnuS5LcimNUhEZQdIDgGIj9MTrXi
PKgW9a6h5BZXtq15vJ1MPUlXkmKHCNibEGSG5IVWUxeO3IWJeZbp1ZJB6kvi
XLtuwVYCn+b+W9Bd3Y7IC1OVhYSBRef0pYGAkfi0RSVoXqADsV9KWkjfltXV
tdY5BWSSsBPex9lpj+rr36VEKN2JLtMSh0mGPXe5gBNukdHMYxatZiHS8cbT
4vXIYWmhSEAO0uZAzEDHuYTDojK2XtyivHKoU5AcpkUt6FTTYRg/YcIioFTs
mtsg2ZZMX8S8ka6TRarpDU+iMobFCamiUATnISSLTAmHyxDaCqCQY62McJP/
ed1U7bSaOOmunpRn5goO/hZzDpNU974Iy0gStsVea9/IpLf4OldnY2ZZm0Du
Jtp7FjwYYVhp7eWHtKaUHCbMtN9OgvornnCHka0tgzshqejUyOSmAeY51ReR
FF2uwh112OhI2MF7L5WwMnbADAx0OGgSEWs1bzU0VKQFeVthhp3Q0PCJnVmH
z5+tw+eJeLWf6p69v6MNPrNMITvF0weT31JhFCYpNf87uJtPHPQ5zkwA8dmX
KcUfDvE59OBUOocGwa6wNGwsdXkpNmd6OVTJ9IjEpFf6iSHQFYNw8PvaeUfM
bLa6NSWBFb/WgG8L4JgzaPj6Ai02hJdAlMkWGWYpt6ij145STIwEK5mxmT11
J+jHSSkCZ68h9MCBsICtvippN7j+NwMckQejVkmNCOi1gg/947pcS87oqjRU
LDSO1wczCRhKhAb+zsmqmY0VlYat0abi0OqM90+K38Kpo2XvkDvOyyko6XS7
+u24zuFn3QbVp+xu0WJ5dbiSBoscBf6Z33BSGSPGNxKtJTrodtRpGgomO4jA
mWNx53MqJZ8tKQoYhZR0eYsIWQXDiWpWtdjyw6vzXY2m3e537j3kglmKU5RU
hIRas1AYgiPS3ZV2PLw75u8dS84ArEtPamqZI5bBwP63O3rqCYQGZzgjgCw0
bp0AFESIWadGnNWi59+KR7AN0G4sEWROW9uYHoFw+bAXnIp7JSYWlifoR3oi
yGELO2W5VLobhvQCq7rHeSt50FlyA28BT1Ij84+R4KO2+fz4FScrcWBbxmnv
65PldJwRJzh6cJSPhdGc0yaNo0Xv3g00ENaSFojJ6ZmMDCKdVY1pOV/W0nC7
6FABAM9mJM2nSJ+EVyUAESvyLuSPJDAZR4R2lt4rRU7qoCadJFDx4tkt8K32
0EvzcCKE8oDTJYQflVkw3fT92tIYraS5ziXeVP3ILGYNSDLMjriLJT6ZPHJN
rMu2IPwgNrDl6hFSVflO9r5KNWzeFS2ozGF2m7uq0JYFwM6o3wliAOToFC1N
8aaqkTdU4sHefseFmlsTg9/CWBNXwsU2V2fU9QIg6DpgOAXXJpOlo3M46Gul
mkXaw/pI3cDmE7gvwK6RAzhrzTLELpeLtgiqf1pAlY1NcYbLSsq0iIUC3GQc
akTG5jYvVun0ER9hZCTB73H5RLIzE5eQjVPzVrHmjcIpzcG+SoUUb4UWkKgZ
i/3XljHhWhpdBegjEq+N1rBJUbF+bhjlu7J2Myhz4ZrRLYGq3eXyd5X1KnMS
O0D5MFfaZP08XRZsg5jMFUPKHRzHoLPQufM65D1yFMT/DjZruZUb7cM0UFFF
fVHIcWsXOwkdAHPVWtmGawMrUfAUJHxkl8VN3aCAopjXsPpl0tEZWIWI/TQg
W8PdkrnbPYi8YdB7jQedKzfIwmV5kvv2cVvu8uADFMjWGJHMdHWSjN2q+SVj
+lbhq7rxYO/8aINBMs0p9rcxkSS48ur+LFiXlwsLAEjIVsB5a34SorquwDPc
dr68ZwasboCKdoMVaj2J/f/GnRXgOwQpaJAV3SI/Tf+xB3mX9UnzAIR6vKzb
4TblGiM3Smg5HeaTKOwuN8x8rsJKZsVFOVPxmzAQ9IQsZwJGtZXhEOJF8bj6
kJOfCPEV7I1oy6Rhb+wGyVqXvaCXfCpLbsxk6wLBiJFx7hrWwI4S++b9HW/X
ZM4Icv2kvlLgXtflxp+4g9BUv2nE6LSq4jxxhSvOrO6E6xbPrTs0eBTRFX1z
OBg10mnAuREtV6jdLCakV5mXHJGv2D/r2rLXWP0w4m99N6Ju0QZwTorZWmu6
AyPCwXpLXXPSfGNwwHVqRnTeQaBN8t53WcA+RaHTBQzVDSJR6VoL8mW7nktO
Vl8HIK9baWgi6XKGaD76nMWeSpLqJQau9V9k19MzSXrndC8xZEk1w3k2O3sj
iBUKEq5Cs3fJwVpwFgzfYpaPklfMZpWZ7j3YD+KGOnSVG5pizZldzossq2Vx
yIpV8JxpCd7IUzOyTqXaVJ1hLmdSHWLWwkhdapb5ouaBs/Wz2J1eOJYDc9iT
wfYOc7QOZvK+qpuNICdIBbG09RWnGLAeYNfLp5z89lYiBG9TPIQH++f731mv
XR2BmDZJKP7V9Wq1bA/v30c1/0jzNu5rxUsbGwm3iubA7A7vribv1kuGcvAz
DcKxC9OwZ4yX5CD98JLkQPkx/Y0bXE6vO3iyDbvHXjXr8qM0H1YAQZ76XnFw
8WDycPpoOBqN9v5BmyqbEiU/eXx5MNkvvyvkJ9aWmDV6nQXpuJwtcPr65Oko
fynRnlQhcDn9Y5svKmZNP4hgffpdPpYroHW0xQWdQ71QaO2xHDanLbw6P335
4ugZ35QUiEf8MnId6T+oVOjkHCgKj4uf0xxn1ZVoJaz4tYIVPLxsirX2883z
HheuTopGfgsVLJkZVFzmQcqeYn5v9OrnvpaR/U4w8nRYIcvOat+8PmWfTc9g
0q2MHlmXKkkE3dGp4gtpBKzVBsBPtERtvDO9NsmbfxAkpXBOAf9b77XgK7eS
RqkqzcKDanLNcVFtJWkHfkvXdxYswHb73ZFivJuQSC4oyVYFH+v/kE0nypnT
48zAMOVHLU+9HlE1stuQzOXUVeGzSrniggdBTgrxG3VHhwF2GyXSRjkeJagW
lbrAI9KdwwovmSe/K8ulwpFjthxdsjhE1amND3lFgi6002WXServRbmprYBl
mWJz00YVi4Dkul10loUClwhelseA1ad2hn9YrRA9NsD8KGOciN+2d5OAtgHQ
wa2V3gquvUOo2gCf9FFxZ6SX9wuurNtIGUd7IVgkOdxfzjuxcKTSlAQjxui8
OueGmp0fheglUjM4IGCPWFqbECocp4fBKB0ofLtYngqiJdnMFcLwwktlhmC/
UiG22VK/ofApJgG/iWyHt5IbKu0uSZYMUmEubRE6W2vRV4Y1Q0XIzJx/T1yZ
HVYqvQmhaHSw37fCaEQiqlGxK25j6do+dSAaJgpY06YNx0cZsnLVGcPxNc3c
/NJCSt+wxXJ8Ub4u8FfbcIexdvlJklwhAYorUuoM7hGpcaJxSURHO60N8qfB
XNJgziComaoZxyYtwbQaspPgo/VFb9az0u1b4tAOQSnBZ/aJuVyiyR7itiw7
zd8GMRinDYh9kgIcFNHKA7yQlUj6vNLezHLud+NSTgcObqzN4ow7TWd2Zo1a
faC1v31/JywDyYYC7hAc8Zz8UDEmEoygWhRjqRzY2p9DXvI0U+uc8yGRRGwg
rxvN0ahn4pC7vBzSDgwVKKZdFgJvlmlapsEtXHOBrrDowkrgrq0LPBHtdSXe
O0l5oiPK1LDdgmF3kUn2hd9UbXUBiACJLqDfRE3UWV9VZWt11xYR1YRUjVNY
C0CfAiWzD3BbZrfurFAwAE1jSgLzxSGVhOiKprRV80hcDCnAdGXExAxBhRCp
GGQWiws7pnMWUcjqQbmYWj2ztg/q5IwyX1gvBGrFVgyupD0TxYs21q/GikXF
G6zOcfmCPRIcqXrz5vRpDn8XHdwjcFSgoRwy429RYxMynSBaJLqHgEBkcAhl
pQALLqBhZMZBfMWeSegsgA4zvRlCKkjHei4JNnboC63uClHFaGWQNNhA8YTS
Jo6jpz7m+J9fd5iHr/RJz0MjTqW0+3FunK767I3gtOYpxjrTHhisJ8DXVM/g
ZoBoS6YlrQta0/pMe4KAjo7wOBOg1MuqNR/IqEoeFZsixqo7zvWIv7Sqkwq0
wCGQuKU/GuRpzRtp1bUiOYQdy7YQM+KS+oDmUWU7YR8X2VXEVorMOoC6RGZD
b64Q+kw6XTEniRDqPpeHW1xaLxPDvyJ7JqbO2x26BrwSvMcry+NjXV2ew10U
JX+Ldjv5GREEeKrA6Gzp2GtCq98UN0I5koCOA8cEePHaGsug4TPL54gHnNBN
wBBxhyH3VDzinVmM8jdIMEk1C+l1FM4CG5LPq6vrVShxzHTvuH1oBewN1iWm
W9B7girE1Wl9GnlsmxXfZuq7g+4Md6V1ihkvAiIbGYrfOzTEzkZXbeK3108t
9Q48vhLvVabmonwsDq1P1pYhbZV+NlzVQ84K4miveugYh+ABntBPILk0mGLB
C8adBWn6M8xsap6vWNaUYUboEgNCSTH1J84AP4skJt0IJioysATMVRSOZ6GF
+itXKnmEGMLTGKA/vkYtyvs7/XvBkfGtHQ6SzlQtdR4HnSwyAyB2bMtiEWSu
yzvadWMVVSPCDBp/IBZX7QXsGDh0B9sBqm6aQw99fL6E0fdmojGSEknhj50x
R4nXPkR3LMinJlopUE59GRLI5u5JvwgxQL5PWrHSbX4etiqJkLRWOgrS7BbL
dYOO6qK2UKKrzgyDGu3v7PO45S8Xx0d8c89ZGIBFQNfMNZ1RlINg12uXIE3g
YJJDpxIUumj0/5IIZxUKWD6RygK1r6hWIeaRhEc12WDHXifmDADVTNmbVYt3
hbQb7CEtTfT0CXWMoM9RCjwZsCItTiWbJ/pdtqOLZxIA8XU9YjNsbzfbg6ut
Jg3w5WfunCpL6FQ8QKzPRZ+C740zpWMkJzIesZ3AU9SM0tg3sr+2i11iYY3m
Ng76DGKy53dWCV7uwMCJHQGLWIgoZYi+GeAE5o0rZASXtTMRS1y3jghkuV4p
SmSa6KauCRk9QZGtBXFlTJz1qgEMCJLf3MHCNlkWk1JTFjf2Ohlg1SlrjOtS
PAlTPeCiQjCaTgOd6ozVdPyeoQR+UYedsblLfWbWHxHHpbmtBSNyskb+kW1c
K8yGI2qigyVRW6B1Fjdkq3Js4FC2dqY5d0mC0CBJSMus7gbIKuyIaw3UN/Ka
2pSRzlaNsjf2TjE9KwuvWfH4E43OSeUZLHe4SDgQsFYMiS1wYsnP5LpMNJpJ
tYdYkqSzO1d3gBYjdZ0EELIeZcB8C+oeF7bCm35Loh7AhhdEHkJvHLZMYEm2
iCXmIoYi17euiLbikIgH/0i7iSeQqbCYK2tpsZBeVKEp5zYWE+cp9xXsGgaR
Kv++Cgxh7J8YiZyU8a0GJZHwP4niyl74UHgU1+mhT8NekOrfU1c2sFSuUBdc
td39MY1dOj3l6SmgEIzYQoGwT0KRX+XnxbuSU1sPBf+o7Dy7XoCFIylmi7wU
cZAVOQ8jlMCerXR8rUtO1hv3MMs/vYsuHXMWuqZ2u2VCdQC6AkeyOnQlFCMn
4RHP2EqTTG/DSuWtViCIWErDmcuRu3Uqjk2Bci0wOgnYfkCkDFVXnCjhNnuU
+W5tbayIDRtoPYMXlk3Qe7uyT90uk1UJrh8bPZogw0NjpzOgtW0qTYJyOzaS
rqO9DJz5QoAMs1ayUbmBT93TNZ9iWMk26aIl5aL0e6BO5bC+QdCQdb+gIOiv
ucdzrzM7ppxqaaph3vk+sHaW2/MyEDn/riRJZatZ6xOkGQSyT5FfYIeFhtGD
VJORb7KkLesgTX3dAhVghWxr1plywVKCn7ZyowR1epjm0nU0ABXStVL+dIfd
ZAU9C+AETicwTSRJSC/eMsY16nRebRkRCd4hLggwGC1L2m4Tc1SlpraJcSiF
YlzJcjOXzDwU0EDg86zqblIji31fsXBRckWBIlJzpOJkWq0YPA1gA4eBsUpF
iz99BvmjjfKqgOU8NRUpFJjwBdm1l3lLk1sFAIu4CLqGTwOXbXOncmereoY2
lOpjQIHQLn4g8ZWjBPYGmV6MbohKGfzhI/s+pAaY4yayc76pRMoP5D66YBFs
b1dgKvVyKdrOuo01mE58BBycllXUrT4qkvRQTXcSpBpupFqadz6LfiAJCR8t
9N7GtlYGOx1Yf+gJvMgSj6BZU/EJnxzvosex/CLrQY+UG30FdlCo3SlJdOHN
3qq6AN9vrUspf0NE+E6eRaWOde6K0BIdVJ6B2OU6ac+85sVMwNCtxXQSxfNI
Rm1oBM3t7RD4EZDPSaK3bJGGJv6l8XXLQNxuWxU1qPDuoUK5+ebrycQMrCp4
aKbWLzshOpl03biNjZmqWy2CDQRh9/yxhaF2QFcjcn+sqTPJBIbOChkbUp4c
v0aq2WEw5ARHTlwcWxJf+mr5WnMe4GGI9lKKri+NureSik2SaAeDDrzd0EhQ
4zeaUunJ22HfwwBbNuUKIapT5HAsOWDvd4izG8MeBfiLob5A/NH+i/Am5liW
ysTuyiXHkVt2aIHtB00jVFsHUANkviCyw6k4mVY0CM276d+UEavYopkuHyRc
TTarwCVDZpUyy3CrtcWLJmo5NC15ZxcZwApeXd9bEm8oVV5zjqdCFwq7dSCg
9vdAUwOdvgCylOLNd8WuKhatu1bI/LTPLWkR/gQrwTHmOUNF3Jn6nx+PDkZf
8/yPXh//JObmB92PnFvbFkD4dK1suT9l5C/aS9XIq8vcANrVz9ZG0uqyl3Y+
eEOtS7tmc4fnekaKxKZjufq6zbLcNcSW0qdP+771dOCzqTeVFCXW1LEwm5QL
6kh/CRPWEftY5ycHDS5bZZ9gRwGt3qA0k/kan/Pj2mY5+8fuaNhVHeQTjPFD
R0XZUVqQW+kBm5p2Kh0G2j1R451WhlxwufeXsFJrC5y2qeA+s3ClKguxtKBk
wd56ZCyrkXWFDXlxCEXYZLdqGEOKEztsS1wdTgySvu4SxUjS7KAoySu2suft
HSGMleR4B+Gpq3XwA4aNmR53KP02ARzMOwtPYKDIzIaa5Lp1MLdFyAIKbchC
eZX8db2wkCCQrFxFTSgBlNftgPfu3oDwDe+DePVD/VdHoXyiXNziT2NjUG/d
8GmGlNyULsR3un09gOGxgUEY+Yn3N0fbpxcS3C5oF4jhQwdsxgjV8tZiIpzM
rIPQgFEhO2bdYzyKBlS8p/bTsrOZ2i9G0z0DArmhc9mLDG+gQySaJ9SuyqVU
CkrnIv7CKl1CnUe18GwBWsqCuCFkttsOqU+R1bAgZOCEKDu3+FZsgJwIf2uB
LESiGsKeqgQSHroiQ3XJsjNEmaw7St21OrrIaZn6D8QLUSz6bQ7PZRKTNrOz
jnpvPJ4CWVrAbhqID5/d3FZoIuuBQW/mjHkOOhxOHU0s6S0Cxu/M+uvpxf7R
qha81SqUZBi3wMyII9RWcWjQPruW5VpzGRwKm+Ziz4aOZH3V06EWxZoYcfA8
OjY89LeSR9ip/C4dAtdT431Kzfc8mkIOKAX6WcZV1fiLQa7azYG2dg9a2yaE
d21yXQqYFD64S3rZLKniMdfHXVbieHdDdEq+yO6iNgDHec+SIbAcnvOVAP53
NUaafs8x3KPN5NTBi40eCCJ+0CBUPYKPwUf+LWWT2Bb7Pt7fScP8X9GXTWh1
qxAm1/WyPWRTPYFQhuKOZhYWHAwQxr4wz/scBbDLov1O3rAh6fCWw0DqIUt7
fPlSrW2YeNyskFweC9lwxJa3Z+2CBUQbLoo4wpAEZOG8H08ADhU9I0Id4tvA
T8uANJ40/gwD5NqDmwNlSE2f6B6rciLvCwBEwUFtpV1f5ecNOowxtG7BMu+w
Y0pu7V3wLUrTHPEssvGKgab1nHUZ2J503+F65tejinkXpHa4wclm/KbtmPVx
1UvWZgA9mfyA5qPTFWNW4aIuShOi8SrNig2gA9REllxqjjEAxwsQ6wzNjASP
TmjluaA5biwz91Cjb3WjZXcK9+jQyCYMzt8gRCpdklc1AIa5eqS3TjDoVWnw
wDB+5KJUCLCAeNnHGp3x25QL95xpEOGagHCBJoDLGHYoNKUZ4daGKx0CPoda
Blr4wsIZjbHlMzz6kzZcxM8GMoQsMR5Gq0jD1SV9wewJvYeC6xAlidr+YGtp
8QLXF6wsJ8qSkar2h+/EwSTx1XuwAyaiwJ4DLTx49jlHl5HymHlofrBoEtoo
khthyjINv4G+gER+9vLHt/yeN2dy8KQ8FiJ5xSa3jpXoZ1c25W7o3RE9fRRQ
YRWloESXhEBH1RxJ8H1CMfBFqxhVcB8raXsSpuGqekOdQAirNJJGw3Oypdpz
laUAxt/yw0xIbyzmCN/45wOTnUZW6qVD7RqwcSUwoelS+AxCiIZQ8DMXB1H8
W2uAm4a55mJjrWIc0hv3buEBUStNyYVUtGgq6mMGaWjApxGE5imJD7eT0h/8
z0rumo7WYQcdsQVepYELn8TY1jOWDGZt8QUluq+bVOZaYe7pJSpzdkEEd4+o
c4IuZxPotOzrKVfbSxmg6kpbINReAoqFLdqFRpPy5+rtOVFHd8xyiL5vTnEQ
xKqub5+J+c35D8NvpaMFnePvzl6+sMSX9+9f/3D87YOvv/v4cZSdACSyO0Iw
w1fIzYr9mb8ik1f9U4cKxrAqOWZ+gMxrxbB/GZ2BLqBGnMqlh/LLO4nicHeR
eF0AuYqpeF3MRPNO4PNJTHIaPp53biqW4/TwcAFvwU2cGykkV6AX9Vc9+F+/
fpgPdcpiFsYJxObQveAIUgcm29RfE8DWPGeJW7GW/jiGCoM15KvfxMbgjE0Q
CO3jkCtW2f2Vbr/eb9suswpTTWUQDl5d8e78oXFcws2EE+mmwQmQjgsNyZv8
okObhw7Z+PXiTgGSSGBzBKjbWi7QLbGMdauY17wVdkSjajAOIG6CVGzRz7yM
kfxqwUZIvuqOEtBC8IDLUgy/Uj7kw1XCH6zQ/8+CyfSVBcIi7fSTjGbH7lIF
WTAFN6XcCddMvUOUvuli0l9x5GpVwkOS9oz4bsDwYl8YPE1p8VdShagXMUKm
4ItDLh60yzaIibQDj6azM6HWzOzDrifa4M/EcDEIOc7p928LUBr9Ycmt40Ey
NFgHmyhK7xcGxB8VMUPi2wWP91XEXgl8zYPiJLXxfQg5HCpLMXI0KGQIJdwB
gSTwW5O5bxOWxpuFToCpjHYOLVI+fOuC4O/yiQL0xuEBK5tdZYVhcTtl+FuB
HHCJHt+Qsopl3Vag5fFn+9UHVsuYAMTqQoP5sU1oHGKOUORsmvaOkNzMTwup
Me+KXQMC6iofPaq55UVSCxTeogpdShdGC1aOgxhJgn2sjNhy8eFZPeRQ0Tn/
lCNGGtzp5d+d+BF6NHyIDB3+PGWCH1IOjK8UnKPz1ZMYmDNUIPxac6y64ydt
bj5ImxL+HAXa/gPrH/4hZUc6E3S0+uAZ4KDzopjg352C8f0PkV/J5wl///CJ
WxF/7gd/0tkzbYLLXF2M1M4LeNVRgnzwhPzZofyDNI4KFYvS8PPmVPwEU3OP
QgJ1TtahPuGXwt8+hPPuTpK5ir31Q5Zx7ZXI3Lj9fPUdE9kXyD3Ye+OlAMVq
fqHaSX11JjFTIcZaQmxJar5Uymvrs07df3dCq+0kSXXkOUAms2r4AZ2wi/0g
9UUpXiT7dLrV/7u09KJdTdJE/5+OpRusf1b6zbchKdflF0Zrqc076Qacq5Yk
y0MDlWkSj/lBC+zDtTU2UaAnuHAm5neoUWaO0hq+gStv7IAmoPtLL7hP1Ko6
MLxf9cZ8MFD0kqtzf2cEaiAqkgcoHCNug+DRbrTvLpwZREHzViSPLpEBFUgT
GwenXkWUTeRKSvexeB/QdIn79g00kRfCI8ktMJkW1XvLaxXNxxqC4o2xUyS2
IWnNiv3r60GLIve0U6dubwLJJm8w9DeM73jAjgKZhs3SLp2I4eAbKltnzP6u
Y5bHKlTk0sNDy6BB/rnWaIPUN+36sImWGZvKNC6n2ZyCrs+XyP2+8EXrcOJc
7zfbS5fyjHlzXUfo7MxWvLaYiwglkq+UOlbpZdwiil20sn0KVhyVgWigK8JQ
T+u6TiwDRb90ta4VSdbN1eGZbdQhAA9sSOBk9yC33GAPQmxdHWzHr9COe1J+
6qzSc9pOtKWh8SF7LDHNnBGxSFvEbVNA81DBc/DgW1KIpO1Cqb1DZZCLoi0f
P1o36opAflndi6vCCpXWTkifbsshlAR3YftpFjvt9LtyM1RVTOgfxqulHTWa
jEGMqLpaID2Ecx9fB8Bn+IgEhgOOm0l9xdm706x7gQZJEh/caPHX6suIrYf1
d1kw3rFdlrLSSevhoh1JLLF5g38rsmLmknTMb7C1AgG4Acvi3GOf+xtMbKCc
9ACEzqWLXLdPVfCeaVGmTxkOVcIKvpq8KOnR+Ky+cs0C6isNBndCJRzJ61Rb
C4WEOl2FWRH84+w2dGzQxrycTcLjSqUqD7ZCZwlLfUdyRltUWhI7yuAKiy7h
kL0XZsVQ8ZwtV8VQlSj1qwLtEurLDMaK+aY3EecqWcfEkPYE6akQX3iA0MiS
Ur4114owWd2oHQY73BoqzyrZ8hbGS+Yy0h6NHowO9tOUNFQC0uRO1PP8/g4f
gfqhP6rVEmYflKvoVrKlGrJF6vna4b1IBCc4ESwqeYb/aBm9EcuhlBbanzTB
g7HlTEgdFI+jlvMqWn4WSL5EVqEbercdx8DyYiNLInfLHCOMaJ1kF+xLRpks
bjRIQDawssbc4MhYauAGkmSp3mVnnSJGar3mPSIGEGhWxXzJLDwoPCJPpRez
R4DTeUsTHam1yXLb1w6nkKkISFd4i2ZFxrnIiLxbIqmBAAaM4FEWodIUscPN
71IbX2FHNF8DI7lAaKpRV4vlOgHFcOk1kkqADwy6ui+7epv8tsEf8BrBMcZ8
1HXWMKTxW158z0bLKgI0R2ujx1gOkwFHtmQcbCIDsu1wXTjSjWD4oEvbsszh
gMjxSnK+QCbwbCyNMDTlTpQ24OiHEGUH+S8wuVK7ZLXLspxcM8ACmDCbZLfF
ZpCFflG2hZ9pwXPqy2H5RmSyyRoi1MugTTa5rUXglJHgEp6pobUsfh0GDIcg
0LQGyXHB0ea6hnSVjRNeU7MaK2w1Yt2I0fSO66a2I/+S1oHrwOUb8cXCRtxE
FIguXgVT1h1R8VKzIL2KFREOCRWXVbks0Z7TEZGJVpTf16RCVC0HxRYxy1ue
UWyxW2nQdGxP+eNXhqTZT3IPOd+ie+W4cic5H2PPi7ICkapaAsSWtmcZ7p2h
L4q0WULJi/rPw97xIJcFDX25nqH4V0qgSmlbYKTDZfnyigTuEHILp3stdC0F
4dz0qG0N4MT6meFDYkvVLzEFN+O7Y2QU+HS/VKBNxi8k2wuS8KV/XVcGHzgZ
fMj27xL9JT3GU9HhXgoUv1DN1+onSaEq4a6D9ViOn8A1HM23cTzAkJAFVKiL
oWQykUqp9dWtKfRilsO/v57PkSCBCEYsi/eDvkPp1RpgU+WsWLYAoZJ6Vkkn
SorWwVKfJht/6FrqppsgqJb4ZYijI60HqJeWFUI/GvhcNPOZVJZsptPnzIqh
FIAtdLtltbMheCRiuCoIBCw24JeES4C0Ex7/hsRJTQyAGS+TmzH7hbT88h2C
1flimF1VVBfE8hiZ8pXJ0+k8ZQite6evtL5ebDmTMdqhJQbwy6KZQdJJx0XW
8lzCgyh5zsOdNlYJrieVJgawIFF3pbXKFedVZP9bjGChuJ7KEzRTzitx0glQ
0glDjIUPwxo+bLvoYanwRgyCt96mO9CC78wiGr3aXb5ebhmUMS/DXpgJrQVN
zXBNtNqsi9AOIKuwSz4EElpRhBQE3DbJF0E+HjpvXyEcXqNIVQMwaiQEnVBT
kgprjmeonC0Ky4FlmaAcOCm/1VZICiCkhDl32TlOFbOkyQXvRDilykAhrBKj
Zzs4b6dI9gOp2ob/0m6fqi4lnpFUjBtM/SBglkv7Giu3TrvYSOPf/lvT6f4b
CUOIUQmGGa19Y+0rnoQLxDcupvMoBpTaXkjfdNeqan1WNQzwI1dNzPY8E2gE
Zr9AzaSx1QEOaCC75vqa9PRW2533GzHja9eTxxl6Z2QPr0UCvkbukXIDTY6i
BWlOGkDbQs6ZJZTzFMXu7Ec9A9/NtvZcXRsuxpGAFqtpwuFL63VbZ5JDaIUu
MSVoaiqAkl/yVM5IvRVRr2SSZqGFUQB71nc5LGLsQrVSKyPr1HA9cMI6kCSJ
2LJpFAmvUysmiaxZfzmhXNPWJR0j4b1T1p44RM390ZNot41pwmo2uLAhLLkt
t8l3QkIzTQoEJFKIV2nrrf5waRm0K4GjwppCX/SeRWs1v6KEujlpR0bZFB4R
3krvHsgL34UqPqrOxTRgJRoY+KxbWB/3ccgL5r7H6xGHMb6CdXbFuZnwAxUk
2ijCr5pJlxfi5UlxUWsaNnfydnVtnv2oAy+0hcyVM4ZbENGM1Vy3a7GK9k5c
ogKdh86p/G3wW6krx7IV1H+VpHJDPxq25cLxdelRyZ4mU1Xh6Ay5pfZ2UyeD
P0GGke5kLUYwvmoBrlKwZAO7laRXJ6c70BTW3rz3DIwRtHE8nEDoW2RCP3cb
xgVkqy701m+EMnbuGNN91P/6JJEXHZLvCRs8wGNLYpxzE0Hh6RKeJE6CppJQ
otyfgNOC3zoFa5vOIJoz2w7h63oZul3roRnvCJ4oHBFUBQlmgpklioeo0z1c
hA0R0Q6yUEcWWgOycLRdCWBpE0mcZveqesj1YNk4zLQ+RlsKSKXjdkc+g6Yy
WezSnDNLUv50H0EcXI+jVY6s4w+ZljfVpBxec0zkBjmpuVU8ZnJVWT2ecv0I
JNH1ZtpYHRj3ThRXlNFxx6sUJBij9KCoKLDlgcPAibS9Eu+HlExZ109R3kDJ
0nL1M5eILN9gDQdNjruEC3y8AqKEdG/fwkcDFGGdSI3PnDD4tf1Ci+kNfNz8
O9cQ6DMhCu+9N0d/dkdKur/Xq/3+DmdrhZARhyMAeSdqgWbhuK41Ost5sSBF
f64lQqKR1ZdZuD7x+48fWV0UD8pU8vl5AhIVeWEoc/nL5qqw7ks0qQg/l0ls
AtTED5L4uiZ9tWgm18h0Db/EzSaSFujwqq1nMR0im5N1XJGy+gtc26cLDDWI
m9Ny1gPrpuLyKLhGY/LOzY+LtmDE0g8YtIsugVhaDx8QMyhnLCXFKyx5oxcb
7iqlODUtbczz+g/D89dHL85evXx9zvcj7f/p36g+o1q2hJ7mBhHrhV1QFNIw
yFJcOlJk2sOIgp7uCpyQ+OI3rYvxojzkplp5d0JQ19IRtJtkEVsUkRrIqQxm
c+OtYbvQt4hDv3v8N+7UIwjb9Kf3+NOwmtIWDIf5ewAPai8d0F4VuxNzpgFH
+Fo5JJu4WpAAmiUOtWKEPm3BJdZndL92MoP5XZoIssdG3N44/9f/8S86+2O2
6jR5W/oLL6X4AJ0+wtulm/hAo+IuSaIlCTG3piC4ZGZS3ADnLzqrJCguG8HT
IHLgKX1yt+hTybFp92TjNOOev5NVvFxodiaR0bK0Cj4AWOM53+iAY/Lx6Pn9
Cv0+n0MEEJv8pWdC98bEHllQt/nZm+/Pjl+ffn/y9sXR85MzptghB7enGQpb
oA8yxXBNoqCr67GFAzsyYjWwXYOduthkVoqlCf9ICBCjOzhZ4/x1zQIrqDEy
GTO4hW0bR/lZWea292GmxKRML7CcVLcMRM2Sxu+RL4RgrudYXeLXXefzDJhW
Hz93FTz+VeUtJR/g6UdiPU87pZPGJL4N829xiwo/Yk//OgfouWr14nRglRWV
N6iZuhhhh5lW8cWfMySW7dGT6Cpyy/Pvd2tE8X8KrxqqMbfMMFKYSN/JInUS
zz3+/ZkRnz6/TeDhiDJ3RPfGiuYeDTsxdNKYneyOQxTL1ClxmfoOSMSU6tCE
iv3qzffPTs9+iiUNWo0IKs4Ci+tDuK8cFPWXcbtVM1Nu9zTuYVJQ0Q8RJU+T
hqNPHwsOsBVhIAeSjBVo5c+ePdfwA56CE1kfex28z+JalofwM3iYt34mfmf3
M/Me6S9f6V/1hZ/x1IufHnl22556QV53DVYQC3ORLzV/EXnAXOple/89qdZM
JGHmULTv2+988c5d9uNGxqw6OfHcl4bWnLSg99kAXYJnviBcUo43k7Cb/5kG
y9A2ZL2CF7FvJAUMRtNhBoLfHbrhpNNr9Koc4/AsfIsjGkvgL4vr1vPw9QXT
qCWaTaksRR72eXj2vESIA0CxbcoyPXdiAb/QkjkLqM1Uu7fuS3YvA2VgozkE
t6wrtlhlu2mdLL2ytDj4U32TX3UWw25BhiDx+xz1J9HvptNKwumZ06xUcTQX
oWmpLp1vEhC24DlQE262yUKVNBuIs9htRl1fUSTSYzPiD7xB0k8y+xWCif6M
ufAfrM0hN2YcjUaqhUxjH0T9aei8Fs58OyNBN+6Q7tJ8styTSo+9Zb1cbvaY
zvaKB8WeVnvs0ebSJVOJrvq5nTG2MHrDAua2vVoch/izGTkhHTKuKEw5wSRZ
NpxGhm4tXKJwtxxdjQaS8EvXV+YcApLcuLFo340hJI8eHHEae11zj2L8SHvp
DUDS8yU3IuEfPj9+pXNhNW5g0WM9Ogv5GMcYADNiEDAabNwE6MDZvPAAdC5F
l/oMboUX4zfE8rHjbEaSF69NQAeJDBLvh1dYsvHXX++X3z7a3x+WD767GD46
mD4aFt8cPB4+evT48ddfP6Jv9vfH+d3bhtsUL/Lx07G4Se4NnAbHq/hhTUqk
M8jA2lgrUHqm3T5UFXVY7GkE2Rwfe83BXn43mSvfR/35xd49p6nF+/B0EMYb
gBYHezqgaN88apa8+GLPCWJpGakKE8N87K3o95980UV4ET+gb+GnMqKRQ3PC
xFUiwC2UwD1fp28vq1m5x3rO3mU7ROit+cwr+WV8++iVTKlYow3E28L/YK26
cp2KG7+jeyiAD+44stpms10ziGN86Rzknu1F9ZihVlSKiIev0J7H4Ybm2sRI
r6j9ur7MxnfppcTTZA7C6WSLW+Z0+JN8imnRZ/xfKPmkFTLp09uz4M0g4Ul/
H/IfWVwGP/SM1sKM6UtfR0PrrTREWbNntqSK3U87AUBXmUJNXI9emCYCi+Gj
txfd8OCwVdOHZQt7Q+16SzNPjLeqJYVikIW/Ww+3qYgsTbFgQUMnYVAq9gZ6
N2yn02hwktnkzc9PuQtcxftnrGChjGBVaif7IpofkT2FsLXEKAPuh/ZPinFl
X4qPPFpX6i4+aLVdK4TTtszKe3x+DjEZ+V/CUnusp6gaDBJr1l7pjlhNH6kZ
GRh8PY2UAVJqIHXsvnLdiLJbkh6LyKHHnvfZmVY77TDE7bdJAxGbHf/eNTkX
94SmEz5xWZuIwMZcBWfSIzX1pqahsqOF/wLVQ9Dfgt879LzZ0nJTm0zqqPNQ
Y2U5rOodMYtUwJeCv8IvMPN6+qA78xLIoNNQrwDUUTgcX7MdlxVdBRPm3bAL
Z2xmoMZJun6OzPfCs/dW6vKDLllrJqV4QEKKoKPlaZ3BT60tBI86RC0xDnoP
Kw4ABJswlhYEG2+Llrtl7g6bF5NrePLLcsUaN/sXQ0dPbV3InY48ZXAB7pKr
TRAosrubAtLKSrpr0Pv9/xb3tkuRI1uW6H89hYb6kVATEZXfdQqmjw0JZBXn
ZCY0kFXWt60tQxAi0ckgRIcikmIg/84DzCPeJ7m+1/7w7ZICqDo9dtusuyuD
CMnlct++P9ZeKy4A2tjB9aVYhlSyGUEj5uzBaofkiUT8mfYynNHUhLa5vVMG
Jx2uqzFQ6goTaynNTCibKveOOjoOM+ZkI3SE6NBD2soerJ5ncvViAqIgIKm9
hBFdHfuDmSVPsO3pfJyW5yBpys6XC6rGIBWHXPyJ1fVjbcBq/a5AIFIiSuOz
p+Q0mAQwbcifhqX/EwEuOA+IMkXktJGpKPIZE0/868f9Hc8TBNTLb+WpjS+7
vf1t7w1y6cNfXoTzS/mAiiYlZ2il3Lm90t0li3ehrK0bneq7bb87/CAQuTWq
k6zxNfxoBlka6lDB93O9qMCdGenM1347GW5rcXuoAWSzFlmqMurOlHrLigfI
so9XhHnTudOLwwXRWfhaFfjweO/k46ExMShuJbtvhgaxgBDiIO4CR7RW14sm
rIUrq2hQ9wxgK0KDpUcehHSy7BnZFJYO3dQ0V8wTQ0Dy/tLAOHs+yg+FbzCm
5+1iuWV9LZEfz1M7RbMXo3xXRhaeCHQaPXnr/vFsjJl9iQ0NuZi0BXmt9iW0
1cNanVo+pzgmTSsnTkRm8yzZZo55WqUxPPawdh9q94q8OXPJcVD0J2k3k5R6
Ysj5BzYf9nr821G+KvWpMvGs2781j9+nF/yF2uIcnL7NH5e+RSWZofEWqTZa
dPCZ15GAJ6ag5JpNyL09L2ZDJEpq+roVHMhs0g6SWyiHpND1OU/usp6U07yc
NWDRPqNFkoUZDr8nhjrmuOJKCd/3rOALZVksHoR3vTyDGYY3b5F22saMner0
uGRxKMvRcTkPsxLXh+x4Cq/i57pEeLmzQ3hV3EzrAtl3yk+aCbOGUAbA1Jwd
uwieDekDdfrbVuSNsamct4S6WJY4ch3XJkKa/bksFltvV8+yNIfI9Q43e5hb
c17TXJSvzrk0KwlMLy6gvoNJkRzDjKpBUhZezqZl0ylUNLGbrcjGkn/9pPMw
thVrgnKr+nPz/UXmyF9baVLaygMBq1K7PU8sSLlaU+gQkO/D9fgcp9tFahYO
n6csTWrDoW7Eb2HBX9Hdwj0wR5pOjOnLnBcCBw/bAhRrLKppTU8iDOe28CA3
HkgilZLnSSvS9nr3E7ye9hAJSnuB/ie0DS2lei+MEkbo0E9Ps5mPbbUgl6co
Otj0dpbM2WnKlD3ewkkiG88yZjxx7DL0onzRprbxu/z3sBPeSQfDKGF9gQZ5
ZKwa364hBFzbzH8Opxn/OPzj4NtYYWRJi4j6oFbpcKnjfj1Auj1iraS7AQQd
bUhYrVl4yspJDLpbLMKeKYhh0foj3ofRC1NuNSN/2a4trM8DzeUIUIzAkwvh
ocdjxd49RaAJ5mSLmURb1YdInBquQkNx1uBSw+nU8jT89nxDUVzdrhFKxUq7
q4hXDn+V/B3O3kqeXf7BReDgfChDRnpw00Jlht1x+otxexfyX90QJyHoOluA
JyI6Be28UqyWSK0HKXgu/3iEpT0vtZoWp+XUN1BNg6e5BP9X8dnAhBy85pxK
ZlY0NwGS+BL1G9dFJrAUo8dA/zvTZv/MvbGx2dA+V1wtT0ESreMG9CKSxjSF
lYZ1OVtOizlgJoRzwxUBhbNEG4NeI9gyBW6j9044UBm8gKRfhnWF6Xu7d7Lz
yxYawIJjQJoLFOJxJkoZjC9p1q5Lot+mrmsycvH+Fmlq42qVQhHvAYR2Aetu
TNEEgFtArc2AmegtvM84vFcwQQR6iw91ZfUzNh0CaLxh0gf3HIoTF3I1g5wT
zF7bepgJS7GRCDmwYVuzvsXKu8V8IVkT3geFNotLUkyaHhlRnEEXNMFZAt7H
cSR7g+J9eVLVpJ//IBZ5XTJYMSHpkXsvrs5Vi/2hnODoiHerC6TjRGAPjSU5
dRhPFH0FHFNR4EnNGRYh+0Oeu0KcEhRBti4R2iA68QNulrASenDzNCbcPfiw
t+GSAew3s7ypX04mbsZ0j0BXnApZ3Yn2kyL5wvFInM4Yfx78PXZ8Scjs7jBg
oKX5J0yitAJeeW7dYwWak5neQveKlyZ2oDmRsVVJHS2Xz1O2wPBNYpVj2SD/
hiwxcbw8ZTuXnp5Jd334Xqbn7B84ZdukLPHw0PesG5JOSG7+p31zwCtsf5cb
/cyN9yikeK3VsoHJVTPHtiX9g2+ElFYmxp14vl1XqSkHmShxhUd2mulsO9Hv
RBoqJWDqQlMWOzJxVTSSZegGYhR3COEm4mETixITmoktuP2u5o8IszovwWoS
bGy5mb/pT1ZiPWyj6V99XjmlMsecF5b9G3PStvPeKgPr8sQUIdlZOyXIzcnf
gLWJYtrNTnj8xMpoiHnEe8mSYHtE4n8AXPftb+g2tGN2uhrWutqGrSzl3qFf
qd5r+G4fHa/4jcEi68KrWV+614qNJFUUZikuvA2BuyX1X85Fholdl8T3hmSt
FF7tOpdQUEtpapl6S7Bmed6br7jfllJgwA4JXiKusuq9eK1KSdtKu+tzGrHk
TDQzxt2+D4UoVgLmQrPAwwDnQvmc3hRdBt5F7DB6A89Qyd60M8nRYdFvVoS4
wrnmCIvCE7xQopFYWtP0QPoUmoZyteukEmhldB1Cim/V2X4Tq30TbpRlL0ad
EEMd0FW2wwBfBqvTSUuJ07T/7t2nw+2j7fd7wbzgpW+3VuSAK0J0MV773FtP
anTh5PqIPpdIgjfww0MagOAsaACZNoCvteGIs7oF/QojfuVG/KcWxemKRYEp
YY7NdWMa3tAlgilB+Bp5zdD05lWDD/BW+XGB0+/O7X0pPzWP2CxQlkdrWHvW
wyS89jk/K6iRFdQpCbO7bWUhukJ7BHQXmGgoCz3jd7ctJT6eh3CjH+MCFlu2
7s6tZzI97VVxWcy/yH5C75h/VCVKhMbym1xVxRgcJPeg34fHoYBYNMewOmiE
b3JmUGjdk9+P97vIyWC7ryWYVv6YW+/n3K3Vxr3q1GV0o0e9vOAxAixAF1HE
oqYf2KajUahYEA++9L9ar10PHwq79lkfFtdiCY8jR6Agh/ffmGrQH97CPvit
XYbkrtt+GMGS6auYMws2MdjHL7RzMxRCiaUuLG+6k9uJFtQna+JB55uuyCgI
vz0Htj/JaCUUtUphhcbbGAQo+0Brb9CR7/ZG94WTQjg9yf0vO9OdCgkzxbd6
WeqD7ofUo4+j3Y9/q6dDMSGoqyQrxCg3SKkFZ9tPtHqH0pzn8Ob8ynqBsdsZ
zzT9UVgCyNeaUkOZZoY8OyEekrtCRDqeZNtwWFMBurtxKCUgKRA3BaKGJylN
fwN3Zlh7N2q/SnLH4+Ur8n9n6THSxjH0WIbWYQamHn/SLGIDYSJkpIkKXW3c
xBzGUmc8QHpLrbftIRcy1xiDkjHGz7OkJ1oOHyz4zvO1DopuBPJEOBMTEwpd
bLW3Kd6HlUKwrJp0HKKR3JZ9jNWLuIBmZo2zB6xxruLaSorq5+FJ00KPyMnH
aJhYleqzLJL1KAwFk0zJShgKTYd/OUUkes2YiSIyvSZABphxOjNFNcBvc1oR
QrORrWCCxXA7ZLBKEsn2W5oYj8tFCIMjAFy7GRv6fFja58Gmu+8fSEaBYg4j
HiRpMTLX4f8pG6LQHFIaxf9QPclpiUQCGp+Ka7oYG1Sam0xzrQpkoIRbqaCV
3MR2wtoAlAkiPCWruNMFwYvub5rfUXB9F0L5mGFjRnT3P3fu/9pn4UJ0qqgy
brjG099fPX357OWLp8/CP34RMhkffHXkciPh5p0kJkxnNwoal31pKFPL4cW1
QEJdzuD9ybQMD7TgzEmWoSGBNDc5R+/06qgrcDL15QjlewNVBVSVZnXWX3eK
qeOaCW8lVZCUyz4SYNc7BNoPZ0tX1Ls6BS40g3K6H7gm3p6nN5nblWJxejzB
mFA3MRJrAOa0b4vdu6XpY1QrMjpcLnECguMPHuutvsMYDX8VK91e4tJSpZTr
WVI/owJgS62MlbeFshicGjEMpGf1NMjoQPXT1mfXLabghhzTutlwFOWZoyhv
Kw0lHQJpdbkWgGYaFHJev0M+pvT99azXnm6ZNlKXoeDBY0lYYGQh6Z3CBPsz
NDHQ/IoWcR0pyfxMG445I/4AK2FrOfOTqpwAP2kL3Ri7BFUMxQPofXbEJd8y
q+EqAMVd4EmL1BavZYvtZlTvKzMhQ2x3DSqQ5pKTpPccXVTH905jcBDpfUn/
uGyNT+oIREJgace/Cm52UsyIKzuWua4KRndZDhV5pbcHR79tH+3+y9NBJOtg
/0r+8GxgupDM+V2RXVRW7/NqynexPp5wYOAutArbWfFR+1GEIWwejPqCewOs
AjsEo7wzY0BYxgShvM3riqiNCdJAL2zLnrKQhjz1p8nknrH4UFiLYdkwgde5
tGwQIRF1zaBF/6xoqKfdrpRMbSRNWNRXKaKdqdaYxhWJ4lPVujUXvkiS54o0
P5KKU6zEWA1K6ATk31L1FgRX3hJMvFHNU7j9De328DTXYa0C/ACgokNCvq8+
s43exJ+wde2P4fQWh8GD9cDuN/9KwayOAWpr+pbWdbH9Vr2toPYTHpXqkxse
7UxXYfJncJeBMYw5Y4A7zncYerTJ/2ygTMg1R/LuZ4uoN0OSu44Ki1uqGNsf
zE14m18IAXwtfBfksrm6Hd5dKfXHYN/FahFaQG4cuWFU6qXmgZjnfCMYFxaN
EHBH4jxoUTcherXgjTgX+ZMj2n1X/DqY6WvKfKhkqfw7UH8OzNbkjDRApUS4
MN4z/A+pkghdrF/FDqVgDHg2j3TBdWU4Jec4Oope9i+YtA2yGsM0dxdxilmu
R1KL5GGADwUmnZTNPNNAWjDoTdn35tyAOMAMMa1IzxmVHhwxi5ySeFmGkMRp
POWWd2/2F1EDu30bkSgz/ZAWB4Ngd3y8QcaJGj4N84Eiv5NrhBmhiZ1OVOFO
RxjHJ4dN/F3zEANZW4gTI0HdHET2s+gtW7FJqZzNyp0vBEbSQ+zH2RggUiiV
lb9FSR4dhdVkKFtgh8CLw49Xm5Fq4R+W91LXmmxQJOZDUyFWCb4lDHlRqnRg
tD75OXEX4ZHCFaLWLgxqD/b6JJ5dpxAh6Mmohwv15NTxTi+YZdFJn7ErlhwY
WukBwqXiGIxBa3Gw0lLOpWRdMiHsCI4SDitAALBh+fQSDwYayU5IHhXYDe30
IA/AXpwQVMK6d0/sNbwVbaSg0z8SlS1YfRrbmC5J/XsXYTfgoRb1JY8nOgdO
4pkBHHPSZV6EezFOfeGPCNNhBmJbNC5QQvXmlXApvE4ntCcMaajqhwLEiBV7
nxdqSQVHmWRap29obOGqv8S5xqrdzE8imSHTcLPyF4MxQKJg+UsmrOcCO6WG
zyLPunZ68J7jRU6tlE+0VVze8s1AD7UGTiHPHNPX/06NIWFzHbPOQNize+F/
FQgjOOLon+S5SMdK6usMmpv+J+Q44AafDv6eiNqGge6YneoRt23n6GTeT1lK
N9awWvSUrlVmmejn5vPlFH5M+H2LS3GTD15VypV1MmSOXVRfz4xkTwl48yg/
3ZWQHfnHoSUnmGb0GNt59yltKBMO0yiCS9r2BPd5SPx2qxtUK30eN88IaUeL
Z9qd8NW8dZj3RG6o8jD401kxzisnP8a518nu0QOcHBx8ert99OnN3i/7H3Y3
/GtsJEeXcGN2aTAhJ06uaVjG+VshKN1ETQrMno14T8mOZq9ODwCMGGsIyX8Q
5UZHxWZF++j5a2pvLGpZOD17JvKJLVUSaFzqOFVXqR2uZ3m7ybUjti1aeREn
sIWjWK+46FVWjpf0yVxZL5Y+rL8KOm9bnnQXDHYUMbSo7Fo5Ao9zDOYDETr6
dwcSkgP65/qxwjmgs8mXdgBReIOxpfPkujaaPadPIQYn1sgM3BY/qdCf/4wt
FCHeIl3fqakRt3hr2jWGLyVsYx5XQ60oxcFjku4jwiPQ/eng0PsPSDnTKUBb
cVK1bGLBju7tN40Boh/enYQj2O+KXUiUmK6tgUAc3RwJhpEG0EM+y7xoUFai
MyzVY+rRXApX2T8XJZ4Hb620uBKPahcv9R0VzaKDu3Jozd7CMrhWNPdJV5nV
K/FWwrOpzqT3c5xHTgiIzqLqo4caMIgCcIWOd4vqdA8aE+6kaxp1YkqyMtDl
Qwd3qXVyOccB27hA1YGXBG3HsAlkHfhF2NIhd8TywfFYzqn9D2S3pSoqXmf6
0yceemT5wPjE9ZVvC2K2wdSQS4p5x6P8br/rdCT05yKll6FLjS0qJr6s2yox
EV6SUkvkaUma6SZffzp89irELsdgDDTlYQzbRIk5IxRWjrZQsDsJlkEvXVyk
vOtaa2tYcoJFLVOGkD5JTGWrpOS/gs6Sh8eal5vreFfkZsnBkcJdev/kCRIl
Zu0SESdFlmvEmK1qYcm5FdeJ5AhanMfG3CT/aIL5vw0Ld82C9bXN/N+Z8iJX
zot8rSmJ0HLtP8j+rmEE4WtGvIFPtanjRSZMB659BfgsWbv3da78IXzvb8qi
jTvT6w4xFDodFSwVzli3NxbWOwLCT2F1h3vABVPBe2sSL+tXow5LvaWUHLlk
+bCj5gtV3JtlrjVpbK65Faa8ILKW/1mVTL7KVWK7/YD4lM64+1dQvS26ZQUP
LJoYCQgI23bDpFYvSbNxOSf3bCk52cpVS5m51YJ98aUknW8TFKDr4lSViEf6
P0xUbIJ8SWbf7cUBHfblstvJ5XXLbW8MclLhM2gNOtLPJL+WZjgd1a0IlWvD
+Xf5icNJM02/SrR0qm+laiHK3gsrTyAvDtmbHIjSEBhWk4NjI22DHmr34UD5
DDwSmbH2soalbJOEDyqgK8NqmRsQgpg59OWsYcpjL4hAfirjicLtg+NF2moT
S8OoSCGOsM9z2uNhwFUN6gR8x4nXUs8G5JM92wKYFpqex2FSafQGpC4YRTRY
Ed5dA5dkkbTDrtOkDzLWqEHn0IArBtq/c9PO3TTy7IaPeEQMlgxN2fu4l6vO
lOEqukqsPBEVabyRgjnjYoXr/c04DkO2Go4HXoGkMzQMui6qhcJ7JPHbjPIP
jKLLkjESk8PxycHhp+O9D7v7H37GvRbVYqnsUPbGOrXIcOevTEOtK511xnvc
vg7jp5Z1q0UKrFHYYdtPHhMtxJiLd8IvjqXgUPPnvfVjq+8DQpN16ra0jfEg
LTCMd/s7Pn/2SJ8/+03FtDuFTRXP7qKv2GMT1BtVONIKQtQd+FqT3FZas56I
FaPj6yZLG1QuqH0NcyRv6LS8KKbn3Vr2Sbx8Ujt+cG7Eu29VNjOFvnHemsyA
/KiUhJVT4wVqli48mRfXzaonfdK0FH8l1ORQMPPZtrA8p+XC1Cc48bvz8v23
b0LEKXq9pPUC8UAcNMG2CdyNj9w6Juc548BvSXZuz4p90rRmP1khhgPVNWLp
j3B403K0Nl8pulEUjGa6dTqp/rFsFkasKOtjYyBsUXj79KhdWgsCWd/PmzDS
SpjVDXL7OS//RZ1JbpIlcoV/oJe2IpkBpnYHwPY9QTTQZpvvqVzN7XekXTpU
vFOINg5UZADHdRd0g2wG+q208gmh1yhDnXk+SjlT2CkjsswQcZDN/M8l0CKU
xqXmxupM9Go0yiPtu9UspZSNlgcIF1DoSZs+P3M/7ArFoF3vvf70hKSEsxTh
hWqGsQ36p5TWZojH38WL3OXvwrPNzui/9pQv7S72WSXIrLue/0r+M1w50t7e
5f8jf/b06SVd79e6ovyJHKPhVUO194KqqHfIHlezZb1stKJxB8zYZTWcp1ej
SyWsvYNeyt7wrQMhuNcTlK74oZ4lF3xD6YHy/JyIgu7yE6e1R5x9lmgL/1Zm
JLr/kfRtRw+TkWThbJUZDq98zk1xxvAdXshwKhOdNJZTlZSvp5z8bBpJ6Goo
Kcwr6Gm179qE84qqhQ2rFSjj7V9Gju6WV8wOM0Hl2yQ0QGVharsJYTt/bIrB
tlBAnEAM6+UEql5CMuFseRI9OhbYFU32+a7JfXrp9+AYsraBpE1jsz6DMmh9
qHlrHW10tCZ2ncyj0siqU8TD5kAWWduYyhDGLAIsSp5PajK4AP+ELQYQAkTm
Sf3wJnRQCKIeV4h51HpWZsY5wop3DGrT9B9aAmklUXmOhQ654Y1YSy4KZtom
fYYYxDk3TntGy0sbCdocrWgobcPcTcBPoXJdDM7kfnuX7GBurs/VLFGk0RZ3
dRNbPcyCrnDVA0wG5b4aV3dtZDwZsmU8HKQdCY/S31SN9XqoGR569H+NVveY
rS4jYMPB+HT4/NWrmA9qwuYtjarGFGaZvgoN0ijskPXVDl+w/JOTs5x/xt4E
D6TsA9Gu6DetYQWDjs6x7dhIYGHtIY5g8++ohA1C2vCfH8N77kBee4wqGS1K
cpFBljq45FDv8u0QEXQ6DCUqSPOoseNOeklz6SVFoMp1CbrTs9fDF4Sj/TiH
f3EsMcmd/ZcQO5NeI4Gqrhax3BvFNhNktxFUN6tJqBmCohuFWx0ulsG2YVAv
ng9fv8j9sYKqkR4pP3hNT/zg9cvhTzRh+wR+Yl/+oUMD3h3/+qfXw2fPf6Rn
XhS0Tie+LT49I+ZtlnTM4fO/hPf1E16YkmPdOdYvNEBGgiqe9vCKf6KJfxNe
12fUvelWJaGoISw5CxNm6c/gK1BJ2V/gp+fYCOECy+kXJr+jru67/O3qY0xg
5GJYJIZQmjLyu3X5LmcCK8emx44QUEvGTQNWaOvZCQpIwr0UCyNAg1h71m+j
MBkv0pSSB+y5sKK000i7OCO5TSe0ISO0DBMwXUZQZejTTBwzjTHTbJFYu2hl
Vd2qqIRbT6xHFuHYpCcTHvSGXADBmDU+OOeIvfXAVCWL9oRLVl2EddE7H3Ii
C+JbzQRZKbapyul/pKv1kJvTgh8gC3moCzn4Ax0FgEp3E2jVyNWpMdOwrTIz
Luc0yrR72YHXbY8nif5Yg3gopdvq802FC7Rf+o0InEF7Lu2P7YEwJy1Bykye
Rf1bbcvqcEML4UF8gujyGdXVI5/n9N7n2c5aY5Rb66bT+6/OMWSWY2DV1Qlp
tJFGqca99XnXlkUGECsPlWXmqaFlZ8fTkTjlZE0JHTzDdp1aNS/FYzO+cQ2a
QQ6L711wtYbz5WzWymMyerbs86Ho6HH8IOFGCbol8Yvy1C/q9Qkp+2PuMWU2
Y6GcvTQYVQawrRP/RKSnG0QIWhZVZTdiQ5WjnUg9TfqjfzZEbxSIs+mi+5L0
GhVAFfvmLcqZgrEuq8kwJig7ZLZa11uFUpIfnArGiWuZq7w1JKDjzeIDD1pw
Ns5ltfOxSb1CE/61pEMpizSsz4e8NijfoPqZzHaTgFK0ZS/B18bhIF1Yzrfi
iBwoIQSai07KtdbeJi5gnLtklLUc11oJQIvG0PQ8onvh/HhnYnwlLpPKYF9H
TT/bW9Sn7hETVvJfHlckGsTFzQB30IecdvV8RhSfI3OFNZsIoPS8S+qylS5F
e11pySVtKZBuvwLVsEjdIsmzuKy3EjFCfqosGZEeb8E9PInuoSaLsmy7Jf/O
w+NDLAa4Etuum9LPIKr5bGS8JZozSV5LaXQ+EWeCYnVXlobLujHIQKgJfk0M
SXxUdZ1BaD20X2GzM5omONXBSdVnCy6/V8w7qYNPU38mP+r2u4X9Q5sBpL2t
iforqeBe/IWdIBJMwRPMhEoUTQGHZAmJIh//sQlIjyT09MRPkDRYBGByX4DD
32BVxn74sVGd3PRgYDGQPMYHqkN7WiELTI0XnpB/5EeHRCFHt+tvw/APlouN
TVKQa5MAbMVJ4cfwALj7eFWTrgBHnVapvh7h8WKfzSkfOIvSPfDpvC4mZ4SC
Sf13TCClwSYO1jqpwiKtTpf6qJwKpTagm03EfUne3LyvmQAAI6hDZrEtCtAu
RbUKlN2ONGXLU+RaP5dBU5aGCWoJfEV4m+qBKvGBKxKkMEa7R4I5DrPxi5fM
PKG9vIluZ/FHCYQMPGc4ES+q6USCeCllggZZK5x0aVp4jdS8Ge0nEkUNH/eG
SvaMO8T8N5+jPy8NeAHKcHrnGAHhX7tYEbB0zrhtO3ktkeJuhSTerm0TmtML
FK2S6JqCal2dqBcEk7ZA8hAdOUqNRwD9efW5oqOW8Ebps/BT9MBWDFljxwMt
Dyo9QPKGOBMxj12cD+qCMo8XnC0LRrmpBNaL62/21bnaWL2Uz8l6CHVN8RU6
jAuxlJJTJSVLFi/SGiok4K2YRnNelY0K4TSLmSWZ0A5OMO45ex6TmouJyuNa
qzkaxI4bSK9qicSxeBLHZ/W1WMSW7kEEfWhNk9oD3PLMOiAlFUsdYJnxKHqW
YYiBioUwGM60NVYyjBi1Yo6sQNnDZAGMVfg+8YtkcoJDNcGeQLD/5cQyoey5
g1KTcz6XYSeidsflPW4pqs/Ph+F+8DrnwVSG+3UoGAqhZ5dmfMwKejTJi5f/
lBZZVXfd98KxMVNz+51Ko7oOI/gXrZ8R+9xUjlw4o05zQ9BsrptHKpI3MOzB
w49SfJT6mNEsTpkKSeCYDWl74sVaOva6Fq7OipLOTdg0U9GfppInwEOflZYW
/RQA6+jPaXsPZANbAXFR+4WINEWmX0a+XFqQqRKg2AeyJLlpf/N1JtXERcIZ
eejLJn6JL4cYCa18UrBqSUxwaGbKtFxwZSU9NJkSJwllhAQfYHBfR/Mvc6ep
kISeyzX3LyK+IFJMLgSXVWNjDaRPCZsVkZOWErMVDOGRohuuk03OQBpH0gMx
asilMDyuLKO5wH3H6skd6l9yV0QNt1ok4oDhCock+hFmAYhu6Nz0KIFsyWB5
gZAVJ8pwLkl4rn63ugWytQXn4ntG5nT/bLB7mQaHLOLMcFGJdnBybo3AnfC3
305YgFdWQIPfk9pPcRVRDZ9JTJlqfEJYQycT+e1VE8xaNq4g8wiitvL3q3F+
e3v0dufHV89+El4OuQ5RpoSpCf+3nm/wpTJ89S+vf3ohigdxiCO+S5eSXbbx
ZpzNbPVsUlgODKngKug3OEEhwjIrBwr1zpKlbV2BtrDZdyt4oxsswAYH8VW/
AniBwYovCfZFxJGYgJieuCwLbqujiMmADZTa5JkSh8N15xyQ2mS+TRNIUqao
nd7ebu+cHBwND48O3u6/26OuuQNAiuSFupQHNdCGG2HsTjuz8u4s4z/1GjGN
jVZeueUFfA8S2a5nT1gQdVhJ/oMILvd3tcN5EOwH1WD5kAZR8kL4+sO0UMrh
FMZOahSyzWTBNAmhEe0Caog+gb2yTm6mIGm9psSmRU3C4HhkiA25b3tOHYJh
bcz0TUXIi6Kvo/F7r72KjT+7ZI6jTI2sn6RLglGS5mVb16MAbWIXZNinFCtD
V14UekzDOBY2Oirg0oGuAXbFXJerjHK7krUlPQfc028iNOEqzH5DgjDW7dw4
xhvoxfUS58C43MUpoxqRHjd3eaqYSvUmOHZn7UJdP/Ch82+qywQrZrUf1o3V
s14M1h1D1+M/vYkCBGJ3yBc5DgYIpazpjRF4Tdxlev/c9Fz8p5+ePosXx4sL
Q1xQowT5ZhjrZbkoKB0xWNUnwsWtcBPCEZAKcBSC0RCPbkc32D7alduxlXg+
eoaztVFx43V6QOSjiv9clhuosUH0WIe9a45tN0bBbQ62P578MgwXlhv9/GH7
MPyBql+zchg2NymPDLSbiUAmvOFtSl6/eCU//W3//fGenYLJdgl/1I+ruGoI
cuA2qNab6Mq41nDnaG/3OLm6XSaYyrDw+WkZICXOiJ7ud/IVahutGwUh8/tI
idDsp3cQvBKSeq5qypsTcgPaVnF0vx1CKSn88/Bk+P74Zxno5cm7Y1XpPKMd
j3xFiaJqsFQm9TIM4d0FcV49ckposv/y8nWyIHb4NsGEvpdll++qDJlunrAM
Gwdyl2oanQu/nJwcHic+zsejd/cPYmf/vS5JyqwR0SmvR34T6zvbJxtYPoC3
SQeg06rsrL+IErzLsntWEKAFNLMcLc2BzMMENgaHZhMX7CwFzlICaky8hlus
cRqRRbuorpLChJ58TNpAS0Mdg/yUrH3ZRNl7btWCkjgOUWoRKm1tn0Oy/bIp
pwLbLXSqaXoJfa9qgTcxFagrRs2HHdNGDBUOc7xKfQkEiSNMJLxcYRRADKdU
B9T//theNebEpIeCZ0U3YnheJo1VadBigHb6KDwVkWHCHWDfK7hnMRFUIRoN
H10ywS17uJzNcGtM/BCUFcAvUgD5TPn2mT9QQZvpAtCM/gyX2a+trdavxNWh
nHSwAYsLXw9B4RgzSXrScdGJG1TQZh0wT8Fc2Ugjv5dw9TFJigRybH4H3gts
r/0oCMf92BJaeceBTLY4LTFpRViMCgR3zvNvg1uFRFMdZICikngiZa5UyZOs
L8yIm2TGx5w4snzCOF9/gPyQUgumT4vM2bqDCw8ouTvP/9///X+CHYm5R/r3
Uck9UMFVpX8SaGQDCZR5qZkBlzKEjq6SSCDzFNyYJ3I+MpMGHoNbMCm3gl/Q
Rg+Hwlx4/JR7rYUK7HjhMorPGinHDBZbJE1caT4pS5L6Mb3Q/xiSm9HhFpmK
7NEbdEvghM+m29vdvXd7P2+f7B98GJ4c/H3vA52V5LTDvuhkELCW1jEnsdBw
y5cK8x0e8ee9DyfDeCF6Sva/nSiWWyrh8tBOhX+ahHGdJBqTfOlU9WTP0vIU
pzIyt/7sbYzyXxCe+LXphtQkx3pnHAMObqS2eSPZ58Zq2GGOjILdrmqhVrOs
FlatV3PV8DUB5Wc2I+X+zNcjMWg2dpgtfHcslWz68dyanFhgxj1c2lOUWfqd
+xlBzsDcL3TnRCoSry7xxrOV0DGxLeb+er/09rtGPx5O7ONgaCIWFTKKShmm
H7JZIHE4FKmIYArf0JYRCcldfkYzmq30uXZrt81Rjoq+yxnYOS+pXfXg+ZbI
ozGCkwmpWE1hkEX7aw+axwdVUqm2OQZzYDtQpKoCwCEt/19DBO/LE/VXZnba
xsqHy7DQUEKs65WoVZr0UYwYs07EKDqx4f/KjSH13fNstuMgoiPGLBwQs5vL
4N9vuiuQzjEnbCifSXxnLkDirkTu5W8EMOZ8jEYGlEkCfT2CrF8wyNpmhRiU
4oKg74twTTGZsOZeBvEdJPbPbkz48O/BhQGZTHD1nXNz+533bdBN5f9M679s
fFAgK4X5/9vWxFwsyXpRKboMHhuLwSIV7bOHcfJoeKqgm1Gc5mbgdfv5t6Mr
JxoI+Ti8EeroZaLpTtK1P5XqdBPLSHQsX1Rwtdp2UwvvyysMUElx86azIsLF
NSgd7OTU4XvxeSBaJxWdYKPOa0AD0qnFW+3Hc42rDCRr5MbU/Xgl3K1AAYln
oz+01c0eHci58Jn0O3Ei5XJxIT4MqyxZCDcA7GWJiNnYOcboraY20JqwAKax
qU4rSndSBk0eUh+AJNTG+bpfT26iwlvDgCTfKu99vTWt+JiAEb9Tcj2XyeBQ
RB/+Ahz0/FXm1JszWBxfUzpf2P4U8LC4IO3KZOwLapBhHL5Ww/IvFR095y6H
J6YpLt9FOZ2KeF5BaXtNxP3tIIR243DRsQhHCs67dccQFPKX7rj8jwXGSST7
3+yuPw+QBOZ0oeurxX//x/WCLnZfciJcz+1VZJ6SdE8+/nKq15GkEvojZZ+3
r4WZTaZSdr//bBiuR1b7jhfX0P9N74V8bXJ5s0xgIQl3u93Mv4MNHqa2NxxQ
0/Jf1pLpRcfTGgxi7/RVjXWKS4JSl1XR+C2SqSYa5W87M2dLHltMqnmxMx97
jstQ/fMkvQ/+qa81JgWid3Y+9oWGH//y9Gl4Scq/5WP63cP6UKLfJGuGgmm4
1xbi3CzmRlCqui+n4mJvMbM0Km46WZH3MddSebv4AJrxW4RXArho+HWmdMLa
d6xuICk1tLuCsf9l1zUrco2C0pNdjuOsd9J1jLQ9GuVTuPE+drrwRtn+wtsO
LWvDZBh3cfx1TI8LQ3DmIn/xyfIVrhU9d99AgpkjmiL3uk9D2AhBBER+cb7x
k4yn2z14cuhSg1gpxC7CK0kIpjn9P5y+PQ9jayA+zBMDzTNCXUjSmZpDTwvP
ajkmXpDhP86a+Of0PMKcZ32KWKq5lJzdfXNPpzkqaxnvyXBIIO1vB12tDaB/
2zmWiP7Hv7zi6t2lusJtH8I4PHuLEvPyMlx1gv6q9EBEJUPUNBbzgvKDIWLW
rk9XUoZvoMdLcuZnD535wu2FWTtsG5jb7zp2ODjKRDKb5BvnZdvaksjLRUEM
vZRMrDEvhdWraCdnaJWl3Bs9OJkf+SIfJy9f/gRL9ZUVkZAUNNw8177abh5I
U1ZllKtGbYnYa7IhBL9rLoJnr5ua3cmFS1zCvNAIaTpU0iHaVZB48CM/3jQO
1Pfwk6stHfX1LLLIFDwnA7V+slHJb2it3RB+XDAdKwsmzm7IGaHkYlgOOKZW
mEUDM7Bx8NshLj71s0Go2zmGZHkPdGrBN9PvJ1dM4trx0BMXtl15TkfNZHxu
mBeFMYAlM0qz1nt440wLZ3HmzmLjaKWcP6eoMV/9By96PM334TraQDNHLCfw
23GmfyTzIJ6d4q1owVie2OdnQKBLDPUzaRbHSU2eOXnG089jPqY4eC2am0vq
3KrOQqz5uSIov2Vhg1X9TDmci0tmqDAMevgpuc3lmOfh/fZO/CrfB+4nO576
ToA1gbO5Cbj1/tHe7miVO0bYyfE/rr+wDPLvr87Cj04U0XrGzglP4N8jqMOl
kxxDKB8vMl3Ly1NKZSwMlu43OGc8GA9C3Lr9dmCUHxDDtkpXtmbfL8BwSwLH
CBNrtm+pajJ3PB0UqPjpOOmP7QZKWj2fFzeavM7tzw23+TNbgP688SsL88mR
zmb7JvL5yIYxyCXogRVKLEzOupCShud8DuI2hUj2Bj/h3gRw4XjrH4vKPzJm
IZyT7VkgSM3rl8u5xNslEaRsD5+/es0HKp7t9fMXL8PGCBESE9RtH+/s7+ca
n9tRumpv4N6XPfd28d1FJ2DtxKm5+hLY7ebjaFGoFYdzgYWGdl0z+JR2xgGw
rUaE/5k7c/lVuaqIxf+rNn/0y5Wo22i4i9aGcjWo9BRw2ySHfKFb/Fu8g7f4
nbFfjinExBFjD+Va6czAOnE+RpaLA8cc9iAGlGZNOnXbGndgLCskWxETKTN9
IoS8jr4eokIzhmTXQiifoyOJRIbCM1+GNUFpW5Bmd3I6TXm2pDkXF9iRm3O+
OK50eiv7McYa8Fg544AypnJ+uh3mheRtFoiUV3NOQiFXKwOaz04tnHJbDPux
/5OV5RN4nIyYxalqWovT2OBaSQhw1oGctpAfV8YLP7D6n3AK0k4GiyWZYqH+
Nc70FliQUYmSt1av1mhi7Gug3A7vRRV9KcWGAkhysDu25kwyYyJl478mCrNP
NI5P96HkwQkEKpfQ+CIhg5aGoJgaax5M041M5RD+gFcFGiRSMjJm9Xey6wLJ
IxVE5ERlz7YQiWJHjZp1ns1p1atoI0qjrE6uB3lUYoc/LT3xpSKBR9Rcq3IO
/DRdhlbmMzen7Zp9Xd+QYYIs9p5XqhTEPCwCkfS5qKzlXcItYscyFtVC9o/B
lZP3CFJXC+XYj0o3j4UfleJ2uxIIugxW5Gpx3eSpMlkRJykKHG5x8OcsoeBo
mGSuGIQtbMsd5zVi1YkPDg3P8+XVQglZ8HzuDbj7pJqQrXH1qO0p2CIcsjwH
5vVEkTDLnEzydWEKHcbPqArXfggwRjP/1frYyyfJp+PYOMhmiBXB18fLWbJC
CULLH0HBKPxOhN0lGaG6AZPw06TkNQy/+hquScm88UafBKFwE8taTWyFJvJ9
tj9m79AwJHu0TfhHBqvvR5Y8XrWyqoWG2fTK3iKwfC8/vv0udbmyzGrGqS4p
h2Gr3LdkA1EWhmthTd3dLjhyecCtxI90Ylj8mRXtgGqWSv2c1cvpRMmmGHfT
JupwPFPwhcdXyzmpn42xRsbBU6waBwrWjYELwx8BE6etWynVMGWbvoBzbjNf
1Ez9JakkmZ3gAGBGw92SCY3RrUm0tPxlzhkhD2RpH79QFKJgPjgHaeRMyNaP
p5gPBgYSpvC4uONJ/H/5QTPwAUPGM2sBw1bn5KdigJzruP0CDRzoekLprSK6
ITwknSFMgan3GuXHHPn3Vf68M5j5Z+9zBQdI+3A12v6KCiCn1IwKKGYQW6GF
kGvHtS1VuSxdhonJ1qtq2WegY8edCYs2itwG877jUxZK+wC1wRAtU/egVrOs
W1uZMHRjH4tXSvxXbUeVjmYWd4o8puH1LSI/Smkg1ySNGSmaspjxDqFuTBlR
64ZUTluVCdUw4f1PGyyDh00dUXp9z1JYeCbLNmWkSMyxcKf07jFmCL16Rasd
jgl3gSm8gozTTCntGlGybGg6aL8n/V4SCwCGlmVJftJIVmXw5Nvv9c2aO/hX
QPzQIJJ4J6pPTgtm+9/ymjV5rfo9L13z4I1GBF4V2h8O3ISmEDoyDQSAov3i
p5szu5CrKhOIlKEyLReZEIhHb5F/JNEFochioNCekiiGw45lur+k9VQUe9un
dh/ZNI2qc+12kMNZz5khRuJSbaQsTCgMNoQ2X/Rat9M8oRrLPn3zdm9STzww
WOUJegsqUR1MML0TGjH91d9TDD5bf0g2FLObgRTqY7MtUbXl3RSmHNiVyXpu
xepQY/FbI52z0mBt+QVMFdangDd4nlIzpxFkN9VgbyBJD7V7jdyQabOzYClv
C4JAM5RHJ1XYY8NlHKGyaGUOYrAhMbe/tmY022/M3bQte9OWgQsHHpJGEHJp
INfTK3zDtSay2Uf1VNzTvpnjnTNIlKsTVxUHtKO2YAvgwvyJ2g/gumqWJhik
xFGIOEqhYpguL2ecDbu95TK1HhvBoALHcwTbmW4Iye5L0l8UU6QvF6kAQUtI
YdX0MsjgGbxwjNIJlw/c9Hv3ileEE4EDFJf76toSbycaTlrNycikkbZyhUi/
WnJanvZFoe+OuopkmC6KyGhPTyA3oEfYSpyB3DMrscvTCqyvSkb3U1aUKmol
2libxLySOqfUHt2dpMUm2TnsvcDZaiyrotkUeHuK0I7uMHgrxvQG5iW5zBVJ
Q8dG/CifyvZVlO0KQJKjaW8bWTFi8KuIJjZK9LH7TNTnGJEJOOIpefFeUoZ0
iup/jBHpf+XFpEcbCnomr8e71+aOjf0ivymdJmBb4S8s6r/m33+/N6kWNTtw
i3Lz++/DOyBvKK9VS0niFHZXuiu0GYTLnOI4m1QhaJiVUQSGmb0RTVSfZ0jc
Rgim0RmKbvRfed26Za4sNBwMLvyP06MgCpOFq9h1JUBCsDUO7+krBEA0NS0m
+GuFXiG7aVgYf9X+psjznJx2LGIssMxqLr2SZFuN2UKuIVNAjU9LdF+fQoJD
HCsp+p2TvkD+tiwnpyJFcV1OSUw0XARrirlIQb1VMZAVCSbVjSWnpwC2kEqs
EI8htjf8ITq76tt2yCRbEQTMNVAY6jBn3gNxEsnF5B8FxFiBS8YIPJFm8Jm4
jxxdItZNhE3uUBVpZq4zOjSJqLxOnVHpbcGsKWC6KDkUgXXHcSHP7d4aDXlx
4fahUFFxtoNPoYGwoZBXS+fwmUfUSm347IKYKLe4DOugqbOJSKFaZjQOfl7G
6WVQO0HzjTjBdVHouNM+ZH5+hULj9SumCS1EXRT1agLOrfzkaHv/XTjg8P8J
gc9RqiOIkxVpwxo5VgTPn9CWZ5UWVNchiJSncA7FtipH8xbe2jmB9AzWSwGR
NhtTwE1wYLBFxhtbq07t+1I/2OXRCpnxAoTrcnvrCIoF99jfP00kbdP6FOqZ
y1n1n0tBgFPdYf3jx/3djYE4F1h3X6vCjYA7Y4lSpIV1ll16CDK5Z5v2KGQ7
BA0uj/KBed0hiOaG6UkvNH9+xjKVTbMEuV6H1B1nYv4ArTsJn8kI9KUJUN5d
u4/CvdZglJrq6EbCztK5H93khedb4nRgvJJtE6KCcwx3BuJUKnmvsmY/HzAF
sHXE4zLhlJ/PiFhnuehpZ+HRUnMdMZhMywnqKPvn1o9ELzssDPrrLOkRXy9H
n0cDcfSEk2AOPeSPR+82BsruQtFq86W60hcuzkpwhtB7QOKuU9Cf8d+fJ8vj
+Wbw6JV3WCH0WXZA71tILzGyRikjk8TWG2nVD3+VWud1nQoObGJtvenq2FIm
qLNYWiyctJ7XxhIHSX2RBnBPZziWWO/t+pen3XGwxsmxRu5dCH/mWNhptun3
8pVwA8CetIHGqlfiQIRQ86vai6qJwm6E4YsEvYZHf0MXmHWZiJQeh8g1pyYY
n795osfCpnsBiwtrVsCCMV+vYoUXdJ7VkRorjmPkVkBUmae8zBvgHInw/Ynq
EBL7qt3zTVJGsh6B8vcrIaGMZMQY0xtZeu79qVXH6xOu+CKlVks7O3Ljchzr
+uAKPxL8ancf1JfAOz0rrlj2tQKhV4sNKfP0skQgI9Sy68ajqT0ykQoe1ejp
1JMyc3QpuVigSLbbTT5s6iUz2CBbRk8SvnrMKNJyknDb8/4GXUtD10vL301w
Lkik8ftIQSAwlnXt0oywnIHr1txYSZ9DEy3kEogb3euo3NILXqzXKjNKGW36
YYCKYKZYncw1hmw/3xbzYzv7eeGbcDkD0NM3pLHuVEmd+f1Z/1C7Aavl1NMB
JKU1ujAL3C20GytxJe5fVpqsTVpnXUaG9gYJfbQV6OpZbHrmMTjVKHjdNDhb
77z8E9HelC6fAwJOGgvBNP2U+2+V+SLCN2dMIaZgA/SEuL7mKsFBZfL6IEo5
U5RGqw6wuPBkhn6JjLK0s1gwqfbkvqu4v5k4k8bznmbioq/6rnUHv0qtQxpD
YOXX+3LFaaY469Eyzfbar8FUMumxUnFhjAy+6lVRza+J6bueZ8TyqJKJBhRb
d31dGwnhtZEH8vW5HJ/Zp9jb5tToBbfYN7lWcnEsNqYKpFwAWMwOddsKVrIB
Jpg/02c2TtAQicCb0uKyGbVmEGXOBzGg+h3lCtWdCYeJF0QubrQHO9o35CrE
O58x/50lqRgGn3HALs2wyruuDEBt2aqEB5IqxMbikkcxARW9H/YwJKYm0pR1
kCnWQW9hUzVC80/ZQ2KXupID3NObR/qCTFkVyRqtlh1KNKTtjk98/EetY2gr
LTKIPNPqd3TbaRXGkWxT7GoS5UKzPUAx9xD0D4Wea7ZC1sEDFtyYYLt1CyKp
UZ1lfzs++DA8OtwBMhDCW3TJs2WzCJ6AzZTEHUY6tpw1CngXXL86WbElVV7p
Q8owmS8wk0RN4SVq6DeJ0hO92/fK4arLnCHrNZiM9PQitSsbFXZXdEAYkCyz
E70RUEzBBhhXI9IAzVVZfMHBF9tdgNwFv7m2CQvHKfwscwmhlMur1Ot30BoP
33fbyt5WAzXd/oUdvJZ0YekeY9kVAwKdCowgQQfNlc4ok5phiy+6tcMGllwK
60EbmfUnGVaAMcRrJKd8SZWQwbMr5sGd5mMQindczz+PqnJxPsJc4+I/pI88
bgvPWmqcFGVfvXpa/uXl06fD8vlPp8OXzyYvh8WPz14PX758/frVq5fhL0+f
itys5fASzdn4sRWWOpLRvhKNGKsHx5RQdgeDctOkNORbeUtcmHk+sWvPlyLj
QouiB8I14hZDWa13WE/S3kYtf8HsppyS3T5DWqd3+fgTTT615NmeVzLw/d3G
cB4Jwf+Z9UqgJxB0gnckLyIqTbax26SCLOlF/gPPoVwh+MD1zyUNXIvxY10R
41U/CdtuxdfHMmv7E1Y+br6E/yIKnu2Ia0ng9aBiBSaHvmz6LYOIjSFVZW6o
zuIhyVWtJunB4L2tfQpeVotur4ZSaQ0Ypm8vMV56s+VjwgTlTuRYy6X2QASv
jlktkVvYRIHeZdCEJbEjn2zCJyAwJg/aaXmpI9223CCglhfQhFPDeof5tul5
3whomNHlFZ9pVKjlsOyquKG2j7CJzG8RzoOlODtyuWtqp1OmPJ2F9CIgeuO7
DpNxCTx+t2X4NgUhEIsAbf8j2sj8AQcDr1O0niQskI4UYXNfVHLYCLU1PV7f
aeYDQOZXdRlbnuAeY52QB+VtzaWwApBSp1gSte+NlMAw7elwjY397Yt8tIGY
kvukuJ9RQIDmM4keTzxZXRW2ZtcmzM5lRa+3yVRPTbohxHE1IYqJtWRp7JkY
JvF7AD3RcxN0/moKu8e7bgFZ8J4TfESMozQvCxYOQwUoOl/o8hKdEgXPhRAz
xL1QPQ+mhLNRt/SfFGOOSai7/CMK5nnUh8m9QEyeBq4LRdtFoTymS6XPJFcf
fOtdPcyc1cjuzFq54+Qtj8mEH/O3dBqxgScrs0r8sZf9UFkP5byBLDzsdFcE
Z3ewdk55PSjHq3D8GuUOJbGnMjR0AXf0jNdw0txz2eLskj7irw3WztyRIpcO
oTjlBMbueBnjZd5zUUs/4qW7d762eCZX+pk9alwtGAl6kViE3x5zWfxgDd+n
ebg6s9zqdIrrQ/YzzKu+w9vvwtQ5fhBywEBJbf6lvWNsHOp0k5+qPB68Vk6F
sFB3Jg3m58oD0zB6DVs08fLh+Yq+wASkLvK2s/ZRVkh1PIGaRn/QZVfOXU4o
0bRv4opnbzCz828z/wMbKHwHy41yvPY/t2eiyRf+PBqNNjKs/WYTf8M9Ea2I
w3hyEcHPmIQokqSWS5BaVspRn1BKnAMndiOGc2BufHKIDSSMO/5SQWzOEIaZ
NK0PuOTnClrRQEoAXEzqq4WTYXZsVHgWF+7KKXCmBMbTsBcpGz1eD5MWppHZ
vXge2S0MY7rl/2LzBNhw59sb40wMHxgGWrPmWBXBP4XIlonq9c1mj36zGw6u
zFLe9AD9PlBiQ3HzL9Sb57qn3jqiN0Ec0+N+E1TsbTP/Gv7b1qw2DCIZEJ5R
XGfOetBkgCqELetdaxbudJvhpUWTex+9LJtaqBGqG3/XM/39L2vACgbhM/r/
vMJhcORSK0yWn37MRcuAt6+2JpcTCymDVa3E/4rR8rUeM1x6XQ8PNzl0jsQu
rhiqms2GD3/953A5r1bZ/JUjsmut9V+MOFKEDiVdOieJIi+tHyJHoe+wksSs
zq2ZPo+d7ANLYMRLWbDHGWSK+ZfKXiPX3syNccfYH5xdR8kDhWIUW7NERMOd
GZreizXkk6Ptnb8fawK4rVpHPzWnvZtptHg2CRdawUJ2T7DQn4x0+YyZRs/Z
A2lHIpJphWGFMqWL7HZ4FhMUJUsAA9BRgr2Le3yM5foDuQJjkNImEoo4nKOm
nZbg8S4pM7H+6C2Kl6NoPVLmSGgDkssb/6Qpuo/95mHLesd5C9ZDw9KgtL9T
7LsL3maquFZJs2Rys55Lk6qHyQVStoGmyfbQD+RH0lS93TvZ+YWOpaSgnTyA
zc8DOzA+0jiRb/pBBG5K3BAJPUV9YqsIAr+rhAP91bglNPrtBpFNX9hIIUgS
EBUNFWS4PrCpUCk2nOi7uCQpC0hs4UQinyIrfy/PlhyfxUH0qN4SLnvBFQ/9
bcRd4ZeZ4XAGiUepF05UaUdIY9KzC/EpXrm0G/IftHo4L4PPNLunKVPjWTZd
hhcrmwUrca97VfTno5dtyroTx7RhPYsWhAp7nlyRljnfaJBQZxlATXYOH2+W
gAXePAPnSpT1GZ9RWRDc7+ORP/0HAohJI3pGgibXj3KwaU9weGJcYZhcQeG/
0mmnQi6wbgR0LMFhxB0gXQQ61w1hyFPJJPmuVm8gwFRIOp9rkVUkiGy06y2T
925/YNygVn3BdtlRgLoESsg1N6/i7KJgxGnVMizdinraUpZVZt5owdmiqRYi
smOCwe5a6XJ61eE/jEgf3c4xDyk5rO7QDEaacF6BKjyCVeeSv6ldkSFmEUUz
fUX5J4aMaZaWw5kHikYhqjg8ODz8N6H99CTjVJbjSV3vVp82GNVbCUXYDtgh
OMMVTMkX3VryucKV+Er6Zb7QSIJ/rYBFHKG6EUU2xpONqEwwdqkj8MuLjIxl
zODKW0WXFAWypB66fbhvTGtyA9IOwcfsM2kNzaermyymvWhtgysdkABqgpY3
oEuUHyj5Of+KLIA9r5nUjHnyRc5kkF+Xp6QmeN0geDxXcDDX4bmZcMhqiqaS
Qg5dRJtqnbeaLZESpNXKA5Z7h4flzU39i+NwQI6xuYk8VneMPhO5VS4TEY4m
awnV91gThqMxbxP6HYpRrqcClbETpHdZSj7LJSFUT6qeW0CXrJus8gZ5QoCJ
bfsGNpwMa+Hf0LQSIyDVvDHDIawQOo5kMaANc+tO5y68pXoOlU+plTGhnGeJ
JkDv51n1v0rrAw434a7f8JaDA4vUqNCJEWa1IG+MbzYWGn78ol0dw2jXNvNb
5DjWbNjho3+XtMdtvkYDovKZ5MjytXI2Qc2PPrxYLK6azR9+oDzaSOLfH/i6
+TfNndxaDiVejIN1+1xm1N0n/u3B++EXP7QviXNtz/2WVF7CT7n9zl9g8+XL
ly/8Ty0JQDNhKSNFB+WcNfwP+f43/H/617fMJX4iAx7vc2yOymOwkLjgVbA7
L84X+dPRi1H+Ed2q+DhTI1aJHha/d0daiTITXyIWZLndirNmJKqA5sMUvaNi
BlDTw++DTY1XYH5+8VRGfTsMdTKqLd/YzxOrGoWg8nUeQQbnn5HtQKwJOc+G
dsJHLAAecxRcZ30N1oid7Fk7Bux7qt4lL92qtF6KIouorNYzmea3zwIzGBtt
jUzMmBgFZb3QD9XJS07+F+nJn3l+FLYYXtiobSjU74j81E1XvAdIcr2W8I3u
MxxhYf3xIcr+yjZC1iYvJ+knqVQZ9iy9vQAYhbRbemfBtdKeQFits4uafDS0
ZhhvdnI/ZhCcNjXhCkPgL1T57pZYXLxcKhZ8tIdHtYpk3GZnN9K7ZssUR0Qs
dh5rEvWfzAK37REsRFoo8GngNfXD1kKEp/Ey/0NKCfSfk3Iaztw1Nhch8LWd
GZN+OxIz9ctJxc8QOKcr+c4a3RqKM9lAmH/I9BM3fVug/1r6EJ2iu/5hE1mj
cEKy+3axvAwLTwRz4n6lS/EUxEHxvzdtvFSahxQy/UcSk4BlJLhfn1QSHWV8
hsJ/qiEV6j7ghTfuHwRPPg3iQz0bTpZz3j6Ulhnib2MZF0XdJ21XgUxdXCBm
YwgEJFvVpalNAC1rLXIGwaRz3b6yNtSq+7lJwjL4kIGuEQooAxwk+IVg/4OR
mBgZj/niBpWUyJQr6hC2JyQrLwy8HiiW7O/Sbm4fANv/BpU35YZPBm7jUi1Y
+LUIWeZfSztxyAkOY1qoTbB55uYEDR7Y5LCoEKt+uWCGiz88H6xvAWdfrgQr
COwc8xkofJbPAOH3DwY+pv0b6c0g/CQDoiyCOUs88AKSgHIj8Ee0reGkxmEf
pc8TxLsS/ThdBHZorfshNkV5knudI3MPY6/Tpcpb0EHGg/fbNV3LPb9vvWNz
N9OPM65WV74HlkLWGMh0eyK4Y6THjxDgVBnhaErPZlylB+jjxp4nGxwsjDvg
jYwPS2p4LPIGzHppWsG8JvRXdJWu1yS+Vpzo03pyE5Z1iiH7H7t/5aOAvUH9
1AJE3QR/XfvGnVF+yhMGKB0qSEvbrS0xw512uMRycASmI2BRCmuh+3YiY5gz
bC/tem/6LL8lMIwsbnoj7S0rEkTaktW6kPR5A48/Tnxwyl50hLlzBStJ95eU
BayYy5w/qtkQcXMDY2Mup+d4o43vk+0N8qTVZ5KS23GmK45DQ12weqNQat9l
0xDOnqv8ley1mJx/z9XRLGsdtwi0+TjpL0b0FiKyx6CWMP/d+gP2dZYS218O
cqVaT7dthYfkHbJIoXqMJezJPgjh/w+ryhGr6o8wTG0H+849BQ1IXYloTwTJ
EmmWetZv+vrhtBen4RIySfwUZy3EYNVIJpxDKUqq4nscpHTVt90o8TglEjtR
S/FgFutIsa190Kq6DKxUEZ20WDA4opQor5eB8J9pt+DZMjwyuYixQKGaxOpX
+b3xdv/du0+H20fb7/dO9o6O6cjhEoc9zjtVY4q4C3D0aYYXENSJDIvrSObd
BZdgLK9qrA+tzxUdxvhcu3DMUv+RLkLTIktYOA+6qlkamtnL56+0XscOQpQ7
x0RxJ81n/DzSpBwrYQrulrfC3Rz47hPuOLYJysRxkS0qqwmvg9dXfJUD9/ga
j/LLyRQDQ4JE4nQmlM7iT1Gqysg2bqC5GGK0LY7c1HfliXVgyIM3f9vbOfm0
u/du/9e9o3/7dLL/fu/g40l6AvEBjhsyb1YhFBql5Y/zMXFj2BJB7hhuIHIN
kyXDyctBppkDq2iM8l9k61p+XM3NxzmDU6gLaNpYxSpbVKr01Gcu6Zf7mgCn
0BV9dX2oSJjiBBiZCoKlidV5iT4dScCthFM6eEd2rNlUPl+DsSWvV/pSUhlL
ILppK2hS93snwNxs9p2ZnRZyWpmcAsq9WKmXOko8Y94T4oO0XPf9BTNGC4Ei
/zXxPkyPzCuGIC8rtpEeHORa2N0rFJnJPPO10Fc5U22JliBTpP6N3DAcQhCa
WjS4+5WeCP16cE29NBfV1abyZkZzoiBRNYpO5ZWGJTOSiT/EMaMyjdoWcbxB
XQ4JJeUncDFK0Vrho2sz8PvsrF5qzY+zZOp35UkTNeVQeEL9M1AIqLYctiPZ
71L6Ml+tpskYEfnOhbbGl6SIflZKonql97YpMSucvKTBDi/fu07im54Dr9Xn
iBItIT8JxvMEnN60YVDPnG1yX27XG2PIiUyYLD6Q4pj3B77qdh6ArcNWbwYP
RW1SzIuxCEOeo1NnRk0PHbCyhRXrlvUof6O+kmgiBzcBz5h2YfYMwVlkp8Uj
lwGgXOZK58Jrylxu8nCijEaT6GhACDZ8FU8Glh62swPjsUx+CtgzHWNec1iu
EX4dvQgwrjAtQl4Ik1sCrnmiwPTsvogg35bl09JUShstc2czuox2VePY4YVO
gwVFHFskSLocg3incfP7zmvhBOJmN5Fhwhk0sZq/Fea8eNbrH2K86N1TOyh4
elzqt1v2PfG53Jy1BrHToUYicgUiqtwblCM4rt0pMABvjU97qImzgDNsqta4
fmyP61CODzpxfC5HyLAkmXHBZSaiwapmX6QPuZUfyHUTyNQmMyvp45g34WUb
k/L8TOEiF0UDiwpk/QL5DPLSikTPWvVpkwIi3YI7ppAuoGxSbi3M3aNXJShh
e2ToTHUFWq5DbtUNE2RnI+/JVz++hvisqoyk9Fe00tpHbUJxrWo4wW+4qDnn
8fHoXbY+vlhckhd5sVgSKfIvnJtpDCPBVRckWvs0kpCPZHqjz/PSdaNqbINd
2zh6N4ar1LOo0sSh+YqVPxA/vY2oEB5EFXkiIjXmvPUz0M0kPmnLKWn7iHpr
VIwuUocFukGRNSAFn5DooRFd2arI2hqTPXrgs4k10LSjS6Z2zLjTHgnFMEk2
x0Ju9HzboSc8zwFn3nCp4aIetrATt7fhlw5xD1Rzg8uZ4xF2hKKuUNeLDeA9
HVi+r1Z7Fay+3AI4O5zxoTStrCo9dMsOsa1FcYGKhsO/2IBw10S7i5B1A/0F
BLT3mCvwV9uX6G2tCQ9H2AaqKSyFA4uENMIpF6zJBJlHagH0c30PZPT56Omf
ztY8DBvFZrEwLPYu/iEUadaDIqXH+4MoUsptSBdfD4y0gxs1JHgKC2XwWQdF
GZHYEZcWHbP47nMbyrHiN5Mx6fUFDxrTD8nlid9pItV24X7aPfiw1w8L/blc
0IJxeNAuBLTd1eOWmwN+Hmuu86TWK7aApXQi0eK8L2kDUnqqhC6v+LI7AIbq
Ff8ghHTbIQIh1UVJgFJbXBPlDjSw83NpvQSmI0tmI45/xL9I8ak+ek9gqkRZ
HU1BTGQ3Zey46MGWcgoA8U+4caY7uLfvf5vZZ7i8YoW4JmLSg9edqUcfvim9
kq5GE509a3occLu7EL8iniYSP/ejLnlVlowkha/S572ggRb21PEWVQtRaBTl
c7u18Bg3Si+EyT+ns0TVQysvZk0ZynLKxBCaARh79iRVC3Z4g0EmnmekO3DY
ABlRpfcVjJl5zOSXiZWLsDyxZCl4wDnJmKLE+ahIeO5hLvCcrakkZQR7eu5F
G7KwjnA6ID9rTJ0sCRrxbyoa0BhAWTPpYWjZPceGJ1cKD+Ea0MG3H7slIOij
3XLJDPdGJ2EBXYJXVSQAsuTKM1/HWdl7SwNKORRxKFTUjHG+YPdSeWcyRQb2
spywoxJ5Tgad9lsqNWaxBze4Str9GN0lKorPr85aGubiISkVuSZs1VMSrb9S
eijHK2k65DTUgJI/m8Hyc9Ahv/tnOwbRmJl2DFqzMrooetoGYy3bocdcA3df
w3z0PKxF/r6OFafR9bADcj/Rx0POCNXS7C1E/BpfazXBgNALAGeVjVuTNgaF
UUpOCuBClGZIcxHsjiffR7drWFSc4tTmubDcP8+LGS1ngwcnP5NMCuhAVaoi
c/vGkOIEOA8f05Zv0wkZ49qsvM46lxcU8JzvkTc3YR/9LtEZPpmXSXyTcQjK
toUrx0XCMssvm0N/ZRRigV5iAoanII6mMsZiNUQeXbb3q9r7Jdm+y8ywZSvT
Hl7FRP+CBNH/+sZSbp0pNSHce5PKLQnesGU4zcyyXfyoqbgX4mgWDFNosWNf
SQ0qrclu+ohFRhvpMUVuupxkUa/nhvnLwJ1KUSUZkVYCkbXWWN2m9QhbOSWp
h1NU1sSmaNYh7MPSCBwIkzfjYDAPy+2CsS4zE3pKmZNGwR3+Wn8Rxk+NDNPV
RhFwxuyvxtaVZFNsE7AIAHi+le/Lm5FMdaPEpVEJE9/ixxhmWyVKp5T5aw7d
QDpLS3f5NrtE28I/HFdY5VmJsz4G49tb+nC4/fHkl/8nnEPGr8IHrFDu3Ej3
OjU4zc+ogNLie9h0NMr90vQL4K71UfUgnwUzyQyclOmMdxNCWea6TspUQMQK
Y5m+CoEqqZ0J7oq03Ot8hIuDgIrJJzL7XHLO7OfDhxG+bQpelakijL9GPSL8
wAir63O7CsQxtGAGxix6HnQYDPLf9t8fi4weH4LxwCYCYiQqF1gWlFbBQ59X
zM0v/N4pd7dOoYKrhAxXVMgS2T338LRxw8gJuCa5axEBFrku7iQDD7keGMzn
iTEEM3ROzVvhJAjPPr+5iouVpGefjV6Yt/evH/d34hDo6nCZOsr1+B49PF2g
nrm3Ta6dDoaZ8TwjOtzWKN3Ry44uZ8tCQb0tRvWk3UoSnp4BDPdM6eUfsLyR
m5/dOo1Qfhw9hxt5tPPLt2+ZzQrTxUZtMWy2ROEoi2XapqGYzLjJ+04JyKUZ
OWXWXGDmKuisY/Z3wB6dy7l+wmve1zsIozB1AL8h9F5bdzPhP2oNYCu0N5tQ
rm6P6fBVi+n2u/I5zJZ8QKm98Jblg8a9a+qB6ywNFBtrDhWkJ5LFoVXQBYGY
isPofTS+17JT8pblO1nLHRTJk/gQWPtlfiC5kjBFB/86PN7b+Xi0N2TswDGp
k3QZ9Vu6RKyChOfCLbS1E7VOHUyUvSq165OTutdFCjqVHyi0SzI5A6H5o7CS
eILMBZX4S0l+xtFgjlfT1ZPLVG/poKWQAS5FcCcXExA7citt7P5ehXrL/l7e
yLo0p7CwQ1iy9aKF2xBDEIvJC4yeBQeCOxF+lbzGCvzPwZ3Qcn58DSPgioiM
ueKW17DgpCr4/GnYfNz+fBUVYzg/T7zq1aItNxlVVIVqteVgaUGFxbrtCS4Z
4RA1BmS/p+8t46Q4zSnQLac36UN6H4pICGFT6HFojQ2y9GKYQgSjy1k0zWQF
mK2jpfJmyuy+L9JOaGaBl7C/x+WzEnUiN8IT2BJBCyc9/Zs2E3JYX2tlcaHf
f6HVocDtsLgxNm3aZD+Bfl1Okqq7CKNgMUav0cp9sKpFW7yzmEyoaIXZlO3U
c88quXpWFvNpFa9Pf74WiRfC9c5MDYTABG3Xvm9PmCyIbCwY//AWFtKeeAKH
mVEJA6xSB4/X8G+QkUIhYihDS09y/cxQo76woS4u3Byw4mZR8a7nVPCHQqzv
i1EguCAyPBxdNZ1ZTaQK9da0Q5yIkOZEiiwW4SMUHqeV+V3pGaVxshbsGevF
FzDmavtx5NtyTU+OhMuiBim/dauM++SCuUG2oMFuqNQwFU9G8gUjS66Jaepa
khyb7l/juibHJ/OOs5DBdiVa5q2Z9lp0GUt49mzeE0wOXnWsi2UML1FeRByg
58aJvwJk71DrWQ+xvwCB2+LYNKkiGJ1qR/M5Vvbx38O7SzlmNZFEd2YuqXr+
OdhbB7BQ25yqMo754UE34nV8WeDlalFDeyqfVjBn12IVLkVIg62YqO5VMOLA
cLDGmHihtSU/LUHZwRuVfIetlqVio4B04udLdmOnTDVjmQypsPCfhc6FqjP8
SVQji8aZkQGLdoTLdYlBhqSOy84Yss3JnM+8vAMFVJPLimvMdMbQipvMi2uE
sdajzFdDI10j2AQJhYPdVJuC9y1Vhgj4ihOqbAyk5WR5X4W/x90m/ZEqfDYw
KQai3yom5SgXwyuItXPqt25DzFgbkVRVwubswrc2xjlcatU0KrIIqRUFsfJ3
Ch8qkhuJunkDokw+k5OcRX6JFgJBJPWwxDl2xgO+ETvo87gnRIpInR3jdNzK
ImYhAjeZ4IOgUq1+kzalrKpSzOrZzSXpcvWfaIX+fdh/thGDskdFLsrpVOn5
+S1JfK5gEj2rEPbPtWwjNN9cZDm9oVCN8DPJaRKrYdxZZGyTvOnlpFK/FaAW
F9AbrRcl+RSo6JFWmaYl4lwz+UTEJ+L06sJdGo938W0FfE5oLHF4GE+ygZMs
xz6ZkbciAnN15qeUyW7T3U2YBm5bFvAhPwenqCStoe0jqRctkn1hKy+A6GEL
K32tVgxqd8Z5xlwBWKFdTNWL2P9KPLY+GwDNx8PD4fbPex84mvqemdAx5ieS
Rh6o6z1mSdBPVTCh44HaBw+6U9rd6CyZG9Aj7Ynzbj2+DOBlJSKOnswFpAS5
ZKYKA5BsvLyKgTcvqiiakeeS6uA1tp485kZkJSlkU6C7jRGyibQu9BO0SUnc
0ogSk9HID+Vm1BHPPoGsTIJkubUJnyF4tWTCxHcz7kNz7C4BSU1so5H4RavG
92cwslzdRSzhvpL3TeY4eFJdTVj5Na2icAnmTAwLmVYIU9jIDnCEPJQUJai/
elFyiUrOS9EL4emluIdJ0xqd97jTXW2HjgmxwExdDZo2tlj8A8L9uf3TLIit
yeCHLEWnmnfIGWUdsFbbi9vSWik/ABCDKQ0QoY6twYBfFE2jWnkz7KgvC9xN
wSG2/fWMgd62UNqI6dqp4V9qjYaULlhtI/PqA5FkTEOqyOuSr5s9aFx+M/xr
A+oBBFIk9QDJU7YSXhzWULIECxcfBt/5PFU8LuPq1NLbGb1TVfYuZkZCTiAQ
I/VxlEDy9nEAZ1EEZFrXX4Ll4+9PpPu2QrEcemTzqvki2vU36m6x5sdl6WQ6
RvmuOyqIifkz57BSeFFXksgmLFpc9LwY9MAhChgxax8M5UshugZKXVwEcS5E
t1sz6EQeSCaSDN8oP9Zr5PEaMVoR4Go8brW0xQNoQTa+z3trVvQUnNUvY4gS
nP3L5aUU6xhtblUjtR9O8CaYytZysfAchFqnc0pA5VyXBJRe2olFIoffm896
Sy+IQ557BZo879WgYatTzTvgwSZac1Goz3WE4rIUi9gTrbUeWM5e+SVtY4k+
nPGfcYNC13NTLnYMNJ5cbJhjnoscYM4HJL3DvCXzuAHSHTMvhxUZrMkyRi2z
LxRkYlvQB667PGef7uqqln1YfK2ZVV+cb87rRUuUm17Dw14aac2zn6b2mo24
YpBTx8wf3ImXBpQzrCIt5HsdWn9Ww8pI0oYJOHM5GrxRLCj9DP56QThqsG8l
S/hpMUFXcsq51IYEwnVRhhftLnIqO3FiPtCqJM6A7eQ23Va2nVfHu9UFVCS/
OAnHGslEUTy92eKiDKWEq0mp7SqUv7mkbBtl3q0oyQ8bZ8BF0fn9ATZHNRwB
JY7pKB9/CesbnBbBD5gXrDTPsH8CvYG2BXx4sHO8WHjrNswyqF6SAynfpBlQ
uV54Yc2nYCRwQfI3aNNqLJGe9jJpkzLY7XkZC07+ib13zJZ24O+hmc5IzYB+
AYUgMSvDFTYS2nzKOU2LXwDhbJ7RgKaK/opqViOAYC9qoJqoLyFOnvimqqAJ
rXH+7iCMEvLxs4TyLudm9DBP0lhK3ZnT6ktvv+lA5LN0dXE/MO2PsKIvCDt0
bV0HmN8QRFMMjLQYgrdCj/4bs+CiHKibWwGJ7lCLoLjYUnmkNlj6IluycNLp
lqrIkVtBlaa3hMeKgoi0KCfhQCYVePEu4pF8n1aaNuqJqxBseZh0MTctqCNH
2SqL3MTe1nkJPTa1HlfUZmw4mvDyaWkpJ2Imc8TZKZseeMUE17PZIVjQcdjg
8nyYozCCSv99+10T/6reXzUL747iL9EUFgZNryNFZ+znsg5H8NUFqUto3YZq
9HQPGMLoMcEJMpkpL0Ar74c9V1H4U65ck51aXjEMmeIjF6Io6jYsbRxVHC3i
3ggsJ58tKQB6UJtbhmOmUrh6sbMlWr/m9JKH4aGuUG6Ynd3YkZafhwVC6trc
xzqtzwhJVqrKHElbXAjYUd7fTKSr3vIPAbVq5F0oSZ92/EGamGKgJkZpekcB
3OAn3JCfKFSbHph85Yby+NsznPPh+VFw8idXPffFnLB9uRJslSImOQPBQwJD
Ub5GsXncaLlcUGM8UEOZc+Yo/A/X1B7tnHtM0oHnNnAN8SgzQCtX4WtpvMKB
Xgi3ymLRuZKW3589jdX32BGEikuWJQAEQjA8HR6dnEA9XTc+O5u05ZITQbcr
umW6+XnGkgAWy8iOnKXPz0qGfOTrCTorYxzWoIXQere3/Wv4cHdv5932UfgP
BhsNYt/+ID/e+/n93odwBUazQyY0kbmi2YhPxaomUdAsLLMyRMgm2n7uXVM9
b6R/M64REqHkGgxoAs45cbDSFxCPzi25TE5SDhScxndYW5QPs0y/Pbqk0t0Y
xNWmVDQmmMaw1b0v9iJJpiHjjfupmn3wBAilzRGSz0yU1ecLyZ2e3khxbSLp
kVYCDr4DJwMmnIuWWihqBecgKtB0uRzYnECWSkFw7SNo2EFm4EGjtW7rfmHP
gozC3AP3yGLO+NhsCnhsjkf4tGwXb5kYhsoEQlPlnHT10SuXoFJBeACmW+UV
8d2YDBj05eDAGENSQ9+psO7tluKrZlxXqy+lN/1G3xnyhSGcnyAQZoT19EY7
53lMcPhCyDnKDgm6WeneQ1CYXyIlVQe/qqYDhye+jrHylDI3LWQRN82FgfDT
hMcc81E0Njd0Edb/Jy4SjRngQCuQo3+2mdVcpO1wtUwBY+132dJnTWE+vJL4
qkirBZ+/ZB7KLoBPrV+zGt1BmSOquOUkIcZZDkkHNuUZlaGtvkSFDlhqaeMD
R+WmVFT0LG7CWKC1iolQrxoJZQ1YJmWYlHkGx0S6wNC6Us9bVX3lxsYCk0I7
5wHD68JCs5IYRSV2gCMo7DJnV02sXU1ZmTtTCIdUH7QBZqIVNxGO9b3uumAp
SEqrbIO8J+Bqv1x5KB25MxTaCKIFRuWPGRlEwCi/wfhBMsM3EbDE9pQyLPUi
j8inUgAcM9RFO8Nz0HZyeztHlkUaNDJqJY1XXtQ1aCpbeKdiwq05Boc02AvD
gmjrcj2VGK6T1zTB5ucnU8jd6Y16acRbkKGUYM+sj2vhMxGWS7NDvzMOWB9o
gThd3ymHhwkJh8gV+bGT1pmphyiFYtOJdwPQzHTJ0Satl7SCW89b1pVGScc9
Flkb+KqIUyZcUE2niueKZjlsg8wgcZP+Qq4CjLm2SN2a2gNiQNpR9k5D9gTQ
fA/AWMnrJfmEHRShavGgwdNecP0pN+9yK9IVTFWHQLi2pBpUYQ2k09GQ/i2g
AUsw+zoAOc5/+37WymVwpwbxX/C3m09FMNazWgBCctySTeZ5Jd6NPa7GYzGH
yWqSpKcTZkcySfq90U8UdnHpfsutHuH5gylKDZmuifVzJ3gULnhytL3/Lisp
KLm9xT842YQ6WtEqkXSVYp0TJesh8d3jSwhLb8e9g+JLiXJBJIwJHw8Xoh1h
uxRzMKXuZmpnEg+2/UhNuWi5w8ICoKy3Vi4Mxhp65jR3elU2rsK4MEnYRMij
Z2/ea0VMUpi74m3kZHMvSz7JwiFTn9NCYirMmEVeKDBBmNrPUTQIdm1J7u+A
O+gnE1JW4ZOh56Rdfb6G0R/sHmzm56K+cpZEK4hk9rc/bHerLlUIkL8J9ZI5
g8Cv4/tU1ED7KV5EhOZwRkcxitw1s2bN8rTsJJ0SHInlTM3snpx8+To93Maa
knrBDQZ8iO5y7GXX0NRc4dDm/pjb2/929HbnL8+ev6bQkpnDQFmMmnKGzNYA
Fs8F6RwsWhfVSLIMRxznH5VFU8+EiAc6NtgWfBCDkn6qDBtjHsV4QKoPwYP6
XIXlDj7cJTKo5WR4Pi+WyCLO6iGcs8nwajmn3DT9ajm7RivTUHw5+mIIO5aE
b4c4ls89jpdXwZmclEOKWSqQ52Zji43cp0QrPS9hFobYhaWOwD6nnzZLOj3C
mp+0EptDRdKQv4y3oXPFSL5UKJRbmHn8+Zui4RKBPBBpM1QrJ5DGELMnNEbt
Vxj6Hhf6A0wFZigb05qfDuvTafXZeIY1JytPMgvx4KrBZ+3Bb+sk5++Rj3wg
aZw+SqZrIZoPjKe6nDCxHNEB2gyT2zskt1cGl62e2fwAezdKPLArxrlT3dpy
92h6jk/2j344/mX773sfhCVF2ggIQi+iJ8FoXF3Us5tRZ6cTS0ay3e1+6Ybn
PSYSCmvH5WJ5lR9wlX5NrQE0FBgyGQ6XD8eHB0cn374xeQUR69+J/mhrhyvH
webdJlMbbLYYD8Lvn/7+6unLZy9fPH0Wfo4OAQoxmSjh9pZEA4YNjWloMPTw
3pgZ+r/gcdFDY3rJO1S+qc6sd5NaD86radmZiN8OT4bvj3/GFHyv38IcbArb
OlXRop3azP+2c8yMS72kMRYZrOBqmpeX4ZydIElo+sgt1/MPzMjYNaVAuGHo
fdz//o/rxVh159fe0xGHt+xmYWBh3XhxczUWwl96QPTjJ+nrv/12IiAjWikz
zJG7PyNDFvFvvePBk+txEYKqy+Dqz5vNfPZDQax02kPV/dOe8Ne1zs1NKogW
85stfSPtIXMoy/x8QM7851Kas3KSqHn9cjkXcrwwIjEbGu8hx8n1L/JjydQR
e833MeXYHkzrVcaAU14mVfnJ30CaRLLr7Wvw8yqV/STVON3sXG87vgIJ/paS
Osrh1UAxY1P7MqJXFn76dl5w9BkrPCtGsy2os4I6TbmJFYN5X3wOXthsSYt7
vdnA17fyt7SJbJvT5wQvoL+8L4JRXdQNdbBRyoVWC029/tYYx7hOc1kET19c
LkZv8IlGi1b9qGQ8x8vgY4SbfSDKiy/LS4KBNDP+x/88o7rQ6Ky+lLcANpMl
7dvNfOfg/fuDD1id5DRF8jb5O51dBmeQ+zx8lx32paJLvZnv7528VVfQuWjn
Mc3u+AQG+d7R0cERue1NrZAs1Wm0LRKOjGCDc5IjIi9SRaUptDwHaPv2O4kw
htf6mXApqXo1d4znzYV0xTdCpzjjVUC7frz7bAwy6t0fQSQ7m2DQDuCz/vHj
/m6zMcrH23TKvtHzdQdpMKq9cWaN4WkGoWC9jWHBPhL956n+UspiYymaxEsw
guQycuNpz4KKhzlgAkBrbwRAAmdUwy2OWQsh7maAO5D3yDB6RIuHt4tLyyTY
ZcSPeVpjIbgk3EMER/cg4WM10kdQQKp5ZsFepU5BJI8ca+XCRErC/7mmOimh
7XB9xw8sfWR1O3JzpO3Eza2tKMAbELktgzriE3AWm+57EaJTQ2nqq2BVJ1Qb
he7jJkrnOFV13CssmjDRYwaKuGcUYntfPnURre0UurmxSyV9EM0FJek06+Gu
bKEGv+fVZAw0KXxOQoXMX4ogQZFTX9RK86i8LCLg1DRXuGQapyROwzLjip92
agOCAyYVbBGiRcm2+eh/g1C3FoYhwaLpTNMzaoOaUJSIkbAMDlNJccrDNn1x
ejovv1bSUcmcHduxuYKsdg9T6bMooS5y6Yv5dE2JOrhyJRWrhMLjkf9j5asH
76668Alp2tr82dqfua1VxOldvnn8JJz2TQIX7h78ZXwAT9r2Tz4BRcdMgPIM
oNoHJQDy9TCc/OkgrLGxMPuPmWUNBixp75i55odCdLzc++Cfi5irPSYrOLxB
yjoOY/tJaxipYAFPoY6XVA/zPPk+hBP88wlbBZ7mGZ6GGbPGKcF/xRDAr+Uo
e5leYCEkPAou07lKSdnCv5+NNzGa2zWh21nbXHs+ehomgLEz4Z+O9y18jLO6
Wdu8HY1G38I00TfCW/42xg4xBqA+CeTFRR+XnUhK3MMgk72iKU8fTkAT8blS
+jh6sFH2Op2UyAKPiX2+QZflxLf2JkBlFagqlKTZpu0U06mwaJAEIamQM28a
8vXi/ilXjBemDV7AeTMkCd3xo03S816T9OB3W8rkazQ48l3XNmT/eanmh/ef
CUZn8gCPGbd89VHj1u8+ctxiVB4ad8dkUE9ecggznl+eKcUmyK7bwBZvbyaa
C8p/cLN8/pQDZyfg0ATf4We0Xf84EJEWWZn8QGPbi1ihD+66+Ar8poMOIe04
nSZRnpl/5iQOfYXgOOErP9Du+iG4O/V8MTprvq590+26eAYpmmBzOi/X7y0p
ZJ5XFCpFiQR5SBGIw2P4Z/TqwqseUkeB4yLcikbN/3UCMcg1Pfvl8aScubb5
78Ho/Me3byKVZV4S9AkI4dySUFZrlOVGjM3Og6mO88Ps7+YX5dTEoASHJEAl
Nk+Ru2xDjK2o/GoKvKAuMGqb1iUhJCV9RDhsVoBZPZJKEBkVGBptuWLZc3Oa
xhRasikh90lFkhBxClSDfrzAoAqCdk1LbrLV3+W8FAAjYEl1fAlVaNDbRYkl
dr8marQzXgL8hh5tyF78AUP2YrUh0yfdCeP5Z43Zn3LiPGemm81HPL59+VET
EL/9B6bgkXZRX/ngsRYyPuc/aSN5g72yg9o/y9jtS2U8DYtdWxriOuWOtLF+
gAa2lX4LjMvnZw/aUvq52dNkigepPZ0Ws89Lcn42165uwhVnayxju4YYCRbX
D4zv/u2bmNieFRMn5bxnUlo2NEcSSGI/caIWTKVBeQ404Mdda3MWgl1LtDWM
lQaGrVmeMjmIhscOfcptXbEdABmGqmk5roASMjxVKl3TMF12IcdxJ2G8DYp+
7fhZvUnNtxUbIg37ct6E1dTUFDBTJR2aXnPq04RtnUhvJLBrsub2dznwZ7lA
W5REpSJHCrxUjdf1pOOLwrCf1ApfFJ9wkKzzcTKxP4hxIF1JOS5J2QST3Tow
7W0nC74zD7Zc8NK5VD6bMIq0c6Fkncgu0UORfl/O5/Vc2gR5zcREhlIyCEwK
9wT0+YqQZ+FTm1GeaiXgcUuIUR1CHkNvDepg8rs7SqHz99rs4fa/VGrJ+X9b
86pLZrwZlzTsyYtBvnYYdiQOzct6skQlhK707PFXeqZX+lk2HhL4wWfnKz1/
/JWed6+0EHHXcKEXOQ9rHA3QWNecRUqf7Zc4ctefvXxOHQRlQ/TMt5v5olpM
y39ZO+h/X0elAH3pUrpAyI9YY8pLpOjnyyvJyPxaV2dCO0+uBamnkoylSNaM
P47zdc1msrbqcDneGITFM/0i3AFfcQVBj4x/HWfuB/xfXylK/VUJ8mlz8m/Y
3ShwHsu2XAjetM7GTUl4e/FwKu07FaAMezg0HsDVoT5Ey/FX1OEXrOWZNVdl
IXSHE93EMJd2w4KJE8SH+fjgIf5ysMaT0JcZuTc10v5lsZxUtf30sjqb11Qj
LbNfHzMImdj/K0kqxlM/8tbJY4T5Ls8uHjvoYCxs0HNetWwq7/912xnidfJP
h7VuuT3mBbivt1+CItv/9NR/2t75+6Nu/Kip+EORcmOO4K8rHMGPKxxAwcBO
2Dlxk2nNLdfEm/fcW4KF7GH4LPFI5WVkHiKW2DhxfiiS/UxeG3iuUQk06vj1
F8+Hr19sGG8BML30oxXqdwPn+egiRDKQFug4LxaxN/QrnIV4p9cvhz+92mBO
dY62av/oA7G/LxQcJzatz83tGDiVToWNE21DtWej3FkqZztyTJVMHLxhP3f+
QdFSI2UUYd2cc+s8vZ6Wb5WkGCO3E+p/cJF+FVRrfKNP7C1Gpowr1K3IHLs/
0WyL/px7JBEo6EvoQpGgIsj61L2Jp8NnrzZiwpEbrcdWQhmLYzpekGe6GCuv
t3s/OmPyirpeGZ8fQ8oBDAnxERmHXDzILYCcMCwuhNyEWuhlNamTxedUMaVE
yQ2p6ywNRs6dT5wwAiYR7zSu+JY/TcWNVyPCtJTmJUutPL7qi8J+UnHnVGSV
qObYUS0pSe7GD+vqisGfdi1rSMHC1MHQJcLjztWJjkRfhCEVEWvUuMJxvWDR
N6RjvaUwbaHwO1kBxP23c7jayR6YVzxwy2dWWxrGebXyslvqwVlidnn5hOcH
D/aYrnxFvnzPSgzLnn5LDnQkm0meXTYCv0CuObDdC4OJWSEOxBJTx9g4LBgu
L4rLrvQ89N1YPIz7GgQsTSktN+jNU+urKhbh0TYNGQo3kGinsJUjDWTJeN7C
bigY3Eyb6vc9hUh4RC7Fo8I+4c4oihDgwULpWakPs3SvzFgn+aVAuK+L4P+d
lmFd8uOEsV6FlUh7ZaJ7hbrOhLN3pw4XOq25vZBxoGiwHB6imYL5AVjbQBUJ
ECNhxZEX+oaAmtflqX2oQqM7QHCCk2JWTG+ax+e4Xv3/Wj/s3t37WCxjjCzG
I4qAr/50EbD7Sz8KVll68JeDjoLOmr6l4Z8rIZ4zcKnJdh7/7Gd/+tnP/vSz
n/U9O6/DqvmTz544dwkHXQJubyuvt2XXHaYki9kZfMj9fUa4yaCIsCfHu6/G
W2SQrxhzf/alxT8HtEtJoOBRf1U3VnCxNV0dd2Sf8aPw7zJ7RbyZt60xkUAJ
UP4MBiopqFr2Euwcbp9EP9AjUeSsTBNTNaMtaOZ4VFBeIRVDuHK+XKkrEVeP
q1ozRjfidw0wUGPuZadRrNdVONHZ99qRsuObJ+7C6YVa1Wd00sh6Ej9jHNfX
GO7EtmGGMGlK6ygTFFbK5WUxv4nT03Oo9hRX9yLLJRAyJjjswTuNKmsmSlyi
CYPJ2AGhEfOAEWqt/jlc64haZ8I5ByUl+ez2Vv7r2zfyq+nvg/xoICwshczt
WbwcC5cP8l84uVUA07qw7MabkV2aParIR3WuGVH4R0cmO5N9Fhkb/SaRf7Z0
bL5t8O3Ha9QMGn6wZsnDRJJPIFU0iToMrZ57Va6+Sjt5t49Wi+PD7uhBM/l6
sCazOpx3DeX/7cMuufuAZXVsAmU09ezrnzOYR+S3AQPyJAefZPbLY6YDGZ6L
P5wb6vzSHxq8JsNLDL7QI87t13/63H7tT9//2ukk48TTqOmFI0kvjHdfj83E
/4IF7qE6A9cPLLaIH8GXMHpsOb0/t7uZh2OeX1VkXzQrz/E0nL7GdhRFNCxR
lOf6hSeNbbTPFPBQfATzLn67If8A+6FZ0pAbUXQSddvhwZ3u/vT0bEB0Zhjh
uA4fhV/6QM2URRTxnKIz4S3xf4VHBEMSfTyw+S7Cv6up9WEC8Ao+QhwDXZob
SkyM/3339X+oia+F4kLT1oTM5YP+NR8dR/cBbGKlBe+FDgAWbjqjAk2I6LjP
mEHE2f8H4v+NnO/JAgA=

-->

</rfc>
