<?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.4 (Ruby 3.0.2) -->
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-peng-pce-stateful-pce-autobw-update-01" category="std" consensus="true" updates="8733" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.19.0 -->
  <front>
    <title abbrev="Auto-BW-Update">Update to Automatic Bandwidth Adjustment procedure of Stateful PCE</title>
    <seriesInfo name="Internet-Draft" value="draft-peng-pce-stateful-pce-autobw-update-01"/>
    <author initials="S." surname="Peng" fullname="Shuping Peng">
      <organization>Huawei Technologies</organization>
      <address>
        <postal>
          <street>Huawei Bld., No.156 Beiqing Rd.</street>
          <city>Beijing</city>
          <code>100095</code>
          <country>CN</country>
        </postal>
        <email>pengshuping@huawei.com</email>
      </address>
    </author>
    <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
      <organization>Huawei</organization>
      <address>
        <postal>
          <country>IN</country>
        </postal>
        <email>dhruv.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <country>CA</country>
        </postal>
        <email>rgandhi@cisco.com</email>
      </address>
    </author>
    <date/>
    <area>Routing</area>
    <workgroup>PCE Working Group</workgroup>
    <keyword>autobandwidth, autobw, auto-bandwidth</keyword>
    <abstract>
      <?line 55?>

<t>Extensions to the Path Computation Element Communication Protocol (PCEP) for MPLS-TE Label Switched Path (LSP) Automatic Bandwidth Adjustments with Stateful PCE are defined in RFC 8733. It defines the AUTO-BANDWIDTH-ATTRIBUTES TLV and a set of sub-TLVs for each of the attributes. The sub-TLVs are included if there is a change since the last information sent in the PCEP message. But it lacks a mechanism to explicitly remove an attribute identified by the sub-TLV.</t>
      <t>This document updates RFC 8733 by defining the behaviour to explicitly remove an attribute..</t>
    </abstract>
  </front>
  <middle>
    <?line 61?>

