<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version  -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>


<rfc ipr="trust200902" docName="draft-enger-httpbis-http4-wiqc-00" category="exp" submissionType="IETF">

  <front>
    <title abbrev="HTTP/4 over WIQC">HTTP/4: Mapping HTTP Semantics over the WIQC Decentralized Real-Time Torrent Transport Protocol</title>

    <author initials="S." surname="Enger" fullname="Sebastian Enger">
      <organization abbrev="ESE">Einzelunternehmen Sebastian Enger</organization>
      <address>
        <postal>
          <street>Linienstrasse 11</street>
          <city>Brandenburg an der Havel</city>
          <code>D-14776</code>
          <country>Germany</country>
        </postal>
        <email>Sebastian.Enger@Gmail.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="18"/>

    <area>Applications and Real-Time</area>
    <workgroup>HTTP Working Group</workgroup>
    <keyword>HTTP/4</keyword> <keyword>WIQC</keyword> <keyword>P2P</keyword> <keyword>Real-Time Streaming</keyword> <keyword>Decentralized Torrent</keyword> <keyword>Merkle Tree</keyword>

    <abstract>


<t>This document specifies HTTP/4, an application-layer mapping of HTTP
semantics over a decentralized, peer-to-peer real-time streaming
transport protocol named WIQC (Web-Integrated QUIC-derived
Content-swarming). By design, the HTTP/4 protocol allows
decentralized real-time streaming via a torrent protocol called not
QUIC but WIQC. While HTTP/3 delegates stream multiplexing and
congestion control to unicast client-server QUIC connections, HTTP/4
extends these capabilities to multipoint peer swarms. WIQC integrates
encrypted UDP stream multiplexing with fine-grained cryptographic
block verification using SHA-256 Merkle hash trees, live
sliding-window chunk addressing, Unified Merkle Tree signatures for
low-latency live streams, mutual peer authentication without
centralized certificate authorities, and native UDP hole punching.
This specification defines the wire framing, stream mapping, swarm
discovery headers, real-time object prioritization, and security
properties required to operate HTTP/4 natively across decentralized
networks.</t>



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>The architectural evolution of the Hypertext Transfer Protocol has
progressively decoupled high-level application semantics <xref target="RFC9110"/>
from underlying transport bindings. While HTTP/1.1 and HTTP/2 rely
primarily on Transmission Control Protocol (TCP) connections, HTTP/3
<xref target="RFC9114"/> maps HTTP semantics onto the QUIC transport protocol
<xref target="RFC9000"/> to eliminate transport-layer head-of-line blocking and
reduce handshake latency. However, HTTP/3 remains fundamentally bound
to a centralized, unicast client-server topology. Real-time media
delivery and large-scale content distribution over HTTP/3 still require
centralized Content Delivery Network (CDN) relay infrastructures
<xref target="I-D.ietf-moq-transport"/>.</t>

<t>This document establishes the foundational mandate for the next
generation of web transport:</t>

<t>The HTTP/4 protocol will allow decentralized real time streaming via
torrent protocol called not QUIC but WIQC.</t>

<t>To fulfill this mandate, this specification defines WIQC
(Web-Integrated QUIC-derived Content-swarming) as the underlying
transport layer for HTTP/4. Rather than treating a resource origin as
a single IP endpoint, HTTP/4 treats content representations and live
media tracks as cryptographically verifiable swarms. Peers
participating in an HTTP/4 exchange simultaneously act as consumers
and relays, exchanging independent streams and unreliable datagrams
<xref target="RFC9221"/> across a decentralized mesh.</t>

<t>WIQC synthesizes four core protocol mechanisms into a unified
transport layer:</t>

<t><list style="numbers">
  <t>Multiplexed Encrypted Framing: Derived from <xref target="RFC9000"/>, providing
connection migration, 0-RTT/1-RTT setup, and independent per-stream
flow control.</t>
  <t>Real-Time Swarm Integrity and Torrent Framing: Incorporating the
bin-based chunk addressing, Live Discard Window, and Unified Merkle
Tree live signature mechanisms of the Peer-to-Peer Streaming Peer
Protocol (PPSPP) <xref target="RFC7574"/> alongside the 16 KiB SHA-256 Merkle
leaf verification of BitTorrent v2 <xref target="BEP52"/>.</t>
  <t>Sub-Second Media Hierarchy: Adapting the Track, Group, Subgroup,
and Object data model of Media over QUIC Transport
<xref target="I-D.ietf-moq-transport"/> so that each Subgroup maps to an
independent unidirectional WIQC stream for immediate peer-to-peer
forwarding and Earliest Deadline First (EDF) scheduling.</t>
  <t>Decentralized Mutual Authentication and NAT Traversal: Utilizing
self-signed X.509 certificates carrying the libp2p Public Key
Extension <xref target="LIBP2P-TLS"/> over TLS 1.3 <xref target="RFC9846"/> and native
path-probing frames <xref target="I-D.seemann-quic-nat-traversal"/> to establish
direct peer-to-peer paths across Network Address Translators (NATs).</t>
</list></t>

</section>
<section anchor="conventions-and-definitions" title="Conventions and Definitions">

<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and
“OPTIONAL” in this document are to be interpreted as described in
BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all
capitals, as shown here.</t>

<t>This document uses the variable-length integer encoding and packet
formatting conventions defined in Section 1.3 of <xref target="RFC9000"/>.</t>

<t>The following terms are used throughout this specification:</t>

<t><list style="symbols">
  <t>WIQC Endpoint: A network node implementing the WIQC transport
protocol capable of simultaneously initiating and accepting swarm
streams as both an HTTP/4 client (subscriber/leecher) and an HTTP/4
peer server (publisher/seeder).</t>
  <t>Swarm Identifier (Swarm ID): A cryptographic identifier uniquely
representing an HTTP/4 resource or live stream. For static
representations, the Swarm ID is the 32-byte SHA-256 Merkle root
(pieces root) <xref target="BEP52"/>. For live streams, the Swarm ID is the
public key fingerprint of the origin publisher <xref target="RFC7574"/>.</t>
  <t>Leaf Block: The smallest unit of cryptographic verification in WIQC,
fixed at 16 KiB (16,384 bytes) in accordance with <xref target="BEP52"/>.</t>
  <t>Munro Hash: An interior node root of a power-of-two subtree within a
Unified Merkle Tree <xref target="RFC7574"/> that is cryptographically signed by
the live origin publisher via a SIGNED_INTEGRITY frame to authenticate
dynamically generated live streaming chunks.</t>
  <t>Subgroup Stream: A unidirectional WIQC stream carrying a sequence of
media or data Objects that share a delivery priority and decoding
dependency <xref target="I-D.ietf-moq-transport"/>.</t>
</list></t>

</section>
<section anchor="the-wiqc-transport-protocol-architecture" title="The WIQC Transport Protocol Architecture">

<section anchor="relationship-to-quic-and-peer-to-peer-swarming" title="Relationship to QUIC and Peer-to-Peer Swarming">

<t>WIQC preserves the UDP packet framing, long and short headers,
connection IDs, and per-stream reliability mechanisms of <xref target="RFC9000"/>,
but replaces the asymmetric client-server session model with a
symmetric swarm channel model. A single HTTP/4 logical request can be
satisfied concurrently by multiple WIQC connections to distinct peers
participating in the same Swarm ID.</t>

<t>Figure 1 illustrates the architectural layering of HTTP/4 over WIQC
compared to HTTP/2 and HTTP/3:</t>

