<?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-nandakumar-moq-e2e-session-tests-00" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="MOQT E2E Session Tests">End-to-End Session Tests for Media over QUIC Transport</title>
    <seriesInfo name="Internet-Draft" value="draft-nandakumar-moq-e2e-session-tests-00"/>
    <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="17"/>
    <area/>
    <workgroup>Media Over QUIC</workgroup>
    <keyword>media over quic</keyword>
    <keyword>interoperability</keyword>
    <keyword>testing</keyword>
    <keyword>relay</keyword>
    <abstract>
      <?line 53?>

<t>This document describes a set of end-to-end tests that exercise a Media
over QUIC Transport (MOQT) relay through real client sessions. For each
test it gives a short description, the inputs, the message flow as a
call-flow diagram, and the expected outcome. The tests apply to MOQT
draft-18 and later; results for several public relays are published
in the moq-web interop report.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-nandakumar-moq-e2e-session-tests/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Media Over QUIC  mailing list (<eref target="mailto:moq@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/moq/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/moq/"/>.
      </t>
    </note>
  </front>
  <middle>
    <?line 61?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Interoperability between MOQT <xref target="MoQTransport"/> implementations is best
established by running the same scenarios against many relays and
comparing what each one does. This document describes such a set of
scenarios, for draft-18 <xref target="MoQTransport18"/> onwards. Each test drives one or more client sessions through a relay
and checks only what is observable at those clients: the control
messages they receive and the Objects delivered to them.</t>
      <t>The tests are implemented in the moq-web session-e2e suite <xref target="MOQ-WEB"/>,
whose results for several public relays are published in
<xref target="INTEROP-REPORT"/>. This document is a description of the tests, not of
any implementation, and is intended to let other implementers reproduce
them.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <dl>
        <dt>Pub:</dt>
        <dd>
          <t>A client session that publishes Tracks through the relay.</t>
        </dd>
        <dt>Sub:</dt>
        <dd>
          <t>A client session that subscribes to Tracks through the relay.</t>
        </dd>
        <dt>Relay:</dt>
        <dd>
          <t>The MOQT relay under test.</t>
        </dd>
        <dt>Client:</dt>
        <dd>
          <t>A single session in tests that need only one.</t>
        </dd>
      </dl>
    </section>
    <section anchor="test-environment">
      <name>Test Environment</name>
      <t>Each client opens its own MOQT session to the relay over WebTransport
<xref target="WebTransport"/>, offering the MOQT version under test. Unless a test
says otherwise:</t>
      <ul spacing="normal">
        <li>
          <t>Track Namespaces are unique per test run, of the form
<tt>moq-web-e2e/&lt;profile&gt;/&lt;label&gt;/&lt;random&gt;</tt>, so concurrent runs against
the same relay do not interfere.</t>
        </li>
        <li>
          <t>Object payloads identify the Object they belong to, so that every
received Object can be checked byte for byte against the one sent.
Tests 05 to 23 send generated chat payloads: the ASCII string
<tt>msg-&lt;G&gt;-&lt;O&gt;-</tt>, padded to 64 bytes with a deterministic pattern.
Test 15 sends <tt>obj-&lt;i&gt;</tt>, and tests 34 and later send the ASCII
string <tt>g&lt;G&gt;/o&lt;O&gt;</tt> for the Object at Group G and Object ID O.</t>
        </li>
        <li>
          <t>Two delivery profiles are used: "stream", which sends Objects on
subgroup streams, and "datagram", which sends them as Object
datagrams. Tests that run under both are marked as such.</t>
        </li>
        <li>
          <t>A wait for a message or Object that does not arrive fails the test
after the timeout given in the test.</t>
        </li>
        <li>
          <t>Applicability names the first MOQT draft the test runs on; it runs
on every later draft too. A test that depends on a feature added in a
later draft is skipped for earlier ones.</t>
        </li>
      </ul>
    </section>
    <section anchor="test-description-format">
      <name>Test Description Format</name>
      <t>Each test is described with four parts:</t>
      <dl>
        <dt>Description:</dt>
        <dd>
          <t>What the test exercises and why, in a few sentences.</t>
        </dd>
        <dt>Inputs:</dt>
        <dd>
          <t>The parameters the test chooses: Tracks, counts, timings and options.</t>
        </dd>
        <dt>Call Flow:</dt>
        <dd>
          <t>The messages exchanged, in order. Arrows show the direction of a
message; the relay is in the middle column. A message the relay
forwards appears once on each side. Lines starting with <tt>*</tt> are
actions or checks at that endpoint, not messages. On draft-23 a
FETCH is answered by REQUEST_OK; call flows show it as FETCH_OK, the
draft-22 name.</t>
        </dd>
      </dl>
      <t>A range written <tt>G1/O1..G2/O2</tt> runs from Object O1 of Group G1 to
Object O2 of Group G2, inclusive. An end Object of 0 means the whole
of Group G2: the FETCH carries no End Object.</t>
      <dl>
        <dt>Expected Outcome:</dt>
        <dd>
          <t>The conditions the test asserts. The test passes only if all of them
hold.</t>
        </dd>
      </dl>
    </section>
    <section anchor="test-cases">
      <name>Test Cases</name>
      <section anchor="t-01-setup">
        <name>Session Setup</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A client opens a WebTransport session to the relay and completes the MOQT setup exchange. This proves that version negotiation and any authorization the relay requires work end to end. The setup path is the same for both delivery profiles.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>MOQT version: the draft under test</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
 Client                   Relay
    |                       |
    * open WebTransport
    |---- CLIENT_SETUP ---->|
    |<---- SERVER_SETUP ----|
    * session ready
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>CLIENT_SETUP and SERVER_SETUP complete.</t>
          </li>
          <li>
            <t>The session reaches the ready state.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-02-announce">
        <name>Publish Namespace</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher sends PUBLISH_NAMESPACE for a fresh namespace. The relay must accept it.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Namespace: <tt>moq-web-e2e/&lt;profile&gt;/announce-&lt;profile&gt;/&lt;random&gt;</tt></t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay
    |                       |
    |- PUBLISH_NAMESPACE -->|
    |<----- REQUEST_OK -----|
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The relay answers PUBLISH_NAMESPACE with REQUEST_OK.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-03-publish">
        <name>Publish</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher sends PUBLISH for a Track that has no subscribers yet. The relay must accept it and the publisher must hold a Track Alias for the Track. The publisher does not wait for the relay to start forwarding.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Track: <tt>&lt;namespace&gt;/chat</tt>, publisher priority 128</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay
    |                       |
    |------ PUBLISH ------->|
    |<----- REQUEST_OK -----|
    * Track Alias known
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The relay answers PUBLISH with REQUEST_OK.</t>
          </li>
          <li>
            <t>The Track Alias is a non-negative integer.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-04-subscribe-namespace">
        <name>Namespace Subscription</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber sends SUBSCRIBE_NAMESPACE for a prefix, then a publisher announces a namespace under that prefix. The relay must tell the subscriber about the new namespace with a NAMESPACE message on the SUBSCRIBE_NAMESPACE request stream.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Prefix: <tt>moq-web-e2e/&lt;profile&gt;/nssub-&lt;profile&gt;</tt></t>
          </li>
          <li>
            <t>Namespace: the prefix plus one random field</t>
          </li>
          <li>
            <t>Wait between SUBSCRIBE_NAMESPACE and PUBLISH_NAMESPACE: 200 ms</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<-SUBSCRIBE_NAMESPACE--|
    |                       |----- REQUEST_OK ----->|
    |                       |                       * wait 200 ms
    |- PUBLISH_NAMESPACE -->|                       |
    |<----- REQUEST_OK -----|                       |
    |                       |----- NAMESPACE ------>|
    |                       |                       * namespace seen
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The subscriber receives NAMESPACE for exactly the announced namespace within 10 s. Namespaces left over from earlier runs are ignored.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-05-subscribe">
        <name>Subscribe and Deliver</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher publishes a Track and a subscriber subscribes to it. The publisher then sends a run of Objects and the subscriber checks each one it receives against what was sent. On streams every Object must arrive, in order. Datagrams are not retransmitted, so a small loss is tolerated.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Track: <tt>&lt;namespace&gt;/chat</tt>, default subscription filter</t>
          </li>
          <li>
            <t>Objects: 30 generated chat payloads of 64 bytes, 10 per Group (Groups 0 to 2)</t>
          </li>
          <li>
            <t>Collection time: up to 20 s (stream), 8 s (datagram)</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |                       |<----- SUBSCRIBE ------|
    |                       |--- SUBSCRIBE_OK ----->|
    |                       |                       * wait 250 ms
    |== Objects 0/0..2/9 ==>|== Objects 0/0..2/9 ==>|
    |                       |                       * check each
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>Stream: all 30 Objects arrive, in Group and Object order, and none arrives more than once.</t>
          </li>
          <li>
            <t>Datagram: at least 27 of the 30 Objects arrive (no more than 10% lost); the lost ones are reported.</t>
          </li>
          <li>
            <t>Every received Object is byte-identical to the Object sent.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-06-subscribe-update">
        <name>Pause and Resume</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber pauses its subscription with REQUEST_UPDATE, then resumes it. Objects sent after the resume must reach the subscriber, showing that the relay restarts delivery. Objects sent while paused are not required to be delivered.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Objects: 30 generated chat payloads, 15 before the pause and 15 after the resume</t>
          </li>
          <li>
            <t>Pause: REQUEST_UPDATE that stops forwarding (FORWARD 0 on draft-22, PAUSED on draft-23)</t>
          </li>
          <li>
            <t>Resume: REQUEST_UPDATE that restarts forwarding</t>
          </li>
          <li>
            <t>A relay may pass the pause on to the publisher. If it did, Pub waits up to 5 s for the relay to turn forwarding back on before sending the second 15 Objects, so they are not dropped at the publisher.</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |                       |<----- SUBSCRIBE ------|
    |                       |--- SUBSCRIBE_OK ----->|
    |===== 15 Objects =====>|===== 15 Objects =====>|
    |                       |                       * wait 500 ms
    |                       |                       * some arrived
    |                       |                       * pause:
    |                       |<--- REQUEST_UPDATE ---|
    |                       |----- REQUEST_OK ----->|
    |<-- REQUEST_UPDATE ----|                       |
    |   (optional: pause    |                       |
    |   passed on to Pub)   |                       |
    |                       |                       * wait 250 ms
    |                       |                       * resume:
    |                       |<--- REQUEST_UPDATE ---|
    |                       |----- REQUEST_OK ----->|
    |<-- REQUEST_UPDATE ----|                       |
    |   forward 1 / PAUSED  |                       |
    |   cleared (if paused) |                       |
    * wait up to 5 s for it |                       |
    |== 15 more Objects ===>|== 15 more Objects ===>|
    |                       |                       * more arrive
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>Some Objects arrive before the pause.</t>
          </li>
          <li>
            <t>At least one Object arrives within 5 s of the resume.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-07-unsubscribe">
        <name>Unsubscribe</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber receives some Objects and then ends its subscription. On draft-22 and draft-23 this cancels the SUBSCRIBE request stream. Objects the publisher sends afterwards must not reach the subscriber.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Objects: 30 generated chat payloads, 15 before and 15 after the unsubscribe</t>
          </li>
          <li>
            <t>Settle time after unsubscribing: 500 ms; observation time: 1 s</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |                       |<----- SUBSCRIBE ------|
    |                       |--- SUBSCRIBE_OK ----->|
    |===== 15 Objects =====>|===== 15 Objects =====>|
    |                       |                       * wait 500 ms
    |                       |<-- cancel SUBSCRIBE --|
    |                       |                       * wait 500 ms
    |== 15 more Objects ===>|                       |
    |                       |                       * wait 1 s
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>Some Objects arrive before the unsubscribe.</t>
          </li>
          <li>
            <t>No Object arrives in the 1 s observation period after the settle time.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-08-track-status">
        <name>Track Status</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A second session queries the status of a Track another session has published. The relay must answer the TRACK_STATUS request rather than leave it pending.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Track: <tt>&lt;namespace&gt;/chat</tt>, published 250 ms before the query</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Req
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |                       |<---- TRACK_STATUS ----|
    |                       |- REQUEST_OK / ERROR ->|
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The relay answers with REQUEST_OK or REQUEST_ERROR; either is a pass.</t>
          </li>
          <li>
            <t>On REQUEST_OK, the Largest Location, when present, is a valid Group and Object.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-09-fetch">
        <name>Fetch from Cache</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher sends Objects with no subscriber, so the relay can only cache them. A second session then FETCHes a range and checks the returned Objects byte for byte. A relay that refuses FETCH is reported, and the test does not fail.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each); a large-payload variant runs on stream only</t>
          </li>
          <li>
            <t>Default: 30 Objects of 64 bytes, 10 per Group; FETCH of 1/0..1/9 (10 Objects)</t>
          </li>
          <li>
            <t>Large payload: 300 Objects of 2048 bytes, 10 per Group; FETCH of 0/0..29/9 (300 Objects)</t>
          </li>
          <li>
            <t>Publisher Track property: max cache duration 60 s</t>
          </li>
          <li>
            <t>Wait before the FETCH: 500 ms</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |====== Objects =======>|                       |
    |                       * cached
    |                       |<--- FETCH 1/0..1/9 ---|
    |                       |------ FETCH_OK ------>|
    |                       |=fetch stream Objects=>|
    |                       |                       * check each
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>Every Object in the range arrives within 10 s.</t>
          </li>
          <li>
            <t>No Object outside the range arrives, and none arrives more than once.</t>
          </li>
          <li>
            <t>Every Object is byte-identical to the Object sent.</t>
          </li>
          <li>
            <t>If the relay answers the FETCH with REQUEST_ERROR, the test is reported as not supported rather than failed.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-10-fetch-cancel">
        <name>Fetch Cancel</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber starts a large FETCH and cancels it as soon as the first Object arrives. On draft-22 and draft-23 the cancel closes the FETCH request stream and stops the fetch data stream. Delivery must then stop. A relay that refuses FETCH is reported, and the test does not fail.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Objects: 600 of 2048 bytes, 10 per Group, cached by the relay (max cache duration 60 s)</t>
          </li>
          <li>
            <t>FETCH range: 0/0..59/9</t>
          </li>
          <li>
            <t>Settle time after the cancel: 500 ms; observation time: 1 s</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH ------->|                       |
    |<----- REQUEST_OK -----|                       |
    |==== 600 Objects =====>|                       |
    |                       |<-- FETCH 0/0..59/9 ---|
    |                       |------ FETCH_OK ------>|
    |                       |==== first Object ====>|
    |                       |<---- cancel FETCH ----|
    |                       |                       * wait 500 ms
    |                       |                       * watch 1 s
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The first Object arrives within 5 s.</t>
          </li>
          <li>
            <t>No Object arrives in the 1 s observation period.</t>
          </li>
          <li>
            <t>Fewer than 600 Objects are delivered in total.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-11-goaway">
        <name>Client GOAWAY</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A client sends GOAWAY without a New Session URI. The relay is not required to respond; the test checks that a wire-valid GOAWAY is sent and that the session starts draining.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>New Session URI: none</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
 Client                   Relay
    |                       |
    |------- GOAWAY ------->|
    * session closing
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>After sending GOAWAY the session is in the closing state.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-12-session-close">
        <name>Session Close Codes</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A client closes its session with a given Session Termination code. The code must be carried in the WebTransport close. The relay may close the connection in response; that is allowed.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Case 1: code NO_ERROR (0x0), reason "test done"</t>
          </li>
          <li>
            <t>Case 2: code PROTOCOL_VIOLATION (0x3), reason "e2e-injected"</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
 Client                   Relay
    |                       |
    |--- WT close(code) --->|
    * session ended
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>The close completes without an error.</t>
          </li>
          <li>
            <t>The session ends in the closed (none) state.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-13-session-termination">
        <name>Session Termination and Migration</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>These cases check how the client handles the end of a session without needing the relay to end it. GOAWAY with a New Session URI is delivered to the client locally, as if the relay had sent it.</t>
          </dd>
        </dl>
        <t>Inputs:</t>
        <ul spacing="normal">
          <li>
            <t>Delivery profiles: stream and datagram (run once each)</t>
          </li>
          <li>
            <t>Case 1: the client closes its own session</t>
          </li>
          <li>
            <t>Case 2: GOAWAY with New Session URI <tt>https://alt-relay.example/moq</tt> and a 5 s timeout, delivered to the client locally</t>
          </li>
          <li>
            <t>Case 3: the client is asked to migrate to <tt>https://foo.example/moq</tt> without the worker it needs for migration</t>
          </li>
        </ul>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
 Client                   Relay
    |                       |
    * case 1: close(), no session-terminated
    |                       |
    * case 2: GOAWAY delivered locally;
    *         New Session URI held
    |                       |
    * case 3: migrate() refused
]]></artwork>
        <t>Expected Outcome:</t>
        <ul spacing="normal">
          <li>
            <t>Case 1: no session-terminated event is raised for a close the client started.</t>
          </li>
          <li>
            <t>Case 2: the client records the New Session URI as its pending migration target and moves to the closing state.</t>
          </li>
          <li>
            <t>Case 3: the migration request is refused with an error that names the missing worker mode.</t>
          </li>
        </ul>
      </section>
      <section anchor="t-14-setup-options">
        <name>SETUP Options</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
        </dl>
        <t>Three tests on the Setup Options carried in CLIENT_SETUP and SERVER_SETUP.</t>
        <section anchor="t-14-setup-unknown">
          <name>Unknown Client Setup Options Are Ignored</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The client advertises two Setup Options with unregistered keys. A
