<?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 2.6.10) -->
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-evens-moq-fabric-00" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="moq-fabric">Media over QUIC Relay Fabric Protocol</title>
    <seriesInfo name="Internet-Draft" value="draft-evens-moq-fabric-00"/>
    <author initials="T." surname="Evens" fullname="Tim Evens">
      <organization>Cisco</organization>
      <address>
        <email>tievens@cisco.com</email>
      </address>
    </author>
    <date/>
    <area>Web and Internet Transport</area>
    <workgroup>Media Over QUIC</workgroup>
    <keyword>media over quic</keyword>
    <keyword>relay</keyword>
    <keyword>fabric</keyword>
    <abstract>
      <?line 50?>

<t>This document defines moq-fabric, the relay fabric protocol used by Media over QUIC (<xref target="MOQT"/>) relays to exchange node, announce, and subscribe information and to forward objects between relays. The fabric is split into control peering and data peering. Control peering stays established and carries the information bases. Data peering carries objects and <bcp14>MAY</bcp14> be pre-established or opened on demand. The two functions <bcp14>MAY</bcp14> share one QUIC session or use separate sessions. A fabric session uses mutual TLS, together with an <bcp14>OPTIONAL</bcp14> token for authentication and authorization, before the peers exchange fabric state.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://timevens.github.io/draft-evens-moq-fabric/draft-evens-moq-fabric.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-evens-moq-fabric/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Media Over QUIC Working Group 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>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/TimEvens/draft-evens-moq-fabric"/>.</t>
    </note>
  </front>
  <middle>
    <?line 54?>