<figure title="HTTP/4 over WIQC Protocol Stack Comparison" anchor="fig-protocol-stack"><artwork type="ascii-art"><![CDATA[
+----------------------------------------------------------------+
|                   HTTP Semantics (RFC 9110)                    |
+-------------------+--------------------+-----------------------+
| HTTP/2 (RFC 9113) | HTTP/3 (RFC 9114)  |   HTTP/4 over WIQC    |
+-------------------+--------------------+-----------------------+
|   HPACK Framing   | QPACK + H3 Frames  | QPACK + RFC 9421 Sig. |
+-------------------+--------------------+-----------------------+
| TLS 1.2/1.3 (PKIX)| QUIC Streams(9000) | MOQT Subgroups + EDF  |
+-------------------+--------------------+-----------------------+
| TCP (Single Stream| TLS 1.3 (CA PKIX)  | WIQC Swarm (RFC7574)  |
+-------------------+--------------------+-----------------------+
|    IP / Unicast   |    UDP / Unicast   | Mutual TLS 1.3        |
+-------------------+--------------------+-----------------------+
|                   |                    | UDP + Hole Punching   |
+-------------------+--------------------+-----------------------+
]]></artwork></figure>

</section>
<section anchor="swarm-handshake-and-channel-multiplexing" title="Swarm Handshake and Channel Multiplexing">

<t>During connection establishment or stream initialization, WIQC
endpoints exchange swarm capabilities derived from <xref target="RFC7574"/> and
<xref target="BEP52"/>:</t>

<t><list style="numbers">
  <t>Swarm Metadata Negotiation: Endpoints negotiate the Swarm
Identifier (Option Code 2), Content Integrity Protection Method
(Option Code 3), Merkle Hash Tree Function (Option Code 4, fixed to
SHA-256, code 0x02), Chunk Addressing Method (Option Code 6,
defaulting to 64-bit bins, code 0x03), and Live Discard Window
(Option Code 7) as defined in <xref target="RFC7574"/>.</t>
  <t>Anti-Amplification Rule: In accordance with <xref target="RFC7574"/> and
<xref target="RFC9000"/>, an initiating peer’s first flight MUST NOT contain
heavy payloads (such as DATA or SIGNED_INTEGRITY frames) prior to
address validation via channel ID echoing or QUIC PATH_RESPONSE
verification.</t>
</list></t>

</section>
<section anchor="cryptographic-integrity-static-and-live-torrent-modes" title="Cryptographic Integrity: Static and Live Torrent Modes">

<t>Because HTTP/4 peers receive byte ranges and real-time media frames
from untrusted swarm participants, transport-level TLS 1.3 encryption
<xref target="RFC9846"/> only protects the hop-by-hop channel. End-to-end content
integrity MUST be verified at the block or object level before data
is passed to the HTTP/4 application or forwarded to other peers:</t>

<t><list style="symbols">
  <t>Static Content Mode (BEP 52 Merkle Mode): Content is divided into
16 KiB leaf blocks hashed with SHA-256 into a binary Merkle tree
<xref target="BEP52"/>. Peers exchange standard peer wire protocol messages
(IDs 21, 22, and 23 for hash request, hashes, and hash reject) to
fetch missing uncle hashes required to verify a 16 KiB block
immediately upon arrival. Corrupt blocks are discarded immediately,
and the offending peer is isolated.</t>
  <t>Decentralized Real-Time Streaming Mode (Unified Merkle Tree Mode):
Since the total stream length is unknown ahead of time in live
streaming, WIQC utilizes Content Integrity Protection Method 3
(Unified Merkle Tree) from <xref target="RFC7574"/>. As the publisher generates
new groups of real-time chunks, it computes the binary subtree root
(the munro hash) covering the newly generated bin range, signs the
munro hash using its private key, and distributes SIGNED_INTEGRITY
and INTEGRITY frames across the swarm. Receiving peers verify each
chunk against its munro branch before playback and immediately
re-seed verified chunks to downstream peers.</t>
</list></t>

</section>
</section>
<section anchor="real-time-streaming-and-swarm-scheduling-in-http4" title="Real-Time Streaming and Swarm Scheduling in HTTP/4">

<section anchor="media-data-model-mapping" title="Media Data Model Mapping">

<t>To achieve sub-second real-time latency across a decentralized torrent
swarm, HTTP/4 adopts the hierarchical data model of
<xref target="I-D.ietf-moq-transport"/>:</t>

<t><list style="symbols">
  <t>Track: Identified by a tuple of Track Namespace (bound to the HTTP/4
:authority and :path pseudo-headers) and Track Name (e.g., video
bitrate variant, audio channel, or catalog track).</t>
  <t>Group: A temporally bounded collection of objects starting at an
independent synchronization point (such as an IDR keyframe),
directly aligned with a WIQC Unified Merkle Tree munro subtree.</t>
  <t>Subgroup: A subset of objects within a Group sharing a common
priority and dependency chain. Each Subgroup MUST be mapped to
exactly one unidirectional WIQC stream. If packet loss occurs on a
lower-priority enhancement layer Subgroup, higher-priority base
layer Subgroups proceed without head-of-line blocking.</t>
  <t>Object: The smallest addressable media unit (e.g., a single encoded
video frame or Low Overhead Container (LOC) payload).</t>
</list></t>

</section>
<section anchor="hybrid-earliest-deadline-first-edf-and-rarest-first-scheduling" title="Hybrid Earliest Deadline First (EDF) and Rarest-First Scheduling">

<t>Traditional torrent protocols rely purely on Rarest-First piece
selection, which maximizes swarm diversity but ignores playback
deadlines. Conversely, purely sequential fetching causes swarm starvation.
WIQC endpoints implementing HTTP/4 real-time streaming MUST implement a
dual-zone sliding window scheduler within the negotiated Live Discard
Window <xref target="RFC7574"/>, extending HTTP priority signaling <xref target="RFC9218"/>:</t>

<t><list style="numbers">
  <t>Emergency Priority Zone (EDF Zone): For chunks whose playback
deadline falls within a configurable threshold (e.g., &lt; 150 ms), the
peer requests missing Subgroups strictly in Earliest Deadline First
(EDF) order from the lowest-RTT unchoked peers.</t>
  <t>Swarm Health Zone (Rarest-First Zone): For chunks further ahead in
the Live Discard Window, the peer uses remaining bandwidth to request
the rarest chunks announced via HAVE frames, ensuring robust piece
availability across the swarm.</t>
</list></t>

<t>Figure 2 depicts the dual-zone sliding window scheduler and wire-level
frame multiplexing in WIQC:</t>

<figure title="WIQC Dual-Zone Real-Time Swarm Scheduler and Stream Pipeline" anchor="fig-scheduler-pipeline"><artwork type="ascii-art"><![CDATA[
|<---------------- Live Discard Window (RFC 7574) --------------->|
+---------------------------------+-------------------------------+
|  Emergency Zone (< 150 ms)      |     Swarm Health Zone         |
|  Scheduler: Strictly EDF        |     Scheduler: Rarest-First   |
|  Target: Lowest-RTT Peers       |     Target: HAVE Bin Diversity|
+---------------------------------+-------------------------------+
        |                                         |
        v                                         v
+-----------------------------------------------------------------+
| WIQC Subgroup Stream (0x40): [MOQT Object] + [WIQC_INTEGRITY]   |
| WIQC Swarm Control   (0x41): [WIQC_HAVE]   + [SIGNED_INTEGRITY] |
+-----------------------------------------------------------------+
]]></artwork></figure>

</section>
</section>
<section anchor="expressing-http-semantics-over-wiqc" title="Expressing HTTP Semantics over WIQC">

<section anchor="http4-stream-mapping" title="HTTP/4 Stream Mapping">

<t>HTTP/4 preserves the stream categories of <xref target="RFC9114"/> while introducing
swarm-specific stream types:</t>

<texttable>
      <ttcol align='left'>Stream Type ID</ttcol>
      <ttcol align='left'>Stream Name</ttcol>
      <ttcol align='left'>Directionality</ttcol>
      <ttcol align='left'>Purpose in HTTP/4 over WIQC</ttcol>
      <c>0x00</c>
      <c>Control Stream</c>
      <c>Unidirectional (pair)</c>
      <c>Carries SETTINGS, GOAWAY, MAX_PUSH_ID, and swarm capabilities.</c>
      <c>0x01</c>
      <c>Push Stream</c>
      <c>Unidirectional</c>
      <c>Server- or peer-initiated push of promised HTTP/4 representations.</c>
      <c>0x02</c>
      <c>QPACK Encoder</c>
      <c>Unidirectional</c>
      <c>Dynamic header table insertions per <xref target="RFC9204"/>.</c>
      <c>0x03</c>
      <c>QPACK Decoder</c>
      <c>Unidirectional</c>
      <c>Header table acknowledgments and stream cancellations per <xref target="RFC9204"/>.</c>
      <c>0x40</c>
      <c>WIQC Swarm Subgroup</c>
      <c>Unidirectional</c>
      <c>Carries a single real-time media Subgroup alongside its Merkle INTEGRITY proof.</c>
      <c>0x41</c>
      <c>WIQC Swarm Control</c>
      <c>Bidirectional</c>
      <c>Exchanges HAVE, REQUEST, CANCEL, CHOKE, UNCHOKE, and SIGNED_INTEGRITY frames.</c>
</texttable>

</section>
<section anchor="http4-frame-layout-and-extensions" title="HTTP/4 Frame Layout and Extensions">

<t>All HTTP/4 frames follow the variable-length integer framing layout of
Section 7.1 of <xref target="RFC9114"/>: Type (i), Length (i), and Frame Payload (..).
In addition to DATA (0x00), HEADERS (0x01), CANCEL_PUSH (0x03),
SETTINGS (0x04), PUSH_PROMISE (0x05), GOAWAY (0x07), and MAX_PUSH_ID
(0x0d), HTTP/4 defines the following WIQC swarm frames:</t>

<texttable>
      <ttcol align='left'>Frame Type</ttcol>
      <ttcol align='left'>Frame Name</ttcol>
      <ttcol align='left'>Permitted Streams</ttcol>
      <ttcol align='left'>Description</ttcol>
      <c>0x4101</c>
      <c>WIQC_HAVE</c>
      <c>WIQC Swarm Control</c>
      <c>Announces possession of verified 64-bit bin ranges <xref target="RFC7574"/>.</c>
      <c>0x4102</c>
      <c>WIQC_INTEGRITY</c>
      <c>WIQC Swarm Subgroup / Control</c>
      <c>Carries uncle hashes or Merkle branch proofs <xref target="RFC7574"/> <xref target="BEP52"/>.</c>
      <c>0x4103</c>
      <c>WIQC_SIGNED_INTEGRITY</c>
      <c>WIQC Swarm Subgroup / Control</c>
      <c>Carries publisher-signed munro root hashes for live streaming <xref target="RFC7574"/>.</c>
      <c>0x4104</c>
      <c>WIQC_PEX</c>
      <c>Control / WIQC Swarm Control</c>
      <c>Peer Exchange (PEX_RESv4, PEX_RESv6, PEX_REQ) for trackerless discovery <xref target="RFC7574"/>.</c>
</texttable>

</section>
<section anchor="http-header-fields-for-swarm-integrity-and-origin-authentication" title="HTTP Header Fields for Swarm Integrity and Origin Authentication">

<t>When initiating a request or responding over HTTP/4, endpoints combine
standard HTTP integrity and signature headers with WIQC swarm metadata:</t>

<t><list style="numbers">
  <t>Representation Digest (Repr-Digest and Content-Digest): In accordance
with <xref target="RFC9530"/>, static HTTP/4 responses MUST include a Repr-Digest
header encoding the SHA-256 root hash, accompanied by a Swarm-Root
dictionary field carrying the BEP 52 pieces root.</t>
  <t>Origin Message Signatures (Signature-Input and Signature): Because
HTTP/4 responses may be assembled from multiple untrusted peers, the
origin server signs the response metadata (@status, content-type,
repr-digest, and wiqc-swarm-id) using <xref target="RFC9421"/>. Any peer in the
swarm can forward the signed header block, and any receiving client
can cryptographically verify that the metadata originated from the
authoritative publisher.</t>
  <t>Alternative Service and Discovery: Transition from unicast HTTP/3
<xref target="RFC7838"/> or DNS resolution via SVCB/HTTPS records <xref target="RFC9460"/> to
HTTP/4 swarms is accomplished by advertising “h4” ALPN endpoints.</t>
  <t>HTTP Datagrams and Capsule Protocol: Ultra-low-latency unreliable
media objects MAY be transmitted via QUIC DATAGRAM frames <xref target="RFC9221"/>
associated with an HTTP/4 request stream, or encapsulated via the
DATAGRAM Capsule (0x00) per <xref target="RFC9297"/> when traversing HTTP
intermediaries.</t>
</list></t>

</section>
</section>
<section anchor="decentralized-peer-authentication-and-nat-traversal" title="Decentralized Peer Authentication and NAT Traversal">

<section anchor="mutual-tls-13-with-self-signed-peer-identity" title="Mutual TLS 1.3 with Self-Signed Peer Identity">

<t>In a decentralized torrent swarm, peers typically lack domain names and
cannot obtain certificates from commercial PKIX Certificate Authorities
(CAs). Therefore, WIQC mandates mutual authentication over TLS 1.3
<xref target="RFC9846"/> using the libp2p TLS handshake mechanism <xref target="LIBP2P-TLS"/>:</t>

<t><list style="symbols">
  <t>Both dialing and listening WIQC endpoints MUST present a single
self-signed X.509 certificate during the TLS 1.3 handshake (chains
longer than one certificate MUST cause connection termination).</t>
  <t>The certificate MUST include the libp2p Public Key Extension
identified by Object Identifier (OID) 1.3.6.1.4.1.53594.1.1.</t>
  <t>The extension contains an ASN.1-encoded SignedKey structure holding
the peer’s public host key (e.g., Ed25519) and a cryptographic
signature over the concatenation of the ASCII string
“libp2p-tls-handshake:” and the DER-encoded SubjectPublicKeyInfo of
the ephemeral certificate key.</t>
  <t>For browser-based HTTP/4 endpoints operating over WebTransport, where
the browser enforces CA checks or certificate pinning, endpoints MAY
authenticate peers by embedding the certificate hash (certhash) in the
peer advertisement and performing an in-band cryptographic binding
handshake on the first stream.</t>
</list></t>

</section>
<section anchor="native-wiqc-nat-traversal" title="Native WIQC NAT Traversal">

<t>To enable direct peer-to-peer streaming between home and mobile nodes
behind NATs without relying on external ICE/STUN/TURN stacks, WIQC
incorporates the native QUIC NAT traversal extension
<xref target="I-D.seemann-quic-nat-traversal"/>:</t>

<t><list style="symbols">
  <t>Well-connected relay or seed peers inform joining peers of their
external UDP socket address using the OBSERVED_ADDRESS frame.</t>
  <t>Peers advertise candidate addresses over existing swarm connections
using ADD_ADDRESS (0x3d7e90..0x3d7e91) and REMOVE_ADDRESS (0x3d7e94)
frames, and coordinate simultaneous UDP hole punching via
PUNCH_ME_NOW (0x3d7e92..0x3d7e93) or grant-based PUNCH_REQUEST frames
followed by standard PATH_CHALLENGE and PATH_RESPONSE validation
<xref target="RFC9000"/>.</t>
</list></t>

</section>
</section>
<section anchor="formal-syntax-abnf" title="Formal Syntax (ABNF)">

<t>The following Augmented Backus-Naur Form (ABNF) grammar <xref target="RFC5234"/>
defines the syntax of the WIQC-Swarm-Info HTTP header field and the h4
Alternative Service discovery token:</t>

<figure><artwork type="abnf" name="wiqc-abnf-syntax"><![CDATA[
WIQC-Swarm-Info = "swarm-id=" byte-sequence ";"
                  "mode=" ( "merkle-v2" / "unified-live" )
                  [ ";window=" 1*DIGIT ]
                  [ ";chunk-addr=" ( "bin32" / "bin64" ) ]

byte-sequence   = ":" *( BASE64CHAR ) ":"
BASE64CHAR      = ALPHA / DIGIT / "+" / "/" / "="

h4-alpn-id      = %x68.34 ; "h4" in ASCII
wiqc-alpn-id    = %x77.69.71.63 ; "wiqc" in ASCII
]]></artwork></figure>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>This section analyzes the threat model of HTTP/4 over WIQC in accordance
with <xref target="RFC3552"/>.</t>

<section anchor="stream-pollution-attacks-in-decentralized-swarms" title="Stream Pollution Attacks in Decentralized Swarms">

<t>In peer-to-peer live streaming, a malicious peer with high upload
bandwidth can inject corrupted chunks (“pollution attack”) to degrade
playback across the swarm. WIQC mitigates this by enforcing mandatory
cryptographic verification before forwarding: every 16 KiB block in
static mode is verified against the SHA-256 Merkle root <xref target="BEP52"/>, and
every live chunk in Unified Merkle Tree mode is verified against a
publisher-signed munro hash <xref target="RFC7574"/>. Merkle-tree chaining keeps
cryptographic verification bandwidth overhead around 5% (as evaluated
under 128-bit MD5 and 1024-bit RSA reference parameters) while enabling
deterministic identification and immediate banning of polluting peers.</t>

</section>
<section anchor="reflection-and-amplification-attacks" title="Reflection and Amplification Attacks">

<t>Because WIQC operates over UDP, unverified source IP addresses pose a
reflection amplification risk. Endpoints MUST enforce the
anti-amplification limits of <xref target="RFC9000"/> and MUST echo the peer’s
randomly chosen Channel ID per Section 12.1 of <xref target="RFC7574"/> before
transmitting heavy payloads such as DATA or SIGNED_INTEGRITY messages.</t>

</section>
<section anchor="compression-side-channels-and-replay-risks" title="Compression Side Channels and Replay Risks">

<t>When using QPACK <xref target="RFC9204"/> in HTTP/4, endpoints MUST NOT compress
sensitive authentication tokens alongside attacker-controlled data within
the same dynamic table context (Section 10.6 of <xref target="RFC9114"/>).
Furthermore, 0-RTT swarm requests MUST only be used for idempotent
operations (such as subscribing to public live tracks) to prevent replay
attacks.</t>

</section>
</section>
<section anchor="iana-considerations" title="IANA Considerations">

<section anchor="alpn-protocol-id-registration" title="ALPN Protocol ID Registration">

<t>This document requests IANA to register the following Application-Layer
Protocol Negotiation (ALPN) IDs in the “TLS Application-Layer Protocol
Negotiation (ALPN) Protocol IDs” registry:</t>

<t><list style="symbols">
  <t>Protocol: HTTP/4 over WIQC</t>
  <t>Identification Sequence: 0x68 0x34 (“h4”)</t>
  <t>Reference: This document</t>
  <t>Protocol: Raw WIQC Swarm Transport</t>
  <t>Identification Sequence: 0x77 0x69 0x71 0x63 (“wiqc”)</t>
  <t>Reference: This document</t>
</list></t>

</section>
<section anchor="http-header-field-registration" title="HTTP Header Field Registration">

<t>This document requests registration of the WIQC-Swarm-Info field in
the “Hypertext Transfer Protocol (HTTP) Field Name Registry” per
<xref target="RFC9110"/> with status experimental.</t>

</section>
</section>


  </middle>

  <back>

    <references title='Normative References'>



<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/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="RFC5234" target="https://www.rfc-editor.org/info/rfc5234">
  <front>
    <title>Augmented BNF for Syntax Specifications: ABNF</title>
    <author fullname="D. Crocker" initials="D." role="editor" surname="Crocker"/>
    <author fullname="P. Overell" initials="P." surname="Overell"/>
    <date month="January" year="2008"/>
    <abstract>
      <t>Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="68"/>
  <seriesInfo name="RFC" value="5234"/>
  <seriesInfo name="DOI" value="10.17487/RFC5234"/>
</reference>

<reference anchor="RFC7574" target="https://www.rfc-editor.org/info/rfc7574">
  <front>
    <title>Peer-to-Peer Streaming Peer Protocol (PPSPP)</title>
    <author fullname="A. Bakker" initials="A." surname="Bakker"/>
    <author fullname="R. Petrocco" initials="R." surname="Petrocco"/>
    <author fullname="V. Grishchenko" initials="V." surname="Grishchenko"/>
    <date month="July" year="2015"/>
    <abstract>
      <t>The Peer-to-Peer Streaming Peer Protocol (PPSPP) is a protocol for disseminating the same content to a group of interested parties in a streaming fashion. PPSPP supports streaming of both prerecorded (on- demand) and live audio/video content. It is based on the peer-to- peer paradigm, where clients consuming the content are put on equal footing with the servers initially providing the content, to create a system where everyone can potentially provide upload bandwidth. It has been designed to provide short time-till-playback for the end user and to prevent disruption of the streams by malicious peers. PPSPP has also been designed to be flexible and extensible. It can use different mechanisms to optimize peer uploading, prevent freeriding, and work with different peer discovery schemes (centralized trackers or Distributed Hash Tables). It supports multiple methods for content integrity protection and chunk addressing. Designed as a generic protocol that can run on top of various transport protocols, it currently runs on top of UDP using Low Extra Delay Background Transport (LEDBAT) for congestion control.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7574"/>
  <seriesInfo name="DOI" value="10.17487/RFC7574"/>
</reference>

<reference anchor="RFC7838" target="https://www.rfc-editor.org/info/rfc7838">
  <front>
    <title>HTTP Alternative Services</title>
    <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
    <author fullname="P. McManus" initials="P." surname="McManus"/>
    <author fullname="J. Reschke" initials="J." surname="Reschke"/>
    <date month="April" year="2016"/>
    <abstract>
      <t>This document specifies "Alternative Services" for HTTP, which allow an origin's resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7838"/>
  <seriesInfo name="DOI" value="10.17487/RFC7838"/>
</reference>

<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>

<reference anchor="RFC9000" target="https://www.rfc-editor.org/info/rfc9000">
  <front>
    <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
    <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
    <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
    <date month="May" year="2021"/>
    <abstract>
      <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9000"/>
  <seriesInfo name="DOI" value="10.17487/RFC9000"/>
</reference>

<reference anchor="RFC9110" target="https://www.rfc-editor.org/info/rfc9110">
  <front>
    <title>HTTP Semantics</title>
    <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
    <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
    <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
      <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="97"/>
  <seriesInfo name="RFC" value="9110"/>
  <seriesInfo name="DOI" value="10.17487/RFC9110"/>
</reference>

<reference anchor="RFC9114" target="https://www.rfc-editor.org/info/rfc9114">
  <front>
    <title>HTTP/3</title>
    <author fullname="M. Bishop" initials="M." role="editor" surname="Bishop"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9114"/>
  <seriesInfo name="DOI" value="10.17487/RFC9114"/>
</reference>

<reference anchor="RFC9204" target="https://www.rfc-editor.org/info/rfc9204">
  <front>
    <title>QPACK: Field Compression for HTTP/3</title>
    <author fullname="C. Krasic" initials="C." surname="Krasic"/>
    <author fullname="M. Bishop" initials="M." surname="Bishop"/>
    <author fullname="A. Frindell" initials="A." role="editor" surname="Frindell"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>This specification defines QPACK: a compression format for efficiently representing HTTP fields that is to be used in HTTP/3. This is a variation of HPACK compression that seeks to reduce head-of-line blocking.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9204"/>
  <seriesInfo name="DOI" value="10.17487/RFC9204"/>
</reference>

<reference anchor="RFC9218" target="https://www.rfc-editor.org/info/rfc9218">
  <front>
    <title>Extensible Prioritization Scheme for HTTP</title>
    <author fullname="K. Oku" initials="K." surname="Oku"/>
    <author fullname="L. Pardue" initials="L." surname="Pardue"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>This document describes a scheme that allows an HTTP client to communicate its preferences for how the upstream server prioritizes responses to its requests, and also allows a server to hint to a downstream intermediary how its responses should be prioritized when they are forwarded. This document defines the Priority header field for communicating the initial priority in an HTTP version-independent manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing responses. These share a common format structure that is designed to provide future extensibility.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9218"/>
  <seriesInfo name="DOI" value="10.17487/RFC9218"/>
</reference>

<reference anchor="RFC9221" target="https://www.rfc-editor.org/info/rfc9221">
  <front>
    <title>An Unreliable Datagram Extension to QUIC</title>
    <author fullname="T. Pauly" initials="T." surname="Pauly"/>
    <author fullname="E. Kinnear" initials="E." surname="Kinnear"/>
    <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
    <date month="March" year="2022"/>
    <abstract>
      <t>This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9221"/>
  <seriesInfo name="DOI" value="10.17487/RFC9221"/>
</reference>

<reference anchor="RFC9297" target="https://www.rfc-editor.org/info/rfc9297">
  <front>
    <title>HTTP Datagrams and the Capsule Protocol</title>
    <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
    <author fullname="L. Pardue" initials="L." surname="Pardue"/>
    <date month="August" year="2022"/>
    <abstract>
      <t>This document describes HTTP Datagrams, a convention for conveying multiplexed, potentially unreliable datagrams inside an HTTP connection.</t>
      <t>In HTTP/3, HTTP Datagrams can be sent unreliably using the QUIC DATAGRAM extension. When the QUIC DATAGRAM frame is unavailable or undesirable, HTTP Datagrams can be sent using the Capsule Protocol, which is a more general convention for conveying data in HTTP connections.</t>
      <t>HTTP Datagrams and the Capsule Protocol are intended for use by HTTP extensions, not applications.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9297"/>
  <seriesInfo name="DOI" value="10.17487/RFC9297"/>
</reference>

<reference anchor="RFC9421" target="https://www.rfc-editor.org/info/rfc9421">
  <front>
    <title>HTTP Message Signatures</title>
    <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/>
    <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
    <author fullname="M. Sporny" initials="M." surname="Sporny"/>
    <date month="February" year="2024"/>
    <abstract>
      <t>This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9421"/>
  <seriesInfo name="DOI" value="10.17487/RFC9421"/>
</reference>

<reference anchor="RFC9460" target="https://www.rfc-editor.org/info/rfc9460">
  <front>
    <title>Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)</title>
    <author fullname="B. Schwartz" initials="B." surname="Schwartz"/>
    <author fullname="M. Bishop" initials="M." surname="Bishop"/>
    <author fullname="E. Nygren" initials="E." surname="Nygren"/>
    <date month="November" year="2023"/>
    <abstract>
      <t>This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9460"/>
  <seriesInfo name="DOI" value="10.17487/RFC9460"/>
