<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-liu-moq-feedback-03" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title>MoQ Feedback</title>
    <seriesInfo name="Internet-Draft" value="draft-liu-moq-feedback-03"/>
    <author initials="Y." surname="Liu" fullname="Yanmei Liu">
      <organization>Alibaba Inc.</organization>
      <address>
        <email>miaoji.lym@alibaba-inc.com</email>
      </address>
    </author>
    <author initials="M." surname="Jiang" fullname="Minghui Jiang">
      <organization/>
      <address>
        <email>jiangminghui2003@gmail.com</email>
      </address>
    </author>
    <author initials="R." surname="Wu" fullname="Ronghua Wu">
      <organization>Ant Group.</organization>
      <address>
        <email>r.wu@antgroup.com</email>
      </address>
    </author>
    <author initials="C." surname="Jennings" fullname="Cullen Jennings">
      <organization>Cisco Systems</organization>
      <address>
        <email>fluffy@cisco.com</email>
      </address>
    </author>
    <author initials="S." surname="Nandakumar" fullname="Suhas Nandakumar">
      <organization>Cisco</organization>
      <address>
        <email>snandaku@cisco.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <area>Applications and Real-Time</area>
    <workgroup>Media Over QUIC</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 60?>

<t>This document defines Media over QUIC Feedback (MQF), an extension to Media over
QUIC Transport (MOQT) that enables delivery quality information about media
Objects to be reported using Feedback Tracks. It defines how Feedback Tracks are
associated with media Tracks, established, forwarded through Relays, and
consumed, together with the MQF report format and capability negotiation. MQF
complements transport-layer signals with per-Object delivery information.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Discussion of this document takes place on the
    Media Over QUIC Working Group mailing list (moq@ietf.org),
    which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/moq/"/>.</t>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/Yanmei-Liu/draft-moq-multimodal-feedback"/>.</t>
    </note>
  </front>
  <middle>
    <?line 70?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Media over QUIC Transport (MOQT, <xref target="MoQTransport"/>) is a QUIC-based
publish/subscribe media transport framework. In low-latency applications, a
Media Publisher can benefit from knowing whether media Objects were received
completely and within an application-relevant deadline. QUIC acknowledgments and
receive timestamps provide transport-layer information, but they do not directly
express these Object-level delivery outcomes or application state.
Transport-layer feedback is also scoped to an individual QUIC connection. When
media traverses one or more Relays, feedback on the Media Original Publisher's
connection describes delivery only to its adjacent peer, not the cumulative
delivery outcome observed by the downstream Media Subscriber.</t>
      <t>This document defines Media over QUIC Feedback (MQF), a MoQ-layer mechanism for
carrying such information in Feedback Tracks. MQF reports are associated with a
media Track and can be consumed by an adjacent Media Publisher or delivered
across Relays to the Media Original Publisher.</t>
      <section anchor="definition">
        <name>Conventions and Definitions</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" 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>
        <t>The following terms are used throughout this document:</t>
        <ul spacing="normal">
          <li>
            <t><strong>MOQT:</strong> Media over QUIC Transport, following <xref target="MoQTransport"/>.</t>
          </li>
          <li>
            <t><strong>Object:</strong> An addressable unit whose Payload is a sequence of bytes,
following <xref target="MoQTransport"/>.</t>
          </li>
          <li>
            <t><strong>Media Publisher:</strong> The Publisher of a media Track on a given MOQT session.</t>
          </li>
          <li>
            <t><strong>Media Subscriber:</strong> A Subscriber of a media Track on a given MOQT session.</t>
          </li>
          <li>
            <t><strong>Relay:</strong> A MoQ node that forwards media Tracks or Feedback Tracks between
Publishers and Subscribers, following <xref target="MoQTransport"/>.</t>
          </li>
          <li>
            <t><strong>Media Original Publisher:</strong> The Original Publisher, as defined by
<xref target="MoQTransport"/>, of the media Track associated with a Feedback Track.</t>
          </li>
          <li>
            <t><strong>Adjacent Media Publisher:</strong> The Publisher from which a Media Subscriber
receives the associated media Track on a particular MOQT session. It can be a
Relay or the Media Original Publisher.</t>
          </li>
          <li>
            <t><strong>Feedback Publisher:</strong> The Publisher of a Feedback Track, typically a Media
Subscriber of the associated media Track or a Relay generating a new Feedback
Track.</t>
          </li>
          <li>
            <t><strong>Feedback Subscriber:</strong> A Subscriber of a Feedback Track. An intermediate
Relay can subscribe to a Feedback Track for forwarding without consuming its
Payload.</t>
          </li>
          <li>
            <t><strong>Feedback Consumer:</strong> The terminal Feedback Subscriber that interprets MQF
reports. The Feedback Consumer is the Adjacent Media Publisher for
<tt>HOP_FEEDBACK</tt> and the Media Original Publisher for <tt>ORIGIN_FEEDBACK</tt>.</t>
          </li>
          <li>
            <t><strong>Feedback Track:</strong> A MoQ Track that carries MQF reports.</t>
          </li>
          <li>
            <t><strong>Feedback Type:</strong> A Relay-visible Track Property that identifies whether a
Feedback Track terminates at the Adjacent Media Publisher or is delivered to
the Media Original Publisher.</t>
          </li>
          <li>
            <t><strong>MQF (Media over QUIC Feedback):</strong> A feedback report at the MoQ layer
containing per-Object delivery status for an associated media Track.</t>
          </li>
        </ul>
      </section>
      <section anchor="scope-and-non-goals">
        <name>Scope and Non-Goals</name>
        <t>This document specifies:</t>
        <ul spacing="normal">
          <li>
            <t>how a Feedback Track is associated with a media Track;</t>
          </li>
          <li>
            <t>how Feedback Tracks are established, forwarded, and terminated;</t>
          </li>
          <li>
            <t>the Relay behavior associated with each Feedback Type;</t>
          </li>
          <li>
            <t>the MQF report format and capability negotiation; and</t>
          </li>
          <li>
            <t>endpoint behavior required to generate and interpret interoperable MQF
reports.</t>
          </li>
        </ul>
        <t>This document does not specify:</t>
        <ul spacing="normal">
          <li>
            <t>how an application adjusts encoding, generation, subscription, or scheduling
in response to MQF;</t>
          </li>
          <li>
            <t>the algorithm a Relay uses to derive or aggregate a new MQF report from
downstream observations and local state;</t>
          </li>
          <li>
            <t>how Relays are deployed or configured, including path selection,
Relay-to-Relay monitoring, and path remediation.</t>
          </li>
        </ul>
        <t>An implementation can use MQF reports as one input when adapting media or local
forwarding behavior. Such use does not replace transport congestion control, and
an implementation MUST NOT use MQF to bypass the sending limits imposed by its
congestion controller.</t>
      </section>
    </section>
    <section anchor="motivation">
      <name>Motivation</name>
      <t>QUIC-layer feedback mechanisms such as acknowledgments and Receive Timestamps
operate at the packet level and do not directly carry the following MoQ- or
application-level information:</t>
      <table>
        <thead>
          <tr>
            <th align="left">Blind Spot</th>
            <th align="left">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Object Delivery Outcome</td>
            <td align="left">Transport acknowledgment does not state whether a complete Object was available before an application deadline</td>
          </tr>
          <tr>
            <td align="left">Object-Level Timing</td>
            <td align="left">Packet timing does not directly express the arrival relationship between media Objects</td>
          </tr>
          <tr>
            <td align="left">Application State</td>
            <td align="left">The transport does not know playback headroom or application consumption state</td>
          </tr>
          <tr>
            <td align="left">End-to-End Delivery across Relays</td>
            <td align="left">Transport feedback is scoped to one QUIC connection and does not describe the cumulative delivery outcome across a Relay chain</td>
          </tr>
        </tbody>
      </table>
      <t>Addressing these blind spots requires a feedback mechanism that reports delivery
outcomes at MOQT Object granularity and associates those observations with the
corresponding media Track.</t>
      <t>In a direct deployment, the Adjacent Media Publisher is also the Media Original
Publisher. When media traverses one or more Relays, these roles are separated. A
feedback mechanism therefore needs to support both local consumption by the
Adjacent Media Publisher and delivery of downstream observations across the
Relay chain to the Media Original Publisher. The latter cannot be inferred from
transport feedback on the Media Original Publisher's immediate connection.</t>
    </section>
    <section anchor="architecture">
      <name>Architecture</name>
      <section anchor="feedback-model">
        <name>Feedback Model</name>
        <t>A Feedback Track is a normal MOQT Track whose Objects carry MQF reports. MQF
introduces no new QUIC frame or MOQT control message type. The associated media
Track identifies the Object sequence being reported, and the Feedback Type
identifies the intended Feedback Consumer and Relay behavior.</t>
        <t>MQF operates at Object granularity. The interpretation of an Object as a frame,
chunk, or other media unit is defined by the media format or application.</t>
        <t>MQF complements, rather than replaces, transport-layer signals. QUIC
acknowledgments describe packet delivery on one QUIC connection, and receive
timestamps such as <xref target="quic-receive-ts"/> can provide additional packet timing
information. MQF describes delivery outcomes using media Object coordinates and
can carry application-level observations such as playout headroom.</t>
        <t>An <tt>ORIGIN_FEEDBACK</tt> report can reflect the cumulative delivery outcome observed
downstream of the Media Original Publisher, but it does not identify which Relay
hop or path segment caused that outcome. Hop-by-hop path diagnosis is not
defined by MQF.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Signal</th>
              <th align="left">Granularity and Scope</th>
              <th align="left">Information Provided</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">QUIC acknowledgment and receive timestamps</td>
              <td align="left">Packet level on one QUIC connection</td>
              <td align="left">Transport delivery and timing information</td>
            </tr>
            <tr>
              <td align="left">MQF</td>
              <td align="left">Object level, hop-local or across Relays</td>
              <td align="left">Object delivery status and optional application observations</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="feedback-for-bidirectional-media">
        <name>Feedback for Bidirectional Media</name>
        <t>Feedback direction is defined relative to the associated media Track, not by an
endpoint role or an application-specific direction label. A Media Subscriber
that generates feedback acts as the Feedback Publisher. The intended Feedback
Consumer is determined by the Feedback Type: the Adjacent Media Publisher for
<tt>HOP_FEEDBACK</tt>, or the Media Original Publisher for <tt>ORIGIN_FEEDBACK</tt>.</t>
        <t>An endpoint can be a Media Publisher for one Track and a Media Subscriber for
another Track. Each media Track can independently have one or more associated
Feedback Tracks:</t>
        <artwork><![CDATA[
Endpoint A                         Endpoint B
  |--- media Track A ------------>|  B: Media Subscriber
  |<-- Feedback Track A -----------|  B: Feedback Publisher
  |                                |
  |<-- media Track B --------------|  A: Media Subscriber
  |--- Feedback Track B ---------->|  A: Feedback Publisher
]]></artwork>
        <t>The two Feedback Tracks use the same report format and establishment rules. The
associated media Track identifies the media flow being reported, and each
Feedback Track independently declares <tt>HOP_FEEDBACK</tt> or <tt>ORIGIN_FEEDBACK</tt>. The
<tt>PUBLISH_FEEDBACK</tt> and <tt>SUBSCRIBE_FEEDBACK</tt> Setup Option bits indicate whether
the endpoint that declares them can publish or subscribe to Feedback Tracks on
the current MOQT session.</t>
      </section>
      <section anchor="feedback-routing-through-relays">
        <name>Feedback Routing through Relays</name>
        <t>MQF supports deployments in which feedback is consumed by the Adjacent Media
Publisher as well as deployments in which feedback is delivered to the Media
Original Publisher. The Feedback Type Track Property defined in Section 4.1
identifies the intended consumer and required Relay behavior.</t>
        <t>In a cascaded Relay architecture, media from a Media Original Publisher
traverses multiple Relays before reaching a Media Subscriber. The Media
Subscriber is the feedback source, the Relay adjacent to the Media Subscriber
can consume its reported delivery outcomes, and the Relay chain can carry a
separate Feedback Track to the Media Original Publisher.</t>
        <artwork><![CDATA[
Media
  Media Original Publisher -> ... -> L2 -> L1 -> Media Subscriber
HOP_FEEDBACK
                                           L1 <- Media Subscriber
Relay-generated ORIGIN_FEEDBACK
  Media Original Publisher <- ... <- L2 <- L1
Subscriber-generated ORIGIN_FEEDBACK
  Media Original Publisher <- ... <- L2 <- L1 <- Media Subscriber
]]></artwork>
        <t>The following Feedback Tracks serve different consumers:</t>
        <ul spacing="normal">
          <li>
            <t>A <tt>HOP_FEEDBACK</tt> Track carries delivery outcomes observed by the Media
Subscriber and terminates at the L1 Relay for local interpretation.</t>
          </li>
          <li>
            <t>The L1 Relay can derive a new <tt>ORIGIN_FEEDBACK</tt> Track from received
<tt>HOP_FEEDBACK</tt> and other information available to the Relay when configured to
do so. When doing so, the Relay acts as a new Feedback Publisher and publishes
a distinct Feedback Track in the context of its upstream media Track.</t>
          </li>
          <li>
            <t>An <tt>ORIGIN_FEEDBACK</tt> Track can be published by a Media Subscriber or a Relay
and can traverse zero or more Relays. Its MQF Payload remains opaque to
intermediate Relays. Subscriber-generated <tt>ORIGIN_FEEDBACK</tt> requires the Media
Original Publisher to have sufficient application context to interpret the
report and its associated media Track coordinates.</t>
          </li>
        </ul>
        <t>A Media Subscriber behind an L1 Relay SHOULD use <tt>HOP_FEEDBACK</tt> when the report
requires Relay-local interpretation or translation into the context of an
upstream media Track. It MAY instead publish <tt>ORIGIN_FEEDBACK</tt> when the Media
Original Publisher has sufficient application context to interpret the report
and its associated media Track coordinates.</t>
        <t>The relative importance of the two Feedback Types depends on the application.
For example, a deployment can use <tt>HOP_FEEDBACK</tt> as input to local Track
selection or forwarding behavior and <tt>ORIGIN_FEEDBACK</tt> as input to source
adaptation. A Relay that derives a report from one or more downstream reports
acts as a new Feedback Publisher and publishes a distinct Feedback Track. The
base MQF format does not define the semantics of deriving <tt>ORIGIN_FEEDBACK</tt> from
downstream reports, whether from one report or by aggregating multiple reports.
Such derivation requires an extension or application agreement that defines
observation provenance, timestamp handling, metric interpretation, and, when
applicable, the represented Media Subscribers and aggregation method.</t>
      </section>
    </section>
    <section anchor="feedback-track">
      <name>Feedback Track</name>
      <section anchor="track-definition">
        <name>Track Definition</name>
        <t>The Feedback Track is a normal MoQ Track where the Payload of each Object is an
MQF report. Each MQF report is published as an independent Object with
monotonically increasing Object ID within a Group.</t>
        <t>Each Feedback Track has exactly one Feedback Type and MUST NOT mix
<tt>HOP_FEEDBACK</tt> and <tt>ORIGIN_FEEDBACK</tt>. The type controls Track distribution and
is carried in the Relay-visible <tt>MQF_FEEDBACK_TYPE</tt> Track Property. A Feedback
Publisher that generates both types MUST publish two distinct Feedback Tracks.</t>
        <t>The <tt>MQF_FEEDBACK_TYPE</tt> Track Property has an MOQT variable-length integer
(<tt>vi64</tt>) value, encoded as specified in <xref target="MoQTransport"/>, Section 8.1:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>0x00</tt></td>
              <td align="left">
                <tt>HOP_FEEDBACK</tt></td>
              <td align="left">Intended for the Adjacent Media Publisher on the current MOQT session</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x01</tt></td>
              <td align="left">
                <tt>ORIGIN_FEEDBACK</tt></td>
              <td align="left">Intended for the Media Original Publisher across zero or more Relays</td>
            </tr>
          </tbody>
        </table>
        <t>Every Feedback Track MUST include the <tt>MQF_FEEDBACK_TYPE</tt> Track Property
(TBD2 - experimental number 0x37FE)
in its PUBLISH Track Properties. This Property is immutable for the lifetime of
the Track. A Relay that recognizes it MUST NOT modify or remove it. A Relay that
does not recognize it forwards and caches it according to the unknown Property
rules in <xref target="MoQTransport"/>. An MQF-aware Relay uses this Property without
inspecting MQF Object Payloads. A terminal Feedback Consumer that receives an
unsupported value MUST reject the Feedback Track.</t>
        <t>The Group division strategy for Feedback Track is implementation-defined. Each
MQF report is self-contained, and a newer report supersedes the value of an
older one. It is therefore RECOMMENDED that a Feedback Publisher start a new
Group for each MQF report, with the report as Object 0 of that Group, so that a
delayed or lost report does not block delivery of newer reports on the same
stream. A Feedback Publisher that places multiple reports in one Group accepts
that a retransmitted earlier report can delay later reports.</t>
        <t>Each Feedback Track MUST be associated 1:1 with a media Track. The association
is encoded in the Feedback Full Track Name (Section 4.2) and is not repeated in
MQF reports. This Full Track Name binding is the media Track binding mechanism
defined by this document; no per-Object binding parameter is required.</t>
        <t>When feedback is needed for multiple media Tracks, independent Feedback Tracks
MUST be established separately.</t>
        <t>Each Feedback Publisher or publication session MUST use a distinct Feedback Full
Track Name. This prevents independent publishers from producing different
Payloads for the same Group ID and Object ID on what MOQT would otherwise treat
as a single Track.</t>
      </section>
      <section anchor="track-naming">
        <name>Track Naming</name>
        <t>The Feedback Full Track Name carries the information that Relays need to
distribute a Feedback Track without inspecting Object Payloads. Let <tt>++</tt> denote
appending fields to a Track Namespace tuple. A Feedback Track MUST use:</t>
        <ul spacing="normal">
          <li>
            <t><strong>Track Namespace:</strong> The media Track Namespace with three fields appended in
this order: the literal <tt>mqf</tt>, the feedback type label, and the feedback
source ID.</t>
          </li>
          <li>
            <t><strong>Track Name:</strong> The Track Name of the associated media Track.</t>
          </li>
        </ul>
        <t>The <tt>feedback-type-label</tt> is the ASCII string <tt>hop-feedback</tt> for <tt>HOP_FEEDBACK</tt>
or <tt>origin-feedback</tt> for <tt>ORIGIN_FEEDBACK</tt>. It enables Namespace prefix
matching. The label MUST agree with the <tt>MQF_FEEDBACK_TYPE</tt> Track Property. A
node that detects a mismatch MUST reject the Feedback Track.</t>
        <t>The <tt>feedback-source-id</tt> is an opaque, non-empty byte string selected by the
Feedback Publisher. It MUST distinguish that publisher and publication session
from every other Feedback Publisher and session for the associated media Track.
It is not required to identify a user and MUST NOT be interpreted as a user
identity. A publisher MUST select a new value before reusing a Group ID and
Object ID pair or restarting its Report Sequence space. To limit linkability
across sessions, a Feedback Publisher SHOULD select a <tt>feedback-source-id</tt> that
is randomly generated for each publication session and is not derived from a
stable user, device, or network identifier (see <xref target="privacy"/>).</t>
        <t>For example, feedback for media Full Track Name <tt>(example.com, meeting,
audio_response)</tt> can use:</t>
        <artwork><![CDATA[
(example.com, meeting, mqf, hop-feedback, subscriber-17, audio_response)
(example.com, meeting, mqf, origin-feedback, relay-l1-4, audio_response)
]]></artwork>
        <t>The same naming construction applies independently to every media Track. The
associated media Track determines the media direction being reported; a separate
direction prefix is not used.</t>
        <t>A node receiving a PUBLISH for a Feedback Track reconstructs the associated
media Full Track Name by removing the final three Namespace fields and retaining
the Feedback Track Name. If it cannot identify the associated media Track or
does not support the indicated type, it SHOULD respond with <tt>REQUEST_ERROR</tt>.</t>
      </section>
      <section anchor="track-establishment-and-lifecycle">
        <name>Track Establishment and Lifecycle</name>
        <t>The Feedback Track is established by the Feedback Publisher (a Media Subscriber
or a Relay generating new feedback) through MOQT's PUBLISH / REQUEST_OK exchange
on a bidirectional request stream. In <xref target="MoQTransport"/>, PUBLISH_OK is a
descriptive alias for REQUEST_OK, not a separate wire message type. The MQF
capabilities required by Section 6 MUST be negotiated before establishment.</t>
        <t>For a <tt>HOP_FEEDBACK</tt> Track, the terminal Feedback Consumer is the Adjacent Media
