<?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-ietf-scone-protocol-11" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="SCONE Protocol">Standard Communication with Network Elements (SCONE) Protocol</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-scone-protocol-11"/>
    <author fullname="Martin Thomson">
      <organization>Mozilla</organization>
      <address>
        <email>mt@lowentropy.net</email>
      </address>
    </author>
    <author fullname="Christian Huitema">
      <organization>Private Octopus Inc.</organization>
      <address>
        <email>huitema@huitema.net</email>
      </address>
    </author>
    <author fullname="奥 一穂" asciiFullname="Kazuho Oku">
      <organization>Fastly</organization>
      <address>
        <email>kazuhooku@gmail.com</email>
      </address>
    </author>
    <author fullname="Matt Joras">
      <organization>Meta</organization>
      <address>
        <email>matt.joras@gmail.com</email>
      </address>
    </author>
    <author fullname="Marcus Ihlar">
      <organization>Ericsson</organization>
      <address>
        <email>marcus.ihlar@ericsson.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Web and Internet Transport</area>
    <workgroup>SCONE</workgroup>
    <keyword>locomotive</keyword>
    <keyword>pastry</keyword>
    <abstract>
      <?line 62?>

<t>This document describes a protocol where on-path network elements
can communicate their perspective on the maximum sustainable throughput
for QUIC flows to endpoints. This throughput advice suggests an
upper bound on long-term average throughput, independent of and
complementary to real-time congestion control signals.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://ietf-wg-scone.github.io/scone/draft-ietf-scone-protocol.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-scone-protocol/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        SCONE Working Group mailing list (<eref target="mailto:scone@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/scone/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/scone/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ietf-wg-scone/scone"/>.</t>
    </note>
  </front>
  <middle>
    <?line 71?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Many networks have known rate limits or apply these limits
by policy to constrain data rates.
This is often done without any ability to indicate rate limits to applications.
The result can be that application performance is degraded,
because throughput limits can manifest in ways that are incompatible with the
rate estimation or congestion control algorithms used at endpoints.</t>
      <t>Having the network indicate what throughput limits apply, in a way that is
accessible to endpoints, allows applications to use this information when
adapting their send rate.</t>
      <t>The Standard Communication with Network Elements (SCONE) protocol
is negotiated by QUIC endpoints.
SCONE provides a means for a network to signal its present best estimate
for maximum sustainable throughput,
or throughput advice,
associated with the flows of UDP datagrams that QUIC exchanges.</t>
      <t>Any network function that is able to update the content of UDP datagrams
qualifies as a network element that can use SCONE packets
to provide throughput advice to QUIC endpoints.</t>
      <t>Networks with rate limits can use SCONE to send throughput advice
to cooperating endpoints to limit overall network usage.
Where congestion control signals --
such as Explicit Congestion Notification (ECN) <xref target="ECN"/>, delays and loss --
operate on a timescale of a round trip time,
throughput advice operates over a much longer period.</t>
      <t>This has benefits in some networks
as endpoints can adapt network usage to better suit network conditions.
For example, radio networks and battery-powered devices
perform better with short, bursty exchanges,
rather than constant transmission at a fixed rate.</t>
      <t>For endpoints, SCONE throughput advice makes network policies visible,
which can reduce wasteful probing beyond those limits.</t>
    </section>
    <section anchor="overview">
      <name>Overview</name>
      <t>QUIC endpoints can negotiate the use of SCONE by including a transport parameter
(<xref target="tp"/>) in the QUIC handshake.  Endpoints then occasionally send SCONE packets,
which are always coalesced with ordinary QUIC packets that they send.</t>
      <t>Networks that have rate limiting policies, or known throughput constraints,
can detect flows that include SCONE packets.
The network, via an on-path network element, can indicate a maximum
sustainable throughput by modifying the SCONE packet as it transits the
network element.</t>
      <t>The propagation of SCONE packets,
including the throughput advice that is updated by a network element,
is shown in <xref target="f-scone"/>.</t>
      <figure anchor="f-scone">
        <name>Propagation of SCONE signal</name>
        <artset>
          <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="192" width="504" viewBox="0 0 504 192" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
              <path d="M 8,32 L 8,80" fill="none" stroke="black"/>
              <path d="M 40,80 L 40,176" fill="none" stroke="black"/>
              <path d="M 80,32 L 80,80" fill="none" stroke="black"/>
              <path d="M 144,32 L 144,80" fill="none" stroke="black"/>
              <path d="M 184,80 L 184,176" fill="none" stroke="black"/>
              <path d="M 224,32 L 224,80" fill="none" stroke="black"/>
              <path d="M 280,32 L 280,80" fill="none" stroke="black"/>
              <path d="M 320,80 L 320,176" fill="none" stroke="black"/>
              <path d="M 368,32 L 368,80" fill="none" stroke="black"/>
              <path d="M 8,32 L 80,32" fill="none" stroke="black"/>
              <path d="M 144,32 L 224,32" fill="none" stroke="black"/>
              <path d="M 280,32 L 368,32" fill="none" stroke="black"/>
              <path d="M 8,80 L 80,80" fill="none" stroke="black"/>
              <path d="M 144,80 L 224,80" fill="none" stroke="black"/>
              <path d="M 280,80 L 368,80" fill="none" stroke="black"/>
              <path d="M 40,112 L 64,112" fill="none" stroke="black"/>
              <path d="M 152,112 L 176,112" fill="none" stroke="black"/>
              <path d="M 184,128 L 216,128" fill="none" stroke="black"/>
              <path d="M 280,128 L 312,128" fill="none" stroke="black"/>
              <polygon class="arrowhead" points="320,128 308,122.4 308,133.6" fill="black" transform="rotate(0,312,128)"/>
              <polygon class="arrowhead" points="184,112 172,106.4 172,117.6" fill="black" transform="rotate(0,176,112)"/>
              <g class="text">
                <text x="44" y="52">QUIC</text>
                <text x="184" y="52">Network</text>
                <text x="324" y="52">QUIC</text>
                <text x="44" y="68">Sender</text>
                <text x="184" y="68">Element</text>
                <text x="324" y="68">Receiver</text>
                <text x="108" y="116">SCONE(?)</text>
                <text x="256" y="116">SCONE(advice)</text>
                <text x="96" y="132">+QUIC</text>
                <text x="248" y="132">+QUIC</text>
                <text x="372" y="148">Validate</text>
                <text x="428" y="148">QUIC</text>
                <text x="476" y="148">packet</text>
                <text x="352" y="164">and</text>
                <text x="396" y="164">record</text>
                <text x="452" y="164">advice</text>
              </g>
            </svg>
          </artwork>
          <artwork type="ascii-art"><![CDATA[
+--------+       +---------+      +----------+
|  QUIC  |       | Network |      |   QUIC   |
| Sender |       | Element |      | Receiver |
+---+----+       +----+----+      +----+-----+
    |                 |                |
    +--- SCONE(?) --->|  SCONE(advice) |
    |    +QUIC        +---- +QUIC ---->|
    |                 |                |  Validate QUIC packet
    |                 |                |  and record advice
    |                 |                |
]]></artwork>
        </artset>
      </figure>
      <t>QUIC endpoints that receive SCONE packets observe the indicated
version and extract the rate signal. They record any throughput advice
only if the coalesced QUIC packet is successfully processed;
see <xref target="recv-advice"/>.</t>
      <t>Throughput advice only applies to the direction and path for which it is
received.  A connection that migrates or uses multipath
<xref target="QUIC-MP"/>
cannot assume that throughput advice from one path applies to new paths.
Advice for the client-to-server direction and the server-to-client direction of
each path are independent, and are expected to be different, for reasons including
asymmetric link capacity and path diversity.
Applications can use SCONE in either or both directions
of each path at the discretion of endpoints.</t>
    </section>
    <section anchor="applicability">
      <name>Applicability</name>
      <t>This protocol can provide throughput advice only for QUIC flows
where endpoints send SCONE packets (<xref target="packet"/>).</t>
      <t>The operation of the SCONE protocol depends on network elements
that are able to modify packets as they are forwarded.
This provides endpoints strong evidence that the network
element has the power to apply a rate limiting policy; though see <xref target="security"/> for
potential limitations on this.</t>
      <t>The throughput advice that this protocol carries is independent of congestion
signals, limited to a single path and UDP packet flow, unidirectional, and
strictly advisory.</t>
      <t>A companion document <xref target="SCONE-MAN"/>
addresses applicability, operational, and deployment considerations in more detail.</t>
      <section anchor="not-cc">
        <name>Independent of Congestion Signals</name>
        <t>SCONE throughput advice is not a substitute for congestion feedback or congestion control.
They are complementary.
Congestion signals,
such as acknowledgments or ECN markings <xref target="ECN"/><xref target="WHY-ECN"/>,
provide real-time information on loss and delay
for a network path.
A congestion controller needs to detect changed conditions
and change sending behavior more quickly than SCONE allows.</t>
        <t>In comparison, SCONE throughput advice operates over a much longer period.
SCONE provides an explicit signal
regarding potential throughput constraints on a path.
This allows applications to set throughput targets quickly,
without waiting to estimate achievable throughput from observed performance.</t>
        <t>Congestion signals can indicate a throughput limit
that is different from the signaled throughput advice.
Endpoints cannot assume that the rate indicated in throughput advice is achievable if congestion
signals indicate otherwise.  Congestion could be experienced at a different
point on the network path than the network element that signals throughput advice.
Therefore, endpoints need to respect the send rate constraints that are set by a
congestion controller.</t>
        <t>Networks can use SCONE to communicate throughput advice
for reasons other than rate limiting policies.
For example, a network element in an access network
could provide reduced throughput advice
to guide application use of network capacity
during periods of unusually high usage.</t>
        <t>Throughput advice can indicate temporary increases in available capacity
or temporarily reduced capacity.
This includes persistent overuse, equipment faults, or other transient issues.
Providing advice is applicable if increases or reductions
are expected to last for more than one monitoring period; see <xref target="time"/>.</t>
      </section>
      <section anchor="unspecified-scope">
        <name>Unspecified Scope</name>
        <t>Just because a network element can set throughput advice,
that does not prove that the flow can achieve that rate.
Nor is it a commitment to providing that throughput.
It is a hint that exceeding that rate is unlikely to be successful,
from the perspective of a specific network element.</t>
        <t>Throughput advice is signaled for a specific flow, but the underlying throughput
constraint could pertain to a collection of flows, rather than a single flow.
The scope of the underlying throughput constraint is not carried in the signal.</t>
        <t>For instance, policy limits might apply at a network subscription level,
such that multiple flows receive the same signal
and combined usage contributes to a shared capacity limit.</t>
        <t>Endpoints can therefore be more confident in the throughput signal
as an indication of the maximum achievable throughput
than as any indication of expected throughput.
In addition to endpoints respecting congestion signals (see <xref target="not-cc"/>),
networks might need to monitor and enforce policies,
even where applications attempt to follow advice (see <xref target="policing"/>),
since the combined usage of multiple flows might exceed the shared capacity limit.</t>
        <t>The advised throughput will likely only be achievable
when the application is the only entity consuming bandwidth
in the scope of the underlying constraint.
In the presence of multiple flows,
achievable throughput could be lower
than indicated by the throughput advice,
with the throughput limited by the congestion controller or application rate control algorithm.</t>
        <t>This implies that signals can most usefully be applied to a downlink flow
in access networks, close to an endpoint. In that case, capacity is less likely
to be split between multiple active flows.</t>
      </section>
      <section anchor="per-flow-signal">
        <name>Per-Flow Signal</name>
        <t>The same address tuple
(IP version, source and destination IP addresses and UDP ports)
might be used for multiple QUIC connections.
A single signal might be lost
or only reach a single application endpoint.
Network elements can apply SCONE throughput advice
to all QUIC connections that include SCONE packets
to ensure that advice is received by all application endpoints.</t>
        <t>The signaled advice applies to the flow of packets
on the same address tuple for the duration of
the current monitoring period, unless it is updated
earlier or the flow ends; see <xref target="time"/> for details on
the monitoring period.</t>
        <t>Rate limiting policies often apply on the level of a device or subscription,
but endpoints cannot assume that this is the case.
A separate signal can be sent for each flow.</t>
        <t>When network elements provide throughput advice to a QUIC flow
that encapsulates tunneled flows (such as <xref target="CONNECT-UDP"/>)
they can only provide the advice to the outermost flow.
Tunneled QUIC flows cannot have throughput advice applied;
see <xref section="3.13" sectionFormat="of" target="SCONE-MAN"/>.
Endpoints can apply the throughput advice to packets in flows
that are subsequently encapsulated,
but following that advice can have privacy implications;
see <xref target="active-attacks"/>.</t>
      </section>
      <section anchor="unidirectional-signal">
        <name>Unidirectional Signal</name>
        <t>Throughput advice is signaled with SCONE packets
that are transmitted as part of the flow that the advice applies to.
Carrying signals in the affected flow,
in the same way that ECN signals are conveyed,
ensures that there is no ambiguity about what flow is affected.
However, this means that the endpoint that receives throughput advice
is not the endpoint that needs to adapt its sending behavior.</t>
        <t>A receiving endpoint might need to communicate the value it receives
to the sending peer in order to ensure that the limit is respected.
This document does not define how that communication occurs
as this is specific to the application in use.</t>
      </section>
      <section anchor="advisory-signal">
        <name>Advisory Signal</name>
        <t>Throughput advice indicates what one part of the network
expects to be achievable for flows that transit that portion of the network.
It is possible that very different throughput is achievable --
either higher or lower than the advice --
as determined by congestion control.
Endpoints that receive this signal therefore need to treat the information as advisory.</t>
        <t>The fact that an endpoint requests throughput advice does not necessarily mean
that it will adhere to advice; in some cases, the endpoint cannot. For
example, a flow could initially be used to serve video chunks, with the client
selecting chunks of different bitrates based on received advice, but later switch to a
bulk download that cannot be similarly controlled. Composite flows
from multiple applications, such as tunneled flows, might only have a subset of
the involved applications that are capable of handling SCONE signals. Therefore,
when a network element detects that throughput exceeds the advertised throughput advice,
it might apply rate limiting.</t>
        <t>Network conditions and rate-limit policies can change
in ways that make previously signaled advice obsolete.
For example, routing changes can cause a flow to move to a different network path.
There are no guarantees that updated advice will be sent at such events.</t>
      </section>
      <section anchor="application-use-of-advice">
        <name>Application Use of Advice</name>
        <t>Applications that choose to follow throughput advice
do so in the way that best suits their needs.</t>
        <t>The most obvious way to follow throughput advice is to
inform the sending peer of the advice so that the peer
can adjust sending rates as necessary.
This document does not provide specific guidance on how applications
might adapt their use of network capacity in response to advice.</t>
        <t>Some applications offer options for rate control
that can offer improved performance when following advice.
For instance, real-time and streaming video applications
can often dynamically adapt their network usage.
Typical HTTP Live Streaming <xref target="HLS"/>
or Dynamic Adaptive Streaming over HTTP <xref target="DASH"/>
clients are provided with manifests that allow them to
adjust the bitrate and quality of media segments
based on available network capacity.
Low priority bulk transfer applications, such as software updates,
might also choose to follow advice.</t>
        <t>Following throughput advice could
reduce the impact of an application on other network users,
reserves capacity for high-priority activities,
and could avoid potential enforcement action by the network; see <xref target="policing"/>.</t>
      </section>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="BCP14"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>In SCONE:</t>
      <ul spacing="normal">
        <li>
          <t>a "network element" is any device in the network
