<?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-altanai-moq-relay-diagnostics-00" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="MOQT Relay Diagnostics">Client-Visible Relay Diagnostics for Media over QUIC Transport (MOQT)</title>
    <seriesInfo name="Internet-Draft" value="draft-altanai-moq-relay-diagnostics-00"/>
    <author fullname="Altanai Bisht">
      <organization>Cisco</organization>
      <address>
        <email>altanai@outlook.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="18"/>
    <area>Web and Internet Transport</area>
    <keyword>MOQ</keyword>
    <keyword>MOQT</keyword>
    <keyword>relay</keyword>
    <keyword>diagnostics</keyword>
    <keyword>observability</keyword>
    <abstract>
      <?line 59?>

<t>Media over QUIC Transport (MOQT) deployments typically place one or more relays between publishers and subscribers. When delivery stalls, degrades, or fails, a client observes only its own leg of the path, and often cannot determine whether the cause lies with the original publisher, an intermediate relay, path conditions, authorization policy, or its own behavior.</t>
      <t>This document collects use cases and requirements for exposing a limited, relay-controlled set of diagnostic information to authorized MOQT clients. It examines three candidate mechanisms: an explicit request and response exchange on the control path, diagnostic information carried in existing responses and error codes, and advertisement of diagnostic capability during session establishment. Because such information can reveal deployment topology, operational state, or the activity of other users, authorization, data minimization, and relay discretion over what is disclosed are treated as first-order requirements rather than later refinements.</t>
      <t>Related operator examples describe capacity and incident observations within a separately authorized administrative scope. They motivate correlation with existing metrics and logging systems without defining a relay management API.</t>
      <t>The goal is diagnostics that are actionable at runtime and interoperable across implementations, not a general-purpose telemetry channel within MOQT. Information intended primarily for offline analysis remains the province of logging and observability systems such as qlog. This document defines the problem space and the design constraints; a concrete wire format is left to a follow-on document once the working group has settled on an approach.</t>
    </abstract>
  </front>
  <middle>
    <?line 69?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Media over QUIC Transport (MOQT) <xref target="MoQTransport"/> distributes media through a
publish/subscribe model in which relays sit between publishers and subscribers.
A subscriber therefore terminates only the last hop of a multi-hop path, and the
signals available to it locally are rarely sufficient to explain why delivery is
degraded or has failed.</t>
      <t>The term "diagnostics" comes from <xref target="Issue1692"/>, which asks how a client can
get diagnostic data from a relay. Discussion following IETF 126 helped
shape the use cases and requirements for any future wire format.</t>
      <section anchor="note-to-readers">
        <name>Note to Readers</name>
        <t>This revision is a problem statement and requirements document. It defines no
protocol elements. Comments are welcome on the MOQ working group mailing list.</t>
      </section>
      <section anchor="conventions">
        <name>Conventions</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

</section>
      <section anchor="terminology">
        <name>Terminology</name>
        <t>A <strong>client-visible relay diagnostic</strong> is a limited report of what one relay
observed or did while handling a particular request. For example, when a
subscription stalls, the relay may report that it handed Objects to its
outgoing transport for that subscription. Whether those Objects reached the
subscriber or why playback stalled may remain unknown. This document uses
<strong>operator telemetry</strong> for the metrics, logs, and traces used to understand
relay or service behavior within an authorized administrative scope.</t>
        <t>The transport roles follow <xref target="MoQTransport"/>.</t>
        <ul spacing="normal">
          <li>
            <t>A <strong>publisher</strong> publishes a Track and sends its Objects to a subscriber.</t>
          </li>
          <li>
            <t>A <strong>subscriber</strong> requests or accepts delivery of Objects from a Track.</t>
          </li>
          <li>
            <t>A <strong>relay</strong> terminates MOQT sessions and forwards Objects between peers. It
can act as a subscriber upstream and as a publisher downstream, and may
cache Objects.</t>
          </li>
        </ul>
        <t>This document uses the following operational roles.</t>
        <ul spacing="normal">
          <li>
            <t>A <strong>relay operator</strong> runs a relay or a fleet of relays.</t>
          </li>
          <li>
            <t>A <strong>service operator</strong> operates a delivery service and uses authorized
telemetry to assess delivery or investigate user reports.</t>
          </li>
          <li>
            <t>A <strong>tenant operator</strong> administers delivery for a tenant and can see the
observations authorized for that tenant.</t>
          </li>
          <li>
            <t>A <strong>telemetry collector</strong> is a system that receives or retrieves metrics,
logs, or traces for an operator. When it subscribes to a MOQT telemetry
Track, it acts as a subscriber for that Track.</t>
          </li>
        </ul>
        <t>An organization can fill several of these roles. For example, a service
operator can run relays and publish content. Each role has its own scope of
access under the deployment's policy.</t>
      </section>
    </section>
    <section anchor="problem-statement">
      <name>Problem Statement</name>
      <t>MOQT clients observe only their own sessions and cannot reliably determine why delivery stalls or fails across a relay chain. An authorized client needs a small, request-scoped account of what its relay observed and did, sufficient to guide waiting, retrying, or reporting a problem. That account can be incomplete and cannot establish end-to-end delivery or identify causes outside the relay's knowledge. Disclosure must protect other clients, topology, cache state, and operational policy, while keeping diagnostic processing and query rates bounded.</t>
    </section>
    <section anchor="use-cases">
      <name>Use Cases</name>
      <t>The following use cases describe the question a client or operator wants to
answer. They do not require a relay to disclose every fact that could help
answer it. In each case, a relay may provide a coarse, request-scoped result,
withhold details, or report that it cannot determine the cause.</t>
      <section anchor="distinguishing-a-local-request-outcome">
        <name>Distinguishing a Local Request Outcome</name>
        <t>A subscriber issues a request for a track or a range of content and receives
an error or observes no useful progress. The application needs to distinguish
between a request that was rejected or could not be served at this relay and a
request that was accepted but has not yet produced content. A useful answer
might identify the outcome category and whether retrying the same request is
likely to help. It need not expose the relay's policy rules, cache keys, or
internal request identifiers.</t>
      </section>
      <section anchor="diagnosing-a-delivery-stall">
        <name>Diagnosing a Delivery Stall</name>
        <t>A subscriber has an active subscription, but expected objects are not arriving
within the application's tolerance. The subscriber or its support tooling
wants to know whether this relay has observed relevant upstream content, has
forwarded content downstream, or cannot determine where progress stopped. A
bounded summary for that subscriber's request can guide whether to wait, retry,
change tracks, or collect local evidence. It should not reveal other
subscribers, shared cache contents, or the identities of upstream peers.</t>
      </section>
      <section anchor="explaining-a-relay-decision">
        <name>Explaining a Relay Decision</name>
        <t>A relay may decline, defer, or limit work for a request because of its local
authorization or resource policy. An authorized client wants an explanation
that is actionable, such as whether the failure is likely to persist without
a change in credentials or request parameters. A relay can communicate a
coarse outcome without disclosing confidential policy thresholds, tenant
configuration, load measurements, or details that would help an attacker tune
requests around policy.</t>
      </section>
      <section anchor="supporting-an-operator-assisted-incident">
        <name>Supporting an Operator-Assisted Incident</name>
        <t>A subscriber reports a delivery problem to the service operator. A diagnostic
