<?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.6.35 (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-00" category="std" consensus="true" updates="8733" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.17.4 -->
  <front>
    <title abbrev="Auto-Bandwidth-Update">Update to Automatic Bandwidth Adjustment procedure of Stateful PCE</title>
    <seriesInfo name="Internet-Draft" value="draft-peng-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 Technologies</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.</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>Restore to the default values</li>
          </ul>
        </li>
        <li>
          <t>if there is no default value for the sub-TLV:
          </t>
          <ul spacing="normal">
            <li>Remove the associated attribute</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>Sample-Interval: 600 (in sec)</li>
        <li>Adjustment-Interval: 172800 (2 days in sec)</li>
        <li>Adjustment-Threshold: 0x49989680 (10 mbps in bps)</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>Adjustment-Interval: 86400 (1 day in sec, the default value)</li>
        <li>Adjustment-Threshold: 0x0</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>TBD</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>
      <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:
H4sIAAAAAAAAA7VZe2/jNhL/n5+Cl+LQpIiMOMnuZo3DtU6c7QbI62LnirYo
DrRE22wkUSWpeH1N+1nus9wnu5khJUt+7XaLW6CNTJEzw3n85qEoihhzyqWy
x/cei0Q4yZ3m/dLpTDgV83ORJ3OVuBnvJz+X1mUyd7wwOpZJaSTXEz50cGhS
pvz+4nKPifHYyOceUYjqw5EnzRId5yIDXokRExcVMp9GRSwjG2jQDwFHx/Oo
pCPR0RHDvz3+66A/uvyNxfBjqs2ix61LmN9ke/zszckJU4XpcWdAzOOjo7dH
x0wYKXr8QZdO5VM21+ZpanRZ9FBW/h38hGX+LS6xJ7mA90mPE/tK8EP/c+7/
RvU6YyBynvxLpDoH2RbSskL1+I9Ox4fcauOMnFh4WmT+AS6eiaIAdj8xBqRm
2vQYixjnKgfphx1+D7qAn149w1mJe6tFbaY9/r4Uc6n4SMazXKd6qoAnByUY
KV399jxNOof8Vne6r17zc6l+QSoPSQd2xsqB0mDtZ0VEY52g0btHoKpXe7RQ
5g4Ve3ELv2QmVNrjaCLrpflmRjw6sc6Wkg86fDDTyaIWfTAz5XO9tkPymt1V
g12CpztKusk3U1xpM3vo8G9B6zNVc3sQT9LOlqvE70LZWPPhwjqZge6v8rjT
ul5/yc9M6eQ3MR4hZozl2qDvP8se4w/vLo673bf+6dXp6ZF/Ouu+OQ1Pxyfd
6umsegJf7DGVT5aE6F8URVyMwWIidoxdfnAyt0rnFiPOzSS/FxBmFzorSggH
eMEvU0nxBmtZmavYr94bDW6mU74PXnx/wIENv7m/HkajS34txjLlw7ly8Uwm
nuL+9RB27Q5py+HIrBXLHIKHJ3KiciCkcrwYRVmHX7mwbkns/uPoLjrv3w6+
uxqM3kf90ejh6vxxdDnko+t/cmDGBbfSIVbYchzBoiWZpYhnuIg0hHNGjUsI
5Q4fwe96Iwqh8jgtE5SCNuMKvODxTORT2AqvJRFJhXW8VjtoyqLyQHRSLuiK
Z9JaMZUdfl7CCwcn4icklUkkpmyGppAfilRBtKQLbmSmn0G6fCkgVwlQVRMF
8owXRDoI22FsNAPJINZLMlsAp1pzuJ8Uh0GJB8dyJp6VLk3HO0emkiSVjH0B
PuuMTsoYr8HYr78G7/vtNyBgY5Ak6P7zXKbDvTqaVoxbB8bSzaWEa69zuEgV
MgBKFwfBululQHYHhxCVNUFYgJCUuRinqIW4cQhc4aZMHYB4ELbpzLh5H73c
+/sI8scEfPkyn8INpMHXG30fYwLdH+yLYQc7LcSA7QSlYviCUm0hYzSpBeM3
o5K0hC6B8oKhq/CINdonJZFBJu65gO/62KgtNNc8A5i1uFEX0tBFLY9AOGsB
GJYUKeBAmf3Yra53+LvSoN8f8iDzWXfNESDAyuKQA6rlcAGBIYHknBQm0XNS
LpCKrnLlFJBOSF5SJZ1uioESp7WCwG/XmLVzIZ9I4bAYcDPhuEhTPbe0xcMN
ipEsAK7xeVlDhMD3muNLYkZaaZ6DFwoLkmofwM86hbCic8H4E+DkQwky+HRG
u4BYp20EsmHDrHjnlQs0xJrPwEllVqR6gaQx8tctQjTGGk6iTlWt06Z58NoQ
Io233kP+EHiSRiEenlUS9n8JrjdR09KQQz7lemy/rHQZ7HBIvAHdYoGBvIRP
YfE+ukDdipQYBHAE0fpcj3+WsfP4S+8gGnKsEgj+wa4tDF06D9pvPlOp3OQb
DdVWbkJ0UfwE4gWZQU6U6LCVS5BcCUJRhXLIF2IUkr2BRGVnkqIzUZa00Lh7
oOhJ0LUtzwhU0l26rtNNI9813D9Q/YTz/6d0dYVxZbV3QuvdImyMIUZQc5DE
FGAK+GwQ5hDtDZjjeekYLF5oSGwLgF+FctELuLAA/fBnkZYSgdpqDDJ67xFL
m6jyObiT3wcXKiE0ASSG9XVW2JPP4A8rfynxYs0bIQEgasGtjXfMXAcFHS51
BmutxFxlY14IA8hSpsI08nLDV5tJmW/OyU1wQ1ciu8MhKEnEsr+BC95qF5Ct
8vdlreLXIYf7EsFaHftQb2mVbrTA+jNNwPyALYsg7AYLtKXnwAZ+o7ZEnmuH
4YyK3ypLojlu8yK1Sa+VJ3DLQlsfSkAUrYVpEPwkOMOEgv7f0mjaU8Uk3wOM
BreQQXHIYu8QIQCU52+ZSdDHVKM7jKHEqgrcljwWvY1MKtK1MhDgy8p0QjJD
cOu0gnoK+Dq0G6qyPt+tcwlR0Axnxl74aFFITv9e+DVgvn+6ha4iPA4CGfwB
+3tYoPHqBPzDhajXXPH/aPUl/IGDXf/+lP4/FGB+CWnYYZJL+cZ/L/zk6AjQ
ACIksUTjuEljWbXvoPPCz16frlA5aVIZQFUQfYzUZmZI63SLRKMZOMdMgw+s
S5RDr0yHXwUJtx6O7qWJYQWhIhx+9ddDfkSnX++6xkb+WyREYm+aomwl1pTn
4xIj3bOmkDdQBGRltpyHbLa6v97b1knx4VNO1prtHjWuc/csDdZIO4zSPtzd
eXjNKO3Dx43Dj3nycdbNwye7D6+zrg8jQpSWMJZQLCDJDigLEOvfFNpUzUcT
d0PpRFj7GdAHDf9XIf2v4rulXrguvD2/HsM7fcUfltTXkawmWWfHNumtNClr
ErwuM1SNtAzbzQudP2NXCynZI+4TJCwch1m+d/M4HMEd6S+/vaPnh8t/PF49
XA7wefi+f31dP7CwY/j+7vF6sHxanry4u7m5vB34w7DKW0ts76b//Z4vYffu
7kdXd7f96z1vs2byEl5LVN4CLBVG0q0sqwp/KgTOL+7/+5/uKYD/X8IkB9K9
/4EjHPiB9b7npnPIy/4n5msmCig4TVX6xqJQDmowqqrAJ6GlQkN02N++TrFy
iF5//XdGuvSjzgR7bl9EgEqHkjp5/qpzjJ7W7qz+yCQF0mLTilXu2zp6aHIa
L6AaT3zDBHsd9ETgBsRY4v0nWFeJqRHFDFKFwnq0lhoc+vfff2f9PxlXrF3X
f8JQBT09xBxGIlsLC9+vbBLHUinULDNz4A87VVXGokbJrcGN4pmMn5C9nGgq
4hMFXVcJVwWp0gRV/O6zC0CdMyNjCRSpQKYisy7T1zocEqmSGxs5cGsgr3Lr
jB8J+Wp4B1Z0eF23EgPWYuCRyncU0n20CmV1MbZNA62yc4ciGIj+JxTBsINd
rRnD7CZe6zwrGTvkuhCZy4mrB7mlf3c73T8Qlxf9+/751fXV6Hsfl+ttNUIx
JqOgx7v7y1t+R+317vHDarcC8Yo3zuWcT1Ix5RFjP/D90fngoEduT4vNmMIB
TFuHtiwwFu3nJkjyfgK9MCNL1sA4VOkFjm4affwPXjxMpVNF/UicekRNqjFj
NfhGgQuJNp6EZgkOobAkdADUuitrtemrkqCZqchm7KLyHCBGQwoccbtWP9Fs
v8O1d4Nw3Z5Xk7SqpaWUv1Le9/hrKMH3PZQewPsN1XSPd98cn+G2Y56IheUb
d9eVUI8ffTh9+/bs7eszOALlXjYu6Az8OcBudV7VHTinmlOgp+qJYAJDtFLq
Jtq2HtE0RzsIkhVKbOoGgHAXJT+kkZNvcmVoxT5Rl5Ay68nABiNVWY5UvFGF
vtfZJzmCAg/XYW2XTo8Yu2ti05+oITf2GttBztuoRjkfw3YV5TYSrYZejSlF
zWATyG/UHdydUosUScWsnQwwSI2aTsPEaL0C9il4tbU1+Iktt7zM/WAnoeA8
F/HTXJiEPhdA3I1VqtyiOWYBuiKeKRlqVosduR9NAohgqdaCafyAkCqBgzNk
j3fz0dzwRNGePaGH6dJ9xDknylhXzRTyauTwCV5dO3CFW8vPQ/2cyw/4AQKR
py3uSvYJWVX6GiZguMc6T5bvB3gNZQ6Y+CDcuXalnQOdlUGTr6UFz0SKiLgU
G3aVsHuaa/rIorxOnqQsqjAB3MePWLaqx/pt/w71P6UeP3bE78DqF5zNVPiN
Q0xyDyiUSwMOwSvsFlVTcj6g72L92/7auy+++EiGfoeKeoeJbPWrxifm+I5n
HBvpmydUjpFTMKVZoOoykaNnIR3i5ZNmFbo7ZUN3CbbY2/odbfWT722ZjaWx
e7wSYrVwMDh0tZD1SW4MqRRHwE6GamKs3JZ8t1V1NS9qgTw60xcv5EBVOrH0
DXMGpq940lcX63BmCx4zMTrzI2mJ828LnoXVG0YwCrV/0j3A+dy5ci8DauWo
rnp5kBOo4aG6eGEvURTV/7EX8IyXEAv72/394OVH1FDnKhr89OK/tuJkEn2q
Hz/lep7KZEpfwoOvMfY/ko9GBBwjAAA=

-->

</rfc>
