<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-zheng-quic-fec-extension-03" category="std" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="QUIC FEC">FEC Extension for QUIC</title>
    <seriesInfo name="Internet-Draft" value="draft-zheng-quic-fec-extension-03"/>
    <author initials="H." surname="Zheng" fullname="Zheng Huanhuan">
      <organization>Alibaba Inc.</organization>
      <address>
        <email>zhenghuanhuan.zhh@taobao.com</email>
      </address>
    </author>
    <author initials="Y." surname="Liu" fullname="Yanmei Liu">
      <organization>Alibaba Inc.</organization>
      <address>
        <email>miaoji.lym@alibaba-inc.com</email>
      </address>
    </author>
    <date/>
    <area>Transport</area>
    <workgroup>QUIC Working Group</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 44?>

<t>This document specifies a Forward Error Correction (FEC) extension
for the QUIC protocol, which provide protection against packet loss.</t>
    </abstract>
  </front>
  <middle>
    <?line 49?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>This document specifies an extension to QUIC version 1 <xref target="QUIC-TRANSPORT"/>
to supports Forward Error Correction (FEC).
FEC is a method of erasure control in data transmission by simultaneously
sending redundant data (see <xref target="RFC6363"/>). This redundancy allows the receiver
to detect and recover limited lost data without waiting for retransmission,
which can be beneficial in latency-sensitive scenarios.</t>
      <t>For instance, real-time communication frameworks like WebRTC, which is widely
applied in scenarios such as video conferenceing and voice call. FEC plays
an important role by recovering lost packets under unreliable network,
thereby optimizing user experience.</t>
      <t>QUIC-FEC might become a crucial foundation for MoQ (Media over QUIC),
which is primarily used for video stream transmission, which can migrate
the impact of packet loss on media transmission.</t>
      <t>This document defines how FEC framework take effects in QUIC transport process.
Since FEC extension introduce new QUIC frames and parameters, it requires
negotiation between two endpoints.</t>
      <t>This document does not define how the flows to be protected are determined,
nor does it defines how the redundant data are calculated via FEC schemes.</t>
      <t>This document also defines an optional Repair ACK frame (see <xref target="Repair-ACK-Frame"/>)
through which the receiver can notify the sender of source packets successfully recovered
via FEC decoding. This allows the sender to suppress unnecessary retransmissions,
thereby avoiding bandwidth waste, while ensuring that the notification does not
interfere with congestion control or RTT estimation.</t>
      <section anchor="definition">
        <name>Conventions and Definitions</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP 14
<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all
capitals, as shown here.</t>
        <t>We assume that the reader is familiar with the terminology used in
<xref target="QUIC-TRANSPORT"/>. In addition, we introduce the following FEC-related terms:</t>
        <ul spacing="normal">
          <li>
            <t>Source symbol: piece of information exchanged by two endpoints.
This document considers QUIC packets payloads as source symbols.</t>
          </li>
          <li>
            <t>Repair symbol: redundant information constructed from the combination
of several source symbols.</t>
          </li>
          <li>
            <t>Erasure: loss of one or more symbols</t>
          </li>
          <li>
            <t>Erasure correction code: algorithm generating repair symbols and reconstructing
missing source symbols from a set of source and repair symbols.</t>
          </li>
          <li>
            <t>Forward Erasure Correction: process of recovering erased symbols
before the detection of their erasure.</t>
          </li>
          <li>
            <t>FEC scheme: the conjunction of an erasure correction code and the specific protocol
elements required to use it with the design described in this document.</t>
          </li>
          <li>
            <t>Encoder: entity producing repair symbols using an erasure correction code.
The encoder can be a library used by the protocol implementation or a program
running in a separate process or machine.</t>
          </li>
          <li>
            <t>Decoder: entity reconstructing missing source symbols using an erasure correction code.
The decoder can be a library used by the protocol implementation or a program running
in a separate process or machine.</t>
          </li>
          <li>
            <t>Coding window: window of source symbols that are required to decode a repair symbol.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="architecture-overview">
      <name>Architecture Overview</name>
      <t>FEC Framework is designed as a module within QUIC-Transport layer.
The primary target of current draft is to establish
common mechanism for integrating FEC logic into the QUIC protocol,
thus ensuring interoperability across different QUIC instances.</t>
      <t>Endpoints use transport parameters in <xref target="QUIC-TRANSPORT"/> to negotiate
whether to enable the FEC mechanism. The FEC Framework specifies necessary
configuration information that needs to be exchanged between QUIC endpoints
using transport parameters during the QUIC handshake process.</t>
      <t>The FEC Framework operates within the QUIC-Transport layer. It facilitates
the transmission of FEC information and redundant data using QUIC frames.</t>
      <t>The FEC framework calls upon the FEC scheme to manage the detailed processes of FEC encoding and decoding.
The FEC scheme defines detailed algorithm process, and the procedures used to
identidy packet payload data in the context of FEC scheme. This draft will describe
the interface specification between FEC Framework and FEC scheme.</t>
      <t>FEC Framework MUST ensure compatibility with existing modules within the QUIC protocol.
Special attention is given to ensuring interoperability with the congestion control
and the ACK handling and retransmission decisions (see <xref target="QUIC-RECOVERY"/> and <xref target="RFC9265"/>).</t>
      <figure anchor="fig-fec-framework">
        <name>FEC Framework</name>
        <artwork><![CDATA[
        +------------------------------------------------------------+
        |                   Application layer                        |
        +------^-------------------------------^---------------------+
               |                               |
   Source data |                               | Recovered source data
               |                               |
 +-------------v-------------------------------|---------------------------+
 |                                             |                           |
 |          QUIC-Transport layer               |                           |
 |                                             |                           |
 |   +-------------------------------------v-------+                       |
 |   |              FEC Framework                  |                       |
 |   |                                             |       +-----------+   |
 |   |  +-----------+ +----------+ +-----------+   |<----->| FEC Scheme|   |
 |   |  | Handshake | |   SID    | |  Repair   |   |       |           |   |
 |   |  | Negotiate | |  Frame   | |  Packet   |   |       | - Encoder |   |
 |   |  |   (TP)    | | Handling | | Handling  |   |       | - Decoder |   |
 |   |  +-----------+ +----------+ +-----------+   |       +-----------+   |
 |   +---^-------------------------------^----------+                      |
 |       |                               |                                 |
 |   +---v-------------------------------v----------+                      |
 |   |   Congestion Control / ACK & Retransmission  |                      |
 |   +----------------------------------------------+                      |
 |                                                                         |
 +-------------^-------------------------------^---------------------------+
               |                               |
   Source pkts |                               | Repair packets
   (with SID)  |                               |
        +------v-------------------------------v---------------------+
        |                      UDP layer                             |
        +------------------------------------------------------------+
]]></artwork>
      </figure>
    </section>
    <section anchor="handshake-negotiation-and-transport-parameter">
      <name>Handshake Negotiation and Transport Parameter</name>
      <section anchor="transport-params">
        <name>Transport Parameter</name>
        <t>This extension defines several new transport parameters used to negotiate
the use of the FEC extension and specific FEC schemes during the connection handshake (see <xref target="QUIC-TRANSPORT"/>).
The new transport parameters are defined as follows:</t>
        <ul spacing="normal">
          <li>
            <t>fec_encode_schemes (current version uses 0xfece01): A list of variable-length integers
specifying the FEC schemes supported by endpoints for encoding. The presence of this transport parameter
indicates whether FEC functionality is enabled for encoding.</t>
          </li>
          <li>
            <t>fec_decode_schemes (current version uses 0xfecd02): A list of variable-length integers
defining the FEC schemes supported by endpoints for decoding. The content of this transport parameter
determines which FEC scheme is used for decoding.</t>
          </li>
        </ul>
        <t><xref target="fig-transport-param"/> introduce the transport parameter format of fec_encode_schemes and fec_decode_schemes:</t>
        <figure anchor="fig-transport-param">
          <name>Transport Parameter for FEC</name>
          <artwork><![CDATA[
FEC_ENCODER_SCHEMES TRANSPORT_PARAM{
  0xfece01 (i),
  Transport Parameter Length (i),
  Transport Parameter Value {
    FEC Encoder Schemes Length (i),
    FEC Scheme1 ID(i),
    FEC Scheme2 ID(i),
    ...
  }
}

FEC_DECODER_SCHEMES TRANSPORT_PARAM{
  0xfecd01 (i),
  Transport Parameter Length (i),
  Transport Parameter Value {
    FEC Encoder Schemes Length (i),
    FEC Scheme1 ID(i),
    FEC Scheme2 ID(i),
    ...
  }
}
]]></artwork>
        </figure>
        <ul spacing="normal">
          <li>
            <t>fec_max_symbol_num (current version uses 0xfecb02): A variable-length integer indicating
