<?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-ek-intarea-ip-enclave-signaling-04" category="exp" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="IP Enclave Boundary Signaling">IP Enclave Boundary Signaling</title>
    <seriesInfo name="Internet-Draft" value="draft-ek-intarea-ip-enclave-signaling-04"/>
    <author fullname="Erik Kline">
      <organization>Aalyria Technologies Inc.</organization>
      <address>
        <email>ek.ietf@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="19"/>
    <area>INT</area>
    <keyword>IP enclave</keyword>
    <keyword>delay/disruption links</keyword>
    <keyword>ICMP</keyword>
    <keyword>ICMPv4</keyword>
    <keyword>ICMPv6</keyword>
    <abstract>
      <?line 58?>

<t>This document defines optional ICMP extension objects that a gateway at
the boundary between an IP enclave and a managed constrained long-haul
link, such as a scheduled deep-space link, can attach to existing
Destination Unreachable messages. On the unreachable errors generated
when an admitted packet cannot be forwarded because the required link
is presently unusable, the objects convey the expected time until the
link becomes usable, the time the estimate was generated, and the
expected one-way delay of the link. On the administrative prohibition
errors generated when the link's admission policy refuses a packet, a
presence-only object identifies boundary-link admission policy as the
source of the refusal. The underlying codes retain their existing
meanings, and this document requests no new ICMP type or code. It
specifies when the objects may be attached and what they convey, not
how transports, applications, or hosts react to them; making the
boundary's knowledge available to senders is intended to enable
experimentation with such reactions.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://ekline.github.io/draft-icmp-boundary-signaling/draft-ek-intarea-ip-enclave-signaling.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ek-intarea-ip-enclave-signaling/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        INTAREA Working Group mailing list (<eref target="mailto:int-area@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/int-area/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/int-area/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ekline/draft-icmp-boundary-signaling"/>.</t>
    </note>
  </front>
  <middle>
    <?line 78?>

<section anchor="intro">
      <name>Introduction</name>
      <t>Some IP enclaves reach other networks only over managed long-haul
links, such as a satellite link available during scheduled passes.
A boundary gateway can report a forwarding failure in a local
round-trip time even when the interruption lasts hours. An ordinary
Destination Unreachable error does not tell the sender when the
link is expected to become usable. An administrative prohibition
error alone does not identify which policy refused the packet.</t>
      <t>This document defines optional ICMP extension objects <xref target="RFC4884"/> for
existing Destination Unreachable errors. If an admitted packet cannot
be forwarded because its required link is unusable, the gateway can
report the message generation time, the expected time until the link
is usable, and the expected one-way link delay. If the managed
service's admission policy refuses the packet, a presence-only object
can identify that policy as the source of the refusal. The gateway
follows its usual rules to decide whether to send an error and which
code to use (<xref target="carriers"/>). The objects describe why a packet could
not be forwarded. They do not advertise services in advance. This
document does not specify how a sender reacts to the error
(<xref target="consumers"/>, <xref target="experiment"/>).</t>
    </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="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<dl>
        <dt>Enclave:</dt>
        <dd>
          <t>an IP network whose connectivity to other networks passes over one
or more managed constrained long-haul links.</t>
        </dd>
        <dt>Constrained long-haul link:</dt>
        <dd>
          <t>a link connecting enclaves whose usability is high-delay,
scheduled, intermittent, or otherwise restricted according to
knowledge held by the managing domain, and whose use is governed by
admission policy. Ordinary transient interface or carrier failure
does not by itself make a link a managed constrained long-haul link
(<xref target="applicability"/>).</t>
        </dd>
        <dt>Managed service:</dt>
        <dd>
          <t>the domain's knowledge that a particular constrained long-haul link,
or a sequence of link opportunities, is intended to carry particular
traffic, together with the associated schedule, admission policy, and
forwarding state. A managed service may exist while no route to its
destination is currently installed.</t>
        </dd>
        <dt>Orchestration function:</dt>
        <dd>
          <t>the logical function, possibly distributed across cooperating
administrative domains and not necessarily continuously reachable,
that manages the constrained long-haul links, distributes routing and
policy updates for them, and supplies gateways with the knowledge on
which the objects in this document are based.</t>
        </dd>
        <dt>Contact:</dt>
        <dd>
          <t>an interval during which a constrained long-haul link is planned to
carry traffic between a gateway and its remote counterpart.</t>
        </dd>
        <dt>Contact plan:</dt>
        <dd>
          <t>the schedule of contacts for a link or set of links, distributed to
gateways in advance of execution. A contact plan is one form of
managed-service knowledge, not the only one.</t>
        </dd>
        <dt>Gateway:</dt>
        <dd>
          <t>the router at the boundary between an enclave and a constrained
long-haul link, holding the managed-service knowledge for that link
and attaching the objects defined in this document.</t>
        </dd>
        <dt>Coordination scope:</dt>
        <dd>
          <t>the set of links, routes, and admission policies under the same
orchestration function, whose current state a gateway's assertions
describe.</t>
        </dd>
        <dt>Disclosure scope:</dt>
        <dd>
          <t>the administrative boundary within which the objects are generated
and within which their contents are considered appropriate to
reveal. It is at most the coordination scope and may be narrower.</t>
        </dd>
        <dt>Trans-boundary traffic:</dt>
        <dd>
          <t>traffic whose path crosses a gateway onto a constrained long-haul
link.</t>
        </dd>
        <dt>Admission:</dt>
        <dd>
          <t>a gateway's determination, against local policy, that particular
traffic may use a constrained long-haul link.</t>
        </dd>
        <dt>Link Condition Object:</dt>
        <dd>
          <t>an ICMP extension object of the class defined in <xref target="objects"/>,
carrying constrained long-haul link metadata on a Destination
Unreachable message.</t>
        </dd>
        <dt>Carrier code:</dt>
        <dd>
          <t>an existing Destination Unreachable code on which one or more Link
Condition Objects may be carried (<xref target="carriers"/>).</t>
        </dd>
        <dt>Expected Time Until Link Usability (ETU):</dt>
        <dd>
          <t>the gateway's estimate, at generation of a notification, of the
interval from generation until the relevant constrained long-haul
link is expected to become usable for forwarding (<xref target="etu"/>).</t>
        </dd>
        <dt>Enclave time reference:</dt>
        <dd>
          <t>the shared time reference, established by the specification or
provisioning of the managed deployment, against which Generation
Time is expressed (<xref target="gen-time"/>). Its time scale, epoch, and
discontinuity treatment are deployment choices, not protocol
prerequisites; UTC is one permitted choice.</t>
        </dd>
      </dl>
    </section>
    <section anchor="applicability">
      <name>Applicability</name>
      <t>The mechanisms in this document apply to deployments in which one or
more constrained long-haul links connect IP enclaves, and in which the
links, the routes over them, and the admission policies governing them
are managed by a common orchestration function. When several long-haul
options exist for the same traffic, this document assumes they
participate in the same logical orchestration. This does not require a
single physical controller, a particular routing protocol, or continuous
connectivity between gateways and the controller (<xref target="orchestration"/>).
The objects are specified for use under a single administrative
authority or cooperating authorities sharing the coordination and
disclosure scopes defined below. <xref target="RFC8799"/> provides broader context
on limited-domain deployments.</t>
      <t>The coordination scope is the set of links, routes, and policies the
participating domains manage together for the affected traffic. A
failed interface alone does not establish that the managed service is
unavailable. If a usable, policy-permitted path within that scope can
serve the traffic, the gateway uses it (<xref target="generation"/>).</t>
      <t>The disclosure scope is the administrative boundary within which the
domains agree to share the objects. Gateways send them only toward
senders in their local enclave, not across the constrained long-haul
link. This lets a sender learn of an outage while the information is
still useful. A policy refusal does not depend on an outage. Agreement
on disclosure does not authenticate ICMP messages (<xref target="security"/>).</t>
    </section>
    <section anchor="conops">
      <name>Concept of Operations</name>
      <t>This section is informative. It describes a representative deployment:
an IP-based enclave in Mars orbit and on the Martian surface, connected
to terrestrial networks through scheduled deep-space contacts. Host
and application behaviors described here are illustrations of what the
signals make possible, not requirements (<xref target="consumers"/>).</t>
      <section anchor="scenario">
        <name>Reference Scenario</name>
        <t>The enclave consists of surface assets and orbiters interconnected by
conventional IP links, with propagation delays of milliseconds to low
seconds and continuous or near-continuous connectivity. Standard IP
routing and transports operate normally within it.</t>
        <t>The enclave connects to Earth through gateway nodes on relay orbiters
equipped with deep-space links. These links are scheduled: contacts
with ground stations occur in windows determined by orbital geometry
and antenna allocation, known in advance through a contact plan. They
are high-delay: one-way light time to Earth is roughly 3 to 22
minutes. And they are policy-managed: contact capacity is allocated to
specific senders or traffic classes, and traffic outside those
allocations is not authorized to use the link.</t>
        <t>A gateway may also offer a Bundle Protocol version 7 <xref target="RFC9171"/> or
application-layer gateway service that accepts traffic under its own
policy. The ICMP cases here concern packets refused or not forwarded
by the IP forwarding service; they do not describe traffic accepted
for delivery by a separate service. BP is not required for this ICMP
mechanism.</t>
        <t>The Provisioning Domain (PvD) option in IPv6 Router Advertisements
identifies a PvD and indicates whether PvD Additional Information is
available (<xref target="RFC8801"/>). Hosts can retrieve that information as a
JSON object over HTTPS, independently of ICMP.</t>
        <t>Future work could define JSON keys for local services, such as an
SMTP submission or relay service or a Bundle Protocol agent. This
would reuse PvD discovery without a new Router Advertisement option.
If the information and everything needed to retrieve it are available
within the enclave, hosts can consult it even during an external-link
outage. This document defines no service keys or application behavior
and does not require PvD support.</t>
        <t>The same structure exists on the Earth side. A terrestrial sender's
traffic crosses an Earth-side gateway that holds the same contact plan
and enforces its own admission policy, and that gateway generates the
same signals toward terrestrial senders. This section describes the
Mars side for concreteness.</t>
      </section>
      <section anchor="roles">
        <name>Roles</name>
        <t>Enclave hosts originate and receive application traffic. Some are
DTN-aware, running a BP agent or a stack extension that can hand
traffic to one; others are unmodified IP hosts, including legacy
instruments and commercial payloads whose stacks predate this
specification. Where a performance-enhancing proxy (PEP) terminates
transport sessions on behalf of such hosts, the PEP can consume these
signals for them, so that the mechanism's benefit need not depend on
universal host adoption.</t>
        <t>Gateways hold the managed-service knowledge for their deep-space
links, enforce admission and precedence policy on contact capacity,
and attach the objects defined in this document: availability
metadata on the unreachable error generated when admitted
trans-boundary traffic arrives while the link is not usable, and the
Denied by Link Policy object on the administrative prohibition error
generated when traffic arrives that policy does not admit.</t>
        <t>An orchestration function, which may be Earth-based, distributes
contact plans, routing updates, and admission policy to gateways in
advance (<xref target="orchestration"/>). It is intended to steer trans-boundary
traffic toward whichever gateway and link can serve it. Routing, link,
and policy updates are not installed atomically, however, and
distribution itself crosses the deep-space link; during transitions,
or when plan and reality diverge, a gateway may receive traffic that
another gateway could have served. Gateways operate autonomously
between management contacts on their most recent applicable knowledge
and omit assertions they cannot currently support (<xref target="generation"/>).</t>
        <t>Intra-enclave traffic is unaffected; hosts that never originate
trans-boundary traffic need not implement the objects.</t>
      </section>
      <section anchor="orchestration">
        <name>Orchestration Example</name>
        <t>This subsection illustrates one feasible path by which a gateway
obtains the knowledge on which it bases the objects. It describes
conceptual information, not a management protocol, data model, or
scheduling algorithm; any existing management channel, controller
interface, or local provisioning may carry it.</t>
        <t>Times in this example are expressed in the enclave time reference
(<xref target="gen-time"/>) as seconds from its epoch; the deployment has chosen
the reference, and nothing here depends on which one. The
orchestration function determines that traffic for a terrestrial
destination prefix should, for an upcoming period, leave the enclave
via a particular relay orbiter's deep-space link, whose next contact
begins at reference time 12,400 s. Allowing for antenna pointing,
acquisition, and modem configuration, it expects the link to be ready
to forward traffic at reference time 12,520 s, and it estimates the
one-way delay over the link at that time as 20 minutes. It installs
or schedules the routing and admission policy needed for that link,
and supplies an associated record. In this example, the gateway uses
the following information:</t>
        <ul spacing="normal">
          <li>
            <t>the traffic-to-service binding: the destination prefix and the
routing or policy context to which the record applies, associated
with the relevant link or next managed opportunity;</t>
          </li>
          <li>
            <t>a revision identifier or equivalent coherence mechanism, an
applicability period, and validity or expiry information;</t>
          </li>
          <li>
            <t>optionally, the expected data-plane-ready time, or a duration with
an explicit reference time;</t>
          </li>
          <li>
            <t>optionally, a directional one-way link-delay estimate applicable to
that opportunity; and</t>
          </li>
          <li>
            <t>the admission and disclosure policy that applies, together with
whatever local evidence the gateway has about the link's actual
usability.</t>
          </li>
        </ul>
        <t>Delivering this record is only part of the implementation. The
gateway's error-generation path must be able to consult it when
forwarding fails, including when the route to the destination has
been withdrawn between contacts and the failure is reported as a
no-route error. Any absolute time the controller supplies must either
be expressed in, or come with a known conversion into, the gateway's
enclave time reference (<xref target="gen-time"/>); alternatively the controller
may supply a duration anchored to a reference time the gateway can
interpret. A readiness time the gateway cannot relate to its own
reference is not a basis for ETU.</t>
        <t>At reference time 10,000 s, a packet for the prefix arrives at the
gateway. No usable route exists, so ordinary rules produce a
Destination Unreachable error. The gateway consults its record, finds
it current and applicable, confirms the traffic is admitted, and
attaches Generation Time (10,000 s), ETU (the interval from 10,000 s
to 12,520 s, 2,520,000 ms), and Expected Link Delay (1,200,000 ms).
Generation Time is the time the ICMP message was generated, not the
time the orchestrator created or distributed the plan.</t>
        <t>Several operational cases follow from this model, and
<xref target="operational"/> draws the corresponding lessons:</t>
        <ul spacing="normal">
          <li>
            <t>A later plan revision selects a different link or changes the
readiness estimate. Subsequent notifications use the current
applicable information; earlier notifications cannot be recalled.</t>
          </li>
          <li>
            <t>The planned readiness time passes but acquisition fails. The gateway
does not continue reporting a countdown clamped to zero; it either
has a newly supported estimate, or it omits ETU. An Expected Link
Delay that remains valid for the selected link need not be omitted.</t>
          </li>
          <li>
            <t>Controller connectivity is lost. A still-valid local record remains
usable unless contradicted by local evidence; when it expires or
becomes incoherent, the basis for the affected objects is gone and
they are omitted. Ordinary errors continue to be generated.</t>
          </li>
          <li>
            <t>Routing state and metadata revisions temporarily disagree, for
instance when a route has migrated to a second gateway but the
first gateway's record has not yet been updated. The gateway omits
assertions it cannot support rather than describing a service
opportunity other than the one applicable to the traffic.</t>
          </li>
        </ul>
      </section>
      <section anchor="use-cases">
        <name>Use Cases</name>
        <section anchor="uc-deferral">
          <name>Traffic Sent While the Link Is Unusable</name>
          <t>A surface host begins a bulk transfer toward Earth between contacts.
The first packet reaches the gateway, which drops it and returns a
Destination Unreachable error carrying an Expected Time Until Link
Usability object. From the object, the host knows that the domain
regards the path as transiently unavailable and roughly how long that
is expected to last; from the bare error alone it would know only that
the packet was not delivered. It might use the metadata to avoid
repeated attempts that would elicit the same error, and to tell the
application that the path is deferred rather than failed
(<xref target="consumers"/>).</t>
        </section>
        <section anchor="uc-handoff">
          <name>Reconsidering the Communication Mechanism</name>
          <t>An application that learns, from a Link Condition Object, that its
present IP traffic will be deferred for a long interval or was refused
by boundary-link admission policy may reconsider its end-to-end
communication options. A DTN-aware host might hand the affected
traffic to its local BP agent, which originates bundles toward the
destination for forwarding during the next contact. An application
with separately provisioned knowledge of an authorized
application-layer gateway might direct its traffic there. An
application with its own delay tolerance might instead compare the
expected wait against that tolerance and fail fast.</t>
          <t>The object is a trigger to reconsider, not a description of the
alternatives. Configuration, discovery, or provisioning supplies the
alternative mechanism and its authorization; the object does not prove
that another mechanism exists, is admitted, or will succeed, and it
does not require the application to change anything.</t>
        </section>
        <section anchor="uc-denied">
          <name>Traffic Denied by Link Policy</name>
          <t>A misconfigured or newly integrated payload host sends best-effort
traffic toward Earth during a contact whose capacity is allocated to
command and telemetry classes. The gateway classifies the traffic
against its local policy, which may consider DSCP, addresses, protocol
and port, or any other criteria, and drops it. Ordinary rules and
local response policy call for a Destination Unreachable, Communication
Administratively Prohibited error; the gateway attaches the Denied by
Link Policy object to it. From the object, the host learns that the
refusal came from the admission policy of the long-haul service
rather than from some other administrative control such as a
firewall; from the bare error it would know only that communication
was administratively prohibited. The object does not say why the
traffic was refused or what traffic would be admitted: admission
policy is multidimensional and local, and coaching senders on
acceptable markings would invert an admission model in which access
is granted through the control plane. The operator debugging the flow
consults the gateway's own logs and counters (<xref target="operational"/>);
obtaining admission is a provisioning action. The application may
reconsider its communication mechanism (<xref target="uc-handoff"/>).</t>
          <t>A contact can start with a flow admitted. To serve higher-precedence
traffic, the admission policy can later withdraw that flow's permission
to use the managed service. The gateway can attach the object if
ordinary ICMP rules and local response policy call for an
administrative prohibition error (<xref target="generation"/>).</t>
          <t>If the flow remains admitted, scheduling preference, queue overflow,
or congestion does not constitute refusal. An internal label such as
"preemption" or "resource allocation" does not determine whether the
object applies.</t>
        </section>
        <section anchor="uc-divergence">
          <name>Plan/Reality Divergence</name>
          <t>Notifications that conflict with the currently applicable service