<section anchor="introduction">
      <name>Introduction</name>
      <t><xref target="RFC5440"/> describes the Path Computation Element Communication Protocol (PCEP).  PCEP defines the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between PCEs, enabling computation of Multiprotocol Label Switching (MPLS) for Traffic Engineering Label Switched Path (TE LSP) characteristics.</t>
      <t><xref target="RFC8231"/> specifies extensions to PCEP to enable stateful control of MPLS TE LSPs.  It describes two modes of operations - Passive stateful PCE and Active stateful PCE. Further, <xref target="RFC8281"/> describes the setup, maintenance and teardown of PCE-Initiated LSPs for the stateful PCE model.</t>
      <t><xref target="RFC8733"/> describes the auto-bandwidth feature that allows automatic and dynamic adjustment of the TE LSP bandwidth reservation based on the volume of traffic flowing through the LSP. It describes PCEP extensions for auto-bandwidth adjustment when employing an active stateful PCE for both PCE-initiated <xref target="RFC8281"/> and PCC-initiated LSPs. It defines the AUTO-BANDWIDTH-ATTRIBUTES TLV that provides the 'configurable knobs' of the feature, and it can be included as an optional TLV in the LSPA object. The TLV is encoded in all PCEP messages for the LSP while the auto-bandwidth adjustment feature is enabled.  The absence of the TLV indicates the PCEP speaker wishes to disable the feature.  The TLV includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs defined in <xref target="RFC8733"/>.  The AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change since the last information sent in the PCEP message. It also states that in the case of a missing sub-TLV, as per the local policy, either the default value or some other operator-configured value is used.</t>
      <t>Since the missing sub-TLV in a subsequent PCEP message is considered as no change, there is no mechanism to remove a particular attribute encoded in the sub-TLV. This document updates <xref target="RFC8733"/> to define such a procedure.</t>
      <t>Note that for the attributes that have an associated default value, they could simply encode the default value in the sub-TLV but this cannot be used for the attributes that do not have a default value.</t>
      <t>This document proposes to use a special value of all zeros to indicate "restore to default", which could mean going back to the default values or removal of the attribute itself.</t>
      <t>The following table includes the sub-TLVs and the default values as per <xref target="RFC8733"/>.</t>
      <table>
        <thead>
          <tr>
            <th align="left">Type</th>
            <th align="center">Len</th>
            <th align="right">Name</th>
            <th align="right">Default</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">1</td>
            <td align="center">4</td>
            <td align="right">Sample-Interval</td>
            <td align="right">300 seconds</td>
          </tr>
          <tr>
            <td align="left">2</td>
            <td align="center">4</td>
            <td align="right">Adjustment-Interval</td>
            <td align="right">86400 seconds</td>
          </tr>
          <tr>
            <td align="left">3</td>
            <td align="center">4</td>
            <td align="right">Down-Adjustment-Interval</td>
            <td align="right">Adjustment-Interval</td>
          </tr>
          <tr>
            <td align="left">4</td>
            <td align="center">4</td>
            <td align="right">Adjustment-Threshold</td>
            <td align="right">none</td>
          </tr>
          <tr>
            <td align="left">5</td>
            <td align="center">8</td>
            <td align="right">Adjustment-Threshold-Percentage</td>
            <td align="right">5%, 0</td>
          </tr>
          <tr>
            <td align="left">6</td>
            <td align="center">4</td>
            <td align="right">Down-Adjustment-Threshold</td>
            <td align="right">Adjustment-Threshold</td>
          </tr>
          <tr>
            <td align="left">7</td>
            <td align="center">8</td>
            <td align="right">Down-Adjustment-Threshold-Percentage</td>
            <td align="right">Adjustment-Threshold-Percentage</td>
          </tr>
          <tr>
            <td align="left">8</td>
            <td align="center">4</td>
            <td align="right">Minimum-Bandwidth</td>
            <td align="right">0</td>
          </tr>
          <tr>
            <td align="left">9</td>
            <td align="center">4</td>
            <td align="right">Maximum-Bandwidth</td>
            <td align="right">none</td>
          </tr>
          <tr>
            <td align="left">10</td>
            <td align="center">8</td>
            <td align="right">Overflow-Threshold</td>
            <td align="right">none</td>
          </tr>
          <tr>
            <td align="left">11</td>
            <td align="center">8</td>
            <td align="right">Overflow-Threshold-Percentage</td>
            <td align="right">none</td>
          </tr>
          <tr>
            <td align="left">12</td>
            <td align="center">8</td>
            <td align="right">Underflow-Threshold</td>
            <td align="right">none</td>
          </tr>
          <tr>
            <td align="left">13</td>
            <td align="center">8</td>
            <td align="right">Underflow-Threshold-Percentage</td>
            <td align="right">none</td>
          </tr>
        </tbody>
      </table>
      <t>Thus, the use of the special value of all zeros in the value portion of the sub-TLV can be used to indicate "restore to default", which could mean :</t>
      <ul spacing="normal">
        <li>
          <t>if the default value is set for the sub-TLV:
          </t>
          <ul spacing="normal">
            <li>
              <t>Restore to the default values</t>
            </li>
          </ul>
        </li>
        <li>
          <t>if there is no default value for the sub-TLV:
          </t>
          <ul spacing="normal">
            <li>
              <t>Remove the associated attribute</t>
            </li>
          </ul>
        </li>
      </ul>
    </section>
    <section anchor="conventions">
      <name>Conventions</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.