that can produce throughput advice.</t>
        </li>
        <li>
          <t>"Throughput advice" refers the information communicated
to endpoints by network elements
in the form of a rate signal; see <xref target="rate-signal"/>.</t>
        </li>
        <li>
          <t>A "monitoring period" is the time over which rate signals
apply; see <xref target="time"/>.</t>
        </li>
      </ul>
    </section>
    <section anchor="packet">
      <name>SCONE Packet</name>
      <t>A SCONE packet is a QUIC long header packet that follows the QUIC invariants;
see <xref section="5.1" sectionFormat="of" target="INVARIANTS"/>.
It only includes the header, with no payload.</t>
      <t><xref target="fig-scone-packet"/> shows the format of the SCONE packet using the conventions
from <xref section="4" sectionFormat="of" target="INVARIANTS"/>.</t>
      <figure anchor="fig-scone-packet">
        <name>SCONE Packet Format</name>
        <sourcecode type="artwork"><![CDATA[
SCONE Packet {
  Header Form (1) = 1,
  Reserved (1),
  Rate Signal High Bits (6),
  Version (32) = 0x6f7dc0fd or 0xef7dc0fd,
  Destination Connection ID Length (8),
  Destination Connection ID (0..2040),
  Source Connection ID Length (8),
  Source Connection ID (0..2040),
}
]]></sourcecode>
      </figure>
      <!--
https://martinthomson.github.io/quic-pick/#seed=draft-ietf-scone-protocol-version;field=version;codepoint=0x6f7dc0fd
Plus https://github.com/ietf-wg-scone/scone/issues/45
-->

<t>The most significant bit (0x80) of the packet indicates that this is a QUIC long
header packet.  The next bit (0x40) is reserved and can be set according to
<xref target="QUIC-BIT"/>.</t>
      <t>The Rate Signal High Bits field consists of the low six bits (0x3f) of the
first byte. Together with the most significant bit of the Version field,
this forms the 7-bit Rate Signal. Values for the Rate Signal are described in
<xref target="rate-signal"/>.</t>
      <t>The Version field contains either 0x6f7dc0fd or 0xef7dc0fd. The only difference
between these two values is the most significant bit, which also contributes to
the Rate Signal. All other bits are identical, which facilitates detection and
modification of SCONE packets.</t>
      <t>The Destination Connection ID field <bcp14>MUST</bcp14> be set to the same value
as the Destination Connection ID field of the other packets in the same datagram;
see <xref section="12.2" sectionFormat="of" target="QUIC"/>.</t>
      <t>The Source Connection ID field is set to match the Source Connection ID field of
any packet that follows.  If the next packet in the datagram does not have a
Source Connection ID field, which is the case for packets with a short header
(<xref section="5.2" sectionFormat="of" target="INVARIANTS"/>), the Source Connection ID field <bcp14>MUST</bcp14> be empty
and the Source Connection ID Length field <bcp14>MUST</bcp14> be 0.</t>
      <t>SCONE packets <bcp14>MUST</bcp14> be coalesced with other QUIC packets
(see <xref section="12.2" sectionFormat="of" target="QUIC"/>)
and <bcp14>MUST</bcp14> be included as the first packet in a datagram.
This is primarily to simplify the process of updating throughput advice
in network elements.
This is also necessary in many cases for QUIC versions 1 and 2
because packets with a short header cannot precede any other packets.</t>
      <t>A sender <bcp14>MUST NOT</bcp14> include more than one SCONE packet in a datagram.</t>
      <section anchor="rate-signal">
        <name>Rate Signals</name>
        <t>A Rate Signal is a 7-bit unsigned integer (0-127). The high six bits are the
Rate Signal High Bits, and the least significant bit is the most significant
bit of the Version field.</t>
        <t>When sent by a QUIC endpoint, the Rate Signal is set to 127.  Receiving a value
of 127 indicates that throughput advice is unknown, either because network
elements on the path are not providing advice or they do not support SCONE. All
other values (0 through 126) represent the ceiling of rates advised by the
network element(s) on the path.</t>
        <t>Throughput advice follows a logarithmic scale defined as:</t>
        <ul spacing="normal">
          <li>
            <t>Base rate (b_min) = 100 kbit/s (100,000 bits per second)</t>
          </li>
          <li>
            <t>Bitrate at value n = b_min * 10^(n/20)</t>
          </li>
        </ul>
        <t>where n is an integer between 0 and 126 represented by the Rate Signal.</t>
        <t><xref target="ex-rates"/> lists some of the values for signals
and the corresponding bitrate for each.</t>
        <table anchor="ex-rates">
          <name>Examples of SCONE signals and corresponding rates</name>
          <thead>
            <tr>
              <th align="left">Bitrate</th>
              <th align="left">Rate Signal</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">100 kbit/s</td>
              <td align="left">0</td>
            </tr>
            <tr>
              <td align="left">112 kbit/s</td>
              <td align="left">1</td>
            </tr>
            <tr>
              <td align="left">126 kbit/s</td>
              <td align="left">2</td>
            </tr>
            <tr>
              <td align="left">141 kbit/s</td>
              <td align="left">3</td>
            </tr>
            <tr>
              <td align="left">1 Mbit/s</td>
              <td align="left">20</td>
            </tr>
            <tr>
              <td align="left">1.12 Mbit/s</td>
              <td align="left">21</td>
            </tr>
            <tr>
              <td align="left">10 Mbit/s</td>
              <td align="left">40</td>
            </tr>
            <tr>
              <td align="left">11.2 Mbit/s</td>
              <td align="left">41</td>
            </tr>
            <tr>
              <td align="left">100 Mbit/s</td>
              <td align="left">60</td>
            </tr>
            <tr>
              <td align="left">112 Mbit/s</td>
              <td align="left">61</td>
            </tr>
            <tr>
              <td align="left">1 Gbit/s</td>
              <td align="left">80</td>
            </tr>
            <tr>
              <td align="left">1.12 Gbit/s</td>
              <td align="left">81</td>
            </tr>
            <tr>
              <td align="left">10 Gbit/s</td>
              <td align="left">100</td>
            </tr>
            <tr>
              <td align="left">11.2 Gbit/s</td>
              <td align="left">101</td>
            </tr>
            <tr>
              <td align="left">100 Gbit/s</td>
              <td align="left">120</td>
            </tr>
            <tr>
              <td align="left">112 Gbit/s</td>
              <td align="left">121</td>
            </tr>
            <tr>
              <td align="left">199.5 Gbit/s</td>
              <td align="left">126</td>
            </tr>
            <tr>
              <td align="left">Unknown</td>
              <td align="left">127</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="time">
        <name>Monitoring Period</name>
        <t>The time over which throughput advice applies is defined to be
a period of 67 seconds.</t>
        <t>Protocol participants can use a different period,
depending on their role.
Senders can limit their send rate over any time period
up to 67 seconds.
Network elements can monitor and apply limits to send rates
using time period of at least 67 seconds.</t>
        <t>The choice of 67 seconds is a compromise between competing interests.
Longer periods allow applications more flexibility
in terms of how to allocate bandwidth over time.
Shorter periods allow networks to administer policies more tightly,
or react more quickly to changes in their capacity.
A shorter period also allows applications
to increase send rates sooner
when rates increase.</t>
        <t>The choice of 67 seconds, as a prime number,
also helps avoid synchronization with other periodic
effects that are commonly measured in whole seconds.
This includes segment length or key frame intervals in video applications,
but also includes timers for Network Address Translation (NAT) devices;
see <xref section="4.3" sectionFormat="of" target="RFC4787"/>.
Any repeating phenomenon at a 67-second interval is therefore
unlikely to be due to other periodic effects.</t>
      </section>
      <section anchor="recv-advice">
        <name>Endpoint Processing of SCONE Packets</name>
        <t>Processing a SCONE packet involves reading the value from the Rate Signal field.
However, throughput advice <bcp14>MUST</bcp14> be ignored
unless another packet from the same datagram is successfully processed.
A SCONE packet therefore always needs to be coalesced
with other QUIC packets;
see <xref target="off-path"/> for why this is necessary.</t>
        <t>What successful processing means depends on
the QUIC version associated with the coalesced packets,
but this minimally includes successfully authenticating the packet as valid.
SCONE packets <bcp14>MUST</bcp14> be ignored if the QUIC packets that follow
are discarded or ignored by the endpoint,
which especially includes packets that are discarded as potential duplicates.</t>
        <t>A SCONE packet is defined by the use of the long header bit (0x80 in the first
byte) and the SCONE protocol version (0x6f7dc0fd or 0xef7dc0fd in the next four
bytes). The 7-bit Rate Signal can be extracted by combining the low 6 bits
of the first byte with the most significant bit of the version field. A SCONE
packet <bcp14>MUST</bcp14> be discarded if the Destination Connection ID is not consistent with
those coalesced packets, as specified in <xref target="packet"/>. Similarly, if the Source
Connection ID is inconsistent, the SCONE packet <bcp14>MAY</bcp14> be discarded.</t>
        <t>When discarding a SCONE packet due to inconsistent Connection IDs, endpoints <bcp14>MAY</bcp14>
also discard the QUIC packets that were coalesced into the same datagram.</t>
        <t>A receiver <bcp14>MAY</bcp14> discard a datagram that contains more than one SCONE packet.
A receiver <bcp14>MUST</bcp14> discard a SCONE packet if the rate signal is unknown (127).</t>
        <t>If a connection uses multiple Differentiated Services Code Point (DSCP) markings <xref target="RFC2474"/>,
the throughput advice that is received on datagrams with one marking
might not apply to datagrams that have different markings.</t>
      </section>
      <section anchor="algorithm">
        <name>Following Throughput Advice</name>
        <t>Endpoints that receive throughput advice can advise their peer of the limit
so that the peer might limit the amount of data it sends
over any monitoring period (<xref target="time"/>).
Alternatively, the endpoint might change its own behavior
to effect a similar outcome indirectly,
which might use flow control or changes to request patterns.</t>
        <t>An endpoint that receives throughput advice
might receive multiple different values.
Where advice is reported to applications,
endpoints <bcp14>MUST</bcp14> report the lowest throughput advice
received during the previous monitoring period; see <xref target="time"/>.</t>
        <t>After a monitoring period (<xref target="time"/>)
without receiving any throughput advice,
the previous advice expires.
Endpoints can remove any constraints
that resulted from the expired throughput advice.
This does not mean that there are no limits,
either in policy or due to network conditions,
only that these limits are now unknown.
Other constraints on usage will still apply,
which necessarily includes congestion control
and might include other, application-specific constraints.</t>
        <t>Allowing advice to expire
ensures that changes in routing
do not cause stale advice to persist indefinitely
when network elements on a new path do not provide advice.</t>
        <t>This approach ensures that network elements
are able to reduce the frequency with which they send updated signals
to as low as once per monitoring period.
However, applying signals at a low frequency
risks endpoints discarding throughput advice
if no SCONE packet is available for providing updated advice (<xref target="apply"/>),
or packets carrying advice are lost.
Sending the signal multiple times
per monitoring period
increases the likelihood that the signal is received.</t>
      </section>
    </section>
    <section anchor="tp">
      <name>Negotiating SCONE</name>
      <t>A QUIC endpoint indicates that it is able to receive SCONE packets by
including the scone_supported transport parameter (0x219e).</t>
      <t>Each endpoint independently indicates willingness to receive SCONE packets.
An endpoint that does not include the scone_supported transport parameter
can send SCONE packets if their peer includes the transport parameter.</t>
      <t>The scone_supported transport parameter <bcp14>MUST</bcp14> be empty.
Receiving a non-zero-length scone_supported transport parameter <bcp14>MUST</bcp14> be treated
as a connection error of type TRANSPORT_PARAMETER_ERROR;
see <xref section="20.1" sectionFormat="of" target="QUIC"/>.</t>
      <!--
https://martinthomson.github.io/quic-pick/#seed=draft-ietf-scone-protocol-tp;field=tp;codepoint=0x219e;size=2
-->

<t>This transport parameter is valid for QUIC versions 1 <xref target="QUIC"/> and 2
<xref target="QUICv2"/> and any other version that recognizes the versions,
transport parameters, and frame types registries established in Sections <xref target="QUIC" section="22.2" sectionFormat="bare"/>, <xref target="QUIC" section="22.3" sectionFormat="bare"/>, and <xref target="QUIC" section="22.4" sectionFormat="bare"/> of <xref target="QUIC"/>.</t>
      <t>Endpoints <bcp14>MUST NOT</bcp14> remember whether the scone_supported transport parameter was present
on the previous connection when using 0-RTT;
see <xref section="7.4.1" sectionFormat="of" target="QUIC"/>.
That is, SCONE packets cannot be sent on a connection
until the transport parameter is received.</t>
      <section anchor="indication">
        <name>Indicating Support on New Flows</name>
        <t>All new flows that are initiated by a client that supports SCONE
<bcp14>MUST</bcp14> include bytes with values 0xc8 and 0x13
as the last two bytes of the payload of the UDP datagrams
that commence a new flow,
if the QUIC version in use permits the inclusion of data after packets.</t>
        <t>For example, in QUIC version 1,
these datagrams contain QUIC packets with a long header,
including a length prefix (<xref section="17.2" sectionFormat="of" target="QUIC"/>).
The UDP datagrams sent by a client can contain:
one or more QUIC version 1 Initial packets,
zero or more 0-RTT packets,
padding or other data that is discarded on receipt,
and the indication bytes (0xc8, 0x13) as the final bytes of the UDP payload.</t>
        <t>The SCONE indication bytes <bcp14>MUST</bcp14> be sent in every datagram
until the client receives any datagram from the server,
at which point the client can reasonably expect that the indication was received.</t>
        <!--
This indicator is derived from the first two bytes of:
https://martinthomson.github.io/quic-pick/#seed=draft-ietf-scone-protocol-indication;field=version;codepoint=0xc813e2b1
-->

<t>A client that uses a QUIC version that sends length-delimited packets during the handshake,
which includes QUIC versions 1 <xref target="QUIC"/> and 2 <xref target="QUICv2"/>,
can include an indicator of SCONE support
outside of the QUIC packets at the end of datagrams that start a flow.
The handshakes of these protocols ensures that
the indication can be included in every datagram the client sends
until it receives a response -- of any kind -- from the server.</t>
      </section>
      <section anchor="indicator-limits">
        <name>Limitations of Indication</name>
        <t>This indication does not mean that SCONE signals will be respected,
only that the client is able to negotiate SCONE.
A server might not support SCONE
and either endpoint might choose not to send SCONE packets.
Finally, applications might be unable to apply throughput advice
or choose to ignore it.</t>
        <t>There is a non-negligible risk of collision with other protocols
or even QUIC usage without SCONE indications.
The indicator is just two bytes,
which could be sent by chance on non-SCONE flows.
This means that the indication alone is not sufficient to indicate
that a flow is QUIC with the potential for SCONE support.</t>
        <t>Despite these limitations,
having an indication might allow network elements to change their starting posture
with respect to their enforcement of their rate limit policies.</t>
      </section>
      <section anchor="indications-for-migrated-flows">
        <name>Indications for Migrated Flows</name>
        <t>In QUIC version 1 and 2,
the two byte indicator (<xref target="indication"/>)
cannot be used on migration to a new path.</t>
        <t>Sending a SCONE packet for the first few packets on a new path