expectation can be evidence of divergence between the control plane's
model and the data plane's state. Examples include ETU or ELD
reporting unavailability after expected data-plane readiness,
or a Denied by Link Policy object for traffic that installed policy
should admit. A planned contact alone does not establish readiness:
preparation may continue after contact start (<xref target="orchestration"/>).
Authorized traffic between contacts can legitimately elicit availability
metadata. Gateway counters provide diagnostic evidence, not proof of
failure (<xref target="operational"/>).</t>
        </section>
      </section>
      <section anchor="interaction">
        <name>Interaction of the Two Signals</name>
        <t>A sender can receive both signals for the same flow at different
times. If admission policy refuses a packet, the sender may receive an
administrative prohibition error with the Denied by Link Policy object.
If policy later admits the flow but the required link is still unusable,
its next packet may elicit an unreachable error with availability
metadata. The gateway checks admission before it discloses link state
(<xref target="generation"/>); <xref target="applicability-objects"/> lists the objects permitted
on each carrier group.</t>
        <t>An unreachable error alone does not establish permanent failure:
routing transients can cause it (<xref section="3.2.2.1" sectionFormat="of" target="RFC1122"/>), and
<xref target="RFC6069"/> used such errors experimentally to indicate disruption.</t>
      </section>
    </section>
    <section anchor="formats">
      <name>Message Formats and Extension Objects</name>
      <t>This section is normative. The Link Condition Object class is shown as
TBD5 pending IANA assignment (<xref target="iana"/>); prior to assignment,
experiments use a locally coordinated Private Use class as described
in <xref target="exp-scope"/>. The carrier codes of <xref target="carriers"/> are already
assigned, and this document requests no new ICMP type or code.</t>
      <section anchor="common">
        <name>Common Message Format</name>
        <t>The objects are carried in Destination Unreachable messages: ICMPv6
Type 1 <xref target="RFC4443"/> and ICMPv4 Type 3 <xref target="RFC0792"/>. <xref target="RFC4884"/> already
permits an ICMP Extension Structure on the existing Destination
Unreachable message types of both IP versions; no new type or code is
needed to carry the objects defined here. The message layout is the
extended Destination Unreachable message of <xref target="RFC4884"/>; this document
adds no fields. The Length field, original-datagram truncation and
padding, extension header, and checksum rules follow
<xref section="4" sectionFormat="of" target="RFC4884"/> and <xref section="7" sectionFormat="of" target="RFC4884"/>. Attaching
extension objects to Destination Unreachable is an established pattern
(<xref target="RFC4950"/>, <xref target="RFC5837"/>, <xref target="RFC8883"/>).</t>
        <figure anchor="fig-du">
          <name>Extended Destination Unreachable (ICMPv6 layout shown; ICMPv4 places Length in the second octet of the second word)</name>
          <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Type      |     Code      |            Checksum           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    Length     |                    Unused                     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~   As much of the invoking packet as possible, zero-padded    ~
|   per Section 4 of RFC 4884                                  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~              ICMP Extension Structure (RFC 4884)              ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
        <t>The objects add to a Destination Unreachable message; they never
change what its code means. A message that carries no Link Condition
Objects, whether because the gateway attached none or because the
receiver ignores or does not process extensions, is an ordinary
Destination Unreachable message and means only what its code has
always meant. Absence of an object supplies no inference: it does not
indicate that admission succeeded or failed, that a constrained
long-haul link was or was not involved, or that any prediction exists.
A message carrying no objects defined here need not carry an extension
structure at all, and an extension structure, when present, may also
carry other independently applicable <xref target="RFC4884"/> objects. Recognition
of a carrier code implies nothing about extension support; the
extension structure lies beyond the portion of the original datagram
that extension-unaware receivers examine.</t>
        <t>A receiver that processes extensions <bcp14>MUST</bcp14> ignore Link Condition
Objects with an unrecognized C-Type, and <bcp14>MUST</bcp14> process at most one
object of each C-Type per message, taking the first if several are
present. A receiver <bcp14>MUST</bcp14> ignore a Link Condition Object that is not
applicable to the received Destination Unreachable code
(<xref target="applicability-objects"/>), and <bcp14>MUST</bcp14> ignore a Link Condition Object
whose Length is not valid for its C-Type (<xref target="objects"/>). An
unrecognized, inapplicable, or invalid-length Link Condition Object
does not by itself invalidate the underlying ICMP error; this
tolerance does not extend to malformed extension framing or an invalid
extension checksum, which are handled per <xref target="RFC4884"/>.</t>
      </section>
      <section anchor="ltu">
        <name>Constrained Long-Haul Link Metadata on Destination Unreachable Errors</name>
        <t>When a gateway does not forward an otherwise admitted packet because
the constrained long-haul link required to reach its destination is
presently unusable, it generates whatever Destination Unreachable
error the ordinary rules of <xref target="RFC1812"/> or <xref target="RFC4443"/> call for,
according to its own forwarding state. This document does not change
which code is generated or when. It permits the gateway to attach
availability metadata -- the Generation Time, Expected Time Until Link
Usability, and Expected Link Delay objects -- to that error, subject
to the conditions in this section.</t>
        <t>A gateway <bcp14>MAY</bcp14> attach availability metadata to a Destination
Unreachable message only when all of the following hold:</t>
        <ul spacing="normal">
          <li>
            <t>the gateway holds a sufficiently current and applicable
managed-service association between the invoking traffic and a
constrained long-haul link, or next managed opportunity, within its
coordination scope;</t>
          </li>
          <li>
            <t>according to the current coordinated forwarding state, no other
policy-permitted path within the coordination scope is presently
available to serve that traffic;</t>
          </li>
          <li>
            <t>the traffic is admitted to that service;</t>
          </li>
          <li>
            <t>the link is presently unusable, and the managed-service knowledge
represents that unusability as a transient interruption of a
service that is intended to resume;</t>
          </li>
          <li>
            <t>the invoking packet was not forwarded; and</t>
          </li>
          <li>
            <t>the message's code is an eligible availability carrier code
(<xref target="carriers"/>).</t>
          </li>
        </ul>
        <t>The second condition is an assertion about the current managed
forwarding state for the affected traffic within the coordination
scope (<xref target="applicability"/>). The transient interruption may coincide
with absence of an installed route: a domain may withdraw the route
to a destination between contacts while retaining the managed-service
knowledge that explains the failure, and the resulting no-route error
is an eligible carrier. A gateway that meets these conditions but has
no estimate to supply, or withholds estimates by policy, sends the
ordinary error without the objects; the gateway need not know when
the condition will clear.</t>
        <t>These assertions are carried by the Expected Time Until Link Usability
and Expected Link Delay objects and attach to nothing else
(<xref target="common"/>). A Generation Time object supplies a timestamp and is not
by itself evidence of any particular cause of failure.</t>
        <section anchor="carriers">
          <name>Eligible Carrier Codes</name>
          <t>Link Condition Objects are applicable only to the Destination
Unreachable codes listed in this section, and each object is
applicable only to the carrier group indicated (<xref target="applicability-objects"/>).
Link Condition Objects <bcp14>MUST NOT</bcp14> be attached to other Destination
Unreachable codes or to other ICMP error types. In every case the code
is selected by existing ICMP rules according to the gateway's
forwarding state and response policy; this document neither alters
that selection nor redefines any code.</t>
          <section anchor="carriers-avail">
            <name>Availability Carriers</name>
            <t>The availability metadata objects (Generation Time, Expected Time
Until Link Usability, Expected Link Delay) may be carried on the
following codes.</t>
            <t>For ICMPv6, per <xref section="3.1" sectionFormat="of" target="RFC4443"/>:</t>
            <table anchor="tab-carriers-v6">
              <name>Eligible ICMPv6 Availability Carrier Codes</name>
              <thead>
                <tr>
                  <th align="right">Type 1 Code</th>
                  <th align="left">Name</th>
                  <th align="left">Eligibility</th>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td align="right">0</td>
                  <td align="left">No route to destination</td>
                  <td align="left">Eligible when the forwarding table lacks a matching entry for the destination and the gateway holds the managed-service knowledge required by <xref target="ltu"/>.</td>
                </tr>
                <tr>
                  <td align="right">3</td>
                  <td align="left">Address unreachable</td>
                  <td align="left">Eligible when the gateway retains a route whose required link is unusable and no more specific code applies. <xref target="RFC4443"/> names a link-specific problem as an example of this code.</td>
                </tr>
              </tbody>
            </table>
            <t>For ICMPv4, per <xref section="4.3.3.1" sectionFormat="of" target="RFC1812"/> and
<xref section="5.2.7.1" sectionFormat="of" target="RFC1812"/>:</t>
            <table anchor="tab-carriers-v4">
              <name>Eligible ICMPv4 Availability Carrier Codes</name>
              <thead>
                <tr>
                  <th align="right">Type 3 Code</th>
                  <th align="left">Name</th>
                  <th align="left">Eligibility</th>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td align="right">0</td>
                  <td align="left">Network unreachable</td>
                  <td align="left">Eligible when ordinary forwarding failure warrants Network Unreachable, such as absence of any route to the destination network.</td>
                </tr>
                <tr>
                  <td align="right">1</td>
                  <td align="left">Host unreachable</td>
                  <td align="left">Eligible when ordinary forwarding failure warrants Host Unreachable; see the IPv4 scope clarification below.</td>
                </tr>
              </tbody>
            </table>
            <t>A domain can withdraw a route between contacts and still retain
knowledge of the future service. In IPv6, if the gateway instead
retains the route but the required link is unusable, Address
Unreachable can apply when no more specific code applies.</t>
            <t>For IPv4, this specification defines no new code-selection rule for a
retained route whose required transit link is unusable. An otherwise
valid ICMPv4 Type 3 Code 0 or Code 1 error can carry availability
metadata when all conditions in <xref target="ltu"/> are met. Carrier eligibility
does not change when the gateway generates the underlying error. If
ordinary ICMP processing produces no eligible error, this specification
provides no availability-metadata notification for that case. A gateway
need not change the selected code or withdraw a route to obtain an
eligible carrier.</t>
          </section>
          <section anchor="carriers-policy">
            <name>Policy Carriers</name>
            <t>A gateway can attach the Denied by Link Policy object only if the
error it generates under ordinary ICMP rules uses a code listed below.
If ordinary processing selects another code, the gateway retains that
code and omits the object.</t>
            <table anchor="tab-carriers-policy">
              <name>Eligible Policy Carrier Codes</name>
              <thead>
                <tr>
                  <th align="left">IP version</th>
                  <th align="right">Type</th>
                  <th align="right">Code</th>
                  <th align="left">Existing meaning</th>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td align="left">IPv4</td>
                  <td align="right">3</td>
                  <td align="right">13</td>
                  <td align="left">Communication Administratively Prohibited (<xref section="5.2.7.1" sectionFormat="of" target="RFC1812"/>)</td>
                </tr>
                <tr>
                  <td align="left">IPv6</td>
                  <td align="right">1</td>
                  <td align="right">1</td>
                  <td align="left">Communication with destination administratively prohibited (<xref section="3.1" sectionFormat="of" target="RFC4443"/>)</td>
                </tr>
              </tbody>
            </table>
            <t><xref target="RFC4443"/>'s reference to a firewall filter is an example of
administrative prohibition, not an exclusive definition. The object
identifies boundary-link admission policy as the particular
administrative control that refused the packet; it does not introduce
a different meaning for the base code.</t>
          </section>
        </section>
      </section>
      <section anchor="objects">
        <name>Extension Objects</name>
        <t>The objects below share a single ICMP Extension Object class, the Link
Condition Object class (Class-Num TBD5), distinguished by C-Type. The
object header is as defined in <xref section="8" sectionFormat="of" target="RFC4884"/>. No object is
mandatory. Which objects a message may carry depends on the
Destination Unreachable code it reports (<xref target="applicability-objects"/>);
within that set, each object is optional and absence means only that
the gateway did not supply that information (<xref target="common"/>). No sentinel
values are defined for absent data. Because the class includes both
availability metadata and a policy indication, each assertion in this
document is attributed to the specific object that carries it.</t>
        <t>Each object has exactly one valid Length: 12 octets for Generation
Time, 8 for Expected Time Until Link Usability and Expected Link
Delay, and 4 for Denied by Link Policy. A receiver <bcp14>MUST</bcp14> ignore a Link
Condition Object whose Length does not match the value for its C-Type
(<xref target="common"/>).</t>
        <t>The two duration objects, Expected Time Until Link Usability and
Expected Link Delay, are defined and encoded independently of the
Generation Time object. Their interpretation does not depend on the
absolute timestamp representation, so that representation could later
be revised or superseded without changing them.</t>
        <section anchor="durations">
          <name>Duration Format</name>
          <t>Both duration objects carry an unsigned 32-bit integer count of
milliseconds. Millisecond precision is not intrinsically necessary for
every value of Expected Time Until Link Usability, but a single
representation for both duration-valued objects reduces
implementation complexity and the risk of unit-conversion errors.
<xref target="RFC4884"/> defines the extension object framework but no duration
datatype; the representation is defined here.</t>
          <t>The maximum representable duration, 0xFFFFFFFF milliseconds, is
4,294,967.295 seconds, approximately 49.7 days. It is a valid finite
value, not a sentinel. If an otherwise available estimate exceeds the
maximum representable duration, the corresponding object <bcp14>MUST NOT</bcp14> be
included. No value is reserved to mean infinite, unknown, or greater
than the maximum, and no saturation is defined; absence of an object
means only that no representable estimate was supplied, and the
protocol does not distinguish an unknown estimate from one that is
known but not representable.</t>
        </section>
        <section anchor="gen-time">
          <name>Generation Time</name>
          <figure anchor="fig-gen-time">
            <name>Generation Time Object</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Length = 12           |  Class-Num =  |  C-Type = 1   |
|                               |     TBD5      |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                       Generation Time                         +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t>Generation Time is the gateway's reading of the applicable enclave
time reference at the moment it generated the ICMP message. It is the
time of the notification, not the time at which any underlying plan
was created or distributed, and not an arbitrary device-local clock.</t>
          <t>Following the timestamp specification template of
<xref section="3" sectionFormat="of" target="RFC8877"/>, this document fixes the timestamp syntax and
units and leaves the remaining semantics to the deployment:</t>
          <dl>
            <dt>Size:</dt>
            <dd>
              <t>64 bits in network byte order: a 32-bit unsigned count of whole
seconds followed by a 32-bit unsigned binary fraction of a second.</t>
            </dd>
            <dt>Units and resolution:</dt>
            <dd>
              <t>seconds and 2^-32 seconds respectively; 1,000 milliseconds per
second, consistent with the duration objects. No planetary or
calendar units are used on the wire.</t>
            </dd>
            <dt>Wraparound:</dt>
            <dd>
              <t>the seconds field wraps every 2^32 seconds. No era number is
carried; era resolution is performed against the applicable enclave
time reference, not against an implicit wall clock.</t>
            </dd>
            <dt>Epoch, time scale, and leap seconds:</dt>
            <dd>
              <t>supplied by the enclave time reference. The specification or
provisioning of the managed deployment <bcp14>MUST</bcp14> establish the time
scale, epoch, treatment of discontinuities such as leap seconds or
clock resets, and era or wraparound interpretation, and <bcp14>MUST</bcp14> define
the relationship needed to interpret elapsed seconds so that
Generation Time can be combined with ETU. Choosing an epoch alone
does not settle time-scale or discontinuity behavior. UTC with a
conventional epoch is one permitted choice; it is not a protocol
prerequisite, and this document does not presuppose the time scale
a future deployment will adopt.</t>
            </dd>
            <dt>Synchronization aspects:</dt>
            <dd>
              <t>a receiver <bcp14>MAY</bcp14> use Generation Time for a calculation only when it
knows the applicable enclave time reference and can relate it to
its own clock with confidence sufficient for that calculation. A
shared time-scale name alone does not establish clock
synchronization, and a common orchestration function is not by
itself evidence of a shared reference or a known conversion;
cooperating administrative domains need one or the other before
their receivers compare timestamps. Where the reference, the
conversion, the era, or the effect of a clock discontinuity is
unknown or ambiguous, the receiver ignores Generation Time for that
calculation. No synchronization accuracy is required by this
document and no synchronization protocol is specified.</t>
            </dd>
          </dl>
          <t>The seconds/fraction layout is the same as the 64-bit timestamp
format of <xref section="6" sectionFormat="of" target="RFC5905"/>, and implementations may reuse
code that handles it. Reusing the layout is separate from adopting
NTP's timestamp semantics: the NTP epoch, the UTC time scale, and
NTP's era conventions are not imported by this document, and apply
only where a deployment selects them as its enclave time reference.
No time-scale identifier or negotiation is carried in this version;
the applicable reference is established through the managed
deployment context. Reference changes and clock resets require
operational handling so that receivers do not unknowingly interpret
timestamps generated under one reference using another
(<xref target="operational"/>).</t>
          <t>Generation Time identifies when the notification and any estimates in
it were generated. It is principally intended to allow a receiver that
can interpret it to account for the time elapsed since an accompanying
ETU estimate was generated (<xref target="etu"/>). A receiver that cannot interpret
it ignores it; nothing else in the message depends on it, it remains
independently parseable, and ignoring it does not invalidate ETU, any
other applicable object, or the ordinary ICMP error. In the absence of
ETU this document defines no use for Generation Time, so a message
<bcp14>SHOULD NOT</bcp14> include Generation Time unless it also includes ETU
(<xref target="applicability-objects"/>).</t>
        </section>
        <section anchor="etu">
          <name>Expected Time Until Link Usability</name>
          <figure anchor="fig-etu">
            <name>Expected Time Until Link Usability Object</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Length = 8           |  Class-Num =  |  C-Type = 2   |
|                               |     TBD5      |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|              Expected Time Until Link Usability               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t>Expected Time Until Link Usability (ETU) is the gateway's estimate, at
the moment it generated the notification, of the interval from
generation until the constrained long-haul link selected for the
invoking traffic is expected to become usable for forwarding it. It is
an unsigned 32-bit integer count of milliseconds, in the format of
<xref target="durations"/>. ETU refers to expected data-plane usability, not to the
start of a scheduled contact or of preparation for one. Preparatory
operations necessary to make the link usable, such as antenna
pointing, modem configuration, acquisition, synchronization, or
analogous link-establishment operations, are expected to have
completed by the end of the reported interval and are not represented
separately.</t>
          <t>ETU is measured from notification generation, not from receipt. It is