Publisher on that MOQT session. The Feedback Consumer accepts the PUBLISH and
MUST NOT advertise or forward that Feedback Track on another MOQT session.</t>
        <t>An L1 Relay that generates <tt>ORIGIN_FEEDBACK</tt> is a new Feedback Publisher. It
uses a new Feedback Full Track Name, Report Sequence space, and MQF Payload. It
can derive that Payload from <tt>HOP_FEEDBACK</tt>, local media transmission state, and
the mapping between its upstream and downstream media Tracks.</t>
        <t>An <tt>ORIGIN_FEEDBACK</tt> type does not create a route by itself. Before feedback
Objects can be delivered, an interest and authorization chain MUST be
established between the Media Original Publisher and the Feedback Publisher:</t>
        <ol spacing="normal" type="1"><li>
            <t>The Media Original Publisher, acting as a Feedback Subscriber, expresses
interest in the <tt>origin-feedback</tt> Namespace for the media Track. It can use
SUBSCRIBE_TRACKS for the corresponding Namespace prefix, or use
deployment-specific prior interest and authorization as permitted by
<xref target="MoQTransport"/>.</t>
          </li>
          <li>
            <t>Each intermediate Relay binds the Feedback Track to the media forwarding
state identified by Section 4.2. It propagates feedback interest only to
downstream peers to which it forwards the associated media Track. Feedback
Objects travel in the opposite direction, toward the peer from which the
Relay received that media Track.</t>
          </li>
          <li>
            <t>The Feedback Publisher sends PUBLISH for its unique Feedback Full Track Name.
Each hop uses the PUBLISH / REQUEST_OK and SUBSCRIBE / SUBSCRIBE_OK
procedures in <xref target="MoQTransport"/> to establish forwarding with Forward State 1.</t>
          </li>
        </ol>
        <t>SUBSCRIBE_NAMESPACE discovers published Namespaces; it does not request PUBLISH
messages for their Tracks. SUBSCRIBE_TRACKS expresses that Track interest in
<xref target="MoQTransport"/>.</t>
        <t>PUBLISH_NAMESPACE is not a route discovery mechanism. A Relay MUST NOT use it to
search a richly connected Relay topology for a path to the Media Original
Publisher. A Relay forwards <tt>ORIGIN_FEEDBACK</tt> only toward the peer from which it
received the associated media Track, and MUST NOT forward it back toward the
Feedback Publisher or another downstream media peer. If there is no unique
reverse media-path binding, the Relay MUST reject the Feedback Track. These
rules prevent a feedback loop in the single-upstream media topology defined by
this document.</t>
        <t>If any hop has no matching interest, lacks authorization, has no media-path
binding, or rejects the request, that hop MUST reject establishment using the
applicable MOQT request error. The Feedback Publisher MUST NOT send MQF Objects
until its PUBLISH is accepted. It MAY continue or fall back to a separately
established <tt>HOP_FEEDBACK</tt> Track, but it MUST NOT relabel a rejected Track to
bypass the failure.</t>
        <t>Relays route both Feedback Track types solely from the Full Track Name and
<tt>MQF_FEEDBACK_TYPE</tt> Track Property. In accordance with <xref target="MoQTransport"/>, the
Object Payload is opaque to a Relay and is not processed to make a forwarding
decision. An <tt>ORIGIN_FEEDBACK</tt> MQF Payload can therefore be protected between
the Feedback Publisher and the Media Original Publisher. A <tt>HOP_FEEDBACK</tt> MQF
Payload can be protected for its adjacent terminal Feedback Consumer.</t>
        <t><strong>Direct Establishment Flow Example:</strong></t>
        <t>Both endpoints have completed the MQF Setup exchange in Section 6. The Media
Original Publisher has prior interest in and authorization to receive the
Feedback Track. The diagram omits request identifiers and other MOQT fields.</t>
        <artwork><![CDATA[
Media Subscriber                  Media Original Publisher
(Media Subscriber /               (Media Publisher /
 Feedback Publisher)               Feedback Subscriber)
  |                                    |
  | SUBSCRIBE(track=audio_response)    |  (1) Subscribe media Track
  |----------------------------------->|
  | SUBSCRIBE_OK                       |
  |<-----------------------------------|
  |                                    |
  | PUBLISH(                           |  (2) Publish origin-feedback Track
  |   namespace=media_namespace ++     |
  |     ("mqf", "origin-feedback",     |
  |      "subscriber-17"),             |
  |   track=audio_response,            |
  |   property=MQF_FEEDBACK_TYPE(1))   |
  |----------------------------------->|
  | REQUEST_OK                         |
  |<-----------------------------------|
  |                                    |
  | [Object: MQF seq=0]                |  (3) Send MQF report
  |----------------------------------->|
  | [Object: MQF seq=1]                |
  |----------------------------------->|
  | ...                                |
]]></artwork>
        <t><strong>Lifecycle Rules:</strong></t>
        <t>The Feedback Track lifecycle SHOULD align with the subscribed media Track it
covers. After the media Track publisher sends PUBLISH_DONE for the media Track,
the Feedback Publisher SHOULD send PUBLISH_DONE for the Feedback Track after
transmitting the final MQF report and stop publishing Objects. When the Media
Subscriber ends its subscription to the media Track, for example when switching
to a different representation, it SHOULD send PUBLISH_DONE for the associated
Feedback Track after transmitting any final MQF report.</t>
        <t>When a MOQT session carrying a Feedback Track is disconnected, a Relay MUST
discard the associated forwarding state and MUST NOT re-advertise the old
Feedback Track after reconnecting. The Feedback Publisher establishes a new
Feedback Track with a new <tt>feedback-source-id</tt>; its Report Sequence SHOULD
restart from 0.</t>
        <t>Feedback is time-sensitive. A Feedback Publisher SHOULD use the
<tt>MAX_CACHE_DURATION</tt> Track Property defined by <xref target="MoQTransport"/> to bound the
period for which MQF Objects can be served from cache. A terminal feedback
consumer MUST NOT apply an MQF report from a previous publication session.</t>
      </section>
      <section anchor="transport-and-priority">
        <name>Transport and Priority</name>
        <t>The Feedback Track SHOULD be carried over QUIC Stream (consistent with ordinary
MoQ Objects).</t>
        <t>Feedback is most useful when the path is congested, which is also when it is
most likely to be delayed. If a Feedback Track is scheduled behind the media
it describes, reports can be delayed until they no longer reflect current
conditions. The priority of a Feedback Track (<xref target="MoQTransport"/>, Section 5.1)
SHOULD therefore be no lower than the priority of the media Track it
describes. Example priority assignment:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Track Type</th>
              <th align="left">Subscriber Priority</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>audio_response</tt></td>
              <td align="left">0 (highest)</td>
              <td align="left">Audio media</td>
            </tr>
            <tr>
              <td align="left">Feedback Track</td>
              <td align="left">1</td>
              <td align="left">MQF report</td>
            </tr>
            <tr>
              <td align="left">
                <tt>video_response</tt></td>
              <td align="left">2</td>
              <td align="left">Video media</td>
            </tr>
          </tbody>
        </table>
        <t>A high priority does not entitle feedback to a large share of capacity. A
Feedback Publisher MUST bound the rate of each Feedback Track, for example by
limiting report frequency (<xref target="mqf-generation-timing"/>) and report size
(<xref target="report-size-control"/>), so that feedback remains a small fraction of the
media rate it describes.</t>
        <t>A stale report has little value once a newer report is available. A Feedback
Publisher SHOULD use a delivery timeout (<xref target="MoQTransport"/>) no larger than a
small multiple of its report interval, so that undelivered reports are
abandoned rather than retransmitted after newer reports exist.</t>
      </section>
    </section>
    <section anchor="feedback-report-format">
      <name>Feedback Report Format</name>
      <t>This section defines the binary encoding format of an MQF report. All integer
fields use QUIC Variable-Length Integer encoding (RFC 9000, Section 16) unless
otherwise specified.</t>
      <t>This MQF Payload encoding is distinct from the MOQT <tt>vi64</tt> encoding used for
Setup Options and Track Properties. Relays forwarding MQF Objects preserve the
Payload bytes without translating between these encodings.</t>
      <t>Fields marked as "signed encoding" use ZigZag mapping and are transmitted as
unsigned QUIC varint:</t>
      <ul spacing="normal">
        <li>
          <t><strong>Encoding:</strong> <tt>unsigned = (signed &lt;&lt; 1) ^ (signed &gt;&gt; 63)</tt></t>
        </li>
        <li>
          <t><strong>Decoding:</strong> <tt>signed = (unsigned &gt;&gt;&gt; 1) ^ -(unsigned &amp; 1)</tt></t>
        </li>
      </ul>
      <t>Mapping examples: <tt>0 -&gt; 0</tt>, <tt>-1 -&gt; 1</tt>, <tt>1 -&gt; 2</tt>, <tt>-2 -&gt; 3</tt>, <tt>2 -&gt; 4</tt>.</t>
      <section anchor="report-structure">
        <name>Report Structure</name>
        <artwork><![CDATA[
MQF Report {
  Report Timestamp (i),
  Report Sequence (i),
  Object Entry Count (i),
  Object Entry (..) ...,
  Summary Stats (..),
  Optional Metric Count (i),
  Optional Metric (..) ...,
}
]]></artwork>
        <t>This document defines MQF report format version 0. The <tt>MOQT_FEEDBACK</tt> Setup
Option (Section 6.1) declares support for this format; it does not negotiate a
separate version number. The format version is not repeated in each report.</t>
        <t>Each MQF report describes Object delivery status for a single media Track
associated with its Feedback Track (1:1 association, see Section 4.1).</t>
        <t><strong>Report Timestamp (varint):</strong> The moment when the report is generated, using
the Feedback Publisher's local monotonic clock value in microseconds. This value
is only used for Receive Timestamp Delta chain anchoring and report ordering,
not for cross-end time alignment. Monotonic clock MUST be used. The epoch of
this clock is chosen by the Feedback Publisher and has no meaning to the
Feedback Consumer; it MUST remain constant for the lifetime of a Feedback Track.</t>
        <t><strong>Report Sequence (varint):</strong> Monotonically increasing from 0 independently for
each Feedback Track. A gap can indicate an omitted report only when the
publication policy for that Track requires a contiguous Report Sequence. An
Object ID gap alone, without a Prior Object ID Gap property as defined by
<xref target="MoQTransport"/>, MUST NOT be interpreted as feedback loss. Because
<tt>HOP_FEEDBACK</tt> and <tt>ORIGIN_FEEDBACK</tt> use separate Tracks, terminating one type
cannot create sequence gaps in the other type's sequence space.</t>
        <t><strong>Object Entry Count (varint):</strong> Number of Object Entries that follow. When the
value is 0, the report contains only Summary Stats (for heartbeat purposes).</t>
      </section>
      <section anchor="object-entry">
        <name>Object Entry</name>
        <artwork><![CDATA[
Object Entry {
  Group ID (i),
  Object ID (i),
  Status (i),
  [Receive Timestamp Delta (i)],
}
]]></artwork>
        <t>Object Entries within the same MQF MUST be sorted in ascending order by <tt>(Group
ID, Object ID)</tt>.</t>
        <section anchor="group-id">
          <name>Group ID</name>
          <t>The Group ID (varint) of the Object in the associated media Track.</t>
        </section>
        <section anchor="object-id">
          <name>Object ID</name>
          <t>The Object ID (varint) within the identified Group of the associated media
Track.</t>
          <t>The media Full Track Name from Section 4.2, Group ID, and Object ID together
identify the media Object being reported. A Relay forwarding the same media
Track preserves these coordinates. A Relay that changes the Full Track Name or
media Object coordinates is publishing a different media Track and MUST NOT
associate its Feedback Track with the pre-transformation media Track.</t>
        </section>
        <section anchor="status">
          <name>Status</name>
          <t>Delivery status code (varint), see Section 5.3 for values.</t>
        </section>
        <section anchor="receive-timestamp-delta">
          <name>Receive Timestamp Delta</name>
          <t>Conditional presence field (varint, signed encoding): Present only when Status
is <tt>RECEIVED</tt> (0x00) or <tt>RECEIVED_LATE</tt> (0x01). Encoding rules:</t>
          <ul spacing="normal">
            <li>
              <t><strong>First received Object within the same MQF</strong> (i.e., the first entry with
Status <tt>RECEIVED</tt> or <tt>RECEIVED_LATE</tt> when iterating through the list): Let <tt>R</tt>
be the Report Timestamp and <tt>T_i</tt> be the Object's arrival time, both in
microseconds on the Feedback Publisher's local monotonic clock. The signed
Delta is <tt>T_i - R</tt>.</t>
            </li>
            <li>
              <t><strong>Subsequent received Objects:</strong> Let <tt>T_j</tt> be the arrival time of the most
recent preceding entry with Status <tt>RECEIVED</tt> or <tt>RECEIVED_LATE</tt>. The signed
Delta is <tt>T_i - T_j</tt>.</t>
            </li>
          </ul>
          <t>A decoder reconstructs <tt>T_i</tt> as <tt>R + Delta</tt> for the first received Object Entry
and as <tt>T_j + Delta</tt> for each subsequent received Object Entry. Each signed
Delta is encoded using the ZigZag mapping defined in Section 5.</t>
          <t><tt>NOT_RECEIVED</tt>, <tt>PARTIALLY_RECEIVED</tt>, and <tt>NOT_DELIVERED</tt> entries are skipped in
the delta chain.</t>
          <t>Since Object Entries are sorted by <tt>(Group ID, Object ID)</tt> while Objects may
arrive out of order, delta values can be negative (indicating the Object arrived
earlier than the previous received Object in the list). Negative delta from
reordering is a valid network state signal.</t>
        </section>
      </section>
      <section anchor="delivery-status-codes">
        <name>Delivery Status Codes</name>
        <table>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>0x00</tt></td>
              <td align="left">
                <tt>RECEIVED</tt></td>
              <td align="left">Completely received and within delivery deadline</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x01</tt></td>
              <td align="left">
                <tt>RECEIVED_LATE</tt></td>
              <td align="left">Completely received but exceeded delivery deadline</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x02</tt></td>
              <td align="left">
                <tt>NOT_RECEIVED</tt></td>
              <td align="left">No bytes received at report generation time</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x03</tt></td>
              <td align="left">
                <tt>PARTIALLY_RECEIVED</tt></td>
              <td align="left">Partial bytes received but Object is incomplete</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x04</tt></td>
              <td align="left">
                <tt>NOT_DELIVERED</tt></td>
              <td align="left">Not received, and the Object was intentionally not delivered (see <xref target="not-delivered"/>)</td>
            </tr>
          </tbody>
        </table>
        <t><tt>NOT_RECEIVED</tt> and <tt>PARTIALLY_RECEIVED</tt> describe Objects that a Publisher
attempted to deliver but that did not arrive intact. <tt>NOT_DELIVERED</tt> describes
Objects that were withheld or abandoned by design. Feedback Consumers SHOULD NOT
treat <tt>NOT_DELIVERED</tt> as evidence of network loss.</t>
        <section anchor="received-late-determination">
          <name>RECEIVED_LATE Determination</name>
          <t>The Feedback Publisher MUST determine Object expiration based on a locally
available playback deadline:</t>
          <t>An Object is <tt>RECEIVED_LATE</tt> when its arrival time exceeds its expected playback
moment.</t>
          <t>When a playback deadline is unavailable (e.g., non-real-time playback
scenarios), the Feedback Publisher SHOULD report <tt>RECEIVED</tt> rather than
<tt>RECEIVED_LATE</tt>.</t>
          <t>For example, suppose the application determines that an Object is expected to be
available for playback at time <tt>10.180</tt> seconds on the Feedback Publisher's
monotonic clock. If the last byte arrives at <tt>10.195</tt> seconds, the Object is
reported as <tt>RECEIVED_LATE</tt>. If the MQF report is generated at <tt>10.220</tt> seconds
and this is the first received Object Entry in the report, its Receive Timestamp
Delta represents an arrival 25 milliseconds before the Report Timestamp. The
playback deadline and the 15-millisecond lateness are not carried in the Object
Entry; MQF reports the result of evaluating the application-provided deadline.</t>
          <t>Playback deadlines are often derived from an adaptive jitter buffer and differ
between Media Subscribers and over time. When Optional Media Metrics are
enabled, a Feedback Publisher that reports <tt>RECEIVED_LATE</tt> SHOULD include the
<tt>TARGET_PLAYOUT_DELAY_MS</tt> metric (<xref target="optional-media-metrics"/>) so that a
Feedback Consumer can interpret the deadline that was applied and compare
reports from different Media Subscribers.</t>
        </section>
        <section anchor="notreceived-reporting-timing">
          <name>NOT_RECEIVED Reporting Timing</name>
          <t>The Feedback Publisher SHOULD report an Object as <tt>NOT_RECEIVED</tt> when one of the
following conditions is met:</t>
          <ul spacing="normal">
            <li>
              <t>A subsequent Object with a larger Object ID in the same Subgroup of the same
Group has arrived, but this Object has not.</t>
            </li>
            <li>
              <t>The Object's expected arrival time has exceeded <tt>2 x expected_interval</tt> (see
Section 5.4.6) without arrival, and no subsequent Object is available for
reference.</t>
            </li>
          </ul>
          <t>Condition 2 covers the "last Object lost" scenario (no subsequent Object to
trigger Condition 1).</t>
          <t>Condition 1 is evaluated per Subgroup. Objects of one Group can be carried in
several Subgroups on separate streams, for example when temporal enhancement
layers are carried in a different Subgroup from the base layer, and the streams
can be delivered in any order and at different priorities. The arrival of an
Object in one Subgroup MUST NOT, by itself, cause an Object in a different
Subgroup to be reported as <tt>NOT_RECEIVED</tt>. For Objects carried in Datagrams,
which have no Subgroup, Condition 1 applies across the Group.</t>
          <t>The Feedback Publisher MUST NOT report <tt>NOT_RECEIVED</tt> for Objects that are not
yet reasonably expected to arrive, or for Objects that meet the conditions for
<tt>NOT_DELIVERED</tt> (<xref target="not-delivered"/>).</t>
        </section>
        <section anchor="partiallyreceived">
          <name>PARTIALLY_RECEIVED</name>
          <t>Applicable to Objects carried over QUIC Stream: When a Stream is terminated by
<tt>RESET_STREAM</tt> or closed due to timeout, Objects with partially received data
SHOULD be reported as <tt>PARTIALLY_RECEIVED</tt>.</t>
          <t>The timeout threshold used to determine whether a partially received Object
should be reported as <tt>PARTIALLY_RECEIVED</tt> is application-defined. Different
applications can use different thresholds according to their latency
requirements.</t>
          <t>A partially received Object that other Objects depend on, such as a video
reference frame, can leave the Media Subscriber unable to decode the rest of
the Group. MQF reports the observation; a Media Subscriber that needs a new
decodable starting point can request one using the NEW_GROUP_REQUEST parameter
defined in <xref target="MoQTransport"/>.</t>
          <t>For Objects carried over QUIC Datagram: Since QUIC Datagrams are not
retransmitted by the transport layer, any Object whose Datagram(s) are lost
results in incomplete data at the Feedback Publisher. If the Feedback Publisher
detects that some but not all Datagrams constituting an Object have arrived, and
the remaining Datagrams are not expected to arrive (e.g., a subsequent Object
has arrived or the application-defined timeout has expired), the Object SHOULD
be reported as <tt>PARTIALLY_RECEIVED</tt>. If no Datagrams for the Object have
arrived, the Object SHOULD be reported as <tt>NOT_RECEIVED</tt> instead.</t>
        </section>
        <section anchor="not-delivered">
          <name>NOT_DELIVERED</name>
          <t>MOQT Publishers and Relays do not always deliver every Object of a Track. They