<section anchor="introduction">
      <name>Introduction</name>
      <t><xref target="MOQT"/> defines how a client publishes and subscribes to tracks at a relay. It leaves the relay-to-relay topology, the information a relay needs about other relays, and the encoding used to move objects between relays unspecified. A deployment that floods every announce and subscribe on the same path used for objects couples control-plane state to the data path and makes traffic engineering, fan-out, and policy enforcement difficult.</t>
      <t>This document specifies moq-fabric. Each relay keeps information bases that describe the nodes it can reach, the tracks that have been announced, and the subscribes that are active. Relays exchange those bases on control peering. They forward object bytes on data peering, using a subscriber node set to say which subscriber relays need the objects. Each hop chooses its own next hop from the node information base.</t>
      <t>Control peering is always on for a peering relationship that exchanges information bases. Data peering <bcp14>MAY</bcp14> already be up, or a relay <bcp14>MAY</bcp14> open it when a forwarding path needs it. One QUIC connection can carry both, or the functions can use different connections. Several data connections <bcp14>MAY</bcp14> exist between the same pair of relays.</t>
      <t>The QUIC handshake authenticates both endpoints with mutual TLS. An <bcp14>OPTIONAL</bcp14> token authenticates and authorizes the session as well, before the peers exchange information bases.</t>
    </section>
    <section anchor="terminology">
      <name>Terminology</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>The terms Client, Server, Publisher, Subscriber, Track, Track Namespace, and Object are imported from <xref target="MOQT"/>.</t>
      <dl>
        <dt>Node:</dt>
        <dd>
          <t>A relay that participates in the fabric. A node has a Node ID, a node type, and a contact address.</t>
        </dd>
        <dt>Node ID:</dt>
        <dd>
          <t>An unsigned 64-bit identifier that is unique among the nodes that exchange information bases.</t>
        </dd>
        <dt>Control peering:</dt>
        <dd>
          <t>A peering function that exchanges information bases. It is kept established for the life of the peering relationship.</t>
        </dd>
        <dt>Data peering:</dt>
        <dd>
          <t>A peering function that forwards objects. It <bcp14>MAY</bcp14> be established before there is anything to send, or opened when a path needs it.</t>
        </dd>
        <dt>Fabric session:</dt>
        <dd>
          <t>One QUIC connection between two nodes, used for control peering, data peering, or both.</t>
        </dd>
        <dt>Origin relay:</dt>
        <dd>
          <t>The Edge node that holds the publisher, or the Edge parent of a Stub that holds the publisher. This document also calls it an o-relay.</t>
        </dd>
        <dt>Subscriber relay:</dt>
        <dd>
          <t>The Edge node that holds the subscriber, or the Edge parent of a Stub that holds the subscriber. This document also calls it an s-relay.</t>
        </dd>
        <dt>Via relay:</dt>
        <dd>
          <t>A node of type Via. This document also calls it a v-relay.</t>
        </dd>
        <dt>Subscriber node set (SNS):</dt>
        <dd>
          <t>The set of subscriber-relay Node IDs that are to receive one flow of objects on a single data session, together with the session-local identifier for that set.</t>
        </dd>
      </dl>
    </section>
    <section anchor="overview">
      <name>Overview</name>
      <t>Relays peer over <xref target="QUIC"/>. A session has one bidirectional stream for fabric control messages. Object bytes use unidirectional streams and QUIC DATAGRAM frames. The application-layer protocol negotiation (ALPN) token is the ASCII string <tt>moq-fabric</tt>.</t>
      <t>Three session modes are negotiated in the first fabric message:</t>
      <table>
        <name>Fabric session modes</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="left">Name</th>
            <th align="left">What the session carries</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">0</td>
            <td align="left">Control</td>
            <td align="left">Information bases. No object payloads.</td>
          </tr>
          <tr>
            <td align="left">1</td>
            <td align="left">Data</td>
            <td align="left">Objects, plus the session-local subscriber node set.</td>
          </tr>
          <tr>
            <td align="left">2</td>
            <td align="left">Both</td>
            <td align="left">Information bases and objects on the same QUIC connection.</td>
          </tr>
        </tbody>
      </table>
      <t>Control peering uses mode Control or mode Both. Data peering uses mode Data or mode Both. A data session still has the bidirectional stream, because that stream carries the connect exchange and the subscriber node set for that session. A data session does not synchronize the information bases of other nodes.</t>
      <section anchor="node-types">
        <name>Relay Types</name>
        <t>The node type is configured for the relay and is advertised with the node. A change of type requires the node to drop its fabric sessions and reconnect so peers learn the new type.</t>
        <table>
          <name>Node types</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
              <th align="left">Behavior</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Via</td>
              <td align="left">Forwards between relays. Does not accept <xref target="MOQT"/> clients.</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Edge</td>
              <td align="left">Accepts <xref target="MOQT"/> clients and peers with Via, Edge, and Stub nodes.</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Stub</td>
              <td align="left">Accepts local clients, dials one or more Edge parents, and does not accept inbound fabric sessions.</td>
            </tr>
          </tbody>
        </table>
        <section anchor="via">
          <name>Via</name>
          <t>A Via node is an aggregation and steering hop. It keeps the node information base so it can choose a next hop. It forwards objects from the subscriber node set on each data session. It does not need the full announce and subscribe tables in order to forward. When a Via sits on the control path, it stores and propagates announce and subscribe information so the information bases can reach Edge nodes that are not directly connected.</t>
          <t>Via nodes are placed where many Edge nodes can share one fan-out. An Edge node uses a Via when a direct mesh would duplicate too much traffic, violate policy, or cross a poor network path.</t>
        </section>
        <section anchor="edge">
          <name>Edge</name>
          <t>An Edge node accepts <xref target="MOQT"/> client sessions and fabric sessions. It is the node that turns a client announce or subscribe into information-base state, and the node that turns received objects back into <xref target="MOQT"/> objects for local subscribers. It computes subscriber node sets for the data sessions it sends on.</t>
          <t>An Edge node <bcp14>MAY</bcp14> sit behind a load balancer or an anycast address. The contact string advertised for the node is the name or address peers use to open a session, which <bcp14>MAY</bcp14> be the load balancer rather than an individual process.</t>
        </section>
        <section anchor="stub">
          <name>Stub</name>
          <t>A Stub node is a lightweight child of one or more Edge parents. It dials those parents, uses session mode Both, and sends objects in both directions on the sessions it opened. That lets a Stub sit behind address translation or a firewall. A Stub does not accept inbound fabric sessions and is not installed in the node information base of any node other than its parents.</t>
          <t>The parent Edge regenerates announce and subscribe state with its own Node ID as the source. Other relays see the parent, not the Stub. A Stub that has many local subscribers still produces one fabric subscribe for a track at the parent. The parent is the s-relay and the o-relay for the rest of the network.</t>
          <t>A client implementation <bcp14>MAY</bcp14> speak this protocol as a Stub instead of opening a <xref target="MOQT"/> session to an Edge. The Edge still presents that client to the rest of the network as its own.</t>
        </section>
      </section>
      <section anchor="relay-roles">
        <name>Relay Roles</name>
        <t>Type and role are different. The type is configured. The role follows the clients attached to an Edge or to a Stub's parent.</t>
        <ul spacing="normal">
          <li>
            <t>An origin relay is the Edge that receives a publish or announce from a publisher, or the Edge parent of the Stub that receives it.</t>
          </li>
          <li>
            <t>A subscriber relay is the Edge that receives a subscribe, or the Edge parent of the Stub that receives it.</t>
          </li>
          <li>
            <t>A Via node does not take either role. It forwards.</t>
          </li>
        </ul>
        <t>One Edge is an origin relay for some tracks and a subscriber relay for others at the same time.</t>
      </section>
      <section anchor="topologies">
        <name>Topologies</name>
        <t>Path selection prefers a direct session from the origin Edge to each subscriber Edge when policy, loss, delay, and fan-out allow it. This is a hub at the origin and a spoke to each subscriber relay.</t>
        <artwork align="center" name="Direct edge-to-edge forwarding"><![CDATA[
Publisher --> Origin Edge --+--> Subscriber Edge --> Subscriber
                            |
                            +--> Subscriber Edge --> Subscriber
]]></artwork>
        <t>When several subscriber Edges share a region, or when the direct path is not allowed, the origin Edge forwards to a Via. The Via splits the same objects toward the subscriber Edges. Further Via hops <bcp14>MAY</bcp14> be added to steer the network path. Via nodes can be added or removed for a track without resetting the publisher's <xref target="MOQT"/> session. An object stream already open on the previous hop drains there, as specified in <xref target="path-change"/>. A new stream and every datagram use the new hop.</t>
        <artwork align="center" name="Forwarding through a Via"><![CDATA[
Publisher --> Origin Edge --> Via --> Subscriber Edge --> Subscriber
                                |
                                +----> Subscriber Edge --> Subscriber
]]></artwork>
      </section>
      <section anchor="end-to-end-example">
        <name>End-to-End Example</name>
        <t>A publisher and a subscriber meet through two Edges. A Stub, when one is present, is hidden behind its parent Edge.</t>
        <ol spacing="normal" type="1"><li>
            <t>The publisher announces at an Edge, or at a Stub. The Edge that owns the publisher originates an announce whose source Node ID is that Edge. A Stub's parent uses its own Node ID, so the rest of the network does not see the Stub. Control peering floods the announce.</t>
          </li>
          <li>
            <t>The subscriber subscribes at an Edge, or at a Stub. That Edge originates one subscribe for the track, again under its own Node ID. Many local clients, including clients of a Stub, collapse to that one subscribe. Control peering carries it toward the origin Edge.</t>
          </li>
          <li>
            <t>The origin Edge matches the subscribe to the announce by the namespace and the full-name hash. It selects a data session toward the subscriber Edge. The session may be direct or may pass through one or more Via nodes.</t>
          </li>
          <li>
            <t>The origin creates a subscriber node set on that data session. The set lists the subscriber Edge. Each hop that receives the set chooses its own next data session and advertises the subset of Node IDs that use that session.</t>
          </li>
          <li>
            <t>Objects follow those data sessions. The header names the set identifier and the full-name hash. The subscriber Edge removes the fabric header and delivers the objects to its local subscriber, or to the Stub on the combined session the Stub opened.</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="fabric-sessions">
      <name>Fabric Sessions</name>
      <section anchor="control-peering">
        <name>Control Peering</name>
        <t>Control peering exchanges the node, announce, and subscribe information bases. It is always on. A node that participates in those bases keeps a control session up to each control peer for as long as that peering relationship exists. The control session does not follow the path objects take. A small set of control sessions, including a redundant session for availability, can serve many data sessions.</t>
        <t>There is one control relationship between two nodes. If both nodes open a session in mode Control or mode Both, the session initiated by the node with the lower Node ID is the control session. The other endpoint closes the extra control session. Data sessions are not limited by this rule.</t>
        <t>When a control session ends, each side removes node, announce, and subscribe state learned only through that session and selects paths again. Object state that belongs to a data session is removed when that data session ends.</t>
        <t>The initiator of a session opens one bidirectional QUIC stream and sends every control message on it. CONNECT is the first message. The acceptor does not open a bidirectional stream. It latches onto the initiator's stream and sends CONNECT_RESPONSE and later control messages on it.</t>
        <t>The initiator <bcp14>MAY</bcp14> open a replacement bidirectional stream. The acceptor keeps using the current control stream until a complete, well-formed control message arrives on the new stream. That message adopts the new stream as the control stream. The acceptor then resets the previous control stream with application error SWITCH_NEW_STREAM when that stream is still open. A new stream whose first complete message is malformed is reset, and the current control stream stays in use. Two control streams are not in use at once. A bidirectional stream that arrives at the initiator, which did not open it, is reset. The initiator continues to use the stream it opened.</t>
      </section>
      <section anchor="data-peering">
        <name>Data Peering</name>
        <t>Data peering forwards object bytes. QUIC streams opened for objects are unidirectional and are opened by the sender. A session <bcp14>MAY</bcp14> carry objects in one direction or in both. Both directions are <bcp14>REQUIRED</bcp14> for a Stub, and for any node that <bcp14>MUST</bcp14> receive return traffic on a connection it opened because of address translation or a firewall. Additional data sessions between the same pair spread object streams across paths that the network can load-balance.</t>
        <t>The bidirectional stream on a data session carries CONNECT, CONNECT_RESPONSE, and the subscriber node set for that session. It does not carry the shared information bases.</t>
        <t>A subscriber node set is meaningful only on the session that will receive the objects. The sender allocates the set identifier. The receiver uses it to choose the next data sessions.</t>
      </section>
      <section anchor="same-session-or-separate-sessions">
        <name>Same Session or Separate Sessions</name>
        <t>Mode Both puts control peering and data peering on one QUIC connection. The information bases and the subscriber node sets share that connection's control stream. Object bytes still use unidirectional streams and datagrams on that connection. A Stub uses this mode.</t>
        <t>Mode Control and mode Data split the functions. The control session stays up and carries the information bases. Each data session is a separate QUIC connection. Object bytes and that session's subscriber node sets stay on the data connection. A node <bcp14>MAY</bcp14> have one control session and zero or more data sessions toward the same peer.</t>
        <artwork align="center" name="Separate sessions and a combined session"><![CDATA[
+-------------------+          +-------------------+
| Control session   |          | One session       |
| (always on)       |          | mode Both         |
| modes: Control    |          | bases and objects |
+-------------------+          +-------------------+
        |                               |
        +--> Data session (pre-set)     +--> objects and bases
        |
        +--> Data session (on demand)
]]></artwork>
      </section>
      <section anchor="pre-established-and-on-demand-data-peering">
        <name>Pre-established and On-demand Data Peering</name>
        <t>Data peering has two establishment styles.</t>
        <ul spacing="normal">
          <li>
            <t>Pre-established. The data session is configured and connected before a subscriber needs it. Path selection can use it immediately. This is appropriate for Via hops and for Edge pairs that exchange objects continuously.</t>
          </li>
          <li>
            <t>On demand. The data session is opened when path selection needs a next hop that has no data session, and it <bcp14>MAY</bcp14> be closed when no subscriber node set still uses it. Control peering is not opened and closed this way.</t>
          </li>
        </ul>
        <t>An implementation <bcp14>MAY</bcp14> use either style, or both. Closing a data session does not withdraw information bases. Closing the control session does.</t>
      </section>
      <section anchor="what-each-session-exchanges">
        <name>What Each Session Exchanges</name>
        <table>
          <name>Messages by session function</name>
          <thead>
            <tr>
              <th align="left">Message family</th>
              <th align="center">Control session</th>
              <th align="center">Data session</th>
              <th align="center">Mode Both</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">CONNECT and response</td>
              <td align="center">yes</td>
              <td align="center">yes</td>
              <td align="center">yes</td>
            </tr>
            <tr>
              <td align="left">Node information base</td>
              <td align="center">yes</td>
              <td align="center">no</td>
              <td align="center">yes</td>
            </tr>
            <tr>
              <td align="left">Announce information base</td>
              <td align="center">yes</td>
              <td align="center">no</td>
              <td align="center">yes</td>
            </tr>
            <tr>
              <td align="left">Subscribe information base</td>
              <td align="center">yes</td>
              <td align="center">no</td>
              <td align="center">yes</td>
            </tr>
            <tr>
              <td align="left">Subscriber node set</td>
              <td align="center">no</td>
              <td align="center">yes</td>
              <td align="center">yes</td>
            </tr>
            <tr>
              <td align="left">Object payloads</td>
              <td align="center">no</td>
              <td align="center">yes</td>
              <td align="center">yes</td>
            </tr>
          </tbody>
        </table>
        <t>CONNECT on every session carries the sender's own node information so the peer can identify the Node ID. That self description is not a dump of the node information base. The dump follows, on a control or both session, after a successful response.</t>
      </section>
    </section>
    <section anchor="information-bases">
      <name>Information Bases</name>
      <t>Information bases are the control-plane state. Nodes advertise entries and withdraw them. A relay also keeps a forwarding information base that it computes locally and does not advertise as a base of its own. The subscriber node set is session state used by data forwarding. It is specified with the bases because it names the subscriber relays that the bases imply.</t>
      <table>
        <name>Information bases and related state</name>
        <thead>
          <tr>
            <th align="left">Base</th>
            <th align="left">Scope</th>
            <th align="left">Contents</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Node (NIB)</td>
            <td align="left">Control peers</td>
            <td align="left">Identity, location, cost, and path of each reachable node</td>
          </tr>
          <tr>
            <td align="left">Announce (AIB)</td>
            <td align="left">Control peers</td>
            <td align="left">Announced namespaces and tracks, with the origin node</td>
          </tr>
          <tr>
            <td align="left">Subscribe (SIB)</td>
            <td align="left">Control peers</td>
            <td align="left">Active subscribes, with the subscriber relay and its parameters</td>
          </tr>
          <tr>
            <td align="left">Forwarding (FIB)</td>
            <td align="left">Local</td>
            <td align="left">Next hop chosen for a node or for an object flow</td>
          </tr>
          <tr>
            <td align="left">Subscriber node set</td>
            <td align="left">One data session</td>
            <td align="left">Session-local id and the set of subscriber relays for one flow</td>
          </tr>
        </tbody>
      </table>
      <section anchor="node-information-base">
        <name>Node Information Base</name>
        <t>The node information base records how to reach other nodes. A node advertises itself with an empty path. A node that forwards an advertisement appends itself to the path. The receiver stores one candidate per peer that advertised a given Node ID and selects one of those candidates as the best next hop.</t>
        <t>An advertisement is sent to a control peer only when all of the following are true:</t>
        <ul spacing="normal">
          <li>
            <t>The peer's Node ID is not the Node ID being advertised.</t>
          </li>
          <li>
            <t>The peer's Node ID does not already appear in the path.</t>
          </li>
          <li>
            <t>The advertisement is new or is better than the candidate already stored from this session.</t>
          </li>
        </ul>
        <t>A withdrawal of a node is propagated when that advertisement was the last remaining way to reach the Node ID. While another session still reaches the node, the withdrawal is not forwarded. Receipt of a withdrawal removes the candidate learned from that session and runs path selection again.</t>
        <t>Stub nodes are not inserted into the node information base beyond their parent.</t>
        <section anchor="node-id">
          <name>Node ID</name>
          <t>Every node that appears in the node information base <bcp14>MUST</bcp14> be configured with a distinct Node ID. When two advertisements carry the same Node ID on different sessions, path selection keeps the better candidate. Operators assign the identifier. A deployment that hashes a host name or a device identifier to fill the 64-bit value <bcp14>MUST</bcp14> ensure the result does not collide inside the fabric.</t>
          <t>The textual form is <tt>&lt;high&gt;:&lt;low&gt;</tt>. The colon is <bcp14>REQUIRED</bcp14>. Each side is an unsigned 32-bit integer in decimal, or two unsigned 16-bit integers separated by a dot. The two styles <bcp14>MAY</bcp14> be mixed.</t>
          <table>
            <name>Node ID textual examples</name>
            <thead>
              <tr>
                <th align="left">Text</th>
                <th align="right">High</th>
                <th align="right">Low</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">
                  <tt>1:1</tt></td>
                <td align="right">1</td>
                <td align="right">1</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>1.2:1234</tt></td>
                <td align="right">0x00010002</td>
                <td align="right">1234</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>100.2:9001.2001</tt></td>
                <td align="right">0x00640002</td>
                <td align="right">0x232907D1</td>
              </tr>
              <tr>
                <td align="left">
                  <tt>123456:789.100</tt></td>
                <td align="right">123456</td>
                <td align="right">0x03150064</td>
              </tr>
            </tbody>
          </table>
          <t>The canonical display form is four decimal 16-bit fields, <tt>high.high:low.low</tt>. Implementations use the 64-bit value on the wire.</t>
        </section>
        <section anchor="node-attributes">
          <name>Node Attributes</name>
          <t>A node advertisement carries:</t>
          <dl>
            <dt>Id:</dt>
            <dd>
              <t>The Node ID, as an unsigned 64-bit integer.</t>
            </dd>
            <dt>Type:</dt>
            <dd>
              <t>The node type from <xref target="node-types"/>.</t>
            </dd>
            <dt>Contact:</dt>
            <dd>
              <t>An octet string that tells a peer how to open a QUIC connection to this node. It is typically a DNS name or an address literal, and it <bcp14>MAY</bcp14> include a port. The contact <bcp14>MAY</bcp14> name a load balancer or an anycast address.</t>
            </dd>
            <dt>Longitude, Latitude:</dt>
            <dd>
              <t>The node location in degrees, as binary64 values. Policy use of these values is deployment-specific.</t>
            </dd>
            <dt>Metric:</dt>
            <dd>
              <t>An unsigned 64-bit cost. Lower sums are preferred. The default node metric is 100. Let <tt>M</tt> be the node metric and <tt>S</tt> the metric configured for one fabric session. The cost advertised on that session, in a self-advertisement and in a path item this node appends, is <tt>max(M, S)</tt>. A session metric lower than or equal to <tt>M</tt> leaves the advertised cost equal to <tt>M</tt>.</t>
            </dd>
            <dt>Path:</dt>
            <dd>
              <t>The ordered list of hops that forwarded this advertisement. Empty when the node advertises itself.</t>
            </dd>
          </dl>
        </section>
        <section anchor="node-path">
          <name>Node Path</name>
          <t>Each path item records the node that forwarded the advertisement, the smoothed round-trip time of the session on which that node received it, and the metric that node advertised on the session that carried the hop.</t>
          <table>
            <name>Node path item</name>
            <thead>
              <tr>
                <th align="left">Field</th>
                <th align="right">Size</th>
                <th align="left">Meaning</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left">Node ID</td>
                <td align="right">8</td>
                <td align="left">Node that appended this item</td>
              </tr>
              <tr>
                <td align="left">SRTT</td>
                <td align="right">8</td>
                <td align="left">Smoothed round-trip time, in microseconds, of the session the advertisement was received on</td>
              </tr>
              <tr>
                <td align="left">Metric</td>
                <td align="right">8</td>
                <td align="left">Metric advertised by that node on the session used for this hop</td>
              </tr>
            </tbody>
          </table>
          <t>The path supports two decisions. A node refuses to forward an advertisement to a Node ID that is already listed, which stops loops. Path selection uses the length of the path, the sum of the metrics, and the sum of the smoothed round-trip times.</t>
          <t>Sum of metrics is the advertised node metric plus the metric in every path item. A direct advertisement has an empty path, so its sum is the node metric alone. Sum of SRTT is the sum of the SRTT fields. A direct advertisement has sum zero.</t>
        </section>
      </section>
      <section anchor="announce-information-base">
        <name>Announce Information Base</name>
        <t>The announce information base records namespaces and tracks that publishers have announced. An Edge or Stub originates an entry when a local publisher announces. The source Node ID is the Edge that owns the publisher. A Stub's parent uses its own Node ID.</t>
        <t>An entry is either a single track or a namespace that covers many tracks. Both kinds carry the namespace tuples. A namespace entry has an empty track name. Receivers index entries by the full-name hash and by successive namespace-tuple hashes so a later subscribe can find a matching announce. The full-name hash is checked against those octets as defined in <xref target="announce-info"/>.</t>
        <t>Announce state is flooded on control peering, subject to policy. A relay <bcp14>MAY</bcp14> drop an announcement on input or on output. A subscriber relay uses the entries it keeps to answer a <xref target="MOQT"/> subscriber and to learn publisher parameters that were conveyed by the local <xref target="MOQT"/> stack. Relays that only forward fabric messages use the hash and the source Node ID.</t>
        <t>A withdrawal is sent when the publisher unannounces. The withdrawal is propagated on control peering the same way as the advertisement. Duplicate advertisements for the same source and full-name hash are not forwarded again.</t>
      </section>
      <section anchor="subscribe-ib">
        <name>Subscribe Information Base</name>
        <t>The subscribe information base records active subscribes. The subscriber relay originates an entry when it accepts a <xref target="MOQT"/> subscribe, or when its Stub child sends one. The source Node ID is that Edge. One entry represents the subscriber relay, not each local client. Many clients on one Edge collapse to one fabric subscribe per track. Different subscribe parameters do not create another entry. A later update replaces the parameters of that same entry.</t>
        <t>Each advertisement and withdrawal of an entry carries a 16-bit epoch and a 16-bit sequence number. The epoch names the counter. The sequence number orders updates of that same counter and is used only to detect a delayed update. Neither value is part of the entry identity. The entry identity is the source Node ID and the track. The source increments the sequence number by one for each update of that entry, wrapping from 65535 to 0, and leaves the epoch unchanged. That wrap is a continuation. A reset is not a wrap. The source increments the epoch by one, wrapping from 65535 to 0, and starts the sequence at 0. Intermediate nodes forward the epoch and the sequence unchanged.</t>
        <t>A receiver stores the epoch and the greatest sequence number it has accepted in that epoch for that source and track. Withdrawing the entry removes the subscribe and updates the forwarding information base, and the receiver keeps that epoch and sequence number while the source is still reachable. Sequence numbers are compared only when the epochs are equal. A later advertisement or withdrawal in the same epoch is accepted only when its sequence number is greater, except for the equal advertisement described below. When a message in the same epoch arrives with a lower sequence number, that message is a delayed update and <bcp14>MUST</bcp14> be ignored, because a greater sequence number was already received. An equal sequence number in the same epoch <bcp14>MUST</bcp14> be ignored while the entry is present, and <bcp14>MUST</bcp14> be ignored after the receiver has accepted a withdrawal for that sequence. This stops a delayed advertisement from restoring a subscribe that was withdrawn. An equal advertisement in the same epoch <bcp14>MUST</bcp14> be accepted when the entry was removed because the source became unreachable and the receiver has not accepted a withdrawal at that sequence. That advertisement resumes the same subscribe. The comparison uses the unsigned distance <tt>(received - stored) mod 65536</tt>. A distance of 1 through 32767 means the received sequence is greater, so after the counter wraps inside the same epoch, 0 is greater than 65535. A distance of 32768 through 65535 means the received sequence is lower. A distance of 0 means the sequences are equal.</t>
        <t>A different epoch is a different counter. The receiver <bcp14>MUST NOT</bcp14> compare its sequence number with the retained sequence. Epoch 1 sequence 0 is not a continuation of epoch 0 sequence 65535, even though the sequence distance from 65535 to 0 is 1. While the receiver retains an epoch, an advertisement or withdrawal with any other epoch <bcp14>MUST</bcp14> be ignored and <bcp14>MUST NOT</bcp14> cancel the retention interval. When the receiver holds no epoch for that source and track, the message is a new baseline and both values are stored.</t>
        <t>When a receiver removes a source Node ID from its node information base and no remaining session reaches that source, the receiver starts a retention interval for the epoch and sequence numbers of that source. The interval is 30 seconds and is not negotiated. The receiver counts those 30 seconds from the moment it removes the source. Receivers do not share a clock. A receiver that removes the source later starts its interval later, and its interval can still be running after another receiver has discarded the same sequences. A withdrawal that leaves the source reachable through another session <bcp14>MUST NOT</bcp14> start an interval and <bcp14>MUST NOT</bcp14> discard the sequences. If that withdrawal never makes the source unreachable, because a newer node advertisement has already installed another session, no interval starts from it.</t>
        <t>While an interval runs, the retained epoch and sequences stay in force. The source becoming reachable again does not cancel the interval and does not move its deadline earlier or later. A greater sequence number in the same epoch means the source continued its counter, including a wrap from 65535 to 0. The receiver <bcp14>MUST</bcp14> cancel the interval and keep that sequence. A different epoch does not. If the interval is not cancelled, the receiver <bcp14>MUST</bcp14> discard the retained epoch and sequences when it ends. The next advertisement for that source is then a new baseline, and its epoch and sequence number are stored even when the counter has started over.</t>
        <t>A source that still has the last epoch and sequence number it sent <bcp14>MUST</bcp14> continue from those values as soon as it returns. It <bcp14>MUST NOT</bcp14> wait, it <bcp14>MUST NOT</bcp14> change the epoch, and it <bcp14>MUST NOT</bcp14> start the sequence over. The age of the saved values does not matter. A continuation uses the same epoch, so a receiver accepts it whether or not that receiver's interval has ended.</t>
        <t>A source that does not have the last epoch and sequence number it sent has reset the counter. It increments the epoch and starts the sequence at 0. It counts its wait from the moment it restarts. Restart is the moment the source is ready to open fabric sessions, not the moment any receiver removes it. There is no bound on how late a node withdrawal can arrive. A receiver can remove the source after the restart, and its retention interval can still be running after any fixed pair of baselines. If those baselines arrived while the old sequence was retained, they were ignored, and nothing remains to be delivered when the interval ends. The source therefore <bcp14>MUST NOT</bcp14> stop after a scheduled number of transmissions.</t>
        <t>The source <bcp14>MUST NOT</bcp14> send a subscribe advertisement or a subscribe withdrawal until 30 seconds after that restart. It <bcp14>MAY</bcp14> send node advertisements during the wait, so receivers can observe that it is back. When the wait ends, the source <bcp14>MUST</bcp14> send the current subscribe state of each entry it still holds. It <bcp14>MUST</bcp14> send that current state again at least once every 30 seconds for as long as the entry exists. Each of those sends is an update in the new epoch: the source increments the sequence number by one even when the parameters are unchanged, and it does not increment the epoch again. An equal retransmission would be ignored by a peer that already has the entry, and that peer would not forward it. A later receiver that had discarded the old sequence would then see nothing. When the source withdraws the entry, it stops this repetition and sends the withdrawal with the next sequence number in that epoch.</t>
        <t>A receiver that still retains the old epoch <bcp14>MUST</bcp14> ignore these updates, whatever their sequence numbers are, and <bcp14>MUST NOT</bcp14> forward them. The modular sequence test does not apply across epochs, so a reset sequence of 0 does not become acceptable merely because the retained sequence is 65535. When that receiver's own interval ends it discards the retained epoch and sequences, however long after the restart that is. It then has no stored epoch. The next of these updates is a new baseline, and the receiver <bcp14>MUST</bcp14> forward it. A receiver that has already accepted the new counter <bcp14>MUST</bcp14> accept the following update, because its sequence number is greater, and <bcp14>MUST</bcp14> forward it. The repetition runs until the entry is withdrawn, so a removal that happens long after the restart is still followed by an update the receiver can accept. A source that has never sent a subscribe sequence is not resetting a counter. It starts at epoch 0 and <bcp14>MAY</bcp14> send the first advertisement immediately, and it does not repeat that advertisement on this timer.</t>
        <t>The entry carries the track hashes, the subscribe parameters, and the namespace and track-name octets. The octets let the origin relay construct the <xref target="MOQT"/> subscribe toward the publisher. Other relays can forward the entry without interpreting the name. A receiver <bcp14>MUST</bcp14> recompute the hashes from the name octets and <bcp14>MUST</bcp14> treat a mismatch as a malformed message.</t>
        <t>Policy <bcp14>MAY</bcp14> filter subscribe advertisements the way it filters announces. An origin relay that never receives a subscribe does not forward objects for it. That is how a deployment keeps a publisher inside a region or a service class.</t>
        <t>On receipt, the origin relay compares the subscribe with the announce information base. Tuple hashes are compared in order. A shorter namespace matches when each of its tuples equals the corresponding tuple of the longer name. An exact track match uses the full-name hash. A match causes the origin relay to subscribe toward the publisher, if it has not already, and to build a subscriber node set toward the source node of the subscribe.</t>
        <t>A withdrawal removes the entry and updates the forwarding information base. The receiver keeps the epoch and sequence number for the retention rules in <xref target="subscribe-ib"/>. The source node sends the withdrawal when its local subscribers for that track are gone.</t>
      </section>
      <section anchor="forwarding-information-base">
        <name>Forwarding Information Base</name>
        <t>The forwarding information base is local. It is not encoded as an information-base message.</t>
        <t>For each remote Node ID the node keeps the fabric session that path selection chose. For each object flow the node keeps the mapping from an ingress subscriber-node-set identifier to the egress session and the egress identifier. A local subscriber is represented by a zero session identifier and a zero set identifier, which means the object is delivered to the <xref target="MOQT"/> stack on this node.</t>
        <t>The table is updated when a node advertisement changes the best session, when a subscribe is added or removed, and when a subscriber node set arrives. An object stream that is already open keeps its previous egress until that stream ends. A new stream, and every datagram, uses the session currently in the table. <xref target="path-change"/> states when forwarding stops.</t>
      </section>
      <section anchor="sns">
        <name>Subscriber Node Set</name>
        <t>The subscriber node set is the data-plane description of who needs a flow. It lists subscriber-relay Node IDs. It does not list the hops between them. Each hop looks those Node IDs up in the node information base and chooses the next data session.</t>
        <t>The sender allocates a 32-bit identifier for the set on the session that will carry the objects. The identifier starts at 1 and increases. It <bcp14>MAY</bcp14> skip values. It wraps to 1 after 4294967294. Zero is reserved and means "no set". The same identifier is updated in place when subscribers are added or removed, so object streams that already cite the identifier stay valid.</t>
        <t>The set is advertised on the control stream of the data session, or of the combined session, that will receive the objects. It is not propagated as an information base. When the receiving node is itself listed, it delivers matching objects to local subscribers, using the full-name hash carried on the object header. For every other Node ID in the set, it builds an egress set toward the chosen next hop and advertises that egress set on that next session.</t>
        <t>A withdrawal retires one identifier on that session. Ending the session retires every identifier learned on it.</t>
        <t>Objects <bcp14>MAY</bcp14> arrive before the set advertisement that names their identifier. The receiver <bcp14>SHOULD</bcp14> hold those objects until the advertisement arrives, and <bcp14>MUST</bcp14> discard them if the session ends or the identifier is withdrawn first.</t>
      </section>
    </section>
    <section anchor="names">
      <name>Names and Hashes</name>
      <t>Namespace tuples and track names are opaque octet strings, in the same order <xref target="MOQT"/> uses. Relays hash them so that forwarding state and object headers stay fixed size.</t>
      <t>The hash function is CityHash64 <xref target="CITYHASH"/> over the octet string. An empty string hashes as CityHash64 of zero octets.</t>
      <t>The namespace hash is computed one tuple at a time, in tuple order. An empty namespace hashes as CityHash64 of zero octets. The hash of the first tuple is CityHash64 of that tuple's octets, so a namespace of one tuple has the same hash as that tuple. Each following tuple updates the hash. The previous hash is encoded as 8 octets in network byte order and placed before the next tuple's octets, and CityHash64 of that sequence replaces the hash:</t>
      <figure>
        <name>Namespace hash</name>
        <artwork><![CDATA[
namespace_hash(tuples):
    if tuples is empty:
        return CityHash64 of zero octets
    h = CityHash64 of the first tuple
    for each following tuple:
        h = CityHash64 of (h as 8 octets, most significant octet first,
                           followed by the tuple octets)
    return h
]]></artwork>
      </figure>
      <t>Each tuple stays on its own boundary. The hash of ("a", "bc") differs from the hash of ("ab", "c"), and the hash of ("a", "b") differs from the hash of ("b", "a").</t>
      <t>The name hash is CityHash64 of the track-name octets. The full-name hash combines those two values, starting from zero:</t>
      <figure>
        <name>Full-name hash</name>
        <artwork><![CDATA[
hash_combine(seed, value):
    seed = seed XOR (value + 0x9e3779b9 + (seed << 6) + (value >> 2))
    all arithmetic is modulo 2^64

full_name_hash = 0
hash_combine(full_name_hash, namespace_hash)
hash_combine(full_name_hash, name_hash)
]]></artwork>
      </figure>
      <t>Prefix matching compares the CityHash64 of each tuple by itself, in order. The chained namespace hash is the namespace input to the full-name hash. A namespace A is a prefix of namespace B when A has no more tuples than B and each tuple hash of A equals the tuple hash of B at the same index.</t>
      <t>CityHash64 has a 64-bit output, so distinct names can share a hash. Recomputing a hash from the octets in the same message and comparing it with the hash field detects a malformed message. Two different names that produce one hash stay one forwarding key.</t>
      <t>The forwarding identity of a track is its full-name hash. Announce entries, subscribe entries, and object delivery match on that hash. Prefix matching matches on tuple hashes. Two different octet strings with the same hash are the same key. A node <bcp14>MUST</bcp14> keep one entry for that hash and <bcp14>MUST</bcp14> handle the announces, subscribes, and objects under it as one track. The name octets travel with announce and subscribe messages so an endpoint can rebuild the <xref target="MOQT"/> name. Forwarding does not use those octets as a second identity.</t>
    </section>
    <section anchor="connection-establishment">
      <name>Connection Establishment</name>
      <section anchor="transport">
        <name>Transport</name>
        <t>The connection uses <xref target="QUIC"/> with the TLS handshake specified by <xref target="QUIC-TLS"/>. Implementations <bcp14>MUST NOT</bcp14> negotiate a TLS version older than TLS 1.3 <xref target="TLS"/>. The ALPN token <bcp14>MUST</bcp14> be <tt>moq-fabric</tt>.</t>
        <t>Either node <bcp14>MAY</bcp14> open the connection. The node that opens it is the initiator and sends CONNECT. The node that accepts it sends CONNECT_RESPONSE.</t>
      </section>
      <section anchor="authentication">
        <name>Authentication</name>
        <t>Authentication and authorization are part of session setup and finish before information bases are exchanged. Every session uses mutual TLS. A deployment <bcp14>MAY</bcp14> also use a token for authentication and authorization. The token is <bcp14>OPTIONAL</bcp14>. When the acceptor's policy does not require one, the mutual TLS identity is sufficient to authorize the session.</t>
        <ul spacing="normal">
          <li>
            <t>Each node presents a certificate in the TLS handshake and <bcp14>MUST</bcp14> authenticate the peer.</t>
          </li>
          <li>
            <t>The initiator <bcp14>MUST NOT</bcp14> send CONNECT until the handshake has completed and the peer certificate has been accepted.</t>
          </li>
          <li>
            <t>The acceptor <bcp14>MUST NOT</bcp14> send fabric messages, and <bcp14>MUST NOT</bcp14> accept CONNECT, until it has authenticated the initiator.</t>
          </li>
          <li>
            <t>A failed mutual TLS authentication closes the QUIC connection. No information-base state is created.</t>
          </li>
          <li>
            <t>When a token is used, the initiator places it in CONNECT. The acceptor checks it before accepting the session. The token <bcp14>MAY</bcp14> identify the peer and <bcp14>MAY</bcp14> authorize the Node ID and the requested session mode.</t>
          </li>
          <li>
            <t>A missing token that the policy requires, a token that fails authentication, or a token that does not authorize the session is rejected with response code Not Authorized. The acceptor then closes the connection. No information-base state is created.</t>
          </li>
        </ul>
        <t>Certificate material is configuration. Fabric messages do not carry certificates or private keys, and implementations <bcp14>MUST NOT</bcp14> embed that material in source. Before use, the certificate <bcp14>MUST</bcp14> satisfy all of the following:</t>
        <ul spacing="normal">
          <li>
            <t>The current time is within the certificate validity period.</t>
          </li>
          <li>
            <t>The signature uses SHA-256 or a stronger hash. MD5 and SHA-1 signatures <bcp14>MUST</bcp14> be rejected.</t>
          </li>
          <li>
            <t>An RSA key is at least 2048 bits. An elliptic-curve key uses P-256 or a stronger curve.</t>
          </li>
          <li>
            <t>The certificate chains to a trust anchor configured for this fabric, or matches a peer credential that was configured explicitly.</t>
          </li>
        </ul>
        <t>A self-signed certificate is suitable only where every peer is configured to trust that exact certificate, such as a laboratory or a closed relay domain. It is not a substitute for a trust anchor on an open network.</t>
        <t>Mutual TLS establishes the peer identity. CONNECT carries the Node ID, the requested session mode, and the <bcp14>OPTIONAL</bcp14> token. The acceptor binds the Node ID to the mutual TLS identity and, when a token is present, to that token. A Node ID that the policy does not allow for that identity is rejected with response code Not Authorized. A requested mode that the policy does not allow is rejected with response code Fabric Mode Not Allowed. The token is an opaque octet string. Its format and the authority that issues it are deployment policy. Implementations <bcp14>MUST NOT</bcp14> embed tokens in source.</t>
        <t>Deployments <bcp14>SHOULD</bcp14> use the key-exchange groups provided by their QUIC stack for TLS 1.3, including a hybrid post-quantum group when the stack and the peer both support one. Signature algorithms and certificate keys remain the ones listed above.</t>
      </section>
      <section anchor="handshake-messages">
        <name>Handshake Messages</name>
        <t>After the QUIC handshake, the initiator opens the control stream and sends CONNECT. The message contains the session mode, the initiator's own node information with an empty path, and the <bcp14>OPTIONAL</bcp14> authentication and authorization token. The acceptor evaluates the mutual TLS identity and that token, then responds with CONNECT_RESPONSE. On success the response contains the acceptor's own node information, again with an empty path. On failure the response contains only the response code, and the acceptor closes the connection.</t>
        <t>A control session or a mode Both session then synchronizes state. Each side sends the node, announce, and subscribe entries it is willing to advertise to that peer. The two directions are independent and <bcp14>MAY</bcp14> occur in either order. A data session does not send that synchronization. It sends subscriber node sets later, as object flows are created.</t>
        <artwork align="center" name="Session setup"><![CDATA[
Initiator                         Acceptor
   |                                 |
   |-------- QUIC + mutual TLS ----->|
   |                                 |
   |-------- CONNECT --------------->|  OPTIONAL token
   |<------- CONNECT_RESPONSE -------|
   |                                 |
   |==== information bases =========>|   (Control or Both only)
   |<=== information bases ==========|
]]></artwork>
      </section>
    </section>
    <section anchor="path-selection">
      <name>Path Selection</name>
      <t>For each Node ID, the node compares the candidates advertised by its sessions. The first of these tests that differs chooses the candidate:</t>
      <ol spacing="normal" type="1"><li>
          <t>Lower selection cost. The cost is the sum of metrics carried in the advertisement, plus <tt>max(0, S - M)</tt> for the session that would be the next hop. <tt>M</tt> is the selecting node's metric and <tt>S</tt> is the metric configured on that next-hop session. Each metric inside the sum is the advertised cost written by the node that sent that hop, the greater of that node's metric and the session metric it used. When <tt>S</tt> is lower than or equal to <tt>M</tt>, the added term is zero.</t>
        </li>
        <li>
          <t>Fewer path items.</t>
        </li>
        <li>
          <t>Lower sum of smoothed round-trip times.</t>
        </li>
      </ol>
      <t>When all three are equal, the node keeps the candidate it already selected. A repeated advertisement does not move existing object streams.</t>
      <t>Changing a session metric recomputes the affected paths and re-advertises the local node, and the other nodes known on that session, with the new cost.</t>
      <t>The inputs available to selection grow over time. Load, geographic policy, and reachability probes can refine the metric that a node advertises. This document fixes the comparison order so those refinements have a stable effect: they change the metric or the measured delay, and every node applies the same three tests.</t>
    </section>
    <section anchor="data-forwarding">
      <name>Data Forwarding</name>
      <t>Objects move from the origin relay to each subscriber relay. Intermediate Via nodes do not parse <xref target="MOQT"/> object payloads. They read the fabric header, look up the subscriber node set, and write the same payload bytes on the next sessions. The origin and subscriber relays are the points that convert between <xref target="MOQT"/> and this encapsulation.</t>
      <t>The origin relay builds one subscriber node set per egress data session. The set contains the subscriber relays whose best path uses that session. The origin then sends the objects on that session with the set identifier in the fabric header.</t>
      <t>A Via or Edge that receives the set splits it. Node IDs that share the same next hop are placed in one egress set. The egress set is advertised on that next session with a new session-local identifier, and the node records the mapping from the ingress identifier to that egress identifier. If the node's own Node ID is in the set, the full-name hash in the object header selects the local <xref target="MOQT"/> subscribers. The fabric header is removed before those bytes are handed to <xref target="MOQT"/>.</t>
      <artwork align="center" name="Subscriber node sets along one flow"><![CDATA[
Publisher
   |  MOQT objects
   v
Origin Edge
   |  SNS 1 = { s-relay A, s-relay B }
   v
Via
   |  SNS 7 = { s-relay A }          SNS 8 = { s-relay B }
   +----------------+----------------+
   v                                 v
s-relay A                          s-relay B
   |  MOQT objects                    |  MOQT objects
   v                                  v
Subscribers                        Subscribers
]]></artwork>
      <section anchor="pipeline-forwarding">
        <name>Pipeline Forwarding</name>
        <t>Datagram objects are forwarded as whole datagrams. A datagram that does not fit the next hop is dropped. This protocol does not fragment datagrams. Publishers that need to cross a smaller maximum transmission unit send objects on streams, or send datagrams that fit the smallest hop.</t>
        <t>A stream is pipelined. The first bytes of a new unidirectional stream carry a fabric header. Every following byte on that stream is payload and is written through without a further fabric header. A relay does not reassemble the <xref target="MOQT"/> object before forwarding. Reassembly is the subscriber's job, and the job of a relay that has chosen to cache. A caching relay acts as a <xref target="MOQT"/> subscriber and publisher on that track.</t>
        <t>A new <xref target="MOQT"/> group or subgroup arrives as a new QUIC stream. The relay mirrors that transition: the new stream gets a new fabric header, and the previous stream ends. One active fabric stream represents the current stream for that flow on a session.</t>
        <t>The time-to-live in a new-stream header applies to the objects on that stream. The timer for an object starts when the object is received. The priority in that header is the priority of the egress QUIC stream and the priority offered to local <xref target="MOQT"/> subscribers.</t>
      </section>
      <section anchor="opening-a-flow">
        <name>Opening a Flow</name>
        <t>When the origin relay has both a publisher and at least one matching subscribe, it:</t>
        <ol spacing="normal" type="1"><li>
            <t>Groups the subscriber relays by the data session path selection chose.</t>
          </li>
          <li>
            <t>Allocates a subscriber node set identifier on each of those sessions and advertises the set.</t>
          </li>
          <li>
            <t>Sends object bytes with that identifier in the header.</t>
          </li>
        </ol>
        <t>A later subscribe that uses an existing session is added to the existing set, under the same identifier. A subscribe that is the last one on a session withdraws the identifier.</t>
      </section>
      <section anchor="path-change">
        <name>Path Changes and Stopped Flows</name>
        <t>An open object stream stays on the egress session that accepted it. A datagram and a new stream use the session path selection has chosen now. The node does not open a replacement stream for bytes already in flight. The next <xref target="MOQT"/> group or subgroup is a new stream and takes the new path.</t>
        <t>Forwarding of new objects toward a subscriber stops when that subscriber is removed from the set, when its subscribe is withdrawn, or when the egress session is no longer the selected next hop. If that egress has no open stream for the flow, the node drops the egress at once. When the set no longer names any subscriber on that session, the node withdraws the subscriber node set identifier there. If the egress still has an open stream, the node marks the egress draining. Bytes that continue that stream are still written. A datagram or a new stream skips a draining egress. When the stream ends, the node drops the egress and withdraws the set identifier if no subscriber remains on it.</t>
        <t>A subscriber node set withdrawal retires that identifier. The receiver stops forwarding new objects for it, finishes the streams it opened for that set, and discards objects it was holding for the identifier. An identifier that has been withdrawn, or that was never advertised on the session, is stale. The receiver <bcp14>MUST</bcp14> discard objects that cite a stale identifier, and it <bcp14>MUST NOT</bcp14> create an egress for one. Objects that arrive before the first advertisement of an identifier are the case in <xref target="sns"/>: they are held, and they are discarded if the session ends or the identifier is withdrawn first.</t>
        <t>If the egress session fails before a draining stream ends, the stream ends with the session. The node removes that egress and every set identifier learned on the session. It does not rebuild the interrupted stream. A later new stream uses a session that path selection still considers available.</t>
      </section>
    </section>
    <section anchor="message-encoding">
      <name>Message Encoding</name>
      <t>Octets are sent in network byte order. Unless a field states otherwise, multi-byte integers are unsigned and big-endian. A binary64 value is the IEEE 754 encoding of that floating-point number, also big-endian.</t>
      <t>Diagrams name a field and the size in octets. <tt>varint</tt> is the variable-length integer defined in <xref target="varint"/>. A field in brackets is present only when the condition in the text is met. A repeated field continues until the enclosing message length is exhausted, unless a count is given.</t>
      <section anchor="varint">
        <name>Variable-Length Integers</name>
        <t>A varint <bcp14>MUST</bcp14> use the variable-length integer encoding in <xref section="8.1" sectionFormat="comma" target="MOQT"/>. The number of leading 1 bits in the first octet gives the length. An encoding is one to nine octets and represents an unsigned integer of up to 64 bits. A sender <bcp14>MAY</bcp14> use any encoding length that can represent the value. A receiver <bcp14>MUST</bcp14> accept any such encoding.</t>
      </section>
      <section anchor="common-header">
        <name>Common Header</name>
        <t>Every control message begins with this header. Object payloads do not.</t>
        <figure>
          <name>Common header</name>
          <artwork><![CDATA[
Common Header {
  Protocol Version (1) = 1,
  Message Type (2),
  Message Length (4),
}
]]></artwork>
        </figure>
        <t>Protocol Version is 1. A receiver that does not support the version <bcp14>MUST</bcp14> close the connection.</t>
        <t>Message Length is the number of octets after the header. It does not include the seven header octets. A receiver assembles a message by reading the header and then exactly Message Length octets. Control messages are concatenated on the bidirectional stream.</t>
      </section>
      <section anchor="message-types">
        <name>Message Types</name>
        <table>
          <name>Control message types</name>
          <thead>
            <tr>
              <th align="right">Type</th>
              <th align="left">Name</th>
              <th align="left">Carried on</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="right">1</td>
              <td align="left">CONNECT</td>
              <td align="left">Control stream, first from initiator</td>
            </tr>
            <tr>
              <td align="right">2</td>
              <td align="left">CONNECT_RESPONSE</td>
              <td align="left">Control stream, first from acceptor</td>
            </tr>
            <tr>
              <td align="right">3</td>
              <td align="left">DATA_OBJECT</td>
              <td align="left">Reserved. Not sent as a control message.</td>
            </tr>
            <tr>
              <td align="right">4</td>
              <td align="left">NODE_INFO_ADV</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">5</td>
              <td align="left">NODE_INFO_WD</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">6</td>
              <td align="left">SUBSCRIBE_INFO_ADV</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">7</td>
              <td align="left">SUBSCRIBE_INFO_WD</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">8</td>
              <td align="left">ANNOUNCE_INFO_ADV</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">9</td>
              <td align="left">ANNOUNCE_INFO_WD</td>
              <td align="left">Control or Both session</td>
            </tr>
            <tr>
              <td align="right">10</td>
              <td align="left">SUBSCRIBE_NODE_SET_ADV</td>
              <td align="left">Data session, or Both session</td>
            </tr>
            <tr>
              <td align="right">11</td>
              <td align="left">SUBSCRIBE_NODE_SET_WD</td>
              <td align="left">Data session, or Both session</td>
            </tr>
          </tbody>
        </table>
        <t>Message type 0, message type 3, and any type that is not assigned in the table are unknown. An unknown type is a connection error, application error INVALID_CTRL_MSG_TYPE.</t>
      </section>
      <section anchor="node-info">
        <name>Node Information</name>
        <t>Node information is embedded in CONNECT and CONNECT_RESPONSE and is the body of the node advertisement and withdrawal messages. The path occupies whatever remains of the enclosing length. The number of path items is that remainder divided by 24. A remainder that is not a multiple of 24 is a malformed message.</t>
        <figure>
          <name>Node information</name>
          <artwork><![CDATA[
Node Info {
  Node ID (8),
  Node Type (1),
  Contact Length (varint),
  Contact (..),
  Longitude (8),
  Latitude (8),
  Metric (8),
  Path Item (..) ...,
}

Path Item {
  Node ID (8),
  SRTT Microseconds (8),
  Metric (8),
}
]]></artwork>
        </figure>
        <t>Node Type is a value from <xref target="node-types"/>. Any other value is malformed. An unknown type in CONNECT is rejected with response code Connect Error, and the acceptor then closes the connection. An unknown type in CONNECT_RESPONSE makes the initiator close the connection, and no information-base state is created. An unknown type in a node advertisement or withdrawal is a connection error, application error INVALID_ENCODING. Contact Length is a <xref target="varint"/> count of the following octets.</t>
      </section>
      <section anchor="connect">
        <name>CONNECT</name>
        <t>CONNECT is the first message on the control stream. Any other first message is a connection error.</t>
        <figure>
          <name>CONNECT</name>
          <artwork><![CDATA[
CONNECT Message {
  Common Header (type = 1),
  Peer Mode (1),
  Token Present (1),
  [Token Length (varint),
   Token (..)],
  Node Info (..),
}
]]></artwork>
        </figure>
        <t>Peer Mode is a value from the session mode table. Any other value is rejected with response code Fabric Mode Not Allowed, and the acceptor then closes the connection. Token Present is 1 when a token follows and 0 when mutual TLS alone is used. Any other value is a malformed message. Token Length is a <xref target="varint"/> count of the following token octets. The token is opaque. Node Info describes the initiator and has an empty path. The token fields come before Node Info so the node path can still occupy the remainder of the message.</t>
      </section>
      <section anchor="connectresponse">
        <name>CONNECT_RESPONSE</name>
        <t>CONNECT_RESPONSE is the first message the acceptor sends. Creating a unidirectional stream before it arrives is a connection error.</t>
        <figure>
          <name>CONNECT_RESPONSE</name>
          <artwork><![CDATA[
CONNECT_RESPONSE Message {
  Common Header (type = 2),
  Response Code (2),
  [Node Info (..)],
}
]]></artwork>
        </figure>
        <t>Node Info is present only when Response Code is 0. It describes the acceptor and has an empty path.</t>
        <table>
          <name>Response codes</name>
          <thead>
            <tr>
              <th align="right">Code</th>
              <th align="left">Name</th>
              <th align="left">Meaning</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="right">0</td>
              <td align="left">No Error</td>
              <td align="left">The session is accepted.</td>
            </tr>
            <tr>
              <td align="right">1</td>
              <td align="left">Connect Error</td>
              <td align="left">The connect request cannot be completed.</td>
            </tr>
            <tr>
              <td align="right">2</td>
              <td align="left">Not Authorized</td>
              <td align="left">The authenticated identity is not allowed.</td>
            </tr>
            <tr>
              <td align="right">3</td>
              <td align="left">Fabric Mode Not Allowed</td>
              <td align="left">The requested session mode is not allowed.</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="node-advertisement-and-withdrawal">
        <name>Node Advertisement and Withdrawal</name>
        <figure>
          <name>Node information messages</name>
          <artwork><![CDATA[
NODE_INFO_ADV Message {
  Common Header (type = 4),
  Node Info (..),
}

NODE_INFO_WD Message {
  Common Header (type = 5),
  Node Info (..),
}
]]></artwork>
        </figure>
        <t>The withdrawal carries the same structure so the receiver can drop the matching candidate, including an inferior path, rather than every candidate for that Node ID. The path in a withdrawal is the path of the candidate being removed.</t>
      </section>
      <section anchor="subscribe-information">
        <name>Subscribe Information</name>
        <figure>
          <name>Subscribe information messages</name>
          <artwork><![CDATA[
SUBSCRIBE_INFO_ADV Message {
  Common Header (type = 6),
  Epoch (2),
  Sequence (2),
  Source Node ID (8),
  Namespace Hash (8),
  Name Hash (8),
  Full Name Hash (8),
  Priority (1),
  Delivery Timeout (8),
  Expires (8),
  Forward (8),
  New Group Present (1),
  [New Group Request ID (8)],
  Track Name (..),
}

SUBSCRIBE_INFO_WD Message {
  Common Header (type = 7),
  Epoch (2),
  Sequence (2),
  Source Node ID (8),
  Namespace Hash (8),
  Name Hash (8),
  Full Name Hash (8),
  Priority (1),
  Delivery Timeout (8),
  Expires (8),
  Forward (8),
  New Group Present (1),
  [New Group Request ID (8)],
  Track Name (..),
}
]]></artwork>
        </figure>
        <t>Epoch names the counter and Sequence is the delayed-update counter inside that epoch, as defined in <xref target="subscribe-ib"/>. A continuation leaves Epoch unchanged, including when Sequence wraps from 65535 to 0. A reset increments Epoch and starts Sequence at 0. Source Node ID is the subscriber relay. The three hashes are defined in <xref target="names"/>. Priority is the subscriber's priority. Delivery Timeout and Expires are milliseconds. Zero means the parameter is unset. Forward is zero to pause forwarding and non-zero to forward. New Group Present is 1 when New Group Request ID follows and 0 when it does not. Any other value is a malformed message.</t>
        <figure anchor="track-name">
          <name>Track name</name>
          <artwork><![CDATA[
Track Name {
  Tuple Count (1),
  Tuple Length (2),
  Tuple Octets (..),
  ...
  Name Length (2),
  Name Octets (..),
}
]]></artwork>
        </figure>
        <t>Tuple Count is the number of namespace tuples. Each tuple is a 16-bit length and that many octets. Name Length is a 16-bit length of Name Octets. Zero means those octets are empty. Tuple Count and the lengths <bcp14>MUST</bcp14> fit in the message. A count or length that runs past Message Length is a malformed message. Subscribe and announce messages use this same structure.</t>
      </section>
      <section anchor="announce-info">
        <name>Announce Information</name>
        <figure>
          <name>Announce information messages</name>
          <artwork><![CDATA[
ANNOUNCE_INFO_ADV Message {
  Common Header (type = 8),
  Source Node ID (8),
  Full Name Hash (8),
  Track Name (..),
  Flags (1),
}

ANNOUNCE_INFO_WD Message {
  Common Header (type = 9),
  Source Node ID (8),
  Full Name Hash (8),
  Track Name (..),
  Flags (1),
}
]]></artwork>
        </figure>
        <t>Source Node ID is the origin relay. Track Name is the structure in <xref target="track-name"/>. It carries the namespace tuples and the track-name octets for an advertisement and for a withdrawal. Full Name Hash is the full-name hash defined in <xref target="names"/>. The message does not carry the namespace hash or the name hash. The receiver derives both from Track Name.</t>
        <t>Bit 0 of Flags selects the kind. Zero is a single track. One is a namespace. All other flag bits <bcp14>MUST</bcp14> be sent as zero and <bcp14>MUST</bcp14> be ignored on receipt.</t>
        <t>A track announcement uses Name Octets as the track name. Name Length <bcp14>MAY</bcp14> be zero, and the announcement is still a track. A namespace announcement covers the tracks in the namespace given by the tuples. Its Name Length <bcp14>MUST</bcp14> be zero, and Name Octets <bcp14>MUST</bcp14> be empty. A namespace announcement with a non-zero Name Length is a malformed message.</t>
        <t>The receiver <bcp14>MUST</bcp14> recompute the full-name hash from Track Name and <bcp14>MUST</bcp14> treat a mismatch with Full Name Hash as a malformed message. The namespace hash and the name hash are the values defined in <xref target="names"/>. The name hash is CityHash64 of Name Octets, which is the hash of zero octets when Name Length is zero. The same check applies to a track announcement, a namespace announcement, an advertisement, and a withdrawal.</t>
      </section>
      <section anchor="subscriber-node-set">
        <name>Subscriber Node Set</name>
        <figure>
          <name>Subscriber node set messages</name>
          <artwork><![CDATA[
SUBSCRIBE_NODE_SET_ADV Message {
  Common Header (type = 10),
  SNS ID (4),
  Priority (1),
  Node Count (2),
  Node ID (8) ...,
}

SUBSCRIBE_NODE_SET_WD Message {
  Common Header (type = 11),
  SNS ID (4),
}
]]></artwork>
        </figure>
        <t>SNS ID is the session-local identifier. Priority is the priority to apply to the flow. Node Count is the number of following Node IDs. The list is a set: order is not significant, and a sender <bcp14>MUST NOT</bcp14> repeat a Node ID. The receiver looks up each Node ID in the node information base. Node IDs that are not known are kept with the set until a later node advertisement makes a next hop available, or until the set is withdrawn.</t>
      </section>
      <section anchor="data-headers">
        <name>Data Headers</name>
        <t>Object bytes are carried in QUIC DATAGRAM frames and on unidirectional streams. They are not carried on the bidirectional control stream.</t>
        <t>A datagram and the first bytes of a new stream start with a data header. Header Length counts every octet of the header, including itself. The payload starts at that offset. Header Length <bcp14>MUST NOT</bcp14> exceed 255, and for the types defined here it is 14 for a datagram and 19 for a new stream.</t>
        <figure>
          <name>Data header</name>
          <artwork><![CDATA[
Data Header {
  Header Length (1),
  Data Type (1),
  ... type-specific fields ...,
}
]]></artwork>
        </figure>
        <table>
          <name>Data types</name>
          <thead>
            <tr>
              <th align="right">Type</th>
              <th align="left">Name</th>
              <th align="right">Header length</th>
              <th align="left">Use</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="right">0</td>
              <td align="left">DATAGRAM</td>
              <td align="right">14</td>
              <td align="left">One datagram object.</td>
            </tr>
            <tr>
              <td align="right">1</td>
              <td align="left">EXISTING_STREAM</td>
              <td align="right">none</td>
              <td align="left">Not a wire value. A received header with this type is an error.</td>
            </tr>
            <tr>
              <td align="right">2</td>
              <td align="left">NEW_STREAM</td>
              <td align="right">19</td>
              <td align="left">First bytes of a unidirectional stream.</td>
            </tr>
          </tbody>
        </table>
        <section anchor="datagram">
          <name>Datagram</name>
          <figure>
            <name>Datagram object</name>
            <artwork><![CDATA[
DATAGRAM {
  Header Length (1) = 14,
  Data Type (1) = 0,
  SNS ID (4),
  Full Name Hash (8),
  Payload (..),
}
]]></artwork>
          </figure>
          <t>The payload is the remainder of the QUIC datagram. SNS ID selects the subscriber node set on this session. Full Name Hash selects local subscribers when this node is in the set.</t>
        </section>
        <section anchor="new-stream">
          <name>New Stream</name>
          <t>A unidirectional stream <bcp14>MUST</bcp14> begin with NEW_STREAM. A stream that does not is reset. The header is not repeated. Every octet after the header, on that stream, is payload.</t>
          <figure>
            <name>New stream header</name>
            <artwork><![CDATA[
NEW_STREAM {
  Header Length (1) = 19,
  Data Type (1) = 2,
  SNS ID (4),
  Full Name Hash (8),
  Priority (1),
  TTL Milliseconds (4),
  Payload (..),
}
]]></artwork>
          </figure>
          <t>Priority is the QUIC priority of the egress streams created from this stream. TTL Milliseconds is the object lifetime described in <xref target="pipeline-forwarding"/>.</t>
        </section>
        <section anchor="existing-stream-bytes">
          <name>Existing Stream Bytes</name>
          <t>After NEW_STREAM, further payload on the same QUIC stream is sent with no fabric header. The SNS ID, full-name hash, priority, and time-to-live stay those of the NEW_STREAM header that opened the stream. An implementation classifies those bytes as existing-stream data locally. It does not put Data Type 1 on the wire. A stream whose first header has a Data Type other than 2, including type 1, is reset with application error INVALID_START_OF_STREAM. A datagram whose Data Type is not 0 is discarded.</t>
        </section>
      </section>
    </section>
    <section anchor="error-handling">
      <name>Error Handling</name>
      <t>Transport failures and protocol violations close the QUIC connection or reset the offending stream, using an application error code.</t>
      <table>
        <name>QUIC application error codes</name>
        <thead>
          <tr>
            <th align="right">Code</th>
            <th align="left">Name</th>
            <th align="left">Where</th>
            <th align="left">Meaning</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="right">1</td>
            <td align="left">CLOSE</td>
            <td align="left">Connection</td>
            <td align="left">The endpoint is closing the session.</td>
          </tr>
          <tr>
            <td align="right">2</td>
            <td align="left">REDIRECT</td>
            <td align="left">Connection</td>
            <td align="left">The peer <bcp14>SHOULD</bcp14> move to another relay.</td>
          </tr>
          <tr>
            <td align="right">8</td>
            <td align="left">NOT_AUTHORIZED</td>
            <td align="left">Connection</td>
            <td align="left">Authentication or policy refused the peer.</td>
          </tr>
          <tr>
            <td align="right">32</td>
            <td align="left">CONNECT_MISSING</td>
            <td align="left">Connection</td>
            <td align="left">The first control message was not CONNECT.</td>
          </tr>
          <tr>
            <td align="right">33</td>
            <td align="left">CONNECT_RESP_MISSING</td>
            <td align="left">Connection</td>
            <td align="left">A unidirectional stream was opened before CONNECT_RESPONSE.</td>
          </tr>
          <tr>
            <td align="right">34</td>
            <td align="left">INVALID_CTRL_MSG_TYPE</td>
            <td align="left">Connection</td>
            <td align="left">The message type is unknown.</td>
          </tr>
          <tr>
            <td align="right">35</td>
            <td align="left">INVALID_ENCODING</td>
            <td align="left">Connection or stream</td>
            <td align="left">A length, version, or field is malformed.</td>
          </tr>
          <tr>
            <td align="right">36</td>
            <td align="left">INVALID_START_OF_STREAM</td>
            <td align="left">Stream</td>
            <td align="left">A new stream did not start with NEW_STREAM.</td>
          </tr>
          <tr>
            <td align="right">128</td>
            <td align="left">SWITCH_NEW_STREAM</td>
            <td align="left">Stream</td>
            <td align="left">The acceptor reset the previous control stream.</td>
          </tr>
        </tbody>
      </table>
      <t>A CONNECT_RESPONSE with a non-zero response code refuses the session. An unknown response code is a refusal as well. The initiator closes the connection and creates no information-base state. The acceptor closes the connection after sending a non-zero code. Response code 2 corresponds to a peer that completed mutual TLS and then failed token authentication, token authorization, or the Node ID policy. A TLS failure does not produce CONNECT_RESPONSE, because CONNECT is not sent when the handshake fails.</t>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <section anchor="redirecting-clients">
        <name>Redirecting Clients</name>
        <t>Source routing by subscriber node set works best when subscribers to the same track share Edge nodes. A load balancer that spreads those subscribers across many Edges enlarges the set. An Edge that sees the same subscribe on a nearby Edge <bcp14>MAY</bcp14> redirect the <xref target="MOQT"/> client with GOAWAY and a new connection URL, when capacity allows. The information bases provide the subscribe and node data for that decision.</t>
      </section>
      <section anchor="subscribe-churn">
        <name>Subscribe Churn</name>
        <t>A subscriber that leaves and rejoins quickly would otherwise withdraw and re-advertise a subscribe across the control plane. A subscriber relay <bcp14>SHOULD</bcp14> delay a withdrawal for a short local interval. If the client subscribes to the same track again before the interval ends, the relay cancels the withdrawal. The delay is a local timer. It is not negotiated and <bcp14>MUST</bcp14> be bounded so a departed subscriber does not keep receiving objects for long. Five seconds is a reasonable default.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>Mutual TLS, as specified in <xref target="authentication"/>, authenticates every fabric session. An <bcp14>OPTIONAL</bcp14> token in CONNECT provides additional authentication and authorization. A node that skips verification of the peer certificate accepts a session from any endpoint that completes the handshake and can then inject node, announce, and subscribe state. Implementations <bcp14>MUST</bcp14> authenticate the peer before CONNECT. A token is a credential. Implementations <bcp14>MUST NOT</bcp14> log it, and they <bcp14>MUST</bcp14> treat a missing or rejected token as Not Authorized when local policy requires one.</t>
      <t>The certificate checks in <xref target="authentication"/> exclude expired credentials, weak public keys, and MD5 or SHA-1 signatures. Trust anchors and any explicitly trusted self-signed certificates are deployment configuration. A self-signed certificate used beyond a closed domain will not be accepted by a peer that requires a chain to a known anchor.</t>
      <t>The authenticated identity is bound to the Node ID in CONNECT. Without that binding, a peer that holds a valid certificate could advertise a Node ID it does not own and attract object flows. Policy at the acceptor enforces the binding and returns Not Authorized when it fails.</t>
      <t>The name hashes in <xref target="names"/> are 64-bit CityHash64 forwarding keys. A collision merges two names into one fabric track, so objects for one name can be delivered on the subscribe state of the other. A peer that is allowed to choose track names can attempt that collision. The hash check on a subscribe or an announce accepts the message when the hash field matches the octets in that same message. A second name that hashes to a key already in use joins that same track.</t>
      <t>Control peering distributes the names of tracks and the identities of the relays that publish or subscribe. Filtering announce and subscribe advertisements is the mechanism that keeps a track inside a region or a customer boundary. A missing filter is a data leak, because an origin relay that learns a subscribe will forward objects toward that subscriber relay.</t>
      <t>Object payloads are opaque to intermediate relays and are protected by the QUIC session on each hop. This protocol does not add a second encryption layer. End-to-end confidentiality and integrity of <xref target="MOQT"/> objects are the responsibility of the application and of <xref target="MOQT"/>, not of the fabric encapsulation. Each hop can read the payload bytes it forwards.</t>
      <t>The subscriber node set tells a data peer which Edge nodes receive a flow. That is visible to every hop on the data path. Deployments that treat the set of receivers as sensitive keep data sessions inside the same trust domain that already carries the objects.</t>
      <t>An implementation <bcp14>MUST</bcp14> bound the memory used for information bases, for subscriber node sets, and for objects that arrive before their set advertisement. An unbounded buffer is a denial-of-service vector.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="alpn-identification">
        <name>ALPN Identification</name>
        <t>IANA is requested to add the following entry to the "TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs" registry:</t>
        <table>
          <name>ALPN identification</name>
          <thead>
            <tr>
              <th align="left">Protocol</th>
              <th align="left">Identification Sequence</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Media over QUIC Relay Fabric Protocol</td>
              <td align="left">
                <tt>moq-fabric</tt></td>
              <td align="left">This document</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="fabric-registries">
        <name>Fabric Registries</name>
        <t>IANA is requested to create a "MOQ Relay Fabric" registry group containing the registries below. New registrations in each registry use the Specification Required policy <xref target="RFC8126"/>.</t>
        <section anchor="iana-message-types">
          <name>Message Type Registry</name>
          <t>The registry covers the 16-bit message type in the common header. Values 0 and 12 through 65535 are unassigned. Values 1 through 11 are assigned by <xref target="message-types"/>.</t>
        </section>
        <section anchor="session-modes">
          <name>Session Modes</name>
          <t>The registry covers the 8-bit peer mode in CONNECT. Values 0, 1, and 2 are assigned by the session mode table. Values 3 through 255 are unassigned.</t>
        </section>
        <section anchor="iana-node-types">
          <name>Node Type Registry</name>
          <t>The registry covers the 8-bit node type. Values 0, 1, and 2 are assigned by <xref target="node-types"/>. Values 3 through 255 are unassigned.</t>
        </section>
        <section anchor="response-codes">
          <name>Response Codes</name>
          <t>The registry covers the 16-bit response code in CONNECT_RESPONSE. Values 0 through 3 are assigned by the response code table. Values 4 through 65535 are unassigned.</t>
        </section>
        <section anchor="quic-application-error-codes">
          <name>QUIC Application Error Codes</name>
          <t>The registry covers the application error codes used with this ALPN. The values in the error code table are assigned by this document. Unlisted values are unassigned.</t>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="QUIC">
        <front>
          <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
          <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
          <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
          <date month="May" year="2021"/>
          <abstract>
            <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9000"/>
        <seriesInfo name="DOI" value="10.17487/RFC9000"/>
      </reference>
      <reference anchor="QUIC-TLS">
        <front>
          <title>Using TLS to Secure QUIC</title>
          <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
          <author fullname="S. Turner" initials="S." role="editor" surname="Turner"/>
          <date month="May" year="2021"/>
          <abstract>
            <t>This document describes how Transport Layer Security (TLS) is used to secure QUIC.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9001"/>
        <seriesInfo name="DOI" value="10.17487/RFC9001"/>
      </reference>
      <reference anchor="TLS">
        <front>
          <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
          <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
          <date month="August" year="2018"/>
          <abstract>
            <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
            <t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8446"/>
        <seriesInfo name="DOI" value="10.17487/RFC8446"/>
      </reference>
      <reference anchor="RFC8126">
        <front>
          <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
          <author fullname="M. Cotton" initials="M." surname="Cotton"/>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <author fullname="T. Narten" initials="T." surname="Narten"/>
          <date month="June" year="2017"/>
          <abstract>
            <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
            <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
            <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="26"/>
        <seriesInfo name="RFC" value="8126"/>
        <seriesInfo name="DOI" value="10.17487/RFC8126"/>
      </reference>
      <reference anchor="MOQT">
        <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>
      <reference anchor="CITYHASH" target="https://github.com/google/cityhash">
        <front>
          <title>CityHash, a family of hash functions</title>
          <author initials="G." surname="Pike">
            <organization/>
          </author>
          <author initials="J." surname="Alakuijala">
            <organization/>
          </author>
          <date year="2011"/>
        </front>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
    <?line 945?>