summary for the subscriber's own request or a short-lived correlation value
can help the service operator match the report to the relay's handling of that
request. The value should be short-lived and refer only to the event, while
the subscriber's access remains limited to its own request. More detailed
logs may be available to the service operator through a separately
authorized observability system.</t>
      </section>
      <section anchor="learning-whether-diagnostics-are-available">
        <name>Learning Whether Diagnostics Are Available</name>
        <t>A client may need to know whether a relay supports a diagnostic feature before
requesting it. A capability indication can prevent unsupported requests, but
it should reveal only the feature category needed for interoperability. It
should not fingerprint a relay implementation or disclose deployment
topology.</t>
      </section>
    </section>
    <section anchor="illustrative-diagnostic-observations">
      <name>Illustrative Diagnostic Observations</name>
      <t>The following proposed metrics describe one client's existing, authorized
request. Their names and semantics are starting points for discussion, not
standardized MOQT fields, mandatory measurements, or a selected wire format.
Counter and Gauge have the numeric meanings described in <xref target="MoQMetrics"/>. A relay
would disclose a metric only when it can attribute the observation to that
request using bounded local state and its disclosure policy permits access.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Suggested metric</th>
            <th align="left">Proposed meaning</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">
              <tt>request_objects_observed_total</tt></td>
            <td align="left">Cumulative number of distinct, complete data Objects accepted into this request's forwarding path after its filters and policy checks.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>request_objects_forwarded_total</tt></td>
            <td align="left">Cumulative number of distinct, complete data Objects handed to the outgoing transport for this request. This local handoff does not establish client receipt, decoding, or playback.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>request_queued_objects</tt></td>
            <td align="left">Complete, eligible Objects still held by this relay awaiting completion of transport handoff for this request, including any retained unsent portion of an Object. Excludes transport-internal buffering and shared cache inventory.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>request_last_forward_age_seconds</tt></td>
            <td align="left">Monotonic elapsed time since the last complete-Object handoff for this request, rounded upward to a disclosed precision when policy requires. Omitted if no such handoff is known.</td>
          </tr>
        </tbody>
      </table>
      <section anchor="counting-and-measurement-scope">
        <name>Counting and Measurement Scope</name>
        <t>The two Counters start at zero when observation begins for the request and
increase within one measurement epoch. A restart, reset, or change of
measurement scope starts a new epoch, distinguished by a short-lived,
session-local value. A 10-second count is the difference between two samples
from the same epoch; a <tt>_total</tt> value is not a rolling 10-second count.
Samples from different epochs cannot be subtracted.</t>
        <t>The Counters use independent acceptance and handoff boundaries. An Object
accepted before an epoch or comparison window can complete handoff inside it,
incrementing only the forwarding Counter for that interval. Their difference
is therefore not a balance and can be negative over a comparison window.</t>
        <t>An Object is identified within a request by its Full Track Name, Group ID,
and Object ID, and contributes at most once to each Counter per epoch.
Incomplete Objects, status markers, duplicates, and transport retransmissions
do not increment these Counters. Cached Objects can count when accepted into
or handed off for this request; the report does not identify their source or
expose shared cache activity. A relay omits a metric if bounded attribution
or duplicate suppression is unavailable, including under subscription
aggregation.</t>
        <t>The queue Gauge can decrease when Objects expire or are discarded, as well
as when they are handed off. The Counter difference therefore does not
necessarily equal queue depth and does not establish packet loss or a cause.
The age Gauge uses a local monotonic clock and discloses no exact event
timestamp. For example, with upward rounding in 5-second steps, a scalar
value of 5 means an age greater than zero and at most 5 seconds; an interval
such as <tt>[1, 5]</tt> is not a numeric Gauge value.</t>
      </section>
      <section anchor="example-and-disclosure-limits">
        <name>Example and Disclosure Limits</name>
        <t>This conceptual report samples an epoch 10 seconds after observation began.
Its Counter values are totals since that epoch began; later window counts
would require comparable earlier samples. The age value is rounded upward
in 5-second steps. All field names, epoch and precision metadata, and JSON
encoding below are illustrative and carry no protocol allocation or
interoperability requirement.</t>
        <t><tt>json
{
  "scope": "existing_request",
  "measurement_epoch": "session-local-example",
  "measurement_elapsed_seconds": 10,
  "metrics": {
    "request_objects_observed_total": 120,
    "request_objects_forwarded_total": 117,
    "request_queued_objects": 2,
    "request_last_forward_age_seconds": 5
  },
  "age_rounding_seconds": 5,
  "progress": "forwarding_observed",
  "cause": "unknown",
  "coverage": "partial"
}
</tt></t>
        <t>Unsupported, unavailable, withheld, or unattributable measurements are omitted,
not replaced with zero. Zero represents a measured zero, such as no handoff
counted in this epoch. For the age Gauge, no known handoff means omission,
not zero. Any indication of why a value is absent is also subject to
disclosure policy. Approximate request-specific bytes forwarded or
a coarse progress category, such as waiting or unknown, can supplement the
four metrics without exposing peer identities or asserting an upstream cause.</t>
        <t>Reports exclude cache-hit status, topology, relay-wide load, and other users'
activity. Query rates, processing, response size, and retention need limits;
producing a measurement must not initiate upstream retrieval or subscriptions.
The working group would need to agree these semantics, precision metadata,
authorization and request binding, and any mapping to <xref target="MoQMetrics"/> before
implementations could claim interoperability.</t>
      </section>
    </section>
    <section anchor="operator-diagnostics-at-operational-scale">
      <name>Operator Diagnostics at Operational Scale</name>
      <t>Relay operators use operational measurements to assess capacity and behavior
across the relays they run. Service operators use authorized observations to
assess service health and correlate user reports with local delivery events.
The metrics below illustrate those administrative views. A telemetry
collector can use <xref target="MoQMetrics"/> data, <xref target="MoQLog"/> records, <xref target="QLOG"/> traces, or
deployment observability data within its authorized collection scope.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Suggested operator observation</th>
            <th align="left">Operational use and measurement scope</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">
              <tt>relay_active_sessions</tt></td>
            <td align="left">Current established MOQT sessions at one relay; helps identify connection load and changes during draining.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_active_subscriptions</tt></td>
            <td align="left">Current established subscriptions at that relay; counts local subscription instances, not unique viewers or end-to-end subscriptions.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_requests_total</tt></td>
            <td align="left">Local request attempts reaching initial acceptance, rejection, timeout, or cancellation, counted once per attempt. Bounded labels distinguish request type, direction, and outcome; each retry is a separate attempt.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_queued_payload_bytes</tt></td>
            <td align="left">Unsent payload retained in relay-managed forwarding queues, counted per pending downstream delivery; measures delivery backlog rather than physical memory or transport-internal buffers.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_delivery_timeout_resets_total</tt></td>
            <td align="left">Locally initiated data-stream terminations for delivery timeout, counted once per stream; helps detect deadline pressure without treating every affected Object as a separate reset.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_cpu_utilization</tt></td>
            <td align="left">Process CPU consumption divided by available process CPU capacity over a disclosed sample interval; the interval and capacity basis accompany the observation.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_process_resident_memory_bytes</tt></td>
            <td align="left">Resident memory of the relay process, with collection method identified; useful for capacity assessment alongside queue and cache observations.</td>
          </tr>
          <tr>
            <td align="left">
              <tt>relay_cached_payload_bytes</tt></td>
            <td align="left">Total payload length of distinct cached Objects, counted once per Full Track Name, Group ID, and Object ID; excludes metadata and is not physical process memory.</td>
          </tr>
        </tbody>
      </table>
      <t>For example, a relay operator can investigate scheduling or downstream
