<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.39 (Ruby 2.6.10) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-smith-idr-rr-deployment-considerations-02" category="info" consensus="true" submissionType="IETF" tocDepth="4" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="BGP RR Deployment Considerations">BGP RR Deployment Considerations</title>

    <author initials="D." surname="Smith" fullname="David J. Smith">
      <organization>Cisco</organization>
      <address>
        <email>djsmith@cisco.com</email>
      </address>
    </author>
    <author initials="S." surname="Krier" fullname="Serge Krier">
      <organization>Cisco</organization>
      <address>
        <email>sekrier@cisco.com</email>
      </address>
    </author>
    <author initials="S." surname="Gaw" fullname="Spencer Gaw">
      <organization>CoreWeave</organization>
      <address>
        <email>sgaw@coreweave.com</email>
      </address>
    </author>
    <author initials="I." surname="Means" fullname="Israel L. Means">
      <organization>AT&amp;T</organization>
      <address>
        <email>im8327@att.com</email>
      </address>
    </author>
    <author initials="K." surname="Szarkowicz" fullname="Krzysztof G. Szarkowicz">
      <organization>HPE</organization>
      <address>
        <email>krzysztof.szarkowicz@hpe.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="17"/>

    <area>Routing</area>
    <workgroup>Inter-Domain Routing</workgroup>
    <keyword>BGP-4</keyword> <keyword>BGP</keyword> <keyword>routing</keyword> <keyword>RR</keyword> <keyword>route reflector</keyword>

    <abstract>


<?line 188?>

<t>In BGP networks, Route Reflectors (RRs) simplify the provisioning of the Internal BGP (IBGP) control plane and mitigate the scaling challenges of maintaining a full mesh of IBGP sessions among border routers. Because of these operational benefits, RRs are widely deployed in modern networks utilizing BGP. 
This document describes common RR design options, their associated trade-offs, and deployment best practices based on industry operational experience.
Operators should consider these suggestions when designing and operating BGP networks because BGP control plane stability is essential to overall network stability.</t>



    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-smith-idr-rr-deployment-considerations/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        Inter-Domain Routing Working Group mailing list (<eref target="mailto:idr@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/idr/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/idr/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/djsmith20171/draft-smith-idr-bgp-rr-deployment-considerations"/>.</t>
    </note>


  </front>

  <middle>


<?line 194?>

<section anchor="introduction"><name>Introduction</name>

<t>In BGP networks <xref target="RFC4271"/>, Route Reflectors (RRs) <xref target="RFC4456"/> simplify the provisioning of the Internal BGP (IBGP) control plane and mitigate the scaling challenges of maintaining a full mesh of IBGP sessions among border routers. Because of these operational benefits, RRs are widely deployed in modern networks utilizing BGP. 
This document describes common RR design options, their associated trade-offs, and deployment best practices based on industry operational experience.
Operators should consider these suggestions when designing and operating BGP networks because BGP control plane stability is essential to overall network stability.</t>

</section>
<section anchor="performance-and-scale-considerations"><name>Performance and Scale Considerations</name>

<t>BGP RR performance and scale depends on a variety of factors including but not limited to:</t>

<t><list style="symbols">
  <t>Available system resources: CPU performance, memory speed and quantity available.</t>
  <t>Number of BGP sessions, associated timers and update-groups.</t>
  <t>BGP address families configured <xref target="BGPAFI"/>, <xref target="BGPSAFI"/>.</t>
  <t>Number of routes and associated paths for each BGP address family enabled as well as route/path churn.</t>
  <t>Whether the RR operates in the BGP control plane only or also in the IP forwarding plane.</t>
  <t>BGP capabilities enabled including but not limited to, for example, inbound/outbound route policies (simple versus complex), Extended Message support <xref target="RFC8654"/>, Add-Paths <xref target="RFC7911"/>, Graceful Restart <xref target="RFC4724"/>, Optimal Route Reflection <xref target="RFC9107"/>, Route Target Constraint <xref target="RFC4684"/>, automatic detection and isolation of slow peers, and RIB/FIB filtering.</t>
  <t>Transport layer optimizations <xref target="RFC9293"/> including but not limited to Maximum Segment Size (MSS), window size, Selective Acknowledgement (SACK) <xref target="RFC2018"/>, and TCP Path MTU discovery <xref target="RFC1191"/> <xref target="RFC8201"/>, as well as TCP-AO session authentication <xref target="RFC5925"/>.</t>
  <t>Network latency to and from clients and non-client peers.</t>
  <t>BGP implementation and performance of the network operating system itself.</t>
</list></t>

<t>Operators should consider all these factors as part of their RR deployment. 
Further, since these factors vary widely among network operators and RR platforms, specific BGP RR performance and scale guidelines are outside the scope of this document. 
Operational best practices related to the management, monitoring and maintenance of RRs are also out of scope.</t>

</section>
<section anchor="cluster-design-considerations"><name>Cluster Design Considerations</name>

<t>The placement of an RR within the Interior Gateway Protocol (IGP) topology is an important design consideration. The resulting network latency can affect TCP performance and, consequently, BGP session performance. In addition, when the IGP metric to the BGP NEXT_HOP is considered during best path selection, an RR’s location within the IGP topology can influence the path it selects.</t>

<t>RRs have therefore traditionally been deployed in close IGP proximity to their clients. This approach reduces latency and helps ensure that the RR and its clients have similar IGP metrics to each NEXT_HOP. Although latency remains an important consideration, mechanisms such as BGP Add-Paths <xref target="RFC7911"/> and BGP Optimal Route Reflection (ORR) <xref target="RFC9107"/> can mitigate path hiding and improve the paths advertised to RR clients. See <xref target="path-selection"/> for additional details.</t>

<section anchor="redundancy"><name>Redundancy</name>

<t>BGP RR redundancy enhances network stability by eliminating single points of failure and protecting against RR-level outages. Note, however, that excessive RR redundancy can be detrimental. This is because the more RRs a client (e.g., border router, PE router) peers with, the more IBGP sessions, updates, and paths the client must carry and process in its BGP table. If we consider two RR clusters (1 and 2), as shown in Figure 1, the RR clients (C-2A, C-2B, C-2C) in cluster 2 must process 50% more sessions, updates, and paths compared to cluster 1 clients. For example, if each of the RRs advertised the same 1.5 million (1.5M) routes to the clients, then the BGP tables on cluster 1 clients would carry 3M paths, while the BGP tables on cluster 2 clients would carry 4.5M paths. That is, the incremental overhead of BGP paths, sessions, and updates increases linearly with every redundant RR in the cluster.</t>

<figure title="Two RR Clusters with Redundant RRs"><artwork><![CDATA[
 +----------------------------+     +-----------------------------+
 |         Cluster 1          |     |          Cluster 2          |
 +----------------------------+     +-----------------------------+
 |                            |     |                             |
 |      RR-1A      RR-1B      |     |   RR-2A    RR-2B    RR-2C   |
 |       /\\       // \       |     |    |\\      /|\      //|    |
 |      /  \ \   / /   \      |     |    | \ \   / | \   / / |    |
 |     /    \  X  /     \     |     |    |  \  \/  |  \/  /  |    |
 |    /      X   X       \    |     |    |   \ / \ | / \ /   |    |
 |    |    /  | |  \     |    |     |    |    X    *    X    |    |
 |    |  /    | |    \   |    |     |    |   / \ / | \ / \   |    |
 |    |/      | |      \ |    |     |    |  /  /\  |  /\  \  |    |
 |    ||      | |       ||    |     |    | / /   \ | /   \ \ |    |
 |    ||      | |       ||    |     |    |//      \|/      \\|    |
 |   C-1A     C-1B     C-1C   |     |   C-2A      C-2B     C-2C   |
 |                            |     |                             |
 +----------------------------+     +-----------------------------+
]]></artwork></figure>

<t>Further, when a route is no longer available and needs to be withdrawn, an RR client cannot withdraw a route learned from its RRs until it receives a withdrawal from each of the RRs.
As a result, increasing the number of redundant RRs could also lead to slower BGP convergence. 
Again, the incremental overhead of BGP sessions, updates, and paths increases linearly with every redundant RR in the cluster.</t>

<t>The optimal number of redundant RRs that a client should peer with is deployment-specific, influenced by the 
network's architecture, scale, failure domains, and resiliency requirements.
A common geo-redundant deployment model involves clients peering with four RRs, organized as two clusters, each comprising a redundant pair.
Further, depending on the network services and control plane scale, different RR clusters may be suggested for different BGP address families. See <xref target="address-family"/> below for more discussion on this topic.</t>

</section>
<section anchor="clusterid-configuration"><name>CLUSTER_ID Configuration</name>

<t>Redundant RRs within a cluster are not required to share the same CLUSTER_ID.
When redundant RRs within a cluster use different CLUSTER_IDs, they treat each other as non-client IBGP peers, processing and accepting each other’s updates.
Conversely, if they share the same CLUSTER_ID, they continue to exchange routes but will ignore reflected routes from one another to avoid routing information loops, as defined in <xref target="RFC4456"/>.</t>

<t>Consequently, there is no benefit to IBGP peering between redundant RRs sharing a CLUSTER_ID, unless either of the RRs have EBGP sessions or redistribute local IGP, static, or connected routes into BGP. This is because the CLUSTER_ID is not prepended to such non-IBGP learned routes as these are not reflected routes per <xref target="RFC4456"/>. As a result, these non-reflected routes would be exchanged between redundant RRs configured with the same CLUSTER_ID but not discarded.</t>

<t>Although using a shared CLUSTER_ID reduces resource consumption and update processing on redundant RRs within a cluster, it can potentially limit resiliency in the event of simultaneous BGP session failures involving multiple RRs and clients within the cluster. Therefore, it is suggested that redundant RRs within a cluster peer with each other using unique CLUSTER_IDs.</t>

</section>
<section anchor="cluster-sizing"><name>Cluster Sizing</name>

<t>In addition to managing the number of redundant RRs per cluster, it's also important to maintain moderate RR cluster sizes (i.e., the number of client sessions per cluster) to limit the blast radius in the event of an RR cluster failure.
Accordingly, BGP networks often require multiple RR clusters - not only for fault containment but also for horizontal scaling (sessions, path selection), geo-redundancy, and improved BGP best path selection.</t>

</section>
</section>
<section anchor="multi-cluster-designs"><name>Multi-Cluster Designs</name>

<t>While the BGP control plane is essential to network stability, the RR design is essential to BGP control plane stability. In general, there are three (3) common multi-cluster RR designs:</t>

<t><list style="symbols">
  <t>Full mesh</t>
  <t>Multi-tier</t>
  <t>Multi-plane</t>
</list></t>

<t>Each of these designs has its own set of trade-offs which are described below. These are also not the only design options, as hybrid deployments combining these approaches are also possible.</t>

<section anchor="full-mesh"><name>Full Mesh</name>

<t>A full mesh, multi-cluster RR design employs a full IBGP peering mesh between all RRs in all clusters as shown in Figure 2.  This is the most common and widely deployed multi-cluster RR design, as it effectively balances scalability and fault isolation while optimizing the distribution of BGP routes and paths within the network. It achieves this by minimizing the number of IBGP hops that updates traverse, which leads to improved BGP performance at scale.</t>

<figure title="Full-Mesh Multi-Cluster RR Design"><artwork><![CDATA[
               +---------------------------------+
               |            Cluster 1            |
               |   +-------+         +-------+   |
               |   | RR-1A |---------| RR-1B |   |
               |   +-------+         +-------+   |
               +----/-|-\-\-------------/-/-|-\--+
                   /  |  \  \         /  /  |  \
                  /   |   \   \     /   /   |   \
                 /    |    \    \ /    /    |    \
                /     |     \    X    /     |     \
               /      |      \ /   \ /      |      \
              /       |       X     X       |       \
             /        |     /  \   /  \     |        \
            /         |   /     \ /     \   |         \
           /          | /        X        \ |          \
          /           X         / \         X           \
         /          / |        /   \        | \          \
        /         /   |       /     \       |   \         \
       /        /     |      /       \      |     \        \
      /       /       |     /         \     |       \       \
     /      /         |    /           \    |         \      \
+---|-----/-----------|---/---+    +----\---|-----------\-----|--+
|   |    / Cluster 2  |  /    |    |     \  | Cluster 3   \   |  |
| +-------+         +-------+ |    | +-------+         +-------+ |
| | RR-2A |---------| RR-2B |--------| RR-3A |---------| RR-3B | |
| +-------+         +-------+ |    | +-------+         +-------+ |
+---|-|------------------|----+    +----|----------------|--|----+
    | |                  +--------------+                |  |
    | |                  +--------------+----------------+  |
    | +---------------------------------+                   |
    +-------------------------------------------------------+
]]></artwork></figure>

<t>However, for massive-scale BGP deployments with many RR clusters, the IBGP full mesh between RRs becomes a scalability bottleneck. This is due to high RR session counts and the provisioning complexity involved when adding new RR clusters to the topology. For example, introducing a new RR requires configuring new IBGP sessions on all existing RRs, which increases overhead and BGP session density. This N^2 scaling challenge can also degrade BGP update processing and network convergence, much like a full IBGP mesh between a large number of border routers without RRs.</t>

</section>
<section anchor="multi-tier"><name>Multi-Tier</name>

<t>A multi-tier, multi-cluster RR design is a hierarchical architecture involving multiple tiers of RRs, as illustrated in Figure 3. This design is intended for massively large-scale BGP deployments with many RR clusters.</t>

<figure title="Multi-Tier Multi-Cluster RR Design"><artwork><![CDATA[
                  +-----------------------------+
                  |          Cluster 2A         |
                  | +-----+    Tier 2   +-----+ |
                  | | RR1 |-------------| RR2 | |
                  | +-----+             +-----+ |
                  +----|---\-----------/---|----+
                       |     \       /     |
                       |       \   /       |
                       |         X         |
                       |       /   \       |
                       |     /       \     |
                  +----|---/-----------\---|----+
                  |    | /   Cluster 1A  \ |    |
                  | +-----+    Tier 1   +-----+ |
                  | |RR10 |-------------|RR20 | |
                  | +-----+             +-----+ |
                  +----|---\-----------/---|----+
                       |     \       /     |
                       |       \   /       |
                       |         X         |
                       |       /   \       |
                       |     /       \     |
                  +----|---/-----------\---|----+
                  |    | /   Cluster 1B  \ |    |
                  | +-----+    Tier 1   +-----+ |
                  | |RR30 |-------------|RR40 | |
                  | +-----+ \         / +-----+ |
                  +/---|---\---\---/---/---|---\+
                 /     |     \  / \  /     |     \
               /       |     / \   / \     |       \
             /         |  /      X      \  |         \
           /           X       /   \       X           \
         /          /  |     /       \     |  \          \
       /         /     |   /           \   |     \         \
     /        /        | /               \ |        \        \
+--/-------/-----------X----+         +----X-----------\-------\--+
|+-----+/            +-----+|         |+-----+            \+-----+|
|| RR3 |-------------| RR4 ||         || RR5 |-------------| RR6 ||
|+-----+ Cluster 2B  +-----+|         |+-----+ Cluster 2C  +-----+|
|          Tier 2           |         |          Tier 2           |
+---------------------------+         +---------------------------+
]]></artwork></figure>

<t>At the lowest level, border routers remain clients of their assigned RR clusters, similar to the full mesh multi-cluster design described above. In this multi-tier model, the RRs peering with border routers are referred to as Tier 2 RRs. Instead of a full IBGP mesh between them, Tier 2 RRs are deployed as clients of Tier 1 RRs, which are themselves fully meshed.</t>

<t>While this design reduces IBGP session density on RRs and simplifies their provisioning, it may adversely affect BGP convergence time given the incremental RR hops within the IBGP control plane. Furthermore, a failure of a Tier 1 RR cluster typically results in a large blast radius.</t>

</section>
<section anchor="multi-plane"><name>Multi-Plane</name>

<t>A multi-plane, multi-cluster RR design comprises multiple independent RR planes (e.g., RED and BLUE). 
Within each plane, clusters can be fully meshed or multi-tier as described above. 
Note that while this document uses a two-plane model for illustration in Figure 4, the architecture is not limited to two planes. 
As shown in Figure 4, RRs within the RED plane (RR-R1 through RR-R6) are fully meshed as are RRs in the BLUE plane (RR-B1 through RR-B6).
In a two-plane design, RR clients (typically border routers) peer with the redundant RRs of one specific cluster in each plane, resulting in four IBGP sessions per client.</t>

<t>Multi-plane RR designs can be used in different ways, and each has a different failure behavior.
For example, if multi-plane is used for increased redundancy, each plane should carry enough routing information to maintain service if another plane fails.
In this deployment model, the failure of one plane should reduce redundancy but not remove required IP reachability.
Further, a multi-plane design used for redundancy also facilitates software or hardware upgrades.
Because the planes operate independently and provide mutual redundancy, they can be maintained or upgraded separately without disrupting IP reachability.</t>

<t>Alternatively, if planes are used for horizontal scaling, different routes or paths may be distributed across different planes.
In this deployment model, the failure of one plane may remove the routes or paths carried only by that plane.</t>

<figure title="Multi-Plane Multi-Cluster RR Design"><artwork><![CDATA[
         +---------------+                   +---------------+
         |   RED plane   |                   |   BLUE plane  |
         |   Cluster R1  |                   |   Cluster B1  |
         |+-----+ +-----+|                   |+-----+ +-----+|
         ||RR-R1|-|RR-R2||                   ||RR-B1|-|RR-B2||
         |+--+--+ +--+--+|                   |+--+--+ +--+--+|
         +---+-------+---+                   +---+-------+---+
             |       |                           |       |
         +---+-------+---+                   +---+-------+---+
         |   Full Mesh   |                   |   Full Mesh   |
         |       or      |                   |       or      |
         |   Multi-Tier  |                   |   Multi-Tier  |
    +----|     within    |----+         +----|     within    |----+
    |    |   RED plane   |    |         |    |   BLUE plane  |    |
    |    +--+---------+--+    |         |    +---+-------+---+    |
    |       |         |       |         |       |         |       |
+---+-------+---+ +---+-------+---+ +---+-------+---+ +---+-------+---+
|+--+--+ +--+--+| |+--+--+ +--+--+| |+--+--+ +--+--+| |+--+--+ +--+--+|
||RR-R3|-|RR-R4|| ||RR-R5|-|RR-R6|| ||RR-B3|-|RR-B4|| ||RR-B5|-|RR-B6||
|+-----+ +-----+| |+-----+ +-----+| |+-----+ +-----+| |+-----+ +-----+|
|   RED plane   | |   RED plane   | |  BLUE plane   | |  BLUE plane   |
|   Cluster R2  | |   Cluster R3  | |  Cluster B2   | |  Cluster B3   |
+---------------+ +---------------+ +---------------+ +---------------+
]]></artwork></figure>

</section>
</section>
<section anchor="address-family"><name>Address Family and Control Plane Segmentation</name>

<t>BGP supports multiple types of Network Layer Reachability Information (NLRI), identified by Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI) values <xref target="BGPAFI"/> <xref target="BGPSAFI"/>. An RR plane can carry multiple AFI/SAFI combinations over a common set of IBGP sessions, or different sets of AFI/SAFIs can be assigned to separate RR planes.</t>

