<?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.21 (Ruby 3.0.2) -->
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-pce-stateful-pce-autobw-update-00" category="std" consensus="true" updates="8733" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.25.0 -->
  <front>
    <title abbrev="Auto-BW-Update">Update to Automatic Bandwidth Adjustment procedure of Stateful PCE</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-pce-stateful-pce-autobw-update-00"/>
    <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. However, 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>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/W7bRhL/f59iz8WhdmEKlu0kjnC4VracxoBj+2zlirYo
DityJW1NcVkuaUVXt89yz3JPdr+ZXVLUh500xQVoTS13Z2bn4zcfjKJIiNKU
qe7Jnfd5okotSyv7VWlnqjSxPFVZMjdJOZX95OfKlTOdlTIvbKyTqtDSjuVd
iUPjKpU3Z+c7Qo1GhX7oMYXo9LvI0xSJjTM1A5OkUOMyMrocR3msIxcO8w+F
M6N5VPGR6OBA0N+e/HXQH57/JmL8mNhi0ZOuTITf5Hry5NXRkTB50ZNlAfkO
Dw5eHxwKVWjVk7e2Kk02EXNb3E8KW+U9ElJ+h59Ylt/SkrjXC7xPepLZ19fd
9z/n/m/UrAsBkbPkXyq1GWRbaCdy05M/ljbel84WZaHHDk+LmX/AxWcqz8Hu
JyFAamqLnhCRkNJkkP6uI280JJTSq+duWtHeetEWk558W6m5NnKo42lmUzsx
4CmhhELrsnl7miadfXllO90XL+WpNr8Qldukg52xKaE0rP1smGhsE7J29wCq
erHDC1VWkmLPrvBLz5RJezKHBM5L882UeXRiO1tKPujIwdQmi0b0wbSoHpq1
luRtDhctDgkd6JArfDOhlVX6tx35LRQ9NQ2DW3Wv3XS5yizOjIutvFu4Us+g
7oss7qzcqL/kV0z45DcxHWFmQmS2ID9/0D0hb9+cHXa7r/3Ti+PjA/900n11
HJ4Oj7r100n9BPfrCZONl4T4XxRFUo1gJBWXQpx/KHXmjM0cRVc51fJGIaTO
7CyvEAF4Ic9TzbGFtVmVmdiv3hQWnmVTuQvHvdmTYCPf3VzeRcNzealGOpV3
c1PGU514iruXd9j1fPg6iSPTlbiViBeZ6LHJQMhkdDEOrI68KMO6Y7H774fX
0Wn/avDdxWD4NuoPh7cXp++H53dyePlPCWZSSadLwgVXjSIsOpZZq3hKi0RD
lWVhRhWityOH+N1sJCFMFqdVQlLwZlrBCxlPVTbBVrzWTCRVrpSN2qEpR8qD
6Kxc6ErOtHNqojvyrZ3rB13sS1PiWHxP9GaaKBo3I3voD3lqECXpQhZ6Zh8g
YraUUpoEpM3YQKjRgukHiTtCDKcQDzFese0CKDXqo/2sPQpGOjjSU/VgbFV8
nG3H+9DMJEmqhfgCrl0WNqliuq0Qv/4anPS338DCxTgUTPR5ntWRXmttY8cr
B0a6nGsNCTc5nKWGGIDS2V5wgielIHZ7+wjehiAWELk6U6OU9BS3DsFj3lVp
CXgPwrZ9njbvUjD4sBgis4zh8ufZBDfQBb3eGiIUOhQl8ACKTux0CBXXCUql
KIdSXa5jMrqDndrBy1oi65G8cIU6imJL9klZZMgkPRe4uA+hxkJzK2cAYEcb
ba4LvqiTEYRzDvixpMhxCWX243J9vSPfVAWFx74MMp90NxwBcVjl+xLgl+EC
iiKHyJVaFYmds3JBKrrITGlAOmF5WZV8ui0GSZw2CoJnbzBbzZJyrFVJ9UE5
VaVUaWrnjrd4VCIxkgVQnZ6XZUXAB685uSRWaKeLh+CFykFS6+P8waYIPD4X
jD8GJx9syO2TKe8Csc6qEdiGLbPSndcu0BJrPoWT6lme2gWRpiDdtAjTGFmc
JJ2aRqdt89C1ESKtt95D/hDGskYRDw8mCfu/hOuNzaQq2CHvMztyX9a6DHbY
Z97Av1hRIC9RVjm6j81JtyplBgFDIVpf2tHPOi49TPM7RENG9QNnCdh1BWqX
zkP2m09Nqrf5Rku1tZswXRI/QbwQM6ROTQ5buwTLlRAU1ShHfBGjqAkK5DM3
1RydiXGshdbdA0VPgq/t5IxBJX1O101WaqXFlvsHqp9w/v+U1S4orpz1Tui8
W4SNMWKENIc0Z4Ap8NkgzD7ZG5jjedkYFs8tctAC8GtILn6BCyvoRz6otNIE
1M5SkPF7j1i2iGqfw538PlyoQmgCJO6a66yxZ5+hH07/UtHF2jciAiDq4NaF
d8zMBgXtL3WGtZXUXSdOmasCyFKlqmhl7pavttO23J612+BGrsR2xyFULmrZ
8uCCV7YMyFb7+7Kk8evI8j6bO2djH+orWuUbLahMTROYH9iyCMJuscCq9BJs
8Ju0pbLMlhTOpPgnZUmspG1epFXSGwUMbplb50MJRMlalAbhJ8EZxhz0/9aF
5T11TModYDTcQgfFEYudfYIAKM/fcqahj4kldxihCKvr4BV5HHkbm1SlG9Ui
4MvpdMwyI7htWkM9B3wT2i1VOZ/vNrmEKGiHsxCPcrjIteR/j/ISmO+frtB8
hMdBIEM/sL9HBZqsT+AfLUS99or/x6uP4Q8Odv37Y/7/nYL5NdJwSUkulVv/
PcqjgwOgASIkcUzjsE1jWdw/Q+dRnrw8XqNy1KYyQFUQfYzUdmZE6/gJiYZT
OMfUwgc2JcrQRfPhF0HCJw9HN7qIsUJQEQ6/+Ou+PODTL5+7xlb+T0hIxF61
RXmSWFuej0tMdE/aQr5DETCrZtGyQdtqdX+91ysn1YdPOdlotnvQus41GiGq
kZ4xyurh7rOHN4yyeviwdfh9lnycdfvw0fOHN1k3hwkhKscYyygWkOQZKAsQ
69/ktqibjzbuhtKJsfYzoK8nxFch/a/ju+OWuSm8Pb+eoDt9JW+X1DeRrCHZ
ZMdV0k/S5KzJ8LrMUA3SCmo3z2z2QH0vUrJH3HskLBqUObnz7v3dEHfkv/Lq
mp9vz//x/uL2fEDPd2/7l5fNgwg77t5ev78cLJ+WJ8+u3707vxr4w1iVK0ti
513/+x1fwu5c3wwvrq/6lzveZu3kpbyWuLwFLOWF5ls5URf+XAicnt389z/d
Y4D/X8LAB+ne/6BJD35Qve+52Qx52f+kfC1UjoKzqEvfWOWmRA3GVRV8Ei0V
GaIj/vZ1SpVD9PLrvwvWpR+CJtRz+yICKr3T3MnLF51D8rTVzuqPDFyQFttW
rHPfk8OJNqfRAtV44hsm7C3RE8ENmLGm+4+prlKTQuVTpApD9WgjNRz6999/
F/0/GVdita7/hLELeXqIOYpEsREWvl/ZJo7jUqhdZmbgj52mLmNJo+zWcKN4
quN7Yq/Hlov4xKDrqnBVSJUmpOI3n10A2kwUOtagyAUyF5lNmb7R4bBItdzU
yMGtQd5kriz8SMhXw89gRUc2dSszECsMPFL5jkKXH61CRVOMPaWBlbLzGUUI
iP4nFCGog12vGcPsJt7oPJfDNXJdROZyMNuOyG6n+wdi8qx/0z+9uLwYfu9j
crOlJhimRBR0eH1zfiWvubV+fvSw3qkgVum2mZ7LcaomMhLiB7k7PB3s9djl
ebEdTzR8WdWfq3KKQ/e5yZE9nwEvzMeSDSAOFXpOY5tWD/+DF4/S6MRwLxKn
Hk2TesRYz8ZJ4FyTfcehUcIhEpaFDmDadGQrLfq6JGRiLrCFOKu9BsR4QEFT
8HKll2i33uHazwNw05rXU7S6neV0v1ba9+RLlN+7Hkb38H5LJd2T3VeHJ7Tt
UCZq4eTW3U0V1JMHH45fvz55/fIER1DqzUY5n8GfPepU53XNQTOqOQd5au4Z
Iig8a6Vuo+2a8Ux7rEMAWSPEtk4AhLskOY/bQ4OrQxv2ibpEumymAluMVGc4
VvFWFfo+Z5flCArc34S053R6IMR1G5f+RP24tc94GuC8jRqE8zHs1hFuK9F6
4NWaUDQMtgH8Vt3h7pxWtEpqZquJgIK0MJNJmBZtVr8+/a63tQV9hcucrDI/
1Ek4OE9VfD9XRcKfChB3I5OactEesYCuiqdGh3rVUTfux5IAESrTVmCaPh6k
RtHQjNjT3Xw0tzxRrc6dyMNsVX7EOcemcGU9T8jqccMneHXjwDVuLT8e9TOp
P9DHB0KeVXHXsk/IqNrXLwHDPdZ5snI3wGsocWDivXDnxpWeHeasDZl8Ha3k
TKWEiEuxsavC7klm+QOL8Tq51zqvwwS4T5+4XF2L9Vf9O9T+nHr8yJG+a5tf
aC5T4zcNMNk9kJKrAg4ha+xWTUPSzouNZpAgIc+CZ4wlvIAuS9nS1XSgjFgX
cMORXlg2pqUxV1rA3Rc0PY4r5zaHvfz9rX/V35Djiy8+Ug28IaO8oaS5/vXk
E+uJjmccQ0JuZ+huhZ7AbYoFmWmmMvJiosO8fIKuYeJZ2cg1g913nvxet/4F
+qqajXThdmQtxHqRUtBw16HCYLkpfFMaNZc6VC4jUz6RW59UXcOLWy2fCfjL
GnHgboBZ+sZ8BjerefLXHXhCwTE2LuzMj741zdkdvJiqREILEmr3qLtHc8BT
Uz4OuGXkGu7xVo/RK8BvHsVjFEXNf+IRlddjiLvdp2Nr7/FH0lDnIhr89Oi/
6tIElHyqH99ndp7qZMIf5uHXpwNqGf8Hr88wkpcjAAA=

-->

</rfc>