capacity when queue bytes and delivery-timeout resets rise together. A rise
in failed upstream request attempts, observed where the relay acts as a
requester, can guide examination of that relay's upstream connections. High
CPU or resident memory with growing load can motivate capacity planning or
draining. These are correlations to investigate, not proof of a cause or of
the quality experienced by every viewer.</t>
      <section anchor="aggregation-and-access-boundaries">
        <name>Aggregation and Access Boundaries</name>
        <t>Every operator sample needs an administrative scope, collection interval or
capture time, freshness, and coverage. Counters have local measurement
epochs; rates or window deltas are calculated per relay before aggregation
so restarts are not mistaken for traffic changes. Gauges are combined only
across disjoint scopes with compatible meanings. Fleet reports disclose
missing or stale contributors instead of presenting partial coverage as a
complete service view. Fleet CPU fractions are weighted by the disclosed
capacity basis rather than summed. Capacity thresholds and alert policies remain
deployment decisions.</t>
        <t>Operator authorization is role- and scope-specific. A tenant operator sees
only that tenant's authorized observations; node-wide CPU, shared-cache
inventory, or another tenant's activity needs separate permission. Collector
access, retention, and incident correlation need auditing and access controls.
Labels use bounded categories such as request type and outcome, avoiding
tokens, user identifiers, full content names, or arbitrary peer addresses.
Detailed logs or traces are retrieved only for an authorized, bounded
incident context, with sensitive fields minimized. These operational views
are not returned through an ordinary client's private diagnostic view.</t>
      </section>
    </section>
    <section anchor="requirements">
      <name>Requirements</name>
      <t>These requirements describe design goals for a future mechanism. They do not
specify MOQT messages or require relays to expose operational information.
Requirements to identify an individual request or report from one relay apply
to the client-visible view. Operator aggregates instead identify their
administrative scope, contributing relays, coverage, and freshness as
described above; they retain the applicable access and resource limits.</t>
      <section anchor="diagnostic-scope">
        <name>Diagnostic Scope</name>
        <ul spacing="normal">
          <li>
            <t>A mechanism needs to identify the request or delivery context to which a
diagnostic applies, without requiring a stable identifier that can be used
to correlate a client's activity across sessions.</t>
          </li>
          <li>
            <t>A diagnostic needs to distinguish, where the relay has sufficient evidence,
between a relay-observed outcome and an unknown or unobserved cause.</t>
          </li>
          <li>
            <t>A mechanism needs to permit an implementation to return no diagnostic or a
less detailed result when the relay lacks reliable evidence.</t>
          </li>
          <li>
            <t>A diagnostic needs to avoid implying facts about upstream endpoints or
network segments that the reporting relay cannot observe.</t>
          </li>
        </ul>
      </section>
      <section anchor="privacy-and-authorization">
        <name>Privacy and Authorization</name>
        <ul spacing="normal">
          <li>
            <t>A relay needs to authenticate and authorize access to diagnostics according
to its deployment's policy. A client authorized to request content is not
automatically authorized to inspect general relay health or other clients'
activity.</t>
          </li>
          <li>
            <t>Diagnostic responses need to be scoped to the requesting client's own
session and request, except where a separately defined and authorized
operator interface is used.</t>
          </li>
          <li>
            <t>Operator collection needs explicit administrative and tenant scope,
role-based access, bounded retention, and auditability. Authorization for
content delivery or a client diagnostic view does not grant operator access.</t>
          </li>
          <li>
            <t>A mechanism needs to support data minimization: disclose the least
information useful for the stated diagnostic purpose, and allow the relay to
omit sensitive fields.</t>
          </li>
          <li>
            <t>Diagnostics need not disclose relay topology, upstream identities, cache
keys or contents, tenant names, policy rules, precise resource utilization,
or information about other clients.</t>
          </li>
          <li>
            <t>Any correlation value needs to be scoped, short-lived, and difficult to use
as a cross-session or cross-service tracking identifier.</t>
          </li>
          <li>
            <t>A client needs to be able to distinguish unsupported, unavailable, and
withheld information where doing so does not itself create an unacceptable
information leak. A mechanism can deliberately collapse these outcomes when
policy requires it.</t>
          </li>
        </ul>
      </section>
      <section anchor="safety-and-operational-behavior">
        <name>Safety and Operational Behavior</name>
        <ul spacing="normal">
          <li>
            <t>A mechanism needs bounded response size and bounded processing cost.</t>
          </li>
          <li>
            <t>A relay needs discretion to rate-limit, defer, or refuse diagnostic requests
without affecting ordinary content delivery.</t>
          </li>
          <li>
            <t>Diagnostic requests need to avoid causing new upstream subscriptions,
cache fills, or other expensive work solely to generate a diagnostic.</t>
          </li>
          <li>
            <t>A diagnostic needs to be clearly identified as a point-in-time report from
one relay. It may be incomplete, delayed, or based on an approximation.</t>
          </li>
          <li>
            <t>Diagnostics need not be enabled by default. Capability discovery and use
should be compatible with deployments that choose not to expose them.</t>
          </li>
          <li>
            <t>Clients need to treat diagnostic information as advisory and continue to
apply their own timeouts, retry limits, and security policy.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="candidate-mechanisms">
      <name>Candidate Mechanisms</name>
      <section anchor="explicit-request-and-response-on-the-control-path">
        <name>Explicit Request and Response on the Control Path</name>
        <t>An explicit request lets a client ask for a diagnostic when a particular
request is stalled or has failed. It can carry a request-scoped context and
allow the relay to return a result only when asked. This avoids sending
diagnostics for every request and gives the relay an opportunity to apply
authorization and rate limits.</t>
        <t>The mechanism also adds a new request/response exchange and associated state.
It needs rules for matching a diagnostic to a request, handling unavailable
or withheld information, and preventing repeated queries from becoming a
resource or probing attack. A diagnostic request must not trigger expensive
upstream work solely to answer the query.</t>
      </section>
      <section anchor="diagnostic-information-in-existing-responses-and-error-codes">
        <name>Diagnostic Information in Existing Responses and Error Codes</name>
        <t>Adding a small diagnostic category to an existing response or error can make
an outcome immediately actionable and avoid a separate round trip. It is a
natural fit when the relay is already returning a result for the request.</t>
        <t>This approach is less suitable for later investigation of an ongoing stall,
and risks turning response fields into a channel for detailed operational
data. Error details may also be propagated or cached by relays. Any details
would therefore need to remain compact, request-specific, privacy-preserving,
and safe to forward or retain for the lifetime defined by the base protocol.</t>
      </section>
      <section anchor="capability-advertisement-during-session-establishment">
        <name>Capability Advertisement During Session Establishment</name>
        <t>Capability advertisement can tell a client whether a relay understands a
diagnostic mechanism before the client uses it. It can support gradual
deployment and avoid sending requests that cannot be understood.</t>
        <t>An advertisement says that a capability is supported; it does not authorize a
particular client or guarantee that a relay will disclose a diagnostic for a
particular request. Detailed capability lists can fingerprint implementations
or deployments, so discovery should identify only the protocol feature needed
for interoperability.</t>
        <t>The mechanisms are not necessarily exclusive. A later design could use
capability discovery together with either an explicit query or compact
response details. Selection requires working-group agreement on the target
use cases and privacy model.</t>
      </section>
    </section>
    <section anchor="relationship-to-other-work">
      <name>Relationship to Other Work</name>
      <t>This work concerns request-scoped explanations that can help an endpoint make