the block size (i.e., the number of symbols in each encoding group) used in block encoding.
This is an optional transport parameter and SHOULD be sent only when an endpoint uses block code schemes
for encoding. For coding methods such as convolutional codes that do not require a fixed block size,
this parameter SHOULD NOT be included.</t>
          </li>
        </ul>
        <t>For a single endpoint, FEC encoding and decoding are independent processes. By negotiating these separately,
the framework can support distinct FEC schemes for encoding and decoding, or enable unidirectional
encoding/decoding only. This flexibility allows FEC operations to adapt to diverse requirements
and configurations.</t>
        <t>To ensure interoperability of FEC negotiation across QUIC protocol stacks, FEC schemes MUST
use standardized identifiers registered with IANA (Internet Assigned Numbers Authority).
This standardization guarantees seamless communication and compatibility between implementations.</t>
        <t>During negotiation, if a receiver's encoder scheme matches any of the sender's encoder schemes,
the negotiation for that direction is considered successful.</t>
      </section>
      <section anchor="handshake-nego">
        <name>Handshake Negotiation</name>
        <t>Endpoints negotiate the transport parameters for FEC during the connection handshake,
as outlined in Section 3.1.</t>
        <t><xref target="fig-fec-handshake"/> illustrates an example of the negotiation process:</t>
        <figure anchor="fig-fec-handshake">
          <name>Handshake negotiation for FEC</name>
          <artwork><![CDATA[
Client                                       Server
        ------------------------------------>

        fec_encode_schemes={REED_SOLOMON,XOR}

        fec_decode_schemes={XOR}

        fec_max_symbol_num=10

        <------------------------------------

                     fec_encode_schemes={XOR}

            fec_decode_schemes={REED_SOLOMON}

                         fec_max_symbol_num=5
]]></artwork>
        </figure>
        <t>Please note that in the actual process, the Client first declare the list of encoder/decoder algorithms
it can handle. When the server receive the fec_encode_schemes and fec_decode_schemes,
it chooses one proper scheme for each direction, and set fec_decode_schemes and fec_encode_schemes params
as corresponding scheme for decoding and encoding.</t>
        <t>Note that if the client wants to specify the FEC algorithm, it can provide only one FEC algorithm
for fec negotiation process, the server could choose to support or not; otherwise, the algorithm selection
SHOULD be based on the server's priority.</t>
        <t>For example, if the client's FEC schemes parameter is set as follows:</t>
        <ul spacing="normal">
          <li>
            <t>fec_encode_schemes {Algorithm1, Algorithm2, Algorithm3, ...}</t>
          </li>
          <li>
            <t>fec_decode_schemes {Algorithm1, Algorithm2, Algorithm3, ...}</t>
          </li>
        </ul>
        <t>The encoder/decoder algorithm used in practice is chosen and returned by the Server:</t>
        <ul spacing="normal">
          <li>
            <t>supported_fec_encode_schemes {Algorithm1}</t>
          </li>
          <li>
            <t>supported_fec_decode_schemes {Algorithm3}</t>
          </li>
        </ul>
        <t>Note that the encoding/decoding option and the selected algorithm may differ after
negotiation.</t>
      </section>
    </section>
    <section anchor="transport-mechanism">
      <name>Transport mechanism</name>
      <t>The FEC module directly participates in and influences the sending and receiving stages
of packet transmission:</t>
      <t>As the sender, the FEC Framework takes the original data frame as source symbols and provides
the required source symbols to the FEC scheme module. The FEC scheme can encode the data grouped
by streams, or mixed data from different streams.</t>
      <t>FEC Framework retrieves the following information from the FEC scheme:</t>
      <ol spacing="normal" type="1"><li>
          <t>Source Symbol ID (SID) frame: SID frame is viewed as an unique identification for source symbol,
which is composed of block ID and symbol index typically.</t>
        </li>
        <li>
          <t>Repair packets: When the incoming source symbols meets the encoding conditions, the FEC scheme
could generate original source symbol with repair packets. Repair packet contains FEC Payload ID,
repair symbol, and optional repair key.</t>
        </li>
      </ol>
      <t>At the sender, FEC Framework is required to acquire and insert the SID frame into the packet
that includes the source symbols. Subsequently, FEC Framework SHOULD generate and transmit repair packets
to the receiver after processing a sufficient number of source symbols. Generally, the repair packets
SHOULD be sent immediately following the source packets from the same block.</t>
      <t>As the receiver, the source packets can be normally parsed by ignoring SID frame, but it might be
necessary to store source symbols and identifications to perform FEC decoding after receiving
repair packets from the same block.</t>
      <figure anchor="fig-fec-work-flow">
        <name>Work Flow for FEC</name>
        <artwork><![CDATA[
+-------------------------------------------------------------------------------+
|                               Application                                     |
+-------------------------------------------------------------------------------+
            |                                                      ^
            | Application data                Received & recovered |
            |                                     application data |
            |                                                      |
      +-----v-----+                                          +-----|-----+
|-----| Send API  |------------------------------------------| Recv API  |------|
|     +-----|-----+                                          +-----^-----+      |
|           |                                                      |            |
|           |                                       Source packets |            |
|           | Source packet                     & recovered source |            |
|           |                                              packets |            |
|    +------v------+                QUIC                    +------|------+     |
|    | FEC Encoder |                                        | FEC Decoder |     |
|    +------|------+                                        +------^------+     |
|           |                                                      |            |
|           | Source packets                        Source packets |            |
|           | with SID frame                        with SID frame |            |
|           | & Repair packets                    & Repair packets |            |
|           |                                                      |            |
|   +-------v-------+                                      +-------|-------+    |
----| Packet Sender |--------------------------------------|Packet Receiver|-----
    +---------------+                                      +-------^-------+
            |                                                      |
            | QUIC packets                            QUIC packets |
            v                                                      |
+-------------------------------------------------------------------------------+
|                                 Network                                       |
+-------------------------------------------------------------------------------+
]]></artwork>
      </figure>
      <section anchor="sender-operation">
        <name>Sender Operation</name>
        <t>### Define FEC-protected QUIC payload</t>
        <t>Endpoints can decide which types of data require FEC protection.
As applying equal protection to all data types may result in inefficient bandwidth utilization,
it is RECOMMENDED that protocol implementations selectively prioritize protection for critical data,
such as restricting FEC to stream frames and datagram frames.
For retransmitted frames or non-time-sensitive data, FEC SHOULD NOT be applied.</t>
        <section anchor="identify-source-symbols-using-sid-frame">
          <name>Identify source symbols using SID frame</name>
          <t>In the context of packets that require protection through FEC (Forward Error Correction),
it is necessary to define a SID (Source Identifier) frame that conveys the identity information
of the data. This is intended to help the receiver clarify the following information
during the decoding process:</t>
          <ul spacing="normal">
            <li>
              <t>Which part of data insides the packet will be taken part in the FEC decode process.</t>
            </li>
            <li>
              <t>Which block and the index inside the block the source symbol belongs to.</t>
            </li>
          </ul>
          <t>Therefore, it's recommended to append the SID frame after the fec-protected QUIC packet data
to indicate that the data preceding this frame is identified by the current SID frame and
is involved in the decoding process at the receiver.</t>
          <t>Based on the above reason, generating and inserting the SID frame SHOULD occur
before the encryption process of packets.</t>
          <t>As the FEC module requires an additional data frame to be appended after the protected packet,
developers MUST consider reserving space for the FEC data frames within the packet.
This ensures that the length of the packet does not exceed the MTU (Maximum Transmission Unit) limit.
Additionally, the SID MUST include Explicit Source Payload ID information to facilitate
the resolution of the current data's identity, as shown in Figure 6.</t>
        </section>
        <section anchor="generate-and-send-repair-symbols">
          <name>Generate and send repair symbols</name>
          <t>The encoding content of the Repair package originates from the original data identified by the SID frame.
It requires encoding the identity information of the FEC for the receiver to recognize the protection
object of the current Repair package, as shown in Figure 6.</t>
          <t>The specific encoding process is carried out by the FEC scheme module, which typically requires
the sender to pre-set the following parameters:</t>
          <ul spacing="normal">
            <li>
              <t>Block size: How many original packets are involved in the calculation for a computing unit,
which directly affects the frequency of Repair symbol generation.</t>
            </li>
            <li>
              <t>Redundancy level of FEC: How many redundant packets can be generated from the block.</t>
            </li>
            <li>
              <t>Repair key (optional): The encoding key required by the FEC scheme module, which usually