an estimate, not a guarantee. It is not a retry interval and not an
instruction to transmit at any particular time. It does not include
Expected Link Delay, which describes traversal of the link once
usable. When ETU and Expected Link Delay appear in the same message
they <bcp14>MUST</bcp14> describe the same link or managed opportunity; a gateway
<bcp14>MUST NOT</bcp14> combine the earliest usability of one exit with the delay of
another.</t>
          <t>ETU is meaningful on its own. A receiver that can interpret a supplied
Generation Time against the enclave time reference (<xref target="gen-time"/>) may
compute the expected usability time in that reference as Generation
Time + ETU, and may thereby account for the time the notification
spent in delivery; any era or wraparound considerations apply only to
that interpretation and are resolved against the enclave reference. A
receiver without Generation Time, or unable to interpret it, may apply
ETU from the moment of receipt.
Doing so is a conservative interpretation of the same forecast: it
expires no earlier than the forecast itself, and later by however long
the notification spent in delivery. It is not a guarantee about the
link; actual recovery may occur later than either interpretation, or
earlier. This document does not assume that ICMP delivery is prompt.</t>
          <t>The finite range of <xref target="durations"/> provides a practical horizon for
this experimental network-layer signal. Unavailability on longer
timescales is not represented by ETU; such timescales may instead
bear on broader application, storage, provisioning, or
communication-mechanism decisions, which this document does not
address.</t>
        </section>
        <section anchor="eld">
          <name>Expected Link Delay</name>
          <figure anchor="fig-eld">
            <name>Expected Link Delay Object</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Length = 8           |  Class-Num =  |  C-Type = 3   |
|                               |     TBD5      |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     Expected Link Delay                       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t>Expected Link Delay is the approximate one-way delay associated with
traversal of the constrained long-haul link selected for the invoking
traffic -- the link whose unavailability prevented forwarding or, where
routing has migrated the traffic, the next managed opportunity that ETU
describes -- as an unsigned 32-bit integer count of milliseconds in the
format of <xref target="durations"/>. It is an estimate, not a bound; a quantity of
the link, not an end-to-end path delay; and independent of ETU and of
Generation Time. This document does not require receivers to combine it
with other metadata or otherwise compute an end-to-end delivery time;
how the estimate is used is a matter of endpoint and application policy.</t>
          <t>For perspective only, the maximum representable duration, if it were
pure propagation delay at the speed of light in vacuum, would
correspond to a distance of approximately 1.29 x 10^12 km, roughly
1.29 trillion km. The range is therefore very large even for the
long-delay environments that motivate this document. This observation
is explanatory; Expected Link Delay remains an estimated one-way link
delay comprising whatever components contribute to it.</t>
        </section>
        <section anchor="dlp">
          <name>Denied by Link Policy</name>
          <figure anchor="fig-dlp">
            <name>Denied by Link Policy Object</name>
            <artwork><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Length = 4           |  Class-Num =  |  C-Type = 4   |
|                               |     TBD5      |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
          </figure>
          <t>The Denied by Link Policy object consists of the object header alone;
it has no payload, and its Length is exactly 4. It is carried only on
the policy carrier codes of <xref target="carriers-policy"/>.</t>
          <t>Its presence asserts that the invoking packet was not forwarded
because the applicable admission policy for the managed long-haul
service refused it, independently of the current usability of any
link. Presence alone supplies this classification; there is no
Boolean, denial-reason field, allocation identifier, alternate
gateway address, or retry time, and this document defines no way to
convey why the traffic was refused or what would be admitted
(<xref target="uc-denied"/>). An error conveys this classification only when it
contains a valid, applicable Denied by Link Policy object; an object
of any other length does not establish it (<xref target="common"/>), and absence
of the object does not establish that the refusal came from some
other control, that no boundary-link policy exists, or that the
application has no alternatives.</t>
          <t>For traffic that remains admitted, congestion, queue overflow, or
scheduling competition does not justify attaching this object
(<xref target="uc-denied"/>).</t>
          <t>Generating the object is optional and subject to disclosure policy
(<xref target="generation"/>). Its presence does not promise permanent denial,
prove that waiting could never help, require the receiver to change
mechanisms, or authorize evading policy.</t>
        </section>
      </section>
      <section anchor="applicability-objects">
        <name>Object Applicability by Code</name>
        <t>Each Link Condition Object is applicable to one group of carrier
codes, as summarized in <xref target="tab-applicability"/>. Availability carriers
are ICMPv4 Type 3 codes 0 and 1 and ICMPv6 Type 1 codes 0 and 3
(<xref target="carriers-avail"/>); policy carriers are ICMPv4 Type 3 code 13 and
ICMPv6 Type 1 code 1 (<xref target="carriers-policy"/>).</t>
        <table anchor="tab-applicability">
          <name>Link Condition Object Applicability by Carrier Group</name>
          <thead>
            <tr>
              <th align="left">Object</th>
              <th align="left">Availability carriers</th>
              <th align="left">Policy carriers</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Generation Time (C-Type 1)</td>
              <td align="left">
                <bcp14>MAY</bcp14>; <bcp14>SHOULD NOT</bcp14> without ETU</td>
              <td align="left">
                <bcp14>SHOULD NOT</bcp14>; no use defined here without ETU</td>
            </tr>
            <tr>
              <td align="left">Expected Time Until Link Usability (C-Type 2)</td>
              <td align="left">
                <bcp14>MAY</bcp14>, subject to <xref target="ltu"/></td>
              <td align="left">
                <bcp14>MUST NOT</bcp14></td>
            </tr>
            <tr>
              <td align="left">Expected Link Delay (C-Type 3)</td>
              <td align="left">
                <bcp14>MAY</bcp14>, subject to <xref target="ltu"/></td>
              <td align="left">
                <bcp14>MUST NOT</bcp14></td>
            </tr>
            <tr>
              <td align="left">Denied by Link Policy (C-Type 4)</td>
              <td align="left">
                <bcp14>MUST NOT</bcp14></td>
              <td align="left">
                <bcp14>MAY</bcp14>, subject to <xref target="generation"/></td>
            </tr>
          </tbody>
        </table>
        <t>A policy carrier <bcp14>MUST NOT</bcp14> carry Expected Time Until Link Usability or
Expected Link Delay: they reveal characteristics of a link to which
the invoking traffic was not admitted, and admission is evaluated
before any link state is disclosed (<xref target="generation"/>). An availability
carrier <bcp14>MUST NOT</bcp14> carry Denied by Link Policy. Under these rules
Denied by Link Policy is never emitted with ETU or ELD. Generation Time
may accompany it, subject to the guidance below.</t>
        <t>Generation Time <bcp14>SHOULD NOT</bcp14> be sent without Expected Time Until Link
Usability on either carrier group, since this document defines no
other use for it and unnecessary absolute-time information should not
normally be disclosed. This is discouraged rather than inapplicable or
prohibited: a receiver that finds Generation Time without ETU simply
has no defined use for it, and experimentation or later experience
may identify one.</t>
        <t>These are sender restrictions; receiver tolerance for inapplicable
objects is specified in <xref target="common"/> and does not relax them.</t>
      </section>
    </section>
    <section anchor="generation">
      <name>Generation Rules</name>
      <t>The rules in this section govern gateways. General ICMP generation
rules apply in addition: <xref section="2.4" sectionFormat="of" target="RFC4443"/> for ICMPv6,
including its rate-limiting requirements, and <xref target="RFC1812"/> for ICMPv4.
Nothing in this document permits generating an error in response to
an ICMP error, to a packet addressed to a multicast destination, or
in the other cases those documents prohibit. Nothing in this document
suppresses a Destination Unreachable error that those documents
otherwise require, and uncertainty about whether an optional object
can be supported never suppresses the underlying error.</t>
      <t>This specification does not define congestion signaling. A gateway
<bcp14>MUST NOT</bcp14> generate a Destination Unreachable error only to report
congestion or to carry a Link Condition Object. In particular,
<xref section="3.1" sectionFormat="of" target="RFC4443"/> prohibits generating an ICMPv6 message when
the invoking packet is dropped because of congestion.</t>
      <t>On receiving trans-boundary traffic, a gateway proceeds as follows:</t>
      <ol spacing="normal" type="1"><li>
          <t>Assess the current coordinated forwarding and service state for
the traffic, including whether a policy-permitted path within the
coordination scope is presently available to serve it. If so, use
that path and attach nothing.</t>
        </li>
        <li>
          <t>Apply the long-haul service's admission policy before disclosing
any link state or prediction.</t>
        </li>
        <li>
          <t>If the traffic is not admitted, drop it. Generate an error only as
called for by ordinary ICMP rules and local response policy. If the
error uses an eligible policy carrier (<xref target="carriers-policy"/>) and
disclosure policy permits, the gateway may attach the Denied by Link
Policy object (<xref target="applicability-objects"/>). If ordinary processing
selects another code, retain it and omit the object. Denial of admission
to one long-haul service does not by itself mean no policy-permitted
managed alternative exists; step 1 addresses that.</t>
        </li>
        <li>
          <t>If the traffic is admitted but cannot be forwarded because the
selected link is presently unusable, drop it and generate the
Destination Unreachable error that ordinary ICMP rules call for. If
the conditions of <xref target="ltu"/> are satisfied and the code is an eligible
availability carrier (<xref target="carriers-avail"/>), the gateway <bcp14>MAY</bcp14> attach
Expected Time Until Link Usability, Generation Time, and Expected
Link Delay objects.</t>
        </li>
        <li>
          <t>If the traffic is admitted and the link is usable, forward it
normally. A forwarded packet <bcp14>MUST NOT</bcp14> elicit a Destination
Unreachable error.</t>
        </li>
      </ol>
      <t>The restrictions in this section govern attaching Link Condition
Objects; they do not alter when ordinary Destination Unreachable
errors are generated. A gateway <bcp14>MUST NOT</bcp14> attach any Link Condition
Object whose assertion it cannot establish from a sufficiently current
and applicable association between the traffic, the managed service,
the forwarding state, the admission policy, and any advertised
prediction (<xref target="orchestration"/>). In particular, a gateway <bcp14>MUST NOT</bcp14>
attach availability metadata when another policy-permitted path within
the coordination scope is presently available for the traffic, and
<bcp14>MUST NOT</bcp14> attach it on the basis of observed local interface or carrier
state alone (<xref target="applicability"/>). Whenever an object's basis is
missing, the object is withheld by policy, or an estimate is out of
range (<xref target="durations"/>), the gateway omits that object and sends the
ordinary error.</t>
      <t>A gateway <bcp14>MUST NOT</bcp14> send an ETU value not derived from its current
managed-service knowledge, and <bcp14>MUST NOT</bcp14> report an expired estimate
clamped to zero. A gateway <bcp14>MAY</bcp14> send ETU without Generation Time; it
<bcp14>SHOULD NOT</bcp14> send Generation Time without ETU
(<xref target="applicability-objects"/>).</t>
      <t>An operator <bcp14>MUST</bcp14> be able to control disclosure of each Link Condition
Object independently of whether the gateway sends the underlying error
(<xref target="security"/>). For refused traffic, the operator <bcp14>MUST</bcp14> be able to select
silent discard or an administrative prohibition error where ordinary
ICMP rules permit that choice. Policy can use criteria such as source,
prefix, or traffic class.</t>
      <t>A gateway <bcp14>MUST NOT</bcp14> attach Link Condition Objects to messages sent
toward the constrained long-haul link, and <bcp14>MUST NOT</bcp14> attach them in
response to traffic arriving from it (<xref target="applicability"/>).</t>
      <t>A gateway <bcp14>MUST NOT</bcp14> assume that a sender received an earlier
notification. If it attaches objects to a later error, it uses its
current applicable knowledge.</t>
    </section>
    <section anchor="receiver">
      <name>Receiver Processing</name>
      <section anchor="validation">
        <name>Validation</name>
        <t>Ordinary validation and handling of a Destination Unreachable error
are governed by the receiver's existing ICMP and transport rules; this
document does not change them, and the checks below apply only to the
objects. Disregarding an object never requires rejecting, or changing
the ordinary handling of, the base error.</t>
        <t>Before acting on Link Condition Objects, a receiver <bcp14>MUST</bcp14> validate the
message as an ICMP error per <xref target="RFC4443"/> and the mitigations of
<xref target="RFC5927"/>: the invoking packet excerpt is matched against existing
connection or flow state, and objects on a message matching nothing
the receiver sent are disregarded. A receiver <bcp14>SHOULD</bcp14> disregard Link
Condition Objects on a message that arrives on an interface facing
outside its disclosure scope.</t>
        <t>The carrier code does not prove that a message originated inside the
domain, and a filter that acts on Type and Code alone cannot
selectively remove Link Condition Objects without also affecting
ordinary errors of the same code. A deployment that requires selective
containment of the objects at a boundary needs extension-aware
enforcement; this document does not specify one and does not mandate
filtering of the carrier codes.</t>
      </section>
      <section anchor="consumers">
        <name>Consumer Behavior</name>
        <t>This section is informative. The examples below describe possible
uses of the objects. None of these responses is required for
interoperability.</t>
        <t>A host might record availability metadata to avoid immediately
repeating attempts likely to elicit the same error. How such state
would be keyed, how widely it would apply, how long it would live, how
it would be invalidated when the domain's knowledge changes, and how
it would interact with routing are all open questions. Because ETU is
an estimate reflecting the domain's coordinated state at generation
time, and the gateway cannot revoke a notification, any such state is
a hint and not an assurance of service at any later time.</t>
        <t>A transport might use the metadata as an input to its timeout and
failure decisions, for example by comparing the expected wait against
a connection's tolerance. The remote endpoint receives no
corresponding notification and continues to run its own timers, which
bounds the usefulness of waiting. No TCP or QUIC behavior is defined
here.</t>
        <t>An application that can match an indication to its traffic might
wait, report failure, or reconsider its communication mechanism
(<xref target="uc-handoff"/>). To compare its options, it could consult service
information obtained separately. For example, <xref target="scenario"/> describes
how future service descriptions could use PvD Additional Information
(<xref target="RFC8801"/>). The ICMP indication neither identifies an alternative
service nor grants access to one. This document does not define an
application interface.</t>
        <t>Stronger reactions to unauthenticated ICMP information carry greater
risk (<xref target="security"/>); which reactions are worth their risk is itself an
experiment question.</t>
      </section>
    </section>
    <section anchor="legacy">
      <name>Legacy Host and Middlebox Behavior</name>
      <t>A receiver that ignores the <xref target="RFC4884"/> extension objects can still
process the underlying Destination Unreachable error (<xref target="common"/>).
How it responds to that error depends on the implementation.</t>
      <t>For context, <xref section="3.9.2.2" sectionFormat="of" target="RFC9293"/> classifies the
availability carriers (ICMPv4 Type 3 codes 0 and 1, ICMPv6 Type 1
codes 0 and 3) as soft errors for TCP, while noting widespread
implementation behavior that treats soft errors as hard errors during
connection establishment; <xref target="RFC5461"/> documents further divergence.
This classification describes existing TCP processing; it is not the
basis on which this document selects carriers and does not define
permanent versus temporary failure. This document neither prescribes
nor relies on a particular TCP reaction to either policy carrier.</t>
      <t>Firewalls and stateful middleboxes inside the deploying domain may
strip or discard messages carrying unfamiliar extension structures, or
may already filter some Destination Unreachable codes. This fails
safe but silently defeats the mechanism, so deployment includes
reviewing ICMP filtering policy on the paths between gateways and the
hosts they serve; <xref target="RFC4890"/> provides the ICMPv6 filtering framework.
Legacy hosts generate nothing new and are unaffected as senders.</t>
    </section>
    <section anchor="operational">
      <name>Operational Considerations</name>
      <t>Gateways <bcp14>SHOULD</bcp14> count generation of object-bearing Destination
Unreachable messages, including which Link Condition Objects were
included, and expose the counters through network management; counts
of the carrier codes alone do not identify this experiment's activity,
since those codes are generated for other reasons as well. If the
gateway knows why admission policy refused the packet, it <bcp14>MAY</bcp14> report
that reason in local telemetry. The Denied by Link Policy object does
not carry the reason. This document does not
prescribe a management or telemetry mechanism. Operators can use the
counters as diagnostic evidence of possible divergence from applicable
service expectations, not as proof of failure (<xref target="uc-divergence"/>).</t>
      <t>After a plan or route change, a gateway may have no current estimate
for the selected link (<xref target="orchestration"/>). It can still send the
ordinary ICMP error. The absence of an estimate does not by itself
indicate a fault in the gateway or its controller.</t>
      <t>When a contact ends, many flows can fail at once. ICMP rate limiting
may prevent some senders from receiving a notification.</t>
      <t>ETU is only as meaningful as the gateway's knowledge of the link.
Using Generation Time additionally depends on the receiver knowing the
enclave time reference and being able to relate it to its own clock
(<xref target="gen-time"/>); receivers that cannot may apply ETU from receipt
(<xref target="etu"/>). The deployment is responsible for establishing and
distributing the reference. When the reference changes or a gateway's
clock is reset, operators need to ensure that receivers do not
interpret timestamps generated under the old reference using the new
one; until that is assured, receivers fall back to ignoring Generation
Time. Cooperating administrative domains need a shared reference or a
known conversion before their receivers compare timestamps; sharing an
orchestration function does not by itself provide either.</t>
      <t>If a host uses stored metadata to delay another attempt, exposing
that state to local diagnostics can help an operator explain the delay.</t>
    </section>
    <section anchor="experiment">
      <name>Experimental Status and Goals</name>
      <t>This experiment asks two questions. Can gateways generate the objects
under the conditions specified in <xref target="generation"/>? Do consumers make
better decisions when they receive the objects than when they receive
the same ICMP errors without them? This document specifies the objects
for interoperability. It does not prescribe a consumer response
(<xref target="consumers"/>).</t>
      <section anchor="exp-scope">
        <name>Scope of the Experiment</name>
        <t>The experiment runs within domains meeting the criteria of
<xref target="applicability"/>: space networking testbeds and missions, other
networks with scheduled or intermittently available managed links
between enclaves, and laboratory emulations of the same topologies.
Link Condition Objects are not intended to be exchanged across
uncontrolled networks (<xref target="validation"/>). No behavior in this document
affects hosts whose traffic never requires a trans-boundary link.</t>
        <t>Prior to IANA assignment of the Link Condition Object class,
