<?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.6 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-chen-idr-bgp-ls-security-capability-03" category="info" submissionType="IETF" xml:lang="en" version="3">
  <!-- xml2rfc v2v3 conversion 3.20.0 -->
  <front>
    <title abbrev="BGP-LS2C">the extensions of BGP-LS to carry security capabilities</title>
    <seriesInfo name="Internet-Draft" value="draft-chen-idr-bgp-ls-security-capability-03"/>
    <author initials="" surname="Chen" fullname="Meiling Chen" role="editor">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <city>BeiJing</city>
          <country>China</country>
        </postal>
        <email>chenmeiling@chinamobile.com</email>
      </address>
    </author>
    <author initials="L." surname="Su" fullname="Li Su">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <city>BeiJing</city>
          <country>China</country>
        </postal>
        <email>suli@chinamobile.com</email>
      </address>
    </author>
    <date year="2024" month="March" day="04"/>
    <area>Security</area>
    <workgroup>Internet Engineering Task Force</workgroup>
    <keyword>Internet-Draft</keyword>
    <keyword>keyword2</keyword>
    <abstract>
      <?line 34?>

<t>As users' traffic faces more unpredictable attacks during transmission, there are more and more end-users now need high security data transmission guarantee, they need ISPs to provide security protection capabilities on the data forwarding path. Therefore, ISPs need to have real-time awareness of the security capabilities available in the network, then form a security capability map, finally provide security protection for users at the routing level.</t>
      <t>The goal of this draft is to collect the security capabilities of nodes, which will be one of the factors to form the routing topology, and use the routing programming capabilities to form a secure routing path. The security capability includes healthy information(such as the device software is up-to-date), security service information, device information(such as the manufacturer information of the equipment).</t>
      <t>The BGP-LS protocol is extended to carry the security capabilities of the node. The controller collects topology information, forms a topology path with security capabilities according to security requirements, and supports SRv6 path sending to execute node forwarding through programming.</t>
    </abstract>
  </front>
  <middle>
    <?line 42?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>SRv6 (Segment Routing IPv6, IPv6 segment routing) is based on source routing and centralized routing. It can realize network intelligent programming and select forwarding paths according to customer needs. At present, there is a lack of effective technical means to inject security factors into the process of collecting network topology and centralized routing to achieve safe routing path forwarding.</t>
      <t>The most important reason for using BGP-LS as the extended basic protocol is that BGP-LS shields the differences of other routing protocols, and the underlying routing protocol types do not need to be considered when transmitting security capabilities.</t>
      <t>RFC7752 standardized North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP, describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol, using a new BGP Network Layer Reachability Information (NLRI) encoding format.</t>
      <t>BGP-LS is a new way to collect network topology. The topology information discovered by the IGP protocol is summarized by the BGP protocol and sent to the upper controller. With the powerful routing and routing capabilities of the BGP protocol, there are three types of BGP-LS routes, which are used to carry node, link and route prefix information respectively. The three routes cooperate with each other to complete the transmission of topology information. The node routing function is to record the node information of the topology, the link routing function is to record the link information between two devices, and the address prefix routing function is to record the network segment information that the node can reach.</t>
      <t>The state information NLRI collected by BGP-LS is described in TLV (type/length/value triplet) format. Each link state described by NLRI can identify a node, link or prefix. Therefore, three types of NLRI are newly set in the standard, of which type 3 and 4 are used to distinguish the prefix of IPv4 and IPv6. There are only two types of NLRI attributes in the original BGP protocol: MP_ REACH_ NLRI, attribute type 14; MP_ UNREACH_ NLRI, attribute type 15.</t>
    </section>
    <section anchor="bgp-ls-node-type-carries-security-capability">
      <name>BGP-LS node type carries security capability</name>
      <section anchor="collection-model-of-security-capabilities">
        <name>Collection model of security capabilities</name>
        <artwork><![CDATA[
                   +----------+
          +--------+Controller+-----------+
          |        +----------+           |
    BGP-LS(Node)                          |
          |                               |
xxxxxxxx|xxxxxxxxx                        |
x         |      x                        |
x   +-----+-+    x                  +-----+-+
x   |Router |    x                  |Router |
x   +----+--+    x                  +-+---+-+
x        |       x                    |   |
x        |       x             +------+   |
x        |       x             |          |
x   +----+----+  x          +---+----+  +--+-----+ 
x   |Security |  x          |Security|  |Security|               
x   |Products |  x          |Products|  |Products|
x   +---------+  x          +--------+  +--------+
xxxxxxxxxxxxxxxxxx  
 
Figure 1: Router and attached security products are used as node units
]]></artwork>
      </section>
      <section anchor="new-node-attribute-tlvs">
        <name>New Node Attribute TLVs</name>
        <t>The Local Node Descriptors TLV contains Node Descriptors for the node anchoring the local end of the link.  This is a mandatory TLV in all three types of NLRIs (node, link, and prefix).</t>
        <artwork><![CDATA[
0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |              Type             |             Length            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                                                               |
     //              Node Descriptor Sub-TLVs (variable)            //
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

               Figure 2: Local Node Descriptors TLV Format
]]></artwork>
        <t>Node attribute TLVs are the TLVs that may be encoded in the BGP-LS attribute with a Node NLRI.  The following Node Attribute TLVs are defined:</t>
        <artwork><![CDATA[
   +-------------+----------------------+----------+
   |   TLV Code  | Description          |   Length | 
   |    Point    |                      |          | 
   +-------------+----------------------+----------+
   |     263     | Multi-Topology       | variable | 
   |             | Identifier           |          |                   
   |     1024    | Node Flag Bits       |        1 | 
   |     1025    | Opaque Node          | variable | 
   |             | Attribute            |          |                   
   |     1026    | Node Name            | variable | 
   |     1027    | IS-IS Area           | variable | 
   |             | Identifier           |          |                   
   |     1028    | IPv4 Router-ID of    |        4 | 
   |             | Local Node           |          |                   
   |     1029    | IPv6 Router-ID of    |       16 | 
   |             | Local Node           |          |                   
   +-------------+----------------------+----------+
              Table 3: Node Attribute TLVs
]]></artwork>
        <t>The security capability is transferred by adding the security capability attribute to the attributes of the local node.</t>
        <artwork><![CDATA[
   +-------------+----------------------+----------+
   |   TLV Code  | Description          |   Length | 
   |    Point    |                      |          | 
   +-------------+----------------------+----------+
   |     TBD1    | Node Security        | variable | 
   |             | Capability           |          | 
   +-------------+----------------------+----------+
              Table 4: New Node Attribute TLV
]]></artwork>
      </section>
      <section anchor="usage-of-new-attribute">
        <name>Usage of new attribute</name>
        <t>When programming the routing path, take the security capability requirement as one of the inputs. The description of the security capability requirement can be structured or one-dimensional matrix, which only needs to be consistent with the router's security capability description; There are many routing rules. After introducing security capability requirements, it is necessary to dynamically adjust the security capability as the position of routing rules according to the requirements. The main rule strategies are: ① Select the routing node that meets the security requirements as the forwarding node when the path is reachable; ② Select the shortest path when all the safety requirements are met; ③ When the same path length and security requirements are met, select the path with small load for forwarding.</t>
      </section>
    </section>
    <section anchor="bgp-ls-link-type-carries-security-capability">
      <name>BGP-LS Link type carries security capability</name>
      <section anchor="collection-model-of-security-capabilities-1">
        <name>Collection model of security capabilities</name>
        <artwork><![CDATA[
                   +----------+
          +--------+Controller+-----------+
          |        +----------+           |
          |                               |
          |                               |
xxxxxxxxxxxxxxxxxx                        |
x         |      x                        |
x   +-----+-+    x  BGP-LS(Link)    +-----+-+
x   |Router |----x------------------|Router |
x   +----+--+    x                  +-+---+-+
x        |       x                    |   |
x        |       x             +------+   |
x        |       x             |          |
x   +----+----+  x          +---+----+  +--+-----+ 
x   |Security |  x          |Security|  |Security|               
x   |Products |  x          |Products|  |Products|
x   +---------+  x          +--------+  +--------+
xxxxxxxxxxxxxxxxxx  

Figure 5: The peer node transmits the security capability through the link
]]></artwork>
        <t>The router and its attached security products are the basic units. When collecting status information, only some nodes can directly transmit the node status information to the controller through the BGP-LS protocol. Other nodes that do not directly transmit the node information need to transmit the node information to the direct node to achieve the transmission of security capability information. Therefore, for non direct nodes, It is required to report its own security capability information through the BGP-LS link state data packet.</t>
      </section>
      <section anchor="new-link-attribute-tlvs">
        <name>New Link Attribute TLVs</name>
        <artwork><![CDATA[
      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+
     |  Protocol-ID  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                           Identifier                          |
     |                            (64 bits)                          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //               Local Node Descriptors (variable)             //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //               Remote Node Descriptors (variable)            //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //                  Link Descriptors (variable)                //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      Figure 6: The Link NLRI Format
]]></artwork>
        <artwork><![CDATA[
   +-----------+---------------------+--------------+
   |  TLV Code | Description         |  IS-IS TLV   | 
   |   Point   |                     |   /Sub-TLV   | 
   +-----------+---------------------+--------------+
   |    1028   | IPv4 Router-ID of   |   134/---    | 
   |           | Local Node          |              |                  
   |    1029   | IPv6 Router-ID of   |   140/---    | 
   |           | Local Node          |              |                  
   |    1030   | IPv4 Router-ID of   |   134/---    | 
   |           | Remote Node         |              |                  
   |    1031   | IPv6 Router-ID of   |   140/---    | 
   |           | Remote Node         |              |                  
   |    1088   | Administrative      |     22/3     | 
   |           | group (color)       |              |                  
   |    1089   | Maximum link        |     22/9     | 
   |           | bandwidth           |              |                  
   |    1090   | Max. reservable     |    22/10     | 
   |           | link bandwidth      |              |                  
   |    1091   | Unreserved          |    22/11     | 
   |           | bandwidth           |              |                  
   |    1092   | TE Default Metric   |    22/18     | 
   |    1093   | Link Protection     |    22/20     | 
   |           | Type                |              |                  
   |    1094   | MPLS Protocol Mask  |     ---      | 
   |    1095   | IGP Metric          |     ---      | 
   |    1096   | Shared Risk Link    |     ---      | 
   |           | Group               |              |                  
   |    1097   | Opaque Link         |     ---      | 
   |           | Attribute           |              |                  
   |    1098   | Link Name           |     ---      | 
   +-----------+---------------------+--------------+

               Table 7: Link Attribute TLVs
]]></artwork>
        <t>The new attribute describes the link security capability and transmits the link security capability information through this attribute.</t>
        <artwork><![CDATA[
   +-----------+---------------------+--------------+
   |  TLV Code | Description         |  IS-IS TLV   | 
   |   Point   |                     |   /Sub-TLV   | 
   +-----------+---------------------+--------------+
   |    TBD2   | Link security info  |   ---        |
   +-----------+---------------------+--------------+

            Table 8: New Link Attribute TLVs
]]></artwork>
      </section>
      <section anchor="useage-of-new-attribute">
        <name>Useage of new attribute</name>
        <artwork><![CDATA[
+------+          +------+
|  A   |          |  B   |
+---+--+          +--+---+
    |SCicg A         |
    +--------------->|
    |       SCing B  |
    <----------------+
    |SCing <A,B>     |
    +---------------->
    |                |

Figure 9: Assosiation security capability interaction
]]></artwork>
        <t>The Assosiation security capability depends on the security capability enabled by the node. As a node directly connected to the controller, node B first interacts with the enabled security capability information of the opposite end in a two-way manner, and then the opposite end initiates the transmission of the assosiation security capability information.</t>
        <t>The decision of assosiation security capability can be divided into two situations: one is under the same security domain, and the other is under different security domains. 