gives network elements on that path the ability
to recognize the flow as being able to receive throughput advice.
The SCONE packet also gives the network element an opportunity
to provide throughput advice for the new flow.</t>
        <t>To enable this indication,
even if an endpoint would not otherwise send SCONE packets,
endpoints can send a SCONE packet
any time they send a QUIC PATH_CHALLENGE or PATH_RESPONSE frame.
This applies to both client and server endpoints,
but only if the peer has sent the transport parameter; see <xref target="tp"/>.</t>
      </section>
      <section anchor="avoiding-ossification-when-reading-the-indicator">
        <name>Avoiding Ossification When Reading the Indicator</name>
        <t>A network element could classify all 5-tuples where the first observed UDP
datagram ends in the indicator bytes as potential SCONE.
However, this is not a strong indicator (see <xref target="indicator-limits"/>),
so network elements are encouraged to
apply further criteria to further reduce the set of flows that are identified
as potentially supporting SCONE to reduce the likelihood of false positives.
However, it <bcp14>SHOULD NOT</bcp14> apply criteria that reduce the ability of new QUIC
versions to employ SCONE. SCONE operates independently of any specific QUIC
version, so any criteria should consult the QUIC version invariants in
<xref target="INVARIANTS"/>.</t>
      </section>
    </section>
    <section anchor="network-deployment">
      <name>Network Deployment</name>
      <t>QUIC endpoints can enable the use of the SCONE protocol
by sending SCONE packets (<xref target="packet"/>).
Network elements can then update
the Rate Signal field (<xref target="apply"/>)
based on network policies or information about available capacity.</t>
      <section anchor="apply">
        <name>Applying Throughput Advice Signals</name>
        <t>A network element detects a SCONE packet by observing that a packet has a QUIC
long header and one of the SCONE protocol versions (0x6f7dc0fd or 0xef7dc0fd).</t>
        <t>A network element then conditionally replaces the most significant bit of the
Version field and the Rate Signal High Bits field with values of its choosing.</t>
        <t>A network element might receive a packet that already includes a rate signal.
The network element replaces the rate signal if it wishes to signal a lower
value for throughput advice;
otherwise, the original values are retained,
preserving the signal from the network element with the lower policy.
A network element <bcp14>MUST NOT</bcp14> replace a rate signal with a higher or unknown value.</t>
        <t>The following pseudocode indicates how a network element might detect a SCONE
packet and replace the existing rate signal (<tt>packet_signal</tt>) with a new rate
signal (<tt>target_signal</tt>) that encodes the throughput advice of this network
element.</t>
        <sourcecode type="pseudocode"><![CDATA[
is_long = (packet[0] & 0x80) == 0x80
packet_version = ntohl(packet[1:5])  # convert network to host endian
if is_long and ((packet_version & 0x7fffffff) == 0x6f7dc0fd):
  packet_signal = ((packet[0] & 0x3f) << 1) | (packet_version >> 31)
  if target_signal < packet_signal:
    packet[0] = (packet[0] & 0xc0) | (target_signal >> 1)
    packet[1] = (packet[1] & 0x7f) | ((target_signal & 1) << 7)
]]></sourcecode>
        <t>Once the throughput advice is updated,
the network element updates the UDP checksum for the datagram.
An incremental update process is described in <xref target="RFC1624"/>
and <xref section="8.1" sectionFormat="of" target="RFC8200"/> includes additional information relating to IPv6.</t>
        <section anchor="when-to-avoid-updating-throughput-advice">
          <name>When To Avoid Updating Throughput Advice</name>
          <t>A network element <bcp14>MUST NOT</bcp14> alter datagrams to add SCONE packets
or synthesize datagrams that contain SCONE packets.
The latter will not be accepted and the former,
even if they do not exceed the path MTU as a result,
can be detected by applications and could be ignored.
This document does not define a mechanism to support detection,
but one might be added in future.</t>
          <t>Network elements <bcp14>MUST</bcp14> only update the content of datagrams
on a given address tuple
a few times each monitoring period.
Network elements <bcp14>MAY</bcp14> update more often
immediately after a change in their throughput advice,
to reduce the reaction time from senders.
If too many datagrams are altered,
that could interfere with UDP protocols that are not QUIC;
see <xref target="other-protocols"/>.</t>
        </section>
        <section anchor="ensuring-throughput-advice-availability">
          <name>Ensuring Throughput Advice Availability</name>
          <t>To avoid throughput advice expiring,
a network element needs to ensure that it updates throughput advice in SCONE packets
with no more than a monitoring period (<xref target="time"/>) between each update.
Because this depends on the availability of SCONE packets
and packet loss can cause signals to be missed,
network elements might need to update more often.
Ideally, network elements update advice in SCONE packets
at least twice per monitoring period,
to match endpoint behavior (see <xref target="extra-packets"/>).</t>
          <t>At the start of a flow, network elements are encouraged to update the rate
signal of the first few SCONE packets it observes so that endpoints can obtain
throughput advice early.</t>
          <t>Senders that send a SCONE packet
or network elements that update SCONE packets
every 20–30 seconds are likely sufficient to ensure that throughput advice is not lost.
To reduce the risk of synchronization across multiple senders,
which could cause network elements to miss updates,
senders can include a small random delay.</t>
        </section>
      </section>
      <section anchor="monitoring">
        <name>Monitoring Flows</name>
        <t>Providing throughput advice is optional for any network.
A network that updates SCONE packets to provide throughput advice might,
also optionally, choose to monitor flows
to determine whether applications are following advice.</t>
        <t>This section outlines a method
that a network element could use
to determine whether a flow exceeds the value from provided throughput advice.
Network deployments that choose to monitor
are free to follow any monitoring regime that suits their needs.</t>
        <t>This documented approach to monitoring is largely illustrative;
there is no interoperability impact
from choosing an alternative approach.
However, monitoring any more strictly than the following
could mean that an application
might be incorrectly classified as not following advice.
A looser monitoring approach,
such as monitoring over a longer time window
than the monitoring period (67s)
or using a higher rate than is signaled,
has no risk of incorrect classification.</t>
        <t>When a network changes the throughput advice
it intends to provide,
applications need time to adjust their sending behavior.
As a result, any monitoring needs to allow time
for SCONE packets to be updated,
for those packets to be received by endpoints,
and for applications to adapt.</t>
        <t>A network element can then monitor affected flows
to determine whether the provided throughput advice
was followed.</t>
        <t>The simplest monitoring approach bases monitoring
on the maximum value
that the network element was configured to apply to SCONE packets
during the preceding two monitoring periods.
This allows an additional monitoring period
to compensate for additional delays
as SCONE packets are not delivered reliably.
Relative to an additional monitoring period,
other delays in propagating throughput advice
are expected to be negligible.
If the network element cannot update the throughput advice in every SCONE packet
(or can only do so periodically), a longer period might be used.</t>
        <section anchor="deployment-of-monitoring-functions">
          <name>Deployment of Monitoring Functions</name>
          <t>Any monitoring and policy enforcement could be implemented
in different network elements than the ones that signal throughput advice.
This enables more flexible allocation of responsibilities
between nodes in the same administrative domain.</t>
          <t>SCONE packets can cross administrative boundaries,
which means that network elements might observe throughput advice
on SCONE packets that have transited other networks.
A network element <bcp14>MUST NOT</bcp14> enforce throughput limits
based on throughput advice that is observed in SCONE packets
received from other entities.
Any enforcement action needs to be the result of configuration
or other authorized administrative action,
not unauthenticated network signals.
Unlike endpoints,
network elements do not have the capability to validate other QUIC packets
contained in the same datagram; see <xref target="fake-packets"/>.</t>
        </section>
        <section anchor="policing">
          <name>Flows That Exceed Throughput Advice</name>
          <t>A network could deploy policy enforcement that drops or delays packets
to ensure that applications do not exceed throughput limits set in policy.</t>
          <t>SCONE allows networks to provide advice to applications,
so that there is less need to enforce throughput limits on flows.
Strict enforcement through dropping or delaying packets
can be inefficient
and lead to poor application performance.</t>
          <t>Some applications will not support SCONE.
Other applications either will not
or cannot
follow throughput advice.</t>
          <t>Networks can monitor flows to determine if applications follow advice;
see <xref target="monitoring"/>.
A network could choose to either disable or loosen policy enforcement
for flows where SCONE is active,
but re-enable or tighten enforcement if monitoring indicates
that throughput advice is not being respected.</t>
        </section>
      </section>
    </section>
    <section anchor="endpoint-usage">
      <name>Endpoint Usage</name>
      <t>The SCONE protocol defines two versions (0x6f7dc0fd and 0xef7dc0fd)
that combined carry throughput advice that covers a range of bitrates
between 100 kbit/s and 199.5 Gbit/s.</t>
      <section anchor="extra-packets">
        <name>Providing Opportunities to Apply Throughput Advice Signals</name>
        <t>Endpoints that wish to offer network elements the option to provide throughput advice
signals can send SCONE packets at any time.  This is a decision that a sender
makes when constructing datagrams.</t>
        <t>As specified in <xref target="packet"/>, endpoints include a SCONE packet as the first
packet in a datagram, coalesced with additional packets.</t>
        <t>Upon confirmation that the peer is willing to receive SCONE packets, an endpoint
<bcp14>SHOULD</bcp14> include SCONE packets in the first few UDP datagrams that it sends. Doing
so increases the likelihood of eliciting early throughput advice from network
elements, allowing applications to apply that advice from the early stages of the
data transfer.</t>
        <t>After that, endpoints that seek to receive throughput advice on a flow <bcp14>MUST</bcp14> send
a SCONE packet at least twice each monitoring period; see <xref target="time"/>.</t>
        <t>Sending SCONE packets more often might be necessary to:</t>
        <dl>
          <dt>Avoid missing advice:</dt>
          <dd>
            <t>If SCONE packets are not sent, updated, and received
for an entire monitoring period,
an application might assume that no throughput advice is being provided.</t>
          </dd>
          <dt>Reduce latency:</dt>
          <dd>
            <t>The time between SCONE packets determines the maximum delay
between changes in throughput advice
and when that advice can be received and acted upon.</t>
          </dd>
        </dl>
        <t>A sender can track the receipt of the coalesced QUIC packet
and send another SCONE packet when loss is detected.
However, it is likely simpler to send SCONE packets more often.</t>
        <t>Sending a SCONE packet every 20–30 seconds
is likely sufficient to ensure that throughput advice is not lost,
though endpoints might send a packet every few seconds
to improve responsiveness.
This period could be determined by how quickly an application
is able to respond to a change in throughput advice.</t>
        <t>For example, a streaming application
that fetches video segments that are 5 seconds in length
might send SCONE packets on a similar cadence.
A real-time conferencing application might send more often.
In either case, the length of the monitoring period (<xref target="time"/>)
limits how fast any application can react.</t>
        <t>Though sending SCONE packets more than once each round trip time
might help reduce exposure to packet loss,
it is better to spread updates over time
rather than to send multiple SCONE packets in less frequent bursts.</t>
        <t>The main cost associated with sending SCONE packets
is the reduction in available space in datagrams
for application data.</t>
        <t>A sender <bcp14>MUST NOT</bcp14> send a SCONE packet
unless a QUIC packet needs to be sent for other reasons.
It is safe to allow throughput advice to lapse
if the connection is otherwise idle,
whereas induced activity wastes resources
by keeping connections alive unnecessarily.</t>
        <t>A network element that wishes to signal updated throughput advice waits for the
next SCONE packet in the desired direction; see <xref target="apply"/>.</t>
      </section>
      <section anchor="feedback">
        <name>Feedback To Sender About Signals</name>
        <t>Information about throughput advice is intended for the sending application.  Any
signal from network elements can be propagated to the receiving application
using an implementation-defined mechanism.</t>
        <t>This document does not define a means for indicating what was received.
The expectation is that any signal is propagated to the application
for handling, rather than being handled automatically by the transport layer.
How a receiving application communicates throughput advice to a
sending application will depend on the application in use.</t>
        <t>Different applications can choose different approaches. For example,
in an application where a receiver drives rate adaptation, it might
not be necessary to define additional signaling.</t>
        <t>A sender can use any acknowledgment mechanism provided by the QUIC version in
use to learn whether datagrams containing SCONE packets were likely received.
This might help inform whether to send additional SCONE packets in the event
that a datagram is lost.  For instance, if a UDP datagram carrying both a
SCONE packet and an ack-eliciting QUIC packet is acknowledged, the sender
knows the SCONE packet was also received.  However, rather than relying
solely on transport-layer acknowledgments, an application-layer mechanism
might better indicate what has been received and acted upon.</t>
        <t>SCONE packets could be stripped from datagrams in the network, which cannot be
reliably detected.  This could result in a sender falsely believing that no
network element applied throughput advice.
Senders will therefore proceed as though there was no advice.</t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>SCONE throughput advice is not authenticated.  Throughput advice
might be incorrectly set in order to encourage endpoints to behave in ways that
are not in their interests.  Endpoints can ignore limits,
though that can have consequences; see <xref target="policing"/>.
The congestion controller employed by a sender provides
real-time information about the rate at which the network path is delivering
data.</t>
      <t>Similarly, if there is a strong need to ensure that throughput advice is respected,
network elements cannot assume that the signaled advice will be respected by
endpoints.</t>
      <section anchor="off-path">
        <name>Off-Path Adversaries</name>
        <t>The modification of packets provides endpoints proof that a network element is
in a position to drop datagrams and could apply a rate limit policy.
<xref target="recv-advice"/> states that endpoints only accept signals if the datagram
contains a packet that it accepts to prevent an off-path attacker from inserting
spurious throughput advice.</t>
        <t>Some off-path attackers could be able to both
observe traffic and inject packets. Attackers with such capabilities could
observe packets sent by an endpoint, create datagrams coalescing an
arbitrary SCONE packet and the observed packet, and send these datagrams
such that they arrive at the peer endpoint before the original
packet. Spoofed packets that seek to advertise a higher limit
than might otherwise be permitted also need to bypass any
rate limiters. The attacker will thus get arbitrary SCONE packets accepted by
the peer, with the result being that the endpoint receives a false
or misleading rate limit.</t>
        <t>The recipient of throughput advice therefore cannot guarantee that
the signal was not generated by an on-path network element.</t>
        <t>The capabilities required of an off-path attacker are substantially
similar to those of on-path elements.
An off-path attacker can generate throughput advice
that will be accepted by an endpoint
if it has the ability to damage packets
in a way that could be able to affect throughput capacity of the flow.
The one exception is an off-path attacker
that is only capable of generating spoofed copies of packets
with modified throughput rates
that reach endpoints ahead of the original.</t>
      </section>
      <section anchor="fake-packets">
        <name>Fake SCONE Packets</name>
        <t>Attackers that can inject packets could compose arbitrary "SCONE-like" packets
by selecting a pair of IP addresses and ports, an arbitrary rate signal, a
valid SCONE version number, an arbitrary "destination
connection ID", and an arbitrary "source connection ID".
A coalesced "1RTT" packet will start with
a plausible first octet, and continue with the selected destination connection
ID followed by a sufficiently long series of random bytes, mimicking the
content of an encrypted packet.</t>
        <t>Endpoints will reject such packets because they do not contain valid QUIC packets,
but network elements cannot detect this.
All the network elements between the injection point and the destination
will have to process these packets.</t>
        <t>Attackers could send a high volume of these "fake" SCONE packets in