schedule by priority and can abandon Objects that would arrive too late, and a
Subscriber can stop receiving a Group to move to a newer one. Reporting such
Objects as <tt>NOT_RECEIVED</tt> would make deliberate scheduling decisions look like
network loss, and a Feedback Consumer that adapts on loss could then reduce
quality without cause.</t>
          <t>The Feedback Publisher SHOULD report an Object as <tt>NOT_DELIVERED</tt> when it has
not been received and at least one of the following is true:</t>
          <ul spacing="normal">
            <li>
              <t>The upstream Publisher signalled that the Object will not be delivered, for
example through an Object Status, a Prior Object ID Gap property, or an end of
Group or Subgroup indication as defined by <xref target="MoQTransport"/>.</t>
            </li>
            <li>
              <t>The stream carrying the Object was reset by the Publisher with an error code
that <xref target="MoQTransport"/> associates with a delivery timeout or with the
Publisher's decision to stop sending that stream.</t>
            </li>
            <li>
              <t>The Media Subscriber itself stopped receiving the Group or Subgroup containing
the Object, for example by moving to a newer Group, by canceling the stream,
or by ending the subscription.</t>
            </li>
          </ul>
          <t><tt>NOT_DELIVERED</tt> describes why an Object is missing from the Media Subscriber's
point of view; it does not identify which node withheld it. An Object reported
as <tt>NOT_DELIVERED</tt> can still be missing because of congestion upstream, for
example when a Relay drops low-priority Objects that it could not send in time.
Feedback Consumers that need to detect such congestion can track the rate of
<tt>NOT_DELIVERED</tt> Objects separately from <tt>Objects Lost</tt>.</t>
        </section>
      </section>
      <section anchor="summary-stats-block">
        <name>Summary Stats Block</name>
        <artwork><![CDATA[
Summary Stats {
  Report Interval (i),
  Total Objects Evaluated (i),
  Objects Received (i),
  Objects Received Late (i),
  Objects Lost (i),
  Avg Inter-Arrival Delta (i),
  Objects Not Delivered (i),
}
]]></artwork>
        <t>Summary Stats MUST always be included in every MQF report and are not controlled
by the negotiation bitmap. They provide a windowed aggregate view for Feedback
Consumers that do not process every Object Entry.</t>
        <t>The Report Interval window of Summary Stats is independent from the coverage of
Object Entries. Object Entries MAY include Objects outside the Report Interval
window (e.g., continuously reported NOT_RECEIVED entries, see Section 7.4).</t>
        <section anchor="report-interval">
          <name>Report Interval</name>
          <t>The time window length covered by this report (varint), in microseconds. This
window spans from <tt>Report Timestamp - Report Interval</tt> to <tt>Report Timestamp</tt>.
RECOMMENDED value is 50000-200000 (50-200ms).</t>
        </section>
        <section anchor="total-objects-evaluated">
          <name>Total Objects Evaluated</name>
          <t>Total number of Objects (varint) evaluated within the Report Interval window.
Includes Objects of all statuses. MUST equal <tt>Objects Received + Objects
Received Late + Objects Lost + Objects Not Delivered</tt>.</t>
          <t>Because a later report can revise the status of an Object (<xref target="delivery-status"/>),
these counts are a snapshot taken when the report is generated. A Feedback
Consumer that accumulates counts across reports needs to account for Objects
that appear in more than one Report Interval window.</t>
        </section>
        <section anchor="objects-received">
          <name>Objects Received</name>
          <t>Number of Objects (varint) with status <tt>RECEIVED</tt> within the window.</t>
        </section>
        <section anchor="objects-received-late">
          <name>Objects Received Late</name>
          <t>Number of Objects (varint) with status <tt>RECEIVED_LATE</tt> within the window.</t>
        </section>
        <section anchor="objects-lost">
          <name>Objects Lost</name>
          <t>Number of Objects (varint) with status <tt>NOT_RECEIVED</tt> or <tt>PARTIALLY_RECEIVED</tt>
within the window.</t>
        </section>
        <section anchor="avg-inter-arrival-delta">
          <name>Avg Inter-Arrival Delta</name>
          <t>Average arrival interval deviation (varint, signed encoding) of consecutive
received Object pairs within the window, in microseconds. Calculation method:</t>
          <t>For consecutive received Object pairs (i-1, i) sorted by arrival time within the
window:</t>
          <artwork><![CDATA[
delta(i) = (A(i) - A(i-1)) - expected_interval
Avg Inter-Arrival Delta = mean(delta(i)) for all i
]]></artwork>
          <t>Where <tt>A(i)</tt> is the arrival time of Object i, and <tt>expected_interval</tt> is the
expected arrival interval.</t>
          <t>Methods to determine <tt>expected_interval</tt> (by priority):</t>
          <ol spacing="normal" type="1"><li>
              <t>A nominal Object interval supplied by the media format or application.</t>
            </li>
            <li>
              <t>Historical average arrival interval within current session (sliding window).</t>
            </li>
          </ol>
          <t>If neither method is available, the Feedback Publisher SHOULD use method 2 or
set this field to 0.</t>
          <t>Positive values indicate Object arrival interval greater than expected
(increased queuing), negative values indicate less than expected. When fewer
than 2 received Objects exist in the window, this field MUST be 0.</t>
          <t>Arrival time is recorded when the last byte of an Object arrives
(<xref target="arrival-time"/>). For media in which Object sizes vary widely, such as video
with periodic key frames, part of the deviation reflects Object size rather
than queuing. Feedback Consumers SHOULD interpret this field over several
reports rather than from a single value.</t>
        </section>
        <section anchor="objects-not-delivered">
          <name>Objects Not Delivered</name>
          <t>Number of Objects (varint) with status <tt>NOT_DELIVERED</tt> within the window. These
Objects are not included in <tt>Objects Lost</tt>.</t>
        </section>
      </section>
      <section anchor="optional-media-metrics">
        <name>Optional Media Metrics</name>
        <t>Optional Media Metrics immediately follow Summary Stats. <tt>Optional Metric Count</tt>
(varint) specifies the number of subsequent Optional Metrics; a value of 0
indicates no optional metrics are included.</t>
        <t>Each metric uses the following MQF type/value pair. Both fields use the QUIC
variable-length integer encoding defined for report Payloads in Section 5:</t>
        <artwork><![CDATA[
Optional Metric {
  Metric Type (i),
  Metric Value (i),
}
]]></artwork>
        <t>Defined metric types are divided into two categories: Application-Layer Metrics
and QUIC Layer Summary Metrics.</t>
        <t><strong>Application-Layer Metrics:</strong></t>
        <table>
          <thead>
            <tr>
              <th align="left">Type</th>
              <th align="left">Name</th>
              <th align="left">Unit</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>0x02</tt></td>
              <td align="left">
                <tt>PLAYOUT_AHEAD_MS</tt></td>
              <td align="left">milliseconds</td>
              <td align="left">Remaining time until playback stall at the Feedback Publisher, i.e., buffered but not yet played media duration. Smaller values indicate closer to stall (0 = currently stalled).</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x04</tt></td>
              <td align="left">
                <tt>ESTIMATED_BANDWIDTH_KBPS</tt></td>
              <td align="left">kbps</td>
              <td align="left">Bandwidth estimate reported by the Feedback Publisher. The estimation method is application-defined.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x06</tt></td>
              <td align="left">
                <tt>UNDERRUN_COUNT</tt></td>
              <td align="left">events</td>
              <td align="left">Number of times within the Report Interval that playback of the associated media Track had no media available to play when needed (buffer underrun).</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x08</tt></td>
              <td align="left">
                <tt>STALL_DURATION_MS</tt></td>
              <td align="left">milliseconds</td>
              <td align="left">Total time within the Report Interval during which playback of the associated media Track was stalled.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x0A</tt></td>
              <td align="left">
                <tt>TARGET_PLAYOUT_DELAY_MS</tt></td>
              <td align="left">milliseconds</td>
              <td align="left">Playout delay targeted by the Feedback Publisher's jitter buffer at report generation time, used to determine <tt>RECEIVED_LATE</tt> (<xref target="received-late-determination"/>).</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x0C</tt></td>
              <td align="left">
                <tt>RECEIVE_RATE_KBPS</tt></td>
              <td align="left">kbps</td>
              <td align="left">Object Payload bytes of the associated media Track received within the Report Interval, divided by the Report Interval.</td>
            </tr>
          </tbody>
        </table>
        <t><strong>QUIC Layer Summary Metrics:</strong></t>
        <t>The following metrics expose summary information about the Feedback Publisher's
local QUIC connection to the Feedback Consumer.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Type</th>
              <th align="left">Name</th>
              <th align="left">Unit</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">
                <tt>0x10</tt></td>
              <td align="left">
                <tt>PEER_RTT_US</tt></td>
              <td align="left">microseconds</td>
              <td align="left">Feedback Publisher's local QUIC connection smoothed RTT, corresponding to <tt>smoothed_rtt</tt> in RFC 9002.</td>
            </tr>
            <tr>
              <td align="left">
                <tt>0x12</tt></td>
              <td align="left">
                <tt>PEER_LOSS_RATE</tt></td>
              <td align="left">per mille</td>
              <td align="left">Feedback Publisher's local QUIC connection packet loss rate within Report Interval, expressed in per mille (e.g., 50 = 5.0%).</td>
            </tr>
          </tbody>
        </table>
        <t>Object Entries and Summary Stats carry the core MQF report information. Optional
Metrics provide supplementary application- or transport-level observations.</t>
        <t><tt>UNDERRUN_COUNT</tt> and <tt>STALL_DURATION_MS</tt> describe events within the Report
Interval rather than a value at a single moment. A Feedback Consumer can
compute the underrun frequency directly from consecutive reports, which is a
common input for selecting a lower-rate representation.</t>
        <t>Because the method behind <tt>ESTIMATED_BANDWIDTH_KBPS</tt> is application-defined,
values from different Feedback Publishers are not comparable unless the
application defines the method. <tt>RECEIVE_RATE_KBPS</tt> is defined by this document
and is comparable across Feedback Publishers. It reports the rate that was
received, which is not necessarily the rate the path could carry. Neither
metric replaces congestion control (<xref target="scope-and-non-goals"/>).</t>
        <t><tt>PEER_LOSS_RATE</tt> counts QUIC packet loss. QUIC retransmits lost data carried on
streams, so packet loss does not by itself imply Object loss.</t>
        <t>Metric Types are assigned from the Optional Metrics Type Registry
(<xref target="iana-considerations"/>). Values <tt>0x00-0x3f</tt> are assigned by Standards
Action; values <tt>0x40-0x3fff</tt> are assigned by Specification Required; values
<tt>0x4000</tt> and above are reserved for Private Use. A Feedback Publisher MUST NOT
send a Private Use Metric Type unless the Feedback Consumer is known, through
an application agreement, to interpret it the same way.</t>
        <t>The Feedback Consumer MUST ignore unrecognized Metric Types.</t>
        <t>Optional Media Metrics MAY be included in an MQF report only when both endpoints
have declared <tt>OPTIONAL_METRICS</tt> in their Setup Options (Section 6). When that
capability is not enabled, <tt>Optional Metric Count</tt> MUST be 0.</t>
      </section>
      <section anchor="report-size-control">
        <name>Report Size Control</name>
        <t>A single MQF report is RECOMMENDED not to exceed 1200 bytes, so that a report
fits in a single QUIC packet and the loss of one packet does not delay the
whole report.</t>
        <t>When the number of Objects to report exceeds the capacity of a single MQF
report, the Feedback Publisher SHOULD:</t>
        <ul spacing="normal">
          <li>
            <t>Prioritize including recent Object Entries (largest media Object locations).</t>
          </li>
          <li>
            <t>Trim the oldest Object Entries.</t>
          </li>
          <li>
            <t>Ensure Summary Stats covers the complete Report Interval window (Summary Stats
is not affected by Object Entry trimming).</t>
          </li>
        </ul>
        <section anchor="encoding-example">
          <name>Encoding Example</name>
          <t>The following is an encoding structure of a typical MQF report containing
delivery status of the 5 most recent Objects on the <tt>audio_response</tt> Track.
Object Entries are sorted in ascending order by <tt>(Group ID, Object ID)</tt>. Signed
fields use ZigZag-encoded unsigned values (encoding convention at the beginning
of Section 5). The Feedback Track carries the <tt>MQF_FEEDBACK_TYPE</tt> Track Property
with value <tt>ORIGIN_FEEDBACK</tt>.</t>
          <artwork><![CDATA[
MQF Report:
  Report Timestamp: 2000000 (2000000us = 2s since setup)
  Report Sequence: 10 (10th report)
  Object Entry Count: 5 (5 Objects)

  Object Entry [0]: (smallest media Object location, first in list)
    Group ID: 7
    Object ID: 96
    Status: 0x00 (RECEIVED)
    Recv Ts Delta: 189999 (ZigZag(-95000): 95ms before Report Timestamp)
    (First received Object, baseline=Report Timestamp)

  Object Entry [1]:
    Group ID: 7
    Object ID: 97
    Status: 0x02 (NOT_RECEIVED)
    (No Recv Ts Delta)

  Object Entry [2]:
    Group ID: 7
    Object ID: 98
    Status: 0x01 (RECEIVED_LATE)
    Recv Ts Delta: 100000 (ZigZag(+50000): 50ms later than Object 96)
    (Skip NOT_RECEIVED 97, baseline=Object 96)

  Object Entry [3]:
    Group ID: 7
    Object ID: 99
    Status: 0x00 (RECEIVED)
    Recv Ts Delta: 40000 (ZigZag(+20000): 20ms later than Object 98)

  Object Entry [4]:
    Group ID: 7
    Object ID: 100
    Status: 0x00 (RECEIVED)
    Recv Ts Delta: 40000 (ZigZag(+20000): 20ms later than Object 99)

  Summary Stats:
    Report Interval: 100000 (100000us = 100ms)
    Total Objects Evaluated: 5
    Objects Received: 3
    Objects Received Late: 1
    Objects Lost: 1
    Avg Inter-Arrival Delta: 6000
      (ZigZag(+3000): avg arrival interval 3ms larger)
    Objects Not Delivered: 0

  Optional Metric Count: 2
  Optional Metric [0]:
    Metric Type: 0x02 (PLAYOUT_AHEAD_MS)
    Metric Value: 150 (playout headroom 150ms)
  Optional Metric [1]:
    Metric Type: 0x04 (ESTIMATED_BANDWIDTH_KBPS)
    Metric Value: 800 (estimated bandwidth 800kbps)
]]></artwork>
          <t>In this example, the Track Property identifies an <tt>ORIGIN_FEEDBACK</tt> Track.
Intermediate Relays forward the Track toward the Media Original Publisher
without inspecting its MQF Payload. Object 97 in Group 7 is lost and Object 98
arrived late. Object 98's delta (+50ms) is significantly larger than normal
interval (~20ms). Avg Inter-Arrival Delta is positive (+3ms) indicating
larger-than-expected arrival intervals. PLAYOUT_AHEAD_MS is only 150ms. These
signals combined indicate deteriorating network conditions.</t>
        </section>
      </section>
    </section>
    <section anchor="negotiation">
      <name>Negotiation</name>
      <section anchor="setup-option">
        <name>Setup Option</name>
        <t>This extension is defined for MOQT draft-22. Endpoints declare MQF support using
the <tt>MOQT_FEEDBACK</tt> Setup Option in the symmetric SETUP exchange described in
<xref target="MoQTransport"/>, Sections 6.3.2 and 9.1. Each endpoint sends SETUP as the first
message on its own unidirectional control stream. Either endpoint can send
first, without waiting for the other endpoint's SETUP.</t>
        <t>The MOQT version is selected during session establishment using ALPN for native
QUIC or WT-Available-Protocols for WebTransport, as specified in
<xref target="MoQTransport"/>, Section 6.2. The protocol identifier for draft-22 is
<tt>moqt-22</tt>. SETUP carries neither a transport version field nor a ROLE option.
The SETUP message has Type <tt>0x2F00</tt>, a 16-bit message Length, and a sequence of
Setup Options bounded by that Length; there is no option count.</t>
        <t><tt>MOQT_FEEDBACK</tt> has an even Option Type, TBD1 (experimental number 0xFE). It
uses the Key-Value-Pair encoding in <xref target="MoQTransport"/>, Section 8.3:</t>
        <artwork><![CDATA[
MOQT_FEEDBACK Setup Option {
  Delta Type (vi64),
  Capability Bitmap (vi64),
}
]]></artwork>
        <t>Delta Type is TBD1 minus the previous Option Type in this SETUP, or TBD1 if this
is the first option. Options are ordered by their decoded Type. Because TBD1 is
even, the value is a single MOQT variable-length integer and no option Length
field is present. These fields use MOQT <tt>vi64</tt>, not the QUIC integer encoding
used in MQF report Payloads.</t>
        <t>An endpoint MUST NOT include more than one <tt>MOQT_FEEDBACK</tt> option in SETUP. An
MQF endpoint receiving a duplicate MUST close the session with
<tt>PROTOCOL_VIOLATION</tt>. A value that does not match this serialization is handled
as <tt>KEY_VALUE_FORMATTING_ERROR</tt> under <xref target="MoQTransport"/>, Section 8.3. An endpoint
that does not recognize the option ignores it under the MOQT Setup Option rules.</t>
        <t>The option declares support for MQF report format version 0. Its Capability
Bitmap has the following bit definitions:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Bit</th>
              <th align="left">Name</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">
                <tt>PUBLISH_FEEDBACK</tt></td>
              <td align="left">Support publishing Feedback Tracks on this MOQT session</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">
                <tt>OPTIONAL_METRICS</tt></td>
              <td align="left">Support Optional Media Metrics (Section 5.5)</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">
                <tt>SUBSCRIBE_FEEDBACK</tt></td>
              <td align="left">Support subscribing to Feedback Tracks on this MOQT session</td>
            </tr>
            <tr>
              <td align="left">3-63</td>
              <td align="left">Reserved</td>
              <td align="left">Endpoints MUST set these bits to 0 and MUST ignore them when received</td>
            </tr>
          </tbody>
        </table>
        <t><strong>Negotiation Example:</strong></t>
        <t>The following diagram shows logical option types and values. Other Setup
Options, including any required by the transport, are omitted. On the wire,
Option Types are delta-encoded as described above. The two SETUP messages are
independent advertisements; their order here does not imply a response or a
requirement to wait.</t>
        <artwork><![CDATA[
Endpoint A                          Endpoint B
  |                                    |
  | SETUP(options=[                    |
  |   {type=TBD1, value=0x06}          |  OPTIONAL_METRICS +
  | ])                                 |  SUBSCRIBE_FEEDBACK
  |----------------------------------->|
  |                                    |
  | SETUP(options=[                    |
  |   {type=TBD1, value=0x03}          |  PUBLISH_FEEDBACK +
  | ])                                 |  OPTIONAL_METRICS
  |<-----------------------------------|
  |                                    |
  | After both SETUPs:                 |
  |   B -> A feedback is enabled.      |
  |   A -> B feedback is disabled.     |
  |   Optional Metrics are enabled.    |
]]></artwork>
      </section>
      <section anchor="capability-negotiation-rules">
        <name>Capability Negotiation Rules</name>
        <t>Each capability bit describes the endpoint that sends the Setup Option.
<tt>PUBLISH_FEEDBACK</tt> and <tt>SUBSCRIBE_FEEDBACK</tt> are complementary endpoint
capabilities; they do not require both endpoints to declare the same bit. A
Feedback Track from Endpoint A to Endpoint B can be established only when
Endpoint A has declared <tt>PUBLISH_FEEDBACK</tt> and Endpoint B has declared
<tt>SUBSCRIBE_FEEDBACK</tt>.</t>
        <t>An endpoint MUST send its SETUP and receive the peer's SETUP before establishing
a Feedback Track or sending MQF Objects. An endpoint MUST NOT use capabilities
remembered from an earlier session to send Feedback Track requests or MQF
Objects in 0-RTT before the current exchange completes. After applying the
default of zero for an omitted option, each endpoint computes the same
directional result:</t>
        <ul spacing="normal">
          <li>
            <t>A-to-B feedback requires A's <tt>PUBLISH_FEEDBACK</tt> and B's <tt>SUBSCRIBE_FEEDBACK</tt>.</t>
          </li>
          <li>
            <t>B-to-A feedback requires B's <tt>PUBLISH_FEEDBACK</tt> and A's <tt>SUBSCRIBE_FEEDBACK</tt>.</t>
          </li>
          <li>
            <t>Optional Metrics require both endpoints' <tt>OPTIONAL_METRICS</tt> bits and do not
