<?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.17 (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-02" category="std" consensus="true" updates="8733" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.21.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-02"/>
    <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/W7jNhL/X0/BS3FoUkRGnGR3s8bhWifOdgPk6xLnirYo
DrRE22xkURWleH1N+yz3LPdk95shJUu2491ucQu0kSlyZjgfv/lQGIZBUOgi
UT2x85DFslCiMKJfFmYmCx2JU5nGcx0XU9GPfy5tMVNpIbLcRCoucyXMWNwX
ODQuE3F7dr4TyNEoV089phCefhc6mkFsolTOwCTO5bgIM5VOwixSofWH+YfE
mdE8LPlIeHAY0N+e+HXQH57/FkT4MTH5oidsEQduk+2JkzdHR4HO8p4ocsh3
eHDwFidlrmRP3Jmy0OkkmJv8cZKbMuuRkOI7/MSy+JaWgke1wPu4J5h9dd19
93Pu/ob1ehBA5DT+l0xMCtkWygaZ7okfCxPtC2vyIldji6fFzD3g4jOZZWD3
UxCA1NTkvSAIAyF0CunvO+IWusBPp577aUl7q0WTT3rifSnnSouhiqapScxE
g6eAEnKlivrtaRJ39sW16XRfvRanSv9CVO7iDnZGuoDSsPazZqKRicna3QOo
6tUOL5RpQYo9u8YvNZM66QkykXXSfDNlHp3IzJaSDzpiMDXxohZ9MM3Lp3qt
IXmTw0WDQ0wHOloV428mtNKmf9cR30LRU10zuJOPyk6Xq8ziTNvIiPuFLdQM
6r5Io07rRv0lv3zCJ7+J6AgzC4LU5OTnT6oXiLt3Z4fd7lv39Or4+MA9nXTf
HPunw6Nu9XRSPcH9eoFOx0tC/C8MQyFHMJKMiiA4/1Co1GqTWoquYqrErURI
nZlZViIC8EKcJ4pjC2uzMtWRW73NDTzLJGIXjnu7J8BGXN1e3ofDc3EpRyoR
93NdRFMVO4q7l/fYtT18rcCRaStuBeJFxGqsUxDSKV2MA6sjLgq/blns/sPw
JjztXw++uxgM34f94fDu4vRheH4vhpf/FGAmpLCqIFyw5SjEomWZlYymtEg0
ZFHkelQiejtiiN/1RhJCp1FSxiQFb6YVvBDRVKYTbMVrxUQSaQtRqx2asqQ8
iM7Kha7ETFkrJ6oj3pu5elL5vtAFjkWPRG+miKK2M7KH+pAlGlGSLESuZuYJ
IqZLKYWOQVqPNYQaLZi+l7gTBMMpxEOMl2w7D0q1+mg/a4+CkQ6O1FQ+aVPm
H2fbcT4003GcqCD4Aq5d5CYuI7ptEPz6q3fS334DCxvhkDfR53lWRzitNY0d
tQ6MVDFXChKuczhLNDEApbM97wQvSkHs9vYRvDVBLCByVSpHCekpahyCx1yV
SQF498I2fZ4271IwuLAYIrOM4fLn6QQ3UDm93hgiFDoUJfAAik7stAgV2/FK
pSiHUm2mIjK6hZ2awctaIuuRvHCFKooiQ/ZJWGTIJBwXuLgLodpCcyNmAGBL
G02mcr6oFSGEsxb4saTIcQll9qNidb0j3pU5hce+8DKfdNccAXFYZvsC4Jfi
ApIih8gVSuaxmbNyQSq8SHWhQTpmeVmVfLopBkmc1AqCZ68xa2dJMVayoPqg
mMpCyCQxc8tbHCqRGPECqE7Py7LC44PTnFgSy5VV+ZP3QmkhqXFx/mQSBB6f
88Yfg5MLNuT2yZR3gVinbQS2YcOsdOeVCzTEmk/hpGqWJWZBpClI1y3CNEYG
J0mnutZp0zx0bYRI463zkD+EsaxRxMOTjv3+L+F6Yz0pc3bIx9SM7JeVLr0d
9pk38C+SFMhLlJWW7mMy0q1MmIHHUIjWF2b0s4oKB9P8DtGQUv3AWQJ2bUHt
0nnIfvOpTtQm32iotnITpkvix4gXYobUqchhK5dguWKCogrliC9iFDVBjnxm
p4qjM9aWtdC4u6foSPC1rZgxqCTbdF1npUZabLi/p/oJ5/9PWe2C4soa54TW
uYXfGCFGSHNIcxqYAp/1wuyTvYE5jpeJYPHMIActAL+a5OIXuLCEfsSTTEpF
QG0NBRm/d4hl8rDyOdzJ7cOFSoQmQOK+vs4Ke/YZ+mHVLyVdrHkjIgCiFm6d
O8dMjVfQ/lJnWGul7ipxikzmQJYykXkjczd8tZm2xeas3QQ3ciW2Ow6hcpHL
lgcXvDaFR7bK35cljVtHlnfZ3FoTuVBvaZVvtKAyNYlhfmDLwgu7wQJt6QXY
4DdpS6apKSicSfEvyhIbQducSG3SawUMbpkZ60IJRMlalAbhJ94Zxhz0/1a5
4T1VTIodYDTcQnnFEYudfYIAKM/dcqagj4khdxihCKvq4JY8lryNTSqTtWoR
8GVVMmaZEdwmqaCeA74O7YaqrMt361x8FDTDOQiexXCRKcH/nsUlMN89XaP5
8I8DT4Z+YH+PCjRRncA/Wgh7zRX3j1ef/R8c7Lr3x/z/ewnzK6ThgpJcIjb+
exZHBwdAA0RIbJnGYZPGsrjfQudZnLw+XqFy1KQyQFUQfozUZmZE6/gFiYZT
OMfUwAfWJUrRRfPhV17CFw+HtyqPsEJQ4Q+/+uu+OODTr7ddYyP/FyQkYm+a
orxIrCnPxyUmuidNIa9QBMzKWbhs0DZa3V3vbeuk/PApJ2vNdg8a17lBI0Q1
0hajtA93tx5eM0r78GHj8EMaf5x18/DR9sPrrOvDhBClZYxlFPNIsgXKPMS6
N5nJq+ajibu+dGKs/Qzo6wXBVz79r+K75Za5Lrwdv15Ad/pK3C2pryNZTbLO
jm3SL9LkrMnwusxQNdIG1G6emfSJ+l6kZIe4j0hYNCizYufq4X6IO/JfcX3D
z3fn/3i4uDsf0PP9+/7lZf0Q+B33728eLgfLp+XJs5urq/PrgTuMVdFaCnau
+t/vuBJ25+Z2eHFz3b/ccTZrJi/ptMTlLWApyxXfygZV4c+FwOnZ7X//0z0G
+P/FD3yQ7t0PmvTgB9X7jptJkZfdT8rXgcxQcOZV6RvJTBeowbiqgk+ipSJD
dIK/fZ1Q5RC+/vrvAevSDUFj6rldEQGV3ivu5MWrziF5Wruz+iMDF6TFphWr
3PficKLJabRANR67hgl7C/REcANmrOj+Y6qr5CSX2RSpQlM9WksNh/7999+D
/p+Mq6Bd13/C2IU83cccRWKwFhauX9kkjuVSqFlmpuCPnboqY0mj7NZwo2iq
okdir8aGi/hYo+sqcVVIlcSk4nefXQCaNMhVpECRC2QuMusyfa3DYZEquamR
g1uDvE5tkbuRkKuGt2BFR9R1KzMIWgwcUrmOQhUfrUKDuhh7SQOtsnOLIgKI
/icUEVAHu1oz+tlNtNZ5Lodr5LqIzOVgthmR3U73D8TkWf+2f3pxeTH83sXk
ektNMEyJyOvw5vb8Wtxwa7199LDaqSBW6bapmotxIiciDIIfxO7wdLDXY5fn
xWY80fClrT9bZhSH9nOTI3s+A56fj8VrQOwr9IzGNo0e/gcnHqXRieZeJEoc
msbViLGajZPAmSL7jn2jhEMkLAvtwbTuyFot+qokZGIusIPgrPIaEOMBBU3B
i1Yv0Wy9/bW3A3DdmldTtKqd5XS/Utr3xGuU37sORvfwfkMl3RPdN4cntO1Q
xHJhxcbddRXUEwcfjt++PXn7+gRHUOrNRhmfwZ896lTnVc1BM6o5B3miHxki
KDwrpW6ibevxTHOsQwBZIcSmTgCEuyQ5j9t9g6t8G/aJukS6rKcCG4xUZThW
8UYVuj5nl+XwCtxfh7RtOj0IgpsmLv2J+nFjn/EywDkb1QjnYtiuItxGotXA
qzGhqBlsAviNusPdOa0oGVfM2omAgjTXk4mfFq1Xvy79rra1OX2FS60oUzfU
iTk4T2X0OJd5zJ8KEHcjnehi0RyxgK6Mplr5etVSN+7GkgARKtNaME0fDxIt
aWhG7OluLpobnijbcyfyMFMWH3HOsc5tUc0T0mrc8AleXTtwhVvLj0f9VKgP
9PGBkKct7kr28RlVufrFY7jDOkdW7Hp49SUOTLzn71y70tZhzsqQydXRUsxk
Qoi4FBu7SuyepIY/sGink0elsipMgPv0ictWtVi/7d++9ufU40aO9F1b/0Jz
mQq/aYDJ7oGUXOZwCFFht6wbkmZerDWDBAl5FjxjLOAFdFnKlraiA2VEKocb
jtTCsDENjbmSHO6+oOlxVFq7Puzl72/96/6aHF988ZFq4B0Z5R0lzdWvJ59Y
T3Qc4wgScjtDd8vVBG6TL8hMM5mSFxMd5uUSdAUTW2Uj1/R233nxe93qF+jr
cjZSud0RlRCrRUpOw12LCoPlpvBNaNRcKF+5jHTxQm59UXU1L261XCbgL2vE
gbsBZuka8xncrOLJX3fgCTnH2Dg3Mzf6VjRnt/BiqhIJLUio3aPuHs0BT3Xx
POCWkWu45zs1Rq8Av3kOnsMwrP8LnlF5Pfu42305tvaefyQNdS7CwU/P7qsu
TUDJp/rRY2rmiYon/GEefn06oJbxfwREC92XIwAA

-->

</rfc>