<t>The decision to separate address families depends on their scale, update characteristics, policies, client populations, availability requirements, and implementation-specific resource constraints. Separation can reduce contention for processing and memory resources while limiting the impact of failures or abnormal update activity. Resource and node-level isolation are most effective when the address families are assigned to separate RR processes or nodes. Separate sessions terminating on the same RR process provide session-level isolation but continue to share the underlying processing and memory resources.</t>

<t>Segmentation also introduces operational costs. Each additional RR plane can require more RR instances, client sessions, loopback addresses, configuration, monitoring, and maintenance procedures. Excessive segmentation can therefore increase complexity and introduce additional failure modes. Address families with similar operational roles, policies, client populations, and availability requirements can generally share an RR plane unless scale, implementation constraints, or isolation requirements justify separation.</t>

<t>One common deployment model groups address families into Internet, VPN service, and transport control planes:</t>

<t><list style="symbols">
  <t>An Internet control plane carries global IPv4 and IPv6 reachability. This can include IPv4 unicast, IPv6 unicast, and 6PE routes when 6PE <xref target="RFC4798"/> is used to provide global IPv6 reachability.</t>
  <t>A VPN service control plane carries routes used to provide L3VPN, L2VPN, and multicast VPN services. This can include VPN-IPv4, VPN-IPv6, MVPN, EVPN, and other L2VPN routes. These address families commonly use Route Distinguishers, Route Targets, and Route Target Constraints <xref target="RFC4684"/>, and often have similar policy and operational requirements. Consequently, L3VPN, EVPN and L2VPN address families can generally share a common VPN service RR plane. Separate RR planes can be used when differences in scale, update characteristics, administrative boundaries, client populations, or fault-isolation requirements justify the additional complexity.</t>
  <t>A transport control plane carries routes used to establish or select transport connectivity. This can include BGP IPv4 labeled-unicast (BGP-LU) <xref target="RFC8277"/> and BGP Color-Aware Routing (BGP CAR) <xref target="RFC9871"/>. Because BGP-LU and BGP CAR have a common operational role and generally serve similar client populations, they can share a common transport RR plane. This avoids unnecessary RR infrastructure and IBGP sessions while allowing the associated transport address families to be operated together. Separate planes can be used when their scale, update characteristics, client populations, administrative boundaries, or isolation requirements differ significantly.</t>
</list></t>

<t>These groupings describe operational roles rather than protocol requirements. For example, 6PE can be assigned to the Internet RR plane when it provides global IPv6 reachability, even though it uses IPv6 labeled-unicast routes. Similarly, BGP-LU and BGP CAR can be assigned to the transport RR plane because their function is to distribute transport reachability.
Operators should consider the address families carried by each plane and the expected effect of a plane failure.</t>

<t>Internet and VPN address families can also use different policies and BGP mechanisms. Add-Paths (primary/backup, n-way, all) <xref target="RFC7911"/> and Optimal Route Reflection <xref target="RFC9107"/> can be used to advertise additional or more appropriate paths to RR clients. These mechanisms are not limited to Internet address families and can also be applied to VPN address families when supported and operationally appropriate. VPN address families commonly use Route Target Constraints <xref target="RFC4684"/> to limit the distribution of routes to client and non-client peers that have expressed interest in the associated Route Targets. Route Distinguishers allow otherwise identical VPN prefixes to be represented as distinct NLRI, but do not by themselves guarantee path diversity.
In addition, RRs configured for BGP-LU or BGP CAR and deployed in the MPLS forwarding plane as part of a seamless MPLS architecture <xref target="I-D.draft-ietf-mpls-seamless-mpls"/> require next-hop-self configuration and MPLS label allocation.</t>

<t>BGP Link-State (BGP-LS) <xref target="RFC9552"/> distributes link-state and traffic-engineering information to consumers such as controllers and path computation applications.
Although BGP-LS NLRI can be propagated through RRs, its purpose, update characteristics, and consumer population differ from those of Internet, VPN, and transport reachability routes. A dedicated BGP-LS RR plane can provide additional resource and operational isolation when BGP-LS carries a large volume of information, experiences substantial update activity, or serves a distinct set of consumers. In smaller deployments, BGP-LS can share infrastructure with another RR plane when the resulting scale and failure coupling are acceptable.</t>

<t>The appropriate degree of segmentation is deployment-specific. A practical model uses separate RR planes for Internet reachability, VPN services, and transport reachability, with a dedicated BGP-LS plane where its scale or consumer population warrants additional isolation. Under this model, L3VPN and L2VPN address families share the VPN service RR plane, while BGP-LU and BGP CAR share the transport RR plane. Further separation is based on measured scale, update behavior, implementation limits, administrative boundaries, or explicit isolation requirements rather than solely on AFI/SAFI distinctions. 
It is also worth noting that separating address families into Internet, VPN service, and transport control planes increases the number of RR loopback addresses carried in the link-state IGP.</t>

</section>
<section anchor="policy-and-update-group-considerations"><name>Policy and Update-Group Considerations</name>

<t><xref target="RFC4456"/> specifies the handling of path attributes when an RR reflects a route. In general, an RR does not modify the NEXT_HOP, AS_PATH, LOCAL_PREF, or MED attributes solely as a consequence of route reflection. An RR also preserves an existing ORIGINATOR_ID and prepends its local CLUSTER_ID to the CLUSTER_LIST. If no CLUSTER_LIST is present, the RR creates one containing its local CLUSTER_ID. The ORIGINATOR_ID and CLUSTER_LIST provide route-reflection loop detection and therefore require particular care.</t>

<t>Operators can apply policy at an RR when required by the network design. Examples include setting or removing communities <xref target="RFC1997"/>, controlling route distribution, changing route preference, selecting which paths are advertised, and modifying NEXT_HOP when the RR has an appropriate forwarding role. Such policies are not inherently incompatible with route reflection, but their effects can extend to many clients and can change path selection, route visibility, or forwarding behavior across a large portion of the network.</t>

<t>An operator modifying attributes that affect best path selection should evaluate the policy across the complete reflection topology rather than only on an individual session. Inconsistent policies among redundant RRs can cause clients to receive different paths and can complicate convergence and troubleshooting. Policies should therefore be deterministic, under both normal and failure conditions, and applied consistently across redundant RRs unless intentional differences are part of the design.</t>

<t>An RR should not remove or rewrite ORIGINATOR_ID or CLUSTER_LIST information in a way that defeats the loop-detection procedures defined by <xref target="RFC4456"/>. Policies affecting AS_PATH or other attributes used for loop prevention also require careful validation. When an RR must modify NEXT_HOP because it participates in the forwarding plane, operators should follow the procedures and deployment considerations in <xref target="I-D.draft-ietf-idr-bgp-fwd-rr"/>. Inter-AS Option C, described in Section 10 of <xref target="RFC4364"/>, is one example of a design in which an RR can have both route-reflection and forwarding responsibilities.</t>

<t>Policy design also affects RR scale. BGP implementations commonly group peers that have equivalent outbound advertisements so that an update can be generated once and replicated to multiple peers. These groups are often referred to as update-groups, although their exact behavior is implementation-specific. Per-peer policies, different advertised capabilities, and other session-specific behavior can divide clients into additional update-groups. This can increase update generation, memory consumption, CPU utilization, and convergence time.</t>

<t>Operators should therefore use common outbound policies across clients where operational requirements permit. Policy variation should normally be applied at the largest practical grouping, such as by service, region, role, or client class, rather than through unique policy for each peer. Where per-client policy is required, operators should account for its effect on update-group formation and RR capacity.</t>

<t>Inbound and outbound filtering can provide important operational benefits and should not be avoided solely to reduce processing overhead. For example, filtering can enforce route-distribution boundaries, prevent unintended route propagation, attach policy metadata, and protect the network from invalid or excessive advertisements. The objective is to avoid unnecessary policy complexity while retaining controls required for routing correctness, security, and service operation.</t>

<t>Centralized policy is an important benefit of an RR architecture because it allows operators to influence route distribution and path selection from a limited number of locations. This benefit should be balanced against the size of the policy configuration, the number of resulting update-groups, the expected update rate, and the convergence objectives of the deployment. Operators should validate this balance through implementation-specific scale testing and monitor update-group counts, policy-processing load, queue depth, memory utilization, and update-generation time where those measurements are available.</t>

</section>
<section anchor="slow-peer-considerations"><name>Slow Peer Considerations</name>

<t>It is common for RRs to dynamically establish BGP update-groups across IBGP peers that share identical outbound routing policies <xref target="RFC7938"/>, including instances where no outbound policies are applied. 
This improves RR performance, as an RR formats a single update advertised to all peers within an update-group rather than advertising unique updates for each individual peer. 
This also enhances overall BGP control plane performance.</t>

<t>However, a slow peer within an update-group that cannot keep up with the rate at which an RR generates BGP update messages can adversely affect other members of the group. A single slow client can force a RR to throttle, delaying updates to other peers in the same group. This degrades BGP convergence and may increase traffic disruption during BGP convergence events.</t>

<t>It is suggested to isolate known slow clients, such as legacy routers with limited CPU and memory resources, into their own IBGP update-group. 
This isolation can be performed manually via static configuration or, if supported by the RR software, dynamically. 
Dynamic isolation involves the RR automatically detecting and moving slow peers out of an update-group so as not to adversely impact other members. 
This dynamic behavior can also return previous slow peers back into an update-group after their BGP processing is caught up. 
However, for permanently known slow peers it is suggested to statically assign them to dedicated update-groups. 
This approach helps to prevent any adverse impact on other peers and minimizes the RR churn associated with the automatic detection, isolation, and reintegration of slow peers.</t>

<t>The procedure to identify slow peers - a process that can be automated - involves monitoring the BGP table version and BGP output queue 
of the peers in each update-group. This information should then be used to 
verify whether the BGP table version of the peers ever catches up with the main BGP table version or whether it is always behind.
Similarly, check whether any peers have a very high output queue value for a long duration. If so, it is likely that these are slow peers and should be isolated.</t>

</section>
<section anchor="path-selection"><name>Path Selection Considerations</name>

<t>By default, a BGP speaker selects a single best path for each destination and advertises only that path to a peer, subject to policy. When acting as an RR, the speaker generally performs this selection from its own perspective. Paths not selected by the RR are hidden from its clients unless another mechanism causes those paths to be advertised.</t>

<t>Path hiding can occur when the path selected by an RR differs from the path that a client would have selected had the client received all available paths. This is particularly relevant when the IGP metric to the BGP next hop is considered during best path selection, because the RR ordinarily evaluates that metric from its own location rather than from the location of each client. Depending on the topology and routing policies, path hiding can result in suboptimal routing, reduce the paths available during a failure, and contribute to the route oscillations described in <xref target="RFC3345"/>.</t>

<t>Several mechanisms can reduce path hiding. The appropriate mechanism depends on the address family, the required number of paths, the topology, and the scaling characteristics of the deployment.</t>

<section anchor="route-distinguisher-assignment"><name>Route Distinguisher Assignment</name>

<t>In BGP L3VPN deployments <xref target="RFC4364"/>, operators commonly assign distinct Route Distinguishers (RDs) to routes originated by different PEs (Provider Edge routers). EVPN deployments similarly use RDs to distinguish otherwise identical EVPN NLRI originated from different PEs or EVPN instances. Because the RD is part of the NLRI, routes with different RDs are treated as distinct destinations by BGP and are subject to separate best path decisions.</t>

<t>Using distinct RDs can preserve multiple VPN or EVPN routes through the RR system without requiring Add-Paths for those distinct NLRI. After import, a receiving PE can evaluate the eligible routes for the corresponding service destination. This can improve route visibility and preserve useful path diversity.</t>

<t>A unique RD does not, by itself, guarantee forwarding-path diversity, optimal routing, or load balancing. The resulting behavior also depends on route import policy, NEXT_HOP reachability, path attributes, the client’s best path and multi-path procedures, and the underlying topology. Operators should therefore assign RDs according to the service design and the path diversity that needs to be preserved.</t>

<t>RD-based path preservation does not apply to routes in the global routing table carried using IPv4 unicast, IPv6 unicast, or 6PE, because those routes do not use an RD as part of their NLRI.</t>

</section>
<section anchor="add-paths"><name>Add-Paths</name>

<t>Historically, some networks used policy to cause redundant RRs to select and advertise different paths. A client connected to multiple RRs could consequently receive more than one candidate path. This approach depends on deliberate policy differences between RRs and can increase operational complexity.</t>

<t>BGP Add-Paths <xref target="RFC7911"/> provides a protocol mechanism for advertising multiple paths for the same NLRI over a BGP session. Depending on the path-selection and advertisement mode implemented and configured, an RR can advertise a best path and one or more additional paths, such as backup, diverse, n-way, or all eligible paths. This reduces the need to rely exclusively on policy differences between redundant RRs to expose multiple paths.</t>

<t>When an RR advertises suitable candidate paths, a client can perform best path selection from its own perspective, including the use of its own IGP metrics where applicable. The benefit depends on which paths the RR selects for advertisement. For example, advertising only the RR’s best path and a backup path does not necessarily expose the path that is best from every client’s location.</t>

<t>Add-Paths can improve path visibility, convergence, and resilience, and can be used as part of a solution for the route oscillation conditions discussed in <xref target="RFC3345"/> and <xref target="RFC7964"/>. Its use does not, however, guarantee optimal routing or eliminate every form of path hiding or route oscillation.</t>

<t>Add-Paths can also increase the number of paths retained, processed, and advertised by BGP speakers. This can increase memory consumption, update generation, policy processing, and convergence workload on both RRs and clients.
Operators should select an advertisement mode that provides the required path diversity without distributing unnecessary paths, then validate its impact against the deployment’s scale and convergence objectives.</t>

</section>
<section anchor="optimal-route-reflection"><name>Optimal Route Reflection</name>

<t>Optimal Route Reflection (ORR) <xref target="RFC9107"/> addresses cases in which the path selected from the RR’s location is not the path that would be preferred from a client’s location. ORR allows an RR to select and advertise a path using an IGP perspective associated with a root client or group of clients rather than the RR’s own IGP location.</t>

<t>ORR can reduce IGP metric-based path hiding and allows RRs to be placed independently of the clients for which they select paths. It does not necessarily produce a globally optimal forwarding path, because selection remains subject to the paths available to the RR, the configured ORR perspective, BGP policy, path attributes, and implementation behavior.</t>

<t>ORR and Add-Paths are complementary. ORR selects a path based on the root client’s or client group’s location, rather than the RR’s location. In contrast, Add-Paths advertises multiple candidate paths, allowing the client to perform its own selection. A deployment can use either mechanism or both, depending on its path selection and scaling requirements.</t>

<t>ORR requires sufficient IGP topology information to compute path metrics from the perspective of root clients or client groups.
An RR can obtain this information by participating in the relevant IGP or by using BGP-LS <xref target="RFC9552"/>.</t>

<t>Maintaining multiple ORR perspectives and performing path selection for different root clients or client groups increases RR processing and state.
Operators should minimize the number of distinct ORR perspectives by grouping clients with equivalent topologies, then evaluate the resulting impact on CPU, memory, and convergence.</t>

</section>
<section anchor="protocol-nexthop-resolution"><name>Protocol NEXT_HOP Resolution</name>

<t>The need for Protocol NEXT_HOP (PNH) resolution depends on the AFI/SAFI and the paths being processed. For address families carrying reachability information, an RR needs to determine whether a BGP NEXT_HOP is resolvable and, when applicable, obtain the IGP metric to be used during best path selection. The exact PNH behavior depends on the specific address family.</t>

<t>Some address families do not use the PNH in the same manner as unicast reachability routes. For example, BGP-LS <xref target="RFC9552"/> distributes topology information rather than forwarding reachability, and Route Target Constraint routes <xref target="RFC4684"/> control VPN route distribution. FlowSpec NLRI <xref target="RFC8955"/> describes traffic-matching and action rules rather than conventional destination reachability. However, FlowSpec validation and route acceptance can still depend on information from the unicast routing system.</t>

<t>Implementations can provide mechanisms to avoid or reduce PNH resolution for address families or routes for which it is not required.
Where supported, operators can leverage these mechanisms to reduce processing overhead, provided they first verify the protocol procedures, validation rules, policy dependencies, and implementation details for the target AFI/SAFI.</t>

</section>
<section anchor="deployment-guidance"><name>Deployment Guidance</name>

<t>No single path selection mechanism is appropriate for every address family or deployment. Operators should consider:</t>