experiments use a class value from the Private Use range 247-255 of
the "ICMP Extension Object Classes and Class Sub-types" registry
<xref target="RFC4884"/>, with its interpretation and scope explicitly configured
among the participants. Such a value is not globally unique, is not a
claim on any permanent assignment, and is used only within the
experiment's coordination scope. The carrier codes are already
assigned and are used as is; no experimental ICMP type or code is
involved. Interoperability reports from this phase are in scope for
the experiment.</t>
      </section>
      <section anchor="exp-signal">
        <name>Network Signal Evaluation</name>
        <t>The first layer of the experiment concerns the objects themselves:</t>
        <ul spacing="normal">
          <li>
            <t>Generation correctness: whether gateways attach each object only
under the conditions of <xref target="generation"/>, whether the
coordination-scope determination can be made reliably in deployed
routing architectures and during transitions, and which carrier
codes gateways actually produce for the long-haul conditions in each
IP version (<xref target="carriers"/>).</t>
          </li>
          <li>
            <t>Information beyond the carrier code: does it help to know that an
outage is transient, or that boundary-link admission policy refused
the packet (<xref target="interaction"/>)? For policy refusals, does experience
show a need for more detail than the object provides?</t>
          </li>
          <li>
            <t>Prediction accuracy and usefulness: how closely ETU tracks actual
link usability, how often it is available at all, how often plan
revisions or acquisition failures invalidate it, and whether
Generation Time and Expected Link Delay are populated and used.</t>
          </li>
          <li>
            <t>Orchestration feasibility: whether the information path of
<xref target="orchestration"/> can be realized with existing management channels,
and whether gateways can consult applicable records on the
error-generation path, including after route withdrawal.</t>
          </li>
          <li>
            <t>Generation rate: gateway ICMP generation rates at gap onset under
realistic fan-out, and the effect of rate limiting on which senders
receive a notification.</t>
          </li>
          <li>
            <t>Legacy and middlebox behavior: how unmodified hosts respond to
object-bearing carrier errors across the stacks present in target
environments, including embedded and flight-heritage
implementations (<xref target="legacy"/>); and what filtering changes deployments
required, including whether middleboxes strip or discard extension
structures.</t>
          </li>
          <li>
            <t>Security and disclosure: whether the information disclosed by the
objects is operationally acceptable, whether the disclosure controls
of <xref target="generation"/> are sufficient, and whether forged or stale
objects caused harm.</t>
          </li>
        </ul>
      </section>
      <section anchor="exp-questions">
        <name>Consumer Behavior Exploration</name>
        <t>The second layer concerns what receivers do with the objects. None of
these behaviors is specified here; the experiment is intended to
discover which are worthwhile:</t>
        <ul spacing="normal">
          <li>
            <t>Whether hosts that record availability metadata to avoid repeated
attempts reduce futile retransmission and offered load during
link-unavailable periods, relative to hosts receiving the same
ordinary errors without objects, and what keying, scope, lifetime,
and invalidation rules work.</t>
          </li>
          <li>
            <t>What transport reactions are appropriate, including whether
comparing expected wait against connection tolerance is useful and
whether connections that wait survive the peer's own timers.</t>
          </li>
          <li>
            <t>Whether applications can receive and correlate the objects with
their traffic at all, and whether the Denied by Link Policy
classification improves their decisions relative to an ordinary
administrative prohibition error, including selection among
separately provisioned mechanisms such as IP transports,
application-layer gateways, and bundle services.</t>
          </li>
          <li>
            <t>Whether provisioning and orchestration systems can use the objects,
and whether divergence telemetry (<xref target="uc-divergence"/>) exposed real
faults ahead of existing monitoring.</t>
          </li>
        </ul>
      </section>
      <section anchor="exp-criteria">
        <name>Evidence for Advancement</name>
        <t>The following evidence could inform later consideration for the
standards track:</t>
        <ul spacing="normal">
          <li>
            <t>At least two independent implementations interoperate on both
carrier groups.</t>
          </li>
          <li>
            <t>Gateways generate the objects accurately in at least one
operational domain outside the laboratory.</t>
          </li>
          <li>
            <t>Each object retained for the standards track provides information
that is useful beyond the ordinary error alone.</t>
          </li>
          <li>
            <t>Tests with legacy hosts and middleboxes show manageable effects.
Security and disclosure risks are acceptable.</t>
          </li>
          <li>
            <t>Independent tests show a benefit to consumers without assuming a
particular receiver strategy.</t>
          </li>
          <li>
            <t>The same semantics and wire format serve more than one class of
long-haul network.</t>
          </li>
        </ul>
        <t>Reports of failed or inconclusive experiments are as useful as
reports of successful ones.</t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>ICMP carries no authentication, and the objects are actionable by
implementations that choose to act on them, so the principal threats
are forgery by off-path attackers and information disclosure to the
senders these messages answer. The mitigations are the scoping of
<xref target="applicability"/>, validation against sender state (<xref target="validation"/>),
rate limiting, and agreed disclosure policy among the cooperating
authorities. None of them authenticates the carrier code or the
objects; filtering and invoking-packet validation raise the cost of
injection without confining it to trusted parties, and none is
dependable across the open internet.</t>
      <t>Three forgery cases arise. A forged ordinary Destination Unreachable
or administrative prohibition error is an existing threat with
existing mitigations (<xref target="RFC5927"/>); this document does not change it.
Forged availability metadata on an otherwise plausible error could
induce an implementation that acts on it to withhold trans-boundary
traffic for the advertised interval. A forged Denied by Link Policy
object could induce an application to abandon a working IP path for
another mechanism, or to conclude that provisioning is needed; this
influence on application choices is a capability beyond what forging
the bare administrative prohibition error provides. This document does
not require receivers to act on any object, and stronger reactions to
unauthenticated ICMP information carry correspondingly greater risk;
an implementation that does act should bound the effect of any single
notification, treat ETU as an estimate that may be stale or wrong,
treat Denied by Link Policy as a classification that may be forged,
and consider that the gateway cannot revoke a notification whose basis
has changed.</t>
      <t>Because the objects ride on ordinary codes, containing them at a
boundary requires extension-aware enforcement (<xref target="validation"/>). The
absence of Link Condition Objects from a message is not a trustworthy
indication that no long-haul condition exists (<xref target="common"/>), since
objects may be omitted by policy, by rate limiting, by middleboxes, or
by an attacker.</t>
      <t>The Denied by Link Policy object, although it has no payload,
discloses that boundary-link admission policy refused particular
traffic, and a gateway that attaches it is a probing oracle: an
attacker varying markings, sources, and destinations can map which
traffic the long-haul service admits, even without being told why any
particular packet was refused. <xref target="generation"/> therefore requires
per-policy control over whether the object is attached and,
independently, whether the base error is generated at all; toward any
sender the operator does not trust, silent discard is the expected
posture, consistent with existing firewall practice.</t>
      <t>The availability metadata objects disclose link schedule information,
which in some deployments is sensitive operational information.
<xref target="generation"/> permits omitting them per policy; operators of such
deployments should protect the metadata as they protect the underlying
schedule. Evaluating admission before link state (<xref target="generation"/>)
prevents disclosure of schedule information to traffic that would not
be admitted regardless.</t>
      <t>Ordinary ICMP generation restrictions and rate limiting
(<xref section="2.4" sectionFormat="of" target="RFC4443"/>, <xref target="RFC1812"/>) apply to all of these
messages. Quoting and padding of the invoking packet and the optional
objects affect response size; a message carrying all three
availability objects is larger than a minimal Destination Unreachable
error. This document makes no claim about the absence of amplification
beyond what those restrictions provide.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document requests no new ICMP type and no new Destination
Unreachable code. It requests one assignment, shown as a TBD value
throughout; no numeric value is proposed.</t>
      <t>From the "ICMP Extension Object Classes and Class Sub-types" registry
<xref target="RFC4884"/>: a new class TBD5, Link Condition Object, with C-Type 1,
Generation Time; C-Type 2, Expected Time Until Link Usability; C-Type
3, Expected Link Delay; and C-Type 4, Denied by Link Policy, assigned
by this document. Further C-Types are Specification Required. The
class registry's procedure is First Come First Served for values
0-246.</t>
      <t>This document requests no change to the already-assigned Destination
Unreachable codes on which Link Condition Objects may be carried:
ICMPv6 Type 1 codes 0, 1, and 3, and ICMPv4 Type 3 codes 0, 1, and 13
(<xref target="carriers"/>). Their existing meanings are unchanged.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC0792">
          <front>
            <title>Internet Control Message Protocol</title>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="September" year="1981"/>
          </front>
          <seriesInfo name="STD" value="5"/>
          <seriesInfo name="RFC" value="792"/>
          <seriesInfo name="DOI" value="10.17487/RFC792"/>
        </reference>
        <reference anchor="RFC1812">
          <front>
            <title>Requirements for IP Version 4 Routers</title>
            <author fullname="F. Baker" initials="F." role="editor" surname="Baker"/>
            <date month="June" year="1995"/>
            <abstract>
              <t>This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1812"/>
          <seriesInfo name="DOI" value="10.17487/RFC1812"/>
        </reference>
        <reference anchor="RFC4443">
          <front>
            <title>Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification</title>
            <author fullname="A. Conta" initials="A." surname="Conta"/>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="M. Gupta" initials="M." role="editor" surname="Gupta"/>
            <date month="March" year="2006"/>
            <abstract>
              <t>This document describes the format of a set of control messages used in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the Internet Control Message Protocol for Internet Protocol version 6 (IPv6). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="89"/>
          <seriesInfo name="RFC" value="4443"/>
          <seriesInfo name="DOI" value="10.17487/RFC4443"/>
        </reference>
        <reference anchor="RFC4884">
          <front>
            <title>Extended ICMP to Support Multi-Part Messages</title>
            <author fullname="R. Bonica" initials="R." surname="Bonica"/>
            <author fullname="D. Gan" initials="D." surname="Gan"/>
            <author fullname="D. Tappan" initials="D." surname="Tappan"/>
            <author fullname="C. Pignataro" initials="C." surname="Pignataro"/>
            <date month="April" year="2007"/>
            <abstract>
              <t>This document redefines selected ICMP messages to support multi-part operation. A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require.</t>
              <t>Multi-part messages are supported by an ICMP extension structure. The extension structure is situated at the end of the ICMP message. It includes an extension header followed by one or more extension objects. Each extension object contains an object header and object payload. All object headers share a common format.</t>
              <t>This document further redefines the above mentioned ICMP messages by specifying a length attribute. All of the currently defined ICMP messages to which an extension structure can be appended include an "original datagram" field. The "original datagram" field contains the initial octets of the datagram that elicited the ICMP error message. Although the original datagram field is of variable length, the ICMP message does not include a field that specifies its length. Therefore, in order to facilitate message parsing, this document allocates eight previously reserved bits to reflect the length of the "original datagram" field.</t>
              <t>The proposed modifications change the requirements for ICMP compliance. The impact of these changes on compliant implementations is discussed, and new requirements for future implementations are presented.</t>
              <t>This memo updates RFC 792 and RFC 4443. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4884"/>
          <seriesInfo name="DOI" value="10.17487/RFC4884"/>
        </reference>
        <reference anchor="RFC8877">
          <front>
            <title>Guidelines for Defining Packet Timestamps</title>
            <author fullname="T. Mizrahi" initials="T." surname="Mizrahi"/>
            <author fullname="J. Fabini" initials="J." surname="Fabini"/>
            <author fullname="A. Morton" initials="A." surname="Morton"/>
            <date month="September" year="2020"/>
            <abstract>
              <t>Various network protocols make use of binary-encoded timestamps that are incorporated in the protocol packet format, referred to as "packet timestamps" for short. This document specifies guidelines for defining packet timestamp formats in networking protocols at various layers. It also presents three recommended timestamp formats. The target audience of this document includes network protocol designers. It is expected that a new network protocol that requires a packet timestamp will, in most cases, use one of the recommended timestamp formats. If none of the recommended formats fits the protocol requirements, the new protocol specification should specify the format of the packet timestamp according to the guidelines in this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8877"/>
          <seriesInfo name="DOI" value="10.17487/RFC8877"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC1122">
          <front>
            <title>Requirements for Internet Hosts - Communication Layers</title>
            <author fullname="R. Braden" initials="R." role="editor" surname="Braden"/>
            <date month="October" year="1989"/>
            <abstract>
              <t>This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="3"/>
          <seriesInfo name="RFC" value="1122"/>
          <seriesInfo name="DOI" value="10.17487/RFC1122"/>
        </reference>
        <reference anchor="RFC4890">
          <front>
            <title>Recommendations for Filtering ICMPv6 Messages in Firewalls</title>
            <author fullname="E. Davies" initials="E." surname="Davies"/>
            <author fullname="J. Mohacsi" initials="J." surname="Mohacsi"/>
            <date month="May" year="2007"/>
            <abstract>
              <t>In networks supporting IPv6, the Internet Control Message Protocol version 6 (ICMPv6) plays a fundamental role with a large number of functions, and a correspondingly large number of message types and options. ICMPv6 is essential to the functioning of IPv6, but there are a number of security risks associated with uncontrolled forwarding of ICMPv6 messages. Filtering strategies designed for the corresponding protocol, ICMP, in IPv4 networks are not directly applicable, because these strategies are intended to accommodate a useful auxiliary protocol that may not be required for correct functioning.</t>
              <t>This document provides some recommendations for ICMPv6 firewall filter configuration that will allow propagation of ICMPv6 messages that are needed to maintain the functioning of the network but drop messages that are potential security risks. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4890"/>
          <seriesInfo name="DOI" value="10.17487/RFC4890"/>
        </reference>
        <reference anchor="RFC4950">
          <front>
            <title>ICMP Extensions for Multiprotocol Label Switching</title>
            <author fullname="R. Bonica" initials="R." surname="Bonica"/>
            <author fullname="D. Gan" initials="D." surname="Gan"/>
            <author fullname="D. Tappan" initials="D." surname="Tappan"/>
            <author fullname="C. Pignataro" initials="C." surname="Pignataro"/>
            <date month="August" year="2007"/>
            <abstract>
              <t>This memo defines an extension object that can be appended to selected multi-part ICMP messages. This extension permits Label Switching Routers to append MPLS information to ICMP messages, and has already been widely deployed. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4950"/>
          <seriesInfo name="DOI" value="10.17487/RFC4950"/>
        </reference>
        <reference anchor="RFC5461">
          <front>
            <title>TCP's Reaction to Soft Errors</title>
            <author fullname="F. Gont" initials="F." surname="Gont"/>
            <date month="February" year="2009"/>
            <abstract>
              <t>This document describes a non-standard, but widely implemented, modification to TCP's handling of ICMP soft error messages that rejects pending connection-requests when those error messages are received. This behavior reduces the likelihood of long delays between connection-establishment attempts that may arise in a number of scenarios, including one in which dual-stack nodes that have IPv6 enabled by default are deployed in IPv4 or mixed IPv4 and IPv6 environments. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5461"/>
          <seriesInfo name="DOI" value="10.17487/RFC5461"/>
        </reference>
        <reference anchor="RFC5837">
          <front>
            <title>Extending ICMP for Interface and Next-Hop Identification</title>
            <author fullname="A. Atlas" initials="A." role="editor" surname="Atlas"/>
            <author fullname="R. Bonica" initials="R." role="editor" surname="Bonica"/>
            <author fullname="C. Pignataro" initials="C." role="editor" surname="Pignataro"/>
            <author fullname="N. Shen" initials="N." surname="Shen"/>
            <author fullname="JR. Rivers" initials="JR." surname="Rivers"/>
            <date month="April" year="2010"/>
            <abstract>
              <t>This memo defines a data structure that can be appended to selected ICMP messages. The ICMP extension defined herein can be used to identify any combination of the following: the IP interface upon which a datagram arrived, the sub-IP component of an IP interface upon which a datagram arrived, the IP interface through which the datagram would have been forwarded had it been forwardable, and the IP next hop to which the datagram would have been forwarded.</t>
              <t>Devices can use this ICMP extension to identify interfaces and their components by any combination of the following: ifIndex, IPv4 address, IPv6 address, name, and MTU. ICMP-aware devices can use these extensions to identify both numbered and unnumbered interfaces. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5837"/>
          <seriesInfo name="DOI" value="10.17487/RFC5837"/>
        </reference>
        <reference anchor="RFC5905">
          <front>
            <title>Network Time Protocol Version 4: Protocol and Algorithms Specification</title>
            <author fullname="D. Mills" initials="D." surname="Mills"/>
            <author fullname="J. Martin" initials="J." role="editor" surname="Martin"/>
            <author fullname="J. Burbank" initials="J." surname="Burbank"/>
            <author fullname="W. Kasch" initials="W." surname="Kasch"/>
            <date month="June" year="2010"/>
            <abstract>
              <t>The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet. This document describes NTP version 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3), described in RFC 1305, as well as previous versions of the protocol. NTPv4 includes a modified protocol header to accommodate the Internet Protocol version 6 address family. NTPv4 includes fundamental improvements in the mitigation and discipline algorithms that extend the potential accuracy to the tens of microseconds with modern workstations and fast LANs. It includes a dynamic server discovery scheme, so that in many cases, specific server configuration is not required. It corrects certain errors in the NTPv3 design and implementation and includes an optional extension mechanism.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5905"/>
          <seriesInfo name="DOI" value="10.17487/RFC5905"/>
        </reference>
        <reference anchor="RFC5927">
          <front>
            <title>ICMP Attacks against TCP</title>
            <author fullname="F. Gont" initials="F." surname="Gont"/>
            <date month="July" year="2010"/>
            <abstract>
              <t>This document discusses the use of the Internet Control Message Protocol (ICMP) to perform a variety of attacks against the Transmission Control Protocol (TCP). Additionally, this document describes a number of widely implemented modifications to TCP's handling of ICMP error messages that help to mitigate these issues. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5927"/>
          <seriesInfo name="DOI" value="10.17487/RFC5927"/>
        </reference>
        <reference anchor="RFC6069">
          <front>
            <title>Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD)</title>
            <author fullname="A. Zimmermann" initials="A." surname="Zimmermann"/>
            <author fullname="A. Hannemann" initials="A." surname="Hannemann"/>
            <date month="December" year="2010"/>
            <abstract>
              <t>Disruptions in end-to-end path connectivity, which last longer than one retransmission timeout, cause suboptimal TCP performance. The reason for this performance degradation is that TCP interprets segment loss induced by long connectivity disruptions as a sign of congestion, resulting in repeated retransmission timer backoffs. This, in turn, leads to a delayed detection of the re-establishment of the connection since TCP waits for the next retransmission timeout before it attempts a retransmission.</t>
              <t>This document proposes an algorithm to make TCP more robust to long connectivity disruptions (TCP-LCD). It describes how standard ICMP messages can be exploited during timeout-based loss recovery to disambiguate true congestion loss from non-congestion loss caused by connectivity disruptions. Moreover, a reversion strategy of the retransmission timer is specified that enables a more prompt detection of whether or not the connectivity to a previously disconnected peer node has been restored. TCP-LCD is a TCP sender- only modification that effectively improves TCP performance in the case of connectivity disruptions. This document defines an Experimental Protocol for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6069"/>
          <seriesInfo name="DOI" value="10.17487/RFC6069"/>
        </reference>
        <reference anchor="RFC8799">
          <front>
            <title>Limited Domains and Internet Protocols</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="B. Liu" initials="B." surname="Liu"/>
            <date month="July" year="2020"/>
            <abstract>
              <t>There is a noticeable trend towards network behaviors and semantics that are specific to a particular set of requirements applied within a limited region of the Internet. Policies, default parameters, the options supported, the style of network management, and security requirements may vary between such limited regions. This document reviews examples of such limited domains (also known as controlled environments), notes emerging solutions, and includes a related taxonomy. It then briefly discusses the standardization of protocols for limited domains. Finally, it shows the need for a precise definition of "limited domain membership" and for mechanisms to allow nodes to join a domain securely and to find other members, including boundary nodes.</t>
              <t>This document is the product of the research of the authors. It has been produced through discussions and consultation within the IETF but is not the product of IETF consensus.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8799"/>
          <seriesInfo name="DOI" value="10.17487/RFC8799"/>
        </reference>
        <reference anchor="RFC8801">
          <front>
            <title>Discovering Provisioning Domain Names and Data</title>
            <author fullname="P. Pfister" initials="P." surname="Pfister"/>
            <author fullname="É. Vyncke" surname="É. Vyncke"/>
            <author fullname="T. Pauly" initials="T." surname="Pauly"/>
            <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
            <author fullname="W. Shao" initials="W." surname="Shao"/>
            <date month="July" year="2020"/>
            <abstract>
              <t>Provisioning Domains (PvDs) are defined as consistent sets of network configuration information. PvDs allows hosts to manage connections to multiple networks and interfaces simultaneously, such as when a home router provides connectivity through both a broadband and cellular network provider.</t>
              <t>This document defines a mechanism for explicitly identifying PvDs through a Router Advertisement (RA) option. This RA option announces a PvD identifier, which hosts can compare to differentiate between PvDs. The option can directly carry some information about a PvD and can optionally point to PvD Additional Information that can be retrieved using HTTP over TLS.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8801"/>
          <seriesInfo name="DOI" value="10.17487/RFC8801"/>
        </reference>
        <reference anchor="RFC8883">
          <front>
            <title>ICMPv6 Errors for Discarding Packets Due to Processing Limits</title>
            <author fullname="T. Herbert" initials="T." surname="Herbert"/>
            <date month="September" year="2020"/>
            <abstract>
              <t>Network nodes may discard packets if they are unable to process protocol headers of packets due to processing constraints or limits. When such packets are dropped, the sender receives no indication, so it cannot take action to address the cause of discarded packets. This specification defines several new ICMPv6 errors that can be sent by a node that discards packets because it is unable to process the protocol headers. A node that receives such an ICMPv6 error may use the information to diagnose packet loss and may modify what it sends in future packets to avoid subsequent packet discards.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8883"/>
          <seriesInfo name="DOI" value="10.17487/RFC8883"/>
        </reference>
        <reference anchor="RFC9171">
          <front>
            <title>Bundle Protocol Version 7</title>
            <author fullname="S. Burleigh" initials="S." surname="Burleigh"/>
            <author fullname="K. Fall" initials="K." surname="Fall"/>
            <author fullname="E. Birrane, III" initials="E." surname="Birrane, III"/>
            <date month="January" year="2022"/>
            <abstract>
              <t>This document presents a specification for the Bundle Protocol, adapted from the experimental Bundle Protocol specification developed by the Delay-Tolerant Networking Research Group of the Internet Research Task Force and documented in RFC 5050.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9171"/>
          <seriesInfo name="DOI" value="10.17487/RFC9171"/>
        </reference>
        <reference anchor="RFC9293">
          <front>
            <title>Transmission Control Protocol (TCP)</title>
            <author fullname="W. Eddy" initials="W." role="editor" surname="Eddy"/>
            <date month="August" year="2022"/>
            <abstract>
              <t>This document specifies the Transmission Control Protocol (TCP). TCP is an important transport-layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN-RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="7"/>
          <seriesInfo name="RFC" value="9293"/>
          <seriesInfo name="DOI" value="10.17487/RFC9293"/>
        </reference>
      </references>
    </references>
    <?line 1402?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author thanks Mark Andrews for helpful discussions.</t>
      <t>The author used AI-assisted tooling in preparing this document,