enable either feedback direction by themselves.</t>
          </li>
        </ul>
        <t>An endpoint that has not declared <tt>PUBLISH_FEEDBACK</tt> MUST NOT publish a Feedback
Track. When an endpoint receives a PUBLISH for a Feedback Track, it MUST reject
the request with <tt>REQUEST_ERROR</tt> if the peer did not declare <tt>PUBLISH_FEEDBACK</tt>
or if the receiving endpoint did not declare <tt>SUBSCRIBE_FEEDBACK</tt>.</t>
        <t>Optional Media Metrics are enabled only when both endpoints have declared
<tt>OPTIONAL_METRICS</tt>. An MQF report MUST NOT include Optional Metrics when that
capability is not enabled.</t>
        <t>These capability rules apply to all MOQT endpoints, including Relays,
independently on each MOQT session.</t>
      </section>
      <section anchor="behavior-when-option-not-declared">
        <name>Behavior When Option Not Declared</name>
        <t>When a peer's SETUP does not include the <tt>MOQT_FEEDBACK</tt> option, that peer is
treated as having declared a zero Capability Bitmap and does not support
publishing or subscribing to Feedback Tracks. An endpoint MUST NOT publish a
Feedback Track to that peer and MUST reject a Feedback Track PUBLISH received
from that peer. The absence of this option does not prevent ordinary media Track
operation.</t>
      </section>
      <section anchor="runtime-capability-change">
        <name>Runtime Capability Change</name>
        <t>This version does not support runtime changes to Media over QUIC Feedback
capability. If change is needed, MoQ session MUST be re-established.</t>
      </section>
    </section>
    <section anchor="media-subscriber-behavior">
      <name>Media Subscriber Behavior</name>
      <t>A Media Subscriber that publishes MQF reports acts as the Feedback Publisher for
the associated media Track. This section describes that Media Subscriber
behavior.</t>
      <section anchor="arrival-time">
        <name>Arrival Time Recording</name>
        <t>The Media Subscriber MUST record the arrival time of each Object. Arrival time
is defined as the moment when the last byte of the Object arrives at the Media
Subscriber's MoQ layer. Implementation MUST use monotonic clock, unaffected by
system time adjustments. Time precision SHOULD be no less than 1 millisecond,
RECOMMENDED to be microsecond-level.</t>
      </section>
      <section anchor="delivery-status">
        <name>Delivery Status Determination</name>
        <t>The Media Subscriber MUST maintain delivery status for each known Object:</t>
        <ul spacing="normal">
          <li>
            <t>Last byte of Object arrives and within deadline: <tt>RECEIVED</tt> (0x00).</t>
          </li>
          <li>
            <t>Last byte of Object arrives but exceeds deadline: <tt>RECEIVED_LATE</tt> (0x01).</t>
          </li>
          <li>
            <t>Object has not arrived but is reasonably considered lost (see Section 5.3):
<tt>NOT_RECEIVED</tt> (0x02).</t>
          </li>
          <li>
            <t>Object partially arrived and carrying Stream is closed: <tt>PARTIALLY_RECEIVED</tt>
(0x03).</t>
          </li>
          <li>
            <t>Object has not arrived and was intentionally not delivered (see
<xref target="not-delivered"/>): <tt>NOT_DELIVERED</tt> (0x04).</t>
          </li>
        </ul>
        <t>Object status MAY be updated in subsequent MQF. For example, from <tt>NOT_RECEIVED</tt>
to <tt>RECEIVED</tt> (when a delayed Object is eventually received). Therefore, counts
such as <tt>Objects Lost</tt> in Summary Stats reflect an observation snapshot at
report generation time rather than final delivery statistics.</t>
      </section>
      <section anchor="mqf-generation-timing">
        <name>MQF Generation Timing</name>
        <t>The frequency of MQF reports is application- and deployment-defined. A Feedback
Publisher needs to balance the freshness required by its Feedback Consumer
against the bandwidth and processing cost of the Feedback Track. This document
does not define media-specific reporting intervals or require MQF reports to be
used as a session heartbeat.</t>
        <t>A Feedback Publisher MAY generate an additional report when a recent Object
changes status rather than waiting for its next periodic report.</t>
      </section>
      <section anchor="object-entry-selection">
        <name>Object Entry Selection</name>
        <t>The number of Object Entries in an MQF report is not fixed. A Feedback Publisher
selects Object Entries according to its reporting policy and report-size budget.</t>
        <t>When selecting Object Entries:</t>
        <ul spacing="normal">
          <li>
            <t>If not all candidate Object Entries are included, the Feedback Publisher
SHOULD prioritize recently observed Objects.</t>
          </li>
          <li>
            <t>An Object reported in a previous MQF report MAY be omitted when its status has
not changed.</t>
          </li>
          <li>
            <t>A later report can update the reported status of an Object.</t>
          </li>
        </ul>
        <t>The absence of an Object Entry from a report does not indicate any delivery
status for that Object. Each report represents the observations included at its
generation time.</t>
      </section>
      <section anchor="exception-handling">
        <name>Exception Handling</name>
        <ul spacing="normal">
          <li>
            <t><strong>Object Out-of-Order Arrival:</strong> The Media Subscriber MUST record by actual
arrival time without reordering. Arrival time reflects actual network
behavior; out-of-order itself is a valid network signal.</t>
          </li>
          <li>
            <t><strong>Duplicate Objects:</strong> The Media Subscriber SHOULD identify duplicates by
Group ID and Object ID, ignore duplicate arrivals, and retain the first
arrival time.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="media-publisher-behavior">
      <name>Media Publisher Behavior</name>
      <t>A Media Publisher that terminates and interprets an associated Feedback Track
acts as its Feedback Consumer. This section describes how the Media Publisher
processes MQF reports for the associated media Track.</t>
      <section anchor="report-consumption">
        <name>Report Consumption</name>
        <t>A Feedback Consumer uses the media Full Track Name, Group ID, and Object ID in
an MQF report to associate each reported status with an Object from the
corresponding media Track.</t>
        <t>MQF reports describe observations made by a Feedback Publisher. A Feedback
Consumer can make valid reports available to the Application.</t>
      </section>
    </section>
    <section anchor="application-usage-considerations">
      <name>Application Usage Considerations</name>
      <t>This non-normative section illustrates conditions that can cause an application
to generate feedback, the information conveyed in an MQF report, and possible
actions by a Feedback Consumer. MQF conveys observations rather than control
commands; adaptation strategies and coordination between decision points are
application-defined.</t>
      <section anchor="relay-local-feedback-consumption">
        <name>Relay-Local Feedback Consumption</name>
        <t>Consider a live-streaming deployment that supports Relay-executed Track
selection through a separate Track-switching mechanism. The application makes
the same video available through a high-bitrate Track and a low-bitrate Track. A
Media Subscriber configures these Tracks as acceptable alternatives and
authorizes the adjacent Relay to select between them. While the Relay is
forwarding the high-bitrate Track, several complete Objects arrive after their
application-defined playback deadlines and the Media Subscriber's playout
headroom decreases. The Media Subscriber publishes a <tt>HOP_FEEDBACK</tt> report
containing <tt>RECEIVED_LATE</tt> Object Entries, a nonzero <tt>Objects Received Late</tt>
count, and, when Optional Media Metrics have been enabled, a decreasing
<tt>PLAYOUT_AHEAD_MS</tt> value.</t>
        <t>The adjacent Relay terminates the Feedback Track and can use the report as an
application-level input in addition to transport information available on the
downstream MOQT session. For example, the Relay's Track-selection logic might
change the selected representation from the high-bitrate Track to the
low-bitrate Track. A later series of reports showing timely Object delivery and
recovered playout headroom might contribute to selecting the high-bitrate Track
again. MQF identifies the affected media Track and conveys the observations, but
it does not identify alternative representations, authorize Relay-executed
selection, define when a switch occurs, or provide a Track-switching procedure.</t>
      </section>
      <section anchor="source-adaptation-with-end-to-end-feedback">
        <name>Source Adaptation with End-to-End Feedback</name>
        <t>Consider an interactive conference in which a Media Original Publisher produces
only one representation of a real-time video Track. A Media Subscriber receives
the Track either directly with no Relay or through one or more Relays. The rate
of the published representation persistently exceeds what can be delivered in
time over the complete path. Suppose a report interval covers five Objects: two
are <tt>RECEIVED</tt>, two are <tt>RECEIVED_LATE</tt>, and one is <tt>NOT_RECEIVED</tt>. On a direct
path, or when Relays forward the media Track without republishing or
transforming it, the Media Original Publisher can interpret the reported Group
ID and Object ID. The Media Subscriber therefore publishes these observations as
<tt>ORIGIN_FEEDBACK</tt>.</t>
        <t>When the path contains Relays, they forward the <tt>ORIGIN_FEEDBACK</tt> Track without
interpreting its MQF Payload. In either topology, MQF reports whether Objects
reached the Media Subscriber before their application-defined deadlines. In a
cascaded topology, transport feedback on the Media Original Publisher's
immediate MOQT session describes only that session and does not provide this
end-to-end outcome. A Relay also has no lower-bitrate Track to select in this
example and, when acting solely as a forwarding Relay, cannot modify the opaque
media Payload to reduce the source bitrate.</t>
        <t>The Media Original Publisher can use a continuing pattern of late or missing
Objects as one input when deciding whether to reduce the source encoding or
generation rate. This is an action that neither the Media Subscriber nor a Relay
acting solely as a forwarding Relay can perform on the original media source.</t>
      </section>
      <section anchor="selecting-feedback-tracks-with-topn">
        <name>Selecting Feedback Tracks with TopN</name>
        <t>Consider a deployment that supports the proposed Top Tracks Filter mechanism
<xref target="TopTracks"/>. Ten Media Subscribers receive the same media Track through one or
more Relays and publish separate <tt>ORIGIN_FEEDBACK</tt> Tracks. The application
defines a ranking Property for feedback selection. Tracks with larger values of
this Property are selected first. Each Feedback Publisher exposes the ranking
value as a Relay-visible Object Property on its feedback Objects, outside the
MQF Payload.</t>
        <t>The Media Original Publisher, acting as the Feedback Subscriber, requests the
five Feedback Tracks with the highest values of that Property from its adjacent
Relay. The candidate set is scoped to feedback for the associated media Track.
The Relay executes the requested selection using the exposed Property, without
interpreting or modifying the MQF Payload. As ranking values change, the
selected Tracks can change according to the Track-selection mechanism.</t>
        <t>In a multi-relay deployment, the requested filter can be propagated toward the
Feedback Publishers so that intermediate Relays also perform selection. For
example, Relay C can request up to five Feedback Tracks from each of Relays A
and B and select five from their combined candidates:</t>
        <artwork><![CDATA[
Subscribers A --> Relay A --+
                  (Top5)   |
                           +--> Relay C --> Media Original Publisher
                           |    (Top5)
Subscribers B --> Relay B --+
                  (Top5)
]]></artwork>
        <t>Subscribers A and B are two subsets of the ten Media Subscribers. Arrows show
the feedback flow; filter requests travel in the opposite direction. Each Top5
selection forwards up to five Feedback Tracks.</t>
        <t>Each branch uses the same ranking Property with comparable values and restricts
its candidates to feedback for the associated media Track. This allows filtering
before feedback reaches the Relay adjacent to the Media Original Publisher.
Selection updates, tie handling, and timeouts follow the separate
Track-selection mechanism; MQF does not define a distributed selection algorithm
or require simultaneous selection changes across Relays.</t>
        <t>The Media Original Publisher receives MQF reports from up to five selected
Feedback Tracks, each carrying the observations of its individual Feedback
Publisher.</t>
      </section>
      <section anchor="cache-feedback-as-an-optional-extension">
        <name>Cache Feedback as an Optional Extension</name>
        <t>Consider a deployment in which a Relay caches a media Track and serves
subsequent FETCH requests for its Objects. The Media Original Publisher supplies
<tt>MAX_CACHE_DURATION</tt> as defined in <xref target="MoQTransport"/>, Section 10.3. For example,
an Object has a cache duration of ten seconds, measured from when the Relay
began receiving it. The Relay evicts the cached Object after three seconds due
to local resource constraints. A FETCH requesting that Object after five
seconds encounters a local cache miss. The cache duration limits how long an
Object can be served from a cache; it does not guarantee retention until that
limit.</t>
        <t>A separate extension or application agreement could define feedback describing
such misses. The Relay has direct knowledge of its cache operations and, when
it retains sufficient metadata, can distinguish an Object that was cached and
evicted early from one that was never cached or whose cache duration has
expired. A downstream Media Subscriber cannot infer this cause solely from a
missing Object. A local cache miss also does not necessarily imply a delivery
failure, since the Relay might retrieve the Object from an upstream Publisher.</t>
        <t>Under such an extension, the Relay acts as a Feedback Publisher and publishes a
new <tt>ORIGIN_FEEDBACK</tt> Track associated with the media Track. It uses a distinct
Feedback Full Track Name and Report Sequence space. The Feedback Track follows
the existing establishment, authorization, and reverse media-path binding rules.
Intermediate Relays forward its MQF Payload without interpreting it. The Media
Original Publisher consumes the Relay's own cache observations, rather than
interpreting them as delivery outcomes observed by a downstream Subscriber.</t>
        <t>The extension could use Optional Media Metrics to convey scalar counters, such
as the number of FETCH requests evaluated and the number affected by early
eviction. These metrics would supplement the existing MQF report structure and
would be carried only when Optional Media Metrics are enabled. The extension
would define the metric identifiers and meanings, the reporting interval and
counting rules, and the scope and completeness of the observations, including
how to represent unavailable eviction history. The generic <tt>OPTIONAL_METRICS</tt>
capability does not establish agreement on these extension-specific semantics.
Cache misses would not change the meanings of Object delivery status or the
Summary Stats fields, including <tt>Objects Lost</tt>.</t>
        <t>The Media Original Publisher could use these observations to assess how cache
retention affects retrieval and recovery in the deployment. For example,
frequent cache misses caused by early eviction could lead the Media Original
Publisher to extend its own Object retention window. This can reduce the risk
that a Relay's upstream retrieval fails because the Object is no longer
available at the origin. Any resulting cache or application policy remains
outside MQF. This example does not define cache feedback metrics or require
Relays to retain eviction history. Interoperable cache feedback requires the
separate extension or application agreement.</t>
      </section>
      <section anchor="relay-derived-feedback-from-multiple-subscribers">
        <name>Relay-Derived Feedback from Multiple Subscribers</name>
        <t>Consider an interactive conference in which an adjacent Relay forwards the same
media Track to multiple Media Subscribers. Each Media Subscriber publishes
<tt>HOP_FEEDBACK</tt> describing the delivery outcome it observes. The Relay can
interpret each report together with local forwarding observations, such as
whether an Object was available at the Relay in time for downstream delivery and
whether similar outcomes were reported by multiple Media Subscribers.</t>
        <t>A future extension could define how a Relay aggregates these observations before
sending feedback upstream. For example, it could distinguish an outcome reported
by one Media Subscriber from an outcome reported by several Media Subscribers,
or combine several reports to limit the number of Feedback Tracks delivered to
the Media Original Publisher. If the Relay makes the resulting observations
available to the Media Original Publisher, it acts as a new Feedback Publisher
and publishes a new <tt>ORIGIN_FEEDBACK</tt> report associated with the upstream media
Track.</t>
        <t>Under such an extension, the Relay consumes the Subscriber-generated
<tt>HOP_FEEDBACK</tt> reports and combines them with its local observations. It then
generates a separate <tt>ORIGIN_FEEDBACK</tt> report with a new Feedback Full Track
Name, Report Sequence space, and MQF Payload. The Relay does not relabel or
mechanically forward the received <tt>HOP_FEEDBACK</tt> Objects. Intermediate Relays
forward the new <tt>ORIGIN_FEEDBACK</tt> Track without interpreting its Payload. Such
aggregated reports are not interoperable based on this document alone; an
extension defining them needs to specify the represented Media Subscribers, the
aggregation method, and the interpretation of each reported field.</t>
        <t>In large-audience deployments, such as a webinar with thousands of Media
Subscribers, the Media Original Publisher typically needs the distribution of
outcomes rather than individual reports: for example, the fraction of Media
Subscribers that stalled during the last interval. Such an extension can
represent per-Subscriber metrics as histograms with fixed bucket boundaries.
Histograms from different Relays merge by adding bucket counts, which allows
hierarchical aggregation so that the volume of feedback reaching the Media
Original Publisher grows with the number of Relays rather than the number of
Media Subscribers.</t>
        <t>Applications such as interactive conferencing, live streaming, cloud rendering,
gaming, and live-agent media can interpret Object delivery status according to
their own media format and latency objectives.</t>
      </section>
      <section anchor="uplink-constrained-simulcast-publisher">
        <name>Uplink-Constrained Simulcast Publisher</name>
        <t>Consider a conference in which a participant publishes the same camera source
as several simulcast Tracks, for example at 180p, 540p, and 1080p, to a Relay
that forwards them to other participants. Assume that the 180p, 540p, and 1080p
Tracks have the same priority. The participant's uplink capacity drops so that
the 1080p Track can no longer be delivered in time.</t>
        <t>The Relay is a Media Subscriber of each simulcast Track and publishes a
<tt>HOP_FEEDBACK</tt> Track for each of them. Its reports of all media Tracks show
<tt>RECEIVED_LATE</tt> and <tt>PARTIALLY_RECEIVED</tt> Objects. The participant, as Media
Original Publisher and Feedback Consumer, can use these reports to stop encoding
the 1080p Track, freeing uplink capacity for the remaining Tracks.</t>
        <t>The Relay can, in parallel, change what it forwards downstream. It can stop
forwarding the 1080p Track and let Media Subscribers select another Track
based on a catalog update, or it can forward a lower simulcast Track to Media
Subscribers that had selected the 1080p representation, using a Relay-executed
Track selection mechanism. In both cases the downstream decoder needs a
decodable starting point. When the selected Track supports dynamic Groups, the
Relay or Media Subscriber can request one using the NEW_GROUP_REQUEST parameter
defined in <xref target="MoQTransport"/>, which Relays forward toward the Media Original
Publisher and coalesce when several requests are outstanding. MQF conveys the
observations that lead to these decisions; it does not itself request new
Groups or select Tracks.</t>
      </section>
      <section anchor="feedback-for-many-media-tracks">
        <name>Feedback for Many Media Tracks</name>
        <t>A Media Subscriber in a conference can receive many media Tracks at once, for
example one video Track for each participant shown in a gallery layout. Because
each Feedback Track is associated with exactly one media Track
(<xref target="track-definition"/>), such a Media Subscriber publishes one Feedback Track per
media Track for which it reports feedback. Each Feedback Track needs its own
establishment exchange and Relay state, and each switch to a different
representation ends one media Track and starts another, together with their
Feedback Tracks.</t>
        <t>For example, with reports of about 80 bytes including framing every 100
milliseconds, a Media Subscriber reporting on 25 video Tracks sends about
160 kbps of feedback. Deployments with many media Tracks per Media Subscriber
can reduce this cost by reporting only for Tracks whose observations are used,
by using longer Report Intervals for Tracks of lower importance, or by relying
on a future extension that carries reports for several media Tracks in one
Feedback Track. Such an extension would need to identify each media Track
within the report and define how Summary Stats are scoped, for example per
media Track and per priority class, so that a Feedback Consumer can evaluate
all Tracks that share a priority together.</t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>MQF reports are inputs to adaptation decisions made by Media Publishers and
Relays. A Feedback Publisher that reports false observations, whether by error
or with malicious intent, can cause a Feedback Consumer to reduce quality for
all Media Subscribers of a Track, or to keep a rate that is too high for some
of them.</t>
      <t>A Feedback Consumer SHOULD treat MQF reports as advisory observations. When
reports from multiple Feedback Publishers are available, a Feedback Consumer
SHOULD NOT allow the reports of a single Feedback Publisher to determine a
decision that affects other Media Subscribers, and SHOULD limit how quickly any
single source of reports can change its behavior.</t>
      <t>A node MUST only accept a Feedback Track from a peer that is authorized to