<t><list style="symbols">
  <t>Distinct RDs where multiple VPN or EVPN routes need to remain distinct NLRI.</t>
  <t>Add-Paths where clients benefit from receiving multiple candidate paths.</t>
  <t>ORR when path advertisement must be constrained and path selection must align with client-specific or client-group topological proximity, rather than the RR’s local perspective.</t>
  <t>Multiple of the above mechanisms where their benefits are complementary.</t>
</list></t>

<t>The selection should account for route scale, required path diversity, convergence objectives, RR and client capacity, topology, and operational complexity. Operators should also consider failure scenarios, as a mechanism that provides optimal paths during steady state may fail to offer sufficient alternatives during convergence.</t>

</section>
</section>
<section anchor="route-target-constraint-considerations"><name>Route Target Constraint Considerations</name>

<t>BGP Route Target Constraint (RTC) <xref target="RFC4684"/> can significantly reduce the volume of VPN updates an RR advertises to edge routers (PEs). 
With RTC, it is suggested that RRs advertise an RT-filter default to clients, while clients send specific RT-filters to the RR, rather than the reverse. 
This is particularly important in multi-tier RR designs: upper-tier RRs should advertise an RT-filter default to lower-tier RRs, while lower-tier RRs send specific RT-filters to the upper-tier RRs.
Failure to do so may cause clients and lower-tier RRs to receive all VPN routes, potentially exceeding their scale capacity.</t>

<t>Further, RTC is most effective when activated end-to-end to build precise outbound route filters, including those for single-domain and multi-domain network-based VPNs. 
This also includes multi-tier, multi-cluster RR designs so that Tier 1 RRs only send the required VPN prefixes to Tier 2 RRs, drastically reducing BGP VPN processing and overhead. 
Operators should also be aware of known issues associated with RTC in specific scenarios. 
These are documented in <xref target="I-D.draft-ietf-idr-rtc-hierarchical-rr"/> and <xref target="I-D.draft-ietf-idr-rtc-interas"/>, both of which also propose solutions.</t>

<section anchor="evpn-route-target-considerations"><name>EVPN Route Target Considerations</name>

<t>To optimize NLRI distribution via RR design, special attention is suggested for EVPN. <xref target="RFC7432"/> in Section 7.6 defines the ES-Import Route Target (ES-Import-RT) extended community. The ES-Import-RT, together with RTC, enables optimized route distribution of Ethernet Segment (ES) routes. Namely, from an EVPN architectural point of view, it is sufficient that only PEs connected to the same multi-homed ES receive the ES route specific to a given multi-homed ES. All other PEs — those not connected to a given multi-homed ES — do not require visibility of that specific ES route.</t>

<t>To achieve the desired behavior, the value of the ES-Import-RT extended community is derived automatically from the Ethernet Segment Identifier (ESI) by encoding the high-order 6-octet portion of the 9-octet ESI value. For example, as illustrated in Figure 5, the octets depicted as 'XX' are used as the value of the ES-Import-RT.</t>

<figure title="ESI Type 0 Example"><artwork><![CDATA[
                 ESI = 00:XX:XX:XX:XX:XX:XX:YY:YY:YY 
]]></artwork></figure>

<t>When RTC is enabled, the RT-filter advertised by a PE (which is an RR client) is also automatically updated to signal interest to the RR in receiving NLRIs (here, ES routes) with a specific ES-Import-RT (here, with the value XX:XX:XX:XX:XX:XX). In large-scale deployments with a large number of multi-homed Ethernet segments, this can significantly reduce the number of ES routes that are sent to RR clients.</t>

<t>In order, however, to take advantage of this optimized distribution of ES routes, ESI values must be assigned in such a way that they are differentiated in the high-order 6-octet portion of the 9-octet ESI value. While this happens automatically for ESI types 1, 2, and 3, care must be taken with ESI type 0 (manual allocation). Figure 6 depicts an ESI type 0 value allocation scheme that does not result in an optimized distribution of ES routes through RRs.</t>

<figure title="ESI Type 0 allocation scheme (Option 1)"><artwork><![CDATA[
                 ESI-1 = 00:00:00:00:00:00:00:00:00:01 
                 ESI-2 = 00:00:00:00:00:00:00:00:00:02 
                 ESI-3 = 00:00:00:00:00:00:00:00:00:03
                 ...
                 ESI-65535 = 00:00:00:00:00:00:00:00:ff:ff
]]></artwork></figure>

<t>In this ESI Type 0 value allocation scheme, the high-order 6-octet portion of the 9-octet ESI value is the same for all ESIs (00:00:00:00:00:00). Therefore, all PEs (all RR clients) update the RT-filters they advertise to the RR with an RT equal to 00:00:00:00:00:00, resulting in all PEs (RR clients) receiving ES routes for all Ethernet segments.</t>

<t>Figure 7 depicts a different allocation scheme for ESI Type 0 values. In this allocation scheme, the values are differentiated in the high-order 6-octet portion of the 9-octet ESI value.</t>

<figure title="ESI Type 0 allocation scheme (Option 2)"><artwork><![CDATA[
                 ESI-1 = 00:00:00:00:00:00:01:00:00:00 
                 ESI-2 = 00:00:00:00:00:00:02:00:00:00 
                 ESI-3 = 00:00:00:00:00:00:03:00:00:00
                 ...
                 ESI-65535 = 00:00:00:00:00:ff:ff:00:00:00
]]></artwork></figure>

<t>Such an allocation scheme results in different ES-Import-RTs (and, as a consequence, different RT-filters) for each group of PEs connected to different Ethernet segments. Therefore, the ES route pertaining to ESI-1, based on the RT-filters received by the RR from PEs connected to the multi-homed Ethernet segment with ESI-1, is sent by the RR only to PEs (RR clients) connected to that particular Ethernet segment.
It is suggested that operators consider adopting this allocation scheme to optimize ES route distribution, thereby reducing both the volume of routes propagated to RR clients and the associated control plane overhead.</t>

</section>
</section>
<section anchor="transport-optimizations"><name>Transport Optimizations</name>

<section anchor="tcp-path-mtu-discovery"><name>TCP Path MTU Discovery</name>

<t>To improve BGP control plane performance, it is suggested to enable TCP Path MTU Discovery (PMTUD) <xref target="RFC1191"/> on both RRs and clients; this allows TCP to select an appropriate Maximum Segment Size (MSS) for each BGP session.
In this way, BGP sessions use the largest packet size that does not require IP fragmentation anywhere along the path to client and non-client IBGP peers.</t>

</section>
<section anchor="ethernet-mtu"><name>Ethernet MTU</name>

<t>The Ethernet maximum transmission unit (MTU) is the size of the largest frame, minus the 4-byte frame check sequence (FCS), that can be transmitted on a Ethernet network.
Every physical network along the path to the destination of a packet can have a different MTU.
The default Ethernet MTU (Maxiumum Transmission Unit) value is 1514 bytes for standard Ethernet frames and 1518 bytes for 802.1Q tagged frames.
These numbers exclude the 4-byte frame check sequence (FCS).</t>

<t>When the MTU size is larger, more data can be sent in fewer number of packets.
As each packet contains a header, a small number of packets means less header data to be transmitted.
Thus, a larger size MTU helps in transmitting more actual data faster and efficiently.</t>

<t>To ensure the RR is not the limiting factor related to PMTUD and BGP update packet sizes, it is suggested to enable Jumbo frame support on RR interfaces with the largest packet size value available.</t>

</section>
</section>
<section anchor="miscellaneous-considerations"><name>Miscellaneous Considerations</name>

<section anchor="bgp-router-id"><name>BGP Router ID</name>

<t>To prevent IBGP session instability caused by changes in the BGP router ID when a physical interface's state changes, it is suggested to statically configure the BGP router ID using the IP address of a virtual loopback interface. This approach is preferred because loopback interfaces are more stable than physical interfaces, which may go down or change state, causing the router ID to change and potentially leading to BGP session resets. This IBGP best practice applies to both RRs and clients.</t>

</section>
<section anchor="bgp-ribfib-filtering"><name>BGP RIB/FIB Filtering</name>

<t>For RRs operating exclusively in the control plane, configuring RIB/FIB filtering policies to suppress BGP route installation is suggested. Restricting these tables on non-forwarding devices:</t>

<t><list style="symbols">
  <t>Minimizes RIB and FIB resource consumption.</t>
  <t>Eliminates unnecessary RIB and FIB processing overhead.</t>
  <t>Improves an RR's overall efficiency and scalability.</t>
</list></t>

</section>
<section anchor="bgp-errors"><name>BGP Error Handling</name>

<t><xref target="RFC7606"/> specified critical updates to BGP error handling procedures. It is suggested to ensure these procedures are enabled on RRs (and all other BGP speakers) if they are not already active by default.</t>

</section>
<section anchor="diffserv-qos"><name>Diffserv QoS</name>

<t>Because BGP control plane stability is fundamental to overall network stability, it is suggested that BGP packets be prioritized using Diffserv QoS <xref target="RFC2475"/> policies. 
This approach helps to prevent BGP packet loss and minimize queuing delays during congestion events, thereby ensuring session stability and avoiding the traffic disruption that occurs if BGP sessions fail.</t>

</section>
<section anchor="bgp-rr-form-factors"><name>BGP RR Form Factors</name>

<t>Traditionally, RRs were deployed using physical routing devices. 
With the advent of Network Function Virtualization (NFV), RRs that operate exclusively in the control plane (i.e., control-plane-only)
are increasingly deployed as Virtual Network Functions (VNFs) or virtual RRs.</t>

<t>Virtual RRs rely on independent compute, hypervisor, storage and virtual networking infrastructure, though vendors offer integrated appliances that bundle these components. 
Virtualization offers operational flexibility, enabling operators to optimize virtual RR resources according to actual BGP control plane demand.
The actual performance of a virtual RR, however, remains heavily dependent on the specific implementation and the underlying compute resources.
When integrated virtual RR appliances are used, they can often surpass physical RRs in scalability and convergence by 
providing superior CPU performance, memory speed and quantity available for BGP control plane processing.
In contrast, RRs that participate in the IP forwarding plane are typically deployed as physical RRs, unless a virtual RR implementation can satisfy the required forwarding capacity.</t>

<t>If a virtual implementation is not feasible for operational, administrative or other reasons, a physical RR remains a viable alternative.
In such cases, operators must account for potential differences in control plane scale and performance when transitioning between deployment models.</t>

</section>
<section anchor="bgp-non-stop-routingforwarding"><name>BGP Non-Stop Routing/Forwarding</name>

<t>A virtual RR is deployed on a compute server which has no concept of redundant route processors.
A physical RR can be configured with redundant route processors and leverage this redundancy to enable BGP Non-Stop Routing (NSR).
NSR preserves BGP session and control plane state during a route processor failover, ensuring that IBGP clients and non-client peers do not detect the switchover and eliminating the need for session resets, BGP Graceful Restart, or its helper mode.</t>

<t>While physical RRs with redundant route processors uniquely support NSR, they generally offer significantly lower BGP scaling compared to virtual RRs as described earlier.
Consequently, deploying multiple redundant virtual RRs is suggested for networks with high BGP control plane scale.</t>

</section>
<section anchor="stale-routes"><name>BGP Graceful Restart</name>

<t>BGP Graceful Restart (GR), specified in <xref target="RFC4724"/> and <xref target="RFC8538"/>, allows a 
"Receiving Speaker" (sometimes refered to as Helper Router per <xref target="RFC9494"/>) 
to temporarily retain routes learned from a "Restarting Speaker".
It can reduce BGP routing churn and traffic disruption when the forwarding represented by those BGP routes remains usable.
Conversely, it can delay BGP convergence and result in traffic disruption, as stale routes can persist while the NEXT_HOP remains reachable.</t>

<t>Note, GR signals that forwarding state is maintained during a BGP restart; it doesn't maintain it.
Non-Stop Forwarding (NSF) is the local mechanism that maintains it.</t>

<t>Operators should evaluate GR roles separately.
The "Restarting Speaker" role is suggested for BGP speakers that meet the following criteria:</t>

<t><list style="symbols">
  <t>Active participation in the traffic forwarding plane.</t>
  <t>Lack support for Non-Stop Routing (NSR).</t>
  <t>Able to maintain forwarding state during BGP restart using NSF.</t>
  <t>Serve as a transit node for traffic that lacks path redundancy.</t>
</list></t>

<t>A BGP speaker configured for the Restarting Speaker mode also functions in Helper mode. 
This dual capability allows the router to act as a Restarting Speaker during a local BGP process failure
while serving as a Helper when a GR-capable peer restarts. 
Alternatively, a BGP speaker unable to maintain its forwarding state during a local BGP restart can advertise
the GR capability without &lt;AFI, SAFI&gt; pairs (<xref target="RFC4724"/>, Section 3) to serve exclusively as a Helper. 
The Helper role is suggested for all peers of a Restarting Speaker.
These suggestions are informed by the considerations included below.
Further, optimal timers for BGP GR are deployment-specific and, therefore, outside the scope of this document.</t>

<section anchor="control-plane-only-rrs"><name>Control-plane-only RRs</name>

<t>When BGP restarts on an RR operating in Restarting Speaker mode, clients and non-client peers acting as helpers can retain 
its reflected routes while the actual forwarding next hops remain operational. 
This can avoid unnecessary BGP best path reselection and forwarding changes on clients and non-client peers.</t>

<t>However, the deloyment of redundant RRs reduce the benefit of Restarting Speaker mode given clients and non-client 
peers already have equivalent usable routes.
Further, on clients and non-client peers acting as helpers a subsequent route withdrawal received through 
another RR does not remove the retained stale path from the restarting RR.
Conventional GR does not make stale routes less preferred either per <xref target="RFC9494"/>, Section 1.
Consequently, as stated above, Restarting Speaker mode on control-plane-only RRs may delay BGP convergence and 
result in traffic disruption, as stale routes can persist while the NEXT_HOP remains reachable.
For these reasons, Helper mode is suggested for control-plane-only RRs.</t>

</section>
<section anchor="forwarding-plane-rrs"><name>Forwarding-plane RRs</name>

<t>When an RR is deployed within the traffic forwarding plane, its BGP restart can affect both route distribution and traffic forwarding. 
For this reason, Restarting Speaker mode is suggested for forwarding-plane RRs that satisfy the criteria listed above in <xref target="stale-routes"/>.</t>

</section>
<section anchor="rr-clients-and-non-client-peers"><name>RR Clients and Non-client Peers</name>

<t>Similar to forwarding-plane RRs, Restarting Speaker mode is suggested for RR clients and non-client peers that satisfy the criteria listed above in <xref target="stale-routes"/>.</t>

</section>
</section>
<section anchor="multi-hop-bfd-for-ibgp"><name>Multi-hop BFD for IBGP</name>

<t>Multi-hop BFD <xref target="RFC5883"/> is not suggested for IBGP sessions between control-plane-only RRs and their clients. 
Deploying BFD in this context exposes the BGP control plane to unnecessary instability, as it may trigger session resets due to minor, transient connectivity issues that TCP would otherwise handle gracefully.
A multi-hop BFD-triggered reset on a session carrying millions of routes, for example, creates significant churn, even when the underlying network topology remains stable. 
Furthermore, using multi-hop BFD to accelerate failure detection within the BGP control plane is counterproductive; since clients typically receive redundant path information from multiple RRs, the loss of a single RR session does not impact the client's traffic forwarding plane.</t>

</section>
</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t>This document introduces no new security considerations to the BGP protocol itself. It describes deployment considerations and best practices that BGP network operators should consider when deploying RRs to maximize BGP control plane performance, scalability and stability.
While general BGP operational security guidance is provided in <xref target="RFC7454"/>, several RR considerations with security relevance are described below.
These also adhere to the revised BGP operations and security specifications of <xref target="I-D.draft-ietf-grow-bgpopsecupd"/>.</t>

<section anchor="bgp-session-authentication"><name>BGP Session Authentication</name>

<t>BGP session cryptographic authentication is suggested to ensure that BGP updates are only accepted from trusted, verified peers, which helps to reduce the risk of unauthorized route injection and session hijacking.
MD5 is the legacy method for BGP authentication, as it has been deprecated for some time now, given it is considered cryptographically weak by modern standards.
TCP-AO <xref target="RFC5925"/> is the modern standard and suggested method for BGP session security as it provides stronger cryptographic algorithms and improved security features.</t>

</section>
<section anchor="bgp-session-prefix-limits"><name>BGP Session Prefix Limits</name>

<t>Configuring BGP session prefix limits is an important measure to protect a network from an EBGP peer unexpectedly advertising an excessive number of routes, such as the full Internet routing table.
BGP session prefix limits enforce a maximum receive prefix count from a neighbor for each address-family, helping safeguard a network from out-of-resource (OOR) conditions which could lead to traffic disruption.</t>

<t>In the event a session prefix limit is hit, BGP implementations typically provide several actions in response:</t>

<t><list style="symbols">
  <t>Bring down session</t>
  <t>Restart session</t>
  <t>Discard extra paths</t>
  <t>SYSLOG warning</t>
</list></t>

<t>Beyond generating a SYSLOG warning, it is suggested to implement one of the listed actions for EBGP sessions based on your specific network requirements. 
BGP session prefix limits can be configured on IBGP sessions as well; however, if configured for IBGP, it is suggested to use only a SYSLOG warning without taking further action. 
This approach helps monitor prefix counts while avoiding IBGP session resets or disruptions, which could result in a more significant detrimental impact.</t>

</section>
<section anchor="control-plane-protection"><name>Control Plane Protection</name>

<t>It is common for modern IP routers to support control plane protection <xref target="RFC6192"/>, including but not limited to control plane policing.
Typically enabled by default on modern IP routers, this capability helps protect a router from excessive control plane traffic by classifying and policing different packet types, thereby preventing potential denial-of-service conditions.
With regard to RRs, it is important for large-scale deployments to ensure that BGP control plane policer rates are optimally configured to prevent BGP packet drops, which could adversely affect both BGP stability and overall network stability.</t>