peer is required to ignore unknown Setup Options (<xref section="6.3.2" sectionFormat="of" target="MoQTransport22"/>), so the relay must still complete the setup exchange.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Setup Option 0x40 (even key): varint 0x1234.</t>
                </li>
                <li>
                  <t>Setup Option 0x41 (odd key): bytes "moq-web-e2e".</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    * carries options 0x40 and 0x41
    |<-------------- SERVER_SETUP --|
    * session ready
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SERVER_SETUP is received and the session reaches the ready state.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-14-setup-relay">
          <name>Relay Setup Options Are Well Formed</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The client records the Setup Options the relay advertises in
SERVER_SETUP. A relay that advertises none passes.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>None beyond a plain CLIENT_SETUP.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    * list each option and its value kind
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Every option with an even key carries a varint.</t>
                </li>
                <li>
                  <t>Every option with an odd key carries a byte string.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-14-setup-late">
          <name>Client Setup Options Are Fixed After Setup</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>Once setup has run, the client must not change the Setup Options it
advertised. This is a local check made on a live session; nothing is
sent to the relay for it.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Setup Option 0x40, set after SERVER_SETUP.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    * try to set option 0x40: refused locally, nothing sent
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The attempt to change Setup Options after setup fails locally.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-15-track-status">
        <name>TRACK_STATUS Reports the Largest Object</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher sends three Objects, then a second session asks the
relay for the Track status (<xref section="9.13" sectionFormat="of" target="MoQTransport22"/>). The relay may
answer from its own state or forward the request; only the answer is
checked. A REQUEST_ERROR is tolerated.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track: <tt>&lt;ns&gt;/chat</tt>, stream delivery.</t>
              </li>
              <li>
                <t>Objects 0/0, 1/0 and 2/0, one per Group.</t>
              </li>
              <li>
                <t>A 250 ms wait before TRACK_STATUS.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Req
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    |== g0/o0 g1/o0 g2/o0 =>|                       |
    * wait 250 ms
    |                       |<------ TRACK_STATUS --|
    |                       |-- REQUEST_OK -------->|
    |                       |       LARGEST_OBJECT  *
    |                       |                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The answer is REQUEST_OK with a Request ID, or REQUEST_ERROR (the
test then ends).</t>
              </li>
              <li>
                <t>If LARGEST_OBJECT (<xref section="9.20.17" sectionFormat="of" target="MoQTransport22"/>) is present, its Group
and Object are non-negative.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-16-namespace-done">
        <name>NAMESPACE_DONE Ends a Namespace Batch</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber sends SUBSCRIBE_NAMESPACE for a prefix with no
publishers. The relay may close the initial batch with
NAMESPACE_DONE (<xref section="9.17" sectionFormat="of" target="MoQTransport22"/>) or keep the request open for
later NAMESPACE messages; both are accepted.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Prefix: <tt>moq-web-e2e/chat-stream/ns-done</tt>.</t>
              </li>
              <li>
                <t>A 500 ms wait for NAMESPACE and NAMESPACE_DONE.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- SUBSCRIBE_NAMESPACE ------->|
    |<---------------- REQUEST_OK --|
    |<---------- NAMESPACE (0..n) --|
    |<------------ NAMESPACE_DONE --|
    * NAMESPACE_DONE optional; wait 500 ms
    |                               |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>SUBSCRIBE_NAMESPACE succeeds with a Request ID.</t>
              </li>
              <li>
                <t>Whether NAMESPACE_DONE arrived is recorded, not asserted.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-17-subscribe-tracks">
        <name>SUBSCRIBE_TRACKS Is Accepted</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber sends SUBSCRIBE_TRACKS (<xref section="9.18" sectionFormat="of" target="MoQTransport22"/>)
for a prefix under which a track is published, with the default
forwarding state: FORWARD = 1 on draft-22, and no PAUSED on draft-23.
Draft-22 and later have no subscription filter on SUBSCRIBE_TRACKS.
The test checks that the relay accepts the request.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Published track: <tt>&lt;prefix&gt;/&lt;random&gt;/chat</tt>.</t>
              </li>
              <li>
                <t>SUBSCRIBE_TRACKS prefix: <tt>moq-web-e2e/chat-stream/subtracks</tt>.</t>
              </li>
              <li>
                <t>Forwarding: the default (FORWARD = 1, or no PAUSED); no filter.</t>
              </li>
              <li>
                <t>A 250 ms wait after PUBLISH.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |<-- SUBSCRIBE_TRACKS --|
    |                       |   default forwarding  |
    |                       |-- REQUEST_OK -------->|
    |                       |                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>SUBSCRIBE_TRACKS succeeds and yields a subscription ID.</t>
              </li>
              <li>
                <t>A REQUEST_ERROR is tolerated and ends the test.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-18-auth-token">
        <name>SUBSCRIBE with an Authorization Token</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber attaches an AUTHORIZATION_TOKEN parameter (<xref section="9.20.2" sectionFormat="of" target="MoQTransport22"/>) to SUBSCRIBE. The token is not one the relay knows,
so the relay may refuse it; the test checks that the parameter is
parsed, either way.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track: <tt>&lt;ns&gt;/chat</tt>.</t>
              </li>
              <li>
                <t>Token type 0x63346d, 19 bytes of token value.</t>
              </li>
              <li>
                <t>A 250 ms wait after PUBLISH.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |<- SUBSCRIBE (token) --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |         or a refusal  *
    |                       |                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>SUBSCRIBE_OK with a subscription ID, or a SUBSCRIBE error refusing
the token.</t>
              </li>
              <li>
                <t>Any other failure, such as the session closing, fails the test.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-19-filters">
        <name>Subscription Filters</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
        </dl>
        <t>Two tests on SUBSCRIBE filters (<xref section="9.20.9" sectionFormat="of" target="MoQTransport22"/>; LOCATION_FILTER on draft-22 and later).</t>
        <section anchor="t-19-filters-accept">
          <name>Each Filter Is Accepted</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A subscriber subscribes to a published track once with each filter
type. Only acceptance is checked, not which Objects are delivered.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>&lt;ns&gt;/chat</tt>, one run per filter.</t>
                </li>
                <li>
                  <t>Filters: Next Group; Largest Object; Absolute Start at 0/0;
Absolute Range from 0/0 to the end of Group 1.</t>
                </li>
                <li>
                  <t>A 250 ms wait after PUBLISH.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |< SUBSCRIBE (filter) --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SUBSCRIBE_OK with a subscription ID.</t>
                </li>
                <li>
                  <t>A SUBSCRIBE error or REQUEST_ERROR is tolerated; a transport
failure fails the test.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-19-filters-deliver">
          <name>Absolute Filters Deliver Exactly Their Range</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A subscriber with an absolute filter receives every Object in the
filter range and none after it.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>&lt;ns&gt;/chat</tt>, 30 Objects, 10 per Group (Groups 0 to 2).</t>
                </li>
                <li>
                  <t>Absolute Start at 0/0: expects Groups 0 to 2 (30 Objects).</t>
                </li>
                <li>
                  <t>Absolute Range 0/0 to end of Group 1: expects Groups 0 and 1 (20
Objects).</t>
                </li>
                <li>
                  <t>Collection timeout 20 s, then a further 500 ms.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    |                       |< SUBSCRIBE (filter) --|
    |                       |-- SUBSCRIBE_OK ------>|
    * wait 250 ms
    |== g0..g2, 10 each ===>|                       |
    |                       |== Objects in range ==>|
    |                       |     wait 500 ms more  *
    |                       |                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Every Object of the filter range arrives within 20 s.</t>
                </li>
                <li>
                  <t>No Object from a Group after the range arrives.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-20-expires-ngr">
        <name>EXPIRES and NEW_GROUP_REQUEST</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
        </dl>
        <t>Three tests that the relay accepts requests carrying EXPIRES (<xref section="9.20.16" sectionFormat="of" target="MoQTransport22"/>) and NEW_GROUP_REQUEST (<xref section="9.20.19" sectionFormat="of" target="MoQTransport22"/>). Delivery of a requested new Group is tested in <xref target="t-44-new-group-request"/>.</t>
        <section anchor="t-20-expires">
          <name>SUBSCRIBE to a Track Published with EXPIRES</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The publisher sets EXPIRES on its PUBLISH; a subscriber then
subscribes.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>&lt;ns&gt;/chat</tt>, EXPIRES 30 s.</t>
                </li>
                <li>
                  <t>A 250 ms wait after PUBLISH.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH (EXPIRES) ->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |<--------- SUBSCRIBE --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SUBSCRIBE_OK with a subscription ID.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-20-ngr">
          <name>REQUEST_UPDATE with NEW_GROUP_REQUEST</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>On a track published with DYNAMIC_GROUPS, the subscriber sends
REQUEST_UPDATE carrying NEW_GROUP_REQUEST. The test does not wait
for its REQUEST_OK.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>&lt;ns&gt;/chat</tt>, DYNAMIC_GROUPS = 1.</t>
                </li>
                <li>
                  <t>A 250 ms wait after PUBLISH.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH (DYN_GRP) ->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |<--------- SUBSCRIBE --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |<---- REQUEST_UPDATE --|
    |                       |    NEW_GROUP_REQUEST  *
    |                       |                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The subscription exists after SUBSCRIBE_OK.</t>
                </li>
                <li>
                  <t>Sending REQUEST_UPDATE with NEW_GROUP_REQUEST does not fail.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-20-subscribe-tracks">
          <name>SUBSCRIBE_TRACKS for a Namespace</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A subscriber sends SUBSCRIBE_TRACKS for the exact namespace of a
published track.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>&lt;ns&gt;/chat</tt>; SUBSCRIBE_TRACKS prefix <tt>&lt;ns&gt;</tt>.</t>
                </li>
                <li>
                  <t>A 250 ms wait after PUBLISH.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    * wait 250 ms
    |                       |<-- SUBSCRIBE_TRACKS --|
    |                       |-- REQUEST_OK -------->|
    |                       |         or a refusal  *
    |                       |                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_OK with a subscription ID, or a refusal or stream reset.</t>
                </li>
                <li>
                  <t>Any other failure, such as the session closing, fails the test.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-21-stream-reset">
        <name>Publisher Resets a Subgroup Stream</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>While a subgroup stream is open, the publisher resets it with an
error code (<xref section="11.3.2" sectionFormat="of" target="MoQTransport22"/>). The test checks the publisher
side; whether the relay passes the reset on to the subscriber is
relay policy and is not checked.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track: <tt>&lt;ns&gt;/chat</tt>, stream delivery.</t>
              </li>
              <li>
                <t>3 Objects on one subgroup stream, then a 100 ms wait.</t>
              </li>
              <li>
                <t>Reset code TOO_FAR_BEHIND, reason "e2e-injected too-far-behind".</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    |                       |<--------- SUBSCRIBE --|
    |                       |-- SUBSCRIBE_OK ------>|
    * wait 250 ms
    |== 3 Objects =========>|                       |
    |                       |== Objects ===========>|
    * wait 100 ms
    |-- RESET_STREAM ------>|                       |
    * TOO_FAR_BEHIND; local stream-reset event
    |                       |                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Exactly one stream reset is reported at the publisher, with code
TOO_FAR_BEHIND, the given reason and the Track Alias of the track.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-22-padding">
        <name>Padding Does Not Disturb Delivery</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>The publisher sends padding streams and padding datagrams (<xref section="11.5" sectionFormat="of" target="MoQTransport22"/>) around two real Objects. The relay must accept the
padding and keep delivering the real Objects.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track: <tt>&lt;ns&gt;/chat</tt>, stream delivery.</t>
              </li>
              <li>
                <t>Padding stream of 64 bytes and padding datagram of 32 bytes before
the Objects.</t>
              </li>
              <li>
                <t>2 real Objects.</t>
              </li>
              <li>
                <t>An empty padding stream and an empty padding datagram after them.</t>
              </li>
              <li>
                <t>A 500 ms wait for delivery.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH ----------->|                       |
    |<-------- REQUEST_OK --|                       |
    |                       |<--------- SUBSCRIBE --|
    |                       |-- SUBSCRIBE_OK ------>|
    * wait 250 ms
    |-- pad stream 64 B --->|                       |
    |-- pad dgram 32 B ---->|                       |
    |== 2 Objects =========>|                       |
    |-- pad stream, dgram ->|                       |
    |                       |== 2 Objects =========>|
    |                       |          wait 500 ms  *
    |                       |                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The subscriber receives at least the 2 real Objects.</t>
              </li>
              <li>
                <t>No all-zero (padding) payload is delivered as an Object.</t>
              </li>
              <li>
                <t>Neither session is closed by the relay while padding is sent.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-23-priority">
        <name>Subscribers with Different Priorities</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Two subscribers subscribe to the same track with different
SUBSCRIBER_PRIORITY and GROUP_ORDER values (<xref section="5.1" sectionFormat="of" target="MoQTransport22"/>).
Both must receive delivery; arrival order is not checked, since
scheduling is best effort.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track: <tt>&lt;ns&gt;/chat</tt>, 4 Objects.</t>
              </li>
              <li>
                <t>Sub1: priority 16, Group Order descending.</t>
              </li>
              <li>
                <t>Sub2: priority 240, Group Order ascending.</t>
              </li>
              <li>
                <t>Waits: 300 ms before publishing, 800 ms for delivery.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                Relay               Sub1                Sub2
    |                   |                   |                   |
    |-- PUBLISH ------->|                   |                   |
    |<---- REQUEST_OK --|                   |                   |
    |                   |<----- SUBSCRIBE --|                   |
    |                   |-- SUBSCRIBE_OK -->|                   |
    |                   |                   * prio 16, desc
    |                   |<--------- SUBSCRIBE (prio 240, asc) --|
    |                   |-- SUBSCRIBE_OK ---------------------->|
    * wait 300 ms
    |== 4 Objects =====>|                   |                   |
    |                   |== Objects =======>|                   |
    |                   |== Objects ===========================>|
    * wait 800 ms
    |                   |                   |                   |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Each subscriber receives at least one Object.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-25-reserved">
        <name>Reserved Namespaces Are Refused Locally</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
        </dl>
        <t>A Track Namespace whose first field begins with "." is reserved (<xref section="2.4.3" sectionFormat="of" target="MoQTransport22"/>), and a client must not originate requests under it. Both tests run on a live session and check that the request is refused before anything is sent.</t>
        <section anchor="t-25-reserved-publish">
          <name>PUBLISH Under a Reserved Namespace</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The client tries to publish under a reserved namespace.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>.session/chat</tt>.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    * publish .session/chat: refused locally, no PUBLISH sent
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The publish request fails locally, citing the reserved-namespace
rule.</t>
                </li>
                <li>
                  <t>The request is rejected before it is sent.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-25-reserved-subscribe">
          <name>SUBSCRIBE Under a Reserved Namespace</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The client tries to subscribe under a reserved namespace.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track: <tt>.reserved/chat</tt>.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    * subscribe .reserved/chat: refused locally, no SUBSCRIBE sent
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The subscribe request fails locally, citing the reserved-namespace
rule.</t>
                </li>
                <li>
                  <t>The request is rejected before it is sent.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-26-idle">
        <name>Idle Connection Handling</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
        </dl>
        <t>Two tests on keeping an otherwise idle session alive and closing it when idle (<xref section="15.6.1" sectionFormat="of" target="MoQTransport22"/>).</t>
        <section anchor="t-26-keepalive">
          <name>Keepalive Padding Keeps the Session Up</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>With no other traffic, the client sends padding datagrams (<xref section="11.5" sectionFormat="of" target="MoQTransport22"/>) as keepalives. The relay must drop them without
affecting the session.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Keepalive interval 100 ms.</t>
                </li>
                <li>
                  <t>Idle period 400 ms.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    |-- padding datagram ---------->|
    |-- padding datagram ---------->|
    * every 100 ms, for 400 ms
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The session is still ready after 400 ms.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-26-idle-close">
          <name>Local Idle Timeout Closes the Session</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The client sets a short local idle timeout and sends nothing. It
must close the session itself when the timer expires.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Idle timeout 250 ms.</t>
                </li>
                <li>
                  <t>Deadline 2 s.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                           Relay
    |                               |
    |-- CLIENT_SETUP -------------->|
    |<-------------- SERVER_SETUP --|
    * no traffic for 250 ms
    |-- session close ------------->|
    * NO_ERROR, "idle timeout"
    |                               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Within 2 s the session is terminated locally with NO_ERROR and an
idle-timeout reason.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-27-implementation-string">
        <name>MOQT_IMPLEMENTATION Setup Option</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A client omits the MOQT_IMPLEMENTATION Setup Option by default and may
opt in to sending one. Setup must complete either way: the relay
ignores the option's value. A third check confirms the client refuses
to set the string once setup has started.</t>
          </dd>
        </dl>
        <section anchor="t-27a">
          <name>Setup without MOQT_IMPLEMENTATION</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>MOQT_IMPLEMENTATION: not sent (the default)</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |-- CLIENT_SETUP (no impl) -->|
    |<------ SERVER_SETUP --------|
    * session ready               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SERVER_SETUP is received and the session is ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-27b">
          <name>Setup with MOQT_IMPLEMENTATION</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>MOQT_IMPLEMENTATION: "moq-web e2e-27"</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    * set implementation string   |
    |---- CLIENT_SETUP (impl) --->|
    |                             * ignores the option
    |<------ SERVER_SETUP --------|
    * session ready               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SERVER_SETUP is received and the session is ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-27c">
          <name>Implementation String after Setup</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>MOQT_IMPLEMENTATION: "too-late", set after setup completes</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |------- CLIENT_SETUP ------->|
    |<------ SERVER_SETUP --------|
    * set implementation string   |
    * call throws; nothing sent   |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Setting the string after setup fails locally and sends nothing.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-28-grease">
        <name>Grease Setup Options</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Grease values of the form 0x7f * N + 0x9D are reserved so that