subscribe to the associated media Track. For <tt>ORIGIN_FEEDBACK</tt>, each Relay
applies this check on its own session, and the Media Original Publisher
applies its own authorization to the Feedback Publisher as described in
<xref target="track-establishment-and-lifecycle"/>.</t>
      <t>Feedback Tracks consume Relay state and capacity. Relays SHOULD limit the
number of Feedback Tracks accepted per MOQT session and per media Track, and
the rate at which MQF Objects are accepted on each Feedback Track, and MAY
reject or terminate Feedback Tracks that exceed those limits. Relays that
forward <tt>ORIGIN_FEEDBACK</tt> SHOULD apply such limits to each downstream peer so
that a large number of Feedback Publishers cannot overwhelm the Media Original
Publisher.</t>
      <t>MQF Object Payloads are opaque to Relays that forward them. They can be
protected end to end between the Feedback Publisher and the Feedback Consumer,
for example using the same mechanism that protects media Object Payloads. A
<tt>HOP_FEEDBACK</tt> Payload that is protected end to end cannot be interpreted by
the Adjacent Media Publisher when that publisher is a Relay; deployments that
rely on Relay-local consumption need the Relay to have access to the Payload.</t>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>MQF reports describe the network conditions and media consumption of the
Feedback Publisher, including which Tracks it receives, when, and how
playback progresses. This information can reveal user activity and network
characteristics.</t>
      <t>Feedback Track Namespaces are formed by appending fields to the media Track
Namespace (<xref target="track-naming"/>), so a peer that can discover the media Namespace
can also discover the existence of Feedback Tracks for it. Relays MUST NOT
deliver a Feedback Track, or advertise its Namespace, to any peer other than
the Feedback Consumer and the Relays on the path to it.</t>
      <t>A stable <tt>feedback-source-id</tt> would let observers correlate feedback across
sessions. A Feedback Publisher SHOULD use a random <tt>feedback-source-id</tt> for
each publication session (<xref target="track-naming"/>).</t>
      <t>Optional Media Metrics and Relay-visible Object Properties used for selection,
such as the ranking Property in the TopN example, expose information to every
Relay on the path. Feedback Publishers SHOULD include only the metrics that the
Feedback Consumer needs.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document defines the following code points for registration:</t>
      <ul spacing="normal">
        <li>
          <t><strong>TBD1:</strong> MOQT_FEEDBACK (experimental number 0xFE) in the MOQT Setup Options
registry (<xref target="MoQTransport"/>, Section 16.4), with an even Option Type and a
<tt>vi64</tt> capability bitmap value (Section 6.1).</t>
        </li>
        <li>
          <t><strong>TBD2:</strong> MQF_FEEDBACK_TYPE (experimental number 0x37FE) in the MOQ
Properties registry (<xref target="MoQTransport"/>, Section 16.8), with an even Property
Type outside the Mandatory Track Property range and a <tt>vi64</tt> value, scoped to
Tracks (Section 4.1).</t>
        </li>
        <li>
          <t><strong>Feedback Type Registry</strong> (Section 4.1):
          </t>
          <ul spacing="normal">
            <li>
              <t><tt>0x00</tt>: HOP_FEEDBACK</t>
            </li>
            <li>
              <t><tt>0x01</tt>: ORIGIN_FEEDBACK</t>
            </li>
          </ul>
        </li>
        <li>
          <t><strong>Delivery Status Code Registry</strong> (Section 5.3):
          </t>
          <ul spacing="normal">
            <li>
              <t><tt>0x00</tt>: RECEIVED</t>
            </li>
            <li>
              <t><tt>0x01</tt>: RECEIVED_LATE</t>
            </li>
            <li>
              <t><tt>0x02</tt>: NOT_RECEIVED</t>
            </li>
            <li>
              <t><tt>0x03</tt>: PARTIALLY_RECEIVED</t>
            </li>
            <li>
              <t><tt>0x04</tt>: NOT_DELIVERED</t>
            </li>
          </ul>
        </li>
        <li>
          <t><strong>Optional Metrics Type Registry</strong> (Section 5.5), with registration policies
of Standards Action for <tt>0x00-0x3f</tt>, Specification Required for
<tt>0x40-0x3fff</tt>, and Private Use for <tt>0x4000</tt> and above <xref target="RFC8126"/>:
          </t>
          <ul spacing="normal">
            <li>
              <t><tt>0x02</tt>: PLAYOUT_AHEAD_MS</t>
            </li>
            <li>
              <t><tt>0x04</tt>: ESTIMATED_BANDWIDTH_KBPS</t>
            </li>
            <li>
              <t><tt>0x06</tt>: UNDERRUN_COUNT</t>
            </li>
            <li>
              <t><tt>0x08</tt>: STALL_DURATION_MS</t>
            </li>
            <li>
              <t><tt>0x0A</tt>: TARGET_PLAYOUT_DELAY_MS</t>
            </li>
            <li>
              <t><tt>0x0C</tt>: RECEIVE_RATE_KBPS</t>
            </li>
            <li>
              <t><tt>0x10</tt>: PEER_RTT_US</t>
            </li>
            <li>
              <t><tt>0x12</tt>: PEER_LOSS_RATE</t>
            </li>
          </ul>
        </li>
      </ul>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The authors would like to thank Cullen Jennings for his valuable review