</section>
</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>This document has no IANA actions.</t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC4271">
  <front>
    <title>A Border Gateway Protocol 4 (BGP-4)</title>
    <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/>
    <author fullname="T. Li" initials="T." role="editor" surname="Li"/>
    <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
    <date month="January" year="2006"/>
    <abstract>
      <t>This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol.</t>
      <t>The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced.</t>
      <t>BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.</t>
      <t>This document obsoletes RFC 1771. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4271"/>
  <seriesInfo name="DOI" value="10.17487/RFC4271"/>
</reference>
<reference anchor="RFC4456">
  <front>
    <title>BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)</title>
    <author fullname="T. Bates" initials="T." surname="Bates"/>
    <author fullname="E. Chen" initials="E." surname="Chen"/>
    <author fullname="R. Chandra" initials="R." surname="Chandra"/>
    <date month="April" year="2006"/>
    <abstract>
      <t>The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed.</t>
      <t>This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP).</t>
      <t>This document obsoletes RFC 2796 and RFC 1966. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4456"/>
  <seriesInfo name="DOI" value="10.17487/RFC4456"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">



<reference anchor="RFC1191">
  <front>
    <title>Path MTU discovery</title>
    <author fullname="J. Mogul" initials="J." surname="Mogul"/>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <date month="November" year="1990"/>
    <abstract>
      <t>This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="1191"/>
  <seriesInfo name="DOI" value="10.17487/RFC1191"/>
</reference>
<reference anchor="RFC1997">
  <front>
    <title>BGP Communities Attribute</title>
    <author fullname="R. Chandra" initials="R." surname="Chandra"/>
    <author fullname="P. Traina" initials="P." surname="Traina"/>
    <author fullname="T. Li" initials="T." surname="Li"/>
    <date month="August" year="1996"/>
    <abstract>
      <t>This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="1997"/>
  <seriesInfo name="DOI" value="10.17487/RFC1997"/>
</reference>
<reference anchor="RFC2475">
  <front>
    <title>An Architecture for Differentiated Services</title>
    <author fullname="S. Blake" initials="S." surname="Blake"/>
    <author fullname="D. Black" initials="D." surname="Black"/>
    <author fullname="M. Carlson" initials="M." surname="Carlson"/>
    <author fullname="E. Davies" initials="E." surname="Davies"/>
    <author fullname="Z. Wang" initials="Z." surname="Wang"/>
    <author fullname="W. Weiss" initials="W." surname="Weiss"/>
    <date month="December" year="1998"/>
    <abstract>
      <t>This document defines an architecture for implementing scalable service differentiation in the Internet. This memo provides information for the Internet community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2475"/>
  <seriesInfo name="DOI" value="10.17487/RFC2475"/>
</reference>
<reference anchor="RFC2018">
  <front>
    <title>TCP Selective Acknowledgment Options</title>
    <author fullname="M. Mathis" initials="M." surname="Mathis"/>
    <author fullname="J. Mahdavi" initials="J." surname="Mahdavi"/>
    <author fullname="S. Floyd" initials="S." surname="Floyd"/>
    <author fullname="A. Romanow" initials="A." surname="Romanow"/>
    <date month="October" year="1996"/>
    <abstract>
      <t>This memo proposes an implementation of SACK and discusses its performance and related issues. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2018"/>
  <seriesInfo name="DOI" value="10.17487/RFC2018"/>
</reference>

<reference anchor="RFC3345" target="https://www.rfc-editor.org/info/rfc3345">
  <front>
    <title>Border Gateway Protocol (BGP) Persistent Route Oscillation Condition</title>
    <author initials="D." surname="McPherson" fullname="D. McPherson">
      <organization></organization>
    </author>
    <author initials="V." surname="Gill" fullname="V. Gill">
      <organization></organization>
    </author>
    <author initials="D." surname="Walton" fullname="D. Walton">
      <organization></organization>
    </author>
    <author initials="A." surname="Retana" fullname="A. Retana">
      <organization></organization>
    </author>
    <date year="2002" month="August"/>
  </front>
  <seriesInfo name="RFC" value="3345"/>
  <seriesInfo name="DOI" value="10.17487/RFC3345"/>
</reference>


<reference anchor="RFC4364">
  <front>
    <title>BGP/MPLS IP Virtual Private Networks (VPNs)</title>
    <author fullname="E. Rosen" initials="E." surname="Rosen"/>
    <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
    <date month="February" year="2006"/>
    <abstract>
      <t>This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4364"/>
  <seriesInfo name="DOI" value="10.17487/RFC4364"/>
</reference>
<reference anchor="RFC4684">
  <front>
    <title>Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)</title>
    <author fullname="P. Marques" initials="P." surname="Marques"/>
    <author fullname="R. Bonica" initials="R." surname="Bonica"/>
    <author fullname="L. Fang" initials="L." surname="Fang"/>
    <author fullname="L. Martini" initials="L." surname="Martini"/>
    <author fullname="R. Raszuk" initials="R." surname="Raszuk"/>
    <author fullname="K. Patel" initials="K." surname="Patel"/>
    <author fullname="J. Guichard" initials="J." surname="Guichard"/>
    <date month="November" year="2006"/>
    <abstract>
      <t>This document defines Multi-Protocol BGP (MP-BGP) procedures that allow BGP speakers to exchange Route Target reachability information. This information can be used to build a route distribution graph in order to limit the propagation of Virtual Private Network (VPN) Network Layer Reachability Information (NLRI) between different autonomous systems or distinct clusters of the same autonomous system. This document updates RFC 4364. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4684"/>
  <seriesInfo name="DOI" value="10.17487/RFC4684"/>
</reference>
<reference anchor="RFC4724">
  <front>
    <title>Graceful Restart Mechanism for BGP</title>
    <author fullname="S. Sangli" initials="S." surname="Sangli"/>
    <author fullname="E. Chen" initials="E." surname="Chen"/>
    <author fullname="R. Fernando" initials="R." surname="Fernando"/>
    <author fullname="J. Scudder" initials="J." surname="Scudder"/>
    <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
    <date month="January" year="2007"/>
    <abstract>
      <t>This document describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined that would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finally, procedures are outlined for temporarily retaining routing information across a TCP session termination/re-establishment.</t>
      <t>The mechanisms described in this document are applicable to all routers, both those with the ability to preserve forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanisms described in this document). [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4724"/>
  <seriesInfo name="DOI" value="10.17487/RFC4724"/>
</reference>
<reference anchor="RFC4798">
  <front>
    <title>Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)</title>
    <author fullname="J. De Clercq" initials="J." surname="De Clercq"/>
    <author fullname="D. Ooms" initials="D." surname="Ooms"/>
    <author fullname="S. Prevost" initials="S." surname="Prevost"/>
    <author fullname="F. Le Faucheur" initials="F." surname="Le Faucheur"/>
    <date month="February" year="2007"/>
    <abstract>
      <t>This document explains how to interconnect IPv6 islands over a Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This approach relies on IPv6 Provider Edge routers (6PE), which are Dual Stack in order to connect to IPv6 islands and to the MPLS core, which is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6 reachability information transparently over the core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing so, the BGP Next Hop field is used to convey the IPv4 address of the 6PE router so that dynamically established IPv4-signaled MPLS Label Switched Paths (LSPs) can be used without explicit tunnel configuration. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="4798"/>
  <seriesInfo name="DOI" value="10.17487/RFC4798"/>
</reference>
<reference anchor="RFC5883">
  <front>
    <title>Bidirectional Forwarding Detection (BFD) for Multihop Paths</title>
    <author fullname="D. Katz" initials="D." surname="Katz"/>
    <author fullname="D. Ward" initials="D." surname="Ward"/>
    <date month="June" year="2010"/>
    <abstract>
      <t>This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over multihop paths, including unidirectional links. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5883"/>
  <seriesInfo name="DOI" value="10.17487/RFC5883"/>
</reference>
<reference anchor="RFC5925">
  <front>
    <title>The TCP Authentication Option</title>
    <author fullname="J. Touch" initials="J." surname="Touch"/>
    <author fullname="A. Mankin" initials="A." surname="Mankin"/>
    <author fullname="R. Bonica" initials="R." surname="Bonica"/>
    <date month="June" year="2010"/>
    <abstract>
      <t>This document specifies the TCP Authentication Option (TCP-AO), which obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO specifies the use of stronger Message Authentication Codes (MACs), protects against replays even for long-lived TCP connections, and provides more details on the association of security with TCP connections than TCP MD5. TCP-AO is compatible with either a static Master Key Tuple (MKT) configuration or an external, out-of-band MKT management mechanism; in either case, TCP-AO also protects connections when using the same MKT across repeated instances of a connection, using traffic keys derived from the MKT, and coordinates MKT changes between endpoints. The result is intended to support current infrastructure uses of TCP MD5, such as to protect long-lived connections (as used, e.g., in BGP and LDP), and to support a larger set of MACs with minimal other system and operational changes. TCP-AO uses a different option identifier than TCP MD5, even though TCP-AO and TCP MD5 are never permitted to be used simultaneously. TCP-AO supports IPv6, and is fully compatible with the proposed requirements for the replacement of TCP MD5. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5925"/>
  <seriesInfo name="DOI" value="10.17487/RFC5925"/>
</reference>
<reference anchor="RFC6192">
  <front>
    <title>Protecting the Router Control Plane</title>
    <author fullname="D. Dugal" initials="D." surname="Dugal"/>
    <author fullname="C. Pignataro" initials="C." surname="Pignataro"/>
    <author fullname="R. Dunn" initials="R." surname="Dunn"/>
    <date month="March" year="2011"/>
    <abstract>
      <t>This memo provides a method for protecting a router's control plane from undesired or malicious traffic. In this approach, all legitimate router control plane traffic is identified. Once legitimate traffic has been identified, a filter is deployed in the router's forwarding plane. That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane, or rate-limits such traffic to an acceptable level.</t>
      <t>Note that the filters described in this memo are applied only to traffic that is destined for the router, and not to all traffic that is passing through the router. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6192"/>
  <seriesInfo name="DOI" value="10.17487/RFC6192"/>
</reference>
<reference anchor="RFC7432">
  <front>
    <title>BGP MPLS-Based Ethernet VPN</title>
    <author fullname="A. Sajassi" initials="A." role="editor" surname="Sajassi"/>
    <author fullname="R. Aggarwal" initials="R." surname="Aggarwal"/>
    <author fullname="N. Bitar" initials="N." surname="Bitar"/>
    <author fullname="A. Isaac" initials="A." surname="Isaac"/>
    <author fullname="J. Uttaro" initials="J." surname="Uttaro"/>
    <author fullname="J. Drake" initials="J." surname="Drake"/>
    <author fullname="W. Henderickx" initials="W." surname="Henderickx"/>
    <date month="February" year="2015"/>
    <abstract>
      <t>This document describes procedures for BGP MPLS-based Ethernet VPNs (EVPN). The procedures described here meet the requirements specified in RFC 7209 -- "Requirements for Ethernet VPN (EVPN)".</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7432"/>
  <seriesInfo name="DOI" value="10.17487/RFC7432"/>
</reference>
<reference anchor="RFC7454">
  <front>
    <title>BGP Operations and Security</title>
    <author fullname="J. Durand" initials="J." surname="Durand"/>
    <author fullname="I. Pepelnjak" initials="I." surname="Pepelnjak"/>
    <author fullname="G. Doering" initials="G." surname="Doering"/>
    <date month="February" year="2015"/>
    <abstract>
      <t>The Border Gateway Protocol (BGP) is the protocol almost exclusively used in the Internet to exchange routing information between network domains. Due to this central nature, it is important to understand the security measures that can and should be deployed to prevent accidental or intentional routing disturbances.</t>
      <t>This document describes measures to protect the BGP sessions itself such as Time to Live (TTL), the TCP Authentication Option (TCP-AO), and control-plane filtering. It also describes measures to better control the flow of routing information, using prefix filtering and automation of prefix filters, max-prefix filtering, Autonomous System (AS) path filtering, route flap dampening, and BGP community scrubbing.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="194"/>
  <seriesInfo name="RFC" value="7454"/>
  <seriesInfo name="DOI" value="10.17487/RFC7454"/>
</reference>
<reference anchor="RFC7606">
  <front>
    <title>Revised Error Handling for BGP UPDATE Messages</title>
    <author fullname="E. Chen" initials="E." role="editor" surname="Chen"/>
    <author fullname="J. Scudder" initials="J." role="editor" surname="Scudder"/>
    <author fullname="P. Mohapatra" initials="P." surname="Mohapatra"/>
    <author fullname="K. Patel" initials="K." surname="Patel"/>
    <date month="August" year="2015"/>
    <abstract>
      <t>According to the base BGP specification, a BGP speaker that receives an UPDATE message containing a malformed attribute is required to reset the session over which the offending attribute was received. This behavior is undesirable because a session reset would impact not only routes with the offending attribute but also other valid routes exchanged over the session. This document partially revises the error handling for UPDATE messages and provides guidelines for the authors of documents defining new attributes. Finally, it revises the error handling procedures for a number of existing attributes.</t>
      <t>This document updates error handling for RFCs 1997, 4271, 4360, 4456, 4760, 5543, 5701, and 6368.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7606"/>
  <seriesInfo name="DOI" value="10.17487/RFC7606"/>
</reference>
<reference anchor="RFC7911">
  <front>
    <title>Advertisement of Multiple Paths in BGP</title>
    <author fullname="D. Walton" initials="D." surname="Walton"/>
    <author fullname="A. Retana" initials="A." surname="Retana"/>
    <author fullname="E. Chen" initials="E." surname="Chen"/>
    <author fullname="J. Scudder" initials="J." surname="Scudder"/>
    <date month="July" year="2016"/>
    <abstract>
      <t>This document defines a BGP extension that allows the advertisement of multiple paths for the same address prefix without the new paths implicitly replacing any previous ones. The essence of the extension is that each path is identified by a Path Identifier in addition to the address prefix.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7911"/>
  <seriesInfo name="DOI" value="10.17487/RFC7911"/>
</reference>
<reference anchor="RFC7938">
  <front>
    <title>Use of BGP for Routing in Large-Scale Data Centers</title>
    <author fullname="P. Lapukhov" initials="P." surname="Lapukhov"/>
    <author fullname="A. Premji" initials="A." surname="Premji"/>
    <author fullname="J. Mitchell" initials="J." role="editor" surname="Mitchell"/>
    <date month="August" year="2016"/>
    <abstract>
      <t>Some network operators build and operate data centers that support over one hundred thousand servers. In this document, such data centers are referred to as "large-scale" to differentiate them from smaller infrastructures. Environments of this scale have a unique set of network requirements with an emphasis on operational simplicity and network stability. This document summarizes operational experience in designing and operating large-scale data centers using BGP as the only routing protocol. The intent is to report on a proven and stable routing design that could be leveraged by others in the industry.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7938"/>
  <seriesInfo name="DOI" value="10.17487/RFC7938"/>
</reference>
<reference anchor="RFC7964">
  <front>
    <title>Solutions for BGP Persistent Route Oscillation</title>
    <author fullname="D. Walton" initials="D." surname="Walton"/>
    <author fullname="A. Retana" initials="A." surname="Retana"/>
    <author fullname="E. Chen" initials="E." surname="Chen"/>
    <author fullname="J. Scudder" initials="J." surname="Scudder"/>
    <date month="September" year="2016"/>
    <abstract>
      <t>Routing information reduction by BGP Route Reflection or Confederation can result in persistent internal BGP route oscillations with certain routing setups and network topologies. This document specifies two sets of additional paths that can be used to eliminate these route oscillations in a network.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7964"/>
  <seriesInfo name="DOI" value="10.17487/RFC7964"/>
</reference>
<reference anchor="RFC8201">
  <front>
    <title>Path MTU Discovery for IP version 6</title>
    <author fullname="J. McCann" initials="J." surname="McCann"/>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <author fullname="J. Mogul" initials="J." surname="Mogul"/>
    <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden"/>
    <date month="July" year="2017"/>
    <abstract>
      <t>This document describes Path MTU Discovery (PMTUD) for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP version 4. It obsoletes RFC 1981.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="87"/>
  <seriesInfo name="RFC" value="8201"/>
  <seriesInfo name="DOI" value="10.17487/RFC8201"/>
</reference>
<reference anchor="RFC8277">
  <front>
    <title>Using BGP to Bind MPLS Labels to Address Prefixes</title>
    <author fullname="E. Rosen" initials="E." surname="Rosen"/>
    <date month="October" year="2017"/>
    <abstract>
      <t>This document specifies a set of procedures for using BGP to advertise that a specified router has bound a specified MPLS label (or a specified sequence of MPLS labels organized as a contiguous part of a label stack) to a specified address prefix. This can be done by sending a BGP UPDATE message whose Network Layer Reachability Information field contains both the prefix and the MPLS label(s) and whose Next Hop field identifies the node at which said prefix is bound to said label(s). This document obsoletes RFC 3107.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8277"/>
  <seriesInfo name="DOI" value="10.17487/RFC8277"/>
</reference>
<reference anchor="RFC8538">
  <front>
    <title>Notification Message Support for BGP Graceful Restart</title>
    <author fullname="K. Patel" initials="K." surname="Patel"/>
    <author fullname="R. Fernando" initials="R." surname="Fernando"/>
    <author fullname="J. Scudder" initials="J." surname="Scudder"/>
    <author fullname="J. Haas" initials="J." surname="Haas"/>
    <date month="March" year="2019"/>
    <abstract>
      <t>The BGP Graceful Restart mechanism defined in RFC 4724 limits the usage of BGP Graceful Restart to BGP messages other than BGP NOTIFICATION messages. This document updates RFC 4724 by defining an extension that permits the Graceful Restart procedures to be performed when the BGP speaker receives a BGP NOTIFICATION message or the Hold Time expires. This document also defines a new subcode for BGP Cease NOTIFICATION messages; this new subcode requests a full session restart instead of a Graceful Restart.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8538"/>
  <seriesInfo name="DOI" value="10.17487/RFC8538"/>