<section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The fabric design reflected here was developed alongside the moq-fabric relay library.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIACsd/moAA+1963bbRpbufz4Fjv0jdjfJSIrtOFqdzDCynGiWLXkkpT09
vfrYEAlJaJMEA4CS2XbmWc6znCc7+167CqDk9MzPk7Vm2gKBuu7ata/fHo1G
g7Zs58V+9uB1MSvzrLop6uzffzk6yE6Leb7JXuYXdTnN3tRVW02r+YNBfnFR
Fzf72aL6dXRJPw5m1XSZL6CNWZ1ftqPiplg2o/D7aGdnMMtb+P3Ti8n54W+D
KfxxVdWb/axpZ4NBuar3s7ZeN+3ezs53O3uDvC7y/Sx78La4yPLlLDtatkW9
LNrsvM6Xzaqq2weDZn2xKJumrJbnmxU0fXR4/nJwW9UfrupqvbLpnOh0Hgw+
FBv4fbY/yEbZIsz11zXMAB7VOF38h0xqALNYF/B2trXFLGup7wdvod9yeZX9
hG/i80VezuE5rMG/lkV7Oa7qK3yc19NreHzdtqtm/+uv8S18VN4UY33ta3zw
9UVd3TbF1/D91/jdVdlery/gy/NycYir+3X/SuO7c1jcpnW9tOWC3htzK+Oy
2vL1lsfj63YB+z5oWtiLd/m8WsKUN0UzaBZ53b77dV1Bh/vZshqsyv3sr0Am
w6yBPaqLywb+tVnwP4BIFvlqBcv0t8EgX7fXVY2LO4L/y7JyCS2cjzOaHD1h
goL5umewPPmy/Efewq7vZwdlM63oecHL3ZY09H+d4g/jabUYDJZVvYDXb2gf
cdP2s9OXB9/tAEXy36PzV2f6bBee6Z/Pnzx5Bn/iv3b3nu3rP+DR65N/Pwdy
G72gLaN1apUs4eeDo/O//Dw5+3mfRqZn66BsNz/nzfUwy4G+FuV8k1WX2TU8
yS7XyylOqHlAX4SVwf9GvDI/jbM35Ycifvhv42wyzz+sy7/n85x+4kO2t7O7
y53n9VUBlKCEIPsPC/P1VVVdzYuvpzAsHMRgMBqNsvyigZlM28Hg/LpscMPW
i2LZZrPislwWjTvxw6y9LvjEyHHJVsIgsnVTzLKLTZayk0efPuHS/fbbY/6w
ydoqKz5Or/PlVQHUMytgcZbLCpaD/jXL4Ig307q8KGC+l7yR1ZJ+gS/hwW1e
z7Lq4u/FtG2yi6K9LYqltD3OzmGAMjSYS7Oaly00Ax9Oq2VbwzhXRVHjmcX2
YOFyfTDODpI3gPBhtHCo8ot52VzD9PCbaV7XJawKroQf30XeFND/C9ekvauD
xe9fT/4Cg4Z1K0a+6arOqlWxxH8tYeUX8CpPpr2tAq3Q1801MEp4reAFhm6R
HWILsAfw5yqvgSD0OYxpoiuir8J7sK3rdp3PkfJhWyugmGvYslugFRhmdvLm
/OjkePIKfvkAqwvTJAoFsiinYT+YaOVkDmFa8F5BK4Mr0IRt1v5bGNiYqW5R
zmbzYjB4iGy+rmZrmuFgoORi5Hdd3cLpmc5LpMnVmhesiSmFiAqJ+AP80MLr
RA7j7KjN5kV+I9tFD0dtNWIKbqtVNa+uNsPOXsr32bIoZtDgRbVus4rWh8mM
6RS/KpbTaoZbTeQPg1gA5W8hzmwN3KKYlpdlMcNNmRWrebWho9Zew6gv51UF
3QEzqzd2JJITAYPDbhvgktkqh72ifnF7tM8pXEXzolF6H63mOVAKrTwtEnzN
ZJ/TTs/gzvqA6wN3wCVsUbG8glUn8h3Cti1HMHeeLixWOd3AC9DbtGAOUeI3
63k7TnmHTtRzD2Dz+fRalvZDUaya7gHilZgVMl0cLbIIeLOF04QrCU3whsl2
0wfXsMew2sXS1m0W9shTCb6MpwfYHd6+LOw4QgV6hjPEQ4ExJUyDTuQm4UHA
9Fp+27OTIewMsZnQfU1TgUPY4kY0sAi31yUsiHtBCAXpjoYumyord12tsul1
VTW0HtDl7RJe/djSD5d1tbD16iwsbFDK3mC78vktdlfJAbefcBjEb67LFa+Z
LlDPliU8DzlUPod9mm2Qz61Xw4za5m3HX5HP4X7eXuN+6Writ0STfOjKdpyd
KIuDbVgWxB+ICJCtQuNwIqltnHTgkPgC8kGkzaJGWgxfw1jP8HgB26O9cr/Q
yIqPZdPaqXUHrazx3pY7BmldBgZrMgN2/KHw3BEWCccGJ2W2quDuaZirBn4L
h7/DYePvPXMV5qW8O4fmivn8Lm7b3SJks+dFvSiXxPF4BiAYZygZNyDi/nJ2
/mDI/5sdn9C/Tw9hiqeHL/DfZz9PXr2yfwzkjbOfT3559SL8K3x5cPL69eHx
C/4YnmbRo8EDWOwHfEAf6Do8gGHDZDwTwYMKJ4UEAdAE4Mps8RJuBsofZvjN
jwdv/u//2X2Sffr0v0Ba29vd/Q4uD/7j+e63T+APJDTurVrON/InrNtmAIJp
kdfYSj6fA+msyjafI3sH0eEajxfwfDw7f/grrszf9rM/XUxXu09+kAc44eih
rln0kNas+6TzMS9iz6Oebmw1o+fJSsfjnfwl+lvX3T3807/Mgfdno93n//LD
gGkEln3RZAd0+Q7h8NRweobZG7mF4Z9nxryGqKZNP8j/ZMdwcppVrkLdCfNK
3NJygTIzXlvIsvS+h1U+Bs61P9iHq1EuaOQ8IM3AqShXdC5KPpV6n0yY2YEo
C3wEv86OXqCoTU9RR+O+6aC3OXY/m9VwjqQveJu6W+LNXF6h8PXsyegCJcYZ
nkW4v2oeRImXd/nrGs75ogJGFe6liDv2nryE7/IElVsq3/oCLntEw/hQrNpI
Jr0UDjgvLwtkUsoPUj4OI/F8+q5hCEduwvUDfYvc6rsOHAh3FbnWBg4wLg9c
b8D9hk6qFWYfc/jB4GUkmOKg+pi+cWSQhWnZh0HuSa7oYXILwxvIjKGrk7oE
0YZJCztC8j6ciQ4iYkQ1nzG3XQUKl/WlV4EYkTHBMufZWbu+2PoZSgoRK5s3
oIIAkyFJBq4oEUJhXGfJ9X/v2Bp35H7P4MJ3946usdH9uczDsOS8IZXB4crg
t3taym76pmli0KOz47PHOl98AC2HUYqYLifVCW9AXnUxLcob1oJAbr7FL1UC
JgEeha+5iLpCXama427V0byCQftjz8cKOoRh0fWJ9p+bsrgdDERmRBJjPffT
JyRYYGGwQHpNI0/CwV2Us7JmMoYOQNEu8gU1LiqRki8wyya/wnN+4qVKlGSA
83TbYBmBDsqLyfnkp9PJa+CnyHNZbYSbbS6q2giGC6M0TX1ZXFVtybzl0eTV
m+PHIoOUTCeTs4OjI+wGj/L7IL+/J8mnLoIssiAWiFuibfKVTDy6rEGWklnK
7PYHg8/Zn/M58NHPdEGgueJz9hbX2cs4qjd/0X+fB5/3R/Sf/q//1z/3H7SZ
7XDrZhb4DIpqhykfV6oFrPLNvMpn8Gz7OLNdaZM4Mf2LdxsY2mq+bnpIskd7
GMdt7kmbP6LMSf/qjJNln3A8TLJNGO2Y2/y0zwas7x/E7Jn3+0H2W1eZYIsC
DlB/ARKnv3FYiYoQXqbH8ZuT6MwCGZYgmeFpwkH3nSaUhKc5HhQ+r3zEvJlG
Jhiu6Y5m6HiSO/g0gs6IZhU0u6zghc1yel1XSxDR+61BxJSI39ClhWzkoZjX
0XjdZJ8e4g8jZKbNbyxwmeiCpxEGfllerWt3zTNPxAnghTsD9tOWeBUaR8MG
cMwyVeXVdfHrGpauCSoicNFZDYojapKxfYjpBdZZ1g1YOmsYcxCWmXqWxS21
O+6caCDEAtTxEsbbOZnuWPoThncM/M9LFTtSm94LXfF8OkXxx0xEbBSCN/zZ
orvwczahd5vOy2zLoOnQmkHnQ/qGZUW6OHm7otNFz0OrfDilSZA5Srj4iN8T
MdfRjSzmolkyi3J5Ua3hebL24+gAHis58LF7CAQEAx4MJrRorOrjlLL86qou
roJprmnlsF1XK5Lf2OCy1UCAmyw2FjYxoBgttgX6PhUKg8Gh7xRBq2ipiU4O
NWOrYDaOyzUc8C3mLpQ1WewHPRWFcTMAj+HWIIkS16EpA18zeTBH80CJDKGq
hQXCFbjKr0TD7u3QL0tTbTnWZogKMpqTTnByzKVA15QjVMxElFrajbmag25E
cjH8sQDR2TeGPQQzr5jhyGwQpELiojx/Ea65V7xsr0GxX8+B5tYsBeBpr7LF
GoYshr5hBkcUfUZi1yNRclpXDba5quCPJZzCqv5ACzlm0sPOgfb8KPL+Yxaz
kg6Jsy4TWBEJAOsaX9cGbINgKH5/gATcjoyYdtG6GQx+aZsiLDqnASqo1JQN
26gauktvXh7wtFqs1kg6PfTeGH/2BE8yMCpCSJzjZOHIkl+itQlUJtRRUXqA
kc1zmHRNNjM8yZtp3gS9lUQ7VWZFQnOXgA5C+QL9G5kytsZNCOuj67JiU5wT
kNkgKaoeaZXRoOqcbjNYWhwarOCsvClnaNWCkzVlxRrpBJkl8ihjpsSkQEW9
ugbOjv8fmEwJ9IkX5BamydyC+CobZY2ZEuF7kYQkB/Ed8WrLZgLfIEucCQ1B
+nE7xBoqrm2O7gK8Injkfntk9cjlx0o1mzVBzC1uQd/BK5c++kI2r1c4vlku
gYDn8yA793NoVOyATbAKFjYCeZ+uGcsQogjSasKlALOr7+J57Bugy1CtyqJz
ZSJ2NdW6noJUceJ8IDATMT5Sb0OaCf6Nq2CrIdb5hjlc52CJeLci/0/RCLfj
hbLxsW2azP2ZKArcJx8Hma2Qu2iuxgvU2RPkp6ZVM4lwODyZynXKxWpOvg1e
dzqkqyL/wJZJU6FyoxHcuyJnSgY6YpO/cRWlUjhqOR/+cdDtde5FQ3IJLZUM
Qxw1PYPFrmWXvDx5WsE9CbuPoh4Jb/A3XTNmBhdvYkey5Of0/mU1B1VaZGaV
llrgNdfs25IpkNGhkgX4SokPraR4QVXOzKKbQl/R/IQV0yXDthLmdEKYJFPk
91tflM6SRtGk9AdUwhOTyp3jsJf/yc5MELOT36JDoCj5sMDCRvITWqKW0geL
btGKIZ021cLcW2y/7EyIPH7YQaNHgvQ5jPlgsjhn52aJVPEGjW5NMRdrGlDc
JX2oAoNSqUl0MiJeroolOTcEek4yh8oOc5AbQArGoQ3lxieRBc3q1S05c8hO
RNfANSylDFo6kkmuqg+9/akJ6b/+678GZnrORqMfshM30NHoj/joLBln/Gxw
tyXhrl+/pHUcIQjveU1ndZTDjbf8/sG0QPfFA3uMV/L3D17w4hfQDPqk8X+d
L4zEfRJxG/FYJRvQiICI5rkruryBJGhTSAzhxsncKrcMbQX6RdMdNsmeDrUY
9QoWrDF+ogn0pRdrW5EDNJH+aVjj7OW6JtLHBkB7aFSegDuU+QjpJhFTIxkz
CwIyyr/2RYUUgH71WXQV4IWFJIb8s21Lscob6/iq6bBhEqDFXCNmAvVUkiAk
sgGcD5CN1w25VWd1DiyebdzsF1IXPl7Wnz7hyEesa7MBEDVjbRzImr35KBVe
1fCIzRSsP6NmdT9R/0DL8t+k7PupWyj8f5jGXwbfbntdV+ura6YwUWazw+UM
aR/+Jzv8mOPdi3ex7WGX+y0K9J5LU+gOEJpjcWPIBwClCLqt6WYd4r+vSyCl
pUpzQWTiO3kw2BVZwvXMVxLHkyzFQoDk18rN525yuhjgRk6cAHLKRPYKt9wt
ybMsVJmoVYoEwELCJL5cWeZNpLOhaqh9YkKwUomYxkNO7XYSc4Iv6PDGgz2e
mlt2F0Jx13LI8P28cS9iUc5iN+A4XcHhykA6hi6SyY2z10FiNDtLuZzO10RO
Kp+Yt2MIMs18nq8aCXPBHfF9d+euJsKy9fzMccbx4BteCc8tQSKfXheJR0UF
Ntvii40pX+QENXkUrR10OCgKkCQDvpnpPvZ2xu08VrZHNaCcAi2E46MqBQ9W
OSorck68imU8djx4Ek1uCiyrjQWi2J7DkTmRPUfdNkDubepjkpFa4EosPLXy
ZW84S7QMxAJUxQ2dsLMo9g0FG7AMcPBU3SmNCLeiS0ZaOs/jGu4BnDHumA3P
OYS2beB5d9ZyXTXOV63NkyGwmMMa1PxzuFFpDVINaSjCtsmgZuVaXJToVzVq
sRdYm0WXlVjvz2SexHH1ELzhQ9C15AcftGqiXxafGXmpLbDIfPRbfPkh2ort
k7nZ7yxWcWUioXf1siiAC4YalxBAb/wSBfU404lv3LikUYeE1dm2gChPbr0F
BogI1SWtRHwJxbEZcLR86eRqHOoNBn1flCBPgYhM9j0MpmC9OCZHUuLZo44n
V3uLJtXxiMPKX7KxgyWo2LKDi73VOzOMfG/lshRHnvIwfM/cCyhD1vGl1VlW
4SskBGoQFDDsSs8vnPG6s9HiIwr2ETGlzstFaaOB/ur1HC9ssf6mG4rmn6Eo
EHB47STeTcdsASHvRiFBQiZjOH4iFibm1kgmDd9g5rOVKEv85KJAyhSZOmJo
OAcRZ0VcT/gqTUJMObIbVc0XncX6wu72+Zc5IDhIn2wOYxk08TQjJ0G97ODk
+Pjw4Fy3kt228o64ksmQBUOw0yLE1eeN45hbuSOrZas2dJnGV013eDKCd6eH
Z29Ojs8O6Sc0Tdcd77gMOl0biyrE00eGdQpG6B9fNCXmOhyqSZS8rjVmkOmK
B7uGW2BO5IYyKtqaMQZvhNwPtjFdWZQrbgqzNQaNQGQke29WreTe9FpDcqb6
ht1ek3uMLM+RypKMm8O5QyhAVtQ1fH729uj84Od3x4dv352dnx5OXjtKlC9L
tc3huiZ6DcuvTCm6IjapEm19c1kZonUYZbDNb1lgjrUvKXQT5npbJS8EfsDv
ZCTeTYk394ZYiDuGN0KsDUYwauielbNAzyVrCjReXu5AYDiYcrnmOHPV4XSl
WnfnPmQuZrdr5PdOXGgc4jH2h7bRcCkf0Y0zT2JASChC7xC/LZwajxMG94Qo
FDwYHC3rTOLINqwxvAnETD7mEAJnLMcuNKRRdG8WtcnEQ4a7jbveKSRSI3Pq
Ap0vFldeCbfWkC5bNfPeI4P7Aiv7bFbKIsSulv6o3WZVk3XWK/0wL3Z0MQtv
NfpEVSe8nNHvMRK/h7CbXjKjaUXMW7UK4WrDDnvrCUy/M/zAO015L+lbNP7M
egMOJ70N47kscjRQgwTLd1zsC+Fub/HM6x46AVWFfdLV0JTEgcpdQVnsydxC
rYornhvxK/NSJ2K+BEec4cadhYSWM01mCTLsaxVbQM9umzT8r5PWg5OsuiGF
esD7AmW2bI0a3NhOby19lTLdJIKLueg9cVxqH2pM0fJDFV/KmuWnkmNnxrIU
KtFRKofF1HDiE+srS41975OAmfGCkP0FuU2HqUef7bmWcdRZ42gheGkDZX+1
xZOKI1LSTKL0TZtAvkY5H15A9lLaP4q6Mp03ZhReryY+AYQidrg/9oSC/TGx
j6U/D0KEmA4A40WC2Y0iWsNPbIr7nD0yHemxvek+Munc2e/4abNvHaYfdYO9
Pv9zcwpNfqlNkazjXoLPHmGKG+zo4/C7z4OjsQ6+qCHLiHv8u4yPZ2kmnAWD
x7qzGiPfJCl5FLa+HHHXd93rFJ0GIot9zClQ7WZO/PgPact8EtOD5IK96Cxq
5IiGWceGGUuSSZw7mv6CQewLSndui/nGuV9WGART42O6a8xIr1e6OL/KOo1t
DwlmJAuBtAntwuRO4nzFdFo+/nsVj1XS60IOk3mLl1USuUvecgtCJ11S2oRX
+647Y7u8Sj3JTyr46Xpzm8Rfb8ndNFn2uYNxccW3RzscQsyzA2iCbQD9AYMo
jc/q/LaPt+q3Peo0NcD3I0XKEhvWS/JQzTUYiPdaZHBJNfYHtcOkPseHDD42
jhPi9npjY9Pf9uMn/s99ZFqqYXJQYbOCk1joqDZJlG/yxP+JTR33BkZsawpI
Y3tTEzXVdpr73U2dbTWI/fNNOVLu/fD+tTqJ45K3j+G+pkI04mtVw0HhMOOW
yBccFixbjZomGR1SqTioKV+JwTfdUfFpkI0PmZlIliz1mnPgnAWJ+aXkiq5a
YTfk6cxm68XKPCK9+ZDMq/A1iXoYmoqiBjKypgUOdIkGCWTCU4x0QiFaiXnM
Wcyhhx/pbhv0xGFLwl5Pcu6YJudiejOYN60ZnhtjHfD1YmwZUpRuoZZTl0jZ
oWnOYnJBbGRonm+SyFTrmwJcNOpI401SW7fXLZw82RYGBkB8MIxLzcPBh2p2
RV4f1QVhpM4Q38mPNZWNv0IuvaFI5B/5/J5NgbELzyMvkXG0bqrAyPjKo+Oj
Hx87TsmRcp+zI6LAlsIcppLqPq0aTYsmc/El2xwpKhRjVnltIj7zaNLfvL4w
C94iEZYpAmQY1kg8NdZ04DuPzra0TWnOzn3nWuvElOTBMwoDaamFgYVlI1k9
esndvCIvBSybXtxTtAhpFjEHqImF3hzulKWzjcWxkDyLL6SzJDcnKGdpppDS
BVlNNCPIM67+jAiyqKMciDSrUiCzmOQwu9j8ztHCOHk06iBOAWUmISH4sH9V
WpwXC5YZeZeiLRSLVbuRIAjvLzGDEXqP9WvOs1qtyHYqDYmZlVuI9G+JfiY9
CeZczijkF9OBCk1udAGkeXYFX7n4P2fwJi/ipfhsrK1G7ZUX6IS2iHGSnuIh
E5Pg2LY8UttDVi5l4QrbZrZM4hQyzRoxeUDaPJe7Aa4P54TQ2EN9dFHEkbHj
/i8D45MwkJAPbMspX3bmgvZQtJ2R5anVYExi7rbO2ixtwkzjqwK3JGONsvZ8
zjZ+jZe1YHXvJ4iHcStrP8cY4RrhcCgA8ZbALYQSo2vz7XWJcYFLJs84x4Ze
j9x++C83ulJdZUSUqMacIpWtJOXQven9n2E11L8iy5D4Ver1skkVBPauDAYh
KcOZgZui5nQzIf7+03lRbCpmG2UdIhUf2kF/MRgckqQSTh0TgSUb97dLts6L
wmttfJqzWQnrCTKRX3Xx1EW713hrHhoilCpR4jfwguBjTNYm5HMI/dlCj7OT
FUb8Vhjj12BiMxt0nImuCz6Czmzy/sPxbkPQOLx3U06LKCG6yi6RXrBNSZe+
oQQgWpJi2axFyAG+s5574yWc6JLWklxzwTk+1lzzj4SQgCuNxPb+T9fl1fUP
+38CPvDDezVfzVnOU7O0WKWoRQ6ntFzub/Y4lxtkgKuCDvUMxI5FPmenOuyH
vbr7zL/amEmLhBhYhErDZ28r0etVFV2UH8ny/zk7R973OfsZxkxX5K2TOkQZ
MpXo/e7+7vsMc5bo/+jJeG9/d++bJ/h45+POzs4u/N8e/g4P5ZWdHXgJEavG
e/D/9M1nT+TNnY973+x9t/PtC20Svnz6bP/b59+N4dP30tbTZ/zdN7tP8dtu
uhGQoG5FwUFZnHx0zqe5WpZ4HwOZryQSlXbrslrXusC6nkAvc/THvseNHOP/
24e9HMP/wXYeRbp1Y26ViKbEDnhb1oU/tpMWROMLFGSRg8a3K9G06BtwZRzN
NME4AATEdKI5/7z5Y46i1o9CPp6gFbiMvd8kuz+ftoIjUE3bwhIzWEotMBea
bUUqIoirMs1yJz5WNpLBJykym1Upgnr24vgsHMylOUvmZYvxoZGNhOMRCkrl
qds4bQR/p2a+LOVkMHhVLa/Kdo03wivYK/xXtDoqFfMJu6qLghE0LsplXm+A
wmgrQQ56wwhC4uyBfYV/8G841cCRRqIfIGN4XcBiTrfANKAUPsajRiFq4iTk
8GaLbJ8VlzmyIRrqglrD3vAsZa9gs96/fp85pCF9BRfz/dl7ei6PkmxMn6vg
4x5wUF6mUou+aZIlB2bML0eJTLec8W8ctdsWi0APKvCRi/L9Iv/46PUwO3v8
3jv7ZJgcoUHSCIyy+BXPMZAWztNhYbkB0oD9e2MOGddNptQ7eA+jvAi+rlo1
kXyqZrNoOsCYSaq1kOR+GdifauwUrmPk52EJVLy2Jjo9J2dfwlkWFQo5mAmx
xiDTGpGMyoVBZFgkxVJ8wdQsdWDpYqXzW8vihrfSHU78aMyA+FsWiEGTQnaI
ig1mDKO1jtxxPk02NaCZbgo8+XP2PJO/TExZ2trTWpF6dXp+Lu+ebVkDIsFF
iU5QzPFFqkpWpbOoJGqGPLoldcVnUzqTP9yyXGzcciVrtA7paiUHWneuISMB
u3xYAlqvkKexxR3vGwO5k827ZD9ZgArsKE+kgdhVJ/guKqsjlWOUvGBztUjs
8wr+f8fUvtZ4pnmxvGIjgGoNQoPrhT5k8mm879d+20aqDaFm0GvyuQbpuEX2
PMsgBJTNqRXOlpIkPw4UjZfkmu/EoIgOOSG4oYH6XE3lj4gHOs5kfER0moEV
ZkaPWQi4s2f8BD12bOQ2i0m/Fp5vNdwqq+i1o/BGW2x2w/5Dg4sLybXodqZA
yih4G41xqqRKlGZPsLiYyHoiu++OFP+ygG/Wqnkk0Kh4IQzrhNMi2ARjccfi
TKZ4U4o15NWQWI8PJRoRgh7iviMUQTpW9ox7jkiF+8RXRBukjqDV4qPZLyU6
JQ6cZR/gRs2paKWyjkbUuaokDZ5WDgcLEXtoGb7kvFkKyGbXvwSwMwho3B06
2K6L6Qc0cqBW2bRiySCRjawYDDgpeR3a2AipjCQ9I0s2caLIi8HzzA47KEQw
VDJ7Aa/hJKlgtEUBjJAXXE4AHQUSoVZrCuLGq2ndrijru2uqM9aja1xagj+m
6TW3RBch/yV8LzCqjOQQKNjZ/DgMBANQYVI3xSbEFzHZh1ZBnPxgEIoScT8P
8Igx9ksQ8G37285ZSQ0iajMyISKMeL1MTl38mbOedLcn6NxoKsmb7n03zl5Y
6nyitWsOA30vwyfnaULfYqgIkopaMzDOxQg55XHZp4e2W6PyQm6+7SHXxvTy
1NTbMdcz6Wxla2Vryfx9pBPyy5ArEYfkHG5NcC+2Mz9La0ErL3dZFy7xtTtM
TicmA5ZPAZGsEEv+4Nge4qw++6M3jRiNnsSuYG+DeSX8HE7ArGJ7BWVEmLWM
xo2nkXnRekVGLYk3FX4e2qAbEKV+JAj+VETbrtCfWAB1V9Rnlqs6Xayq6bUE
McijBuT2ApnScr240OArfi84UKZwTFr9MfmCpftGppOMWz7UXPV1Y9HRKHq1
dJlz1if8wC2Ms2O5l1iBL+lGs/QkubzEoyLDjZ6ZGBHTkfIL2UFHaaDr1nI0
2575XWyYHFAXwuWXfdN5Uucg7dWMUc5a/rOnT795ipPcYYHN6U28tsB2yOuu
qAH4OQdDSXREruFKFE4aHJP44l2j5+Z5zPeNCvhvnU4axgJ6LQHnS/CH2E2V
KYdOgjdFvg2TQi6cehC6H15xxlCHCJGTkJBA3ERRDXKl3xDhGHin7OpbOQjK
opVVBGtyOK/4mRIt+wu2ej+D1G2TUutp7k9VOo9bspY7YrSgaPPzIaBs9BHb
INDNSvGZwbVh68dvkL4duEnMFKo6us1cUCsPtnSLG3ogaT3dika2qR5iJA8C
Uuj9xRp/3HEAVsX8hVsD2bHg7s5QNMRajN9sfEhGMeSFdhHiKdeg5VeTenm1
RHdJwPXKdQ7dHcqD4qbaKUnyPLnOanSGn/TpttzEbEsj7RmjRAVEpBWRfuQW
cbG9PC4Jy2IlM6xJvCd09jHFs6oTQGkR1fLGOlm6ySceq61Tt7EGMmWhIA+J
KgFhzc4CPlog0wg+784p41Cudsty5G13NTouLnQiWCAASVwhoZOtbXjSysbr
42YmRFcM2jaz94/MdjESb9xjDKYknvrsPSun8i7cDLuZpv98s/fts28pcLrx
U3O8wp8wVFWMIPTyRCbeeKdH2INhtuO+Z5sdcfl0QDiM5zYovgjuGRSdxLSd
HfeVvuz5ETL+4HsKzCZC03bChO20oiEr5+tlRhZ6UBdtLhGYuvWH1Ndu+GYn
XJr+TqVQC3p3J7xLCzJEYwflFHLelrvZbAmSe5QMweoVjSiXR8giMu9Ux4oU
M2lx5W807a2XuxgHoZXCEc11PVD4If0P1vYGb4a3ehrDaSIk12V13z06FBuQ
47borMabkPCdSfNG7V9s77hdfCZCXp1bCL5881Qgo6XEXe73j2Iny8o5pdXy
F9zMNvRhPE+Ra/KeZQmX17ZL20mwAlqEdGrfw2p8g4RDZk+PwRQATBPKJnpX
DCr3rYGlLCpmsG0sqEjvwSgiWoWidkxBr/nAEqL0JBnSaRtq++BVKSmHR2Yz
Z7ajgTv2nNJLSVAB4qvXS4Yl4gC2pRaycDwazsc0WNOZzSp3wCE6Om8ZJCtP
xhguAcN5SIIMjO5pIgwfJsONjoWMJWZRlN0q+Sk2lCUaN7V8RRiKu5G8CAFH
QCOOekyfIkMEJK5k+KiPhgHLXsgRoFPDcRXhFQxnGMbMrkuzkuxQUuTUNFag
YeTVgpOZ7X4luASXDGQMJFpKe4FqkSBhzGBydPSLvJ6X7Ooj2sHN3SZbdSUG
d3fwGDUtjslPboY4G5o0o4Tt9t0d2yaDgnoqJnTvKJ2y0El84MNazRX+Ju7b
k9ydu6V2EkrQZQcoOv0TeS3hy6zPLhMuHE7tdv0jMGa+2kxAU9GCbOdIi6gH
3JDveqLdSjKnR8+lMKHt3TFYoaTx6dYqn6uCrxY7raolI5FJnp9gxOshvs0p
m9I9sfoqRbhQZ9EbzBeie5vmxOFXV8Fzl6OoI2MJtJ63Qs+RtGAyoRe6yKJs
JKBGL65I0jJui0SUBcgKDBszosIFJd9bZ8FtPORd+B2Lfp1L6mlsscEogD4L
wT36f6vXFhIYbkb/dcUt4CXFiy+mF3klVnyZQWr0QoJmGND/5FuUhDoyBMOA
CbQB8FMGRoRdwrgIwiLNA9qAMHm8yljHjO5KhmAlBueG6bUxmlE4ZT2yxJ23
5Ca7xMgeq/2i51avIgWuoGcyQq8+VnO316xKMWPhyiNsYDdNl6UlLp7AIlMj
lU8ELMSrZzaBwIaMBOFNShZypwodDRq7jkh+a7ze1Ph3ybm2UlJRUQekudBI
EeMwdSVh/6PbPc6b9xKX7FBu5GfFJaiT7v0MZ3xtNnvmK43h/9cMFVZdMJiG
RrmXDPHqhGg6AxxA0SYTpH7p0ElqeooLocHdYhEwrlqRW1PZnjSD3jZth77m
S5uFpoaT1sUr64XJFMxElXAFLyHLsUXfssldwt3YgKLBinDFEIfYj47vF5lI
4zvG2bI5AV2Mg8a4jdVZ654/MS6GGSOA+h2dCTqx04wozM6FJIs8du0XQ814
AvQijTgfCzEYtajFYvV1Pkuk3PiAUlMtw+0VehQd/chCKmlHo2KM6ZXk5tbF
qmjLgMNNW9XG/qkA1o7iQ6/gpYbJ2BbrLnXVUHUuTuPkRcVfMOuYbaQY0AD/
y41gLGxHb8rrYhiL4s5mLAAUiwrYR+4+JvtvCKNerTBSjbPr2dhpty0l5dnF
jqYI+4xEXTVEkaS7AD4230Rmp47NAOlfjCVvLT7a3dboOI9YJREt00ATN9kj
6w3xUqLl4kOZ3izCa5gBEOFI3qIKbLR5QUa0gDe1WXf08h4rNe1ETNwpWQfd
xYxsygdUSqRWBI2YLeUaWc9jGbq0m7styEYdfkwsyxvRUxw38/3IjGomSqMI
uL1VobymYKZm21qb3Z2HLvzCeF+0ZiQw0GTJc+5kM9og2lKSuPyV5WkKKTJg
SuaRLKamidZsULQkenvR6hIsSmJ8DZm4XfaJa6em0ORelYJoGAxUy9UcuwZb
9YhJsITGHXWdmg4dPcakw6/Zbc2REALexFER8yLCaWUPMlxZTVuvp/xT11Ps
M+xdhEsEHk3xG94lxSZngfS0cm9673OAySQ5Gej6pnQ2ekfCRUIdxDCnQLiI
uYBbDxcRxY1wolsArFHgo8FAglVxby/LeRx9kggoLGCQaMCvBqjtZtzBROaY
uOIm3FER6J7HJItL3aKQwAeOI9a4MKoL5NdEwBAkIVZnxYgVSQ0LGaH2DqoJ
wxHzQFbtsG+zyZ6bet/sBtsajQXj9FE8kVdM6znQCb3GYnC1I0tFWCRRpBDB
h2BoubIpSRTq2a45CZMhRqlDURORlUizLId8xOBnPiy89aYbppB+E3mBmGLT
XZO2uofYQSa4VC+oSy8aavTNxRoDJ7aVBg3wFMy8rOaW34E0UsbbDfkw/Q4H
aWKQCakl2/XWgKeuehUCszUcPBVFsPwWqSgyzz6hSH2YXZR4M6kICDzQ0hUG
nFAsjctP7A8YvCsvtpTuNN6eok6wpi8VmmSLXlJsIrCIlxpTgIvfFi6kVOYZ
FjIpwCxoiDFyA4r248wa9XmTPS0ufGgAjfOK0gFc/TRKVUhgLCVZqpCXXQKW
exynCnUKUbGUy25Rld0JcMVgH2LYTPvVj0QjbINRUSZMqQCq9Mpw45gzuxiX
jIODm8xyY6mBLFZwsC83xOFbXnD8gpW/YNDEEG3VdDCo+RCnb7oDLB7xHrDp
NNSYLClSCLltAoib7IIKUQGUjRV+j8XGo4lBpofO6qXp96ySzjeqJ7YcvJDg
V7PKKpzXHRtSb5LINQGBPIMZf3rYLJs0Ui1OD8c+cXyS8e6T9oGz3V5XBgZy
SXEHRwoqu7UcYAyMRbkJJAWgIuawwBYOgnZeVR/Uk2PIsevV3Yl+hA0iKLWm
skUwuDLxFBortwS0tKqgg9TtQ98K4bgR9pZrJoihu5I1grFqir9K4uiHcmV5
N0etOKHhNO2KeP1k77sn3z37Fv7/OPtPPJ0CfVffiJ+Sz+WDJZ3bB8LD8Y50
43DHDdaQAuGYdjzzJndX5xA1VQrKFin+01KkunjWG5xTObMlb5MqaFVcA0pB
2i6N/sJZZ0hNfjvGAxq6vehFQgtXhYsy7dwWcrMmflw8TprhK8nbmnGASoFC
A1tQs8MH7tyLQwdcmUSfavqJLIgsNYMQyx1DPIOdXBasqSTJxnsSU9gHrtdF
JJ9I1r/B93SgmlFPCl8qkYvRozcDGmV+zVd3W5/kUI0RON7ieM2xzJ/yxNzH
AdeVnXWKCE2VyolZ+1raxMLjdBEatEZTlvV2sDsp14yWQWEzun1BIU7CP/my
cKq1c0YtUIz0U+RI2zo9GF67Zv2TEEmoAjM1/DPL4J8e0iyAU1txZpWpTRWU
iTK4ZI4Vj31OI0Ed85A4ERFZnl3Oa+JAEg9OZEiTaASOPbpQNOgrokzxh7Ll
vSn/oZc7tWU1imG6B2W7wUk9w7LfB0fnf/l5cvYzVvES+1Y0aBb/KV1BMjNV
J4kaAm7AqHGsBgvkgy2UZRGwyjkjEmWNgzRKS6wSLUT0G+05bui+zjObtaIh
kFWBmy7TL6XUGfyGZi9qQYwsoVeptGWZFWETOVq9ca3IlRnsRPyVVyYC9nmo
liEL5MTn56p/I2qJoGsiGKAQDsGncBk8dwCJPaSzwVd7Jm1aSRSGjSPZZ0Q/
W4B3+PARU/vjfUKbw8PF1I+jxl3aNxQ6QS/dukP04nX2fWdQ0VbRWxZ5nKxn
6KzbzqNrv3zDbIEpmhjUhlmxCC3O9E1dDe+q6+ENZiT3MXFSs48HbqbXCq2n
KXgRvVIKHhEFN8CokdXSMpTIlZfXm5hyHz3IHwyzBxfTB4/FZe/sM+6lC3wL
XgpGqrSFuxug7/MHj92hNXLsbtAWk1d6g7JUoPIiZhuyPDVk8ct0L6QKoTb8
8J18+Kgp8FKnb4Tg8AlsNf3Pf5ycZo84RP6P2c7H74pvvv32u4vv4A/6MPvT
n7Jnj/EvfueHH7K9x7xhiJGS18DvF3DhUS4zWeWrbO9/P3syGOA03uE0iOKh
u514WPHvwyw+IY/vf1nei8nlZbR4RC5v6gIYeZBkIktSvCtFoKyLjYhFQ2cl
Oidhg231XY4cGzU5g0r0xq5lJ7w4YRP8iocJowg//chS7ERt+oQiKryCgjR/
ZLUrDFtpceKtU/FPP0aVuihFDvEDwkKQMV9T2zn5i9i4AYrw1Rxqg+Yyq1Ox
g7K9mi9LK+VlDNi6NvhxQpmk8Fk0jbTBqMdNULYyp3n0G0kJpzuE4qiIlLda
0I+uHGpMQF0jY8yHYjPuWmg0DYQwZVgkYVG5u5lqepQkuKFT3O2RkzFEuN6I
dU9lSm4spdaFQdhnPhsxnXMkHDlsrSgNzJ7gjA3CFoU9im6qLCnK7FyWIkdv
AcXNJKzA7MpustEsGyunk0kFepcx403i8PimsLjV3sKQlrnXVJyVpKUcKPiC
jZiRdYaNrc4gZ/o5e/HifMtc3N8hHQil1oMAiHHo8VS5qh06kTH9W9BIwrtk
8vj0CTE1YCC2Eeevzmj54MB8KBzuHLAZfnkEb6CJMkUjMSeoBYbCeLE1VM/I
bDGfacg2Pt4dfwMtSmM4tsmrN8fAhj4USwsDfr+ofh2xJRAxFg45T8oAjckc
1EbTGjsMEsqvJC9ZaSaVgFDfKaeQfurCnPrLLkjy9Rrahd0QSI9PD/PoAfD1
5A1S+uBRVZf/kCd1YTlfBjEFUgYriJcwZiBuEfh6ELgxGP2jpVcdRjCSXDl+
Tdg0sNYJkBEpdIiIyBGfvPgUWnHPkAXch96HlT15c350cjx55ZR3rbyACdrs
GHL+O6qszhlbZJm18UVJbc0agfC1vKf2r0qnasN/YNmb9s0yJPNsijrjJeej
Ci+PSduYhZur1GclfOs/JBUN4tgexe0MampoGa8lrfIQMPgYn9ONCl+7QKOb
+qENOU2LVsRdJtnBSeiBuKsNRJ8Hpollboqz+BxwSc7LvMQgJ7cRCQW4YjQd
0PLjbQWmSfsjVzjNTSLljWowO3KYnEpRSghdKD6YtiqUlU6vKM4z/ZJYNzyF
EsCPR0WlvVBHdExYafokEmvRtK5wFGPJ46pRcA52S70YxqbQu5A5bpR/A5e6
SZaXC8P5t0KESB/Zs+3x74x2TazbYIJRlYRJtMSX6MNZXykUt5+/fysHB46M
FxjpUHLgsAL+CI94meSza5owmWvdUSATzaoub7A9uPKFtsttN0yxuCgkrin0
vrQMgh+ZLNaNsBd/6DjyDBpsLje94ImGmahBaYSBIwYjYSS+QTKvIsNawTgq
O8Ooeubtupaq82c/T0Z7T5+JO7mt2dXKgtTrF09puvjObviwsVtQd3rM9YJP
zya4SCSMa5Dc3s6T5xlIwexEKeZzdBVMRzCHG1pRHsWbnjHQKzpqPzFSH6Qc
U1uvMURjOb3m0i4e1Yn8SsybhlxMj+VAiU4DoqGTp4Ert3kE3F58RNAAUIk2
HBmMIE+SixZxcLwNSnZZaf5mrWGB1E+MB4/aDI1ZENnRk+3aQ1lQQxnm+UVF
2H8bXhmBNWffyaxaUFjekctIRnEPQb3aUGjbrQ7dliyZhGrZrwNfDaj2TWBF
Ib1b7xUfr2IwbNv5UbAD6FXMzCQ5+helupHN81ptvYGhRXPwGc+23E4tGSnd
TGJ4IMcGHWQoOmZNYvc3/e/hZRO3BAsT1rZ3eE/zwqNeW1ds/kkEHNrSjnEX
6YJ87Yu8tQ0Qht1u1HvZrPlCo+LiQfZSkJOtcrRwORxC49jbYPDCGmnUgK4x
f3DUR1Z/4Kqu1isC9rgpZ2bRKmutn4SaIm6HSONxGsr1BtZlBqNs2hEo6Mt2
veAGQ8ArtxDJN4wAzoBTjHBxZowwn19VZIVh47k/3sjzJYybdXA0I7GXJ4Pj
eSOBCz+biKW46sAzLPaNZmVSWCpYsCLQ4+vaogeozk8ggOUy9g4vDO3V12nr
RWfvIhb3nNX7xO3ew1ygocvsy1tOsDukQ775JfxHdO+OToPVKQRiSPiNnRa3
EE6675u1Fqrtg2s+WZII5DBPk/almmARH9SwakEQ7JVh8BpJ60EQmw4FYhxo
G0x2A4wbLkPgLo0CyweE1BB4c3dBRAcrRLIC3MAkGDqEeOWYpF4YOGpSPAyt
XIRSJ0gnpOZO4ZImbDLWfy0SrL9oRoirD1MTgexIVdneOkKaHNn4SBoJRDPR
D62YR3aqtv03kT0aZPeXxJFaNp8Vwo8P8h89RdPzHz7/U63pjZrU4PgBGorv
SvrsT8lnocaiAQz+jkF8D//1aOzf6384iOyRKzFK5IkH4DGP5p7vv//8O+v7
ONsCw7czRN+ZxlS5EK1I6iAiiezRHs88QjDkkGhfKJj9OxbPjRHwYvVUD4UP
F7GG96nIuGCVhqAvQjBlW1ZjZp0mRv1TZ37ZA8w4ZNQ/ggTdGWZAXNnrx+9d
oImPLtGsC3OzITIlIYNqxzwwiVH4qknRUDVBrAOI6n37I4wFCJ76nIK8BJAw
gCAEWMEUivQWrtUWi7W7+rPi7TO06mrFO6nJq+oQ7A47uuhkGGSPnIl5R+a1
HTZ1KKOkzJGC0Y4ZrXAPlEJKKzaAxYZqhhsiLZnA7oB3fKug9+11XRQBiMGR
aYj4C0jqZQiU4R1TSXJVcCxKDOoS5QNTRlGILNHwG1SDUc4SiJF4wSzQWjYM
yJwEUKmBS6UURlHkh4LFLaO7zlVFyD4s8artgOO61JhbPh1a7JXK/UkZ5Tnd
P+EYgSh3K87/Ek3Qr6ocpP2rorqq89U1QmOSeDqUsVJCNZViRnHyQpwqNeH/
eQJnw2mKXCuoLbNquuaE3/Kj3dsGRsIebgp9qAilDdtmIZeBJ7OG9b+CFpPS
tTY+S1aGIOd4AXoxHbQZo6OFqD9FB55beR008jM9EW8iqzrVegqG+RAEQzQR
vEVJmDMXUk6w2RJ8KasorwYRWILGOQWquA4RcbsNpZOyqcLXRx9SjB7V/L7u
jSWU6Mtaw8Ok0ueGkaypzmClmXAhykiTGnh2kahjGQnqqCEXhzB0AkCsW4sn
tDkxQXOwQ75q1lyrVEg1WkSJoUJHTF9oJILSSYhUFFMoUG1tIrB3Rs2leCmK
lXjQ2gKvopZkSCwhmgyoHqPkEDo3Vhw7LPdPtGMkoCIJaOk4n4bVWCtUj5Iz
gC3ykvu8jjxkIZYMnQgcGyIla0MkmcDGhciyniDAJM5M8akocjapKxMiki1F
RmCgDXg6CrZmRSmNlDaBuCeG+ihUovoqQnQl16YLuqPlTYBLeyL4Mq3JEhht
D9anyit+u3z1cYu5IRLiGp01W/7Z5qRtipz8RtMbRGbEH5WG8NHN4ITJDOlA
3jk7BmU8+z77lDUSvzsZ2j9/BJmNvgP6ce9/G7+f/RbkUPz5efSztNEpY9l9
QF3dK+neDELHW/+zzntWold87lmse0cCQzlzYbRb/nOv/D7huU9lyin/Tiso
WV3McsXAQc6x++nhSp6OgvP+N66LiTHoUfFqB4FKHGtehIK3qvjRR7Gv4LJs
AydHnoCXbl2tVmzPYpDXtpqCrhG+qfMrFnpCB28C5rPwBSZvTlMFnrtAyBc0
9X4sFyCzRZnK66U4TD23FJmJDMT0W6jfy04RGTm33FhJJFdcXZdv5pUKucAu
hVH1FgwWf0OesGFxlIYYM46z6xR117tSoI9U1lbUHs3Ag+bXNUlrSTcTMyWb
+zNvQNC8kACF9NoXJuNrwJ3qFwHr04gR2OPfq4vAieEPXg+XO0cOSQ49xl1E
OCnC/cingp9AxcymGmSwDQU5ZMnpKnGkBFUUgdW379hOWFECIP/b6sprDq8r
4a4hwTiIRVnXlZIdkRXlyO6bgCv7ckWHj54k4pCZIzXKMsoEQThdwf3VBCP+
OUHXDYgE9KsZrSm3qFpmaS4DCtGjthphvAyXpIChjeRruUhM5Kz6ZQm3GJS/
mpSDkxQGs76G5J+A43hOEy/Z/KxZ8eEea/3Pii/Ll6/bD7eE9uql5hbdcXcS
6ztZFYwKkr2EpRJ9rSMok+u7IvnCY8LPPOpDEUKLHKRy2bJZ4Ce2bffLeKIH
R+ax3twx1EcnLv+kNxcnCqovElgJXyc5VudQ7ELV9oxj0H1hbxEX8z5Z0QmJ
KYQ7fbHmWnxBK/WVxWezkAHmXmiHEuNkUmOcr5Z0UTrwI6ph5+g9AXRw7fDN
h6t8IOli5NRs6fohasB4ep89ReD85CmLs74sVtbRZ2SWCTi5bXQbcuqcYxOG
wNlPBI4vLjGH6lwlWePVUnhIgqUXCUsQEdCg0IA9lFfXrQMxuIMlGpyBP3UG
zYY/cDW9gRMiMOYSq+hZiguX6/B0y8Aaof5dmoXIkqyJ5UQcAQzX5/E5/AEF
Mu/ZEAYmktzhYBHDuFOzlykUnXwqMaK0thGDZSnKmXJQeGl8rznjwXickaJ1
A5BcjOXGz7tjMrH2Y2K+5/Tj5V6YaqLLYHhh6vXVNEPrZJHXH6JJQI+E8DjO
fty0RdCcGT7Mix+MZ4Y9iNgRkTsXrggUhClsBD0q7Ut/frHCXXjnKjuI9aCR
el51mcVVxBWCSTOGJr2L2ZO2lHDBbi3OVeODXT31c3b/UOLjlOtKblxppcod
hrAYQwzSRFsqOSwBs5BIZ+0kDFFURUQKIlVR/FZ8UCzKgRELtlY9GjJIRz5P
k8mjpCY76kQjZSt2sHnRUcMj7DgF4tcdlfJb4+zEt9fN5erD4mCEfZ+hrDWZ
KR+c0teXzW+/iUWONOJiPjNRjB8FLKH/RopWcva0oDZFVGkwWCD/DrW7B95k
48w+YsdQZIDAs4L5MDkKLlcuau0oAiwJob+E1FGvV1xGl0U+verjm6txt25f
+jszBsQWKSkTzCy9ZL/UyvaHmFzEBkyJI64L9gv0phiNs1+Wc5qwhLNLgjMZ
om9LDKlarOdtOaJPrPwjA15J4A7B5ZZXI1jnMieWFRe2UwHj6PDwMPv26RNO
gJL7TcXsHGWXEYdPKyg6haq6lkF7LkWLlPp8PGbzYmDYXLm0pJX3Nxi535pX
Bv/EBRtJPSotfBnVteFvMEh5Is3D4wtUfChNwEJiEuR6jNMutcgfPsAKkZR7
UrSR64HbVPYfIwGhh5ti62UzdZwNSHfX+ZqzYNe6YYS7Q/BDWJKYBbI/6xRf
8adHumOfHsrEkFnzP5l/qMy0bXFss0o17w5BxmWSfD7e1WjugJcHJ4Te36UA
NbOJslOQommuzPLJfXEQm/UjUflVtkSbigOocUqbL0+pI4W+0S5eZUB4Ehun
SefoVqeYZ5AUrCOZKLNacm/o1vJ6AOl2IXUk7pZFDsK849Z4+Q+qxQLW5WcS
6rVwrkYn6K5eFFd4dwpHQpwaMR2cxI4AcReIcTFqOvs0yLI3atz5s0TcP9p9
nH2f7WK+m7IDrNSZPdp77J8JaTx6Ak9/S9KUpBcekWQpJb0wJHgKtBXCESQa
iNZQPmHA1HklpBZFbySj0nQlIyfdf4v70dU6ihH2qJwns2SE6RMtWFmBG65a
YxpXtuGC/S0aU6wa/FIg7yigEE57MlZt/CDeYMXyWaKaudQKS9juRY+5ignH
7xceVmlK6qhS9Vzcyc+Us9xrQD0ICe1b//s86BRQTP7b+kP81gCr8nK3Em7R
HU8UdjUUBsCI0BZPgg3tRQ2FAIwvaMhCg7Cdb/j1F5PzybuTH/8tGdRnxHAl
8IYxxf0xwpkWpHG7N6bGnvA3xycvDt8dHb88eTd58ee+2WkMh17cyWpnT9N2
3r7oXaX72nnGr5/98uPZwenRj8mgvrydb3vb0UF9eTvP+fXJ8fHJL8cH6Rp9
eTvf9bVja/Tl7ezuJPOiFT87PKdBfWb3roe26GmN2tnd1g4O6kvb8fw05v10
nomvvnZPsGCRfyP7hqVpKkeIf6udhsJcG7v3WNBg6HOSyChmYMyVgDl+gD7X
wkuaC1ag1XXIFkqJQaRH2dHxnyevjl68Ozg/ffXu9dlP787/8kbyntgh52KT
Pj0k+CQq/zcYHKeBkJQyflGQiSrkdnCeenrUxdZOLLKama2yB5rIq6p54Lhi
Cs2JKU/Xq5IwegTO05TVy0TMUukjll9CqIrVZuMW8EqYlRZbu/eErxX9Kdoj
lpoFbW3vCe9AH4oeXr+2tHStq+fz0XO6telPvsZ36YEU1LZrnIW56KdH4zH9
bYWptTEtT61/S01a+YuseUdYJxcbyMbjMQoIg/C4Z3hUwfS1K5Xb13QqZaTE
QgciTJQWi1WHvpriQN6Ky2L6hS1tD/EH4rsnNlwyK7NDOR5pAGp7RybN9l4D
mYdKDOEG7JOKFO76C3Jz+vrtxfRKKmb9XoZweHxw8uLo+KdxSn4le5BUaxKl
JM2yCZghKCTzugwGbluCiqB8sBepyO99/HrvjFR0ln6U5X6io+LF6Ue0diA7
8znA0HbKEJAjd055AW9EO5CHf+WnPcdQ3sdD9Dc7wnS++WB2hG4eH4vb1nd6
CrwRhRMhGKKs5zT8EwkQv5Pc4xVBlSBOHeGdZ7Vth3/yyYZzgi9qJMqwZwb9
2fR+wb+Q8Hg4HsbCkjw4w2Pstkeru/XlDncKQPvWuIRzRijNYpgKrTZVuM3o
cgm4+nRZafS7XiRWEVvviHBmjJfY4QncpfcURRvasFP0AHkHO+36Heiaemzo
S19yusJA7j9mrI+eKl0e0FHjh3+ND8vftp4W6y9cHvRVr4Um7gpe4RoQ8X7b
OvVvNyph9PlWJSxzNeu/6L/79bEv1cgi1WyHh3Jc8U3WM8pzx0vKUI1vvG2U
pu35G7LbpFCIZmwhoTN8eciPHluTezpKn+/VaTJOZfZJZJbyxY06FXALi5MW
+zPqelsMRHfqeWijgT9EdZOOgPrWLlqR7yIt8v7j8eRx/60xiNTI+9t5uqWd
u4UxE6pplrhiUbWRkKfIZbAI6Bqze4TNRTjjVMWbmJmB3GiMdpR+RriAmFBb
S8pUndN9QNHmbIcPwd3m4dGa2EH4J+knlnNaUwwEzNDauSikmgi6SO8oO82b
2KN6378Dz2gHuHSfMDgrh6p/x1XjVOo3qB3EvvFPoweIKtR9+kYDOURSeaG4
LuflosDgJXnv8OOKnHLamMBpa2fFLYdddASf8MupHHQeOAk754RIQ2Myuu2a
G+5fum///9J1jmogz63n9bC/tDUHZzgQfwqY4XKqI6kSoK9aEoqi+FOOWOQk
SfGrk6JSUv7uMC4F7U883co2HgZf7RRBs+LQoTrLYVrc6Swu7JSQRCd8TgP0
SXSjFAAHvx5NkZEgfxsHkuiLxdOYqXGXUnCQSibY+gKTBEVJFkjZAO1sdQhI
Kl5SDLcSlWTT4KKsqAqFc5Czorgc6Qvy07iHBIOQ3kuEPRK7K8LwxUI6M0tH
yXjCGej+gCR0VanokSpPe+6Z+C3VhjEej/X4xm/To+hlOy4PHYKdHJ1zw+7k
a82NqONyCDhnDGkmOVoGLmnF5cWDZHm3C6pvKrqGH3LPR9CPm0FCEB4HClOe
UAodR8uo2hq3Jmnkl6XVMTalaaKaUR05vKgKyQpDvroOmF7lK/AetkwKIJb5
PNiPiDEOkVggoEn6emxA1FbUiIjb1zUp339XPL/jOujn8x1WCy/O86uGyROd
pKlF+v5RfPc/PoqY+0/6KklEzL+f+/lQzLHvs7QYGhHhiPGFs0OwX20k86VH
w+iwgxmp4axd+y2jaAQpbZyujmqycZ5HP3c+D7TuC38qQHgChihxJw4jLwrF
gd0kdZdiVek6CqsFhPwjHK8dPLi8ST7H5AOo7gEnPM/Qvjw3aLmTpZYZ1uFQ
HKoasqA19pUrAow6p4irG+yTqwZWWUUSCr6Sqg9CH7TQFFDiWWTui+EwDp3n
UOghhw6wR2cK8i2WGv2W67QmUakc9+q0uuFkAunPogDC+xSzEIGuNgyvEQ1K
ph1G5Wekvwp33DoazWzSa7LDmPtusW6IVlxMJyHOhFjCpnXq6dBoEoLfUmPH
IAkdBfsiRTGAohb83HpM7kB9dcuqZSfKABWcQPuKEBGvIuX7Bgx8Au3yIfB5
D5EOIwDm5JdlmsbN0b6ObWwrt5Dqa5Er8AtswDvMx4/PiH8/6dULjtlfQALN
nlOzieGb56TfjfgFQ9jtDGGrKuDiLeO7gD+2vPX+lL6ueGtZALhpVK5OoWKp
7oSbeEduClbXUIMCKYJqTzBbLNp9yfwVe4vDbNYt1pgdjW6U+l95rO/b4eSi
FSDMehiDO0tWpCmWeIJwLOxGwb8+YIxPlOXJYVq5Ru51HSzs3MldgqbG55Gf
OIR5ST6mRTsyHZNjmcmg0eRjl3PoEA4odQOjHH46nbzGfC4FsedkrK49VzOK
dZpJ6YM4KCXxt+DtEsXbBxNzkosVgvlrY7mUkaHxOkLjwjKk/K4UWaCwMDHQ
aGZPUBYZ71jNPJyeFSp8MO7n5SXpTHEnAVvp4xRz2vaePh2aCEIXD4XbKMvk
yrusKT0RMSWa/O538jRMWBQet310ruNxqDEBX/KuXOATNISR4K5O1ZEgDCQ+
8i/CatIJ3x4T9Fn7F4n/c/YLSOd3WZs/x3/KK86YbAQX+th9EveJUs4sTm8c
e+Px4X8cnZ0fHf/07uz89BBb+ox3cuGbOCbf+S2ihabxdzONygpxcxbboA6J
yK58+NY60gF/Fw/4ZUrHvcdnHBmCaRNCFMdDObo4Z6EEXaheMkDm/qRDCwhC
3r1ztlio5AD0W4iS9FIz4eqxKRXlKXE2EVPRzRvrQLyE2xfgX0mZKYuCToas
33cLlkncbNmEWi+W3zHmZUUrxRntADKhfk+ViIBXij0VNp2CP11VqRAqKGXE
BYjfkuVCpcmAqst8KQ09HCY5fEOXNqoRHYH4tpLBd31ksPfFZJAIJOfnr7LX
zsJkgsud5HIcGHcU8hmLBEQcWxIJNQFDAhLUVV02dno6I1O1lO+4eXlZEOam
OuNEdO1Ln/5NSONQc92YPjivRrHhwtoPLUdXyV+j9nE1fQok0bCqCssqzelF
SuFNGSaC/9DWRbQmnxhKmO5izOFFc3QhlGeo1QLUG+IcEjxUrkaJQpsaiEQ6
aCz1TxNQ6dqlMzffxHGyiPwfSG5X1wMZrjswjJnBt7wMk6H3w6dVcM/s+aua
WPLu0E6ZSAJb40rOzien5+9OXrpTa1cIDyP0KYd0h9LcNb2Ekh/YHYlwgXNK
fTAUdIWeYwHJsuFvymou8Ish/ibBOeZiXI3Wd728LJazkGWilaVQTelMbspV
9+51F3/GTK26cF7jL3AI6y/hDe+ffXVikbNxTw41nt2gBlZf8iJ08JTdXXp6
+OLodFuUb9wswUIKSiVB56AasWRyEQuUix8F2ezd5Jfzn09Oj/7z8MXWhhNE
dfQSKubyJYaQsOJCOHvkBt7LfETx66OzMxA77ho103oaqH8r1UkNKJIa/yZq
HKMQfA/pyLdcXNi0nHqJtugiM1JvT6jN3rjM/qlEcaTkTJCgUGruadScRnX1
rgwGjPBgcRosSQ41pJ90GkmPiaLvqJdnUS/JGcfw2tCuUx1mJRerdyqEv8+J
zPeeU3ju26Pzg5/f9Yh41vK5D+gI59hgAtK4Mi/jESfoP9Ys9U26sX2pkSkO
umI6beID5kL34rdJVaZPgGAQEaSYz8cJPH1vXBYDrdJN3GyPH0zx1ftboru0
EabnJkbMLYviIYBNhDrDYu0hPiCZrgqN7yPANLVCkOg5jCpFSQ9PDRp1qDZc
VfQVV3dC7SrUaLjxpNBKumGhpruLQlxqYoCldQWUf8o6pNvmZFUw4jnM5UDS
8fg2IU3+tJDzDut2MMdyBo1Z5uuKi9BcbPoTZitMHSawqk6VSLHCMHgZmdIY
GYowpQhejEvRIsxXPs+XU13/ZoWpLSo0RIUnGeCFvFbYDKJ1zfP6ygiV3H4O
taopotAP8whVjICR1xfcEFmTa1kH+sAS46e0InxcfjqZvEVAfkvjd/T3y+kr
SVSf5qt8SvC25KDUg5CCZArscayriH90JuAQFjkyA3Vb4DyiqI+D63W9TNKZ
6QPxaHMW2t8rDCf/dV1OP2CAGYFGWsKkGXY6sH9R4VxZex/iSpVfI3wGuTL1
Pp0xcIsPcGFzBJUIFy2LEk5vqGCzBLzwiodqOD2kxPC9LjFYW3HZtFLuHClL
yjd5F865xhMw9+KxEK6JR1O3WjGzyK1BxdEwIKvieu3A/4sIgs6OM9UDCoVC
fW44QgKABkqCd9A0csLfgbOKSRKz4jJfz7n441kxXZM+kx7hAN5OcQ+hJA6p
JUm1l9+GUYSaGrTiatZ0imLwWR+VLpRLeB6l8JX7C7JMPO4nIQFAzwywTbf3
pQlFEfS2VrkJucZSH3sTJMKIbTcJH6QrJheovHJJOtzdWMly6fQCn/cWY0lE
IpxrQGZ3FQbuAFOfV1cEFmA56akzhuRdEg0kVFrumiYNSCQexOScFPrIuMI6
BT5GhRQK8Xh1qQUNkZSoWFBgyMxNBh0vRf6BAXKmriwG1ouo6k65CPTkhjoE
jeULhQoLXKiA4hx7qyw0KUR9Us5je3kGkrkvik1FnFsqKHDtBK4KLFGfBtxC
FdCDSGArmHPZCRYZxPxO85F13R79SSxDOZkz+hvNvBWgLuoQCyHAhg+jUSD+
g8TYl/H8psTSPeO2HpwyzaNFECNkom2Eoj3O3jCxSK2CgOKOF5fW4ZRhyU2B
ZSb7ya9sTfyIHHlFE7n5aD+lPJ7z78UV5RoOCUF7DMcP8H1/W0nQGDCAihHu
mIfRBeHKURu4BA8DWcFF4QrSq4klPv7Kj+iaxBGEbcBDLQG6iFZG0NBRqV3s
AtYY3bzKmmT0rpgmOxyruDq9RCBY8TbhfS4+xkt6VtJPS5rQgF15QOS0rj4g
nxAq0MaRRlqYTj2eWIjFoQWhsMmiQ2hKEdU0TxCXherClVhy4sIQhXklcBHZ
n66uGDkSZWHpbYKJxQgSDLYlOES8KHhFzlvuZUtZu8ixZfa6RYFxfGUjBlWG
XbYKhBwziLftlSiPcLaB/VSIbBaKn4YiSpc0CmbpbLAC7hekckKZ9li7IoXh
EfFbTOxGKDwFSkoBkdj+YN41y7N3tZzbikUfxe5V7Fs85gi4WlctXxcSucBG
RC07IHhhBIK0BX8R7vhQ169YTuvNikMm8w2BFCIAdoWAF8yN5XLQ6g4EdaBW
2ARJMCD0ijZZCoKzEIZXaMldGFoYMj+T3Bk+9zFwL0fAoVuTkRIEmzgGFi6t
hLVyqj4lpwVt1jad2AAHHARFxorK5+J0Phc+cQOnXqCtWc7CAQnD4eYoL8cX
TBFkwUJLi7KfUZ3HZD4FjQ9hB28YSjyCkWsiRHY+sHjpyl3H3mM54T5MSnZk
TJBniR2XhV6+vuhYLbAWEV2pBHGUajZDetxXwSH4Mqs7YX7KOusUbRfzg0re
F2vE/JPTWCyB5EYVXP2gA5RTxHGYUuk4EJuPJseTPq2XqjkeSVzBVOLm6WUy
BWvKBVXIEC+yRQtwbU+5yx+gGj8JtDp6hScjgF0ciwpBgBfY6+Pw29GL5gFx
IGCem320wNpPn5PBhcBhRAagYqVTcpHudyyt222wan19jdyC4dWJIVCFd01D
cUPw9S3JRuVR0r0FilazjAasOSfS6inPskS/R+8yKyZU9gDOeDSisEQCUycQ
2moBrq1poCEO+gDdXJ6KoF0Kq7OWFEbmTDzZvMinLOjNVHT+9On05cHz3b1n
5sqJgEpOtbVPD8t8mY9SFIzzMLqNDzKTyNrY9Kn5ow7QZJz9mYOkdtidv5cp
rCuHnXMSvSbY29u79truLr1jKfhUJTUepU5Mi29gFlKzfejPaeTEBjkNyYmw
OtghelRwwHud3p1BMUoKlU+/sZHvPe1MT9yslnadrr5Lur5v/KyKwqtfNOg0
n/vLBxvl8d2xqkIQiVm1m5LtCEL7/qZ3jeOW4kV+cjcV8ciJLzi2Jj6re+ax
xQjNt0UIhEB2wbKwBAEK8YdPHEpEPDXHgQgLjItwSTOdmQC/g0tp+gFvgskU
FbZ5MSM8aZmECA8wRvgEbdgCDkl+rltKI7kBnoIQoYSlbZdr4Iwi8M3LixpF
xsH/A2rRfNaLCwEA

-->

</rfc>