1. The decision rules for link security capabilities under different security domains are as follows: SCing represents the enabled security capabilities of a node.
Example: SCing A=[1,0,0,1,0,……]，SCing B=[1,1,0,1,0,……]，SCing Assosiation&lt;A,B&gt; = SCing A &amp;&amp; SCing B</t>
        <t>When the link passes through more than two nodes, it is necessary to logically and operate the security capabilities of all nodes in the path to obtain the link security capabilities.</t>
        <ol spacing="normal" type="1"><li>
            <t>The decision rules of assosiation security capability in the same security domain are as follows: SCing indicates the security capability of a node that has been enabled.
Example: SCing A=[1,0,0,1,0,……]，SCing B=[1,1,0,1,0,……]，SCing Assosiation&lt;A,B&gt; = SCing A || SCing B</t>
          </li>
        </ol>
        <t>When the link passes through more than two nodes, it is necessary to logically or operate the security capabilities of all nodes in the path to obtain the link security capabilities.</t>
      </section>
    </section>
    <section anchor="bgp-ls-prefix-type-carries-security-capability">
      <name>BGP-LS Prefix type carries security capability</name>
      <section anchor="collection-model-of-security-capabilities-2">
        <name>Collection model of security capabilities</name>
        <artwork><![CDATA[
      +----------+                  +----------+
      +Controller+                  +Controller+  
      +----------+                  +----------+ 
          |                               |
          | AS 100                        |
xxxxxxxxxxxxxxxxxx                        |AS 200
x         |      x                 xxxxxxx|xxxxxxxx
x   +-----+-+    x  BGP-LS(Prefix) x  +-----+-+   x
x   |RouterA|----x-----------------x--|RouterE|   x
x   +----+--+    x                 x  +-+---+-+   x
x        |       x       xxxxxxxxxxx  |   |       x
x        |       x       x     +------+   |       x
x        |       x       x     |          |       x
x   +----+--+    x       x  +---+--+  +--+---+    x
x   |Router |    x       x  |Router|--|Router|    x            
x   +-------+    x       x  +------+  +------+    x
xxxxxxxxxxxxxxxxxx       xxxxxxxxxxxxxxxxxxxxxxxxxx

Figure 10: Security capability is transferred between ASs through Prefix
]]></artwork>
        <t>The router and its attached security products are the basic units. When collecting the status information, only some nodes can directly transmit the node status information to the controller through the BGP-LS protocol. Other nodes that do not directly transmit the node information need to transmit the node information to the directly connected node to achieve the transmission of security capability information. In the figure, nodes A and E are direct connected nodes, which are connected to their respective controllers. Nodes A and E are responsible for collecting the security capabilities of other nodes in their respective fields.</t>
      </section>
      <section anchor="new-link-attribute-tlvs-1">
        <name>New Link Attribute TLVs</name>
        <t>The IPv4 and IPv6 Prefix NLRIs (NLRI Type = 3 and Type = 4) use the same format, as shown in the following figure.</t>
        <artwork><![CDATA[
      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+
     |  Protocol-ID  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                           Identifier                          |
     |                            (64 bits)                          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //              Local Node Descriptors (variable)              //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     //                Prefix Descriptors (variable)                //
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

            Figure 11: The IPv4/IPv6 Topology Prefix NLRI Format
]]></artwork>
        <artwork><![CDATA[
   +---------------+----------------------+----------+
   |    TLV Code   | Description          |   Length | 
   |     Point     |                      |          |                 
   +---------------+----------------------+----------+
   |      1152     | IGP Flags            |        1 | 
   |      1153     | IGP Route Tag        |      4*n | 
   |      1154     | IGP Extended Route   |      8*n | 
   |               | Tag                  |          |                 
   |      1155     | Prefix Metric        |        4 |     
   |      1156     | OSPF Forwarding      |        4 |       
   |               | Address              |          |                 
   |      1157     | Opaque Prefix        | variable |  
   |               | Attribute            |          |                 
   +---------------+----------------------+----------+
           Table 12: Prefix Attribute TLVs
]]></artwork>
        <t>An AS has at least one super direct connection node, which has the security capability information of all nodes under the AS. By adding new attributes to Prefix, the security capabilities of the entire AS can be transferred.</t>
        <artwork><![CDATA[
   +---------------+--------------------------+----------+
   |    TLV Code   | Description              |   Length | 
   |     Point     |                          |          |                 
   +---------------+--------------------------+----------+
   |      TBD3     | AS security capabilities | variable | 
   +---------------+--------------------------+----------+
             Table 13: New Prefix Attribute TLVs
]]></artwork>
        <t>AS Security capabilities means the security capability information of all nodes under the AS, that is, the security capability information of all nodes is spliced, such as {[IP address (A)+node security capability], [IP address (B)+node security capability]...}.</t>
      </section>
      <section anchor="usage-of-new-attribute-1">
        <name>Usage of new attribute</name>
      </section>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
    <section anchor="Security">
      <name>Security Considerations</name>
      <t>TBD</t>
    </section>
  </middle>
  <back>
    <?line 366?>



  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+08W24jyZH/AnSHBBqwpRVJSZRa3c3xDJZSq70y1BqhpfF8