receivers are exercised on unknown values, which they must ignore.
The client advertises two grease Setup Options in CLIENT_SETUP and
expects setup to complete. A local check first confirms the grease
pattern itself.</t>
          </dd>
        </dl>
        <section anchor="t-28a">
          <name>Grease Codepoint Pattern</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Values 0x9D, 0x11C (grease) and 0x40 (not grease)</t>
                </li>
              </ul>
            </dd>
            <dt>Call Flow:</dt>
            <dd>
              <t>None; this check is local to the client.</t>
            </dd>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>0x9D and 0x11C match the grease pattern.</t>
                </li>
                <li>
                  <t>0x40 does not.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-28b">
          <name>Setup with Grease Setup Options</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Setup Option 0x9D (odd key): a byte string</t>
                </li>
                <li>
                  <t>Setup Option 0x11C (even key): varint 0xDEAD</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |--- CLIENT_SETUP (grease) -->|
    |                             * ignores 0x9D, 0x11C
    |<------ SERVER_SETUP --------|
    * session ready               |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>SERVER_SETUP is received and the session is ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-29-update-multi-track">
        <name>Pause Scoped to One Subscription</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>One publisher session publishes two Tracks, A and B, and one
subscriber subscribes to both. Pausing A with REQUEST_UPDATE
(Forward = 0) must affect only A: Objects on B keep arriving. This
catches a publisher or relay that applies a pause to every
subscription in the session.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Tracks A and B, each in its own namespace, stream delivery</t>
              </li>
              <li>
                <t>10 Objects on each Track before the pause, 20 after</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |---- PUBLISH A, B ---->|                       |
    |                       |<-- SUBSCRIBE A, B ----|
    |                       |-- SUBSCRIBE_OK x2 --->|
    |                       |                       * wait 250 ms
    |=== 10 Objects A, B ==>|                       |
    |                       |==== Objects A, B ====>|
    |                       |                       * wait 500 ms
    |                       |                       * got A and B
    |                       |<- REQUEST_UPDATE A ---|
    |                       |                       * Forward = 0
    |<- REQUEST_UPDATE A ---|                       |
    |                       |                       * wait 250 ms
    |=== 20 Objects A, B ==>|                       |
    |                       |====== Objects B =====>|
    |                       |      B arrives in 5 s *
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Objects on both A and B arrive before the pause.</t>
              </li>
              <li>
                <t>After A is paused, new Objects on B arrive within 5 s.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-30-room-fanout">
        <name>Room Fan-out of Namespaces</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Four peers join a room: all of them subscribe to the room prefix
with SUBSCRIBE_NAMESPACE, and then, one at a time, each announces its
own namespace under it. Every peer must learn about every other peer,
including peers that announced before it did. The diagram shows
one pair; the test covers every ordered pair of the 4 peers.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>4 peers, room prefix <tt>moq-web-e2e/chat-stream/room-&lt;id&gt;</tt></t>
              </li>
              <li>
                <t>Peer namespace: <tt>&lt;room prefix&gt;/&lt;peer&gt;</tt></t>
              </li>
              <li>
                <t>500 ms after every peer has subscribed, 500 ms between
announcements, and 1000 ms to settle at the end</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
  peerA                   Relay                   peerB
    |                       |                       |
    |- SUBSCRIBE_NAMESPACE >|                       |
    |                       |< SUBSCRIBE_NAMESPACE -|
    |- PUBLISH_NAMESPACE A >|                       |
    |                       |----- NAMESPACE A ---->|
    * wait 500 ms           |                       |
    |                       |< PUBLISH_NAMESPACE B -|
    |<---- NAMESPACE B -----|                       |
    |                       |                       * wait 1000 ms
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Each of the 4 peers receives NAMESPACE for each of the other 3.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-31-room-fanout-tracks">
        <name>Room Fan-out of Tracks</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Six peers join a room with the full sequence a conferencing client
uses: SUBSCRIBE_NAMESPACE on the room prefix, PUBLISH of four Tracks,
then PUBLISH_NAMESPACE of the peer's own namespace. On each NAMESPACE
for another peer, a peer sends SUBSCRIBE_TRACKS for that peer's
namespace and must then receive a PUBLISH for each of its Tracks. The
diagram shows one pair; the test covers every ordered pair of the 6
peers.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>6 peers, room prefix <tt>moq-web-e2e/chat-stream/room-&lt;id&gt;</tt></t>
              </li>
              <li>
                <t>Tracks per peer: timeline, catalog, video, audio</t>
              </li>
              <li>
                <t>300 ms between joins; 1200 ms to settle at the end</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
  peerA                   Relay                   peerB
    |                       |                       |
    |- SUBSCRIBE_NAMESPACE >|                       |
    |                       |< SUBSCRIBE_NAMESPACE -|
    |----- PUBLISH x4 ----->|                       |
    |- PUBLISH_NAMESPACE A >|                       |
    |                       |----- NAMESPACE A ---->|
    |                       |< SUBSCRIBE_TRACKS A --|
    |                       |--- PUBLISH x4 (A) --->|
    |                       |<--- REQUEST_OK x4 ----|
    * wait 300 ms           |                       |
    |                       |<---- PUBLISH x4 ------|
    |                       |< PUBLISH_NAMESPACE B -|
    |<---- NAMESPACE B -----|                       |
    |- SUBSCRIBE_TRACKS B ->|                       |
    |<-- PUBLISH x4 (B) ----|                       |
    |---- REQUEST_OK x4 --->|                       |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Each peer receives NAMESPACE for each of the other 5 peers.</t>
              </li>
              <li>
                <t>Each peer receives a PUBLISH for all 4 Tracks of each of the other 5
peers.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-32-room-fanout-catalog">
        <name>Room Fan-out of Catalogs</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Four peers join a room as in <xref target="t-31-room-fanout-tracks"/>, and each
also publishes a catalog Track. Other peers subscribe to the catalog
Track only later, through the PUBLISH the relay forwards after their
SUBSCRIBE_TRACKS. A subscription starts at the next Object, and a
relay need not hand out the latest Object it holds, so each peer
re-sends its catalog as a new Group every 500 ms; a peer that
subscribes later gets one of the re-sends. The diagram shows one pair; the test covers
every ordered pair of the 4 peers.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>4 peers, room prefix <tt>moq-web-e2e/chat-stream/room-&lt;id&gt;</tt></t>
              </li>
              <li>
                <t>Tracks per peer: timeline, video (stream), audio (datagram),
catalog</t>
              </li>
              <li>
                <t>Catalog listing video and audio, re-sent as a new Group every
500 ms</t>
              </li>
              <li>
                <t>400 ms between joins; up to 10 s for every catalog to arrive</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
  peerA                   Relay                   peerB
    |                       |                       |
    |- SUBSCRIBE_NAMESPACE >|                       |
    |                       |< SUBSCRIBE_NAMESPACE -|
    |----- PUBLISH x4 ----->|                       |
    * incl. catalog Track   |                       |
    |=== catalog Object ===>|                       |
    * re-sent every 500 ms  |                       |
    |- PUBLISH_NAMESPACE A >|                       |
    |                       |----- NAMESPACE A ---->|
    |                       |< SUBSCRIBE_TRACKS A --|
    |                       |--- PUBLISH x4 (A) --->|
    |                       |<--- REQUEST_OK x4 ----|
    |                       |=== catalog Object ===>|
    |                       |                       * wait up to 10 s
    |                     catalog lists video+audio *
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Each of the 4 peers receives, from each of the other 3, a catalog
that parses and lists Tracks named video and audio.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-33-publish-done">
        <name>PUBLISH_DONE Keeps the Session</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Ending a published Track sends PUBLISH_DONE as the last message on the
PUBLISH request stream, which then closes. Sent there, it must not end
the session: a second PUBLISH on the same session must still succeed.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>chat</tt>, no subscriber, 3 Objects (one per Group)</t>
              </li>
              <li>
                <t>Second Track <tt>chat-2</tt> in the same namespace</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                          Relay
    |                             |
    |------- PUBLISH chat ------->|
    |<------- REQUEST_OK ---------|
    |========= 3 Objects ========>|
    |----- PUBLISH_DONE, FIN ---->|
    |------ PUBLISH chat-2 ------>|
    |<------- REQUEST_OK ---------|
    * Track Alias assigned        |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The second PUBLISH succeeds and gets a Track Alias, so the session
is still open.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-34-draft23">
        <name>Draft-23 Wire Changes</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-23</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Checks what draft-23 changed on the wire: setup over the draft-23
control framing, FETCH answered by REQUEST_OK with the draft-23 Object
ID rules on the fetch stream, REQUEST_ERROR with Error Details that
leaves the session usable, and a grease Error Detail that the relay
ignores.</t>
          </dd>
        </dl>
        <section anchor="t-34a">
          <name>Setup over Draft-23 Framing</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>WebTransport protocol offered: moqt-23</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |------- CLIENT_SETUP ------->|
    |<------ SERVER_SETUP --------|
    * draft-23 negotiated         |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The negotiated version is draft-23 and the session is ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-34b">
          <name>FETCH Answered by REQUEST_OK</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>chat</tt>, max cache duration 60 s, no subscriber</t>
                </li>
                <li>
                  <t>Groups 0 to 2, Object IDs 0 to 9 with 1, 4 and 7 skipped: 21 Objects,
so Object ID Deltas on the fetch stream are non-zero</t>
                </li>
                <li>
                  <t>FETCH range 0/0 to 2/9</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |---- PUBLISH chat ---->|                       |
    |===== 21 Objects =====>|                       |
    * wait 500 ms           |                       |
    |                       |<-- FETCH 0/0..2/9 ----|
    |                       |----- REQUEST_OK ----->|
    |                       |==== fetch stream ====>|
    |                       |IDs match, bytes match *
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The FETCH is answered by REQUEST_OK, not FETCH_OK.</t>
                </li>
                <li>
                  <t>Exactly the 21 published Objects arrive, at their Group and Object
IDs, in order and byte for byte, followed by the end of the fetch.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
                <li>
                  <t>Tolerated: the relay refuses the FETCH; then only the last check
applies.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-34c">
          <name>Refused SUBSCRIBE</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>nothing-here</tt> in a namespace nobody publishes</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<----- SUBSCRIBE ------|
    |                       |---- REQUEST_ERROR --->|
    |                       |       waits up to 8 s *
    |                       |<- PUBLISH_NAMESPACE --|
    |                       |----- REQUEST_OK ----->|
    |                       |                       * still ready
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The REQUEST_ERROR decodes, with a numeric error code.</t>
                </li>
                <li>
                  <t>The session stays ready and serves the next request.</t>
                </li>
                <li>
                  <t>Tolerated: the relay accepts or holds the SUBSCRIBE open; this is
reported, not failed.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-34d">
          <name>Grease Error Detail Ignored</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Publisher announces the namespace but publishes no Track</t>
                </li>
                <li>
                  <t>The publisher adds a grease Error Detail to every REQUEST_ERROR</t>
                </li>
                <li>
                  <t>FETCH range 0/0 to 1/0 for Track <tt>no-objects</tt></t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH_NAMESPACE ->|                       |
    |                       |<- FETCH no-objects ---|
    |<- FETCH no-objects ---|                       |
    |---- REQUEST_ERROR --->|                       |
    * grease Error Detail   |                       |
    |                       |---- REQUEST_ERROR --->|
    |                       |                       * wait up to 8 s
    * neither session closed|                       |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Neither the publisher's nor the subscriber's session is closed.</t>
                </li>
                <li>
                  <t>Whether the relay forwards the FETCH to the publisher is not
checked.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-35-publish-forwarding">
        <name>PUBLISH Forwarding to Namespace Subscribers</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-18 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>SUBSCRIBE_NAMESPACE asks the relay for NAMESPACE messages only;
SUBSCRIBE_TRACKS asks for a PUBLISH for every existing and future
Track under a prefix. Five cases combine the two requests with the
order of PUBLISH and subscription. In each case the publisher sends an
Object every 100 ms and the subscriber is watched for 5 s. A plain
SUBSCRIBE from a third session (Ctl), sent after the 5 s watch with
filter Largest Object, checks that the publisher is reachable; if it
gets no Objects, the case fails as inconclusive (publisher not
reachable) rather than as a forwarding failure.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Prefix <tt>moq-web-e2e/chat-stream/e2e-fwd/&lt;id&gt;</tt>, Track <tt>&lt;prefix&gt;/pub/t</tt></t>
              </li>
              <li>
                <t>One Object every 100 ms, a new Group each</t>
              </li>
              <li>
                <t>Case 1: SUBSCRIBE_NAMESPACE, then PUBLISH</t>
              </li>
              <li>
                <t>Case 2: PUBLISH, then SUBSCRIBE_NAMESPACE (500 ms later)</t>
              </li>
              <li>
                <t>Case 3: SUBSCRIBE_NAMESPACE, then PUBLISH and PUBLISH_NAMESPACE of
<tt>&lt;prefix&gt;/pub</tt></t>
              </li>
              <li>
                <t>Case 4: SUBSCRIBE_TRACKS, then PUBLISH</t>
              </li>
              <li>
                <t>Case 5: PUBLISH, then SUBSCRIBE_TRACKS (500 ms later)</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <t>Case 4, subscription first. Case 5 sends the same messages with
  PUBLISH and the Objects first; the relay then sends the PUBLISH to Sub
  in answer to SUBSCRIBE_TRACKS.</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<- SUBSCRIBE_TRACKS ---|
    |                       |----- REQUEST_OK ----->|
    |                       |                       * wait 200 ms
    |---- PUBLISH pub/t --->|                       |
    |<---- REQUEST_OK ------|                       |
    |=== Object / 100 ms ==>|                       |
    |                       |---- PUBLISH pub/t --->|
    |                       |<---- REQUEST_OK ------|
    |                       |======= Objects ======>|
    |                       |    Objects within 2 s *
]]></artwork>
        <t>Case 3, namespace subscription. Cases 1 and 2 omit PUBLISH_NAMESPACE,
and NAMESPACE is not checked in them; a forwarded PUBLISH is reported
but not required in cases 1 to 3.</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |< SUBSCRIBE_NAMESPACE -|
    |                       |----- REQUEST_OK ----->|
    |---- PUBLISH pub/t --->|                       |
    |-- PUBLISH_NAMESPACE ->|                       |
    * namespace pfx/pub     |                       |
    |=== Object / 100 ms ==>|                       |
    |                       |---- NAMESPACE pub --->|
    |                       |                       * watch 5 s
]]></artwork>
        <t>The control, in every case:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Ctl
    |                       |                       |
    |                       |                       * after 5 s watch
    |                       |<-- SUBSCRIBE pub/t ---|
    |                       |   Largest Object      |
    |                       |--- SUBSCRIBE_OK ----->|
    |                       |======= Objects ======>|
    |                       |    Objects within 2 s *
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The control SUBSCRIBE receives Objects within 2 s; otherwise the
case fails as inconclusive (publisher not reachable).</t>
              </li>
              <li>
                <t>Cases 4 and 5: Sub receives a PUBLISH for the Track, and its Objects
follow within 2 s of it.</t>
              </li>
              <li>
                <t>Case 3: Sub receives NAMESPACE for the suffix <tt>pub</tt>.</t>
              </li>
              <li>
                <t>No request errors or stream resets from the relay.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-36-request-errors">
        <name>Requests the Relay Cannot Serve</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Requests that a relay cannot serve must be refused with REQUEST_ERROR
and the error code the draft names, within 5 s rather than left
unanswered, and the session must stay usable. Three cases ask for a
Track nobody publishes; two send a FETCH whose range the relay cannot
satisfy (<xref section="3.2" sectionFormat="of" target="MoQTransport"/>).</t>
          </dd>
        </dl>
        <section anchor="t-36a">
          <name>SUBSCRIBE for an Unknown Track</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>nobody</tt>, never published</t>
                </li>
                <li>
                  <t>Rendezvous timeout 1 s</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |----- SUBSCRIBE nobody ----->|
    |<------ REQUEST_ERROR -------|
    * within 5 s; still ready     |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_ERROR arrives within 5 s with code DOES_NOT_EXIST or TIMEOUT.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-36b">
          <name>FETCH for an Unknown Track</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>nobody</tt>, never published</t>
                </li>
                <li>
                  <t>FETCH range 0/0 to 1/0</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |------- FETCH nobody ------->|
    |<------ REQUEST_ERROR -------|
    * within 5 s; still ready     |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_ERROR arrives within 5 s with code DOES_NOT_EXIST.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-36c">
          <name>TRACK_STATUS for an Unknown Track</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>nobody</tt>, never published</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
 Client                         Relay
    |                             |
    |---- TRACK_STATUS nobody --->|
    |<------ REQUEST_ERROR -------|
    * within 5 s; still ready     |
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_ERROR arrives within 5 s with code DOES_NOT_EXIST.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-36d">
          <name>FETCH Starting after the Largest Object</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>t</tt>, max cache duration 60 s</t>
                </li>
                <li>
                  <t>Groups 0 to 2, 3 Objects each</t>
                </li>
                <li>
                  <t>FETCH range 10/0 to 11/0</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH t ----->|                       |
    |                       |<---- SUBSCRIBE t -----|
    |                       |   Largest Object      |
    |                       |--- SUBSCRIBE_OK ----->|
    |                       |                       * wait 200 ms
    |====== 9 Objects =====>|                       |
    |                       |====== 9 Objects =====>|
    |                       |                       * wait 300 ms
    |                       |<- FETCH 10/0..11/0 ---|
    |                       |---- REQUEST_ERROR --->|
    |                       |                       * INVALID_RANGE
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_ERROR arrives within 5 s with code INVALID_RANGE.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-36e">
          <name>FETCH for a Track with No Objects</name>
          <dl>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>t</tt>, max cache duration 60 s</t>
                </li>
                <li>
                  <t>No Objects published</t>
                </li>
                <li>
                  <t>FETCH range 0/0 to 1/0</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |------ PUBLISH t ----->|                       |
    |                       |<---- SUBSCRIBE t -----|
    |                       |   Largest Object      |
    |                       |--- SUBSCRIBE_OK ----->|
    |                       |                       * wait 200 ms
    * sends nothing         |                       |
    |                       |                       * wait 300 ms
    |                       |<-- FETCH 0/0..1/0 ----|
    |                       |---- REQUEST_ERROR --->|
    |                       |                       * INVALID_RANGE
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>REQUEST_ERROR arrives within 5 s with code INVALID_RANGE.</t>
                </li>
                <li>
                  <t>The session stays ready.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-37-subscribe-ok-largest">
        <name>Largest Location in SUBSCRIBE_OK</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>SUBSCRIBE_OK reports the Track's Largest Location. A subscriber that