</reference>
<reference anchor="RFC8654">
  <front>
    <title>Extended Message Support for BGP</title>
    <author fullname="R. Bush" initials="R." surname="Bush"/>
    <author fullname="K. Patel" initials="K." surname="Patel"/>
    <author fullname="D. Ward" initials="D." surname="Ward"/>
    <date month="October" year="2019"/>
    <abstract>
      <t>The BGP specification (RFC 4271) mandates a maximum BGP message size of 4,096 octets. As BGP is extended to support new Address Family Identifiers (AFIs), Subsequent AFIs (SAFIs), and other features, there is a need to extend the maximum message size beyond 4,096 octets. This document updates the BGP specification by extending the maximum message size from 4,096 octets to 65,535 octets for all messages except for OPEN and KEEPALIVE messages.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8654"/>
  <seriesInfo name="DOI" value="10.17487/RFC8654"/>
</reference>
<reference anchor="RFC8955">
  <front>
    <title>Dissemination of Flow Specification Rules</title>
    <author fullname="C. Loibl" initials="C." surname="Loibl"/>
    <author fullname="S. Hares" initials="S." surname="Hares"/>
    <author fullname="R. Raszuk" initials="R." surname="Raszuk"/>
    <author fullname="D. McPherson" initials="D." surname="McPherson"/>
    <author fullname="M. Bacher" initials="M." surname="Bacher"/>
    <date month="December" year="2020"/>
    <abstract>
      <t>This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic Flow Specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix.</t>
      <t>It also specifies BGP Extended Community encoding formats, which can be used to propagate Traffic Filtering Actions along with the Flow Specification NLRI. Those Traffic Filtering Actions encode actions a routing system can take if the packet matches the Flow Specification.</t>
      <t>This document obsoletes both RFC 5575 and RFC 7674.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8955"/>
  <seriesInfo name="DOI" value="10.17487/RFC8955"/>
</reference>
<reference anchor="RFC9107">
  <front>
    <title>BGP Optimal Route Reflection (BGP ORR)</title>
    <author fullname="R. Raszuk" initials="R." role="editor" surname="Raszuk"/>
    <author fullname="B. Decraene" initials="B." role="editor" surname="Decraene"/>
    <author fullname="C. Cassar" initials="C." surname="Cassar"/>
    <author fullname="E. Åman" initials="E." surname="Åman"/>
    <author fullname="K. Wang" initials="K." surname="Wang"/>
    <date month="August" year="2021"/>
    <abstract>
      <t>This document defines an extension to BGP route reflectors. On route reflectors, BGP route selection is modified in order to choose the best route from the standpoint of their clients, rather than from the standpoint of the route reflectors themselves. Depending on the scaling and precision requirements, route selection can be specific for one client, common for a set of clients, or common for all clients of a route reflector. This solution is particularly applicable in deployments using centralized route reflectors, where choosing the best route based on the route reflector's IGP location is suboptimal. This facilitates, for example, a "best exit point" policy ("hot potato routing").</t>
      <t>The solution relies upon all route reflectors learning all paths that are eligible for consideration. BGP route selection is performed in the route reflectors based on the IGP cost from configured locations in the link-state IGP.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9107"/>
  <seriesInfo name="DOI" value="10.17487/RFC9107"/>
</reference>
<reference anchor="RFC9293">
  <front>
    <title>Transmission Control Protocol (TCP)</title>
    <author fullname="W. Eddy" initials="W." role="editor" surname="Eddy"/>
    <date month="August" year="2022"/>
    <abstract>
      <t>This document specifies the Transmission Control Protocol (TCP). TCP is an important transport-layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN-RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="7"/>
  <seriesInfo name="RFC" value="9293"/>
  <seriesInfo name="DOI" value="10.17487/RFC9293"/>
</reference>
<reference anchor="RFC9494">
  <front>
    <title>Long-Lived Graceful Restart for BGP</title>
    <author fullname="J. Uttaro" initials="J." surname="Uttaro"/>
    <author fullname="E. Chen" initials="E." surname="Chen"/>
    <author fullname="B. Decraene" initials="B." surname="Decraene"/>
    <author fullname="J. Scudder" initials="J." surname="Scudder"/>
    <date month="November" year="2023"/>
    <abstract>
      <t>This document introduces a BGP capability called the "Long-Lived Graceful Restart Capability" (or "LLGR Capability"). The benefit of this capability is that stale routes can be retained for a longer time upon session failure than is provided for by BGP Graceful Restart (as described in RFC 4724). A well-known BGP community called "LLGR_STALE" is introduced for marking stale routes retained for a longer time. A second well-known BGP community called "NO_LLGR" is introduced for marking routes for which these procedures should not be applied. We also specify that such long-lived stale routes be treated as the least preferred and that their advertisements be limited to BGP speakers that have advertised the capability. Use of this extension is not advisable in all cases, and we provide guidelines to help determine if it is.</t>
      <t>This memo updates RFC 6368 by specifying that the LLGR_STALE community must be propagated into, or out of, the path attributes exchanged between the Provider Edge (PE) and Customer Edge (CE) routers.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9494"/>
  <seriesInfo name="DOI" value="10.17487/RFC9494"/>
</reference>
<reference anchor="RFC9552">
  <front>
    <title>Distribution of Link-State and Traffic Engineering Information Using BGP</title>
    <author fullname="K. Talaulikar" initials="K." role="editor" surname="Talaulikar"/>
    <date month="December" year="2023"/>
    <abstract>
      <t>In many environments, a component external to a network is called upon to perform computations based on the network topology and the current state of the connections within the network, including Traffic Engineering (TE) information. This is information typically distributed by IGP routing protocols within the network.</t>
      <t>This document 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. This is achieved using a BGP Network Layer Reachability Information (NLRI) encoding format. The mechanism applies to physical and virtual (e.g., tunnel) IGP links. The mechanism described is subject to policy control.</t>
      <t>Applications of this technique include Application-Layer Traffic Optimization (ALTO) servers and Path Computation Elements (PCEs).</t>
      <t>This document obsoletes RFC 7752 by completely replacing that document. It makes some small changes and clarifications to the previous specification. This document also obsoletes RFC 9029 by incorporating the updates that it made to RFC 7752.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9552"/>
  <seriesInfo name="DOI" value="10.17487/RFC9552"/>
</reference>
<reference anchor="RFC9871">
  <front>
    <title>BGP Color-Aware Routing (CAR)</title>
    <author fullname="D. Rao" initials="D." role="editor" surname="Rao"/>
    <author fullname="S. Agrawal" initials="S." role="editor" surname="Agrawal"/>
    <date month="November" year="2025"/>
    <abstract>
      <t>This document describes a BGP-based routing solution to establish end-to-end intent-aware paths across a multi-domain transport network. The transport network can span multiple service provider and customer network domains. The BGP intent-aware paths can be used to steer traffic flows for service routes that need a specific intent. This solution is called BGP Color-Aware Routing (BGP CAR).</t>
      <t>This document describes the routing framework and BGP extensions to enable intent-aware routing using the BGP CAR solution. The solution defines two new BGP SAFIs (BGP CAR SAFI and BGP VPN CAR SAFI) for IPv4 and IPv6. It also defines an extensible Network Layer Reachability Information (NLRI) model for both SAFIs that allows multiple NLRI types to be defined for different use cases. Each type of NLRI contains key and TLV-based non-key fields for efficient encoding of different per-prefix information. This specification defines two NLRI types: Color-Aware Route NLRI and IP Prefix NLRI. It defines non-key TLV types for the MPLS label stack, SR-MPLS label index, and Segment Routing over IPv6 (SRv6) Segment Identifiers (SIDs). This solution also defines a new Local Color Mapping (LCM) Extended Community.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9871"/>
  <seriesInfo name="DOI" value="10.17487/RFC9871"/>
</reference>

<reference anchor="I-D.draft-ietf-idr-bgp-fwd-rr" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-fwd-rr-05">
  <front>
    <title>BGP Route Reflector with Next Hop Self</title>
    <author initials="K." surname="Vairavakkalai" fullname="Kaliraj Vairavakkalai">
      <organization>HPE</organization>
    </author>
    <author initials="N." surname="Venkataraman" fullname="Natrajan Venkataraman">
      <organization>HPE</organization>
    </author>
    <date year="2026" month="February" day="23"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-fwd-rr-05"/>
</reference>
<reference anchor="I-D.draft-ietf-idr-rtc-hierarchical-rr" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rtc-hierarchical-rr-07">
  <front>
    <title>Extensions to RT-Constrain in Hierarchical Route Reflection Scenarios</title>
    <author initials="J." surname="Dong" fullname="Jie Dong">
      <organization>Huawei Technologies</organization>
    </author>
    <author initials="M." surname="Chen" fullname="Mach Chen">
      <organization>Huawei Technologies</organization>
    </author>
    <author initials="R." surname="Raszuk" fullname="Robert Raszuk">
      <organization>Arrcus</organization>
    </author>
    <date year="2026" month="November" day="02"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rtc-hierarchical-rr-07"/>
</reference>
<reference anchor="I-D.draft-ietf-idr-rtc-interas" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rtc-interas-00">
  <front>
    <title>Inter Domain considerations for Constrained Route distribution</title>
    <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
      <organization>Cisco</organization>
    </author>
    <author initials="J." surname="Haas" fullname="Jeffrey Haas">
      <organization>HPE</organization>
    </author>
    <author initials="K." surname="Patel" fullname="Keyur Patel">
      <organization>Arrcus</organization>
    </author>
    <date year="2026" month="August" day="17"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rtc-interas-00"/>
</reference>
<reference anchor="I-D.draft-ietf-mpls-seamless-mpls" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-seamless-mpls-07">
  <front>
    <title>Seamless MPLS Architecture</title>
    <author initials="N." surname="Leymann" fullname="Nicolai Leymann">
      <organization>Deutsche Telekom AG</organization>
    </author>
    <author initials="B." surname="Decraene" fullname="Bruno Decraene">
      <organization>Orange</organization>
    </author>
    <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
      <organization>Cisco Systems</organization>
    </author>
    <author initials="M." surname="Konstantynowicz" fullname="Maciek Konstantynowicz">
      <organization>Cisco Systems</organization>
    </author>
    <author initials="D." surname="Steinberg" fullname="Dirk Steinberg">
      <organization>Steinberg Consulting</organization>
    </author>
    <date year="2014" month="June" day="28"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-seamless-mpls-07"/>
</reference>
<reference anchor="I-D.draft-ietf-grow-bgpopsecupd" target="https://datatracker.ietf.org/doc/html/draft-ietf-grow-bgpopsecupd-15">
  <front>
    <title>BGP Operations and Security</title>
    <author initials="T." surname="Fiebig" fullname="Tobias Fiebig">
      <organization>MPI-INF</organization>
    </author>
    <author initials="N." surname="Hilliard" fullname="Nick Hilliard">
      <organization>INEX</organization>
    </author>
    <date year="2026" month="April" day="07"/>
  </front>
  <seriesInfo name="Internet-Draft" value="draft-ietf-grow-bgpopsecupd-15"/>
</reference>
<reference anchor="BGPAFI" target="https://www.iana.org/assignments/address-family-numbers/address-family-numbers.xml">
  <front>
    <title>Address Family Numbers</title>
    <author >
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="BGPSAFI" target="https://www.iana.org/assignments/safi-namespace/safi-namespace.xml">
  <front>
    <title>SAFI Namespace</title>
    <author >
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>


    </references>

</references>


<?line 792?>

<section numbered="false" anchor="acknowledgments"><name>Acknowledgments</name>

<t>Authors would like to thank Ketan Talaulikar, Jakob Heitz, Lokesh Khanna and Phil Bedard for their valuable guidance and collaboration on the numerous topics covered in this draft.
We also thank the following people for reviewing this draft and providing feedback: Dan Voyer, Bin Wen.</t>

</section>

    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false">
        <name>Contributors</name>
    <contact initials="S." surname="Litkowski" fullname="Stephane Litkowski">
      <organization>Cisco</organization>
      <address>
        <email>slitkows@cisco.com</email>
      </address>
    </contact>
    </section>

  </back>