GMYgWZUk06oHXZkliba82AP4xzew/eFT7Gl8gb2CIyIflUVWUc/u3R27ejAo
VWU8Ml4ZGZHFbre7vqY0z+IfeJJnYsB0UYr1NTkr6Fbp/s7Ou53++lrE9YDJ
bJyzV+xoKqIrgCtHqVRK5pmezwD05Pjyw/oaLwQfsAsRlYXU8/W1mwm8ybQo
MqHZcTaRmRCFzCbskqsr9iEvIqC3vhbnUcZTwBIXfKy70VRkXRkX3dFk1k1U
V1l83YjP+EgmeLuzh4Ba6gT5ngombrXIkB/F8jE7/Pl59/SC6ZxFvCjmzKFg
HoUUigHDo1Ehrgd2fP9ofS3hGTAtsvW1q5vB+hpjXT+D7ntkzzy7EvObvIhB
OK9YzDUw0d/p73f3uvus26UnTCo2lkkiYhAd46XOU65lxJNkzkZzdpsm/WIc
MTlmWa7ZRF4jTRg2zQug22VFjlMTsdR5AXIvRJpfCzfcaIoBZjVAlWT4h5Hh
RwHTAxG7p3kxwSEy4+xjDlMnuAhkAbMW8hcwlB7kZaaLuR2JT0TKZTJgqIzU
oPz3CN+lhKQX5SlyaWieSnZRvgAxVSZymYr51wW58pHSBY80/j1UrFSiUD8F
YfDxWEZszCNQapoXgpXZrADRRZqPEsG41jy6UiwuyfhgfKas9XbQeAAALNdA
gjuYG5HFXSIAAr9hYLgxm8rJtDIlUDKv4WKTksOfWgjCOjdAJxfnCg1xVuTX
MhYVPDzQItIIWLNK+BsNmtCP8+KGFzFyPeN62mOXyC08BRKEmEgA9ikH4wDv
S7papjALgBKZUOQMiK3ZAfg1iJ1EJA1RsHIw6yviP0PqKeMNsHOW8lkHzDsj
c141NcBh9ARaIBJFXmqcTyKuRdJDTcKc2CTnieEV3IbCAPoP+m8OLhTpFZPI
0SVioTrsZiqjKbsBp2MjAXIUbvZgGeBFhI/mFPKh81me5JN5h1QPrNbewkwm
BU9TvK9RdaiseAIIp6dGucksSkpglk1BV3o6p7BaYGTIsw1VAvtcGfWLaxkB
jnysUZcojXLW1XkXY8tmp0IOsqWRAaKOg25DnvKsRJkA30U4yMlL/LaUs1Rk
etMryEZU1GwOOkF+KOTGxv5MmF2pJLIvUJQRTgQrR4G6LZyKlVdFfS54C9ZT
vUUJg5b1tM2qoyg3PgOM+SEFTgqiKMxKGV2rcjbLC6B78en6wGBVMCELKG4B
UhuWQz/UU9A0xIHAMnouPqUyjhNa0l7hqlHkcUlegE+IyMaFmCAH7JO1lpPz
64MO/R9om1fWkDZRxCOuQL6gGJWXsFh6I0P2Ixhc8ET+DkbY5z12okEWGUUC
eOH8GQSqRZLICeIPTZrEIMjBFkLNghgjSAfyFJSFAUf12BDxCBCXdhFUoo4S
iLOoazEeo/9DTII4MM1w2WOpgFCJuGT2GyToNeO8E5jMyUqAw8jGLmsbyIWb
i7eDFiEgCQ6LCMQXpvi47pnBNL1pp7mCaJOiLXCUv+DKBy6Es6ZvfcdbPegG
Fp3QIfQUYpwdrYCBJLa+LEEcEI8j4wg5CiyMMITAGiWOLwF/kczx7eIohukW
RMic0gAX/UfkTwpiMKx6EAYhdtuFSRN0o5/Q/D99OHrz5nWfUR6IckFBnoEk
pt1DWKVj9l7CkitHpQsPpzK76l5oTHCQ3Uu79obJ3cbl8SaYfxVVvnNixMCk
IkCHXgoGEU15JlWK+ZCJ3QliVxX241p0QsumqZJNAKPjIk+dXShjzFNOIsDo
gJoqYIUCAFBuho5vNapNQFuSbse+54D0hkacWaM75XPQ2ScBhuVCeTjDjbPT
TyebkDNEOXmMeUMStvZA7oFYb/g8XNcWrdpEx6ZICGakIsgBcX4jE2tPgMPQ
AFWZprwgHdoRh+EI4+1g4tbPIP5R+HWRuMe+R7mRC+Y3ohiXSS3iuPumyB4S
CpMqCJdCWKutEnPEVK3YOK5U4UKCQbdD1uAJY1gQY3lbEwmEoJkJNImTHNEz
+GFqOcwQrckYBGjPeh9pIJ0lQpv1vpbH4ZQaFGAI0HrgJDEuM5PmmGSlEBgy
/UrXtLRW6Qb+RTO8HxkNC5GNwGoEevlNbtf6IHzwOC4wfFp5PYBXa4NuBQop
UUzzE7JrSzT1wdM4awiBrhD4KBhi5QLO/WlPdHn6S7aBlrGdiGyip9vXPClR
FRL1sumciB1zGxkssQoJ4DbUgC0IfpmW4zm6WWU9EMSNGGqp84JREg40QvDP
BDMq7fJhFxY7OMwYK0KxPRL2fs1ywT1RzqVU1oWM+AEQlvd9AsB13jJCoHkG
5FCHC6xoE3KFcnzkhZxgsl1zM9jrnf/APh0Pj/7jBwLsVJCGzd39r2jMd2cr
R73umZTF6ok0TW/QGdHHGzJZgnjFjuz6DHpPAYxy+MbVBsf/J1y421u6trr+
2goH+OdbRz5IBWPrg++asAVE7sxgM8mNM+B2s4GV+uAFzO2Db+11525uVw1e
xHzfYDOjLTOdhsH+vRl+h9klBLm7luH+fYB9q7sC+1aIPWS8mfO7hWk2D96q
VHT/4EAFC1wThmDwVvB4y97CvZWMq00hwgDIP7+r39cui+LcpPVqEYV7fhfe
h/pr5rVb8eqN+nbpQurw3wc5wb3m7oBZFWJUofLGVMS1/bdh0ccnroxbl5nU
ynkiefAZ5CToDJDSu6gAgVm5+H6aY+5OA95T3J1Rro6xGxMHLiGnX3qLubNf
M3gWTfPCpV0J4YMM2i2IGKZ7DIIiLA+UJKUYcgHNnIhg7Qz28w0RW7GNKtCb
1c+E3M0eq6LNToN97jY86zc823NBYAdA+hD099lrdsDesLfs3WOeWTToR8/6
Z/Es2OUlRurwqr8/pbW19v7z8vPoy/GzvV1/vmBW7KIcddE02cY1JLlYtqoF
8O3tF+bnBeSztNpZB+4PVjnWB0p8Ki+lQbzmnja3tn9QkpbCxmIkzB7EJFi6
qttU0JQJc0MY3Yh8DyscSZLfoJc2BAOiFoNvZSIe1FbycDV2wXbpWlreUUM4
0SMkBX85AWAaUamBeeO9Yx6MnecSUtR2NYcrBXsmjxAWDvYsqo9lomX30u0L
HAVnijUeAw5OTFoqIVa38Lh8BYh2d/r7Zhip5UPCYSMNIXwRerdOH8Bem/ff
zvhvIakm6IDofWxX+n8q2wcB22c8XUDUTB/A3pj3Jxfdkws2hL3GA8Cq98+X
9luLCFN2s8Z2T97jkhNC77fRD5z6ifTfefoHrfR3D16c/tN8JLguSS17g+Zc
wkWy1rK4MjvwsShseQM2sS5laAIItjCmlhHsmVxiQbKgivM/Vci6PHy/a1CR
KnzG6ync50RHlZhfnsclk9kftKSgtSz1O8Un1M7BEprXNb78HqudYU271r7h
egrbfX4lWi0p6Atglhx0jWQ2K7UyVZ84UHdrS62OzFYrlS5K6rTEWIwA9N1Y
pqZVjUVxDlO5dYUwqgdQhT2s6iqN6G5caY5qW8VPG3flIZ9fBYUGyKnnXihF
mQgs4Y81dX9Mm6K5TLzYNpHUlssElud5QYXMeJ7x1Pa1efybUrX16uaugj7L
lXSCrPFUbznQXAPqRhEp7DhoNAqWazGhjk8hBuzvf/ozGLtvFjrMpppBCZIQ
WtWZC/E79oJGCMGacjryjf0DmH5hqsCJ+Apo/iWkqWCjAxFI2xYVAprNi+lE
LBFEzQiNaP7KvndkFC6WhMCUxWzZtpFjg6DjejieS9MdS5F4kvOYNmQLnQ9f
7sGK/o+33LMUvRqvp5Z7br9IuceWrFBRtONpK/fg09vlGPyvcs//y3KPr/a8
HlDkmwlsv1I0s7091RppXZPaFVjqGVhR1Y4QyT31I8Rhep1UPOqZSBU0ZrEq
X6p6055WMpWnpgakaDGMIW5FGivelv+qRrSMwq0AwTmBcFILxxF67Ftq6xhi
FO1ti3QF0ZCa66SuHmV5MjitLqpmc1MfqfkMSL2l5LoSGKSzPAvRw5J7os2a
Q2E/Np0bbFWT6vKb7D4STWILmyl4zGjGoyth2pW2IkiLwnJFsB7U/y/X1qpa
0Lm1EdxHfdHaV+NmdOG6ewAetnGwz0ag7gf0K15qXou1uLZyVXMprqrFfTZ+
Pok01+KhDH1+flBE6DMPEM4L89OYYjFfajwwqwcxR93Fxepi48a4eTu38NTv
Ov3GuHlfDCNMPQfHsXDb6XbGzeaPT7dt1beCezqbvsDTXN/BEbt7+9sAwups
Vgw1FVgWmG+YS42Bd46BpQIPMbC/85kZ2Nt5lgRCx3siA7vPksDzGXhrbGAY
pzKTtI3Ek2oBZL+/7cq+DQxMYD2dsQ1YUvJik4VwD2bA2MBHfivTMjXLcQ0S
GHjXzsAIMrcbGde6Oo9j4N2OY6CHZ2hEcU21GA8J9Hd32hkghhe4eCQDxga+
ywx1SGzqkMjA7meVQJ/uL48hYo15mWj2UUC2E4UMvF1iAOD26J7C6Xl1zDlk
vL9CckvNusczvk/3H88hj3OpDShSXTlI6ztLjL+mezwy5mdao9gGd0D3F+Zg
3ScJhE6tva6A85h/Ts7yrAm/oXvbyDgNfOVBDDR1Mh7JgAkXZgWtdzKaGXjK
CrW0ipvq6JtBcyoebudqJdHghKU/OdZYi8PDYrV9ZOvQ5s2EVBXR9gL7jzSP
uDx836+MwguNvpGiEd4kXGr+fJswBvF20L4/q9XLRVvB3IwKyjH22vJ0YQLD
ujDh9tBMxdZb6nBbXjrs7uJIRhOCD6fPFuf8jX3uiAAYnhH243+2JJ4KPwz8
2bBz+M0q/N1v6vhDfnxl5d2ADZXKlTTG3Wz8kJ9we4o/9Lr7AGMxE1nsP+dp
GiIyVKk/q2s+jhgqe4KxKl1EeZaZw5RLRZGOGXrIxrLAU+yWW1W1CxyR+zzb
djXyGZXn6fsnOnyD5xO7eGg55cBF4Y+ZZk3DpQaJ2NCzdKQWu3T3SrsqjThB
xyKSDsd98LbnEkv8Him2XxTc5AxYLAlKDajDg1/T4CH7quBefdaVY4uhOk1r
zgt7AHeWXy9CKDx1tOu6RZZl09bAwk5LdMVy+32IqQrHlT2iATMwLlAI+wWG
ukfP9pQ2d73Q41uOJ58dnuHXv9rt7MA//P/f/+tv8N+v/+e//2gdEl/utrwM
XMD449cOJfvJT5xH+x6dX2NmoEWyEbOU0Nd2esrNaWZb9WpoNCX5xLWZ8PSY
Pdi98pMj7H+YkqAMWjiAKx/hybVVy577QKLfqNEHmKLMWo2rRaEyi2GCzn2a
cHotmhLnFHCM8Bi41f0X0u3d3WfULfZIv5BqfQfs3JzU/tw9sJZGFVt+6yGC
PlgDRO3t46mwML94ZIdseAGJcVP91w1+RIcMcPV3dh7UJ1s8Zb2yX2bUuolP
whG3ta7ZsKVrduv7Zsd3FdA9vbPboHtWAYVT8kA1wdyFA1YB0f/DTtqDgRoO
Aa2a063vrFV9ta0AqPGI+a1/fuelVxtAV71H1kS1G3bIPNU2g1p+UVlHdWJ6
p/pdglUHj+x3NcOLKoYZM/qsHTT7qck/Yxetlt6+SEftxAT/MSm+YyczJF0d
m4Ospr9WJ1v7GG0x4ZZF8KVZIExQ5dkSehyJx3Zwt4aZ36Ke21a0PJC9WcDq
ZMf0QekDmnRooLVPjtwCZ0/NUxeAClFf2w+Z7B/7m/77d0pbjFA7mKqoKbYa
7bpanRU2Qu79qzHYhL/1+jE1Bh/XF/wSjThr7P/bjTi38Oya/hs65DY5oz9C
Hnjlw5pydqFuuprPglYHVlsqaqzlxGp1ZLXNAFceKn4+5xAvdl/3LXqsWePJ
dxXS8FQXjr4j4F4ASGkIu+STBcD9f8uWAfcDwGP3ob/B4Ie9XQIMeAroPEZW
FQev7TBrHPVSvYfet7cLwAd21LcX5x/QpNw5xmZg1jaJof2A+MmTeOP4MDV7
OxcPHRxAbmXh0d8fPMvm3GVqrLv9geO5rcQ6xByRNuCQJCWCK011JVXOqJQT
JhiUGNGHaibBmPL2Df5CQa7a5FbVquFFjx368/G16i6dGjaMd+7/LRZcgwrE
56pmQSK86sR8q1SfE4ecTp8Ui17UNtpnQWV/F1pAbM3SXT5f/xzCS6a5Z+r/
95nnRcNuB7mzP8LyHPPrmJ2BVG02tgIP/kbFLJGRiDvM/SDR7391cu5/s2Bj
uLll9jLLaH/dYbWhhyuG9nq9P/R8L6StFWJ/qWd4NgTzNL+fYqrE7Pev8Okf
TDotUW5pXv14U5bTgTw86Q0ehyPNJ6eIzct9CaN7Y7Aevq9+12zE8Tf1zL9/
AKGU7WWXTwAA

-->

</rfc>