</reference>

<reference anchor="RFC9530" target="https://www.rfc-editor.org/info/rfc9530">
  <front>
    <title>Digest Fields</title>
    <author fullname="R. Polli" initials="R." surname="Polli"/>
    <author fullname="L. Pardue" initials="L." surname="Pardue"/>
    <date month="February" year="2024"/>
    <abstract>
      <t>This document defines HTTP fields that support integrity digests. The Content-Digest field can be used for the integrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digest and Want-Repr-Digest can be used to indicate a sender's interest and preferences for receiving the respective Integrity fields.</t>
      <t>This document obsoletes RFC 3230 and the Digest and Want-Digest HTTP fields.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9530"/>
  <seriesInfo name="DOI" value="10.17487/RFC9530"/>
</reference>

<reference anchor="RFC9846" target="https://www.rfc-editor.org/info/rfc9846">
  <front>
    <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
    <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
    <date month="July" year="2026"/>
    <abstract>
      <t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
      <t>This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9846"/>
  <seriesInfo name="DOI" value="10.17487/RFC9846"/>
</reference>


<reference anchor="BEP52" target="https://www.bittorrent.org/beps/bep_0052.html">
  <front>
    <title>The BitTorrent Protocol Specification v2</title>
    <author initials="B.5.S." surname="Authors" fullname="BEP 52 Specification Authors">
      <organization></organization>
    </author>
    <date year="2020" month="September"/>
  </front>
  <seriesInfo name="BEP" value="52"/>