a runtime decision or help a user report a problem. It is not a general
metrics format, a relay management API, or a logging protocol.</t>
      <t><xref target="MoQMetrics"/> provides a numeric data model, live subscriptions, and retrieval
of cached measurements. Its Counter and Gauge types are candidates for the
observations illustrated here. The proposed request semantics, attribution,
and disclosure rules would need an agreed mapping, including naming and
authorization, rather than a competing metrics transport.</t>
      <t><xref target="MoQLog"/> provides structured operational logging over MOQT, while <xref target="QLOG"/>
provides event representations useful for protocol analysis and incident
correlation. Existing metrics, logs, and traces can support either audience
when authorized. The operator examples here motivate reuse of those systems;
they do not define a replacement collector, dashboard, or management API.</t>
      <t>The following are out of scope: exposing a relay's complete internal state;
distributing network-wide or cross-tenant telemetry to ordinary clients;
proving end-to-end delivery; standardizing operator dashboards; and defining
a general-purpose query language for relay state.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Relay diagnostics create a deliberate information channel from a relay to a
client. The channel can reveal operational state, deployment relationships,
traffic patterns, and policy decisions. An attacker may use repeated or
carefully varied requests to infer whether content is cached, whether another
client is active, how a tenant is configured, or when a relay is under load.
Even coarse fields can become identifying when combined with timing and
client-side observations.</t>
      <t>A future protocol design should apply data minimization at the relay, not rely
only on clients to protect received data. Diagnostics should be tied to the
requesting client's authorization context and scoped to that client's own
request. General relay health, cross-client statistics, and operator
correlation should use separately authorized interfaces. Deployments may
choose not to provide client-visible diagnostics or may provide only a small
set of coarse outcomes.</t>
      <t>Operator observations need separately scoped authorization, tenant isolation,
access auditing, and retention controls. Aggregation does not by itself make
data anonymous, and small groups or repeated queries can still reveal an
individual client's activity. Correlation with detailed logs or traces must
remain within the operator's authorized incident scope.</t>
      <t>Implementations should avoid returning stable relay or client identifiers,
precise timestamps, exact cache keys, upstream addresses, internal error text,
or raw policy and resource measurements unless a separate, explicit trust
model justifies them. Any event correlation value should be short-lived and
non-reusable across sessions. A relay may deliberately make "unknown",
"withheld", and "not available" indistinguishable if differentiating them
would expose sensitive policy or state.</t>
      <t>Diagnostic queries can consume CPU, memory, or control-stream capacity, and
may be abused to probe policy or amplify traffic. Responses and processing
need limits; relays need rate limiting and discretion to refuse queries.
Generating a diagnostic should not trigger content retrieval, cache filling,
or upstream subscription work. Where diagnostic messages can be replayed,
cached, or propagated by other relays, their scope and lifetime need to be
defined so that one client's result is not disclosed to another.</t>
      <t>Clients should treat diagnostics as advisory, potentially incomplete
observations. They should not infer that a named upstream component is at
fault based solely on a relay response, and should not use the absence of a
diagnostic as proof that delivery is healthy. Operators should consider the
privacy of diagnostic data in logs, support tickets, and telemetry pipelines.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="MoQTransport" target="https://datatracker.ietf.org/doc/draft-ietf-moq-transport/">
          <front>
            <title>Media over QUIC Transport</title>
            <author>
              <organization>IETF MOQ WG</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="MoQMetrics" target="https://datatracker.ietf.org/doc/draft-jennings-moq-metrics/">
          <front>
            <title>Metrics over MOQT</title>
            <author initials="C." surname="Jennings" fullname="C. Jennings">
              <organization/>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="MoQLog" target="https://datatracker.ietf.org/doc/draft-jennings-moq-log/">
          <front>
            <title>Logging over Media over QUIC Transport</title>
            <author initials="C." surname="Jennings" fullname="C. Jennings">
              <organization/>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="QLOG" target="https://datatracker.ietf.org/doc/draft-ietf-quic-qlog-main-schema/">
          <front>
            <title>Main Logging Schema for qlog</title>
            <author>
              <organization>IETF QUIC WG</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="Issue1692" target="https://github.com/moq-wg/moq-transport/issues/1692">
          <front>
            <title>moq-transport issue #1692: client-visible relay diagnostics</title>
            <author>
              <organization/>
            </author>
            <date year="2026"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 519?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author thanks the participants in the Media over QUIC Transport working