including drafting and editing text and converting it to the
kramdown-rfc source format. All technical content, design decisions,
and the final text are the responsibility of the author.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+1925Ib15Xl+/mKHPJB5DQAsYqURFa121MiKZkzosgWS+Nw
TExHJIBEIZuJTDgzUUWYpL9lvmW+bPbal3NJJKroth4cHUNHWGQVkJdz9tnX
tdeeTqeuL/uqOMvuvXqbvawXVX5dZN83u3qZt/vsXXlV51VZX91z+XzeFtd3
f26R98VV0+7PsuLD1rlls6jzDV1/2earflq8n5Z1n7dFPi2300KuM+3s69NH
T1y3m2/Kriubut9v6YuvXl7+kGX3s7zqGrp9WS+LbUH/V/f3Jtm9Yln2TVvm
Ff7x6uJ7+k/T0t9+ufzhnqt3m3nRnrklPdOZc/T0jx3uTRf9+dK598X+pmmX
Zy6bZvRW+jT417Ko8v3Xy7Jrd9ueniSjh3vf8eeev35r/71+4v/2rbsu6h3d
JMuu2ma35Ttc/PLygn4gr/HHpn1Pb5j9iF/TTzd5WZ1ltBhTPNF/K4t+NWva
K/pN3i7WZ9m677fd2ddf43P4SXldzOxDX+MHX8/b5qYrvrZLfI17l/16N6dV
Kt7TExdfy6KXi812Ote9Cot9j75Q0cp0PX3BbidfnMmFZmVz+yW+/qJdna37
TXXPuXzXr5sWy013zrLVrqpENu69bMv32f/Ane/xr+gd87r8S461P8su8mpP
W5xdFot13VTNVVl02at6MePPFrKS9Mq8Pv/tCv+eLZoN3bFu2g1d5Jo35pcf
nj/67tmp/vXk6Yn99cmTJ4/tr0+fPtG/Pn363XckNGW9Glzk5OTUf/Pps0f2
12ff2F+/efLtif316ePv7K/PHn3j/3pqP/320bfP7IbfPfN/ffroxP/1qT3c
s5Pv7KfPTp/RT91sNnNuOp1m+bzr23zRO3e5LruMTt1uQyeEBHlFi9plDYtx
XrG00snsixonLGvm/14s+i7r13mf5dkVicNNvs/y3vXrIrMNz+ZFf1MUdZbX
0UGhfy3pO5u8zq+KZbZoajwD3W6ZVQ2d5XW+qxwOziTrdot1lnf06W6xLpa7
ij6zLIrttNvmiyKTDy3o6nnf5/TRvqFnLLuehMe9KPBfFoXs15pkbLHO51WR
bYquoxt3s+xNneFpd9Evi7Zt2i67KuqipXdaupu1PH6+3JQ9/SCjG78vety0
bnp6wYy2+SZvl/SrebHId13BF22LP+/KFq9Ez+hoabdt0dHKVnu6367DzSb8
QVtJWobrYs8/IgVIP6Lv9uUGj9eXFX7Oa4KbNPQKWXwN/hx/k16ZZK7IbvLo
JSa84riCv3JTF1NsGCusrFnxt3F9vyp44brEzkCE6fGbdTkvsZpuuEgZL5Jd
4auOv8uaONs2VbnY02qsaGGwj7J89EROFmRRTJuaFkWWISuhn8sVDqrXGvza
B5fMO36jrtm1JAn6BnyfvJpll7yvy6Kt9lCei2ZJV2yLnsQMHyzbICebglRG
fdXZKsXHALtIa9pldZPVxY2cAuhlGAtcdJa96l1HiyrP7BfCdnWT4xCoeNJK
4RY3ODP0ob3u+YSu3rt1c5PRYtfdtml7PMx2S+/J4tuxbVo3eBCIag85pwts
zun6bBywErZetP7v6+aGjsoV3fgaZgCSTV/pYP5o4+gNSe3iH0s+MTU+wLLR
lnhtOTM3pMrlAPI98RykNFhrbMrlkr7h7pM27dtmueNfZx/vl/jnZ+fekYhG
J14ee5019JwtLWRP5vM9KRfe+Gv6kemC9Px3iQIgSauqshchi15suWuxBEFB
bPOOZG3mLoIeMv0EVdEWWGG6oh5cfHlFF9u1BS0L/bxqFnnlWnx32rflVo5X
QYY67C/Wr/VGPsfOrEkSSalckHLERem2R1UQHyCSsgKCRbtJL8ZXlQ3yd5ED
T7sVFEKj51+PP9/urpNKHhAd93A7PWN7uk9Jq5scUVYTekhn/1Gj8PGjWsTP
n7HIzo5adut60Nq9Wh1XtW5U1ZZ8JCJVi+VKFWy09073Hj9WM2BaDI+EfZ7c
poG9Mrfrq17NDvQqPworV34rvqHIuOuK9rpcFLepybAHE6jMEUXpIMl+I9kK
J3oxu0Uv6oK4VVNV5AnyGu66He1nS+eng5AtSaEtCwgin1jVHdgclShWYyQ9
DkoQv8dmPPj4cZG3bUk65vPnh3IzkwnSv4u2nOOae28GSAHuqqUbGlL+Jtmm
hsU1X5KG6MsOx4NXruNjurzOaU3w0bJzQURNyEUn7zOo1dwOFiuyTrWnvIrD
Q5Nqo6/jqSckvEER4i0c1NxzKOqadSC/+wucBD5iHQ5JkVFIkCEm6LJ7r399
d4mgAv/Nfn7Df//l5b/++uqXly/w93d/uPjpJ/8Xp59494c3v/70IvwtfPP5
m9evX/78Qr5MP82SH7l7ry/+dE8k8d6bt5ev3vx88dO9jM1cfHbJyRbtIaqL
ZArimtPS6cYs8Z3vn7/9v//n5Aktwn+hI3x6cvKMjrD84+nJdzjP0E1yN5ZG
+SeMmSODVeQt7w2ps0W+LXsKvSYQyI52oc5Ikgpazv/6v7Ay//ss++f5Ynvy
5F/0B3jh5Ie2ZskPec0Of3LwZVnEkR+N3MavZvLzwUqnz3vxp+Tftu7RD//5
94hKsunJ09//C4mQRr5n7kx9YTWCtIANSTZJYE3HpLwu+z22aWAoxaKJqSQN
4xDoZJumLW53oiX6pCV/fvS3/ECirewZSE97sy1PB21XVng0kqh1ebWesmab
0HN4qzsRuWLNXffssPBL3ODgkgIjQ8oKMl8sGrG5fUPfD57KuqhIre+DqsRn
lg0FZSpv9iwFnuIKa4HXme8R+Q4UKTmxaoLFpSpxAvj5Vggb4LuJnjLDT9fw
moOegTRiUa3gXBW2OnfEK2IZMqhAddxkxUSDvNavqgLDouM15e0Sf03jqW1O
Gm+xowD+lttNRA6g3chLrUXb88M2W5i5HTRUQSdw4O/h3ffRLZBqoHB8VS7o
JDdXovLZ++M4oOuaRcluvm325GDBeYfoOpFL1ZEbCf/Er5u+PLvE7BHAgpDx
J9eafK2e1RMtPLYichPo2Re7tpXIqaSlIOVCFsK5Ny09jTg99LHVrmYf1JYW
wT55cf7nE3pQeuA5XWQJV6mc70QaW/oxrXGzZSegvlJpivwp2SXR+5APOiRw
HdqyYgeevrRrdl21z7w/g43hjZRXF4N8ywmdRM/U8WJgAWVF1arvtshFdVhg
9vzlSHQ7yBr9WE16F7YtiBS5gZm6enFkMmoh5nnHi0sKgwKWXtUVn5xrWk11
teVi+S2vhG3bVuS3scTR/UXmVMxCWiAkDuhtxJfbND0Wa8dWimQ0PA1f0TbY
ZBEyv5Dfy+roeaW/deRg6IlIllgfya9Z8Cbw8eJDsdhBZCC7i+jOeCf40Ujr
0Ac5FceSPTXJ9ms+Ebceq80uWw2796Pcz16AZZ4eVz43ljFJ0yXRYiP/lmoC
cnOqpQaCxx9LpYduqdqKr8yhqX03uGsr3tahlPBuSHzD565b0Mnxe5IsOL+g
RtUDfQGR5ehcvpZvxKSNHeiJWUhRAqJWguDAiybb2Iorlnk3k57zRdktqqZD
WJc85eB4+5XH0SnrkZOCgxESQrJqww+XrKhh+uTz2C3yoBGVkD1om20LFSqC
11IoCV/8VQ+RgpqgyF51xHBp+WaaRCB71jY3RYu4DFbN51XtXPEb6hGTVdvm
pA5Yx3HyxU4bPWlz7PxCuJAHcu7CNk2chLDiy4ItvTwnbfAV9GMvcbM3CBKT
jBgZfh2Y8dsUCN3+JxxjOvpL9rOzN7wb5kCNBZ4W7NCp6RIJ/vhRt5L8e9NF
khU6qr82RZ+Txs1pqeg5o7iVvj+STMSxUI8CAZE+5Z1xLwdPjYkRlIv5dT/J
AR2+vk8oif+yHIZc5GhaJHqJyPVXjlx5JX/1TtyDl5e/PrTTEHbVcocTiGQU
FdOq5tBn5UrTURNdaHo+bxlWbbOJvxRC5raoClKu/a3SdmuSg9VW5FnQOxf9
Tl9XdSTH6RTl0omrg4PVrfPWgnj/ywnelK5bduvCe5yawlvoK0Nc6dRelxAv
3LNJYngSrm3V7Dfs6Zr4yyb+6NeALsF7IK9GLnAn+0WrNMUTcYj8CuEoPtXR
2cGjbZvF2rwpMlnqYHBYQHLTe0sdniBbrBtExWJ06Kn7ZtFU/AIFp0a6kvTw
efbr5XMzYVt11Jf6XQlyL2LHNft4P3VkJc7dFCS6pD03Yw4EfX4v2QN7Nv5U
LN2OpfsWX8jCkDh7KDYkVreWHvSGVIOj4BqZph9YHYkb1NptUNTzezrfs0ba
bFgAxmzRLPsjMnMd6e+WZD4IsSTEOnVr1UdjuxZ51uladcg4dBI5i5Yst7AQ
kp+W75oTmzyNZDxCuKLZryx3Hb0WnZbtet/x1yA7bUPucjtJQwrzME1WJpLN
NlfWJdGoOSTeXbLVDZeHVCfPyGfzcmBCLUu+5AWCARAXgOIXefDUMGvVD4/A
T+c99Mx+gf3ECTffJbGeOEHLgQcQjMK8qJqbmSQqUT77/FmOO6oE87bJl4Xa
8w+94youHRfyqCQUiOV7JsdixHCX3R0+kZdJyHMQgRD2diqaISgzySKRUlUp
0kWuqkMky+bOotxB1tcrPbHMsTYzR7Hs3K72iXVJx/pUp9j1aVAd7FuoH8SX
lPdGmhUXlIJUJP4hE8s5zrJXZVhEMsOLOdw2W8ovddycj9iu2kIKH2tOfwWB
nGU/mjhzYhPKQHz1voGZcb5UYuUicW5UI4mq1eDxaHDnpJ7Gx7Uq+i7kIasi
b8Ww0v/veuyxxMJSWtDCMUe/jqxyVWHJVrsKIUmcKkZIZvsr6Ab2V+yi9HGs
AAQVUhytq/8WzhISm0BfiFdl5VHsTkehUOuzGJIHXRRblug3W924jkwFvX+z
7T5rwaArFha7R1VwdnjNP8ditIXWRDXO9qfqzHGObMrRqA+DaCte57QlTTsn
2ZEMJC/Ya5wd+ga9GQR/YiaEnHVkeotW0k+0WD6h1q/pJF6tx6vKFk7Osj+Q
Y+44fgnFONId6/y6RAE0pE6R2mQlR3u1My3YYZms2OcE1dBJUkmTESpIqsLF
YKb5aKz7/fvZL+a8ZO8WBcUBZUOL3ulf1TTbOnHogYIU3V2XhGOkXlQ3L5+I
Nv3HLxUSaQuf5UZt560pLc4pIIYhT4dXgLN/fP0NvW9J201uKqfVSas6+ydu
FowKlHhNYj+NfhTbmVn2rs9xnpd0ZxflQKKiaCY2ACkjkqmq8ke/7GcHa1AX
mup/SeKx9jtuOqjminCDciBXwHVVHLZiuy0kwhtiDTquTHT6D7FqJkFnXm4c
f/WKC4gcr4osLOgssRNT1kuUXSyKEteDH4CW/aogx7dv9yJ2iCjrHAn1xnxv
RPN1nLOwN8uTbIXUUNjBCRnbs6g+dbXuFTdgS1Ry7ulqTev6GD89PXX0eDBY
KDMupWSNC6opUPPhXxw5/3yhaWJ9ZEm2mHftK9CwYxoNcrRmNtF+SNuP8Jlu
SVGsC6/PtWvTW+QD/EXCBQNdWODqdxnREvBfJKsrdjW+pz0hPftWPZ+MPDl2
EL8TXwBIGfIFyE+NTvyUVo6+bNc0aymp2gX0YecfXFwaZLJol5xloyGarFwX
OUwfa4sFVClZAamEdb7+inPS9KEY5jRCofMYZ1flIc5lU7RS5mts9jTydHQN
OA4kAaRmkWLasyUilwNnSa80y75/a4vrC6rib9BPGb3mfX89bG/jAOmFuEYP
3l6/eKgFYgjpq7fX32a/SKrrwgp5rOhcBPXIM/qaOvlLtkWdrz3iNxdLiYKh
llLrGGAAD8SZe/rohAOrPzBaQur9pPyLa92w2LoCV+D++7s3P/sEAmKIP1xe
vn2HcobHC1aMkMEa0Jv/sOthQbl4w+VLdSozvtD7Yi9pSPEXrGIZARlq9+71
5dssoBWx46KETLKaMUmlo1b3Wu684fu2BeQe68OBIu8tVA+tNiL24mZ04XVz
Zk7L0smC0A4guNn3nBCsi0JLBn4NS4k+/bI77wAWwTla+7VnS1b1+BrjJzSB
zLkRejLaUEb3OPNXxvEGdeOXhtcX6zNikFllHsRFWB/kyZvWjATHVmSkdwve
SQ7aOnMmRBVC+cDZip0H0V1fdc5rLsur1fKtKassUxMsbUjLdiGgixU0P22B
xeeKtmiM8cKKXMsubKlIxT/xy6hvIc7ryFN3urTmmQU3DNdgt4offiWB4ALV
YVr5Tr2PBrCAj/db/PdzSLrIPpMavkLoI7nKtlgU8ObiDfJRCsOCSH7ci8uf
pzk9KwlLu6tZgeRQQCzkWtSilXof5fh4DSBTa4R2tgeoldakBrnWKBZ5V2+a
pQSapDP5GXGaF9WONWdVXOWLvUPKpt2JyyWeyoY8rgWWbJvvKwoBrfrJD8L4
vSWncHEAk3QRpwVwKJBX4cMEsEZR04MuNMz+sCfN+PLtw8wSpwWLkfg1tCu8
5SyDEOZqJb4baQx9fEgQfT+cKcH7dcGtDIWhrokiPFPZX1FcSzu6Kns+1WnE
QFEfLAPCCdyPhNB0hPNhEiT5i6oLCJaC22SJGhX0SL45BIa0LNmv1bCmqQ+8
iYkLZYovqlGcmXrixJWLU7mjcM8hkNHwR7JDB1n2DPlWKY5byGYpTKzqABrk
XhR1KS4ep2Hf6nuqwbkLa6kglSHUcvAkMf4nhHZ4DXhDx9JZEw2ZNaUsOoxj
rqQg6WKtpTkMiLWWJEcLPJwGjApszpzVsUyRFkLiEnXXF0WbpesfnXnWcvzw
sFZJEVGgDIgGOQdBK8BWkB54okVzn3sJVVWoDUbGWX2ZxK3ZIIlW7WHObnCb
ieWUZGHYARGcgBkCrumnEcO5mTzBIQia0zWK8eOyomjNnJOuS5xD1A/zxIU1
pepXgPab3kNQIh7fxk7BGoqZ330ZJTkscCK3mSL1DdernWX25ERLKtkqqY3l
Pbg2hftrghcJ4So69byctFZ9VIdTcKsgpEP1Xq3wWNoHMNLcGgD8azKUz3Jd
52puWNZr3ndveY6dVK/qys22kjeMk0Bs3FIcwcsPOT5Kxi4VU8ts7OY+uWGR
fqFl4SLnkF7yYvO9r5Ib3K6Z95yVGlbn9YO0gvPcpMinqeKUiVtI9gVIvchr
02RUvI0hscuKj+xhwUlep9Eq29vqCknU9eacJHAfalWxNKxRwa8mUarX+fwi
J4215BcHAhuGWqLaL1F5uSlCraDQ5c3Z77KiSOo/Dso1Li2ZMJxMMwxcdILn
xFWTcz1/vi6ypo8uYMJrpxhIKwAplIOdXDbdYgq7pBbHYZsbV50heFeBNIkT
BELkgLkYzEIvvCo/AA5HR3UiH65JC5HzwY5C0ZYN/bwqck2fWmvRdZkPUvhx
1oJLsoOmCPFdavKf7FDTeb/irGgflkLW+uR08uTRowxhPhChDIjmR5Psw7Yp
a1agLl9IOUnKvqhMk2RtcINVebVrVRzh7HMtrwvGUaCHpOaWeyTlNJINhmzs
mb45pWfS2k/vy5Pisg76F7T2o1CtXvcE1yEZoMv4PMYrr+Q7aGHL3nS+kmRZ
pwODpsFQAqEQY+JROFDmAS1FSrNpSQm/SmX/MBXO0ilgXNw9Otpnzk3jNPq0
b7zfNUeoXF8pkuxQyMz/yPxr0ZPru2hpA7sS4A7yvKLk2az7VwF+yHBFvpxr
KBsWMaskBODZ/hzPjiSvqIbQ2QG9nSE4u84rsTlr3XjvrWLTAbRICpJ2OvBi
9NVyqaUhkrUS2iYsG9/aQOrVfgDphkqcwvIWU5ZHhX3zwV2qEPP7MtQD30Od
ZiigB/egL1O4udA0RYwDl9xb6M2JzCjjQVic4pVjR0N3PnWYoxS++VmchbI9
S+B7DPuiG+JwaPkCFS7JGQYRhJrM50ga2AkCqGYBM0NX8NhPIGokgyT1NmQL
RWJK7eSAerJCuTe4vmZZuAhqAKd2GsEF2GZuyJ5ys4y2q0TJA3hLbtCvkUR1
vjHDQwmHx4JekzRgIVu7bPOb2pc2vddjpU3fDtJptwhDpbPc1c1UbsBvgLTo
Hi10TcU3tS6sqDLqdQO/XFFic9DJEBs/Lb/Sl/mU5Zri5Wy8ZCdJ/zaJ3viq
c+PWcgAwIFGqOM+CuKLaD57OwVbzE+5j2SdHfd204ojnQ70cSw5KfR5NjnQJ
zhNsYjf6WcnKVLmHenKONFzfUrvwg0qJaF9e/ooI5tA6PJo8eiTWwVoJrDZq
6k9DI62+6GPMsp8bQ5XoRnL2h6Nma9vRNogtNzahsH5r20rSU2Ey2ymYEeeD
7Dyp6s6V3hfOopISx4psQNtNF+t6TqJrJCqhhzaRdRHGRBAmD2w5Hk6wYtmD
3jqUPDTHPgHjG0wr/4V/scF38VgeP8TR6gvWXA9OJqeP/Odmbnh/rc/6PY/r
iMNORAVGOv/h4GDhFADjIknwBK+JfUVRw7l3Cr5orPwIoAP7zWJB5XVZPanb
i6WjqDN8/vNnNJXfWOUWrtq2qTU5REav7tjuXnCTcytBmjdjFPAJooEecMUy
GUwhrJfCfRnmZ4fBNP8se4f4AWDtPkFUdb6CoRISGb8qSdGeZ0XeVjCi6fdD
OyoJnUGkpyyahsMdHE7tKZgjWRzcOtGsaZ9QhI3X4l2halHydgzWXbLKqsjF
EcXxl6JtztlvE52XiZ1BWjqEgqjuetRZg7oJh5Idn3u0tiXSSNcQeWSb1xZS
5GdXIGBueHusF8zHf7QujRwlXpbnQUEnWBcU6inIhCrjsvtULi7GU62d3ldN
Y4V8EqRG1CqtsBZTBxb3XCyUuMbkJ3SCMbNmXjJk4gX1ouaDBkzgHh67DSBT
XShMzNfl7BVD94N26vptEzfcH0deDE2PGLIWXr1lzEzqSWSKDW2YgN7pZDKy
ggMYBgHSV6GaJXumihXbvSmvWq0BcskJYZtXlXPxONA1ULZdHyERdaVxBWze
vsAGFrWma5apxmWBwXkJ6YfSt2dbyoGegvvY6IBaPC2yq9404MfBAdP2G/40
q6h64LTFelqyCL/S+X3OaujjfTrLU1ZJn/Gr+9mlKvR3OPZ/9ElDVrCvOrIo
Kkj0zQX5iqRUSMF9RhnTyveclbXwjRauei/5pBX35nEkJXWLoUcjKCxZX7WT
bL404NE1tETgsm22vHqSkup3Le53RxerR9Pm0XEdgE9dAJ+KCM+yH0RNW6pD
xJ7fE96PRdW+SYbchKu8XVprZM+1NN/bw031oRTIj6+VbPT/AZEjObMBzBSN
u+dmMXDqWnsrAU/B8+SsGp5J8UFr5TjQ5bzJDX7DvjGkk2LMDZfXTan784Rj
cN2US/ShiqEjm04ny9JacrNC4g1fNeIn0oRy45uFXVJhsdXipSk5N44cxDKR
fIGIuTGECSAmhlk3PN3zZrOh86C3eG3BmcgpqjDNavWZ88sHj8IAJ3IweGnz
bBTKrRBxnF7FAaFe4/HrQD3Ni/Ai2tvRcISsrg3yqLkvnaNSfgdpgCZT9UUl
d4Qu72ZK/3GL5IUV1Alj4MtVIqGyu2sPM1X1HBelcGWxAFbVskPmk5awvSjx
hrIdoGvRWRvAni2RvE7TOtICHjZA0CdW3kdYZtm5YhnnHaXV2sMobgE8yOtK
dMsvFtLQ6Oik+yeyyPe3eqaEvn1DppZNhFwLFoO8EQQ9W0XmBWqKmxwaSEHV
Itj+61hySDH9X2flXGOOgGokj/HqShqWwzZbglQU/9ZA7XyGQnREG/08zWP5
qjr7JkmS04d1g4uEFIbvaLIlVvctqLzgVeHS5BFzJK9J/XAdC1CScACCjwPS
7RaLwgg+yt4dVL9ZPuPT2aiXiqQvJ0BnqZEaL1epacKv2DBtGJnOi6WQFXbr
cDDV4msRVQ5Mx8nVOcn2tFiRSPfDWo5YL0MH+BKgtv4cgxXhvApMCjVv5Bt6
8nkUUDSIy/BDAZtEttuZmIXjamX3UBrz2uLFu+dv0fq45MidtsRj7aWk1Erb
K7LpsokkbSQZZS7bY9Y1cs8k0IQXZy4mIpHOJ3fgyaviO2KEJ6mW5p6dUEmk
LXmrtUS42rAj50lU7kNK/NBvvRupVLJOu81si8r3lsgZQHUBE+ZN7IFGNuoZ
3wVgHlliuPD1DhkSWdhBvVQzGgFj48jjoferqnHjfsSsZ4n+d7As+XA5t345
Y3qDiHYg3zPDAYe4ZsryBN11E9cL5DnmhT/bZ2GJFD4Gsd/sqr5cgpOgk5CX
S52QmYmiF7SHzwPsSCcz+Eu6lHLmEOv0diUSS71Rbch2cLAceizw5a6Dv0Tn
uZYYXGCGUQqJQ8tCF4Lja4aZzXdXV2apVkCE+qRIksFi+1A1V4a/4I5Pxr8m
sfrDc62csWrwz8vqPtHJ+cKnGhOVR2fYDWx+auiDrqV7R64Nu0ahB5SLyj1y
nJqmw7v5faP7NlpzBt6yaKcB3GCSMBk/AriwpBosNSniiOvTMjHiXgQigjoO
sPsDbRcxYkUWcuV8iotTNF79ZHepHxTwb4cojFZ1V14GfLgebFhUi9xGtbk/
7woKVGF38T2uldMOXEH9oe4WZSLoJz0iTU9ucqGtyjggFAkUXiO4e1vg4Nn0
32OeP3pVIUgJ2NJ7MZZeq3uBAQU1J1lGTbar3XxLR+DrX7R8/0LK9/BUxGL6
f5PV/DlJ2KjCqVe00n0or4RqeRRwmkoUF0mEFluMPLJl9EmPhrv5OPDgsH7V
OTnp5rxyXKK/sp59LYJ3ml8vOKmIbOxPL1xI/PiISwK7fAUJHqmyhMQTb2Z+
xMXQ1V1F0GAFbBomQ6TSSfVU4S1oiND8lp3To30v/jnOEHCwf6z6ISRI5C3s
UnLcR7ubLiIA8qCr3ZcT+GBT1C4ZLtpTjexG4UkerRFUobYk0cbmVzXZWLqH
7bdv9muAFXNWsDhQnpKdeIXriX40g3t50yj7Zie8XfYBSTxIn4rAZwV7Mm8Y
F5mgzSQ+FT3Yh4QoJ3eVzuluJjhJ2/H9YqzLl+gcf2xuEylGuurdRc2y6HRB
N2km6pBISntvjE7K4Vsce2nwz1QWuqf1CLBMDMX4bif6el0AYhgWa16s0CdZ
9lbxoxXjh+IT6oa69jwb0I5MfcMzfa3rE1BJ6P5EUxDzshkbClOQCmTs8GWO
nitcj845xe8qhme+f8NnaBQOrJxdkNN3iqN5PDul/51ALpUjk17IsvZKdEmv
wd4Tq3PNaUZ0dZW0nRp2PAv8q9K19FpLET9wFr3TOocBS62z+uN9ybKPtTHV
oYnp0lJ3w3yG9p2XRndEZufy+xffZECWYC1eXfx8gSwlHSGGp9AalGTEefu2
bdlw1Bp+P4kI+Trtl2czzbQj2m5Ia/K2La/x0shAyhPkUWeS4/Z3utKUW+k+
f5YXWETN6tzIE7eRC8K7ErCGPFDgkPzb2BFZ+zyXntp0F7hpDD//7A46Ra25
nZ79LhLPM6PRvcRtT5R67smTx3gNemCh2834t4/lt+ByxTrELHX2tnI0Ok8x
EKTknceLK2ZzrLnfjTwiLwivMWvQV2+t56Q7t3WLlwxNDQF3r7QpI6BXSb1c
rsN9qnyPIr4U4xwDp3GVO1ZQNt+vxHm6xaSCl7y9FDlXS42pfyrqK3oT/tHE
8lnVFGqNggWKttpdvQhduFu6BsMvA5Z7XeRLBVSq7ttt1BuVKp4L+uGJagbb
KfpK+OV3yS/JGzAyEzdCVdscXYuSdzymBdgiMdvWTrpKwNEr3HBKzev/AZZd
MbN//etfXfYoO/xzMvKz05GfPcbXT+hXj+mdv8m+pZd7mj37W37m/mn6d/7P
feJH4ePCf+TfzyGY0b/1z3PbuvDn02/1DCpkB/e0P6ia0D6N/fnNnuHv+PPJ
/ZX+/wKRO3K+1mpz3TBdq7oPpKhDIygKplOcFXmrv/IjkD7Khgchg7B/yRP8
o6xC9OeoUn1gL/Yw/cJff4Nn+PvXAWf741l2f1VeTZe7jJnvf3fv5V0q9oHY
JtPM7Bacm0misAWNPyrnRvsgJdKGQigPpdKfgV3y4b2htVxqbfUOLa99ggyb
dpoAvtHqi5gdsCBzrcObLem3gSVmC5D6PE69pomPkGPy60F6ETV44baJPuTU
0W8z8i8aqYgnKfEFQydMVjQD/gXkuvYCUsnO686YKuPXBRosrxgbj88gkJx3
FkjnnlHI5/lruJfGLsN+uT6p816n5O+9C6+pecn5SeVNK14pl9eAeAjJQi1r
SUfCdVNda8pfKwR77kUqRStIeQBkx/beviBLzzzmNQRUhHgX2ozHq+xCWxxu
VWl6Mf5I6JybaBODFO8mvtnWyXUlVZu2UUZJjdj98nB3FCGvhFjVMe9Q7Kgy
qFA2Q6DbglqMnkyq/efBAUofOONvz4t9o8kPTmWEmNhcmcxcGanJ+CtNd7VU
AU10BdRbMr3bhf+p7JNKcBHLcMZEpyLvRw6UxowSgPFiIMXwfAqTLJvB17Dz
YexhYAUNLFgc1Ml32ISoaJD8ebpwBQWUK09ng7483UvB8unbxM98pJSrmRo5
EIdICb3UcUWJ3XVD6swQwz6MXvz2B3FSMTKlKmcoIIRw/HVZHkSkYA+5hhkv
OKClMUAP3635OtNKrj1++xESUf2eaIiElF5IzKwoUwKbZ3XOEGWzjcFCbvIK
8SnqOF6yV22+UWQ30zTynSLJN9/ayllcwc5RdF6yXERn0EK1wGPyExTTH6CY
+F1fR210x/bxpYTmH+9X/Y4s1R/XCcejfylD/0PP9sYRO2T9VlPhNIV5jKjN
52y45JsvpPScMoi6sdkLZR910nqc9JE3UyJ1URJJ8c7CJ4wFYeaAJAS1DDpa
JwLvra+OH9KlDhqgfbabTbaTXdQwMWpb1H4yhp5YCBvbYbgIbIpdkrL1uJSp
YM0HuM7JF+B5joNGzfTg2tqRqkCWbieHRbXDwg5RaBPSzEtC5fD64k9W0xh/
iaEfNBqMe9JqJqlWvR96L9Dl6psuPECem7hzem6keRVvNA7lHSEFtTYKSeuF
tLwPBnwPDK4EesLjhL+39VtMAhlKx1cZMlJJQ0YshlHBIUkpDcVywq6Ewjjv
4IE6xoXljyCgeulQita4GXQlzgddLzH0wcuSEWDYZz3r7MhRt1rH0dZlRuvq
N7U0I9/W0oZASxIiaZv9AC8FPNgxKcigmZWuu9uEJx1GgebqecaPpP9DBfer
zh97OGMVOSqMdItPQuwrCRV1Sg15GYIJf+b0gh48GXWCmGTY3IKhVBxlIzsm
DE6EYYwim/NKR1ZY6jNljYkEAm7KE1c9FIgYeAqqUuVpwzejkqpC/h0rithC
HBRupLNbxsUcYdV1A85utAn59k7NgwfJgwhUvTjlcQeJG+ynbhj8r4RHYlMU
otK7RF+icIFIho6n7y7CkeKWDkUJ9WvRX6F/jnwTQ7kIMIeLmwlk2POIRKnH
FDnigwjGUHB/TqLMBZ+0ACpERK8rYohunOZVgpu7mUvdXbYmJgpofJhQVF0h
oEfON7O7d9BDMQz4ckbJk2RttgKuEuc2+HVx5ZVjsoiynWNc+rnKgZaKX9ou
G1Xsc86+f7zvj+kR0ltZrsivVqY6LX2NWzxJ7aP6E1EkqGEVwZSRPIaec0eu
n9SGfI1leXCMI3d9duw1bM5DMhLJjzu4/U2kPiKfDJ6zZNe5yZKJa7gXRDUP
qQt+5coIzkLOPoY/DC1iaLE60HiCi05AEoOEOZ2LUiBKFdOJqa2qNIdXM9eP
8dpAbHyZhATkItbmKiSxfExZ3WsKaNwJspPw4HZfzo0dr8nY2Xo4ZByW8ocL
PhNvD4iRmlaLMRMNLkKJz8p74haTh/Up04INp5Y/ZT+jkPxJj4i80yf3aRr9
Oft0xv/V/+gf+lD2CN+PhgjEqv1TOHW+RTDaVoFHVUzwgg76XlBUtJEkSmbf
4uuZQk99w1udixCikAR+/IjQ6PMMb5c9pse7EDhhUm8de2i7oRilzrdZSMB7
dASStroLqbSnYWNXwnAsScCCuYqdcuhP/ee3bUPX2gh/lW/iZ++57HQO2ifO
kNKCTr24Xn/rU6X2PpoRHZN0UYfIcHpJejKUpCezx7MgTRpzSanYPvLN7HT2
3eAjQeAe/2YCp/Nbbts3b1NHJo3RvwGs6/yFElCnRzLGns7+eHOrEluKWJ3Q
g4D+7O9/Nr5K9GDnpMq0xQ8pbCV8JZMXqLOVWXdMGp6MS8OTO6Thwtw5IAi8
O2fyP9rDK7gNOSouwbzz+RcGN4+ceyU0dRMkw+Kjpih1Z0fOe5DHASMh5tBz
nRqyvFaSbN6C24+lHgM+BGK7E4ryiBsNJWR8dRrsDEybIPf06c07HuoLpaU5
eAGZY2fJGScptLSYzgfpEewy/+3E9wPVllgeZWHywXca96tiZE9ng25ik4Mi
nFA3yIccaseEGy3OtWmr7qshBFLzqErThX5fXlLvkGvK4nADnOeLrpvkTaf+
TeMOzcAbAQcl8u9dyMbLO/VxF6MMCGgPxR6uEKNigZM6CB/Un1AY1JgnIc7L
5zjBMgCN3sFbBbS/9FB4THVYfGHBHAObKvaL30t9U9EYAGn5L0S74vtttTEC
35yMWkTuzJIjpJREMexpBhMQwBeZ2oNPZg9eev4bGQcKTRor/k9qExLTMDQM
rBXFrp885mvHOOPbsPkPbjdgDzO9/LeZ6PeTg6srX23kqhzHrqf4q9Q5ezim
u41sYqC/UwELKjvyKLid0/fuI/I2bD79BT6ypTS8U3EL7E87efDpRbXrhDXa
JvHFgHz3t86RjSeVHOku0K7j4ZTM87gamJU6D7VwcYO4yZR5lCB6igBSY1g0
i6bSei+fFaUz97z5g6J6jEaTk8Ip2yNwtQfP8Z/pz7tNBrTaQ6F+owvv/HwM
qZgoHZJ8VwA8vHWDSSsmVk8HyJyfmyjURNcOmgX2oE4sfRTKPrgmagONVMTN
1DOf3i2zVJimRbiib4lPz11CWw8QahoLhwmnnFFQJywqJvsuUF/bKEWJK5vG
AdVsmn74medp0msUFUzrTinobCHZcM+5I1Kwot9HtXVFGQoyu2NQ2ZGsvsyN
siYSCdz5EPHLhpSfJgfCEE2eShQNyxKbZF5KE5X8DB/AVF8vozVE7zYd6UUv
46+0Bid1ubPs5FQgDgIkjkamSKj6VLg/7p5kc5APchyzSnrjCV9l1IzdUd88
PCtJWdEfdo4XeXF4EwclxjTlJOeYvPTAs9IYhOLL3tSNROeTRG6EURYHYXlI
X4yzM5704pNdtmEwaJ62WoTJArhGQncj+bGYyB/yZQyk6c+VoJAh2I6JKq5L
bYmiU0NWhsESlnhkb8jmtJhD88KWzmNIbTGhKL9vpIcwWd0ActjVgmTNHp9O
MUGAmxXZo9iBc3blYjL7WfY6/It5SktrOzI1Tz6HMET6iYB7mXbMeSiRCFr3
uzd3IiQcqs7dYNUgVPP4zaZ86UAGQW483FaXUi5xb21VfLBjwuFK2b3HI6Fe
NI3ohXT8soshGRZfCNR1MGgLdeeCo1Y8eR1k2kHxICV3rvFR8irlAL6qI4Xy
D+UG+E//YZ3qrdL06MMP+icZNwA8kHsyOX32ZPLs2+9mp8++yfxveOTaB+u6
ePJs9h0p0n3nR64ZJACeQyEa2JqETS/bMOqoQO2rVj7XTm4Iee+SQL/rNSQn
GZPN6GJGSVGnan3JJkJEiDmohNCTYQAFlzzk0Se0lUwWxbn+KybPaZ3nrdBH
Mr5DjFC30xG24nxQTlEHamDseEpn8mZ+EVC/0rS5R4kDSaK85UGNBL9CjqPQ
XPnrcKcmbIXW0Jz8XiSsT++uGfWhPvt433Nf/ecC5OKPWp/fwXpG8MYsCx7c
7+TfgnD5Hb/opzsBlAr5RatC9O/fFkD5G4A4j/xmKALH/vwmz/CbAklNVC2q
Gr6JuB4Ip47wbcWEOfkymlIXVXKMQHTAEmf04I34e32EJeHsXkTgZUqzN9Iu
vUk6EdDmnQrnpg3DQ84ySsIw7T3UxTjNl+dl5Yo0qE3bnP1/pOmm0qK6oP+8
59yYlR/sruKKpEkycKsw3xxZ9yji1dDk6dPvGMifFnBW5QcjCQhX3ZPaYUpN
UKVrkpFZWjUryM2tkq6g2IYCyS5kacNUI/eu/AvPJvz2STYvZTiezQGf73vG
FhUtCtjqoniXxXwUOKKMMvEUuLwOhU6vG35trineqPfPaJhoDX/1r4Ju2Iop
rfF08QCf03+bPj71P4HxYrIsMqvn2YkwwsUjgLYMEZF/TWwSEVbVd+oN/TO2
dNwn2uNRmVAKoxARsme62G0h7V/aeXNTsu/wxzanoB3BfZg/q4uCzpTshn7f
aVXw9N/CW/AdSdizereZcxCrM0FLGEP8IiwHI0qE1B/+tSclGT1j2cGgSZZl
/RLM9kapRDn9YaL8UkY+xlMgVby29si8K2pirVw+zv8oSZD/8DRLcUbiUXFy
A570Hg+oDMMoufE4zKnkoXxavYhfQXcW78z+TK/MvlhvJDj9Zg7CkAj6KQ6L
EJ4JkSQc/3W5jQaV+C9n9Pst9wzq/TUocYcmQ1upyWGes2/KssoMdM/XTdPZ
wBK8uDRBxox49CZ9JYs05SVSpRYN7rT5JDMewSkIFsF5hWlbcvUj4zk5xeTZ
MY9M+Bxr0Ivg9AWDozWHEGQNaCwriERiwOANHgMBysV9vVi3JDl/0cQiK4FO
pgKHMPriT9ylOFxdoS+heyG5JvLoMXgltsP4vsbO1JDdlBvG8tpoRMGSBQZd
w1OKePEKMz2NADQCbi/OwvvnwfDELB4Vq/uIUujxple+Fb6XLo7i5W+fI2p7
Od/Lsx/ASexpwovzIg55Yc8F5xcGY44PrucKgzZgcEJc+zXQYiynqWwjSLsn
ZTLz19mAEzl3Xrv1TN4XHkd5ltt8YncqGBkmryR7k54MVr0WCOAV6QReYTTc
JMaNhw6RMdnSQ51sKPJrQ6HF+LVc2FTigjxnvrJoMKuGSoOv+3Am1IGYPjFg
6rqvvZlNOjGlR16zzN8+YQPtl9ZJhlBQxOaffKv+yTfPHn0D/4ThR0lw32mn
PPDRnPeUYUO50InxzAv6nXlH4XH80C/hZeMxL/WV+/ny7Vdd7O6YEyNmlX7t
1T79E0psYKz0CtDlQatFYzU2Svap6+1Xe+Lhs3tnWoGzcJEqsgIQ8kBYRuFs
G7V9jvY9OsAp43hdXJHH6qPfqMeYH8kfqYEiSuiJ4w7RmA/HIJLxUGahWJ9F
oxuNHpaVWGQITR5dzGnLm8kepU+m2QHVaW9ybpAz2gez58KpjXx6rcfV8evs
1LAJrneMOOIg7Ag1FV94TWqc0iq0j6CGZQ3a4xtsaiAd1YBi2wLTueUMWgyX
zZnGN7IsUtjL68i4s+Jn6NauDtTPLA7e7pdiMPhTpNFqhCAOTCZJ5iIsUhgr
ng17eZRNNKwy7LHqpLI/T5CG1spnhYyofFH2E6lQCINsmqKlk9kVAa/Ml+dx
AEl1yfeS0Ivgg3RuBG4WgfeUmWvYrxBAczqToIgyP7ww/bHpa7DraaZeQWVd
E0o27t0f3vz60wtOZRlxzFCElCsXfBmYyuirGHT32/p/DEB5d5784/2CW0/+
syV/QvbnaZySuCX5c5r9gyZ/vmAXf/tniBMvJCGhhffOZwlpmC/48AMS5IeH
+ZlAcq1lw2OJlzSp4tvGIyZ3F4hf6DThEfrbG6Q8lkS1pDtoPBmQ4gontbFb
D0hI4Vu8Erjw3RWVYb7ewy/F5XEfP4byzecZs0yxfeLkyRiT1C6UTDjhxCkW
JyxN4jf7ec5G4USPT7+J+Z7wRjze563+sGn3wfR2UTWHu+7eRyPeDNwVhnny
hBznJ+SMD8RJxuYcBAw8uJLijCuMRGbcpXczdF6nPdrE5ib5vcK0LyeVnj5O
DSxNdvz4Ci9EbKTVMfM59QITz40xFjkJ2oqSW6M7ZvhkfzGx9UEMZS/4E2w1
t7GIBMmX4PVqlzOfoE8ryo9bZu5MnlHygDqnURxj7DfwajxtrB+i7mH9ZWBW
MJdsXsYLp0p5HQZhtrnOQDRKSmb1B32fQeK4nxFLc6wPgexXkbe+mR+OvxnH
Hv33msawKb32GZsfMDZFJxog5gtFmqmQveZxAF0fzgaeH64ean9R3k0aJVY2
Ni7ZZCSFVrtKfBQOpUd9oMgBy30+6sBNjLNkXzSkhBkaIcQ77ZH1Eh7eiS9g
iI0oH9AN0QPZP5lrtOQgCe9aIDk65isOVS7menL7kR+WrMPRDpJURiepOkNQ
ndo24RT9kVTT7dhxbvF6kEy0ZYrSeBeBH8FK4gfeV4MMqfXRxc6x9uJzXIVd
9iSoandIQuyouheNRhllp8wEOIOcQBi8gvFR5BJ5F4u868GF4GykAYCTOp3C
1yDtg5rn0Nwm07DN9zZakW2WO4gnDnYjVRpel4SmNSczF2V6EVNAc/oXqyHz
1+XO/HTaqDFMN6KCLy9xtBuXPC4ZwErbzF61H63NYQ1JsnFTS5k2axnZyUF+
ZPEyDyFFUg+5gwVPYG3Lv4iZcjo3LBCdWblAGbqFjm9GvkiCAEIKApSZrUSD
CIb94PRI5WMDSDrOxZxFH91E4Oc5FBpw3W3DkK+IWZVsGdlO5hWIs8u8hAnD
6jQwrC4VSNGZAh5PWDplWR46/pGuJU+/Wv5/T5/+8Tj7B/X09c/Y7h15xt/a
08fM4oGnHz3EiGsf/bb0SWnDkmTp1MFo1h+PWzvwIP4Gr9x3BXvW6GnU1yzw
swHhKp3jaznHkX8OsDon0TwFYzqHJXRVSzLvWDe5KDeE5cFDoieSBqC/ye9X
byjJdCZuv2JyDn1FBu7CAfrzDulI9mycrUmAAvv5DdKJzntzLjmUkGBhJJZ6
bnSVgSk9qumNRj8k33gunbhfZPnYvTLGfmvBayPQkLk16YN6eyGTBDGjhN0A
S0yVnRQ8S+1Kg80CrUu95EgjJh3oA5RZW0YApdMqLXskkxgLdBSeVK4yzdS5
LY8XbJstuSjaa8Li3hsOtODwotJRDtl1vtgxxwjwfS5gnATujQJ/boWNBJd1
Mjt9ln3ITh7928lp9n4zsZktjn/RtxAiuvv7jRQ1xYjKqWyFH5XXkHz/KxAh
F7UPcfmw6dTF+rqkaGsTOvs35GJc2yR3v+cqAs1c3R9yBsX2UuDJIeL5qB7z
tNZBfJfJ8EcnjwE5aMtORhUq1wh+1tRCjgqMOaMglGhf7N6xYQzLavuf2vLF
9Ha3Wb4n2T+K5UsY4qqtWZ3xDQx25/KuRhuFUHSeoirB33N18hzZaJmVZVM3
bB5IFzEhGRr7iWnc0NDLoYsMNTLi96P0sNY5BMKgV73xbSysuT8a3HQnz4WL
KeOiBPZBi4bZSLNT3pY6a7a1tgzOsI8gnz2ZRRIlI32OM8qpIH0LrvdG412w
UDo7RJTtuegf8afd901TUfw8yTAcJa8wUbaD8y7cqIFcPipGTfxMTj+W0oaK
cEgnuRAZSjtS0g9ZeWH2cVxx81MnAgnHyNSJg2kTTiYe6GQXIcKyPj6+7OgS
pBV8zrRJSzJXJybxXt4m3OcR3FQbXMWUVgOcfai6C3W0R9VP4v4Mlx6RkW97
0TycTYLhIs46zLjfZ+Jxr2kDkcqkjeUxQEE/mMilBzIZMCT2OWG3PxyLEIYd
HMxCGExwh/0o+jIF6//7jr67MupFP6pXl3m43aHIp7XiIy0wStnE3fXDEcQH
bORQMJFiiDkdN/CJAl+4HJoJ91JqPI3pT/JyEFUmrCRtV20nyUijkJqyeUbO
x5iyKX6yFXkGAo70ThIZVm3ruEgGTKPVCcX0j/fH61Da4TLOgFd2gxGB0CPC
mUFyqdqTi/U8WptWdLPJZX4A902h3W5AizNLG6NNAzukkdJWXNHTj3irTgLv
9bdGshD//rGLiIGUUYIpyBPVL8X7w7ugrxEF/8Pr038ejJiJh9x4qYv0afyN
6OdvB3ePui9Hei2P/ByuwMFsXHUWTh7SXV5f/Ok8i8qUlllDZPAp+sW5FT0T
3szk0+7TlxSy7O6nevdJfJKs5flTaAFILhtP4NXrPP4brjOueu1KTx4mnx+5
aHymo57QdCi7+jnjZ+LweKlf8SPOhfT2DzyOkOPmtp0vWGLSiSMrxsgVuOfX
BfT8Okd+rWjRgrDopFbE2pzelPNQLvFYYhvKYWY8hzkdQlSgSwNev9OZDTBj
YVQDN1roCIfl4Ywcnt0Xt8kfWYcjXWy/Mq6jZ3Il7q9245sOX4U1aaG4QoM4
6lSX2fDY8GRwD5xgtyqSDS5u7splLqNmuH37oAwQHbM5D/jowwH6gjGhPj+b
8A9NFNZxzCdSE254BR1luqtDTc/a16ZaUQgtmjpXBtlHHvcAXMq8CLunEaJu
aLNr2ReNx5TFnKGQy9BwfTbEs8hM8ANtFauYDpivvVNHwjRReDXFz4bssIJ9
Ncctv2DHiPO54n9yN2Yg5Gr96JUWMEXhFO7OY/tqlKR80+gFXTSM2CPixJaZ
f8YPGOVSqvxDpu18Lmne+YW5Abh7xw6HxEZCGjBgr8qu4BHVVhfrTHorScaH
izhleOLiDKgSlqKfziKw3enMDxgQBpxVoDHSdiype3fY6oJ8wI04KOqOcGJh
omMJAieNv8oToNIEHWSv4eXWqDqvgg+Wm/td1oFpipx8G0hhfBRNGHxvAwk1
38Kj4rjiEpEBsOuoZUn1cnlYcc+JRXugzvfaA0I5/tAOsZEMQLyFdtzoUtkx
Tm7hQm5MV3CiZ3RB4SP5wuhX5HKOEYvndfBF1Y1VxHaYIi7aLXq0foz+w+a6
pEQqoc0VJyweNiblFczIjPg6vGY25Mady2BsalKLd9ENhNNMO1THHUvGaoUq
98QdZ27wuzeUKHXWDJHmyfqGETq2uW22Wybl8CR24XlpAd/YQCg/3Wdq4VFI
LAfKXybyQIdkbq0q3ZlzJ7Se2KUuCc2PMJBy+KFhvueddFmW5rLDSfVicydT
KS5yB1npGFUpQ2BWFDFOoIzlScD3zUOpAwGhYgJpzU5n7AlJeH4w6PKr7jDh
oa6Emh5UBeguA8eCR9IaDTzd5TE/VZwBKIfOCzaXH/9HL7p1LKN5x0siZJrc
d7wfJXE5OjHQHgGXkesK30vEcDnw90ZDhkzm2h+GmqYxUwKYjZ80wD9OXSBc
J02p3YYzzMZZaHCRcSIaIZ8xRwOkM1EYPeNnkXpQmOoJgZHw8EAWshH+cG74
RWpvIM24jiXE4gnEkpg4JykptggGbVwtSynJyZMxOfH0uui2VbTrvAipumRw
g1+MiPhqjHZXxY1XxitLvcAXGI4xyTM+bWZyUh0Q8UhxpjLwSHV0/Y7dEuuA
H+HQ5aM1RqM7FianghcoqXGRL2n0P4BwxEgiXOSQ1JS27Jtbt8zezVN46fIb
yzo32WTm0sKUhW1Vxe9tmg2zS7g4s+xwixTfEHuNx9y0kIkan3igs0kU1c6i
PKCou5WUXTIVEbo8ogy31zLe8Ho//gxaYI0oUfwpCNlDnWU/xgLuUhbwo5zf
Sel1MMF14hQuM6De5uT4wEDYVA4kjjHKFzwaLhoKMjaxcuBHREbalsndSq8u
vG2q/G4zrcoD/KV21QOyvPdAyn+4c2VvzZ/zvCv5oEulrjBLxDCeVS6tUpZu
U9ZWzumP0k4D0ceuo89EkzmWW4CmqGTtPxlkRplTGdCCiEhZJjDEBVy4sM3K
SdXyQVLzHqgRoyqDztMRs+zzjFMzp6T4tk74NJ4AgaPwRohL2/LcDRZdnn2j
8nqUrDRqt8RlxWUVxq0tt0zZK7pFlW+2EnRgdFVy7kgv8gPhaY6g19DTGHcM
8OdvCYfvaA8AW6FNoOanR5FD3TYj8IrcCZuRMq4NDipI0RRg/5J+fw7iDDwq
6cBda1L2A1d1lDgsVgFHH1nsq+vKivMb9ODQ5CJkd09F5Wyln5MUmU85r4rn
5NbSWci81pxbsJn1HuMsc5KRo6f46IMUPNQKcVVoXB713B7hgWYeExngyJkh
1zdsqm4HzQxkM7h8G/QZRdFyGKlAaoAjFT0Ao0pg/PkjiF8eciQ6xwbnQTCC
LgYssplmbDJTW3eeoocDc03LSACPLv2Ou4c650dJBAPiz6OkSn6xdMzbQIz4
8b4laT5zSeN/SmcQlvnj/Wv/D/rlG9Mf4ae8kr7FjNOht3pkXHMQex5g5nZ/
NDgkxNrskSA2ZOXBoqcTbo5NNuFdDHT5Og9X2O4SbK0oRKMOeFF2bXHlA0VT
n6LSNb2AKih+qshETyzlkuaoaC0mZmeCq/O9pnb5KrBE43I9SfqhIUrx6B/n
B5OF+aJyYMMonjC4lD0EuvpVbq6t0DN98+z0u8+fz0Yr7KAjardso5iaLEIZ
2wYh+1Crf4bODqYTFEeDAxgVWEhIRMWntNga0rqkAseZ3VyiVdkMccL8B1TJ
+1+PU6wN7ikHD8e3kN/UkYWn/8NjkGUABlsG/gTdzt6G+qfJ+LC4EHntz7af
DCPDv6RXgq+LPZMeauvqVsZK+aY+M1dT8GuuHYqvIb6jUz5eJt9siw1uekQh
mqHjrjiZp8FvmFj+LkFgC+v2RdwqqxVlFXt/d6vQG/Q7eDM8Pyz3BW7uFI/m
lU152pkrkCRfcKZzyHYfaBA4pyZcf0nWV6geCydLF5FPJBiTMH2Krttm3ytj
Ag8Jlp+NTWX22Xuby1zY4HrRHL7TwqZsOta56RIg1Vkbqw1nJcWOdEmn+Irz
p/QGbLLFeLDlWIMie8NQOMDNMdXq6HSi66ZEJ/eG/HRGwIHqrdAsXQ+umh4N
QO8L0XQai/kN19bNP+DEwjbLKHAP6Xhf7JHjAZbwhqQXGW8DfOQyDgS/gkUN
vwAKkX/uyggcErpMl6HRVw4CqfpAp639zHI4kovYOHmpMxkSVcZKV/B66own
R0OzBXZL6UeJu4bgNVVyFtKHiHOF6uT3ceI/Rs8UMcOxFCJIbSJtm3bbIZwK
C8tPkq0NbWmsROQWtIZm9BOepBVJWwsAJ4VgBAMo0mFAp0DP2YlW2+56mwmG
L7MaoBDIyNgjxDxCJePJne+VqMHWxjfNAEFhet9xR4cqfPT4WzlHIZWklPoi
4EpVZ3MlLeWqO+jzVhaHgp2bducbh/gdWoP3O1Yt6iZ35AJXNdK+cKkF58Fc
DZfP38IY/euvr557spSIoc4pWeBFnYBefVeS0HDyWi79L3VB1RHkLXC458Ri
Gj+jh51z6+fRCaExsbIHlih6Bq5Cs1rJ2KLG02Xw+2+1Tw/5Az4JrL4qP67K
xQVHIfDmDIBvveNYQfcYI6a7RUEGoGyYkVGB2IwXTkns9Zdye701BO7t9Qsw
0ZdaPnkV7q6TrZ8+fXTiBzCxSxItos0yiRr/cQZCstHj72qmH+SZAfmCB1NK
ivMosFqLLXmdgKa8iQfrDMVs6GHhqX7yXnTNXQ1gDx5HptDoI4dFlWKKUSEy
42Uajp1r40m4LHbvhkSCYwlQoeBLZWcJWBCs+yKr11vimP9EHg0FTzwngYOT
crmsinnzITZhFX/o8+GIUKMQwOmIuTcPZ5dDzHmogbPBn4PA8/Z8aspECwvC
NAR8urt0PN+AbnlAPKIQNiW3mCQzXp7NTmenWpB6dvqMxx8qbFDe0Y2lWTud
kjyOZZqkQCaXAJkeSni66s09gn4kXTLR+V3QWSgIocVqC4q8IUWq1zU6fY5k
Jr0gXX8Nj1X/udy1Axc66dQ91/nwT749wXH1RdXVruVjtMTOXwlTyeUIqjJ0
WvhwCpoxlCFiHiisp+bC6tFWKqtXBEBX7JYpl1aA4qG5YdcxY17DtHs2u2pw
gk0nIJWn6kiGGjFeln34qCcXz28HjX2aMkofRuMKflBOeBvfQYcX/agbO04M
AjCnXF1erE8Y9IbJxeXWyLewaT7D4Aci7+pVviHpy9uxccaMGxTgSwVp2Zu7
D2zoraNrO10kLFnnunwlE0Ike1OhXWjFoiXmX60Jk2dEzrtxYTjwIhc3PpgO
jrOumh5MZFw7n102LITnX4Vf2klmnfOk56Zhnj2KOw/7tZ/JE27k6X1nThWc
XM0XcYzvBJNHrLGVNLPNAcw7zZh0oiXfRLw2z9PG2Y/3Y9oZ536099CoUVqK
Is4DzvxCKU7RmThQfWMjP7u0OFwez0px84sx8Hp0jXGm8ZNwB5AS/xhzo+RS
RQHwhzo3FuJ4KjFpTTc4zqDFE9VgBG2oFjnDOjWdDUFLSh3CZMAHSmDnrLBu
iqrydVjzfIVjDRDxg1rz4UQDdl+Qw1XAgoaVDGwva823k7dC79yjJ/fOJgZo
HRcGjkv6AJc75h44r124/8nWl3OPdt9wkmYqYFDRlsbEy/sdw4yCMidjC/Rf
wrRmgWGkm7XOE3BO5uOIg21MDNIHjIMEifSj/jJFWPvLaYZx1QskoeIJ9jrE
RQKouBQD7QNOBxR8LS3oM+5WKUmLr+O1nj64DJJaTwoJMRXQZcIDlFQxDqvR
Ydp9Tm8Mx7ZMB/A05kFzyr1i5a5joI2Ro2AykA1CJqSfZM+wfAikGo5NJGWN
2xjcivWydjyKQlYNExFPcKY3jeoCy4ECHGK2g3xI03IwKYqbQ9yvnG89oDnw
bnU1nFER3Dxl6OLVv4XScF7IOHtJ/sfkhim1oUuJEwJOr/PRkORctPk/883/
2u7vIpKry3VC+Sg840h9lFaW896N4nCcJ+u1oDMiLPijZQraA8IzJi8MYxWF
+0x5zUFU5U8vMxXCTag5kzfKe+YC0cEtXGec4KliBsXAh0dWy6FvyvPnyMhe
ju2h+MMdV0hXzEkp8k4YI9eAcWJGpuTLOBiP8Dq6Ia+j4X/6O5kZz/mKsj3u
CNnkCKZEzb+6Y+jkQgWAU1mcIUNff7FMklfaA6r1X01XTcRASk4Yo1R6nUAr
NiIoXTnk6OMQOJ+WvXRorjp1dAPxF17GjAfv6Jo78Wt+bPIKLkMwl5YUjAK0
vHvf8ZyNKMP0PI88pBiKYgGWC1ITwUkGsNYYuv377EWT+dwk0wQ58sWg5X3C
xifP9raHSeqVIcMHH3E+3xeUdBeP4938fmA07Sm75IUErjtIWCbsOLGNtTfx
2U8ZXmKpV2Vgy95xIV+VY9gl2ZIpJ94VuBttSLurO0Pd2XHAPGM7jr7iyCWO
QXnujF4PKX91tvg7tK3zQvmp1ZmB7w7BdPo5uWFEB2WrwXCFAQLBtxWStu+c
edSqrjtjLJk3QhWVFRvlGU3z8X1DDlVzxaP7bpniazyCxnY45ykSrChJQSxa
ckhIGL39XGb+jWhHorKejhEK6bIhTle88U5ddwG4WDpsUCDLh0hOsXvubVsK
QvXVxc8X0I+kAuMiwnjXhwyeinIm3MzODLCYXKSjcoyRhu7Bzdi/dtbhffrk
u+npN99Ys/+98fFW3BOsWET+e/ZuN5/yNOB79GZXUMH7eKLJRERCaNcPqHkE
ogJ9hKQ7kD1K4VUsXb5pVFQlsi23SHTN6IZIO4YxHdjaq6qZs0ewq8s/Y6qI
gTCBlyg3UsraRy1wYVW1abczrvNqH2NVkxDhEF0j5nwQcHC+nUNZJ7dRtJgn
VAedasfNTgnJDK84lpLrpQKZY9o4EBcBSJSqFT9ySzcVQJ91ru0FpcF/hM8m
1gyiU2z+6TsGW2cvpZ9GytisVfjnn41PpyUbJeQ3KoSRplnAe2zrbqBmiw0Z
PTrJZ85NYzeOM9yLHhnpMw/xCIG0wAviwWDYEyYsHrEVDD2MLcQkRo24FGks
qpIsBWuk2jKXDGrf5EtmNy9JN+2F/Ag+GsMDQyVlsSalKWkLSezsWo/ILjVE
wc8l4DU8VKaSEV6SiZJkNiCmCHk0VkBepGM6CwE7RoMUI5ik2IlpnGamN9o3
VtWPpPNM7BA61+EUkI7hOfJSWQXkkN40V7oHfic+IJaqu2Okn4a0yhSvxXF6
TitLif78Pefa46+QdzGR54qaZ0ANzny07MJhfXho6xLA3yrzPFcqIpZY+T3W
4W1A5Hn6ae518JWQMy7KcX+Reuv0tjyMmjeGbu55BxVBis83FE3WmgsMZgwr
V1XxJ3jeRiaDtkRI25iL0GLWLuaVtb4iFd4Ruvyj5HcM097COKqewSawQLxJ
PVOK/XWi61kCrYrz+AwobADyPYhv7aSQZqu4gZYVu8+ZRvkC2NW6oF0FzX14
qSD/PKxWSzQJ6TMquX7koILZp1EaCo8XJ5ZyDvB1xK4Oa82r2UDjwO0887Hy
oFspk9mpKGTm2wxOWC+qhrcwr7h3kfasntJdQnEzcKwnAXNIC2ugzFcRL/Qg
Rp5aIUNcKqthmHMhUrqrN81S3GHxKQLNC85rmpSzs26JdHZsxFnqWcAVCsp+
CwhcAFKOuVrixS025O8tVahWzDszpW0soSHAoD/gRqeTriUXhMiy79xxZ/lN
i0tD9CurI7X+sWaSOBF9kGj2uWToCp9N5mV9p3Un0dEeo3Jc7EOvqICs/Mp2
0pPvc6UV92cW217A3vH1IiyM+pF4vQMDJRB5j2ZOjj303JW4zbRfVfwYXKsH
eKyVPr4x2Aaph6ppYyvug7HPMWe+WnJvt28OAn7PXzlEazhBa5iIDtoQUTE+
H7oHZRd73o67OJlfUWYVWRWQi0fsK/xRF8Ny6fmXYjwE18EWyAM7ZEwf6rYl
axhlMhXDJbRUSAoA9JibPVf9P/XMXxWzJ5QNMmgyAeWa4207kL4zS6MS7NsA
Q2ShpJ8+6Q/I+2LPIDl2TiZ051XBOApVnt5IsK5iPKnUCHiluIDmIX9JbZVZ
n7ZtySizg7PFTokBGUZBDBGEIepHFUeZ83jcLWSSGz6sW8aXotNwbQH4tmDM
YgArzOLNjurRnc4aUa3JqIdWs3Oxi8nsbzZIw2NP1RzHp6o/linn0ThJMZCU
GlBqnV41JBXibc9DkwQ26Q5gcLz4YVQ8Rzc8tMlACIHNkXNARqvhEcHk/Pmt
FtMalkyJKc3AyuvPdxhMYViFdLmTuUR8DBJfodt3dH6SvL6X3IFRj1L4oUgw
ko7Xos6SjSpdg/PYJKngVGJguHck6KF6TvnpmGYrHMAJvFheQwyj9IflMSxU
8RPKfMFhoeAoqHuFCyU8sp6/DIxp5N8uO3EHWRld9JinBMLYmyZhthuav5D1
YcZCmRCcZUkfPe0BOSa3ZcTUY2V5QOu03V3GH8WTKrQGa2hMjh58tgT3iecC
S79cxHs4eNVQmYysost8klaPfBRVpPpNqmy462XR6dHMqriImbg4MOfwbcRn
FMSE5E1mdNMj1psBIqravAmecdwTdqXn22voMKcFXkk+P+QMPeYTUHOWfkx0
CrXzgLDFYSiueC0vLd0UBs3xGQAxjjIsSpfqRhLI0BC1DY1mdzpEdppZIuH+
RQN4rWNZvgx2Wcesx9kcfvGgfVGx9l8nHQGwgpBJF1r/9et4UPz1uBwnbQo2
TxrMSQHnU9pcpUQ+FZDdCAPyfO+GB8HaHBppCmA2+FqR5p2wWPgZJKjqokbP
QHd2flpmLCGjPJXOXqQD3huOYsRl44KFEtJraUpcFI9DIJV5U2jFLYZ250pq
BLsrANnDPOgkAe+rXdS2BMm6D9ODE5fEAwphvmoRxR421oYcVzRQyimJEoa6
JTDZTbw7mnhOoNaqxxrr8Au+t3oSjFufamge+xV56evtHTdQlfW/q6Xyo6Eb
Hn8rQFbu9th10oPW4kltjGTNaSs5kRIghyCEIaisKOkQMFac1sXvu3AjkEfS
FdouKb7wHe2I0D539eZo76mZGJE6cSCC3Ylk40EE+n94FH2tTRTgjfxBHnbc
QRUgfWBg2FbkzJcBJ8YGCjXenYzOGeClEty7rD33wqHQlmaQPYutqfnQp+hZ
/qOlHfeJPAWiWE17qAQDSsd6DjwmCsxWICD/hI/siicrGDurh90o6UKjI2qk
eT/2QspOBwpq0wod9mon1br07tJC1Slzer71TEdinSTqpDe0nok566y7RMQs
4Bg4wh0lpVXtxiR6OgBIoFQjKEr3hSjKBAJceVQl279zd0Q+WCjxNMqnwyIx
yFQw1LrkaecpBpsxeELUm3CqyqVR154XEpEKHz+928TJl8YRKHlnhYdoKmx0
LRHAicsjTv/M8wR+CXBcSyuMxWOyHi3mcNtQ4Lf009rhIzVRc7NSwmmPhgZv
Gw4fnC/I+FLNoDcji3ozRgpElwBdBmzHkbKUNjZbI4zn12e9yiHx3sXQaqVF
HEkRK/nAgKORYUyeLkgXvjHCgdBDS38dmCz6SeSqMT4Poxxqb41nd1OoMt3m
mhFbhzypzvIt3d+SWI68NBe3LUdAHlGV1geoqVoc7bmwdOeLqjhj+LO+CRlB
ASluctZi3UQ7L9WeRWQ+naLet0Zd5gklxyglmCeALsIEyWZCBXDSQ3EzKKze
u8jzjAhb9Y1nw9xR7zmYTTSBJZ0asFM7bjW9EoLf0ESta8M5vUk6Ci3NZoVG
PHwt4DwkviYVLa2jeAX1h/q4s9bbSJbmSTZoqVWSd8s7OIoMe+4KGM4u9tZ5
pVBVG9lgrWZHLK5KvcmZMrhoXTrWuRMneSgUzIBvipKTMrqRCzvXRRJ7Rd+f
ucEWGbsUnzSvV7YefnseAW/Ec1+7+KaqvzH5knnfBr0rDFqIfxnQ6EZSSt6T
lfMUGdPF8JaIzGZIjOcU6tUNmrbHFi5u+O0Dyy2gQhHTbSbNh5UMlXiTIOHi
HHxMaMGjsRMU2oPjxGGTmP/roeKvZJyhby6zFlCy7f+6a3rzh7fAkoXOuGFb
p498lAXLq1Ip8QcSnq78S3EeaXIPfMYzwNUcQPCjzDKTqCuNHV2ADNGGxOtW
4o2hfwIMDCtXqXT7mSwJuhATsP20ndhPEpRrsvzqCEkMyRCEg/ixpLjdMED+
QaCROPqmZwFCOZSzdbgrfngMNSxtla+iq3BLY1SlR0xfi2Nx+f0LKf87BQXT
K3M5vUaIT/LosQHIgDZSDvvBoA+/FbLhjIuTNxrkg+d8Mm7qFQJhjKiTIWfj
uf3qdPIFbDb2afd4MlYPlMqLsY1Oxm30JDNgghvOhp1lP2jfhFxD4uR3CXfb
L1qyEU9H3t9W6KtOOieWOyHr/oGhA8+hWuWv74Q+BBEKb1PnHk1Pn3w7u02c
rFtdsgcKrph6cMVtQhU1ahzxw9QzUl72sxGO3S57NEFTDLe/yH9Gm2f8h04S
tl/zCcs2SnIKHrZTDH9wXt10OmXsI07fxcKwsVIt+3hGEj5HueJ391Z51RVG
Zi8ZA9Yj77vsNfky2UW9JIsp3Tko9iM3BK2+E+TWLPkiu1cXr3hJOxly11TK
QyhD/DyltR8iHNE0LskOeLVaLKUSilYl61nkKDRkDkhq3rf5ZkknetquFupy
aSaNAlToTYoca57MxF1P0AC0xrTfUWemMxW9KmvGxn/ofVbHg2o97XzvX3fm
/h/McbDASQ0BAA==

-->

</rfc>