</reference>


    </references>

    <references title='Informative References'>



<reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552">
  <front>
    <title>Guidelines for Writing RFC Text on Security Considerations</title>
    <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
    <author fullname="B. Korver" initials="B." surname="Korver"/>
    <date month="July" year="2003"/>
    <abstract>
      <t>All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. 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="72"/>
  <seriesInfo name="RFC" value="3552"/>
  <seriesInfo name="DOI" value="10.17487/RFC3552"/>
</reference>

<reference anchor="I-D.ietf-moq-transport" target="https://datatracker.ietf.org/doc/html/draft-ietf-moq-transport-23">
  <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="I-D.seemann-quic-nat-traversal" target="https://datatracker.ietf.org/doc/html/draft-seemann-quic-nat-traversal-04">
  <front>
    <title>Using QUIC to traverse NATs</title>
    <author fullname="Marten Seemann" initials="M." surname="Seemann"/>
    <author fullname="Eric Kinnear" initials="E." surname="Kinnear">
      <organization>Apple Inc.</organization>
    </author>
    <date day="2" month="November" year="2026"/>
    <abstract>
      <t>This document specifies a QUIC extension for traversing Network Address Translators (NATs). Endpoints use an existing proxied QUIC connection to coordinate path validation attempts that create the NAT bindings needed for a direct path and test its connectivity. Application data can be exchanged over the proxied path while NAT traversal is in progress. Once a suitable direct path has been validated, the connection can migrate to it.</t>
    </abstract>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-seemann-quic-nat-traversal-04"/>