needs to be included in the Repair package for the receiver to use for decoding.</t>
            </li>
          </ul>
        </section>
      </section>
      <section anchor="receiver-operation">
        <name>Receiver Operation</name>
        <section anchor="process-recovered-symbols">
          <name>Process recovered symbols</name>
          <t>In the FEC module, the block triggering the decoding module generally needs to satisfy the following conditions:</t>
          <ol spacing="normal" type="1"><li>
              <t>The block receives a sufficient number of source symbols;</t>
            </li>
            <li>
              <t>The block receive at least one repair symbol.</t>
            </li>
          </ol>
          <t>However, the specific required amounts of source symbols and repair symbols SHOULD be
determined by the FEC schemes module.</t>
        </section>
      </section>
    </section>
    <section anchor="fec-frame-types">
      <name>FEC Frame Types</name>
      <t>FEC will introduce three new frames into QUIC protocol: the Source Symbol ID (SID) frame,
which SHOULD be attached to the original packet; the Repair Symbol frame,
which contains repair data and SHOULD be encapsulated and transmitted independently;
and the optional Repair ACK frame, which allows the receiver to notify the sender
of source packets that have been successfully recovered via FEC decoding.</t>
      <section anchor="SID-Frame">
        <name>Source Symbol ID Frame</name>
        <t>FEC SID FRAME contains the identification of the current source packet,
which declares the encoding flow and the block current symbol is involved.</t>
        <t>SID Frame SHOULD be inserted after the fec-protected QUIC frame to indicate
the range of FEC protected data.
Since the maximum length of the repair symbol is equal to that of the source symbol,
it is necessary to restrict the content length of the source packet to prevent
the content length of the repair packet from exceeding the MTU limit.</t>
        <t>SRC_SYMBOL_ID Frame Structure:</t>
        <figure anchor="fig-src-symbol-id-frame">
          <name>SRC_SYMBOL_ID Frame</name>
          <artwork><![CDATA[
SRC_SYMBOL_ID Frame {
  Type (i) = 0xfec5,
  Flow ID (i),
  Explicit Source Payload ID(i),
}
]]></artwork>
        </figure>
        <ul spacing="normal">
          <li>
            <t>Flow ID (i): A variable-length integer that identifies which data stream the symbol belongs to.</t>
          </li>
          <li>
            <t>Explicit Source Payload ID (SID): A variable-length integer that serves as a unique identifier
for the source symbol. It MUST includes the block id and the symbol index of current source symbol.
This can be formatted as follows.</t>
          </li>
        </ul>
        <figure anchor="fig-explicit-source-payload-id">
          <name>Explicit Source Payload ID</name>
          <artwork><![CDATA[
       3 bytes            1 byte
+---------------------+------------+
|      block id       | symbol idx |
+---------------------+------------+
]]></artwork>
        </figure>
      </section>
      <section anchor="Repair-Symbol-Frame">
        <name>Repair Symbol Frame</name>
        <t>In contrast to the SID Frame mentioned above, the Repair Frame SHOULD include not only the identification
but also the encoded content of the source symbols.</t>
        <t>Repair symbol frame SHOULD incorporate the following informations:</t>
        <figure anchor="fig-repair-symbol-frame">
          <name>REPAIR_SYMBOL Frame</name>
          <artwork><![CDATA[
REPAIR_SYMBOL Frame {
  Type (i) = 0xfec6,
  Repair ID {
    Flow ID(i),
    Expilicit Repair payload id (4 bytes),
  }
  Repair Key (4 bytes),
  Repair Symbol Payload (E),
}
]]></artwork>
        </figure>
        <ul spacing="normal">
          <li>
            <t>Repair ID(i):
      - Flow ID(i): A variable-length integer that identifies which data stream the symbol belongs to;
      - Explicit Repair Payload ID (4 bytes): A variable-length integer that serves as a unique identifier
   for the repair symbol. It MUST includes the block id and the symbol index of current repair symbol.</t>
          </li>
          <li>
            <t>Repair Key (4 bytes): An optional key generated by fec scheme, and is used for FEC decoding.</t>
          </li>
          <li>
            <t>Repair Symbol Payload: The content of repair symbol, whose length is typically aligns with the
block's longest symbol. This can be formatted as Figure above.</t>
          </li>
        </ul>
      </section>
      <section anchor="Repair-ACK-Frame">
        <name>Repair ACK Frame</name>
        <t>The Repair ACK frame is an OPTIONAL mechanism that allows the receiver to notify the sender
which QUIC packets have been successfully received through FEC recovery.
Its semantics mirror those of the standard QUIC ACK frame (see <xref target="QUIC-TRANSPORT"/> Section 19.3):
the receiver acknowledges packet numbers using the same packet number space,
but the acknowledgment is triggered by FEC decoding rather than direct network reception.</t>
        <t>When the sender receives a Repair ACK, it can determine that the data carried in those packets
has been successfully delivered to the remote endpoint via FEC recovery, and therefore
SHOULD suppress any pending retransmissions for those packets, avoiding bandwidth waste.</t>
        <t>Support for sending and processing Repair ACK frames is OPTIONAL. An endpoint that does not
implement Repair ACK MUST silently ignore received Repair ACK frames.</t>
        <section anchor="distinction-from-standard-ack">
          <name>Distinction from Standard ACK</name>
          <t>Although the Repair ACK frame conveys the same packet number information as a standard
ACK frame, it MUST be treated differently by the sender:</t>
          <ul spacing="normal">
            <li>
              <t>An endpoint MUST NOT use a Repair ACK frame to update RTT estimates or to trigger
loss detection. RTT estimation and loss recovery MUST rely solely on standard QUIC
ACK frames as specified in <xref target="QUIC-RECOVERY"/>.</t>
            </li>
            <li>
              <t>An endpoint MUST NOT update its congestion window or pacing rate upon receiving a
Repair ACK frame. A recovered packet was never successfully received by the network
in the normal sense, so its timing carries no meaningful congestion signal.</t>
            </li>
            <li>
              <t>The sender MUST NOT remove packets from its loss detection state solely based on a
Repair ACK. Instead, it SHOULD only cancel scheduled retransmissions for those packets.</t>
            </li>
          </ul>
          <t>The separate frame type (0xfec7) ensures that existing QUIC implementations and
congestion control modules can unambiguously distinguish Repair ACK from standard ACK.</t>
        </section>
        <section anchor="repair-ack-frame-structure">
          <name>Repair ACK Frame Structure</name>
          <t>The Repair ACK frame follows the same range-encoding structure as the standard QUIC ACK
frame, but omits the ACK Delay field (which is used for RTT calculation and is not
applicable here) and the ECN Counts field.</t>
          <figure anchor="fig-repair-ack-frame">
            <name>REPAIR_ACK Frame</name>
            <artwork><![CDATA[
REPAIR_ACK Frame {
  Type (i) = 0xfec7,
  Largest Acknowledged (i),
  ACK Range Count (i),
  First ACK Range (i),
  ACK Range (..) ...,
}

ACK Range {
  Gap (i),
  ACK Range Length (i),
}
]]></artwork>
          </figure>
          <ul spacing="normal">
            <li>
              <t>Largest Acknowledged (i): A variable-length integer representing the largest packet
number among the packets recovered via FEC and being acknowledged in this frame.
The semantics are identical to the Largest Acknowledged field in a standard ACK frame.</t>
            </li>
            <li>
              <t>ACK Range Count (i): A variable-length integer specifying the number of ACK Range
fields that follow.</t>
            </li>
            <li>
              <t>First ACK Range (i): A variable-length integer indicating the number of contiguous
packets recovered, counting down from Largest Acknowledged (inclusive).
A value of zero means only the packet with number Largest Acknowledged was recovered.</t>
            </li>
            <li>
              <t>ACK Range: Each entry describes a contiguous range of recovered packet numbers
preceded by a gap of unacknowledged packet numbers:  </t>
              <ul spacing="normal">
                <li>
                  <t>Gap (i): The number of unacknowledged packets between the end of the previous
acknowledged range and the start of this one, minus one.</t>
                </li>
                <li>
                  <t>ACK Range Length (i): The number of contiguous packets recovered in this range,
minus one.</t>
                </li>
              </ul>
            </li>
          </ul>
        </section>
        <section anchor="sender-behavior-upon-receiving-repair-ack">
          <name>Sender Behavior upon Receiving Repair ACK</name>
          <t>Upon receiving a Repair ACK frame, the sender SHOULD:</t>
          <ol spacing="normal" type="1"><li>
              <t>Identify the QUIC packets whose packet numbers are covered by the acknowledged ranges.</t>
            </li>
            <li>
              <t>Cancel any pending retransmission scheduled for those packets.</t>
            </li>
            <li>
              <t>Not alter the congestion control state, RTT estimates, or loss detection timers as a
result of processing the Repair ACK.</t>
            </li>
          </ol>
          <t>If a packet number acknowledged by a Repair ACK has already been acknowledged by a