<?line -6?>
      </t>
    </section>
    <section anchor="updated-procedures">
      <name>Updated Procedures</name>
      <t>Section 5.2 of <xref target="RFC8733"/> defines the AUTO-BANDWIDTH-ATTRIBUTES TLV and its associated sub-TLVs.</t>
      <t>This document updates <xref target="RFC8733"/> by adding this text at the end of paragraph 3 in section 5.2:</t>
      <artwork><![CDATA[
A special value of all zeros in the value portion of the sub-TLV
indicates the attribute identified by the sub-TLV is restored to
the default value. The value of all zeros is not considered an
invalid value and MUST be checked before individual fields.

For the attributes that have an associated default value, on
receiving such a sub-TLV, the PCEP speaker MUST consider it as
an instruction to restore to the default values. Note that, the
PCEP speaker could also set the default value in the sub-TLV
itself.

For the attributes that do not have an associated default value,
on receiving such a sub-TLV, the PCEP speaker MUST consider it
as a removal of the specific auto-bandwidth attribute.
]]></artwork>
    </section>
    <section anchor="extensions">
      <name>Extensions</name>
      <t>The section 5.1.1 of <xref target="RFC8733"/> defines the AUTO-BANDWIDTH-CAPABILITY TLV as an optional TLV for use in the OPEN Object for auto-bandwidth adjustment. This document adds a new flag -</t>
      <t>Z (TBD): The flag indicates that a PCEP speaker supports the use of the special value of all zeros in the value field as specified in this document.</t>
      <t>The presence of the Z flag can give a clear indication to the PCEP peer if they can use the updated procedures defined in this document.</t>
    </section>
    <section anchor="example">
      <name>Example</name>
      <t>Consider an LSP with the following information in the AUTO-BANDWIDTH-ATTRIBUTES TLV in the PCInitiate message:</t>
      <ul spacing="normal">
        <li>
          <t>Sample-Interval: 600 (in sec)</t>
        </li>
        <li>
          <t>Adjustment-Interval: 172800 (2 days in sec)</t>
        </li>
        <li>
          <t>Adjustment-Threshold: 0x49989680 (10 mbps in bps)</t>
        </li>
      </ul>
      <t>Now if the PCE would like to not use the Adjustment-Thresholds feature for the LSP and set the Adjustment-Interval to 1 day, it could send the AUTO-BANDWIDTH-ATTRIBUTES TLV in the PCUpd message with the following sub-TLVs:</t>
      <ul spacing="normal">
        <li>
          <t>Adjustment-Interval: 86400 (1 day in sec, the default value)</t>
        </li>
        <li>
          <t>Adjustment-Threshold: 0x0</t>
        </li>
      </ul>
      <t>On receiving the special value of all zeros in the value portion of the Adjustment-Threshold sub-TLV, the PCEP speaker would consider that as removal of the Adjustment-Threshold feature.</t>
      <t>Note that, the PCE could also set the Adjustment-Interval: 0x0 instead of the default value to trigger the restore to default. The Sample-Interval remains unchanged.</t>
    </section>
    <section anchor="backward-compatibility">
      <name>Backward Compatibility</name>
      <t>Note that to achieve the same objective, an <xref target="RFC8733"/> compliant implementation could send a PCEP message without AUTO-BANDWIDTH-ATTRIBUTES TLV first and then include the AUTO-BANDWIDTH-ATTRIBUTES TLV with the updated sub-TLV.</t>
      <t>An existing implementation of <xref target="RFC8733"/> that does not support this update (Z flag is not set) could consider a special value of all zeros in the sub-TLV to be a malformed sub-TLV thus ignoring it and keeping the previous value. A PCEP speaker SHOULD use other techniques in this case.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document does not add any substantial new security concerns beyond those already discussed in <xref target="RFC8733"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <section anchor="auto-bandwidth-capability-tlv-flag-field">
        <name>AUTO-BANDWIDTH-CAPABILITY TLV Flag Field</name>
        <t><xref target="RFC8733"/> defines the AUTO-BANDWIDTH-CAPABILITY TLV. IANA created a subregistry to manage the Flag field of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation Element Protocol (PCEP) Numbers" registry. This document requests IANA to allocate a new bit in the AUTO-BANDWIDTH-CAPABILITY TLV Flag Field registry, as follows.  IANA is requested to make allocations starting from the least significant bit (31).</t>
        <table>
          <thead>
            <tr>
              <th align="left">Bit</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">TBD</td>
              <td align="left">Z flag (special value of all zeros)</td>
              <td align="left">[This.I-D]</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <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="RFC5440">
        <front>
          <title>Path Computation Element (PCE) Communication Protocol (PCEP)</title>
          <author fullname="JP. Vasseur" initials="JP." role="editor" surname="Vasseur"/>
          <author fullname="JL. Le Roux" initials="JL." role="editor" surname="Le Roux"/>
          <date month="March" year="2009"/>
          <abstract>
            <t>This document specifies the Path Computation Element (PCE) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="5440"/>
        <seriesInfo name="DOI" value="10.17487/RFC5440"/>
      </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>
      <reference anchor="RFC8231">
        <front>
          <title>Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE</title>
          <author fullname="E. Crabbe" initials="E." surname="Crabbe"/>
          <author fullname="I. Minei" initials="I." surname="Minei"/>
          <author fullname="J. Medved" initials="J." surname="Medved"/>
          <author fullname="R. Varga" initials="R." surname="Varga"/>
          <date month="September" year="2017"/>
          <abstract>
            <t>The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t>
            <t>Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for PCE control of timing and sequence of path computations within and across PCEP sessions. This document describes a set of extensions to PCEP to enable stateful control of MPLS-TE and GMPLS Label Switched Paths (LSPs) via PCEP.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8231"/>
        <seriesInfo name="DOI" value="10.17487/RFC8231"/>
      </reference>
      <reference anchor="RFC8281">
        <front>
          <title>Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model</title>
          <author fullname="E. Crabbe" initials="E." surname="Crabbe"/>
          <author fullname="I. Minei" initials="I." surname="Minei"/>
          <author fullname="S. Sivabalan" initials="S." surname="Sivabalan"/>
          <author fullname="R. Varga" initials="R." surname="Varga"/>
          <date month="December" year="2017"/>
          <abstract>
            <t>The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t>
            <t>The extensions for stateful PCE provide active control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) via PCEP, for a model where the PCC delegates control over one or more locally configured LSPs to the PCE. This document describes the creation and deletion of PCE-initiated LSPs under the stateful PCE model.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8281"/>
        <seriesInfo name="DOI" value="10.17487/RFC8281"/>
      </reference>
      <reference anchor="RFC8733">
        <front>
          <title>Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCE</title>
          <author fullname="D. Dhody" initials="D." role="editor" surname="Dhody"/>
          <author fullname="R. Gandhi" initials="R." role="editor" surname="Gandhi"/>
          <author fullname="U. Palle" initials="U." surname="Palle"/>
          <author fullname="R. Singh" initials="R." surname="Singh"/>
          <author fullname="L. Fang" initials="L." surname="Fang"/>
          <date month="February" year="2020"/>
          <abstract>
            <t>The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests. Stateful PCE extensions allow stateful control of MPLS-TE Label Switched Paths (LSPs) using PCEP.</t>
            <t>The auto-bandwidth feature allows automatic and dynamic adjustment of the TE LSP bandwidth reservation based on the volume of traffic flowing through the LSP. This document describes PCEP extensions for auto-bandwidth adjustment when employing an active stateful PCE for both PCE-initiated and PCC-initiated LSPs.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8733"/>
        <seriesInfo name="DOI" value="10.17487/RFC8733"/>
      </reference>
    </references>
    <?line 183?>