group for discussion of relay diagnostics and issue #1692. Additional
acknowledgments will be added as the document develops.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA71d65Ibx3X+308xWf1QogKWWpXl2KRzWS0pmSlSlEgqrkSl
IgeYBjDiYAaentk1LOtd8ix5spzvXPoC7EZOJZWqRN7FDqa7T5/Ld75zurlc
Lt3UTp1/XF3cdK3vp+W/tqFddb567bv6WD1t620/hKldh2ozjNVL37R1Ndz6
sfr2u+c31dux7sNhGKfqb1+++vbt3124erUa/S29D7+fv+XCrevJb4fx+Lhq
+83gmmHd13uaQDPWm2lZd1Pd1+1yP/xxOeLLyyZ9efnppy7Mq30bQjv00/FA
X3v+7O2XrqF3Pq4++/SzXy+vrpZXv3HroQ++D3N4XG3qLnhHM7py9ehrmtkf
/Kqq+6Z63k9+7P2UVnHhPvjj3TA2j11VLStagv3vW/6BZ8Q/ZbPi34dV8ONt
vWq7djo6V8/Tbhj5LfT/VbWZu06WeXEtK6y+aMOOBsRfh3Fb9+2f64lWhZ1o
w3qQv/h93Xb0kYrln4d56obhw+V62F841w/jnr506zHQ6y9vPru6+q3++Jur
v//VY+cg4uyZl8O3ca2PeQDb/Qc3VuaR1qPzpa9A8hBN9Yev5KG0C/Lqetz6
iR7cTdMhPH70iP5eT2O9/uDHy9ZPm0t6zyPa/0ey9fiI932ysR9dyJxf+mkk
QZ/OmD+UOWOH7pupyvzmsvoX3/dtvw3/J1P9UV/G093LRGyyL4ZtOVH6YEsP
60T/J3L+/5h9N2x55t++ePXViYDrtq9s8m/WO9JF9gF/pK/8glbw0v4v1eKP
c7teYuAlGUS/DDwbnvfzEGZ/9evfflZOvtCjqsVD1Uf8WLUWR3erjo5tOrfn
v27W23bazSsY4iOMdbd9VKouDxkeYcgLtyQ/i/9U9SpgqZNzv+RJq8YfuuG4
p6mGilxdu6677lgdunrtq6Gn/x+r/TDq/EO18tOd9311mFcdeRY/BvZx5C7D
emxX9Ptl9YcdPdD4jrzBeKzCRG8MC/pgO9aNp5/olRvyN/RTrVJSv+bJzHoa
vaW5DHd91XlS50017Xx1qKfdgocaNhO9fl33/TDRS8m37lua593O03MjP7yu
5+ArenOo7kh+/NkwtqRhdZdmjtdRcMALIKRJ17jgsSpy7U0LT4lpsgKq56wO
Q9euj7wMm+jK7+rbdhgvnXu7a0NFajVDpPSWrvNregoTWtfBi7hGT5o2epE6
lN3/6TAEGEBN0963k28WMpslzWMa8RYSMsUQEkfSoSr6XZrWNMR50rMcFkW4
tCPPJxqhhpxok3ejx1xoeVC+au/XOwoLYU9BjARCM6HltRPP0YdJ50s6Q6GO
/oqHt1ANkbTMTrfngZmt63FsaU4t3t7Sn2md9kaRhx9HEsJ6YPXAB3VDujO1
gUV0suh1fdAAWDXziJfRaxCpK5puzZuLb11WX3hRhDCvdycT6mkCt560Iak/
CZB2dthiZw9+5CfpAXrl5HmzsV6yqfYWI9OUBtY3GmA8VZEFzLquSN60l/aR
yFGcANmK55mwYd7tavgO/rwbAkmKEEQ1EYqY8DNpSDuGaUl4gR4uVIdmKTpP
C+roafx5Q7vMfyVlBC7CO2RBrGf1/tCR1EnSbK8szTVWhPm1/bptkj3yzMWG
aO9qkvOhpvd4MtFM1eoGC4XDQfyvCFQc/GX1dueP5DnoIyjZehixdl4zm2RU
BA1rPHynUSAcw+T3MjBBEZosLUqsQyS4J5SyFd24/uY5W52vtgNtF4sxgckJ
ooU0sXG0n/DE9Mk491O797pmkhsLiP+4HocQqhZSwvtrdQFwNnW19T091y0P
80j2Snvk8dREXg5m0fvOZAXzI7PLdA7D9A2J6zC2+3psSYYw/GGz6eC+aEHd
MdDsR2CxPojTG4db2hIPbTPZsAvMUWCUFqs5aQviF+Sf+yGWoI9vpZXuq3CA
j8f78CkpRLvtYdDYSZpteAL3PPRQVXKvpHOVrAYy7vxmYo9Dn3XdcLekFcbB
BkwZ7ySI+wFz3o7DfKh2NDdyYRNcGT1OKlsfaC71encpUWvfNk3nnfsIkHkc
mpn37K+IYd/ngPMH2BHp1GqeaMHs2uHzhnlL0nHq/R/FgEU6SqEKvulu15IA
Nc4F8oB/Raxz19mvWDPZH6KlRKV6sogGaXQ1edPdcMBuknOYu6ld4tcU2ugp
h12gVKKqbylEskqSmGky3SCRGco80n/oxzBvNuSqxXex4655GccUfNvgNO42
cGHYAoRe36jNYJ7VRY5KaMv3NOvNOOyr7yPq+WGh4qnDh0CLuEuhm5ypI8yS
e2j2fvwGNdhLys3CehYvLRoDvWAQd/XZr6ud7w6+cWFXH0RzfiFc1j1ZzzzN
Y6GYtKaPPqq+HiaW2WtPqx6DRmRy9y2PTj/XyQTg3Flnz4YxbebgaebTD46+
Og0U1ivfqZutboa9fAd7c+c7SNACJBKX0gyQauE3Uimd8c3Q39L34WhkVyg7
xJeaQOj4uzdvLxbyv9XXr/jn18/IDF4/e4qf3/z++sWL+IPTJ978/tV3L56m
n9I3b169fPns66fyZfq0Kj5yFy+v/+1ClPHi1Tdvn7/6+vrFBYxjKtwJx6eB
DES85wEuApHKWVjhYP/FzTf/+R9Xv6p++ulvNGv8+Wf9BXkj/UKgTSMjW4n8
SmI7OnINvh7xFtJ6BKmWYCTiLJnmDpALpkbi++R7SOaHx9XvVuvD1a/+UT/A
gosPTWbFhyyz80/OvixCvOeje4aJ0iw+P5F0Od/rfyt+N7lnH/7unzhILK9+
80//6Fhn3rKDYbziyAl98skvpBuffCKar+iS/s4OlFwRow8gfWEdFImzuyCE
CLOn11F0azqJwAQB6H1zV48GES+rLxO0WPAukqdVv3jg6GdJAEzCQvjRJsFB
mlwcBqGBX61+ZMjMfi84AgDbAUOnPGvDaIy+lI/BeYfCIcRmew3BKErj1Lkm
Xz2M7CnJZx5XlBTKDOkxmRdicDX3H3pStdNYSr4puE8+iZgqggCS8UZxoqKa
BcK2QlokZJ4TgQZLm3t4p4n+4kQg9E1IvqXYaelERF79L+ItdedRRATK4cXZ
1Z7ER1hNBZWJcY0mbj9DR94iS5ZQR5AlcJaTbUqdhbxLfVX6hN6lahGwpHq9
9ge4U4tIpHH2Lo0QPJy9iGVB78gCKKcyCvElHpCU72q4R3tTjNSeE9DnEyXT
APmE+uAx8hlX8yEAWu8lz+BoYHKgPb7r5a+yZ3um4dZQIBvrLMWDOvCep7iW
5w+8EVHkutWqOpDVjDVVUQUobnZe8jxBIlHCqhvZd+VH3rKUbetjmD3PLCkO
rSThVexjgFCznYG7pRx8areA7Ehs1ELjJAjC1gB4aQ6mjABH8U0coit9GDPB
XgTPoZ1mUSQXmWJHs5ZvpkEjyJZsmgdmbybQV740+rVvmULAtMn8/C3jPzFE
GlZMEWOIJQqQiItR3qKdkrKourMCxlnQm1hjF3i0hvadalhch2q2u+4L7pXF
sWkprgWaI+UTSnKQ0xJtKf1pbZvqosvhBHbuDaxCxKrEnJEzbHlWA80O7LxD
ZCrYW9B4DoZJu89uSBMAy4Q/DspxAJ5U3yhWemNYiQB5Ri4YdRNxbjvKQLnB
KltD020J0h4L2uZ4ShVFfsiSMTMPyrFa8sbXhTdUFNp73/A27OkVC3NBS15u
Ay80zH0Kdy3HBTY5C3eYJsW7xQmq3s6UEFd3dYtkdcGKdeSfBjMOjYoiJcQK
ZJw6HvaJQRJBQtrLyefSiGxFRV52OQ1Ljynk1ohUvN0chc8iucxTwGxiEKWN
QoSisLX1ArG7IQAU72dKNYBUyVqUp9DtWmQ0h/g1JTgYhGV+y1guif8fvD9g
oRnIp9dDgywnJXnTrMUfrQaoVcPq8x1p9Q2QvESo5CQTxI9cBBbG+wYjSdzg
mPiLu5p5ysFRMLuj8CM0QzNUol6M36O+0PYZpVJ5cUwICGyatD9dw3mHvop0
Agl7BbTA81pkbMNRUvHGc0pcj/jriYqNPlBGt3AI2buhw05OQnJGTYlA54y8
jKSlJARPhRuZSTdEu14g+aOMRhi5V/OEFMOVyacwwTxpeUy9MAdz/nEU5m5j
PkKTHnGbDtwf03D4P6Nj+wH7tJk7CGBLawwscmTupB7izcT0RNg2bWcROU2H
F39Xw/AQSAVhyjZAGLT9ZomTZBsifI7S7uwlgivoaUrz2cHhHUfPWt/MazgG
c4TXtgTZaLdvt7spGReTwyLRyoqGPKoxymbz/GSo9z4uibLrrv2AVJxWD13i
ZBHy4OkwqVuaq1gV+e4OTKcYIGV7rCWOcynGDPZ+mWPLTIMoBpufKMVTcxVv
4DZPtAEiEQDEGDHDyQsWGc1NN0EhFFI6JrnGsb2lAZxiz6nc7Y+x0x1ZY78W
kq8qMTU8a5gPou7D0PGb1GjZWWVEfdxjTDY6YvrI3wI4RKCmO7nAc06xX9rg
ArRJbDyrDIw+6i/5u4Fyy4b0wqmfognv97XiljyvoDV9HOJuwJlrOLAlDBwZ
NCwsnHLjbHJi+IpYhL0hJ4QdheBITSiNNd1XLpoddZaj0CvCjvalUUXRBYfI
Rot+TKhzkFVHeQkKZoV5JqSQKIxWyf2amRAoTPJvjV8jxUSZZoPSCI3AqSKT
F+pKTBAr5dVpTGw3r82VNRL2eWGYR4KiiiXuj9uiG1p3qHv+tpuUEE+k7SKy
m3mdBygB4Q6EZLRDChWBHJGRx66udFtImdckTIis7hQmyoLAau+hLwHeQsFG
DTJ0v597aD7ZgBPHH31FJKclxEDEtEGbVgcwU0e5JSAgIPQyrnX82HYetTDQ
DTVlGr5G5N7H/dXwoR4vRis26mniMmY1zb13MduqR6hzBt0+qt6IJUqMrl5p
FF1eB0jIozVB+P4T56GoP88rjDEjAbMbPMlGILeEDVxpUL60J6BDkzzrFYln
nJYYqCkKBbd1N3uHjeCV3zcu6e603qmLVadTONxIXDDEricXOQv4Lh7BLHHl
i5lIcNzArfWiWXivv2VPxKjInS1NQbVx+Ea2CJORL/yyegmaWDaZUjPkJmyH
NImC+b130ZHOzioyLrOt++oDohAvfD2yNzCuJO+8uaYZXdvgUAm1UcyLg9qp
CzeApA6fFSYBxI2vmaFdMSVugsfgLUflrI7X9o2hCWz3YWQxU3Kib/ZNJBU4
fLk2+k/zncay26gxlGPmmlxmpR4el5mCzA9vaHJgM1tgI11bWQkSVkwxZcqY
nIFqhrzPu26O9EwScPUqy3tP0TDZ14FLf1YPi6AY1JxsBCmYlc0WeV6fqzRl
X2jn0EoF6WHPW4voTkBfXMFhaI1IbyItzyUux4QUhddUQyb0wb5rjz9MEOiZ
q4IadoImCjb+BjkQ1ISm8lU9b5GJ3goe6ue9p2XiXdwjUhXE8fepGeeH6JGd
OMEo/VpFlahjhdbwj1L+EWyXpC4GlZwAAUPIw2CABGnOh6QyOMWaLDRKHfoB
sGIyW6cN/wu52e3Ws0PVKf0FWbPtJ6+w+gs9hyKX/pd+e6+zeKcQ7J1BoHfT
QIjuPT16M+/nTvSIJMYQa6Mwe01eKGaVXHAxMixCY9rlwWAWj/RxMOqM1QBt
DvVm8oLaNm03WYlLl0qgg4DM5f2zjUDsfzldZX3V1z3I9qZVKB8ru4VvDxsa
ZfCSA6SsWr0XJziHCchmPTSWuxvve7I4+u9MK9I18pp00ouKQuGWuXWbOa2r
6xCbKHYci5xF+QJbMTuOTbYkm/Xp0hagCrq5kYANIpriQ0/SmdFnSEAFwVxe
hnjO87gkkIfvgK2yAZYxlVjNGwphlqQXcLLlqhNZ9IkMUKe03X1Xb/274NEM
w9J4OZCMB4JEJI36wFQ26uihtZIvFzlto5cyw/9muaOa3nzAaEK3pTYIigOC
VcW8LXmSNJ/08hUZIiv6BokqI0QbqhVqpMfapMaGkr+K4WXyYNUbpO/Knt8N
lfqsIN4SueifKWTI+LknWfktIrwBnKxZhtI4gpl18Mbew4FnPrMinLLeiVvj
QZA+BD9JvqDdNRuXf0NIO34YMbb3d/KSRZ5ye9bCAk0tnLJwSzEWhjsY+erT
pWxqJTxVKwx200JZkKFERh0yCdIz4pivj0kwzwA9Au/NAQiaaoM2S6BrCRI/
GezSvdEeFH6fjalyCZa/rRhacRdbrFbHzUH2QZjBH9BS0U/q8pCT8v6aErBj
r8cWunJt9uISdSC1eiQfGFrytT0BqjZwmwq95M7yAHFcUbt6JuIo9ZPdxi4x
yIwoJLlZi4IxuWTbJFlZvE5Sd7IP2kMgUlzVXVyX0om934qT5ZaI+nzSQjmr
8dE7I4/QpF6emMxJu92XM7kyKfx8Tbu7qL7iYvXzpwuHkfVd9KtMBG1f2mFB
K9oPwbo+BiHQbNEULFXf3fNEgqoDXXCsnQF8xw+c7jazEA0+1cysnuX5Z+3J
Dk4pvyh95c9NQy6rG6n6ma+WbYSuS3kyj5GOOyPYD93npZ7k6UWMMzl/RJuo
ue4wOmV9CldrbWMpvRwEQxhgaDcRhRh6QSIMhGYiYZQ9aqdbC+Y+Jgp52BBC
Pyd8XL3djqwyQ6+GxGFOMRkkQ6FRXRaEYzKjlQDOAeEhVyG3zPGei/B3vqOc
P8gXULHnZ5IUJb8yNcgcS9JvE6XrPZCU9ESRyMlRyfzIvoFQwIqfR/cDUmAQ
K0HqjMafMju5tcVJCUyxwj4GL4ovWuG0YMNUp/8T+GHOPRziGg22P5xWt9G9
puGKoxcnNH31uTk5woEHbm0lcXX16MQrUsT+nLGg0HI0tS3392nzHgcZpjrV
mj6vNOo+iV2q9CJnLMj7768W1ec/vE/e1hC1rFs8vVJAPHN+e1YieIHc1Lpj
0OZFwp6Ze2Q9V5+fnOPVpzYjxYwn0bAm3XpOSmNbzjMI2imC3o0IEmp19fKt
J9q4aO4WXw+K9Y3QFwfHKTHlrwTrRpufstG2YoijhBTubGvIBsnVcVojqdJC
p8PANyIOMswaOFUc0b+8efW1I/1lAEkTR1UdS2vzVE9c9Iicc6hin1DdQfs0
eXSnKWjedET79f79+x/Jj7ufXFVdcNi/eFxdWNb3Tj3SBcqZFxlCeMcrwKNF
wF+q1t7zvKA3g3b0zatP9SFOu+iDn7gh/eK/T1Lwxc/4m/c8epIh4Nmrvz95
tgTc9MhnJw88hEbp0c/pyZ951vjcjDF/gP9ozC/Ek+JyXIgIh70HntCmD/0U
EZZejj9w3wutwv2MXXLuu0ROLEpnzCUgUi9GdPQXdeisv3nyzBo0CIZdOCGC
ufFewjQ7hcvq3+Ea6A8Aib3GDH5Hww8kZpSUTvGJYyuSXJojmULOL62L2fwj
kn7ByRHaiI8aNNDKtGQi131B1HAtFYAzWl694iQFP3UBeFxAAwXYsyya3obe
zz+1e+m711LagaxvQ05sdZx8zFW5UuSs8JaIfGN4Mm5Y0y4WOy9rIa0HtFFd
hAluQ7E68ixG48YOfLDnBbM+cqdEZFFTWUILdq+VLfWShknIX+5AUTG8yUuu
0tN/B/AI2lfLrqmR/GOXoMK3qaK6yKqti9SNH9o/e2ssn6SDUIg6Jh7DEyfF
MGH/84SC68OCn2iR3O1hq9LWCVBqJYwIElvLZkbx00YO1ttRmjwwN+OeFvc5
1ZNygXVfMiBte8nSORz2KE8cuPZMA+TEkPGKJ63aWlJcd3W7Pyf8QM8ZDV5w
nxSUXmXV7zfkPb30z6d2Hck78iJ5Yc2ppaboqbdmLqfdDJGdDoKbxpmS1Dcn
FK8MdU7pyhJR/5aRjBre+bpTrGQMetnBIx5FcFAk9Rnp6L6aPUhsi3HNazfd
SdPZbevvuFiS2mJicw6bHKZf7JbE0u/l5NoPYGXQ4Eqf4ETYD9qTw2XQ7EhG
SWQzbaQJDKPnrJokg3OrofbD5bRcZM5z0PKXYsdZ3n1RiNG8+17mjvbvnRRX
31mnizBgo+SyhlONRk3tMFmz5RMubISs0WPoe10GV4V4P5kSCHbWpRmlnnd5
30xyc31oOsVDUmzn7imej8AvY0LzDk5KeTnB1rMQc9+SubIeICEHQk5NLKXb
yCdqLH7iDKW1IfInFAv3B+vaFGjdcjktpfgL7SBg0howndy3VX7XlJZoWc1i
IOelyEP13ZfVF8b31qTsIedQUrPC8YBaKAGzdTq9o5W/J5Lics1X29C0CpOG
yJasCOdQH7Gl7zi0YeHfKaUnnyeqr9W2rqUccmlyLoHfFdLaDpxiSw6SyuDR
wJ+YNme9eSA9KRYVR4cOu2NoOUPy+0F6jx6kEsv9tNe+0314x1TW6fbiSJ8G
moateKkTtS5PVkWuR9g0476ebaN81UwHZf41qv11wy3SnCHLuQCJ63yMCvKR
DqCa1sCVCmU06mL/ePbFAteH+R3l4p1GqvdC7XOV7+ab7/i4zLwXC2lalPeF
hYslvEP+sIUF5W0S0SnZTEzzhHGw3zSv0O+u6sCVcc6J+uNpiaOYvA6OTWEX
8072N+nga/1D3PhN1qGt39aUN/Ow5O93Q5OxSk+sw2bDVmjBj0OUnBfohn7L
lJlk9rKidTn1UrP4z/eYzVtoVrSazvdbmlxWZpD3NoljOlOgh6muqqC6nhii
CxG3SFlIUu5oNLbFIkMmnE/6N8uuX46Peactjhk3c6fINdmxi6JklkVEJ9C4
zloFl2oror3kOls0HQ1brtEy40QfIA+Wkz851Cud7iI14UjPTNKF2OdqpTP0
iKSGGDlcGvOCFFE+DkUbjwY32unft9udg1FIp0ihhaxvhC+5MMrbjJHSWUKT
ChpGepGaS2HxLcPPeiwOHcppgiRzCWK0czjHuTH2iFvfNk7aEGvGHOiTIjzc
r8WwxYlI1BN65TqRa7wr19IC8EWknp17Jg2dtv1q7Nqx2t/bz7/I7S06Alon
LZ7L29jzRbVBb0nPRirQT9LVy8SUc8VV6a+EbJxw7U+0X3OI9Avp1FRLYkpf
wSkPCzOiB0aZp0W7MFghIzWRUfY41R98L1zqWKOj1oDMpaSeOsiwX3HUA3Nu
CJlM+UeUqEUUwfwP+bup1Ryai8aU0HKvvEFc86eOk1exJrQU+8RXA1kDyVC4
wL5rUi3VUE7vowxF2yNlbUAbW2/jQn03ozQp2eEv9BZ6rQf65OHdif/Ooy+a
ZdCPdmOPpJYhyYE6Sj4lb0Y+Ks0lOUpuNL1CMTomN2WCxbxY55dSBYRYY7It
KL7o60evfnBazIj9+B+HhxKSJ7TpjZe0loRibWtLdsUu1hmlWaCXdDe9045U
i0HEWMx1dgbNUGfNLbRtfZES3kV5cDnvH+K0tJ6bNhb+tD9HT62TvF4IBITt
G/+utAJEbbxCjgpzJEhj3w4t0JebBlJ3mhfnXFnf5oLvZIm9iko4MqW+asky
0FoFwqFuGiAXHBV5qk1BfGAhO6/AJz/1YIMemNMjDGlbFrYMl0mEhv7TpGEc
19W07GekscMOqUMBxXPm+S2nec6smgafx56PUmn/EShNWj5WEVtUDqO46awT
iI0Gqffr7IQlVyKCPzl1aV0vehwZZ7r1pIYd+Iz3FRTN307U+SjZ1h71hK2P
TX5tusBCTsoOJwvNbge4dPksOW5YesZxm2HenOUsqb+bC5oxu+O22aPTxoaT
83niR5K1qkP1yT2VBSb3UJRQxyZ3KmCFi+jCxDRijCjPZ9YreuqJUhCce+St
vnIUno1F73+Q+pYQS0UzMjZYi+g4rxO3J/WFF63WmdQi2FcV5X5aOWXsqlx/
eFJekaggHeyQ8FpBiNVkc9rgL7VSHLfDwach40XqpKzR+WjosTRdzh5lU7iv
yX1xBpP4iHs6P2L9vuCS84Z4ZHfpnKX2kwrdZcSlcJjxIeUaHxCwtCSxepbd
atOgRgueN1sNNA4nouT8l7obOcEQK3q6pA69zHZyx6cW5gcFxC6RJ8JN8xuB
jitsW4SClLJqExq59Iq+O3GbcfBbNTqOOrHqGpXbmgNULqKH38DhrIVsu86j
niikfDFNj56Apqytyys6T1P4KReVpFqcfYsacVPYPUelqtgumQVJlr92j2sE
kOzB8a1GAzyOHusvvkQ+AO35dt+EaZeQfACp+ZGej/EyY41pyZldpltWjKJd
qeuIDVdZW2a0CtI/eqfdqpKRswukRP4wqeIXN4LIGfmmlClsL6IKxrEbXDrR
yjlYzDa6wAzwymbFm2hOXB83BghgES9IYzC4IWjlLcbHQHiKFBgPxP7PQl8Q
Z3Dc084VZEex4mGkk6iWKtPbsUBQ1h34gMXaEYmze2IepwZHbqcizA5lyW+v
yXLtyc5vNcXJLLmdRNfLJ4CTPU8DtgTu4hQKlLoT0jmWOCN7g1Uzoj2ncoke
aqExcKxFWmrs1IJummKg8iiM1Ah8ijQZ6YINZvVJMhB/UpgBy7o/nneQJ6lH
5V8UXVLaCAC3DQc48ZknGBW4IY4LS7MFrEc/kHyAz3owTxnjj2x6cS5Rxrae
7pxwnB+sIqKVrIq1xGL1Yn0N90lS+pV6Uqbguw1OOYhzwwuFNkVDd6lFpFkf
LgvllEaQDq3sYtGwSJSJtaKjgUp6PuhtJ+146OqWQwf1xmvtIyfYv7A6yL02
kaw1q21J/UT/kp03XA9BTwfnzj27Vgl+l9awZLiSn2kZyXRCgU2NkVZZQ62E
I5QE0tDtiU8487N6BiNWwjgIImrjNWjYi7ZSkOOLeLwc54ElMxCtBvFA9nkr
FTfa5k7Pt0hMYBiTlvFwOMYVTx26Jo55G5ice0cIXrY9E0g5hoW9GYrls0p6
MiGdY4VM6Y9eatzieLM7fbiuy1j6AZdCL/N8sIdTZdqfmixPUmAr9uB2SqFs
5Sg7IlI8qJGxAZzWFLfYMfzbDfBYGCshfhLsHlO60aPLtlvMET90exlE1RBs
t2OBUIW2n714Usb42bFn5eKCnglTwLzQdvz1PDJxlU5X38R72F7Ge9jiyS2O
fq9Tayn4WrEOvV3mRq9f+6aedtzzd3Z7W+e5ZcCgSbCzXNlipSEuu9cjtse3
IV6LUV4eBJ3gjjrudonNhHYW1vA8XNh5/DFIWhviTA38ND9JREFxw4QCX0EB
8JVDMr4xj3Ujv6Ruy6f/M84SZ/uh03PPrMqgCdk9pWfIP6Y2Ug0198StDJSd
W+Otjvjo/Eo8uU8iDGupc3BcRk+U2iIHOp46n1mS5CXbBu59jjgrnlvKYoLT
G0FO48HCWpdulcsiU5a743Aou7VO25Unq+FhXYyy6IQfhxV/yqfKyoNcUb6x
YYCyze02d08uOrYTP6XHqvVM93g8SxrL29FI4fVGuNfF1YDP+EzyDa4GJA1v
Gk36cMy/vBRQj/vwyOf3DHKFUm4ZBJdcf/A48Gy5V7vXKyC7Y3FTHHaUPXle
I+JTdiQHOe0LTXU9zhzV6Co7y5+4G4bk0xxV7+0eO1b9k/5xu1zELkaTq9aQ
l86tpLn4gjTMJTY7nQgYejk8wVYrnbtjixu7bOAoDmV/+IhIHW+v28SDh764
DQA3H9eXuhd2MhFBga1jxWWuQ72t7VS3lGBWR6UkpHdIv6e9fVmfs7dMiW/d
Yde+nrID9kpULoRaWh+XTNuOOKUsawyEOPAGrZTqDSB4mcm3awmTIMpZlqIE
LSJXbNXT27hSDLoubqF8KgX4NwoFn+WXTTqXfa28vBL6RorVJS98enwuXQUE
XcqUOnkh5d0TkSSdre0UXbFlFLjsbcaOJX44qbE604RXjCrRmKwzGYZGWsjL
lQTpWcH9FsXhvXjiG5XANuuRzlJrl10ble512M410ibv7bUikLuWjTse9MoP
FTJ1cd8dVJE2zaaGO9aCXreSjvaddAxxl3XCDwuG1BF9KOaIHFZs8Y8Nnnbi
UA4aunsPGp5ElVQpKXqfUW6ET4UTFiOPtzJiDgBB6/sQkhX79GrNVrQrQwNy
OYedb1jjAJz6ATVKdCBZ9h0BvbZ6LaXVi5u79H5HFoDcVezKq/rUROVWReV8
tQS3aw8w0lc8uz/Qu9XZcdzgDuSxD6dQIjsWnrQ1noQ2HkkderzX0yoiDFv4
2bwZKr+u5fmUWqiVbXHWCiXhKb8HJL91VI8+2r2cmRMp+p704pCQtWhL0g8B
Laru9HqGEBv6pA3P4b4O8ad5txlmnpqt0wlLlCisfqfIMp5SckUTWWrxauQy
PW6ljudQLfJnfXzZyQTxu1lbp6CbrB2Qu9xHzzeqcf9efkihr/daknEnF+fm
hTE52eKLa2JjX4rKmZvJooxpPfN64t7YnN3viqvRX3371q61keYzF78vx45j
s61KKiNcUle33deaV59cxj1cJkDz8GVwueM2syUJ8VkgAcSRSJPtOb/Il6mA
WBsfvV7MIF17ejXsEzdl1+RICGSt5m7j/KLqYcTdxWG3GiiOsobfe9VuOrfM
Lcwz36zEFvs4v8raWgBiFTX2EjE4fuLiTa2SJTMLLGXESLQoaVTcXHZSdJJG
11tu8jm/SelJlQ41p8vZ4PNtnXzGoom3DLvze37Ff5IjooC1FRCmJ98F5JOb
e2PJHeVkaGcY7Zz369OL3yM/k7Et5fXUhsayG1QZ1zpZr6iCPZVdZn3PvdUZ
DBgzRxwWzsryB7R/jOZ3lNRJJWW+tsMunADkm5ml0wSDOxJAqoDDvq35mu8E
LkBkb/iCawlPGQcuLm2RsJCUhXWFdvnHLa1ALptVNZCzKnx7hnIPmr1GsC3n
n9A1conGi97axhXwSllIQL+GdCgFvyU2I8il8W30UVq74wamomEJlyRoWTJ6
Bg3ZihuEHzijeatY3+Ab5/VytKPU3KECylBMQ7zGSy9qkga6y4JWSbzI1EZm
393H7Je5b5anF1UBRNm8FhAx1lf31CMWaqi6c9C7NmjA6FPrbe4bbcJ8Ofu9
d4rHUkEAsEvcDi5kLKkdu5jrpL6a29swFld4sYw1hXR6p355t0vRSFEETQ5t
2ZTtfrkyiEVlHbQZ1W7bs2aE06b92JBQtBNFHC1nNEHtMs7RTrShP+6H2bgl
TogZqWnV+4QC4FDDB9bVWdS9y4rZZxVRNF2c3NnePNCYAHLAafaW3RplO1/2
jcS+BOvTfn7Sv2+GwwlLSpm1zBsvyjRHkbVaOCsixLN7ONvFZ/rym7bSBaDW
c7FIgUk4Am6YQF4w1nfmEos6eNH4P/ecoyeOYJGQNwESEo7cMf4j/YipBiEi
OSkWxHFes3jwThpH+75EmM+vq49l66q80ykj86E5+emmC2OS7LpnxsBGNV1w
o0MsU0iFfZMOa7fSU4t1aD5vx15jUUnFJj1YHCQz7ifXSumh1c4haQFcWOGI
jGIZj9tIe5RURuyunJXdpwtEnw8KeMQ9BxLmLk9opVRNcPmJGesS4c8SLWj9
QyclBikm6FounXjH6YzZy26YMfrMImGE+YusDMC8xjDeXzLgdInvKh2LOkZs
edHGBwZ3IOidhVqBr0bTkE8Z9Ho76RrRc8x85AFrjZRJKh07Y0+CRonibhql
tDSdSs3NzMjxWKQDRr2rTE6Z95DT7agRsofUDnKDka5sGuYuoEzGgjmUUECx
scl7UPekBIYwJsd1B61fKHU5JDhhWbK62DTErOVZPvEm/z5DQdzUQXtLeRbZ
bfwaM4+p9SeKYq24kWO3pdHlv3zCjr/tNY+I1+y1OAltiUXEyYf24NESH+RO
ouuvr8+gaXmRsdyiKE9qU6P+www4M4CXXK/tulHp4PrpsVzz4pt/uOB//+zi
Z8kPxN9zFvdB/9EJZmzaA1/3pgHi4X/XQZkHJ8xDeVFRvBq5VBtuzI7//BI5
wkb++R5cTVdOW+glOI+mkVIYt2qmfyrj1nfDgdb+X4AoU0m3bgAA

-->

</rfc>