standard QUIC ACK frame, the Repair ACK SHOULD be silently ignored for that packet number.</t>
        </section>
      </section>
    </section>
    <section anchor="operation-management-consideration">
      <name>Operation &amp; Management Consideration</name>
      <t>The QUIC-FEC protocol are expected to be a universal solution against packet loss.</t>
      <t>When implemented, the QUIC packets will be finally divided into different FEC blocks according to the
stream size or fixed size. Since that, the FEC Framework only needs to focus on whether the symbols
within the block satisfy the encoding/decoding conditions, regardless of the upper layer protocols.</t>
      <t>It's important for FEC Framework to determine how to group QUIC packets into blocks, which needs to consider
the optimisation effects at the application layer and the FEC scheme support.</t>
      <t>For example, dividing data into fixed-size blocks is a more convenient approach and allows better control over
the packet repair rate.</t>
      <t>However, this may result in some repair packets arriving too late for the source packets to be protected,
just as for source packet 4 belows, repair packet of packet 4 will not be send until stream 2 finish the sending:</t>
      <figure anchor="fig-fix-block-implementation-steps">
        <name>FIXED BLOCK Implementation Steps</name>
        <artwork><![CDATA[
              +-------------------------------------------------+
              |                Application Data                 |
              +-------------------------------------------------+
                                   |
                                   |
                                   v
              +----------+ +----------+ +----------+ +----------+
   Stream 1   | Source   | | Source   | | Source   | | Source   |
              | packet 1 | | packet 2 | | packet 3 | | packet 4 |
              +----------+ +----------+ +----------+ +----------+

              +----------+ +----------+
   Stream 2   | Source   | | Source   |
              | packet 1 | | packet 2 |
              +----------+ +----------+
                                   |
                                   |
                             +-----v-----+        +-----------+
   block size = 3 ---------> | FEC       <--------> FEC       |
                             | Framework |        | Scheme    |
                             +-----|-----+        +-----------+
                                   |
                                   v
              +----------+ +----------+ +----------+    +----------+
   Block 1    | Source   | | Source   | | Source   |    | Repair   |
              | packet 1 | | packet 2 | | packet 3 |    | packet 1 |
              +----------+ +----------+ +----------+    +----------+

              +----------+ +----------+ +----------+    +----------+
   Block 2    | Source   | | Source   | | Source   |    | Repair   |
              | packet 4 | | packet 1 | | packet 2 |    | packet 2 |
              +----------+ +----------+ +----------+    +----------+
]]></artwork>
      </figure>
      <t>Dividing the block according to the QUIC Stream can avoid the problem of long time difference
between the generation of repair packets and the arrival of protected packets.</t>
      <t>But not all the fec schemes supports variable-length block codecs. It requires the fec scheme to carry
the block size information with the FEC frame. For instance, certain algorithms employ a repair key field
to specify the number of packets and their indices within a block, enabling the receiver to determine
when decoding is possible. Without this information, the receiver cannot support encoding schemes with
flexible block sizes.</t>
      <figure anchor="fig-flex-block-implementation-steps">
        <name>FLEXIBLE BLOCK Implementation Steps</name>
        <artwork><![CDATA[
              +------------------------------------------------+
              |               Application Data                 |
              +------------------------------------------------+
                                   |
                                   |
                                   v
              +----------+ +----------+ +----------+ +----------+
   Stream 1   | Source   | | Source   | | Source   | | Source   |
              | packet 1 | | packet 2 | | packet 3 | | packet 4 |
              +----------+ +----------+ +----------+ +----------+

              +----------+ +----------+
   Stream 2   | Source   | | Source   |
              | packet 1 | | packet 2 |
              +----------+ +----------+
                                   |
                                   |
                             +-----v-----+        +-----------+
   block size = 3 ---------> | FEC       <--------> FEC       |
                             | Framework |        | Scheme    |
                             +-----|-----+        +-----------+
                                   |
                                   v
              +----------+ +----------+ +----------+ +----------+    +----------+
   Block 1    | Source   | | Source   | | Source   | | Source   |    | Repair   |
              | packet 1 | | packet 2 | | packet 3 | | packet 4 |    | packet 1 |
              +----------+ +----------+ +----------+ +----------+    +----------+

              +----------+ +----------+    +----------+
   Block 2    | Source   | | Source   |    | Repair   |
              | packet 1 | | packet 2 |    | packet 2 |
              +----------+ +----------+    +----------+
]]></artwork>
      </figure>
      <t>In short, the FEC scheme determines which block partitioning method can be chosen,
and the application layer optimization effect determines which partitioning method should be chosen.
And the specific codec flow and repair key design should be decided by the fec scheme.</t>
      <t>The both steps can be applied to most application layer requests based on the QUIC protocol,
and it's been proven to work with the HTTP/3 and MoQ protocols as the above steps.</t>
      <t>However, FEC should not protect all application layer data without discrimination in the QUIC connection.
In order to reduce the bandwidth overhead, the FEC module should provide the upper layers with an interface
to switch off the FEC module at the Stream level.</t>
      <t>It did make differences on when and how to switch off FEC among different application layer.
We offers an abstract steps as an example here:</t>
      <figure anchor="fig-close-fec-implementation-steps">
        <name>CLOSE FEC Implementation Steps</name>
        <artwork><![CDATA[
      Client-APP                                      Server-APP
          |
          v
set_fec_close_API(stream_id)
          |
          v
stream_state.enable_fec = false
          |
          v
generate close_fec_frame to packet
          |
          v
            --------------------------------------------->
            QUIC_Packet {                                 |
              ...Frames,                                  |
              CLOSE_FEC_FRAME{stream_id}                  |
            }                                             |
                                            parse close_fec_frame from packet
                                                          |
                                                          v
                                            stream_state.enable_fec = false
]]></artwork>
      </figure>
    </section>
    <section anchor="security-consideration">
      <name>Security Consideration</name>
      <t>TBD</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document defines three new transport parameters for the negotiation of enable fec for QUIC, and three new frame types.</t>
      <section anchor="new-transport-parameters">
        <name>New transport parameters</name>
        <t>The following entry in <xref target="transport-parameters"/> should be added to the "QUIC Transport Parameters" registry under the "QUIC Protocol" heading.</t>
        <table anchor="transport-parameters">
          <name>Addition to QUIC Transport Parameters Entries</name>
          <thead>
            <tr>
              <th align="left">Parameter ID</th>
              <th align="left">Parameter name</th>
              <th align="left">Specification</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0xfece01</td>
              <td align="left">fec_encode_schemes</td>
              <td align="left">
                <xref target="transport-params"/></td>
            </tr>
            <tr>
              <td align="left">0xfecd02</td>
              <td align="left">fec_decode_schemes</td>
              <td align="left">
                <xref target="transport-params"/></td>
            </tr>
            <tr>
              <td align="left">0xfecb02</td>
              <td align="left">fec_max_symbol_num</td>
              <td align="left">
                <xref target="transport-params"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="new-frames">
        <name>New frames</name>
        <t>The following frame types defined in <xref target="frame-types"/> should be added to the "QUIC Frame Types" registry under the "QUIC Protocol" heading.</t>
        <table anchor="frame-types">
          <name>Addition to QUIC Frame Types Entries</name>
          <thead>
            <tr>
              <th align="left">Frame ID</th>
              <th align="left">Frame name</th>
              <th align="left">Specification</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0xfec5</td>
              <td align="left">SID Frame</td>
              <td align="left">
                <xref target="SID-Frame"/></td>
            </tr>
            <tr>
              <td align="left">0xfec6</td>
              <td align="left">Repair Frame</td>
              <td align="left">
                <xref target="Repair-Symbol-Frame"/></td>
            </tr>
            <tr>
              <td align="left">0xfec7</td>
              <td align="left">Repair ACK Frame</td>
              <td align="left">
                <xref target="Repair-ACK-Frame"/></td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The specification has been materially improved through technical discussions with Ian Swett.