arrives before any Object is published must see none; a second
subscriber, arriving after Groups 0 to 2 of 3 Objects each, must see
2/2, the last Object sent.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>t</tt>, max cache duration 60 s</t>
              </li>
              <li>
                <t>Groups 0 to 2, 3 Objects each</t>
              </li>
              <li>
                <t>Two subscriber sessions, Early and Late, both filter Largest Object</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                Relay               Early               Late
    |                   |                   |                   |
    |---- PUBLISH t --->|                   |                   |
    |                   |<-- SUBSCRIBE t ---|                   |
    |                   |-- SUBSCRIBE_OK -->|                   |
    |                   |                   * no Largest        |
    |==== 9 Objects ===>|                   |                   |
    * wait 500 ms       |                   |                   |
    |                   |<------------ SUBSCRIBE t -------------|
    |                   |------------ SUBSCRIBE_OK ------------>|
    |                   |                   |       Largest 2/2 *
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The first SUBSCRIBE_OK carries no Largest Location.</t>
              </li>
              <li>
                <t>The second carries Largest Location 2/2 and indicates content
exists.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-38-publish-namespace-lifecycle">
        <name>PUBLISH_NAMESPACE Lifecycle</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A publisher announces a namespace, withdraws it, and announces it
again. A subscriber with SUBSCRIBE_NAMESPACE on the parent prefix must
see NAMESPACE, then NAMESPACE_DONE, then NAMESPACE again. The
publisher withdraws by cancelling its PUBLISH_NAMESPACE request.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Prefix <tt>moq-web-e2e/chat-stream/pubns-life/&lt;id&gt;</tt></t>
              </li>
              <li>
                <t>Namespace <tt>&lt;prefix&gt;/pub</tt></t>
              </li>
              <li>
                <t>Each NAMESPACE or NAMESPACE_DONE awaited for up to 5 s</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |< SUBSCRIBE_NAMESPACE -|
    |                       |----- REQUEST_OK ----->|
    |-- PUBLISH_NAMESPACE ->|                       |
    |                       |---- NAMESPACE pub --->|
    |--- cancel request --->|                       |
    |                       |- NAMESPACE_DONE pub ->|
    |-- PUBLISH_NAMESPACE ->|                       |
    |                       |---- NAMESPACE pub --->|
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Sub sees, for <tt>pub</tt> and in this order: NAMESPACE, NAMESPACE_DONE,
NAMESPACE.</t>
              </li>
              <li>
                <t>No request errors or stream resets from the relay.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-39-namespace-prefix-update">
        <name>Namespace Prefix Update</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber moves an existing SUBSCRIBE_NAMESPACE from one prefix to
another with REQUEST_UPDATE carrying TRACK_NAMESPACE_PREFIX (draft-22
Section 9.20.20). The relay must answer the update, stop matching the
old prefix and start matching the new one.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Old prefix: <tt>&lt;ns&gt;/a</tt>; new prefix: <tt>&lt;ns&gt;/b</tt>.</t>
              </li>
              <li>
                <t>Namespaces announced after the update: <tt>&lt;ns&gt;/a/late</tt>, <tt>&lt;ns&gt;/b/late</tt>.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<-- SUBSCRIBE_NAMESPACE|
    |                       |        <ns>/a         |
    |                       |-- REQUEST_OK -------->|
    |                       |                       * wait 300 ms
    |                       |<-- REQUEST_UPDATE ----|
    |                       |  TRACK_NAMESPACE_     |
    |                       |  PREFIX = <ns>/b      |
    |                       |------ REQUEST_OK ---->|
    |-- PUBLISH_NAMESPACE ->|                       |
    |     <ns>/a/late       |                       |
    |-- PUBLISH_NAMESPACE ->|                       |
    |     <ns>/b/late       |                       |
    |                       |-- NAMESPACE --------->|
    |                       |     <ns>/b/late       |
    |                       |                       * wait 500 ms
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>REQUEST_OK arrives within 5 s.</t>
              </li>
              <li>
                <t>NAMESPACE <tt>&lt;ns&gt;/b/late</tt> arrives within 5 s.</t>
              </li>
              <li>
                <t>NAMESPACE <tt>&lt;ns&gt;/a/late</tt> does not arrive.</t>
              </li>
              <li>
                <t>No unexpected error or session close occurs.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-40-stream-credit">
        <name>Stream-Credit Flow Control</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
        </dl>
        <t>Since MAX_REQUEST_ID was removed, each request holds a bidirectional
stream and each subgroup a unidirectional one, so the limits are the
QUIC stream credits the peer grants.</t>
        <section anchor="t-40a-open-requests">
          <name>Requests over the Open-Stream Limit</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>One session sends far more SUBSCRIBEs than a typical stream limit at
once. Those over the relay's limit must fail quickly and leave the
session usable; once some subscriptions end, credit must come back so
new requests succeed.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>170 tracks, published by several Pub sessions, 50 tracks each,
each Pub under its own namespace.</t>
                </li>
                <li>
                  <t>150 SUBSCRIBEs sent at once; 20 freed, then 20 new SUBSCRIBEs.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pubs                   Relay                    Sub
    |                       |                       |
    |-- PUBLISH x170 ------>|                       |
    |                       |<-- SUBSCRIBE x150 ----|
    |                       |   (one bidi stream    |
    |                       |    each, at once)     |
    |                       |-- SUBSCRIBE_OK or --->|
    |                       |   REQUEST_ERROR or    |
    |                       |   stream refused      |
    |                       |                       * <= 20 s
    |                       |<- cancel SUBSCRIBE x20|
    |                       |                       * wait 1 s
    |                       |<-- SUBSCRIBE x20 -----|
    |                       |   (new tracks)        |
    |                       |-- SUBSCRIBE_OK x20 -->|
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>All 170 PUBLISHes succeed; otherwise the burst cannot run.</t>
                </li>
                <li>
                  <t>Every one of the 150 SUBSCRIBEs is answered or fails within 20 s.</t>
                </li>
                <li>
                  <t>The session is still ready after the burst.</t>
                </li>
                <li>
                  <t>All 20 new SUBSCRIBEs succeed, each within 10 s.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-40b-short-streams">
          <name>Short-Lived Streams</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A publisher sends many single-Object groups back to back, each on its
own unidirectional stream, exceeding a typical initial limit of 100
streams. Delivery succeeds only if both sides keep granting
unidirectional stream credit.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery.</t>
                </li>
                <li>
                  <t>150 groups of one Object each.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |                       * wait 300 ms
    |== g0..g149, one =====>|== g0..g149, one =====>|
    |   stream per group    |   stream per group    |
    |                       |                       * wait <= 20 s
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>No send fails at the publisher.</t>
                </li>
                <li>
                  <t>All 150 groups arrive within 20 s.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-41-unknown-parameter">
        <name>Unknown Message Parameter</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Message Parameters are not greased; an endpoint that receives an
undefined one must close the session, with INVALID_PARAMETER in
draft-23 (<xref section="9.19" sectionFormat="of" target="MoQTransport"/>) and PROTOCOL_VIOLATION
before. The client sends a TRACK_STATUS carrying one parameter of
undefined type 0x3C.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>TRACK_STATUS for <tt>&lt;ns&gt;/t</tt>.</t>
              </li>
              <li>
                <t>Extra Message Parameter 0x3C = 1, undefined in every draft.</t>
              </li>
              <li>
                <t>The client first checks that its own decoder rejects the message
for that parameter only.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
  Client                  Relay
    |                       |
    |-- CLIENT_SETUP ------>|
    |<-- SERVER_SETUP ------|
    * encode TRACK_STATUS   |
    * + parameter 0x3C = 1  |
    |-- TRACK_STATUS ------>|  (new bidi request stream)
    |   param 0x3C          |
    |<-- CONNECTION CLOSE --|
    |  INVALID_PARAMETER    |
    |  (0x305, draft-23) or |
    |  PROTOCOL_VIOLATION   |
    |  (0x3, draft-22)      |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>The relay closes the session within 5 s.</t>
              </li>
              <li>
                <t>The close code is INVALID_PARAMETER (0x305) on draft-23, or
PROTOCOL_VIOLATION (0x3) on draft-22.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-42-fill">
        <name>Fill with SUBSCRIBE</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
        </dl>
        <t>FILL_PARAMETERS (<xref section="3.4" sectionFormat="of" target="MoQTransport22"/>) has the relay open a fill stream
with past groups next to the live subscription. In both tests a holder
session subscribes first, so the relay keeps groups 0..4 cached.</t>
        <section anchor="t-42a-fill-subscribe">
          <name>Fill on SUBSCRIBE</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A subscriber joining mid-track asks for the last 3 groups as fill. It
must get those groups from the cache and the following groups live,
and nothing older.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery, MAX_CACHE_DURATION 60 s.</t>
                </li>
                <li>
                  <t>Cached: groups 0..4, 3 Objects each.</t>
                </li>
                <li>
                  <t>Fill: last 3 groups. Published afterwards: groups 5..6.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay              Holder / Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE (Holder)-|
    |== g0..g4, 3 obj =====>|== g0..g4 ============>| Holder
    |                       |                       * wait 500 ms
    |                       |<-- SUBSCRIBE (Sub) ---|
    |                       |   Largest Object,     |
    |                       |   FILL last 3 groups  |
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |== fill: g2..g4 ======>| Sub
    |== g5..g6 ============>|== g5..g6 live =======>| Sub
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Every Object of groups 2..6 arrives at Sub, byte for byte.</t>
                </li>
                <li>
                  <t>No Object of groups 0..1 arrives at Sub.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-42b-fill-update">
          <name>Fill on REQUEST_UPDATE</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>A subscriber that joined without fill later asks for groups 1..2 with
REQUEST_UPDATE. Exactly those groups must arrive on the fill stream.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery, MAX_CACHE_DURATION 60 s.</t>
                </li>
                <li>
                  <t>Cached: groups 0..4, 3 Objects each.</t>
                </li>
                <li>
                  <t>Fill: start group 1, end group 2.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay              Holder / Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE (Holder)-|
    |== g0..g4, 3 obj =====>|== g0..g4 ============>| Holder
    |                       |                       * wait 500 ms
    |                       |<-- SUBSCRIBE (Sub) ---|
    |                       |   Largest Object      |
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |<-- REQUEST_UPDATE ----|
    |                       |   FILL groups 1..2    |
    |                       |------ REQUEST_OK ---->|
    |                       |== fill: g1..g2 ======>| Sub
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>The REQUEST_UPDATE is answered.</t>
                </li>
                <li>
                  <t>Every Object of groups 1 and 2 arrives at Sub.</t>
                </li>
                <li>
                  <t>No other Object arrives on the fill.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-43-fetch-cache">
        <name>FETCH from the Relay Cache</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A holder subscription keeps groups 0..2 in the relay's cache, then a
second session fetches them in five shapes. Every Object is checked
byte for byte. MOQT sets no cache size, so the test caches only 3
groups, which the smallest relay cache seen keeps per track. A FETCH
end location is inclusive (<xref section="9.11" sectionFormat="of" target="MoQTransport22"/>), and a
FETCH ends at the Largest Object, so Objects published after it are
not part of the response (<xref section="3.2" sectionFormat="of" target="MoQTransport"/>).</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery, MAX_CACHE_DURATION 60 s.</t>
              </li>
              <li>
                <t>Cached: groups 0..2, 3 Objects each (Object IDs 0..2).</t>
              </li>
              <li>
                <t>The five cases in the table below.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <table>
          <name>FETCH cases</name>
          <thead>
            <tr>
              <th align="left">Case</th>
              <th align="left">FETCH range</th>
              <th align="left">Variation</th>
              <th align="left">Expected Objects</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">whole</td>
              <td align="left">1/0..2/0</td>
              <td align="left">none</td>
              <td align="left">1/0..2/2 (6)</td>
            </tr>
            <tr>
              <td align="left">partial</td>
              <td align="left">0/1..1/1</td>
              <td align="left">none</td>
              <td align="left">0/1..1/1 (4)</td>
            </tr>
            <tr>
              <td align="left">descending</td>
              <td align="left">0/0..1/0</td>
              <td align="left">group order descending</td>
              <td align="left">0/0..1/2 (6), groups 1, 0</td>
            </tr>
            <tr>
              <td align="left">cache-only</td>
              <td align="left">0/0..2/0</td>
              <td align="left">Pub closes its session first</td>
              <td align="left">0/0..2/2 (9), or DOES_NOT_EXIST</td>
            </tr>
            <tr>
              <td align="left">live-edge</td>
              <td align="left">1/0..4/0</td>
              <td align="left">Pub sends groups 3..4 after the FETCH</td>
              <td align="left">1/0..2/2 (6)</td>
            </tr>
          </tbody>
        </table>
        <t>The descending range stops short of the Largest Object, so it is a
range below the live edge in every relay.</t>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay              Holder / Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE (Holder)-|
    |== g0..g2, 3 obj =====>|== g0..g2 ============>| Holder
    |                       |                       * wait 500 ms
    * [cache-only] close    |                       |
    |                       |<-- FETCH (Sub) -------|
    |                       |   range of the case   |
    * [live-edge] g3..g4    |                       |
    |== g3..g4 ============>|                       |
    |                       |-- FETCH_OK ---------->|
    |                       |== fetch stream ======>| Sub
    |                       |   Objects in range    |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>No FETCH error, except that cache-only may instead get
REQUEST_ERROR DOES_NOT_EXIST with no Objects.</t>
              </li>
              <li>
                <t>Every expected Object in the table arrives, byte for byte.</t>
              </li>
              <li>
                <t>No Object outside the range arrives; in live-edge, none of groups
3..4.</t>
              </li>
              <li>
                <t>In descending, groups arrive in descending order.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-44-new-group-request">
        <name>NEW_GROUP_REQUEST</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber asks the publisher to start a new group. The publisher
declares DYNAMIC_GROUPS, the relay must pass the NEW_GROUP_REQUEST to
it, and the new group must reach the subscriber.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery, DYNAMIC_GROUPS = 1.</t>
              </li>
              <li>
                <t>Pub sends one Object every 100 ms in group 0 until it gets the
request, then moves to group 1.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |   DYNAMIC_GROUPS=1    |                       |
    |== g0/o0, o1.. =======>|                       |
    |   every 100 ms        |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |   DYNAMIC_GROUPS      |
    |                       |== g0 objects ========>|
    |                       |                       * 3 Objects in
    |                       |<-- REQUEST_UPDATE ----|
    |                       |   NEW_GROUP_REQUEST   |
    |                       |------ REQUEST_OK ---->|
    |<-- REQUEST_UPDATE ----|                       |
    |   NEW_GROUP_REQUEST   |                       |
    * start group 1         |                       |
    |== g1/o0.. ===========>|== g1/o0.. ===========>|
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>SUBSCRIBE_OK carries DYNAMIC_GROUPS.</t>
              </li>
              <li>
                <t>The REQUEST_UPDATE is answered.</t>
              </li>
              <li>
                <t>A REQUEST_UPDATE carrying NEW_GROUP_REQUEST reaches Pub.</t>
              </li>
              <li>
                <t>A group 1 Object reaches Sub within 3 s of the request.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-45-namespace-discovery">
        <name>Namespace Discovery Flow</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>The complete discover-then-subscribe flow. A subscriber learns a
namespace through SUBSCRIBE_NAMESPACE, subscribes to a track in it by
name, and later sees the track and the namespace end. A late
subscriber must learn the existing namespace, and a sibling namespace
whose last field only starts with the prefix's must not match, since
namespaces match field by field.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Prefix <tt>&lt;p&gt;</tt>; namespace <tt>&lt;p&gt;/pub</tt>; track <tt>t</tt>.</t>
              </li>
              <li>
                <t>Sibling namespace <tt>&lt;p&gt;x/pub</tt>.</t>
              </li>
              <li>
                <t>Pub sends one Object every 100 ms.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay              Sub / Late
    |                       |                       |
    |                       |<-- SUBSCRIBE_NAMESPACE|
    |                       |      <p> (Sub)        |
    |-- PUBLISH_NAMESPACE ->|                       |
    |     <p>/pub           |                       |
    |-- PUBLISH_NAMESPACE ->|                       |
    |     <p>x/pub          |                       |
    |-- PUBLISH <p>/pub/t ->|                       |
    |== Objects ===========>|-- NAMESPACE <p>/pub ->| Sub
    |                       |<-- SUBSCRIBE t -------| Sub
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |== Objects ===========>| Sub
    |                       |<-- SUBSCRIBE_NAMESPACE|
    |                       |      <p> (Late)       |
    |                       |-- NAMESPACE <p>/pub ->| Late
    * stop, end track t     |                       |
    |-- PUBLISH_DONE ------>|-- PUBLISH_DONE ------>| Sub
    * cancel announcement   |                       |
    |-- (cancel PUBLISH_    |-- NAMESPACE_DONE ---->| Sub
    |    NAMESPACE) ------->|-- NAMESPACE_DONE ---->| Late
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Each step completes in order: NAMESPACE to Sub within 5 s, at
least 3 Objects on the SUBSCRIBE within 3 s, then within 5 s each
NAMESPACE to Late, PUBLISH_DONE to Sub, and
NAMESPACE_DONE to both Sub and Late.</t>
              </li>
              <li>
                <t>Neither Sub nor Late receives NAMESPACE for <tt>&lt;p&gt;x/pub</tt>.</t>
              </li>
              <li>
                <t>No unexpected error or session close occurs.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-46-subscribe-tracks">
        <name>SUBSCRIBE_TRACKS Flow</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>A subscriber asks for every track under a prefix with