a denial of service (DOS) attempt against network elements. The attack will
force the intermediaries to process the fake packets. If network elements
are keeping state for ongoing SCONE flows, this might exhaust memory resources.
The mitigation is the same as for other distributed DOS attacks: limit
the rate of SCONE packets that a network element is willing to process;
possibly, implement logic to distinguish valid SCONE packets from
fake packets; or, use generic protection against Distributed DOS attacks.</t>
        <t>Attackers could also try to craft the fake SCONE packets in ways that trigger
a processing error at network elements. For example, they might pick connection
identifiers of arbitrary length. Network elements can mitigate these attacks
with an implementation that fully conforms to the specification of <xref target="packet"/>.</t>
      </section>
      <section anchor="other-protocols">
        <name>Damage to Other Protocols</name>
        <t>Network elements that update SCONE packet fields might do that for datagrams
exchanged in other protocols.
If the first five bytes of the datagram match
the QUIC long header byte and SCONE version,
the network element might modify the signal,
resulting in damage to those protocols.</t>
        <t>The most serious damage occurs when every datagram matches
and is subsequently modified,
because that could mean that the protocol is
effectively unable to operate end-to-end.</t>
        <t>To avoid unrecoverable damage to non-QUIC protocols,
network elements only update a limited number of datagrams
in each monitoring period; see <xref target="apply"/>.</t>
        <t>In addition, some heuristics might be used
to detect SCONE-compatible QUIC flows.
This includes identification of a QUIC handshake on the flow,
the presence of indications (<xref target="indication"/>),
or other heuristics.
If these heuristics indicate a non-QUIC flow,
the safest option is
for network elements to disable updating of datagrams.</t>
      </section>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>The focus of this analysis is the extent to which observing SCONE
packets could be used to gain information about endpoints.
This might be leaking details of how applications using QUIC
operate or leaks of endpoint identity when using additional
privacy protection, such as a VPN.</t>
      <t>Any network element that can observe the content of that packet can read the
throughput advice that was applied.  Any signal is visible on the path, from the point
at which it is applied to the point at which it is consumed at an endpoint.
On path elements can also alter the SCONE signal to try trigger specific
reactions and gain further knowledge.</t>
      <t>In the general case of a client connected to a server through the
Internet, SCONE does not provide much advantage to attackers.
The identities of the clients and servers are already visible through their
IP addresses. Traffic analysis tools already provide more information than
the throughput advice set by SCONE.</t>
      <t>There are two avenues of attack that require more analysis:</t>
      <ul spacing="normal">
        <li>
          <t>that the passive observation of SCONE packets might help identify or
distinguish endpoints; and</t>
        </li>
        <li>
          <t>that active manipulation of SCONE signals might help reveal the
identity of endpoints that are otherwise hidden behind VPNs or proxies.</t>
        </li>
      </ul>
      <section anchor="passive-attacks">
        <name>Passive Attacks</name>
        <t>If only a few clients and server pairs negotiate the usage of SCONE, the
occasional observation of SCONE packets will "stick out". That observation
could be combined with observation of timing and volume of traffic to
help identify the endpoint or categorize the application that they
are using.</t>
        <t>A variation of this issue occurs if SCONE is widely implemented, but
only used in some specific circumstances. In that case, observation of
SCONE packets reveals information about the state of the endpoint.</t>
        <t>If multiple servers are accessed through the same front facing server,
Encrypted Client Hello (ECH) can prevent outside parties from
identifying which specific server a client is using. However, if only
a few of these servers use SCONE, any SCONE packets
will help identify which specific server a client is using.</t>
        <t>This issue will be mitigated if SCONE becomes widely implemented, and
if the usage of SCONE is not limited to the type of applications
that make active use of the signal.</t>
        <t>QUIC implementations are therefore encouraged to make the feature available
unconditionally.  Endpoints might send SCONE packets whenever a peer can accept
them.</t>
      </section>
      <section anchor="active-attacks">
        <name>Active Attacks</name>
        <t>Suppose a configuration in which multiple clients use a VPN or proxy
service to access the same server. The attacker sees the IP addresses
in the packets behind VPN and proxy and also between the users and the VPN,
but it does not know which VPN address corresponds to what user address.</t>
        <t>Suppose now that the attacker selects a flow on the link between the
VPN/proxy and server. The attacker applies throughput advice to SCONE packets
in that flow. The attacker chooses a bandwidth that is
lower than the "natural" bandwidth of the connection. A reduction
in the rate of flows between client and VPN/proxy might allow
the attacker to link the altered flow to the client.</t>
        <figure anchor="f-vpn">
          <name>Client identification attack on VPN or proxy</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="256" width="472" viewBox="0 0 472 256" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 8,128" fill="none" stroke="black"/>
                <path d="M 8,160 L 8,192" fill="none" stroke="black"/>
                <path d="M 80,32 L 80,64" fill="none" stroke="black"/>
                <path d="M 80,96 L 80,128" fill="none" stroke="black"/>
                <path d="M 80,160 L 80,192" fill="none" stroke="black"/>
                <path d="M 200,64 L 200,160" fill="none" stroke="black"/>
                <path d="M 264,64 L 264,160" fill="none" stroke="black"/>
                <path d="M 312,144 L 312,176" fill="none" stroke="black"/>
                <path d="M 368,80 L 368,144" fill="none" stroke="black"/>
                <path d="M 440,80 L 440,144" fill="none" stroke="black"/>
                <path d="M 8,32 L 80,32" fill="none" stroke="black"/>
                <path d="M 88,48 L 136,48" fill="none" stroke="black"/>
                <path d="M 8,64 L 80,64" fill="none" stroke="black"/>
                <path d="M 200,64 L 264,64" fill="none" stroke="black"/>
                <path d="M 152,80 L 192,80" fill="none" stroke="black"/>
                <path d="M 368,80 L 440,80" fill="none" stroke="black"/>
                <path d="M 8,96 L 80,96" fill="none" stroke="black"/>
                <path d="M 272,94 L 360,94" fill="none" stroke="black"/>
                <path d="M 272,98 L 360,98" fill="none" stroke="black"/>
                <path d="M 88,112 L 192,112" fill="none" stroke="black"/>
                <path d="M 272,110 L 360,110" fill="none" stroke="black"/>
                <path d="M 272,114 L 360,114" fill="none" stroke="black"/>
                <path d="M 8,128 L 80,128" fill="none" stroke="black"/>
                <path d="M 272,126 L 360,126" fill="none" stroke="black"/>
                <path d="M 272,130 L 360,130" fill="none" stroke="black"/>
                <path d="M 152,144 L 192,144" fill="none" stroke="black"/>
                <path d="M 368,144 L 440,144" fill="none" stroke="black"/>
                <path d="M 8,160 L 80,160" fill="none" stroke="black"/>
                <path d="M 200,160 L 264,160" fill="none" stroke="black"/>
                <path d="M 88,174 L 136,174" fill="none" stroke="black"/>
                <path d="M 88,178 L 136,178" fill="none" stroke="black"/>
                <path d="M 8,192 L 80,192" fill="none" stroke="black"/>
                <path d="M 136,192 L 152,224" fill="none" stroke="black"/>
                <path d="M 136,48 L 152,80" fill="none" stroke="black"/>
                <path d="M 136,176 L 152,144" fill="none" stroke="black"/>
                <polygon class="arrowhead" points="368,128 356,122.4 356,133.6" fill="black" transform="rotate(0,360,128)"/>
                <polygon class="arrowhead" points="368,112 356,106.4 356,117.6" fill="black" transform="rotate(0,360,112)"/>
                <polygon class="arrowhead" points="368,96 356,90.4 356,101.6" fill="black" transform="rotate(0,360,96)"/>
                <polygon class="arrowhead" points="320,144 308,138.4 308,149.6" fill="black" transform="rotate(270,312,144)"/>
                <polygon class="arrowhead" points="280,128 268,122.4 268,133.6" fill="black" transform="rotate(180,272,128)"/>
                <polygon class="arrowhead" points="280,112 268,106.4 268,117.6" fill="black" transform="rotate(180,272,112)"/>
                <polygon class="arrowhead" points="280,96 268,90.4 268,101.6" fill="black" transform="rotate(180,272,96)"/>
                <polygon class="arrowhead" points="200,144 188,138.4 188,149.6" fill="black" transform="rotate(0,192,144)"/>
                <polygon class="arrowhead" points="200,112 188,106.4 188,117.6" fill="black" transform="rotate(0,192,112)"/>
                <polygon class="arrowhead" points="200,80 188,74.4 188,85.6" fill="black" transform="rotate(0,192,80)"/>
                <polygon class="arrowhead" points="144,192 132,186.4 132,197.6" fill="black" transform="rotate(243.43494882292202,136,192)"/>
                <g class="text">
                  <text x="44" y="52">Client</text>
                  <text x="232" y="100">VPN</text>
                  <text x="44" y="116">Client</text>
                  <text x="232" y="116">/</text>
                  <text x="404" y="116">Server</text>
                  <text x="232" y="132">Proxy</text>
                  <text x="44" y="180">Client</text>
                  <text x="248" y="196">Apply</text>
                  <text x="316" y="196">throughput</text>
                  <text x="388" y="196">advice</text>
                  <text x="444" y="196">signal</text>
                  <text x="152" y="244">Observe</text>
                  <text x="212" y="244">change</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
+--------+
| Client |------.
+--------+       \      +-------+
                  '---->|       |            +--------+
+--------+              |  VPN  |<==========>|        |
| Client |------------->|   /   |<==========>| Server |
+--------+              | Proxy |<==========>|        |
                  .---->|       |     ^      +--------+
+--------+       /      +-------+     |
| Client |======'                     |
+--------+      ^           Apply throughput advice signal
                 \
                  \
               Observe change
]]></artwork>
          </artset>
        </figure>
        <t>An attacker that can manipulate SCONE headers might
cause an observable change in sending behavior; see <xref target="f-vpn"/>.
Though clients that use a VPN or proxy might choose to disable SCONE,
removing SCONE signals is of little help against this form of attack.
Lost or ECN-marked packets are likely to produce a congestion control response,
which are alternative methods available to an attacker
seeking to match flows.</t>
        <t>An effective, but wasteful, defense is to provide cover traffic
between the client and intermediary
to mask changes in sending rate on tunneled flows.</t>
      </section>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document registers new QUIC versions (<xref target="iana-version"/>) and a QUIC
transport parameter (<xref target="iana-tp"/>).</t>
      <section anchor="iana-version">
        <name>SCONE Versions</name>
        <t>This document registers the following entries to the "QUIC Versions" registry
maintained at <eref target="https://www.iana.org/assignments/quic">https://www.iana.org/assignments/quic</eref>, following the guidance
from <xref section="22.2" sectionFormat="of" target="QUIC"/>.</t>
        <dl spacing="compact">
          <dt>Value:</dt>
          <dd>
            <t>0x6f7dc0fd</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>permanent</t>
          </dd>
          <dt>Specification:</dt>
          <dd>
            <t>This document</t>
          </dd>
          <dt>Change Controller:</dt>
          <dd>
            <t>IETF (iesg@ietf.org)</t>
          </dd>
          <dt>Contact:</dt>
          <dd>
            <t>QUIC Working Group (quic@ietf.org)</t>
          </dd>
          <dt>Notes:</dt>
          <dd>
            <t>SCONE Protocol - Even Signal Values</t>
          </dd>
        </dl>
        <dl spacing="compact">
          <dt>Value:</dt>
          <dd>
            <t>0xef7dc0fd</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>permanent</t>
          </dd>
          <dt>Specification:</dt>
          <dd>
            <t>This document</t>
          </dd>
          <dt>Change Controller:</dt>
          <dd>
            <t>IETF (iesg@ietf.org)</t>
          </dd>
          <dt>Contact:</dt>
          <dd>
            <t>QUIC Working Group (quic@ietf.org)</t>
          </dd>
          <dt>Notes:</dt>
          <dd>
            <t>SCONE Protocol - Odd Signal Values</t>
          </dd>
        </dl>
      </section>
      <section anchor="iana-tp">
        <name>scone_supported Transport Parameter</name>
        <t>This document registers the scone_supported transport parameter in the "QUIC