<!-- ##markdown-source:
H4sIALMY/WoAA+19WXLjSJbgP08Bi7SZlDpIKiTFXtNjpSUiUpWxqCXl0mZh
UwaSTgklEGABoBTMVLb1IeZn/uYsc5Q+ybzV/TkASplZOWbz0aqsEAW6O3x5
/vZlNBoNmqzJ3evk0eG70+TsLDl2y7xcL1zRJEdlUWczV6VNBp8eDdLJpHI3
v6rpNG3cZVmtXydZMS8Hg1k5LdIFvGZWpfNmVC+y5mqUzapRVY1mfpjRNBpm
9GRvUK8mi6yu4c9mvYT+J28u3ibJV0ma1yXMJCugt4N/iubRMHnkZllTVlma
4x8nB4fwq6zg09nF20eDGczp9QBf4Yp6Vb9OmmrlBrCe/UFauRRGOytXTVZc
PhrcltX1ZVWulvDwpGhcNTouF2lWJL7FtVtDo9nrQTJKYDtGT+UD/qq4EX48
O9MHLqncPHdTmN/gxhUrmEqS3P+OJOE1P/oBpgNPknfYHJ9DuxxXP6v+nLlm
Pi4rap5W0yt4fNU0y/r1zg62wkfZjRtrsx18sDOpytva7UD/Hex3CaexmkDP
2d/oZPae7L7Y3Wkf1eRyee9xPRoMlhmuqimnr5O1q/kjtG9gVrBBSV1WDexC
rd/W60X4c5Cumquywh2FrxIAHPjieJyc4wToCUPQcXqTzZK/2C9gXWmR/UTT
eJ0cZfW0pOeO90lW9ecpfjGelovoFefj5Nsqc5V5xbmrLp15+sD4tbvGppvH
f5fe2tEBYKeu8k9bo5eV+8GlNy56w2V6++cpfHOL33RecTJOPri0qM1LTuoq
dXny3n4Tv+jg4r9e2Hdki5f7ey/+nDZNZ/xvYbN/Sqvr8jab/mRe8m3107r+
qSnnybtOi/hl35y+se+61o7j2vf689VSVgY/eE2bKpusmjZEwHa+zxroUl9n
dlMbt7xKC9f68qGTy7m1ObpBUVYLaH9DF/Ts7dHTvRe7+vHps+evBwNEaXGb
3d1X2mb31asX8nHv6Ytn+vHJ7kv5uL//lJ7C5WDMewh4hMChcbfpOjmtSrg1
ZZ5sATrZTk5dVWd1g0j2jNDIp3qa5TmtCNEuYDz4ROP5CwQ/I39/PkxPr2AM
aeNvUfsL6fA9QCsMH7W1z8K4P6R50x3UPJWmB+PkzDVpkUZN46eEmpO9J0/2
Rk9e0pPawZWqcadfSz/YOsBQuHuP5Mnxp5PXye6T8e6Lpy9f7MjW8s6mcIGb
14liwtvb23E1n46YPhAexKF34Jn0wdPdf/5UD/r5S//xxV74+EoP8dnLl/v6
8dWenvLz3Vd78vHF0/3w8ZmO8OL5k+f68dXurv+4/9J/9HN4CTDjP75QmHr5
zLd9+dyP+/LVM53Dq90n2vbV3iud5Kunr7QtNNWZvXrJoH0yOh4ztkcy4ZH9
/HYGCD+GVaT8BIZnSs2SW8CtyUf3pUm+KZeAO/N5DzQKwkjzrEr/lnyfwq+b
9Po6zdNMThMOJeAJ7fAxbaB9WiTfu+I6hWNNF2nR10EhaO85cA2jvf0NQESE
tnDN6BiXq+xIz6pHT/ohCd6DU5peuyrQVOBudq6aRb7zwHA9+1w109EVEA+i
09M0b2/4my9w9ZH9qYGWJmcXI+S0YALAJ8B/35ie8bkgdjifuiKtsrLeeB5/
yVxyXCKrYnZ0ld66LLlw06uizMvLzNVRnw/p9Co5unLFb+l0Vk5cBRgsrX9a
XduOB1U1XdXtI9zdRd7vdx1hz4aOnrz4x89y47gbDjXDaaZ1dJg09UTYvJh5
SoCkJP5s3UxOcwaon8hgP46/l/bJDgei50/dzeeVWyffpGl93+X71q1XVXIK
x5I/fGRPXo52X/z+I5PtGj158sccVTRe64gWy7we1S5d5K6u6a/olM7lm+TD
6ftzWC2cdwM3alW5jSfwMQOCnWbJe7cG/BTdjGO3aurplYO7kbvrcpEcvIu6
HlarooRWU+DXCmd7fqrS4tJFjY+An0fmMXmb5fUc/t856OR8DczConNlM3ed
fIvglYIgVQQ27cG+x1l1jRCWFXCDI0ThHxLcrnKWeQxU7D4dPXk+2ttE0O+B
iu4J/cN3eNOQLdgAiewW8Xa5rN10tZx1qN+npb+yaTEDYJmuqqxZbwSNi3KS
pTUcmJtk0fZ9OD0ZnXx824aja0DqeZ6l1cw2Pvn45sfOjXuqm/Kb9ra9wtHu
P0jp+geEvTp4e/J6IzuWAe/HAilI95cFypP1TjqbVXg883SR5etRsVoAfG16
PP6yyO3pPDrgZslbapZ85GaPeDLnv302dTrPRngw9TKdutafnbfjC4Bfka9B
GB6Px4PBaDRK0gli9WkzGJwUBENwMKhhqIdtXqpOts7O6u2kzgBAs/k6aQBx
LKvyJkMWAFUAIGvhMz5fIPo43NYJSQokMoHcsMyRFiBwgtSbXQLAUJcaiBaO
ML1K89wBZqlxMCRFDfwfv0mT+SrPE1jBFX6FowJo1cx9pAvgE5IJyyqk0IAT
SA7dNF3VTqaFH/R6wNwmgNDmWYPLPIMBKges4szBybAKAYgckMFFCQMWfksS
IHV59hNOB14/TgYXV1mdANitSM80c/UU6CHMHWQ1mBGqoeAZHBm8mW7lECeS
VQkcZDnNYPGzBDZ/5kblfA5f4rYEDQZMsW5gg+FwsikMOklraF8ibzVbwaGt
o/W4L0u8aIB/xwNGA3hi9VW5ymeenMs+1KtL2GHGE7fALMksaZthCjIsrzIs
fiLbiQ/j4wTEPYGNadYJbAecCUw+gykBT1jewFBwbDJIaCnQt8hms9wNBl8h
0FTlbEXMYQcWk59/FmH3l182wiW3ASn4l1/+E0b/E0b/ABhNEDBPXUUaFeRs
iKgCGLiWTnkwEK3zstW4psasBq5xX9LkBqQeB9OAE5+nDL9ZMc1XM1wMMNNJ
UTZJngHo4c6Xr2ES/5Qc3KC6dAJj1cQGJUBLylUFWw7s0el39r1DgL9FCTtf
Lx2MgLP4+woYK1x6qsOMcVCmQTgRC6jD6OSzBYApDQLEEx6NSCtcj2lW2E3I
X0LkLyO4KubZJTCkM7iRTGjx0tLnc/qj9XK6C/wO8+Zl2lyx4OFQpuu8ap2A
/AgrwU7JrYPzg9801A52hVu6qopxQvP84coBUBFk4SEx7Djcd3rUBZaygPHh
1ajI11YnpzibW+B98KConQxP/dMlQw1ugc7svnMd8tq+pICo4MyAWS1XxWwH
FkAfRC2/LPNsikNuEUZzCcBqvaLLC3992R6yDD6DIT/A1qSXeHGWyxLEWUKH
qIbB3QfuY3RKO0qPUb+Dj9/BxXWAswCZAtRrJ9Qq4befACEs+mR3aoW6nICN
L4hvCUKiDvX8JQ0FzGeJSskp3IVGRsEDz+pStIUACHVe3gIkwwoZzZydHO68
PTlMQJYAZAnbSIBzAZJHTSvM0zVCEM5StKiyPNQtARG4b/tB7PiSLVYL4JEv
CZGdZz+5ZOvD+Tns6S1gL5hKDY+GqDPCCd+45GB6DcIJHOyloy5b5wdH3wrd
QR0qLRTmfXF0ioLpVfLh4jsUkqeIYdbcDpWxMDU+HOhEfQIAQ9fRwSe9i8Sz
I6KapmHfUaWnd0gwFmwhINU1LgvfP69AkpvCZQQ+kR4UZTHiv3l7xwq1BFO4
ltSfiMVgQisVMQacK0gISJPL54gLNmNzxKyM0RXbwTKXCGs8OlAaIkFKUWC0
t6sKr+sQDgBnEfcG9LlWMsgkNZ5eKegKkTHsC64FwAlw4TSbA/jdi6cvVzhu
VjgmtgDYuAYh/jA8T9mQU5jsp4heR8Swcnkq0IZDwNtShhxA0cCMoDFQqBkx
EYA1ZNOV2hP6gVnQ5cAJjJEgHeVAWVFVw2S7TYkukOPJ4V4TjELPlIg8KkIV
kyHvk5V9Wv0T5IOacolqMqKU0BmABG5byswDvjFSDo0TfCHgZZax/WkoTE5h
hHQ+hytE96K18UMazP19BXPN10NLiGzTMcwZ0T+ZE4bMD9BKoPnCNRUcrGwy
DgDi6MVfv/l0ivPXucIxzFa033xIeD1rJwhtyHv0H//+v+okL+Wy2Q2DQf2m
4IJAms1XToCTB8saGQ9vFx7gVXpDX1cOVuGIh8oYTgByJ444msDFTfOy5hcB
t/oF0dRalgQXRO4ybjUeyRKaIE2ERa0QznSrEZKuXL5EAlSv8J1XaaNEj7At
4APFCzQ9ICpohTX7SJpcori6i+PkIG/gUl9e+RdVaKEqWsARQQUyIcAnF1m9
AJSwguHg1uPZ9BIimhzrLzZQnK1PZ2fblu7QMXj2nE7gKpvpfYJZAc8fTgem
OgMc3GQ1X0fYD7+n587BwNhq5AECxkfqrBAHMwKyBawTnu1XX8HEZkCiATDX
nvGr/CPY/CuE2brLUCYT+BZpUCFoFP7JkchneCLEEGY5HhwhYriUOBtc0iVu
dwPvGeXuxuWIEwCVwOQ/QpthclXewuNqyAfuvkzxBt241rxwxybIjMI5E87P
BaCywDcTnkJwJRQkm5RsufHleBjLLsPk9I183GaqQjdmGIY4iblK5h+FtPOh
YFN5xQJwGsywqta6eFwE3gwEWhypIb41OZkDsTTCwq2cJuFE4JN2qf/eNpFV
IEa3ZIt4SxxpsjvU66DXYOtotHcwTODfQ/r3aJtvI6PYPZ6XzubZk//CS7t3
VcibpRUDmg60G+DtbcT2zfmyCaWlXTeQioQnXcC8x88A2POcrgL88WFbuWZB
ezI6LS8wtbRlJHZ05pHcMpmmHd//wFNHzJrl7p7+e739n8KMeASEKADBjGeC
HFjF/EVOYtaVS2cqb8gbjdjhhYyaO4IsCcgNyHFa5Wu25DnipBSo8UYoey4z
RGbk3/7t3wbJ49E9P49JD3lvk9HjQXKX6M+R3z//c2f+jdrsmTZ/9Dx6fjrz
6GvjxwAUsnsQPh62x4CHewfy7d6hfjiKxkh2Pn/WTzuJfjTzuNPvd+70w85d
PI+dBDp+pg/wUQexY/jv73y7eAzsh1/9KB9lkGgMfPZ5hz/tULtoDO6HI9D/
/SDxGPAMl3lH/+4krTF0oDt5ne1oP9IL/sl/ao+xw7/vdA59Y/D772Q+7TF2
dA/vdCU9Y+AmfOZPn+lF8Rh3rTHkSTSGntid/P7828fYkbl+1kl//mzHOFIY
PVIIhQ9H0RhHAqb0Sdu04bT351felz/g3iIe+vk16+D/+dEFU6ojpVSEz84M
Jqsf/TIIsg/xuKmoAYBCFyWwpsUlSlReF0SynXMzIgMTR0POqvRWGVolrkD5
UfrVr/2wOWBWNOeSwIh0FunPCuTNHNnZyk0dcBHIB2hPQOPUtkWzxoMDbMVC
wFCRN3IuJD4GTY9dLdBJpCAk4+RIF2ANqAGApqKQuUFPN+L+BwfIAT1MU+6l
y/8QTUEhpxTudNOCiPvyTJMIwsga8XtQbgzuiSqRDoMwMUP+EN87EM7x65q8
JtXCO2QxdejZxBkZ62WRsPuogGP+/O+rjDcJz0ZVvZeuHIUZGyUuqpDhyIub
MsfzVhKPU8dDpNnPyxVK6vVQ3dZY84b8lzJfQ4YL5H+qrGaFeHjfMs2qcYBv
1omSRr6ItAy1q25IfMZFtXS4vPxZBvJk5fioPOe3SFGsUr0xQjUwWqFpn65S
mf/YhAfM/8ShKgoHIHYPdTgrFkppshleuGU2ZWng6P135xdvzv56coyyOOk+
U7ZiRLdbBcrUM1Mo4uO9lOPiG3CVVi4wfmHs8eAHxAjV/UMiDx/WHHozPwbQ
BTegketLKtG0ttohYtlFAydMr4pU6XTqliSNhN4kMMtNGw+O6MaCDLUmvpbe
t3E5Mh8836xYOZI6v6DEeOmUtUWl3S0wvUl2WeApiIuym2kDQkUlmWp4Maj/
uimzmTo5J94ZEo4tL8slKbcB9ObkxZIV1maEt/woUkaQ8C64V0wx+Aq/SaxN
aG5d51xw2Qz/dsWrgjw3XEaTNSw/yeJvImsRgB4MqQ42jtQSOcrpQxQnG8Qb
0AS2r4i2BATJku0+fZKdgVRaFUo27KHOsIdyOkIDrVCJg6rna1HEBahtHccS
FhXtZ0QUuDOO3unIogTcXYWA2YZtNaYFwkk9cOVVvXhnU5BXZ3BJvQJjJViJ
wHJmu6kuRe0qJGGuFkuvF2Uwt7eifOg2DpGKotS9LBs2NwHJIRW0RdZCa4AK
sbquzhawYYDuylUd6cME69eCqHEK2DJDswAJjogvVToLyitPxC5UF0XzymqD
KolyPYBaAiEz6IM3dFVkcGksuiHTWVBVnpNBksy6qlNBgCON6ENsAoKV2VCk
iWSV8YonGoiNsGwMxXMKlIHU+CDoZ2M3HrbepKRab515F6pB5bCwzyRPa9ii
dJat6s6RKbPF75NzAsI7nZZkLVLNpjdTlvOGgJvwvj3FQM4+jwiMyRKFhGie
QivCl7BONr0CpNNW4NdXZZX9VBJTpHbqrcANxerO7WHECkzXQ6s0Y01cj5aU
lM8fcK6jWAVdD4A2Wb1BTLXb9taOWswrZUS/3O5wjzGXFMPAJKIFVxE2U5wK
KPvW/rbyPrTHIz0i/66azatvvdke/+I1Nhk0DH/yiweDN4H1RVrLowAGr4mB
RnVT7di24Y3mqFVBDWjlvPl9xiwGXUrBqXSUeOS4GXTsbbs8vONqPakya4An
ddOE3Q8EP4t62BkbwrIESCD1GV1LWu4HWC6gxuCyMNy0SYlb4Otq9W+ICCDt
mqJrNPbgnc34owfmHlXc3jjxNIpVhqgA5MNCaGx7OmyYG+0K3FFHJgYQV1C5
nuasgMWboKpXMozRHQo2R9Z2iQFR8ZD1alW5wpioWZYw+FXAGSARriMw6w5Z
aOIRgZtfwMmYsQPmoT28Ao6Eca/qvQBoiIcaCsygYETSXXQ5IyNKw2yxV3zF
P/fLqKJf6hOQ5adH8UXicbeLvulx592PN3W5E3XUnZ/MnWil7v6gt9CXO6O7
0Wf4n/3Zkafd5ePPjtcd2UfytKeDKoU+J9plxz7t9tjR9XBzVivZp50uO34L
pM+PnaftPl4hlIR3fG4/HfT28UDwo/k3PG310k5BMfc5/DIAFXfzvUS3FSZp
NGDdfqGbaKCiGao2qtvR9Autkx1zxD+aFqan6bgTBjday0RUlJ2uoafXGiaJ
WWGSBLBp9fVd7Qn7p5G61PfWztoqPsswmfhUtLv03mlP/S7+M9KQmv6fB3jX
7uRyhZ87+ZsuLF3Hz74d/3zWdo8Hd+F9Rpt+Z2+GX/Odb7KfeIC5gyHuQxEy
xL1NBneMmPY6iGnvMDyhB/udJvuIu/6QWfB22o0yO2q2s9PiTpsM+DU9qs4W
VXjc/v5OUemv6t2ewOPQ+1eQn+740vvhvhtGbClekdsZIbfTYl4pSBx5CNS7
fqMmVFL6pGQ/HbFXCFJcy3CRDATEd235deZhiaoHH1Bli5AlAjm8XJAy1XIl
k7KBOYIMfx0k9hmrQ64yEFjhDSr+TcuV+vN0nFrFHYy8G1mLNxMF8mzGThm3
kXAhVkP1aWgbJcUVl2Vl6SvCShDCddzYy7Vkzg/mUpMGhjSGzMsE/atX26rd
X9c4w3Ay5OppLz7+j72u0y07lCBTO3OXyGLTAF3pnHXjLGkYXTIyuchXZdcu
YmdjNjbJ0Z3NsGux2y6BAPrloO6bWWoGrQsMygaeeuEliM1MNXpyJDZoK9L1
9gn5OF4t/kHM9+Y4akVORoGz3pftC+8h56KZqEQFuFEVgYv8LUC+gcd88K72
8VgGr3hUf9DCAO0ejwPGwJ0mS6s+6++BOHk3iVEkPtsjLP3AO1qr63+Hx8GW
v9wZRTi45ycm3TsbF20ae67q1zW2/MyDjS0380DjmAe5d0ssH/D5vi3xlkUj
cBwkxrLY06MNDLvJg8AAsPCkDQwAC0/+Exiixv8fAsPh/wtg2O8BhqcPA4OV
Ce8FBj34z/L/HQMMn3tW3hLxdvgf82yDgOfP4nMSBJqHRDXPVXvQ+GzBZZPI
5eHIAsmvEZz6ASbpFZxiucnKh6FzS/ZpiS+RTGq7cqcgkYbujwOIWlD9McYA
j/0zA8ryG+QXgYfojfIs7O1dD1r5rK0Gd0if9nto1lPvWpGQT8XZ2bOeVs/h
Kz+PQFoP75uHb3UUWg0MgfbENuxp91NPq8F9bEFX6ult1WLmA591Hzd/wFpU
9Caom4R8JodtHo6dWL3FxHujc5Clm8XcvXrKCuccePyYvROeK6h50wkwu6Sl
JpVgYAzZ6D70NsDI2N6aasrWT1eJkRgDBXiziQE9KeDd7ASxkaWF1yyGppdo
o0W5mtZ2HwSDGtZdjLiL2pGDAL5jTeO7GfKEqv0PTKea0056uPukLLy9SuL0
MlKZ4u5bsYbsVGjWJ5fImjz+2ZO85SBCYUrJJXC1RcdFBE6R1KzWnbtjUAAB
iP0SFmQeS72HBW2p3w9v4mnWS+TY87WYN1njLVKDNRWNjXBwShaEn79aBHvC
L0FYoL83SwviVOHqIA6Y9GIS7YCBC+Kre/bmmKWr99+92YYz+oGXT6Y7eZWX
BsUx2J4qGpcNrJLRvAXSA/Q9Zu31rTl/DTRc1STsggAmphN2MkEJxIstWWkt
Ak/5MsRSUN2O20GHE14qugV17QpPh9Z8SbcLtoKnsHV2NgJxoLmqyBqMfz3f
JuCO1p7y7RBDBhm1YBfNGIfRGIfPt8dk2TSLVeOE9TQOQBNf721jWm0olsKa
PwEC0cXBB7AoaLQOMwRgwBfkqxPL5WzZxJkASFqLVjCFKRysahYngx/JbboW
JyN6JRq7UvO1XpaJu0pvshK9fFo+zgbE8UjpDQQJohKYJdYYGdblo4nIzdgV
tOV9zh3WBiwORPhedQzhwebswa+4uO0AxeBnbj7uezQNxmrWp169DQDdYLyB
9+Q5OYXPsAwf7ez9ntJoM+R2+w0xQ7NpN53iAGQbqst5c0txSRUcQTWjz6sl
KUFgWYfG0UNwgQQ6WkyRe//6GwxtWqyaFSBJu/vsl8OgoHvKCEHeBVjbLVMc
WDzoUBMyy+pqxf5BnbWj/wUGW7N5jgBCJkgr0LV3TdjW1UtMcNCOLXDi7hVc
ZNBFqSrr2vQRPPF7ThyHl0OlO9l6OwJkRpHO+Zq99lJ53bilImkzN336zk6b
0B35q4DA+v1W8ZnBUFYYIVdZJSa7m7trm8PduLtyiB3eMdncxnS/I4R7N6Lf
e3e93e8IoXKbQ2gTv/2xjPz4nrdHbeKd9wr1e3Y+ahNLS3et330/vs0f9mYc
0ZvoN7y90ybujj8ArBsn32kTdzdc9sbuUZugsOfmQn6xaQ+v399m4CfWC/Qt
maMD9GEZd/KicK0eyxRaY/Sekxmj2+PXPhl0h/5dTwbdO/C7ngz4Ku7LVXwK
V5GfPJMnz/XJobQ59G0Opc3hcytZeozwu54Mukfc+8SecN+TQYTg9nQc/2Rf
nnj8tpe0n+z784pQcA/i/hVPeqVVZvzvEVe/SlrZgZBEH4mAwr0lTF3iwL9q
eSxzGKJE/hsRAVP0EgupkeLvKWT+zJBnkB4DG7X18f3ZyTZQaGQVUCwjl/TW
5E70yyrZOnh7ss1ZMVYT8Zy9r/k5tb9J85WrTXaIKDlEclB4cYb4EGb+/Jqg
1Q6lM2LHJ4n7R5MSOiuyA5G4YLUiECN/cGhCO6PDefbXy//oESuMTpCvxhwK
MANuvBbG0zfqpMIweT9YuhUHdrFWwRlgrDjI/XWTTdFNT7I9DNUxcVkuV+yr
hPw3x33wqVkXf+++Z2L5fXxB7NHKuRnI8Z0mTYbFVOV1EorxtNDbtKza5jTJ
K+JTj4jcR8KZejjBLGBJJpaVmKZ0Qolrc105RsjfkKHvTGfHeQpmTiJcg5MW
8ojkHOZdvEL8d2fHyeNt0wHyanhG+KqwDSGiM4Hj8PG5EplALsZhAM88S5/O
jFEosI7twQkemGxX5WtKIHL/3gKcRVdeMpGwYdaz9hybPIXdgbWQZ6IJWY4u
kfc15eBezH7bkJPcsO0EOyRP+Uk6vdbtpUY2ssHmLxh2EhjQymZ49DAnH4tc
29XgjEJovEqB1oxNEK3LtatSbn3BB3jQhgASo1VbZ3cJcKl7+I5hpMOme0bT
FmfTXGMbUoOtxMFfbnkruYa5foSKArxE7/gb0AdMXFX7Cwqg8Klwito6YTuc
kKd7FSgUQFPtDZPvTz+qZMzLbHwelUgVVr+mfEOF7xp//X/+N4s+dXKZlxMM
STi9eUrjwYfnseDHZmjOl4CZWBw3XhXZNK1hStTD/4VjPNeYcsn5hH9LSppX
LzGji+gOYGV6CcM0nrfFTliGXfamhcgL2wO/34e+w+T9Hv0iIEcShJO1o9Y9
y4SvR7jUoX56Pkw+0DBv/GCsmKDRZQbeGbibUQlPHiAOxXtOjXDM7hWrrL4i
9bRNwqPZc/rz8tStxDw4FfJGjxJC0C1Z20xbfIdsYFkSR8vIfuEKqR8vrbuY
vjukwG1PS2+VQdJBy2lVVZwdTAj7lNM6PUBo0xk65rIOElZNGZcwLdcGrKDu
96MH7qyQpMzjZUVnAowbrtxGUMSkTJM8w2xylfjhx2MUzhPSDhAi70P3DXAZ
dJ2N5KZR6vbR+++2NQnRixcmA8dRmZfV6IB0S1LrgTokRwc+AcdLTMMXUtfx
cGGEgzOGJX+qbSxMTQ0MwIEHyOvbf6+SaoFL2IsALJwiBaPAMJQVNgjTYlVr
pnnzCjagWrFumZBWpCRlfgYmVd4qPxNnwZO3dYCaw29F3YZHd0kJxwzoboLb
X8UX9lKqzSC8mbjwLUkokR7whineXOZo4RyJkMC6g66/Sz8T+JMzqWFYk6YN
itFCpPxFDN7DWIcUjC4cHu9I1igKrjci9yHF3iQS1ZWJtYGataFdces5w5eE
4rQBdsMUuwBm4+ng4OarghPUUEio0UaarjFVujfvYR+6ZEUjZo4JanF1AsSE
ihRJx7wxm6uCspuikAZ+n7HXRpxMDGYcPuqTz+lOhZw+Y5PIZ2tZZQu4YjvI
M66Ww6QY3aYYU5Tn250sP78mp1x0S9DcqRlRLHLV2FwKd4EZaBqgup3fh4Hb
pCPSAEZjVApb1BEoMKhOt2dCr8sz7tS7lQTCIohL9kVziVC0D/MdbziNLrm/
n4rHkWrt+JWQKEbQSF9GOFZgE9oGmCKmn/hvAAS4Q2IFM7gw4jfGvUwJ41Hm
c27x8FipgI6OuGx4yTz74nFn5fCt0IDtbzMaCiAaFRJDkqhmHB3FIfJqib5c
AaqETpICapahoZjuWZQwrBU8irKtIAH+RDggZDZl+xcumbKst9M+2gx2aVJH
Gdkj6+XPPz+Y3B1OT0Wzwn1pRlflEtNQzWOBi+ZG4xN6o62dqnCA83+fFdej
c7QTCXk/V2L97NkevCMgJsp+cD2qqa3IAXOgBSNXXGaFOCG0TGscC4tnqqm8
hH/JNTkop9wEfmel8ireE54ipiDQAFyeG52q3nK8Dukl001vVK2HFE63XFXL
sr6PkeMcATQ7Qx+V0FGEOLyaE+xGwlBbCLJY2hONAwCIGS6DA69w6pFUrbKC
wUuVVWhY+mnDzlyhwynnp84DN2UOa8HZmjMYmsy5eAYTypSfdfUpQ2YUK87a
4S+RqMP8MZI/Sr1Aj+rKev0Ow6yU12rxTCRdq1U1pttNlAaQvYo56I4F9ilw
F+TKTSwcZROQTLSoULNoHB27He1BpDToz5+BhyQpF2E/WCQmbqCru6N771F9
zE9Yie4+0BjKFnQBw28F7lojWgAJ0u/AJ+ATxFu1hRwPIOPku4IZAvQYYkMl
SVf3yVVBydQnRGlmrx7WJ3TsY6fFbm3UEZRUQNM8L1xaE0qNOVj1BOgoQYhM
Pci9ArQj59FsYmMtEwot0A4NTbxiWOGecE8yOKFgdyLgt7A4THEg6kqMnZR1
IVz+URoUE+kQB33CtnZ1a57FE5Jj0PPJu1MKuj4N0vh3nIWZiu11Un9GGdD5
fsgcYKdmuaQ/J1ydNp4ecKBIwUEexI/VmiEoDq/mNrPSsVMOQKYKvZorcpgc
nP/19ODiGwDYT0cH7/96evbmLR3pB/RHCu+UUyNHEp8BlJOfRvUI6TawQYAD
mZFJYPRWhCCTT2cn704+Hlx8olQO7N8gqne8iZw7wyR7EO5en7w/Ob+gxIJF
GT1DsBGuJOQNxAQqlBPPaTA+Ecye13Bm1O7colcoBaFVj8KqCVBayZKDxlRZ
BuRCsumK5OaUmP0gXhDXClR47ZU5jaaCvQrJB3zOIY2VYY8U1NySBFd7fQIQ
EVaKV+wYIXFHCxC0KOk1pzd+9YqSQit/gI2qTrGgYUJ5PsKXS/Ju5PgcyTeA
rpDkeyj5O5Fo+MyIoo8jAMSWPuOrp0To9pcSlFjKYjg5FGdBKkR+Jsg5Ihlk
xRVJQDmGU1E6xwaj5xn1t+GTuVMWB1kM4713lJhb0lyso3zMZNXiXDftRLQ8
OrpAKr1B5VOYtmJWdXZRvgHRkDD8Nih9MDgofGJks2HmKnLWKpYfe7I+qJjq
0GqnpRAUongOlGWEdF3RxoSUuRZfc2p1QjhZAfx6NkMHJFHBIL4heZhrCoaD
oUTPrWQwZBpEGUm3FrZacpZZIZbBR3cdp0l0O/IfZWxerjDd5VVJ5GHMWJdJ
K+1AuH6cRZUMRcSIDtmwg9F8SF3I0hWzPlIJUS0MIkSGpeZ+M+NFikUhU7Mc
ZqI1ms5UcIAeu1xeOnUMHeSJGwc1ury3Vda0ERMW+IpQn5EAyLcV80QTqMzg
qqZNLQ7WIK4EJBUsPz7H0mQd5wTym8oQh7AoJAOnIDmpAnB65zBCh4AmbsQ8
SdRA0SDiPsxiDyCazYSF+iFQNcrhKtTKYwrV46C6ibBotrQ1Adoy39CkF5dt
nZck4Eowpi68VR+jVUiNUk7dW9EQN4kr7h6ck7YEK2kOjfstDHEu+737BA+e
93f/OenzMyZNon9jCVUDAQv15uZ0Nano/AlqO/SH4NegSwecTiFYKSP7pHAl
MjodSCr4D2GPk1J0s8wbBQdpHLsKCDhUOEnKraPVEDzqZwawLgVtFV4yZGGS
eZWGmFO518AJ5MKpIy5WNwJOhJ8Y1ackfZfUPJG3fVT7AjVbIs4K1v+SEu4U
zIwBl/22+DEWExmRt28wQwZUZTL/2nIS1l6kJmdv3fdvxQ0gdBrwIfGvRsBo
VfCwFgO2v8peyiZKGm+yS5tsWEMqOMJVZlLNnj7ruOOPe4oCBAy6qr1B059x
wPaMCX0uKxKpNpmh0LMZZIqxMslYXiW1hIvxMeVc94hX0qIT6Qwp+9Pc68CH
XtMxWQemv3KXQqRR1im9sWKapzUckyVzqsqQ1FhCMH05E4QBwlGIwAEmvIaf
mmW1Z8968A7IzhgKzg7UsAGq+y2iA04C/pZyCAhTUzZGnRRyrRCwdP99mY1I
tRHybPVVJuIgjkBmcI/R9oISIbP4RJTJiG9Tp0kAeMtYEM/AIQmaKmscqTWt
vChEAXdaw5yVqWTFEoNo06TK6qGjf5NiCbmhzbQescGcErUgisIiqToyxKiI
mfxy8jdxTWE7AGchtOYnebHxcGCBvHIqQgjLHI6eHcLFBjctAR1NG5AuKWc2
1/Xj6aus788HDvgI5gYyG2XpDEAV5evXjIY+f1mkujTkkfS4tYFDTEfkCyB0
ufugEAxMJG1n6lXuQSRWPabiI52VwBTAk2Rzmvks+OSSg9VahOnxWxt5qLRT
yqliqoXKIyuK4D8kIENvY7GIzZ9zHTiuULikg++EH5HQGFmIRw2bHLZYcdQ4
lm1Z0CFvm/h+cz4IcWhZj8ztyssU8AagnRXND5PyCxrvYG0d0WN8DqVilMuK
U1HxMLIlMcwUkfoqOUce6BRJWlsbwXoXwfIIy5Qjt0xm6yJdSCRMsHCHLA4j
pcZMBkJOUtHYsF7SGxOiiknErykdEdvTPhXmCcWAvOuTLLMo+2hQ5amF1lCT
FFx1q34MZWLgG8Qol3J8cGUHVc9GxScwP0YomJAVgYuRk7V0RLuaNIuaK8wT
EyNHMV3h+RJH5otRaJWzbjI9W2fFJEJJQz2mTROl85Dk0tfOLeFbE8ZEK28i
nlPZs9om7Vhw4SrRWLRD/ZjvAfidSPILHJtej5pf2WeaaUh2nTDhSPGVpOup
KM0KctF5ug5YgMBRIoToQDLj8CfvkFQaHGXTCTxk37d1YKHEmuLjYdAWwblS
2l2JalFKjZN2Ns5SFJ8uwYJThV1eHTiT3F2m03WUk8QjWGTR+twKh8wUMt+K
Q5+0752Hdq96VTsNgwmm4kuLFd3emyyVbLQtcxVpfufGDipKJpQLJIppaPEA
vPSY/zLv9fmopaevIUbvFqnTY0jSR4UKYlo2qQ2ydckpjxtvWCZgU7dVC2y+
dqLMLGK1Rf4EWlkQB5JhtlbzetLxMgPemgHIfWzsz9j0aBA38eNAGjAfILw9
ykmEbC7cVlIVGKgQuO1CEJ8Lm5zJq4HMpoR/veWiXdIvLi/EpYTII445LFRj
yZb5DSui+8M1MynlYTg3qsRnjcceRfRUhRsGANC05sjWXSpg2SpxmpfdS990
c9jdfG23Z4ReEeK8qziLWFV+P0xpFKDNlObSfKZkqKLSe8re4FOAsCUAGdPZ
gTIjikcIM8cXi++VUawEsSjydxjAm3AFt6ZsYXca0QsRTmBVDaX9tFiYYtx7
Old+9EzMIxjkiTAO1GQ8MN4yMCSAsrZGGOBXio8XJc+nXFXRfpCPPxdRoroF
iAVFM3MCZ1hqDmJMxJSLZqnxuVDN2RkBY+IUL87YLII85rnnMWP+I/n5q1ZN
p8HgENEGefIheSPXr6VLr5061xnKHTShnszOiCMLIpWn6jUrNTkGELvgrafp
I7ImlpGuETFqqpkS3CWsAzOiOpvgGydIVxKKtvhpTTgLjZB5RL50nLBPDiI4
bh0hX9zbq2wGVySMoGK2qBrVuOsdZljJWgs36F1sJpatQW2QKcGF16ucgowS
9PFGHuAZiTGJlB+1GuqlXVxIgdODs3uqDnCVCnPOTUTtOyPeKtTH8CWJOLFa
sJZQ4H7ublAOeqCYHHplYAaB31BMzqZcx3KjqEEDYRXZXVGiCxqSt0WH6evP
WS7Qb4//tpTCURLTnRy3yyl45XvawxoPo4ppHB9QU25cdF6aaKEL6TZUCV4P
qDZ7LBvhUyZ4bZB3hCtDBG1S1tMsFx/GWKdJzPr+/lOubXnuiF21blsmTMVM
nuVva+MJgBuH37TKxw7FYUFk7SAqSl0qu4dBGDTp6KwjSo80yIXiun5RyYEv
4u7LXLNx36Zfi3S6QfL2mlMh6d7Do9cBa+vsuKY05j56ObtEBMYXMOgdT99A
21PW91TJm5mWYKjq7TH7c9up1Uoa2D/t2Ds+ypt7Pb5oFPL6MZMgqI6nAbiW
mnoZLbgZ02061nusO87+YRozkJEPmK8OcsxyHBW9aPmVGWROOj4qD4JIHalP
wNneiSRcdA39QhX4d8S2hVM4rkV3xlbqoG3GNena1CFP1ADKF3NJVY2nZ8Ak
84h3tERKxFg4co8DOYhYSlbtDKnmAqJD7Czet5HxzuVwAnh1tYxGWYmio2It
PyEF1SqZjbIqYymw2DZXqvGdlw/HhmaZtmve4EBFWThPdScY4ilwQdmhcesL
JohRPMww6WApMhMBYWBFi0cOQfcTjKecP9KjB6myRBsodHoYTEWx/0/LfWJo
6BDVQwmQ4mNGeOrBSBTwiQkIC8k479Gby70nyNbqAophzYmRQUYThUbbxoTH
Fo3S00IifnY8YtcemTB9Ix516vbBPgUBq4jMLK7aSmmY3VTXFi4TcV/0DxzK
89M3lnYinMsrxPUTnyPbcNwtIUz3gFCuvy6DwTdwSwDdkBAEnFi5cKECA/Ha
ojlED0d6aaucU6kxFxG317YtoxpCVQ++HIu1NIVaV7bWrTdVkxezmMbJjjVj
nSEO3q74akAWCxVPOL2HLMMahm3mWbV9ex1FHDtoYlQ2F2j1Hvlp8PoPhJZr
pQZFVTCyGbwlahUmAhyta4IvejiYmH2PD8HHvwUtqnhbBzdfXwTNqNFQYokv
KG669yUPtjKtTqlWIHFt53vkvI97yQWuPUq1HKfmwGKzAgNFhcKO+4JJfDgH
K1rNNx9fByDdlyXpZKMNHg8GxtptxJJ6lek9tFCF+Mdqy0TI6PX+2CRoWIUq
ITJ2sdWWtqAwa1nFIZiKUCBWVkW/AWnr76NUUeQyC2GOte2R5chCnwhj2L8H
IadyloIXFauppYa4dN7kWBzJZCCuf0dSr0H6xh07XCBLKGkg69YT5SSO6rcp
C22CIGKH8zJf+RDtXtbaOJxo7bIOk03vkCuObCbWr6g5AMRTZF9XONDjFtEl
05hUNHayLQRL6mcoIoZYsqJZdvZKYpxVkxoZcBgq2FqGV1uDucUVzGjYhZkT
WbrXzt1n1O6xfcvFDAq6rqUbiQnxHGSUbK7ahZh64n08TenDZqxDUGQbSSgt
Om4SL4nljSwExuLo5ZgiGKLwforqzprTAn9P0Byct/uNX0xpN4XyoOH/V5fx
tm6wNXMTjAa6SgMvBLcrtUuSuPi++qJiS+/LIUbIvmubfCIPUzJ0MhrdRP1T
fodUEmNMZ/BiR8+JnrRlo+gW7gFrgX3xqbrlNuCXp2jUoJZPQs1EDA5I1nJt
pgy6LEhox4SiEKeECWw+MJGkdDpz0g3KEax1E4SwnTT9KHOpgfrCB+KwAgTW
kypFW6SyeIHIaD15I3j1qRrksWrLTEDPJzbJBeJEinXh4zsMezdbhkldR5uM
LQJuSiv1b6QO1ZrBJegM6Q3eJ55Rsj9zPkzvK0LHHwFf23GkA+DkhU0aFWKV
zcQCqfccQZfU23BWmQRqI4Xoh6pVwd86cmBLKT2dVi0MTF/J/o6tSp4UtROz
EKTBFb1JXJmU9toXFqhXaDnjOpSosFYFVicYCaOM5KorjxH0h+YqkjO5P4fO
IWBckmcQywnlDmzaKvrJ2rgHSnpFRsuiPsSp4lasBSVINIgJvsKEi5JHL2KO
W0ArgVR8LHpbLCcWpa+5d2EmACGkLVGkQKEFPXRJ7TYtwutVDZ3pTtbeXSqq
O2gd+OQQM6eUKNJEmKSV3px0dPqduit0yC3TnVMVQLyAjklkmCdigxBx27hf
3aZbpx+/2SZ7qDBRLSWhDyKx4jOyfiZnixO/pd5g3TWDuQkmiwK5mLh4+Vvd
iF0wsBDu8vPNuCRlfqMFn7UytGenhwF22zpsZR83K6uZF2cHRtiZoCFpbYt3
TomVqKipRbG6m/koSOzYHYe2tvVFCowKpZX1Ydp94XcRi9+9WFFUYy+6iHTo
1pnVKnTuSZahCggbbKvOE16VFzk/waQB3Z7DdrGkyzkWYL44XdF31z7mcoEW
O0+thRiu2nH2dAO8+7exQsXZVry52M8g+EN7K4APvUOOjsL8Giyxy8dNCNxs
n8eqNpielIOkrERHwrZrr/EcNLp77xInKU6nDBLmGs777pNKDZYpYbOhLZtM
lZFJbSveBpHGHCaUkzHh0omBMZ7XZufEoa5kxpzQPKtgC8Q2K17fjF2sZs/s
OZ2kFyOU5ZpmG3iQGQo3eVCXNAyNipEY+R0HyvxulWHKVjcYfCzVbNmiGYFa
qxYpBMKItBZf6KS0AaE9qkg1gVGWoGOr+GYx/z6Nd1CCkFU6VmIPkgRzpHje
hodTuqLaAoLIoN7exPXIaJ802IlZwFjcwqCAicmKJvqj9g5iMzjSy4JpG08o
OOt50qsuUULw0OgB2/0F/XHW93J4eWS/9QVHxXufDFeYcNuCrbrnoeYzeOJ2
uFQmhp1IHus/zChBgjc3iJrDDVIgZbcOsq73Lx627GYb1I1d2CL536fD0OCZ
eurQelpyyaPUwHQsLKu8wQRbSB4lxl8zz0OOWjgqeX1xIpTAcqYhR7Hv3WI9
NlKJtucjUvBNbbfOLo62Y4KCWNhmZLHm1hAPjhdJ3dY6mj5UDRq7HbA5b2pN
+57AGzeUfCZtRRBtYdSLETthq6NEyBtRawyx3skaKYa/CL5nbeW0NtyjJ1FV
u+BkFhvlg3dyVtj887ZeL2B5V+njADsPrgKLQYR+upj46YNril8+HrwVIEVW
rkTnMoSxOCoNr0DrLSZQDbXHAUUOo1Lh6HPuVMOqWYKsG79PKg4nnFCseDdN
IqUGIHUELG3UlCMJSpysspxMdVPctMiJ1okjfh0reVEnijiDSc1oVhIWD0Yu
eSAmFlFJwNrqyCFVwknrX1MjLQT6hJIUrN6lc4rUY+2cIqHUBUioKDj7gg1S
2Q4vKXeKxKMQmtAVkXwSGE7DPhdHvKyuMZ9pW/NDh1Ikxq9bEBnth7o6acEE
VdD2BIdVzXRkC8VRlJjobzc0p9QtaY3eA6SWhLmKHy5HUZek4VbuSxR6RKs7
eMsitotSqyWLISfy+0d3UFOYmRaOkZCN5hSNENBcuIOxaKGf7iNLb6LbXoyf
Sxgha0LfnI9O2EIbzXHLPx+dXWxL2C0FV3Js8pplHNtq6DN0+ZMawvVAaar2
C5z1cPe4j2+wHyaQkPycOIFtL7J8BPEGrY2saywkHV6IrEACVWZcNv4mc7cB
MXtKRABPUI4eEZFNMQhQdGGuSnTHfXPusQlvk1J1BTxyR+PqKHG/cXIA6If9
vfBd//Hv/1PuOfLX0Zv7B6AeIutpMKZxBiD+BV32dSY6tzGBklTLFg10zdHo
PnMEUT/yIhQ2yJ5gzzFzfpCK3cAiV2EvxnSOzuYmfnN+sk1ptopp6c1a6Ng4
4modz0clbEbTjrR+JY+hO0+3bZnaVKbxGS+RelNmk2wqTipf//jj16E0Qlrf
vxXtggP6gxP65+TJk9c//tj+71//lf9LWumqscvFeumSJxr+j9mpybYoFIYv
yUzSIXgyG5tfUnQ72RJxTZkVJofbPhVHfETM2LDjMiAPzIaiyac8N4F7F1h/
RD/A5yAnPPRwVW+r0t2AnIEaae69Y3lTOxu0TRpXWx6zUxqzWyI0uhkKaJLA
hrRfYoXayOqFofxyxBMSuWBR25rMZuQ+RrBpLHW4W+k1+WbCC1DoJZDJLF7r
YLRzz354KK69gORz4pFvIJKQEAtOcjFRMVVMZgrlv/v2mGJSVyCyOuACWtcZ
CQe05+Tmu8Nkj+WM/SEFgvuJ4z6I1KbNAbC3OHrBpNCC05Yr+VyuIcGs6cNg
EnoAKb8CKYv3wNtDggsl6pMf3u3EpLu65xKPdvkab/xvN+nvt/dAv70N/fYf
6Lff7TYej/vHev7s2f6ze8abz+G/zViou+VbEhK/u42oSQu7mC4bzmr4ewGS
IjqV7M7F3wO+BdzTWc42sRrsqkWGF3atxA/h3m6rqTlCobXcJS/GBLQnObcS
pHp/R9CFrzqvblWA8u+27w3IM8CgX1EbY6F4wbfiRbgVNli9czR6L+1B1KH0
3YYjEWzzxyKR336bdv3n33ab9h7qt+E27fvP//htoksUxvsdt2mPbhMlwyE/
jHY7U+UuQIClrAjlaJtoJ3Sy6Q0CrG+HoApvDe/wuuZFHdi01yzieUFiUzsb
DEHnPYwts+bG+aiBECBBrGIv230fefdEBt9GcRpFYwZlh6SyeyFbL0kbow3p
vGTcjRMkQcE4h4vmLJ2VS8lw1nfvSP2lUpzfuTg/E3mcToy0TFJkrJASDGLz
N1r+xFvQjFwcB556URt1axc+mdonnpvKnCCYXhydcrDPh4vvUOk8xZ5rkiHU
v+resNYe7VcprOyGsZOtU/j7WBR1u7uv0Alyg4/Pn8I+39Y0nvUdidTuH9Iv
2WK18PLHOR7B1ofzc3MjrFOkJ3DkbBjlqlbTms9hkU6vEVjYghvzJSyYnZwC
eKe2pkSxFt88itAK/jObUsWGUGxRGCiIwl6xstk/WchKKUfeIuMCoCinwXIv
vtv2VNXE8etKYJJIHBZZseJGT0eTNSql8LmEo/mEcVtvj863h4mN6pNXNpwF
BvCRn5TPivWGznh5ta5JUa9JH7r7IKKpt7hxgmXeap9Ax5JFWNxYKsSw5tHu
EawdtmWF+3Jh9+U72JftwG7sPtt9muCSmTxjJMQsrQzaoZ1gGIS2L03bl0/2
xrv/AqwvAPpM2o1F28TyRc3upzP367ZWfUuxMa6ADgzj9vCwUHOHfrOYSkN3
n3Af1qB0t4CKrAMfbhr6XNSSAkV2kZPoId1AXCCR55ixpdsZcxEUGPhc19KY
X82mbnPuuOQVubnyPHnaOH8Oas2K0JrsSOT9O6VaiDTiPCVNJO6wU8UMp0pH
xFGvKh/dZZzPfCGcOQxFls5c0SJhEx85KgygubL1fSjqL7APpZyRGDm5hi4L
yfA2jX3ZhBCEKY4SN3wAXOdyRJUYutzW9MHt9laMKjk5ppVrIHBU1ZdCdUTh
Q5pvoqec3i4UUIUOlY4liulw//wyvq7FVCPde3fFRDZ7F7Cel7A7DjlFnHor
J93fm6yik/a5OP372/72nABS3AfVb63brZYiRSins8M158fvrM8XVEYzwSXa
DG4pFleSAdLah7SLOvewHsTK3IzMlMZOkMNVEI7HHgxGbzTq/0pHNjHJjjS9
BbsG9rqueiA4Odx5e3IIUrKk5xlQgVdSxrNtD15undrl0CN6HEoIYWsdMmT8
8Zk38IQByOm4/IkylKl7s4UIKiGFDi9aggrpomhyCyRen0fG82PmKMMvWa8/
+EB1mA2tHGcUlcsS72Cyyr5RN+dWXQnTty/DEXY90cwhpAr7OiTjUNwiyV1R
1xTK18juv6kq2OxvNIHrz19hrjiHD+tfJOXri+dPbMpXOMIq47g7k+cCx6Ju
IRmsrdTUk4QiILo6TnEHD0URqLW8t8TdVJTJ1gF7GzNBeEURRRDlFVllUzZT
TXxUtrg4ADHFuKPkX8rzwcBUGWkxeAHtZFiSHGiklPxG/lY2WCm7b7vBEEqM
jRAZ8hnOStzCn3zskp0UM4V7T1+gU4/C7cPpE8I7AIXUcbIEippnAM0xDj8Y
oHGWCPOcLiRw5nQ4HKjH1z1sB50FutsoEulJSsKyA8Zo13g+EWuJNnJz+89Q
ob1I3hJRQyMQljZnez5aOqjatrPV5HnHPPZTpyG5e2qVJtFgRjtjChS+1YIa
3zOSFjkg2fr49vttfpkRe9yDaCfZysZu7BPSctnlEUpk24M01B5Dk+Y6rADE
WHl/Z2IA699/fAtQDRdJCQkr8L4Pf3GcDxHHUKNdHFeHyRWI49VNVqOVAyPU
UsHpOpwALatybPp1PH3SGMKuzUpKhzOnUuCcIMNJZlFO+EPbNIFrkesVxgmU
hWSdae1vyXH41ldjjo4avt4K3ndCbDYNmBcjw06Y8oBRhKJwV91rPHMgo82Y
aZZGRnSLKTa6FHhVt3qNA5q9yfLgYNV0nBZbjlY9wZfqVGzq7xHba7bWLNHs
spppTJEiziAJt3OZYrFAvQZSTt7g+E6EBVzrAfuz0MVeYc5/TMx6+l0szUr8
CqxPnJb+vsJ6ADiid5aXGhdtodhTKJItg1O5v1gmGapeKBQcOyUwKqou6pPx
hItjFzz0WSXs9rUL46FRBD7W4lZn89/pS23uQgsQraGEGZ/jjdZNMCDdyTvv
U84iDuD0vHb+HsTwheyAG7yEaAPJIEKRK9bpkJ3GjJuV59badcpaFM3H3dgb
wAkqUFwhrMuevBwf2C4GaJi2jyC2nzflUqt47bwNu4kR2PY86nCAJDDrbaC4
YHW8vKK8SThj9B/lpHoanegTLiJwlageOIj2UWRDE7HBqbQ3DsBeM8FvMwuJ
kTlgV0SjvpUCrTg/A8EV/jX54i1n7DNUWF6iMbksWtMhilgS0vFkly4LcdVW
39WpqyPGcc5vxFgJlj694ghYFC+FrVRa7X3XYzaetT/vgHenkHrkedOK46bR
+Q+ZDUcJvtG3asA2tAj1PLThHJGPrjUiYcL2CVIL6WjKbvkw9m3i7dXkGJgx
XZLnGhJJ+Rd8yg+XVrBP1XgQVxFkQIx8O8Ok7WAdXxIf2k0rpYxEPTwjZSX2
l6S9n8Bdo5jhRqzblLrKnVZb7862h4bd1sjKpy/2ntrIypfPOPegBpYlg0dn
3gZzzvzxo2QLI9Mx7WLNaYd91uFv+FBFBseP7Pz+9BW8ZTsZoH7KoQaeY7A4
OFLVsiAUVkUIenskc7dvJo2yiSdTaYsTnFDSrlAfyDKPPmVO5FMfCjiR6rus
jURee1S6qlkDcUR0ryZnmYynQbxvb4q9YFrtzoaMDnRq+iqJacbU6uLlh3M1
6Rx4JuI9T/DwsUTG7N2ZeB8ILTTLYwSBPnYSyhPCKjhio+L9/RMuBlWvxdeN
bwvPAB0pmjKIGDDVW68LZWfglnurDlHTGF2XNB9PA3PnCn2asgTVVchT9Z08
l2HsXCErtsnrnWvkpDWMDGVL4EtSrhPLIpwJkeJ88VbqaPMOJBK/RwWKohp8
9yYsji+R4D+/nZ1zMSkW5RxECIH9pSHOKR8JWaeEklIFaPa1l3nSgnOYl0Sw
BYJDKUtsurBWLTFSBXZ2mSN6ydll7oUHmP03Ea7mFIOI1XzO77UiDKMAYg6a
V9DzKg+KDEQmr6D6UQ/4JlCSEEk8pjMRddy7sxFNQZKj606isHAQ2B68r3Hu
tFWRtg8o4zjS3kOyc9TDilI0DHDZ787sfmiw8387eHsyTDAa4r/DGWXo6GwQ
79C7Du5vsw2muoklRLNqdsLULei/DyFTK0kh3X1X1bp0oxOWqlmcKlOMgJ0q
AKSBR5UinPM4+PGqDztSg6r2d/IdZ27rqX7FEWFNsIbCLuGbmNOYAkvq/X/U
0ZSo31eo8G0JxEhWRdtvzqaWYh1ox/TKPjjiDfA+vJ8dCmnvmGPRtF4ENQME
GylBoO6XtcHgIh0awNLkbEpeLLOvd4tgq5OPO6hD+arH4apW8hBFNgoq96zM
Zs5lo5Ey5hGjzLoB7/JlcnBvwh/sdrnh1QPZVVGotcsnMK1V31QDZvevpeeU
Uqo6x2ya8I54J2dVekv5+MWQrh5NA1MiztghqQQJi3hCQpluc55F9dKswk6c
nQmjoNFv72z9KfRziwg/iZpBYS8hyy3GKWCJ3TbzmYr5YcYhN8ONh1IWPQol
OlxU7G/mYwb/rxmZt0yNKJeRSLSG3HQxXP8qBEW8Nbm3iHsOCIIRghUcJUX0
fYSfazp28L6UHvJVSLrJ5LsDwuXmpZJgiCvdfFidRc971iWOykYNoXxOkme1
Bwlm9SMZ4RfZLdiPI3OpPoZLhdnRYeMkpypSpr4Z/IYFtJws+ou5/v61cAAa
liJNDt8ec9VEOLXBIH5Od+rZy5f76LYvKUejacbFtVVnseHiiFIuq7z9KRkc
e2EQ36fh+TgA4n1O01N7018s6cEuW3xvrJTsk93QVQU4u7x0bWEbWBXmZ7KC
PNGJYzQJvqjWpoZ9cHzK0alkHAnZD8nMgnnEWXpEfvzAuxHRFo7k9W7GL2bt
i87FR5MD2OS0hd7phlNCex9zLUpnBHMW4KROtpfXjMZTLSOhSJcm4eCynImS
iwXxFauQ2MsDAPGkUyCcpInXeL1QDsqghO750EGu0DDKuUOQt/wTxhZNTUEv
r2DUAIdASYlmdIKVbdK1oUhVavaVEFnK3ME77EmJpB9ofIaMr+v7xJevkIRQ
BY5uhIxltVB9zIlRSHVWuFtfuqPNEpqMsz6smLMhctIVHzq+ubYU3qDIwlsH
25aedqeYjHcaIxgJ2hcJUyM3HlTwP+Bf1dZq+8s2Fl2U6JA4cbYxMvj9uJRo
Zra5S9y1KlZePH1GlLuWtLCIAOPFk9LHDybZOaYSYuWVTsJvM9POYQgzjqWV
JLXuhoIYollKDmodW1lv+Y4KcLWisC6r8hZLegFjCr2WM8WrOOy5wN7BCl5I
2VEJelnT5K9+tV42JWCO5RXy+HHTjWZaOWsfJIoxapQsliL+fQalCqPsQGqg
SHZUXxHRUM8Eb7Y0bGqV1de4UJD0YCplZaKjsuJvNs2LzP8q+xvI0WRl+HD8
zCs4uGDBwsEYQeEQr06RM2qbJ6LihsufKk2hLI5Uo6Qob4fCHWdNKztztH+E
QG6BnqI0hgS1KrxPFTpHHZ2ODj4JNXu194ypGbl8xm15hX7nW8vwZliFE16H
D08GlgaNuVX7bPNLtDRfLWpNCYCeAgbcsNgeWeg7EHRK0Y7JeyqpO0BW1rtX
2AlxUKRU3u1UAZLqLmyn5jJIaVwECUMh1O8PIECL5eTrKOkeFbzUEkmm7o6Q
K82jSKokoIWmDLNNGDoebJ65loNKvW+hEgVpJ+YW1ncWLru8mjCzx/5m4gI0
0vTPCOiknEjnDvPbzdoLh4mNyvnIO4Rsffp0tm1T6/GF4dSe6INDWKTD1o+T
RAIVpOaHIfF2hXg0V1kz7C2ZFyihZtdQVJgGxZLU6HOvE1R5HRIkzDi3E78O
H6sO2z5Dt1fcAOCqqlQC6Elr9q/n7z+9w2LVBZuNDt0alu+T5JE2J27U67Hl
V8PZNsXdU1hRmT9FD8QMo7ptr2H/gzFXzyhKJZXcAzhd41NZtHjTFF0Y8vxP
wbiczdtKPuzRuzpKfUl4tr1hqrZqUjLmz6WWdiqpd3odRrTWkwVqVYJ4p47I
AU94VkoPpUDn0TlDpwlNEjc1wynOMF+QuM4wI8S4RjREySmR+1PGDpRjqVPZ
STDlifrfeS+uTnFsxTI4cUK5z3df7cX1mbCcLjJlWsuGcn5FQ5DLDRKXC38t
1B8pOBNRefL2vHwcnlct8q4H3Cf6Vk7z6TFaS7aQS45+jlj6T4vq+gJSePFM
lmDy+aFwteC/o7VMyfXNW4ddAb8Q62gy54Buxuw2UwERrcTV3vtHBnxOtVI3
BC728Ao9G4va0MA/sELSulrONvg0zapy2QK7TjEnEvIJdiNnpY3eWsRrnxx8
PHiAzxbbNLUUhAJdR6MRJXvFQQ6mGKsPEMIRJIOfXzORcrN/fjQHTpAiXQ+I
u6lFksPSJBKYUVwn3zrY3+QC2NwVfJECivhLel1Okm9c1vw0TN6X166+Sr6F
tkVKizqFK5scOuIcxEgAwi2Za1Ap5/ldNkbnwD6XWuSGiQVM0FXomwsiGua4
o8gEjYvC1SPDCVAhnCxPM7bVLF25FDcIZG3drY8Koc6SrV0dTubOzXC/XifH
sNTvyzUiwkN43Q8OsdX/BX7DthaQ7wAA

-->

</rfc>