SUBSCRIBE_TRACKS. The relay must send a PUBLISH for each matching
track, forward its Objects and PUBLISH_DONE, and stop after the
request is cancelled. The publisher also sends SUBSCRIBE_TRACKS for
the same prefix and must not get its own tracks back, since the
request excludes "tracks published by the subscriber" (<xref section="3.6" sectionFormat="of" target="MoQTransport"/>).</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Prefix <tt>&lt;p&gt;</tt>; namespace <tt>&lt;p&gt;/pub</tt>.</t>
              </li>
              <li>
                <t>Tracks a, b, c; track d is published after the cancel.</t>
              </li>
              <li>
                <t>One Object per track every 100 ms.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<-- SUBSCRIBE_TRACKS --|
    |                       |      <p>              |
    |-- SUBSCRIBE_TRACKS -->|                       |
    |      <p>              |                       |
    |-- PUBLISH a, b, c --->|                       |
    |== Objects ===========>|-- PUBLISH a, b, c --->|
    |                       |== Objects a, b, c ===>|
    |   (no PUBLISH a..d    |                       |
    |    back to Pub)       |                       |
    * end track a           |                       |
    |-- PUBLISH_DONE a ---->|-- PUBLISH_DONE a ---->|
    |                       |<-- cancel SUBSCRIBE_  |
    |                       |    TRACKS ------------|
    |-- PUBLISH d --------->|                       |
    |                       |   (no PUBLISH d)      |
    |                       |                       * wait 2 s
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Sub receives a PUBLISH and Objects for each of a, b and c.</t>
              </li>
              <li>
                <t>Sub receives PUBLISH_DONE for a.</t>
              </li>
              <li>
                <t>Sub receives no PUBLISH for d after the cancel.</t>
              </li>
              <li>
                <t>Pub receives no PUBLISH for any of its own tracks.</t>
              </li>
              <li>
                <t>No unexpected error or session close occurs.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-47-goaway">
        <name>GOAWAY Flows</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
        </dl>
        <t>GOAWAY does not affect subscription state (<xref section="9.2" sectionFormat="of" target="MoQTransport"/>): delivery continues until the sender ends its requests
and closes. A client cannot make the relay send GOAWAY, so both tests
send it from a client in the middle of delivery.</t>
        <section anchor="t-47a-goaway-sub">
          <name>Subscriber Sends GOAWAY</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The subscriber sends GOAWAY while Objects are flowing. Delivery must
continue, and the subscriber then unsubscribes and closes cleanly.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>&lt;ns&gt;/t</tt>; Pub sends one Object, in a new group, every 100 ms.</t>
                </li>
                <li>
                  <t>Drain period: 2 s.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |== 1 obj / 100 ms ====>|== Objects ===========>|
    |                       |                       * 3 Objects in
    |                       |<-- GOAWAY ------------|
    |== Objects ===========>|== Objects ===========>|
    |                       |                       * 2 s
    |                       |<-- cancel SUBSCRIBE --|
    |                       |<-- session close -----|
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>At least 10 Objects arrive in the 2 s after GOAWAY.</t>
                </li>
                <li>
                  <t>No unexpected error or close code is seen.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
        <section anchor="t-47b-goaway-pub">
          <name>Publisher Sends GOAWAY</name>
          <dl>
            <dt>Description:</dt>
            <dd>
              <t>The publisher sends GOAWAY while Objects are flowing. The subscriber
must keep receiving, then get PUBLISH_DONE when the publisher ends the
track, with its own session unaffected.</t>
            </dd>
            <dt>Inputs:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>Track <tt>&lt;ns&gt;/t</tt>; Pub sends one Object, in a new group, every 100 ms.</t>
                </li>
                <li>
                  <t>Drain period: 2 s.</t>
                </li>
              </ul>
            </dd>
          </dl>
          <t>Call Flow:</t>
          <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |== 1 obj / 100 ms ====>|== Objects ===========>|
    |                       |                       * 3 Objects in
    |-- GOAWAY ------------>|                       |
    |== Objects ===========>|== Objects ===========>|
    * 2 s, stop, end track  |                       |
    |-- PUBLISH_DONE ------>|-- PUBLISH_DONE ------>|
]]></artwork>
          <dl>
            <dt>Expected Outcome:</dt>
            <dd>
              <ul spacing="normal">
                <li>
                  <t>At least 10 Objects arrive at Sub in the 2 s after GOAWAY.</t>
                </li>
                <li>
                  <t>PUBLISH_DONE arrives within 5 s of the track ending.</t>
                </li>
                <li>
                  <t>Sub's session is still ready.</t>
                </li>
                <li>
                  <t>No unexpected error or close code is seen.</t>
                </li>
              </ul>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="t-48-track-properties">
        <name>Track Properties</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Track Properties sent in the publisher's PUBLISH must reach
subscribers unchanged, both in SUBSCRIBE_OK and in the answer to
TRACK_STATUS (<xref section="3.7" sectionFormat="of" target="MoQTransport22"/>).</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>&lt;ns&gt;/t</tt>.</t>
              </li>
              <li>
                <t>Track Properties: subgroup delivery timeout 4000 ms, max cache
duration 30000 ms, default publisher priority 64, default publisher
group order descending, DYNAMIC_GROUPS.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |   Track Properties    |                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |   Track Properties    |
    |== 1 Object ==========>|== 1 Object ==========>|
    |                       |<-- TRACK_STATUS ------|
    |                       |-- REQUEST_OK -------->|
    |                       |   Track Properties    |
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>SUBSCRIBE_OK carries all five Track Properties with the values the
PUBLISH sent.</t>
              </li>
              <li>
                <t>The TRACK_STATUS answer carries the same five values.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-49-object-properties">
        <name>Object Properties</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>Every Object carries two Object Properties of types the relay does
not know, one even (varint) and one odd (bytes). Both are below the
Mandatory range, so the relay must forward them unchanged (draft-22
Section 11.1).</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>&lt;ns&gt;/t</tt>, stream delivery.</t>
              </li>
              <li>
                <t>3 groups of 4 Objects.</t>
              </li>
              <li>
                <t>Property 0x40 = group x 100 + object (varint).</t>
              </li>
              <li>
                <t>Property 0x41 = <tt>p&lt;G&gt;/&lt;O&gt;</tt> (bytes).</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |                       * wait 200 ms
    |== g0..g2, o0..o3 ====>|== g0..g2, o0..o3 ====>|
    |   props 0x40, 0x41    |   props unchanged     |
    |                       |                       * wait <= 5 s
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>All 12 Objects arrive.</t>
              </li>
              <li>
                <t>Each carries 0x40 = group x 100 + object and 0x41 =
<tt>p&lt;G&gt;/&lt;O&gt;</tt>.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
      <section anchor="t-50-setup-options">
        <name>Setup Options and Concurrent REQUEST_UPDATEs</name>
        <dl>
          <dt>Applicability:</dt>
          <dd>
            <t>draft-22 and later</t>
          </dd>
          <dt>Description:</dt>
          <dd>
            <t>The Setup Options in the relay's SERVER_SETUP must be well formed,
and the relay must honour MAX_REQUEST_UPDATES (<xref section="9.1.7" sectionFormat="of" target="MoQTransport22"/>): the subscriber sends that many REQUEST_UPDATEs at once on one
subscription, and each must be answered in order.</t>
          </dd>
          <dt>Inputs:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Track <tt>&lt;ns&gt;/t</tt>.</t>
              </li>
              <li>
                <t>Updates sent at once: the relay's MAX_REQUEST_UPDATES, capped at 4;
4 if the relay sets no limit.</t>
              </li>
              <li>
                <t>The updates alternate pause and resume.</t>
              </li>
            </ul>
          </dd>
        </dl>
        <t>Call Flow:</t>
        <artwork type="ascii-art"><![CDATA[
   Pub                    Relay                    Sub
    |                       |                       |
    |                       |<-- CLIENT_SETUP ------|
    |                       |-- SERVER_SETUP ------>|
    |                       |   Setup Options       |
    |                       |                       * check options
    |-- PUBLISH <ns>/t ---->|                       |
    |                       |<-- SUBSCRIBE <ns>/t --|
    |                       |-- SUBSCRIBE_OK ------>|
    |                       |<-- REQUEST_UPDATE #0 -|
    |                       |<-- REQUEST_UPDATE #1 -|
    |                       |<-- ...  #N-1 ---------|
    |                       |------ REQUEST_OK ---->| #0
    |                       |------ REQUEST_OK ---->| #1
    |                       |-- ...               ->| #N-1
]]></artwork>
        <dl>
          <dt>Expected Outcome:</dt>
          <dd>
            <ul spacing="normal">
              <li>
                <t>Every Setup Option with an even key carries a varint, and every one
with an odd key carries bytes.</t>
              </li>
              <li>
                <t>Every REQUEST_UPDATE is answered within 5 s.</t>
              </li>
              <li>
                <t>The REQUEST_OKs arrive in the order the updates were sent.</t>
              </li>
            </ul>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The tests send only synthetic data to relays whose operators make them
available for testing. A test that sends a malformed message (for
example, an unknown Message Parameter) expects the relay to close the
session, and does not attempt anything beyond that. Authorization
tokens used to reach a relay are not part of the test descriptions.</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="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="2" month="November" 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-23"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="MoQTransport22">
          <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="MoQTransport18">
          <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="12" month="May" 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-18"/>
        </reference>
        <reference anchor="WebTransport" target="https://www.w3.org/TR/webtransport/">
          <front>
            <title>WebTransport</title>
            <author>
              <organization>W3C</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="MOQ-WEB" target="https://github.com/Quicr/moq-web/tree/main/packages/session-e2e">
          <front>
            <title>moq-web session-e2e test suite</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="INTEROP-REPORT" target="https://quicr.github.io/moq-web/interop/">
          <front>
            <title>moq-web MOQT interop report</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
      </references>
    </references>
    <?line 2556?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The test scenarios in this document come from the moq-web session-e2e
test suite <xref target="MOQ-WEB"/>, and the results that shaped them are published
in the moq-web interop report <xref target="INTEROP-REPORT"/>.</t>
      <t>Thanks to the MOQ working group interop hackers who brought their
relays for interop testing. The tests have been run against the
following relays:</t>
      <table>
        <name>Relays tested</name>
        <thead>
          <tr>
            <th align="left">Relay</th>
            <th align="left">Implementation</th>
            <th align="left">Provided by</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Cloudflare moq-ng</td>
            <td align="left">moq-ng</td>
            <td align="left">Cloudflare</td>
          </tr>
          <tr>
            <td align="left">Meta</td>
            <td align="left">moxygen (mvfst)</td>
            <td align="left">Meta</td>
          </tr>
          <tr>
            <td align="left">openmoq</td>
            <td align="left">moqx (moxygen)</td>
            <td align="left">openmoq project</td>
          </tr>
          <tr>
            <td align="left">aiomoqt</td>
            <td align="left">aiomoqt</td>
            <td align="left">Marz Research</td>
          </tr>
          <tr>
            <td align="left">moqtail</td>
            <td align="left">moqtail</td>
            <td align="left">moqtail project</td>
          </tr>
          <tr>
            <td align="left">laps</td>
            <td align="left">libquicr</td>
            <td align="left">Quicr project (Cisco)</td>
          </tr>
          <tr>
            <td align="left">quichemoq</td>
            <td align="left">quichemoq</td>
            <td align="left">quichemoq project</td>
          </tr>
          <tr>
            <td align="left">stitcher-moq</td>
            <td align="left">moq-dev moq-relay</td>
            <td align="left">Paramount</td>
          </tr>
          <tr>
            <td align="left">xquic</td>
            <td align="left">xquic</td>
            <td align="left">xquic project (Alibaba)</td>
          </tr>
          <tr>
            <td align="left">lminiero</td>
            <td align="left">imquic</td>
            <td align="left">Lorenzo Miniero (Meetecho)</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section numbered="false" anchor="disclaimer">
      <name>Disclaimer</name>
      <t>This document was generated with the help of AI tools. The author