Thanks to his recommendations with the draft and FEC mechanism.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="QUIC-TRANSPORT">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="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="RFC6363">
          <front>
            <title>Forward Error Correction (FEC) Framework</title>
            <author fullname="M. Watson" initials="M." surname="Watson"/>
            <author fullname="A. Begen" initials="A." surname="Begen"/>
            <author fullname="V. Roca" initials="V." surname="Roca"/>
            <date month="October" year="2011"/>
            <abstract>
              <t>This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) that is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined that are not specific to a particular FEC scheme, and FEC schemes can be defined that are not specific to a particular Content Delivery Protocol. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6363"/>
          <seriesInfo name="DOI" value="10.17487/RFC6363"/>
        </reference>
        <reference anchor="RFC2199">
          <front>
            <title>Request for Comments Summary RFC Numbers 2100-2199</title>
            <author fullname="A. Ramos" initials="A." surname="Ramos"/>
            <date month="January" year="1998"/>
          </front>
          <seriesInfo name="RFC" value="2199"/>
          <seriesInfo name="DOI" value="10.17487/RFC2199"/>
        </reference>
        <reference anchor="RFC9174">
          <front>
            <title>Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4</title>
            <author fullname="B. Sipos" initials="B." surname="Sipos"/>
            <author fullname="M. Demmer" initials="M." surname="Demmer"/>
            <author fullname="J. Ott" initials="J." surname="Ott"/>
            <author fullname="S. Perreault" initials="S." surname="Perreault"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document describes a TCP convergence layer (TCPCL) for Delay-Tolerant Networking (DTN). This version of the TCPCL protocol resolves implementation issues in the earlier TCPCL version 3 as defined in RFC 7242 and provides updates to the Bundle Protocol (BP) contents, encodings, and convergence-layer requirements in BP version 7 (BPv7). Specifically, TCPCLv4 uses BPv7 bundles encoded by the Concise Binary Object Representation (CBOR) as its service data unit being transported and provides a reliable transport of such bundles. This TCPCL version also includes security and extensibility mechanisms.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9174"/>
          <seriesInfo name="DOI" value="10.17487/RFC9174"/>
        </reference>
        <reference anchor="RFC5226">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <author fullname="H. Alvestrand" initials="H." surname="Alvestrand"/>
            <date month="May" year="2008"/>
            <abstract>
              <t>Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t>
              <t>In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t>
              <t>This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5226"/>
          <seriesInfo name="DOI" value="10.17487/RFC5226"/>
        </reference>
        <reference anchor="RFC9265">
          <front>
            <title>Forward Erasure Correction (FEC) Coding and Congestion Control in Transport</title>
            <author fullname="N. Kuhn" initials="N." surname="Kuhn"/>
            <author fullname="E. Lochin" initials="E." surname="Lochin"/>
            <author fullname="F. Michel" initials="F." surname="Michel"/>
            <author fullname="M. Welzl" initials="M." surname="Welzl"/>
            <date month="July" year="2022"/>
            <abstract>
              <t>Forward Erasure Correction (FEC) is a reliability mechanism that is distinct and separate from the retransmission logic in reliable transfer protocols such as TCP. FEC coding can help deal with losses at the end of transfers or with networks having non-congestion losses. However, FEC coding mechanisms should not hide congestion signals. This memo offers a discussion of how FEC coding and congestion control can coexist. Another objective is to encourage the research community to also consider congestion control aspects when proposing and comparing FEC coding solutions in communication systems.</t>
              <t>This document is the product of the Coding for Efficient Network Communications Research Group (NWCRG). The scope of the document is end-to-end communications; FEC coding for tunnels is out of the scope of the document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9265"/>
          <seriesInfo name="DOI" value="10.17487/RFC9265"/>
        </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>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC5510">
          <front>
            <title>Reed-Solomon Forward Error Correction (FEC) Schemes</title>
            <author fullname="J. Lacan" initials="J." surname="Lacan"/>
            <author fullname="V. Roca" initials="V." surname="Roca"/>
            <author fullname="J. Peltotalo" initials="J." surname="Peltotalo"/>
            <author fullname="S. Peltotalo" initials="S." surname="Peltotalo"/>
            <date month="April" year="2009"/>
            <abstract>
              <t>This document describes a Fully-Specified Forward Error Correction (FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), where m is in {2..16}, and its application to the reliable delivery of data objects on the packet erasure channel (i.e., a communication path where packets are either received without any corruption or discarded during transmission). This document also describes a Fully-Specified FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8) when there is no encoding symbol group. Finally, in the context of the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding ID 129), this document assigns an FEC Instance ID to the special case of Reed-Solomon codes over GF(2^^8).</t>
              <t>Reed-Solomon codes belong to the class of Maximum Distance Separable (MDS) codes, i.e., they enable a receiver to recover the k source symbols from any set of k received symbols. The schemes described here are compatible with the implementation from Luigi Rizzo. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5510"/>
          <seriesInfo name="DOI" value="10.17487/RFC5510"/>
        </reference>
        <reference anchor="RFC5052">
          <front>
            <title>Forward Error Correction (FEC) Building Block</title>
            <author fullname="M. Watson" initials="M." surname="Watson"/>
            <author fullname="M. Luby" initials="M." surname="Luby"/>
            <author fullname="L. Vicisano" initials="L." surname="Vicisano"/>
            <date month="August" year="2007"/>
            <abstract>
              <t>This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for bulk data transfer over IP multicast. This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered. The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined. The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5052"/>
          <seriesInfo name="DOI" value="10.17487/RFC5052"/>
        </reference>
        <reference anchor="QUIC-RECOVERY">
          <front>
            <title>QUIC Loss Detection and Congestion Control</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="I. Swett" initials="I." role="editor" surname="Swett"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document describes loss detection and congestion control mechanisms for QUIC.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9002"/>
          <seriesInfo name="DOI" value="10.17487/RFC9002"/>
        </reference>
      </references>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+09/VPcRpa/66/os6s2UJ6ZNTjJXshm6zDgDbW24YBcNnd1