Transport Parameters" registry maintained at
<eref target="https://www.iana.org/assignments/quic">https://www.iana.org/assignments/quic</eref>, following the guidance from <xref section="22.3" sectionFormat="of" target="QUIC"/>.</t>
        <dl spacing="compact">
          <dt>Value:</dt>
          <dd>
            <t>0x219e</t>
          </dd>
          <dt>Parameter Name:</dt>
          <dd>
            <t>scone_supported</t>
          </dd>
          <dt>Status:</dt>
          <dd>
            <t>Permanent</t>
          </dd>
          <dt>Specification:</dt>
          <dd>
            <t>This document</t>
          </dd>
          <dt>Change Controller:</dt>
          <dd>
            <t>IETF (iesg@ietf.org)</t>
          </dd>
          <dt>Contact:</dt>
          <dd>
            <t>QUIC Working Group (quic@ietf.org)</t>
          </dd>
          <dt>Notes:</dt>
          <dd>
            <t>(none)</t>
          </dd>
        </dl>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="QUIC">
          <front>
            <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
            <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9000"/>
          <seriesInfo name="DOI" value="10.17487/RFC9000"/>
        </reference>
        <reference anchor="INVARIANTS">
          <front>
            <title>Version-Independent Properties of QUIC</title>
            <author fullname="M. Thomson" initials="M." surname="Thomson"/>
            <date month="May" year="2021"/>
            <abstract>
              <t>This document defines the properties of the QUIC transport protocol that are common to all versions of the protocol.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8999"/>
          <seriesInfo name="DOI" value="10.17487/RFC8999"/>
        </reference>
        <referencegroup anchor="BCP14" target="https://www.rfc-editor.org/info/bcp14">
          <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="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>
        </referencegroup>
        <reference anchor="QUIC-BIT">
          <front>
            <title>Greasing the QUIC Bit</title>
            <author fullname="M. Thomson" initials="M." surname="Thomson"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>This document describes a method for negotiating the ability to send an arbitrary value for the second-most significant bit in QUIC packets.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9287"/>
          <seriesInfo name="DOI" value="10.17487/RFC9287"/>
        </reference>
        <reference anchor="QUICv2">
          <front>
            <title>QUIC Version 2</title>
            <author fullname="M. Duke" initials="M." surname="Duke"/>
            <date month="May" year="2023"/>
            <abstract>
              <t>This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC.</t>
              <t>Note that "version 2" is an informal name for this proposal that indicates it is the second version of QUIC to be published as a Standards Track document. The protocol specified here uses a version number other than 2 in the wire image, in order to minimize ossification risks.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9369"/>
          <seriesInfo name="DOI" value="10.17487/RFC9369"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="DASH" target="https://www.iso.org/standard/83314.html">
          <front>
            <title>Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats</title>
            <author>
              <organization/>
            </author>
            <date year="2022" month="August"/>
          </front>
          <seriesInfo name="ISO/IEC" value="23009-1:2022"/>
        </reference>
        <reference anchor="ECN">
          <front>
            <title>The Addition of Explicit Congestion Notification (ECN) to IP</title>
            <author fullname="K. Ramakrishnan" initials="K." surname="Ramakrishnan"/>
            <author fullname="S. Floyd" initials="S." surname="Floyd"/>
            <author fullname="D. Black" initials="D." surname="Black"/>
            <date month="September" year="2001"/>
            <abstract>
              <t>This memo specifies the incorporation of ECN (Explicit Congestion Notification) to TCP and IP, including ECN's use of two bits in the IP header. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3168"/>
          <seriesInfo name="DOI" value="10.17487/RFC3168"/>
        </reference>
        <reference anchor="QUIC-MP">
          <front>
            <title>Managing multiple paths for a QUIC connection</title>
            <author fullname="Yanmei Liu" initials="Y." surname="Liu">
              <organization>Alibaba Inc.</organization>
            </author>
            <author fullname="Yunfei Ma" initials="Y." surname="Ma">
              <organization>Uber Technologies Inc.</organization>
            </author>
            <author fullname="Quentin De Coninck" initials="Q." surname="De Coninck">
              <organization>University of Mons (UMONS)</organization>
            </author>
            <author fullname="Olivier Bonaventure" initials="O." surname="Bonaventure">
              <organization>UCLouvain and WELRI</organization>
            </author>
            <author fullname="Christian Huitema" initials="C." surname="Huitema">
              <organization>Private Octopus Inc.</organization>
            </author>
            <author fullname="Mirja Kühlewind" initials="M." surname="Kühlewind">
              <organization>Ericsson</organization>
            </author>
            <date day="17" month="March" year="2026"/>
            <abstract>
              <t>   This document specifies a multipath extension for the QUIC protocol
   to enable the simultaneous usage of multiple paths for a single
   connection.  It introduces explicit path identifiers to create,
   delete, and manage multiple paths.  This document does not specify
   address discovery or management, nor how applications using QUIC
   schedule traffic over multiple paths.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-quic-multipath-21"/>
        </reference>
        <reference anchor="SCONE-MAN">
          <front>
            <title>Manageability Considerations for SCONE</title>
            <author fullname="Sanjay Mishra" initials="S." surname="Mishra">
              <organization>Verizon</organization>
            </author>
            <author fullname="Zaheduzzaman Sarker" initials="Z." surname="Sarker">
              <organization>Nokia</organization>
            </author>
            <author fullname="Anoop Tomar" initials="A." surname="Tomar">
              <organization>Meta</organization>
            </author>
            <author fullname="Khurram Abbas" initials="K." surname="Abbas">
              <organization>Verizon</organization>
            </author>
            <date day="28" month="October" year="2026"/>
            <abstract>
              <t>   This document describes the manageability considerations for network
   operators for providing throughput advice to application endpoints.
   This guidance is specifically addressed within the context of
   communication networks utilizing the Standard Communication with
   Network Elements (SCONE) protocol [SCONE].

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-scone-applicability-manageability-03"/>
        </reference>
        <reference anchor="WHY-ECN">
          <front>
            <title>The Benefits of Using Explicit Congestion Notification (ECN)</title>
            <author fullname="G. Fairhurst" initials="G." surname="Fairhurst"/>
            <author fullname="M. Welzl" initials="M." surname="Welzl"/>
            <date month="March" year="2017"/>
            <abstract>
              <t>The goal of this document is to describe the potential benefits of applications using a transport that enables Explicit Congestion Notification (ECN). The document outlines the principal gains in terms of increased throughput, reduced delay, and other benefits when ECN is used over a network path that includes equipment that supports Congestion Experienced (CE) marking. It also discusses challenges for successful deployment of ECN. It does not propose new algorithms to use ECN nor does it describe the details of implementation of ECN in endpoint devices (Internet hosts), routers, or other network devices.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8087"/>
          <seriesInfo name="DOI" value="10.17487/RFC8087"/>
        </reference>
        <reference anchor="CONNECT-UDP">
          <front>
            <title>Proxying UDP in HTTP</title>
            <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>This document describes how to proxy UDP in HTTP, similar to how the HTTP CONNECT method allows proxying TCP in HTTP. More specifically, this document defines a protocol that allows an HTTP client to create a tunnel for UDP communications through an HTTP server that acts as a proxy.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9298"/>
          <seriesInfo name="DOI" value="10.17487/RFC9298"/>
        </reference>
        <reference anchor="HLS">
          <front>
            <title>HTTP Live Streaming</title>
            <author fullname="R. Pantos" initials="R." role="editor" surname="Pantos"/>
            <author fullname="W. May" initials="W." surname="May"/>
            <date month="August" year="2017"/>
            <abstract>
              <t>This document describes a protocol for transferring unbounded streams of multimedia data. It specifies the data format of the files and the actions to be taken by the server (sender) and the clients (receivers) of the streams. It describes version 7 of this protocol.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8216"/>
          <seriesInfo name="DOI" value="10.17487/RFC8216"/>
        </reference>
        <reference anchor="RFC4787">
          <front>
            <title>Network Address Translation (NAT) Behavioral Requirements for Unicast UDP</title>
            <author fullname="F. Audet" initials="F." role="editor" surname="Audet"/>
            <author fullname="C. Jennings" initials="C." surname="Jennings"/>
            <date month="January" year="2007"/>
            <abstract>
              <t>This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. 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="127"/>
          <seriesInfo name="RFC" value="4787"/>
          <seriesInfo name="DOI" value="10.17487/RFC4787"/>
        </reference>
        <reference anchor="RFC2474">
          <front>
            <title>Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers</title>
            <author fullname="K. Nichols" initials="K." surname="Nichols"/>
            <author fullname="S. Blake" initials="S." surname="Blake"/>
            <author fullname="F. Baker" initials="F." surname="Baker"/>
            <author fullname="D. Black" initials="D." surname="Black"/>
            <date month="December" year="1998"/>
            <abstract>
              <t>This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2474"/>
          <seriesInfo name="DOI" value="10.17487/RFC2474"/>
        </reference>
        <reference anchor="RFC1624">
          <front>
            <title>Computation of the Internet Checksum via Incremental Update</title>
            <author fullname="A. Rijsinghani" initials="A." role="editor" surname="Rijsinghani"/>
            <date month="May" year="1994"/>
            <abstract>
              <t>This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1624"/>
          <seriesInfo name="DOI" value="10.17487/RFC1624"/>
        </reference>
        <reference anchor="RFC8200">
          <front>
            <title>Internet Protocol, Version 6 (IPv6) Specification</title>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="July" year="2017"/>
            <abstract>
              <t>This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="86"/>
          <seriesInfo name="RFC" value="8200"/>
          <seriesInfo name="DOI" value="10.17487/RFC8200"/>
        </reference>
      </references>
    </references>
    <?line 1305?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t><contact fullname="Jana Iyengar"/> made significant contributions to the original TRAIN