provided the test scenarios, the test descriptions, and the expected
inputs and outputs, and reviewed the result.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+19a1PbWLbod/+KXem6NcBYBhuSTiBJHQdIN3eSQAOZzNxT
pxJhy6CJLXkkOUB35/z2u177JUu2eCSd7mlqpgOS9nu99noGQdAq4mIcbasH
+8kwKNIA/lEnUZ7HaaJOo7zI1SjN1OtoGIcq/RRl6qe3B7vqNAuTfJpmxYNW
eHaWRZ+gg9eHP52q/d6+3/xBaxAW0XmaXW+rOBmlrdYwHSThBIYcZuGoCJIw
GYYfZ5MwCybpv4OoFwU5dxAU2EGwsdHKZ2eTmJ4V11NoebB/+lKp71Q4zlMY
OU6G0TSC/yTFg7Z6AHMt0iwOx/jHQf8F/ANLeHBwfPryQSuZTc6ibLs1hFlt
twZpkkdJPsu31Qg6i1qwkM1WmEUhdPugdZlmH8+zdDbF5dEWHOoteND6GF3D
++F2SwVqYvfn37N4gI/ipIiydBpl4Vk8jotrfIYLipNz/DWLxuF161OUzGAa
StWOohQv+QH+OgnjMfwK+/RfcVSMOml2jo/DbHABjy+KYppvr6/jV/go/hR1
9Gfr+GD9LEsv82gd2q8/aLXCWXGRwlZADwH8X8GUYR9OOuqNORJ6zKd1MrsI
8/Ir6DlM4p/DAo5mW+3G+SCl5xHPNJfD/a8BvukM0kmrlaTZBL7/FNHAr9Of
DCzBuQZ7HYYKnDfBQ6HfBr3NVgshqK55r7esg16pRffxkhbdx9DiXXRmp0ir
0yjjvnlAb/SWKiW7s63ebe5yozA7j2CN+pQuLy87l5t0NqfH65fRmRl2Had5
+FPwbv+FPx5ODj5UGj8AVwikVD6Li+hB5TDncXExO8OtX/8JIDNbl07WiyyK
EFSS9Wk4+BieR/m60y/0dfDmdP/48Cg43j86PD6tngnhvEA6gLTdiPI0ECuy
jkwmTs0spO16qxUEgQrPctiFQdFqnV7EuQJKMZsAUqthlA+y+CzKVQiLL1Q6
UhGTK/iHtiBXxUVYqOgqygDWIviOMKlVQbLUCs56lTEQmgHmnV/AX+FYDcYx
Dif7kHfUSyAcUTi4aNE2x4U6B8ijWVxgTzyvKUJ/G3qKYCumsyLn3yfQC2yr
Go3TSwWoEwIlHI8D+hOmdp6Fk7YKcf7wcXQ1jQZFNFTprICzijrq9CKSlYXT
6RgmmtJutxhYu4+p6RioWLYDk89nYyHVeQRLhrVMZ2fjeMCrhD6yiJ/kF9EQ
0IhnKKfoH2CHjmISD4fjqNX6Th0kRZYOZwNcZat1UCJr6iwqLqMoYVD45RcX
vz5/VvFkOo7wDIlE5ApOFY6xaMH/Q5mNOrtW2SxJgDDSrHIgNyofREmYxSnM
/BxgFDZ/EibXZjXJEEj3ZApfQKNLOnk4JZUmEQBNlOPuVcNPPoPPNBC1zCht
2jqztf4yuo9hIWlyGWZD6HkfByJwGGYEDDgoNJ6ksMUlADLQFQq9xzMbXESD
j9gMDpWmDjNNz/Io+wQ7ApBbQKs0130BRcZNAUYFpzBuCVBhzxFuxyCCORgo
Ojz7F0ARLDwaw+MM9hagBl5MOohRBp5gouZc4JsSNLjUhQgLbgeTo8+f261L
mtwNIQ7GaP3yi09RPn8uH1OMmOXgFOJ5oafdVklKh4Zw4IMVoxG0RkAGMYCW
PcYjhtaZs9YsRxgnaI5asi/fqd00AT7M8Ikd7UWjOInp71braHa23dpW/dLR
MrnR68uRuuCh6vPGWdM+wAAni3oAyUaDJsx5QS/H+C/2g+dIuMb0awbrzWiH
4KNdGoFHywE1AJz0aHjIlk4mEZIahECAXtoEFNbUfvIpztIE96rVIkCXOQPC
I/JC8/RSUN0sI7XzZAnIZYtw6u6fAEBwhKMo08hOXUEj6spZi3qbjGEAgAf8
s5UjRNFpXgJ1B9a/xnsF8ghgBDCwiAFulsT/ngHcSTdIV9oailByAN70QeAc
4Xv9KQDDKB5Hz9efjsOzaAz/wlSH6eT5h7bKU0S7wSzLcAugK0OMUCrTlIoX
PkwJPImSwvJwT9cEHdU0vB6n4RD2DyXUeHTt4CrjMYyc4oakNChzMtgUkBk1
ig/194Mwgc+ZiBDtLGhl/Iumldg/kiWQbQEslAjyGw/xsHqb+HiozqMEsBbx
f0CgLJNkctM/2T04UMCMSVqFPcvPg6c/PA+eHj4PYGem4VCw7NEWjZyrS2Dt
hL2wARNAHxB0B/BdAX8megqq+5DGztWH9OxfwdMYdzk0HHxzy/I0nqOZCnTA
k1EfzmEe6ylM5AOt29lKWMUPKEarH6gfeXqwpw7pNE4vU00Yr5Wcu0BNHg1B
qIERonACt4XLixhAn2eqSSrwPoXYSoK64k9znv0DuEsQOy81RQKDjJ+7gOb6
O+RPFhcBsATyz1LcQ5gQiNd4uCHzK5p9X12GIH/gkkMjWsAfBoygJ2R9BIZh
hqwJrjTxODcUFC8KI9xaehBPIhA1SJ5JNAcQKgKDgcQRDzSHR/mfuxnFGZwi
4SzxStOKsSNNdlBGwt9hMEBoAmI5UGmQph1YC7XhOdPNDdvCukZRWMxg/Qxe
MKsQ+nGbA43PP8bTKbwdkWiWAX3KENZzS8X2HA7ykq4LQsxYiMuNODBkqB2l
swxANQNe22o5jZGOvrsInVVq8ZL5xOXFdZsmCfO+JFyLkgFN5IDEQE2toWvY
QeI+pqfBRQpsFLCNSX4bKM0sIckxBuw55wFSmgZ2uAuSo3oJkqPu08gB0RWg
b3IeDWkqcB+NMtjgDC96KKRe0pDDGMiI5qi4p9J8xyHdxD5ZECDRD2Y0nk0S
PC0NbuZj6AG2nwQilE7hGPAABxGdOe50DqSuo17FCYpccBcoSE7Dzf6w9gFB
HIFxwCwXzlFEolBgAgBimgIpZZavl9pRh4mIaEDDcBUv9093fySpIckvSdwB
UfJ4/6e3+yen7w//tqNQ4Cb5W/YCgBNwiprBexLTES25zx4BOmx2X2W4o+oy
i4F8JerDD931w26n80Nv/bD3gUF9lKUTjXuHXdxWIT1dAPGWftFzXvTwgAbj
WY7XctVPcJW6B/hqA9YZJgwhIGKB6O00ZaLMyx0gchOeq33TA8x6X98gDvkG
oSEFWNiQhRkLfWEO4maR20sGwGieRyKUxgAjsG/MNpFlwnSGFr12Q/gS/vrO
KHpOogKm+ct3RbDRDXL84zPsoktDcDLzF5c5bOv78kboiRLVEgdJ1ClKeIUQ
KZFOcEoaOUTQBKL/KRKqq2WOJDpPi5jESOoLpUu+xYtawxkri+AamyGzS7OP
dH4wFfiH95GHBJZ3gSBp5ANizkjY53iPQyiA5u6VX28Ll6FpadahVpBdEK4h
oq1CQ1eEYkBhWmmlKY9+tP73f/8XAGAQxwHgZUuxzKjmf44F05X6teItPae3
a3RavtRHbwO8R+6+Oth/c/r+ZP/07ZHCJ8+51a9P6fXJ/vHf94+d17pPfdiw
A8NrnHMVhMPqvf5xp7weNWR0kP9fRG6vgwuBFxoBqRR+RnB9xGK9FS4ZtntB
mCRApgfRrcFbXxgyERGO3r54dXDy4/s3/df7J0f93X1h8COAsgtmvDg+AxgD
4WSGCDwYRFNUSNwTDJmVbtfJx3rpgSMya1F5IXwp3M4q6GkKX78GFdtUgqPA
IfsERgBH9TBz6lAPZBxV50DMynZaggyCh81AjvO+wUGAgG84RK1Q9QoE39wW
YcrXUVEPFkYjYEegD5CSm5774zjMjRBNz7hH28hIlEb4tNQQaB+xdi0KAIu/
J2ikqQAkPjUI8HwdLyl48zBTm2Yx0GgQT7u9x18aABnE9Onwn8sBkAmZu9cf
E7g+3wYw58GRP3Y7J+1JkiYBsDTSkNNt9BzkQYZdS81OGIxYQiZQ3goMaAVm
028N1hZMBa5P3r442T0+eLE/R+imWTSKr0gSQ0HaHq+mN7QoM3PhaXRhpZZz
KFBEAAjEfO0kwjO86uDDBAR125vcWe2czL2KuX7VtFEGIJU7QfI9AfwRraWW
9iY5LMYS3g8+wSY0pw7UFMRLuvgzZYb7WjQewtfvEHu1orZqVTi/ORq4rXob
IJbmd8CuqhcAfYuRbjEy1r19GlQsTKNhbatq3H2+pFXN8zUmk7Jr3H8N71q8
xjqSsrjV4jW6499pjRZ/cgCnJdTMwULRZOXKpwHRFVwEx6wT00g/LCEpXEy7
GyrvuOq+cQQyLukb6S6mVQGspkMN93mSwpVQiN+JnodoeAlRmfY9tLTvHhi5
VQlrNku3Co8mejrfuCgzXaKFTDhD0g7BTUyroTRfd7qTy7MxgKAGRm+1VgiS
neES9UmoEcSLtGiwREUj91AWIkh55KoT9rTeijYWxYEsImvlBC/IQ1Jawgon
SCXGaU6sqIArLKkXv7xMMIxG4WxsdOnM1qBzPCqthIVxNjfqdJ64wVqR2UZI
Q/0x371X6J8crueoOsWJ7KbjsShTUIm2reArfAfwqVZ4Latt9Rj/0stZ/bYo
aJ04s7jV/dIk6c2QbJnFckrmsK97otYPLbV+9swg2sb6RqfTW3+inj17Xvv8
luMSxrJduZ56nhAobZMqBkDXEACLnQyhjqqb0JV10glSAv42Z9MkCE2MUig7
aozeRp3bOAoB7Xvfa0PJ3GhqBe4etpPuxv9BNC9WWX2Iv5IGlqgD25AR7dfU
PmF62YKBJmDAtICtIYNwrBU68p6NFnzdCmc5U+zjKJ9N5B7+yBFWZ1N05LkP
SXWKY7GNyyMknuT99mivf7ov4mpGc8qJgusNw8k7anb+hOkq6RxKxLtNekk2
homiWaua6G5lTLnXpSEuL4B48pyHDlUm/RSppYDTGSvwPZHgBpS0jSaes2jE
sCITpH7heXlbUPDF99ul7RXLaJFOc+duqVZeHh6/6x/vAS1OjSK411ZH/bcn
+3vOs02cLANMdddmc23vZGGRawT8H9WhzgKs0tFw6Y46GCGrHcbA/5CAIzHJ
hRk8VPn8ZbmYZYm7njMUDtJEbxcyfOMCEaHWFvdM9lzsgtG1OethlpIZRKDG
zutPXlN++yV4zTP8cQ5I0YPntc/vwqEeOveJG/eQAz8RMj68ZReEA9vL97iM
a432eMHt62lllw2gYIUNZ+F4W/B30RxMKzKBDAXXAU1WG7WqfFvzvELiuHEP
TDp/T6chJE911bqm1Q32dQBSCbKylXgkbG51qR2CdtenwPBgyViMriTdODj7
vPb5Lc+NOmI8XCT0IbaWhK8yO0XJqq+lNhTztPuDSHtyYcYdEIGOYUZkqreJ
ET9YnPo+mCV3vwFXXfRzbzV8cyW757yY5Rp3eyyIaEtvgaa7QQiSiDgzWEJe
UsaZsXzNt1ylUfpgkzWJYywwzYtkv42wNCciOWeCcBEVxZi9NuQb+x6Ehm3h
ETvakdC5nnbVN6bA+1Mk+DoiARJsRhtvnfc2bh2BrOv5LuMiEN+aajqohLTz
TVqmmOL30lW5hz/TKIvToYOTucVCIaas4TspwmKWMzV9jOEDg49BTs9uT075
BqDt1UDmyOmDZsGjoSeP0TCyo6v+Gq2FxvV23khIpiW2+R33d//2/uS0f/r2
xBBToFSshYSrPjCZT6RRnPLt5OsZ+IYiJrkHibtwfc/E7Dj69x+CmPln2YSY
ucOvq/3j48NjhcTsJubJklkSfbn0X9Thjopi9sFGXTZK2IiBwOptGw6WeIXx
IgB8r9KBuHRfoqwwBdElQkcwav8pHMfDObWXoOLLqABeTraAXXTuYHR8Eozw
+b1Z6DWVoYV7Fnl9RZcdGpC2bYy/4GTI2Xwer0kgIr8uMhiw35kTJMD9oebA
6M9y3+e3Y/QWotoYkRrLuMZpfZwNNeHYBW3YRx/R+8DqHZj+GA8xEPEGTiuL
w8S4hupOcFNoFFLab7vaxlo1/I6sBz7oov61u/5ErXRNQyQpBEBatMJevW57
G1uPl3TMit0n2LPTmKyzBgaY3E4p/gWASE3CKznf4SxjpvFoA1iVsbga0kXD
aDHtP1cee8bCkCcJ3VpmWOO9X6LWoLswn7KBnYZ34cC4ija0mT4jYqMhXVb5
he0E+64BTyQZoSP+hZAsqJ78kwLKx8NovkkjG4I/cCOl/hoqTYs5LmKdWz1+
QhykbWmWQ81UyNQrn03lgSu1IE0zll/mC7ssCCNP6G4wTwhYOL4XLxdWJwsF
lLUQGZdrKzse5yk6mbqu9L4guvASHGlhfjBGz3Fn0/xbMLVj5TmNQ8tHqm1u
yYbAs8MMWZvh+2+Fk7iX50dALxeQ77ZQAPT7tmC1UkOWsWfZMQT2bSb5D4Hk
V96w7Zb/eb2uaUXE/JHDau9CzunCyudjDubLUWqcuYeDTS7lLGkLHvJUG0ja
Nc/vQ7t/GSJ2L74dn9ZQG0dReItrMTZ5GV1qkusCAZqobAQq9pIW4VjIsbib
/3DYf9f/J9PjbnCehpfh9V2DBlhCl55xcej1F6o30aWJVHh7fODeh+N8zm4K
F44pSOg7bqiOiOIh9nYJHwZyEeGRYm31Jaoo9jgt4GsrbhbGyf3dn0tL2iZW
/WW9/AXPAr3qwMMz66+P3AntqfXw2B/p+D40d0p37p7ZSCTpzHPO1+veRTao
dtNhxJqXbs/kDSEOeVdoEjZLimoZUvxFOWbOZjnBeEdGjUE6FF99/I35KwZr
UsiOCbT2glpoGE9Hg5dHWlvB0TuJeBvFiQBnTnFbHDgOJ55e3puFH0N7VHeb
Z//mkCUwtbJxtbHaRmV5DtN4IFw/iR7oFj1pcXR8eHq4e/jq/d8PDl/1Tw8O
32DbTactZneJk38RUDz48gCr3p3yXq7g/FZVFcBSwPgS8snnYcOMDHGB5lmW
ZuXwEjZxWBhGOxai6GolJLsQhAf0Oj4XqYXgetPJh2M+vCV0wyRxIRjBJbcL
HSIoUA+0fDgW6RIDnEjL6MI/Lhujx7WrgnFvwK/RE8ahv/PEl6Mv/eQEeuhx
iuF6122UkGP3mnARDpnC3lu4i4ZzZ3QH3THEXZbsQLi7rvKqPug0J+G4CDhi
P7oKEVow0ckHcQFFi5zE3baX7YIeeNObJCJ8/pHbTAhKIvzVDD9KU39gfWIU
VZhmHyOyiOL5sXl0okHtS4eIDTRlIWxcbZPurATWy27yblf2QOxGytbtyHf6
p3xYF+gT33ggOADZ6ZVVuRMtohYasiqXh862fIogDuQSwxy61F4EGRQa2IVO
Q5/zNosGacbh5XNrCxmCRVtvj1fy8RAgTjgIMq3isD7U2eb6iknXQNoDQXAh
gMyPbKA4ZevCkF+GuQnyRaZ5FJZ3yIHNTN+2OGQ0kGjnppTt9CKLdEYTHa9B
EZi6c4frLgwSpImhXZyiczSw+331QaQ9YIdyf9IzbvW5itLqAwuHAJ8FhY0X
l2mpZ9rGWZJF53FeEBh/jK5zuIsDEE4j1py78im7tSsZt9TZyi+/nIi08Kiz
2aHwYz9F1ufPqyVFNQkpeRED9msGp41dbgStG9S+5g2rNq62NtQKwjbOfXWb
NL+w7o2rbm9zC5M/zDfoqpV0OJTvOYPEAyf45cFiN7ZagtScMPnI/mtVpKr9
eW5JAgdfC6zy0hGgcEnuTdr8lCNcq+Nbm820huzQgbijEMiI060JGFga+YpI
wEqJedh/h1FVmEuhDP8EQwuh3yVXfseOItBiSIx5Njz09NVSzqekn+TA9RJ4
vsE3Z9F1Snx3Og5LNOCbhK6mkDOOc53uampkRqT6cCudRepjnCxmb43giZW7
qeMCHVI6D0JxgwahoDrjeGUbwXKnCZmvOJuLQF0tyX0ZX8HE+MJokwwY4Buz
63cJ9g6TgaZeaAinFEAO+zTOP0zYKuAyplQpGs6GkjyALJAkYojkPAmHEact
QQFEI9gO9n2BvC9GpQ7JrV7CAvZKW0ZP25SijBWRJWb1+4XcIuOoYczMZZe6
bUQKcwPQW4i7d3dYRmKEiYgmUzoKOXf/zENRSuAzTpsjk2GxxTOuH5MiPPfs
1qI6I/B8eD8uIGXTc0ECj3EIl4jZkkEZrge5pDWx4GbCu7XviCMnPOl0NyvF
hJJOAlGCHUfIxG7uScg80OyvvTwZ0Ela3GEDOAf2UVNCCUldhXTds/TURY1t
K9dhJDeeInLVMwESRIOcMJ022vtoh3v4BzELbTjgj/vax+TSsda6R33fzvR3
djYpq/Wbq/bntPvL3WLPN9bTDXXepf/28L/LVPs3cHCWWZXdVpYq++dMFA2U
/fLvq/7xD9Tyxf/d3z2F2d7yLJaRGg3r7lRFHXIs96iDvfacr4xaYbxVOjuW
+MquMrAejMoL8LC4t9Hpfl+JyIoy32g/GsANwgAayIkd47gSmzyA6Z4J1X2/
d/hmHxMOIRe0mQRekP2BqN4jmzggQO3g18seoJ1x8MakaWZer1Kl3I7Axc9o
7tgWGpYW6hPImn2FKXyMoqlL8jgVDkyupfOWzSUXyHdsnjfO1zFH7SrTASDV
C5jmrSc5bfEHTcbYhmSTdPiB/f7afgMJouoAF0sQc8Rq7itnjSsbnU6yWvmV
+x2frJVGSi90zMhOY7NcI4pQtfZ8BueOKrg5qsAH+u4iImeG0gwlikeudxjs
OeQMaZzOi8AIVSxmRKKtJ+oAhGkBNEbV750AShJV7uCnWo+sMrqPSo8rUaml
fITmNB+cSzFUNEWiYto3tM07h4gnwd8t5YbWkVSyrXTA4DPV9UMG2bulInIQ
93/PdcBgJL5AL1jr7edGmGPr8pop32WV+dC58dKB5C7tKBMB4whbaOGHd8cm
XmJJSBQs5X2fLiMisBg+fOnhpdm/bXdnbdwlbCNxLbNzq3jZkX2okqhYqBaR
5ZsLTPxqstTNpKL5k2ziYKAPy0GC5WlB7iBLza+0EQ2UFRkCiCh2jUlqcpsi
g7FL08JFlwRqrlOt6uylLgU0Woi+l9HvNP0YiXHtcYDJ/oICn9wHEYR7JuvX
cNC3pz8eHh/8P7KEvj89/Nv+G5sLdE56q1bW4oXVLEfyNdLsxXUBbzWWqqBO
OG+j2sHT8FI8OV6xQfyrcWzg6DI9N7qnwZ85klrx4L6kNNSLL2V8ZLy9WLYC
7vePNje3HkEv3Sei5sWYNPqA1FV/ko3aVjciGw7Mr9D2rja6TM1HMzUnAMSw
Ca5AmP4SlylvciIqlWhEm2dhF8/WKJoVp67mTN20JQJrybXkhUc9zyyL2lIU
IPf05GIYa5eSKHfcbEKSYpj4nxizngTMDpubsS5Ta8Sy65Be5qjEkyoqsaNe
He4ylXl58Op0/9iVduxgq6JupVzIPOt52dAsIGARZV6/2q/PZRQ64TsstZHZ
nc6ONNaSlYeL2qC761iLQuhTh0RNtEMs2LIEWOlX1kBBRInQZuSw5gkpcmDb
6k10Veg4AF+Rt6P6Z3k6nhURBndllFt8Y32DTcvm1TEpEkkfBi+1mlfcJjhM
pfsngattdRMC59I3PssvT+DKc74bqdKAUKZVc2ogV8LZ4euPk1VXiFYVWfrO
QqamSTrR2b4kWQP5Ic4EbkvoLpi1BN+1QBXqkeQWZGK+o/lwBLybyVcmvolj
CwgP5owhVbhso4QWJ+iSXa5C3m0psiMKMN0Ew31MtE+pOW+U4LaP1xW9UQy3
Wult0EH5XZayhqFPDmYMM2r80SwjnsRqh/9cmvA1KUB1ArDzjU7nvEdQRizr
Dg7tTqQTOm8SMDWM/HZ0UBx68yUELC+CR1dJ8TDV9xTvUQQR6c6Mszhxv1AH
ZdoMT257Fpr2/3F0cLx/wirJ/Xfvfzg+fHv0XmCDqFFvIwCkwgzrQXKe3cYR
qEbLIhoW9gm6xsuxnsycDv1R9TWsetJzrSvFs1Un5Ib8KWU6mOYyupStQ6rP
z2Cjf/mlCLa2AngbUL2RQFp8/iyE3uICSV1s3LMaI6LSeon+zlb7ari2Rtgm
3RS9jguThHjHT2OJlKulHAmwARnXHW8aSPpdSkYrso5V9dtLRlbTfYMsD9+Y
ZMS+R35yIXa0raMTTB/mPD+Mtnjq48LeP9/0Xx/scl8n7VLKF1Zdw9pLUzDU
Ym4aTuUML0W6KLIRabzc8cvwwp8falp/z9gBq4GVHP2HYcdTbx0mRVYDnJqH
8i9lm/YwL7qKqRwgOxk5C9Yum+xE3Awvy2Gg31VZotjI45fVAGSusEbdwtCk
PV0oobSTQFpKHpU0E0uRcqfOpMIfffgdI+i3dLG/lcHjjqaLL665nHf8qNZb
6jlgEU32ZkI/jeL+FJU2dcVxRJJdiGDENew4wTDjYFeMggGNf0tDyDvKSRuW
q+RRfdNpJF6YVtLMeEYAKKJUgFWzSoSCyRzZututdWbvVBhanUFQPo2H0Q5m
k5H8APpuIBWv+AG5JJokrw6tIUuINEhhR651qVH2IGVPtlv6qm06xQW5XKO/
cUY50LXuHdySDpO36fTw8P3L/vH7F/s/HrzZq460w6p7wSjMgrMIrnHDJc71
f2TK9DUFhWr1wmY5+cm9qBeePXN6c0fvurUocKtO9k/fn5we7/dfq0b7vFaC
sB3xgXbpBcc1fQH9hGgtCTcc+uhnAiklQBbfEEQOmlEZQfBjjuAVVNEREm4t
HV14WCQFSkU+JGloD+WcN4D8eyA8zbIze7UnQtoLpvzh7QM05xx/pUdTsgFb
62empGiJXj6sUWMAecHlXqZc8Fzgp66QFCtv9Vg4Ljm8CRmzIaBOT7ekhUfe
Gt1MUJXLxQ82e/IBO+4aW5+ZCfbbK82OGatCX/Dr0sZK+b/SOzOi0W1N6rzu
7Ir+JK+lt1+HvML3U4wV5uMEAHqhGqxUWg3plAGoXqgm+wPEt3dzUu7NsC1j
Lh2r7m3dHJpCi6tk/sI3Ti8vsKk5gehahaFvUkxsEPwcZalaEUxc1cnd/Bjy
kFxtdCZAaiwOK046CYnB97IE6QoKjOaSxKPjFwvSGQ73YqxZjo6xR1x1Lpak
E73NQNehuy3Bv/TL+tnkzFoYxSKirNSiuQz1XGCxBjuO3x8dHxweH5z+k4bi
q/nh8d7+MbvZeOzhYadbLUtDjy/QNVnKVdBpGaq2w9p8uq0M2b/dkYHbWG9+
gEQ4x4RMs7Fs6hmVTR4BeWxi5dvywQDOobvtFPp71BZl+SHNAMs467Sk8nnP
+byHUVTu96H/OaboyzlToE0zKryXLlSP+c0dSXsVWceFlb/D2deiYONndSS/
ksQs6OFpM9K/oIeqNxVpl2/YwzxLqF7ZjXZyjYCG4Athatn8S2tYocYEbQAL
i42SNSyt/OOzuE0/6fJWg2xbN9yThikZb9RD1Y+/rseLXeybr2vRFYKqkS/i
QTaDPhN/vFtn6Gbv1JrDWNRjCVJ8xXGBTP4f0gUIP29K/vtyz7BK0MsLjEzh
DF1UsBFo0XmsUwM86Dzg647MyqHjvc5Wpzp2ry0ZR8ohr0AYzykVhbWIsqs9
Jm4h0s9mVE6YUopstXlpXTPrXF4Ik9D+WofBWs76nSFLb2nYsGK3yxvrFNmt
DzIvODt2qum3LCu0+2ZrKVezoY6sUjuy/o7DbPUeeEuqjLI1x3F/gbZ6cA0Z
XjBtWw1AdjLXRjlgczQ0g2w2Fq/g0zKAiTZLICwuSrBlSfINoMutfNEAvqx4
dnMI01/+AUDMboO/qmooswdzf3BmZ/DVIU0dDMeYec5kZvsRk2bhYARcj4IY
3t/K/xe1K6xpYc3/ZYw++ziaocFEkYkSS+Ye1J+jmpg+c5VADzuPagV9wpe/
wWjcn9a+4BOdqUOSCk31oj7qr+cR5Z0kQ2drBdxVRqN44CVd8BVZN1Va5coM
Pq+qwkJopJbRya7gRGEC2KuppkZrKaGlXT2Wyc7wYtMV5zsKt8XtlAoQWw2c
8r5phBW9g6/Qmu+r0Vdr4uLJm9Wm69HWPQVLujn0EOMoKxFnqWH1mzkJhF+S
xPigTsWnctfmRtYQ7OCkSQxZT+jFSJZfYG5G1nQTYmmnTUquTMAsOSo66gAh
jkDRxhibRRR5NB4xgpJCGbrBksfkilUCyAN3HFZrMSjuwQYAeUFVye8ZCNeQ
RAhxIKgpqe5cg2akqsZZMzkp2+qBeywP7g5678TFUfnWVXLLM/nbhLmID4TO
j8l6Y5oCQZk+Q7YvMMt4ffjT6fuD10ev9l/DZnJuTC/pC4Hp90GMGbgmcIgU
qRZwmpy7pjJNJ7GEmi6dxtm1CSWkXHEELemUXblTk7UVLk0daciQrzOH2WCx
batrgy44bRlPgiOt/yIJizAPCGx9pu8WgzSBu9Ak91PeUS5y6EfSx9AR0d5w
hIlN92Ny57FISM91FsSq1fO+h599XKz4cpsTzuN0Vpzw2MW1nZcgZFN0rEFG
LMuLALOq5lCxjIL8U5l87CZY0jjNGL2DzufOYcEhnDU5BJ0lTqGBu/f9LZPI
3mb71wjyfATVQOgc0dwh6RNa5p/CP2sVqPItn+yBvx8nvB9hKWVX7/tBo8NF
RwUkZg/c/FeM3Cb77ldFuGD+QKt537JjWQY5mFsQVlVcZOllvuNlwFp6dFFh
ZV13/yvSWVUIMMSffkBmVU6KRSf3ODind7dkQtKxWCF0kEGaTdTG1fcjZOnq
r/Drkz2pHi6XaQpgDgtyviFAzDj+L7qKskEsdVp1EkzuvC3hggWWSSauxJik
szFUZ+M8r1p4RcpQdE6SgB/eVswkJiCJLMzNDMe6PI+R8TBkTC9gm7RkKEgk
m4TJzKcpps48kq/4BMrc6e+8mbhrbcyy2d1VKzzAqk5GuYHMoZBhfR61TekR
MQ5ch1siTvP8vVzEnTqA4+OigXDsCSXSsavUa2TplSajvUPn2cECwCvzg1KS
PJiDk0PUyyvYqkg5SrtUlaR0b7+/93VpSolB6KO7MYdwAODbZRFc412dDNIp
Z7A9hJuMF0BNp/0kmE3h0hkFExCqYnYEviXJwQFcHxqelH7CaE9KOSAZfern
BSvMsYiCqo9uxrRNHVoOkti+X6yIvaOh+YrkUVHP1MaqeNOQOoKz4fW3Xa+/
F+xQQ5ZVukxiqknoZIAoRdky7UIort3mQcWN4S9ofzFAEe/ldgFTXTWgXgfC
u2A3gQLe4sRk9zP6sjmvHcKw7oa7FmrMxo1yyeI2ho4RT/rWXGMcS2m/3dD1
o+6t58tsu7uhk8tVr4GsWPe80ufwmXtQNK27+Bw6lj7p6zetb38OXE7gd9np
lCMZ+g2qC9WO62C5pr3V/df1fJ/n27vX83VO+MVNihW/cCsHYbGDtUXcxKEc
lA9PDrG+6jk53ZFc26dkYFQUvk0hlB5FlQ7c6kZk103TiXoZJgFqAkAOdcy7
yIA2N4IMvghGYQIf3JLzvExnGWVtz9W/QI5D6xD0uY3OTCL6TuYdfPATCS2B
NRJTqUgaZ6quJZzYgooRoaZJqHaYwLyTAZewQJ2NS74dKy/H/FJmeeJN4yjM
MJwfd4UVu6zFxy8wk1CcDMYz0vnwupj5yGCuhWQYS6nhYcya4/wCbjI4E8rS
HWdu5qGUBHoZD51zoiF9oy8IWzxaiV3J07a7ZfX5zeg4n8bD5x8IdI5wyWZH
0PHI6eX5+lPsWj4Vlzi+REV2w0i/pI8PQO+hdh0qLqOIb+l6Z/CeJ2UUuxv8
GauusMicGM/hFraYHeKg/Qp8q2OH+P0SKlj3XPhhZbrCW/PD6sSPZixhvM67
/q3HYrnX7cnTG3uejk13o35d8zN/obzsk8p7E3wpPiCgtdQBxscq6wTj51ON
nE+ZCGxWk04RG4lsdl2yebdskieAzXPE02Z6HM0AU3K00qLGN6T7NTpCDpA4
8Y0V9hL1xNuVgCdFQhysbxvZDxY1Qtot14KW4tCb+XOW7cFp/qUkI1P1TtpD
83lL8lomDk1FiT1aFsUYFjIE9GCpOGnkTc1O7aAZmlW4h4giPK+GqDL049Hl
W1HlR0KTynT50V3osgDTVPZnm5gamruwuGcRjtPztvoUD6MUdg4YUUqNNj3K
S/CS76hu709KW0VpvWvO1ZYKmtxyviJ9brQuwY9+k7ABb7Ur/Sbad64T7Ti8
yj5VeGK6rW63G08rT2TZur4E36mIvn3RKGzf2+EXq6rJWJU7vGCsZWyN6Ghj
ZvZQ0y5V3d6no0gstjRxgn4q+qNVaXpYwSZ3mXwJo+x5jFJI273eM6j6FyeP
qWbLn1kgpYLiIKqO89TRioWa3PKigZsZnlURlSDfompd8vyNr3mybbJhzM6Z
aesttXEXkqE2twFVMYbpzuVQtjH/U7GXcI1tpugJpu7ja584u7Z0nC5WtyNb
7QXp9KT6Hc7N1ukAXL5Ix8OcamFFGhaoi4AZc0zZgnhDMMbESdXDDFKXhBZ2
LtYKR2PIqaPPo4KZbapLGvIAFXelep6MxoeveVdawJOJFasVbrcqPFmtaH+h
1TZhhQWPNY0GVLcIRTXugc4M27ZlS4rKbabejIJoTRyAyoyfzTFY4J5xn/ZK
nx5mSCKVwJ8iwM1EgDW6/Hd8urB8Xag/0k1sbe2lY2kocLGrwR7+KaQsFxzq
TuQuV0+Lcgt6GTionzPi/5UJxkLV4KI7a5szzlXcVduWhdGU+BaFSaw5hpgn
IaQNL1XDMikSe5VAFNVcmPeIJWa+qaMS7lLqZJ99qdykuVKliTiQNw9J+jHG
iBUpJCIXWlirhiPtwqzDS409XJzqcvTZSogfYjaR2IkMicjC7ViKtm1tKXNJ
TmxAoraqOdUjJal7lYlJfZAAv8QNdmw7yRBWvPJMq2LApeGdHoLeB2PQwllY
f+5bmZX455Y+IXpXcF511UyqstQElkyKsn0+JcTzKrJNgNBWLw/eeGSpYjpB
T914Pmte/oMQTvc8AYA0a1/qteuBipfg/5x9ap3+TQlSXWYZxzAOv5gshlFR
SnFsqndxFqldKtwm4vRWQBjW26xHvt7mHMrtco6YSzwz/ZEUhBtq+L6EsbbF
yQOlLy6GoXtUqHcqsnQMdCicUJzoy/3T3R+l7BNHGZfz/7g9yGFDRwd7FIJg
yteOIvSj0MjrJwXmjI6UHWcvKiTTD0mc4yj8FPlOq7M8PBtHOghMnDLcxqU8
mS3jn+n5Z9DizRG85OXK7pddUrya9tMsLdJBijYP1NANtxXInXwevz/XLXNu
SXSeFjH5ATdGC6cNyvHiHGG6XOJbx4DVrwYsPoeyj4xPbifhFbDEAULfTCo5
P6Kswx4dJmLr5URuazHhYE8ePWEI7GKMNs76e5V/jKdTPNte16Rmpi3LU9sa
s6MUYSWEm4pjGOVPU+DlZm7O5d76k2/YY8CQ/uXJIshK220QuWtb3bfVAibO
Owx72+nAzjbzTqhiG8tER1qud9hNrMgIbORL1pbELuxYtlBURCTjVWF91kpM
4VIC9JHJbagzC1ECiq4jgNlaA3hjbIu6IdbZxm3BPFoKzLiNAglnRMCX5ISG
d1D8BYNjxgC3NvWE5BA3uGDDzzQJyIvw2lABrqYiueAdh3rtEE9PaGU7LOaZ
gpskKJJzH5sl2VvIVHnmGD3rrMLEpOyjK8REHEUDlBpJ/godm0SSnqXDa6tH
+rbQte5tRSKChshQ4ssNkEH+RWTO5dr0mJwjlsyw4mr7hdC15vmaG4C1DAn9
bRlGmH8rb+v0h8lsEmXxwMnvtxDyxUs504INaftMmbRarNDpvmEI0u7xvc2c
McqV4vYa861VJxFrm8ylJnLkhwqp6YCEpKFgy/BzdcG2zPHFoMkbXDmbFY7C
NREvRLMR1tUvHFJBrErJTfz8/A2v459YARepkcHkIGUC9+HbwtOgEtpv74gn
e2HX67h61b1dNsNq3F/Yaq3yCG9Nte5Ef8o/nh7nsahx1gDV/OxJnDrpVjYa
nYipcGH7Lwj4WSnN5l/y+WxNfinMCvuB4X3aJmHxh3MTsSba5Oh0sk/YUofY
1iYHcBM/EZI/NHoeW1jvtt4NFepZXa3bqdU9Xy+WmPpOhYmEm3NOZc8FgOgD
ZXfWaftGs2JGKfKYEOjcBWwW6KiX6EcwCFGigOM7i6WoHKcJlEQh+iLbUiLu
gByjRyVy7RhrOupAXCGw09LhsHaLAiblnuAGFNs7kZuEFWAVHaKHtD506cP6
6OMwTtxt0bUoOJpQA9TKbjFebXMgja1Pge6Jl24BYKl74ZeBas/XyHNhLMMl
4lV7R8XocQHdkK4jSc2NSIxluS7YQya6QYpOdTlu+ortkCHW9LkKlFxAH+vt
ID9wijtKSuDKwsH1Zh6MmRtdDtfJ0tPWXMHUFYW5rBdsATo0WXFK4d6ehYYN
iWjigQV2K2G87XnS2K972/qZfFGFHyty+eHyZbbxZoOhCJCqHHiILHiL/mB7
3tqeQ7O6FTysX4EufetP3+O4PFq7XFI2AwFHuhdEMcpOQw8EYt11FjbvJXey
45AVmpztzJhkU+HaKNFzzXK32KSpZfubCwd1b59Wpg7/yiIy+2N7WXYdDQFh
VJMklBX51oLlQol11Vbrmn7e3ve7buZNfFnmZ75cQ/BsLmlYk1PQLS5twL5o
CJg0tB2B2+dJu8TguoQwPQqKn6cP7ZZXMb2U5VCMD5MdS4wjq/R2shK3UNTH
hsg+44xbDmR8wLLNbxmtFlqS61otRqvbIcWtbgVrzvlPR1dI35vsxhdAJTtn
nMPdiAxKKsARGNApmpWtEKR+0v4OeXQfVzmQl74EWNUujoUyI5At12Jagc9A
0vKxfcGu0Yw9DdGNdJ/3Tdnq1S7aGGX3xPizzXe342SVYkleNZdNHcm0Y4Sg
XMwBIAsBNarzpSt0dnU2SaEeTCZHU2Alqbts8l+2o5C853bvu/rxbWFEki9K
cyaHsLaHk9YpL1fZyPm+YOQknf5R7jv4nHFkF/U5hTpBfRRfCx/pgmwBd73A
BtlbcCV0xqJwHhbXBjwcqb/Yvk5Jzlhl68WcatWPlgCd6hnG4sjUsO2EQ3n3
inE0Iq/5ROvO23NGKTHxw8zYroiea1hxj9kZ3EH5Cmoul2WN8A7dI1H+hCXy
hZ1TXrKmysqpvHDoJw+LOB9du9nBKup/2ERmzg2QvO3VW0kMwBPiIytbLI1K
DGeLrglIRa0loMV1NuCi/POndJabxExd9dUTUDjrk72ttGLOKYZcK6Y9/h0v
rRaP1aCUjaQ68gtCEtHW1RbU3uH+yfs3h/DtPw5OThHdTg9e7x++PV1i5XBs
nQvOr8bSufD8qjWiv4EVWisc7el98+fX5NDo0vX+5LR/+vZk0dnVGpZqzu7r
HpC/DHtIf4ADYrijKsg2LQxS3JI4xMdUtmjIMS3wJKhyHbDuTEY/5OJhVyPi
Mkz8TWz7zjWlaBYnU/f2aYl0S3ffkKRa87xCpyEi7ZMb+S8skZDne7vLbDcb
5BAwhp8ueUAgADbUF92j0eXgzd/7rw723h/33/ywf090wevzhsxWkJwzGhq9
tRCE6HYEwennzvz4TyrwrVCBNT9v2NIevgI+ex5Ngs7/efhsYAUT4uqkPx4g
EDZ/79RZTT8GY250y6ur1z1rPXN7z/9LPjenjl/DVZxX9TbYogEmQsuhHXIF
jchfMNoxnukt5XmT6yxKIuZ4YgkVDPMEk7bpFbrprffa1m9KpiAJv7+IROSX
/dFHC/f0/TCTLH2vQvQgo9wolcbJ+ylFw+P5PzhyLTo0flah+a3X+i7ooerN
03miesMevlAhmSQ1p+T3MC/y3HAfqtxB72cn7c88o9I/C3eyqoNycZsFBHbR
M72ZgKDLlaGcd9GbApZwj9nZao4iOYSVghf0t3PkFAcnxWUyBDpZkJdEUuhS
BlxG248dsgrKV/EoGlwPxqI5fGwcSoyVIhjrT25Ji/uu55hxPQvd7G3IW6Cn
S4xrlbgAJ18QEuLzMC7T6LpURNqbexpSSTSJLUVqigQZqHTZIm/+lhAW/6Ee
m7NU2KXYOZ+RbnAQjbmqWJFX7LPxDryRQwSMluR0AOs2+tX6A1V4Cex7CT6U
67EjkVqIpuKpws5VD5eoDP/glr/79OyjoWrtaviSAcWo/u8gugflk6XRvvK6
FqXjhI8A26QEA1k+hEqxjyt5aW27yFjCQ5qSeXYnq4lFGcG4t5TMk2neE4fW
MT5Jrs9b0zuHSE1Ssjcl1t+tCoZpzhRiyNMrUjKbcORoRR5P4gXX2BvrBu3O
HR3vvzz4h1rR84R+tI3iSae3Af9bna+mK9418JQXjuk00ynHN0jmZugnHQ/1
/MihDrV23jfkeoWp930id2ja6XKK4Ycd+tZ/aixjNvOdTeRmVYM8RdPVOh4C
yLvSB//5jZW4rXvriYn2EBve9Xj9Tceqjq78GlqtucSTjTQMZcBuskY4WAb/
Z7w5cshNGMTc7twDIXUA1M5wUau7jnV2g7Hq3nqEvol4vHAOd4Guh0uTxzlH
Nq+wEGJi1uIRiMbfC30xGcKloeFGsyTSU2PzdlryTVfpYDDTKXhOuCr9bhYN
YYFInbBOF3lIICva2hDBLxjQF00Z0AnWtlWv+/94r3fkYA/2EJUwyH+GkoNT
c04OPgnVWTyMM2YO4bjlVBmPpCrlOQeVwSLdL5HEmwjpcUzFW0LOhdr66e3B
rubHvIbcJKRT51mYFDbIS5wLTAzz4TRKAt4huJag+xvvSRhgZIx2acjn6yOh
M7BRPpEOcBQi582c6Jpc/JRVcT2NMZW8TJLmr0jZg5VakDfSoX1ynfr/kst3
xC7RG0X9exYPPoomhEKchUn6Mc47Uv4lnfjOfjlG2rVlh0yJmkidUXoFZP7I
Ho1ve3Xqgu73G1x4GUQsq4uCy0iO5kpY4hFJYFpz81B/zeolvhviQeNnOgFr
OWcggXkXmjobya7qBS1tB3P7jrIIYYyuTfAnTt1+3oAV5xU04CtUm7/CDdTk
bXGrure+nucKN6qZ+pzySSD+aThcPhb+hxWDsverTWZY1nkAeWpGzn19MDRr
NEMjirM7UJMZ1jxfU08pcfRyo5lcqZxz6G3cifF0lw8a+MM1tZqsIG4wFq6a
5zc7QB5t8dWrD/iGwC2QHhkKUvKwU2czqgTCHl3ZTHROnIPZSQpWIgBuKDMA
Bnvnafe4Dc1JXZNAZbE8MwHJnQ2v56iHnrhwMBmku6FMKgishBe8ojoPzDty
YRtnAVXJE45awTb6c0E/E1TwY/WEcRSIkv2cVeVEmLHGAnkJcnafxEllXeKQ
OklGdIWT5yw6mvHESVzE8C9zFNjh7gamaJdpdjAlAZUwsElKKGo6HrGuPY+H
ERecZH7K5UQqxxf+Um0jIOkGDQWlygmW5MvSYYapE20TYlT4N3W7ckg6L+oe
qySYDm+Ipfd9u3r2TJ1vdDrn3a0nnF9dfBLqnptx5XSnJH6hNLfo+V1mq6n1
ooBLcbMUd95SxJqlAg7w+cnyexrvjRfXa8k1dRRmILMgVSHk7wZSeymY6he3
VObMDZBLYhBdvAhoKmp3kiFXRiJXWetnnBBuDqNRnFAGn6imEqdEomvL6lH/
GO4hp/vHikIITUIWx+P0Saf7pMLllMPKjg9PD3cPX73/+8HhK6pdBp2wDbPj
VxOlUEffwcyoljjdo95XCkyzSwFqFqmNq83dMnUpu9xpQqMTWwD3qzg17Alu
7d22M4SJHKDlW6Yik5cqVk4ApBZfObo/kzrJfAGR6DSCcJvD2q4OSOwSslbn
2Lfco8/SqYpsP44XX1WiH21cixIyvXvba01vf3WWorfSHddrZkVeEkdICvVT
s62a5VC33GV5OTjh3cM3b/Z3qUbi7qvDEy8DxDwsuyRmBfrceNg2oL2KkoR5
Ow/A5bamZW9Vz2qJ9U2cuG0FXi2clFUADGOIoLTlILvML4Wnv4pCgF4B0N+M
Zlgxefzc/bjHVOwlikS+GYvpVy8YwaumJOvlwatXdm4nvl/6VnXR6ovQjezG
CzbGjFGePAKBFk1riu4GQoopyUWhb/2fytFrB1InhYuFh6RkgMmZe7lNPEuI
axQIPIGPlMdQRgKGtsW+CzrbBW1UmsxtU0j7ZB1HqoQ8RxmP6ViRsk3iIecc
tiHqxrli07CenPbDLaB8TqVdETLkG2NrYE8LHZrAESM4knyH+9VucSSE9k+i
/bmZbNYmHc9uf/fH/fd7b48Zth4ZiXuXtmzb3caycwd/iNu57S+3Y/KDiK6d
khiYvh52Oo/uT+z7kdau1r9lyW+FJ7lq8yGypEVbmp79qyyBbZnsiOJ7yu3v
QQF6k0nDhq7eJuCs3WSD4P9Iakp4ctMLbDPRGBN0EZSe95zNhW01IIMbD2B5
/qi08fY5UalnXstFWV1J1pBrDtBMWR4M/8hoi0FmgF7afhotowuea4tef6W2
JYJWsowwVTtjqmaMkItIGskxSNck+ApjgIiMc3pvQ99kRt1Op6cD9P2xO07S
MYfCsYGQpXCdJc9yid+SfLH9kS8vIDfixYL/6P1JqP64hKrRBt2O5NzWUslE
0UWwJjNcZHOsa2WJIgxz3lNNSZubAE1W5ujwXKXfHAnT6QjKVExIHnsoSCv9
jUMnRM5lf34tLOmwVRSZiOJtBpRtMCAp6tZeFyxx+hlLynJlT+dn1nYdGlJs
FyHZb8jXToutNC++L0yw6YgE34twismqvS3TxYoplMDnD1RMXOWSeodFxTz+
2RrRuJRCSCORsg/z+PKknSzZKp8AVcNPdTwqdRRFepmozCm4OEaf9xy6Qbo4
No7XORfM4/hpT5nQrbwn2OIVfIasMCgqYrTaNrGq6xrNql40sVF+J9SbTJFu
m3ITMFaSR41iab8kq5lzg1Yrbo5Z+GDV3g5HNh+VgFOB1j51FgHHgYn+ymHh
v3oBJb+qv4dZzOfwq7KIKmP+2kKi4P0f+rkEoMamXc6JugG/oo+5fdJTK49W
sTFtK+qVf1Ub610MN+jaj82TlS3+eAjIE3F+919teMKvwkE5gVbVNzRc2xCH
ttqg7ggUAwLdX3X+VuwOOa3cuOPCJlFj1Y35Ejp9sorX53KILnaN5xlEw3Oz
5i3TM6uvZC6beGm0hgXe+blt+gVrhRTj6NkD/oAO8cFnzlnhLJiPDL2gckVm
BA2wFUAfE/KHLW5DMGAvyTRzo8nSLml/iifnvRrxpPdFxZM19d8WVv9H1DzL
N2jRUhmQjEDTTGRgWBGYohwXVpn33wbk/0edb5LEtnyGuH2bVdLdrdall+V7
yTcRT8pJlf0724Id0XQQcIU3Ry3R6YH0ITwJ/W7Y1jYVBbxDjyaANHGSF1FI
mf5pHr5tu0R0SPFlU+S50lHkE22f+Iv0s+xyCBwslgQYvE5pt4O9mZNvM+U2
chhNG0kc93eQOMSqXTKWxO5LpuXiBbv/7v0Px4dvj7SbEEtfW0ESXQbUh3ay
uQ/PV5M80lpZsfAh3do4Sx8N2fFzy6K1IxqMQVrI1d4/3/RfH+zynDnPneu2
Og1zHmB+XeQ/q0MJtGcq8zZqSrliSmkcbypg+LNDjTufjeVMaXWSQjwgnsuG
miVFPEYOQokZddIbOQURS9mFGPZO7rp/FPOrv4HPug3GIiaxnm6AsAACjWpO
5bz912+/sqm3BDClGVa2ovWq1I1Dv0so+qZDZb/QXXgeF+94F66bSV1vZqzK
mSxstebrlLx1LRgLD6kLQGkB0ko0Vc8XBk1UBYf5gGOvIcuu9P3aqIH5vSGK
CGMd6ct932yDkDD9BcZ1iMlsk3NhMV3W8U1euMVenFOJwGt2diV+89CJtxjq
97fkOJxjbDIdRwVWK+TOAiSb1iikRngr85kTlZXP6WJr0/HpwpCVuVsdAxZW
7OOLNpJyIN5n19JP206VYl9YPGBLk+ZEZjjgETirMUezujEjtvA9pc3SkSNO
wByXzsnjs7H3Avrh3FWkoh/F0XjICgWpTmmq/XDkxV9yW2FLKlvk6Ers7oou
c8GdnV3zLzVxbE+nzzG0ww1Q49i0HdmFD9oR4KQ8dfqW0iF+aMhH748PIkiv
Lw4rbkAH6t7eJcoD9kSuFv5Yd4kU4CNpvq67jXXlD3YDYWIqGZ+XjzWXzlAo
rRfLoNcdNLmQVARwM9dZ2vLW5q7KFdxwpreBLgR7DV43iQ1x99OgzhrpTNga
wxhfqIVdzoEYhTLqTat7brZlTXv/6kixCfvoLB9vRRrq/ucWaEcsH4P5xFz4
n9e3pK1ZVkwSrqdTw8dyU7LHiY6UdNiOs0qboxaowhrZYzUAifrdgq/l1nKj
cLJ6SMYH5Y/EuR28refxifP435vX5P6Bc9TZIeTuK2UW8A2WVsA3dakyyzzg
5gE25YTbVux45OQXkYLT93XLtVUNior6BdreOl9CuhSHKTkovVoJCB06xhL6
KDhNqSR3dlOVevnkOY6dozTTqVWLtszdkuwVHLQO4mK5vguW3mbeO7ehI/Jy
MlnfnYBQI0qgm4z2xZOQE/abJuGiNI/oajCeoUvzA/nUC2Xxr+gPfDPBo+Vm
gqWCiUjTPHTYVgDhAy2sDP0sL1a5zBvHTZ1KBMb+8oXEFP75KrGoJl19Yz5S
NVZ1l82UkvN9Lm7lSA5yjE2C6xdIDpW9NebiupV/XV9JUttvpzNssC78j44+
OLKC4LKbrGXAoft28VhldhuqajYcNrJWPw3mY3PeL4VD/I8tlmB+5k956Ean
Ll7XgrHcExmuNm1V9aMzki32ga9JQ20L9+WW7gN1QzCilwO5NrnNvTOhbHkV
Hznrw0/qyNjRgjYYFUMpr12SfksG/cNh/13/n0QMJVDn++A8DS/DxhoA6cEG
5I5GlA3LNfvDdbcoGbirbMrbRp1LGXPiBDiSqGTZQZj4OPFBXLyOx6QaDLpi
dV/7o0sU1ST86CaNJp7OUyZjofWRbdErgBgpCyTdiE1hEg+HYzIA2MAcDniy
sscJzUz2g/cylM1EWWfec+zUr1uUu+0vL+KxLdKCMQ4j9mF1IpIkh47eKycX
t+uQFmE4lKMusbsF/0Qhe9rXq9p3Km/+bSnsqPX47RKPRWDcy0L4CLhwnGLd
V/Wtsd5vP1DpGcYNoFHWqTEhqsxKNvlV9NACoBXcoG5a9zzdXpN40Lko1KVH
ga18QilrWxTZWch1r7tRqgWrCQfWJ5AEg7RvC+m0H+aArkRCZWyxyAoic6aJ
zLSOyJQDK5fTGJ80tcThnsIcmS2RoZOIC14vPNZ3iU99S6OuJmWvTKT61CzM
ROknzD3mYuv/JEmLWi2C6D8MSaqmPLe9UCycLpGY9pzq7L61ZrckLOzyuZi+
+NeD+eSxYiWS2zF5JhhZ1a+u6cSJ34Z0CeYeZSkgXYHWM6JZj1nlE0zN89sa
nMrd547Q5lYR1Whl/Q08Iw/KmYMLdAAZShLVclJckystsuXvWsoP5fPUId9X
enAuJGyO9sNZ07bN/WLkY11fZGtDCi2a/LIEiybH7OaG/mAYjcLZuHCI8hSo
YAZbrR5tVbymfqr9D8vOFn8UIjoHTMvHqnv7lX0ZKmfuEGzRiJUoYOXz5euq
iF5dvq7bJTurXtdNDfYIm+QjPNedMcB+CsezyHr8aPjhnM7awO8tXIiAHsNo
YGkg7o4poOxxmQQ+kWrSd6eBnt+7mc9lWjEy0v3raeTGmuLFvcWe4Biiz2kL
QHJK1MqnMIuTgmPYyf1tOFQr6EWXr3bUCySSKDMaD1vo5TV8GhYputYiLS1F
lXK6JtGVkwu/IbqVGRK73U73ho7mfFgmGA7Wu+V7DspmXKuNq60N9Uwo3BUJ
M38V1x6z8vkmXWjyYfr0h+frTw+ffzC78QchgJVvv50MHL2KDBw9AFj4N920
cmjlczMuoltOp9/mA/WeW4BssDOLZ/v0mS3BuCAvUK8k34mDK1fDZlxeBKqI
mwyXNFcLm2KAiwpocyhZzvDj3TQZzDJKxey7IzFdergR5NgmSLnNHRyB/LFL
gT5ebgVdtu4yQkqdZhOQwlq2UJ1DPS7SJJ1lXm49nv1JKX6mRvzaLuvHdKHj
sOB0Q+U9keReaMUFEmhlRlpV26bn00swmZi00biBwMfZb/1MbtveblWstw3g
MZ2iHQykwB06/C3MSuTqOjnCiTIbWS42k9FCLBKQoGJ2Gs5yjpbPonw2ib4x
clb39ml1Bo8GhGk+r0cDwuSDc6MZ1jxf49A0JSj2eyfaFS6h320szQNe1arb
qFWn01HquzdB12oCbunSCvO8bcPu0p2kaXo/1BDmvTzs3YU1FlLDhIWyj9G1
lWsVyylChnSaOJqZboQym9uGBBY3iKLea7UyE4vdirKmk2+JhUNhsBddFgVZ
EfAdvG4CB8KYC76h5hzrxWlKyATDDpLXCfRUxAMFXYVobCWalos/JQpkKGfm
xr4zaYWfwnhMoR+UQCQiJ000CFE4J1F4nWBpEo6Zy+g8RGoF/SiiqxBdfnA7
1awuo9WqhJ24MjRMz6SQapkUUngo1ixWFNFkivz6mvONnEXXKfG3sIBJzooL
uIv/TFvSKtKPEZAYStlIK0cGo+u96nRXbtgmrXBoOTDdPNRB/02/YrPhhIfp
YEaeWZh2BjgEfRkOdFMEebRxYyf9Ae7DOBqeY4O89ct2MpucIXg8ezAKx3mk
o/VoDqghAJBMc5NW3gxFCVVNzLFUWNCaJqy00OIeZjEmgv/l9eFPwbv9F58/
tx0xIJ+NdflbCvqVWwRuia0cpi12MgLgRwSinVQdgp4P3pzuHx8eBcf7R4fH
p58/d3D+YfIx19l0YGh1mWYfTcIY08cFbArqigAI1Rk5J1PobZy1BDoR8vTH
BgItfF9gYtozjBDOZgkXsiDQjFo2RQ33tI1Rq8xQf1UHCJW4iTpaFW4kn+Ih
u+SUAlUx2HWczoYjjNmhTaB4UfOL8xK/fR0BduHrq+tzvPJNPo1yuPHpF/AF
5iKC1tzHFXzBn+I3+hWIziSL4udhnMIjjCa1v70Os59hMXkUZgDI+BW+wLS9
Vb+5vY1DkMkx6PQME/xm8OtP9K/+ZmUXfcw5hha/AGigqVb/7vYMZ4Oh5Flg
1hYMo0/0bybbTiifzhJucIX9qPK/ZiJ9mGN4FvJUxpM4iQEI4LN4It+/SkHm
/jlVr+XVyusIyMngIvXjYI8ZkBBeoiHi1nfktD8O4wmI2TXY5+IZ5pmG80GM
1wWgEagvovEUyUX/AMA8HecMliHRndZUw1Mxh8jtagJjsVKrggHvUMplZcGs
wN/bIlN+iqPLyMXhTuv/A6IaQv5LWgEA

-->

</rfc>