comments, proposed revisions, and insightful suggestions on application
scenarios for this document.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="QUIC-TRANSPORT">
          <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="MoQTransport">
          <front>
            <title>Media over QUIC Transport</title>
            <author fullname="Suhas Nandakumar" initials="S." surname="Nandakumar">
              <organization>Cisco</organization>
            </author>
            <author fullname="Victor Vasiliev" initials="V." surname="Vasiliev">
              <organization>Google</organization>
            </author>
            <author fullname="Ian Swett" initials="I." surname="Swett">
              <organization>Google</organization>
            </author>
            <author fullname="Alan Frindell" initials="A." surname="Frindell">
              <organization>Meta</organization>
            </author>
            <date day="1" month="October" year="2026"/>
            <abstract>
              <t>   This document defines Media over QUIC Transport (MOQT), a publish/
   subscribe protocol that runs over QUIC and WebTransport.  MOQT
   leverages the features of these transports, such as streams,
   datagrams, priorities, and partial reliability.  MOQT operates both
   point-to-point and through intermediate relays, enabling scalable
   low-latency delivery.  Despite its name, MOQT is media agnostic and
   can be used for a wide range of use cases.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-moq-transport-22"/>
        </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="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="quic-receive-ts">
          <front>
            <title>QUIC Extended Acknowledgement for Reporting Packet Receive Timestamps</title>
            <author fullname="Ian Swett" initials="I." surname="Swett">
              <organization>Google LLC</organization>
            </author>
            <author fullname="Joseph Beshay" initials="J." surname="Beshay">
              <organization>Meta Platforms, Inc.</organization>
            </author>
            <date day="2" month="March" year="2026"/>
            <abstract>
              <t>   This document defines an extension to the QUIC transport protocol
   which supports reporting multiple packet receive timestamps for post-
   handshake packets.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-quic-receive-ts-01"/>
        </reference>
        <reference anchor="TopTracks" target="https://github.com/moq-wg/moq-transport/pull/1981">
          <front>
            <title>Top Tracks Filter (MOQT Pull Request #1981)</title>
            <author initials="M." surname="Zanaty" fullname="Mo Zanaty">
              <organization/>
            </author>
            <date year="2026" month="October" day="12"/>
          </front>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA72963bbVpYu+n89BXYy9omUkIwkX5IolRoty3LiXb61JFft
dI06FkRCEsokwACgFZbtfo3zQOfF9ryvCwDZOaP7eIyq2CSxsC5zzes355xO
p25Rz6t8VRxmiya/6qbLcjNd1b9Nr4picZnP30737rmu7Jbwg+f1v2dP5GOX
N0V+mH1xtF4vy3nelXXVZnm1yE6LfDk9L1fFF+62bt5eN/VmDb97XizKPHv5
rmiyf3/99PgL97bYwveLw+xp1RVNVXTTx/h+59blYfb3rp5PsrZuuqa4auFv
2xX+5R9uXi/K6vow27TTvJ2XpYNXF9d1sz3M2m7hWvh9voIxT86fuHLdHGZd
s2m7g729H/YO4FuY4Jt8WVcFfVE4l2+6m7o5dFk2hf9lWVm1h9mvs+xZuaF/
8878mlerorQP6+Y6r8p/0aIPs6NleZlf5rCO+Yy+LlZ5uTzMVmVe/7OcLber
f8v5J9MSfjKvVy5+3fNZ9r/KvLoOXvgcFnmzKYPPZdB/4gcr/hZWde/frvHz
gUFPZ9nfwiWc1vhMrh8mS6i67Gc8qGgBzex282951dERDrziGOZdVBVMpg1e
dLxZLosq/iZ+23HZzuvsbNt2xaoNX3i13Fxdbf9tjt8PvO9slr2AA8zfblZ5
E7zxbHOTt+lXA68MX9VW/PPwZVXdrOD37wokByTS6fnp0YuzVy9Pz2EzruY/
7O3twTdwC86bvGrXQJ1AadPHM744ZdFd0c3p9NvpwYFzrqyuwoF/25TzaVPM
C/j3tGt7IyTfT/f24aHzeg3vnL9tD2kRch+/gI8z/jx7Ui7hGmU7z1/++3n2
Cs4ALuJvm6Ltsi/3f/h+f/cLfjBvrguY9U3XrdvDb7+9LrubzSUu/1uc+e31
t9ECvl3DQN/i8/S0vyz4Z6q0Wmf/kVd5t5XPPVUHHy/gmh5mB3sHD6f7e9N9
2JfpdJrll3Bh8zlc+vObss2AE21WBdDiorgqq6LNmGnUyjSM+cAy//3J7gT4
TVb83hVVC4ecdXXwe0e/t3PifdnNupu8y4oqv1zC6ItiCXvcbOFI4IJ228xO
CkbLL+tNl61wQPfy8p/FvGvxDZdF1hQ4YrEAHgQE7ufEBzHLnvr539S36fcZ
8E2Xt209L3Mc5BZOgF8jP5hkcGgwwbK9KRaTDGZ0mzcL+GV3A/fw+gbOdZlv
W1z8Athh1cKWwe+6Gg72BjaKBoS/ZbBFMteMl0XseZ6v88uSllsB4+xKWu4M
fw2jrdbLAk8A1mpEDG+DYdvyusqXLQ+/Lpopb4rfxGDzZo6Pd1UuFktgsu5L
ZPJNvdjM8Wvn0nNNzmmSvX8f3rKPH3czII+cL+Vl3hYLt97QFn3bbi7beVPC
ufAm2ryzqwbIE0UQHEmVLetbWAnQynyb5YHMgn2U6bziEWFOc6Cry6KCQ8RR
6lX2tqpv8axvb3iP+VVKFrdFg1RBN3Yhm9gVyy3tN+5XWSGlBm+F+70s3uVE
6fliCbQy440AAoBXLYvFNZ8CnrGMDJd+hZSxWrfZuqnflYuid0jBGUyyS6Bf
mO0WrlVW1fCqEkbqlltX/L5uirbFL9tCVjGF+RRLf5pA/LAQIOG6CScOQhb2
cObOkxerskDHtGzrDJjqGmm2xpWX1aKE+cIt41UC1VbFnOnubzdF5ezo4N0t
vrQq8MWrGjZWyd1egVcdyZvPoCmvSyBMf3pftc6PDwti6ghue13B0cDEStzf
xT/zOXKcdVE0E9omHBvY0GZJHNulO5LVl23RwEFnl1v67aK+rVjtkCmdKUU2
s//PfA2FjGztqpjfgCRrV3iLQd1pmi2SYruZ30QMC4isx4o8CyC+k6V8J3cB
5xH2gKSfKV/BRSLp6jalNwUOSTYIKD+fNzWQFR8Y7vBdxwR78+WX2XFdvYNx
TXl8jBtU8r/ff7mwf33EnSwy0BkzVBpb0Cdfn51/MeH/Zi9e0t9PT2A3T08e
49/Pfjl69sz+or84++Xl62fwvZO/+SePXz5/fvLiMT8Mn2bJR8+Pfv2CeG72
xctX509fvjh69gXuOdzu1tkB4yazlChRq4V7hnudt0aHC3zm0fGrbP8+MLn/
cfrk+GB//4ePH+Uf3+9/d//jRwd8puKXEbHyP+kuw10scrzocM2WyMzLDu7b
BF/RgrSpMtjaYsa7dVUvl8y3YCorpoBN6yVJTQwioM9DYNvZ118jCz78+use
ldqlnwRDp5x6RkMwU8FBjpB6FshvUOhmGzhPWE8NjOdVvl3W+YI5e4vKSjWH
63UFNNcV7QTUhk+9JaFGfB2uOyDPKxg6JHEU7Nk10GuVkaIEzKYlgeWH89eX
ph/8+w8OR/eAx0DDqaqRYaP+ISK9jcQ+XqVUVbgsutsC2GPml8TXxM+p/fRZ
jN1A3a7+NxOmWORVyAHg/enIE9wLvN4R/0i5S7Igns7RCC/pnx6J3tubco5D
pYcDkxLBSIIsfHnvhNZ505Vz4OhNfEyoqgnDy2E8OjA8h7v5Fi7CFvYp4ot3
AC7xdg2idInKAb8C3htT2F2LAVkss7wG9aQBxg+nnoMi59VMNBb8ZtvrP0XV
yUnhtSUORq/vCtsd3C6vcqF4Tx5F6lYKJ5UJKAEZDUsU/ATkLlI03/5kmscs
d2w3cQa0/wML4ctkfLYlFTZTeTej53sDI7fBHR6jQhKyWXbxy8tXb56cnDx+
dHT8lwu6c3cRBS364uXp05+fvvCPJWuj7fH8gHeL1oBCvSzaUFynz27XBT9K
xzB9V7YlslMe5FUDylbTbWVHFihRr3BA1VeRypJjkp0FTpvl3d1bUtOumZyH
U4fhPn1HcDU7Y5rOLq/GlDoxVGQquD+k/cCLgHC6vERfwqDZgQrppqUDQEVl
8OKwrnGGKikd5QvQwH+u0Zp5/yUpqlP4dFrBp9f46cdUbWvXxZw2lAQkGnU9
qkch1mN/wRR+lAcHrMERe4/lvx3TAkfAveF7eFnc5O9KXHTy1iIHdhnRjT74
R+zBH8nymIKpvFjXcMX8+xoQ1CVTgTIh3lS7iPw3pEiS+PGt7GnENRAgqt28
x1u/w5HBhBropoU7DjoCeQAnxgHR1BGOtOZ/wSzbOWzmBgwrdJ6BsgT6xxo4
AHEsmJBuSb68rhvYtZXx1Q2aH/CjRdGgzYUbfH3dFNe0SmK04TaCgILxAwuA
jYPAG7qsgduz1aQkIPoxnvyiWC/rLWwmvAfo/Kq83jR48mU1X26Ifa5zONMW
rEUyZybKh6ddPeUJr2rQqGARuCX4QnqgKZhvsy2OvFwNe95N5OKw0tg+YLOr
rNabjjRO2PN8TRKG6RjmSKtxAXdXspgBXwa6wzHtRGHgJTCUwCKHJV4DsdMM
anQILNmLkfcmqFq9zRKV6u06Z6sVNqSi1y/LFVpx8HDdsrGCwqX/miXZG+5L
YCxg1OXshCBnQmK+mrHVsoEFmzJgksMZsEl+bia5I3pHImEOtobH4CqwVY2P
JEY48Xw2IL3+hkYfbLMLPQU8QmDowQ35kD0C0gY1cA0jfgCjyYg/++A+TIM/
0T+m8KWY+/CM8M+XYtZ+CJww8ZKDO4pk7IVKpq4OHfQWt+tdXi7p4l8WV2i/
JxdZHR6Zn8z0Ga0RNhM34QOoBrR3Hf/b3m5bF/gvMpSc7+CGNcWSb91NuVa9
OXHT4AuDaEV2Rqv5wHqGrd1eh1uQAQVviTBuYNpNDfpo4g9htWbtfSP0mhMQ
J3BDT8iilY2OreNwu0Pnifeb4GVMvCVCSLofhWphkcei58PRNyuLAwovkVDc
EdtlZCCSK+iSqAomBbslfB4f698OVjSUc+gLnTmN4EtStIUurmGpqH2jkMEl
mMzCM0RTMGKb6sCEe9ww3154JqTy/Cnq9UwRwkWRVCd3KzLqnOrrLs7rLuSR
8s7EOzxSvGnAXgrm5m0BhgZKYlCf3eCmgfpEd6KCL0nMtJs1kcBlDWtmWRFS
FLuY3OiCiB7suK/GJRFTAI4V0sCnXDR0NYCqOvaJItGRZ+OqaFADIPHX9cn4
kw46YNhiV4SuQGLQR838puzgExCEpLWZKvMc7OclEO2Q5pVR6GbJRMcfs49B
7z5z21C/Jr2kFK803SiS7nTjyHOMx03jiQyBg2zb/LpAE67grUm1TScz8go4
7oNcAvNwXBZIzhpFmJhxESltLhkEdaoKowB9i4YFUqgUwlbiUkUk0XXs30Re
gmltzM7QFqz0xzldftyLiZvfbKq3pFrVgQecvDll6CsInAKiZMYMU6YWRBom
GUzyhs25SpUGvF3DAQh2lLtUKhszFMEbeHuHOCnvujgQXOBZV6n//n0Sh/v4
kbQm9bzniwU5JoHo1qG4cmEYhAhuyAOtfJIjSKGYgjnWqFrxuWGEJ6+Eevta
QXTHdeYostDgVonFCmDPOFUddk6bfoUK5icFibq+Xchnru687ByGKAO5KoS9
Fc8OUa67qddIKKLtstoxz8VZiUTEM5hlv9Tr6eV2ir+nH8Nbr6u6BRosaXgX
kCLs/gyVpTOiHBC5PydyiC3CD9nTwI3+ig94EWpSsRY1pl1FatZANCckuTCY
YwqPHOogwUYKgx0MsQ5Wk8JQAE4ASc+0PRp5AtbHespCBi9loo+MGNbkhF4L
qYeaT0R8H2Jejdb4o5LFMz/Jvi5nv7DvQvbBSty7QgXTsDXPYRoKTDizT1EK
Z+IDCO6JWO7z4H2gnBbLGTphUo8iUZratK2XZ/mczaOISSdSssefXehxWhRs
x3sWGXt2Pu2Sih1Sk095KcccUsgKbM/U9Tn0QqJBHxbq+19pVnnF0kCchifo
ewgdlnMO/hVr3JsKdXcQUEWkTPkzdolvBAyd//zP/3QnOt2jbOyP/eQR2Mcf
KPIcTOIoCy/nnz9k2aPDIXfyhz/Bg4lyET3LT/YpAJ8dnZv8+aAvCGf2KEsY
R5YdDU9t2p9a+PCf+cmBqeEOUjCou617zic0rsmcRnWn7xoyvxRxr2YDei4R
uxtxTycqi2gBYNsOqjzoqHKpLhfRyqKYA7OG0RJv7CBp08QuXr1+9Ozp2S+J
6/bi7PWjs+PTp49Ogi/Oim6zzl6Kok1uBDA05oGF63AVdluIO9iU4KsVKwS8
1eR0Cv3i6V7XlWPxCqpz1SXhooh5noKwY5ssxHuw3iT2QhvYPDhvkaWhIRlG
cPvcxQU2BAIYlksO+Xxi0NAH7PmPGzMdIiaX+qqV6cOLzoQ135/tj+q981Dd
NSdkT+8lu3Cet/N8YV/ngU0xUbLE2FI+yj+dt/xAHepKUFZVUopbo0H65fBL
L+xPi+etCRimRB5sP9t608yLSeDUtTB7ZJgFnICUQd4Igi8YFKmnWnqzIjT4
AmXSqbXaCwx8Mm6PPEVjV6MCaPrnbDab4X+eHdD/7+P/91YU3mz3KSYa/IHh
/jTtD8fOUZXhiyxhE3dNGIbDCcN/YML4//vB4f1XDTk4aePR3hOYcg/Su0GJ
uQLTm3RjuQ0ckThKOaRKXw4rDYB6EgzLQCQyCj5YjAhWwPR0pd7gxILE0M95
+EMkOXGms/+8b4lI3BBvpKGoBkNwrGxEKD3zNgrZ8kvJfe0d6hyxWtRw5cS9
s6gJQ1NHt0/UvDiemnhbhN0XGMJEB1QLrBq05p4cY1uqhr35vUMbCW/rZi02
U+TKmmaD5plXoNColbcyHqevi/nAME5LYDzKwrJ/FU2dOK8w9M3xRkVhNAiM
BU2+Xue/bQresTACbA8OXooh81L8hyF9DdwRODfSCdvNFejpJdlJsX+VthDx
WhZgQj9WZiFDjD117VjMPLCnUf3t7x0ID/R6woYZzQo2CNWjhAqJsHBF/HJn
q2TGM3QjSFVH022pOC0h1YA6wJIZJA4EKDw/+hUBtR2Y86Zs9LfbJjYmkTPE
SP/BTdZV/qEtPqfnxJDDyEzT5QLs6Xp6KOgFpHaAjG/Vbxh5i57A7hW/5+gt
Qlic11AshpXyiVZCWLAYPg6apLMYWhbjE3wgtRoi43A4FtiOwmLi4JF4vCqH
DcFR8jA+GBk7gd9E/JDuj3GdcZ7DCjBiY+laixofBAtQ25Lg2SoHFWvekscY
54z70F86uXf7M55YAMiWJ8uFVSJ7kngpebZUd7LwL4UJ6aVMej7MEEK5kyBL
DiOSs1D3mVCULvBAkF+uqJDQJt63AjRfYbDpGrW+rinnydUkJYnWU2nM7XIp
GhnMGKYF7wRiT3kGe0VsoTWGC7qbeoGKfHIspNrzNfHYxuz9lwh7fzvtARzv
8m0bZuQW4wg0SWXecJAU9xcfDj5WOe/tFss8iFzDL7xMydssttMtnld2N25V
A/3UlaCWgPKAGMhtKT96+tgwzppD4k5iEALNGvkP3GSK4CHRxMYBbqgFfVfl
725A/A8bfeSPVyd9Ky/DSwJHtdGomStbUYcWKpxjIM0FbI4N/Ob811cnF4nB
gpfdnDuB/IqdRhTI6Yit0XKUYyPbG7m5yjQ/PQXaw1ywhu/ypkRynS6L6rq7
IdK+Bm1y5+Jd+fD+xS78YLkBYibEBJ+y4lhoD/qQPjXDvp/tU5D5rzhA9iF7
kVN8eDjM/GEs0Hyx9/ve3gU8l5zkB0r4IpvuSrxY48gj0aMGjOZM37FP7+hx
r4HXjOrp4god0JPQsXlCunNCzXS4DNPgq/jp03M7548egy2E8WtggAR2WGbV
ZoVayN7v9757crLr4GBQ0oofIx6hZP8LkLIRREmxtE1HKrCuc1leFcgDgS2Q
z0EhfaGsAkW7vq7KfwGdll1w8+oFuuYJ57OqUYB38YMugHfICDiAQVpZ+Zzf
8Lj5fF6zmBWdZ1OhR7zye0JepSFyJAgi7Ok0v831OASdE+2A4Ath45C6Seog
nxPmJAyyxUX0sYTmotUtYTgpamOVeFqAfOge8RY1xT81TpJCW+kKE//LMNmh
ZUAAMoVrtpb6rD3GvEzFIcLM2sXMGrSXq6kg4dSBRhpD0eivYMKo7S9E5eZZ
s25ZLxd0mQpSKNkPIZHoAOXOu5AP6SAgTVHTxhc6XiOuqIiFysSnHqlq3uo5
7LH6l0uaIaZ2yuswwSIXCNSybhVV4DWXS9Di3kZR7nDZpjWiD1PSP0NOnSWc
mqOLPcUEKRCFEi8OyLZYg24mGwLqAtLlquyQHIq8WZZ+29m+ReLE7KLGazqD
QpCo6DKKbOwf7g/gBeMAM+KVytZYuUgwG/sJpvvxC4hX73iH2sEuG0gGySro
pWWoHihXSYe5LBl5UYb+XP5evzJwg4tCwAHC70eMrAfATX0SnU8rDIvg8OrP
g10j8zz0OSJWQpi4nVqcLxdqLolodbrhAcbScBrLbe+UItAryW7NexKpQ+Oh
2TGkiOMGOr+Bsq2gR74Tl6qfp2pfoEuSGr0mHALhndTJ45R5GWMnPz2TKGhd
eK5eB6vRX6u4m9t6sxR3yW2JTn64FmDGUaIFvEOBw7NAO4UJUwqBaKYV/TPV
SlMKUQ8Te2q9W4YujkhQPD90J5hKVvTRswoSD5h4j4E/A5v04ptvLuC2ASkX
qLALChA0miXDafJgcu2awIcboJeIIQQXEc5RUl6SxxR+HpK8H1PYHNgk+mqe
C9+rjOkf5F7RHIo8BjIHuXOx+u3qYhI7gUl5pZCk99jqlzAUm5xwvrNkmjrD
4DDuzB1QHdOy+vHFU3rxhWHiz46fPkWhRfYgBov11xccT4wUOYef1KRMpb/r
6+lPfdat30e4GFeg6QPNkCdd4UYwJT4eMvu8UPksFd35NBsMupJxDfZESy/5
PCHu94h3f1ouLtikEucYBqCrabFag/qBuUq6ZexiMK+q63MVdujgJJh5XG/I
NiDB1Df4Y9bjiE8ULATJ/h5xFiirUq4xRhCsCrBY8Jhug2fkeD2a2DDr57Xx
ryRqw0aSXwk9x7si/g3WSiyEwviXPOJpzvO0dV42rIuSAiLJI8BYSPKeKaCK
qAmop2Y8MPx/9VYw7ZqTKHuCYZGhbROHn011kARI/UVhBZOsV0vLwRHhRNrQ
kMgI5C97iBYSfXIt6+24gxP47l2J3gsYqio6zFv2AdUm22nhKrx/v0bHyXz7
8eMuEGvkGzOOQoKSzjnl1hc78mvM90eXSIFbOnH5ZlHWbxQiv3uhrjUJwA8/
lQEzY0SJvnniA6DNdP872Op43DsHShjJhFyI2+lyf3q/P5AFTEggsqiikEjX
bAQoi96cIhK5nPTL9ydVtMYi2obbCDUgDyWJw9o/UhojqxbO/4i5nFIAQprI
D018ik0OvgNq8lEmSyqu0NiS5aXpbm74sIEHkQkn6F6QVGj6sNTyLFjlF8VU
Jc3G9TmjqDNPMY6hSFBjFOM8BrHsHjwuUFfWFTjSviD5N8FR5QoK4Je5/gUm
9J6cnb85OT19eXoRqisnETYB5/8MrN75dg73SXWYCL9AKT5L/c2ouy3UE1Oo
jucXOwP5iMPJecj0lKh3LaSPStpX3sr/NtOFvvwL3GhUqa8LR6mLlxGKqpGS
HmrnPB1y4ygGAsZCqeUW6rfBENyyzFmf9G9kPJWnXdj7phhAu1KFCM0Wwstl
YgM2Si2Oh2biaDYRfs/8PjoP4V/5YOiSlaQ7DPbBLD6XOI7yBGYxkhEo1h47
VOVEUA6Z1MsX79D70hZB6ICHT+iHmD3L5gTfcRRElxKPYd91VY5HA1CBcOQF
SX6RXP/JsJBkHTMI+9F4QYiW5qZeZZJSKfCMYypBrQ1QrlrLfuB8HuKVwII5
vsK5GFEAlPMYLLIQmnNjcFVSlI2ZoBOaDAm4T10hiT/F8mqWPWJaMx3aI8Ap
kmoIlgn7vIHG8EKRP4Wq20jJIAFMCDG7iC3Iiu52Kaagbp8o7Nx+gBAZTr9m
G4j0q4HM14mmwFAY2q9C/AJ9rTxg+KIUplFGEfk4nAdLnZ/C1p/ZM3E+RqrH
k+YiQ/gwnUdgguqCiaTjO47YZbzxXadZ5wMJ7QcSy+iHpsmz0A6o9ep7NFS6
hP7wBZyyY3pWxMruzw5oa8A0X+fXMSTUliHFRGjRnqCxmggZpAyhCh2kd2jk
YQ63ZS5QFH+pR1uDDG3BnPRKCFb+EYZU0HvDtHkOlMv+KLaCL3lkCtxLeGPg
+aPIbKib0EWuSgQJjHEfqiJGx4Q4bXHaFsPijnDYSnHwlae+lwQIgt2fF4tN
M+wlJpVO72aadp49EV7NmV77wFr86C+Onp+cvTo6PkFTbI4JymFIzIi7/TEC
r6sAlqU4kZLmoikbq73Su0Z2Z/kAFClid9f1qd2pLPezFT1SOZ9Ofutdcd5h
H2VRlhjDdm2BaDh8HOgD0xAZYW5Yua5e18taXNY5Y+wHEWFhxtSRBwUxkffZ
t9yTUUotOxfQ5zj0OzJHVRbD0tiZYuMP2N6MDmfp3JM9OB3Sb8kzzpssVO7Q
fYcwGvrllHZEnJgheugTrgW8X8AbOdwhHsEwtW5Zw02RS84uummCCLGTCQpz
RJ5WRD+iu39Ltw5DhbAGda4YoYEEzynxPOS9E/u5rdHZGskAF2ZEvn26AhOm
YnxVuPQYM7zR5MIgvM6qkV6komnqFC36KnYg4EkjGwriOq3bAMNeRqEy1JpI
kysWhpvBiElZbVhxw4I5QiaBtov1sALhPqyNSg6LTQeNU3RT5bJseFBFjQvS
lK/ycrmhcjziCxVtBWPEqYyikHFbL7FuGN0LIqLEqEPl6nPcYIiCpdAbIW+I
F/btBDyW2MuKe2j4L7NmAv8FMeO2ZU/RKn+LGlggUBcg6lnTHlThQrgZAdQs
CoUQt6buxHsmVW9GbK9P1eKY9eGQaLmEL45epzLNg29HzQ44yK+/fsxJp7EB
+gRR7ifs3jj8+mvnHuEZK3a8ZYibpkvL/GE3GIOuFl8IhX4YgohH0FyJRlVW
A0oVnJOlHIVsMQgyYQpVg5lcq1Lyfmk08z21AfaS7i47DUIgcIin6/0ZxVjv
9J79Nnl0JwUEfOsGSGI3eWpAY979nBwNy9PwsnuHPAk/JQ4o+iHMbn/XvyIU
U5Kx8ak/f05ehurQHbP602cM+eGPrVN4585dP4R1HuzqZqd+Or/ejKuxktL0
E+3FG/t39s03wUvxz84Xq9+usKxaMh58FP8w+yJyKn6xOxlYRpYNHdNk6Idr
4ZE/9bgonOau/vDzDy/QZO/c6v+Gw/u7FFkjTtIWv/2094+hw7sHRKrSU/Cc
f2iFvdfs91/zx0ZETPwnV0g+3q+/9l69U1SdiLcOeO7Msad+xHxZXlc+dmRE
lGQsdY5VfxAaV13RM42DWEZkCL15/PLFyZAtPRmTWhZhgJMYHCRZUI7TcYY7
iL24ATaEAj4dZsPyq3zotBWouwcFB4yWFoPsPqycExvKovpc+SADg4xb2FRS
KR3pCD4nwRCTolJ6p+74qkez/3gDsmgDULVNN0ARA3kMDrMymUOFmshmErNn
YmoOKncYpJ6riRKYIIFhyR6DyAxpiql3EZKVvhxZDrnxK45wjyq9Xh0VL186
lqBFKJliIFD142CQjI/CSSiNVcy9WZCRiy7VclVMW8TgorN4BEYTgONRo7h4
fvS/3xwfHf9y8ubx69MjrIzZgy0G2JAhA/6y3rBO5xAXV7NKxmZhoPKr5iaZ
K7QAQppF2C7z+1m+mHfjgglC1UyTCk5o5oJBVtabdih+Z1EHLY6DtIyaF4YX
h3iRbNBlYYhTX/7sjC26HZxd2XZ4beg0GUDfbB2ifGXBu8nprBAdBdt+tVl6
uD+Zo5zuhzWPCoIzk0EttU7ol1SlwdEAy/JtwaEw9oYi9oos36GbImW0SCmn
LAljD670BWiwhIPAqLyXlTBdbKV1WLi0Qjg+zLGxagOC6sST4loKUrNvLZs7
VJgw2xmHrT6Y7e862fzItKBX32qFiS55Rcryy87Zwmaq0/sngCuAZJFqqR/k
GYIwfwg1WaWQP1KeafhTwrnGmg2iW/eynZvyGnhEtwv/OsLvZRn4QLJrH7L9
7ENI9zQo1jmIBz2A//0VP7Wh3FGGr/HrN1cYBfyXIZQFxcESC8xn7Q1iNmFz
MV40Z1zAkEuG3et6/TOKPimWPV5CLIgut45C/T78CjeZOd0WSQSUy6mvDzfl
EglYRZwDnYyXLP9VOPgt/3OK/5wKihx+6RGKQYlCzpDKs3aFvoSrJp9r0RRk
XrxltIbwclC0F5iugQ3JdluCTFsaShMZdALnLINSWiPQ84AT5x4giUwcsVS9
m7JLFwHPR25C7nghBquTPDWdARqWMEG/FXBOlgAclJV2+SVCIqiCQ1TKJYRN
sgCMoZvF78ADue6Pz37mlz8hLJlUC2ytmPeVxeIviV9aPUCrNnMVc3jYuuXS
sPES7sYdI3b8V8XQP2MM/VP+nR915/TJcYZ9Hzyb2X+4CxsBumjrPMDOkPVa
4DD0ddhorHswaNB8PKS3MGbf/5Iqn2CFhTBLnQ3xPiRcnEuBkhKKTVLKGrH/
dUpUYtlgd5aeFsTrOipupRNCKn7Cm7fKm7eM/fkCOWHh1/cFbex/lNf/kV9b
/I9cEk2RRbSA/jt5mM4Bcxms/PSJDIcQtwv73U/ZjvztT3/KwPD+v+3ff/5z
9vDe7gU9+7gInvVP2ih/hh/Tw1P/2f8Fn1w491wmLDymPcwu9jBlee9ikl1M
KXt5H/9KfzugDymx+R7+lf52XxAKqnoRXIPqWJGjBM5EvnlPZRzpr1ZBMNsp
dyf+c9Pb5GNx1J0Af9pmx8Axu8FvdmazXbSvJpTMu1rhFcHoR0vf0M+1lstz
zoiKx0q+9MN9VNDNYDn7XmVRtKnwsuyxSL9AIk9rLzipvbDjfV5wNFZhQfEi
bCqUrQwdx2MMZBAmtOvLObWCZ5DMq4+HZqFjRkWaMOWrON1VgFbRtaEvKC3Q
ihw2VWoQAx5gvYHjFkVYFWGXPI99kuF7s2tw1ZqOJUlSxcUaVG3CPvkRM/Wr
VuP7mvSVzQl+z3IKdmlVIqAOzZiFwsbpOwTGUYxHOVe/RiaWQuxyCazn1fyG
qpaGIpkwswRJw8PBQQi9Ny24zFHBVj3FOrLnyQwVdkIAK9oNGBPOkHJgUEGm
X+FfsDBcdQe4Bydk4ZC88tkrrucQ/tGiAqwcMAgN+3oM5OIM1EP3h+rve3Cm
z8dS79h6S9BtKC4GNCdUHq7ztdbi4QoniGUVZqx7r40G2BAL7KB1DX/dyoos
cBnUh6Qoy/UG7adkNRgICPCcOA3qvjUx0ZOzphwA2X+GH6mXLqlD39f970Cm
BqG1tkVcCNUT+6y8QpJjxk40zUCrIeABYK4IhmycgOEEj2I1/mClrcXsWSWC
X3/V+l8waBUpYIi1B0TwghPEgH6CH5YaReaSEd7V4+SmttneJOQBkjsklzQR
DXi0N0XedJcFIZEbLKdL9idIs3B6LMmiCaMsM/huLJL8B2fMI+Vffx9jDfD9
P0zUJKuVHFNLg0DerHe+5UQtZCvtXJICiJfgLb/Yoem5p48nfmK7LKq/tKmH
+Vs4bzkANRA1sba6G2L/pd8vHTLYCx0zWEqAPOF3j4D4XQhQHwZ8Ek8IsCsT
W80kSRXRVlEugnBGVQhjZGsvwq/uSDqJsPSlKpvaXCgsDRAnIHLIqx0McwIj
G62J6DOX2b3n/Y9RK4rAP+cl8JDsNRcxTJ0bn/k0lv7hMiE79ziR/piXZQcc
i+8Hs3vEO+litjLOyA1wWDXOF5Ykd6qidHX4SZao3buHwEPJ8RowcZko7NbF
6cnxydO/njy+yHYwJXeX6mfph2+eHZ2f8DegZWSqe3O1L1HIn5RNa+mRizA5
PLmQwK12ylkxkxwXeqwgLkGZ5MYHgikNzEU8VoqgVcwsS9MWmCKnAp1ewIBS
/binGRFbP39TXugveNJftVYwGoXyhEPxlLQTKjaaU/j5ChJrHHwwMBizM9x8
mEM2zQi7jFuJHiKSAL39xNAGL+z8zT9t2uFszVlVt510P8FEMvwvHZnf6c/a
509MGWdBrosFmlTqu1YIOu9tjq/IvuFnL0znuRqkFxYgXP6ZFhk/SJpLO7o9
/LiA/2TSNmXNizS4SWqEDtQaewCLuwDu8Mb2CMy4V0en50+Pnj37NfyUaAl/
+fjkGXx0ittZiFSiss9vy/Wac7/w1Quv5SLgrMQLnMgyeopllhdQWSKg0I+7
9BWMVzlsXsNNCTbk5yAJN5H3MXdR/2tFdSneofXIGp/ui1b2pYEWTnNZA8eo
OMLT7ZebThdwlr3Q8fnlVCmkKVR9ZwAzzKhcWCoLh024hi/rFcZChViP4Qjb
/8qyA574P8Dg1pTPVhZ05zNjLqpO76sLJBxqeDwECRW/zzlddXzEAxoxojxc
bC0+GT89S4X2nkzmAzrSPRppgGappGwDdvEyHRTn6IuEAG1qBX8d877NLqB2
nJ6/kT5RMSj7T3X6WG4tt5LrpK5CyV2CD6f2IbojP6Q3kK/a0IKsvLPBYjk1
24NJsEr5at0xNEleIy0QMRcQSbFWwsfZ5nMwItOFmpXvovdQg0cklRuUw2jo
m8PzEk8YyXrWhwu1mW8y5ygFt/dCrImCbngpkKS3hUwW0RRC0oPLYFYIlZHR
M6HWltNF+G2a4pJ43S21SU+x+H1dCpVRh01unUXSbgmsxwqtWUsEpexDQux7
qhqR57HolZvCQWgsiEFYLB3bsSfDB3d7L8UXbSo/q51idj3jxMwGG1DTO2w4
tApAearb3cmY1W/5R3TlAuYRuLRdKkKTHDxyWUkMOO55EaSRUXHVYLts8RSS
CzYapaKtO+942y7292b73wOD+wxVxfWUFAa4Zsu87Thzle8DlfejkX94YCNP
IsOndVZrMu8dsQ0cF63w+ZEy/MGBn7hjJsKFuz+hNaj00ToTHN9ONGhRBwyF
QAm7SnIHD0DBW8LGyK5JRtKQ7sgJgX2CU6a3/2AaDEVVHyrsRoJCnVwBcZkh
XoejdfwYNdzhFbWbJUnzAiW4F9RhEeu1liS3ZrHOvUrnxxOor7pCk3k0zVQb
+cBm/bOkXg6XG7SZOAuHzCenXv/hSlcUv0byEz9D4CbGn7OzmENBnOW9GMmz
jdqGpHxCbmBQVMddnB+d/nxy/ubVs6NfX74mznn065vnZxdaz2vn/XstTj5l
7DJ/0aJ88TVG+klfc83+sVp3dtDM8vNWkkhZUUBBievTydPWetuzt2/CvUPx
JpSGJ8ytbkYZdMyLooYMicAk3koV5jgG6SuI+qg6YQeKTiqFBip2YMhp5DZ0
xIXGHazsOvRPULUVdfxQVSrWKLXrcGl+cvakdloX1OwwY3uRVOAiYaJDXRxk
/+//Yz98o/HIC1Io0Jo0Vf7+7OGudynygKymVPXAisPYqjT8awo6SXLJmQ2e
HWSSGYJr/oLYplbUByPsi0zlSrYz+J6uBrFfXuO2+jHJmR/8k2QAX36UgHj8
stkz03ZQ27fqNNqi1/iMazFDAbZQHySpYP5LziJoB6BcqDHV+GBR3SBSHGWu
o24bzE0CVhY6WowYLIZJZQfpQa8cymtdmnjHOOWtOOjIHuyCwQVoILWuvAXM
lYy8NYL7YRNRV8/EZwJOuH9EKGujVTh7OOnq3rtkMwxGR51kZE8e5x0hp9uJ
Y8wNobyBEnToSXjslpPum/FYvbxPpT+oVhJf/qtgWszoWAS5bYFcNm9rZMbb
SMPgezqRTNb4cczIp2kFvIN6DyRK605flxd211fdQTf0mR/w/nQbU2jUYSYa
nyClUDmwFogYAwCpcQYS4ez89OToOfk1QLdBdXXBWQsCf5jYm7hhPZtDobm2
gNNzHqsVnf+ACSKnpOgKTKRvb+rlQjoq14FC7RukDbxW9AF4Fkv0fMaLiVsF
2oCVCXtspBz2s7e6qP5K2VzbXkG2smEFZr7VUrZU/Z0cP6OTZ2rhsIbuMgei
Mm7GKI3zMgIYOWOt0kuIZrgscoYk9AvybiolFnY9qaLUaT07vjU9XSooB/rj
UJFkmjV33mJYJQ1P77LyIr4xhuZBIJ/xfqUXJ3978/Ppy9ev3gjw29excoGT
aSCTb4iHeOJXVnKYscMo+tB0SxdDaiSE2Rk00Tjw1mQ7dcHSgXbaXRoKhZdj
1ZOiVIEfAG+FFvseTD+/GvnKabkd2uYW2wWhKkBG93IZrIW8iGW3EUiv1xPe
FV6L0CxyDqviL3ubMcDW1ArM+7LYBUqKNk8ZuFV2v1kRWWN5g93IEhIc7edw
DNwskAZ+5uogDZbsbMm9d9wtlbQmdKBoGovO3n8ZM2jnCGWUdBEX3JB0psyX
t/QvcZ1woRSZEAWvfcrQ1ikwFGnQQyOl8Lh4R2LhwiXJ5Jy6uia+I4UMQ2Q6
NZhGQHtYG+VnFdRUk5KAhowko5qGXq9G1mOumwFtmeZAeWu4zEvu2Ol7xWaa
wIZe/votYWVd6JPRwosjFSTJziLlC38MlI6v61CewSFs5oX7bZNTp11rio0q
yrj8/5QdEMhkhfkC3Tru00dvDVydObaByoWjiRrvzQWUs82Gy6HhbCz5NEgF
J+ftUhPIQwcg2MOZdAcMCiywZq0ap8Zx/DLY8Tv5BAZgIm2dSLxcmdFRez1Z
YQ1SROAOtLlaIbI2yxJInJnoQOiUvfoNYEOp4pxVCvlRsTfYix6qPehwKeZV
D59ZN77TZRZFmJQKqeY4XgVtd8uslWu/yEp6Uo61X3puXSyCW2SSM9o6311b
enrzNqRw20wrCfmrJ4U8L6nFw7xYWkyY5odxfq4HbnMvomQTDb8MeV+Bmrex
k4yKjCjwZUhr+Kp1LLuBst+VxW0ME0t6zlHtJfPnUolbe5lyXDdwyZg3IbFj
vp9M6ZKBJYR29o2H9f7wLYisLk04WQCBI6O5nRoHjTgmlloiDkLVk4qKXUro
hen7M1qv3aguii0nURMLuyFzVwjEanu0de8YdBI+Q1oqwegXz0B9EKhjDCR5
hF5GxojEXwSAx6dixSsY5LzGKsg69IkZwhGUxNx9458/w9UkX+JE9bOjd9f8
7umRWJSGOQkfwUDHYx+5wC8FjxKviAsUssgk7BE5rRhISNc8ydEy76A2pF44
4S9B13VsQ7XK2QO59a0mgVRBnt4Wi6AXOdJ4VFbYJaQgUl0ytmNxzrFUFjvp
sfC7kJrjBZdx/VK7iOQgwUJRQElxmHOWxf+WThbs3TPPxqZry0XkidWpOJmK
KHWSy19vWrJIRC+KHGwSlY3xF9/N7u8a6iJ+gVl0umoppU5rKnwtWzlHj+8Y
BELqfNt1XomD8KIHTJimk7jA+9r7HVyvsDKzgboe7MGf6QH+/16284D+ump1
fSN3CdZZB6XGDUnWekiSd0AFsI5h0pi5p3yGrT/EK9LxGQuDB0+3o0Btx3MN
u6nfWBGH+PJ+E9/bb4bvJDIewfKR09LXXBaz7Z1m4Qk0J2ppu/P+vQriKX+P
uR5OwUqbijMa0IKo8jUYzaDngLpY3YmpjdIzEo1wLv1Ui9aGZ/ePWq7WChpN
840gR3WDeAwQ5HlDNMcxi5y9X2PHE6DQ/K47l+II2xiQptsVRL4CUrhzbDq+
P/4CDQ9+4i1IDJ8/eKzwI+plwDJzY+8cERLOHQmTU2+k+qKpaifz7lF4lmgG
wCs2GIRxqTcFq5y2/W0Y4DLH+XK+WYYdRw7ZsRAM33PW8PA75XQfRtwNcCeR
492/XtiYFP8kgAeIQcyiOML/TrMjHGt3VxoZRK55NyZlfyIo9Y6OtstweczM
YeH6Nyq7c4FvsHLEKfZJtUFB5AzEBfhB1wst6C+w+TRtWxs77IbG2gks212u
2YZFOznL1DzKQgUY+F2W3iVzZwPsg1n2Swn6eYO47iwfoyw5Ee19oZnNO+2y
lApXeEy7XPWnKsqO23Lj8qIAx6ci3hsqbUSPHSDysi0kgMOoQ9goTBN+VXNS
sAKNDEkeIorC6V8TIlqgRbq/bkdA7LBVv22KDV6PiUcrpWNjklU8gAQgr9AC
cfTNQQ9Ix2llWXKZgiUpbBjXdRQSGYl6dJCiHFSG74PlcXN0jpxjBqGsnTAH
6AuneAGTgHXRlKda6rjxLiegHtyGrXeXsrOUvdWUBl3Os7fFlp2moNOgO1bt
ds91JJm2DV8gkAXeH9nmu+ApYRzUNol8kxJYsqhnmN4nqdOS8UJHl3DuSG7/
MRYeejZ6vFpqaZmfR1TrUAcfslVGotbvvxyJIDs38kS5ksKDlHSBHpRYV57B
64eyrC6cLVjzBZnTecUs9FvGQ7Q/Zrlv6rHn9JJQnoo16F75ULzth2YzScjc
yvF55w/aKpif8C2PjxJjllEFoyBhEh9Bt7QbaTzkkxfVAXNVm2pmrQxCBKaI
mHSv3lNLTfor5VWLhSYfMTowNMwey+tkfVxJCzcA+7AwPWCw47bOcL+uazQR
DrOjwPn7DP3mus8ETCH/O3+sRytfU8rG6MNUn+SD5oMLgvF1Bab8CJBx8D8J
nJERg4qBOPrl5OgxYSA+xJiWD6CQqbec2Bln3xuSBXOQl+O+fdAOCLrN4BDB
CuK9wmjimvP5pQD2ppH2d2eYP1w0PcZNIbmG/Vf40p090ABEki23/GGxAE4Z
ww5Pzs6fPgel8PGbR0cvHv/t6ePzX9785dErWurbyzUu8RGcDnBOLK7VwiLx
ZWYLjqZ0ST4YP+CVp9HIms7qIc3qNZhgp6evX7w5fvn6xTl+JP08PgS5OdRz
7i7jSbvP8Fnc2ashu8kXVowvbnG6tu6m0hZlR7A8mJrdNJsq2NPvafZn56D7
WmmOYbph8zDRA3srgGMnvYPk2WeuBL2pctp+Ykc0sVFoT296iHVCjym32ekQ
p3LncX/VpkCnMSjtZCB620uNwBIB4yjLj8GOH4dg4Tew4ycp+Sb19hide/cW
mnozfjQTY3WyJ8n3OEPgWuNMzcoqeZmgkgQ0LwwhtvJA1Hz3kiPhI+hDTpSg
l2rVG19jaKi23n8x39xnGPirk5PTN6fn529eC20FeR4f7krxSGfermqMeS8y
GGySFENGH45+/6bpOgzPZVI74MAIZP/Az+jZy7MzIhH8CFE/SPTFH5vRGn5W
dBxsksrtRCI98tDSs6Qb+ZeJZ+0BcucHs73/SaScJt5Rgd7IFcgdxNn518Sg
T08dM1NgnOpN6tAka4kbn2En8oADW69cKsmxLLDycRDWR+HbY8dkDA5wOYOM
C7fuXR9nnC1Ua1XJIni5pnMzGjmshxQCCR1Gz7GwJ46tjDgoSMK1mtWNHtvq
1lJVa/bgYCtqE4xdZ1GFks61FAilOjbTRsReUG4r8IqxAUoCTqr23CFYh0Xg
xIlET2COfdoMcK+EkOSGJpVYboWLYdBXQSsNapg6yC3LKIYX1bh1Uow0eJn4
0wamRmVgI7Rt3nl4p/P5DLb7XFIAHeag4y634UNSaokjMnQDMA2GrG4nmie8
irvLhSEX9vejFGnn9bqgNhSIUr+u82XLyKkeQxBPIV334I7P+BMPAmm5Yx5h
NgxTUjkD/LV1xCJ8Sz0FyVELQgsLSNZBoHuLM7QVl5Y5/VPbhBn3aXGNPb62
aBOXeZVPqcrVQgQuLZbV95azdKZ7v9+7uohfcUlMplpgGWl3NGcwzzt76D4/
dDX0mBSaZ1o7ld4U+rCjhzEziKIxlzWhTQhXJPXEaira9A5P+3U7VvzMckop
HpeHT0Q2i78Bw80rqAvmRGPiLq+G+x1P4pbcZecRubf5NgUOHEclz2BjkDtv
KmvUuQiniCc9Yt9inCaJacVV03ya6WVU5tYRiEcqeGBe/SvkxkfP3jw/OT99
enx2IU6Zssniuja+BMiupbLnne82stXLafDyEQs78u0EpVjQK3IsVxGzZvol
n6hKE7P7OIshjMPgFLDiPCGUs/2DvT1W4YJ+llpj86pkbJUJkfA2K0aWrqWA
e+WroGM350oX7vamtuJRmhITuw0sblzrxDW9hqS0FOFiGI9fpNN8ijsdhAQJ
kXJm1O2VyILTw+cB2Fn1hR0CkrddnFCOCgyd9S4hF5qSGQl2Jm3TIfAXJ0DK
TZEqHh6MbYC1kfjlTvSky6xuPogy7dEWpZjAm1cIytdYmmVCSwW4VD/mhnDm
82i12A9vcrddk3c3IKUAaZHWjhED4AGX+Iu21RJ8eiXgJC19PLX0znIIabYp
2PKcVBt4fDiJdmrZtVowSdjxji0elvaOs//UvXAJoqCitWIgWR0+u0nNSzZw
wiaSn9FFmXyFrKP1Gw2mpZYOByotHWYcP93LduQvcAQ/ZQctXg2szIGsabdf
iukw24dH9vc6LRO0O1iX6RDOceeBFXF06Y/+vvePw2yHKq+N3pKJZEPBEVLG
LTbCsHIOh9l39G87vcPsh4f0CQOqDjMUrtmO2rH89Gkxf5edtxyPgaV8/wP8
yXb4jHemP2BkeRdGerCy7Kh043igncFyABPKAcD8mZ/6j/W2YP8fh59c0nfp
kg6ynTC6J7N5UcdLG3jbwWe87fv0bft+A8kRMLyLQkeyi99QeB528cEe7OLS
xz/kTT88lEmfvS3XMXThh++CHQx+3lvMvc9YzA9/lBrux8s4kGUcjCzj+4F5
3f/0vGC3/psn9gNNLGL9hzJsJCX8ye17BrBPUAr6+QiQAg42WJMPgB9m9wY/
p8A4vCv6EiMS+tlIuPQwe7gne5X5xd/jtefwTC/ado/2AxO4dqOXRSEY2HE3
VgEO9nTgK+RVNF6gOOpdTP3Ru+EPSc2HVT6ALV6L++6myBdNDRbE/gPZ6N7r
9kdedz/bGTNhh177PZ6s+odB1JvPGL5AR5x0kHxasXFp+bsogZLSxVagh8R9
v1KU9lLttaOyeozBqEH/m9GmCAOtkFGTjHq2Kbl/hwKCL9x3qJCQNRjU+gGu
ppB3vCz+we8JZUrwt2/oMKjYL0h3MqDIRx8WCq3QqbN0Rm07/3lAqKNRUB0W
6dGAMRAuvcAKUTgeeopDT0dj9WDtphSWaY05IiANAzIsmVwCl5J/IVEIctSC
3qqdGBnHHZQbpsqjLzz+jiGNgWUiBQ+L3zssis11A8PoFqHqF01+1U0PsDOZ
9fsQG4hr5kshQ194b7AcorzS0i63K3ErnJ2cv37lm4SoX2sx1DLKypS22cPZ
vdkBUcMPs30pnKKWmlSz55HzIP9aG1qh1olkB1YqtkEKe1CqR0N7UJ4w8sCG
JpAs/MvRgL7S223O9Xo1CaKOHvtKZiM2LW1sUKzRWitLEELREEPtho6evXpB
b6kIVeDI8IJ//u18eqSxlClc8K6e10tOyvhbcWmbOMENsXqud24y7PGB1qzm
4cKWvTiw0gYm0F+s6t/w76hr08ar4qvgjTxI5dG1czC+4uaiL5+dSKh3RrvE
w+iRYcoKOR8u9n4/eLKHdUvzbP/h9LLs7Ddc51bTGKwYXX2VFJqlmszqfwOd
np/7EQ/O2mPxTNhZhV6shKgp4YbQsJowTrObZOePHoNyhRcfTC70Xxoyce/3
Jye7vsUlUslfiu2UuPr0FTaD9qV0hzqf6rF8P7snseVoTvE9e29FjzjKjBV4
KdB87L0OjwiPa99ZwNmegp2g5YDluOEJWwWdYM18p0shcUpooKfKK/rYRRUQ
5IB9zV+0KdF6s/AO7ANnxi1odKttKIO2DvecpZkBR73dTzdrJIQvGdNysnzo
bBESS2d/szDeEBsQ1DDmbrIKFuiBA9xGohCBZazgAG79aYzEsl8VMxzDH1N6
q419MiPB0pP4EhsvTChabNjbVvBbKF7NbFcYCxUsu3h1+vL85fHLZ2/++vTl
M+5tgI5B3lWBWYu7hhvMd1yuGnZ3qR2YSuz+VC2WklLwl5Nf3/z16NnrkzdP
Xp6CQnP+9MXP0t+YYwd30zWlKuiSXDwFc/Qxf5X9IDcg1lmR4Ttlr9FtoHpv
wnzlycFKvHeW+n0KEsPfHie35yZP8SaXpdQOZjlMhfQfUazvjppPo6G+PYqp
SXcRTw9Yjp/nHdQLjF0P4lzBct1h8xAcFOvlD/gv/aAjvtMdX5TgwS6NdEBR
eOvxNDRB7U4jkcTPnuS96cN7BPsQH/aHQAMhumYsH17Wy5Ldg3u+NKI4iOH7
FTtzzaSnaHGgF0WdzWI3mDYPa2/qW1RAr8ntJRQkUJxKXUbA1EjQheWf20ng
UcTM1bCrdBemt06YFXLyKwylmLCmmLiA2Qr2B3m0ua4oK0zVJnL+s9hGUFAk
RLmISZjoYJ1dKDH6R+G/7E4jYeiTjCiWkmfqoiPgZ5hWTQ1hQQsSL5WeFTCU
0T/2m0d/sIEZLmqHj6H96e/jP8yy93hKP6HomPAx/YTIl4/BD8FQSy5C9g09
/I+089rAW8J+wkr7f6xd1P9vi74XLzplKX9o0emO/Tf1AOOuVRSFodW3h6NL
foQl6o+CFsatRlNm8Q+P8IePoh8uyjb4pf6wFwXEixeOKV28wKgKdKqQr1BP
L4EnBsGey7B/Bt1yE+KcAllop+dQhs3cgBRgdMAA96X6JhREUCCCSdWwyT1d
+K1mU8llTsJeUqqADD6Lz11SWmHauokiqMHFhyf9FdfKLmE/Ugu1heziJm+D
KNvwooNhw5+7oc0YUrw44bAzI7HSXFIJhheES+EvxV9s80Y9r9e5p24sjzVo
TxHpM3HD4vAYHHJQtBGCqlZavFIlIqINcdLJe6WQQ5ux9mKwYVAU96an5+dh
LTAF25uxrWEmaxBHTaS0qS3oMLmU7/pX0dSc1OArqzMnmnBpU28fM1ikNVJx
oXXNVRm4VtO0q6ePwv4zUnH96Kt27NQf4VeDJzzNHuF4RwPjPRof7+iO8XrX
f/h2fDWkR5E6QvXH6GJhmjhX/RBT2CZpeyPqwKotlu+K1FTgVsS5Bk7Hb4YR
mOiEQS6/lNiW+jNVajdQpfuwD3pK4JOgFwBVnOBsMa4iQkGrC20WKep+eWVX
yQpUKh/pz91hr9cryUFTS8Ym2Xt++JqPV25Txj0a3M+i4L7rHypd5cA+6Nlv
PYK5/XSkn02SkBts2VaRdm6YOLdcsmpsUw1VSnbGTlzcK6GWfh+hSs2IgUcF
rBOrEQSV7sSNLiu3mpQhC/RaoC9fN2KiSudsOnYw1qkwKOuo+GauQsEEnDNb
6Tsk+ObIG8U8c4GZg7z2TptihO3arUjlVlcHkzYLQnp+91i9XhM1KJwAh2QA
Kex12WrZU7Ju1OrUZWmTdG2NFzVVQe+84t4Q5oFQdxC6wU4dEwMXB67aqOme
ASnxg1aNvpab4UvzGH/wFEiVXbRncytQ7EmGvftUGCkOpSmmgThnj3OvZoPS
HGJQhssWaR/SNqp6lEuZkxH8BlYeGAcWS/cW31vL61t5v6Chu5Q58oarux+D
vBjukqJS77+McqHEl5uuSGgHHxpM9KObyWJ6loUJWi5wv8uy05Y3UbZWd5NU
vG4Vn5A2RIV7jKdHBZTgdE0t7OwsKU0urqc6wVJVHk/i2m3bgS3NnWoW/9y0
HRfT4l3CQu1c1sOX98GGbJbjth/i3idR/jeXqAugy4yNHS6kndYIThOe7zoV
zB9BlMpgeyM6F0Kuya6SmvIs3PF0t8MS21ItuN+QYPaJUXxh7XZomLiFASom
UeVJq/qEw1CGnxXGU3wixseoVETSt2EXo5FJSjG+5iB8jS+Tpi/iOkhSWsbX
seM6dYfDGckZDXzvrvnTZn5GqW0Yq1+g77CXV4fvo8oImjnIBy3gv816oY2x
gpw0YD6c3WghUy5zEG2Ro4IGfsOk6In2BPVFXYi/b6IKc4wQ4tadE8HBOs2Q
jJP6yNMbwcO0sSiq4B407jP5886NVFSP8hopIBvRP/bsm3NJV+K/P/vHuZIr
3LLhlpPiLjMoOBB3yMAT9DXL9WK9rLfIOXxC0mD7R6sccJkvsQIPO1mx1B/V
Iw79aFHfE4WJuvwaOwIJYMti5DgHqRrC2K7W0k7TxlJRNzgXIBdx2ixrphJJ
m8uaOXYjId6MEgTZaIiq+VElbIoUUB1BFarWo4jqEw7Bc4F4tSwDFz62Zipy
8kKMEcbOqfSXKxBSQxi1LKlcw++dz881TGbSJwmYyJLZCBNAitQ0uF4PWiva
71X5e3zuAUKAY6FtOlRU2tG38eSqhtTBy3daI+grMMTFdWGIUp9mEA9MTJ4q
2XElvzkMUy6C1O8QeqiY4TFMKaJzWPqtPaKUDwO18ktxZKtzAK3gXmUmRtVa
nC20OJh3qf1theflXLE2Wsa5CnTgCxq/X0OEeZ9YWvLOgWIiEi0J9FiPRGIq
kBRpbSHoTQTrwrY1RuMCQUsamCpAJ74vYVjcnEI8QWqMh2tT6ajWJTyOifQE
xCjr2b9gTIqKUE8z60H2ctNN66vpS/Jui+alzQXvVOOwnMQceTlscK+uBEb/
fXeQWKXzCez8vMI0qLcPa5w/YpEgnBY73TVzYaDHiHYXwRU9tgifENPoOjQL
XmuEWWywRaUu6G4WddGaaPzEhxJl4VIlsClIkfLQinhnZt4S8PyrbwgktdOt
Fi7rVpYawMXuvZ4fc2qnhsKgHBg1BG7q2wCr5O+wSIfEGFFcxx3N0RSGx28W
hM1QUpWF/wdbnY13NisrF7NTdA9Y96+gw6e/0VrUTwbRFBcX5/fFKwmXbWlm
0WVc5QsqmzdUBX+4XBAyHqpMyTRtJl6Y/Ys7chSWEkEaCj7IXhPI4zhKuxET
GHOOKk7Oe1fYYYPBAWZKI/WJrOozd2jLK19DO1BTUL8zIauOOmb4YXYogcK3
A+kjfGjrGmQ6rMvlgleKd8sTJz7IY7XxHodiWkBJlDwHo2OxBKzFKQogLfBa
kxmtmxx5FaXxgdVcFGcXtbUeyA0XMgZVdvqMcjKTGQtR6xFgyh7s95TBUuzc
UfVOYhnsiWhl0OJ3zA0spM2zyHri4Vo+M2lMOW2Bguc3TKQo18p2JQ6WgDCQ
slpnwQmqNRLSlg2Ozd4RMeRfIFghrFMYfY7RjR4vhXO4Kq83jTUAlBB2TvoJ
iB5O2VsC22J0Fh2JyzcddoP9l9x6MJ5z0s+kX2AtyknYnHqFntpyqZXj8Hdl
65L+hP3VTLSmic8g8XVEqDYtNyqnMO8QBfRb0bSWztMvSpkJ+NUZ+BUIjQrg
SHn73g56T0+eJb1KJbPIJ5L0bOBYI0P8F1x78iH2y7AhNvnCkYlFN3LC+tKI
h5icv1RUNujwIWtBLWKgPIWWhDkfOFEvxvp2hdUR1mRWLaOIGx0dCScIc6Zs
6bV9YpWGpIsy1o3iOasGbJbbSorBRq7g2Mg1EoMDlUtn95IgD9kKCE3tCMER
CWAxTtP1KZQDF026DA/dNFFSEVnEBQNUPiDuQgt++ExOs17xcqGKxt6BHhKb
ps3Ms7ykDOY6sAOGp8lmI/PlAB1N91adYWkrTuXfqdJK7ULcYKXWgEcke4h0
rfwi4ZqeX07UChWDj7lkVs/nm6YlBJ4vr5nyUdJvFsDEpMZpvWlAvz/yAoV0
hpNqgQG1kyDiGPJ9aS+D0u0ddVTQIvhWEiofBYHjDLBedOsoGINot4SMKMnM
N7pifm7E0mMqGsJyHosugTbLTac1VbVcUNLlWCZQueiGwXccTGHOhRThxDGg
TKtH7mt0vLcdm3fqw7tV7SJpC+LYAfxOQGrGoDHxesZgKSr6aMUGBI4uaYFX
uNGq7CO0x1EgLOjkiHCf6DNmm6yQ1NxULO398ZK7huAuOZwI0Q4R1QDMPyp9
YpZPFJhx1mOWof2TO9MBBvoUmQKrbY1jHXhErHTqVQsEDEvoSKcCC3koqc5S
TiUHXnpJS2yNIRLhPozkSeieOFvRYHrD00qps6vXNTDY7SSyNLS/hlbJbFCx
L4ZFcBDdL5vBiv8mxunFuZvn7TxfUFUYfbkXJhaXlqzMsXP7qnVWJSzG7Xnz
iu624Fn4uyisp/yJEMIFMxuqgb7p4GYUvp0yWJy1Nqzn+hA9sSLqk8CQrRy1
l/o5c/y2XqIUIadboErRe6hvByFd64X2jK7X+W+bQpo1a1EbSkJG9sWCkLmn
TGkWBh9GyJ0ru0q5X+LH2NuxIaa3pJrVjRbfDmv90/0lVYBWhAo910kUahmc
luHJ4WIGDhOaKpvFnOebqxJORbaFOIfITZD6uGHuMzaVFgxMEvmB0lSt28Lb
yjMVUWSyOcWIEvs+r9cvIttj1NhgpHq9ps458JgO86REsestCff+PXzLX378
CFsy2CMuBAb5luBKfpEccYEcYTtQQs5m1YzwjrZn1DitJwISIa/e4q5Y2hY6
I+yumlIwi3ZLMpwkm5l6y8Bh2xCUSa1aHHlwxBc34HfmIklaZITm4qSMTKvk
MH1XksFrNaD0RZJqY9MVmp6EtbFdyCDvvkMTvcxpYNif2MSDonBsEpyDBKUa
IEJYbJ+YlPxWo0ZLcB7R8R0tl4/LO4sRioxeJiyCQjzC1vspx9G5GXii5mnr
RFoCenJMGfeNevhEFjbNybDsIcUG2Zk+Fwmio9YoS/srk4ZPEs8ZcciOkb+E
LYC0zVLPavCmOqUh5tlqs+zKacONAezWTpKVXvH1FN0JL3B+nXMLHJW9rk+e
rVWnKAfSFEl8KAsKrsoT37dgIvt/HHVG4o4sg8RDNEHuNiAXec8R1e55RJde
5BE9qxZR2fgUPiOb9lDbCXhuc5RNp3+WGeHfv3F9dOwOcK0Hu4JVHf3zjR/o
mAYdzcq8G+yr74um+SiY5qM7p6n9BcIlyl41jFGnEGxnhSK6IS5MfnUE4aNJ
SIq+v2GgFvyoxOOvfpOz+SyinDI2C4+4E3aHUwz8UCLB2juOXwuOXsLlgf+Y
M5dEQ49VE6MJ6jnJTWMXeoveB1DxSio7pkTxR9gHS/Ec8xVa2QLkzqIWBmBI
1CHbwJtkLgu5wmO0MXNnnv9Q5Ag14rLgrB94l7RE5LYvrVaMZScByzw3yh64
Y2waWUWDpBWTPWR/+RKrm3Y3KxcEVtsSeUteFRgs87/VmKeUzxLL7hPqmUEh
I8c/XuCAGpQvJhiyVoCwUdOdyPgA6uaiOVTNcBM4V12w2wwnn4eSjTMNzXN1
oum6Y7pQYIKrFjZnj1vquKB4JCIQDALx5OT8+Bd/iTQubHDmO/dP6oSDkfX8
6H+/OT46/uXEitZdhL2L7kxv3N/DPLDQQ+XCPmq4DlqQFWolvkEhXunsvCpy
LK8jWGoDT7Haellc55oMxPYZr0pk8Lty3mldITK7FK0jftOmKKw59QKMg66W
6oVwm1nppg5wDSKNWoqFhDtqbY6iUZGunA6KOvsGBVmr/clluWgUqNoRLX9Z
UrE0jGcta0ozUtCLSFKtAcbxWno6biB0vYGLCu9EYSzoGymvS/BVegGBEkyN
9Tnjcf13X9xLasnJnfaI50Jxmwx8wVWpt5iPgPD8xKUJjbUsFtR+JWMmOSdm
rtEfb+Ohm41jkpjRd3VVzkucxAo+wgJy3JYR+Qq8eUMgUKMp64gsJ45eRaID
bHOQN1rZsA6bJ1foZtcHyGVSt72DwYi8dNlDSgi9sb3IAhufJfrRGDDKsSmx
rvjonDZlMvRgj0BY37GDDav9aQKXheSv8nK5QSASFwbysoH9pliIryzE7gnj
h3k10D8NyOM1JWAynKnyFDIJpY5Ys4PtswN7CbmVq4rbUVdLIA5NlY/k4tOO
JXMuhz7vPMNOAq7SLTCqhoRtbubFYEEnlnDsbKRa/IRUDzP1vQdXyh2xtEc3
nuKGyNN0WXL4VbJT76qykXiRMl9HI3I1BQzaDfkfOOwY6AFfcREEuVeR7zoI
QMZWBYanmJuLG158Nq1HuFC0M6B3T+kigz3/YDaBtD4SmwEOyw52sK5ysGoz
5Y/cXMDlaZX5RIb55j8ayJKfhsXS6J7zrWdLmpyHWiWYOyv6wq5ZdPZBQN7X
SUMmcqtNcH31Sk0++HSmglT1NmF/G7JTJneqn+FLMrBWiZ1IYFatGlcpLI1m
RltopBd0tUb71TrCo3uawHaimMf0YUkIjpAUtXeOI3DYQlG6p2BpY1cQsZzJ
GwWz7+dZhMkSxsfsegXyhf1JbbBHHo3XFiuQZ4RqPDbeWOhBeoyUbCTvWABg
65WwIyU8aZLGFQLCbIxeX4a7vYFG+QOuaoZ24Obj7tL9dF44M+m2yqP5VDMJ
hW3V6PE6YaJPCWKzCwRHIRLH3wZ/cjzRZZEPFfcJIJtUO7LTzDoPpA60Ct/j
omzF3DanZVO2b6UnlDEnEzR+pSi2WutLGAinUnzEcK6N8wQomHj2O2JmyFbS
0Aj/yYwv1mEEUMjdeVunjiqCB58HJZV6lguPZrqOsg9vrjhh63RbCEDVvx4k
BkjFwdknQ1pWG7toPlsbC5EdjwtGXJtcI6n+HHcEFxUY3X8w4lelgXCzptU+
dpHrtGa/EL50wN4nI3scQOAS+IBXLIX2Y+GE+q6Ip0jbnIfSLcRQwfSu2bXO
7lRStAIHd8wMBcTtrDm60T5qiz1iFESH4LOplI4XllF4WwcEO7dE4Wey9rZo
4uYQd+wlqu5XG5JLqeAVykUmo+aitWEcjKGxa8FpsqtRpt7UBFxgbT4T3VuP
xRqSXnIkuHfgqnKmD+CSFezSW/HE1eZvs18F+GuyaFK1IfHy+dhtV7s7XSTa
Nly0ZwQjifBVNhPuoOuB3sZ93WUXqMyoDw9gjhO1ORtWmw1l0tebjcfS5XQK
A/wMdT7SJ/32T613YHpJDffHGsalFkxf8Wy45jeV2AjL4qMy36GNp+O2IU5s
dK3SmjjaNq/6O8ZaDur9rBBFznLPMYKCNHCKWMIfS6STR2tO2R5hqNiKjiQb
YQ6VAaXfhQPcZQSNGAGtn/UZKch6nwPcpTWVCmXNJXUu03osmvkAJiVczB/R
reCZB9e3UWPAcjVYAduq6snqIFXmTi8oCTCdWWlNa7wqaosyH08McCXti+ML
FOqaYgVhOkKv9njGjG1mi0vMtFS6rzctQikpZyVJl2s/gVqQ8seYnmRVqM1l
yZN1xqdDHGfg+5OTOAw7UfNrrxoJxw7NTAKd3HNGy8XhU5QZaJ0A6eCja0uC
zmvocOTTgMlaY62W9RAseiNBMsrVyC43VL6bCqflXMX6F//DpI+CKDmrAo6F
TMEFiQoZg9OetC0Bu67dDdgveTO/4aaBAVlobAfX+K5ebjiHMnZsW3RrzO69
psiBMTzP82Wm4RlFP+hBQEmWegWrNfoaVI7IPb4kr7EiZCeYKLfBm1hxwsDE
XcsXSPkEp82v2XWFr44RMiPmSRiQcxxsQu076tNIowMToDwtGqbkSgOgF76G
BVVvp8fquYQDP0O/+hyJykua0N88DPmibMF5uc6rLkbicHRkDv/XaMwfDXcV
za29TZ3pYYN2mP3+93vrSfbgPv4/rmR/jz6ghu3s1yUqCRXOFX7LZRiDaaFP
tkWh5clqcGwnWgAhQ20B2jJTyiL6YclUwU305ei5AbrQLykQNLCVBa+8tZJC
xTSFwgsdygfp6UbKFJPt63nSEuGjfqzGgpgdIY6fdr5xrzQ9DvR1Cb2loFwq
QTOQ8xnHDIKtogqUo1c1D0ucKEx+EgJm2yLU5IAHrX35vWSXMYGzKPBepIej
YbXGespZcC+yDahNLSoawG+XE/Ua3EoDeyM3r72TskJFQmFiKWA7JAC6j0U/
FV2jWPADJl7WVkw2I0sA9l9fSziOEHslv1MVB+mk06MLzf/vSxTsyWYRfz/V
GO84EQSCQj4Ml8qjD8X/EXRGhTbmucZJI0sHC5hprmfu6N+kigBj0+S+Et0X
BtGLYQke8rPYVsBG5wwbFPXCwJ5D7nYL9KPV4ZEVL07+9ubn05evX72RciZ0
+itMOnd3hq+YBaaoybGSyC6m+HmdL8F+FTyvN1jEhUmV4TZdi61jKMcszBrB
lcauIzxQ9tbUcmE0/6ON4z6SbKY7Abqm4/3LrDGTvxcgJ56EUennmN/3POAP
g/UdKJsxEBZzC74VYClV25jDYD/hCvXvKw/PoAMKIMCecYXSBnlTxW+7pq6N
WOMZ4eBWP9QVEbyJx0K+mphE8Np5J7jksCjHzvv3HQWyfW1H7K4uGsBdqQ44
UvLeNfVV8r6QK4ohUZ8m39RJtZwUmcWP8KURT5uLSwVbhScObeA1QFVBDBuW
GQwZJwlqqptLAM5UiSzZCI4c4/1slUdNEmcJqSBpgHzGzbxN16VfhuKG+u19
Lz1nAq8qtgimGAupPFhmP+ygOBnae+/2hkUcPAjJp5X6avQ6t/9wj5sXBkrl
LHvsLQieZp9Ssc1cr4pI5NCkPl5U9iGaDhuIhkOjuGEMUsa2Ri12KYMnmTGJ
lpCU+W/DgRA9Sjy/XOGPcrpFdcNvp5pejoRHzw0kyXBcqznMdlQuFC27pOq0
ydEOmRviaS8YDWd5DwW36vW3Kuhbpy6KKvJKxT53gi0SyC5WEdP7RBoQpRqw
wgZaN9zzsJHRYK87Cxa5XP0EanLdUEcuP6BSPKcpnoEkpI/j7MTs/ZetfPMx
TqzkdPL1hrWYIJ3PWLVlWSYJqpxTprkKg4UCaMZ2lkApaexGvYro628a4LV1
o4QOpg0lnnMdjkmYJzmwZx52/BtYtaJZ0eb19RrK6hC9rKZH3xbFmvCt2rgO
S0XXNYEymQbBhHaqnw4n00p+M9WZissHIWbzXdnWzTZxJ6EyYU2/yXY13+lY
C8Cg3/zANjiZBBaZyg3/FPI2rU89dFhhe1bSgUp/MTXQw6rggBuF+lfy29mp
iXfmt005f4vB/mrr5MUCTglyqwJAJwqRoALSESgHC6kdTQyLkxv7lbAEUUJl
s/T8LHmJ/KZap8t8nWM4NhQNPT+XYKoEb87gIuGsNwWnKWikSZIMvP9oFOyo
4+iTUay+18A10NPCKrtUN5/VgUjyUgPEZQmHtp0vi48fUeglfmVxmoZiWXIC
2TaZqRIZHStqeeO+aj6ggnlelJChjDDYbNojrt9H7+5E8wjqVjLN66BaTi6t
CEhO0qNfnRRKwzutmY+9GRJ5SGe5joQew5ZstWQlq97c93jKZnBZPFK5BPaE
QUecXGBWED22tcYSyT045OgP7rjgbzB8CrxxubpTZZcc+bjbsWjplDKCkwqW
FXqEOXt5K9AsLDbQsT2DYVNcS7UI84DHcDLRV2Ymu1AkeptGkhbEJuMpyYvb
uEOX1arPjlKngeW/yD0fnLls42XgvuXiYTiNIw0OprUfrFCi6cwNOzxoD38M
HbpMJqjRIFWyGSoYKJ+gLmqH2fFdzW4cJOi21Svu8w1AflOny/mA+F7zFx9H
yiKwiz5tvSJADPLfBdNiQTYAYQ8xBHwXVd3y9TkZ5saXDv0wlqgNB3FN7Y9b
zekJyxSQRvqugA3aYM968lCimKZeCFKMBAgDXZdFY5WgEj6PoRIKjDCR4/AC
8lmvNQ7I7RJkb0MNzx7OzIKqSKFn66mOBIig9OaWJskj2RikYjPGLfwVYXG0
Tk0Prk8OEmM01uRUPG4DpU4xiq6F0UlO2PvZ5QjGAE259gipwQtpV1VeXQdp
hlTGiEGVXDbgQu2PKcvqabm4EDUa/UQSvEZehbU7lmF5CoE5O2H6Y2qh8FDW
5RqYGxY3G3orWd9kYeOzgiVQidI/xTsqr6r5OZIehHKYQCdBJ2gQ4lYTrbsZ
gNSLuYDpYN6alEbuIe0jTyKgo/iB/ObPBmWAVsqREqeSwOhRYOowdv1zJluc
OcnToxdHfTYy1DBYSpdYnC1sIO1bEKCHTMt2XBGShNoQ0xiHXAwIC71j/Z+4
Hcx4DxrdwV6fDCwgJeNv8ZxHIdoPZ/d3J1ZcJm2CwzU1sLgg9UxJap9jhVfO
HvN9cWdc2pCWckBLSRtlji3n3nfxguCtAW195mK+Txdj7TgzXlCQq4Z+r0WO
UJ20mVpjHpdcV07rnPi0MByPmZKt/b6t3XOhsN00bEb0WyzaOOUO0xeHWSij
7Yt9+CJRoLhoVFJK8xhJa+g9WhzSv0fd+tE7okiAfXMA34RZ5vbFPfiiHyiw
r+/Lc1bEkUt33dmLO570g13zKvk7wmguzErIUDhY++3syDJ+wn7dk5FO28QT
s7hJNwvjsEm2DJa24n7//n+cPjn+fv/g4cePh9FGpXVFot0YawpoP3oIP3r9
4vHJ6enrF2+OX75+cW5ffQ9fnZ3DTlsGRjj6EXx7fnT688n5G50BbPvRr+Fv
jv0J+/b1+u0+EgU1dj89P3/z2n9+oJ9bw3cu4zRXLD+pcVI2hSwvRWUuy7di
JQLDz443yyVcxP9VVIzNxJ2lWsfon7mkhtHvyuKWSiJxpN8SfvGbVippUBWx
FvHsV5sl2A3X0rmeZHGYbYuthPOmrLXSV8CYZ+7/AMycpF1IKAEA

-->

</rfc>