S/VIPaBYI81KGjAB9m+/99VfkgYGx7mrq9qppMxopO7Xr997/b41Ho+TNm8L
s6PeHOypg4+tKZu8KtWsqtW//3C4l+jptDZXO/QF70myKi31HB7Iaj1rx79c
mvJi/Pdlno5nJh0bO8L45ask0y3cd7u/e3Zwn6Tw5aKqb3ZU02ZJki/qHdXW
y6bdfvnym5fbia6N3lFntS6bRVW3yXVVf7ioq+VC5v4RvuflhfozXks+mBu4
IdtRh2Vr6tK0430EJ0maVpfZuS6qEqa+MU2yyHfUf7VVOlINDFubWQN/3czx
j/9OEr1sL6t6JxknSuVls6O+n6j/xCXBd14mfVPfL3V5Cf/D5aq+2FG7RT7V
Uw3TpxO4ZuY6L3YUIeNSbp38cnn5b62uprqapNXcT/HTRL3Nl26Cn3Q5N7lc
emDwea6rn/NJcTP/N803jHO4AYdOkrKq57rNr8wOPID4Gp+d7L4/PT46OdtR
9Sz95uXLl+6Xt6f22hZcO3mz9/Wrr1/t8J/bW998I39+s/WHL+XPr7a3v7ZX
t7/+agf2r5yFU+I9X229tH++/GrbAXJysHf0HwcnP9k5twHc8Xis9LRpa53C
np1d5o0CulrOTdmqZmHSfJabRmn1pqqvdZ2pg7oGgtyr6tqkLdLnBpDipnLU
liC9tpeGSWVRV7DhVTFS15d5eonfr/LM0HV5Xl9o2ItWLXT6wbSqqJpmwmDN
8ywrDMD4HGmrrrIlPfEAlKWHQ7UVg3Blavq+pW5v4+24v0/gpma5QCpvHlnh
JEG2zBEVcwOUmqlqpkytm2VtVFohfAUQlQJO08BNwDvzvKGJpzeqyefLAtjB
VMumuEkaU2bIQLXJlmWmYQ301EZjDAApVHB/vzlRtFJ7W3qjdFFU1w3hF6Az
sOU1riEziE1Yf4aXK7iqinyetyZDfMrw1zmAvWzVtc5bnB03qjYhqKOEdykF
RE4N/FeaWZ7mmhZWgNQAEMYN4heJTTWpKXWdV7hfgDxkKVhjakYwrC7GbT5H
zMznyzIHkUOyrAY+Q3HSAHwfjPrRTE/O9ixxwFKvgTgAQXqxKHIAHqZ1k8BG
wT26UUhAFaJ8ZmqAyOBacOVXVZ7ChICiCYnQRaFvmgSWks9xgxHNsEcG90OQ
hE8Sfpj2GgVoBtQty9oUuZ7CvSDOENxRAhivDTxZLWBZ+S/45LKBe83HBYyD
YAASiLxw6nl+cdkC/mD1BggmrZeExVmF+9haqf6u+ne18c5kuVa0Zfj4pt0D
QMaizuew9OIGp8roEV47cKvR84jKLA5x62D2GjYLYca1A2MjrQb8pQCAOc0b
DjHpMlYGu18CW11W14RQt3uq1bB5ZgbHDCANNokYrbUHBnJ3apCNT0EsGnrW
82UurIzIveYnaeCGNnGh8W84SOBsyGHDDJxnNZwdJZxYbc64m8KmGAMcfl0p
4KRFBUM2fegrGLKs7DJoFYiRGXNQhRQuYgiQC2cecVE9h3uzEUpxHiGP8cCc
F7EtPgpUly6RQ4AMAa244ia9NLCqHly6aCo3JOwWUlRVAnWcmIXOa7W79xdG
iJMHdH0M18dv8DoIBthaOHsvLmXTQ3FAFADLzmc3dB1lDVwFAmiqZQ1Yt7QO
7ISbNFsWhWMIkyUW/AyuoJASGRQIHhlRRCdsDvJNaXAwXd90RErjWUcDg5LY
m8JGA6O3AL5uWkOkC7wG9LEklmwvdUsz0TKs7LD7CecdbBPyPkk0FAQXpqFb
rBiGvTs5O1N4dU4PwyY8fw4ivbyCHUCoiNb2cRNy/n77PHPf7nHLjALFRqFm
06hn7344PXs24n/V+yP6++QAaPfkYB//Pv1+9+1b9wffkcCXox/eyu/4l39y
7+jdu4P3+/wwXFWdS+92f4J/AMbk2dHx2eHR+923z5DP2piSAAVMx4QS2Aqi
ZLjDNGmdT1mAvt47VltfJre3/0I6xdY39/eKv/wraBXw5RpUJZoMxAKQAn8F
9MOOLRZGo1zH7Qe1cZG3QL0jnKIBZigV7izg9kcQck0DQPmtAwGFRALgzvQ8
B2la827hb8xlVVFdiGTLy6R/Nk/g0Fc6y2hLgEZMIDmIjyskSaQXINcxSGzi
Phy7AaVorE6Z3EHBnFagsy1yoFBkA6cuVagtpJcayCfDQ6EjTpSK+RaIqwHp
Wzei2QgbLfRNUWkgEkRKOCVpMZapLRRedIRg4NCggJMgmtXVnNYHZ8c0L+kG
1EaBfw1wKMiJgVkOWA/ZEek+g500yAXzqnY3BvfB2E65AS6H53QBBgHsz1xd
wKEPpwerJwHsjdMuBNacNHNic7g3BopXoQHkNpA8PEA4JgHv9S4GzmteO/Yk
wUGCMxvVLkCVXZgCFpjhShFtrArhyuAZuACTiZbGkznJvCNYLn9elu4B1CCH
cUTQk/hjdTN1ui3aBYVBGmnseZUhXwJp4+nhyB64Mr8oY+aMGJq3ssTZwCJD
SdXe4CxA8gPbsWxY8VkFMFMwilUa0Cp1GjSvaY2CmlhvyqeEXQvqC7wWpkyg
IY0/gkIxh/FqEPQ4K0oE2Fw8rFvjNwkITqeXcLDRSvZNvJKYdlZRzrrLysxn
WpZdFNmEayxrj45F2NYyq6535N+Ayu1CSBSiiA5pgqGGWaLNnJCNs1vDJEi8
uOojIPWr3FwnZHa8cZpX3ggdsaQHYwTIo+CjUBSxsbPcQWe/MfWETjNWJgEt
ur5grkyXgFhUYtBcx4EBPjgyQe/Nm8sEFXdSE1FC5s2c1E88Zy5EOiBcIMKB
EeBqNWDywcG/bPypTmdUBdqynsJ5APSg0xqlVZbPSJFv+XFrRKBsOLDSmHgp
0C+dkohb1j86cCVWYTSgTxtUQWh5JWn1CCup6XZxEyKpGNPerHS6TYJGR36x
rJmKQhFOu10ak1nVMjhaRF2l5bkDJmFCH1xUZvUgQSkMlDWXqHM7zTrpA0y4
bU1jacE+3qMHddjCqZziLuD9ZCdEFisQBxm7wfpYdkd6Ly8gUOADqLypgPYY
7N+iKh3aWf4inua61BdObmvQAjO7RNNYMEiAWSPPqaVuKhnNatRuHH+kyYgj
J8LpAiDZNCwt2iqBkx2kVHZjzSQ51nmlgkxUL8GOsXDxxKIfMxNd50XhBDzb
X6Ss6tSfG7ENE28hAhgM3WV+Uj+JoUg9WMBQwkt0yJiPecOilWRCjxAca4Jh
hsCALqHbljVi5P8LsB9KZpNVPOsOs77WnVjsogGDFFvYPYstAtzCnEwDa+BE
vingXnyG3CDo4EI3SJL84x//APnMnxfjX/F54Ya5U/3PLvodZIeIVwbu4Ye7
0PztkXmHf/fQPABUb17RbIk0H30ANFAx7ewBhc99wrwx2q8eWe/dw3vw2Hzr
Q3cXDTYk7z55sM8D2XrkavH54uHBOvPF4mFt6IYHe+Rj7w7X8yIaLP7lxYov
/NAf6c8/3dESTknc3UWD3anv3al3RxdPD/cZDvgiZpWK1nHXgTYc7L1VB/h5
Qpod7JhFfncwp4v3BlNq4+x40wLzvZV10ZfeYKIOdwZ7Cs4e3gC8/AQptILQ
Ag54XLQ89gkge0xeBL8/DBn+v+cPnz1x+fyejp3fAWFEZ80qIJ/Em0/A2a//
9CTtp50sAvCvOV8WH0DxXud8IVYUfwg+v0FaArDr5poT0udFjxAGP8O/P3ys
w+eH/eOHT/RhaD7t84L0ldsd9RysBQrGBq5zjPF+9yyS3M/uyQD0Au994O1G
bcifaMfWSiCP5sB1dfvc2RRjsimae3FBex+8VZatSwk98YOWiKjHgTWFGh5a
Y+xd6fj2EVbnHwmc4KFFA+piKfa8t2tCTTAw5DZZzV8JHnvtcS1kDbNLkN1/
gPVzdn2cWyA2rMVrQ4JLtDJefoRbzcutzR21q8D0Jf3+StcUABoXprwAYibD
F54C+uD13djlhKuUUCL7H5ylR5azNWLY0kSvOcaMGItoevdXR/6IDLVR1OTF
hiXbSvxVmjRy3FeyarN4HosD9jisg4Ps5fa6OGBf+dMwEAYUxJYq20cQ4CIy
jUQ6AoMvb3xYzFuFye0t8lyHBcCoiJ3HA9MpNnYRogHaQcruo3OHLROA6vzg
/d7R/sHJ+ene9wfvDk6Vo+Lz492T3Xe3sBpLaWoj3xyhG2uAe98yrh+44z90
sQReIUlFmSKipJwKpPEIKlCwttTh/sDl7fDyZIIOtvvknmzP8/2D9VaV/X9Z
VSiYO0RiRfMQeEhkMDYKamaruf54zs6783I5f4itpsJWK9jJMjl7IJE2p0WV
flBN/guIxXxiJiOOhS3nU4njiYMRLHujgSecf4RydDZtSEXG8QJBAhp5HHUc
4gQkdglZTSne1/rQELlmhbF5lTwP+TWFLWCqWOZhdoAAyckTPpoPguCqKpYC
DY4irtOsouiteE+VVrP8I8oVh50R4Qvj5A5wH2fjqFhaLDOTSXqCVuiwokAj
gz9a7V6ikwV2xiww2Fm23is1Ua9v3HEoIrAxzmtc3FDAM3KAlVYsqowcNGkb
ycwQVREQI0W/kMtyWeZZLn5wXST2/t87gHGDxBc1K8xH6xiSuC3Ox/5BcrzA
ia4zvWjJJY1R48a5qSmOQb6cyNlJzr3KOp96fiFxiYVRenHvRo4n1bSgJjaj
aP3o1UpQpaCEMV1nsLdAwOSQm+V4zNfmAhBHPgxSLQ933++qDZtvpnYbcYi/
Jx5p1C6lkgFcpD8ARvzIDNvFEjYLHicVSM8LdPPHmSqMgNDFZj12cSgB8bLP
yk2w+JHKZ+Tk55j8F42LwsjhBQcN/IGceGM1KQ6r927lAHqEWc6wQhaxFIFM
beOT6OhxoX2KLKzSLG+fOwVsjOPfhx53p/GtOi8bKxQfU+5GCbB5tWwLUtNA
MJ3KHa8mW+7ARiXZPYHHdVEsMSmttWldGtFucRViQzhTjuK9Ikd2Xe9zauor
0jP4s45q/6fE3d7XEr67PTk42D8/PXp79O7o/eivRyf38e2x9vDdbf+O+Fz5
buul//mP68Dnb48+Q7DGk68CMVzR/YrRVwD/Vc8M8gq/nLWeMLsELqdtclwY
3VAqiGQXiENbp+0SDgzn28drsvmzvMacN5MWWoLCVqUV1vq9DR66GEGT5C1J
anJcm4n6EY86ZkukEcvKnHmwrno4olEvq4qiGSUFHhZeCJDgxxPc8TGHKDBq
PqC62zk6U7ONl9BRCjoIcCknFwaT+FMNhggshPceqcxXKSPwWqMEwAQftnWc
mu/wRclZiC+b0En6AS4xuo2SQQHmIYYdhehNq2WRCaqUT8rEAxB2/ltVofVz
nTeGn/KxncYUjLrEKyxTyg6owv37grLp6EwQbUAkyihe+hdNdDR5zQIPEdiW
x43M210L29ZIub+3g79fjVAfvR+2z9Z/PAmC+32CdlrgAhN7MTESj4hLQK+N
5bXLuvSRchaFtChnw50/vLz73r0r1/LqPiS21gIeKzALd/DyvhWSmeeWNNc3
Ei1WeoYGYkBVmOEVGBYusutDkhIoZ14rMNBXA17yBR0xOU+clzMwQzD67I5k
H8RCAUCM1eoL0HF9SmXocQQM7oZpciPHO95Pj9mTfA8s7CJHvZdiOZz118sj
4rxI5jMO1rqMgm7KQdWNsfKifXhbLqekxJPKTrFXnJ2sB5MlmK5M+aUN6Z9z
0roFvmoehOvlrl6UEsN9ubmSJfo0rTCc7LKcgnycJNmaWN/jKa0ITDi1QX5E
Qs0OhQAYSznmAZtryYIoUT/+OxiQVmtM/UES4SjIrkXtriJBMROjAgYn8ctz
o/b/UbU3ixxD2Cg2ticdZ+eOPyZAq6/mA+ksc4NJYiHFo47ESW3NqIOChMWg
pGAF5BENyjpwHUHSgYzcK5hWT4MfSyz7cH+URHknkvVnTUH57YPBxe62ERX3
slDCrBadio1GLAQSl58NdstmiDB4iRzkZJ4Jt8RJbep0OW1gBthNsKg6s4uk
d2gikcE82Hbwksi8LjuWBIc9goi3QYbNMMsdSTowsjvw/JkmKxAYHi+apWMs
53PKrkZrMKD/YJk2edCxQYNYIiqcOAFiYR4NPSlpT1RsUrA0k7wnMIUq0scd
+kdqumzxwLZp6YnP1sWztqUswb7MiZmJxAtoL8jEUYaw4NQJyCRGzopFomr4
q5zsA58XyWPhhjDAv87n7jeAMRp/LSh6n791BgmXRaK68zlhUsrU73ymdxDs
WB8S3Z3oUwbpfewgjGuO8KwKhA98+LE7SwL8DTQaIOHd40MYfv3doXSJq+ix
OyGqaJanAve38LG7iEw/FWfRl08a8TQWKQ+OGN07OFpIWiJMPgOM8nkIxjhw
2NsackANfOSxu/AxGfEuckGvDSo/Fsb5uzDerYBx1SdOLopgdHN+0mf9vW5W
DfEU6rEBYVEHVnw6dz044u86qtjQeL17Ph89Dj7GI9oD47GMns7HPnYXPnaX
sFCSDJVTrrxZU57dyVMi/Gt+LAkns58nwmhTDj7LWdY9QaLqigc+0X3xIFef
Csn/vkKi1HsuMfw/hLHrpUNwxlgmZ710WPCt3uCFwDP3/LmlxyMbWIBrz7mq
iqyasS+vk80iOyT0MqMai/mgYIhKKdvNgjN/SbuwwR8q53QlwxPUkFEToSA8
3MJ+QFv3gQZJISY1D4eOg9o0y4K8hwCdU/h9KdqyzQsJD5DbDkycoCiLHRcr
ygka64W6QoVf/EwYvguAQsSleDkVa3+U2AgYQAYGc+qS6ltX4BnUReIjVK1g
U63fhNW7LVcO0d3kMiup+jao1aUpOTwaxcik0pYK5J6rQ9b4b4aLMpxoTpLD
Xka05URClN23cFekYhFB2FhVar1pUR8ZKFLAqQmADTl3Dl18SLwDPDOGE80N
G1Bsv2COhPc8JBJBQHxMXEAU41lAymTMXppi0amoLHRtvaCD7owkiIA4q8jH
JcbqRy5+13XrSDunaE0TWMWcPQ57gv6hku/Ofda8lI64CgA7KvsurNuMvRY8
eBBN7pnYME9RlRdo1HHafk0lVOjX/aIhTQ5sWIsSrAOU8f3xzFaf+MP7rE4r
olRjGMAmsnj/H+FggSjOGHMYt7SeHRf7c+5JG14Ppi+zhHbuqiqubDFVH/3K
1SPyZsJiX4fuYT0FlRWrFRv0vgfFb96XYXfWzy0sVKUAVhLUnpkyrW8WoZM7
4Axv2AfeSFvfjC4sW+sYuwO5moR3AL1dDuse4zzBKMkMCCAMMHBM1UUEUcJg
NRF6pxZYimBbNBBZuamiegEeU8KnHPVt/O5JCoPwkt1sW3BtPqbGMLm8O/tB
bbzTH/P5cs7uWZuZ+UOZt5vcpQDkuVu6dbAgsmkR4iVSBx/R8gTpIPzvnVpx
HU4VlLaIs7SR/AILryt8gqV/0TgxEdS1AhLeYOjbqK9FMv45dDahU6xTjhe4
48XH59ObTKiHYr2L+PXQ8eycI7EruM8BjvomyaGvi/czrhJ4YaKe3Xcn2QBb
yOoXJZ5WAVGRoJz+bNK2i7N4JStRdhYWSjoYLVOg91XXNa4OG1JMfYApcluP
vE7APljfDsC7JskrVeNR13YEtI9Ukwx+7RJHdtT3oMrMKfZusW6PL877iGWK
Le6357gm3/GSBMMSyBgTURhSF1zQ0huBU0HIkZlSpD+qB3byBnUarBV2fT4K
ZGXJqgjA9RVYHT+g9YUG9cPiaHMlyFjOvmF9vZs7KqJX/NF5dB/bj2WzxN3A
tjlBwZvNtrFY69D8EO1h0kcnfQ9YzdorgV5JLHgs1BO4GYT3DsuOXB2FRx9s
8YXpn88igS+sY9cvpoFJm9557932HKk4czPIkpr1fMnfYhyh9zCeUxjpbimI
2q0OBQIw3hNs+cptmJ5XS9Sm+0Wo/ZJrn9iV+H4X/S1vbOgI42rO/a7OUJ/m
gA9pK2FWZW04U1cOE/L5R9k/XHH9UITHhme8P123rQaAMhvb6jDstyGpyZDR
SC4QIljgjh1RfhswgV400r0jjCW0RMwuB6y4+dbVuK1s2mF5ZKBRD+VRdxtz
JP3GHHTKXuorbMBjyhV9OlSvTwdbZF3k8rbdPgccS/cQ3j08Tt6c7L478Bjy
J4iLn3WEfwSoxbDkWXSCXGQ+WmxJhqAdReJrXnkD2E8drH5jWP2KlJ4BVdOp
SVbJ5FMfa29tWpp/gtR+aUuDt81FNYkVmohjKMOabEwiQe2OxE5gccBwsZad
t5XKtjNVhFI5y7BJSbL6kSi8wvKeNS4r4lDpEsUqOT3ZOz/96d3ro7fnHsNU
g4/9IjgMM3QPZuIis2PGrfqOM1m/woOO3ADItZxbu1otoxvihNumTseMrnGe
jWXj2MUwAAMn2wbzPZRFyxFFqzXZdHHidtst6XLQ9hk/pFmSaHp0Wkoxabgc
vxOHpuwye/RFBENV2KGG2wSskmc+DyKMRgdV+/FgNrlX1AHW/tqoKgJTAYMy
2lcg81EBDT5bdGmFg+lF7DMSv5YDV7xTDtzs40pXVWekkECMbMWYVzcWjxFQ
i6WT1ZslPqn4LLDiT3oo8VUnCA+leBmPXTlfvByac2E04hBtxFF40kSSyloo
aPpQGlRfkCYYgKXGT05ImqxrJPT6usS64qwzZ1UvqtrmZw66JWxO5MnB8e7h
ibDXA/z9NTK0TApokGR85j+XSg8bkPMOOAWPdwD2aONLJiq69d4P9hdUPcPf
4k2ye7hx0JMYLOus0IgkxsCqWGK4FaDI8MmdwUp+A0HybTCRo1GBJBQoFgu/
WqgoFajUobb4K+VKR/UcD+4hQB+UEKDx4A0QUCUx44/VSM4wCUt1Yp1lPEwK
O90aoU7ayjUmstljEauHnIWoi/yibFyfgkREFJj5BReNOjStlJdixhLXT0KZ
gkpeR6D4pmxs8/Z6uHG1hW3iFbRT4fYw62qJTIVRyGO1hsih/tDhKmrjDfoO
0FsNxmSbp6Dj5+SAbQmdVgxJrjzP1utG1+u1YrO5t76ZvAJ+i7Nt0g9ldV2Y
7IKSKUlhKSVJX/qf2LyQ6Ff2U41IbJKXzo1DrbioXoysOqa3KBsFqPCSmagU
e9x2cSS4FpItGCT4lplP8EV285vo0lydqdTxYFo3Btm8iESbEXQJhNTfnMwU
OavvLi9pjmmRrqDGavV2w1zPEnbP2kQj13gPnQIL1000arwn4iEAarSyBR8q
ipJxSylzQd5jkCrVJW5y5FjSnqBIcOuQCh7bsc+GS8IhSEY1eUGWFWctGU+9
vbnED7cvFTQuifDUkivcmiS7BfY4vbgMD2tPwmFwYIDoon43ZM3L2Elg3uUi
XdFPD8cBGRU2JRLWMQ3ZlvxOIVps/0DyfOg+gOgTWWCv5rB/Icd0kGCY5kGm
UZs31+ls0ul2SPtGt1gy4olrDE81VWEoVTtmdBg02Ff06kn7oyxoseR7tExW
r4zhz9sm7BFju2SR2SJcargrkE+s1V4zcLAAWQVGrw2UaDS0UMAMiz7ZBGF7
buxFFyhbDjcHE8lBG0MosZ8runeIk5FeQUhrLG6FQcMlYI2RLmjhZ15suHUj
J191Mvtw+HirEOmtsZvgEtXjlWPnQ2BKnRG12WADapYpdsYq6GxF50y3tc4A
z1tfrG1qJnRGmh8pfX/YjN37rokQd+PqBDox6jLQcNM2HEopE1fPp3CEUqtj
qXi7WObNZby3gJ4mYF1h795J62zVFeerGDeepcnwHzs/RGOfR5oePN6SIEey
mufitMUZ9k2hQZnJTQG6qcsbdpoMMl3oGhZNBwWepMlh4R6K7k2ndR3svVd7
7KyjcSeRhh4oGAPq+R9Qc36L7dtAi9n1J2tmbXF8/IT8HjSFvfyGymH8j727
NyaTTawpQOU78ZcRhj/rRf/+sBZ3UF0H0hvU1d36WFFftZaHdGOYgWrnXVSu
kEEks1hZYa7nldxhWbLvO8NdmXL/6BAE25dRwi1K+N0qTRQiIFU8tU4hM7wW
Jh3uKhjQuh0YRWh/yx5afaf3gHcxu3HQ3YCzCjcze3Dnyz4ZrFeW3JkKeZ7Z
O1F93I6wlId3J8OwEDH6io1G+6QBgb2JOEZIsAQcZvjF1CyEG29PuxA5gCiw
DI56rQNgYhTvqAMul27rG9ekraFojl2Rdxv2zhxRW3HNFLXmY0arC+AQuB+k
XghG/BBaoWPLS2zbeHwOPtn4JtfkMMhcrLU2VznjXsVUy6A7866VZAOi5KoE
AQfH3JL+nBA4Q/zchS3ATJ+LLJvQxOwcCKYgcS4JQq8NGCs5iEw68E/cge+l
eZL80NEFBjzrgbbOhyIHYlzSCv4emUjXwUno7A5q1y1LEEWhj0c4N7cnao+P
29VKdnASD5y8rybqfYVGnvVeD5ycpA+MYnWP6m46egOm89TsDkBMSzYTZhd4
/TzWeWELDrEIOdZxo6USAQd4RqNFF9i6+YaNl97dyQrrcNRVuIOKiFjFt5jS
bQwZBZpcxE/9Tr2j3pBkNexJIoO2r3+QxpbWt085Wbiv2I2f/PySNYGeE6xu
pxIaSQIYft8EmYNO20E51qcmSc+Z5ZSngIXzOcc7qYrelkUhUORzAFymaVWz
W55OiUQ8SNTbASsjqbYKv02UjUnodqhkjOSgC1DOqpTYzLWF8Q6dJgmSOKRX
QhDO7JfdhdVItbmArS0kbwXvB6MQ3yVBjZMsphFdh5gl5N+rYB07QY1bFdjM
1Di/4gqzGKeEO8aWjZy5Vdr0lcQG3IDppG23RNfFEte9ro1WCgYhbKlU7FZ/
0ibSacVJWYhd3JUx7ZHsI7/1o6rFgiwpvguz1hUeKDiZOHJAaLdUzSp96K8E
eqE18WKhIh4HdfNujmKDL47o1NGggXLFxFTR2zi6gQUXQIzfbTBKfl42Urpa
dwJOX5IL85r2Powq+eLGL5nu0bnN5U2ZwvO9sN7QbeQH1O6tdAYId+KGnfx5
et5qt3tZL5c2LHvZHyh76aQFfw4YBj/daT79pqvVAK/uDhh/oQ5uvDdbKkjn
52aF63zpoV1IYYvuky/b4ZdX4ZcvH0L72qtYd4hgudsPLXfdRT1l3sc+n4Mu
BmuiohaQ+HzQM+g72A3345+kKIU/f/SX/cVH5r8LhPqdv8hNltaG/+4R+B/7
/JbM07kTB+FcsS1Z6jr8o4JWiJ/MQp07P89yPjNStj8/Ur4M8dDDUHjnE/jz
4eVEJQ/5xzHxzzj2do2b1iwa17Dx8K8H++r12yNQbg/jtwmc4n3o0ti3yoRX
vroqIKs/IrDQXUYueZt7CXb4HM/egnwX+P4sq1emJgktQp84GETHnKIg2g8p
DLoQKyFKFkYd7vWypWMdiyUkt6bbx6/puQd8s6+0oVCjy0SNhyAFDgC4SQJF
FMVT6GR33cRdy3huFeZfJJaaGpOTgkYtygDyqxv/CgWMPpLLI+k0LPFmbAcx
uXg3fMazZghH3G3L7mAYknPKbEJN0Jz6jO3HwILIp9Q0Rt6wRgpdsNBRPBxs
O+Ld9jjxvkpBPgKVcBOvIsRdM/ksetVjatVvr1X9U6n6p1K1ct7HPv9Uqv4/
KFWfX8P6/OpWpIB0HvsNVr32kCvR9Yju9alICX98iobVhTNSquD4Wkerenvw
18PXbw8eUawOS6wyqdtuw5x+g2DmWerthEP4jqM21Yd7YI1cJnffeSSv+Axd
Tf15hmYAELF9j5tkkux23xlGipNPjg5UGHk7mB+Dy2Kdj9qrVhLSnVagPDEy
7Tuw5K2p+GIdfKtpf2lUidJgdCGsgeu8tonimOjfIxcwNp7it8KQtHIq2/dn
Z8e/f0WrwPeYOuegjbNyYR3BF/q6aO94jagDiV5KOmgf3Oi1tVmOEZu5vBJP
he+18V0nJ0gqoHDb2ibX8NknvKBT7pKC63HNiAXLdrTruD8lp0yX/pU+pHDC
1RRTs2fd4cQ5KccoFfSQ4xQWkqk5tjz0ur115nIQWdylwdAUrKSApvcz99A1
wfcwVvgzlxPKS52FRnTURxOj0pGXjlsnjnePj1cdBPGH+8Xh/YG4CEXHVdKY
lrrCpQUww/nu8eEGuwzP82xz9UN8C4VFJtz7FgeBA3imi8asfM41g+LZcF6X
UuNCw8OPhssaP+Xzp+hRpMRzablw+yj+ulJ2MpmQStCMHn209+ze26PTg3Ns
100VHbcOzfePPTtwwxPmffhDHal620Hx4N6GPPXzNEjiT1ehefjzGD2GZx6t
lTooPHTk0W4RR6867TBumi6xV2Un8nX2ep9eho7tj6NfmlWvbvZVWSs7+HKm
lG/PSW1SKXUF14l3IGXbRMSoyIvbK3CO7PsVc/Bh5fPTOfxOOWWd/ut0+/19
cATqLPOpks9I1A80Z2+eSYNofPkjl4S624/lWHqmUORzmZTv6n64r+6CJu+l
7U0DWlX4srYk4vrB7itDFxPX75/HHOimedfHAmAgsa9jCB7stNZ86MFp9GCn
Uf2KB5GEh7bDEq0t0Fa2pm9oH9RBiZ0fG6nEeO9qAbs0EBCPe30HUQT9MKYf
HiOEoB7xifvPT/LLpJR7F5Tb/M+8/1/5MV1pifIT3d76yjzZv6/dj1G1iX9i
qJhFnv1D91mfUhY9G7xMnMWXR/zKLQ8wHu10kIDDzeOj6m8tzcBFncQEhzqn
+DkISdQtfaY6aIKXJTdIAV1vKSmN3PEddJfTa9NSRwJdfqAgJyWf2E4VkqDo
37ZLL2S0L1T0b/pMkv8BlLD6uWqFAAA=

-->

</rfc>