specification that forms the basis for a large part of this document.
The following people also contributed significantly
to the development of the protocol: <contact fullname="Alan Frindell"/>,
<contact fullname="Andrew Yourtchenko"/>, <contact fullname="Gorry Fairhurst"/>, <contact fullname="Ionuț Mihalcea"/>,
<contact fullname="Kevin Smith"/>, <contact fullname="Martin Duke"/>, and <contact fullname="Zaheduzzaman Sarker"/>.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9V9y3IcWXre/jxFCh0hAeqqIgBySDa62TMYEmxCapIwgZ6J
sTRqZVWdQuUgK7OUJwtgNQmFws/gnTfeaOE38NorP4fDDr+G/+u5ZGahW7IW
dodCQ1Rmnut//sv3X854PDZt0Zb2JNu7bPNqnjfz7GW9Wm2qYpa3RV1ld0W7
zN7Z9q5ubrKz0q5s1bps//Ll+3dnB9lFU7f1rC73TD6dNvYW28En0QNox17X
zfYkc+3cmHk9q/IVdDhv8kU7Lmy7GLtZXdnxWj4ZHx0Zt5muCudgAO12DS+f
n129NtVmNbXNiZlDiycGvnG2cht3krXNxhro+7HJG5vDGH5vpxnMJjuvWttU
ts2umrxy67pp9wxO5LqpN+uTjIZqbuwWfpufmGyclTCAVd0Wtxb/Wueubbbm
1lYb6DDL5DOe4h78wIPb+z00WVTX2Xf4HH9f5UUJv9O8foNTnNTNNT7Im9kS
Hizbdu1OHj3C9/An6G+irz3CHx5Nm/rO2UfUwiP88hr2YTOFb2nF7q550fgF
fF7Corg2ajt5b8KfT4pamty5+pNlu4JdM/mmXdYNLgo0nmWLTVnyvr3Nm7ao
sqtlvXJ1RQ9h1HlV/EQEAy/UPxVlmdMTyyuxan9T1ndAOU293k5gQ/rNvlw2
hWuLvMrebIoWvtOWT4CWiluYXfZ+1tbrjYNdnU3i1pf8wW/kfwfbp7+y7OQk
+1///M/Z//yv//S//8t/kN9yNyuKk+yv8582yzp7f7MJPb8GAii3cV839FZ9
s/nNNf4wAXIZWqK2zf6qbnIXmnpr23RJ4J3Jn/Cdh1tqZjjjJZBJaOusKWZO
F9+3h29OCnzzN1ZeoEaNqeoGugMiw2X4dz+cvzzJPrx++dXh4SH8ff7ud6cf
zk/fXV3Sr8+/+uorY4pqEX/z6vTyDS+hcotzfQFYRGtny6ou6+tt9j/+6T9m
r7Yw9mKW5fN8jQ3AuYdTucIDUt/aJntzdXWR7WOTB/T+BRBUdoQrNC/ybN1Y
ONYttzy3btYUa/o3nmdnr5H/ZNy32+Mh5c21BcpXwr+7u5sUrqaz5ISpPXr+
+PHRE6Jt+sbBClmHs1TKOL98/+j8DFbm+PHh4Vfjo5Pjw+NjekbsJsM/x4fP
jRmPx1k+hTnls9aYq2XhMuBpGxoXj3dqXYYT4QOV3S1tY7O6Gq9zYKWVsFIr
rBT4Y5XNPMu1Wbu0RZOtbePWdkbrh0u8tLDDH4vVZpUBy2vzosqnJb4MLOd6
ud60BtaE9jZbwFFzWVtntpqv6wL6mGQ0zPAy7M1tMYOd2VxfA9eA4VZms4Y+
s2m9gXWGHsu6uh4D91xlOWxafh33NcqKam7X0D5Oul7g3gA/Xq15Tnmzxe5h
08txW6wsTK/CbnAX4Z/ABMrMFddVXrqJ4QVdFfN5aY35All2U883M3zbmLd5
tdUlc9kShpLdVPVdlTW4VGWxKmDwMPF8vS63uEpOfzXTbbauy2JGY0FhATsG
fAt2M6evoW9aFfi/etFaeAJskMRdjQsE/ebToixa+h7my7sT9wu/Y78iKak9
eMG6TdlmuKtTXLO8jV/CfSXirWD1kXLsdZPP7XxkpnaWb1y8ytoNNgUfFAtY
QhhIdpdvnTQMdFVUuPDQOJIDCWtYBUPDxCWXIwpLNLAJeQmCGT5ZuQy6nmfQ
ZKAZY97kt3hokfaUav063GH//bHSPiB5wAGAcfIwC2fy2cyCOCeSjQhzBEMg
ao3XEd/glcDdifgMHKTKMFfhYcE5AV4xp02ZGFr+f5UWo0fVQIcVKCsghlpY
DqAgOlDRmrByA+/fFnM65SsLigXyI/i3LhKMn8k7wyURhgbUANsnW2LptD58
oEcGXukd2ZHJgbHPeIC63XLk4SD+8OqCKByoaiVEwlP4OFvmuP+wTKfhSIGk
qWbMw3mjsly2aLOeCzMiapFznjRv/mGTl8WiwHVw0fSFs3GTSLy4mbJw+ezG
wtmEDmQNB5gSPOwuu3mnLICmHB/CtANceqSIXquGmEANxy8n6vGN4yfUFAkn
IEc/j40Drjcxvyf2vZuFZaBDu81siYtw9hHJGNp6GV5/B+S0UDrcP3v57iD7
9OnX8L8vQNo+Pnr6/P5+BHygxFONMq6sHbXJYyXun2fIRt0sh71Bbps1xKVb
EI30ZGT6qyifO5a5QKg4RGTqloRLUc8nIr2WMPCprewClxNOrqtX/sDDyXXR
WuFi0wFMFwnXcGpbkBZAy0V4CCs1L4Q3vgZqth9zlBEj2MB5UQe+jtOe5vj9
drwGPbEB2p5bnIYzwjC1fdp/B5opCKHppnHAnj1tj5DtwW4h5VXM8nOkQ9T9
xZpAFpdni+Kj9VyDBhYYktBRbz1X+Y11fmYkWZDybwviaiNztyxggXGBYPQb
+OAOdEcLmhxS+hRJbmq3NZFm7YUUir8vsvewQ7eFvTMmpXtqzfMjOotI6UAB
PEjgT8D9y80cW895nmjjwDGD82lhucz+p0/t+v7+APcVv6cOYHXmbgnzmWTZ
WTgHwF2zejbLcZ3gHGz5JCUHV6eJgicvSRDNaqBKN1NuBIYUcLJGOKd8xqwA
OuA24/NMT0iuh0ON09EFHqHoYpEf7YkX5zgkXKU5zHbWqupDvIxWpsN4WETL
Jo5g83KgvV2q2YjW30u8XPm1GebXuB2rel4stio0466ROxRCiwWvtun0JxIM
yGWdX4vYXnTXP2w49jDAPIWPM/8mGdbjzCOUc3CG7nB2wIzEBLy/hxH84z/+
Y5bn7vbafDmW/75kBTnzP+gv4Yfxl+YzWxZZ9lle/+zl7Wf9QV/JPsPrl6g+
NtHrIpbD6x/szBbIvT7TYL7sDebL7mC+lMFod+l/vV8+G/2Sl3n/1wfAecff
wov8Ny/qgbxI338pUwidyk9j+vIXd51lvwPpSUI2Oir/gs+RaTZ2BgdORdwv
njVssvl0kn0hG89G3Yu9iyHKYym3d99jTkRpDW9RSqVZPQX76pY5lp6fuYGd
dGrI2Y9kP9EbdPC5GzRUgEnotKrtgCCvK2BNxUJUE2U+0Roi+YNARoUTDekt
nij8w86/Ns5aIHho/3bMzRHRX/WlJ3ZCSqklDQE7mxeNnXlTlDgGanHMEQtS
c2U55sBYT5FJVTbSrlbFtUjkBvm4A5FctgW2Y0AhwAmM3168OB+/Iiho/A+b
Yjb2r9zfI5+ramQkDoxNZandgS+aepXhntL4ohlU9o5+Ax54Kq+SfgmLCK9U
7bitx7RrTWei+Ao/wFf45eiVemFsDgvA/ZFB4k3DETWAP9qPaMzCPpGmAJ8v
FiDl8Q0cBViKDhV/z9xA69iuQII1xQxEQgWaRA57i7aYX/p5QfTUbmE+sfGQ
6oPA32xBOkGNti19JyN3Bmg8GnormwwWvNUjEKugIKilIzYLRXvyZj52vFup
JYJKTXTDwEA4UX15m4H85n+CDBf5IDosDzASMzoOXn2HemMPa/BWo6r5LLB8
d7ljKY2vwGDvwJACYvYTZaMnGjDowahL4+/VzNOkl7BGTYElN5yRcqd2M0qm
AaG//RpVJFi9jA+rs7MNGKnb+3scklnXaIwUYFzRZ7LrdMYKJ0u0Qyy2nf1q
EAPKyMhM0Iyg6xvR8UfcGdNvDsyqui71iMGeoVkkvAd3dpSB4enpLC/pGBiH
1NzirGFIrm62aIplZLxXhHUpiATMgLZ0/Pb0XWAHjNLmMQWOV3kF2rf8BRwi
n88bZHTenuYno0AzMhgkkrLeUneoS8H+NbKScGJWNWw/aFSISiLdIyiTLFBk
3VyKEfTpC+BN49kM5MQuDRqNa+RfwJyn8HG7aZkHRabVwtr5FBZyGK8g7Y2J
MwGbJiYakO6Yt8mgOVAfSzu/ZqMfmgbjC/FSxOxdzxiDv3//5g9j+e354fNn
YKAZPdkB1IqRCcLLnJOlBVPOpIgAUsqEdrs7pxLOQwWzJh4tWiybM/PIfDLY
MP9MXILNCVCbC4QRcLtQWtwQBAZsiHeAoRXYwfOKyawBsqt2Wzi/xGLs4h8V
cnY2eXnhQQRe582cT7Oe1GHNnS1bXhriMDuwIGcTQcdwr9MZg0kikN1dzlwE
ASaBWWDzl4W97WrqLCRZSZnHkBwsVp+UumZAF/UyqnN7qcYdkOCkJuwAIDEx
Z7Gd15fsohh5/YlNuIFDFc2xGGJeYew1SsK7wqHh9zImxU05R7GMUhp4YjVj
LDAPMzI0UkWiY7Jmiot/TfAfHcPA/K9Q/MHK21EkUvAsMHhM8LdoH4LxJdTj
ZRnSB5o5ZvB0xcZmDytKcfeuphmrJnUAFoYN1Q7C0YfDEBOF/yO91AtIXvrA
XBA52IFeXW/wlRhLFjDAoy2iI5k5yEscGZ1ZggU31cZtyKZfFiBYBdka0HsT
Um/tal03aMyDYoYLYUk85LfotURy8z2iJikvF+XWz0OfK9LOJrkj50bhGFQE
XgPzABKA87xm504OSi8b/rLqZDTTGsIJwaW+oAUj2CMcAxF5fAzCiGkTxaHg
TFcZLXNH7iTmorS/qD2v6qpo62gZvxZtBFk/2QwoFn+okEgRAgW9bQb805i/
2jiEehnL7xMBrm+HnymuS/Q8ry1LSSSJiBWgWsHoGx12ecII1jsYfUHoQk4E
XbR8/BRjZbAgsRYm5pzRXqAHPan24wzOnn+ZmY8D0imLG1tuRXMPhtXIeC6X
OKsQn5RlmXXnP0hzaK4pm2Sx6T9nbWq64UXYIGBQCrzi/V6BJwgjg9EgPMOq
2gyZgFoqrHcj/BhOs9fm8BnjQw63UrXrwU4jRqRqDauTcwXaxJ5leLEgJBI2
WT1Sgl2DRbhsVRduI3JBDck7PkvY71L0GTYkySgsFfZXG5y6zVfaN+sM9Wpa
VDAsxmmJLRawnmwTwtyXeRMdVB4YjDqRTdgyc2qkADoo0NCimAtb6yBR2j2p
B8JMInNFvR6Dotnwnjiy/dNvw6mNyRjxaFaSEseSyg/ctllfou/zYRaV9f5g
ZDwWzXuiYkj4AGMWqPDNbIAmDWxMJe7dRGlBKHu1piO4qFGpUVKXfrmF6pp6
BvKbqaMl2SyYc2eneWx8UHm7d2wfUjGZGakwuStKNJvoOJNBOo01JLRHeTNj
IVOw5UavozoHvSDxb8ifP4V1uSvm7dIo2e84OuG80J4R0yC/2GxgniMzrLZ5
PQVjSRomlaAeTbfDkCgriN1nas/JV8OKuTiWdSlUBUl9p+pGKVaCtcRqD/lu
axAJIA4YjJrK8qotOa/vKoI4cOq4jKmGANxqVqLDAF+uPIFPsvNKHWwoPT0F
wEBK/Jx32QjThv5QKrV3FnbYL3bOHHshZgIItAvbjF8jvbJZx4REPEVMy6zd
wJdm//wiEzhvlLl6g8eCbR9Yw4pXC16J7FG1kuumdQeGCXlq2e1M4lcHRfhI
gM4QrlIOLU5V/zGsS4uqB9FmQ1CO5+bxvvlFU03QAyIsUon/7rCKcAXRKdgd
1gNOBkOMyG0adf97MafwIKmr0OjQIBXD8CJRPu+AkaQQwMnRPkUz7++Vh/lA
K1ReaojkNw3ZKj1VB+ELoqEi9iQYmzcwADoUfgAINKWaEXXH2AEaeNRTrweY
4odBJVoiMXhHZEok/litYJ8gjiAWkCODCoJ92JriQA+aNxwYIiqLbjIPPWvE
hpP4IoYGWSlAH3AfTXvYhZ0HpI9VO+B1+dptKE4PtgYoiRQeYuz7ClZ8+vRr
IKV3Zy+vxnBcEID46vir5yAnDOFyM1JPGdKWrm3UJzHqDQbtIMsRhUZ7imKD
ZIXI7dYfvLAnBcsvRX16PDl6jNsQwCnUg1NFwYfhDK+JwozA5RgBDTYc7CdY
ALCsJGb8Ss15c1mKet00MlZoDmsMEAS1iliwCGEdPjO5MYhk6NxFqnuM0EX8
7iHtlARJ56zrDMTL3KJQgY1cY1CbyEE6Kl6V753niXkJuiOJyWCx86tgfZPK
Q3qwl7F4xn1wDWJZ+hkjY9Wt3eLCMQ8KztdGILgsBzUDrElE06cEnOALNEg0
CaTPiXkDUhaY/IhPDwe6+FnocUvcQANmvhH1uP+NR704oKAQADyGtggh5bbj
mI2OjtYJnstu83JjkXnpqIwcDW1+bS3q5OirZjQ65tbEcigepPBapMfAQ6Cf
2mlzuwCVLVvqDs+SsKN6BlyWYiiUA3nTRsaUqFpk0rMkPhWQ+CHKFNXH8Qay
0ydQncfgSW92Yr9FmhUyuchhLq5p/gPldKSzS1tqNq5rjeXCd4FGthH2FZFA
Ck6Nx0Z8MQhCsCQp2SGgEJLMDN7MHaGhzYoU4ul2EA4+G3ZG0loLVw+mi5IL
BqPyNscILpocAZdHAbxg/yQe7yCdoQ/gUq4dCqb0NAE6AohPhkLw2AhAKPp3
PqejSISP333tY25QMrlRelSYVU8yMCNNBC4xHkD6cAHCtchFtSR9ijBT9L+i
iIDzsdxUqEd6NZh9eMAfS7WQ6A3c7LCN06JlNHiaY5uo/qr2Ino12eXIpEEc
Q9toncKcgF+XN6zV1vlcdVSSNyhd4WSVoEhsg5o9n2CsHpBU0YouysBCUFMj
02qUqaRMJehIeAIJR5IJ7Gawrao7RXVblzT6BF5W9o0K9JTDqzA8psRliR3g
FEOreCVbSn10h/F7zyU9gbDF5pTELZytjmWmpkrRJqBAAjUGJDPyDHAYALw2
ZqblNSkKKyaPgUliRjGOCW0v4K8bh0E+HT2znrq6tIgrpRFbICiYVCjUipsX
kIvlGxrLt6L6BDJKPSBXbCvjaURAE/SvqrUqojRkRQZCh0UVMjSpcOPR4hZv
rHfH0vn9gbFQdm2b1CXMNLisxYwSk7wvquZwbmqVvV7AUtwmhrXR/hXirhEm
QYpWPaXF5E92t08KaC2h9X2BJKxWI7PrII7wseHQuz8hvKif8fnMnWc4251i
SvVFL34QTaYgZFg7FF7xqRDzjOUyz3kH1IyLhTISU3ECR4O1uUR+lpy0Giki
q9f8F0HrkTltfLAovweaHAKgiXOG4n8jVVA7SxG24KCjhAGfesC8MJkmd0eh
35yyQFw0nnYnFPRqu8aXOIPhe4p78e2D5v7m+0tyGR4fPb2/R8NUMyFONRPi
ciAT4tMnTIXA+A5iy6zFyX6JyqnR38qvhL7sCulJiAIJRXg2zZyCc2GHEF2h
xArJnXDGM/QA5Hf3dWK+hx5ArUaIAwQLsnTSD3Bvhvmxg5W8w6HzMXYjpaLS
1f3D5wnldaTZ95wRKN+MhFMSD1+tUShTwkGiOeH/kWYRNsw2GA9qSRC6QLBI
eKh+jP3kyEAAZopDZsgUpWp+WxfzyIUp4B+dqpwNIoGOpEs1gwO2xzEjL1Ef
rwKvfoUKo3h1iYXcgF2H+Wcu23v7w+XV3oj/N3v3nv794QwMtw9nr/Dfl29O
v//e/8PIG5dv3v/w/avwr/Dly/dv3569e8Ufw69Z8pPZe3v6hz2OB9h7f3F1
/v7d6fd7zP9iJpI3EuALj0DYg+xgG8dotguB3r99efHf/vPRE1iBP4N/Hj25
v6fzys2TWOY/0Y41sHc2Jx0cYRDYnKKlKItc4xJRTsD6/eXf4FL88ST7Zjpb
Hz35Vn7AGSY/6iIlP9Ii9X/pfcyrNvDTQDd++ZLfO0ubjvf0D8nfutDRj9/8
ukQbYnz0/NffGnLXk+ZxAvMHWbrX0TL2SK2utoqGFIn3FZMSlZWuKZFmwBbH
lc32ehbFHjBPOOCupxxHFtYcO4iB9um2H2aU6aBI0nHEekBa9KSQ1sI/0WH5
y+w02+thRXuK2xBPJ7bJEXdRi9gjKUwDXjrR4i44POfTFxJOhZZlEp9L3jDC
SDDkAQgwR+NQHtKSMuviwdCLoFKCkg8qjOtiJb+aHOG0Q2odDuZc1FPvBsWG
uB9RziuESLaoN8PQP31aFNeanCkxYHQ6nF/a3Bt7yVQ2TuODZ4H5sFIdhvik
P0AO/m2YjtJlgwV+wyvyGrd0/+gge5EdjeDnD1bCKOA3+hu3hY3W7A06m3+L
mtP+U3r4OwkB3X98jA0cfny6eDafHS7maAsefrTyF776KoKSX4ZIyvNX2fe2
uobF2n9+8PB7+4eTyfHhk0N67ZJB6odaGnwlauQ+xM12NkYDaJM1e00bhIGz
3/wZGLQh5RfTZ1vOno3ScincE9SLm0dfAC3NX+xOjxbg/etFYcv5C/1rVs8t
HckXYVXNRQlqqfYsfcFhfjSQQ/yIfeuPnvzKjMffRtotHjFKYGGjEFbk4/PD
AyU8PT0ei0jw1uhEmeRETbKMI/E/+kZhjQVyYXoiWayYLArdWc1xRaDzgJCh
eNnfnl8xRopBWqKSDxMgLRbHuqEeJaNHVcQVH3EIDsfweKETM4uiQU/+Fiyh
7Kq+tqReeBN6cGWkUSVy6hL9+gXpuys+t8/G+Go0yAkGgsPKe6A+nkBOkXhB
zJo+27zqdkk6dQ4asYa+7jpmZNIyT1KDDawgdRO1lEwJzIABNY+fD019JDyZ
lb3EyWw6U5pkpyDyWVujZaeYYXQlo2qtDS1AWysxutM6saolHNlQxGrkFu7k
d9By7OYJvECkQwhdKTaIoCpN1Eis6s81IrvNM4mQbd+aJsp1hcPR8eQYv0YK
9js4yHy4IwSzeKDAT2ZMfw+8Xi8MagcDkgsO3bnieR/bcHTZPSSjDTYjwyhm
d1e6WZFjhYhYF4NOS87ZWiLoMCEpCMnjrgw6GP3c7HTr0L++NRqf/hB3T787
nGiAqo5Sn3QTmWhf4ywms//QPh7QYLQxkfFziajOmJuEFc/9eocsZLBIVgwa
UgIp+jIWW3GVUwIDRXKhdTVoLiHM09XEQuN0Mj1OQFG+SCUEOYa4dBEmLjsi
9nvss5If2FJF99aID2KEGjSbHApC8R1n+6j27j2nadhVqpGly0SQT8RIMOY4
5oXYS8w6Sfwwt91U+A4x0NZiOOv+4fjo+NkBM0AKifNSgKwd4P+DYmTkMyJK
mw9IgB0s0uySDupa5AThrcpL1a5HPXkQeAGMf5JJihTn/zH3gm7gUV8gD4BR
m4oS60YqJ3SzO9H7Tj2xPsUjIEpRCB5LLxAlNT13mzXlItKWEtM3TBUiTfYP
dVAw3qcHIPc1UZp4iS0IgoXZCMol0SxsdHdT5/bdQTzIwTAzVd9zkPrXOYVu
FLOMk2rZi4OnlYyu3yInI/tif/rjqqhI2T08zG5gHx/B0OHfo0P4mwgGqyY4
i4jsAX6qEEwrfqgKvqVGsr+ENv5uv3p0fHhgJPejYlvO06XK3kOiM1iXsCwh
ViUWpmgm2I9jWiMwD0pSbsiZIOR2G3QLtZWUhEGfYuyOfW4ycHV9Q9Of/Ww4
jywmxM/m88k4+q/zF3wbLRh9fZikoMHzo+Pk+VH3Ocw+fn7cff7kKHn+uPs8
e+uf0veHnecTGIB/BZ4fdZ4fxg18zp50vz+aJN8/6X0fN/A5e9r7/jh93v0+
+y4Z//Oh8X8X+n/eH/938fhxPL3xR98fHR51vo8bwP3ofn/ced75/quvJr/y
b/B+xs9/YO6jowOeFZ6ikaVkrcbVGbsiXDc1kWG1lJjpQzS9SGi8DZjCBWEK
IDkIIZBsoQ6wsCsiwnHBDuYUBIiZXEAKHNPTZ8IGUOBp+SvyyBazYp1riAS7
TIKDRGJuDCfYEM+rBH1u6tJODOfJ8sfs42nTyheSr4HJkjgTbtBs1jjGeFCD
wU9xgCP7nEJxE9+DMwIphPYJ1WlFDCZTxyWdLeuCI/vCIxbImIjS1Cvg5Z7Z
4U+WdBrCFxHnRvw5yjuR1JDUoUCaw6K0HwvJx0NF1qKZhT489kjhZxQX4AMV
ebFwIrCyqMX0OvGRoOTPAMaNkepNcKyxxoLYNiafcIrArO1k4dTeUVbobgZs
/ZT1J98zK2cD2S+GKs9wIHu0G8DgQVlq2AvJv+hbD6z/iKt0oJYJgodKqY0M
9by05doJ4u221QzoX6t5xbowD7aYGUshIrHztF6tyIxcwRg2DQPCd8saY/aU
LtIMAC3kVLKOjjn+oDossGwBU8GthMH03TYcEUQDD0gazKlhKadUfipBcFT5
rZTqG+9Orw60skTXLHsy4fCmD69fPnnGeAJWSgEBbFnjXsNyg2SttIrE02dj
np0fseh/7CU2ncj5+YZg9HQtM1lLUW81oAHL51HBHFaBYlyJ1N4of5l4jb6b
dzVo8nkjqJL7mgGslvjY/Vioi04aBf50OaG3b64rmOLcSKRgXsUaf5T+FNvB
u/OyJ10wNkRtSJUJHywUG2pmh6GmO1svFmPOnZZE7a0HpiKPKWjg7F2Wgemw
cL046Clk1BqP/fpk9oFqPMGS9GUbOIUBw6iAn6zIzxjOQrwmWHaPsRAtchQV
kLjFigGTHfarbImmxvfrb7ACTBkwmOVMub148vRDUS+98SG1PigEqkiHnLSb
Noixb95rNt/wueW6Qz3AXYWp9CxOZgbmAgbvQUfvVUBj2iA0d+DtsU4StG7P
/i7sK7hNPuLKbBpqz4lJ2APpFImUugUakoTx+rpNKDuekklgNO7PQ4i/DDi8
TUzDTNbLyHrpPoellp3eDVRpagqjnshvcRyGK9D0qZTcbz6hiUqDqONhAusg
kTsj7ZdBF9PrEiuSaYejvnfi7ekfkmmoDSw/DLAx4Zxxu+lEXZxBCO2zWJMG
d5yGO67qpGsAn9Z9lhUFICJ4ASPXRgMyIf42xVx3AxqTpC3czdBYejJ4fePg
5GCtg/WJyIUx5wtSp/wyRCUlQO6+UgWTedMlVhgCLgPrNrfZBcmY/VeXLy8O
kkRokH3HT549wYTndjiIV1JdfSxYXUX1xpgfY/octykhABSNzZHBdbc6GYGM
QRvWwYg8DNEBkT0v5Ss+feFTMO7N7lDAoQxHBhNEL4uDbziftxt7IyFZXvnO
8lW94Ux4qiZYcEgOnHtVxHteTCzkwE5J2LrTEqvSUnFNPE5JvB93JaneVNzw
rvLxsJRZQAoDJTrQgcSA71m94nBQDGimlGji3NwWclUJF+TMFcytF+WUEm0p
oBFxExwVF4j75eG93Icutye/sKMMQGgZtTgXAuEhyYJJ1LvoKOMh4ReVxVo3
AGb5uiuZpL4yaMoxbr8gl/N00XLG+wPb5tPMQzzyYH0aPjm+c5mw/biGzXHd
ePnGUswcIbEhtdnIomMhSQxwVG2KGxnMJZewL0HuUW3xJBwC7tiyG2kULjB4
SUfElA3msf3KbSMuuKOt+dJl0uid8qWJeU+tdhL8OZWNYvlASknOi6fQOFLW
Kxf9SF+CrJjSFDcmrW8UU87Yx7ZFQ8DNTePFKHqBFjINkI/sNYl1NIJkMijq
WgQKo1wGzmGm2iEU0YPpVneDeSI1x4reSeGaOonI8xEZXAJhDb9j4kkytl6A
RVzCJYqPWtBhrmBHiRMrnCFl13yApQKBePIc6S05DnJGtv1Qto43CGjz4kQF
MoSwBd+1aQp3ExeJieT6gM9igYTZC8TwgWnkTvJIcydCFA4nDYjSKCO/00zT
KRS+aThXjLEU5Q+aTaYsi0osmsEVMCGbnKUEmHXFsq7nQU4EOe1rQFH0yTsp
3xfiiT990a7JWZFA/V3AvkiqcQ6X2ZpuO+XgyJH/oyDvyCj6FQFRIz4++sqi
BnHGhBYGoDVeym00HDy70EFFGWU7hjLpywzPjPTE/sIBGk6R71VCYqVI5XUS
QzPQiibR/YIFSTyKExN7VMDUH/9km3osMMW/pDlKMwAbNXepmmabpmZ9Y7u2
2dWH03eXF+8/XP14cfrh9O3Z1dmHH88+fHj/oYtOHB9ySJF3Gv8bB5W0a4kn
gX/EoSRIK1+74if74ljjQhDkGJh4IfbpoDfx0yceuLgVJX7j9piiNx4//Uqe
BN+h2kKqf9RgMf0k+63tgqjtj0N8dAwl4RrjibwusPoS1q4CNj4tC7dUA+dS
8zmPjyfHIwP//zE3AP96kiz4WaqWoBMTxLdFHA1DG1uuKPDLaO4u93WBNXPT
awwRrZA4Yej1cPzh6qpLFM8mT1KquGL1fNQ5O1H+heUqLjFJGtBli3LXSeqx
NKoGpfjEpXj5sM4tCLjXBGF++iJk7t+TACbpF+UacZ24ItRZziUphR/L4jkx
gGm9lY2Qmc7yTXxbhx9nz2nLDj8ePdboDarrgcEr/L6PVqLoOv0zLWfs87co
Kz33Yx6ZGFJRwuRkLRQQK0kN4CE6iUshyyAnxTL4wZOUCmghafGIVEdnIxNJ
rMrUfBUffASRxGVBc8VUgaAWxccsCrg4epYELHCxi7RidHBEy35wdXoaxYlB
005LpaRDB5qgLKSAeCHf9C8T9YZna6zZgNCmVnihxQpllDw4JUlH63bkvZZR
UQje2n3c/xFt/kEIt0BhnGw912jT4MqrZagQ2GkvBAdxdQvL+W2yRNFhkRXy
xhHF5CooECBQKp0I429FH1MZaeMl5jJDwJq2UuciaBbRAJFtRGeRRIDg6vQO
F4IBgiBbyA+Bcaj4MJz8G0qOML4HIhJnz48e2+PpEcuQ0+S0E3CRpwTFbIBQ
Vybn8dxqyQY9B5Gt5ysaq2Hh9YOHBVE2IIi4oLCym1BigqW2eB6ZQRkwFLB2
ntJYckxDoqyygwj2ADHUtJI6xefQT0Ep1lkPZ7rEHDAdqhBo0occ9Wg2JjYG
KpiIi5h4Qx7PeMwZFtvsBnrBPzvELGLg+7j+4sJLBRiRFwB1w2lp7t4khFpQ
vcOetZq6dTUBzCfhdkxRnVKkJ4di2Rx2QoFHVNM0IFFJYAqxFbGHexgM5axQ
8nI9oJFOzOuC6mSPOn5JX9ui0mFpWnyvlG0TZcYwDJ9p/RbO1mYdFKZVFteU
cYvWFdeoBK3cdT10Si/YMhWnIYpUG5zxiy7bk6LYCQvhjCJlGL64udZfUSmB
NjOnkOEouWGpJnI1kDMebX5eoiwRfNptFgv0rXLRKrU8JLXeJ6bTVDyOHnwM
qG4mpxLW7xWQTMHp4ApYKLq0zAW7iYejqUqR/zeY796Zq473lngmVq1wLZxK
dkP5gnW1vBZnDNVqvISEzqhwXKxTaXLcWy4WPGeVipJCOhKXGJjgtLJT0SaC
2I+UsPsDE3TAjaR/cT1iqZwUAAoMkBQzuYNLa4Ayy5MFvS8Fn2OEw1wTRxmC
QTi3PJc91EK6bFWyhs8dCCYxtTSKjhE8XEqwU20dHQDXgln2SxMiOk+0sqlk
ALtreeisVR3E44kJMFKdKGFqUhKqWCQ543d0bnD1fQHGwdr6aeF/eiPdAeOD
PAKoI4Lz4vTqzY8vMb/p7N13Z6hZ0S8fzsC6fHd5xvbQxINMWkqGSiILH+UL
lohbhvsQyHMZl9wm8xvr+fpYvQGjwSOsazKdMFcXowtwN987F+K3yfHzIXJO
nysBo5LQK55H6zgD1d5hZCymjv1qTEVunFThCtTpq3uC3me8ICSFQjx/4ayw
VpQ4LkV8pCUwQgFbrnscnTaebk/qUX2vun8UqAphBfPBi5XmlMVJImKxaRhE
bYB7NUVOGZPyW4TzcVp7z6CiIHr03Zl4LpjjzYwxYFApbBjhWdgqnB3kr65A
B4WLFgGYVkiME6EWRsqGum9UL0+irOE7IlLj9TDEYFdYgVjDQ3lYvgJtikWJ
NuLx3bgtLD/F+LkOxC2ZTLBIWdkOGW6atcX5FJ0cKMLseLte+SLJgzdzeBaQ
eK5TRzTeQqXp2g9V9h6MzWrJ/CfMs5tFIVHtEQIa0np7d5RQfnRU6oKKvvSr
eEZZ9dthl1sIvOZehw6p1kDoyA5YBz6SoYiPPlrmqv6b2O3PeaM71jWo9Ds9
/AeToeHRmnrvBp2OBrY5n9nd2S2aEpRm2ahB+lC+UQxTQCN0XxEqfFzNoT+6
1JvmV0iyvjGKJ/KTJEmVyc0mvr1kaok/ecH1SNyS5YD8nEtpPYkRGrqA6mvj
hRi7LusGVFP8WOaJrKjBAmAVauxrzufqgO7eoOgO2Ot3XBiG/VOTgZWKMDia
YroaipGEQjPqPadBaoUX711eO7uZ12iwRsA3lUXYsUVSqTtPQzT4Sg4eDzvs
8EpLiUfVoe3/Pb/9I//99wc6WGST+KLxL3Kp6/Ci1hGrPfLdL+K9YFnVieGX
5M4wT1O4H+m0vcj2eTx/c/jH7M8zTu578YL+IfP6UVnni6xq62WpHxyd/OqP
B1n2BaeZNsFPBQS1xHOEjC+vED7T3nCF9vc7zWKvzxb8n/StR/oAr2dM1gsH
3BkxZu198012dJB9zrptf/tt9vjoADOSF1mynNk3abt8D2RouLcus0NqP20E
mqfW/ZdH8ZdHf5S50ZedT/8cBwzDfnZAeaXmvZYBHc7VYNcX6/tdmpSSCx7n
mi3t7MZtVqH2n49nOa04VpRK55d6zZsmGBF6FCX1c0jI0dPjJ3i7AOxdABOf
M/L8ayp4cXh4fx8xprly10TuNLbMtUD7+cXtU5Y3X7ASCCo1qYjZD5rg1BM/
QwzTs4EcYypilAWDdzsaNlrFbluhUYiWRgeSUax14MKoMpe7xxDJZiMKq3Su
WxvEAM4TcT41ANooFyaq2ErGz9urHzgYl338jDhNrXAVQcSTgrK+LkUI9Pu5
kmR4NyHarYVbEYcX2MNnU6pqbwNiASvG+77YoGEbFRzyegktONkDwzcEBjid
bEI0wapO8dCcTEdyt3KRxQGPc7/f0z9oj4QoU90WU6yotgn63gVrz33sjMZd
D0VoJOovxW+TGYyWFYkmzlaD3cd8ybrmXLlAL3z9Gcaqz0fqNuBSXPAbxr0w
SyfI2UN4Xk/HPUJtx4epojz1eKovUYjRwI4hzr4mdsram15EU0v0dp91UKgD
tDEyfVHmg2rj+ndFzE76Jec6J0rLFoSot4ejaHzQP208dzQxv/V3nxZxtC3b
EdFMe/m+hq8DIuFLF3CEslT+4gGKGcbr/3CzepZYWkqwR2FAAXPLIF/vU3l5
19L47Ij2rtgVWkGkyFm9Hi3w93qIUUkhp1JowPE1QKcSc9BKub9cCqX/vJ0Z
n9pY10giVvF4dpzv3qB2vjJVagzVU2SeA/dQYtnYrWBKXFtEkP0utlE3A9Bb
qAvWWV1GuI8P/7ya52759eNDn2ZC0R4ceJ8Ci2mVxx2303CcyFXKIARz7eZG
5LMGac5HkAjXSOHSJKUyARWRJkO1JBel+XjnQ+YwVhx2qpoDV6KbZSb9pCb1
ugby4qwAX/t/YK5ciEvg0+iS5VjXjlbfdQjiQcSMzpTklmg/eIIC1q1ZR1IF
tg61Hr0rPZV/jR0o/MUC0Gl5/02LZXT4Ut52Wc8VQB6GkWBXdnQspY2jmn1R
yoQvzDWAQqrQCpcr9WrPycQpgGvR2KQkVho3ikELWr54uPpcJPy5rCFHjoVe
KKXKgfYCaicCeGW5wbg4hHW+Nm1UEJbkFoEvwme50BaXjFGDlWpuhchV32EE
EEX98mwauvydr73yRT79RsrtJ8H/k1b1ClXCMfK74dhWhf8KTjXAI9snjFM4
xrDgCcPV4YaLoaKHcuORXHZEegA0OOfSzXL7el+qPX3mDgxd5sdguVibDTPY
vIprB6PjgdZamYmfk58Rz1rD4QPd+mDdIdsAK0bi9lXz+FCOTHJ8WLwROdVZ
qBcnSYRpxd3TSC/t0mQo2csV6KBFE9wvEW+Y2mCwsA1SR0UE+IW4GHqEN1Pw
Tt05/1oleBA08VCZz2WMyybvYC8ccrPrLBv0tDNdWQ0XoIoMGH48QFRUJDWm
KI3q0csuODe/ez9egD1yx1dqXFP2XHAZ1h2xl8Y3z+S+lru6T56uc6lWFZtl
/QhHrqMMmpfTJPDodb6dGlHldKdVm0Xf/C3d2gw2XoFRDBhHVzKf4IsLHup8
JJUB5BLsogp34A4GjQ5cKBk8pKyzD6yxOMAiBWhQv2XFItFM9usmVF7nIqGa
v4eC7WAUWIewhuR+A1XnA5yM5z+W33IJu+O72RMuOtcY7didGExBvQXPYozq
QNnVWJNiiqyr9I6KYXda4QTeTvJsMQCaM2olyEliBjgDt7DOFw+qCKKKq+Fo
Ki3LH1jGFeiLvWIspL+TVtV5f4o3nudNEbzRkXN5h1YfrqHt3yHb5Vk+F0XK
YCOU3kYVJd2DIKReDdO9YCQqtrk7l8a7qnomhGeRfGGdRCm0tNScnTpQljJO
lWTzlvwgfK8lcRiWrj74ClMOgdx+osDqZNFzAQro3FRRaiK86q8qkvLI5gdK
d41ZeW9bBA6Rewek6DJrHG3N0aP+mrq09I6AM9H9SkmFJXE3LvIbGywlPXes
HlNo5BkDMUPJRL5uZyxi+KCxPjd0EDnSGZgVOVmEf+26BiQWaF1gqEM25OHz
+Rn+lAgvjzPU0zSCfjJNlMvE6l7Jl8sw59xJt0ixEslxSQpcZ9pcuAVnvpZA
Ppo88XTdMg1LsmqEkWwHm5i6Xted23XSaxj7BYQ9+pZWlpG0k+RVCejRL0yt
RYrMrtrM3VsCEwMlSzQIdO7HnSUVbRXTiUyx+0mPoII9ICOdF46rjzesuVYD
xGZCvX52dksgj5N7fBjPa+xY/JKodiEbRLAl2jsYfmweqLfDPGwWcyRGdB0C
+kl9tvoPGGAUB1VGlxEvyCajMnJDLjuO2/U+Ox+EyxdhUSbHLtY5Q62d3WAV
X5elNeu9GIpq0FBBnagkiXg7g5n83geESGwEOUIf9IKm0EwvCRHda5TyTyWt
B0SyFfP4QXPaX+O5IzGC7CYOC6Gqilp5cW5nRYilzAWdMCsKMbwTNyiw+g3f
AeDRTdSxd+YBx4m2AaVIQ2+iimfqGEtKeY26pdYi3TCESv+w5vwvaEf8B2lO
ZuEzU3ZmpYziKBwjoQuDVzYlmeWEf6Vh0YqMUvTkJHtVo4rvQnGOXl4Q3ldH
1+LSvSV04cGOu9q7xbZGzOXFukhNIAkjzNMWyNNIXTgYr48fNRxULVW7fZYj
fh7vouBx9ubBECuO8CJghJQeXAjT3fgU8ByG9nu5l5eD0REBgQ26dKhe19Yn
MB1CvBFEC6b/iTnBEofDVoqjfHS1S8VZywqWyQQHI/WqGbD2sUBsp+i4BA1G
10xV9TAHZe6p5ibefsXgIl6eUc22OGrknWShK+tK5+DFj0vMSr5rOguldOKi
M10+ktGU5ZK/9Bal2BynPBwyrTZrgiN88T4ytBu8npv1SorMV+g4nOlIcTMc
U0aZPazVJRRDYyHcvnDe+ZUGHBXOg7lk7DTDwbgJZL8rfnEnZmyiXv51kDG6
gUglCgeLyUOQ7mQEyF+0Zwx45bsOvDF1azHXTqwwMSi9xZdeioMhClpzqAOe
JdmDVBhLLkSN3GN9Jahzh3G4PiFumquJ2HaGwSNcoEcvFwherl+Fuk+VxPCb
aEnS3aurKKF9ls9txTBeuMwBJQEVqO0MJl7mxG1TqW7FFyQSf5ZiQ4tdgF5I
9hYtGNd3gSwNJWzcq+RszDhYm3Z+OMwrLgehTLFBWxZOUrFmCI2ngFWY1Otg
P65rpjy9NI2OCd0PQ/yE/NF4EtYYFORBel/cysRX3OqJ8Y6Knuwjo0BSeIHX
bhrna+mimQ6r79peqZvBCRspgemvXM6SG6PdOmeYJfiJO2AfPRksGTrkNNL6
QzHTSSxgf51fLUGUdJ23XmTl8oWN8MyhO+vKfO2sZoBFuXmFi6J5i3nJtwJh
+6hU0/XXcrPEFuG9lvIQ+apMh1GBN9aS6RTfKZkjjJbhxUY+LX5HEFs+ELyl
2dH9adzlFJLGwSCGSt50K61SlIh1VF/AX4ynwlpiDLUoByzvFKXAVZ2xVy87
pZDCoBgv5JV7DFzvRh4OMlLGsOUyUI5xFR4eSAPU29Nqa+IYsp5SLdJMAUS5
8kvF1W2XlW3Us+GRNK4loJWJfAhF1+MyGG6RS/C+BoRD03Q1W5q3dbVU+DK6
YVe0+JBG3p9BPG66xkTuqUrvs2Zdg54hCW7aGhefr7bRK3J9wDZoD6gavqFI
t8EViu9+GIoIoCu/BvaKjW/25XtX/tBdd75QTaru8vVVZCbP4zcIbreOLkTz
koquzU2VM7mVORTcmTeUDcDFWdGXwAH7md64ZSSwJ9Yy/d4GA4U3SOM3I8WI
6jqilJhhoCGsPRe4CzE43tsgu9AJSjYbRgRAhW4q76bopYL2JQwVMhLtJSay
QlUQEixy65R3f4hIiGY2aBDRfVvqSI0LuZGfPMvSu5cQGkksp1CKgRINcpMa
DKQX4oqNg7EUM3LCNnQ5UWdXxgB2LP7MoiZVKXOpde2XIsu8Phmfk8ZSlLPB
287kslk9FmM6Fp2dZGsyrjfCb/kN9u5Kks0KrDADWFIyi60e0LI7OLhPtUI1
Ya0QcCCH9NYXrcTuk3yMOmKCWi3YALcsoDDZ5ULEFPdPtwiWhQ1h2lXdxXHD
/dV9BVKjPOj0t76KH8UXajV00pYYj7xjn6hXP/G6Fjvb0L1ML1EXnttGGMKn
L5w8udfF2qmRJ0g1TXy4bFHHtSyga3QtqETOxOZyzb5SUmL8rXpGbUwfdRZK
mWYeJ5PgDs7z02I8fj3k0h5qG5EZrqdi3dDFUlfLXVeWc1qFJtXL1grrQYeC
6tP9hAAfIu4zlWMvGsUtkpVGrj4qj8OKWq8wnGYuSpZMwJp/xpaK8jyHxHr/
Tuf+Jdm9lFGskRLfrI36y/vFYnyB0znFqxgdOZWAvHy1SL37JL1nQk+mrmVE
E/AT2RSD0SaFI+kkCTWM9SFuHocThlvHCOHJe2mCoAZ++hRX/bxHrMcXiwlD
IRclx6aGy4RZd/UZ7L5UXZpfULTyofgViPVnfCPfmEu/0x3KyCqQF0ELlnKK
jFvDucTSFUMW5SUXI+80EXE4tVJRQhjvsmtytMNpaYrqTxgmodBgdurbYDNk
Q4xPPEl09SXdG6dN6cb50gYBExxlM6rSkohZgjFYK4RjTZByxyHsY369545/
H2Ue7mjTQg4cc6JkC2NoGvKvRXhmFP+3qCWVTVMrBEadZJdroLQoBT4B7/zN
oiEUhevZkbwTl6g3WaZau4KCh/h2CHGnb9c51XTdmkCHGA1LIJUnAmHxsO3X
uCSDK+VCnDQcRJ1rdBWtyCFWWvuXS0fp6SSe0JOzKlwpGYNheGKswvvFuvAZ
t323gQok4Sf+CtLMJ9ZrAokEF13byja+Sgla8UzInWOudZdjMkRzmuwpvq+w
f4z04nPQnjhRzygEQhp/zUll2mO40+N0qDGUHTrYAfBPTEZmj9GmJBA5ZwUt
BcGPXLPzfIVi0Nv4yND8Bam9k8zxN/Eg/PWL0Y3oLMUw/hy9oGs1hYZWynhX
ObK36KpemTBVJJOjMavXBWPgSYwys/NUaWmC46uxcS0sGAUmofkrfuQYqv2L
N+h2SzInrmeM0FUe5QV7ysbUE0g3H9vo+PAlYmNU6Pf8FCiLUG9rRrZdUDGK
8wsNrbdOYkUaVVR9g1HuETwxXKOJh6/Wh1QDT7/bm4e6smYWl1uVOyPTtxna
yNIXEcMLwPDe0Yerqz2vqXNNQAxhpqq0MK0y3/C94pLDCxJcmCrKrKLaRIV0
eT0QrYjK30ZFjfDGIAngEl3II7tY5B41E2DeQioSYMvVDoDDrIrZjcRZmSi5
gc7KrNmuQxmSpDAUTamxtM/E8X2lNh/gHpJCNN+ENySOdmBP7i4dSFLPMFZ+
QrWVBoKdXBbd4iWURz524qoqvuINpqFzYEbt04FYigWf3GlHegsiRxfo3Nbl
xl87Al/t4YnY61mVBh2TVcEh546r0mb7r95fHuBpxxpsWX6N2kl/AWL5Q0tt
NHhBasZTLkgj3ttoDtmC7rxW/eF80Wua9HdF5EizYsywuq6DwS0XjbfBsrYf
lznGUq7sqsaTpvgesza8tfs6gng0EMpFeOScCpPhXWnzDBZBZudOvOQWnbyb
+LBb24y9orIGXxvgMXiwUEVXnAtvwQEFq6U6ychXNuitjrmDdoXanomX8Gvg
iCMCPIj/Qivo79c72mT3Xg3PbICKSPloGXCZYZmhsGc9TCLcYw6NX1+DaMjj
eu1cXG8gIizFi/gc8h5ijaOYb/gs+oY4Q+Bw7D2Y+Ozw9BoN3mutOCKTZdHT
Qxd5AlzvHf0afDeglJ+WJHdvd0Q1uEn6vGJRDK9z4MuFTzACE6aTSTSQv7Ur
o4ITlpWw5xI1hIQalFiQ0+Q8opiATsUZH3YpLnSK2Yvrb3lIiNJdQiH9pNL7
Vi6vTsTTcM4jD5TE+jayBenOZ/RzUHCLKi5en4rGG91wadl8kZfr2WzTSIhE
p5ASjd1y2hHdZjBlMx1FimoYIxO4vdeOkoq8ITwGjEOu50yloKOKQVIJATWS
cVuP4X8mUZrXpsJ6KbcYr4+1lv0csQoPCxKd5oApHSfv5ZkW1WIVIM3gK6qf
ceIHv8B5iPAd8f1TSwtGITCWmUujYTUceyY+iDGqQEDtOBMae1xAyKeU6qkM
50JcPr5sloLMXLFPAqQdlfKjaPtQXqdbGmcUQiHDoJWeXTITj+rlYa1Dh+hN
QrVFdVlC6YcyfzTcy1/mFy87w2AXYCDmswEUbM0P7jWFfbZxPuk7hwOwdYW/
qtN+bMWRzYBOqMAQp61HtjiVBoLXkYcPQEQRkhLhy1O6DY/0pTnm/Zf+Bp4E
0WdXC5V5UOrGcDf4kt4PdWhpq9ttXP0ywNRG5h+JnHAHfZ797uLdhKOoB31m
nKmmUcFJ4qqUJiJeKN5d0pIGUtpa9ekIEMp+qch3c1uwGhtdSTcKsTpsa3mU
TSr9KqZah3eyzjtU0mSF5nobm20T877KEhORi9zzpUKtJDvEtdWoFxS4LEO9
0DGaCsvWBFGBlp/xMDyfdmySra+SL/6kI6kVDVmcSiaDFhXSqFFc1HPU1yrU
7nlc3pumYXAr2tL5LZjGwtw8dCT1yuYaCe0jUKhzF9Ux0kxdLpyhuxKNo2hM
bENN8LYgwZ3kJLU1ilZtwo+OKrVF5wMhlh1XJjiufiLRqlLajW6ZvEN+bisp
DiKKrZijBB1wPzoWupowyBBMGrpVDGr4OtzEAcQcFIu9myzR+fyp/pou2JU+
OKgUM5+L9abstK/QYhK5cGspmwADjfwZjg52FBsSUKhlMYdXEVLHUoNweimQ
Gpb5o6+MdiETPRWdChkzw5wUSNPfdTKPXVQLsKUKPfl1UKNJAzQg6HPHzq8H
V5Fsoz2UADeYZbg34WDy6BvjOagPXeWyfGmzbbHSrI7IXBKSa2uTblSChFEI
c2uvKVC/5031yCIZMhtfX4YqHfneOTTUbbyKU+hMyWyYU5JgyCgZZaC9c8lF
kgvADEiyhzr7RTPbrNj5h3ZVpUwWA27SqXfcW0wsbocXgg0wOdWBy+HGR7m2
0QGf8TVS8clmWwt4LoZ/5ITnaiXWM2/Cv2R29caWZZ3tn718c0CcU7Fvre5J
d/hZMYR0e9i5j8zZr4eQXx4VpuStCB7IgmlXaiB4Y1lng1qjECj6kru59mii
JyTySweg1Tdp8xUFVJtlHugANNd6ZYeJAXmDuBLSw+Tj4ESVFBFG9c3rNFie
wTYMQVb+ElXO0kJGXGsrNZn8vbyC36ZJ7dQgKX82x8IVIeDIbKqk2FPijdsZ
joaah+WVJGyexClhpsjjV1LRjicgbAlrYtEPY7H90EuJiQoExyeZN3w5HqUw
KTUrE+PLIYENKhfcGsVIUALOPKJB1C3VWFNYHjRzfiUWbKZQTUTxKOW3DBti
T4zpodIQY0cwosZ5xAg+YHCqiAJgUDOQCVGDUuwj3MjpWAPlUr+NvjAJC1RR
8JUItmgmpVQSo7hjUabKorqJR2igz0dhAoNr4gseDoWvdMLX1DpHhDpthcNR
cDzhNkkBpg2Xq/JJdnsV0mFe7sUXT3ZDyPCGLx8mpzukaA8nevi43lChMUw3
KlpqkoXDKBJcJfqRy5TwEsrJ5NakJFSeu9tr86Xe3Pul+axs8TP/MokeygWt
f8v/86X/Juv99xf44NvPeqNr/Cjqq9dyeB9JKfv8zQv/n2+Mbo9Nxyj/0SuP
st53l8wXPz/Q3wUt6a7++vObDMzv735+fo86K9ebD/f9F/0O6b1ue38XPT0d
LjIsbLU/hb8dmFXvt/diLDHwQ4Wq8G7exfh2XenFvDL0joku6iz8K2ZneCfv
aRWRqlplXs9US4UhIWHShgEVb71x3UIfydzNYvf5gDhMjpcgvUDZrJYd7/Da
tPBzZKezSDZ0W1PAg71/ndT3smhhNVg+KwZKGhfFXXn9Hm+2daTOnb18N8br
ziJ3blS6hNFbCgbOB0I9fLVuzYb1JYmkOgOXwIiv0pE8bHWpoddYYGIuQCO4
C93kopgUqYAcvrrYlCOMh7NYIrxIcg9nHHbMeqyJpUfEtyKEfstVb9xNnK+g
e8gMED7HMNhSk/gZFDk/fXfaR0QKMJDuu+GZfOeHJTvgrlMFHgEg+GYsP2BZ
otxX0h26U8R/gfVsD8QNyETwO22Ux+Hb3D2eNi6Bgfkm6rEgwUEj1Ub39OqS
rcEwbMmABdr9Rsv3393dTbDfSd1cP0JD6boiBIDq9387ijoig31TzFFZ58Ie
0eUyx/HFEDC/32G5AkxLCZl6IK1BFds4/BUDB/KK6qJexng1J7JE0zbmJR/S
lz5CiVJ0zq5eZ/sw7evf4I0COPgDgxdJAm22+AKtwu9rugsw+w442jrbxxnF
r7+rW0ujEVesYqrj7AxrjklFTpqJQ6aFoefQ3Is9AhxnLbKiaJ72/795vscC
d79kmkiu3WtprjyZX3gyFxqm+6keIt9fcsWN6DNE0Gags4i4s4S4zf8lcWcp
cdOVPruIG283MiYswDv4X3zSmWBMExf/T9HEfgUDPYB9l92GjQPtIMPYe2SY
p2kIK7zHOL+dv9ijgBqkjk+fPv0VrHJ2vrXVdd7c39/DhsxtUgWXxA568zQX
MY6LwFuszt+Z1HWl/qMVk8w0dywL0eeABYnIqvawhC7apFuY1dZrqjrh6jAG
ucJOxlaSOGF/9q0t63VUcd87Qk6AID6dliAAXzdYXLos7/GmD/yxAmvkLvsD
mJPo26luanyCr39XY/Lx67xolpgQoz+f19Xmv/+n7G2xzMuZzbWdv8aY2ewS
TOClvvmW7gnIXm1uLP3EBTQ//ft8CVr/Tz/lQEfZJWoAuOYT838ASV/RBY3L
AAA=

-->

</rfc>