<section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TBD</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA7VZ/W7jNhL/n0/BS3FoUkRGnGR3s8bhWifOdgPk6xLnirYo
DrRE22pkURWleH1N+yz3LPdk95shJUu2491ucQu0kSlyZjgfv/lQEARCFHGR
6J7cecgiVWhZGNkvCzNTRRzKU5VG8zgqprIf/VzaYqbTQma5CXVU5lqasbwv
cGhcJvL27HxHqNEo1089phCcfhc4miIyYapmYBLlalwEmU4nQRbqwPrD/EPh
zGgelHwkOOgK+tuTvw76w/PfRIgfE5MvetIWkXCbbE+evDk6EnGW92SRQ77D
g4O3B4dC5Vr15J0pizidiLnJHye5KbMeCSm/w08sy29pSTzqBd5HPcnsq+vu
u59z9zeo14WAyGn0L5WYFLIttBVZ3JM/Fibcl9bkRa7HFk+LmXvAxWcqy8Du
JyFAamrynhCBkDJOIf19R95CF/jp1HM/LWlvtWjySU++L9Vcx3Kow2lqEjOJ
wVNCCbnWRf32NIk6+/LadLqvXstTHf9CVO6iDnaGcQGlYe3nmImGJiJrdw+g
qlc7vFCmBSn27Bq/9EzFSU+SiayT5psp8+iEZraUfNCRg6mJFrXog2lePtVr
DcmbHC4aHCI60Il1Mf5mQitt+ncd+S0UPY1rBnfqUdvpcpVZnMU2NPJ+YQs9
g7ov0rDTulF/yS+f8MlvQjrCzIRITU5+/qR7Qt69Ozvsdt+6p1fHxwfu6aT7
5tg/HR51q6eT6gnu1xNxOl4S4n9BEEg1gpFUWAhx/qHQqY1Naim6iqmWtwoh
dWZmWYkIwAt5nmiOLazNyjQO3eptbuBZJpG7cNzbPQk28ur28j4YnstLNdKJ
vJ/HRTjVkaO4e3mPXdvD10ocmbbiViJeZKTHcQpCcUoX48DqyIvCr1sWu/8w
vAlO+9eD7y4Gw/dBfzi8uzh9GJ7fy+HlPyWYSSWtLggXbDkKsGhZZq3CKS0S
DVUUeTwqEb0dOcTveiMJEadhUkYkBW+mFbyQ4VSlE2zFa81EEmULWasdmrKk
PIjOyoWu5Exbqya6I09LvChwInwkUjNNxGI7I1PoD1kSI0CShcz1zDxBunQp
oIwjUI3HMeQZLZi0F7YjxHAKyRDeJZvN41GtOdrPiqM4pIMjPVVPsSnzj7Pt
dJz/zOIoSrQQX8Cti9xEZUg3FeLXX72D/vYbeNgQp7x5Ps+rOtJprGnosHVg
pIu51hBxncNZEhMDUDrb8w7wohTEbm8fgVsTxAKiVqdqlJCiwsYheMtVmRSA
di9s099p8y4FgguJIbLKGO5+nk5wA53T643hQWFDEQIXoMjEToswsR2vVIpw
KNVmOiSrWxiqGbisJTIfyQtfqCIoNGSfhEWGTNJxgXu78KktNDdyBvC1tNFk
OueLWhlAOGuBHUuKHJNQZj8sVtc78l2ZU2jsSy/zSXfNERCDZbYvAXwpLqAo
aohcoVUemTkrF6SCizQuYpCOWF5WJZ9uikESJ7WC4NprzNoZUo61Kqg2KKaq
kCpJzNzyFodIJEa0AKLT87Kk8NjgNCeXxHJtdf7kvVBZSGpcjD+ZBJHH57zx
x+Dkog15fTLlXSDWaRuBbdgwK9155QINseZTOKmeZYlZEGmK0nWLMI2RwUnS
aVzrtGkeujZCpPHWecgfwlfWKOLhKY78/i/heuN4UubskI+pGdkvK116O+wz
bwBgqCiQlwirLN3HZKRblTADj58QrS/N6GcdFg6i+R2iIaXagTME7NqC2aXz
kP3m0zjRm3yjodrKTZguiR8hXogZ0qYmh61cguWKCIoqlCO+iFHUAzlymZ1q
js4otqyFxt09RUeCr23ljEEl2abrOiM1UmLD/T3VTzj/f8poFxRX1jgntM4t
/MYQMUKaQ56LgSnwWS/MPtkbmON4mRAWzwyS0ALwG5Nc/AIXVtCPfFJJqQmo
raEg4/cOsUweVD6HO7l9uFCJ0ARI3NfXWWHPPkM/rP6lpIs1b0QEQNTCrXPn
mKnxCtpf6gxrrdxdZU6ZqRzIUiYqb6Tuhq8287bcnLab4EauxHbHIVQtatnu
4ILXpvDIVvn7spxx60jzLp1ba0IX6i2t8o0WVKImEcwPbFl4YTdYoC29BBv8
Jm2pNDUFhTMp/kVZIiNpmxOpTXqtgsEtM2NdKIEoWYvSIPzEO8OYg/7fOje8
p4pJuQOMhltorzhisbNPEADluVvONPQxMeQOI1RhVQ3ckseSt7FJVbJWKQK+
rE7GLDOC2yQV1HPA16HdUJV1+W6di4+CZjgL8SyHi0xL/vcsL4H57ukajYd/
HHgy9AP7e1SgyeoE/tFC0GuuuH+8+uz/4GDXvT/m/98rmF8jDReU5BK58d+z
PDo4ABogQiLLNA6bNJaF/RY6z/Lk9fEKlaMmlQGqguBjpDYzI1rHL0g0nMI5
pgY+sC5Rig6aD7/yEr54OLjVeYgVggp/+NVf9+UBn3697Rob+b8gIRF70xTl
RWJNeT4uMdE9aQp5hSJgVs6CZXO20eruem9bJ9WHTzlZa7Z70LjOzZPOqUba
YpT24e7Ww2tGaR8+bBx+SKOPs24ePtp+eJ11fZgQorSMsYxiHkm2QJmHWPcm
M3nVfDRx15dOjLWfAX09Ib7y6X8V3y23y3Xh7fj1BN3pK3m3pL6OZDXJOju2
Sb9Ik7Mmw+syQ9VIK6jdPDPpEzW+SMkOcR+RsGhIZuXO1cP9EHfkv/L6hp/v
zv/xcHF3PqDn+/f9y8v6Qfgd9+9vHi4Hy6flybObq6vz64E7jFXZWhI7V/3v
d1wJu3NzO7y4ue5f7jibNZOXclri8hawlOWab2VFVfhzIXB6dvvf/3SPAf5/
8cMepHv3g6Y8+EH1vuNmUuRl95PytVAZCs68Kn1DlcUFajCuquCTaKnIEB3x
t68TqhyC11//XbAu3QA0op7bFRFQ6b3mTl6+6hySp7U7qz8ybEFabFqxyn0v
TieanEYLVOORa5iwt0BPBDdgxpruP6a6Sk1ylU2RKmKqR2up4dC///676P/J
uBLtuv4T5i7k6T7mKBLFWli4fmWTOJZLoWaZmYI/dsZVGUsaZbeGG4VTHT4S
ez02XMRHMbquEleFVElEKn732QWgSUWuQw2KXCBzkVmX6WsdDotUyU2NHNwa
5OPUFrkbCblqeAtWdGRdtzID0WLgkMp1FLr4aBUq6mLsJQ20ys4tihAQ/U8o
QlAHu1oz+tlNuNZ51tM1dl1E5nIo60Bu6d/dTvcPxOVZ/7Z/enF5MfzexeV6
W01QTMnI6/Hm9vxa3nB7vX38sNqtIF7pxqmey3GiJjIQ4ge5Ozwd7PXY7Xmx
GVM0gGnr0JYZxaL93ATJ3s+g52dk0RoY+yo9o9FNo4//wYlHqXQScz8SJg5R
o2rMWM3GSeBMk43HvlnCIRKWhfaAWndlrTZ9VRIyMxfZQpxVngNiPKSgKXjR
6iea7be/9nYQrtvzapJWtbSc8lfK+558jRJ810HpHt5vqKZ7svvm8IS2HcpI
LazcuLuuhHry4MPx27cnb1+f4AjKvdko4zP4s0fd6ryqO2hONedAT+JHhgkK
0Uqpm2jbekTTHO0QSFYosakbAOEuSb7PIyfX5Grfin2iLpEy68nABiNVWY5V
vFGFrtfZZTm8AvfXYW2bTg+EuGli05+oITf2Gi+DnLNRjXIuhu0qym0kWg29
GlOKmsEmkN+oO9ydU4tWUcWsnQwoSPN4MvETo/UK2KXg1dY2p69wqZVl6gY7
EQfnqQof5yqP+HMB4m4UJ3GxaI5ZQFeF01j7mtVSR+5GkwARKtVaME0fEJJY
0eCM2NPdXDQ3PFG1Z0/kYaYsPuKc4zi3RTVTSKuRwyd4de3AFW4tvyD1U6k/
0AcIQp62uCvZx2dV7WoYj+EO6xxZuevh1Zc5MPGev3PtSlsHOiuDJldLKzlT
CSHiUmzsKrF7khr+yBI7nTxqnVVhAtyn71y2qsf6bf/29T+nHjd2pO/a8S80
m6nwm4aY7B4olMscDiEr7FZ1U9LMi7VmkCAhz4LnjAW8gC5L2dJWdKCMUOdw
w5FeGDamoVFXksPdFzRBDktr1we+/A2uf91fk+OLLz5SDbwjo7yjpLn6BeUT
64mOYxxCQm5p6G65nsBt8gWZaaZS8mKiw7xcgq5gYqts5Jre7jsvfrNb/QJ9
Xc5GOrc7shJitUjJacBrUWGw3BS+CY2bC+0rl1FcvJBbX1RdzYvbLZcJ+Osa
ceCOgFm65nwGN6t48hceeELOMTbOzcyNvzXN2i28mCpFQgsSaveou0ezwNO4
eB5w28g13POdHqNfgN88i+cgCOr/xDMqr2cfd7svx9be84+koc5FMPjp2X3Z
pSko+VQ/fEzNPNHRhD/Mw69PB9Q2/g+RUMgLlyMAAA==

-->

</rfc>