</reference>


<reference anchor="LIBP2P-TLS" target="https://github.com/libp2p/specs/blob/master/tls/tls.md">
  <front>
    <title>libp2p TLS 1.3 Handshake Specification</title>
    <author >
      <organization>Protocol Labs</organization>
    </author>
    <date year="2024"/>
  </front>
</reference>


    </references>


<section anchor="acknowledgements" title="Acknowledgements">

<t>This specification synthesizes foundational work by the IETF HTTP
Working Group, the QUIC Working Group, the Media over QUIC (MOQ)
Working Group, the Peer-to-Peer Streaming Protocol (PPSP) Working
Group, the BitTorrent BEP 52 authors, and the libp2p specification
community.</t>

</section>


  </back>

<!-- ##markdown-source:
H4sIAO/p/WoAA61ca3PbRpb9jl/RpdTUkglBiZT80ky2hpZoWxW9IsqTmZ2a
SoFEk8QYBBgAlMzEmd++5z66AVC0k62NqxJBENB9+/Z9nPtohGEYVEmV2lNz
8O7+/vbw5NRcRet1ki0M/W4mdhVlVTIrTf5gC1Mtrfnh4vszc25nNquKKE1+
trG5s1Ea3icra+7zosAfzH0RZeU6LypzW+RVPsvTgyCaTgv74GeSEWm0gyDO
Z1m0AhVxEc2r0GYLW4TLqlpPk5J/noSPyU+z8OgomEWVXeTF9tTYj+sgWRen
pio2ZTU8Onp1NAyiwkanZrRepwmeTPKsNFHWoDB4zIsPiyLfrE9lhT/gd1ru
W7oXlJvpKilLvFdt16DnYnz/JvjweBoYExqhmy+JbL64Hd7yz5oFkwokrDAk
328zStnDf7myxYcUHCusDcoKRP4YpXlmeTk2CKJNtcwLmTjJylMz6Zsx8QV3
jBFuTew0Kqskyhp/yYvFqRkn2c823WSVLTK7XNls76NuQ8aTMf9egnJbnZrL
JEtsht+isrRmMOA/zpIKPH+NfY1tNt0UC/DVxNjBd9GDTeWRPAZR5+Hg5MWL
53oHNNBevbUFBGnLNyFSSdogvs8U/fUt3e7P8lUQZDmerpIHS8u/e3M2HAxe
6eWz4fGJXr549sJfvjx+qZcvB/7uq6OjI3c5GDQu/QPDo/py8NJfDgf+8tUL
d3lS3z157gd7duwvX548p8vX49tnw1NeqVOte6jN66RyyuFUwkzWdpbMVVDN
w/BAtsXvPP0Lda8xrHk23HllxI+W/GgMxTg1w6PhUXj0SqaPigXt5wFpUHl6
ePj4+NifJlUldPQhKodTuy7pfz8eHT0b9pfVKhUiSlsktkyyee4IAQGnoCAI
6GZ7f46fyYovwvN+Yqt5uMp/CitnAtxfSkvGJAt/2iSzMIsqegImoIxSeuLy
4jV0Kby/nLR5lybT9XBtcN8M+seQtiwul9EH2+bEfs6xLnhuX0bTHU6d7GfT
IqmWmymJ4qHMflhiLrApzaeHKwitLQ6rtKT/+qv4IAjDELpE+jKrguB+mZQG
Bm2zor0uhUpbqvXokdpEtXkK02gLJVqp0c3n/FxQtu1uBE1r2JGeWVsYyCoP
6acpyPZUZHtKb3s8983arZ/kKBbz3fnBTsMLmIdFAV7E5vv3F2chlBlbGgdn
MH6YKywfo4LG6vbN6y0IKJNF1mMXoAbcjxylaf5YBi0a91FlHpIIa1H5q9+f
YQC8keVVQJSY6aZiOvvmh2WS6nzHICG1C9Bb6ohmtUmrZJ3ajzQ2BCOY5TAl
JasGLqsCY1e52WRgdlmZWZrwumxBPOWZ8FRmZ+wnes6+249YflzSSmH+ZtE6
miZpUtEeYjCZM0+IfmI+c6nsC18Tx9IysNms2K6Jue/Pb/cS/AgxM/MksyFe
wY/Y8Bs5flsvk1kAcZt9MCC11vdNSS9O3o3C4bPnzoMso3JpyHRjCSl2MCjT
JMZzcJlZnD+a2XKTfTBRHBe2pPd75n1GIhk3XZCh3Y2qDZ4xUO8AGwrRBCNm
Wx5UV4ApVptqE6WyeFI4S3Iq5NGK8k0VNMVgZotKFmBVP5mVPXbLGVsR5tAy
ByXrTTZbgsS+aFHZMnaxJWbxvmCmwpp5wVLV89wVJerJngRxUs5Ie7ZmaSMI
N+asZTKf/hv7DhFMmKCfeQohqrSzDe5tA8jnmqjHnIWF1SqwHEgA3aTVqBbI
GtKtiWZFXpZtTQ0yWxHiKPsBm4lVEscpvPtX5oLEM96w7JHRAHcKrL0CVRu8
bOxDnm543bAJrHRbIgbCKeBqDvZ70wYRIGoXvMNMDKgAniGtWiaLZZha3G3a
HVNbmF9+UQf566/BvMhX0BdwK92SqNVmZAphwp2ypZOD/oBZxr8MwaWUuJas
oiIBDZiFSVVEZc5UJT3Znfuz2+4eHTwOHE0nv/5K2yrWs0EzRsqZK6zFT42d
DgAAgAHwqE0TiArtmn9WLS/JRpjPwxSyZVjlnDHBdm9mpF7O46g+9M27/BH8
LBy1WDewC5DmHJyLyOzDnm3NFOAnDjB5ZFq2e785qvJ1nuYLjH7nhRT2Oolg
VkkBIcbE6ZScVVjCYlo2cWRHIehVkUxVWmgwpQuWME2d7La0Um084KmOfS1y
ajpn59dd2shoC2sGDcPQmxnbBfB0v4P/9df+rtuDEY6maVIuVV/nxAsWPIg2
NpFcMNkZ/mMGoQ4WNiO1UoF/tFPTABCsH7te55EWx67HPPU85qnnCb7gd0zb
72DCHLuZzmmKilamNPfkt/2GiYOCL7lW88S1mkj4U6tcw3OLgBKXZOkQjQgP
E9MAImhpFcsqFlzmmwKyClu2SIAvyiAyZOohJBe3Bt6MHZbzcPJq6eWnsGuM
QGJbB0zsSFj+aB9mH0qitOWfWMbFO2GrrXeEt3AMsEYRDOcsWQuJRFPmZrcf
Z6B/QS6H/GGU2XxTsv2seBKQACHCGEQHSyLsgr4kg8V2bSkMqZxXYpI3GR4W
WrBVEchclWoHgOhhB9RA74ApaFm5xI6zAy+3Gbl93Cc3uClADRyNF5iVJSqS
EjMmGWv2Rlzp7q5BZAd9c+XcPWYZezzwRtwWIiWVCja6DYPVowkf2IcHHEQ5
+wj3sSjUUx2Fd/f3hwP6P+xitVmL82oyB/4iFAbRMHNSFEVFWO6w34xZae+M
SC08H4/kohVP7kUGZmCJsqVgE40KtxAijiNH/wRmXJJvP4cXjgrgTgYjQmQb
f9AwDEEEZzgc0mS2usBbRb30s46z+TYNUvuV29vJLTwL85TCRNp8BNeLMokt
jzR4br5LXu8gKRojtdG8jbkwdyN2exhiVA7x2Ood981kMw0n8LYZrYf05V0C
QwZfjrB3FEdrxy3yhbMPPUk09Og1TkP0aFZiyo0gEhJds0IkndLMMmLu8arP
q9Bbn7fHpiTvGMEOR7Oln0o8KYltRq83RQViHMNHzNRCiy4IqiL7k6zYFMBm
NwMPlqq8gOzE6jPNOCrg1UpyLFHMLvVNUuDXzvj8TdeUsyV8asoAL4A5aydH
rgRYjtqYkka9Ht3TyjVYNO/h1pKfVTtKm85DEhqM8Pf+s6NXTcQJaxIVxdbt
gMaStxu4ppn5znI+Ykxwn/HJL7/UQSh4yFx3caeoJ0J8EiWPXOl9mLhlCIWd
0iwESW2pO/P5gFdBiXOSNIywvx3Y0dClM1vOQ49Ew0QUAEkQ/5sOOFR2+4Qr
4WIeiH3OkJ+Tc0r4d3GjH+zWYCAEOAdX7yf3Bz35aa5v+PpuDEG7G5/TNdTj
8tJfyBMBfrl5f6l/p6v6zbObq6vx9bm8jLtm59bV6B8HbAGCg5vb+4ub69Hl
AfmGqoUdIug+uDO1HE4V8E1kNSNC1uUMOMeSlQten92awYnsC+WHwFK+pvwP
rh8hQ2Js8gy+RX6FDGwJBNuoYJeUpgHCuwRwjeIRuPVl/pgBERb2CaDZlIpk
HoBtyccAUmcLBHAc8mGvgAxzrwZraLqtAsmTsAGYNbZF8AKtwkzUsJOIQd0b
TqAvuzXPCeCwANuCHB2YsyFzWy2h0gsKt/ZAErifr0WJx+r7YYuMxiLAO7CC
yQqOiZbmlIMfrxr2pQGT1uxVQeCOy2bJUhSCZUezmRV7JxGYqf1zCTgMbtUo
QNCv6ZSbqexqcZhaWHxbdGWsrM63SqAtOLmz3giwLA6hX0BNJPZfOw9Gxox8
C57TO+ddWnoLuZikfgyG76cNhS2mhkGyHEdoA1w1I+G+eYMbJWGmWfPlSAMZ
YqkjwSQiO8fDcLqFEd0J4Is8J3531gnsYcm/dhtehidqx+B7Bic2iV0jBYeA
LUh1KE2hzlOxoWdf0zsyCy/J9b2mCOjUkOiVK4LHJTsHHqXNxJaTxMAkP+TM
5gnBHfge9bGdwfPe8csTQysvu6x3MwCJOMpmVnIgTYf6NdxAVuTmXVQusXGZ
2AAE6SK1xBsiJTJrxGAFBW6QaQMhogQID0cTgIx9OY4mHmD3mOzDtOpMpiQT
4jUe9nBPUlmTi7fX4/MfL67vx2/vLu7/IQ6AfWztxmhv4m0GsCITaKhj4+au
spEgCFWKPDufLTCHZPgLPtp7OcB+RHuWWJvPMa0geHCPYYVAjFLWjpgWtoTA
sIaAmgsR9Ef5AwWgDiXMtl9AHOx77p0ZeVr+MaM6u0H5j6+APlPRlWWyJoYx
vqGp2yhPIyXF56xksAOiT5Q3ElNb54II5kkaZ0nzu9RP0EDRF+eafqoBspHQ
gfJ82x3g2QTmAUWIUPU0mikJUbkFNkL4PduJ50srSQ+BciznUVA/zAbS0DwZ
/swP9bHHGrSp6UnzBYkMR/CkiDNYpakNSvCtZOHGomYbBqaUb9j6/KLsQiOx
QgymNEGSKcbYE6HRcsqojgbOsadvkgVB8YFBILyhDHfl1t1KVnHM08hfN6t7
4PwKc0nuTBNFPmd0DE/1n//8B2ycJUkIioJvwv/nv2+CT+bpv51qZgd7aijn
1d3zrPm0l4q9lH2OXKJCF+vmOu6aTy4z4+6dYP5PSl6TaX8gFRj8dnT2nYvj
aGDzPd/5xrw75tvY08ZNJu1kODCTZNH/o6gQHD08JKDTuf3u4u/dT6LxYt/K
DmkYMejq5vt7b/1KkIPI4Q/jxT1AY2ciOiYTf/IIv3M2MkwY8YL3QPSgoz6j
+wfuCGVlDslFcSJQRICtWfumRkSOwj9WOveI/V5dYLogKpSfv9X8/B9FBVQ/
+OXUfDVPFqGDm7DIMOlS//v2Sa9Ao3jKj52xcUnKPDv4ld2KbFpdJiRTc6Zm
9qpRfgmC802hyNw5Bh+QMeRneMfOQWBu6qsEbNZcVq1sJLTEqDcrRvGTHI/L
RyAK8sBH0kVC+pWtIvbW13aRM7oGnvc4vgSKl9u2RoEUPzah7826knw7ENOw
2/PZ3jrBQ1zURWO+ZR7TEK33jvGeYifCYgKg3mD/+ZHWoyc9BX1VTsMouu1x
P4A5+njEJHB2aOSzQzpte6DnnAxBeBTRRlFckpvnJ+E04fJDWY9IxNHG7skw
PVnIi67Ejj7mauPeIdwuGBeOEA/VePZuQ8Xni31Ytb2FnIZpZO6irBkUkaf9
rxLcoRzIPE0Wy8q4YJtzcVHCqRiglAcAsGib5hECcwRFsyVRfT66H5Ec7oeZ
QNOM2ZTvmnpDhJomsbYUAPw5jIFIAbgmZy+t2aTb0f27H+/Gk9uba2kBaWL6
PqvTWQvzewE6JfWDJ613wSXIrsDzMghe21mEONUn7QlyAMfMLD3LQVBBKiM5
iqJd8dDVuWIUt/dg60S7PGyBLvSa1RyucDlTqdVXqq01MzecC1iL7AuOWeZr
xGQhfjhGUZtNTPgTCu5S5EHiNYe3b2qVVRLp0EBSrQVntbIo9EztnBLIpM8B
go01ddQwEGqU0ZtVubxwGTWtNXK+n7nHMb1y3Sk0Mdt0tDVEtZXuIeZ1j1AS
I3lIYpZ9FhSNyzjTyVSXXELGAyzhLjjVBDcUL0JwoINTlBWYZnDK6f6GCaRO
JtJGjtm5TNvInpdlhD2nWBcY3AwHPTMciiYPjznRyLVshbs9IUuxuv6FeNsV
gZ/bClrCxUXINCyT1sJ3yrW8UQhq3Lp5yXjd5zQhEps1ZRoLmOoI+38GUd6s
K8ccCpNisTHExPo1slZEGkfX87nlAqksHFyHT6KCYczh3Of65eoktmzlvqhV
NhRzAbjMxOpXeQVcoN7JJaJK8OBDRhmsiKIejvtpDpi8VHKVPtIUF2Y2nEgF
v36HgzDHtG176Os+8W2wqKJcdbTsQl7a+8w+GkV3ILHWfYl+ewbWnkKGjQs1
VAJdjO+yJfSnFecKaNOpjPwgMYiUFB9bgTbGEIPT4/DeZUzq97W1IoFZWJMY
VJwoFdHz9VUQtGuJVQR2LbNL2nJMRXaLqi1k/JyElE4uKUOPQbR6sqA6csVk
CG1TUA0pVzuCwHM7JdjDpZ5aEjkBFVI+rLZLwk4O/CATKis8Ncfq+2SQRhUQ
MvGZehIfTcSRP5CCxDnhkyuObLVdlCumWEpiKaOxmYIYLonU2+u6ST5ThdPi
bMDc8pXKKM7XzlJrWYUj4laV5AuFaTaaXHg5rRES5XaoDYn6I0gE+e/mmvZt
jcDedLhy37bS4PCpa1+RDMkpZefNurSbOA81zSCpy3o807H9Rb9nyP6SyQKS
4dYRTiJTQTbaxEnuPE+PzD8cQYS4X6quktt8K+2qI1PZFdXffHMBZwDSVPUU
K8k1wQMrXEgas5JiT6tmuoVEFXmmcNZIM5PHHBElSO5I+lmUu2TlJO9ENdpU
kmOSzxArss9mifCqyrYSWrQOyvnaqkmwS9zJWjk3JeksWIJVnnE2upWd8ikp
8C7J4LNbhS7npKkjyOFS+zHiJeSZ/UIqrW8u5i6nlJKc5rPZpqCGE84qppx1
9LTYbEnQkMMFqdb7sh733TSfpSopjdB6jKxNPrPKUUrm7+1HYQ5K9m4nN6ug
j/PzAp44W6ty57sAuDphCa6yKGqaEuJ2mT+aG9gM9hhngkgphLi8Oes6QNoV
KPhuOy2S3yrxcbM1PGZZhXK7tiQwEUUUJ8rz3WaMkruH4DL4B0Hw5iicGg9K
q7LeM4+wA3D+0cdkxR5MwGFMmcySuQ1WQlRz6mdzVjOIleKyL2WyoiQv7uaU
zCkFegItODiMuPAjo5NWPSg2ZpGpQ8BWNcUXDp42QLJg+ochUjEC/PBnkknt
2jPatae1UgZRrBvi1jT2a4c+gYQ+TR9MHROVIhLOfXk55AI7W3btjRi8dAHo
eGWLBWvVrXv6f4g02lq+Aq6kYoS6lsdlXtY+SUI3FYk5xLOh1XAFc8oksphW
S2zKMk9jJ6V/MYNnR2ZVdnuuq0DbWhkGlh7i1UpD/piVGaN/Rh45DmSRRPxG
bTQEUjidDxWGXFHfBGUz8g829m5x6ILwd9g7WDhZfUsSn7JhvikYpQvqkoCO
Jtrb/sCwiFbHciWNY7S2KRTnMYkxJ9yOrtwNVPD8bjq4Ctj+Gbl6ajYY/W2s
mANbnpWS0yjy6cZrDYWGD1GSuvT2E2ji07xDMqyJC41+h2iSthPGl+grEKvS
anLVwtCTNO+nv+xmg/bxS/Kkkn3befy/9yegfl/mqc5AfTINqZft9uLYzIo9
FYs6HYcnJo4lFBirbHLisjVG/VBLpHSMe+1Dv6wFVIKr5hjuId731+DuuTN5
fww/vpgL3Pvvk3/n4Xe/8/D/T/Pz3kmatl0qM52jjydHUNF/cipZvOa/zDfm
n/R0jdz/pXxvpHpdg6rhMQY0Br9DzKbHMcYu/v/XZxKh/9e1NDOhXr/CdbK2
bNI0Gypnr0gvWQR3G7gmLcVUdtzqGJwfNeOPa5eB23fAizOb7OzFh+kYHuT7
HsxmGc4XIflkFmU9fdlMOngfuWM40Y5nGogNT+h6FtwIdOaK8hyf3Lz3uEGJ
K3+DQfUnCL0Hb2TRPpnbTbEmZ+SDlUbGmDb5FEw2+3/gr0cfj47wu9t+nesT
IdsmTOyso6SgGsUZpQooGBzf319cv530zNub0Q+jf/TM1ejvP96+n7z78eJc
m8mfpIT7bsoB043Q83PzYdVcS6SDLNIYpKlF8lj0ItgM+AT3aOMadLT6EPxk
Q1/gGTMULPZNdy5Fai2amordNQJSaqiiIuLadQ3QwSmK83XwYz/4uf3s4O+a
gwIvZPljauMF4SDJAnoxgnNLtTb8uSlPjtpFGm8D9kzsdsuD4d10o3+57hGk
AFzjmTq0B6/zuadgYPbajk+wyu35x5obK9lo9wx1WI0n9z1zNro+G1/i57ub
73D//bVesPLuz/jS7A315OKduYy2FDlw/51rZiuDYJSm7jlNSkgz0RfbmLSO
TmEKjYng2rUovegPdvT6VPSzkwC4XcowfE2ECGW3EkCYTr+PIILS6bEEAIRy
OLndId3DO+/Go/Px3YR/H3Qdb1iX+N4x4lCnbnzjBA+xpt3e3VxdTMZ881nX
qSL/+kKJaWhlQPfjrk8wNA+V1L1WEhDyvgrr2CjJmnjN7he1R7e2WCUV6aWW
M0mZuFtNChG/xwSdDI6cSLHD+Zx4jRT/QTcA47TLIJ/XiZ+6YuJy7K3cnJ9t
6GarhWy/Th02ZnfK1Eq3wjypsmi6ijWlNW8zZewpOHYUPJH230+IzzG6JlBJ
PXCjkJI3b/dP+dDnCUdOHD234783/MHh/o3g/hSn3KaDd6iW8nACudTL5+7y
+64cdqCcji1SqtLUp5N2aHHq7Qzmm8SmsSxiX5v2jTQmtbtmg+AH/NZqz/NN
JDlFVuU6l9iwPi5y0mvEs7N8BfnRg8mEx5mipDVz3amt2S/JCjV0Z6WlTIku
71quCT6cjuoB4eN2qL9wsVbPSMit7k4VjsBmXYij47cU60obXqNjD8uj+ErC
bYjqJqZWp8ZUWnWLm52bXE/V6oeXnx5PvlpHmU8c8jaEd5KHxkaKqS+o6w5b
1W451tpMo7VPwkzdtispiVCrhTt91/HX4UW2Vrvu74EfWlqjuZ8seBVtKe9F
ZabVNHV1Z98WVBfTOOL18bZ2t7nWJZch9wP7nTSdvxKvN1yLlX0i0MZ1W4Ie
Yczc7Wlk+NNMjrqESdzVDLvs2wkdyKDK61brJZkjxQGmzBXCBGKKbuuOcVqs
p22iWy0rcrqGW7D40AQG+Mxxla30v3H9wC1LGMDIyiUKOG7WjK8cU/SmRhr/
Rykdr5c/EVBLZtJtcO40+1T64MThaTFTmjv0lJvR4jEdX6fqZGHOryfccKpH
/yjCn/zt7PUhvUB/mXHjtvLwuRxuawiCnMGhUpAILZMrUhs/EIrjLThYnhyY
0eXtda3w0o/PSn7uzs6INkbrckOdH5qmOzXvU5ixsHk+tD54Q6Roy6Emdq/g
iqd66k5dJC2Ky88EAN7eja7qrnl/VoeZX5b5TNCupJsbLbliysSec9ochDCl
kZtBd9DP4RYigKOJK1+90H5xo/35LjiSQxLUd01LIm/DlZN2LY+9wG+dWZDS
SbubR4qtdHphIsLNI0mRotoGjJb210iM1kikjgT9U+lOqewQ55RS4sPepZyJ
poQRzP6UUrvtwxEsk5Rht8WM0p7U/mTOGgd2R/WB3aBzNiq7fco+F1yM0hqi
Howr3bngnSPBzUMUrVK8WIPGqQx6qD5r6Xswd05lcEHnNbWSx4lkMeW0Goxa
5pFb7cfYAajb8QFA8BunRky88YVEt1s1ZR2uOJRcDKAmazmNR+F4cwieWFog
Gg1GJEtkZnAtpR3K5T95zTmsvUdWaohPZZ1WSUtPELU6gS7Ou0R//3l/0D/B
f8+On72inwM/vfXnX7QhhUtAo8l1fxBq2cCIhNLs/jgoHdjWBmGX0/yv0rWg
L3NoJ/Wha4Z3HA+fPRu80s7+nXPupoEk/FdmqLOVzIs/g0U3R5OziwtO/vK8
+m2IsErL0O/P6YGvySOgqFewYeYIH7GQi2yeS4s0PWnXSwslgPg2NwMLYC5R
rnda5I9wj3rWzZ1k9HImZ8I9oPrBTn0LNNUqoDI6k46DV6FDBAnORma2tNRn
QBnlxuzrJMu4VN+Q5hHXmxud5WoDsPnw9zb2MKY5EJe3O3RHCuXe18oRfnUM
WpCQrmg6uKKnIPh8X7bzbQJ3GhyD1IqRS41Cmp20msaG71p8JKvmjlm8z7E8
ObK55/xTjdentnq0sNDLfCVOdpVPKaeUcbfR1C4TMbmlr6NRSYf3I2MJLygW
vzgbH07u318f3r+/uzbcZ1hqN1/iDzdqMKiOnR0VEe3PbtUKE/z2MS85iGPT
NFQrYPVIK3cXWgfEjHxTxfw7l2qA3BSpTwouXuoS+GMSOZcnXb9XbUlvXk/G
d39DIDU6P0f8MRHHyjIsmWS/2YSP4oRPYeswVjOA9iO3iS8cEKt7yEGGTIXR
/Qxwp8fxC/vqqN/Xq4EWAcdXN38bP3nupEudO1qvYLnKczo+SJQ0Dxc9/SYE
H+E2iPmvz979eDX+8frmBz/q0M9+TPUeAzEFMhVdlRc06eJay4wG+2I4fZTD
DXFndNhtfP12LKcRmj1yjd66wOyc1vqK7MQKWzTZwox+NJ3R6+s33d1TXKMN
Z7ww72tI36YMr6NNwW/qC0T7ahUpOqHPHQENNbMUpQyvJpGEN5SAhE0aQziF
yRKOOGu4PAn2IdY6Dq3yDzZzhZppNg92x/7WHDg0/+0BN/GF/rTJwZ8Pgt0s
Pyw0tWjg2Q6uOEEQPgwPEE8f6LHpkMLyA9Pd8+o/MaTUm/D+4Ovzi7cX9+Zf
n3mQS2MhSbJMBvN0LBPh6jnQbhevBm2KDa0H3uLrjnk9moyfn2Df7/Ag7gWN
G/zvW4LL70YYUOjAwN/w8If8/28PgmB5EkbpOgNv3Ct/+vj8Zf/4xPxZADcF
6eS/Ag6LGs/Sky9e9J+/6r8Y9J8f0/P0SOMNLQ5EBZ/fCwnbfXsgw2CfQpEI
ye9P9OMlFEZTJlOOi5d6nLFUHBLBlGx/VoGieiziIX/m+EkCvXVkK6ijb/rs
k4j+V77YAEGX0GVUsXmll9uAmQWqZHzbMvbtDA31LkCZkllCxkCbCTExdVWY
zZqyikFdM52xo2L0M5PmvboBqnOw9kRFTNRBl7ui6AsNsQ3qnqonLVsCcAF/
F+oWEnG17LtJmwX85sU2+MLZOO3dqk9KnxrLCtdsSKS6sWYxVnw8s2x0mGpX
WDM/0Tg6WKfW5GytDM7slK4ybMHeHp3PzRMFn0mqMZJopatkvJAb8xgXE1c+
WLsuv8gRv3G5az2JCu65evYn04lK8CdKNxTKBfxhDDMYvuSc5tX5M7Zng6Oh
JDnvJiP40znwFan0OiLrXnEjltScGFwQUImtYG9ybvUB0Ea8Vh9xB3WZnmVS
yXEeua8H1+ap16PYtBvHVezrBmiWIf1kkLpYuDb6Coznu54vvbht+GKuZkVB
0ZirNU+RlB/6jVMBHDgoqGR4R1W9sP0OfQOn2j3TJglyfnu2zBtYPqBP/eWr
lFqsQEzmT1FcnHP07I8uDxuFAU32isgHPuonDu70uP9mi7vrFtY+9HwlhUvM
OKEKjVLjPu9IWmzuwJRSc58CVaQq1Sgg1RXC3m6YKD35Mk1QWk7cPNjdgJa9
ZNkoFYlNgarotzUo68Y5Jel+CfyxOj0CqhUwTp99rEzH8/Go/3ynwIIY8Y00
l6w44D6Sr30wMPPdMUw7N7ZP9Wg4f7Ehpl5B7l3X2ISqab7Jz5261kMWGrax
zZDPvbCJBCse9AMxYG8gK5UkyMXoevTEx2CfOK3kz+hAVO7sIuGDg/qdq+ah
er8GHo0bX+hhDQEboKnxvbxL6p8L/AyNQzIAUJi8S8c73XHGAwrfn7zt6Qv2
vN2gvTxQgoot4/g6B/bkjOPXPupWMZkozDg1R4AB+B+AQIdwQBfP3jmLRc18
DYa05riLHpt1h/rLH1+c68ULmvAVXQ3o6hizMpr44rx7aw6/b+uKxkOfA6UC
RFUXDr70IbMOUdHV+bm4pkRsD8jo+O+CkeFiPCDZaPoWLKypfHpLP7XGPWmQ
1JEvNXOIWwJJbbJsg3C5sPGvwb4vze18Baj+chV/PmG65UXSp2ElTdj6hGyv
/izZnvu733PpXN183903wOc+ddP6xE3XTRE03mx8rEaLD5LF1nirkVRqLZqO
6a6od3TbD/4X5ZcCGBdYAAA=

-->

</rfc>

