<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<?rfc comments="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-idr-bgp4-rfc4271bis-06" category="std" consensus="true" submissionType="IETF" obsoletes="4271, 4486, 5492, 6286, 6608, 6793, 8212, 9072, 9687" updates="7606, 7607, 9774" tocDepth="4" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="BGP-4">A Border Gateway Protocol 4 (BGP-4)</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp4-rfc4271bis-06"/>
    <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
      <organization>Retired</organization>
      <address>
        <email>yakov@juniper.net</email>
      </address>
    </author>
    <author initials="T." surname="Li" fullname="Tony Li">
      <organization>HPE</organization>
      <address>
        <email>tony.li@tony.li</email>
      </address>
    </author>
    <author initials="S." surname="Hares" fullname="Susan Hares">
      <organization>Huawei</organization>
      <address>
        <email>skh@ndzh.com</email>
      </address>
    </author>
    <author initials="J." surname="Scudder" fullname="John Scudder" role="editor">
      <organization>HPE</organization>
      <address>
        <email>jgs@hpe.com</email>
      </address>
    </author>
    <date year="2026"/>
    <area>rtg</area>
    <workgroup>idr</workgroup>
    <keyword>BGP-4</keyword>
    <keyword>routing</keyword>
    <abstract>
      <?line 109?>
<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 4271 and many other RFCs. It updates
RFC 7606, RFC 7607 and RFC 9774 by subsuming their functionality as 
relates to RFC 4271.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-idr-bgp4-rfc4271bis/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        IDR 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/ietf-wg-idr/RFC4271bis"/>.</t>
    </note>
  </front>
  <middle>
    <?line 132?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The Border Gateway Protocol (BGP) is an inter-Autonomous System
routing protocol. This version of BGP, BGP-4, was first documented
in <xref target="RFC1771"/>, which was superseded by <xref target="RFC4271"/>, which in 
turn is obsoleted by this document.</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) <xref target="RFC1518"/> <xref target="RFC1519"/>.  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>Routing information exchanged via the procedures documented here supports
only the destination-based forwarding paradigm, which assumes that a router
forwards a packet based solely on the destination address carried in the IP
header of the packet.  This, in turn, reflects the set of policy decisions
that can (and cannot) be enforced using BGP.  BGP can support only those
policies conforming to the destination-based forwarding paradigm.</t>
      <t>Since its first publication, BGP-4 has been extended by many other
specifications. Notable extensions include <xref target="RFC4760"/>, which generalizes
BGP-4 to allow support for advertising routing information of address
families beyond IP Version 4 as documented in the present specification, and
IP Version 6 in particular.</t>
      <section anchor="definitions">
        <name>Definition of Commonly Used Terms</name>
        <t>This section provides definitions for terms that have a specific
meaning to the BGP protocol and that are used throughout the text.</t>
        <dl>
          <dt>Adj-RIB-In:</dt>
          <dd>
            <t>The Adj-RIBs-In contain unprocessed routing information that 
has been advertised to the local BGP speaker by its peers.</t>
          </dd>
          <dt>Adj-RIB-Out:</dt>
          <dd>
            <t>The Adj-RIBs-Out contain the routes for advertisement to specific 
peers by means of the local speaker's UPDATE messages.</t>
          </dd>
          <dt>AFI:</dt>
          <dd>
            <t>Address Family Identifier, as defined in <xref target="RFC4760"/>. Often used
in conjunction with SAFI (q.v.) as "AFI/SAFI", which collectively
are, in effect, the type code that defines an NLRI encoding in 
RFC 4760.</t>
          </dd>
          <dt>Autonomous System (AS):</dt>
          <dd>
            <t>The classic definition of an Autonomous System is a set of routers
under a single technical administration, using an interior gateway
protocol (IGP) and common metrics to determine how to route
packets within the AS, and using an inter-AS routing protocol to
determine how to route packets to other ASes.  Since this classic
definition was developed, it has become common for a single AS to
use several IGPs and, sometimes, several sets of metrics within an
AS.  The use of the term Autonomous System stresses the fact that,
even when multiple IGPs and metrics are used, the administration
of an AS appears to other ASes to have a single coherent interior
routing plan, and presents a consistent picture of the
destinations that are reachable through it.</t>
          </dd>
          <dt>BGP Identifier:</dt>
          <dd>
            <t>A 4-octet, unsigned, non-zero integer that should be unique within 
an AS.  The value of the BGP Identifier for a BGP speaker is
determined on startup and is the same for every local interface and
every BGP peer.</t>
          </dd>
          <dt>BGP speaker:</dt>
          <dd>
            <t>A router that implements BGP.</t>
          </dd>
          <dt>EBGP:</dt>
          <dd>
            <t>External BGP (BGP connection between external peers).</t>
          </dd>
          <dt>Export Policy:</dt>
          <dd>
            <t>A local policy to be applied in selecting the information contained
in the Adj-RIBs-Out. As described in <xref target="rib"/>, the Adj-RIBs-Out
contain information that has been selected for advertisement to other
BGP speakers.</t>
          </dd>
          <dt>External peer:</dt>
          <dd>
            <t>Peer that is in a different Autonomous System than the local
system.</t>
          </dd>
          <dt>Feasible route:</dt>
          <dd>
            <t>An advertised route that is available for use by the recipient.</t>
          </dd>
          <dt>IBGP:</dt>
          <dd>
            <t>Internal BGP (BGP connection between internal peers).</t>
          </dd>
          <dt>Internal peer:</dt>
          <dd>
            <t>Peer that is in the same Autonomous System as the local system.</t>
          </dd>
          <dt>IGP:</dt>
          <dd>
            <t>Interior Gateway Protocol - a routing protocol used to exchange
routing information among routers within a single Autonomous
System.</t>
          </dd>
          <dt>Import Policy:</dt>
          <dd>
            <t>A local policy to be applied to the information contained in the
Adj-RIBs-In. As described in <xref target="rib"/>, the Adj-RIBs-In contain
information learned from other BGP speakers, and the application of
the Import Policy results in the routes that will be considered in
the Decision Process by the local BGP speaker.</t>
          </dd>
          <dt>Legacy IPv4 Encoding:</dt>
          <dd>
            <t>Although this protocol can encode information about many different
address families, IPv4 (uniquely among all address families) has two
encodings available. The encoding specified in this document, which
places IPv4 prefixes in the Withdrawn Routes or Network Layer 
Reachability Information fields of the UPDATE message, is referred
to as the "legacy IPv4 encoding". Its use is discouraged; 
the preferred encoding is that specified in <xref target="RFC4760"/>.</t>
          </dd>
          <dt>Loc-RIB:</dt>
          <dd>
            <t>The Loc-RIB contains the routes that have been selected by the
local BGP speaker's Decision Process.</t>
          </dd>
          <dt>MP_REACH_NLRI:</dt>
          <dd>
            <t/>
          </dd>
          <dt>MP_UNREACH_NLRI:</dt>
          <dd>
            <t>Path attributes defined in <xref target="RFC4760"/> to allow NLRI of any 
AFI/SAFI (q.v.) to be announced and withdrawn, as well as 
next hops of any AFI/SAFI.</t>
          </dd>
          <dt>NLRI:</dt>
          <dd>
            <t>Network Layer Reachability Information. When used without 
modification, one of the IP address prefixes carried in the NLRI 
field of an UPDATE message. When the NLRI field itself is intended, 
it is written as such.</t>
          </dd>
          <dt>Recognized:</dt>
          <dd>
            <t>A path attribute, or other message type or part identified by a type
code, is said to be "recognized" if the local implementation
contains support for processing it according to its type code.</t>
          </dd>
          <dt>Route:</dt>
          <dd>
            <t>A unit of information that pairs a set of destinations with the
attributes of a path to those destinations.  The set of
destinations are systems whose IP addresses are contained in one
IP address prefix carried in the Network Layer Reachability
Information (NLRI) field of an UPDATE message.  The path is the 
information reported in the path attributes field of the same
UPDATE message.</t>
          </dd>
          <dt>RIB:</dt>
          <dd>
            <t>Routing Information Base.</t>
          </dd>
          <dt>SAFI:</dt>
          <dd>
            <t>Subsequent Address Family Identifier, as defined in <xref target="RFC4760"/>. 
Often used in conjunction with AFI (q.v.) as "AFI/SAFI", which
collectively are, in effect, the type code that defines an NLRI
encoding in RFC 4760.</t>
          </dd>
          <dt>Unfeasible route:</dt>
          <dd>
            <t>A previously advertised feasible route that is no longer available
for use.</t>
          </dd>
          <dt>Unrecognized:</dt>
          <dd>
            <t>See Recognized.</t>
          </dd>
        </dl>
      </section>
      <section anchor="specification-of-requirements">
        <name>Specification of Requirements</name>
        <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
        <?line -18?>

</section>
    </section>
    <section anchor="roadmap">
      <name>Roadmap</name>
      <t>TODO: This section is a work in progress. It's intended to become the
roadmap mentioned in GitHub issue #58.</t>
      <t>This document is the keystone in the Internet Standard TBD_STD_NUMBER,
but that Internet Standard includes other documents as well. The reader
should consider all documents that are part of that standard to be
required parts of a useful BGP implementation.</t>
      <t>Beyond that, the BGP protocol is made up of both this base
specification, and a multitude of other specifications that extend and
modify it. In the nature of things, the set of documents the reader
needs to consult to have a complete picture of the protocol will change
over time, but at time of writing the documents mentioned here were 
important to be aware of.</t>
      <t>The reader should also consult the "updated by" metadata, available at
time of writing at this document's IETF Datatracker page.</t>
      <section anchor="core-extensions">
        <name>Core Extensions</name>
        <t>Extensions listed in this section form part of the base BGP protocol at time
of writing. Because the document set that is considered core will change over
time, readers should consult TBD_STD_NUMBER for the current list of those 
documents that form part of the standard.</t>
        <dl>
          <dt><xref target="RFC4760"/>:</dt>
          <dd>
            <t>This document extends BGP to provide multiprotocol support.
The original BGP protocol, documented in the present specification,
supports only IPv4 routing. Support for RFC 4760 is required in
order to support IPv6 routing, and other useful features as well.
Even though RFC 4760 remains a separate document, AFI, SAFI, and
the MP_REACH_NLRI and MP_UNREACH_NLRI attributes are discussed 
herein because they are integral to the error handling procedures
in <xref target="errorhandling"/>.</t>
          </dd>
          <dt><xref target="RFC6793"/>:</dt>
          <dd>
            <t>This document extends BGP to provide support for four octet 
autonomous system numbers. The present specification documents
only the original two octet format, but references RFC 6793 
where relevant. Implementors should be aware that four octet
support is considered the preferred mode of operation, while the
two octet mode documented here is for backward compatibility.</t>
          </dd>
        </dl>
        <!-- Editor's note: This section is here because I moved the Acknowledgements to
the end, which is the more normal place - but that results in all the
sections being renumbered, and I would prefer that Section 9 remain Section
9, it's stuck in my head that way. Perhaps we can put something up front
here that's relevant, like a short discussion of what's changed since 4271
(not a changelog though... an overview?) and/or a discussion of why it
should be an Internet Standard. -->

</section>
      <section anchor="other-extensions">
        <name>Other Extensions</name>
        <t>Many other extensions have been standardized. Some are referenced from 
this document, where they interact with this specification in ways that
the reader should be alerted of. This is not a complete listing of BGP
extensions even at time of writing.</t>
        <dl>
          <dt><xref target="RFC8654"/>:</dt>
          <dd>
            <t>This document extends BGP to provides message sizes of up to
65,535 bytes, increased from the 4,096 bytes specified here. 
Although it is considered optional for purposes of the core 
protocol, some other extensions either strongly advise, or require,
its use.</t>
          </dd>
        </dl>
      </section>
    </section>
    <section anchor="summary-of-operation">
      <name>Summary of Operation</name>
      <t>The Border Gateway Protocol (BGP) is an inter-Autonomous System
routing protocol.  It is built on experience gained with EGP (as
defined in <xref target="RFC904"/>) and EGP usage in the NSFNET Backbone (as
described in <xref target="RFC1092"/> and <xref target="RFC1093"/>).  For more BGP-related
information, see <xref target="RFC1772"/>, <xref target="RFC1930"/>, <xref target="RFC1997"/>, and <xref target="RFC2858"/>.</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, from which routing loops may be pruned, and, at the AS
level, some policy decisions may be enforced.</t>
      <t>In the context of this document, we assume that a BGP speaker
advertises to its peers only those routes that it uses itself (in
this context, a BGP speaker is said to "use" a BGP route if it is the
most-preferred BGP route and is used in forwarding).  All other cases
are outside the scope of this document.</t>
      <t>In the context of this document, the term "IP address" refers to an
IP Version 4 address <xref target="RFC791"/>.</t>
      <t>The functionality documented in this specification supports the
destination-based forwarding paradigm, which assumes that a router forwards
a packet based solely on the destination address carried in the IP header of
the packet. BGP as documented herein can support any policy conforming to
the destination-based forwarding paradigm. Some policies cannot be supported
by the destination-based forwarding paradigm, and thus require techniques
such as source routing (aka explicit routing) to be enforced. Many
extensions to BGP exist, which may enable such policies. These extensions
are beyond the scope of this document.</t>
      <t>BGP-4 provides a set of mechanisms for supporting Classless
Inter-Domain Routing (CIDR) <xref target="RFC1518"/> <xref target="RFC1519"/>.  These mechanisms
include support for advertising a set of destinations as an IP prefix
and eliminating the concept of a network "class" within BGP.  BGP-4
also includes mechanisms that allow aggregation of routes.</t>
      <t>This document uses the term 'Autonomous System' (AS) throughout.  The
classic definition of an Autonomous System is a set of routers under
a single technical administration, using an interior gateway protocol
(IGP) and common metrics to determine how to route packets within the
AS, and using an inter-AS routing protocol to determine how to route
packets to other ASes.  Since this classic definition was developed,
it has become common for a single AS to use several IGPs and,
sometimes, several sets of metrics within an AS.  The use of the term
Autonomous System stresses the fact that, even when multiple IGPs and
metrics are used, the administration of an AS appears to other ASes
to have a single coherent interior routing plan and presents a
consistent picture of the destinations that are reachable through it.</t>
      <t>BGP uses TCP <xref target="RFC793"/> as its transport protocol.  This eliminates the
need to implement explicit update fragmentation, retransmission,
acknowledgement, and sequencing.  BGP listens on TCP port 179.  The
error notification mechanism used in BGP assumes that TCP supports a
"graceful" close (i.e., that all outstanding data will be delivered
before the connection is closed).</t>
      <t>A TCP connection is formed between two systems.  They exchange
messages to open and confirm the connection parameters.</t>
      <t>The initial data flow (sometimes called "initial convergence") 
is the portion of the BGP routing table that is
allowed by the export policy, called the Adj-Ribs-Out (see <xref target="rib"/>).
Incremental updates are sent as the routing tables change.  BGP does
not require a periodic refresh of the routing table.  To allow local
policy changes to have the correct effect without resetting any BGP
connections, a BGP speaker <bcp14>SHOULD</bcp14> either (a) retain the current
version of the routes advertised to it by all of its peers for the
duration of the connection, or (b) make use of the Route Refresh
extension <xref target="RFC2918"/>.</t>
      <t>KEEPALIVE messages are normally sent periodically to ensure that the
connection is live.  NOTIFICATION messages are sent in response to fatal
errors or special conditions.  If a connection encounters a fatal error
condition, a NOTIFICATION message is sent, and the connection is closed.
For error conditions classified as non-fatal, less extreme mitigations
are applied.</t>
      <t>A peer in a different AS is referred to as an external peer, while a
peer in the same AS is referred to as an internal peer.  Internal BGP
and external BGP are commonly abbreviated as IBGP and EBGP.</t>
      <t>If a particular AS has multiple BGP speakers and is providing transit
service for other ASes, then care must be taken to ensure a
consistent view of routing within the AS.  A consistent view of the
interior routes of the AS is provided by the IGP used within the AS.
For the purpose of this document, it is assumed that a consistent
view of the routes exterior to the AS is provided by having all BGP
speakers within the AS maintain IBGP with each other.</t>
      <t>This document specifies the base behavior of the BGP protocol.  This
behavior can be, and is, modified by extension specifications.  When
the protocol is extended, the new behavior is fully documented in the
extension specifications.</t>
      <section anchor="routes_adv_store">
        <name>Routes: Advertisement and Storage</name>
        <t>For the purpose of this protocol, a route is defined as a unit of
information that pairs a set of destinations with the attributes of a
path to those destinations.  The set of destinations are systems
whose IP addresses are contained in one IP address prefix that is
carried in the Network Layer Reachability Information (NLRI) field of
an UPDATE message, and the path is the information reported in the
path attributes field of the same UPDATE message.</t>
        <t>Routes are advertised between BGP speakers in UPDATE messages.
Multiple routes that have the same path attributes can be advertised
in a single UPDATE message by including multiple prefixes in the NLRI
field of the UPDATE message.</t>
        <t>Routes are stored in the Routing Information Bases (RIBs): namely,
the Adj-RIBs-In, the Loc-RIB, and the Adj-RIBs-Out, as described in
<xref target="rib"/>.</t>
        <t>If a BGP speaker chooses to advertise a previously received route, it
may add to, or modify, the path attributes of the route before
advertising it to a peer. In some cases, such operations are required.</t>
        <t>BGP provides mechanisms by which a BGP speaker can inform its peers
that a previously advertised route is no longer available for use.
There are three methods by which a given BGP speaker can indicate
that a route has been withdrawn from service:</t>
        <ol spacing="normal" type="%c)"><li>
            <t>the IP prefix that expresses the destination for a previously
 advertised route can be advertised in the Withdrawn Routes
 field in the UPDATE message, thus marking the associated route
 as being no longer available for use,</t>
          </li>
          <li>
            <t>a replacement route with the same NLRI can be advertised, or</t>
          </li>
          <li>
            <t>the BGP speaker connection can be closed, which implicitly
 removes all routes the pair of speakers had advertised to each
 other from service.</t>
          </li>
        </ol>
        <t>Changing the attribute(s) of a route is accomplished by advertising a
replacement route.  The replacement route carries new (changed)
attributes and has the same address prefix as the original route.</t>
      </section>
      <section anchor="rib">
        <name>Routing Information Base</name>
        <t>The Routing Information Base (RIB) within a BGP speaker consists of
three distinct parts:</t>
        <ol group="ribparts" spacing="normal" type="%c)"><li>
            <t>Adj-RIBs-In: 
 The Adj-RIBs-In store routing information learned
 from inbound UPDATE messages that were received from other BGP
 speakers.  Their contents represent routes that are available
 as input to the Decision Process.</t>
          </li>
          <li>
            <t>Loc-RIB: 
 The Loc-RIB contains the local routing information the
 BGP speaker selected by applying its local policies to the
 routing information contained in its Adj-RIBs-In.  These are
 the routes that will be used by the local BGP speaker.  The
 next hop for each of these routes must be resolvable via the
 local BGP speaker's Routing Table.</t>
          </li>
          <li>
            <t>Adj-RIBs-Out: 
 The Adj-RIBs-Out store information the local BGP
 speaker selected for advertisement to its peers.  The routing
 information stored in the Adj-RIBs-Out will be carried in the
 local BGP speaker's UPDATE messages and advertised to its
 peers.</t>
          </li>
        </ol>
        <t>In summary, the Adj-RIBs-In contain unprocessed routing information
that has been advertised to the local BGP speaker by its peers; the
Loc-RIB contains the routes that have been selected by the local BGP
speaker's Decision Process; and the Adj-RIBs-Out organize the routes
for advertisement to specific peers (by means of the local speaker's
UPDATE messages).</t>
        <t>Although the conceptual model distinguishes between Adj-RIBs-In,
Loc-RIB, and Adj-RIBs-Out, this neither implies nor requires that an
implementation must maintain three separate copies of the routing
information.  The choice of implementation (for example, 3 copies of
the information vs 1 copy with pointers) is not constrained by the
protocol.</t>
        <t>Routing information that the BGP speaker uses to forward packets (or
to construct the forwarding table used for packet forwarding) is
maintained in the Routing Table.  The Routing Table accumulates
routes to directly connected networks, static routes, routes learned
from the IGP protocols, and routes learned from BGP.  Whether a
specific BGP route should be installed in the Routing Table, and
whether a BGP route should override a route to the same destination
installed by another source, is a local policy decision, and is not
specified in this document.  In addition to actual packet forwarding,
the Routing Table is used for resolution of the next-hop addresses
specified in BGP updates (see <xref target="nexthop"/>).</t>
      </section>
    </section>
    <section anchor="invariants">
      <name>Protocol Invariants</name>
      <t>The following requirements apply throughout this specification.</t>
      <section anchor="own-asn">
        <name>Autonomous System Numbers</name>
        <t>Each BGP speaker belongs to an Autonomous System (AS) and <bcp14>SHALL</bcp14> be
configured with an Autonomous System number.
<!-- xxx this is probably a place to mention AS transition 
mechanisms where the speaker has more than one AS -->
        </t>
        <t>The configured Autonomous System number <bcp14>MUST NOT</bcp14> be 0.
 
Unless explicitly specified otherwise, any occurrence of an Autonomous
System number (or any of its synonyms) in this specification refers to
an Autonomous System number other than 0.</t>
      </section>
      <section anchor="astrans">
        <name>AS_TRANS</name>
        <t>The value AS_TRANS is used in backward compatibility procedures
involving 2-octet Autonomous System number encodings. IANA has
registered the value 23456 for AS_TRANS in its registry "Autonomous System
(AS) Numbers".</t>
        <!-- other candidates:

 "its IP address"
 version number
 max message size
 bgp identifier
-->

</section>
    </section>
    <section anchor="msgformat">
      <name>Message Formats</name>
      <t>This section describes message formats used by BGP.</t>
      <t>BGP messages are sent over TCP connections.  A message is processed only
after it is entirely received.  The maximum message size is 4096 octets
(although <xref target="RFC8654"/>, if used, modifies the maximum for message types
other than OPEN and KEEPALIVE).  All implementations are required to
support this maximum message size.  The smallest message that may be
sent consists of a BGP header without a data portion (19 octets).</t>
      <t>All multi-octet fields are in network byte order.</t>
      <section anchor="message-header-format">
        <name>Message Header Format</name>
        <t>Each message has a fixed-size header.  There may or may not be a data
portion following the header, depending on the message type.  The
layout of the fields is shown below:</t>
        <figure>
          <name>Message Header Format</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="240" width="528" viewBox="0 0 528 240" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,64 L 8,224" fill="none" stroke="black"/>
                <path d="M 264,192 L 264,224" fill="none" stroke="black"/>
                <path d="M 392,192 L 392,224" fill="none" stroke="black"/>
                <path d="M 520,64 L 520,192" fill="none" stroke="black"/>
                <path d="M 8,64 L 520,64" fill="none" stroke="black"/>
                <path d="M 8,192 L 520,192" fill="none" stroke="black"/>
                <path d="M 8,224 L 392,224" fill="none" stroke="black"/>
                <g class="text">
                  <text x="16" y="36">0</text>
                  <text x="176" y="36">1</text>
                  <text x="336" y="36">2</text>
                  <text x="496" y="36">3</text>
                  <text x="16" y="52">0</text>
                  <text x="32" y="52">1</text>
                  <text x="48" y="52">2</text>
                  <text x="64" y="52">3</text>
                  <text x="80" y="52">4</text>
                  <text x="96" y="52">5</text>
                  <text x="112" y="52">6</text>
                  <text x="128" y="52">7</text>
                  <text x="144" y="52">8</text>
                  <text x="160" y="52">9</text>
                  <text x="176" y="52">0</text>
                  <text x="192" y="52">1</text>
                  <text x="208" y="52">2</text>
                  <text x="224" y="52">3</text>
                  <text x="240" y="52">4</text>
                  <text x="256" y="52">5</text>
                  <text x="272" y="52">6</text>
                  <text x="288" y="52">7</text>
                  <text x="304" y="52">8</text>
                  <text x="320" y="52">9</text>
                  <text x="336" y="52">0</text>
                  <text x="352" y="52">1</text>
                  <text x="368" y="52">2</text>
                  <text x="384" y="52">3</text>
                  <text x="400" y="52">4</text>
                  <text x="416" y="52">5</text>
                  <text x="432" y="52">6</text>
                  <text x="448" y="52">7</text>
                  <text x="464" y="52">8</text>
                  <text x="480" y="52">9</text>
                  <text x="496" y="52">0</text>
                  <text x="512" y="52">1</text>
                  <text x="252" y="148">Marker</text>
                  <text x="116" y="212">Length</text>
                  <text x="332" y="212">Type</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                                                               +
|                                                               |
+                                                               +
|                           Marker                              |
+                                                               +
|                                                               |
+-------------------------------+---------------+---------------+
|          Length               |      Type     |
+-------------------------------+---------------+
]]></artwork>
          </artset>
        </figure>
        <dl>
          <dt>Marker:</dt>
          <dd>
            <t>This 16-octet field is included for compatibility; it <bcp14>MUST</bcp14> be
set to all ones.</t>
          </dd>
          <dt>Length:</dt>
          <dd>
            <t>This 2-octet unsigned integer indicates the total length of the
message, including the header in octets.  Thus, it allows one
to locate the (Marker field of the) next message in the TCP
stream.  The value of the Length field <bcp14>MUST</bcp14> always be at least
19 and no greater than 4096, and <bcp14>MAY</bcp14> be further constrained,
depending on the message type.  "padding" of extra data after
the message is not allowed.  Therefore, the Length field <bcp14>MUST</bcp14>
have the smallest value required, given the rest of the
message. (<xref target="RFC8654"/>, if used, modifies the maximum for 
message types other than OPEN and KEEPALIVE.)</t>
          </dd>
          <dt>Type:</dt>
          <dd>
            <t>This 1-octet unsigned integer indicates the type code of the
message.  This document defines the following type codes:</t>
          </dd>
          <dt/>
          <dd>
            <ol spacing="normal" type="1"><li>
                <t>OPEN</t>
              </li>
              <li>
                <t>UPDATE</t>
              </li>
              <li>
                <t>NOTIFICATION</t>
              </li>
              <li>
                <t>KEEPALIVE</t>
              </li>
            </ol>
          </dd>
          <dt/>
          <dd>
            <t><xref target="RFC2918"/> defines one more type code.</t>
          </dd>
        </dl>
      </section>
      <section anchor="openfmt">
        <name>OPEN Message Format</name>
        <t>After a TCP connection is established, the first message sent by each
side is an OPEN message.  If the OPEN message is acceptable, a
KEEPALIVE message confirming the OPEN is sent back.</t>
        <t>In addition to the fixed-size BGP header, the OPEN message contains
the following fields:</t>
        <figure>
          <name>OPEN Message Format (non-extended variant)</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="304" width="528" viewBox="0 0 528 304" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,64 L 8,288" fill="none" stroke="black"/>
                <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                <path d="M 136,192 L 136,224" fill="none" stroke="black"/>
                <path d="M 264,96 L 264,160" fill="none" stroke="black"/>
                <path d="M 520,160 L 520,192" fill="none" stroke="black"/>
                <path d="M 520,224 L 520,288" fill="none" stroke="black"/>
                <path d="M 8,64 L 136,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 264,96" fill="none" stroke="black"/>
                <path d="M 8,128 L 264,128" fill="none" stroke="black"/>
                <path d="M 8,160 L 520,160" fill="none" stroke="black"/>
                <path d="M 8,192 L 520,192" fill="none" stroke="black"/>
                <path d="M 8,224 L 520,224" fill="none" stroke="black"/>
                <path d="M 8,288 L 520,288" fill="none" stroke="black"/>
                <g class="text">
                  <text x="16" y="36">0</text>
                  <text x="176" y="36">1</text>
                  <text x="336" y="36">2</text>
                  <text x="496" y="36">3</text>
                  <text x="16" y="52">0</text>
                  <text x="32" y="52">1</text>
                  <text x="48" y="52">2</text>
                  <text x="64" y="52">3</text>
                  <text x="80" y="52">4</text>
                  <text x="96" y="52">5</text>
                  <text x="112" y="52">6</text>
                  <text x="128" y="52">7</text>
                  <text x="144" y="52">8</text>
                  <text x="160" y="52">9</text>
                  <text x="176" y="52">0</text>
                  <text x="192" y="52">1</text>
                  <text x="208" y="52">2</text>
                  <text x="224" y="52">3</text>
                  <text x="240" y="52">4</text>
                  <text x="256" y="52">5</text>
                  <text x="272" y="52">6</text>
                  <text x="288" y="52">7</text>
                  <text x="304" y="52">8</text>
                  <text x="320" y="52">9</text>
                  <text x="336" y="52">0</text>
                  <text x="352" y="52">1</text>
                  <text x="368" y="52">2</text>
                  <text x="384" y="52">3</text>
                  <text x="400" y="52">4</text>
                  <text x="416" y="52">5</text>
                  <text x="432" y="52">6</text>
                  <text x="448" y="52">7</text>
                  <text x="464" y="52">8</text>
                  <text x="480" y="52">9</text>
                  <text x="496" y="52">0</text>
                  <text x="512" y="52">1</text>
                  <text x="72" y="84">Version</text>
                  <text x="36" y="116">My</text>
                  <text x="76" y="116">Legacy</text>
                  <text x="148" y="116">Autonomous</text>
                  <text x="220" y="116">System</text>
                  <text x="116" y="148">Hold</text>
                  <text x="156" y="148">Time</text>
                  <text x="224" y="180">BGP</text>
                  <text x="284" y="180">Identifier</text>
                  <text x="32" y="212">Opt</text>
                  <text x="68" y="212">Parm</text>
                  <text x="104" y="212">Len</text>
                  <text x="148" y="260">Optional</text>
                  <text x="228" y="260">Parameters</text>
                  <text x="316" y="260">(variable)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|    Version    |
+---------------+-+-+-+-+-+-+-+-+
|  My Legacy Autonomous System  |
+-------------------------------+
|           Hold Time           |
+-------------------------------+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         BGP Identifier                        |
+---------------+-----------------------------------------------+
| Opt Parm Len  |
+---------------+-----------------------------------------------+
|                                                               |
|             Optional Parameters (variable)                    |
|                                                               |
+---------------------------------------------------------------+
]]></artwork>
          </artset>
        </figure>
        <dl>
          <dt>Version:</dt>
          <dd>
            <t>This 1-octet unsigned integer indicates the protocol version
number of the message.  The current BGP version number is 4.</t>
          </dd>
          <dt>My Legacy Autonomous System:</dt>
          <dd>
            <t>This is a 2-octet unsigned integer present for backward 
compatibility with older editions of the protocol. If the Autonomous
System number of the sender can be represented in 16 bits (in other
words, if its value is 65,535 or less), that value is placed in this
field. Otherwise (if the value is greater than 65,535), the value
AS_TRANS (<xref target="astrans"/>) is placed in this field. This field is
ignored on receipt; the actual value of the sender's Autonomous
System number is found in the "4-octet AS number capability"
(<xref target="as4byte"/>). An exception applies when backward compatibility
procedures are in use with a peer that does not support 4-octet AS
numbers; see <xref target="as2byteopen"/> for details. The value <bcp14>MUST NOT</bcp14> be 0.</t>
          </dd>
          <dt>Hold Time:</dt>
          <dd>
            <t>This 2-octet unsigned integer indicates the number of seconds
the sender proposes for the value of the Hold Timer.  Upon
receipt of an OPEN message, a BGP speaker <bcp14>MUST</bcp14> calculate the
value of the Hold Timer by using the smaller of its configured
Hold Time and the Hold Time received in the OPEN message.  The
Hold Time <bcp14>MUST</bcp14> be either zero or at least three seconds.  An
implementation <bcp14>MAY</bcp14> reject connections on the basis of the Hold
Time.  The calculated value indicates the maximum number of
seconds that may elapse between the receipt of successive
KEEPALIVE and/or UPDATE messages from the sender.</t>
          </dd>
          <dt>BGP Identifier:</dt>
          <dd>
            <t>This 4-octet unsigned integer indicates the BGP Identifier of
the sender.  A given BGP speaker sets the value of its BGP
Identifier to a valid BGP Identifier. The value of the BGP
Identifier is determined upon startup and is the same for every
local interface and BGP peer.</t>
          </dd>
          <dt>Optional Parameters Length:</dt>
          <dd>
            <t>This 1-octet unsigned integer indicates the total length of the
Optional Parameters field in octets.  If the value of this
field is zero, no Optional Parameters are present. If the 
length of the parameters to be encoded exceeds 255 octets, the 
extended variant (<xref target="openfmt-ext"/>) is used instead.</t>
          </dd>
          <dt>Optional Parameters:</dt>
          <dd>
            <t>This field contains a list of optional parameters, in which
each parameter is encoded as a &lt;Parameter Type, Parameter
Length, Parameter Value&gt; triplet. If the length of the 
parameters to be encoded exceeds 255 octets, the extended
variant (<xref target="openfmt-ext"/>) is used instead.</t>
          </dd>
        </dl>
        <figure>
          <name>Optional Parameters (non-extended variant)</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="128" width="496" viewBox="0 0 496 128" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,64 L 8,96" fill="none" stroke="black"/>
                <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                <path d="M 264,64 L 264,96" fill="none" stroke="black"/>
                <path d="M 8,64 L 328,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 328,96" fill="none" stroke="black"/>
                <g class="text">
                  <text x="16" y="36">0</text>
                  <text x="176" y="36">1</text>
                  <text x="16" y="52">0</text>
                  <text x="32" y="52">1</text>
                  <text x="48" y="52">2</text>
                  <text x="64" y="52">3</text>
                  <text x="80" y="52">4</text>
                  <text x="96" y="52">5</text>
                  <text x="112" y="52">6</text>
                  <text x="128" y="52">7</text>
                  <text x="144" y="52">8</text>
                  <text x="160" y="52">9</text>
                  <text x="176" y="52">0</text>
                  <text x="192" y="52">1</text>
                  <text x="208" y="52">2</text>
                  <text x="224" y="52">3</text>
                  <text x="240" y="52">4</text>
                  <text x="256" y="52">5</text>
                  <text x="340" y="68">..</text>
                  <text x="48" y="84">Parm.</text>
                  <text x="92" y="84">Type</text>
                  <text x="168" y="84">Parm.</text>
                  <text x="220" y="84">Length</text>
                  <text x="320" y="84">Parameter</text>
                  <text x="384" y="84">Value</text>
                  <text x="452" y="84">(variable)</text>
                  <text x="340" y="100">..</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
     0                   1
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...
    |  Parm. Type   | Parm. Length  |  Parameter Value (variable)
    +---------------+---------------+-------...
]]></artwork>
          </artset>
        </figure>
        <ul empty="true">
          <li>
            <t>Parameter Type is a one octet field that unambiguously identifies 
  individual parameters.  Parameter Length is a one octet field that
  contains the length of the Parameter Value field in octets.  Parameter
  Value is a variable length field that is interpreted according to the
  value of the Parameter Type field. If the length of the parameters to
  be encoded exceeds 255 octets, the extended variant (<xref target="openfmt-ext"/>) is
  used instead.</t>
          </li>
        </ul>
        <t>The minimum length of the OPEN message is 29 octets (including the
message header).</t>
        <section anchor="openfmt-ext">
          <name>OPEN Message Format (Extended Variant)</name>
          <t>This version of the OPEN message is identical to that defined above,
except for its encoding of the optional parameters. To preserve backward
compatibility, the non-extended format (<xref target="openfmt"/>) <bcp14>SHOULD</bcp14> be used except
when the length of the parameters to be encoded exceeds 255 octets, when
this format <bcp14>MUST</bcp14> be used. Configuration <bcp14>MAY</bcp14> override this to force the
extended format to be used in all cases; this might be used, for
example, to test that a peer supports this specification. In any case,
an implementation <bcp14>MUST</bcp14> accept an OPEN message that uses the encoding of
this section even if the length of the Optional Parameters is 255
or less.</t>
          <t>This encoding permits transmission of larger sets of Optional
Parameters, including Capabilities (<xref target="capabilities"/>), than can be represented
using the non-extended OPEN message encoding.</t>
          <figure anchor="ext-open">
            <name>OPEN Message Format (extended variant)</name>
            <artset>
              <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="304" width="528" viewBox="0 0 528 304" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                  <path d="M 8,64 L 8,288" fill="none" stroke="black"/>
                  <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                  <path d="M 136,192 L 136,224" fill="none" stroke="black"/>
                  <path d="M 264,96 L 264,160" fill="none" stroke="black"/>
                  <path d="M 264,192 L 264,224" fill="none" stroke="black"/>
                  <path d="M 520,160 L 520,288" fill="none" stroke="black"/>
                  <path d="M 8,64 L 136,64" fill="none" stroke="black"/>
                  <path d="M 8,96 L 264,96" fill="none" stroke="black"/>
                  <path d="M 8,128 L 264,128" fill="none" stroke="black"/>
                  <path d="M 8,160 L 520,160" fill="none" stroke="black"/>
                  <path d="M 8,192 L 520,192" fill="none" stroke="black"/>
                  <path d="M 8,224 L 520,224" fill="none" stroke="black"/>
                  <path d="M 8,288 L 520,288" fill="none" stroke="black"/>
                  <g class="text">
                    <text x="16" y="36">0</text>
                    <text x="176" y="36">1</text>
                    <text x="336" y="36">2</text>
                    <text x="496" y="36">3</text>
                    <text x="16" y="52">0</text>
                    <text x="32" y="52">1</text>
                    <text x="48" y="52">2</text>
                    <text x="64" y="52">3</text>
                    <text x="80" y="52">4</text>
                    <text x="96" y="52">5</text>
                    <text x="112" y="52">6</text>
                    <text x="128" y="52">7</text>
                    <text x="144" y="52">8</text>
                    <text x="160" y="52">9</text>
                    <text x="176" y="52">0</text>
                    <text x="192" y="52">1</text>
                    <text x="208" y="52">2</text>
                    <text x="224" y="52">3</text>
                    <text x="240" y="52">4</text>
                    <text x="256" y="52">5</text>
                    <text x="272" y="52">6</text>
                    <text x="288" y="52">7</text>
                    <text x="304" y="52">8</text>
                    <text x="320" y="52">9</text>
                    <text x="336" y="52">0</text>
                    <text x="352" y="52">1</text>
                    <text x="368" y="52">2</text>
                    <text x="384" y="52">3</text>
                    <text x="400" y="52">4</text>
                    <text x="416" y="52">5</text>
                    <text x="432" y="52">6</text>
                    <text x="448" y="52">7</text>
                    <text x="464" y="52">8</text>
                    <text x="480" y="52">9</text>
                    <text x="496" y="52">0</text>
                    <text x="512" y="52">1</text>
                    <text x="72" y="84">Version</text>
                    <text x="36" y="116">My</text>
                    <text x="76" y="116">Legacy</text>
                    <text x="148" y="116">Autonomous</text>
                    <text x="220" y="116">System</text>
                    <text x="116" y="148">Hold</text>
                    <text x="156" y="148">Time</text>
                    <text x="224" y="180">BGP</text>
                    <text x="284" y="180">Identifier</text>
                    <text x="40" y="212">Non-Ext</text>
                    <text x="84" y="212">OP</text>
                    <text x="116" y="212">Len.</text>
                    <text x="168" y="212">Non-Ext</text>
                    <text x="212" y="212">OP</text>
                    <text x="244" y="212">Type</text>
                    <text x="316" y="212">Extended</text>
                    <text x="372" y="212">Opt.</text>
                    <text x="416" y="212">Parm.</text>
                    <text x="468" y="212">Length</text>
                    <text x="148" y="260">Optional</text>
                    <text x="228" y="260">Parameters</text>
                    <text x="316" y="260">(variable)</text>
                  </g>
                </svg>
              </artwork>
              <artwork type="ascii-art"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+
|    Version    |
+---------------+-+-+-+-+-+-+-+-+
|  My Legacy Autonomous System  |
+-------------------------------+
|           Hold Time           |
+-------------------------------+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         BGP Identifier                        |
+---------------+---------------+-------------------------------+
|Non-Ext OP Len.|Non-Ext OP Type|  Extended Opt. Parm. Length   |
+---------------+---------------+-------------------------------+
|                                                               |
|             Optional Parameters (variable)                    |
|                                                               |
+---------------------------------------------------------------+
]]></artwork>
            </artset>
          </figure>
          <t>Only the fields that differ from those of the non-extended variant
are defined below.</t>
          <dl>
            <dt>Non-Extended Optional Parameters Length ("Non-Ext OP Len"):</dt>
            <dd>
              <t>This 1-octet unsigned integer <bcp14>MUST</bcp14> be set to 255. Its value 
<bcp14>MUST</bcp14> be ignored on receipt once the use of the extended format 
is determined positively by inspection of the Non-Extended 
Optional Parameters Type (Non-Ext OP Type) field.</t>
            </dd>
            <dt>Non-Extended Optional Parameters Type ("Non-Ext OP Type"):</dt>
            <dd>
              <t>The 1-octet field following the Non-Ext OP Len (which would 
be the first Optional Parameter Type field in the non-extended
format and is called "Non-Ext OP Type" in the figure above) <bcp14>MUST</bcp14> be
set to 255 on transmission. On receipt, a value of 255 for this
field is the indication that the extended format is in use.</t>
            </dd>
            <dt>Extended Optional Parameters Length ("Extended Opt. Parm. Length"):</dt>
            <dd>
              <t>This 2-octet unsigned integer indicates the total length of 
the Optional Parameters field in octets. If the value of this field
is zero, no Optional Parameters are present.</t>
            </dd>
            <dt>Optional Parameters:</dt>
            <dd>
              <t>This field contains a list of optional parameters, in which
each parameter is encoded as a &lt;Parameter Type, Parameter
Length, Parameter Value&gt; triplet. The rules for encoding Optional 
Parameters are unchanged with respect to those above, except that 
the Parameter Length field is extended to be a two-octet 
unsigned integer.</t>
            </dd>
          </dl>
          <figure>
            <name>Optional Parameters (extended variant)</name>
            <artset>
              <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="192" width="408" viewBox="0 0 408 192" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                  <path d="M 8,64 L 8,160" fill="none" stroke="black"/>
                  <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                  <path d="M 392,64 L 392,160" fill="none" stroke="black"/>
                  <path d="M 8,64 L 392,64" fill="none" stroke="black"/>
                  <path d="M 8,96 L 392,96" fill="none" stroke="black"/>
                  <path d="M 8,160 L 392,160" fill="none" stroke="black"/>
                  <g class="text">
                    <text x="16" y="36">0</text>
                    <text x="176" y="36">1</text>
                    <text x="336" y="36">2</text>
                    <text x="16" y="52">0</text>
                    <text x="32" y="52">1</text>
                    <text x="48" y="52">2</text>
                    <text x="64" y="52">3</text>
                    <text x="80" y="52">4</text>
                    <text x="96" y="52">5</text>
                    <text x="112" y="52">6</text>
                    <text x="128" y="52">7</text>
                    <text x="144" y="52">8</text>
                    <text x="160" y="52">9</text>
                    <text x="176" y="52">0</text>
                    <text x="192" y="52">1</text>
                    <text x="208" y="52">2</text>
                    <text x="224" y="52">3</text>
                    <text x="240" y="52">4</text>
                    <text x="256" y="52">5</text>
                    <text x="272" y="52">6</text>
                    <text x="288" y="52">7</text>
                    <text x="304" y="52">8</text>
                    <text x="320" y="52">9</text>
                    <text x="336" y="52">0</text>
                    <text x="352" y="52">1</text>
                    <text x="368" y="52">2</text>
                    <text x="384" y="52">3</text>
                    <text x="400" y="52">4</text>
                    <text x="48" y="84">Parm.</text>
                    <text x="92" y="84">Type</text>
                    <text x="240" y="84">Parameter</text>
                    <text x="308" y="84">Length</text>
                    <text x="144" y="132">Parameter</text>
                    <text x="208" y="132">Value</text>
                    <text x="276" y="132">(variable)</text>
                  </g>
                </svg>
              </artwork>
              <artwork type="ascii-art"><![CDATA[
     0                   1                   2
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Parm. Type   |        Parameter Length       |
    +---------------+-------------------------------+
    |                                               |
    |            Parameter Value (variable)         |
    |                                               |
    +-----------------------------------------------+
]]></artwork>
            </artset>
          </figure>
          <t>In parsing an OPEN message, if the one-octet Optional Parameters Length
field (labeled "Non-Ext OP Len." in <xref target="ext-open"/>) is non-zero, a BGP
speaker <bcp14>MUST</bcp14> use the value of the octet following the one-octet Optional
Parameters Length field (labeled "Non-Ext OP Type" in <xref target="ext-open"/>) to
determine both the encoding of the Optional Parameters length and the
size of the Parameter Length field of individual Optional Parameters. If
the value of the "Non-Ext OP Type" field is 255, then the encoding
described in this subsection is used for the Optional Parameters length.
Otherwise, the encoding defined in <xref target="openfmt"/> is used.</t>
        </section>
        <section anchor="capabilities">
          <name>Capabilities Optional Parameter (Parameter Type 2)</name>
          <t>A BGP speaker's OPEN message <bcp14>MUST</bcp14> include the Capabilities Optional
Parameter, listing the capabilities supported by the speaker. The only
exception to this requirement is if the peer does not support
Capabilities. This exception is discussed further in <xref target="capbackcompat"/>.</t>
          <t>A BGP speaker determines the capabilities supported by its peer by
examining the list of capabilities present in the Capabilities
Optional Parameter carried by the OPEN message that the speaker
receives from the peer.</t>
          <t>A BGP speaker that supports a particular capability may use this
capability with its peer after the speaker determines (as described
above) that the peer supports this capability.  Simply put, a given
capability can be used on a peering if that capability has been
advertised by both peers.  If either peer has not advertised it, the
capability cannot be used. If the capability has been advertised by
both peers, it is said to have been "exchanged" or "negotiated".</t>
          <section anchor="capabilities-format">
            <name>Capabilities Format</name>
            <t>This optional parameter of type 2  contains one or more triples
&lt;Capability Code, Capability Length, Capability Value&gt;, where each
triple is encoded as shown below:</t>
            <figure>
              <name>Capability</name>
              <artset>
                <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="192" width="256" viewBox="0 0 256 192" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                    <path d="M 8,32 L 8,160" fill="none" stroke="black"/>
                    <path d="M 248,32 L 248,160" fill="none" stroke="black"/>
                    <path d="M 8,32 L 248,32" fill="none" stroke="black"/>
                    <path d="M 8,64 L 248,64" fill="none" stroke="black"/>
                    <path d="M 8,96 L 248,96" fill="none" stroke="black"/>
                    <path d="M 8,160 L 248,160" fill="none" stroke="black"/>
                    <g class="text">
                      <text x="60" y="52">Capability</text>
                      <text x="124" y="52">Code</text>
                      <text x="156" y="52">(1</text>
                      <text x="196" y="52">octet)</text>
                      <text x="60" y="84">Capability</text>
                      <text x="132" y="84">Length</text>
                      <text x="172" y="84">(1</text>
                      <text x="212" y="84">octet)</text>
                      <text x="60" y="132">Capability</text>
                      <text x="128" y="132">Value</text>
                      <text x="196" y="132">(variable)</text>
                    </g>
                  </svg>
                </artwork>
                <artwork type="ascii-art"><![CDATA[
          +-----------------------------+
          | Capability Code (1 octet)   |
          +-----------------------------+
          | Capability Length (1 octet) |
          +-----------------------------+
          |                             |
          | Capability Value (variable) |
          |                             |
          +-----------------------------+
]]></artwork>
              </artset>
            </figure>
            <t>The use and meaning of these fields are as follows:</t>
            <dl>
              <dt>Capability Code:</dt>
              <dd>
                <t>Capability Code is a 1-octet unsigned integer that unambiguously 
identifies individual capabilities.</t>
              </dd>
              <dt>Capability Length:</dt>
              <dd>
                <t>Capability Length is a 1-octet unsigned integer that contains 
the length of the Capability Value field in octets.</t>
              </dd>
              <dt>Capability Value:</dt>
              <dd>
                <t>Capability Value is a variable-length field that is interpreted
according to the value of the Capability Code field.</t>
              </dd>
            </dl>
            <t>BGP speakers <bcp14>SHOULD NOT</bcp14> include more than one instance of a
capability with the same Capability Code, Capability Length, and
Capability Value.  Note, however, that processing of multiple
instances of such capability does not require special handling, as
additional instances do not change the meaning of the announced
capability; thus, a BGP speaker <bcp14>MUST</bcp14> be prepared to accept such
multiple instances.</t>
            <t>BGP speakers <bcp14>MAY</bcp14> include more than one instance of a capability (as
identified by the Capability Code) with non-zero Capability Length
field, but with different Capability Value and either the same or
different Capability Length.  Processing of these capability
instances is specific to the Capability Code and <bcp14>MUST</bcp14> be described in
the document specifying the capability.</t>
            <t>The Capabilities Optional Parameter (OPEN Optional Parameter Type 2)
<bcp14>SHOULD</bcp14> only be included in the OPEN message once.  If the BGP speaker
wishes to include multiple capabilities in the OPEN message, it
<bcp14>SHOULD</bcp14> do so as discussed above -- by listing all those capabilities
as TLVs within a single Capabilities Optional Parameter.  However,
for backward compatibility, a BGP speaker <bcp14>MUST</bcp14> be prepared to receive
an OPEN message that contains multiple Capabilities Optional
Parameters, each of which contains one or more capabilities TLVs.
The set of capabilities should be processed in the same way in either
case, whether it is enumerated within a single Capabilities Optional
Parameter of the OPEN message or split across multiple Capabilities
Optional Parameters. <!-- see Issue #159 about possibly cutting this -->
            </t>
          </section>
          <section anchor="as4byte">
            <name>4-octet AS Number Capability</name>
            <t>This capability, also called the "Support for 4-octet AS number"
capability, has been assigned type code 65 by IANA. Its value is the
Autonomous System number of the sender, encoded as a 4-octet unsigned 
integer. Its value <bcp14>MUST NOT</bcp14> be 0.</t>
            <t>This capability <bcp14>MUST</bcp14> be sent with the OPEN, unless the peer does not
support capabilities (<xref target="capbackcompat"/>).</t>
          </section>
        </section>
      </section>
      <section anchor="updatefmt">
        <name>UPDATE Message Format</name>
        <t>UPDATE messages are used to transfer routing information between BGP
peers.  The information in the UPDATE message can be used to
construct a graph that describes the relationships of the various
Autonomous Systems.  By applying rules discussed below, routing
information loops and some other anomalies may be detected and
removed from inter-AS routing.</t>
        <t>An UPDATE message is used to advertise feasible routes that share common
path attributes to a peer, or to withdraw multiple unfeasible routes
from service (see <xref target="routes_adv_store"/>).  An UPDATE message <bcp14>MUST NOT</bcp14>
simultaneously advertise a feasible route and withdraw unfeasible routes
from service.  However, in order to preserve backward compatibility, an
implementation <bcp14>SHOULD</bcp14> still be prepared to receive an UPDATE message
that simultaneously advertises and withdraws routes. (<xref target="RFC4760"/>
specifies an alternate encoding to advertise and withdraw routes, and
can be used to support address families other than IP Version 4.)</t>
        <t>The UPDATE message always includes the fixed-size BGP
header, and also includes the other fields, as shown below (note,
some of the shown fields may not be present in every UPDATE message):</t>
        <figure>
          <name>UPDATE message format</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="208" width="448" viewBox="0 0 448 208" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,32 L 8,192" fill="none" stroke="black"/>
                <path d="M 440,32 L 440,192" fill="none" stroke="black"/>
                <path d="M 8,32 L 440,32" fill="none" stroke="black"/>
                <path d="M 8,64 L 440,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 440,96" fill="none" stroke="black"/>
                <path d="M 8,128 L 440,128" fill="none" stroke="black"/>
                <path d="M 8,160 L 440,160" fill="none" stroke="black"/>
                <path d="M 8,192 L 440,192" fill="none" stroke="black"/>
                <g class="text">
                  <text x="72" y="52">Withdrawn</text>
                  <text x="140" y="52">Routes</text>
                  <text x="196" y="52">Length</text>
                  <text x="236" y="52">(2</text>
                  <text x="280" y="52">octets)</text>
                  <text x="72" y="84">Withdrawn</text>
                  <text x="140" y="84">Routes</text>
                  <text x="212" y="84">(variable)</text>
                  <text x="56" y="116">Total</text>
                  <text x="100" y="116">Path</text>
                  <text x="160" y="116">Attribute</text>
                  <text x="228" y="116">Length</text>
                  <text x="268" y="116">(2</text>
                  <text x="312" y="116">octets)</text>
                  <text x="52" y="148">Path</text>
                  <text x="116" y="148">Attributes</text>
                  <text x="204" y="148">(variable)</text>
                  <text x="64" y="180">Network</text>
                  <text x="120" y="180">Layer</text>
                  <text x="196" y="180">Reachability</text>
                  <text x="296" y="180">Information</text>
                  <text x="388" y="180">(variable)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
+-----------------------------------------------------+
|   Withdrawn Routes Length (2 octets)                |
+-----------------------------------------------------+
|   Withdrawn Routes (variable)                       |
+-----------------------------------------------------+
|   Total Path Attribute Length (2 octets)            |
+-----------------------------------------------------+
|   Path Attributes (variable)                        |
+-----------------------------------------------------+
|   Network Layer Reachability Information (variable) |
+-----------------------------------------------------+
]]></artwork>
          </artset>
        </figure>
        <dl>
          <dt>Withdrawn Routes Length:</dt>
          <dd>
            <t>This 2-octets unsigned integer indicates the total length of
   the Withdrawn Routes field in octets.  Its value allows the
   length of the Network Layer Reachability Information field to
   be determined, as specified below.</t>
          </dd>
          <dt/>
          <dd>
            <t>A value of 0 indicates that no routes are being withdrawn from
   service, and that the Withdrawn Routes field is not present in
   this UPDATE message.</t>
          </dd>
          <dt>Withdrawn Routes:</dt>
          <dd>
            <t>This is a variable-length field that contains a list of IP
   address prefixes for the routes that are being withdrawn from
   service.  Each IP address prefix is encoded as a 2-tuple of the
   form &lt;length, prefix&gt;, whose fields are described below:</t>
          </dd>
        </dl>
        <figure anchor="ipaddressprefix">
          <name>IP Address Prefix</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="128" width="240" viewBox="0 0 240 128" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,32 L 8,96" fill="none" stroke="black"/>
                <path d="M 232,32 L 232,96" fill="none" stroke="black"/>
                <path d="M 8,32 L 232,32" fill="none" stroke="black"/>
                <path d="M 8,64 L 232,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 232,96" fill="none" stroke="black"/>
                <g class="text">
                  <text x="60" y="52">Length</text>
                  <text x="100" y="52">(1</text>
                  <text x="140" y="52">octet)</text>
                  <text x="60" y="84">Prefix</text>
                  <text x="132" y="84">(variable)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
    +---------------------------+
    |   Length (1 octet)        |
    +---------------------------+
    |   Prefix (variable)       |
    +---------------------------+
]]></artwork>
          </artset>
        </figure>
        <t>The use and the meaning of these fields are as follows:</t>
        <ol spacing="normal" type="%c)"><li>
            <t>Length:
 The Length field indicates the length in bits of the IP
 address prefix.  A length of zero indicates a prefix that
 matches all IP addresses (with prefix, itself, of zero
 octets).</t>
          </li>
          <li>
            <t>Prefix:
 The Prefix field contains an IP address prefix, followed by
 the minimum number of trailing bits needed to make the end
 of the field fall on an octet boundary.  Note that the value
 of trailing bits is irrelevant. Trailing bits <bcp14>MUST</bcp14> be set
 to zero on transmission and <bcp14>MUST</bcp14> be disregarded on receipt.</t>
          </li>
        </ol>
        <dl>
          <dt>Total Path Attribute Length:</dt>
          <dd>
            <t>This 2-octet unsigned integer indicates the total length of the
   Path Attributes field in octets.  Its value allows the length
   of the Network Layer Reachability field to be determined as
   specified below.</t>
          </dd>
          <dt/>
          <dd>
            <t>A value of 0 indicates that neither the Network Layer
   Reachability Information field nor the Path Attribute field is
   present in this UPDATE message.</t>
          </dd>
          <dt>Path Attributes:</dt>
          <dd>
            <t>A variable-length sequence of path attributes is present in
   every UPDATE message, except for an UPDATE message that carries
   only withdrawn routes.  Each path attribute is a triple
   &lt;attribute type, attribute length, attribute value&gt; of variable
   length.</t>
          </dd>
          <dt/>
          <dd>
            <t>Attribute Type is a two-octet field that consists of the
   Attribute Flags octet, followed by the Attribute Type Code
   octet.</t>
          </dd>
        </dl>
        <figure>
          <name>Attribute Type</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="128" width="272" viewBox="0 0 272 128" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,64 L 8,96" fill="none" stroke="black"/>
                <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                <path d="M 264,64 L 264,96" fill="none" stroke="black"/>
                <path d="M 8,64 L 264,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 264,96" fill="none" stroke="black"/>
                <g class="text">
                  <text x="16" y="36">0</text>
                  <text x="176" y="36">1</text>
                  <text x="16" y="52">0</text>
                  <text x="32" y="52">1</text>
                  <text x="48" y="52">2</text>
                  <text x="64" y="52">3</text>
                  <text x="80" y="52">4</text>
                  <text x="96" y="52">5</text>
                  <text x="112" y="52">6</text>
                  <text x="128" y="52">7</text>
                  <text x="144" y="52">8</text>
                  <text x="160" y="52">9</text>
                  <text x="176" y="52">0</text>
                  <text x="192" y="52">1</text>
                  <text x="208" y="52">2</text>
                  <text x="224" y="52">3</text>
                  <text x="240" y="52">4</text>
                  <text x="256" y="52">5</text>
                  <text x="48" y="84">Attr.</text>
                  <text x="96" y="84">Flags</text>
                  <text x="160" y="84">Attr.</text>
                  <text x="204" y="84">Type</text>
                  <text x="244" y="84">Code</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
     0                   1
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Attr. Flags  |Attr. Type Code|
    +---------------+---------------+
]]></artwork>
          </artset>
        </figure>
        <!-- [rfced] this text should be indented under path attributes -->

<ul empty="true">
          <li>
            <t>The high-order bit (bit 0) of the Attribute Flags octet is the
Optional bit.  The attributes ORIGIN, AS_PATH, NEXT_HOP, LOCAL_PREF, 
and ATOMIC_AGGREGATE have their Optional bit set to 0. (The reasons
for this choice are historical; the bit setting must be carried 
forward to preserve backward compatibility.)</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The second high-order bit (bit 1) of the Attribute Flags octet
is the Transitive bit.  It defines whether an optional
attribute is transitive (if set to 1) or non-transitive (if set
to 0).</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The third high-order bit (bit 2) of the Attribute Flags octet
is the Partial bit.  It defines whether the information
contained in the optional transitive attribute is partial (if
set to 1) or complete (if set to 0).  For the attributes
ORIGIN, AS_PATH, NEXT_HOP, LOCAL_PREF, and ATOMIC_AGGREGATE,
and for optional non-transitive attributes, the Partial bit
<bcp14>MUST</bcp14> be set to 0.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The fourth high-order bit (bit 3) of the Attribute Flags octet
is the Extended Length bit.  It defines whether the Attribute
Length is one octet (if set to 0) or two octets (if set to 1).</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The lower-order four bits of the Attribute Flags octet are
unused.  They <bcp14>MUST</bcp14> be zero when sent and <bcp14>MUST</bcp14> be ignored when
received.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The Attribute Type Code octet contains the Attribute Type Code.
Currently defined Attribute Type Codes are discussed in <xref target="pathattributes"/>.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>If the Extended Length bit of the Attribute Flags octet is set
to 0, the third octet of the Path Attribute contains the length
of the attribute data in octets.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>If the Extended Length bit of the Attribute Flags octet is set
to 1, the third and fourth octets of the path attribute contain
the length of the attribute data in octets.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The remaining octets of the Path Attribute represent the
attribute value and are interpreted according to the Attribute
Flags and the Attribute Type Code.  The supported Attribute
Type Codes, and their attribute values and uses are as follows:</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <dl>
              <dt>a) ORIGIN (Type Code 1):</dt>
              <dd>
                <t>ORIGIN is an attribute whose Optional bit is set to 0, whose
Transitive bit is set to 1, and whose Partial bit is set to 0. It
defines the origin of the path information.  The data octet can
assume the following values:</t>
              </dd>
            </dl>
          </li>
        </ul>
        <table anchor="origin_values">
          <name>ORIGIN Values</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Meaning</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">IGP - Network Layer Reachability Information is interior to the originating AS</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">EGP - Network Layer Reachability Information learned via the EGP protocol <xref target="RFC904"/></td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">INCOMPLETE - Network Layer Reachability Information learned by some other means</td>
            </tr>
            <tr>
              <td align="left">3-255</td>
              <td align="left">
                <bcp14>MUST NOT</bcp14> be sent</td>
            </tr>
          </tbody>
        </table>
        <ul empty="true">
          <li>
            <t>Usage of this attribute is defined in <xref target="origin"/>.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <dl>
              <dt>b) AS_PATH (Type Code 2):</dt>
              <dd>
                <t>AS_PATH is an attribute whose Optional bit is set to 0, whose
Transitive bit is set to 1, and whose Partial bit is set to 0. It is
composed of a sequence of AS path segments.  Each AS path segment is
represented by a triple &lt;path segment type, path segment length, path
segment value&gt;.</t>
              </dd>
            </dl>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The path segment type is a 1-octet length field with the
following values defined:</t>
          </li>
        </ul>
        <table anchor="aspath_segtypes">
          <name>AS_PATH Segment Type Values</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Segment Type</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">1 (deprecated)</td>
              <td align="left">AS_SET: deprecated</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">AS_SEQUENCE: ordered set of ASes a route in the UPDATE message has traversed</td>
            </tr>
          </tbody>
        </table>
        <ul empty="true">
          <li>
            <t>The path segment length is a 1-octet length field,
  containing the number of ASes (not the number of octets) in
  the path segment value field.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>The path segment value field contains one or more AS
  numbers, each encoded as a 4-octet length field. 
  (Unless backward compatibility procedures are in use;
  see <xref target="as2byte"/> for details.)</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>Usage of this attribute is defined in <xref target="aspath"/>.</t>
          </li>
        </ul>
        <dl>
          <dt>c) NEXT_HOP (Type Code 3):</dt>
          <dd>
            <t>NEXT_HOP is an attribute whose Optional bit is set to 0, whose
Transitive bit is set to 1, and whose Partial bit is set to 0. It
defines the (unicast) IP address of the router that <bcp14>SHOULD</bcp14> be used as
the next hop to the destinations listed in the Network Layer
Reachability Information field of the UPDATE message.</t>
          </dd>
          <dt/>
          <dd>
            <t>Usage of this attribute is defined in <xref target="nexthop"/>.</t>
          </dd>
          <dt>d) MULTI_EXIT_DISC (Type Code 4):</dt>
          <dd>
            <t>This is an optional non-transitive attribute that is a
four-octet unsigned integer.  The value of this attribute
<bcp14>MAY</bcp14> be used by a BGP speaker's Decision Process to
discriminate among multiple entry points to a neighboring
autonomous system.</t>
          </dd>
          <dt/>
          <dd>
            <t>Considerations for the deployment of this attribute are 
given in <xref target="RFC7964"/>.</t>
          </dd>
          <dt/>
          <dd>
            <t>Usage of this attribute is defined in <xref target="med"/>.</t>
          </dd>
          <dt>e) LOCAL_PREF (Type Code 5):</dt>
          <dd>
            <t>LOCAL_PREF is an attribute whose Optional bit is set to 0, whose
Transitive bit is set to 1, and whose Partial bit is set to 0. It is a
four-octet unsigned integer.  A BGP speaker uses it to inform its other
internal peers of the advertising speaker's degree of preference for an
advertised route.</t>
          </dd>
          <dt/>
          <dd>
            <t>Usage of this attribute is defined in <xref target="localpref"/>.</t>
          </dd>
          <dt>f) ATOMIC_AGGREGATE (Type Code 6):</dt>
          <dd>
            <t>ATOMIC_AGGREGATE is an attribute whose Optional bit is set to 0,
   whose Transitive bit is set to 1, and whose Partial bit is set to 0.
   It is of length 0.</t>
          </dd>
          <dt/>
          <dd>
            <t>Usage of this attribute is defined in <xref target="atomic"/>.</t>
          </dd>
          <dt>g) AGGREGATOR (Type Code 7):</dt>
          <dd>
            <t>AGGREGATOR is an optional transitive attribute of length 8.
   The attribute contains the last AS number that formed the
   aggregate route (encoded as 4 octets), followed by the BGP
   Identifier of the BGP speaker that formed the aggregate route
   (encoded as 4 octets). (Unless backward compatibility procedures are
   in use; see <xref target="as2byte"/> for details.)</t>
          </dd>
          <dt/>
          <dd>
            <t>Usage of this attribute is defined in <xref target="aggregator"/>.</t>
          </dd>
          <dt>Network Layer Reachability Information:</dt>
          <dd>
            <t>This variable length field contains a list of IP address
   prefixes.  The length, in octets, of the Network Layer
   Reachability Information is not encoded explicitly, but can be
   calculated as:</t>
          </dd>
        </dl>
        <figure>
          <name>NLRI Length Calculation</name>
          <artwork><![CDATA[
   UPDATE message Length - 23 - Total Path Attributes Length
   - Withdrawn Routes Length
]]></artwork>
        </figure>
        <ul empty="true">
          <li>
            <t>where UPDATE message Length is the value encoded in the fixed-size
BGP header, Total Path Attribute Length, and Withdrawn
Routes Length are the values encoded in the variable part of
the UPDATE message, and 23 is a combined length of the fixed-size
BGP header, the Total Path Attribute Length field, and the
Withdrawn Routes Length field.</t>
          </li>
        </ul>
        <ul empty="true">
          <li>
            <t>Reachability information is encoded as a list of IP
address prefixes for the routes that are being made available for
service.  Each IP address prefix is encoded as described above
under <xref target="ipaddressprefix"/>.
<!-- not really the right xref but there isn't a standalone subsection-->
            </t>
          </li>
        </ul>
        <t>The minimum length of the UPDATE message is 23 octets -- 19 octets
for the fixed header + 2 octets for the Withdrawn Routes Length + 2
octets for the Total Path Attribute Length (the value of Withdrawn
Routes Length is 0 and the value of Total Path Attribute Length is
0).</t>
        <t>An UPDATE message can advertise, at most, one set of path attributes,
but multiple destinations, provided that the destinations share these
attributes.  All path attributes contained in a given UPDATE message
apply to all destinations carried in the NLRI field of the UPDATE
message.</t>
        <t>An UPDATE message can list multiple routes that are to be withdrawn
from service.  Each such route is identified by its destination
(expressed as an IP prefix), which unambiguously identifies the route
in the context of the BGP speaker - BGP speaker connection to which
it has been previously advertised.</t>
        <t>When an UPDATE message advertises only routes that are to be
withdrawn from service, the message will not include path attributes or
Network Layer Reachability Information. Conversely, when an UPDATE
message advertises only a feasible route, the Withdrawn Routes field
will not be present (Withdrawn Routes Length will be equal to 0).</t>
        <t>For backward compatibility, a BGP speaker <bcp14>MUST</bcp14> be able to process UPDATE
messages that include the same address prefix in the Withdrawn Routes
and Network Layer Reachability Information fields.  A BGP speaker <bcp14>MUST</bcp14>
treat an UPDATE message of this form as though the Withdrawn Routes do
not contain the address prefix.</t>
      </section>
      <section anchor="keepalivefmt">
        <name>KEEPALIVE Message Format</name>
        <t>BGP does not use any TCP-based, keep-alive mechanism to determine if
peers are reachable.  Instead, KEEPALIVE messages are exchanged
between peers often enough not to cause the Hold Timer to expire.  A
reasonable maximum time between KEEPALIVE messages would be one third
of the Hold Time interval.  KEEPALIVE messages <bcp14>MUST NOT</bcp14> be sent more
frequently than one per second.  An implementation <bcp14>MAY</bcp14> adjust the
rate at which it sends KEEPALIVE messages as a function of the Hold
Time interval.</t>
        <t>If the negotiated Hold Time interval is zero, then periodic KEEPALIVE
messages <bcp14>MUST NOT</bcp14> be sent.</t>
        <t>A KEEPALIVE message consists of only the message header and has a
length of 19 octets.</t>
      </section>
      <section anchor="notifyfmt">
        <name>NOTIFICATION Message Format</name>
        <t>A NOTIFICATION message is sent when a fatal error condition is detected.
The BGP connection is closed immediately after it is sent.</t>
        <t>In addition to the fixed-size BGP header, the NOTIFICATION message
contains the following fields:</t>
        <figure>
          <name>NOTIFICATION Message Format</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="112" width="528" viewBox="0 0 528 112" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,64 L 8,96" fill="none" stroke="black"/>
                <path d="M 136,64 L 136,96" fill="none" stroke="black"/>
                <path d="M 264,64 L 264,96" fill="none" stroke="black"/>
                <path d="M 520,64 L 520,96" fill="none" stroke="black"/>
                <path d="M 8,64 L 520,64" fill="none" stroke="black"/>
                <path d="M 8,96 L 520,96" fill="none" stroke="black"/>
                <g class="text">
                  <text x="16" y="36">0</text>
                  <text x="176" y="36">1</text>
                  <text x="336" y="36">2</text>
                  <text x="496" y="36">3</text>
                  <text x="16" y="52">0</text>
                  <text x="32" y="52">1</text>
                  <text x="48" y="52">2</text>
                  <text x="64" y="52">3</text>
                  <text x="80" y="52">4</text>
                  <text x="96" y="52">5</text>
                  <text x="112" y="52">6</text>
                  <text x="128" y="52">7</text>
                  <text x="144" y="52">8</text>
                  <text x="160" y="52">9</text>
                  <text x="176" y="52">0</text>
                  <text x="192" y="52">1</text>
                  <text x="208" y="52">2</text>
                  <text x="224" y="52">3</text>
                  <text x="240" y="52">4</text>
                  <text x="256" y="52">5</text>
                  <text x="272" y="52">6</text>
                  <text x="288" y="52">7</text>
                  <text x="304" y="52">8</text>
                  <text x="320" y="52">9</text>
                  <text x="336" y="52">0</text>
                  <text x="352" y="52">1</text>
                  <text x="368" y="52">2</text>
                  <text x="384" y="52">3</text>
                  <text x="400" y="52">4</text>
                  <text x="416" y="52">5</text>
                  <text x="432" y="52">6</text>
                  <text x="448" y="52">7</text>
                  <text x="464" y="52">8</text>
                  <text x="480" y="52">9</text>
                  <text x="496" y="52">0</text>
                  <text x="512" y="52">1</text>
                  <text x="40" y="84">Error</text>
                  <text x="84" y="84">code</text>
                  <text x="168" y="84">Error</text>
                  <text x="224" y="84">subcode</text>
                  <text x="324" y="84">Data</text>
                  <text x="384" y="84">(variable</text>
                  <text x="432" y="84">)</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error code    | Error subcode |     Data (variable )          |
+---------------+---------------+-------------------------------+
]]></artwork>
          </artset>
        </figure>
        <!-- the extra space before the close paren above is to keep aasvg from rendering a spurious line -->

<dl>
          <dt>Error Code:</dt>
          <dd>
            <t>This 1-octet unsigned integer indicates the type of
   NOTIFICATION.  The following Error Codes are defined 
   by this document. The authoritative list is maintained
   by IANA, see <xref target="iana"/>:</t>
          </dd>
        </dl>
        <table>
          <name>NOTIFICATION Error Codes</name>
          <thead>
            <tr>
              <th align="left">Error Code</th>
              <th align="left">Symbolic Name</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">1</td>
              <td align="left">Message Header Error</td>
              <td align="left">
                <xref target="msgheadererr"/></td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">OPEN Message Error</td>
              <td align="left">
                <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">UPDATE Message Error</td>
              <td align="left">
                <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">Hold Timer Expired</td>
              <td align="left">
                <xref target="holdtimerexperr"/></td>
            </tr>
            <tr>
              <td align="left">5</td>
              <td align="left">Finite State Machine Error</td>
              <td align="left">
                <xref target="fsmerr"/></td>
            </tr>
            <tr>
              <td align="left">6</td>
              <td align="left">Cease</td>
              <td align="left">
                <xref target="ceaseerr"/></td>
            </tr>
          </tbody>
        </table>
        <dl>
          <dt>Error subcode:</dt>
          <dd>
            <t>This 1-octet unsigned integer provides more specific
   information about the nature of the reported error.  Each Error
   Code may have one or more Error Subcodes associated with it.
   If no appropriate Error Subcode is defined, then a zero
   (Unspecific) value is used for the Error Subcode field.
   The following subcodes are defined by this document. The authoritative
   list is maintained by IANA, see <xref target="iana"/>:</t>
          </dd>
        </dl>
        <t>Message Header Error subcodes:</t>
        <table>
          <name>Message Header Error subcodes</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Unspecific</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Connection Not Synchronized</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Bad Message Length</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Bad Message Type</td>
            </tr>
          </tbody>
        </table>
        <!-- XXX maybe adding the title makes the above titletext redundant -->

<t>OPEN Message Error subcodes:</t>
        <table>
          <name>OPEN Message Error subcodes</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Unspecific</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Unsupported Version Number</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Bad Peer AS</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Bad BGP Identifier</td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">Unsupported Optional Parameter</td>
            </tr>
            <tr>
              <td align="left">5</td>
              <td align="left">[Deprecated - see <xref target="RFC4271"/> Appendix A]</td>
            </tr>
            <tr>
              <td align="left">6</td>
              <td align="left">Unacceptable Hold Time</td>
            </tr>
            <tr>
              <td align="left">7</td>
              <td align="left">Required Capability Not Received</td>
            </tr>
          </tbody>
        </table>
        <t>UPDATE Message Error subcodes:</t>
        <table>
          <name>UPDATE Message Error subcodes</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Unspecific</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Malformed Attribute List</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Unrecognized Well-known Attribute (deprecated)</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Missing Well-known Attribute (deprecated)</td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">Attribute Flags Error (deprecated)</td>
            </tr>
            <tr>
              <td align="left">5</td>
              <td align="left">Attribute Length Error (deprecated)</td>
            </tr>
            <tr>
              <td align="left">6</td>
              <td align="left">Invalid ORIGIN Attribute (deprecated)</td>
            </tr>
            <tr>
              <td align="left">7</td>
              <td align="left">[Deprecated - see <xref target="RFC4271"/> Appendix A]</td>
            </tr>
            <tr>
              <td align="left">8</td>
              <td align="left">Invalid NEXT_HOP Attribute (deprecated)</td>
            </tr>
            <tr>
              <td align="left">9</td>
              <td align="left">Optional Attribute Error (deprecated)</td>
            </tr>
            <tr>
              <td align="left">10</td>
              <td align="left">Invalid Network Field</td>
            </tr>
            <tr>
              <td align="left">11</td>
              <td align="left">Malformed AS_PATH (deprecated)</td>
            </tr>
          </tbody>
        </table>
        <t>Subcodes 2-6, 8, 9, and 11 were defined by RFC 4271 but are no longer
generated by the error handling procedures specified in this document.</t>
        <t>Finite State Machine Error Subcodes:</t>
        <table>
          <name>Finite State Machine Error Subcodes</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Unspecified Error</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Receive Unexpected Message in OpenSent State</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Receive Unexpected Message in OpenConfirm State</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Receive Unexpected Message in Established State</td>
            </tr>
          </tbody>
        </table>
        <t>Cease Error Subcodes:</t>
        <table>
          <name>Cease Error Subcodes</name>
          <thead>
            <tr>
              <th align="left">Value</th>
              <th align="left">Name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">1</td>
              <td align="left">Maximum Number of Prefixes Reached</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Administrative Shutdown</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Peer De-configured</td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">Administrative Reset</td>
            </tr>
            <tr>
              <td align="left">5</td>
              <td align="left">Connection Rejected</td>
            </tr>
            <tr>
              <td align="left">6</td>
              <td align="left">Other Configuration Change</td>
            </tr>
            <tr>
              <td align="left">7</td>
              <td align="left">Connection Collision Resolution</td>
            </tr>
            <tr>
              <td align="left">8</td>
              <td align="left">Out of Resources</td>
            </tr>
          </tbody>
        </table>
        <dl>
          <dt>Data:</dt>
          <dd>
            <t>This variable-length field is used to diagnose the reason for
   the NOTIFICATION.  The contents of the Data field depend upon
   the Error Code and Error Subcode.  See <xref target="errorhandling"/> for more
   details.</t>
          </dd>
          <dt/>
          <dd>
            <t>Note that the length of the Data field can be determined from
   the message Length field by the formula:</t>
            <artwork><![CDATA[
    Message Length = 21 + Data Length
]]></artwork>
          </dd>
        </dl>
        <t>The minimum length of the NOTIFICATION message is 21 octets
(including message header).</t>
      </section>
    </section>
    <section anchor="pathattributes">
      <name>Path Attributes</name>
      <t>This section discusses the path attributes of the UPDATE message.</t>
      <t>BGP implementations <bcp14>MUST</bcp14> recognize ORIGIN, AS_PATH, NEXT_HOP, 
LOCAL_PREF, and ATOMIC_AGGREGATE.</t>
      <t>In addition to these, whose use is described below, each path <bcp14>MAY</bcp14> also
contain one or more optional attributes.  It is not required or expected
that all BGP implementations support all optional attributes.  The
handling of an unrecognized optional attribute is determined by the
setting of the Transitive bit in the attribute flags octet.  Paths with
unrecognized optional transitive attributes <bcp14>SHOULD</bcp14> be accepted.  If a
path with an unrecognized optional transitive attribute is accepted and
passed to other BGP peers, then the unrecognized optional transitive
attribute of that path <bcp14>MUST</bcp14> be passed, along with the path, to other BGP
peers with the Partial bit in the Attribute Flags octet set to 1.  If a
path with a recognized, optional transitive attribute is accepted and
passed along to other BGP peers and the Partial bit in the Attribute
Flags octet is set to 1 by some previous AS, it <bcp14>MUST NOT</bcp14> be set back to
0 by the current AS.  Unrecognized optional non-transitive attributes
<bcp14>MUST</bcp14> be quietly ignored and not passed along to other BGP peers.</t>
      <t>Optional transitive attributes <bcp14>MAY</bcp14> be attached to the path by
the originator or by any other BGP speaker in the path.  The rules 
for attaching optional non-transitive attributes will depend on the
nature of the specific attribute.  The documentation of each
optional non-transitive attribute will be expected to include such rules
(the description of the MULTI_EXIT_DISC attribute gives an example). 
All optional attributes (both transitive and non-transitive), <bcp14>MAY</bcp14> be
updated (if appropriate) by BGP speakers in the path.</t>
      <t>The sender of an UPDATE message <bcp14>SHOULD</bcp14> order path attributes within
the UPDATE message in ascending order of attribute type.  The
receiver of an UPDATE message <bcp14>MUST</bcp14> be prepared to handle path
attributes within UPDATE messages that are out of order.</t>
      <t>The same attribute (attribute with the same type) cannot appear more
than once within the Path Attributes field of a particular UPDATE
message. <!-- xxx possibly make the weak 'cannot' into a MUST NOT -->
      </t>
      <section anchor="path-attribute-usage">
        <name>Path Attribute Usage</name>
        <t>The usage of each BGP path attribute is described in the following
clauses. Refer to <xref target="paerrs"/> for details regarding error handling
when processing path attributes.</t>
        <section anchor="origin">
          <name>ORIGIN</name>
          <t>ORIGIN <bcp14>MUST</bcp14> be included with every update.  The ORIGIN attribute is
generated by the speaker that originates the associated routing
information.  Its value <bcp14>SHOULD NOT</bcp14> be changed by any other speaker.</t>
          <t>An ORIGIN value not equal to one of the defined values of (0, 1, or 2)
(listed in <xref target="origin_values"/>) <bcp14>MUST NOT</bcp14> be sent.</t>
        </section>
        <section anchor="aspath">
          <name>AS_PATH</name>
          <t>AS_PATH <bcp14>MUST</bcp14> be included with every update.  This attribute
identifies the autonomous systems through which routing information
carried in this UPDATE message has passed.  The components of this
list can be AS_SETs or AS_SEQUENCEs. (Other segments and behaviors 
are added by <xref target="RFC5065"/>, if used.)</t>
          <t>When a BGP speaker propagates a route it learned from another BGP
speaker's UPDATE message, it modifies the route's AS_PATH attribute
based on the location of the BGP speaker to which the route will be
sent:</t>
          <ol spacing="normal" type="%c)"><li>
              <t>When a given BGP speaker advertises the route to an internal peer, the advertising speaker <bcp14>SHALL NOT</bcp14> modify the AS_PATH attribute associated with the route.</t>
            </li>
            <li>
              <t>When a given BGP speaker advertises the route to an external peer, the advertising speaker updates the AS_PATH attribute as follows:  </t>
              <ol spacing="normal" type="1"><li>
                  <t>if the first path segment of the AS_PATH is of type
 AS_SEQUENCE, the local system prepends its own AS number as
 the last element of the sequence (put it in the leftmost
 position with respect to the position of octets in the
 protocol message).  If the act of prepending will cause an
 overflow in the AS_PATH segment (i.e., more than 255 ASes),
 it <bcp14>MUST</bcp14> prepend a new segment of type AS_SEQUENCE and
 prepend its own AS number to this new segment.</t>
                </li>
                <li>
                  <t>if the first path segment of the AS_PATH is of type AS_SET,
 the local system prepends a new path segment of type
 AS_SEQUENCE to the AS_PATH, including its own AS number in
 that segment.</t>
                </li>
                <li>
                  <t>if the AS_PATH is empty, the local system creates a path
 segment of type AS_SEQUENCE, places its own AS into that
 segment, and places that segment into the AS_PATH.</t>
                </li>
              </ol>
            </li>
          </ol>
          <t>When a BGP speaker originates a route then:</t>
          <ol spacing="normal" type="%c)"><li>
              <t>the originating speaker includes its own AS number in a path
 segment, of type AS_SEQUENCE, in the AS_PATH attribute of any
 UPDATE message sent to an external peer.  In this case, the AS
 number of the originating speaker's autonomous system will be
 the only entry in the path segment, and this path segment will be
 the only segment in the AS_PATH attribute.</t>
            </li>
            <li>
              <t>the originating speaker includes an empty AS_PATH attribute in
 any UPDATE message sent to an internal peer.  (An empty AS_PATH
 attribute is one whose length field contains the value zero).</t>
            </li>
          </ol>
          <t>Whenever the modification of the AS_PATH attribute calls for
including or prepending the AS number of the local system, the local
system <bcp14>MAY</bcp14> include/prepend more than one instance of its own AS
number in the AS_PATH attribute.  This is controlled via local
configuration.</t>
          <t>The AS number 0 <bcp14>MUST NOT</bcp14> be added to the AS_PATH; see <xref target="own-asn"/>. The
advertised AS_PATH <bcp14>MUST NOT</bcp14> contain an AS_SET unless AS_SET propagation 
has been enabled by local configuration.</t>
        </section>
        <section anchor="nexthop">
          <name>NEXT_HOP</name>
          <t>The NEXT_HOP <bcp14>MUST</bcp14> be included with every update, unless the encoding of
<xref target="RFC4760"/> is in use. It defines the IP address of the router that
<bcp14>SHOULD</bcp14> be used as the next hop to the destinations listed in the UPDATE
message.  The NEXT_HOP attribute is calculated as follows:</t>
          <ol spacing="normal" type="1"><li>
              <t>When sending a message to an internal peer, if the route is not
locally originated, the BGP speaker <bcp14>SHOULD NOT</bcp14> modify the
NEXT_HOP attribute unless it has been explicitly configured to
announce its own IP address as the NEXT_HOP.  When announcing a
locally-originated route to an internal peer, the BGP speaker
<bcp14>SHOULD</bcp14> use the interface address of the router through which
the announced network is reachable for the speaker as the
NEXT_HOP.  If the route is directly connected to the speaker,
or if the interface address of the router through which the
announced network is reachable for the speaker is the internal
peer's address, then the BGP speaker <bcp14>SHOULD</bcp14> use its own IP
address for the NEXT_HOP attribute (the address of the
interface that is used to reach the peer).</t>
            </li>
            <li>
              <t>When sending a message to an external peer, X, and the peer is
one IP hop away from the speaker:  </t>
              <ul spacing="normal">
                <li>
                  <t>If the route being announced was learned from an internal
peer or is locally originated, the BGP speaker can use an
interface address of the internal peer router (or the
internal router) through which the announced network is
reachable for the speaker for the NEXT_HOP attribute,
provided that peer X shares a common subnet with this
address.  This is a form of "third party" NEXT_HOP attribute.</t>
                </li>
                <li>
                  <t>Otherwise, if the route being announced was learned from an
external peer, the speaker can use an IP address of any
adjacent router (known from the received NEXT_HOP attribute)
that the speaker itself uses for local route calculation in
the NEXT_HOP attribute, provided that peer X shares a common
subnet with this address.  This is a second form of "third
party" NEXT_HOP attribute.</t>
                </li>
                <li>
                  <t>Otherwise, if the external peer to which the route is being
advertised shares a common subnet with one of the interfaces
of the announcing BGP speaker, the speaker <bcp14>MAY</bcp14> use the IP
address associated with such an interface in the NEXT_HOP
attribute.  This is known as a "first party" NEXT_HOP
attribute.</t>
                </li>
                <li>
                  <t>By default (if none of the above conditions apply), the BGP
speaker <bcp14>SHOULD</bcp14> use the IP address of the interface that the
speaker uses to establish the BGP connection to peer X in the
NEXT_HOP attribute.</t>
                </li>
              </ul>
            </li>
            <li>
              <t>When sending a message to an external peer X, and the peer is
multiple IP hops away from the speaker (aka "multihop EBGP"):  </t>
              <ul spacing="normal">
                <li>
                  <t>The speaker <bcp14>MAY</bcp14> be configured to propagate the NEXT_HOP
attribute.  In this case, when advertising a route that the
speaker learned from one of its peers, the NEXT_HOP attribute
of the advertised route is exactly the same as the NEXT_HOP
attribute of the learned route (the speaker does not modify
the NEXT_HOP attribute).</t>
                </li>
                <li>
                  <t>By default, the BGP speaker <bcp14>SHOULD</bcp14> use the IP address of the
interface that the speaker uses to establish the BGP connection
to peer X in the NEXT_HOP attribute.</t>
                </li>
              </ul>
            </li>
          </ol>
          <t>Normally, the NEXT_HOP attribute is chosen such that the shortest
available path will be taken.  A BGP speaker <bcp14>MUST</bcp14> be able to support
disabling the advertisement of third party NEXT_HOP attributes in
order to handle imperfectly bridged media.</t>
          <t>A route originated by a BGP speaker <bcp14>SHALL NOT</bcp14> be advertised to a peer
using an address of that peer as NEXT_HOP.  A BGP speaker <bcp14>SHALL NOT</bcp14>
install a route with itself as the next hop.</t>
          <t>The NEXT_HOP attribute is used by the BGP speaker to determine the
actual outbound interface and immediate next-hop address 
used to forward transit packets to the associated destinations.</t>
          <t>The immediate next-hop address is determined by performing a
recursive route lookup operation for the IP address in the NEXT_HOP
attribute, using the contents of the Routing Table, selecting one
entry if multiple entries of equal cost exist.  The Routing Table
entry that resolves the IP address in the NEXT_HOP attribute will
always specify the outbound interface.  If the entry specifies an
attached subnet, but does not specify a next-hop address, then the
address in the NEXT_HOP attribute <bcp14>SHOULD</bcp14> be used as the immediate
next-hop address.  If the entry also specifies the next-hop address,
this address <bcp14>SHOULD</bcp14> be used as the immediate next-hop address for
packet forwarding.</t>
        </section>
        <section anchor="med">
          <name>MULTI_EXIT_DISC</name>
          <t>The MULTI_EXIT_DISC is an optional non-transitive attribute that is
intended to be used on external (inter-AS) links to discriminate
among multiple exit points to reach the same neighboring AS.  The
value of the MULTI_EXIT_DISC attribute is a four-octet unsigned
number, called a metric.  All other factors being equal, the exit
point with the lower metric is preferred.  If received over
EBGP, the MULTI_EXIT_DISC attribute <bcp14>MAY</bcp14> be propagated over IBGP to
other BGP speakers within the same AS (see also <xref target="phase2tiebreak"/>).  The
MULTI_EXIT_DISC attribute received from a neighboring AS <bcp14>MUST NOT</bcp14> be
propagated to other neighboring ASes.</t>
          <t>A BGP speaker <bcp14>MUST</bcp14> implement a mechanism (based on local
configuration) that allows the MULTI_EXIT_DISC attribute to be
removed from a route.  If a BGP speaker is configured to remove the
MULTI_EXIT_DISC attribute from a route, then this removal <bcp14>MUST</bcp14> be
done prior to determining the degree of preference of the route and
prior to performing route selection (Decision Process phases 1 and
2).</t>
          <t>An implementation <bcp14>MAY</bcp14> also (based on local configuration) alter the
value of the MULTI_EXIT_DISC attribute received over EBGP.  If a BGP
speaker is configured to alter the value of the MULTI_EXIT_DISC
attribute received over EBGP, then altering the value <bcp14>MUST</bcp14> be done
prior to determining the degree of preference of the route and prior
to performing route selection (Decision Process phases 1 and 2).  See
<xref target="phase2tiebreak"/> for necessary restrictions on this.</t>
        </section>
        <section anchor="localpref">
          <name>LOCAL_PREF</name>
          <t>LOCAL_PREF <bcp14>SHALL</bcp14> be included in all UPDATE messages that a given BGP
speaker sends to other internal peers.  A BGP speaker <bcp14>SHALL</bcp14> calculate
the degree of preference for each external route based on the
locally-configured policy, and include the degree of preference when
advertising a route to its internal peers.  The higher degree of
preference <bcp14>MUST</bcp14> be preferred. A BGP speaker uses the degree of
preference learned via LOCAL_PREF in its Decision Process (see
<xref target="phase1"/>).</t>
          <t>A BGP speaker <bcp14>MUST NOT</bcp14> include this attribute in UPDATE messages it
sends to external peers, except in the case of BGP Confederations
<xref target="RFC5065"/>.</t>
        </section>
        <section anchor="atomic">
          <name>ATOMIC_AGGREGATE</name>
          <!-- xxx Aggregation behavior is currently specified both here and
in "Aggregating Routing Information". Consider restructuring so
that normative aggregation requirements appear in only one place. -->

<t>When a BGP speaker aggregates several routes for the purpose of
advertisement to a particular peer, the AS_PATH of the aggregated route
might exclude some of the AS numbers present in the constituent routes.</t>
          <t>If an aggregate excludes at least some of the AS numbers present in the
AS_PATH of the routes that are aggregated, the aggregated route, when
advertised to the peer, <bcp14>SHOULD</bcp14> <!-- consider upgrading to MUST -->
include the ATOMIC_AGGREGATE attribute.</t>
          <t>A BGP speaker that receives a route with the ATOMIC_AGGREGATE
attribute <bcp14>SHOULD NOT</bcp14> remove the attribute when propagating the route
to other speakers. <!-- same here -->
          </t>
          <t>A BGP speaker that receives a route with the ATOMIC_AGGREGATE
attribute <bcp14>MUST NOT</bcp14> make any NLRI of that route more specific (as
defined in <xref target="overlap"/>) when advertising this route to other BGP speakers.</t>
          <t>A BGP speaker that receives a route with the ATOMIC_AGGREGATE
attribute needs to be aware of the fact that the actual path to
destinations, as specified in the NLRI of the route, while having the
loop-free property, may not be the path specified in the AS_PATH
attribute of the route.</t>
        </section>
        <section anchor="aggregator">
          <name>AGGREGATOR</name>
          <t>AGGREGATOR is an optional transitive attribute, which <bcp14>MAY</bcp14> be included in
updates that are formed by aggregation (see <xref target="aggregating"/>).  A BGP
speaker that performs route aggregation <bcp14>MAY</bcp14> add the AGGREGATOR
attribute, which <bcp14>SHALL</bcp14> contain its own AS number and BGP Identifier.</t>
          <t>(The format of this attribute is different if backward compatibility
procedures are in use; see <xref target="as2byte"/> for details.)</t>
        </section>
      </section>
    </section>
    <section anchor="errorhandling">
      <name>BGP Error Handling</name>
      <t>This section describes actions to be taken when errors are detected
while processing BGP messages. In states other than Established,
any error is treated as fatal. In Established state, some errors 
are treated as non-fatal; this is discussed in more detail in
<xref target="updatemsgerr"/>.</t>
      <section anchor="fatalerrors">
        <name>Fatal Error Handling</name>
        <t>When any of the conditions described here are detected, for any
Message Header error, or an error in any message type other than the 
UPDATE message, a
NOTIFICATION message, with the indicated Error Code, Error Subcode,
and Data fields, is sent, and the BGP connection is closed (unless it
is explicitly stated that no NOTIFICATION message is to be sent and
the BGP connection is not to be closed).  If no Error Subcode is
specified, then a zero <bcp14>MUST</bcp14> be used. For errors affecting the UPDATE
message, see further details in <xref target="updatemsgerr"/>.</t>
        <t>The phrase "the BGP connection is closed" means the TCP connection
has been closed, the associated Adj-RIB-In has been cleared, and all
resources for that BGP connection have been deallocated.  Entries in
the Loc-RIB associated with the remote peer are marked as invalid.
The local system recalculates its best routes for the destinations of
the routes marked as invalid.  Before the invalid routes are deleted
from the system, it advertises, to its peers, either withdraws for
the routes marked as invalid, or the new best routes.</t>
        <t>Unless specified explicitly, the Data field of the NOTIFICATION
message that is sent to indicate an error is empty.</t>
      </section>
      <section anchor="msgheadererr">
        <name>Message Header Error Handling</name>
        <t>All errors detected while processing the Message Header <bcp14>MUST</bcp14> be
indicated by sending the NOTIFICATION message with the Error Code
Message Header Error.  The Error Subcode elaborates on the specific
nature of the error.</t>
        <t>The expected value of the Marker field of the message header is all
ones.  If the Marker field of the message header is not as expected,
then a synchronization error has occurred and the Error Subcode <bcp14>MUST</bcp14>
be set to Connection Not Synchronized.</t>
        <t>If at least one of the following is true:</t>
        <ul spacing="normal">
          <li>
            <t>if the Length field of the message header is less than 19 or
greater than 4096 (the upper limit is modified by <xref target="RFC8654"/>, if
used), or</t>
          </li>
          <li>
            <t>if the Length field of an OPEN message is less than the minimum
length of the OPEN message, or</t>
          </li>
          <li>
            <t>if the Length field of an UPDATE message is less than the
minimum length of the UPDATE message, or</t>
          </li>
          <li>
            <t>if the Length field of a KEEPALIVE message is not equal to 19,
or</t>
          </li>
          <li>
            <t>if the Length field of a NOTIFICATION message is less than the
minimum length of the NOTIFICATION message,</t>
          </li>
        </ul>
        <t>then the Error Subcode <bcp14>MUST</bcp14> be set to Bad Message Length.  The Data
field <bcp14>MUST</bcp14> contain the erroneous Length field.</t>
        <t>If the Type field of the message header is not recognized, then the
Error Subcode <bcp14>MUST</bcp14> be set to Bad Message Type.  The Data field <bcp14>MUST</bcp14>
contain the erroneous Type field.</t>
      </section>
      <section anchor="openmsgerr">
        <name>OPEN Message Error Handling</name>
        <t>All errors detected while processing the OPEN message <bcp14>MUST</bcp14> be
indicated by sending the NOTIFICATION message with the Error Code
OPEN Message Error.  The Error Subcode elaborates on the specific
nature of the error.</t>
        <t>If the version number in the Version field of the received OPEN
message is not supported, then the Error Subcode <bcp14>MUST</bcp14> be set to
Unsupported Version Number.  The Data field is a 2-octet unsigned
integer, which indicates the largest, locally-supported version
number less than the version the remote BGP peer bid (as indicated in
the received OPEN message), or if the smallest, locally-supported
version number is greater than the version the remote BGP peer bid,
then the smallest, locally-supported version number.</t>
        <t>If the Autonomous System field of the OPEN message is unacceptable, then
the Error Subcode <bcp14>MUST</bcp14> be set to Bad Peer AS.  Autonomous System number
0 is unacceptable. Beyond this requirement, the determination of
acceptable Autonomous System numbers is outside the scope of this
protocol.</t>
        <t>If the Hold Time field of the OPEN message is unacceptable, then the
Error Subcode <bcp14>MUST</bcp14> be set to Unacceptable Hold Time.  An
implementation <bcp14>MUST</bcp14> reject Hold Time values of one or two seconds.
An implementation <bcp14>MAY</bcp14> reject any proposed Hold Time.  An
implementation that accepts a Hold Time <bcp14>MUST</bcp14> use the negotiated value
for the Hold Time.</t>
        <t>If the BGP Identifier field of the OPEN message is zero, or if it
is the same as the BGP Identifier of the local BGP speaker and the
message is from an internal peer, then the Error Subcode is set to
"Bad BGP Identifier".</t>
        <t>If one of the Optional Parameters in the OPEN message is not
recognized, then the Error Subcode <bcp14>MUST</bcp14> be set to Unsupported
Optional Parameters. Note that a peer that does not support the
extended OPEN format defined in this specification (<xref target="openfmt-ext"/>) would
send such an error in response to receipt of an OPEN message that uses
the extended format.</t>
        <t>If an Optional Parameter with type code 255 is encountered in any
position other than that depicted as "Non-Ext OP Type" in <xref target="ext-open"/>
it <bcp14>MUST</bcp14> be treated as an unrecognized Optional Parameter and handled per
the above paragraph.</t>
        <t>If one of the Optional Parameters in the OPEN message is recognized,
but is malformed, then the Error Subcode <bcp14>MUST</bcp14> be set to 0
(Unspecific).</t>
        <section anchor="caperror">
          <name>Capabilities Optional Parameter Error Handling</name>
          <t>If the BGP speaker is configured to require support for a certain
capability, and determines that its peer doesn't support this
capability, the speaker <bcp14>MAY</bcp14> terminate peering. If it does so, then the
Error Subcode <bcp14>MUST</bcp14> be set to 7 (Required Capability Not Received). The
Data field in the NOTIFICATION message <bcp14>MUST</bcp14> list the set of required
capabilities that were missing.  Each such capability is encoded in the
same way as it would be encoded in the OPEN message.</t>
          <t>The decision to send the message and terminate the peering is local to
the speaker.  If terminated, such peering <bcp14>SHOULD NOT</bcp14> be re-established
automatically.</t>
          <t>For example, a BGP speaker may need to terminate peering if it
established peering to exchange IPv6 routes and determines that its peer
does not support Multiprotocol Extensions for BGP-4 <xref target="RFC4760"/>.</t>
          <t>If the BGP speaker receives from its peer a capability that it does not
itself support or recognize, it <bcp14>MUST</bcp14> ignore that capability.  In
particular, a NOTIFICATION message <bcp14>MUST NOT</bcp14> be generated and the BGP
session <bcp14>MUST NOT</bcp14> be terminated in response to reception of a capability
that is not supported by the local speaker.</t>
        </section>
      </section>
      <section anchor="updatemsgerr">
        <name>UPDATE Message Error Handling</name>
        <t>Because resets of sessions that have reached Established state and
exchanged many routes can be costly to recover from and have far-reaching
impact, other error-handling approaches are used when feasible; these are
detailed below.</t>
        <t>An implementation <bcp14>MAY</bcp14> offer a configuration option to disable this more
lenient error-handling and revert to the reset behavior that was
specified in <xref target="RFC4271"/>. If such a configuration option is offered, it
<bcp14>MUST</bcp14> be disabled by default (i.e. the behavior specified below must be
enabled by default). Furthermore, if offered, it is suggested that its
scope be limited (for example, to a given AFI/SAFI or a given session)
by default.</t>
        <t>In the procedures below, reference is made to AFI, SAFI, MP_REACH_NLRI,
and MP_UNREACH_NLRI. These are specified in <xref target="RFC4760"/>; additionally,
brief definitions can be found in <xref target="definitions"/>. Although they are
defined outside this specification, they are discussed here because 
they are integral to the procedures defined in this section.</t>
        <section anchor="errapproaches">
          <name>Error-Handling Approaches</name>
          <t>In this document, we refer to four different approaches to handle path
attribute errors.  They are as follows (listed in order, from the one with
the "strongest" action to the one with the "weakest" action). Actions
other than "session reset" apply only to errors found in an UPDATE
message.</t>
          <ul spacing="normal">
            <li>
              <t>Session reset: A fatal error. A NOTIFICATION is sent and the session
terminated, as described in <xref target="fatalerrors"/>.</t>
            </li>
            <li>
              <t>AFI/SAFI disable: Section 7 of <xref target="RFC4760"/> allows a BGP speaker that
detects an error in a message for a given AFI/SAFI to optionally "ignore
all the subsequent routes with that AFI/SAFI received over that
session".  We refer to this as "disabling a particular AFI/SAFI" or
"AFI/SAFI disable".
 <!-- XXX but we haven't introduced the concept of afi/safi -->
 <!-- XXX revise this -->
              </t>
            </li>
            <li>
              <t>Treat-as-withdraw: In this approach, the UPDATE message containing the
path attribute in question <bcp14>MUST</bcp14> be treated as though all contained
routes had been withdrawn just as if they had been listed in the
Withdrawn Routes field (or in the MP_UNREACH_NLRI attribute if
appropriate) of the UPDATE message, thus causing them to be removed from
the Adj-RIB-In according to the procedures of <xref target="updatemsg"/>. For this
approach to be used, the NLRI need to be successfully parsed; this is
discussed in more detail in <xref target="nlrisyntax"/>.</t>
            </li>
            <li>
              <t>Attribute discard: In this approach, the malformed path attribute <bcp14>MUST</bcp14>
be discarded and the UPDATE message continues to be processed. This
approach <bcp14>MUST NOT</bcp14> be used except in the case of an attribute that has no
effect on route selection or installation.</t>
            </li>
          </ul>
        </section>
        <section anchor="path-attribute-length-fields">
          <name>Path Attribute Length Fields</name>
          <t>There are two error cases in which the Total Attribute Length value can
conflict with the enclosed path attributes, which themselves carry
length values:</t>
          <ul spacing="normal">
            <li>
              <t>In the first case, the length of the last encountered path attribute
would cause the Total Attribute Length to be exceeded when parsing the
enclosed path attributes.</t>
            </li>
            <li>
              <t>In the second case, fewer than three octets remain (or fewer than four
octets, if the Attribute Flags field has the Extended Length bit set)
when beginning to parse the attribute.  That is, this case exists if
there remains unconsumed data in the path attributes but yet
insufficient data to encode a single minimum- sized path attribute.</t>
            </li>
          </ul>
          <t>In either of these cases, an error condition exists and the "treat-
as-withdraw" approach <bcp14>MUST</bcp14> be used (unless some other, more severe error
is encountered dictating a stronger approach), and the Total Attribute
Length <bcp14>MUST</bcp14> be relied upon to enable the beginning of the NLRI field to
be located.</t>
          <t>For all path attributes other than those specified as having an
attribute length that may be zero, it <bcp14>SHALL</bcp14> be considered a syntax error <!-- xxx is this needed? as clear as possible? -->
for the attribute to have a length of zero.  Of the path attributes
considered in this specification, only AS_PATH and ATOMIC_AGGREGATE can
validly have an attribute length of zero.</t>
        </section>
        <section anchor="nlrisyntax">
          <name>Parsing of Network Layer Reachability Information (NLRI) Fields</name>
          <section anchor="encoding-nlri">
            <name>Encoding NLRI</name>
            <t>To facilitate the determination of the NLRI field in an UPDATE message
with a malformed attribute:</t>
            <ul spacing="normal">
              <li>
                <t>The MP_REACH_NLRI or MP_UNREACH_NLRI attribute (if present) <bcp14>SHALL</bcp14> be
encoded as the very first path attribute in an UPDATE message.</t>
              </li>
              <li>
                <t>An UPDATE message <bcp14>MUST NOT</bcp14> contain more than one of the following:
non-empty Withdrawn Routes field, non-empty Network Layer Reachability
Information field, MP_REACH_NLRI attribute, and MP_UNREACH_NLRI
attribute. <!-- xxx make sure that the field restrictions are reflected
in the relevant field definitions. -->
                </t>
              </li>
            </ul>
            <t>Since older BGP speakers might not implement these restrictions, an
implementation <bcp14>MUST</bcp14> still be prepared to receive these fields in any
position or combination.</t>
            <t>If the legacy IPv4 encoding is used, the NLRI field for the IPv4
unicast address family is carried immediately following all the
attributes in an UPDATE message.  When such an UPDATE message is
received, the location of the NLRI field can be determined using the
Message Length, Withdrawn Route Length, and Total Attribute Length (when
they are consistent) carried in the message instead of relying on the
length of individual attributes in the message.</t>
          </section>
          <section anchor="missing-nlri">
            <name>Missing NLRI</name>
            <t><xref target="RFC4724"/> specifies an End-of-RIB message (EoR) that can be encoded as
an UPDATE message that contains only an MP_UNREACH_NLRI attribute that
encodes no NLRI (it can also be a completely empty UPDATE message in the
case of the legacy IPv4 encoding).  In all other well-specified cases, an
UPDATE message either carries only withdrawn routes (either in the
Withdrawn Routes field or the MP_UNREACH_NLRI attribute) or it
advertises reachable routes (either in the Network Layer Reachability
Information field or the MP_REACH_NLRI attribute).</t>
            <t>Thus, if an UPDATE message is encountered that does contain path
attributes other than MP_UNREACH_NLRI and doesn't encode any reachable
NLRI, we cannot be confident that the NLRI have been successfully
parsed. For this reason, if any path attribute errors are encountered in
such an UPDATE message and if any encountered error specifies an
error-handling approach other than "attribute discard", then the
"session reset" approach <bcp14>MUST</bcp14> be used.</t>
          </section>
          <section anchor="syntactic-correctness-of-nlri-fields">
            <name>Syntactic Correctness of NLRI Fields</name>
            <t>The NLRI field or Withdrawn Routes field <bcp14>SHALL</bcp14> be considered
"syntactically incorrect" if either of the following is true:</t>
            <ul spacing="normal">
              <li>
                <t>The length of any of the included NLRI is greater than 32.</t>
              </li>
              <li>
                <t>When parsing NLRI contained in the field, the length of the last NLRI
found exceeds the amount of unconsumed data remaining in the field.</t>
              </li>
            </ul>
            <t>Similarly, an MP_REACH_NLRI or MP_UNREACH_NLRI attribute 
<bcp14>SHALL</bcp14> be considered to be incorrect if any of the following are true:</t>
            <ul spacing="normal">
              <li>
                <t>The length of any of the included NLRI is inconsistent with the given
AFI/SAFI (for example, if an IPv4 NLRI has a length greater than 32 or
an IPv6 NLRI has a length greater than 128).</t>
              </li>
              <li>
                <t>When parsing NLRI contained in the attribute, the length of the last
NLRI found exceeds the amount of unconsumed data remaining in the
attribute.</t>
              </li>
              <li>
                <t>The attribute flags of the attribute are inconsistent with those
specified in <xref target="RFC4760"/>.</t>
              </li>
              <li>
                <t>The length of the MP_UNREACH_NLRI attribute is less than 3, or the
length of the MP_REACH_NLRI attribute is less than 5.</t>
              </li>
            </ul>
          </section>
          <section anchor="typed-nlri">
            <name>Typed NLRI</name>
            <t>Certain address families, for example, MCAST-VPN <xref target="RFC6514"/>, MCAST-VPLS
<xref target="RFC7117"/>, and EVPN <xref target="RFC7432"/> have NLRI that are typed.  Since
supported type values within the address family are not expressed in the
Multiprotocol BGP (MP-BGP) capability <xref target="RFC4760"/>, it is possible for a
BGP speaker to advertise support for the given address family and
subaddress family while still not supporting a particular type of NLRI
within that AFI/SAFI.</t>
            <t>A BGP speaker advertising support for such a typed address family <bcp14>MUST</bcp14>
handle routes with unrecognized NLRI types within that address family by
discarding them, unless the relevant specification for that address
family specifies otherwise.</t>
          </section>
        </section>
        <section anchor="rules-for-processing-update-messages">
          <name>Rules for Processing UPDATE Messages</name>
          <t>An error for which a session reset is specified <bcp14>MUST</bcp14> be indicated by
sending the NOTIFICATION message with the Error Code UPDATE Message
Error.  The error subcode elaborates on the specific nature of the
error.</t>
          <t>Error checking of an UPDATE message begins by examining the path
attributes.  If the Withdrawn Routes Length or Total Attribute Length
is too large (i.e., if Withdrawn Routes Length + Total Attribute
Length + 23 exceeds the message Length), the "session reset" approach
is used. The Error Subcode <bcp14>MUST</bcp14> be set to Malformed Attribute List.</t>
          <t>If the value of either the Optional or Transitive bits in the Attribute
Flags conflicts with their specified values, then the attribute <bcp14>MUST</bcp14> be
treated as malformed and the "treat-as-withdraw" approach used, unless
the specification for the attribute mandates different handling for
incorrect Attribute Flags.</t>
          <t>If any attribute is received with its Optional bit clear, but is not 
recognized, the "treat-as-withdraw" approach <bcp14>MUST</bcp14> be used.</t>
          <t>Type-specific error handling procedures for attributes specified in this
document are given in <xref target="paerrs"/>. If an optional attribute is
recognized, then the error handling specified for that attribute must be
performed.</t>
          <t>If the MP_REACH_NLRI attribute or the MP_UNREACH_NLRI <xref target="RFC4760"/>
attribute appears more than once in the UPDATE message, then a
NOTIFICATION message <bcp14>MUST</bcp14> be sent with the Error Subcode "Malformed
Attribute List".  If any other attribute (whether recognized or
unrecognized) appears more than once in an UPDATE message, then all the
occurrences of the attribute other than the first one <bcp14>SHALL</bcp14> be discarded
and the UPDATE message will continue to be processed.</t>
          <t>The NLRI and Withdrawn Routes fields in the UPDATE message are checked
for syntactic validity per <xref target="nlrisyntax"/>.  If either field is syntactically
incorrect, then a NOTIFICATION message <bcp14>MUST</bcp14> be sent with the Error
Subcode Invalid Network Field.  <!-- could cover MP_ _NLRI here too -->
          </t>
          <t>If a prefix in the NLRI field is semantically incorrect (e.g., an
unexpected multicast IP address), an error <bcp14>SHOULD</bcp14> be logged locally,
and the prefix <bcp14>SHOULD</bcp14> be ignored. <!-- this is ok as written because it's the *prefix* that's 
being ignored, so it could never have been accepted to begin with, so
there's nothing to t-a-w -->
          </t>
          <t>An UPDATE message that contains correct path attributes, but no NLRI,
<bcp14>SHALL</bcp14> be treated as a valid UPDATE message.</t>
        </section>
        <section anchor="paerrs">
          <name>Error-Handling Procedures for Path Attributes</name>
          <t>The following subsections elaborate on the conditions for error-checking
various path attributes and specify what approach(es) should be used to
handle malformations.  It is possible that implementations may apply
other error checks not contemplated here. If so, the error handling
approach given here should generally be applied.</t>
          <section anchor="origin-error-handling">
            <name>ORIGIN Error Handling</name>
            <!-- I wanted to just call this subsection "ORIGIN", similarly for
 the following subsections. But that appeared to give the tooling 
 fits; apparently it doesn't like duplicate section titles? It's OK
 to leave it as it is now, but it would be nicer (IMO) if there were
 a way to revert to the terser title. It's contextualized by the 
 parent section, after all. -->

<t>The attribute is considered malformed if its length is not 1 or if it
has an undefined value.</t>
            <t>An UPDATE message with a malformed ORIGIN attribute, or with a missing
ORIGIN attribute, <bcp14>SHALL</bcp14> be handled using the approach of
"treat-as-withdraw".</t>
          </section>
          <section anchor="aspath-error-handling">
            <name>AS_PATH Error Handling</name>
            <t>An AS_PATH is considered malformed if it contains AS 0 in any position.
It is considered malformed if it contains an AS_SET unless acceptance
of AS_SETS has been enabled by local configuration. It is also
considered malformed if an unrecognized segment type is encountered or
if it contains a malformed segment.  A segment is considered malformed
if any of the following are true:</t>
            <ul spacing="normal">
              <li>
                <t>There is an overrun where the Path Segment Length field of the last
segment encountered would cause the Attribute Length to be exceeded.</t>
              </li>
              <li>
                <t>There is an underrun where after the last successfully parsed segment
there is only a single octet remaining (that is, there is not enough
unconsumed data to provide even an empty segment header).</t>
              </li>
              <li>
                <t>It has a Path Segment Length field of zero.</t>
              </li>
            </ul>
            <t>An UPDATE message with a malformed AS_PATH attribute, or with a missing
AS_PATH attribute, <bcp14>SHALL</bcp14> be handled using the approach of 
"treat-as-withdraw". <!-- but bgpsec changes this -->
            </t>
            <t>If the UPDATE message is received from an external peer, the local
system <bcp14>MAY</bcp14> check whether the leftmost (with respect to the position of
octets in the protocol message) AS in the AS_PATH attribute is equal to
the autonomous system number of the peer that sent the message.  If the
check determines this is not the case, the attribute <bcp14>MUST</bcp14> be treated as
malformed and the "treat-as-withdraw" approach used (unless this default
is overridden by configuration).  This is a case of semantic, not
syntactic, invalidity.</t>
          </section>
          <section anchor="nexthop-error-handling">
            <name>NEXT_HOP Error Handling</name>
            <t>The attribute is considered malformed if its length is not 4.</t>
            <t>If the NEXT_HOP attribute field is syntactically incorrect (does not
represent a valid IP host address), the attribute <bcp14>MUST</bcp14> be treated as
malformed.</t>
            <t>An UPDATE message with a malformed NEXT_HOP attribute <bcp14>SHALL</bcp14> be handled
using the approach of "treat-as-withdraw". If the NEXT_HOP attribute
is missing, and if the UPDATE message uses the IPv4 legacy encoding, then
the update <bcp14>SHALL</bcp14> use the "treat-as-withdraw" approach.</t>
            <t>The IP address in the NEXT_HOP <bcp14>MUST</bcp14> meet the following criteria to be
considered semantically correct:</t>
            <ol spacing="normal" type="%c)"><li>
                <t>It <bcp14>MUST NOT</bcp14> be the IP address of the receiving speaker.</t>
              </li>
              <li>
                <t>In the case of EBGP, where the sender and receiver are one
 IP hop away from each other, either the IP address in the
 NEXT_HOP <bcp14>MUST</bcp14> be the sender's IP address that is used to
 establish the BGP connection, or the interface associated with
 the NEXT_HOP IP address <bcp14>MUST</bcp14> share a common subnet with the
 receiving BGP speaker.</t>
              </li>
            </ol>
            <t>If the NEXT_HOP attribute is semantically incorrect, the error <bcp14>SHOULD</bcp14> be
logged, and the "treat-as-withdraw" approach used.</t>
          </section>
          <section anchor="multiexitdisc-error-handling">
            <name>MULTI_EXIT_DISC Error Handling</name>
            <t>The attribute is considered malformed if its length is not 4.</t>
            <t>An UPDATE message with a malformed MULTI_EXIT_DISC attribute <bcp14>SHALL</bcp14> be
handled using the approach of "treat-as-withdraw".</t>
          </section>
          <section anchor="localpref-error-handling">
            <name>LOCAL_PREF Error Handling</name>
            <t>If the attribute is received from an external neighbor, it <bcp14>SHALL</bcp14> be
discarded using the approach of "attribute discard".</t>
            <t>If the attribute is received from an internal neighbor, it <bcp14>SHALL</bcp14> be
considered malformed if its length is not equal to 4.  If malformed, the
UPDATE message <bcp14>SHALL</bcp14> be handled using the approach of "treat-as-
withdraw".</t>
          </section>
          <section anchor="atomicaggregate-error-handling">
            <name>ATOMIC_AGGREGATE Error Handling</name>
            <t>The attribute <bcp14>SHALL</bcp14> be considered malformed if its length is not 0.</t>
            <t>An UPDATE message with a malformed ATOMIC_AGGREGATE attribute <bcp14>SHALL</bcp14> be
handled using the approach of "attribute discard".</t>
          </section>
          <section anchor="aggregator-error-handling">
            <name>AGGREGATOR Error Handling</name>
            <t>The AGGREGATOR attribute <bcp14>SHALL</bcp14> be considered malformed if any of the
following applies:</t>
            <ul spacing="normal">
              <li>
                <t>Its length is not 6 (when the 4-octet AS number capability is not
advertised to or not received from the peer <xref target="RFC6793"/>).</t>
              </li>
              <li>
                <t>Its length is not 8 (when the 4-octet AS number capability is both
advertised to and received from the peer).</t>
              </li>
              <li>
                <t>The AS number it conveys is equal to 0.</t>
              </li>
            </ul>
            <t>An UPDATE message with a malformed AGGREGATOR attribute <bcp14>SHALL</bcp14> be handled
using the approach of "attribute discard".</t>
          </section>
        </section>
      </section>
      <section anchor="notification-message-error-handling">
        <name>NOTIFICATION Message Error Handling</name>
        <t>If a peer sends a NOTIFICATION message, and the receiver of the
message detects an error in that message, the receiver cannot use a
NOTIFICATION message to report this error back to the peer.  Any such
error (e.g., an unrecognized Error Code or Error Subcode) <bcp14>SHOULD</bcp14> be
noticed, logged locally, and brought to the attention of the
administration of the peer.  The means to do this, however, lies
outside the scope of this document.</t>
      </section>
      <section anchor="holdtimerexperr">
        <name>Hold Timer Expired Error Handling</name>
        <t>If a system does not receive successive KEEPALIVE, UPDATE, and/or
NOTIFICATION messages within the period specified in the Hold Time
field of the OPEN message, then the NOTIFICATION message with the
Hold Timer Expired Error Code is sent and the BGP connection is
closed.</t>
      </section>
      <section anchor="sendholdtimerexperr">
        <name>Send Hold Timer Expired Error Handling</name>
        <t>If the SendHoldTimer expires, then a NOTIFICATION message with the 
"Send Hold Timer Expired" Error Code <bcp14>MAY</bcp14> be sent and the BGP 
connection <bcp14>MUST</bcp14> be closed. Additionally, an error <bcp14>MUST</bcp14> be logged
in the local system, indicating the "Send Hold Timer Expired" Error 
Code.</t>
        <t>The subcode for NOTIFICATION message "Send Hold Timer Expired" is set
to 0 and is not used; no additional data is to be appended to the end
of a "Send Hold Timer Expired" NOTIFICATION message.</t>
      </section>
      <section anchor="fsmerr">
        <name>Finite State Machine Error Handling</name>
        <!-- need a variable for AS_SET support -->

<t>If a BGP speaker receives an unexpected message (e.g., 
KEEPALIVE/UPDATE/ROUTE-REFRESH message) on a session in OpenSent state,
it <bcp14>MUST</bcp14> send to the neighbor a NOTIFICATION message with the Error Code
Finite State Machine Error and the Error Subcode "Receive Unexpected
Message in OpenSent State".  The Data field is a 1-octet, unsigned
integer that indicates the type of the unexpected message.</t>
        <t>If a BGP speaker receives an unexpected message (e.g., 
OPEN/UPDATE/ROUTE-REFRESH message) on a session in OpenConfirm state, it
<bcp14>MUST</bcp14> send a NOTIFICATION message with the Error Code Finite State
Machine Error and the Error Subcode "Receive Unexpected Message in
OpenConfirm State" to the neighbor.  The Data field is a 1-octet,
unsigned integer that indicates the type of the unexpected message.</t>
        <t>If a BGP speaker receives an unexpected message (e.g., OPEN message)
on a session in Established State, it <bcp14>MUST</bcp14> send to the neighbor a
NOTIFICATION message with the Error Code Finite State Machine Error
and the Error Subcode "Receive Unexpected Message in Established
State".  The Data field is a 1-octet, unsigned integer that indicates
the type of the unexpected message.</t>
        <t>Any other error detected by the BGP Finite State Machine (e.g., receipt of
an unexpected event) is indicated by sending the NOTIFICATION message
with the Error Code Finite State Machine Error and the Error Subcode 
"Unspecified Error".</t>
      </section>
      <section anchor="ceaseerr">
        <name>Cease</name>
        <section anchor="sending-a-cease">
          <name>Sending a Cease</name>
          <t>In the absence of any of the conditions that are indicated in this
section, a BGP peer <bcp14>MAY</bcp14> choose, at any given time, to close its BGP
connection by sending the NOTIFICATION message with the Error Code Cease
and no subcode.  However, if a condition indicated by this section does
exist, the relevant subcode <bcp14>SHOULD</bcp14> be used.</t>
          <t>A BGP speaker <bcp14>MAY</bcp14> support the ability to impose a locally-configured,
upper bound on the number of address prefixes the speaker is willing to
accept from a neighbor.  When the upper bound is reached, the speaker,
under control of local configuration, either (a) discards new address
prefixes from the neighbor (while maintaining the BGP connection with
the neighbor), or (b) terminates the BGP connection with the neighbor.
If the BGP speaker decides to terminate its BGP connection with a
neighbor because the number of address prefixes received from the
neighbor exceeds the locally-configured, upper bound, then the speaker
<bcp14>MUST</bcp14> send the neighbor a NOTIFICATION message with the Error Code Cease
and the Error Subcode "Maximum Number of Prefixes Reached".  The speaker
<bcp14>MAY</bcp14> log this locally.  The message <bcp14>MAY</bcp14> include the Address Family
information <xref target="RFC4760"/> and the upper bound in the "Data" field, as
shown in <xref target="maxprefix"/>, where the meaning and use of the &lt;AFI, SAFI&gt;
tuple is the same as defined in <xref target="RFC4760"/>, Section 7.</t>
          <figure anchor="maxprefix">
            <artset>
              <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="160" width="272" viewBox="0 0 272 160" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                  <path d="M 8,32 L 8,128" fill="none" stroke="black"/>
                  <path d="M 264,32 L 264,128" fill="none" stroke="black"/>
                  <path d="M 8,32 L 264,32" fill="none" stroke="black"/>
                  <path d="M 8,64 L 264,64" fill="none" stroke="black"/>
                  <path d="M 8,96 L 264,96" fill="none" stroke="black"/>
                  <path d="M 8,128 L 264,128" fill="none" stroke="black"/>
                  <g class="text">
                    <text x="32" y="52">AFI</text>
                    <text x="60" y="52">(2</text>
                    <text x="104" y="52">octets)</text>
                    <text x="36" y="84">SAFI</text>
                    <text x="68" y="84">(1</text>
                    <text x="108" y="84">octet)</text>
                    <text x="44" y="116">Prefix</text>
                    <text x="96" y="116">upper</text>
                    <text x="144" y="116">bound</text>
                    <text x="180" y="116">(4</text>
                    <text x="224" y="116">octets)</text>
                  </g>
                </svg>
              </artwork>
              <artwork type="ascii-art"><![CDATA[
    +-------------------------------+
    | AFI (2 octets)                |
    +-------------------------------+
    | SAFI (1 octet)                |
    +-------------------------------+
    | Prefix upper bound (4 octets) |
    +-------------------------------+
]]></artwork>
            </artset>
          </figure>
          <t>If a BGP speaker decides to administratively shut down its peering with
a neighbor, then the speaker <bcp14>SHOULD</bcp14> send a NOTIFICATION message with the
Error Code Cease and the Error Subcode "Administrative Shutdown". If used,
<xref target="RFC9003"/> specifies additional information in the Data field.</t>
          <t>If a BGP speaker decides to de-configure a peer, then the speaker <bcp14>SHOULD</bcp14>
send a NOTIFICATION message with the Error Code Cease and the Error
Subcode "Peer De-configured".</t>
          <t>If a BGP speaker decides to administratively reset the peering with a
neighbor, then the speaker <bcp14>SHOULD</bcp14> send a NOTIFICATION message with the
Error Code Cease and the Error Subcode "Administrative Reset". If used,
<xref target="RFC9003"/> specifies additional information in the Data field.</t>
          <t>If a BGP speaker decides to disallow a BGP connection (e.g., the peer is
not configured locally) after the speaker accepts a transport protocol
connection, then the BGP speaker <bcp14>SHOULD</bcp14> send a NOTIFICATION message with
the Error Code Cease and the Error Subcode "Connection Rejected".</t>
          <t>If a BGP speaker decides to administratively reset the peering with a
neighbor due to a configuration change other than the ones described
above, then the speaker <bcp14>SHOULD</bcp14> send a NOTIFICATION message with the
Error Code Cease and the Error Subcode "Other Configuration Change".</t>
          <t>If a BGP speaker decides to send a NOTIFICATION message with the Error
Code Cease as a result of the collision resolution procedure (as
described in <xref target="collision"/>), then the subcode <bcp14>SHOULD</bcp14> be set to
"Connection Collision Resolution".</t>
          <t>If a BGP speaker runs out of resources (e.g., memory) and decides to
reset a session, then the speaker <bcp14>MAY</bcp14> send a NOTIFICATION message with
the Error Code Cease and the Error Subcode "Out of Resources".</t>
        </section>
        <section anchor="receiving-a-cease">
          <name>Receiving a Cease</name>
          <t>It is <bcp14>RECOMMENDED</bcp14> that a BGP speaker behave as though the
DampPeerOscillations attribute (<xref target="fsm"/>) were true for this peer when
re-trying a BGP connection after the speaker receives a Cease
NOTIFICATION message with a subcode of "Administrative Shutdown",
"Peer De-configured", "Connection Rejected", or "Out of Resources".
An implementation <bcp14>SHOULD</bcp14> impose an upper bound on the number of
consecutive automatic retries.  Once this bound is reached, the
implementation would stop re-trying any BGP connections until some
administrative intervention, i.e., set the AllowAutomaticStart
attribute (<xref target="fsm"/>) to FALSE.</t>
        </section>
      </section>
      <section anchor="collision">
        <name>BGP Connection Collision Detection</name>
        <t>If a pair of BGP speakers try to establish a BGP connection with each
other simultaneously, then two parallel connections will be formed.
If the source IP address used by one of these connections is the same
as the destination IP address used by the other, and the destination
IP address used by the first connection is the same as the source IP
address used by the other, a connection collision has occurred.  In the
event of connection collision, one of the connections <bcp14>MUST</bcp14> be closed.</t>
        <t>Based on the value of the BGP Identifier, a convention is established
for detecting which BGP connection is to be preserved when a
collision occurs.  The convention is to compare the BGP Identifiers
of the peers involved in the collision and to retain only the
connection initiated by the BGP speaker with the higher-valued BGP
Identifier.</t>
        <t>Upon receipt of an OPEN message, the local system <bcp14>MUST</bcp14> examine all of
its connections that are in the OpenConfirm state.  A BGP speaker <bcp14>MAY</bcp14>
also examine connections in an OpenSent state if it knows the BGP
Identifier of the peer by means outside of the protocol.  If, among
these connections, there is a connection to a remote BGP speaker
whose BGP Identifier equals the one in the OPEN message, and this
connection collides with the connection over which the OPEN message
is received, then the local system performs the following collision
resolution procedure:</t>
        <ol spacing="normal" type="1"><li>
            <t>The BGP Identifier of the local system is compared to the BGP
Identifier of the remote system (as specified in the OPEN
message).  Comparing BGP Identifiers is done by converting them
to host byte order and treating them as 4-octet unsigned
integers.</t>
          </li>
          <li>
            <t>If the value of the local BGP Identifier is less than the
remote one, the local system closes the BGP connection that
already exists (the one that is already in the OpenConfirm
state), and accepts the BGP connection initiated by the remote
system.</t>
          </li>
          <li>
            <t>In the case of an external BGP connection, if the BGP Identifiers 
of the peers involved in the connection collision are identical, 
then the connection initiated by the BGP speaker with the larger 
AS number is preserved. (If <xref target="RFC5065"/> is in use, a session 
between one member autonomous system and another member autonomous
system is not considered "external" for this purpose.)</t>
          </li>
          <li>
            <t>Otherwise, the local system closes the newly created BGP
connection (the one associated with the newly received OPEN
message), and continues to use the existing one (the one that
is already in the OpenConfirm state).</t>
          </li>
        </ol>
        <t>Unless allowed via configuration, a connection collision with an
existing BGP connection that is in the Established state causes
closing of the newly created connection.</t>
        <t>Note that a connection collision cannot be detected with connections
that are in Idle, Connect, or Active states.</t>
        <t>Closing the BGP connection (that results from the collision
resolution procedure) is accomplished by sending the NOTIFICATION
message with the Error Code Cease.</t>
      </section>
    </section>
    <section anchor="bgp-version-negotiation">
      <name>BGP Version Negotiation</name>
      <t>BGP speakers <bcp14>MAY</bcp14> negotiate the version of the protocol by making
multiple attempts at opening a BGP connection, starting with the
highest version number each BGP speaker supports.  If an open attempt
fails with an Error Code, OPEN Message Error, and an Error Subcode,
Unsupported Version Number, then the BGP speaker has available the
version number it tried, the version number its peer tried, the
version number passed by its peer in the NOTIFICATION message, and
the version numbers it supports.  If the two peers do support one or
more common versions, then this will allow them to rapidly determine
the highest common version.  In order to support BGP version
negotiation, future versions of BGP <bcp14>MUST</bcp14> retain the format of the
OPEN and NOTIFICATION messages.</t>
    </section>
    <section anchor="fsm">
      <name>BGP Finite State Machine (FSM)</name>
      <t>The data structures and FSM described in this document are conceptual
and do not have to be implemented precisely as described here, as
long as the implementations support the described functionality and
they exhibit the same externally visible behavior.</t>
      <t>This section specifies the BGP operation in terms of a Finite State
Machine (FSM).  The section falls into two parts:</t>
      <ol spacing="normal" type="1"><li>
          <t>Description of Events for the State machine (<xref target="fsmevents"/>)</t>
        </li>
        <li>
          <t>Description of the FSM (<xref target="fsmdescr"/>)</t>
        </li>
      </ol>
      <t>Session attributes required (mandatory) for each connection are:</t>
      <ol spacing="normal" type="1"><li>
          <t>State</t>
        </li>
        <li>
          <t>ConnectRetryCounter</t>
        </li>
        <li>
          <t>ConnectRetryTimer</t>
        </li>
        <li>
          <t>ConnectRetryTime</t>
        </li>
        <li>
          <t>HoldTimer</t>
        </li>
        <li>
          <t>HoldTime</t>
        </li>
        <li>
          <t>KeepaliveTimer</t>
        </li>
        <li>
          <t>KeepaliveTime</t>
        </li>
      </ol>
      <t>The state session attribute indicates the current state of the BGP
FSM.  The ConnectRetryCounter indicates the number of times a BGP
peer has tried to establish a peer session.</t>
      <t>The mandatory session attributes related to timers are described in <xref target="timers"/>
Each timer has a "timer" and a "time" (the initial value).</t>
      <t>The optional Session attributes are listed below.  These optional session attributes may be supported, either per connection or per local system:</t>
      <ol spacing="normal" type="1"><li>
          <t>AcceptConnectionsUnconfiguredPeers</t>
        </li>
        <li>
          <t>AllowAutomaticStart</t>
        </li>
        <li>
          <t>AllowAutomaticStop</t>
        </li>
        <li>
          <t>CollisionDetectEstablishedState</t>
        </li>
        <li>
          <t>DampPeerOscillations</t>
        </li>
        <li>
          <t>DelayOpen</t>
        </li>
        <li>
          <t>DelayOpenTime</t>
        </li>
        <li>
          <t>DelayOpenTimer</t>
        </li>
        <li>
          <t>IdleHoldTime</t>
        </li>
        <li>
          <t>IdleHoldTimer</t>
        </li>
        <li>
          <t>PassiveTcpEstablishment</t>
        </li>
        <li>
          <t>SendNOTIFICATIONwithoutOPEN</t>
        </li>
        <li>
          <t>TrackTcpState</t>
        </li>
        <li>
          <t>SendHoldTimer</t>
        </li>
        <li>
          <t>SendHoldTime</t>
        </li>
      </ol>
      <t>The optional session attributes support different features of the BGP functionality that have implications for the BGP FSM state transitions.  Two groups of the session attributes which relate to timers are:</t>
      <ul empty="true">
        <li>
          <t>group 1: DelayOpen, DelayOpenTime, DelayOpenTimer</t>
        </li>
      </ul>
      <ul empty="true">
        <li>
          <t>group 2: DampPeerOscillations, IdleHoldTime, IdleHoldTimer</t>
        </li>
      </ul>
      <t>The first parameter (DelayOpen, DampPeerOscillations) is an optional
session attribute that indicates that the Timer function is active.  The
"Time" value specifies the initial value for the "Timer"
(DelayOpenTime, IdleHoldTime).  The "Timer" specifies the actual
timer.</t>
      <t>Please refer to <xref target="optionalevents"/> for an explanation of the interaction
between these optional session attributes and the events signaled to the
state machine.  <xref target="optsessattrs"/> also provides a short overview of the
different types of optional session attributes (flags or timers).</t>
      <section anchor="fsmevents">
        <name>Events for the BGP FSM</name>
        <section anchor="optionalevents">
          <name>Optional Events Linked to Optional Session Attributes</name>
          <t>The Inputs to the BGP FSM are events.  Events can either be mandatory
or optional.  Some optional events are linked to optional session
attributes.  Optional session attributes enable several groups of FSM
functionality.</t>
          <t>The linkage between FSM functionality, events, and the optional
session attributes are described below.</t>
          <section anchor="group-1-automatic-administrative-events-startstop">
            <name>Group 1: Automatic Administrative Events (Start/Stop)</name>
            <dl>
              <dt>Optional Session Attributes:</dt>
              <dd>
                <t>AllowAutomaticStart,
AllowAutomaticStop,
DampPeerOscillations,
IdleHoldTime, IdleHoldTimer</t>
              </dd>
            </dl>
            <t>Option 1:    AllowAutomaticStart</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>A BGP peer connection can be started and stopped
   by administrative control.  This administrative
   control can either be manual, based on operator
   intervention, or under the control of logic that
   is specific to a BGP implementation.  The term
   "automatic" refers to a start being issued to the
   BGP peer connection FSM when such logic determines
   that the BGP peer connection should be restarted.
   The AllowAutomaticStart session attribute specifies that
   this BGP connection supports automatic starting of
   the BGP connection.</t>
              </dd>
              <dt/>
              <dd>
                <t>If the BGP implementation supports
   AllowAutomaticStart, the peer may be repeatedly
   restarted.  Three other options control the rate
   at which the automatic restart occurs:
   DampPeerOscillations, IdleHoldTime, and the
   IdleHoldTimer.</t>
              </dd>
              <dt/>
              <dd>
                <t>The DampPeerOscillations option specifies that the
   implementation engages additional logic to damp
   the oscillations of BGP peers in the face of
   sequences of automatic start and automatic stop.
   IdleHoldTime specifies the length of time the BGP
   peer is held in the Idle state prior to allowing
   the next automatic restart.  The IdleHoldTimer is
   the timer that holds the peer in Idle state.</t>
              </dd>
              <dt/>
              <dd>
                <t>An example of DampPeerOscillations logic is an
   increase of the IdleHoldTime value if a BGP peer
   oscillates connectivity (connected/disconnected)
   repeatedly within a time period.  To engage this
   logic, a peer could connect and disconnect 10
   times within 5 minutes.  The IdleHoldTime value
   would be reset from 0 to 120 seconds.</t>
              </dd>
            </dl>
            <t>Values:      TRUE or FALSE</t>
            <t>Option 2:    AllowAutomaticStop</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>This BGP peer session optional session attribute indicates
    that the BGP connection allows "automatic"
    stopping of the BGP connection.  An "automatic"
    stop is defined as a stop under the control of
    implementation-specific logic.  The
    implementation-specific logic is outside the scope
    of this specification.</t>
              </dd>
            </dl>
            <t>Values:      TRUE or FALSE</t>
            <t>Option 3:    DampPeerOscillations</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The DampPeerOscillations optional session
    attribute indicates that the BGP connection is
    using logic that damps BGP peer oscillations in
    the Idle State.</t>
              </dd>
            </dl>
            <t>Value:       TRUE or FALSE</t>
            <t>Option 4:    IdleHoldTime</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The IdleHoldTime is the value that is set in the
IdleHoldTimer.</t>
              </dd>
            </dl>
            <t>Values:      Time in seconds</t>
            <t>Option 5:    IdleHoldTimer</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The IdleHoldTimer aids in controlling BGP peer
oscillation.  The IdleHoldTimer is used to keep
the BGP peer in Idle for a particular duration.
The IdleHoldTimer_Expires event is described in
<xref target="timerevents"/>.</t>
              </dd>
            </dl>
            <t>Values:      Time in seconds</t>
          </section>
          <section anchor="group-2-unconfigured-peers">
            <name>Group 2: Unconfigured Peers</name>
            <dl>
              <dt>Optional Session Attributes:</dt>
              <dd>
                <t>AcceptConnectionsUnconfiguredPeers</t>
              </dd>
            </dl>
            <t>Option 1:    AcceptConnectionsUnconfiguredPeers</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The BGP FSM optionally allows the acceptance of
BGP peer connections from neighbors that are not
pre-configured.  The
"AcceptConnectionsUnconfiguredPeers" optional
session attribute allows the FSM to support the
state transitions that allow the implementation to
accept or reject these unconfigured peers.</t>
              </dd>
              <dt/>
              <dd>
                <t>The AcceptConnectionsUnconfiguredPeers has
security implications.  Please refer to the BGP
Vulnerabilities document <xref target="RFC4272"/> for details.</t>
              </dd>
            </dl>
            <t>Value:       True or False</t>
          </section>
          <section anchor="group-3-tcp-processing">
            <name>Group 3: TCP processing</name>
            <dl>
              <dt>Optional Session Attributes:</dt>
              <dd>
                <t>PassiveTcpEstablishment, TrackTcpState</t>
              </dd>
            </dl>
            <t>Option 1:    PassiveTcpEstablishment</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>This option indicates that the BGP FSM will
passively wait for the remote BGP peer to
establish the BGP TCP connection.</t>
              </dd>
            </dl>
            <t>value:       TRUE or FALSE</t>
            <t>Option 2:    TrackTcpState</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The BGP FSM normally tracks the end result of a
   TCP connection attempt rather than individual TCP
   messages.  Optionally, the BGP FSM can support
   additional interaction with the TCP connection
   negotiation.  The interaction with the TCP events
   may increase the amount of logging the BGP peer
   connection requires and the number of BGP FSM
   changes.</t>
              </dd>
            </dl>
            <t>Value:       TRUE or FALSE</t>
          </section>
          <section anchor="group-4-bgp-message-processing">
            <name>Group 4:  BGP Message Processing</name>
            <dl>
              <dt>Optional Session Attributes:</dt>
              <dd>
                <t>DelayOpen, DelayOpenTime,
   DelayOpenTimer,
   SendNOTIFICATIONwithoutOPEN,
   CollisionDetectEstablishedState</t>
              </dd>
            </dl>
            <t>Option 1:     DelayOpen</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The DelayOpen optional session attribute allows
  implementations to be configured to delay sending
  an OPEN message for a specific time period
  (DelayOpenTime).  The delay allows the remote BGP
  Peer time to send the first OPEN message.</t>
              </dd>
            </dl>
            <t>Value:       TRUE or FALSE</t>
            <t>Option 2:    DelayOpenTime</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The DelayOpenTime is the initial value set in the DelayOpenTimer.</t>
              </dd>
            </dl>
            <t>Value:       Time in seconds</t>
            <t>Option 3:    DelayOpenTimer</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The DelayOpenTimer optional session attribute is
   used to delay the sending of an OPEN message on a
   connection.  The DelayOpenTimer_Expires event
   (Event 12) is described in <xref target="timerevents"/>.</t>
              </dd>
            </dl>
            <t>Value:       Time in seconds</t>
            <t>Option 4:    SendNOTIFICATIONwithoutOPEN</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>The SendNOTIFICATIONwithoutOPEN allows a peer to
   send a NOTIFICATION without first sending an OPEN
   message.  Without this optional session attribute,
   the BGP connection assumes that an OPEN message
   must be sent by a peer prior to the peer sending a
   NOTIFICATION message.</t>
              </dd>
            </dl>
            <t>Value:       True or False</t>
            <t>Option 5:    CollisionDetectEstablishedState</t>
            <dl>
              <dt>Description:</dt>
              <dd>
                <t>Normally, a Detect Collision (see <xref target="collision"/>)
   will be ignored in the Established state.  This
   optional session attribute indicates that this BGP
   connection processes collisions in the Established
   state.</t>
              </dd>
            </dl>
            <t>Value:       True or False</t>
            <t>Note: The optional session attributes clarify the BGP FSM
description for existing features of BGP implementations.
The optional session attributes may be pre-defined for an
implementation and not readable via management interfaces
for existing correct implementations.  As newer BGP MIBs
(version 2 and beyond) are supported, these fields will be
accessible via a management interface.</t>
          </section>
        </section>
        <section anchor="administrative-events">
          <name>Administrative Events</name>
          <t>An administrative event is an event in which the operator interface
and BGP Policy engine signal the BGP-finite state machine to start or
stop the BGP state machine.  The basic start and stop indications are
augmented by optional session attributes that signal a certain
type of start or stop mechanism to the BGP FSM.  An example of this
combination is Event 5, AutomaticStart_with_PassiveTcpEstablishment.
With this event, the BGP implementation signals to the BGP FSM that
the implementation is using an Automatic Start with the option to use
a Passive TCP Establishment.  The Passive TCP establishment signals
that this BGP FSM will wait for the remote side to start the TCP
establishment.</t>
          <t>Note that only Event 1 (ManualStart) and Event 2 (ManualStop) are
mandatory administrative events.  All other administrative events are
optional (Events 3-8).  Each event below has a name, definition, status
(mandatory or optional), and an "Optional Session Attribute Status"
field that lists the optional session attributes required to be set for
that event to occur.  When generating Event 1 through Event 8 for the
BGP FSM, an implementation <bcp14>MUST</bcp14> verify the conditions listed in that
event's Optional Session Attribute Status field before generating the
event.  If any of these conditions are not satisfied, then the local
system should log an FSM error.</t>
          <t>The settings of optional session attributes may be implicit in some
implementations, and therefore may not be set explicitly by an
external operator action.  <xref target="fsmimpldep"/> describes these implicit
settings of the optional session attributes.  The administrative
states described below may also be implicit in some implementations
and not directly configurable by an external operator.</t>
          <section anchor="event-1-manualstart">
            <name>Event 1: ManualStart</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system administrator manually starts the peer
   connection.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <t>The PassiveTcpEstablishment session attribute <bcp14>SHOULD</bcp14> be set to FALSE.</t>
              </dd>
            </dl>
          </section>
          <section anchor="event-2-manualstop">
            <name>Event 2: ManualStop</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system administrator manually stops the peer connection.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <t>No interaction with any optional session attributes.</t>
              </dd>
            </dl>
          </section>
          <section anchor="event-3-automaticstart">
            <name>Event 3: AutomaticStart</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system automatically starts the BGP connection.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The AllowAutomaticStart session attribute <bcp14>SHOULD</bcp14> be set to TRUE if this event occurs.</t>
                  </li>
                  <li>
                    <t>If the PassiveTcpEstablishment optional session attribute is supported, it <bcp14>SHOULD</bcp14> be set to FALSE.</t>
                  </li>
                  <li>
                    <t>If the DampPeerOscillations is supported, it <bcp14>SHOULD</bcp14> be set to FALSE when this event occurs.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-4-manualstartwithpassivetcpestablishment">
            <name>Event 4: ManualStart_with_PassiveTcpEstablishment</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system administrator manually starts the peer
    connection, but has PassiveTcpEstablishment
    enabled.  The PassiveTcpEstablishment optional session 
    attribute indicates that the peer will listen prior
    to establishing the connection.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The PassiveTcpEstablishment session attribute <bcp14>SHOULD</bcp14> be
set to TRUE if this event occurs.</t>
                  </li>
                  <li>
                    <t>The DampPeerOscillations session attribute <bcp14>SHOULD</bcp14> be set
to FALSE when this event occurs.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-5-automaticstartwithpassivetcpestablishment">
            <name>Event 5: AutomaticStart_with_PassiveTcpEstablishment</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system automatically starts the BGP
    connection with the PassiveTcpEstablishment
    enabled.  The PassiveTcpEstablishment optional session
    attribute indicates that the peer will listen prior
    to establishing a connection.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The AllowAutomaticStart session attribute <bcp14>SHOULD</bcp14> be set
 to TRUE.</t>
                  </li>
                  <li>
                    <t>The PassiveTcpEstablishment session attribute <bcp14>SHOULD</bcp14> be
 set to TRUE.</t>
                  </li>
                  <li>
                    <t>If the DampPeerOscillations session attribute is
 supported, the DampPeerOscillations <bcp14>SHOULD</bcp14> be
 set to FALSE.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-6-automaticstartwithdamppeeroscillations">
            <name>Event 6: AutomaticStart_with_DampPeerOscillations</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system automatically starts the BGP peer
    connection with peer oscillation damping enabled.
    The exact method of damping persistent peer
    oscillations is determined by the implementation
    and is outside the scope of this document.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system.</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The AllowAutomaticStart session attribute <bcp14>SHOULD</bcp14> be set
 to TRUE.</t>
                  </li>
                  <li>
                    <t>The DampPeerOscillations session attribute <bcp14>SHOULD</bcp14> be set
 to TRUE.</t>
                  </li>
                  <li>
                    <t>The PassiveTcpEstablishment session attribute <bcp14>SHOULD</bcp14> be
 set to FALSE.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-7-automaticstartwithdamppeeroscillationsandpassivetcpestablishment">
            <name>Event 7: AutomaticStart_with_DampPeerOscillations_and_PassiveTcpEstablishment</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system automatically starts the BGP peer
    connection with peer oscillation damping enabled
    and PassiveTcpEstablishment enabled.  The exact
    method of damping persistent peer oscillations is
    determined by the implementation and is outside the
    scope of this document.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system</t>
            <dl>
              <dt>Optional Session Attributes Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The AllowAutomaticStart session attribute <bcp14>SHOULD</bcp14> be set
 to TRUE.</t>
                  </li>
                  <li>
                    <t>The DampPeerOscillations session attribute <bcp14>SHOULD</bcp14> be set
 to TRUE.</t>
                  </li>
                  <li>
                    <t>The PassiveTcpEstablishment session attribute <bcp14>SHOULD</bcp14> be
 set to TRUE.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-8-automaticstop">
            <name>Event 8: AutomaticStop</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Local system automatically stops the BGP connection.</t>
              </dd>
              <dt/>
              <dd>
                <t>An example of an automatic stop event is exceeding
    the number of prefixes for a given peer and the
    local system automatically disconnecting the peer.</t>
              </dd>
            </dl>
            <t>Status:     Optional, depending on local system</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The AllowAutomaticStop session attribute <bcp14>SHOULD</bcp14> be TRUE.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
        </section>
        <section anchor="timerevents">
          <name>Timer Events</name>
          <section anchor="event-9-connectretrytimerexpires">
            <name>Event 9: ConnectRetryTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the ConnectRetryTimer expires.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-10-holdtimerexpires">
            <name>Event 10: HoldTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the HoldTimer expires.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-11-keepalivetimerexpires">
            <name>Event 11: KeepaliveTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the KeepaliveTimer expires.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-12-delayopentimerexpires">
            <name>Event 12: DelayOpenTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the DelayOpenTimer expires.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <t>If this event occurs,</t>
              </dd>
              <dt/>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>DelayOpen session attribute <bcp14>SHOULD</bcp14> be set to TRUE,</t>
                  </li>
                  <li>
                    <t>DelayOpenTime session attribute <bcp14>SHOULD</bcp14> be supported,</t>
                  </li>
                  <li>
                    <t>DelayOpenTimer <bcp14>SHOULD</bcp14> be supported.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-13-idleholdtimerexpires">
            <name>Event 13: IdleHoldTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the IdleHoldTimer expires,
    indicating that the BGP connection has completed
    waiting for the back-off period to prevent BGP peer
    oscillation.</t>
              </dd>
              <dt/>
              <dd>
                <t>The IdleHoldTimer is only used when the persistent
    peer oscillation damping function is enabled by
    setting the DampPeerOscillations optional session attribute
    to TRUE.</t>
              </dd>
              <dt/>
              <dd>
                <t>Implementations not implementing the persistent
    peer oscillation damping function may not have the
    IdleHoldTimer.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <t>If this event occurs:</t>
              </dd>
              <dt/>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>DampPeerOscillations session attribute <bcp14>SHOULD</bcp14> be set to
  TRUE.</t>
                  </li>
                  <li>
                    <t>IdleHoldTimer <bcp14>SHOULD</bcp14> have just expired.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
        </section>
        <section anchor="tcp-connection-based-events">
          <name>TCP Connection-Based Events</name>
          <section anchor="event-14-tcpconnectionvalid">
            <name>Event 14: TcpConnection_Valid</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Event indicating the local system reception of a
    TCP connection request with a valid source IP
    address, TCP port, destination IP address, and TCP
    Port.  The definition of invalid source and invalid
    destination IP address is determined by the
    implementation.</t>
              </dd>
              <dt/>
              <dd>
                <t>BGP's destination port <bcp14>SHOULD</bcp14> be port 179, as
    defined by IANA.</t>
              </dd>
              <dt/>
              <dd>
                <t>TCP connection request is denoted by the local
    system receiving a TCP SYN.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The TrackTcpState session attribute <bcp14>SHOULD</bcp14> be set to
  TRUE if this event occurs.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-15-tcpcrinvalid">
            <name>Event 15: Tcp_CR_Invalid</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Event indicating the local system reception of a
    TCP connection request with either an invalid
    source address or port number, or an invalid
    destination address or port number.</t>
              </dd>
              <dt/>
              <dd>
                <t>BGP destination port number <bcp14>SHOULD</bcp14> be 179, as
    defined by IANA.</t>
              </dd>
              <dt/>
              <dd>
                <t>A TCP connection request occurs when the local
    system receives a TCP SYN.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The TrackTcpState session attribute should be set to
  TRUE if this event occurs.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-16-tcpcracked">
            <name>Event 16: Tcp_CR_Acked</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Event indicating the local system's request to
    establish a TCP connection to the remote peer.</t>
              </dd>
              <dt/>
              <dd>
                <t>The local system's TCP connection sent a TCP SYN,
    received a TCP SYN/ACK message, and sent a TCP ACK.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-17-tcpconnectionconfirmed">
            <name>Event 17: TcpConnectionConfirmed</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Event indicating that the local system has received
    a confirmation that the TCP connection has been
    established by the remote site.</t>
              </dd>
              <dt/>
              <dd>
                <t>The remote peer's TCP engine sent a TCP SYN.  The
    local peer's TCP engine sent a SYN, ACK message and
    now has received a final ACK.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-18-tcpconnectionfails">
            <name>Event 18: TcpConnectionFails</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>Event indicating that the local system has received
    a TCP connection failure notice.</t>
              </dd>
              <dt/>
              <dd>
                <t>The remote BGP peer's TCP machine could have sent a
    FIN.  The local peer would respond with a FIN-ACK.
    Another possibility is that the local peer
    indicated a timeout in the TCP connection and
    downed the connection.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
        </section>
        <section anchor="bgp-message-based-events">
          <name>BGP Message-Based Events</name>
          <section anchor="event-19-bgpopen">
            <name>Event 19: BGPOpen</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a valid OPEN message has been received.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The DelayOpen optional session attribute <bcp14>SHOULD</bcp14> be set
  to FALSE.</t>
                  </li>
                  <li>
                    <t>The DelayOpenTimer <bcp14>SHOULD NOT</bcp14> be running.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-20-bgpopen-with-delayopentimer-running">
            <name>Event 20: BGPOpen with DelayOpenTimer running</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a valid OPEN message has
    been received for a peer that has a successfully
    established transport connection and is currently
    delaying the sending of a BGP open message.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>The DelayOpen session attribute <bcp14>SHOULD</bcp14> be set to TRUE.</t>
                  </li>
                  <li>
                    <t>The DelayOpenTimer <bcp14>SHOULD</bcp14> be running.</t>
                  </li>
                </ol>
              </dd>
            </dl>
          </section>
          <section anchor="event-21-bgpheadererr">
            <name>Event 21: BGPHeaderErr</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a received BGP message
    header is not valid.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-22-bgpopenmsgerr">
            <name>Event 22: BGPOpenMsgErr</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when an OPEN message has been
    received with errors.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-23-opencollisiondump">
            <name>Event 23: OpenCollisionDump</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated administratively when a
    connection collision has been detected while
    processing an incoming OPEN message and this
    connection has been selected to be disconnected.
    See <xref target="collision"/> for more information on collision
    detection.</t>
              </dd>
              <dt/>
              <dd>
                <t>Event 23 is an administrative action generated by
    implementation logic that determines whether this
    connection needs to be dropped per the rules in
    <xref target="collision"/>.  This event may occur if the FSM is
    implemented as two linked state machines.</t>
              </dd>
            </dl>
            <t>Status:     Optional</t>
            <dl>
              <dt>Optional Session Attribute Status:</dt>
              <dd>
                <t>If the state machine is to process this event in
    the Established state,</t>
              </dd>
              <dt/>
              <dd>
                <ol spacing="normal" type="1"><li>
                    <t>CollisionDetectEstablishedState optional session 
  attribute <bcp14>SHOULD</bcp14> be set to TRUE.</t>
                  </li>
                </ol>
              </dd>
              <dt/>
              <dd>
                <t>Please note: The OpenCollisionDump event can occur
    in Idle, Connect, Active, OpenSent, and OpenConfirm
    without any optional session attributes being set.</t>
              </dd>
            </dl>
          </section>
          <section anchor="event-24-notifmsgvererr">
            <name>Event 24: NotifMsgVerErr</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a NOTIFICATION message
    with "version error" is received.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-25-notifmsg">
            <name>Event 25: NotifMsg</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a NOTIFICATION message
    is received and the error code is anything but
    "version error".</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-26-keepalivemsg">
            <name>Event 26: KeepAliveMsg</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a KEEPALIVE message is
    received.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-27-updatemsg">
            <name>Event 27: UpdateMsg</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when a valid UPDATE message
    is received.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-28-updatemsgerr">
            <name>Event 28: UpdateMsgErr</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event is generated when an invalid UPDATE
message is received.</t>
              </dd>
            </dl>
            <t>Status:     Mandatory</t>
          </section>
          <section anchor="event-29-sendholdtimerexpires">
            <name>Event 29: SendHoldTimer_Expires</name>
            <dl>
              <dt>Definition:</dt>
              <dd>
                <t>An event generated when the SendHoldTimer
expires.</t>
              </dd>
            </dl>
            <t>Status: Optional</t>
          </section>
        </section>
      </section>
      <section anchor="fsmdescr">
        <name>Description of FSM</name>
        <section anchor="fsm-definition">
          <name>FSM Definition</name>
          <t>BGP <bcp14>MUST</bcp14> maintain a separate FSM for each configured peer.  Each BGP
peer paired in a potential connection will attempt to connect to the
other, unless configured to remain in the idle state, or configured
to remain passive.  For the purpose of this discussion, the active or
connecting side of the TCP connection (the side of a TCP connection
sending the first TCP SYN packet) is called outgoing.  The passive or
listening side (the sender of the first SYN/ACK) is called an
incoming connection.  (See <xref target="activepassive"/> for information on the
terms active and passive used below.)</t>
          <t>A BGP implementation <bcp14>MUST</bcp14> connect to and listen on TCP port 179 for
incoming connections in addition to trying to connect to peers.  For
each incoming connection, a state machine <bcp14>MUST</bcp14> be instantiated.
There exists a period in which the identity of the peer on the other
end of an incoming connection is known, but the BGP identifier is not
known.  During this time, both an incoming and outgoing connection
may exist for the same configured peering.  This is referred to as a
connection collision (see <xref target="collision"/>).</t>
          <t>A BGP implementation will have, at most, one FSM for each configured
peering, plus one FSM for each incoming TCP connection for which the
peer has not yet been identified.  Each FSM corresponds to exactly
one TCP connection.</t>
          <t>There may be more than one connection between a pair of peers if the
connections are configured to use a different pair of IP addresses.
This is referred to as multiple "configured peerings" to the same
peer.</t>
          <section anchor="activepassive">
            <name>Terms "active" and "passive"</name>
            <t>The terms active and passive have been in the Internet operator's
vocabulary for almost a decade and have proven useful.  The words
active and passive have slightly different meanings when applied to a
TCP connection or a peer.  There is only one active side and one
passive side to any one TCP connection, per the definition above and
the state machine below.  When a BGP speaker is configured as active,
it may end up on either the active or passive side of the connection
that eventually gets established.  Once the TCP connection is
completed, it doesn't matter which end was active and which was
passive.  The only difference is in which side of the TCP connection
has port number 179.</t>
          </section>
          <section anchor="fsm-and-collision-detection">
            <name>FSM and Collision Detection</name>
            <t>There is one FSM per BGP connection.  When the connection collision
occurs prior to determining what peer a connection is associated
with, there may be two connections for one peer.  After the
connection collision is resolved (see <xref target="collision"/>), the FSM for the
connection that is closed <bcp14>SHOULD</bcp14> be disposed.</t>
          </section>
          <section anchor="optsessattrs">
            <name>FSM and Optional Session Attributes</name>
            <t>Optional Session Attributes specify either attributes that act as
flags (TRUE or FALSE) or optional timers.  For optional session attributes
that act as flags, if the optional session attribute can be set to
TRUE on the system, the corresponding BGP FSM actions must be
supported.  For example, if the following options can be set in a BGP
implementation: AutoStart and PassiveTcpEstablishment, then Events 3,
4 and 5 must be supported.  If an Optional Session attribute cannot
be set to TRUE, the events supporting that set of options do not have
to be supported.</t>
            <t>Each of the optional timers (DelayOpenTimer and IdleHoldTimer) has a
group of session attributes that are:</t>
            <ul spacing="normal">
              <li>
                <t>flag indicating support,</t>
              </li>
              <li>
                <t>Time set in Timer</t>
              </li>
              <li>
                <t>Timer.</t>
              </li>
            </ul>
            <t>The two optional timers show this format:</t>
            <artwork><![CDATA[
DelayOpenTimer: DelayOpen, DelayOpenTime, DelayOpenTimer
IdleHoldTimer:  DampPeerOscillations, IdleHoldTime,
                IdleHoldTimer
]]></artwork>
            <t>If the flag indicating support for an optional timer (DelayOpen or
DampPeerOscillations) cannot be set to TRUE, the timers and events
supporting that option do not have to be supported.</t>
          </section>
          <section anchor="fsm-event-numbers">
            <name>FSM Event Numbers</name>
            <t>The Event numbers (1-28) utilized in this state machine description
aid in specifying the behavior of the BGP state machine.
Implementations <bcp14>MAY</bcp14> use these numbers to provide network management
information.  The exact form of an FSM or the FSM events are specific
to each implementation.</t>
          </section>
          <section anchor="fsmimpldep">
            <name>FSM Actions that are Implementation Dependent</name>
            <t>At certain points, the BGP FSM specifies that BGP initialization will
occur or that BGP resources will be deleted.  The initialization of
the BGP FSM and the associated resources depend on the policy portion
of the BGP implementation.  The details of these actions are outside
the scope of the FSM document.</t>
          </section>
        </section>
        <section anchor="finite-state-machine">
          <name>Finite State Machine</name>
          <section anchor="idle-state">
            <name>Idle state:</name>
            <t>Initially, the BGP peer FSM is in the Idle state.  Hereafter, the
BGP peer FSM will be shortened to BGP FSM.</t>
            <t>In this state, BGP FSM refuses all incoming BGP connections for this peer.  No resources are allocated to the peer.  In response to a ManualStart event (Event 1) or an AutomaticStart event (Event 3), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>initializes all BGP resources for the peer connection,</t>
              </li>
              <li>
                <t>sets ConnectRetryCounter to zero,</t>
              </li>
              <li>
                <t>starts the ConnectRetryTimer with the initial value,</t>
              </li>
              <li>
                <t>initiates a TCP connection to the other BGP peer,</t>
              </li>
              <li>
                <t>listens for a connection that may be initiated by the remote
BGP peer, and</t>
              </li>
              <li>
                <t>changes its state to Connect.</t>
              </li>
            </ul>
            <t>The ManualStop event (Event 2) and AutomaticStop (Event 8) event
are ignored in the Idle state.</t>
            <t>In response to a ManualStart_with_PassiveTcpEstablishment event (Event 4) or AutomaticStart_with_PassiveTcpEstablishment event (Event 5), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>initializes all BGP resources,</t>
              </li>
              <li>
                <t>sets the ConnectRetryCounter to zero,</t>
              </li>
              <li>
                <t>starts the ConnectRetryTimer with the initial value,</t>
              </li>
              <li>
                <t>listens for a connection that may be initiated by the remote
peer, and</t>
              </li>
              <li>
                <t>changes its state to Active.</t>
              </li>
            </ul>
            <t>The exact value of the ConnectRetryTimer is a local matter, but it
<bcp14>SHOULD</bcp14> be sufficiently large to allow TCP initialization.</t>
            <t>If the DampPeerOscillations session attribute is set to TRUE, the following three additional events may occur within the Idle state:</t>
            <ul spacing="normal">
              <li>
                <t>AutomaticStart_with_DampPeerOscillations (Event 6),</t>
              </li>
              <li>
                <t>AutomaticStart_with_DampPeerOscillations_and_
PassiveTcpEstablishment (Event 7),</t>
              </li>
              <li>
                <t>IdleHoldTimer_Expires (Event 13).</t>
              </li>
            </ul>
            <t>Upon receiving these 3 events, the local system will use these
events to prevent peer oscillations.  The method of preventing
persistent peer oscillation is outside the scope of this document.</t>
            <t>Any other event (Events 9-12, 15-28) received in the Idle state
does not cause change in the state of the local system.</t>
          </section>
          <section anchor="connect-state">
            <name>Connect State:</name>
            <t>In this state, BGP FSM is waiting for the TCP connection to be
completed.</t>
            <t>The start events (Events 1, 3-7) are ignored in the Connect state.</t>
            <t>In response to a ManualStop event (Event 2), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>sets ConnectRetryCounter to zero,</t>
              </li>
              <li>
                <t>stops the ConnectRetryTimer and sets ConnectRetryTimer to
ero, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to the ConnectRetryTimer_Expires event (Event 9), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>restarts the ConnectRetryTimer,</t>
              </li>
              <li>
                <t>stops the DelayOpenTimer and resets the timer to zero,</t>
              </li>
              <li>
                <t>initiates a TCP connection to the other BGP peer,</t>
              </li>
              <li>
                <t>continues to listen for a connection that may be initiated by the remote BGP peer, and</t>
              </li>
              <li>
                <t>stays in the Connect state.</t>
              </li>
            </ul>
            <t>If the DelayOpenTimer_Expires event (Event 12) occurs in the Connect state, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends an OPEN message to its peer,</t>
              </li>
              <li>
                <t>sets the HoldTimer to a large value, and</t>
              </li>
              <li>
                <t>changes its state to OpenSent.</t>
              </li>
            </ul>
            <t>If the BGP FSM receives a TcpConnection_Valid event (Event 14),
the TCP connection is processed, and the connection remains in the
Connect state.</t>
            <t>If the BGP FSM receives a Tcp_CR_Invalid event (Event 15), the
local system rejects the TCP connection, and the connection
remains in the Connect state.</t>
            <t>If the TCP connection succeeds (Event 16 or Event 17), the local system checks the DelayOpen session attribute prior to processing.  If the DelayOpen session attribute is set to TRUE, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>sets the DelayOpenTimer to the initial value, and</t>
              </li>
              <li>
                <t>stays in the Connect state.</t>
              </li>
            </ul>
            <t>If the DelayOpen session attribute is set to FALSE, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>completes BGP initialization</t>
              </li>
              <li>
                <t>sends an OPEN message to its peer,</t>
              </li>
              <li>
                <t>sets the HoldTimer to a large value, and</t>
              </li>
              <li>
                <t>changes its state to OpenSent.</t>
              </li>
            </ul>
            <t>A HoldTimer value of 4 minutes is suggested.</t>
            <t>If the TCP connection fails (Event 18), the local system checks the DelayOpenTimer.  If the DelayOpenTimer is running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>restarts the ConnectRetryTimer with the initial value,</t>
              </li>
              <li>
                <t>stops the DelayOpenTimer and resets its value to zero,</t>
              </li>
              <li>
                <t>continues to listen for a connection that may be initiated by
the remote BGP peer, and</t>
              </li>
              <li>
                <t>changes its state to Active.</t>
              </li>
            </ul>
            <t>If the DelayOpenTimer is not running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>releases all BGP resources, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If an OPEN message is received while the DelayOpenTimer is running (Event 20), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>completes the BGP initialization,</t>
              </li>
              <li>
                <t>stops and clears the DelayOpenTimer (sets the value to zero),</t>
              </li>
              <li>
                <t>sends an OPEN message,</t>
              </li>
              <li>
                <t>sends a KEEPALIVE message,</t>
              </li>
              <li>
                <t>if the HoldTimer initial value is non-zero,  </t>
                <ul spacing="normal">
                  <li>
                    <t>starts the KeepaliveTimer with the initial value and</t>
                  </li>
                  <li>
                    <t>resets the HoldTimer to the negotiated value,</t>
                  </li>
                </ul>
                <t>
else, if the HoldTimer initial value is zero,  </t>
                <ul spacing="normal">
                  <li>
                    <t>resets the KeepaliveTimer and</t>
                  </li>
                  <li>
                    <t>resets the HoldTimer value to zero,</t>
                  </li>
                </ul>
              </li>
              <li>
                <t>and changes its state to OpenConfirm.</t>
              </li>
            </ul>
            <t>If the value of the autonomous system field is the same as the
local Autonomous System number, set the connection status to an
internal connection; otherwise it will be "external".</t>
            <t>If BGP message header checking (Event 21) or OPEN message checking detects an error (Event 22) (see <xref target="openmsgerr"/>), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>(optionally) If the SendNOTIFICATIONwithoutOPEN session attribute is
set to TRUE, then the local system first sends a NOTIFICATION
message with the appropriate error code, and then</t>
              </li>
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If a NOTIFICATION message is received with a version error (Event 24), the local system checks the DelayOpenTimer.  If the DelayOpenTimer is running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>stops and resets the DelayOpenTimer (sets to zero),</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the DelayOpenTimer is not running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer and sets the ConnectRetryTimer to
zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>performs peer oscillation damping if the DampPeerOscillations
session attribute is set to True, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to any other events (Events 8, 10-11, 13, 19, 23, 25-28), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>if the ConnectRetryTimer is running, stops and resets the
ConnectRetryTimer (sets to zero),</t>
              </li>
              <li>
                <t>if the DelayOpenTimer is running, stops and resets the
DelayOpenTimer (sets to zero),</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>performs peer oscillation damping if the DampPeerOscillations
session attribute is set to True, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
          </section>
          <section anchor="active-state">
            <name>Active State:</name>
            <t>In this state, BGP FSM is trying to acquire a peer by listening
for, and accepting, a TCP connection.</t>
            <t>The start events (Events 1, 3-7) are ignored in the Active state.</t>
            <t>In response to a ManualStop event (Event 2), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>If the DelayOpenTimer is running and the
SendNOTIFICATIONwithoutOPEN session attribute is set, the
local system sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>releases all BGP resources including stopping the
DelayOpenTimer</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>sets ConnectRetryCounter to zero,</t>
              </li>
              <li>
                <t>stops the ConnectRetryTimer and sets the ConnectRetryTimer to
zero, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to a ConnectRetryTimer_Expires event (Event 9), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>restarts the ConnectRetryTimer (with initial value),</t>
              </li>
              <li>
                <t>initiates a TCP connection to the other BGP peer,</t>
              </li>
              <li>
                <t>continues to listen for a TCP connection that may be initiated
by a remote BGP peer, and</t>
              </li>
              <li>
                <t>changes its state to Connect.</t>
              </li>
            </ul>
            <t>If the local system receives a DelayOpenTimer_Expires event (Event
12), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>stops and clears the DelayOpenTimer (set to zero),</t>
              </li>
              <li>
                <t>completes the BGP initialization,</t>
              </li>
              <li>
                <t>sends the OPEN message to its remote peer,</t>
              </li>
              <li>
                <t>sets its hold timer to a large value, and</t>
              </li>
              <li>
                <t>changes its state to OpenSent.</t>
              </li>
            </ul>
            <t>A HoldTimer value of 4 minutes is also suggested for this state
transition.</t>
            <t>If the local system receives a TcpConnection_Valid event (Event
14), the local system processes the TCP connection flags and stays
in the Active state.</t>
            <t>If the local system receives a Tcp_CR_Invalid event (Event 15),
the local system rejects the TCP connection and stays in the
Active State.</t>
            <t>In response to the success of a TCP connection (Event 16 or Event
17), the local system checks the DelayOpen optional session attribute
prior to processing.</t>
            <t>If the DelayOpen session attribute is set to TRUE, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer and sets the ConnectRetryTimer
 to zero,</t>
              </li>
              <li>
                <t>sets the DelayOpenTimer to the initial value
 (DelayOpenTime), and</t>
              </li>
              <li>
                <t>stays in the Active state.</t>
              </li>
            </ul>
            <t>If the DelayOpen session attribute is set to FALSE, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>completes the BGP initialization,</t>
              </li>
              <li>
                <t>sends the OPEN message to its peer,</t>
              </li>
              <li>
                <t>sets its HoldTimer to a large value, and</t>
              </li>
              <li>
                <t>changes its state to OpenSent.</t>
              </li>
            </ul>
            <t>A HoldTimer value of 4 minutes is suggested as a "large value" for
the HoldTimer.</t>
            <t>If the local system receives a TcpConnectionFails event (Event 18), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>restarts the ConnectRetryTimer (with the initial value),</t>
              </li>
              <li>
                <t>stops and clears the DelayOpenTimer (sets the value to zero),</t>
              </li>
              <li>
                <t>releases all BGP resource,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>optionally performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If an OPEN message is received and the DelayOpenTimer is running (Event 20), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>stops and clears the DelayOpenTimer (sets to zero),</t>
              </li>
              <li>
                <t>completes the BGP initialization,</t>
              </li>
              <li>
                <t>sends an OPEN message,</t>
              </li>
              <li>
                <t>sends a KEEPALIVE message,</t>
              </li>
              <li>
                <t>if the HoldTimer value is non-zero,  </t>
                <ul spacing="normal">
                  <li>
                    <t>starts the KeepaliveTimer to initial value,</t>
                  </li>
                  <li>
                    <t>resets the HoldTimer to the negotiated value,</t>
                  </li>
                </ul>
                <t>
else if the HoldTimer is zero  </t>
                <ul spacing="normal">
                  <li>
                    <t>resets the KeepaliveTimer (set to zero),</t>
                  </li>
                  <li>
                    <t>resets the HoldTimer to zero, and</t>
                  </li>
                </ul>
              </li>
              <li>
                <t>changes its state to OpenConfirm.</t>
              </li>
            </ul>
            <t>If the value of the autonomous system field is the same as the
local Autonomous System number, set the connection status to an
internal connection; otherwise it will be external.</t>
            <t>If BGP message header checking (Event 21) or OPEN message checking
detects an error (Event 22) (see <xref target="openmsgerr"/>), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>(optionally) sends a NOTIFICATION message with the appropriate
error code if the SendNOTIFICATIONwithoutOPEN session attribute is set
to TRUE,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If a NOTIFICATION message is received with a version error (Event
24), the local system checks the DelayOpenTimer.  If the
DelayOpenTimer is running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>stops the ConnectRetryTimer (if running) and sets the
ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>stops and resets the DelayOpenTimer (sets to zero),</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the DelayOpenTimer is not running, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to any other event (Events 8, 10-11, 13, 19, 23,
25-28), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by one,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
          </section>
          <section anchor="opensent">
            <name>OpenSent:</name>
            <t>In this state, BGP FSM waits for an OPEN message from its peer.</t>
            <t>The start events (Events 1, 3-7) are ignored in the OpenSent
state.</t>
            <t>If a ManualStop event (Event 2) is issued in the OpenSent state,
the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>sets the ConnectRetryCounter to zero, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If an AutomaticStop event (Event 8) is issued in the OpenSent
state, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all the BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the HoldTimer_Expires (Event 10), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION message with the error code Hold Timer
Expired,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If a TcpConnection_Valid (Event 14), Tcp_CR_Acked (Event 16), or a
TcpConnectionConfirmed event (Event 17) is received, a second TCP
connection may be in progress.  This second TCP connection is
tracked per Connection Collision processing (<xref target="collision"/>) until an
OPEN message is received.</t>
            <t>A TCP Connection Request for an Invalid port (Tcp_CR_Invalid
(Event 15)) is ignored.</t>
            <t>If a TcpConnectionFails event (Event 18) is received, the local
system:</t>
            <ul spacing="normal">
              <li>
                <t>closes the BGP connection,</t>
              </li>
              <li>
                <t>restarts the ConnectRetryTimer,</t>
              </li>
              <li>
                <t>continues to listen for a connection that may be initiated by
the remote BGP peer, and</t>
              </li>
              <li>
                <t>changes its state to Active.</t>
              </li>
            </ul>
            <t>When an OPEN message is received, all fields are checked for
correctness.  If there are no errors in the OPEN message (Event
19), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>resets the DelayOpenTimer to zero,</t>
              </li>
              <li>
                <t>sets the BGP ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>sends a KEEPALIVE message, and</t>
              </li>
              <li>
                <t>sets a KeepaliveTimer (via the text below)</t>
              </li>
              <li>
                <t>sets the HoldTimer according to the negotiated value (see
<xref target="openfmt"/>),</t>
              </li>
              <li>
                <t>changes its state to OpenConfirm.</t>
              </li>
            </ul>
            <t>If the negotiated hold time value is zero, then the HoldTimer and
KeepaliveTimer are not started.  If the value of the Autonomous
System field is the same as the local Autonomous System number,
then the connection is an "internal" connection; otherwise, it is
an "external" connection.  (This will impact UPDATE processing as
described below.)</t>
            <t>If the BGP message header checking (Event 21) or OPEN message
checking detects an error (Event 22)(see <xref target="openmsgerr"/>), the local
system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION message with the appropriate error code,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>Collision detection mechanisms (<xref target="collision"/>) need to be applied
when a valid BGP OPEN message is received (Event 19 or Event 20).
Please refer to <xref target="collision"/> for the details of the comparison.  A
CollisionDetectDump event occurs when the BGP implementation
determines, by means outside the scope of this document, that a
connection collision has occurred.</t>
            <t>If a connection in the OpenSent state is determined to be the
connection that must be closed, an OpenCollisionDump (Event 23) is
signaled to the state machine.  If such an event is received in
the OpenSent state, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If a NOTIFICATION message is received with a version error (Event
24), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to any other event (Events 9, 11-13, 20, 25-28), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION with the Error Code Finite State
Machine Error,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
          </section>
          <section anchor="openconfirm-state">
            <name>OpenConfirm State:</name>
            <t>In this state, BGP waits for a KEEPALIVE or NOTIFICATION message.</t>
            <t>Any start event (Events 1, 3-7) is ignored in the OpenConfirm
state.</t>
            <t>In response to a ManualStop event (Event 2) initiated by the
operator, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION message with a Cease,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>sets the ConnectRetryCounter to zero,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to the AutomaticStop event initiated by the system
(Event 8), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION message with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the HoldTimer_Expires event (Event 10) occurs before a
KEEPALIVE message is received, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION message with the Error Code Hold Timer
Expired,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a KeepaliveTimer_Expires event (Event
11), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a KEEPALIVE message,</t>
              </li>
              <li>
                <t>restarts the KeepaliveTimer, and</t>
              </li>
              <li>
                <t>remains in the OpenConfirm state.</t>
              </li>
            </ul>
            <t>In the event of a TcpConnection_Valid event (Event 14), or the
success of a TCP connection (Event 16 or Event 17) while in
OpenConfirm, the local system needs to track the second
connection.</t>
            <t>If a TCP connection is attempted with an invalid port (Event 15),
the local system will ignore the second connection attempt.</t>
            <t>If the local system receives a TcpConnectionFails event (Event 18)
from the underlying TCP or a NOTIFICATION message (Event 25), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a NOTIFICATION message with a version
error (NotifMsgVerErr (Event 24)), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a valid OPEN message (BGPOpen (Event
19)), the collision detect function is processed per <xref target="collision"/>.
If this connection is to be dropped due to connection collision,
the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection (send TCP FIN),</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If an OPEN message is received, all fields are checked for
correctness.  If the BGP message header checking (BGPHeaderErr
(Event 21)) or OPEN message checking detects an error (see <xref target="openmsgerr"/>)
(BGPOpenMsgErr (Event 22)), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION message with the appropriate error code,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If, during the processing of another OPEN message, the BGP
implementation determines, by a means outside the scope of this
document, that a connection collision has occurred and this
connection is to be closed, the local system will issue an
OpenCollisionDump event (Event 23).  When the local system
receives an OpenCollisionDump event (Event 23), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a KEEPALIVE message (KeepAliveMsg
(Event 26)), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>restarts its HoldTimer, if the negotiated HoldTime value is
non-zero, and</t>
              </li>
              <li>
                <t>starts the SendHoldTimer if the SendHoldTime and the
negotiated HoldTime are both non-zero, and</t>
              </li>
              <li>
                <t>changes its state to Established.</t>
              </li>
            </ul>
            <t>In response to any other event (Events 9, 12-13, 20, 27-28), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a code of Finite State Machine
Error,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
          </section>
          <section anchor="established-state">
            <name>Established State:</name>
            <t>In the Established state, the BGP FSM can exchange UPDATE,
NOTIFICATION, and KEEPALIVE messages with its peer.</t>
            <t>Any Start event (Events 1, 3-7) is ignored in the Established
state.</t>
            <t>In response to a ManualStop event (initiated by an operator)
(Event 2), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends the NOTIFICATION message with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>releases BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>sets the ConnectRetryCounter to zero, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to an AutomaticStop event (Event 8), the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>One reason for an AutomaticStop event is: A BGP receives an UPDATE
messages with a number of prefixes for a given peer such that the
total prefixes received exceeds the maximum number of prefixes
configured.  The local system automatically disconnects the peer.</t>
            <t>If the HoldTimer_Expires event occurs (Event 10), the local
system:</t>
            <ul spacing="normal">
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>sends a NOTIFICATION message with the Error Code Hold Timer
Expired,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the KeepaliveTimer_Expires event occurs (Event 11), the local
system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a KEEPALIVE message, and</t>
              </li>
              <li>
                <t>restarts its KeepaliveTimer, unless the negotiated HoldTime
value is zero.</t>
              </li>
            </ul>
            <t>Each time the local system sends a KEEPALIVE or UPDATE message, it
restarts its KeepaliveTimer, unless the negotiated HoldTime value
is zero.</t>
            <t>If the SendHoldTimer_Expires (Event 29) occurs, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>(optionally) sends a NOTIFICATION message with the BGP Error
Code "Send Hold Timer Expired" if the local system can
determine that doing so will not delay the following actions
in this paragraph,</t>
              </li>
              <li>
                <t>logs an error message in the local system with the BGP Error
Code "Send Hold Timer Expired",</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>Each time the local system sends a BGP message, it restarts the
SendHoldTimer unless the SendHoldTime value is zero or the
negotiated HoldTime value is zero, in which case the
SendHoldTimer is stopped.</t>
            <t>The SendHoldTimer is stopped following any transition out of
the Established state as part of the "release all BGP
resources" action.</t>
            <t>A TcpConnection_Valid (Event 14), received for a valid port, will
cause the second connection to be tracked.</t>
            <t>An invalid TCP connection (Tcp_CR_Invalid event (Event 15)) will
be ignored.</t>
            <t>In response to an indication that the TCP connection is
successfully established (Event 16 or Event 17), the second
connection <bcp14>SHALL</bcp14> be tracked until it sends an OPEN message.</t>
            <t>If a valid OPEN message (BGPOpen (Event 19)) is received, and if
the CollisionDetectEstablishedState optional session attribute is TRUE,
the OPEN message will be checked to see if it collides (<xref target="collision"/>)
with any other connection.  If the BGP implementation
determines that this connection needs to be terminated, it will
process an OpenCollisionDump event (Event 23).  If this connection
needs to be terminated, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION with a Cease,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a NOTIFICATION message (Event 24 or
Event 25) or a TcpConnectionFails (Event 18) from the underlying
TCP, the local system:</t>
            <ul spacing="normal">
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>releases all the BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>If the local system receives a KEEPALIVE message (Event 26), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>restarts its HoldTimer, if the negotiated HoldTime value is
non-zero, and</t>
              </li>
              <li>
                <t>remains in the Established state.</t>
              </li>
            </ul>
            <t>If the local system receives an UPDATE message (Event 27), the
local system:</t>
            <ul spacing="normal">
              <li>
                <t>processes the message,</t>
              </li>
              <li>
                <t>restarts its HoldTimer, if the negotiated HoldTime value is
non-zero, and</t>
              </li>
              <li>
                <t>remains in the Established state.</t>
              </li>
            </ul>
            <t>If the local system receives an UPDATE message, and the UPDATE
message error handling procedure (see <xref target="updatemsgerr"/>) detects an
error (Event 28), the local system: 
<!-- xxx this is wrong now that we've integrated rfc 7606 -->
            </t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION message with an Update error,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
            <t>In response to any other event (Events 9, 12-13, 20-22), the local
system:</t>
            <ul spacing="normal">
              <li>
                <t>sends a NOTIFICATION message with the Error Code Finite State
Machine Error,</t>
              </li>
              <li>
                <t>deletes all routes associated with this connection,</t>
              </li>
              <li>
                <t>sets the ConnectRetryTimer to zero,</t>
              </li>
              <li>
                <t>releases all BGP resources,</t>
              </li>
              <li>
                <t>drops the TCP connection,</t>
              </li>
              <li>
                <t>increments the ConnectRetryCounter by 1,</t>
              </li>
              <li>
                <t>(optionally) performs peer oscillation damping if the
DampPeerOscillations session attribute is set to TRUE, and</t>
              </li>
              <li>
                <t>changes its state to Idle.</t>
              </li>
            </ul>
          </section>
        </section>
      </section>
    </section>
    <section anchor="updatemsg">
      <name>UPDATE Message Handling</name>
      <t>An UPDATE message may be received only in the Established state.
Receiving an UPDATE message in any other state is an error.  When an
UPDATE message is received, each field is checked for validity, as
specified in <xref target="updatemsgerr"/>.</t>
      <t>If an optional non-transitive attribute is unrecognized, it is
quietly discarded.  If an optional transitive attribute is
unrecognized, the Partial bit (the third high-order bit) in the
attribute flags octet is set to 1, and the attribute is retained for
propagation to other BGP speakers.</t>
      <t>If an optional attribute is recognized and has a valid value, then,
depending on the type of the optional attribute, it is processed
locally, retained, and updated, if necessary, for possible
propagation to other BGP speakers.</t>
      <t>If the UPDATE message contains a non-empty Withdrawn Routes field,
the previously advertised routes, whose destinations (expressed as IP
prefixes) are contained in this field, <bcp14>SHALL</bcp14> be removed from the
Adj-RIB-In.  This BGP speaker <bcp14>SHALL</bcp14> run its Decision Process because
the previously advertised route is no longer available for use.</t>
      <t>If the UPDATE message contains a feasible route, the Adj-RIB-In will
be updated with this route as follows: if the NLRI of the new route
is identical to the NLRI of a route associated with the same BGP 
session that is currently stored in the Adj-RIB-In, then the new 
route <bcp14>SHALL</bcp14> replace the older route in the Adj-RIB-In, thus implicitly 
withdrawing the older route from service. Otherwise, if the Adj-RIB-In 
has no such older route, the new route <bcp14>SHALL</bcp14> be placed in the 
Adj-RIB-In.</t>
      <t>Once the BGP speaker updates the Adj-RIB-In, the speaker <bcp14>SHALL</bcp14> run
its Decision Process.</t>
      <section anchor="decision">
        <name>Decision Process</name>
        <t>The Decision Process selects routes for subsequent advertisement by
applying the policies in the local Policy Information Base (PIB) to
the routes stored in its Adj-RIBs-In.  The output of the Decision
Process is the set of routes that will be advertised to peers; the
selected routes will be stored in the local speaker's Adj-RIBs-Out,
according to policy.</t>
        <t>The BGP Decision Process described here is conceptual, and does not
have to be implemented precisely as described, as long as the
implementations support the described functionality and they exhibit
the same externally visible behavior.</t>
        <t>The selection process is formalized by defining a function that takes
the attributes of a given route as an argument and returns either (a)
a non-negative integer denoting the degree of preference for the
route, or (b) a value denoting that this route is ineligible to be
installed in Loc-RIB and will be excluded from the next phase of
route selection.</t>
        <t>The function that calculates the degree of preference for a given
route <bcp14>SHALL NOT</bcp14> use any of the following as its inputs: the existence
of other routes, the non-existence of other routes, or the path
attributes of other routes.  Route selection then consists of the
individual application of the degree of preference function to each
feasible route, followed by the choice of the one with the highest
degree of preference.</t>
        <t>The Decision Process operates on routes contained in the Adj-RIBs-In,
and is responsible for:</t>
        <ul spacing="normal">
          <li>
            <t>selection of routes to be used locally by the speaker</t>
          </li>
          <li>
            <t>selection of routes to be advertised to other BGP peers</t>
          </li>
          <li>
            <t>route aggregation and route information reduction</t>
          </li>
        </ul>
        <t>Routes contained in an Adj-RIB-In associated with an EBGP peer
<bcp14>SHALL NOT</bcp14> be considered eligible in the Decision Process if no
explicit Import Policy has been applied.</t>
        <t>The Decision Process takes place in three distinct phases, each
triggered by a different event:</t>
        <ol spacing="normal" type="%c)"><li>
            <t>Phase 1 is responsible for calculating the degree of preference
 for each route received from a peer.</t>
          </li>
          <li>
            <t>Phase 2 is invoked on completion of phase 1.  It is responsible
 for choosing the best route out of all those available for each
 distinct destination, and for installing each chosen route into
 the Loc-RIB.</t>
          </li>
          <li>
            <t>Phase 3 is invoked after the Loc-RIB has been modified.  It is
 responsible for disseminating routes in the Loc-RIB to each
 peer, according to the policies contained in the PIB.  Route
 aggregation and information reduction can optionally be
 performed within this phase.</t>
          </li>
        </ol>
        <section anchor="phase1">
          <name>Phase 1: Calculation of Degree of Preference</name>
          <t>The Phase 1 decision function is invoked whenever the local BGP
speaker receives, from a peer, an UPDATE message that advertises a
new route, a replacement route, or a withdrawn route.</t>
          <t>The Phase 1 decision function is a separate process, which completes
when it has no further work to do.</t>
          <t>The Phase 1 decision function locks an Adj-RIB-In prior to operating
on any route contained within it, and unlocks it after operating on
all new or unfeasible routes contained within it.</t>
          <t>For each newly received or replacement feasible route, the local BGP speaker determines a degree of preference as follows:</t>
          <ul empty="true">
            <li>
              <t>If the route is learned from an internal peer, either the value of
the LOCAL_PREF attribute is taken as the degree of preference, or
the local system computes the degree of preference of the route
based on preconfigured policy information.  Note that the latter
may result in formation of persistent routing loops.</t>
            </li>
          </ul>
          <ul empty="true">
            <li>
              <t>If the route is learned from an external peer, then the local BGP
speaker computes the degree of preference based on preconfigured
policy information.  If the return value indicates the route is
ineligible, the route <bcp14>MUST NOT</bcp14> serve as an input to the next phase
of route selection; otherwise, the return value <bcp14>MUST</bcp14> be used as
the LOCAL_PREF value in any propagation of the route into IBGP.</t>
            </li>
          </ul>
          <ul empty="true">
            <li>
              <t>The exact nature of this policy information, and the computation
involved, is a local matter.</t>
            </li>
          </ul>
        </section>
        <section anchor="phase2">
          <name>Phase 2: Route Selection</name>
          <t>The Phase 2 decision function is invoked on completion of Phase 1.
The Phase 2 function is a separate process, which completes when it
has no further work to do.  The Phase 2 process considers all routes
that are eligible in the Adj-RIBs-In.</t>
          <t>The Phase 2 decision function is blocked from running while the Phase
3 decision function is in process.  The Phase 2 function locks all
Adj-RIBs-In prior to commencing its function, and unlocks them on
completion.</t>
          <t>If the NEXT_HOP attribute of a BGP route depicts an address that is
not resolvable, or if it would become unresolvable if the route was
installed in the routing table, the BGP route <bcp14>MUST</bcp14> be excluded from
the Phase 2 decision function.</t>
          <t>If the AS_PATH attribute of a BGP route contains an AS loop, the BGP
route should be excluded from the Phase 2 decision function.  AS loop
detection is done by scanning the full AS path (as specified in the
AS_PATH attribute), and checking that the autonomous system number of
the local system does not appear in the AS path.  Operations of a BGP
speaker that is configured to accept routes with its own autonomous
system number in the AS path are outside the scope of this document.
<xref target="RFC7705"/>, if used, documents variations on this procedure.</t>
          <t>It is critical that BGP speakers within an AS do not make conflicting
decisions regarding route selection that would cause forwarding loops
to occur.</t>
          <t>For each set of destinations for which a feasible route exists in the
Adj-RIBs-In, the local BGP speaker identifies the route that has:</t>
          <ol spacing="normal" type="%c)"><li>
              <t>the highest degree of preference of any route to the same set
 of destinations, or</t>
            </li>
            <li>
              <t>is the only route to that destination, or</t>
            </li>
            <li>
              <t>is selected as a result of the Phase 2 tie breaking rules
 specified in <xref target="phase2tiebreak"/>.</t>
            </li>
          </ol>
          <t>The local speaker <bcp14>SHALL</bcp14> then install that route in the Loc-RIB,
replacing any route to the same destination that is currently being
held in the Loc-RIB.  When the new BGP route is installed in the
Routing Table, care must be taken to ensure that existing routes to
the same destination that are now considered invalid are removed from
the Routing Table.  Whether the new BGP route replaces an existing
non-BGP route in the Routing Table depends on the policy configured
on the BGP speaker.</t>
          <t>The local speaker <bcp14>MUST</bcp14> determine the immediate next-hop address from
the NEXT_HOP attribute of the selected route (see <xref target="nexthop"/>).  If
either the immediate next-hop or the IGP cost to the NEXT_HOP (where
the NEXT_HOP is resolved through an IGP route) changes, Phase 2 Route
Selection <bcp14>MUST</bcp14> be performed again.</t>
          <t>Notice that even though BGP routes do not have to be installed in the
Routing Table with the immediate next-hop(s), implementations <bcp14>MUST</bcp14>
take care that, before any packets are forwarded along a BGP route,
its associated NEXT_HOP address is resolved to the immediate
(directly connected) next-hop address, and that this address (or
multiple addresses) is finally used for actual packet forwarding.</t>
          <t>Unresolvable routes <bcp14>SHALL</bcp14> be removed from the Loc-RIB and the routing
table.  However, corresponding unresolvable routes <bcp14>SHOULD</bcp14> be kept in
the Adj-RIBs-In (in case they become resolvable).</t>
          <section anchor="route-resolvability-condition">
            <name>Route Resolvability Condition</name>
            <t>As indicated in <xref target="phase2"/>, BGP speakers exclude
unresolvable routes from the Phase 2 decision.  This ensures that
only valid routes are installed in the Loc-RIB and Routing Table.
<!-- XXX The SHOULD above (a) seems wrong, (b) is unnecessary but worst of all (c) conflicts with a MUST in paragraph 4 of the previous section. -->
            </t>
            <t>The route resolvability condition is defined as follows:</t>
            <ol spacing="normal" type="1"><li>
                <t>A route Rte1, referencing only the intermediate network
address, is considered resolvable if the Routing Table contains
at least one resolvable route Rte2 that matches Rte1's
intermediate network address and is not recursively resolved
(directly or indirectly) through Rte1.  If multiple matching
routes are available, only the longest matching route is
considered.</t>
              </li>
              <li>
                <t>Routes referencing interfaces (with or without intermediate
addresses) are considered resolvable if the state of the
referenced interface is up and if IP processing is enabled on
this interface.</t>
              </li>
            </ol>
            <t>BGP routes do not refer to interfaces, but can be resolved through
the routes in the Routing Table that can be of both types (those that
specify interfaces or those that do not).  IGP routes and routes to
directly connected networks are expected to specify the outbound
interface.  Static routes can specify the outbound interface, the
intermediate address, or both.</t>
            <t>Note that a BGP route is considered unresolvable in a situation where
the BGP speaker's Routing Table contains no route matching the BGP
route's NEXT_HOP.  Mutually recursive routes (routes resolving each
other or themselves) also fail the resolvability check.</t>
            <t>It is also important that implementations do not consider feasible
routes that would become unresolvable if they were installed in the
Routing Table, even if their NEXT_HOPs are resolvable using the
current contents of the Routing Table (an example of such routes
would be mutually recursive routes).  This check ensures that a BGP
speaker does not install routes in the Routing Table that will be
removed and not used by the speaker.  Therefore, in addition to local
Routing Table stability, this check also improves behavior of the
protocol in the network.</t>
            <t>Whenever a BGP speaker identifies a route that fails the
resolvability check because of mutual recursion, an error message
<bcp14>SHOULD</bcp14> be logged.</t>
          </section>
          <section anchor="phase2tiebreak">
            <name>Breaking Ties (Phase 2)</name>
            <t>In its Adj-RIBs-In, a BGP speaker may have several routes to the same
destination that have the same degree of preference.  The local
speaker can select only one of these routes for inclusion in the
associated Loc-RIB.  The local speaker considers all routes with the
same degrees of preference, both those received from internal peers,
and those received from external peers.</t>
            <t>The following tie-breaking procedure assumes that, for each candidate
route, all the BGP speakers within an autonomous system can ascertain
the cost of a path (interior distance) to the address depicted by the
NEXT_HOP attribute of the route, and follow the same route selection
algorithm.</t>
            <t>The tie-breaking algorithm begins by considering all equally
preferable routes to the same destination, and then selects routes to
be removed from consideration.  The algorithm terminates as soon as
only one route remains in consideration.  The criteria <bcp14>MUST</bcp14> be
applied in the order specified.</t>
            <t>Several of the criteria are described using pseudo-code.  Note that
the pseudo-code shown was chosen for clarity, not efficiency.  It is
not intended to specify any particular implementation.  BGP
implementations <bcp14>MAY</bcp14> use any algorithm that produces the same results
as those described here.</t>
            <ol group="tiebreak" spacing="normal" type="%c)"><li>
                <t>Remove from consideration all routes that are not tied for
 having the smallest number of AS numbers present in their
 AS_PATH attributes.  Note that when counting this number, an
 AS_SET counts as 1, no matter how many ASes are in the set.
 This number is sometimes called the "AS path length".</t>
              </li>
              <li>
                <t>Remove from consideration all routes that are not tied for
 having the lowest Origin number in their Origin attribute.</t>
              </li>
              <li>
                <t>Remove from consideration routes with less-preferred
 MULTI_EXIT_DISC attributes.  MULTI_EXIT_DISC is only comparable
 between routes learned from the same neighboring AS (the
 neighboring AS is determined from the AS_PATH attribute).
 Routes that do not have the MULTI_EXIT_DISC attribute are
 considered to have the lowest possible MULTI_EXIT_DISC value.</t>
              </li>
            </ol>
            <ul empty="true">
              <li>
                <t>This is also described in the following procedure:
<!-- XXX I wasn't sure how to get the indent right for the above. It's part of the previous paragraph, shouldn't get a new bullet, should get the same indent. Same for the later paragraphs that I've crudely indented. -->
                </t>
              </li>
            </ul>
            <artwork><![CDATA[
    for m = all routes still under consideration
        for n = all routes still under consideration
            if (neighborAS(m) == neighborAS(n)) and (MED(n) < MED(m))
                remove route m from consideration
]]></artwork>
            <ul empty="true">
              <li>
                <t>In the pseudo-code above, MED(n) is a function that returns the
value of route n's MULTI_EXIT_DISC attribute.  If route n has
no MULTI_EXIT_DISC attribute, the function returns the lowest
possible MULTI_EXIT_DISC value (i.e., 0).</t>
              </li>
            </ul>
            <ul empty="true">
              <li>
                <t>Similarly, neighborAS(n) is a function that returns the
neighbor AS from which the route was received.  If the route is
learned via IBGP, and the other IBGP speaker didn't originate
the route, it is the neighbor AS from which the other IBGP
speaker learned the route.  If the AS_PATH attribute
is either empty or begins with an AS_SET, it is the local AS.</t>
              </li>
            </ul>
            <ul empty="true">
              <li>
                <t>If a MULTI_EXIT_DISC attribute is removed before re-advertising
a route into IBGP, then comparison based on the received EBGP
MULTI_EXIT_DISC attribute <bcp14>MAY</bcp14> still be performed.  If an
implementation chooses to remove MULTI_EXIT_DISC, then the
optional comparison on MULTI_EXIT_DISC, if performed, <bcp14>MUST</bcp14> be
performed only among EBGP-learned routes.  The best EBGP-
learned route may then be compared with IBGP-learned routes
after the removal of the MULTI_EXIT_DISC attribute.  If
MULTI_EXIT_DISC is removed from a subset of EBGP-learned
routes, and the selected "best" EBGP-learned route will not
have MULTI_EXIT_DISC removed, then the MULTI_EXIT_DISC must be
used in the comparison with IBGP-learned routes.  For IBGP-
learned routes, the MULTI_EXIT_DISC <bcp14>MUST</bcp14> be used in route
comparisons that reach this step in the Decision Process.
Including the MULTI_EXIT_DISC of an EBGP-learned route in the
comparison with an IBGP-learned route, then removing the
MULTI_EXIT_DISC attribute, and advertising the route has been
proven to cause route loops.</t>
              </li>
            </ul>
            <ol group="tiebreak" spacing="normal" type="%c)"><li>
                <t>If at least one of the candidate routes was received via EBGP,
 remove from consideration all routes that were not received via
 EBGP.</t>
              </li>
            </ol>
            <ol group="tiebreak" spacing="normal" type="%c)"><li>
                <t>Remove from consideration any routes with less-preferred
 interior cost.  The interior cost of a route is determined by
 calculating the metric to the NEXT_HOP for the route using the
 Routing Table.  If the NEXT_HOP hop for a route is reachable,
 but no cost can be determined, that route should remain in
 consideration, i.e. it is not considered to be less-preferred.
 (Some implementations may choose to render this issue 
 moot by ensuring a cost can always be determined, by applying
 a default value for routes that otherwise would have no cost. The 
 details of such a strategy are beyond the scope of this document.)</t>
              </li>
            </ol>
            <ul empty="true">
              <li>
                <t>This is also described in the following procedure.</t>
              </li>
            </ul>
            <artwork><![CDATA[
      for m = all routes still under consideration
          for n = all routes in still under consideration
              if (cost(n) can be determined and cost(m) can be determined)
                  if (cost(n) is lower than cost(m))
                      remove m from consideration
]]></artwork>
            <ul empty="true">
              <li>
                <t>In the pseudo-code above, cost(n) is a function that returns
   the cost of the path (interior distance) to the address given
   in the NEXT_HOP attribute of the route.</t>
              </li>
            </ul>
            <ol group="tiebreak" spacing="normal" type="%c)"><li>
                <t>Remove from consideration all routes other than the route that
 was advertised by the BGP speaker with the lowest BGP
 Identifier value. (<xref target="RFC5004"/>, if used, modifies this rule.)</t>
              </li>
              <li>
                <t>Prefer the route received from the lowest peer address.</t>
              </li>
            </ol>
          </section>
        </section>
        <section anchor="phase-3-route-dissemination">
          <name>Phase 3: Route Dissemination</name>
          <t>The Phase 3 decision function is invoked on completion of Phase 2, or
when any of the following events occur:</t>
          <ol spacing="normal" type="%c)"><li>
              <t>when routes in the Loc-RIB to local destinations have changed</t>
            </li>
            <li>
              <t>when locally generated routes learned by means outside of BGP
 have changed</t>
            </li>
            <li>
              <t>when a new BGP speaker connection has been established</t>
            </li>
          </ol>
          <t>The Phase 3 function is a separate process that completes when it has
no further work to do.  The Phase 3 Routing Decision function is
blocked from running while the Phase 2 decision function is in
process.</t>
          <t>All routes in the Loc-RIB are processed into Adj-RIBs-Out according
to configured policy.  This policy <bcp14>MAY</bcp14> exclude a route in the Loc-RIB
from being installed in a particular Adj-RIB-Out.  A route <bcp14>SHALL NOT</bcp14>
be installed in the Adj-Rib-Out unless the destination, and NEXT_HOP
described by this route, may be forwarded appropriately by the
Routing Table.  If a route to a particular destination is excluded from 
a particular Adj-RIB-Out, and if a route to that destination had 
previously been advertised from that Adj-RIB-Out, the previously 
advertised route in that Adj-RIB-Out <bcp14>MUST</bcp14> be withdrawn from service by 
means of an UPDATE message (see <xref target="updatesend"/>).</t>
          <t>Routes <bcp14>SHALL NOT</bcp14> be added to an Adj-RIB-Out associated with an EBGP peer
if no explicit Export Policy has been applied.</t>
          <t>Route aggregation and information reduction techniques (see <xref target="informreduce"/>) 
may optionally be applied.</t>
          <t>Any local policy that results in routes being added to an Adj-RIB-Out
without also being added to the local BGP speaker's forwarding table
is outside the scope of this document.</t>
          <t>When the updating of the Adj-RIBs-Out and the Routing Table is
complete, the local BGP speaker runs the Update-Send process of <xref target="updatesend"/>.</t>
        </section>
        <section anchor="overlap">
          <name>Overlapping Routes</name>
          <t>A BGP speaker may transmit routes with overlapping Network Layer
Reachability Information (NLRI) to another BGP speaker.  NLRI overlap
occurs when a set of destinations are identified in non-matching
multiple routes.  Because BGP encodes NLRI using IP prefixes, overlap
will always exhibit subset relationships.  A route describing a
smaller set of destinations (a longer prefix) is said to be more
specific than a route describing a larger set of destinations (a
shorter prefix); similarly, a route describing a larger set of
destinations is said to be less specific than a route describing a
smaller set of destinations.</t>
          <t>The precedence relationship effectively decomposes less specific
routes into two parts:</t>
          <ul spacing="normal">
            <li>
              <t>a set of destinations described only by the less specific route,
and</t>
            </li>
            <li>
              <t>a set of destinations described by the overlap of the less
specific and the more specific routes</t>
            </li>
          </ul>
          <t>The set of destinations described by the overlap represents a portion
of the less specific route that is feasible, but is not currently in
use.  If a more specific route is later withdrawn, the set of
destinations described by the overlap will still be reachable using
the less specific route.</t>
          <t>If a BGP speaker receives overlapping routes, the Decision Process
<bcp14>MUST</bcp14> consider both routes based on the configured acceptance policy.
If both a less and a more specific route are accepted, then the
Decision Process <bcp14>MUST</bcp14> install, in Loc-RIB, either both the less and
the more specific routes or aggregate the two routes and install, in
Loc-RIB, the aggregated route, provided that both routes have the
same value of the NEXT_HOP attribute.</t>
          <t>If a BGP speaker chooses to aggregate, then it <bcp14>SHOULD</bcp14> <!-- MUST? --> add the
ATOMIC_AGGREGATE attribute to the route.  <!-- This attribute is now
primarily informational.  With the elimination of IP routing
protocols that do not support classless routing, and the elimination
of router and host implementations that do not support classless
routing, there is no longer a need to de-aggregate. -->  Routes <bcp14>SHOULD
NOT</bcp14> be de-aggregated.  In particular, a route that carries the
ATOMIC_AGGREGATE attribute <bcp14>MUST NOT</bcp14> be de-aggregated.  That is, the
NLRI of this route cannot be made more specific.  Forwarding along such a
route does not guarantee that IP packets will actually traverse only
ASes listed in the AS_PATH attribute of the route.</t>
        </section>
      </section>
      <section anchor="updatesend">
        <name>Update-Send Process</name>
        <t>The Update-Send process is responsible for advertising UPDATE
messages to all peers.  It distributes the routes chosen
by the Decision Process to other BGP speakers, which may be located
in either the same autonomous system or a neighboring autonomous
system.</t>
        <t>When a BGP speaker receives an UPDATE message from an internal peer,
the receiving BGP speaker <bcp14>SHALL NOT</bcp14> re-distribute the routing
information contained in that UPDATE message to other internal peers
(unless the speaker acts as a BGP Route Reflector <xref target="RFC4456"/>).</t>
        <t>As part of Phase 3 of the route selection process, the BGP speaker
has updated its Adj-RIBs-Out.  All newly installed routes and all
newly unfeasible routes for which there is no replacement route <bcp14>SHALL</bcp14>
be advertised to its peers by means of one or more UPDATE messages.</t>
        <t>A BGP speaker <bcp14>SHOULD NOT</bcp14> advertise a given feasible BGP route from
its Adj-RIB-Out if it would produce an UPDATE message containing the
same BGP route as was previously advertised.</t>
        <t>Any routes in the Loc-RIB marked as unfeasible <bcp14>SHALL</bcp14> be removed.
Changes to the reachable destinations within its own autonomous
system <bcp14>SHALL</bcp14> also be advertised in an UPDATE message.</t>
        <t>If, due to the limits on the maximum size of an UPDATE message (see
<xref target="msgformat"/>), a single route doesn't fit into the message, the BGP
speaker <bcp14>MUST NOT</bcp14> advertise the route to its peers and <bcp14>MAY</bcp14> choose to
log an error locally.  If a route for the affected destination has
previously been advertised, that route <bcp14>MUST</bcp14> be withdrawn.</t>
        <section anchor="controlling-routing-traffic-overhead">
          <name>Controlling Routing Traffic Overhead</name>
          <t>The BGP protocol constrains the amount of routing traffic (that is,
UPDATE messages), in order to limit both the link bandwidth needed to
advertise UPDATE messages and the processing power needed by the
Decision Process to digest the information contained in the UPDATE
messages.</t>
          <section anchor="mrai">
            <name>Frequency of Route Advertisement</name>
            <t>The parameter MinRouteAdvertisementIntervalTimer determines the
minimum amount of time that must elapse between an advertisement
and/or withdrawal of routes to a particular destination by a BGP
speaker to a peer.  This rate limiting procedure applies on a per-
destination basis, although the value of
MinRouteAdvertisementIntervalTimer is set on a per BGP peer basis.</t>
            <t>Two UPDATE messages sent by a BGP speaker to a peer that advertise feasible
routes and/or withdrawal of unfeasible routes to some common set of
destinations <bcp14>MUST</bcp14> be separated by at least
MinRouteAdvertisementIntervalTimer.  An implementation <bcp14>MUST</bcp14> also provide an
upper bound on the interval.</t>
            <t>Since fast convergence is needed within an autonomous system, either
(a) the MinRouteAdvertisementIntervalTimer used for internal peers
<bcp14>SHOULD</bcp14> be shorter than the MinRouteAdvertisementIntervalTimer used
for external peers, or (b) the procedure described in this section
<bcp14>SHOULD NOT</bcp14> apply to routes sent to internal peers.</t>
            <t>This procedure does not limit the rate of route selection, but only
the rate of route advertisement.  If new routes are selected multiple
times while awaiting the expiration of
MinRouteAdvertisementIntervalTimer, the last route selected <bcp14>SHALL</bcp14> be
advertised at the end of MinRouteAdvertisementIntervalTimer, and the 
intermediate selections <bcp14>SHALL NOT</bcp14> be advertised.</t>
          </section>
          <section anchor="freqoforigination">
            <name>Frequency of Route Origination</name>
            <t>The parameter MinASOriginationIntervalTimer determines the minimum
amount of time that must elapse between successive advertisements of
UPDATE messages that report changes within the advertising BGP
speaker's own autonomous systems.</t>
          </section>
        </section>
        <section anchor="efficient-organization-of-routing-information">
          <name>Efficient Organization of Routing Information</name>
          <t>Having selected the routing information it will advertise, a BGP
speaker may avail itself of several methods to organize this
information in an efficient manner.</t>
          <section anchor="informreduce">
            <name>Information Reduction</name>
            <!-- it seems to me we can eliminate this subsection, it's almost
 vacuous. In the 1990s it needed to be explained; in 2026 it 
 goes without saying. -->

<t>Information reduction may imply a reduction in granularity of policy
control - after information is collapsed, the same policies will
apply to all destinations and paths in the equivalence class.</t>
            <t>The Decision Process may optionally reduce the amount of information
that it will place in the Adj-RIBs-Out as follows:</t>
            <ol spacing="normal" type="%c)"><li>
                <t>Network Layer Reachability Information (NLRI):
Destination IP addresses can be represented as IP address
prefixes.  In cases where there is a correspondence between the
address structure and the systems under control of an
autonomous system administrator, it will be possible to reduce
the size of the NLRI carried in the UPDATE messages.</t>
              </li>
            </ol>
          </section>
          <section anchor="aggregating">
            <name>Aggregating Routing Information</name>
            <t>Aggregation is the process of combining the characteristics of
several different routes in such a way that a single route can be
advertised.  Aggregation can occur as part of the Decision Process to
reduce the amount of routing information that will be placed in the
Adj-RIBs-Out.</t>
            <t>Aggregation reduces the amount of information that a BGP speaker must
store and exchange with other BGP speakers.  Routes can be aggregated
by applying the following procedure, separately, to path attributes
of the same type and to the Network Layer Reachability Information.</t>
            <t>Routes that have different MULTI_EXIT_DISC attributes <bcp14>SHALL NOT</bcp14> be
aggregated.</t>
            <t>Path attributes that have different type codes cannot be aggregated
together.  Path attributes of the same type code may be aggregated,
according to the following rules:</t>
            <dl>
              <dt>NEXT_HOP:</dt>
              <dd>
                <t>When aggregating routes that have different NEXT_HOP
attributes, the NEXT_HOP attribute of the aggregated route
<bcp14>SHALL</bcp14> identify an interface on the BGP speaker that performs
the aggregation.</t>
              </dd>
              <dt>ORIGIN attribute:</dt>
              <dd>
                <t>If at least one route among routes that are aggregated has
ORIGIN with the value INCOMPLETE, then the aggregated route
<bcp14>MUST</bcp14> have the ORIGIN attribute with the value INCOMPLETE.
Otherwise, if at least one route among routes that are
aggregated has ORIGIN with the value EGP, then the aggregated
route <bcp14>MUST</bcp14> have the ORIGIN attribute with the value EGP.  In
all other cases, the value of the ORIGIN attribute of the
aggregated route is IGP.</t>
              </dd>
              <dt>AS_PATH attribute:</dt>
              <dd>
                <t>If routes to be aggregated have identical AS_PATH attributes,
then the aggregated route has the same AS_PATH attribute as
each individual route.
</t>
                <t>Otherwise, for the purpose of aggregating AS_PATH attributes, we
model each AS within the AS_PATH attribute as a tuple &lt;type,
value&gt;, where "type" identifies a type of the path segment the AS
belongs to (e.g., AS_SEQUENCE, AS_SET), and "value" identifies the
AS number.  An aggregated AS_PATH attribute can be formed as
follows:</t>
              </dd>
              <dt/>
              <dd>
                <ul spacing="normal">
                  <li>
                    <t>determine the longest leading sequence of tuples of type
AS_SEQUENCE (as defined above) common to all the AS_PATH attributes
of the routes to be aggregated.  Make this sequence the leading
sequence of the aggregated AS_PATH attribute.</t>
                  </li>
                  <li>
                    <t>for each pair of adjacent tuples in the aggregated AS_PATH,
if both tuples have the same type (which they will), merge 
them together, as long as doing so will not cause a segment 
with a length greater than 255 to be generated.</t>
                  </li>
                  <li>
                    <t>Attach the ATOMIC_AGGREGATE path attribute to the aggregated 
route.</t>
                  </li>
                </ul>
                <t>Except in the identical AS_PATH case described in the first
paragraph, the aggregation procedure will not consume all tuples.
This is why the ATOMIC_AGGREGATE attribute is attached.</t>
                <t>Optionally, the resulting AS_PATH <bcp14>MAY</bcp14> be truncated further. 
Details of when and how to do so are beyond the scope of this
specification.</t>
                <t><xref target="RFC9774"/> refers to the style of aggregation 
described above as "brief". It also defines a variant known as 
"consistent brief" which further truncates the AS_PATH under
some circumstances.</t>
              </dd>
              <dt>ATOMIC_AGGREGATE:</dt>
              <dd>
                <t>If at least one of the routes to be aggregated has
ATOMIC_AGGREGATE path attribute, then the aggregated route
<bcp14>SHALL</bcp14> have this attribute as well.</t>
              </dd>
              <dt>AGGREGATOR:</dt>
              <dd>
                <t>Any AGGREGATOR attributes from the routes to be aggregated <bcp14>MUST
NOT</bcp14> be included in the aggregated route.  The BGP speaker
performing the route aggregation <bcp14>MAY</bcp14> attach a new AGGREGATOR
attribute (see <xref target="aggregator"/>).</t>
              </dd>
            </dl>
          </section>
        </section>
      </section>
      <section anchor="route-selection-criteria">
        <name>Route Selection Criteria</name>
        <t>Generally, additional rules for comparing routes among several
alternatives are outside the scope of this document.  There are two
exceptions:</t>
        <ul spacing="normal">
          <li>
            <t>If the local AS appears in the AS path of the new route being
considered, then that new route cannot be viewed as better than
any other route (provided that the speaker is configured to
accept such routes).  If such a route were ever used, a routing
loop could result.</t>
          </li>
          <li>
            <t>In order to achieve a successful distributed operation, only
routes with a likelihood of stability can be chosen.  Thus, an
AS <bcp14>SHOULD</bcp14> avoid using unstable routes, and it <bcp14>SHOULD NOT</bcp14> make
rapid, spontaneous changes to its choice of route.  Quantifying
the terms "unstable" and "rapid" (from the previous sentence)
will require experience, but the principle is clear.  Routes
that are unstable can be "penalized" (e.g., by using the
procedures described in <xref target="RFC2439"/>).</t>
          </li>
        </ul>
      </section>
      <section anchor="originating-bgp-routes">
        <name>Originating BGP routes</name>
        <t>A BGP speaker may originate BGP routes by injecting routing
information acquired by some other means (e.g., via an IGP) into BGP.
A BGP speaker that originates BGP routes assigns the degree of
preference (e.g., according to local configuration) to these routes
by passing them through the Decision Process (see <xref target="decision"/>).
These routes <bcp14>MAY</bcp14> also be distributed to other BGP speakers within the
local AS as part of the update process (see <xref target="updatesend"/>).  The
decision of whether to distribute non-BGP acquired routes within an
AS via BGP depends on the environment within the AS (e.g., type of
IGP) and <bcp14>SHOULD</bcp14> be controlled via configuration.</t>
      </section>
    </section>
    <section anchor="timers">
      <name>BGP Timers</name>
      <t>BGP employs five timers: ConnectRetryTimer (see <xref target="fsm"/>), HoldTimer
(see <xref target="openfmt"/>), KeepaliveTimer (see <xref target="fsm"/>),
MinASOriginationIntervalTimer (see <xref target="freqoforigination"/>), and
MinRouteAdvertisementIntervalTimer (see <xref target="mrai"/>).</t>
      <t>Three optional timers <bcp14>MAY</bcp14> be supported: DelayOpenTimer, IdleHoldTimer
and SendHoldTimer (see <xref target="fsm"/>).  <xref target="fsm"/> describes their use.</t>
      <t>ConnectRetryTime is a mandatory FSM attribute that stores the initial
value for the ConnectRetryTimer.  The suggested default value for the
ConnectRetryTime is 120 seconds.</t>
      <t>HoldTime is a mandatory FSM attribute that stores the initial value
for the HoldTimer.  The suggested default value for the HoldTime is
90 seconds.</t>
      <t>During some portions of the state machine (see <xref target="fsm"/>), the
HoldTimer is set to a large value.  The suggested default for this
large value is 4 minutes.</t>
      <t>SendHoldTime is an FSM attribute that stores the initial value for
the SendHoldTimer.  If SendHoldTime is non-zero, then it <bcp14>MUST</bcp14> be
greater than the value of HoldTime. The default value of SendHoldTime
<bcp14>SHOULD</bcp14> be the greater of:</t>
      <ul spacing="normal">
        <li>
          <t>8 minutes or</t>
        </li>
        <li>
          <t>2 times the negotiated HoldTime</t>
        </li>
      </ul>
      <t>The KeepaliveTime is a mandatory FSM attribute that stores the
initial value for the KeepaliveTimer.  The suggested default value
for the KeepaliveTime is 1/3 of the HoldTime.</t>
      <t>The suggested default value for the MinASOriginationIntervalTimer is
15 seconds.</t>
      <t>The suggested default value for the
MinRouteAdvertisementIntervalTimer on EBGP connections is 30 seconds.</t>
      <t>The suggested default value for the
MinRouteAdvertisementIntervalTimer on IBGP connections is 5 seconds.</t>
      <t>An implementation of BGP <bcp14>MUST</bcp14> allow the HoldTimer to be configurable
on a per-peer basis, and <bcp14>MAY</bcp14> allow the other timers to be
configurable.</t>
      <t>To minimize the likelihood that the distribution of BGP messages by a
given BGP speaker will contain peaks, jitter <bcp14>SHOULD</bcp14> be applied to the
timers associated with MinASOriginationIntervalTimer, KeepaliveTimer,
MinRouteAdvertisementIntervalTimer, and ConnectRetryTimer.  A given
BGP speaker <bcp14>MAY</bcp14> apply the same jitter to each of these quantities,
regardless of the destinations to which the updates are being sent;
that is, jitter need not be configured on a per-peer basis.</t>
      <t>The suggested default amount of jitter <bcp14>SHALL</bcp14> be determined by
multiplying the base value of the appropriate timer by a random
factor, which is uniformly distributed in the range from 0.75 to 1.0.
A new random value <bcp14>SHOULD</bcp14> be picked each time the timer is set.  The
range of the jitter's random value <bcp14>MAY</bcp14> be configurable.</t>
    </section>
    <section anchor="backcompat">
      <name>Backward Compatibility</name>
      <t>This version of the BGP specification integrates many other past
specifications, which were themselves introduced as extensions to the
former base protocol specification, <xref target="RFC4271"/>. The main body of the
specification documents the expected behavior of current implementations.
However, other behaviors are needed to remain compatible with older
implementations. The subsections below provide the necessary details.</t>
      <section anchor="capbackcompat">
        <name>Capabilities Advertisement</name>
        <t>Capabilities advertisement was not a mandatory element of <xref target="RFC4271"/>.
A BGP speaker determines that its peer doesn't support capabilities
advertisement if, in response to an OPEN message that carries the
Capabilities Optional Parameter, the speaker receives a NOTIFICATION
message with the Error Subcode set to Unsupported Optional Parameter.
In this case, the speaker <bcp14>MAY</bcp14> attempt to
re-establish a BGP connection with the peer without sending to the
peer the Capabilities Optional Parameter, if doing so would not 
conflict with the speaker's configuration. (In practice, this will
seldom be the case.)</t>
        <t>Note that the Required Capability Not Received OPEN message error 
subcode was formerly known as the Unsupported Capability subcode.
This document revises its name. Its semantics remain unchanged.</t>
      </section>
      <section anchor="as2byte">
        <name>Two-Octet Autonomous System Numbers</name>
        <t>The previous edition of this specification (<xref target="RFC4271"/>) defined
Autonomous System numbers as 2-octet entities; this is why the "My
Legacy Autonomous System" field of the OPEN message is only 16 bits and
a capability is used to carry the speaker's actual Autonomous System
number, an encoding adopted from <xref target="RFC6793"/>.</t>
        <t>RFC 6793 refers to a BGP speaker that natively supports the 4-octet AS
encoding and procedures adopted by this document as a "NEW speaker", and
one that only supports the 2-octet encoding and procedures as an "OLD
speaker". It refers to an AS number whose value can be represented in 16
bits (in other words, whose value is 65,535 or less) as a "mappable" AS
number. Finally, it refers to all other AS numbers (those whose values
are greater than 65,535) as "non-mappable." These terms are used below.</t>
        <t>An OLD speaker is any speaker that does not advertise the 4-octet AS
Number Capability <xref target="as4byte"/>. A NEW speaker is any speaker that does
advertise it.</t>
        <t>An implementation of this specification <bcp14>MUST</bcp14> choose one of the following
options. Either it must use the procedures specified below
(<xref target="as2byte-procedures"/>) when interoperating with OLD BGP speakers, or
if it does not provide such backward compatibility support, then it
must terminate a peering attempt from an OLD BGP speaker according to
the procedures of <xref target="caperror"/>, including the "4-octet AS number
capability" in the data portion.</t>
        <section anchor="as2byte-procedures">
          <name>Interaction between NEW and OLD BGP Speakers</name>
          <section anchor="as2byteopen">
            <name>Peer AS Number</name>
            <t>The OLD peer's autonomous system number is found in the My Legacy
Autonomous System field of the OPEN received from the OLD peer.</t>
          </section>
          <section anchor="as4path">
            <name>AS4_PATH Attribute</name>
            <t>The AS4_PATH attribute is an optional transitive attribute with type
code 17. Its usage is described below.</t>
          </section>
          <section anchor="as4aggregator-attribute">
            <name>AS4_AGGREGATOR Attribute</name>
            <t>The AS4_AGGREGATOR attribute is an optional transitive attribute with
type code 18. Its usage is described below.</t>
          </section>
          <section anchor="generating-updates">
            <name>Generating Updates</name>
            <t>When communicating with an OLD BGP speaker, a NEW BGP speaker <bcp14>MUST</bcp14> send
the AS path information in the AS_PATH attribute encoded with two-octet
AS numbers.  The NEW BGP speaker <bcp14>MUST</bcp14> also send the AS path information
in the AS4_PATH attribute (encoded with four-octet AS numbers), except
for the case where all of the AS path information is composed of
mappable four-octet AS numbers only.  In this case, the NEW BGP speaker
<bcp14>MUST NOT</bcp14> send the AS4_PATH attribute.</t>
            <t>In the AS_PATH attribute encoded with two-octet AS numbers, non-mappable
four-octet AS numbers are represented by the reserved two-octet AS
number, AS_TRANS.  This will preserve the path length property of the AS
path information and also help in updating the AS path information
received on a NEW BGP speaker from an OLD BGP speaker, as explained in
the next section.</t>
            <t>The NEW BGP speaker constructs the AS4_PATH attribute from the AS path
information.  Whenever the AS path information contains the
AS_CONFED_SEQUENCE or AS_CONFED_SET path segment, the NEW BGP speaker
<bcp14>MUST</bcp14> exclude such path segments from the AS4_PATH attribute being
constructed.</t>
            <t>The AS4_PATH attribute, being optional transitive, will be carried
across a series of OLD BGP speakers without modification and will help
preserve the non-mappable four-octet AS numbers in the AS path
information.</t>
            <t>Similarly, if the NEW BGP speaker has to send the AGGREGATOR attribute,
and if the aggregating Autonomous System's AS number is a non-mappable
four-octet AS number, then the speaker <bcp14>MUST</bcp14> use the AS4_AGGREGATOR
attribute and set the AS number field in the existing AGGREGATOR
attribute to the reserved AS number, AS_TRANS.  Note that if the AS
number is mappable, then the AS4_AGGREGATOR attribute <bcp14>MUST NOT</bcp14> be sent.</t>
          </section>
          <section anchor="processing-received-updates">
            <name>Processing Received Updates</name>
            <t>When a NEW BGP speaker receives an update from an OLD BGP speaker, it
<bcp14>MUST</bcp14> be prepared to receive the AS4_PATH attribute along with the
existing AS_PATH attribute.  If the AS4_PATH attribute is also received,
both of the attributes will be used to construct the exact AS path
information, and therefore the information carried by both of the
attributes will be considered for AS path loop detection.</t>
            <t>Note that a route may have traversed a series of Autonomous Systems with
two-octet AS numbers and OLD BGP speakers only.  In that case, if the
route carries the AS4_PATH attribute, this attribute would have remained
unmodified since the route left the last NEW BGP speaker.  The trailing
AS path information (representing Autonomous Systems with two-octet AS
numbers and OLD BGP speakers only) is contained only in the current
AS_PATH attribute (encoded in the leading part of the AS_PATH
attribute).</t>
            <t>Under certain conditions, it may not be possible to reconstruct all of
the AS path information from the AS_PATH and the AS4_PATH attributes of
a route.  This occurs, for example, when two or more routes that carry
the AS4_PATH attribute are aggregated by an OLD BGP speaker, and the
AS4_PATH attribute of at least one of these routes carries at least one
four-octet AS number (as opposed to a two-octet AS number that is
encoded in 4 octets).  Depending on the implementation, either the
AS4_PATH attribute would be lost during route aggregation, or both the
AS_PATH attribute and the AS4_PATH attribute would contain valid,
partial information that cannot be combined seamlessly, resulting in
incomplete AS path information in these cases.</t>
            <t>A NEW BGP speaker <bcp14>MUST</bcp14> also be prepared to receive the AS4_AGGREGATOR
attribute along with the AGGREGATOR attribute from an OLD BGP speaker. 
When both of the attributes are received, if the AS number in the
AGGREGATOR attribute is not AS_TRANS, then:</t>
            <ul spacing="normal">
              <li>
                <t>the AS4_AGGREGATOR attribute and the AS4_PATH attribute <bcp14>SHALL</bcp14>
be ignored,</t>
              </li>
              <li>
                <t>the AGGREGATOR attribute <bcp14>SHALL</bcp14> be taken as the information
about the aggregating node, and</t>
              </li>
              <li>
                <t>the AS_PATH attribute <bcp14>SHALL</bcp14> be taken as the AS path
information.</t>
              </li>
            </ul>
            <t>Otherwise,</t>
            <ul spacing="normal">
              <li>
                <t>the AGGREGATOR attribute <bcp14>SHALL</bcp14> be ignored,</t>
              </li>
              <li>
                <t>the AS4_AGGREGATOR attribute <bcp14>SHALL</bcp14> be taken as the information
about the aggregating node, and</t>
              </li>
              <li>
                <t>the AS path information would need to be constructed, as in all
other cases.</t>
              </li>
            </ul>
            <t>In order to construct the AS path information, it is necessary to
first calculate the number of AS numbers in the AS_PATH and AS4_PATH
attributes using the method specified in <xref target="phase2tiebreak"/>
and in <xref target="RFC5065"/> for route selection.</t>
            <t>If the number of AS numbers in the AS_PATH attribute is less than the
number of AS numbers in the AS4_PATH attribute, then the AS4_PATH
attribute <bcp14>SHALL</bcp14> be ignored, and the AS_PATH attribute <bcp14>SHALL</bcp14> be taken
as the AS path information.</t>
            <t>If the number of AS numbers in the AS_PATH attribute is larger than
or equal to the number of AS numbers in the AS4_PATH attribute, then
the AS path information <bcp14>SHALL</bcp14> be constructed by taking as many AS
numbers and path segments as necessary from the leading part of the
AS_PATH attribute, and then prepending them to the AS4_PATH attribute
so that the AS path information has a number of AS numbers identical
to that of the AS_PATH attribute.  Note that a valid
AS_CONFED_SEQUENCE or AS_CONFED_SET path segment <bcp14>SHALL</bcp14> be prepended
if it is either the leading path segment or is adjacent to a path
segment that is prepended.</t>
          </section>
        </section>
        <section anchor="error-handling">
          <name>Error handling</name>
          <section anchor="as4path-error-handling">
            <name>AS4_PATH Error Handling</name>
            <t>A malformed AS4_PATH <bcp14>MUST</bcp14> be handled using the "attribute discard"
approach.</t>
            <t>The AS4_PATH attribute <bcp14>MUST NOT</bcp14> be carried in an UPDATE message between
NEW BGP speakers.  A NEW BGP speaker that receives the AS4_PATH
attribute attribute in an UPDATE message from another NEW BGP speaker
<bcp14>MUST</bcp14> discard the path attribute and continue processing the UPDATE
message.  This case <bcp14>SHOULD</bcp14> be logged locally for analysis.</t>
            <t>In addition, the path segment types AS_CONFED_SEQUENCE and AS_CONFED_SET
<xref target="RFC5065"/> <bcp14>MUST NOT</bcp14> be carried in the AS4_PATH attribute of an UPDATE
message.  A NEW BGP speaker that receives these path segment types in
the AS4_PATH attribute of an UPDATE message from an OLD BGP speaker <bcp14>MUST</bcp14>
discard these path segments, adjust the relevant attribute fields
accordingly, and continue processing the UPDATE message.  This case
<bcp14>SHOULD</bcp14> be logged locally for analysis.</t>
            <t>The AS4_PATH attribute in an UPDATE message <bcp14>SHALL</bcp14> be considered
malformed under the following conditions:</t>
            <ul spacing="normal">
              <li>
                <t>the attribute length is not a multiple of two or is too small
(i.e., less than 6) for the attribute to carry at least one AS
number, or</t>
              </li>
              <li>
                <t>the path segment length in the attribute is either zero or is
inconsistent with the attribute length, or</t>
              </li>
              <li>
                <t>the path segment type in the attribute is not one of the types
defined: AS_SEQUENCE, AS_SET, AS_CONFED_SEQUENCE, and
AS_CONFED_SET.</t>
              </li>
            </ul>
          </section>
          <section anchor="as4aggregator-error-handling">
            <name>AS4_AGGREGATOR Error Handling</name>
            <t>A malformed AS4_AGGREGATOR <bcp14>MUST</bcp14> be handled using the "attribute discard"
approach.</t>
            <t>The AS4_AGGREGATOR attribute <bcp14>MUST NOT</bcp14> be carried in an UPDATE message
between NEW BGP speakers.  A NEW BGP speaker that receives the
AS4_AGGREGATOR attribute in an UPDATE message from another NEW BGP
speaker <bcp14>MUST</bcp14> discard the path attribute and continue processing the
UPDATE message.  This case <bcp14>SHOULD</bcp14> be logged locally for analysis.</t>
            <t>The AS4_AGGREGATOR attribute in an UPDATE message <bcp14>SHALL</bcp14> be considered
malformed if the attribute length is not 8.</t>
          </section>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC791">
          <front>
            <title>Internet Protocol</title>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="September" year="1981"/>
          </front>
          <seriesInfo name="STD" value="5"/>
          <seriesInfo name="RFC" value="791"/>
          <seriesInfo name="DOI" value="10.17487/RFC791"/>
        </reference>
        <reference anchor="RFC793">
          <front>
            <title>Transmission Control Protocol</title>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="September" year="1981"/>
          </front>
          <seriesInfo name="RFC" value="793"/>
          <seriesInfo name="DOI" value="10.17487/RFC793"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC2385">
          <front>
            <title>Protection of BGP Sessions via the TCP MD5 Signature Option</title>
            <author fullname="A. Heffernan" initials="A." surname="Heffernan"/>
            <date month="August" year="1998"/>
            <abstract>
              <t>This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2385"/>
          <seriesInfo name="DOI" value="10.17487/RFC2385"/>
        </reference>
        <reference anchor="RFC4760">
          <front>
            <title>Multiprotocol Extensions for BGP-4</title>
            <author fullname="T. Bates" initials="T." surname="Bates"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="January" year="2007"/>
            <abstract>
              <t>This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, L3VPN, etc.). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4760"/>
          <seriesInfo name="DOI" value="10.17487/RFC4760"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC904">
          <front>
            <title>Exterior Gateway Protocol formal specification</title>
            <author fullname="D.L. Mills" initials="D.L." surname="Mills"/>
            <date month="April" year="1984"/>
            <abstract>
              <t>RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="904"/>
          <seriesInfo name="DOI" value="10.17487/RFC904"/>
        </reference>
        <reference anchor="RFC1092">
          <front>
            <title>EGP and policy based routing in the new NSFNET backbone</title>
            <author fullname="J. Rekhter" initials="J." surname="Rekhter"/>
            <date month="February" year="1989"/>
            <abstract>
              <t>This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone. Of special concern is the restriction of routing information to advertize the best route as established by a policy decision.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1092"/>
          <seriesInfo name="DOI" value="10.17487/RFC1092"/>
        </reference>
        <reference anchor="RFC1093">
          <front>
            <title>NSFNET routing architecture</title>
            <author fullname="H.W. Braun" initials="H.W." surname="Braun"/>
            <date month="February" year="1989"/>
            <abstract>
              <t>This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1093"/>
          <seriesInfo name="DOI" value="10.17487/RFC1093"/>
        </reference>
        <reference anchor="RFC1267">
          <front>
            <title>Border Gateway Protocol 3 (BGP-3)</title>
            <author fullname="K. Lougheed" initials="K." surname="Lougheed"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="October" year="1991"/>
            <abstract>
              <t>This memo, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1267"/>
          <seriesInfo name="DOI" value="10.17487/RFC1267"/>
        </reference>
        <reference anchor="RFC1771">
          <front>
            <title>A Border Gateway Protocol 4 (BGP-4)</title>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="T. Li" initials="T." surname="Li"/>
            <date month="March" year="1995"/>
            <abstract>
              <t>This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1771"/>
          <seriesInfo name="DOI" value="10.17487/RFC1771"/>
        </reference>
        <reference anchor="RFC1772">
          <front>
            <title>Application of the Border Gateway Protocol in the Internet</title>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="P. Gross" initials="P." surname="Gross"/>
            <date month="March" year="1995"/>
            <abstract>
              <t>This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1772"/>
          <seriesInfo name="DOI" value="10.17487/RFC1772"/>
        </reference>
        <reference anchor="RFC1518">
          <front>
            <title>An Architecture for IP Address Allocation with CIDR</title>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="T. Li" initials="T." surname="Li"/>
            <date month="September" year="1993"/>
            <abstract>
              <t>This paper provides an architecture and a plan for allocating IP addresses in the Internet. This architecture and the plan are intended to play an important role in steering the Internet towards the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1518"/>
          <seriesInfo name="DOI" value="10.17487/RFC1518"/>
        </reference>
        <reference anchor="RFC1519">
          <front>
            <title>Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy</title>
            <author fullname="V. Fuller" initials="V." surname="Fuller"/>
            <author fullname="T. Li" initials="T." surname="Li"/>
            <author fullname="J. Yu" initials="J." surname="Yu"/>
            <author fullname="K. Varadhan" initials="K." surname="Varadhan"/>
            <date month="September" year="1993"/>
            <abstract>
              <t>This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1519"/>
          <seriesInfo name="DOI" value="10.17487/RFC1519"/>
        </reference>
        <reference anchor="RFC1930">
          <front>
            <title>Guidelines for creation, selection, and registration of an Autonomous System (AS)</title>
            <author fullname="J. Hawkinson" initials="J." surname="Hawkinson"/>
            <author fullname="T. Bates" initials="T." surname="Bates"/>
            <date month="March" year="1996"/>
            <abstract>
              <t>This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="6"/>
          <seriesInfo name="RFC" value="1930"/>
          <seriesInfo name="DOI" value="10.17487/RFC1930"/>
        </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="RFC2439">
          <front>
            <title>BGP Route Flap Damping</title>
            <author fullname="C. Villamizar" initials="C." surname="Villamizar"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <author fullname="R. Govindan" initials="R." surname="Govindan"/>
            <date month="November" year="1998"/>
            <abstract>
              <t>A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2439"/>
          <seriesInfo name="DOI" value="10.17487/RFC2439"/>
        </reference>
        <reference anchor="RFC2474">
          <front>
            <title>Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers</title>
            <author fullname="K. Nichols" initials="K." surname="Nichols"/>
            <author fullname="S. Blake" initials="S." surname="Blake"/>
            <author fullname="F. Baker" initials="F." surname="Baker"/>
            <author fullname="D. Black" initials="D." surname="Black"/>
            <date month="December" year="1998"/>
            <abstract>
              <t>This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2474"/>
          <seriesInfo name="DOI" value="10.17487/RFC2474"/>
        </reference>
        <reference anchor="RFC2858">
          <front>
            <title>Multiprotocol Extensions for BGP-4</title>
            <author fullname="T. Bates" initials="T." surname="Bates"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <date month="June" year="2000"/>
            <abstract>
              <t>This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2858"/>
          <seriesInfo name="DOI" value="10.17487/RFC2858"/>
        </reference>
        <reference anchor="RFC2918">
          <front>
            <title>Route Refresh Capability for BGP-4</title>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <date month="September" year="2000"/>
            <abstract>
              <t>This document defines a new Border Gateway Protocol (BGP) capability termed 'Route Refresh Capability', which would allow the dynamic exchange of route refresh request between BGP speakers and subsequent re-advertisement of the respective Adj-RIB-Out. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2918"/>
          <seriesInfo name="DOI" value="10.17487/RFC2918"/>
        </reference>
        <reference anchor="RFC3562">
          <front>
            <title>Key Management Considerations for the TCP MD5 Signature Option</title>
            <author fullname="M. Leech" initials="M." surname="Leech"/>
            <date month="July" year="2003"/>
            <abstract>
              <t>The TCP MD5 Signature Option (RFC 2385), used predominantly by BGP, has seen significant deployment in critical areas of Internet infrastructure. The security of this option relies heavily on the quality of the keying material used to compute the MD5 signature. This document addresses the security requirements of that keying material. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3562"/>
          <seriesInfo name="DOI" value="10.17487/RFC3562"/>
        </reference>
        <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="RFC4272">
          <front>
            <title>BGP Security Vulnerabilities Analysis</title>
            <author fullname="S. Murphy" initials="S." surname="Murphy"/>
            <date month="January" year="2006"/>
            <abstract>
              <t>Border Gateway Protocol 4 (BGP-4), along with a host of other infrastructure protocols designed before the Internet environment became perilous, was originally designed with little consideration for protection of the information it carries. There are no mechanisms internal to BGP that protect against attacks that modify, delete, forge, or replay data, any of which has the potential to disrupt overall network routing behavior.</t>
              <t>This document discusses some of the security issues with BGP routing data dissemination. This document does not discuss security issues with forwarding of packets. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4272"/>
          <seriesInfo name="DOI" value="10.17487/RFC4272"/>
        </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>
        <reference anchor="RFC4486">
          <front>
            <title>Subcodes for BGP Cease Notification Message</title>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <author fullname="V. Gillet" initials="V." surname="Gillet"/>
            <date month="April" year="2006"/>
            <abstract>
              <t>This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4486"/>
          <seriesInfo name="DOI" value="10.17487/RFC4486"/>
        </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="RFC5004">
          <front>
            <title>Avoid BGP Best Path Transitions from One External to Another</title>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <author fullname="S. Sangli" initials="S." surname="Sangli"/>
            <date month="September" year="2007"/>
            <abstract>
              <t>In this document, we propose an extension to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed extension would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external path from one BGP speaker contributes to the churn. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5004"/>
          <seriesInfo name="DOI" value="10.17487/RFC5004"/>
        </reference>
        <reference anchor="RFC5065">
          <front>
            <title>Autonomous System Confederations for BGP</title>
            <author fullname="P. Traina" initials="P." surname="Traina"/>
            <author fullname="D. McPherson" initials="D." surname="McPherson"/>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <date month="August" year="2007"/>
            <abstract>
              <t>The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP speakers within a single autonomous system (AS) must be fully meshed. This represents a serious scaling problem that has been well documented in a number of proposals.</t>
              <t>This document describes an extension to BGP that may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the "full mesh" requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system.</t>
              <t>This document obsoletes RFC 3065. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5065"/>
          <seriesInfo name="DOI" value="10.17487/RFC5065"/>
        </reference>
        <reference anchor="RFC5492">
          <front>
            <title>Capabilities Advertisement with BGP-4</title>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <date month="February" year="2009"/>
            <abstract>
              <t>This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated.</t>
              <t>This document obsoletes RFC 3392. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5492"/>
          <seriesInfo name="DOI" value="10.17487/RFC5492"/>
        </reference>
        <reference anchor="RFC6286">
          <front>
            <title>Autonomous-System-Wide Unique BGP Identifier for BGP-4</title>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <author fullname="J. Yuan" initials="J." surname="Yuan"/>
            <date month="June" year="2011"/>
            <abstract>
              <t>To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only Autonomous-System-wide (AS-wide) uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issues. This document updates RFC 4271. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6286"/>
          <seriesInfo name="DOI" value="10.17487/RFC6286"/>
        </reference>
        <reference anchor="RFC6514">
          <front>
            <title>BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs</title>
            <author fullname="R. Aggarwal" initials="R." surname="Aggarwal"/>
            <author fullname="E. Rosen" initials="E." surname="Rosen"/>
            <author fullname="T. Morin" initials="T." surname="Morin"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in RFC 6513. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6514"/>
          <seriesInfo name="DOI" value="10.17487/RFC6514"/>
        </reference>
        <reference anchor="RFC6793">
          <front>
            <title>BGP Support for Four-Octet Autonomous System (AS) Number Space</title>
            <author fullname="Q. Vohra" initials="Q." surname="Vohra"/>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <date month="December" year="2012"/>
            <abstract>
              <t>The Autonomous System number is encoded as a two-octet entity in the base BGP specification. This document describes extensions to BGP to carry the Autonomous System numbers as four-octet entities. This document obsoletes RFC 4893 and updates RFC 4271. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6793"/>
          <seriesInfo name="DOI" value="10.17487/RFC6793"/>
        </reference>
        <reference anchor="RFC7117">
          <front>
            <title>Multicast in Virtual Private LAN Service (VPLS)</title>
            <author fullname="R. Aggarwal" initials="R." role="editor" surname="Aggarwal"/>
            <author fullname="Y. Kamite" initials="Y." surname="Kamite"/>
            <author fullname="L. Fang" initials="L." surname="Fang"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <author fullname="C. Kodeboniya" initials="C." surname="Kodeboniya"/>
            <date month="February" year="2014"/>
            <abstract>
              <t>RFCs 4761 and 4762 describe a solution for Virtual Private LAN Service (VPLS) multicast that relies on the use of point-to-point or multipoint-to-point unicast Label Switched Paths (LSPs) for carrying multicast traffic. This solution has certain limitations for certain VPLS multicast traffic profiles. For example, it may result in highly non-optimal bandwidth utilization when a large amount of multicast traffic is to be transported.</t>
              <t>This document describes solutions for overcoming a subset of the limitations of the existing VPLS multicast solution. It describes procedures for VPLS multicast that utilize multicast trees in the service provider (SP) network. The solution described in this document allows sharing of one such multicast tree among multiple VPLS instances. Furthermore, the solution described in this document allows a single multicast tree in the SP network to carry traffic belonging only to a specified set of one or more IP multicast streams from one or more VPLS instances.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7117"/>
          <seriesInfo name="DOI" value="10.17487/RFC7117"/>
        </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="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="RFC7607">
          <front>
            <title>Codification of AS 0 Processing</title>
            <author fullname="W. Kumari" initials="W." surname="Kumari"/>
            <author fullname="R. Bush" initials="R." surname="Bush"/>
            <author fullname="H. Schiller" initials="H." surname="Schiller"/>
            <author fullname="K. Patel" initials="K." surname="Patel"/>
            <date month="August" year="2015"/>
            <abstract>
              <t>This document updates RFC 4271 and proscribes the use of Autonomous System (AS) 0 in the Border Gateway Protocol (BGP) OPEN, AS_PATH, AS4_PATH, AGGREGATOR, and AS4_AGGREGATOR attributes in the BGP UPDATE message.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7607"/>
          <seriesInfo name="DOI" value="10.17487/RFC7607"/>
        </reference>
        <reference anchor="RFC7705">
          <front>
            <title>Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH Attribute</title>
            <author fullname="W. George" initials="W." surname="George"/>
            <author fullname="S. Amante" initials="S." surname="Amante"/>
            <date month="November" year="2015"/>
            <abstract>
              <t>This document discusses some existing commonly used BGP mechanisms for Autonomous System Number (ASN) migration that are not formally part of the BGP4 protocol specification. It is necessary to document these de facto standards to ensure that they are properly supported in future BGP protocol work.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7705"/>
          <seriesInfo name="DOI" value="10.17487/RFC7705"/>
        </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="RFC8212">
          <front>
            <title>Default External BGP (EBGP) Route Propagation Behavior without Policies</title>
            <author fullname="J. Mauch" initials="J." surname="Mauch"/>
            <author fullname="J. Snijders" initials="J." surname="Snijders"/>
            <author fullname="G. Hankins" initials="G." surname="Hankins"/>
            <date month="July" year="2017"/>
            <abstract>
              <t>This document updates RFC 4271 by defining the default behavior of a BGP speaker when there is no Import or Export Policy associated with an External BGP session.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8212"/>
          <seriesInfo name="DOI" value="10.17487/RFC8212"/>
        </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="RFC9003">
          <front>
            <title>Extended BGP Administrative Shutdown Communication</title>
            <author fullname="J. Snijders" initials="J." surname="Snijders"/>
            <author fullname="J. Heitz" initials="J." surname="Heitz"/>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <author fullname="A. Azimov" initials="A." surname="Azimov"/>
            <date month="January" year="2021"/>
            <abstract>
              <t>This document enhances the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short free-form message to describe why a BGP session was shut down or reset. This document updates RFC 4486 and obsoletes RFC 8203 by defining an Extended BGP Administrative Shutdown Communication of up to 255 octets to improve communication using multibyte character sets.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9003"/>
          <seriesInfo name="DOI" value="10.17487/RFC9003"/>
        </reference>
        <reference anchor="RFC9072">
          <front>
            <title>Extended Optional Parameters Length for BGP OPEN Message</title>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <date month="July" year="2021"/>
            <abstract>
              <t>The Optional Parameters in the BGP OPEN message as defined in the base BGP specification are limited to 255 octets due to a one-octet length field. BGP capabilities are carried in this field and may foreseeably exceed 255 octets in the future, leading to concerns about this limitation.</t>
              <t>This document updates RFC 4271 by extending, in a backward-compatible manner, the length of the Optional Parameters in a BGP OPEN message. The Parameter Length field of individual Optional Parameters is also extended.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9072"/>
          <seriesInfo name="DOI" value="10.17487/RFC9072"/>
        </reference>
        <reference anchor="RFC9687">
          <front>
            <title>Border Gateway Protocol 4 (BGP-4) Send Hold Timer</title>
            <author fullname="J. Snijders" initials="J." surname="Snijders"/>
            <author fullname="B. Cartwright-Cox" initials="B." surname="Cartwright-Cox"/>
            <author fullname="Y. Qu" initials="Y." surname="Qu"/>
            <date month="November" year="2024"/>
            <abstract>
              <t>This document defines the SendHoldTimer, along with the SendHoldTimer_Expires event, for the Border Gateway Protocol (BGP) Finite State Machine (FSM). Implementation of the SendHoldTimer helps overcome situations where a BGP connection is not terminated after the local system detects that the remote system is not processing BGP messages. This document specifies that the local system should close the BGP connection and not solely rely on the remote system for connection closure when the SendHoldTimer expires. This document updates RFC 4271.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9687"/>
          <seriesInfo name="DOI" value="10.17487/RFC9687"/>
        </reference>
        <reference anchor="RFC9774">
          <front>
            <title>Deprecation of AS_SET and AS_CONFED_SET in BGP</title>
            <author fullname="W. Kumari" initials="W." surname="Kumari"/>
            <author fullname="K. Sriram" initials="K." surname="Sriram"/>
            <author fullname="L. Hannachi" initials="L." surname="Hannachi"/>
            <author fullname="J. Haas" initials="J." surname="Haas"/>
            <date month="May" year="2025"/>
            <abstract>
              <t>BCP 172 (i.e., RFC 6472) recommends not using AS_SET and AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol (BGP). This document advances that recommendation to a standards requirement in BGP; it prohibits the use of the AS_SET and AS_CONFED_SET path segment types in the AS_PATH. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a BGP route clearer. This will also simplify the design, implementation, and deployment of various BGP security mechanisms. This document updates RFC 4271 by deprecating the origination of BGP routes with AS_SET (Type 1 AS_PATH segment) and updates RFC 5065 by deprecating the origination of BGP routes with AS_CONFED_SET (Type 4 AS_PATH segment). Finally, it obsoletes RFC 6472.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9774"/>
          <seriesInfo name="DOI" value="10.17487/RFC9774"/>
        </reference>
        <reference anchor="I-D.ietf-idr-bgp-issues">
          <front>
            <title>Issues in Revising BGP-4 (RFC1771 to RFC4271)</title>
            <author fullname="Andrew Lange" initials="A." surname="Lange">
              <organization>Alcatel-Lucent</organization>
            </author>
            <date day="27" month="March" year="2012"/>
            <abstract>
              <t>   This document records the issues discussed and the consensus reached
   in the Interdomain Routing (IDR) Working Group during its efforts to
   revise and bring up to date the base specification for the BGP-4
   protocol as documented in RFC1771.  The document focuses on the
   changes tracked from August 2002 when the last major push for
   revision began.  The results of these efforts are encoded in RFC4271,
   which should be taken as normative for any of the issues that were
   discussed.  The discussion here is intended to record how and why
   some of the changes to BGP were made.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-issues-06"/>
        </reference>
        <reference anchor="IS10747">
          <front>
            <title>Information Processing Systems - Telecommunications and Information Exchange between Systems - Protocol for Exchange of Inter-domain Routeing Information among Intermediate Systems to Support Forwarding of ISO 8473 PDUs</title>
            <author>
              <organization>ISO/IEC IS10747</organization>
            </author>
            <date year="1993"/>
          </front>
        </reference>
      </references>
    </references>
    <?line 5249?>

<section anchor="acknowledgements">
      <name>Acknowledgements</name>
      <t>This document is closely based on RFC 4271.</t>
      <t>(Further acknowledgements to be supplied.)</t>
      <section anchor="acknowledgements-section-of-rfc-4271">
        <name>Acknowledgements Section of RFC 4271</name>
        <t>RFC 4271 contained the following acknowledgements:</t>
        <t>This document was originally published as <xref target="RFC1267"/> in October 1991,
jointly authored by Kirk Lougheed and Yakov Rekhter.</t>
        <t>We would like to express our thanks to Guy Almes, Len Bosack, and
Jeffrey C. Honig for their contributions to the earlier version
(BGP-1) of this document.</t>
        <t>We would like to specially acknowledge numerous contributions by
Dennis Ferguson to the earlier version of this document.</t>
        <t>We would like to explicitly thank Bob Braden for the review of the
earlier version (BGP-2) of this document, and for his constructive
and valuable comments.</t>
        <t>We would also like to thank Bob Hinden, Director for Routing of the
Internet Engineering Steering Group, and the team of reviewers he
assembled to review the earlier version (BGP-2) of this document.
This team, consisting of Deborah Estrin, Milo Medin, John Moy, Radia
Perlman, Martha Steenstrup, Mike St. Johns, and Paul Tsuchiya, acted
with a strong combination of toughness, professionalism, and
courtesy.</t>
        <t>Certain sections of the document borrowed heavily from IDRP
<xref target="IS10747"/>, which is the OSI counterpart of BGP.  For this, credit
should be given to the ANSI X3S3.3 group chaired by Lyman Chapin and
to Charles Kunzinger, who was the IDRP editor within that group.</t>
        <t>We would also like to thank Benjamin Abarbanel, Enke Chen, Edward
Crabbe, Mike Craren, Vincent Gillet, Eric Gray, Jeffrey Haas, Dimitry
Haskin, Stephen Kent, John Krawczyk, David LeRoy, Dan Massey,
Jonathan Natale, Dan Pei, Mathew Richardson, John Scudder, John
Stewart III, Dave Thaler, Paul Traina, Russ White, Curtis Villamizar,
and Alex Zinin for their comments.</t>
        <t>We would like to specially acknowledge Andrew Lange for his help in
preparing the final version of this document.</t>
        <t>Finally, we would like to thank all the members of the IDR Working
Group for their ideas and the support they have given to this
document.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-4486">
        <name>Acknowledgements in relationship to RFC 4486</name>
        <t><xref target="RFC4486"/> was authored by Enke Chen and Vincent Gillet. Its
contents have been subsumed in this document.</t>
        <t>RFC 4486 contains the following acknowledgments:</t>
        <t>The authors would like to thank Yakov Rekhter, Pedro Marques, Andrew
Lange, and Don Goodspeed for their review and suggestions.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-5492">
        <name>Acknowledgements in relationship to RFC 5492</name>
        <t><xref target="RFC5492"/> was authored by John Scudder and Ravi Chandra. Its contents
have been subsumed in this document.</t>
        <t>RFC 5492 contains the following acknowledgments:</t>
        <t>The authors would like to thank members of the IDR Working Group and the
IESG and its Directorates for their review and comments.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-6286">
        <name>Acknowledgements in relationship to RFC 6286</name>
        <t><xref target="RFC6286"/> was authored by Enke Chen and Jenny Yuan. Its contents have
been subsumed in this document.</t>
        <t>RFC 6286 contains the following acknowledgments:</t>
        <t>The authors would like to thank members of the IDR Working Group for
discussions on the "IPv6-only Network" related issues that inspired this
document.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-6793">
        <name>Acknowledgements in relationship to RFC 6793</name>
        <t><xref target="RFC6793"/> was authored by Enke Chen and Quaizar Vohra. Its contents 
have been subsumed in this document.</t>
        <t>RFC 6793 contains the following acknowledgments:</t>
        <t>The authors would like to thank Yakov Rekhter, Chaitanya Kodeboyina,
and Jeffrey Haas for the numerous discussions that went into the
making of this document.</t>
        <t>The authors would also like to thank members of the IDR Working Group
for their review and comments.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-7606">
        <name>Acknowledgements in relationship to RFC 7606</name>
        <t><xref target="RFC7606"/> was authored by Enke Chen, John Scudder, Pradosh Mohapatra,
and Keyur Patel. Its contents have been partially subsumed in this document.</t>
        <t>RFC 7606 contains the following acknowledgments:</t>
        <t>The authors wish to thank Juan Alcaide, Deniz Bahadir, Ron Bonica,
Mach Chen, Andy Davidson, Bruno Decraene, Stephen Farrell, Rex
Fernando, Jeff Haas, Chris Hall, Joel Halpern, Dong Jie, Akira Kato,
Miya Kohno, Warren Kumari, Tony Li, Alton Lo, Shin Miyakawa, Tamas
Mondal, Jonathan Oddy, Tony Przygienda, Robert Raszuk, Yakov Rekhter,
Eric Rosen, Shyam Sethuram, Rob Shakir, Naiming Shen, Adam Simpson,
Ananth Suryanarayana, Kaliraj Vairavakkalai, Lili Wang, and Ondrej
Zajicek for their observations and discussion of this topic and
review of this document.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-7607">
        <name>Acknowledgements in relationship to RFC 7607</name>
        <t><xref target="RFC7607"/> was authored by Warren Kumari, Randy Bush, Heather Schiller,
and Keyur Patel. Its contents have been partially subsumed in this
document.</t>
        <t>RFC 7607 contains the following acknowledgments:</t>
        <t>The authors wish to thank Elwyn Davies, Enke Chen, Brian Dickson, Bruno
Decraene, Robert Raszuk, Jakob Heitz, Danny McPherson, Chris Morrow,
iLya, John Scudder, Jeff Tantsura, Daniel Ginsburg, and Susan Hares. 
Apologies to those we may have missed; it was not intentional.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-8212">
        <name>Acknowledgements in relationship to RFC 8212</name>
        <t><xref target="RFC8212"/> was authored by Jared Mauch, Job Snijders, and Greg Hankins.
Its content were subsumed in this document.</t>
        <t>RFC 8212 contained the following acknowledgements:</t>
        <t>The following people contributed to successful deployment of the
solution described in RFC8212: Jakob Heitz &amp; Ondrej Filip.</t>
        <t>The authors would like to thank the following people for their
comments, support and review: Shane Amante, Christopher Morrow,
Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,
Brian Dickson, Jeffrey Haas, John Heasley, Ignas Bagdonas, Donald
Smith, Alvaro Retana, John Scudder, and Dale Worley.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-9072">
        <name>Acknowledgements in relationship to RFC 9072</name>
        <t><xref target="RFC9072"/> was authored by Enke Chen and John Scudder. Its contents were 
subsumed in this document.</t>
        <t>RFC 9072 contained the following acknowledgments:</t>
        <t>The authors would like to thank Yakov Rekhter and Srihari Sangli for
discussing various options to enlarge the Optional Parameters field. We
would also like to thank Matthew Bocci, Bruno Decraene, John Heasley,
Jakob Heitz, Christer Holmberg, Pradosh Mohapatra, Keyur Patel, and
Hannes Gredler for their valuable comments.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-9687">
        <name>Acknowledgements in relationship to RFC 9687</name>
        <t><xref target="RFC9687"/> was authored by Job Snijders, Ben Cartwright-Cox, and Yingzhen Qu.
Its content were subsumed in this document.</t>
        <t>RFC 9687 contained the following acknowledgements:</t>
        <t>The authors would like to thank William McCall, Theo de Raadt, John
Heasley, Nick Hilliard, Jeffrey Haas, Tom Petch, Susan Hares, Keyur
Patel, Ben Maddison, Claudio Jeker, and John Scudder for their
helpful review of this document.</t>
      </section>
      <section anchor="acknowledgements-in-relationship-to-rfc-9774">
        <name>Acknowledgements in relationship to RFC 9774</name>
        <t><xref target="RFC9774"/> was authored by Warren Kumari, Kotikalapudi Sriram, Lilia
Hannachi, and Jeffrey Haas. Its contents have been partially subsumed in
this document.</t>
        <t>RFC 9774 contained the following acknowledgements:</t>
        <t>The authors would like to thank Alvaro Retana, John Scudder, Ketan
Talaulikar, Keyur Patel, Susan Hares, Claudio Jeker, Nick Hilliard,
Robert Raszuk, John Heasley, Job Snijders, Jared Mauch, Jakob Heitz,
Tony Przygienda, Douglas Montgomery, Randy Bush, Curtis Villamizar,
Danny McPherson, Chris Morrow, Tom Petch, Ilya Varlashkin, Enke Chen,
Tony Li, Florian Weimer, John Leslie, Paul Jakma, Rob Austein, Russ
Housley, Sandra Murphy, Steven M. Bellovin, Steve Kent, Steve Padgett,
and Alfred Hoenes for comments and suggestions. The comments and
suggestions received from the IESG reviewers are also much appreciated.</t>
      </section>
    </section>
    <section anchor="compare4271">
      <name>Comparison of CURRENT_SPEC with RFC 4271</name>
      <t>This section describes significant technical changes between the present
specification and RFC 4271. In addition, RFC 4271 contains a comparison
between that specification and older BGP specifications. Readers
interested in the evolution of RFC 4271 should also
consider consulting <xref target="I-D.ietf-idr-bgp-issues"/>, which "records the
issues discussed and the consensus reached" during development.</t>
      <section anchor="version-00">
        <name>Version 00</name>
        <ul spacing="normal">
          <li>
            <t>Integrated all verified errata.</t>
          </li>
          <li>
            <t>Converted source to Markdown format.</t>
          </li>
        </ul>
      </section>
      <section anchor="version-01">
        <name>Version 01</name>
        <ul spacing="normal">
          <li>
            <t>Integrated RFC 6286, "Autonomous-System-Wide Unique BGP Identifier 
for BGP-4". This also obsoletes RFC 6286. (Issue #16)</t>
          </li>
          <li>
            <t>Integrated RFC 6608, "Subcodes for BGP Finite State Machine Error".
This also obsoletes RFC 6608. (Issue #17)</t>
          </li>
          <li>
            <t>Added a pointer to RFC 7705 ("Autonomous System Migration Mechanisms 
and Their Effects on the BGP AS_PATH Attribute"). (Issue #21)</t>
          </li>
          <li>
            <t>Merge RFC 8212 ("Default EBGP Route Propagation Behavior without 
Policies"). This also obsoletes RFC 8212. (Issue #22)</t>
          </li>
          <li>
            <t>Merge RFC 9687 ("Border Gateway Protocol 4 (BGP-4) Send Hold Timer")
This also obsoletes RFC 9687. (Issue #25)</t>
          </li>
          <li>
            <t>Address IANA review comments related to IANA Considerations section.
(Issue #54)</t>
          </li>
          <li>
            <t>Say "session attribute" in FSM section, to disambiguate from path 
attribute. (Issue #56)</t>
          </li>
          <li>
            <t>Created a "roadmap" section, which replaces the "placeholder" section.
The roadmap section is a work in progress, but there's something
there now, at least. (Issue #58, still in progress)</t>
          </li>
          <li>
            <t>Change from "trailing bits are irrelevant" to "trailing bits <bcp14>MUST</bcp14> be
zero". (Issue #63)</t>
          </li>
          <li>
            <t>Removed the requirement that Partial must be set if an attribute 
is added to a route in flight. This was found to not be universally
implemented in practice, and its removal poses no interoperability
concerns. (Issue #83)</t>
          </li>
          <li>
            <t><bcp14>SHOULD</bcp14> prepend -&gt; <bcp14>MUST</bcp14> prepend. (Issue #84)</t>
          </li>
          <li>
            <t>Tighten up "no cost can be determined" rule in tie-breakers. (Issue #90)</t>
          </li>
          <li>
            <t>Removed a bullet from "information reduction" subsection that 
related to use of AS_SETs. (Issue #95, partial, issue remains open)</t>
          </li>
          <li>
            <t>Add an informative reference to I-D.ietf-idr-bgp-issues. (Issue #101)</t>
          </li>
          <li>
            <t>Mandate that ORIGIN values 3-255 must never be sent. RFC 7606 already
says what to do if they are received (treat-as-withdraw). (Issue #102)</t>
          </li>
          <li>
            <t>Add IANA registry for AS_PATH segment types. (Issue #103)</t>
          </li>
          <li>
            <t>Fix HoldTimer description in OpenConfirm Event 26. (Issue #109)</t>
          </li>
          <li>
            <t>Clarify that detection of an AS loop is a semantic error, not a 
syntax error in the AS_PATH, despite use of an error code that 
includes the word "malformed". (Issue #110)</t>
          </li>
          <li>
            <t>Remove mentions of RFC 4020 from IANA section. (Issue #114)</t>
          </li>
          <li>
            <t>Clarify apparent (but not actual) bad cross-reference in 
Administrative Events section. The old text said "section" where
it really meant "field". Cleaned up the surrounding words a bit, too.
(Issue #118)</t>
          </li>
        </ul>
      </section>
      <section anchor="version-02">
        <name>Version 02</name>
        <ul spacing="normal">
          <li>
            <t>Bring changelog up to date, including for earlier versions.</t>
          </li>
          <li>
            <t>Add references to RFC 8654 ("Extended Message Support for BGP") from
all parts of the spec that it touches. (Issue #23)</t>
          </li>
        </ul>
      </section>
      <section anchor="version-03">
        <name>Version 03</name>
        <ul spacing="normal">
          <li>
            <t>The primary contribution of this version is to integrate RFC 7606
("Revised Error Handling for BGP UPDATE Messages").  (Issue #19)</t>
          </li>
        </ul>
        <t>This also pulled in a couple of dependent/related issues:</t>
        <ul spacing="normal">
          <li>
            <t>Removed the paragraph about "unrecognized well-known attribute."
(Issue #136)</t>
          </li>
          <li>
            <t>Deprecated UPDATE error subcodes 2-6, 8, 9, and 11, because the 
corresponding RFC 4271 error conditions no longer generate
NOTIFICATIONs under the revised error handling procedures.
(Issue #137)</t>
          </li>
        </ul>
        <t>Because this was a large change, some details beyond the obvious 
are called out below:</t>
        <ul spacing="normal">
          <li>
            <t>Added permission for an implementation to revert to session reset 
behavior by configuration.</t>
          </li>
          <li>
            <t>RFC 4271 said a semantically incorrect Next Hop should result in
the update message being "ignored". This isn't mentioned in 7606
but that was an oversight. Changed "ignored" to "treat-as-withdraw".</t>
          </li>
          <li>
            <t>The Withdrawn Routes field was sometimes (inconsistently) given in
ALL CAPS. Made it consistently mixed-case.</t>
          </li>
          <li>
            <t>RFC 7606 is not fully obsoleted, because it also revises numerous
other RFCs, and it didn't seem desirable to pull all those revisions
into this spec.</t>
          </li>
          <li>
            <t>Added a definition for what "recognized" means. There seems to be 
general understanding of this by practitioners, but as far as I can 
tell, we've never formalized it, and some of the error procedures 
rely on it.</t>
          </li>
          <li>
            <t>Added definitions for AFI, SAFI, AFI/SAFI, MP_REACH_NLRI, 
MP_UNREACH_NLRI. This might end up being the wedge that pulls all of 
RFC 4760 along, who knows.</t>
          </li>
        </ul>
        <t>To do and/or not done:</t>
        <ul spacing="normal">
          <li>
            <t>In the FSM, the description of an UpdateMsgErr event in Established 
state is wrong now. This wasn't fixed in RFC 7606, and our FSM needs
more work, so I've opened #140 to track, but not otherwise addressed
it.</t>
          </li>
          <li>
            <t>Section 8 ("Guidance for Authors of BGP Specifications") isn't 
integrated.</t>
          </li>
          <li>
            <t>The philosophical overview of Section 1 isn't integrated. It might 
be worth creating an appendix talking about the error-handling
philosophy, to retain this information, since it's non-obvious to
those who didn't live through it. That might also be a place to 
put the Section 8 material.</t>
          </li>
          <li>
            <t>Because not all of 7606 is integrated, and especially not the various
attribute updates for non-4271 attributes, some fancy footwork may be
needed with "updates" description text. I stubbed in a beginning, but
it will need polishing.</t>
          </li>
        </ul>
      </section>
      <section anchor="version-04">
        <name>Version 04</name>
        <ul spacing="normal">
          <li>
            <t>Add references to RFC 6793 ("BGP Support for Four-Octet Autonomous 
System (AS) Number Space") from all the parts of the spec that it
touches. (Issue #18)</t>
          </li>
          <li>
            <t>Merge RFC 7607, "Codification of AS 0 Processing". (Issue #20) As 
part of this, also introduced a new top-level section, "Protocol
Invariants". For now, this is the home for the definition of the
system's own AS number (this previously was not defined!). It 
seems likely we will find more things to put in this section; if
it ends up holding only the one definition we can look for a place
to demote it, if wanted.</t>
          </li>
          <li>
            <t>Merge RFC 9072, "Extended Optional Parameters Length for BGP 
OPEN Message". This also obsoletes RFC 9072. (Issue #24)</t>
          </li>
          <li>
            <t>Merge RFC 9774, "Deprecation of AS_SET and AS_CONFED_SET in BGP".
(Issue #47) This required substantial restructuring of the aggregation
procedures. RFC 4271's aggregation description relied on construction
of AS_SETs, now deprecated. The replacement algorithm collapses to
"find the longest leading sequence".</t>
          </li>
          <li>
            <t>Merge RFC 4486, "Subcodes for BGP Cease Notification Message".
(Issue #147)</t>
          </li>
          <li>
            <t>Changed the definition of AGGREGATOR from containing an IPv4 address
to containing a BGP Identifier. This finesses the lack of an
IPv6-specific encoding and is barely a normative change, since the
previous definition already stated that the address <bcp14>SHOULD</bcp14> be the BGP
Identifier. One can also view this as fixing a long-standing
specification defect, since a BGP Identifier has not been required to
be an IP address since RFC 6286. (Issue #150)</t>
          </li>
        </ul>
      </section>
      <section anchor="version-05">
        <name>Version 05</name>
        <ul spacing="normal">
          <li>
            <t>Fixed two lingering places where BGP Identifier was described
as an IP address, that were missed during RFC 6286 integration.
(Issue #154)</t>
          </li>
          <li>
            <t>Got rid of the mandatory/discretionary/well-known taxonomy, 
while retaining "optional" and "transitive". Instead of relying
on the taxonomy to tell people how to set the Optional, Transitive,
and Partial bits for any of the mandatory attributes, spell out
the concrete requirements where the attributes are defined.
(Issue #49) (Issue #55) (Issue #138) (Issue #139)</t>
          </li>
        </ul>
      </section>
      <section anchor="version-06">
        <name>Version 06</name>
        <ul spacing="normal">
          <li>
            <t>Renamed "Unsupported Capability" to "Required Capability Not 
Received". (Issue #158)</t>
          </li>
          <li>
            <t>Integrated RFC 5492, "Capabilities Advertisement with BGP-4".
This also obsoletes RFC 5492. (Issue #160) Capabilities are now
mandatory other than for backward compatibility; they're 
necessary for four-octet ASN support.</t>
          </li>
          <li>
            <t>Integrated RFC 6793, "BGP Support for Four-Octet Autonomous 
System (AS) Number Space". This also obsoletes RFC 6793. (Issue #164)
There is one normative change vs. RFC 6793, which is that support for
the compatibility mode is made optional. A non-normative change is
that much of the explanatory material was not carried forward. Section
5 ("Handling BGP Communities") is only advisory and was also not
carried forward.</t>
          </li>
        </ul>
        <t>To do and/or not done:</t>
        <ul spacing="normal">
          <li>
            <t>No changes were made to the FSM as part of the integration of RFC 6793. 
Some FSM text still reflects assumptions from the 2-octet ASN era and
will be reviewed separately as part of a planned FSM update.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="tcpopts">
      <name>TCP Options that May Be Used with BGP</name>
      <t>If a local system TCP user interface supports the TCP PUSH function,
then each BGP message <bcp14>SHOULD</bcp14> be transmitted with PUSH flag set.
Setting PUSH flag forces BGP messages to be transmitted to the
receiver promptly.</t>
      <t>If a local system TCP user interface supports setting the DSCP field
<xref target="RFC2474"/> for TCP connections, then the TCP connection used by BGP
<bcp14>SHOULD</bcp14> be opened with bits 0-2 of the DSCP field set to 110 (binary).</t>
      <t>An implementation <bcp14>MUST</bcp14> support the TCP MD5 option <xref target="RFC2385"/>.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>A BGP implementation <bcp14>MUST</bcp14> support the authentication mechanism
specified in RFC 2385 <xref target="RFC2385"/>.  The authentication provided by this
mechanism could be done on a per-peer basis.</t>
      <t>BGP makes use of TCP for reliable transport of its traffic between
peer routers.  To provide connection-oriented integrity and data
origin authentication on a point-to-point basis, BGP specifies use of
the mechanism defined in RFC 2385.  These services are intended to
detect and reject active wiretapping attacks against the inter-router
TCP connections.  Absent the use of mechanisms that effect these
security services, attackers can disrupt these TCP connections and/or
masquerade as a legitimate peer router.  Because the mechanism
defined in the RFC does not provide peer-entity authentication, these
connections may be subject to some forms of replay attacks that will
not be detected at the TCP layer.  Such attacks might result in
delivery (from TCP) of "broken" or "spoofed" BGP messages.</t>
      <t>The mechanism defined in RFC 2385 augments the normal TCP checksum
with a 16-byte message authentication code (MAC) that is computed
over the same data as the TCP checksum.  This MAC is based on a one-
way hash function (MD5) and use of a secret key.  The key is shared
between peer routers and is used to generate MAC values that are not
readily computed by an attacker who does not have access to the key.
A compliant implementation must support this mechanism, and must
allow a network administrator to activate it on a per-peer basis.</t>
      <t>RFC 2385 does not specify a means of managing (e.g., generating,
distributing, and replacing) the keys used to compute the MAC.  RFC
3562 <xref target="RFC3562"/> (an informational document) provides some guidance in
this area, and provides rationale to support this guidance.  It notes
that a distinct key should be used for communication with each
protected peer.  If the same key is used for multiple peers, the
offered security services may be degraded, e.g., due to an increased
risk of compromise at one router that adversely affects other
routers.</t>
      <t>The keys used for MAC computation should be changed periodically, to
minimize the impact of a key compromise or successful cryptanalytic
attack.  RFC 3562 suggests a crypto period (the interval during which
a key is employed) of, at most, 90 days.  More frequent key changes
reduce the likelihood that replay attacks (as described above) will
be feasible.  However, absent a standard mechanism for effecting such
changes in a coordinated fashion between peers, one cannot assume
that BGP-4 implementations complying with this RFC will support
frequent key changes.</t>
      <t>Obviously, each should key also be chosen to be difficult for an
attacker to guess.  The techniques specified in RFC 1750 for random
number generation provide a guide for generation of values that could
be used as keys.  RFC 2385 calls for implementations to support keys
"composed of a string of printable ASCII of 80 bytes or less."  RFC
3562 suggests keys used in this context be 12 to 24 bytes of random
(pseudo-random) bits.  This is fairly consistent with suggestions for
analogous MAC algorithms, which typically employ keys in the range of
16 to 20 bytes.  To provide enough random bits at the low end of this
range, RFC 3562 also observes that a typical ACSII text string would
have to be close to the upper bound for the key length specified in
RFC 2385.</t>
      <t>BGP vulnerabilities analysis is discussed in <xref target="RFC4272"/>.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section anchor="path-attribute-flags">
        <name>Path Attribute Flags</name>
        <t>IANA is requested to create a registry called "BGP Path Attribute Flags"
within the "Border Gateway Protocol (BGP) Parameters" group. The allocation
policy is Standards Action.</t>
        <t>Bits 0-3 are defined in <xref target="updatefmt"/>. Bit 4, marked deprecated, was
proposed in draft-ietf-idr-optional-transitive-02 and later removed in
draft-ietf-idr-optional-transitive-04, but not before at least one known
implementation had shipped. At the time of writing, it is not considered
safe to assign.</t>
        <table>
          <thead>
            <tr>
              <th align="left">Bit Position</th>
              <th align="left">Name</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">0</td>
              <td align="left">Optional</td>
              <td align="left">(this document)</td>
            </tr>
            <tr>
              <td align="left">1</td>
              <td align="left">Transitive</td>
              <td align="left">(this document)</td>
            </tr>
            <tr>
              <td align="left">2</td>
              <td align="left">Partial</td>
              <td align="left">(this document)</td>
            </tr>
            <tr>
              <td align="left">3</td>
              <td align="left">Extended Length</td>
              <td align="left">(this document)</td>
            </tr>
            <tr>
              <td align="left">4</td>
              <td align="left">Deprecated</td>
              <td align="left">(this document)</td>
            </tr>
            <tr>
              <td align="left">5-7</td>
              <td align="left">Unassigned</td>
              <td align="left"> </td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="message-types">
        <name>Message Types</name>
        <t>All the BGP messages contain an 8-bit message type, for which IANA
has created and is maintaining a registry entitled "BGP Message
Types".  IANA is requested to update its reference to this document.
This document defines the following message types:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">OPEN</td>
              <td align="left">1</td>
              <td align="left">See <xref target="openfmt"/></td>
            </tr>
            <tr>
              <td align="left">UPDATE</td>
              <td align="left">2</td>
              <td align="left">See <xref target="updatefmt"/></td>
            </tr>
            <tr>
              <td align="left">NOTIFICATION</td>
              <td align="left">3</td>
              <td align="left">See <xref target="notifyfmt"/></td>
            </tr>
            <tr>
              <td align="left">KEEPALIVE</td>
              <td align="left">4</td>
              <td align="left">See <xref target="keepalivefmt"/></td>
            </tr>
          </tbody>
        </table>
        <t>Future assignments are to be made using the Standards Action process
defined in <xref target="RFC8126"/>.  Assignments consist of a name and the value.</t>
      </section>
      <section anchor="path-attribute-types">
        <name>Path Attribute Types</name>
        <t>The BGP UPDATE messages may carry one or more Path Attributes, where
each Attribute contains an 8-bit Attribute Type Code.  IANA is
already maintaining such a registry, entitled "BGP Path Attributes".
This document defines the following Path Attributes Type Codes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">ORIGIN</td>
              <td align="left">1</td>
              <td align="left">See <xref target="origin"/></td>
            </tr>
            <tr>
              <td align="left">AS_PATH</td>
              <td align="left">2</td>
              <td align="left">See <xref target="aspath"/></td>
            </tr>
            <tr>
              <td align="left">NEXT_HOP</td>
              <td align="left">3</td>
              <td align="left">See <xref target="nexthop"/></td>
            </tr>
            <tr>
              <td align="left">MULTI_EXIT_DISC</td>
              <td align="left">4</td>
              <td align="left">See <xref target="med"/></td>
            </tr>
            <tr>
              <td align="left">LOCAL_PREF</td>
              <td align="left">5</td>
              <td align="left">See <xref target="localpref"/></td>
            </tr>
            <tr>
              <td align="left">ATOMIC_AGGREGATE</td>
              <td align="left">6</td>
              <td align="left">See <xref target="atomic"/></td>
            </tr>
            <tr>
              <td align="left">AGGREGATOR</td>
              <td align="left">7</td>
              <td align="left">See <xref target="aggregator"/></td>
            </tr>
          </tbody>
        </table>
        <t>Future assignments are to be made using the Standards Action process
defined in <xref target="RFC8126"/>.  Assignments consist of a name and the value.</t>
      </section>
      <section anchor="error-codes">
        <name>Error Codes</name>
        <t>The BGP NOTIFICATION message carries an 8-bit Error Code, for which
IANA has created and is maintaining a registry entitled "BGP Error
(Notification) Codes".  This document defines the following Error Codes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Message Header Error</td>
              <td align="left">1</td>
              <td align="left">
                <xref target="msgheadererr"/></td>
            </tr>
            <tr>
              <td align="left">OPEN Message Error</td>
              <td align="left">2</td>
              <td align="left">
                <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">UPDATE Message Error</td>
              <td align="left">3</td>
              <td align="left">
                <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Hold Timer Expired</td>
              <td align="left">4</td>
              <td align="left">
                <xref target="holdtimerexperr"/></td>
            </tr>
            <tr>
              <td align="left">Finite State Machine Error</td>
              <td align="left">5</td>
              <td align="left">
                <xref target="fsmerr"/></td>
            </tr>
            <tr>
              <td align="left">Cease</td>
              <td align="left">6</td>
              <td align="left">
                <xref target="ceaseerr"/></td>
            </tr>
          </tbody>
        </table>
        <t>Future assignments are to be made using the Standards Action process
defined in <xref target="RFC8126"/>.  Assignments consist of a name and the value.</t>
      </section>
      <section anchor="error-subcodes">
        <name>Error Subcodes</name>
        <t>The BGP NOTIFICATION message carries an 8-bit Error Subcode, where
each Subcode has to be defined within the context of a particular
Error Code, and thus has to be unique only within that context.</t>
        <t>IANA has created and is maintaining a set of registries, "BGP Error
Subcodes", with a separate registry for each BGP Error Code.  Future
assignments are to be made using the Standards Action process defined in
<xref target="RFC8126"/>.  Assignments consist of a name and the value.</t>
        <t>IANA maintains a subregistry below the BGP Error Subcodes registry
called "Message Header Error subcodes". IANA is requested to rename this
subregistry "BGP Message Header Error subcodes". This document defines
the following BGP Message Header Error subcodes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Unspecific</td>
              <td align="left">0</td>
              <td align="left">See <xref target="msgheadererr"/></td>
            </tr>
            <tr>
              <td align="left">Connection Not Synchronized</td>
              <td align="left">1</td>
              <td align="left">See <xref target="msgheadererr"/></td>
            </tr>
            <tr>
              <td align="left">Bad Message Length</td>
              <td align="left">2</td>
              <td align="left">See <xref target="msgheadererr"/></td>
            </tr>
            <tr>
              <td align="left">Bad Message Type</td>
              <td align="left">3</td>
              <td align="left">See <xref target="msgheadererr"/></td>
            </tr>
          </tbody>
        </table>
        <t>IANA maintains a subregistry below the BGP Error Subcodes registry
called "OPEN Message Error subcodes". IANA is requested to rename this
subregistry "BGP OPEN Message Error subcodes". This document defines 
the following OPEN Message Error subcodes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Unspecific</td>
              <td align="left">0</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Unsupported Version Number</td>
              <td align="left">1</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Bad Peer AS</td>
              <td align="left">2</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Bad BGP Identifier</td>
              <td align="left">3</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Unsupported Optional Parameter</td>
              <td align="left">4</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">[Deprecated]</td>
              <td align="left">5</td>
              <td align="left">See <xref target="RFC4271"/> Appendix A</td>
            </tr>
            <tr>
              <td align="left">Unacceptable Hold Time</td>
              <td align="left">6</td>
              <td align="left">See <xref target="openmsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Required Capability Not Received</td>
              <td align="left">7</td>
              <td align="left">See <xref target="caperror"/></td>
            </tr>
          </tbody>
        </table>
        <t>IANA maintains a subregistry below the BGP Error Subcodes registry
called "UPDATE Message Error subcodes". IANA is requested to rename this
subregistry "BGP UPDATE Message Error subcodes". This document defines 
the following UPDATE Message Error subcodes:</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Definition</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Unspecific</td>
              <td align="left">0</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Malformed Attribute List</td>
              <td align="left">1</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Unrecognized Well-known Attribute (deprecated)</td>
              <td align="left">2</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Missing Well-known Attribute  (deprecated)</td>
              <td align="left">3</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Attribute Flags Error (deprecated)</td>
              <td align="left">4</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Attribute Length Error (deprecated)</td>
              <td align="left">5</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Invalid ORIGIN Attribute (deprecated)</td>
              <td align="left">6</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">[Deprecated]</td>
              <td align="left">7</td>
              <td align="left">See <xref target="RFC4271"/> Appendix A</td>
            </tr>
            <tr>
              <td align="left">Invalid NEXT_HOP Attribute (deprecated)</td>
              <td align="left">8</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Optional Attribute Error (deprecated)</td>
              <td align="left">9</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Invalid Network Field</td>
              <td align="left">10</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
            <tr>
              <td align="left">Malformed AS_PATH (deprecated)</td>
              <td align="left">11</td>
              <td align="left">See <xref target="updatemsgerr"/></td>
            </tr>
          </tbody>
        </table>
        <t>RFC 6608 created the registry "BGP Finite State Machine Error Subcodes".
IANA is requested to update the reference in that registry (both overall,
and individual code points) to this document.</t>
        <t>RFC 4486 created the registry "BGP Cease NOTIFICATION message subcodes".
IANA is requested to update the reference in that registry (both overall,
and individual code points that reference RFC 4486) to this document.</t>
      </section>
      <section anchor="aspath-segment-types">
        <name>AS_PATH Segment Types</name>
        <t>IANA is requested to create a registry called "BGP AS_PATH Segment Types"
within the "Border Gateway Protocol (BGP) Parameters" group. The allocation
policy is Standards Action.</t>
        <t>Values 0 and 255 are reserved. Values 1 and 2 are defined in
<xref target="aspath_segtypes"/>. The values 3 and 4, defined in <xref target="RFC5065"/> are also
included. (Note that it is not an error that the order of SET and
SEQUENCE are reversed between the respective types.)</t>
        <table>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Value</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Reserved</td>
              <td align="left">0</td>
              <td align="left">This Document</td>
            </tr>
            <tr>
              <td align="left">AS_SET (deprecated)</td>
              <td align="left">1</td>
              <td align="left">This Document</td>
            </tr>
            <tr>
              <td align="left">AS_SEQUENCE</td>
              <td align="left">2</td>
              <td align="left">This Document</td>
            </tr>
            <tr>
              <td align="left">AS_CONFED_SEQUENCE</td>
              <td align="left">3</td>
              <td align="left">
                <xref target="RFC5065"/></td>
            </tr>
            <tr>
              <td align="left">AS_CONFED_SET (deprecated)</td>
              <td align="left">4</td>
              <td align="left">
                <xref target="RFC5065"/></td>
            </tr>
            <tr>
              <td align="left">Reserved</td>
              <td align="left">255</td>
              <td align="left">This Document</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="bgp-open-optional-parameter-types">
        <name>BGP OPEN Optional Parameter Types</name>
        <t>With the publication of RFC 9072, IANA assigned value 255 as the
Extended Length type code in the "BGP OPEN Optional Parameter Types"
registry. With the publication of this document, RFC 9072 will be
obsoleted; thus, IANA is requested to update the reference to refer to
this document.</t>
      </section>
      <section anchor="registrations-from-rfc-5492">
        <name>Registrations from RFC 5492</name>
        <t>IANA maintains a registry called "Capability Codes" whose reference 
is RFC 5492. Since this document obsoletes RFC 5492, IANA is requested
to update the reference to this document.</t>
        <t>IANA is requested to update the reference for Capabilities in the 
BGP OPEN Optional Parameter Types registry to reference this document.</t>
      </section>
      <section anchor="references-to-bgp-specification">
        <name>References to BGP Specification</name>
        <t>IANA is requested to update all references to RFC4271 in the "Border
Gateway Protocol (BGP) Parameters" registry group to refer to this
document.</t>
        <t>IANA is requested to replace all references to RFC 4271 in the IP Flow
Information Export (IPFIX) Entities registry group at
https://www.iana.org/assignments/ipfix with references to this document.</t>
        <!--
# Aggregation

RFC 4271's aggregation rules were seldom implemented as written (basic
aggregation was pervasively implemented. "Complex" from the appendix was
not) and almost never used in practice. This specification simplifies
aggregation, to document only the implemented and practiced procedures. 

etc

-->

</section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+y963YbR5Ym+j+eIhtaZ0xWgTBJUZIlV7ualukyp63LiHRV
9erVyysJJMgsgQA6M0GKLWueZZ5lnuzsa8SOyAAIyjVdNee0upeLADLjumPH
vn57b2/PdXU3q14Ug+Pi20UzqZriD2VX3ZZ3xdtm0S3Gi1lxVOx8+4e3e0e7
A1deXDTVzYuCPrvJYjwvr+HlSVNOu7266qZ79aTZu7hcHu010/HR4bODi7rd
23/qxtDo5aK5e1G03cRN4NOL4nD/8Klzi4t2Mau6qn1R4PPD4ujoq6fD4snR
88Nh8fQQ/376dP8r+O+z54+HxVeHB/D98/1n+N+nXz1zqyW2Bm8/e7oPz8J/
n8Evz54dOdd25XzyczlbzKG3u6p1y/pF4YoCpsWf6c9JteyuoHP41C6arqmm
rf7a3l3bj+PF9XU17/xnVy+bF0XXrNrucH//+f6ha1cX13Xb1ot5d7eETk9P
zr93ZVOVsMBNdzlwt5cvClgi9766u4XlpuHsyXLiX81i1dXzS3dTzVfVC/jq
Er5Zwtun370b4Hip2cGfFs17eKz4A/6K31+X9Qy+h6b/CbdhtGgu8euyGcPU
Blddt2xffPklPoVf1TfVSB/7Er/48qJZ3LbVl/D+l/jeZd1drS6wQdzT20vc
1i/fff9SdnTgXLnqrhYNjHAPHi8KpoN/Kd8vbop31furrmroe+ignNf/UXaw
JC/gl65uqgn9UvGQ7/CVf/rLal4vq2Y0r7q4xfPF/K74sc609cPbE9tOBw+O
ZvU/yf/GrZyt2nJe/AAb0eZaWpW3VW0ba99f/dN88h9XI9jxuKX/vriaF2fj
1WSSnWAyqL9ctv90tay4GfjXLPCoVZO6WzTOzRfNNbx3UxEVwOo+e37wQv96
rF8eHhw8938//uqJ/n0ElC5Pf3Vw+FS//urg2RH87er5NG3++f6RvHCw//ww
/PlY/zx8+kz/fPbsIPzpn31y8FX487n++fzxvv/zubZwePT4uf/zmXZ8+NUT
beHwuW/s8ZOn2gUSWPjTf3v05Kn/8yv/57NDbffJ/n748+kT/fPITxMZif75
5ECfRZaiK35woEN/dvRYX0OeEv70Dzzbf+I36qk2hpxJ/3z6RL99vr//2P/p
J4ScS/98xqtzuvfdyHLQPeAjK+BrDn87O9h/dkRvAAsQhn2qO7yYI68eV8B3
gCWc3bVddd0CLzmvZhWyLDhbY3qsLYAfFva9kw/jq3J+WRUXVXdbVXPztmf/
8HR4bjGF9+Fw700WQOLz4h3wqwq7ta2W1wv6Bp67BmIH9uzb7RZwGJdL4LPF
94vmtmwm+DK2evam+Oro2ePi7Xc/tQOaKN8SQFOP6aPnOPRvr5A/6Ai+wPe/
PD15qUvl3N7eXlFetF1Tjjt3flW3BVxXK+TfxaRux6u2rWA4V9Xaaw8vvd1h
cXtVj6+KunXAQWqa+vEKmMzierFqZVrKtYulvDty0GMFH+vrsrkrpqv5mBYG
5lkSs2+XVUkMvOUGalqZSlcZ2CDcDu8dXBzwzUU9q7u7ojYrfAv8uVjA6Bts
TlppR0VBE7339Xo+nq0mMH/7Jfw/LsesbjsYqOvNsi12js+qdheeKrtibduw
4DdVA4s74lWP+m2LdjWd1uMatwEJawxUCRfomJavhNuuXF7hMh2fOfhpXsEP
N9gDPtthc1G/02ZxLRukWzBbLJYtXId3QNJu2azm1WSIZA//6Wh+x2fFrLqp
ZkO47a9hjxazenxXTKpx3dIR4VeLCoc9riawlXQ7497e1LhmZdFWuELFdYXb
VbewMji8lukaB/FyVrbtDA6kHBb3XTgt+PvOS7jOd2m7qrayDcnOaGPYsCsn
sKBd3fISSecwEmhKjzWe7OL0LQyymtYfaMJFNauv6QkQJ3DisJ5jEHXwZSGQ
YjDGgQ6InGB4MFEYE0+3nLULpPdmMVkBa3FmjLT/5Wy2uC3Ky8umuiyVuHET
qnYos6DxRg84WPxl2V21dEDskfRSILJEEgRpDtclXP9M5/A9EPhpV4jA5/BB
lvnkr2f0Cn5Anlpc3MEqXrSraxwHNFE3/iCWRD2wanBEZtgYnj7teMS847qe
TGaVc49wD2kV8E0+2BtZBlL5el7heryCzyyeGVlFaGTIuwDcBwY5rRs4krpU
ID7BVn38KLf0p0/KovBRIBs8e5NqgtOnh3BK4SF41XWrho6irjk929nt+C/+
9Z/Cv4ZbMrC/U/4F9PV7kQo/fQofnn/6tIGzOcPZigdzNlwJZxhb8XmMzQXG
VnweY3PJA4ax6SJZwtGTMSlu6pIGvUSJbbICjcSc7AIOhOf9rVvMZ3f0sFmS
vYsSzjeungpPy7IpJ/XltR5xmDg0p7PhoTdOXsDtX5bj97DU3BCyAOhFDo/p
CDZn0iAJjMumqeHJmh85feuuqhLZH0ybZkLNydkd0mPAYIZA6VOQPzsWsmRv
U2p1NMgxbPEO8m74Y77odi39FiuiDr+D9LDSkCzQooWTgi3XMG2gBlx3Io7F
9qsHG3cGu1sVdaccd7m6mInkLPy4uAJ6vEA5ufrQVXNhs+GScsAXx/VUxe1R
8XrRlRezih/n86k3PDNnuLYCc76s5lUDd9N/wO3G/cEMmB7XnZomQ2zIpXnv
3LS8Bk5T4aDvFij7vy3+KBfNEZ4tQ3qyvXDOWmRu0UxIoHDm5af4OCxdV49X
s7KBxXv0qPgOTui81iG8BM2D9ucnXPFzUAXa4uOjiX+m/SQyQFvx5eIZlHmG
+Sa9S5RyBbwZOYUMDqQSOLphp5E+9F4lYYDPAJypFQ6iu4LluryCJaOnO9gV
GPnx5C97706/3Tudo27xAjlXId+18CUSVIfMbzVfspYFLeWWnfoipcRTie4U
9s0jnC3G5YzvPLxC4RQBASHJLStYWjOaN6uO9PZkPPC1HxC2x4wpIouKBCro
T1eJB0UdELnCmrV6eHk8MpYv2uKnt98dn5/AM21bXuIdiK+64+9PeW2OhSd8
j3R1V5xOoCvoomqGRE24cUxKhrpHxZspUD9tATVX05r+RYUKkgXOoIti599H
N6NdbGkAH7/E7wZ6NmBHZ3SbArdidbCpiNlU0yl8P+QdvVvidQCnizaDx0M3
yOsf350CT4HfeNt4TUjkg0HiuveUOpAWds0W0I0CizmJqBya7r9Zm0uW2S+b
nVZzZJvwE4xhhvQ3vkLVHEh1AvyqRl2VTxvzPBUia9jcSxY1eSe9uHmK4iYx
TjpssG1dU49JFptUeGxg+sUVsA/4ggbC7xPDbvVyZKGCdYa44z241VJxFZpi
5Tzbvm8bvmDxDkUu4NzMW0kCkoWUVvxi3hIBwfYulqiy1Z0cozFKOTI/InNd
PhicjAUoC5b7BnlnAUvSsryE4lFXX+O1rT+2ODSSfHidZAXKOTVzfMZyC7Un
5wMnmdlh2KrKGxCm5bgjghuy7e8GiP32Cv5zvZp19RKGqoPyHStLYrKNt5/N
ikxaZ0W5hLPZJAuKn5QV8mKMFyg6wLlXihF7o2zerGQeruwdCRRFV+gUX1rW
Y7izddKyM0YK82xUpFckXualsE8sYRpeIKyiONpbjLsKjuYKOrokRXwOV/B/
VA1pltVl1XDLLbDk2QRv/dW8/vdVpfvC53weNuamnK381sSdCm1Yzlq3MaVO
UMppO7i1VktajFpkkxIoDF9HKrkTlkjrCDtb0dUn+wq/0hUDrFRmLX3plPm0
86zqa9h68heQ9OLcCfyPMJQTkAeaudwEOyTWiLYAQ1RbXKUPEevexRY+kBDw
lqQo7ZPHK5IVEAYsIxDNTES2tiK2KaKyva/kGglMuUsumlFxjEeyHTf1hXJ1
+BPllfRRakLvpd6l6O9DHgwLYP37ikUobMmsbEvTNgvB035b+WVGkQp2flLD
RUBHoH9c4cF5uO6oC1Y5ofHvq7KtkaJp72RRo6ubOZt2Vt6gEwVfwEkgq7hg
Ib2B23ZZs/Z8iltNTZECdd9O1/N0p0/n907Zk25/vmVrL3ed6Wk0JrxVegaM
PVEYIo6/EvlFlZiItdQ9u6/ceJ65en7th0kNnPlhXT+MqEWSypKyrAuz8yDD
bUvJQdqTMxG6mAEXxg5IYzeWC6HSoYibMsyxt3iRxR7VJjtLoJUW7ga/jSLF
0ebe1rMZTpfYM8gLNF7fzHeiOanFX4mvJ1fCwv4I+in0dfr25qg4EdFH1ncG
ShNyb7qQ/UajakUyUry65QVKzKTl+EPGrFmkQdUyhtzXDnNxkA+ZIECD6T26
S0wBlHVmrTI6c7pGxPC9xCayrO6wsVWJgMiSzaxElZ5GwQaDyq/xn4AcJ015
Kz4LkAOa4rWYC34s72A/WSS0diHr1IDOZxMvN8dy8rAgyw4sjXo3UXHjQziY
mW3Q+QzQktkS98Cp1O14sWqgocnXhd/qpTZo5FahkWg1rKiNL7sfF2Mk56DN
yBdK222P5kiWiDk00xUNpkdboCekdAjk9urtz+9Ojl/+8DPK2i/w40+v7RfE
w0qQ9csOhKAL6j2vMQS1l8R2koXueGFUL1BdQVjDfL4AdYItZcR4aKdJKbmt
kPxafn0OdyoIrMtWG9X2RNEJI41JYx1VjIo/XYlqQ93iQaGWrmHDgva8mHup
BZRoPQueQhMLC02aWiGaE1kwpjjp2D/OT4IiWc2mfD+wfWLIDdV0adw2dYea
GBmKx1doqwLx+nJe/0c1Uca7jHZoiKeEuZ10zDoWfIvaf1Gr/EUEU9KPIgtM
+FS0ZT2RXRo0vrdBUVv904tKQQD2tGotH8vg5oQZlePxgo040D7q0F79k918
Z250FC1JIetJJ8uybto15kfSTfUcGLolQzgtFd1GizayMrUirnKLfXEaJWkx
eQPzwpcDVVT8c3SjAflQIz3a6VHOWqLl983Ud5BsdjdSGM2BJimCcu9SbCrc
GmM8So63b11lFWoh6QeoUJmVmk7tQL8tW9pPd+atEGeri7aCGwZlvc8ySNAw
glUia5G4xyAhRBqMEp9hkIjuPnzV2CN+mk9zgilu/E0NMhR2GETU+FkvJc4X
cMDmqGf5e5X5Ckuuckx+mjcJGzirqiKwBnns0SMQ2qxVEDf2HexD3bCaw06j
99VdgaFNsGavfjo7h/Wi/y1ev6G/3538j59O3518h3+f/XD844/+DydPnP3w
5qcfvwt/hTdfvnn16uT1d/wyfFtEX7nBq+N/GbAgNnjz9vz0zevjHwc9eYGO
FzMkErthQZGCy9ZFAuK3L9/+7/91cAR08w8ShEM+jn+QEBv4gCo+90ZmTv4I
m37nWGcntWSGUtWy7spZSxQJqi5IIKirwx7/5l9xZf7tRfG7i/Hy4Ogb+QIn
HH2paxZ9SWvW/6b3Mi9i5qtMN341o++TlY7He/wv0Wddd/Pl734/QzPR3sFX
v//GoT/13aKcXJdLIJc33715UURGYDKdEQ+rySJ8iacbhaUvwp3Gu0d2IWTN
DTdX4OZCE7x9f6i7H1YXBcXQFI+efNVzOAtLA2ptO7ye1btBehfw7TOMHSyb
SXH+7Xc/n51/9/Prn159e/Ju6C5WbOzJPOrdknxjal+tiiEs0zbkPXFi9FAx
n0glvOEtLnTNEgdFuU97ohVwDR++CT0klxIc6+mKpbX4VkWDBTsByFTVt5fX
6DsETrVaYksXi07UA3SZuL47APoi+1aHzgx4geccO0B41OwrITsKiUVo8IYt
5QWHO9FbnlADGFp3kV0Pv3DzqpqQBQyXDkZgjGFAE0v0aCcGrTBHUq5Ei13c
oD5dXwPXxj1F9yp8wFdQTlKLSRhCoC/y0t3if1xNal3JBgyURG9L6lY86Dxk
NXBRTIUfNeoGHMuAwtMAbYMlfCqHxsRQdi4dFLmBDSXDwcAo0+I7eBWDndDy
teR7FTj2ywUM58R7n9iWIp4o9JQbhUqPIF69huwqIoDEtcJr5cKwRsW31bhE
fcYuGu2jXkZGoR3jqMxeFLgXjveCl6wtzPnA5YqPofjT4W5dNWTzEa+/yGIu
OUi9KelBgkUygoG39ltGwdRLNjzcY/FSiW1XF0SEVL4pceMXTX1Zq9lHHxtu
7W9jE5X4gfl+If1RrC4jH0SH66BSAyuhwhLEZsCBKugMkhegmafajNxedHCF
b4Ag0ZFTWlkWtXJyQ7oGmQx8bw0Guc5ZckYvalcZnRwkpSE5dYbefoqzjXRE
6j1RE630iCdJQ/Um4lkD8qnRbuZpjeQuNiejhV+MQ6A3w8IAbU1mYsoSZ7va
Oj9+pEf0CVGdC6YGDAsFatieGKyOMgVNviDDd6Fhi2qdk2CZ+er6Ag2bLF/n
9j9wHd5EjQPwVAVivvTBgjKzMDIYgDwpUVQ4DR7DLXGsBnT7G2BVIzRG8c2w
CAfNMy85MToLS4rJMY6tFNcLuQiWlfqxQFKeVV5/CoOmR9Owh5rdmBfAwtA5
T8wc2mH9BQ7q7/5hb684odjpL1C0xeDQVHaghpQ6TqGfGxnm8fj9fHE7qyaX
YpLvFhQUV6GnSEM86clr5E0Umj1je1KxV/g739jt8L7GmUnvaOEmh3zF2yth
hzCIW1peXidu5UwG/FzOkH7hnqPfCybXdqsxSUDXdwUGW4hlsLwbFW8rINol
Hk4y1y1hZOTowssTr+5pA5qjo3XAl75o/bYPgUm+J5fRFW6lnCyR42/5WY1S
acldh6FjbgdWGq9W+mW2uBQ+MBqNUI1Bxn1TV7e/Jz/kl+SDSVvG+94ZKpv3
RadRsbf3DV1Yb4gb2RvrVYgBNGEUxmQlbZCqUpyhWMiuKjkMYrN1Pashr1F1
x3oAOvFE3Ueaio5jje7JO75MXNe713FSs4oUYbj5mShJ++qsTIJXlAQ7A/tw
Zi7kMezLH3o5YTT5Q9hR6201LYaSYItAGOIrffpk+OTxExA4NJ4JptLqGuHU
job7z5/y78bOSBqLmODUeFyn/GCx5OBKttWsmuWirbzFlO78yH8tEWy9ra1q
FiU7IOVL1nNBySVTlFxvQzFqtazFgk5xtrqmUEXo7I3yn/8TsZoYgIoy8aqe
YfgRDBt6q5HMiku21xANnaCzh1RKY4D4PedgfPrEPnt8ZkXbpNabs+9fn5wX
3wIDvECVZCfVSSXEbv/5Iaif2IT/Aq4rDCf+HpaI+BdGD3Fo68QZgw16wit9
69mzQ3SAyKfnj/ftp+fP8FPoAxM38JL8r7jQv2pc6L0RoEU+hN09MARUlC20
KqIFnLWtiBtWEjcomqc19/sAdA488NFKJvwu8iYAX1jhs2KN3gFRlAM/uPdh
z03vjcQDeG8gP7Mlq54Km8Gr9nrRdntB4AhPiTNfbXkhvA8PxTFc1ExSY+B0
rSMFbdUh02JdYLxYVr0l2WbRfIDIIFhmB3zx0EqVcxcH3Imxks1Iz54f+BMV
B6anWkLvPvKaAa7Krw8O1RdgbX51cGjhg0OdDQ7FvSp7oa5odzXhnHjRCzFH
UZxu+yhOvv9DMCgFlOJhkD6AH148KKaW3borr1lJ1Na/r4CS0IlCRj0QlseV
P7875fsSLwYcQ6ffqqvKH8oC5RorBcDvuErVB2BUul14kqs5mQKoM53YSOKr
w+tE1hdq4NlA1b8iGpyjEvZ+fTC4y6S5PDwY3CVZLnpaNRi83CIc3Emei9wb
DwgG71kUVxoPRizhi9498wVFFBYhCJUXxv26wEIOKnS/JqjQizfu4QGFmWBC
96BgwnWBitsHEq4PInRbBhHmAwjdQwII1wYPZgJL1wQPbgocdNsEDt4TNOju
DxqMAgaTeEG3Nl7w4bGCdFTOX771N+FjFGhbduI25bwlpmCkbjppetR55cgO
TPKIGjMCz2WzKshW5aW3f6NlkdqWBP2hK2ObABMtOxbHZGQjfkxWUgyYntOI
aWQHz57L4WVDE9wx4XL2PMTLI3z5mYsXG/J3eOkGIB6O0fw2AJpGaWqnHlWj
oWdBJK6glotbgyZiHyQ0gTW5Qd3LXVTTBeuzNsCMTgm0OMGYsmPqN/4VL1m0
P0sgGpporNANyrGP+tKYcKKqZTUXPjGf1s112i/en9d4sFsRcOiAwgGi0U+R
qe744wW39Ax2oRjoQ9AQTOoStarBbuHEMEPXEVO5+i6UXDshMzI0O2LaPoQF
qYKoiQSLoXbm477qC46q32HViMLCYLVOUTMm4plpxiH77cmFGEJofPdqPBGy
mSzgxKHsoXIDiFZ4xibAsOD2gmN1pTOJmsFl1+gXjlZUiYhaD6G/olM3sOLi
cvYRKHhmO9Y85hSx6sLWtKn4Lc5AUbp3yl08J5peIOZ1Z7ITTexQnN4A5w5j
QJBcp0ZJEEu9m6wCl4qphTT7nYtdkHbeR/yT4jeKd7xaQVRSlfT5Aauk/3xy
8vb4x9M/hrQF2im24YH4Slumi0/foE46b1dq7MThxccCTxXsxOs356ffn748
Rp9m3HjLbBOXegmLSh7lKdD2jDkCRZeRzM7kPKk1LuR0yqHX2hm6/1dzuslL
boGN186/hRuWGwgpTp5vrTv4I4dGAWZTYSByd5Jpp2wpLJv6HhaU9QdLjcRf
XMPTLPewfCkhmMRLcHd7kbdnNhBOguDKJJJZzcKl0yZCJOua96P4WFxEE1TL
UqCNp+b4Gck+YsSaumQff3FKD6D1hWOyTzmQRxOZcAQoMfgL2MZ4qprJsjOd
WLxP0LiJRtAxRwSHC5fuaNRwGnQXtaSGdNDS3NBfdK2iIVVFO2w+StBATbbI
PIzEG93fweTGyymivueHp3wBT5LmiU6Iz7LhLqPvsibON5nmVpkhOTMkHQlt
DI5MHDP9IQEzqyVIFHfTL3Y0OsS34eBy2kAyE6F4wavdE8XVbtkG/+VFhR0t
Gnt9JAKG88+gUnpRDWXDhxLNx+MNbChN9qOQPBf5m+vWZwqyxDaHFfLd4P27
Qn7Ucwu6tb2QkVxCWDEfy8bQ43DPugUGkhYfH/EO/AxM+ucWvqw+ubVbHCyy
pdpdQvAUHkGNnnOfFT2XRs65LSPn1kbNuS2j5jIRcyokbB05tylqzvWi5gIz
toFzG2Lm3L0xc5l4uYX3j5orWGW4iGXV6QCBgl4pc+uFAPsu00HxgTC9ORvZ
H/dAGY0eAMJz0jQemwLgoslumidRsN+tdXGCbbGDcfy7LwitaXY3dF7M4/B+
PoQSDx32yqaySOBgMLs7EQr1trDC0/hqsRCzqF8bvFBCkB7IZ1V9o1kkyEMd
GnWAKuElknw4JmYYiCY+LZ6ZFiziR3AgNcWdlHIvns7ZIEx2ziFbjLw3thWl
jOMDRBEzHiNv+Li4U1thPNVSM3uCcOfkDsgHJXpOkglDDCGI5+SHY8dzU6GV
CLjCJBrGZX0T07UMBsW5rnLWlhlyjXwUOJvY5Yp+4dxHxKC7m1X/OGDiKf6f
8e4AmONv1IJpOQUoD0ZZtxZQNiOEmTtKiEgm3zs367IRnI/2lgdStkI2yOuS
Yd+Ip7btYsxyjU/tLNULvWHFhzjTEtkQOrfp3uCxem5NHICCMXrDR4LVlYr2
I0ie8g5Ln963fs2aOS8TyJaLGzzYcOd7HlTRVYIU75nXVTlJdAzky9gCC1l2
Y4GgX6KG5JdHD9FOu8vGQE+OGDeO42mvJGzdGh5db2HkSuovGF8hLd3pO+I5
33U2gAXYy1VpkgyTu0h+8lEd3B3d8Os4HN7rwIxYqV77EHLB3ZCAlewUimst
G+jxwE3ILz3uOIqQDgh0wR8KUU7+caBfDfKHBw6VPkFHyfBciqrqZdUTQ89m
kUmmFZ0I3OB6fgGDmKT3mMREcGCL8Ng4OQtb8FmENIK6YW8OGrRgPyX0xl6D
dKfaWGm0Ss0xykIE2Eziy2/0QgkzzWbccK5DHjqA+rL7ZBNxUO26Y3bf2sy4
mm8eeTvXcCQQ4dtRUpzY5WHOTuKzcolopCusTTNjM5hJreFMWpLN6fIKzkHV
gWDZF7Mb4kmChuLWZBkpgZ+TZSSiK8VH6MMjMGUlyxuaN1RxTz5qgGUQDiDY
nEkSRCyaREPxuXyRsLlutimBU5BtYmKhi0KwIuIzh2eKgyDWJjXeB2Hh4mzd
h6JXfE2T+/xkM7NH6xPNvs4KbQrDWZne3GZQDLZO7dwDiOGSTSE7asie9P6m
FbyEUW0zYaeXK7xeWi+UWxnURfJnLHt2HOfAxji6NfGCCZEvyqbmLo7u5sPl
tWTm7D4uc7xY1rE0iXRc2zw2xri4WqAZA+13ces7dKg/lPjtsHgcGnSpenPT
Fgf48x3LE8sF2SbaXQ2I4sAI5kmSY2hQE3PYSWqii+huJVK3+Gy9G2oH5BMJ
DafwC/axBMcuW4pX4u5Vb7cJGEDdUJexr3Ccq4k2/Q6FihXoOoRMp9S+AGJA
++zsTgUkaFF8kiif4+KOPbaUvKXXnw/IOjWWCskzjh/la4+dmn+6qoh0Sh+x
b8IkQrganMuO7eC5CXLM7q021W8Bo/4ajJ9QqUr4Awk5Rkh2oR+8xuaSI0Du
8iF7M6NEbw1hUcsLUoxr16b+kiUQhSp2/qEmNKaT2NtWVgTjHdOAkSmdLriS
VtY8jdfZHl5n3sIQD4TcWOIXENcBvgJvkPvAPQqRZqfzm7KpSxQ6Pj6q/QcR
4qYLtPVz6GjIpeI7v4gQi9IwEJYU+/7F1xxfDJ0tbud7ZTuHnk7wQo4Yd4UK
goSpZBohXzUZlCir6IIs5NP6ctVojFv2NQ5+HXGw7ocPH3jYbGK6gGXHJFGO
qoWOJaOCnLBsScVPFmrSB2n6cZN1lj1dJdt44G0KHj1nbqxjXDe2QlOs8Bzs
j9z//l/up7lYvVVJMYGPRLK3FH9Icahjdokwl4yWwMXd7ODtM79TZ0h7N1/M
766REWZDenzUkNuwriLb0tT3ZfvPfj5/d/z6DHa7bGkVha4YK8X/bMKj8hHW
NkgeiBQkNKTJQ8ZwWT8in7o/Kk6PXx/j/oAKdYkWYQ0R55EcPj568pQOWxgT
y6T8eHNXDPoRmESGQtADDQLXaK75pGbsd+eKAbZkwrCcR9TkgTq4HD9EgbGu
uLhchgzmxnEIcvFKnvmebiA8RtftJV9HKWSZmolCxO1UXlKhmb0MePD67iNK
QIpdsi1Z+Y2DJ8hr6M1w5RTDtdgOj+NuKmNiknsJ5llfr66jueLzRxjXS7vZ
up1SZRgTYTzEaDsOLhCDt0TES4O4dzYLvHWGHN+8PXlN/MJ74zT2LhYlYjMU
0rvGANGhyA1ebcLozatQytExoGAgQJm0oEa3lVtLgtHUMVqy/1k9yTsHz2VB
WKybsbVSSF4AHzi9xIcSYWA0Z9WIKV7J5QfuiqlGGK6O9Ips6Gj+nOzRdvC4
eGLoHYJJ4OLC/0i4Go/U6UjDJYEbwm8PgfyWFQcFiJJjd0c0s1l5hzOXW03m
VGsiKt4Ct3B8/if8K8qyvQHtZr/o/zvIfHeY+e4xvn4APz0ujoonxdPiWfFV
8fwh37nf7v3K/3O/ZAb2kH+/uN/+yhb+/sfwqmzwNv2bjmGbfzCGvc3/0t97
n+0YfqzmlyC6JH3w/5xjrv5n9kkHCBVyAuf/x0GWKaCdjNfd5HIcPLXshqE7
KBhxInHk5or+Gjk/iS8XnFFF6ZULjrmYU0giT9C0rxe4YrB55DU1n0vM4gIj
D2a8PAYGLgDceI9O4EDkZSP+Scxm1ZKLmGJXWg9a0S1Ixu9YjNsRwrOOn122
Hflbj3kZXIw8x66pyuscAJxsJjdFy1LOKE0H+WeH2lHL2WvA5vFmmi+KS2ir
0ysLL0TWNF4d/wu+NF01LFkEHXUo6B2bGe1giUrI/HKAQ8PgCblo6Lr2yY/m
WqfUIA5T0ksAfTvD/Lw49dE76PQe5MXQq3QobhLS8CvNho12cVTsPPC6t2/z
nV9svPNHuyAhYYkaQ+BbEqBHysiNO8l7UhyNLtKffBNcNONFcTCiIVJThyOx
r9Gnx6MopIa+OxqFefD7tFgcZuS7RI2D9Y8ANsOCAK1GLDyiCgaUM71GyfGY
ZLcyE4QHuwWqEfkjhnJNN0bOIdkGIw/Q+UFpC5y1RB2GJTrlU2G/FW9HtexE
re/HSmkEn55sel0ii0hT4EQIq2TzCL0sE+SsYX8AagV08VaxHPJ3LnjwxaHp
G9mLIfvOq7tCoNf6WtM2l0t0af6wACZwjomB5sLa4oL6fCEpwdVc8y+3Fg/7
h2N4s+yKt2VzjTzvr9Xmr/v3S9LCG81pfOtDWosdMuHAidrdpoXPGcND591f
h0QgyTGnHQz780DmYpYib57Q/MO5uA98EuWbQdfEdjG1t6BanAW/AYkuVthJ
ZUVYufWnyYyPbIlrZR319EX55YLgZE0gnH44Q9Gm0kjJBEJkpHw2C2eZzLWt
CPFZXOLe48hmmIOnxQUaLXZQiuoU+pSgk4ac99bKFQ+Tk7RdGD+aqnYlNtz/
TCY1byAN2HEjzqdG+xX0MzXmGHgpEoa4g91heISTfdVWA5KD2pc+7fa71O7O
/d8Kvws7Qf4xsnGNq3rZfc0OejbVRhIdr9cX7ebFpbB19AiLpDg4UiPVmT4y
LpcSvsWlpGj0R6i7U6LsMVVkqJacyrZkLwtlXuRtY5q2rBUbxCaAocpsCuVo
WMb4WlQs36ldI4zOnIb2a0nFLdtDHBaKCSBlIIFOMPx6JvAQvDyJybJw/lZ4
uKQfKLStMCC49fKpUCvMkxO3FWMl2iLfM1ovflrKEZedFZuolQDScHOayric
jclX4iW9NX2g2MNpREHybdSkGoy91ES4KdVDGL7xEQJCMonoJC5s84JoWRoW
T5jVaNAVtcI72GgF0dAliLGx2wz1iqb6C8bmGxufKhEXZVu3ds6MHgPdK3PU
ZZrooY12UgV1v6OiE9KYgnWsmpXLNlR4Y/3Ab1e7GhOk4g2vQJAPBc4hdUp7
txRTSxb8WynyaDuKTAQOmYftBI2i/SAwSsaKCLRmrG1+3zRJMXLwVD1JOhv1
tcrc+xQN61HEV8ttcMS5kQyYuIUQz0kXPRV+Ww1qjQqf68OHmnn1/XSannV7
j+AU8Qwggnu2QYIq49vN35AMHmvHY/KCfDosqlATYscI63X45ImMaRjaSGUU
ZOeiV6H8IheSuDfgpign+aU1a8qz8jEKpQeQ8hgWYaiE6hhAHym2xf/Klnie
BFl5f+f7I4vSMPRPb/Pumm+LP+KSf1N0DYbJhtWLF45voIeuni6csNjtF8+q
Zfgvq5rpTxtVLHpoW9vtaMQwTCBAo1YwUpvcL/JRzXf8u10/I5NLj5sVCf2M
Paaick7iXysqF8U3RbzjLIsS5K8x7BE7Xs3L6wu4sjhU1rueCJwYD/NNPVlF
pDeyE5XZr23eFUm8WURB6YL1WYAl1D+qkFgWurDanpmPAA17DE0LyMvsJ2Kt
yTqJyJil94jUoZ0HEPtGQndFSurkMqvndJPGY0gtKYfqLUKR3VhDnXfzkBWE
vP+IZJRTuU50kH8UGgomIhqkOBiTfLt0JEw5Y8U788iyE8Rqv6mGjqVbuozw
TvQYs9JehsmNMO2QOHiD4VkiBrtIDJYUFnsUJAo0LDUus6QUauwgD8bdKmD1
r7gSbjnDRhJXS28Np45GxUuRCIP05SNV6CUOGBqz2JnOgXtXJzkjt4IY/LU4
JuvLq04fGFJdTh8PhZtQtQIRJrqAgejoxW1Q1Mr8jtofUl3ZRGwkWzbZ7VJx
WviIBqSbjXURiCPlkte5k5VjbzWtshPtUtOpfONLlHw0NVvSp7G5WdlcqhxG
wEvcsnsbXZ16Ul6qToYMDwhmbD4D1QxZD+3ryi4oABHpRcuiYx0V/2VTzNqD
/r9hU9xinq+BRoDLAnnghTmyn/HWgTF6HgwEO0oki7/OGNauw3b//v9kg+wL
VcUjDL0jgwhI8Qp9KZELfNlRwrGqoouQMJ6T0ihxWa9HincA/iZE4clgjRJW
7AxichrsbqOX6aUk7llgrVzug4Uhkk/1kb51rFgwwEmUCZ/eVWxsiLTS5QLj
5wiJnhLw8MqxAY3RlNcqhiSY7SRnRhIet1k3fn+QNBCWrfKrxmJkHNgSL3ax
I4WNKeaUhnxRGf9Yv38jV6qlx5KEYt9fl53q7Qo9kQ5YX2cDE4tVuznfO0kn
8+hqHBVv/G4O2fDAMjA+q4WAY926u/LGnSjkOd13ErgNdP92NLye4UX0/Jmh
At5+uJWhIWdn4KeUpre2M/xfrOPjQWhWMzGyekHLz4eaSaa9mis6K9mcEXkC
DYs+jZpFf5G2i1CNNNa8ouACk56u+OUIAbNn4ItTYtjWOJD57nArg0H/uweZ
EII0QrdYz5Ag/3oLorce9/XQG7+wbW/575f+W+uNGpve2rqvh3tTtzGNZM0i
p4QBpABgsUNA1JLFvBJCW8+8JEF8Z1bCzZ3waZTuBoLlrQLDJ8kz4SqT4ntw
ke9BMeojy4RiadvLqD8+12euG8bn75F4fN3CBcgzqbJQ9TT03JIIyxXvhqPg
i55lJRoXlTvyZqVMm8iPXW81+rPw7AKuMIE1saOOYWpZEcUaPT7CxSdabJ7b
yHl35TBelghI15satGmxuEQaZkY62EkEhUO0vkRqKALbxEl5kZZJBKTYhTi+
bI+BTIYe9Lkjd4552ONRavKbT6g8J9qb3bngoiQeX7c2Q4REAbGgVFRsJHY7
Ojs08cuGBuvWIOtr2ButLQwSjT9s9yHQg2hFgsTZ3jMnTQuEv8lSUs91HfQa
jt5VF73IXXb0mWveZ1TK4vVNJGZJnXj/jPNK3C/x1LjEiodls7BAwZ9MLjXm
IYQi4r+nS9lPmgP1zSDswu1YhAknsqUfdcZ8FLohBMRrTA1aElQFu8XsOMSA
suKcATFHUU6dFJExz2qqp7MwInfMlTTzFQQ2cYLSwK5KiV40kAYMhZsMQgLZ
2TAnUl+m6wjB5M6FrhVuSLGBQ9roQCHpJgP0yQ7m1eWiIySEATOChBNoSD6d
gb7sR1yP2IGxn5N9XcC0WWpr3e9ehuG/pPp25guV+cxXLPQp0jxF73FTiTy5
PhTf/9t8c//WPPlLkYyy2Dng623XywG/qk3VKnyrn9vm/fJKpveeXPTLZ7V5
3zgTuScMYCDZVcgBuKB3OQ/XduvtFIQj0IpEgYGOya6wmpJuFflb1poVMi4k
1pmCH8nc9pa7jqL+rYO5v7FbjMGfEq9fxCbm3n71tMBoPPRMbzgZD9TefR4o
Gk/qhYplm3TJ1bIRoSaFAmn+to9zDimvVZMAe7eADwbYhmFgqm06bYQeXCBa
EHAGDCaQcC9T/hIxaAVZyelgWonnuLJ81ssFikOpqIRa+gbxjpyG91KsgrY2
WXDGNmP3c+yepfZQdtWsALpLVj2QSTV3wTYB3xVoP3Zw4ICdR4nyvadbgs6c
LfbCTh3rJ8QFSjMEwDApoTB9b4dYBeECO/RogDvsUStBEfJl6Wlg0bjsG9w6
ul2jXWUuEmZhdtf4kZS0U2qmZAZZ6wjDCh9O4PHuenLpnbhD75WjSdxaZ347
3HVyfgiAkbLNJaMlE31F5s4Qf2LLDtwyhEK3CBuvZBKJjplWCWdLRgFk3BKQ
ZJB4SeQq9vaQJlRC53o+izZu3MF75z/+sV/N/J41GqGXhc+uW1/VaJtjIsKr
yzoCPSf2K3OPRgInU7FZ2LialXii5cXpE0yXovLFMr/HFAipqhbSE/HFsSgq
nQpHHs9CkQU0jxWosqEot60WOUwm6x4n4NUZlQduFu2alclZDkcFJRdjWOYp
l408ePJcip8voaUas9fHq070ORi51CwCedNEoHKysj2ZmJnNsacig4YDN5Sa
gAGTeGAru/UCWwfOvhtk6Fau6ZBF8xRr/FBKtvU9SCGN9fnlNg53GBs9e9F8
Tk2CpoMkUjWdr3GNzLtwWeIGDqFhSsPvqbQ+QzgivJ2errorGbkSsthLxWG4
Bk7G6WHtCK46MVa05aODKYeoZFAWnQUHisvQ0CQSWESrmHULFyBKtDyMBHJo
SjkHas44a/qqXvpQURSHMDK6X8kGsacNXBRbmAPbIxVjmMN/kZozBIAeajKV
0HpJsdFSUQZ1WAIxQaGFUdwmCtIVQ/yjcp1CT3pDUISWGJcu1gL3VwHEt4eQ
6REPCT4RPinUXzjrq6R6cussVpzH+k4RUqmIUn/cStSurbGHcl4lWIeY3B1X
YLZ16O8ZjbkqSETWio29YJze3dEDAZIbDy40xp3K3CP9Qt+M+rRuam00lVaL
X0gmIdfN9MgolJZWzgiLuTPWuxge0y6Ngt8gQcUHJFSFEdC8KZb4ruMMRFte
h3IP+8dOckJ9iQ/26tnsNafZawS4FdUDITswdcd63TDR1zEwEOR0x4dGmCf9
LHqgSek3Fi4KEE4Guhvr/p/nfefYgxRc0uvshwp30NeN/6r9bQ5O+NX9nZMH
8i2yhWNlC5vn+Ov6i3vaYnq/sr9twYitFeRz+0ssHcnhmfrE9TU01Xcftw/0
Hyv0YK+DTIy6FzMkx1xC3GPrw5arJ0YEqoooVxtHUvAZ9wBAGjKC8zwOtoT9
aFbAQOcLXxaBKjEpgHvAoCXkQeb5Cj0sJt91c2fNPTAOXqs6hQoc9bcnTY3b
YELJOMhPKQUiRis1CUEpYOY9k4WdIzSUPhh36lc/3OtWeH2H7AXCG/7dTGwl
/BqZVBexrS0ou2vsqJvOR/Df9oybke1wuzbe8tx6TGKbNpLTCCt2LCvGrQ6K
R/VSFpEXI7FH9q00G2yS65GQw+FmONMoaCA6zUJPCCtVd15EzREQZfGEo0rW
ltBWaWGX8WUYz/hKQIIjoPcdBhakp4dSZHCoLeKbAdLnN7JsfiKyN2lkyLxP
m0NZJ3ZLCI/SOHGjLTVlTSWmafZYkoiFFyplwh5Mskpa/B2QZAiwg+rnkkpF
ALdlcyd2v8AYfCJmrys82E2o6Hwe/WgC0GjoC0lgi+OUYmtR3WKNs2YSBaOh
Brf+srW5Xr8OZyS9Ybfj/dKOWd8NvF/5fczs0fhZFFl2fx+/N4a+qFt89Z5b
Zy6MNFlVmzcb+UNzHD9Zshf+gooZvdSzojmkilTdJndLTi71EUUEp9rTjcSl
SEjYtBFo8wtXgaoLfAPEA+CbiV1i+Op/m3Vfhx87CqwKn/UOCN/Q3vy3y+5r
nJvOO8gDemf750NyTohxiu9Bjx4mZBne/X5WXrZMjRFnoG1MukBLrOdDf4Nk
Kr2JcFgjGXnxC3/yA9wu0ql3I8VTxcuCjGb/2kzH1eTfmFSpWqrFGp1wzvuK
04sTIiQj2jfEna/qy6s91n+BjRU7+J/9XV/NJrcZatHy9jx4Rywypo83707/
cPp6iNnsb4/PfxgWr0/+fP7zD2/eDosf37w8/vHnt+9Ovh8WVEro+PzNq9OX
Px//4Q/vTv6AlK7AO3VT2F40AHQfdGEK5wMVH+skaYCngunirQsfu0WDCTuc
+y6vd1wgg1GxNaLBKaTt/SYA1Hi/kXopmPSbXcCDzQuo1dXOBYDzppIlPA0w
Ox4Jdu7d5y46xV14GVEGZGWw54Y8K/3fEaR3H69oHj8sWJMf/uF2w3+LsRp+
+zNj72IbnYuQ0TubE2UGG01yKV3ADFw0Q1/h3cx9X8txdxElui0pMUeIQyJP
KjGlQ03WNvQzTBfFJTHp+37ppwsM/8mu/ePt1t6HF4uYuHEPfEsu+JtDMmO0
gmTdu12EpDtDWX74yIgbGThOJRJD8ywD8e5Xcw5M4RqHujgkJVGeWqv1lNJA
fcpA84ibOorMDSCdRRmZmcdG7iVDoGAZKAlyyzwmWo435VKsFrLSsOcUrPWN
OtIym3IvI9VzKZWt6Uzyjz7MMJJXMtmmTl3D/iECQguS3F9niAd2iHwsiIqF
VHxqYSRuyHBdP2Bh42iZuSMmOClVUQ/JgoSaEngnJZIKmxcJOWR9yqw5Hzxz
j3afIR3BRfVRd+HdQDe+yFHdpKJTK1V6q4xq+E1R7sq1Cdebp+kDzBd4oT8w
DFlolbXy6JLkLSuYquh3UsWiy8Y8dMDD5YYM+7LtoLsJG7EgcFxCJdr3Pro9
7a2cypLkXV/y3mKT8drAGvzCTn0OK3olSvXW/35xv4gQ9cve5/yjFK59EeUQ
A35vW8uWxsSYsntSYoYEjuOz7GAlZh/z4x7SmWLQSyUPetmjQJGP4Pn+0adP
me4OdW6vX7559fbHExC1HtwrCODGX8WFHJJ+Hu9h2s0vReSapDP6C8q1j3hp
fpYToYHuTOBEAC2l+X9T/MTuZUlZiUSDODqZGhRufLGrV709Rod8jPSXv905
EmUTJZgFBYxOqZRfUBmBWOg0tRVVUvaaXPK9tGMRrhDwX5S74nfRs6zZRV95
A1/J6rx+T7vyjWfDvWbiaLXItqnOZZeebN2t+ISfSaseBfY/54QfFDsTXDQ0
LEx25UQQ7NbZyfmLIvy2bgSSuRze+h8/nbx+efKC/YjVRIM2sCBpKIKVdVBT
qaqmROyBTH98WsoW9+Bn2ANGA1W1UCg5WsVwejK7N8tEG9r9GwY0C5/97a1u
NBl0vSXfq+eHrBld2uVNiEXMU5R5IB8XQxBeAuAlgTTZEAk7kRFGSe5IiYF7
ofcNtNjXrogxwhJ8MFL+tmVKvG/ElMa7XumwPOkx8KQX4ZfP40m//mK3t/rO
ag46c9vtWvOsLYko8agJ3kTJaKO+IJXcgVExUarqnq/+6e4x3q2rVvli683w
hULgrQlmlf54fvrzyZ9Pz3/+7vTspd2UI9oU78aZ36/6+bDY0qFMvMYq24dT
tgN2goesRQzKJCcmrclEOU01OmCua3L8l9cLW/oTzlZzx6WAJHpjXoG6ebHA
vARXhjAWLu9Ka/kSrXETX7tSXU/AEGeLOzqt/XXGs+MYJ4zWGYSPZ8+fHtE6
b78719WE3qh2jUpuN+UJbYr57W90VrbZ5eN+1SSuGWpKeTL4ZFRj2x8zWxsx
EMCkukT4OzQpU90SkhbYPuzSGpgPWnuCS8M2aQemu31rnNmHp7tcAe5F/6kH
7gi2wo/8uk3BdnhfEB2FL4F9dSZszaq7xXU9pgW4hAWQOb15Z6f+LEw9/J5w
iCx3COP6aqROsZ6GLAo94hwGSE3iK0gzHKhI6tPlJfqMOg162jGX4ZFexn1z
uSDsRZB/afBv2l3aFzaQ7W70sLsW25Hr9r7L9mGbKMNdNLSR26k11p+WR93K
+ur1ahS3EfnqhcGrXO0tGsOsp2yjy0qiEAIsk1ZJ4ph4jtoiLSLAVZaK7Y3f
J2KmWHv2isPH8J+ce9Fn/8LLe+uimVLPBBWslbZfykhg+IzRBuobZ2Hlx1Jb
HEmdqEeA0FgxZ5HON7hFmVP4Ybs4CKtsTP5xm/bmtx2tzVpfL1diHBaPZGcg
7gsiu9iitWbUZOnfED0luQ6aYrwukExlaFrYiHDqmHAi6dhElzwwtOS6nFRx
JWP3wNiSEB9Csf+OfVEfP6bRFJ+kdBlnzJQzQZ9pCP3rAzxDNN8RLdXt/AuM
3sX8jEk5Q0UhZD37kmR5bLl+ZCxsqNgWoXtfmMjpwtCGat2N3xYa5eYXbt1W
waMueXRj+FxnxcJ1NAzD3feWSf/0pnbr1pG7px9ci/zDywzo3gVVq+2GpHeJ
7pq4DIcO98BLl1auH2pFcxNcFcn9HFhMYTGmUrNUqupVvbc+Ii1DngTPSp0+
LsISdRUXfeWC2hkNwgUNIr84dGz8bNMDwgEN3uGeRhbT4aCcMF/+Ok6JQgHQ
Vmzc0YrnfGjnoSD6rhbzXoti6Q+wkzlTseUPXe5+31tXPxzjuQmHpTalaLMF
5jHsDX01/aAEE71M8QjZRXP5CvFDiaHilqiCLzIDTUFKaQRY0XaXO6ETkm0F
b87baOBu3cDTuPJh/qwzfo4fqwk23lnHF7Q0cfXvK4aRpOP5/YNTlYghk6ua
VcF4QrLmFjIhVwhdyCUdKzk8HxLO2fY0HiqfgxWEugyZePgh1ISoGLsv69tb
tsnCSflaKbCbToKTTwJ+di/95H1VLcsZ8BDOQMFR+uRMDt+7w9owexclIUzi
43v0fOELYlJJWQ8eUk85A0Uq6tHCUHXaUwY3HRa9ai/8rM+fd5rNojpfB39X
c1oFsq5hapICphhUdvge2ETdYGfHjiMfiBAUkrxDcEFtPDOKWw0OQS5PXjx1
HAZsQlJI4XIZFbkWetZ8NNAB9yPbdUfXtuSHLgmiEuMjOLkjg9FeTv6yatlp
R/WSsfo5sTqK00A09dxKUk2/1TxCWSMY93j4zp1qSVnFKcjMMiBfdVe0IU29
mNRjU5Jo7dQJyCJb2MfHMy0URi+GqqU7nIoTuiCeeNmDKdrWSeoTNVBJPb2T
Akfxs0a24WwvYnnFtEQpoWoaipyYS1khwbLD5CLONcTjEVdJGs/IRVFfg0qI
q4js0ZTDlJV4WK2i3IBdpAX/X1az6MEoWb8UJ7IVk4odCfwZJFn6ijEVvkPX
qY9oLkzew18DLzPV5NZTHGhzJJ7jznCdtXaJsPoXVD6NZQ4kE1SfkNooz5eB
f5Gf8q7xdd9QjiNl/kIjK0qpA1lrXnFEGq9CgGp4cC0zzmywcxGdPFBU6EOD
2NmCQCkJd0VS65pMNSu4o5oaWdeNAOkgNrGvVy5vYtrnUOwZdTkvP31CZ5fp
T5Ayzu6uL7DydvG6jMFgyR6ghr3Curq2cHf1fg7eZW48qY7Iw7J9f/x43V7y
OQVGgd7j4DHmZyIs0bgBbQJRoqAZ28Dj8ESSJJobA+eLJk0chWfMhXhCt+Gk
N4YreATvwgauS9vKk/DY96AfwpVz1uHF8woucSRBHQ63Mm2v7ctPw8sv4epd
667kl8f4iH99zSkzlIgGk4gFbEP/onVJaW5FKWDjWpDROJearsKyQ1hN9eVU
EsBCt4JqLTQIbIIsnphIR5GY1h/H4zzjceKN3C7Gtc8kh4uBLbJTTM4BRa1Z
LBv8OX7P2O7k8i19KsHOT3OdzG5IoY7QzOK2xDJSpEe99WO0aLT3n3EKZ+4d
87VnPHuytG/iAezx/iU98X3ieYBzG6lyX8+VX7C17Qor+AUVIr3fX4O0eXY3
H181izlc1BP/rLq3vy0n/rDmqrhSqEfm2Zw//5f1lVrjFdPr5s9//jMS4AXJ
/OqOpgYo0YO5Pl829C0pvcAPMKsDJB+6UDIc6+92Y+BZH1Sm+bWCa5DdmLeY
rp+LK8pszCYocHz2KDOGDNQIPftEnv3X70KcxJ6cCcxOPnx2AGzveEnVWz8U
x/8mfTz1fYTqmDlUdHz2mTz7TkuWG2QHpNp3Wlrql3VQ1z2actnL5++WGl6V
M3HEGLMe8iTz7KFvF/Zhccln+E/VbLb3fo7p0OFNG+9iaeNVzRg4977Uo5Q0
WJSXs/eKGe2T3pvCUja+ainndM7lpCRQbMNIUzp6KK1+lfToIzQ29olvPpc3
/ekJb2yYJ+38ftKn2GC+J/NlQiUHPSrRgLc1O8Bv9nKO1x8Xf8Ef7j0dFl8N
i+fsooCub6v4PoWVLHApyUyPd+0cy0/PQUZxl9VcYGbED8k6qOJgWcdgSAfT
9Ct/RTu3QWA7+5wj3F+azw8ryx5xmEYqIa/p1x95YWrQBgquBPmh2wMr8gZo
9AxVel6DImYB97/7kksOy+uWCWx+9yTUSfbvBjLaYl+QmFhk/jvar8Bm2Xb2
2oezvVXvGFk905g8u+bHE3QzYX1OUgzPrlbdBDnopr3WNafL+7tqL5RTvJ9O
POuN+31XocfmnneV+Rrp7x3VSLynY8t+CSY4KffzknHq1r6rDNj0+xLkc45k
gpEvZqtOirL03lUm/GZFzgx8etUgJts9/yx95ggPCRJtK0bHymfqG+icSV1e
zhdilGXbK3lEi6Jn0tI6kuiGmYesBbLmcLtc2Z5KGmoDQRckJhsNGOFn6cYi
3qmsU2IlyAJbFD5mgvMv44Tm2AtqBiLgLyYzV1EErNkySkQXNo63zmpWUs33
8C/RFf6xODwofssdSvzABu/sOjvm4YG6ZU0FsEz1r148w8dHSa6OIGMpRLYm
9rSZvJU27zMWgMTYmi3GYS+Dbcp8dPclnCFMZ9+cygBuSH/oGKita13wpSqf
6ku29Vm7UJNqpLz7QKXID8vhUwawcoIv6G3AWEXoas3N3SMGYXp9tnXYcucv
fC5Wu7ISa/+tpMoK05zT5E3ZmTRqbJ5kFU1DEtOIk90ZUNDlO8+m9JkoV1Za
KH3tFPFHaa25EPG6+axLatSmCIBpWbbCYzifQguVtgby/b7mXRRrxrClRAoK
bUh9IO7dQjBDPMkPo57Ft+WfiGLu5huyxDRgL7M64WDACD5rbXjY/RXy0RCb
hun6yWw0Up/Gom5uOK4Efx17ejpyzWKw7b7yPi2ffnyG1ZizW7M2R9SnhMIx
q9BjpimOOBXCndk8ZVt/JU+xEkYM37D4Iv4Y2pCLO2cTkzCrlao9oxc0dKRu
XFlJfFPuNMa2o/AYbp+O472TZr+33Hpch9nFxkivF/uXNH1MVIBS/X2E6H1/
QLb3tKtEawBNOTIDp+J2JFYFeOnSehTT6PDQ8CVh2pdYy5wKEe4Cwz7Os75i
hytNmPHRJtsh7w5lwxwbvieUcWvMpru4PxEor90WJxChFFjFrDVxtysqbJOD
AWDoz0y4G8XetGPUinGHG20+AooQ1i55uWv6z6Gr0mXAM3C90fSKX/sAkgXL
gTQanTnFNQSd3BKAxYTuqKCWAOTD6lalSE7isB5X2nvXSzBtQwBRVJ4giSRi
INMPHz4E3FKPR3MLW1d8wd1/gfZ7DMf3fEYQTdMgLop6VaAhiZygW56YQQ/U
I6kGYuzgbjzDeAK4ism9hDuAacwgTbZxwG3BYDS45bGazmVEDRJ2QkhafJXt
Mh8lvQ8ryfE3Pp9bMYlpdxj4hOlejrs8byfWNyFE0crKy9QeHLwRGcTNCNLG
4I0jEoSUeYq4oZYHoSgxGRu/TMG5GsVDAtZU4t7YKiKBpvDtzv4Q49hhNQ93
3U5IgdGcRUmCxCo1mRgDXFY17XyURDD0+stXWy5slGeSxI71MkHw64aiUTgc
IwPI6qIwux5QDkU38EXmlaFrUHaCOgTbSg4WUUA48w7jumw6HQJess6piZDE
QC+qqxIubOCEVGUQJGXeNrLoPdl/+uTTJyp3RFgDu4XGq0VXG7LX8lIwsCRI
r/MJruSqLudBKgpJGGlUcI0xMJMkEu+L1u9ZWHaKMJLbjyrU2/smCsKXWLzQ
nt5mDoliI4SYTJWDJm2jJsYtNItsaF5EOSjDdQkocFyOf/yRqJMmLCA86TR7
7kDf2+hzx4elrrYYH5N7u3ZYJs++QDm11phtrGoYZSQqHEJIFJZiJYROFOhz
6LdyJkeHbjkKXaIUH7Sm+1QOxrzqNMejYiUqgD9L+u/OEm65IMbOqmmHobmU
ZkDFJoFo+qXoqvCjz8iUJjhBQXLDFfY0YL+X405SipZy2xOxcQQaJ+xjOecp
4q6qaC0Lo+u1U4+q0dAUCMDcb8wW3aUcHxWppQtKRLuNFhu9hWZdSfSnUfML
/bXU0kymIXT/Hn7Wrgr3GfrtyW4oj7rXYp8qPKaEKv/BaNGfiKJLIhZwmMdj
Pw8z2up6qcXAoxGOMc6SsfySPO7M0g6L5ayksgZhKCSOKACgvMu2CXnWDk+f
9kMbZfmruZWVv6Iyu5F3Wc3EHmyPC5xbvv60h/l5J7QbKcxw4WdSZhhSpM+C
KNazkBJRWjONkpQTQPfMZOBm6N23nrsL/VHYIGdvGlE/3hnqPSLGXCNhz/Jz
H2217Dh/pL3M2jH5ory0fu2i6wXWbuc4aY+asJIsilNs7MqnYXU+/wEjRnaF
AlHoYbMl3cfx/dofOqL/UxCyC+dz0Vg+yO8le2qPnjmMTrbSFEz5UtnX+sIp
gaBdIOj8ThU+HxmXoVlQ6QKE/+Dux9YoL7pRGPt+JFmywBSfYs3Dg9HslS3i
aJBqZ9JKI4kTW1LrYjkXBqqlBOSTili4C87nFFQUskzyGi9lOnIUeIO79eMj
TdvmOfkf7hd8o9IGptKjMxjqprSvhc7CNzYmv7te8rvEGm+d/J4qj0U0u+g4
RBl+RooBGeZPgpo14YhKDw+Zk+tqMwux9lKcE+4C8ArPsTkeK+LmRlMKsh8F
WvYHLItu80hC8mJh3F0MAq3VjPxZMOsuq6qdwCJJ5gm9QlM2M9gLM7hPvLX1
bqABmZ6G3NMLUwxwXUcARjtSfuurMgERsNu+bkN6gI9b8+Jumy5hkMj8Dk3q
BgQ8XrW5t2KZZkhkgZZlax80cO3/gQOv29AVIhKimFbxvcZ9Gqt1hoTIe+F3
2sIVa0cZktphkd9OiYMcdbqKvqDOOho+35wVO4cO7zkriY7xZ5+NyUVRakFZ
JbaAB7zECju+sKVMkp1he/E+ci5lWOXbsk31zGg1eT1pV9utDieq0EFWL9ZT
QXQQlCZ2eNnNq/gE/7jbp5gsufDL62lm/dYOZcZR+iAN78+cNCjJttdwh7Sr
C+hSlUrtVeZo7seSM4tg0gNGqkOT3d0g0/tI9suUv60fuHU8iIyG2t+d5EYR
mRNn8BfYLBCXdEc4DMsTl8IeZiawyy2kpVcFnpuBJ3Dx+ablSY1DlraIb8W6
zdlqX7iFdHOy+yJ4qfH2CAU8fI+iRc8ZTeqWd1CX2YsymyjLmPL8QRJSi+vv
IWmYYxjvOoqBep0wmyvMrRYbSMgboUyAzq3mrspiyOsZUZAphVKiBqrxRuuY
viqL+S2hXparGWN/zs2kOZ7Wpwi1XNdo17Md2e4+V8/LTAmP9pwmwkbBxDYN
MvLsLU5OFdoLFo2c7AHTe/wQPr+GzfusX+b1bZ7ZFzvle1h2ehhvhBMY9GBX
r4DzhBguqlj0CQbIe7Y61jQ5m8sYv4JynVvdiFnJJmuxZEGr7a9iTOwJrgwZ
Ij6U404y29j/0m6ahNecZDCCWmKX0mdksnS5iSnt9ml4rby6lizTi7LHQLch
SxllQpt5snyNpo7Z7G7dmheMXN0i5a7GV2ZAVxiL3XYu4DCIZ53dmx0Md57N
v7VpwlqdfFK3OB3Rbf3eGmAnvS4zY0RNyfk6WeLCq6+XsIYspV409QQ9KJQp
SOmRvNVGLk9hrYxR+SIiNl9tzK2YzufxFup1BKRnBOjjfNtczRMWrPTmdK4a
jpdkorqNEj0z2iKF5krpLUoQRvqCA4KuIeiMikxYmWxukimp1z2SJ2VyTkVY
j0fOnmLYlfH7ioG8utjNZZVMGf2GDnqBNbh/C/yI2hTIGqumRU81L9RssXi/
WhaLpUCCeVHOHKn0tjLyA+9dd9UPhnsnPqVzJFFMqJnhoUL9fF45sX1NYyyz
mt1p7HQbL9CE/gFUalGdowalBSKTBmMMb/pK/drjSmfLSQEzKdrKRrLebgad
jTu0FdmcD8Bg8YJxezyn04bL3hYFBcrdP9a8HcLvv0sbT0dMhdfCsPUkRONx
VqC7r8c+xaGJjalXiZorFZKhJ42z+PgIgeCYitPfHojFR9hqczF16XAXRgTY
0fKJu5iB+r7lMM8AqOdSQL0PeA49nl5QMukSNOB6HBiE9rOoCPb6mBLRWnqQ
cmIVHGqpUpRm4J2xIKdIjTxgNugMZW2FjsdQBOS6czTe4Ikj4HZpRSqRTKum
0ag2r2ugy8ehSDO8Z+gi3Hhxhl8tTpE9dgvXCypqbZwFLdzxGVeGJFL8+HF5
BZLOYVdXF7DA77k4JC7l+iH4QbNOluyENX06M0wfWhU/TrEMmdvURz3SJigy
xI536mbMsLuFxk1q5Zz1c2BslKi4p1xWElAXB2a1iTTJLxLPWN+HbdUzGTL2
wMtwHkRqcBPCb1Aga70tlJNnUQitnYkD9/R1c73wr8LqsZJeD9GS9r4tDqiJ
Q0EuyiFHIKkka18ka08FMWlFtjyEEe2TOG+W3q1det9Psakft6kfTYDFlnSZ
TWFfDNDGa/HXbQnvqPs1W1Ic7nIouusfU5IMQDJGbQvuFeD8yGJYhVwwoSnP
NxieHx8F7ElnQqNFdkuqmKMIlw8OCwEFfqMYQcSf8hhoc42s6C3tbu2y4jQZ
gviDtZUVNrrDqUXaUMoSM/7vWN+0wDzZTqjcRVbNW5D+1psMXpdYSwR1KW3Q
mQZNEJ6y+wxGaTQe+7qFm7cIrHMaTY9mkJ0riRxwhegMR0WWHFYixnXsBwHC
VeZ3NFLiW18qS+GvMOED1hM7xFyVyuPZwph+70OEYNUkuiqFMf34SMBApcwS
hvQdC7IkF6Pm+CPiBb6MiClmhkGfhFWHbAxGNfBvw1aqoGpglAYjD7zLB2cF
6gNxgnbhpMwlPXoTEDlrKhdHsfoSGcVBjRTujxZj5OEzklEpvDDjo/fgnhgT
DbSmtBxs8ctVgwj1SA2xssjqWQiFDHZPdROq/UD7EL3fXROmH+wYR+KaCr7e
XWnro6nyACpOt/JG0pbhfVAp9ACl0iSSEdIrqAdbNe6SAaegZWECw+yEhvFh
NfHWtCQiLRMdjXWPV8vLptTyI3QWcIssV+jRpDUmxGdJlBy6U9pYw8215Hq6
A57DID9E8L0c88leXLlreBc9W1WpTqJfSaAj0iei+2uN1PMLCqjFcAPC9VNL
ADcUgWAUO2Xr4gIRsEGzcolhlj0rGotBymH7MutfcdGxWGUrGkl5W4YIeBTj
g91HDAhk60Gc7whtsezlylZmQapAmPUMQzFvZO8clpvfmyJ7x12F2cN9ZEpl
E9VSSEnauAZq9Gx6GthH97oBRQYWGqB4YfEeBJesiIeiWhgJwIUYPzmekvyM
diXDGKXSfBnYrhSZjyQEsSKRMKTbb1thjDIpBORn4HrjFNlBwiEygX/zFH8B
Voyq10kEVB7YuJ7S9duhISSPDujyFQzug1R+RKPhDMMfNC3r46M4uTBNlZPg
cszPYaGOSZjsj3yg6H2FWmFQMcckaOLGsWe900do3G472lBTXd7kG2PxtTsJ
RUfHM0W6cRQE4plRAzY9mRobMuOX4VCIsHkRrQb08te85rTSpr4XcRFeLCS4
FI+I0dm+JzS13gpSu9zvJ4+SeadnxfhUQqg+iwlmyYaC6H6XospQuxRGXs51
Sbh97+EgAKywkNip66EYu1ya5TDwLgXVmpiU1GGcj8o18UIaKbAkgYIL/pS1
SHI7PkDEkS/Bh4bQ5omrcb5Ymw3KdKeV4ly+L4FRvBBgsonEu0KzKQiR88wu
giHyEjMXrEOETqXv6VRMldh1HMbDyEBTLIpWhaQKun56ZITnf3nVoLA62LRg
AymwhM+cv4wcED7Ahp8cppbh48lf9t6dfrsHp8Q8WmEWDm8UKCmu8VnVLPXB
6idDIQAoenmC2MwLog7EixKjrCQQ/bgYY2/5AHCQLzpxsiG1X5fNez6PNYNd
MPxgFNeKIBaijnHoJ3CfLpVQowgrAe6WR/p9FMW3AbFOvrTl4ycVgghNXHD1
SZhf3Zn49KFqYap9cEVixbVlg+emcdAhZkvrrZ0UEIWA6IcL2OK+4ysmdzuT
Ne0RbTUgRsMw9VAb3iEBxczQsnhMhrNFwHCO8t3kOCjfKnqsnqwgcbtqYQo8
BnMwTbhl9tB7KgoMKQu5JXpwfMKrWXmxaPiOmauPj3HS4gxERkHjc+mTBmOT
Dm5kE69+guxZU+V0B8qXsbRv9x4lprW+a7S6EzdqPT4XSyWamIUZraR9TjzP
jWdOILyh9ugG2C/RplRvMtEAAUqNrt9V9cK5PQ3AiGAB1s5LQjCB8BDiFOPt
Luk2lkvqaP/5U3YGr5aIGTurrxlZVLJqQmbPV0+fHHFmD7SBbHkXD9KG8UDr
hAhlLo8wGBoswxC4IgEisG/d30cfVD7qBVrfBoz+vn4yULNaIkKz0A6eYzjV
Pc2su1a3G3NWdnBOHVYZCjTVb/tgcnJikak5HiO9YuGekdznFQbLJ1UQ5HAR
0twWR8vmoHv/2tbDPffZrpYD0wnLDzYMixlsBprMsFcDmvkA5hoR91+PtfaH
+tdhrLJhN4JsFwe8K95dtJPeUo5DcgnZe5w6E3C6aT/deni9/s6SQ+4w9cYJ
7qbqfTH87KxsQKcBCViNv6E3mbLG+MdMSNfDiEma7F9cgHyyQ4KDbqrIWtHK
+KSuoYkFbjHeJD8el25BG7PkLUY1DEd+Q0fJXgcaOA4pMGcs7EX7nnLtlQEM
5N12WzEbAUhExb/XIQ/J7aftj0BGvFtoho2xsA5F3mTXiyaXOANluK4TUjJB
wkPjHy/ZeLH0OPhOc/PC8gRMxAcuy/1MLY+9SBDtLnW0MaYNYkSZEYW8ZkGV
wVrhHNgJAmzeXSeNoK6KhidSAzf3zfYdGimexNA9DUrjugy0Ow3Ll20Jjfs1
TQAwNy4sI8LzWap9wXUb6pa0FuUGRSZ2KeljGk9jvoPtPMfDPF6JG/RhPAc8
PSOv9SE7ffBIOklM/8hdipuPlWGiLtPZyABPlRKYi3+HsBcBC8JFqbQSOQ1N
bGHGZksnUC8VMewxwPT0utuDt8mWizUNyDXkA2m9cQQzZEEvrNhDDhxz2eXk
QhohOsCIq/hR8YC8pyGDhsq3J970tFSY9Sr1j1a4ueK0nN+5kJtrrTM022U9
FsvU4PVivnfyoYPBkfgwYMMBhtPgnD99cppIexFZtFL0ocxAueAABuxN0OBJ
8+RA3yU8c9mUy6tfQ0qGjKhIEKEmCy7ltoS17yzqs5iUPegrmhky8+oJUuNy
Sbv/KTr3G8ImiL17qiTTWzEGRR8r1o895CxbS3zcnNZXERsAUTcWpQrEDWzd
vi3SkY8G1juELSIYDoW6Yi3npF1sy82fFTv3AeTuciKflW3m6+VBap+AGWjI
XAhKIcHClGpdAgICvWYM2ajuUZi9LQkmLjfipBhTXVKemC9LklRls2QmivlE
Xc0Y1FqJ2uvL+OBnv7LdlV9dn0mDfNTshajo+grQKo1d34rxQZpqrwqmZqqf
ii5ZEnmkho8gAqVFe8jFUolnMN15uWNM0/4X8nQzLElx+vbmqTdVbaBF1+O0
ryh8TfP/T5C7tb64Kwxz76gwCZGj7MHxni66vDzdl3abZRie1TuJr9VxLJrA
JwLMFqNf8cuhMYp7d8G/PFynuNq01gATY2zQcDO0rZdm5Mmw47lbwuNA2ek5
tahFqofGAovdUqmKNL58rQPDqyKLsHPfVgy5gN5pjpOVocsOkxW2EUjSntOD
bOG+whCQ3NzX3xKIFYyY5ZppuA0YeiSSyISbnpbNHjVPkDnXy3KMmfR0XxFL
3fMIfgROheNgqynFVZIHSKtmoWulasmv4dgIXglM4dqIrgU6uygjx4KLsptQ
4jI5mP2q5nIHWDqnRutmOjiYT4PRDB4YgxY0BG0w3yqN4b/QssWMBk28mGWJ
/HAIOQJ9cxOkYw/oJkMkogjZNSMQcHEUvn8TJ4IrUlxjDaQLDFlO3wbW/T27
EnDClPdk+iXRcHWJOqd6TeDEOdYtLio2pKG/ZWo5EwVucLDU8fenX57Bf8il
JN8Jye26MAqu7kPcNHgbBXMyRAjRlT+hMwRNDosz+u+rtz+/Ozl++cPP6J1m
rxF89dPr8CXdTkwqRWZDiCd97cEwKYXCXTR1NWVBsdaif0TiU4nOhpfNr7ij
x7NQZexO6JLlzKCXpcLm0D9sPITkr7uQo+r8A2QZaNgMlyxVT6BlI6xIOMQV
9jxXOA5Hixyy4ah9km0wqNhDuH55CzhhYNUYp7E5pOsA18TKxNYPnkfILy8M
UhUlfQxDBhThMyCQJn4YtF2DUN9tNxDfsC6CPkYfBgiBZh4C4j5mT7IzQvFA
2TUd2gEnn0kdrYVaxfw29yr5jdD0eWabeFEc29pXGPYWXSTqI9ErQ/p3Vigo
E2y1jx+to/cTdeoPk3CBFzAMXoxnyMot5IDEA5e9gBLH5r42dvD6u25qzqnv
DsNVlno0igFfpw4DJWk2WBj1303clO4HMAvfRByPSgORVRhgxr0hMQ5SAE0l
5BFFUWDa5ACN0IN0SQZUoMVX9kBF4ZbCUyqUnWsEtZisxhXvwxgh+URdm9Zf
tvAfCimyLSBsZysnl8KN9opzVIv2ynZPvXEvfAKdHohhxviuFmcNlEnB9eYF
LGIbrCKxAiasBRfd1y51st5X5YRdp6HsJRW9Q8l3ygzGPxIBRPSrALP0vrPw
NtOEldoBT12EILnG49BdrVoCepJ5X4vP3Iah0xk3juRyPF40GruWsDoidC/W
IN/9ni5c0IZ09U0uhuTC4chVOr4gbE60cU9XSM9AW/Cgj9RwGyI1oOf5rKnb
O9iAD3oo/YLgi2UzWUcNXltNYRXVhybvG9kyQ0D1fFVpfIKY6tFPfh7N38qh
JDnlg1cxtDFOaLmi4BVXUfgBmtzT2G0iDMpzs1Aq+cLAVFKiJZ1K4k/QjCfl
ASngu56bfGquMdxrhb2jcPlS3sOsHptEE5AKON4jLSMcmr2Gsd9UXLL3Tksh
sn2R3IynWgq8IaBARVqKPVKMpWZMLnF/jpXLUE9zzVR413AvqomKs0h9yhHW
TWdkBirp7TzSaXUbLD0UUc2YbHC20FuEx9g8gpe301rxCv2V4Czz+b8SC+SJ
mqlkAhdUNLPbZaTOi+qyns/llNIpopfiHHJSaIaFTy/mfDpkTHjoqbrpNeEt
reYYurrC8zFBO4JFpTLpocjR76oOsy1XU5CiSDynF/DuJt0e/dkwqpn3ve4V
LRmt4rZY5pTACt7ols8GRj/Oe3UsZeB6NgfEnPecuQcGRXwC9fRpNBLHCmN/
gmNHEdEiIrnEqjcBSueIWCxDTtJP49vfDTFQCa052SodQFPNUNjFKgC8QqLh
VGb71O8aylh3C2RIGoXDhocyU0Y7MjViEHcQr8tWo0I5TVHITA4WcRu0WVxU
YgkH0vL5GBrETNlozG1lO3ysPNnLCZwPz9LvsTuKOsI/BBq3+j3d2Gqvj/Kg
SBstzTHHQQDBvpnmqM6ZAWVtxkMWHz2iVgZyn1gYhebMpNxdxH6TkShfZeYA
325ZK3kHN3FXWC8CW4XripoEZUBBqvBJYM4LDArGhtSelXqfUtqwMrEvrCog
7OGO8zMjLnvOkoSRI2BT1osWiBchEfS7niqcWu6EOREKl4FgjESp3gj5rs4D
R1ugsRhHLY1QeeEwtJOB5fKy07AIT6zfM9erb53osTZQOaPROsNk/ZGguPV2
pZYuvtZwx6I8Ka4oPZ1x7Gyt3tdZdYP17LR0iFdsJbPjrKZ0r9kkTbTkVAsq
o+6TF5mT2l5xElnXH8i7jDFgkbtFWZB2OPqz7+VA3nx9IXQaTIqz6rIc36Et
8ygAskla/TCl5ZBpfnPkVnM4zSg2a05xeV3P7hgcTYCITYHiELUkipAFGc9S
oCCLqQepF9KjGOeTAPm35gj2K6p48drFwS/DlEz990hVa+SUnVvxfrO+LtWm
6TBGkMzBKl5zWXI25M/uOMeehhP4GsYX3NSTVYxeHzc0EialFeOYR4lie3gE
iq3NfgdeNtlbTCkgVEeyc7J4t6um3rk1+JdYdD5ddX5QMR+JicND6zkTaa7c
YksBxPjzTs2dUcYoplxQBD2GeSLGJrGCPvA9Lo4K4uvodpexWUqfhn2LFfTC
HeuFlSQCW6Ua3i2ZV1AORW3ckac264JyQtYuyS7pBJ0z2MoBpCvb04P4ouk/
2zv5bFYs0Gbj5KxMFdzEyu7T6gBGoOnNGD0i4oRTQRMN4DpZR/ZHNDdIBQCF
45kwTxSWTG2FaGerijpWRYNGKzWgZHJ36T1nkiFif7Bbw2MoL5Sbsi+waBXh
Sqyxxtv1GZSp5jswLsWMka0vGetxP0MJBW6KcfFy0SAc4VwwWGixjB5pmSAM
eQ3JZuRIGI/2QUYsuM64pwEuSKQErIlHPY+0QpNy4VOHaGxpnNPjQ5I8/mR1
PXrQW3H0VIgYsEb7JE7IRklWIAVX/xp3EZ9M9SfWqxhSP7Q/wqscrrWymZHD
+SFSmcvJ56zT+uVU8uotJWfIPHgt63m4fYLeT/ZJ521/sfeBGQHxUTlrbZD0
k71BGyI//PS+hw8Ov9rddiuN8JbfTsd0/Cu201k9lle0V5Rqmug97EToLygo
bjlHlfpq0/26xyxow3wfaxqC671+/8tPlD1goMpEZIGXHDcRC2k13oIREbx6
eXx2vvfHt695Lk+fHFBYt3794xkLFc8ODp7h91QNzz/97OjxIYgaxKRpgD4T
EONwMMWDxGEXXLQUnyNRawZ6JJEkuWgpJiajctMGM2zsPkf5eufV2z34313r
/Da7or451XTZbu8SuCh/JUexJ/4A9YY3n8CULpJvOSqY5XTjl+7Z5TkxjFm2
82tgfAC9/NaovoIZoLhFaa3TMZKtVBxN1tsQBSfxnsHrZjPKnlx/cefk3lLL
dATm7FWiODjM5y9Ja05aC7cnXZEIIjmS3P93VM8KX3wbYqtjx31LLmu+h/FB
Nl+WRXSJFrVN2gnY1CEW231OLHYyFGejsStbsHdDNHYRRWM7jcbmTsZX1fh9
qMqXyCRkhmrRI42HN+CNJJJZyHTpXfqitUBPeX2GYisXCw6e1joScEusa+i3
62xqvy0OH0fsOq5dKfiV6yQfJ0roKBPnnoRcrSvLbQLcNWdIRJfOBtPhSkRl
C72aldarU5N6KMZX2+AB5mgmui7Jlr+onHFRGeNPbCPNm0hZIecT5ywxxSBw
octraJaILzigvYAqEPsihCRWbQ2vvItvGu+TVKS+sIJo6CZzIgOqSUhOGsq6
eX5xcieIr8CQ9vyBWV+hWureqUbSK1jt1DVP9wlzcrqztdgWxZbY/Peo0FU2
HDcZTegzsLuwDRJLIkntlcmTWXetr9EhzYVmLMSMMdJGlriAV9t3L+JFls03
NqfKCo/xyRv4s+biszYQYCZfpsuYJ2+vKvrKFmVsooqfuxum0eOBHpqJ7UiS
cjcfVxkZLkm9Zvsnmiq9cO7diG6NG5FL74gvsedKNHoWvp9Xsdr8drC5CNk9
JrjizeEVO7J8oxSD+XeJG5UWWhiZT42J9LVwtn0C9UN3XEvNF6eSk6tWCFIv
R4XCp5Anj6IUgFwLJlRyVOEVQrZQgutaUgHvCBgjDB1k9XlP0yx2qtHliKw1
q1ADnYD/yOwYYCN3jf8pICHOFpcYdScJMEO/uzKS8KAU+xTLsAIQLN4jj75t
6q4j3x17K+vuC77KfsPN/IZOO3znGOlP2kK4AxQ5eXm4CkqwYfhqqkRLlzUH
IgwZWAiW7gtin1fqz98r924FuuUee5yuXM+9i0xZrG/DoJbaeHUmuL4TIBMP
9TbmvbkCz8RY+WQElZYCX8Sq7kUjlYwMEMNU8/r3VBJyWAkcU3hSfxruqYJ2
3hLbldtkp2p3EadXgpgFwFUlYbl5BZ5VKy175YDj9pKKyuh8o8gnZ+Iv+fDy
bUdoqvASLSluI8csLoaZGyOEHvB9RAdGhsshs3gULoi5oz9SNTupdhiHrTIg
1mlxC4eIiYqiWcbMHykiURe+GHALAyA2NWtwxfRu3VaNim9XYo5jFs1dXIrD
AY85UYWD89y1X+NDpaBvSeAxGgBn9XvgtCvMmy8pQEKC0rAefPt72ACg+Tf/
7LBlECNuqPAfB6KTLHErcoWJS5/XY8T7Pn31Zlec801Foe8OiBnj2MkxYmNO
MVsC7wLsc8Rd0p59QFQfupQkctgVPAUdJrCXKWVszGbi3onNB5zCoBaeINbV
DOwtqrwIRQchh+lKE0Wi+pSj3Dnv+QvTmpxkONCn2Bvg+s/4o6+JJwEMOJgs
py4jpykFqss2IUEcsimLtn45ArM6Piv2FS1FvVQjx0dxm/d7JY4kiQ4tDSAG
8G9nxbZFjoQJaI32bPdpVo+W8iJdPrGdo4CdDNg0pnXlEP7IFwTLz9ttayJs
KgVyAqpvVoQAJLgaxKPPpJ8cRAAZ2XQgdhppqM49QTqjdCxI3GYwfJC8lTYT
WKbLIeEutXqZNEaF03+DeW+nCzEz8gLZjOYY/+dSsyCD/GP9DCxLNQ9l1HTu
nKDOlsvTTuybG5dP4g+2OLO9AmK5Q5t5aLtTW2SPLQs1yDwvLpfAz6SkrkSD
qHyWEU2twqfpkZmSKr1Ca3QjFirxszmXq2WCHrC5RKaLSmT262NyXUQmw37V
u9aDLnAqXa+iX1wzLuRBtuKDN45nXhLHc4nSelg4JCgjiQwc5jV9I125z9D0
fRAUR5dz2D+aROhw15MJCqV3MQ/bjQq7qLNUpeshJQB5NWGoyDe14M0Ac/dY
5il3/xX33VFQdzNQ6Xn1xSoBPnWpqRQkUoVVKgUSAhB2H7IT253YLLh7fBhd
/jBmz+LadcCNFQYwVK9j5kx6QFjy1ogHXJ3fJgmfw31lqMq5N5GcaLEbkPhp
La+rqksuoTEoSFVTlwKWbegi0upkOzeWGj3t4oSwq2y9P+JJpiQmlcs8jQN1
Gb85XH9o5pWMW+FpjHiFAM5F0S8fVnnX7dAaDHvLE1Xb89TmOwQB07yS1EPD
dzdVMvGAVKZMRQzi5dJ6LKYzDha6ovSRfK0uGnxYTeNo2Hhg16rrVs3xurVj
JXy4Pd/zES0JJPhfmSNtcfbXg5L7CLvN9/EGKdrgNacTO00tWBsvYsXJj+JB
XYiMXzOyfijCaMuePUJCvuftd8EjJB3xfRsnp6cBOluKQGHJXV9zSQNMN5NU
znl/z5T2txQD1+IIb01Z2f3jWQZU19z8zM8PmGpQP5xRP8g0IVkBvbV4ylFx
NPQjwewJ6KtxJjre7jFWM8LWL7qE+rzUxi7qZ88fM4x5rvuvHtA9QoMn/Zub
Iul81zv4TcFrUvJuqrvWSqFbk8PGLblHylhDCLG1N5/trIbZyuPy543EgXn7
u1NoQaeUS5HjgHVjrw9vS7gXFWDMOyLIdONRG6RRhNu1ON6EUXNH3m92oAaD
caylG9ftoondGbvmqoIx1WNkP4nhmKZ/QSU3vdJSolHYBJsC+aArtu2aKARV
hnlOukXJ+LwTTtkbgshxi+Yp6A9OkVsLReQzS3ljA4wOTOXDklAmelnsV/BM
h4+g2bwR4I1S9SCPRqBxw6KF458e0G4odEvT/3LRZDcqCt6AnurFJPW/Gdwf
txbfx3jWNnrh3drJv/S4PCZvtIfe6jhfiFfyDKEqtllNPBzZFcU+sBVshNuo
qI12s9PF+1ncYM0YBnZWgrjdm5kzU1PZU+ZXHNvc7HAu9TGmcA1mj6unS3yE
cpv7huhwjKI+aNwDGvCzM1/fGEMqIYT9Pus/TKEryjScL0yyuWQ7ebj25dLX
kyIBdD5xBBOxvq/c0ARCGqP4YU8pt+MVwS5kMCKm7TWTAJlWKE0SNVJQgjSy
SOySGqQTvGBZ/A7iV8HBpYHZzMycP5Ff8oH88t2bn85P9kB0fHdy9kOwjSzm
Jv6lRmikan5GRmzC3/Y4RYzQwoulMty9lGqQCDesUR7ydCCoN8VPfpI+6N6O
k1ocrIH9O+A7fNjD/RO1KkL909AqUoV7Kzv6/L1AnvUZ24AFT+rmWpHQFZ6C
dmL7lY+o033myhdh5Z0dGi9+Shf3bIbTzSj+BpsRgSy6dNktFsuZLvumA5AX
RO7bhvgAuM/ZBjtU97AzsGbZ3VbLfuwDNfhu8LCmppRmdqqy/gG7zcX7hHb1
bpeDkR8Ae+oettZrSN4NPGCZXuUDwf55WaF16OOjMf4vM/BHIgZwcCY94IFV
yotWS3bl6wX4IFcLBEoimwt+wwDQybbxxQINxiXjLrLvF8UKwoChy5vUSsRI
Mrf7Z4LGyoRwoeYLvZxHKEGK4FlPGU1HEnaj7eqiQhMgMTrK51VRXmM9Zdnj
+pP90lIwdwMyWHh4qgW62XHWZdEvzwX8hdCnub6nxAkEI76aujgQQ7iNQZXD
sB0OoRA80LQUoSaYscU09FS3CukUgcQhu0MrIvrzmsUMh5DxI3qD4U65qzpZ
S6DyGgDrx+v1Ss+Fdjh4GF1bBvkilWM9you+xxizOxe7AUSrXfdizN9zuGII
5zZhzIQAjCZU2WutdH7wGiJzzy711OrQgg0VzZCD3SSjMci4zZ36maKNOS8Z
Jv6q/EDY26/91N7qlN4xtSjf9gMCqgdJm4+SzMdrgxJ/BY9EJaZktb6nIGmQ
cUJ2V4RWI0OMqJZXY4C3xkCTYxBR6woL31DA43X5gbcBA+KDdRxVU0XpWoUE
u995zKhvXLfCWqsJ5mpUycmE2nuQHeAD/xP+FWXZ3lxSZe7f7m3+91t66peC
slQOBZ5ht0j+/fKgtjjl5YAb+5Vt8ZZH675z5Ie5bVu4KOgHeRQ2JCMGmXNo
rQs3mCTZXlHZ4tu5x/3DDSTGUBrLbHpGlE9vI3m69GCsEzKPo8EVZzA0HBm7
uyhomXNHnu/vP44TUoNOZwldCDlIPzkZ0SzOpApMQuxZa2fuHipzZ2buAyMH
BGX9nelezejbbyQnKqitSDfRsNW/zSa+o1D8/7QdrFvC35InzB0jsqa3/IJs
JaF2ChgrfHXXRJb4fBkPVU0FzUj60JgCZx1tfoXj4qNbrbK7n2DCKptyH+8I
fvv/BMUUE45SToESBbQ0CYjGqigBSc0RAPF/Es29oZG8jAb5kgZ536Jsf4qd
HQYVBaxaxID04jzIiJp8spitaAw+t0DqFUYoc/6NT5927Tr1BGFFCDd7/tL3
9s73lp1qs5oTOD3jA2gpKDkM19X1okGCJ8RZXRPHdOGV4MwekhT+1yTnNzzC
dzpCcUIJzHGsVJHr+93JyzevXp28/u7kO1GfomkTHGdl0Ns6Akm+XiKjfdOO
a0HRskX5dj5+nLbXBDpeSTycJGHUAohL4AxNtdc1dzykhMf0GYepIcnDX09o
pd959MasuwqHLndXDPMMgYT53Nr2QVqF2lSHmhebFCbyzVbjFdd1VKRkmCwV
DEMsH1R3ad2yelCKR8KRgW23WBZmdUGtjdcXkaq6ekZgTi7mZuxMvmFPCqij
lGim3O0Yb4RjHeZZVzady207sIPvj388O2ELrtQX7p+478i8QYL0o3CG1QdW
1o1WJ/ZILTAjQoDyMRo9yiEKwBWSkPC2xuyEkorNSG2wOWG4IaD7bFbNomW5
FSQXjUcSVYz328ZyUMDIxZ0B2GmrqCUjl7tSK0b7Emy5pojzdxTfomfbvOHW
vCGgb1E9PKsQRMN3m/q0jQQebOtnMZIHkh3Zk3DiuXeGFnbIrkniEXHuW1ML
PC4hFtdvkNEJVZJD1xjopt5SRjcvpZ32iwRqjhBsVEMJc5x0FWZKs9Qa4XFv
aAjCeqKinMWDa53xLFLtusXsJrjaQgflXJCBKPmbsVqvKmtUIsCiMjH4KQf0
lyjXL9+j9aJKFy4qmPrTkq7OdVUcTIioOh9pXzhztWKglimCkkd7Zyxr1EDP
ht6rFA9XmyM0GW05Oh5zLhVh/SESTP5+jqivMnvXLx7CpXXuxHurPlr9UWvE
YPzKELEI5peudzpNXHJE9iShmSo+ajW4JVy4pJYJxRS0KrDlsPj1INetS8/J
JEDM2pExtGzAk7StORP6YySJaCd9kV5iDSEgUGnQ5USqF84dcELvpmot0gNF
dV17mCvdJozY670oKylv7uSqMVPBKnhZnQawby+peY1/M+eMStDiUnOMLcWG
SNY7hd0tOPIUa/kyEjMvP0YfedxWGMNRWq0K3hWjPWbZHvqQ0IghhZI1Zp6Z
cnA6aRhn5qQR58vaAQmUCV4vZzDeyZ0iNe4oeWmkov7eP4b4Np0jAVZUVSvT
WY/P8KCpBRooIRC7x6M0iNOGuaWhkXWOc7cFtnQPg8xcO8RpqBVYvWEhYZW9
F7ZjmJQ031AjJkCoDZfBqNg5FezpJ/tPn4A+TZ4SvCaHxoeFDVxU3S1mruCe
gNRPZat7Ue20/HMWQHoPhVVWj7oJ8Rro8g6MxLxqUJbEitRHo4I0NIRm2Exe
8+oWQ3wlylqOqNXilbByVWj55biqnDmkTF8Rkq8amYlsGTqtiomXjtkm+hXi
DcVdyf6AGVh1ojavFVZY/J87P4rMIZOtJdWpVxyCrOUckmJAReO1DO3BUG0V
p+yQAo5WqFGIozS3kbN36+kEoV9EXCa1A9HfMSCI6n9Dly9lcJlzzXk3rE4b
X8Zm9k9uQUSrBlWC12KDb8vda5gbad10XzpQio9h/y6S5lH59aXJmOXKO8lt
Ttd9SVmnlGuMhm8M97omUxJIOUBFOT1yiKvGt4S3hJD0BNdEUtuPwsst9xDf
WKsp9NSJ9uqmVLBa6C0qAN6vCinseB6r6sMNdRbXmL8o8ekGelb8216BQlDT
Gq3Q3SsgqdVowiPp+8uyFcXAP7yhCBLNy/V7ohTRePnwIVK66AaYLEKxG6qN
5whgQELipbEA2SF+Q+YHfI2jGF0uCYbWZwI5LxuTQmTbYsWFZYIudI5r60tO
BiodFtMVIcHoSFQNlUJ/voqpJEtIuCFtPO50NirPH4u8//77s1e7HMYkKdoU
UQVK+WrcUVY3NgwPxQUWolhExbnEWx8kU8dYf3TBkAlHUM7UYAAtwP03hotk
dhdXbkDRmNxUswWeKb5P0tRr6zoOr05X8zEbn9GVLOSBwsxVjXAkXjHVWw66
vqk5wVvrvlDcmvFzB8u2Hgc4iE0walco7lJ0WTYWh1ZWnYDS5BQ6xksA5Ve2
BHQtC8Hf0Ux8YaMT1AFDDXXes2ttmcwdpAm3nz7touCYvI7v4J7xk7RK+KDT
whsmaV5LhxU7jBBD1kRKuke+ZC1jKq/zNKFTuSveVV1z95JzRFFys19TsB0K
D+mX7smo8JGS7mn44J6Nin+uqiVs5E3Fv36VfCPxhR3njiczSgKOGAxE9byg
4ztYHtmczDSSRkyuIHQvhUEccSkCeydQ18Q6JJHUNDqJiPQL3B817gNjBSBp
4Ky13n1kb+ZfPn1yVMaNPklS6oA+DJjh86cBi0Esqc5YqdiVoXh0mwxFYL9S
6IIrQhVSAci/lBm+oJGbkr8S+bDkIAmvZvI3VngEqioOsNYM8o9grmt/mgfz
KBpMQX49HGUtgcXj/veLpSuI7kQCYZOfEbyYjAugw5xR2RVP8VTNyjsUFF3x
zHwiGiy+Sr5pXPF8RFKUJ+WD/fiLxh3ARN+WFF19Pl760VCK8wHMDuOPLBfH
e36x6kgOPoBZnjfl+D28yYM/OBrFIcfu4En8TbLbmY1TdhpgoaZV2WmxEOV8
MXsN1c6QOQvmVOBWdNkA9+Ez1wmYFoNrnAPbu2wWq6VvPjMmNkPwiYgPBNJK
UXzDTRQHL8IWDOPdGKabY987fJHd82G0WcNk6xi/RBDTtbzlju0/0+SuJuHL
Drg+v+pFSQrULccp68KzqIzyOB9HNzinI86mgviqik683xV6oRm4nWSd7Cz1
vpJnk3ahf7zeaTeAj7ydkTvI1x7Cwq88S72aGI0LNfflrIwh8cnYz3WmnGq2
3b1cRs3T3EGBZpRy5u1BrrXXJEyFRoTNYBMtFXZqfco/cs32ikRBELdu6upW
5alwFBgGESspbxjUjgCGNkKnXBo1vcL1UHDEOC8QO8gCcJq88mM9f8+TepOy
6QhZJ1luydqdL1ddayxk1CuhHNNjWAOUu0HQbWHSF+ZycjBgbRnBOqnsho5D
Fp6vCB1lujgx8OCbDUsnBTWokgc8ERgDjNlFPEfuLeyUcQ+ZZHBu0XNDGWJw
Zaw/eukVq/UPKXXuD8ph/J1SJA49WcYduoO+xBsHJKwNO/aCzDgvcjfYkGKF
MneY/JDlVvzTRpbFo8FZZFrHm9MZwdGPL4SpWsMC48GTWivQBejtW7IZExS3
xJsngZEKQhD/KiYhipzskeEK7W4X6qBhmRtBiYrEQwh0yjGYYpoLcZiXsFnG
8uNhA/9f9t68uY0jyxf9Pz9FXTjeMzkBsklqV88SFEVZbGvhkLTdc2/ccBSB
IlkWgEJXFUTBar/P/s6aebIWAKRlj2emO+LekYmqrFxOnv38DnnZcXGxTSFM
DxV6fGPgw6EDZm6cesFLTwTZq6oWge/AS11bhsR565sW8LQCfAR7FoXZd70e
AKuwGQRtO3lHL7rjoR2qsGXfvBtktzV8N2owmzCwd14UV1pXHr+065hWTMZo
IyCso7puyjNpPKI6ltmc3FyTJTuzdcm4YOrORCTCt7ny500+5JQ9yNg11Acw
bEybT47DbM9d331qXCVtDN+4Y6UuHY+hMx1BepDGm69DNXYpm11T5ZzJnRLy
LcAQn85194voA1eeXrxHkSAB+LS4n6DgHzbOlO0D87divttcYUPqG+xp/NHE
XSQJC8z20LMaBxLFb15SM9eC3SfoQpPFzMAIb5+P3MJorzHFS15iY4c1z2Ii
ecHqKApf1dNBQGCGs8aZd54TbzTpZ8xc0M8aMl6jLWFVKtfUHOrjjOEFGS8L
IcuPqCBvyX9l4z9h1rf+xzZTttK51kumvLNcMonbUAhdcAQP3qGpDtWqVJhF
GpUzf/xHkv092jGyU2X8R9jKS6Rxc4t5ZfjKreE2maTH7+Hx7R/sSeM09CV9
z93fOF/24uy7Y+TDlHPhxc1Bp7gBg6xL2lwoR7IG8wp9y1S2JE0Oar0V3MLT
8HJ6nESWcbA3uBoWEXe+k+Qhw5nsbfpjl/ihV+JbHnBr6RxFgV/7HKFdNQuB
6TUtBo4wfzc7mwfP+/SJntNZyeSMzpcQA+5ywnQfEBO2QBoEkU1czxBExPjy
mZy58JlzufG0bll2z7ofPm8qS73rja6HJLXw/dcoDsGJ+7hrWz7E50DDzPQK
+Rk9as2o3GhKYFHlDCErRDfReJNypcTuWg9bVeCZ5EOWzfmlSA9RpsotbQ1S
/Vgh8vil1tg/cmVtxXo435vgw+KXxJGlZuLaHTMKOfAW6xdK2DG0kdq93r/U
0Jc3eKHnvNTsMo1/hSGxHa3QhMovuvQ/CaNpIq9JhEGEDHprXtoUQsNXksH6
yQ+CZUSvtDmtmTIuxsQvPOW3XDwySw2YNPUdRjpKZAvwmpaU6Si2/8IeLek3
VttavyZ0hupqQNkjSA/joYIdajotjDqTJN8vJoi2SvVoqP74AMfnz//GzecP
xKnBTW2rFu/BhFPkPekE81wN3QLfvTg6VaRoAtzYgGZ7XIXDhh8wpts+/2Kv
9BWFtYdnkxUD3ERIjgdH5SXNQ0sMk7rEkT455zamFe5CZEd8XM+8WaForHnN
1ZthiAwvXo2vMRVnBOSiKd8pGVNHsdrAUVY0KXxivGm9Bk+bdATr3ZAMT/95
tGrltpBpYmsjvOcrxLLjaeAbJiwoLLz3ReajNLF0GfRYYjW+JQ6iPNjgvQoL
s3gJBQU3W4h7yLLoBYaMXCN2Demj6KUgpoSmT+9wB1Y4eMmOi3y89KcVHnT6
fV1AIL5LJgTQqx7pE6uUVmalrqnxaXKo4XpUwwQjaiIEvNPIoxSZHLwawXiA
h2P3rjp0eUjD0MOFhXcoHZ2tuyIUTbKv2355M1WLb2scLVm7eVbZiv3XQdlq
HHdrNj2K1oP2fPo1rfixlXYI3ThVo3iDOZ7BCSztBFiCg4jvnBb3R1+NVSh8
YYt8jWCJbTcVqj5dat2msD68KtzUt0Mr3lECS60Q6CoykXeExHTHZLsMh8Wi
bHm0DpKq6ziG3X4qTDJbTFWkNc6DPsT9OBhQB72YPHXvu/BeBj9JgnnsBo1Z
pQtEWv9aJtSx9+9EoKEbgF8zBQ1bVZY16pHIppeqAmlE0Jt+Jl5acmlsYHmr
gsCWe0OKaDOMKmR/deW9+aTRNfuGeW5MeKtiMCMwTRD234hgqdXibef2ZpKb
ZwOcbc8lSLZ1XxOPJarf6hTgSFezKobRFjAxLh1TpAMzCqfpDMiFQb4VzbNy
0Qx9P8DGzMAoIfiAjPsIvz15UbktzYE6YGyybAkXfZsMBRONr203YCELQkKQ
Lgc4se6pSRlXZ/CDIO0ajn9v96Ffn/89M35Z9eeHD1C+EC7ntABNHSFsrzHL
hYN7eqI7V5xjE4X4SFyxb7d05JHR829GAvFEL9MqcoOyX0cArqS5s0sX15Kj
hDU2K2iAwaJ5jmky4sZ6ToFWdFb8kWmGSlNeTRthOfY3GT+lZOz7xsy4jcz6
Hw2T2IH+I/LQH3t0/V3qR8s3lM4gKKdNNz2toBUvpHhBh/1GjgPh1SEwxvEH
r5OKPcHJuS5Vg4R01XiafDD298z+rrNzEb/xFkmnCcLuMqULUZFdFu+OyZ6l
ahgRr8nWWwo/0Xq4ppJ/OQi/FHO6Wy4k83TRP11V33i48wkaxVPYlkQTH+w8
RZ2N8nv49lBUUrJ8ZilGJkKDcUozrRfABMJ0TPh22yeADvoVbfKiLaqBAPLR
pkyoBKBewwZ96hgrseQ1hotII/DcMTiMURcFV+FuJsTidMvrGwJTlP9+qsfp
5KAJr66r9zlwPWX4BoZH8pYEcpKrxb6uVsTRZfWCrHSZXWE+qJlmrTVnpqGV
qbrT72pzygreqq7ydp2MguJLUA+RQFKOEGq7vwvSHWv86tqUAxFA7NvIicNS
RWVDXvggVsnrwtckJxwPC9My8HVq58jZ61Jh4Zl0qloqJRLi8ONs/ssvXgWt
ZCt0Js6uYA39yO1vRIY527wZleeGO9IhvLnspph0KnbHOUrRiQHGp3zPZVRN
omvVwL8Q5vPE8AJUyPTOqT72xtY/mEUUpQSxEZkDXw6hqobu7xwTH2s+b30C
xgqrOLFvBJ28Rwx06HDNknRTLuvXfhDWzkGbaOmbrryYmxjdl101KsNtdwjd
zRXkFq3xwfOknQqxcp36dPNgW4FxO1ldEzLtuRqGsyj98W4Ll3q5zeL/rcMm
gz2/MoqBFp+Suy5UoPUR1Ep72OqbBAPeTWr4pQf+S53RpQ3HSm59nn68GHvS
D6ObvFJt+oLXPKoFwYYrKMD7PkueUm5IFKtE6/d/fdyNYQ9QXSLhOGPblgNp
JmVZfYO/Eyl7Sr4H62LX8mY0fbDbH8Ncc2HkM3citkdNtvIr6W0F02lQWVC/
vzyVfVEiS383bvmr2GU4fSQwiXYefEGalSHXcMI+vyOOFVn33a/3fL9D6D/u
pty+TIF7k20Xh2Tabcb7KRUASUCJlt7C/QeLeYR48vVNQQji+uAcPSFIfnX4
StGQKz4Bz1fuxtoj0zoDnmwEw35HAt7dhIJ/S+L9dawwptwvchk6iPHJ5sT4
I5zVb8Jf70+onoT6tibmwkTN9M5aim5SM721jqI7qJnzmr4QRa+M4v2PpGge
0hL004igO6yqdZSp1lR3Gm7sRQTrNk7xDD5ZBlWVXMxGjDdA0VJ8kfGIiepM
Kmxc9h/PMmQhqjJJLS9+Exm/kp5gxauOPxyPNgNg39vnr2woLTq/Z8/bZY0a
pus6y0P1fYsrSWF/cFNaA2mjiH7T2Dom9p4nrWSru06h1aNis0/vP2+UZt73
+/Eod5vEwfOecOldJ9EI9XZPQilxM5qUhPiGiTAUcydkCmxoqg/Fgomj5Ctf
9jqhY37WWGTHkw2/14Pn3fl8d93dOOFQW6Fw1qttKtKdHYrWMuFCZLXIU/T1
U/BO3P3YAGinuLrSTjPUy5VnEwlvmwppcsla+ZAUB6Bovl9CEL40Uq/YtzV6
oa+wE4HgmeFGebSmC2Qkn3jmJ43sEXRyemEfmO4dp61uYS7WFz7fzGm9/6VI
eq5F4OH3EeA+xSxpaATxyco7tDRqhM6UKFTP+V8ho3CHceE0uGnvxUOgm9E8
PPrj99h1tOtWHEvQM+qcE4lNxLfxtfopmzVxHhqGVhBNQmAlucNpQNMjBZMR
9YacV1hgSU03zh9HASR1LTktfKlFiCPhPKQBrH6FlEb+k2iZnRiCXRYVX/K4
xEoIGK7m11U0FuWThpOl/9x/8oxgIPi7Vzr0yeG7Q3+Hu/eLpgO0HHRhjr7Q
XQybr3ikOMr5f7z71eQtekiUoXhHAu5xYUU0+Iho8Mejsx9P5GR+D/KT4jzK
hAz0oGSiDVlLPrqZwMgUrRfsoXe/ZYikTSKip4Yt3IBIDvvWxbsbOH0PkVCN
8O9MI6Hq73408tjTyOHoQ3Y/Cvm68jslE7DIFo09lcwBCb+Lxu/lbGPYxrvS
wFm2mLUDD/7l//6nw6NvY2RD8x78tpne+KTBwAX8a+MtEkUlukmopuh8mSlz
qFGxz0Mx/1FLvbnMslm8t01UvKTKQ0HbRbzHspeaKxPtoykE4Nn2voCbnpjd
JeAcfG8mKQfmMGCLYKiNt/tpY7tfYb78l93qxqYiMtaC4/D5qGvfVC+UrdAk
Ii6nIw2Bt4WGf3Ui+2j2UGrksGd9MRurcIYnd2hb8LVDAd+bF5hY5buKNtbk
tdPQZYeLADHTUXLlmpnpcjIIIZ2NV4dq4iOJsq9XaDjPiPNqrnOvrg+raaj7
qp9Eua5K4v7Qfk3gN+KgGyVcdzl7GjFI7z7qNJGk73i5mCHAWyNAvue3iomg
MYS89IW2kSYbbaVWZWW+IpZrErlz59ViwjXUEWcJXQ9ioiJcVQZJkrcolVnF
gs1mVgysmUl5/SIy8c6G8SYH2Ht4+3R4r7N0nJXHZXnnU/KngNthUomTGxpS
sTXpMDfilQcHnpzeVtf3mNKs++rF4pR1OUw22szRcvDguYBkaq7yYtrpt+zw
ArT6VAjmNX6tF+ybSDxgVWLzKzZgfb0Iq5SjYor/jpbs4Y4bX/DjVtmEx+Vc
NVuVzcR03kygpktG8IC2m4mdtfe+R75Y3T1JgW3k/knCStgqcRQ0XPa2INYj
RuAu1lyW1F7pjJtl8epKAuYgpC1SJxaTzFfPRotUeA4+QHQEkFKpkLqYnyaf
svB9iHl2WygCTJRr++v8ZwZSIk70ZSh0oQSrA5uS4FZW+9AzmTX59j1pFUmy
ng/xJ6SqcOZz1VsXR6aLZWG0wyL9m6irDLk69PjkrO42sJZ9+cSajCfBKoH5
NjjgQ0ygqvMr4Dbf348HdvZs1KklA01JJ3YzSAx++Gas51GY4JebWm7VWQWS
ImDUkfSLhv2sKUcBto9eaSxks8k/Zi/5Ifq377MA3+PXcze5gnfbQ7B3vpvD
D/eaA2sicbP65iZuNo2nZhpdlLZOsqlbiuciYVLdlg3mEk0GVNwIL887t5PE
zsv1iDXvL4hB90jV0ugBjKQzCbwPlfAGRKfHAmN0TtHU8a9hIoxaTOnO2gWS
QMERf65m7myROm3htOaQe6BK7GrCmdGgOBbUsD6dxKFtRLqV+lfqO8GAIoJx
JM06FoyQHRcsgn2FUxPDJfdgLOQGCo+68KiUEcMsX4k/X7DGQzwaJPQiNC8S
8Dss9DAxRtuAoWEvEfal/t60FZ1FmeYiNLGdYWajDxl3rMWoJoJQLerrAtVI
Ngdl6jgTznXyE9lShTk0IuCxxYdhB8VaIdVkonLALVZEeLnyLVFGGnoIngqD
0MreIFPT2XGfFQI029YGrF1p9OaU8XXJ3oJf1auMfjZK6++YLnfTkNJmIhTu
+xNTD9fx00k7ItWOkYaMr2UkvrZsyWfw9xlj7VNlVplpi4JUYz9RgRGD99e+
SS/HP6S/GRKxw4JEDpN3zATPCBuBSNqmL5uJei8gAgM9BMt6uSiZklBHIeSo
y4LBuf3ouLNKRZYKUd+itfioFmEUN66ykl5eMce7ykq5d2j1tRp89NUD7vaQ
Ad179H5QJ+JpgW19ERy7h7s4mdIwmU8WVftJv+imd6Yw7UUCdi5aSsusZiXd
b/JY2ReV0mMxHHlcSAmkdBkwVfHLLTABpg8pjyDlnUr4i6gJjEcPDL2eBEuL
8R8tgQu0tWF2C2pQHDAidYgQFMmohLDzuDyI/KB9yJXvuE69m8STSuLrgq75
gO85g/wO5KYPQIrEzIJLSXo5Azm6eLslUouJ9LOs9pUQX1fuYzFKLxHvZcm+
hgnSBS47G4GNS+PROIilmVG7iqvFRBjkbVGOK9f35WqSX9/UlC2iOygtZ8Uf
n87nE8FTTl2DiLzbgz/FjXQocksNJaRfQS4zhL85/baWhZHK3KKcoTeVTEyM
uh96pPmYOykw8g+sLlms/DySjqmewdDlbGAh91nMkSNJYCWSbkk04VYrK1Nc
xann11kd9aQKndtaEpFLCzmkTkn12Mh79jXOqq598x+c3m0aUQ7/AH90QWzj
QdPG6zGOMulvwU/3S2aH196GdEDAKJ0zVil8sqNVm17uPDCdudTBRgL0h45u
LcFkl8iPr+9W65obeKWSZpc2BEJoVUKN6bWLk/AZtIUj3B4swZtlSqiH2lKw
m1UTk6i4MU0H2x56Q1wr42zsRQCpuK+ZsVFBe5pLq7N4Y9ciyga43NV5fQw/
sfTRwUZlLCboAsEwNO5WBBSxbUsUBTNXFMEVxqwzwyY0rG/8s8INrKilHErj
aUgfTAorDIVSVMIolBZtlxynQAS4kDHDk5WMOz+N0PXKg1SGr+fCJholepwW
eO5rknsBf2qkaq0RHbqH9PSjAF9g5sZNQ1pnF20KKjCNXCO2hwVYmYfz0Rh8
zpckVra5g5PaT5NNRIK7Wf4nEN5bDV8triJK2NhmX7ZjoG6spO4pvWYw8B0i
BRs9kpkM4SfJlqLNZ0uN/6bVlnhvmxPEBumsy7Gu/Zy7lrt43nfAHY9W93wj
6FF1Pvn/xSBxNB9tENmzfEXejpdnth/Nl27A8tA3qEUdisMOhyaYQ01CkdLv
dvePVroZXTE2y7n1TMWHwn/Sfi5b+zsHT7eTRZ1P8p9N65FYGhukB5fm9JSw
J7XxtMeHxX2MMQJcM7cKewRJc6kq8xOqPX54AioTqDofDGiCMxaaTe4mWhKT
g2DhSs/UDaC2AvrglWJVuplCQxuHbx0Ka/KQcPHkgQYxtRY3klwMWrcLFkCt
UAUggnPCydbtIMT+GLOWrAUG48l/DtYCC1FehTwV+hIr5Mg4I0XDY1dFoxRX
zn5WvXGmI1gYkNOElW3PGSOCiA7FeR/+sE9xIpy2ULOdGr1eEuJZvQvJ8Hww
Jh+eybWje46cSECfBW5xwiu1eGCkUrArvQ2TCxN9DboE9R3m1kjRK7qdhFSf
zVgvVvgI/Jq5D0O/oWB1YDsxaqnpDbJmJ96oMTJM411hdh33B9F8Rr4pyY1X
aE5mEgKvpLW4qa8Un5kCFm1LIlAj2T966MF2u6EcsXZPNLKSmNDUZG7UFw/x
zQq14q6+LjDdn7Oy4IdCuUc7JdtX00VgVMMwrdonB7VzYTgFQM+RXmLHiubW
N1U4refv7Y7oxyJ7BMYTFDZql8WMDL4tyxDxFmq44/0+YGSLOF9efgNey6BT
1BQuRg2KQJZX0cDKmsd4Lg+JQO5QMhm//uhepBNIpHn2X5JMfuWJrz9tjhXJ
YbOciRqHtmdLXWd5r9jmYx9XXjubF34FMiindADuX+khvInaY06+6xWRjasX
22pFUJxrQno3YIkiHkNgUiCtY3qkI9+0YExp5/H28C6vUZ2Z60XX1FGf8Kjd
kLjKFR9sR92SP4qWAlfpgW9f0UqAIkngFRInO2PS3lsFYiIDQ1WZPImpKSsK
yzaufDxEXwqxOnspq+TZzv7BMNl/RKqbD7m1Ts2h/4HbkGLzSyFyfa6yDbsa
BZQkdYW8WSI/7xWF2MOvUTrQZtqXWXCN7Pr2YiqoKr+y/WHyYOcJg2s1uKNO
Zy2DbLPjHh6GUfyqY8JEYGVGIeeV3G09Z9MPtFkFZ1k2BuGfwJDGEVbyJjzl
9iZ0fqoBGC278uyeu7KKWzcW3WGKEvR9FWydaLvuJfdHtletRFfuIxHaGgCs
dFn1Ut9VxxK7dxpBJcUr1jVYzzFgmKtqZR7BGrV/ZyxkQ0EG3QWWKywrV9KR
5kGEJQUVN2Rot+syGkt8CFy50yPq0QrHoWFQlC+O0UrdGNezy91TMmn6jdmI
1uIaSfmIg91J2R0zc/HM+s6/mW6NCYKYJqQzeYzal+ZHd9w4OJRMwZNXJel5
d2rI1QrtV1e92KUOtGltBZ/ayq80zW87MK2a0p+7WJfhfkqbDT4gdzlW6O51
6Vaul1yhX3TBq5er8q3qsOr/cy70oRnEK64PtVcJYwBdwwAsk7spmrshKzk/
3ZSE2QvYplCvJssO95zPajGzyijYRPrgfkm/iej8foUgcasEyWrjoneLCNd0
5TatImO7tPsqOhtpIG0UZpsHRlmmq2nA62l7fSrJb8OfwoX1Hq7o0hp6wnFH
sE1lJ2lt+UsbUdX2sPfa21/a6WisDF012EAM2k30MduRxZATO7KkGwXg3TeG
z1deNqpZxHvwD76V+9hftSTJJlWIzayYZzxH85nGHNdOpn1n6Vz6uKAkdIYr
FhnviKwwK6bFolI+xgiVApFOeSLcIFvUiMPwwjm/oKV4JHBivaZi0EuKhzsC
0ptFyWB/ZlX2Nkdox9o7IQcKmjjgWZsEeE1+J25rbw27AKML6J/h3GlGCqZE
TH0JVFIJhWK5wbS6hp99LLR1/7ZCm5VtZemrUMo7MZWaasis9S2DVl418kyd
Ls0TcjoHVQjUIjzwkGTqVbnZbyXm19iFK1ktdY6YsluhxzEGNsn+sLXn86zE
CEfVX2sumTX3dBJtyOc7U39jdi/l1Dar1xPdw99Je/iN1FkvCQxz6pYElv/f
l142PJPfQnWw29Ltnvjdb8OmF6C78drKC1Cu06i7XS1p7JsLLqynw2R/b2d/
H/7PA/h/z4bJAfzfA3LW9TnTV/iT/TF20V8Hr+ogwXztNeoc+7ej7f+Cp08e
UdbZN3CIhjTddEQQ3lpMCEvyOc3YkUDww6nvFp1E0/N1T2epzPTL+UrXsWID
YXVXzQDPYijvRqKhSxFQCXOEhLeGCJHGJgtKOfJtKfkzzV41a2j1yzl7ezlq
wgPdhxHd0ePr7mptb9GWR2r99m/hr20O0WVqO+6EfTdTO0RtT9rRDutU3MCb
6/Z7r8jKA+7SI1ZblDGr3cxYpQuDD3T5mAy4QaBq/AHb/QZ3/G/layJwee9w
CskRHKoKHQ7XH9M6d7Tb79Q0Q9+cLj8X5VFy15J0WbkePrp2Yiud0q7j5T6n
dJiLOset9OkO/Uh9eldBTodH2t3BI70CRavLNX1HV+09XdOruaq7tzPaNXu8
dXunu2njCzinN+MjX4AjtFnB7+t15k7PA/OVgTQ4MW6fO/IDgkFpXL1exXsj
ydeij+0v4xnsVVzurB+bLrgbewq6E2W/nK9ghU9Yo21/OI/wHY70nrL5C/iB
+/y/q9y/eN8boZJf4fTt8Pmyl7dj1MZEmorN6lmsV4n/i/p51c37Rby87ot4
eekgIqdjp/m1yg/Lzntb8X8/V3FAFPIwrY7oexPByPS0wi+BD6yw9vDnzXlv
a9PuwH9/HQfGL/+m/lp3X39t03G0xl/LnOt+7Hw1Qw8j39Fr++toaOPzuZ/v
9h834a43YaXjdrXf1q3w2/4BD6KYZX/ooyAvqtoK/R5UzCettMIq7sxdFlNv
utzTN6rfd8ZyW+URpaqSqlq0R1AUpB4zTk2v1f7LDc29X+Nr3ygVf3PFPi5s
iHbr6YrdcuvTHX+b3VKt/A8Vqf2N7a9Il27lx/fbVRvpfEbFw28kitLDnxn/
XmS9/pD+uOfT7cU06bQRyHDw3m0z8rPrRtpt+D2ebFtljyBgqEs9YZUbK8Z7
2dGHd40IG4qHEp5vAB3UiLIsCHhhIgZWwIAKbsUF9wkcTT5Bg6nPQ0BepBg4
PjkTvGSRCupjpVrcrQZod3C5Mjti/t+58d3uonjb/E1x5qYQIkCw+O+eJ//r
8g0Zke9+GYc/dGFaxoQCl1FamRM+C+r87LN30jl9xkTCnAbjm4QLLPCXnvPb
D6hvvrfwoF9B73Tk4qLXJSD3OVa8PzcjlKOmkwJ7teMnarDTGYlkuyc3Nx3B
fowl1tvlNCED3CVigl9Na7S/7+bOMEP6SE0juw6fazaewSU2M+y0iTLSpkIZ
tDwmwQHizld7TJI1HhNXd0CFMGrnQJ0lg25vCeGn5Nhp2CTFNYC8iEORSyWf
zrE6T+D0LJ5p5RqNjhGty5QV3N3v4jbJrlvjdnF3Frk96W5/GEn7e6pDG8vZ
II08iCzsLL6RVzCnplxChFdBUxCMJBehNeKm9Tq1VXg8CxUfB3vbu06QSwmm
CgdvQ+DijsZl9ORRTsu8Ijo/dA10VQN32uyz0K7TdwHedoiHhFhQm5QfDln2
9MCfIYYIfdvIVXvHu+ykRisT3ui6A29HMVcYdGfIYCtNuFe9aw+2KbkUZHw6
CYX0MfQE8blqMSLQOA+FaQonXYdVdwcF+T/DpvtjXcnfPZu02zt5l/jpb5qY
uZnL6dkw2d/fQXfTwV6UItjO0VllH+Nfj2lvjtAks0AaLlEoDX7iH9S5cbKf
0cVWZfwZX5VRNOE/u6hbarqrFkZHcFgFe8VyUZlIcFltntDXKnh1CkN4N1dM
pJJsloD3hTxTG9LsPeulu7xZrRph6ZvpvVxfaOv+cRPv68mKLfY9X2F9mV0h
KGnqukC+u2z6ux5fg9n+sf1f/wWOti+pp7sPaiPPb3+dH7M7pyLyzsQf8lNv
1H9baWCYMHlDWRPv8+m1CuUFnczdLVuPvHlcTQn6qplOR4zWt6ogLx0zMHLk
GVXbe8NaFfsCUe71rwARz862VfmMbI2T/DKfjdIaefQvktXlKByEgywQE3yy
VFhkksadd1jFYhdEwO+hPf63v7erBJ8o8k4U+bhFhikT+yNr9qtX39Fgaksb
WQUH6LaiosbuiajPrcfNIBd73FPGabfX+OLWUW+aMecbdpnvKyOW/7m2LfpL
JeDw6uTd9n+P+/Ilfe2rvZZR363gw7xTiXCH69IpEXOPEePo/HWBxH94NX8N
XQ3hjpe+KXVwehMOKvsbomRTJZ8GRHLS8BCm63yErukj7G85pj7CxPcP62JZ
6ujrUScwm4DChT09n4Ir0KKT24FcYNFdvsTmMP+5vr//9nS7Wu9v2W1bUbMn
PaXHvazHa/dRQYNHqjDhNP3RR9NcErKqaS2Ji9Kqo7ZENr3VjxTKILu+gwye
mpfEX+nbMdNG7W5OxYPgVHyy1qnYTdCU3YFtlLpgeZN/eBPv6E20vfMib2JX
Wz0v56k7C0rmT4LdyBHOobMnxjXErXtT8UmaZDl0PbbhgVe5Hs3U7uJ6jNxn
BJLODsdtf3t/ZwcaY2Uz7ZUF1SEZKGxRRyJ9OqbZ/7R8u+aVX5179xvLrS+x
k//jbv/7GQZ/00o6NPUcYV49Tw5lY4KmIi354gudalsXxpu9yj9lGn+4hhdn
vFqKdmpTbFcXNTbF1qd9gA34CruKbjBY+imfLqYdo6POJu12oo7dIrxTXQ8V
oIXGrzys8J41jlzx3nbmJ9pkiXuS32bWyD/cul9OvVvpvm2c9v661Jj+BK5I
12t6cqWVYo/SB7sQJVFpYxVKr2ppqO2pAKnE7TsxZcn9iglJ8XGYzklbv2yl
8h4809BHF/NPUH+9T1UXkixdB0c1NnAjBjgNcy/0VgxUDY6rhFJqG+wtS2ZF
Y+rPVxVs12EmGrVCp9cDRrl0kHDcv5cbKKRlel2m85uhLGlSXBuXhferdGCK
3WdJ+pVVt5if2IQd8JP9V55/3/jWd5zpXeo7fsXN5y+vuPzwwAZXyDiwKMvP
RmNcbGGZCxNZWdHF1XjKKsNOVC7fPW2UMs5743sU2if3KS3mom3y+QcswYJe
HfAr0G+i/Vdaqj0mTs5RA5dEr4GQmFKY8xQ2kHvAudBrcsW9QGc9IERrhtxP
hvHfuwMykofF+dxkJfh4T9M1uwbfYps/dpnZjOuWBqu9lDTbq8MHjAldHBy7
WqBOYdrvrURWbgW5kvPXh2/emPVJ7nnuUQZjz6wGxda78RN04zccubCvOZ/7
nduht/MbOSXNzkCLh9VDDNuJrlq42rAccruNs1ZSo5MYnvoKogxa41HuTRrU
Q4qjDT7CeMmNMPNZqk0PiQa0kfxG7jadSfQJ1/eJ39419z/JxvmdAoA+todt
0XwIluO0HYFeU4nREeLFpqW/LkL4JU5Yb85vdMpf1oXqnabrIMC+gM+0nTzR
EoNr1zBr6NZ+BU/6VhCjO3Vme/xB1xbaD8T2vii3QAfjCV5kWuEYrHAN0S3m
Y/ieD9KZUJ6L6xE6PUOJ++f/tbOTfPr0iWkdaynKAr4zowaNwPRvs68/olJd
Z6B7U8+4q1Hy5PHe42Rn5183M6txsTRLXsw/uPBvaXnfPT6wc3Dw68pS7pJ2
fG/fzT88LqvjC8pP3srpvFaO8fkrzyJ+IcW+wVSlsNBbD9Rvup+vnfleWm3+
jO13PcH5cg+10H0j75lrvmc1aGrK6YvNTCYEK+R5vRxiRZc20aQwRZMN+owL
r2MjB1fzDBtu271ezODrxfUMe59qydnfFnlWiyczLcem5W9o9to9nIuHw208
BcmDsEuXMPYW/gFIvBwnN/n1zU5RYvIG/LKtEH9hMMYjLEZ1Vhua2A+yIlpG
ieVDM8kawZSK9DpV4y5gcEoD9aq9RY3BdAkJt6EPiU2CBAcjwsXhvqGUcMAk
Uy9Dh8/20LK9IbGJZTj28dTp8+r4PMckoOEeIqGU8BCSwbyA+3I5yTZdYxCq
IfGlmNUkv1MiDMxFXCY/APMZl+ntLDljxkREyDYY9nTLi0UFFJGOP2ZwnJiU
xQwMzOuboqL+uDXaJ3Spt7JP85JTt2DrTk6d+tEZjUImYHrt8seCrYpVvWTM
i+rrDsc/7ZydvNg5mWldtlmqvFcuZsQdXsLdIJ5yKibYZUbW/7q1MPQMyAHg
M6CVfwQ9HO5/RtsOr2+yn1fAgPF0eECm/zB17xyQ8zUcnyeAbcfJp1I9V93s
3ZuzE6WoWXbLD6KHNMfeuxhx0Cx+fTL1gzUli1Su4s55SGjf3h2TVKghY1VH
MMp+9qbEFifi+Cuy9dl8ko7YvwIaJGyf7GjXIIuKbO18lOPnyDxHytM0Hvs+
nX+VlR/zUbabvK9DaexVc28d3tJZwWEfM8Yw3rpAYzRjv05LYRiyksVYKuNT
q7q2pU2JrosSKRSetAn081dj+dMvDOjSeqIC2Y6KrWgNSJLV4rJCRABQbDwl
U5vIy6XD4k3fmJr6GedZFTuHT7nL8UloJ528QDfc1unJi22gKe7nw58LJIGr
krVXehmpy/F84T16Onmnk9eyae7wLmOyfi0OHXMVgZpRlaj+TPee1+25TehV
HBGpaPV8Bl+bGb5f1EMXVahzc2fBzcHTbW11qJamsn5WxxCdfJFOmD1rU0ln
mo977xGmq5Y4ZoYsxgyHgpuYi4Lt5Y1u4NpXHVcUJqEZsSB96qXKvmWSfbrJ
QW46f6u1RBy++jFnJqQdyRUliPYyD8gUuDY6fW58DgreGNg0Y5mHTFz2fsHO
Vi6SupK2zxFXz79ApqblNeXGCeZYvShhcVlOAmor3XYsdsDoTEl9IOsKfgJ+
VtRKs2MwuLJMQ7BwDnghpVTYyb1G8+5ymyXzIrPvq7vOs3UQNpP8mjaFjssB
u65hr5iE3hQjJBeab8AnROB0I4KAhXyqk/kN3pHiSrif31LZ4njTgChHi4nn
Gb1rkk2MOCoYHdSJlVTKq2Z8iNXgfAa3DkQF/ph9IvyMUYb9ylkZUAFNk0dB
r48krUe0z3Va37j4gO1zcNvP4mWzSID7gY1etXbboX/7Yz5eoO6DVeQj7ci+
Yhv8xnFjeteUpLz4UI42uinyUdC1ZsYiQ80StBHX9aHdHv7K+Tm45JmymoaW
klm+B0xlNmZNkczNXPQEsRt1dwy3IyaxQAYnOp+vq2OutfrFmD/GmPKULSn3
7xpWLDohXT4RwoHFA9NcsHPZnXUsE3MzgkhtahDw67F+1QUyvcyYAkDkYkKF
XjTZtdZWo05bONAQSQNITqbE9EQcoRC/zNBOYviBvvMifsQinD+EJw3mCjCA
kdzSiq0pB9R8fU1To8zecX5FtCApYHBin5+DOFlOsn8Z8D4l/89oewCC+J+S
U7rt+x0H7e/2KoaFwUZ8low6PosQpkK2kmpuiH7qgJnVx+ID2aKKqyskwcxn
H42xujEn/RRci6LSOV0iWhB/lyNy4rVFfT1Wb2mjMFqtO2jUeZZ5+JQwTRye
ljTCkWaeyqiHA31YGKpZ2AO7sPSKssDCg+HYp8WY7FpdI47Y3HqYJGg6NDuY
idwToTYdUNlI4rucN2FqvFbUuuegACmnw/ebl6rzOlGOogGhvsz40+Qckfvj
Q/m4I5wVqRT2PDlSeuKjfunJ6TQwyc9f0av7oiQqdaruGBXP6F4jLgYQemn0
JAyyqr6qPtmhJchhh3eD09yVDYGcd16lHlI3CrqLJPaDeE6TW29W0l93N5g5
QnRhtkPtM/qHGrJWlGkGJQHmITr/1aIklnhblB/wfMfF2g/BVnyoGvzO4/iz
NMA4S8FOHSbxQClynHkt9vqMh4MZMW37AeASO7x0uFloRs5iuVZ1jQlzf6Vc
A94DagruqTLa6S5z05+xt0lMJDPtlr7G7nTuXzUo6rUnRAKfeZ41SzzKMxOL
qHb4iqIokab45v3R4ZsfT8+OX8XeFeTdM8VP6poP0k67sBJPf7FSlyrMvN1l
WjEPRW3cZ++J/m8vMdz1dwgh5kPxEyzQLB26BoH1LCZYDJ+EO4/fDJ3t8WN4
zpOimKN9t373VFGX3avjag17OdevuHuRrnOROi9SyDW+w5kI8gmdsgvq8tD8
8Pa78wsS+GiQq7JPOmiA/lIV2akGE5SaCNqqNRMaXFWktGoSkE6XbqN1fRXR
bs/QJwxbSAdxQWoxomKBqMCgkQL8tLfH9r/GPecUAOShE3LLElviA5oSdQj7
VrH9XBTjc6/BCa8+iHj1wWpe3RL4wr52oyHuyCsT4ZWun1eyEa/jq3GoOp0N
VzgWA7CXTTXPOgU2WPIlMky9FNrzIHTKpXfdg77t0jk2Zt5k7pOJM9MK7B32
BtjniIITiFwir8W8HKYxRe4dTiQ4AN8d//Xix9fvTw1fI1uYgi5ECONsnktN
YToel5zCRZ42R+jWWQWUldIFK0pJYLktFhOEaIMvZuSW12fU28VD36ZVbL7q
T6TcpP7Shsno3YpsWlevOqOw1sPzH08PL173LzW4P0GYnhMjDHV2wgNuZGkd
ZnX/FBIdzgXsMoLnAmMPVPkKVK6ZqrqYJYWPowWbbAGlRxES8iA318E9bUIZ
qOf/7X4JPiG8LZXUF4QGCzB6fx14KrCG96wKoINHN84zeO98DfIJw5bUCy94
vKSEpQAlKkzNxVOLP0s3dD3A2a77/Pns1dGTJ3uPfvmFfKoLKkLU37FHOFam
8uRVe9UYPJIIz77MxRGNy7EhCNVpmDLGBW3UFH6iFQMTrrl5A588GjTXKSvp
Ddkh3kKiIs7kA9Z9K8+S6HWotmEWsNWexOMYxSbQgmAW2XTXsw8lNJsy5n6P
ZsU++Ks8kp80VSDqlZal8VP06jJB8VRIN/TzSWeIxrJIZYJxxdVKYUzzbtqw
6PzD3r9KIS5Rd0Sm6s2sc7hvJayYDmYxycgqa4QgWdrBo/QkBSEvmp5ZcW2R
xiMcjOcWBQvEhBs61nQ1vbS9E2ZFHWGMywxp64YiqdHAtkIW1fLAyUi2xIyV
vCSEqcGMdYQ3S9H5WJFFU3NWLUo5eSIiY5iKJ717xgxHemv9J5p5ij/ZMBiN
Es2GF+J173gtYiZwAFqm5NALaJbLexCNmXBIs9KApqhKRrcsAsyiHGvnUZPM
scnv6CIHS5gK3VFP3Lkp5l42+gV2S9bae699rE4SgHAkGOiXXziF0hlbpONz
4uY8IbTiyqut/qNbt+jyjyfCfhbSA9HNVCyuyRF2otu4rZkJQ39h2HUQdEGV
v8EdANprjjIW8T9GSjgfiSjpA/6QKuWaNtSwkkZNo/vWBmxVIPSaYQecnauJ
KadCxEMPIoXaNqYN1wzNIFwXV8CRjDDTIUW8jMswHKUccrSTRTxFtzXOEehh
stTMlGy83aITVdPVv68jbwE/mwLnymFl+kcMNlNkmR0yZFeQs32EgRxZlREj
cBrfWZ1Ltr83JB1FDYwK5mq5m6+LW3S8AM9ADAt0YZG0WnR+5P13b17iVz6g
5Bc0Tqu7buUzn7G/VB0xDLStRbZih5zJLzkFjY7w0+z0Pay8zRcxbpT/keQW
Rc11TbdXd9PYPPNDVnkdySLmaZrzVLaJONrOmM1xlt5f//pXUvZlr9JLOA0M
J2EG+FQS94YUEKKkFp82kQATQWOn8g7QrdG21z98RSHdUbQstM4meaicR1MG
MLmeFVNK/rvwEr+Mdnuku81or1fk3Ik8LPu7yaG8elZn+8NExT47jCYcGCAv
S7jBNRps5I/Uu5BXVm60zYWYLaiaTkPU6JXAHZlZKgpzOkgEdr0G9biiWX4t
5UjtSflrKDERNnCwICv/mJH3ii89vh+uOfmT9b+2PWvFT7Gzwl9omgXeLPQF
BwryHuxh2DPK3ahq/0pwacC7YbPgthzsaqKL3Xxa3hXJTe58iMoi9+qKlm7O
wSS19B8Fp4MVvgTJ63nj8Emi27nUUCQnpxbPhO4UDohOAvayk7Iir8J62hLD
4y2HRQ3pMqCr+jJrSTUb8O9UDSSmSS/DUgjFAROeKkzrKip+QFLTlnYrSezq
AzI9ktdhzj5aRQpTWxYorfHRZ5/m/FcsAJHv1ZyHcFksZmMXdiahdMx85P2t
MP+uV8J8hxLDNITurxysBJfNklud4rEGaeggtuERRbvKQfgQbwiahmG7X1c9
lxYdN/wFT9mRhQ0vqriFFb9doIhjvzHfQl39Vqk0j/PSQI7jgCJrR1NQtD4S
UWO34iu4Y+Ksi3gcGs3eAKQnc4rjpbNadPGGliFEqbvjTS8XpYOs8YAsk9us
Q3Y0lXTSpPiNvPQbU4lK7cdcaKDMidVA2012b9HFQbdIlU5xYfgAJRqJW0wn
DkyrZ+u3VTbS1kUSsuEU8B4FNZHW3knJWXCqouBlwgFI54nDzOwxK0m7o2JA
IO1cA++cAR1/AHNg6cyHzHN4+nriZYH5/JpnogwO/lwXo2KiU5a7K303KBqV
9tnRmr1GC7uiUhgcsoP8NK0Pv8rbrpvOrry4MtYFHWtSXF+TDGCN6YWathf4
/S3Raba9B9fbtJRf3kiAGjZWgkEDUtUrXGY6CUzN262uZQWybh+MxI60BQM6
EMIDyMrIyGABiMKcT6AKqhqJWVDlyLWmObZBSQ82cduE63IAe+vCmblWzfAN
iwZi+XHAO4ocVZxF0fVcFCOpNLnG57/Akex4j0QoCoF1LaZyqYYh8g77NM4x
dU8Th2ztUoerqu3/w51Oq1FWIjN2HCYQfVI8jrSwnIPTwARH2bYeuSpH7BEO
ENT9lq7OcqYVtoE2Gm4xl06uixImPpUtijbG/whEf41C5HLpz5R/nyTZ34hd
OT49q+T3eFp8pGTWzEkEud00k/RrGoLCKYZZ+ZJGNBuTqsBYa+U8Katu7WuN
ukZD3yOsJlUb20neiLIeTjD3virYpnO5mNpnQgdA4RCy7lg2zKtsMS52EAjK
Rgk5kTj8hv7t2xk65jUlglIxJmlJfBNZcXZ1hdkGs9HSZzYwiwd5M44VGba5
S9BZFhN0KEeCFN5uw9eBDX/4Hz5bzGwwMhe4HuPFKDOda9jLVzmKwErutsl4
3EW/pTK957DrVP7xLwP906Dbp/n5eWI45T+BCYqE0EEHlpsYJ1iNr3P6Pui3
KFBEyammKOvhugVYlsNz+Q90RwO3I7xyFvf4csvVX0Ux3lvOWcM6aPoEmizS
35gxG+D98+MLfoRocx8PUSJ/CZw1/BM2+vDc27LioaqxZp7FvPrlkbCnGcIB
oO5JSgs+O1BP/SSbXdc3g90vumWYKQcb9r7M4d7HIQJQiOTPfnfWfNsyfsQi
2GFeUbJB9/a7NxcnPx7/9eTix5cn50fxnjd/zCuWVNzcJZW8pUtQD7LMfyiK
l3uinWX59c1lQYwL9m5LDKnGn+P+Kn6EduyHDurM7GjkZrvJ+teFex9bk3h5
/Xuy9Vqm0RqHAtkSnuaSQ9KlwhUUYgrCzsu358ERcoLMZvZ1nZDfGSkS5nAt
zbnBrKbMBNiZ2rfXIX/JLrCer2P4Be/cCAAjEq7D4XHIlDzLlwug3Vp/89+i
s+EP7ibn+B/6Qcx7LcOoss0nWE85KhfjjOqsxpQwLQ6V/w/+R/1XcYhp8i+W
6kH+wH9QAXRMntwlW16a3fUl/B8YCltKRofnW9Pt5F/+JTF/mG1z0+Wtt8cv
4T+Sf07wH9Pt7WiUhKx6ukNiqHXcJV4i5oiId93IEDqgYSIfodh+nE2smdRI
+b5bGX9r9nXVT7DsTZEHMTAFkqf/aQ51+S+bjwppu9WkDarQbrY7TLDxEyz0
PJ/mIMWwxCna0nUL1IfxUtM+csguioJ7ndEkt6i7R5kI9rHDhJCQ4MG27kmU
IJUTsRfEF1FPNFoYV2yxFdM7pTCmV851An6oMMkWN8JyHglccDEWuhlYZdO8
WxZJdjrSeO5cc47SFSyLPO+sl4ljv8x2NJkPPWtqdfkEGslLCl24QqoRewNE
W8d8YNf/YdRL+Bba8IdWEzZReCl5lVVPuUqNkUO2lPPVdWaKFGppvJBfhe8O
vZYYIjEkj9IpBjNwLTt6bj7jHbVMSqSln130O5l7NKVL7VimudIn7cFcyHul
5QUldPXdbe2vOU7J2qRaIOLpdhFO0/uV9n0MbYArGnSs2ONScW1L88vyWZO1
1nxCYqOOfA+5tj70R9S3N7BQjNqftPdYChia34nyxXJRHlz4UqU8hdCYuGNR
Nu9LSt8F0x7jHapANb9G0fiu7RKLurlCDBC2HpZdoz1Uz9MKPoyHZu6o4W+a
Le3I/0KuG/aE8M+aivhPdMusq19tHjWIvW5nmCmxTFzp0AWRtoFKSp45cf37
gXCIY8rHu4N5oMH+Xp3TG9tohcsVjf5myyBjlZD6xraS90FBL/NRKxysqgwP
FNyFojraQHwzMQyDllza42dBpEgOSlJ6FzXaFDRb8amHaQqqeJQ8xYYwxgaN
8ikmOYpcEQ3WyZppi8F4C0n33TpHH2vTjkR+xlyYmTCpToKNgRDk+Oa0KLDG
kF2YXCvmV5FObtNl1VwM1l1IQSIFTjAqlmKiCWsMuE+WknyaqPiDiRPJXu3S
YQuwnvaL5L6GcMExEfJ6yRjT2bJQrted/LTdoMl7aOS7Rmm9p9raqbjCFzfT
XVl7xY1BnapFR5zghr9OO35tK7DxcJi7DCofpanNdJiul4zue0+t13yyRyvU
0hK93jTQhq43rq5LEj3JNa63zW1x1vtoewKfIA8RfAyZqqnbEj+81Tt9poYY
jahLwYsn6g0vxVpERLOzV0eP9vYeRnl6UixTMWFjZha29v0nKRkxU4qdq9ZM
RdAO2aYmjzb5zQ80v/llKL3BbIILnwPQm6q7MrP5gDLRuMNsV51jxngtlNe3
Mp2OhojjJKYSiFXlKAuQeAon7oz9AFqZd53NMoH7iV0SreaxMGM5tM4BU5+U
ZXzqCiDna54Mtl+8paszvfl6tPK81cJbk+f9wIuwlx0H5zbJz+5PZ1fwO8RS
bAWwfKJH6ZfCYfAiqtsOFVuOe/jEFRwaTpMENTQ0JGUlyNzoe9wpi7IC4wBi
ar2tWg0EE8D8YxnJ1zq6jvQrfie/pEkbuM6W01zZju3HvUxCofJQ0WhMllXo
DuMrRl2H7uGjZkW8HBtqyqtG9rXrW7kCOdphmzmkQGbjxBk0Da7aDPxOWA28
FY1sfU6I/tAG4Zi13vLKfqgms8AQuC9O7uVVF3CaxQpDUCfMFvT1r1EdK7BC
ycGeRRNYWQlLBa2JL2g9/rSmoJVZ6WZlhXU2upnlf1tgZJKXwc/RExlCnlGd
UlR5aD6F/Q6Y+8k9EZFKAQBvNlVyLXpW7zQDhvSixqPBFRHnMZj8bEqIQx9H
sUFGuvO5uXRe0szHXzPPHES3i4PV1FyH+WFfyjbwMr6eDMq2QwDIylHhSzGd
SJnPe6DRCewqfknI5vNXBf8RYaVaIWBCR5rmcRJ/YUZ5J6lTb9IlUNAZmwYc
3LaIHFsI6rLNR9JC+MGgBmG+8LjOdkJPO3PfKVih2gXxL8wI9vlVPuPK2+Qv
JMSOX81mqLFV/E02hihJiZF9hn4a5EEQQ0BQKtQ/UWYC+3WTzyvDX4UhEmE5
jveUnQvYShWeh79LGmOV5mroTIsyU3CsEStmacc3EmB4172fcGBxlXX4xp+T
Kngx1w/nouHi+ZFwWD+/VXsgkV4s+MvGVCpgdxUDjahfUOLdGBNp5uRSiz7s
vEDGC3xbkBioCLugm26CwCJ3maiy8WIkCThRvLZ1I8kgQjV6yXFMl4RR9Z7j
wTa+VSmqyR2+UmYSL0SFCtk0qrHm041PJFpWoNlKnECnZravNQCNBwGiRBR3
zJVsKQqIeBGmeM1tkumdPd0s7071/gS+jK5nDQroHDFBReK0LMl625r+MUcS
2CdvUX6Hig7rFzZqGlcxoT3mMXdOJGkw5XmSg6tztyi9k963vkbXQoGQpF3S
x4YGycXXJEsiSuY/6PqIicrVRSSzhMKLYbITzWec/wxZmfqWd/OhWy4n+Yjk
YzdLw4ScPeOjON1GadfJGRe5/67sELBZyXGiMCHuzb9hYA1lNX3z8OL925Oj
Hw+/+ebs+BtUkIL5K4JcAxU0AKnXUQxhVtyCxpdP0zKfROWz6QRrUdSazSa5
moi4uJNTnxqviWFxzFVxj0YTULPooOT54Lg2Q/rK4pKx+dAf0HRjrRzd+dFr
BXgyqG+E6032Urbjd5gClD5ezLvsRGW0z1FkY2a06iAvJHm2LKVYbNVp+ELr
juEvmCNxkmoAh/NgR1gUWVB10jQdN0idneyqlnEFB/vOpE7Tpx5eL8DUnNWZ
zBvlvFSBsHQfSZYj6DnY0ZYLzhwlREywMD7YRl3Vo9bTgk4Gq4oFSDSjhzGn
79LYOpBZrM+82T4Ir81Es8ooEQedRgp35OeleTxOGHAbfqYLcFFLr8WKQ90T
dsLBTpiqJLr47QyzgkkvJDO0Kj1VNe7h5G2zpxutwYXwHX6mjaKIdFdmO2Ff
/LbgDbZWSgM4BeikiRmiuxSn/bktYyXrx9MRp9rw8thEOsuuMF5VYPPfs1dH
Dx8+esym22HIYVBvRoQD0EI6CxXRCreEdpnCMEY5nWL5M2YHsTk1940wwNJy
/rmN6BEKTC1/aQGk8Ha7FriTdqurjLfpiqM3JV/neJfJydI4R5ICeJB+aA/U
5mcbktap+M7sARlYtiRdUsg6aExIQAMjHl5SxDhHljohN8U47XYNgYT5wEUz
ZnublVi77kgggVV6eYUoUqc8rkpfCTUPLMatPQ1OB42X7NvOeqGJoqn2BZPa
Q6zKf8763RHu8+dpdc1XCUh6SKUBs2tfgoOMGFMSrvJatPSbgOiutOxzDby8
CMdt3NGWpJB20VXmYzxuUlyHXGlxgMY+JZ9BRJYFbEvsBapWOIGiOFbLiaMY
GkdARGXBuFLeni9TzJgkyxtbPAe8Rp9cjtooyJ9c7Pl0iul6mhNDFCljbIkW
P2wgL1Mx5ExSRNFNjAdpVMZ89gG029n4Nh9jv1LQC+iGBpdV8yZ6dcVU7swp
giIviwOvS5yMcypcqm9ivLYWOFVDomkW+6uSoEBH5ERn7nkYgYJ+/moKeyWS
FB3JU4wDJW/zGT0dPXyC7BqUU4YYjxqhZA7+RQQe9lt6HWG9GAb/wRqdV5nP
6ktnMTwp5nz/qQiGEGdBhKTjXv8lobdF6AmFAqiJL5i843SKjbxw8ofRFcUX
yp0oBR8MGNSn0onU3uIuexyjDfZHsKl1cI/LxwOjuQ6GRJNSKgZqbUhzv6Ik
httqVct07mFbFGFWMYZ5EfCkmHUam3orNbrAKHmSNLDB8lFWzhoKOA9KDFVM
IUz2AT2cLDIsthJmmctImJadEwwkZioAzcPXrsm3gcKT786K/Hw19xyWg1L6
xvpT8/XADd0klImoF8iH9zYc1VHhQVTA4LFKPXMgumyEmHNfYeqsCMfIOUXj
JaSMlKNVfXGJhEXnCLo8szUSCFKE2FCS2KlBGnz7qejusmDwwG/sUPRJReo+
dJztzNEiIM7c51lk2F1ODcMNiEucuKmHMfTfUmXAxg8EvgXNA5j+JqMrv46r
/fzGtIIDRnnh2qEOtvtesggZBOoKHiiuivC3Lg58eG5eWsV8E2G+blPmKz3E
CKXf7gPqlE1pqLEBtpZFtfK4hVlkVxk2/HVTrZJLWal4P5bSB8xHv05n+c/e
M6DC3ni8nXvNaez+pI31EUlG6bMV1jVsiAc0w6hGGPWfbHJFmSJS/AFbf1Nw
b62CJ0VtCarIvmFuk/npT8G0VuSvr5LIT3/mAzafv4oCNI5ztqnbGpapwwfh
vG4z7mktXo1MLj86yeVG5pinnU6mBTBhkEajBWzsriZQ7D97tkdgg14nYWgl
sDBQVfgzzvxg7+AxPuKS60LOEUM4VYpZOJJwfdIZcsJ9Q36+JEAY/SsMeV2m
swUXtVDBF3n1sNUcam/JjkAfRjtYUVc2JElpBkEWgofeJDx8z+DQMo/DFWjo
p/WNtw/gsuVwNUgykD+nDx62ERPjw2ioiWaiDGumFGVQZZtRJ1vF35+NEAV3
kjXBHWxR+tKoIyenobI8lGqL2zqThgr6CLyrARh2PY2oAQwVFwfzMzUQFAwb
KOyBk9k0TQa0aThsUpg0c4pvckhDopMmqwbfa3kx0jEyKMrDKkrfCo9yfzVp
nNLK8DQc5/OonUQuUHRnsY+soe8mTX33UKOnxmawe/v5qzQ8gSE6E22VBGoT
9AP96NJbscj7ynSESUVwKiNilco3AniwydTi7LPbVKKrDVOOj9DIKdSYzGwI
OBYjd83GmB1Wgusk5C7uGKHrR50OXOTpiHeGh2/aU61xGyWvIHcc4fET3WSf
WHZIzLPlJdv1flQh7uDedCZRsJEJ5PWaoddUMRqHgP6Ed+arjjSaQ4yG2rEQ
MUtm50YXM+QGhOrccPD9BU+RtuCM19a503iSnQPTZDnEGpy4ZnPq4prAnmAD
m8O11ky5deKHDEM0WiHEO0zAXsDWNA6BfCl5Lk2LzG0r+7fGJ7hQRmCY37An
wKHzbkZQ+H3eTQlXL70nk6Ay2iBUPCHtRsUj2LH5XN+fnXxz8i7MQBbZzJMW
1ZeqAux6KS4VJovOD/qQDOvz+dh8PHl39P7t6Zvji2OTL9+9VjKYfA1Zc5b9
A+/K92vbGGXTpcgxRevpWcqxrwiJ18BDGP/OxmuAEUliySSAUUl3VkZut0Z4
93gBTCVpbSqy+BNCgW3FH8KJBxv5snGqHzPTXaddTDr01NV9pLSP/j62IyBK
NVSaYHolSEiEfmudq3rh5osSI/okhM2t7JglaJk8yhSYwYS/dnhuNfquqQFz
rxeYA/LPyEhkqXQS/zoUvWKAvwxi0Abb+Io4cpVdk9+Jv8PDXGYYcqIt38p2
r3eHXNb0798dvzs6lv+4EFjOAX1z0IBY5HF8+S87H8z+t1ckQkZx12TrgxZH
1LDTQKpTGCG4RmM2RsjK4xXi7jDLhTXrhPwyCHzUoz5hdvO2ul9Exe3ceZmX
jWK0SRMrahGnTVwFMicOb9NEeZBotjF9tr676/idnQCXME9zKrJOxz8Bq8Uj
5BXnLWqX0YRIcoUE4sdjUAuijy0fFlmSbgJHPUVHT+Iv1DRRKRd1yxkXdAqF
r06SepfUkxmPIFheXFMN9kqWegfOwaNHsp8+u3fXpLLrLhzWdSpFfa0Abaxp
+CTzsB+GG+4m9h4ffxoxrht7vVq8hZDd2gUHeVnVPIApzm0INePxCZsDxtNi
yh3V+TRkqVrgcHuz7F5iFO5PaS+Q7CKe5M0qRfHGZELLgzDAQP3GFzPGmZNU
ZB3nZajckNTvsZYwj9FhubJ+Q0hcItqCiWDnR6HCZ0+ePPzlF4bAClAWaK1F
jBO2j18Ke8+4ckBzg0swQ64GWDKtBSFXgqFPqLhAdB9m5PmoZJCB9MEh1y69
LHFATcXWHakiHkDGlSyLnLV5OVpMuZRBD8610gV6NJfVDCRoLGuIe63CwsqZ
3PEoTwSDftkEXbo6+PszmSwG/MIfrQLr6xL6Jk4glfRlccYRqM04XJbmNCXZ
3YZ8+SaxhhgX1FmCQOplypf0/TDjhl6rGbn6dlFydDrAMAYI0COBGXHuG2I/
dH0UewllP2rfDBvCpYRBXWPdTSxQl07I7Vtz0H8zmGfBfKLHwQByGbEjdLFQ
zl/UqxlkKyNZe4avSBVFowmhIOxaJARPNmltngvWzMc8u2UXxmVWK2umlMGl
bTSVbMUZVDZPoImWjW8zXrbB42IwWLXMeUyqTyTsKS6eSX1OQ0IVkwj3QWV2
yM52aV9MbBBb+WYfSeKwS/VqMTG5I2Pt+EHgyuhJ91CFKpPyD9kkvykKck57
VC3VTzjfhE5qUQkOCWy8gl1+LHLFpFnMqFxEr4rk6tc26o8I2ziBdJ7DQtHt
A8wkQz/NKETMMSgcmmjpnfn3RUrmFu8LbjzqRcAN9bMD1s5o7EGy5S+uAcmc
UZMxLBQjiYQu8lxA+8pcAKIWtbwF95hSjvFcsczGuwfo82Jz+TXLbg3m2Yyb
1g1Uk7xcRgWaXipWsVz9/PnfQDwcPHzwzN9V73uXdBhNLm1ndXuAAIvPe4kp
Ij9lI28cN9Nk0hGtnwJrxOCZ0jm1Q2aPNbcMKrzN8X6qmT1sG7h+CpWdQ1pV
+fWs0SfEGTRx+Uxk/vN918tEc9XKOY8fhh6ZeVrpxuJRlz5I2nJQCT/0vSxx
hy8sGhnxVsmzsJenM53KWCou8KbYR8YZPN6V11npQdzPg8yL1sHyuDCzSBQc
25+XucAUCgBjkg4KH2rAZGezj3lZzEgVjQws3XmxjxydMN6gEGcUt+pESq+j
A6He1vg9igZhVlxN//iFAT+z6XxSLBHkGOUw/fK8o0m4bMtVNaVck9fFZEw/
OPkBeNfsasqJKN9m2Ryu1ses61W3OlilD7diXr+wUbdJNF3GoGQFuqEX1Not
9J3mjRAdU5I7s/FzoMZJunwPK5HYHrYGDyulLYcT83+JV7ab6D89u6DblGvn
3+amslt9CsOi3F8mr87fWtMAryq5RPlOYl/4HIR3qHfGv7YOSnSWanGN1idl
2jTrpPEydM1l/2APg8egMqOLXFd5r1ny15zO0u/YZrNLzLfdMzupl1wtTixQ
Uu+D55LwcacoZWdZk15xzeHcQitwqbvQItme2fG8EBImPIyDPMRgKl5wwoQL
lCFN2++wVQTAhX+NCIxVkObIyGR+zsoi5GwrJElkrUbuL32fa9/jXS/iT5j0
BRxCxyyu2NPxT0nyVJdNPSD4bwcJR+xZvbsuaq5084NSjC1iDHciLNfaLfpS
zGlWU5frfIkI/08+99PvkxSGrCHU1bwMCGb/kaHeTS7mBuytkMLBUAdMBvmD
vd/kUycdn7KLamfucEGzJvAo9mS4fWyYeRmFKUk+qyokPQ19omEYQ2rlmX1z
E147DK674PwGDsZnVmX2ZoCX12ayPoEBw0eO01zjMvvJRBPpEvwbzO+nnOyP
cF0UN5IVICfzbNZ9rqSZpvAcbpThgjvVJQkOBbbAroR2lMPl6liThUi/y4D/
+jdS5Osc3dXcVmciwU5WEk2YHd4NUFba5Jx9MOz8nNV/dppDqR+kMgkx64xB
1kEMvRQdIoz+NCTDNwZskbwiHxXEiqM4OGDKpJnCOLWuhL0tpu4qHVE4mhdJ
3QFyVM+xQs4oodpJi4KXZNfs7T4hp+H+7h4q42TR0pDy9UA985yq5RlsiDNy
dCYsr0QL5cFl1rzqr6t4UNFsGncDtMB09AFLN4BYpmCP52I/fv7qEn4gp0H9
iySBYUlGHnrjCQUFhxkF0q653/E02N5zzPiLHvQlDbeSTyDg4DgA54STMY/J
brNKaQmvD7nbSz4pn7AbDT2UnP6DJ/u//MKSjfBtLouxAkHEczFdqeobAwFv
wacVx7tRD7TrfC8OXqm+w2QesmgEY2ckO6zNVID7YZl3Y1CRV5qzU1F449Zn
PLIw1SYUglbDFudROmfzH6MazTTdUTqPTjR6OEriouR6aj1mJHHGc+RS5rDB
DVsySiuj1BfOEPeJ575qynzdxV/Pryh9WspvMqkbf396/C5uGmuLnqLFqCc5
OdVkuGHk6gm1LejVOHl1cnR4cfL+neY+h4jiMSWvny8uGYyXtcPvZt446PgS
An6xlwx97/F3xQOIUHycc7HjETok9cGgePhJ0Pb5NKtsZqLsTlJ6s2Tt+vMr
E+wghxQesNN2JeFzIfsuNhiTLep0CCwv51YGuaRZwc0dEwAGvY6rRrCYuPPp
WSamr5/nEnFz4e+CHxOdLtcMuEr2/Zayo/DeA2P1rnEc1h6FGVle3GWmpdc7
QUcSJjEhTc7SKYGWIg+dokAbVXpJFzNBW+E7dXFb7LwHhlAnhyEt6ZzTkt4J
VvDnr9Lq4HJZZ7/4Gmr2WWWCga+e05jxbJmLtK2xPdf+jEISw6oPdgqaSyYy
+M9J3Qi9DN4u3RuQy6Nle8IDMOixb5mGvu2mK4Tu/uPkkhougVmdhmu6JPkm
pUR485YNapH2R61vugCBzJX+jPJQzGvF8qBdePzk2QPk187BfyT4XybIkrb9
VeypniyVoTBBPJTtOTx34Vta1cdeO/20IqR48qAQ9eDd8Q/6oQH7FoqZEDJt
T/S5cBo93yKLb/D+zUtNHuWwj1nZLASd4QgLr4B0JOgBbe4/dnQ42LWJJc5t
UY5JmoZXYVGPHw0fPXiEyeGonG3L2qagzrCrFfZHA92vcom55dG8fN6EgcSW
bizmW8C6yyyOh/Kn6ZMDBoHgj+4OEnbZsd+XvK8EX4XCjU0G2CfrjkcFIjrz
0BIzKkcyh84X0vKCz5/T6iFdzV+wOZI53t5PmDoc6pndacx0XGcuZecCKBMy
85lQAi0KAv6YyzZzya1eyEIM5YQmiLQ/bgvXQSxmJzyFXIPBmVDzD63BiZfj
ZsZFpAUhyuRmH1WloHjGpeqBo0gPFIL3fgVHU/YQ+1JXQsQvok3rQxsziJzE
rrFe0iqA2RDrJyyyCDZzEM5YqNEFzjRQDRs0FQ++IEniZBOlLFE1ORVpAC+q
zu9c/cKejds9lrzQ04zvglCYfxRdnML1cTzcC2SGfZ1eEfJBugKxr2CZMLPu
YPttXt2GW9NvIuPk/NXzhxz9PfReE5zrQ4y0yTz9I3FQfmZ8oYgyk9eU3d/I
s8LUFJLK+09Yfi5Uehh0CbnSfkImNuunFebSFbndeEYupCXuP91sRhwopZvC
ld+VVEBjOg2YcCNzi9pkjAE+pKDIfMabj6qZs3HNRsq/Dc2HNTD4jXgBatA1
iM5d4Lriv+r8JIU88LtJz3ed/27ryLeiLwNRls0rhmWMHNH1XjLKJ+FkLZIQ
V30f5nAqYcQgCTuVAt0fItHKeeYN1bmxbGdaxftVN5e269zJ3bbbTGWYWKHl
uqfL/Z6CZJZqfvzvkhqfmYG9/gOTuTg7fHeuRYVcEiDvMP8PfRuoFT0IoWXY
Y9faYy4YBxK4ySaEQOyRrfrIwTMQcqc0aaqHcQ/ZFJciEG0iiS00feNCvszN
8biQdjGqqz4iNI0UaLI2vintdCmy3kdlvo1ZzY24j96/e3X8MuTMEah6+OtF
lEK4gsIU8Y8Eo32nslNuLYcTF/yyyYTo5rhD8YF1MLihT6+XigWXjsqiYqRG
MniBJJrS3RuIDN05CgRCgyGBuIjWLJX3XMo4TSM6Giyr9MhV+VXXRnKyqmVP
HWyeGzXlcTohpXw1pSEI1aAoU5Bg7T01uUYR11R1K5Y9zmQawZyqTFNM9aMs
jrVgSJsxdw7gcQOEH5gpGS4QTOTc3/GwQF2aWUWvsLS4LhWj3bHSEsrFvaUd
i7w2E7DAHxIF7+ULoA36FsRlxiD15O2iIfpuCePD+H5fYStbOaSms0GnyoK8
T1na0FGSqDpuQwqY3iZvvOr1lIME7bCLxn0RJ/e0k+icYT1STgS833zYdXzY
oGZfcZcHZvSYG4T+MmWhtvMjpxb5pm8KhzOOmEDrklSiEnXItUjj9VzDyl3y
qEmmP65Ec6y8k62TjTWS9AywNrtTgH0tZoInPMYCppHFkJhkV3wMVIrbIEXR
fBCKASEcXJcA2PJiuJNrVG1B79ZuyLbkggk+Apn92nCA/cDt7P+gTsmTmuFt
k0rkrUAj29QbmkrguAVc6PFbkUGOBCCxkLjQLRAx62G9ime7VVGv3kQFaanJ
cswFIbmSnnfconLINieimClwjK3/IN+Q67v6cZ3L5bJb3ZgJrlh7gKIzLTUk
Aim52oc6hQOl0xdzVlDJxdRxa4Q7V84c7sOEHqJUwJeUrENyXDKwIz/B0OAz
dS3GN/ecINbYeBGSM23iqG8Oq0pOc097D1Q+oBFKapU9dISCkU7a1XchnZLL
FvG+ZukUPUgo5kM+do52heKhrjB3KjYYGEio34BZIz26RXQkQzp1iz6xBaYy
ib4eccG6vciUIJnjZmeuz2bFDVQRz5KbMmFXi+8VJ8hYTlTikuTXswJzYcOA
XYP5WGcNi/WecmsEYKrxZSGJklbpmgGNDxVms8eA6h5e5SdWa0RqYig02nDW
7UX27doXXmibiCVMkvlCeKPYk02UE2Y/fsaUmLH16fN7Y22j4zPaeimE9OrC
UYWG7yYiGntXl8KmX2E29lRkVRGfwSoABca/SLmrjYa0v7BaPkv+D3UHePzo
/4ZeGgHFgmEkN56avSaC0sYJSW716106Rxb/6FYQkrldq2nZxbTcIOR7r5QR
fCkfHWUotkVV++A+6+4V9H4xhkrJMSE9WyvtLRkpQLFtm1oyDC0d2qpMWwyZ
9q3IzDVMyZVXPStylcC/963phuIW3duktU5OMeRjJSuyIqxmTVLwzr6CsL2y
OsRfvJKra1AYw16Zdwu2WH3ZWyHdfV2oZWQ0YD+2eK85/gykMyYFuOHh5V9f
+18P4YQnUo/oH1L7jAbJxoYTDAKdjvMKFKfxwFG+Szq66fVbRKamQVRoo9GJ
t9015D6jczeVAUGIEcuz52qbe9X1QRH3zIo7vTqyzOBri0Uw6kn5bBGhrOGj
MTKab7eOrtBm72/f6YPwQmfpZMl5SiehH/owfN4f/3KO+RptkmR2bmjSSb+W
x49++aXvKHo0CQsZaNaywVlUndPNZ31Kfic4YV9QiOqvzME0PoYZf+OfFgJg
V4Lo+YgFckbJQ69MFfAHqPxp7WEmHYfZauTed5h9MZQuooy4MjsBXLilC2mD
ZeESggUYNMfwEfEO5z4/R5H1kfuxRYYoJEXB3Y2pIRf3zQwi9/F2gF60LiuO
6kfmFRdYq+8KE3tlRhFB6KRmjTEDa8TMZJ4bq4imoNHr8M1F9n+PQj5dX8M9
MZFXIlRu6UWpFc+7ysKHHRePdUOuvw6Xj0omO4Na6zixefRX8+O1DsBVXNnZ
GOjdubLrD9dtypFjbNH7cWTXf4k35sgrt/MeVzm/WnlTn2Lh384OBdkx6fJw
hIlMQADXDJvmGrlKVLVWVNScR3HwMTEGk4Uw1rv1Skp/08ZAYqpg1J5atWxT
ElPzc8m5ZJkhWJoMy5k3+C/j/Ip5U/Njz5vTxlQtqc/BPZ8vpP0UapZcIbd/
8PgJyC7Y4fejukC9bv/Zs/2h+6nIqeNBugD7RIravs0RUgfLwtAGQ4L4j/RD
8TE5yz7cUKqd+0F9HJjSTbnKn+YEOVUsWOf+QBvyzQIU38kUixrfYA53UcFK
+JL/Jbu6KrNlcrSbvC5m+bWyxlxgqSQl3Nd6Z2k5oQZqnArrtrAb5/52Z8OZ
5uTI6KKNMRuJ3BW446JqfO9y6V5msxkM+SorrxcV4zx0TGGjT2sTIcrwhm2B
PbhMXpTpGJGbtRtlhmW0quE3v0ILPWgvlMUtjnHDblM2PoBlkBGJaUJcYVlM
iWbs7Mj9o1MM83pN/buHycu8ZJRuHF3BuGR6lNgxy+rkeAbUJhko57X84xvY
0Hkw/eosnVIxKq0QzQf01GPHucuJOp1o7V3b27dwSS/EsYeJCDSZ4MvssijT
m+QYk8BhIW/zSZG8zcb4778UN7PkbQFqyhmYCqk7zcoJWGbwEJhXNymtgfZw
ju/B1pzXu/SSFD+cpotJcoGByXyZYuUlouVILTC8VpAKge67kKqEN2hGYOXA
R6+Qj2LIMa+mfAVGcFnqrFpiNZq4oX3qsab16wWHdZUFllrfZOlHbNZAPP7k
5dmp+z8n5/t7Tx4++b8mIR7ffX9+giXQeF5qQb4gjJ5XUkAFu1dioqSThqQI
pZFL+1lSMd/BCH99cP5g90FyjQeL1cZa+PpmCZuXHN2kc2LaiGaF/1Vi1fu3
i9nPOXZfoPw4Yk44Hs6WMjMF6FZB5mnsdeSZzX5Kp/DG4WVaXqazbDIECoQn
jm6QYo/HmEHljsr08jKT84P/KPG37zH2AVv4Tc4N74+xM+w3ZQqUoEzodZpW
SPbTvC6X7nVafUCKAYqYo139Ld02op9vy/R29PMSeNhLOIYxcLUzpKiXsBVv
ka6XQ/cXOGNS996ldYpee/zxNMuR0GAXbpOzHPHoxlWhRHk+WozHuFn4Xw6+
eovHdXJyQl/JsEPEBH9mCkSAbKC/swVw2x9ucvQAHC0waw4WOpnAHv2clhze
PZxkn5L/jTB4EXNts4PVfPJwNi5h2m+4jEL4jWQ+OHYge3g3lD+r+KNPerxt
fpuPWeF0ppnkp1wp5SQ/FCU6VByxGLMg0AjSANStae41QtJQOMyQNGjBZi5d
4pnS303zJXiNhPPDp4+dk54FTx+DHKVeoEZkelqkmcQkR9lRBKtJ36BZXTKY
6yXCugS0YDM7/WyUatGpEgSNIJMpVZ17G8lwoKZsDLYBMD/sRTeUU3Z0yszw
XsIRflMUY6AKiaDyhgvLpmA9lwBxScZdNvTRw2cHsqH4z44NtTeDvnUGFw45
DMwz5Xwz3VG3+Y7ix77cjvZTKQtCH1A7OT7/RmAdKi9dU+0t0dpWc0fvsKeP
DzyR4j/XEulfQMtZJv+xSGfxdhKBuo22E7/zO24nluWi5bKouDZJgn+Dk9OP
j3coXCx4kAPeIJw4drnWmphZNSfx9Ss4ASbI6yZT5vyaTf73RYoMOfm+uGmS
bXIHuqW8/N+KE8Clyut0tkyTb4sxaFBLFDCOSSTIR6+uer3ZHoV0jJ+F7hZg
o33wemO8ovb8OiT+OmpwX/DqPHm8p1cH/7nqVJsy+xR0+aK6Ac0SVKG0LmXn
vs2WYAmdIqppx+3iQ5eAMBU3rD5+nNQ9jx9rnPye/mWBdQ+TUZpjHA7MnPzn
5EV6A/owrOSsQAsN03CH7i3WPfJyQTAsWdshjeVFuZgViBRSptksC0rSq7SE
nQWt7Cz75F4hotFsXLCGJerV0U0JK3tNLdf+UmQT/OccHhyipLlO/pLDaIcf
8hLIMK0LrLUliryZwTA/4Oigfi2wVdkwuSiAc72BfxxO6gKbxME8UJ3EVz6k
t6AeXaTTtHJvi9k4pc+JTvZ+PF7K66flz8vrPIMHcOlAajWImOrnBeh28f1w
pDCeIZwPfmYJJs15Vt8sSrQ/4E34G1A6bOC7NCcYqnPetzE+mE/nuG3uEPYD
TIXzRblMZykonykqcd+CNVCmPyXfg1qdfkw/fEgnKazqTT7JYcnaL+09iuaf
3P9Of8pH2QcjMopLzHMz2NrhRvprVxdz7rrorJkZk9jdbsqTcFOedNyUxlGd
pUg/LxbVzTB5naXkOzkHGwq7YX6Jq+LaV+XJl7gqx5Pb5YzoHrUjc/1fIFQc
CPHRh3AfXLgPDVL6C5ASGNZZXv9MlgAQ3tvRKWwCvcxX4i3ZdkOXv0HDsmES
4P25ANqpgN5ohBxuzjewtstFKfRxvqhgRq/B2ql2E3c4LybFda5dlKhwyGS0
TbHhOyLKh2rTnLabbNO7EcPTg33S4tC/hP/uUuMou+RtCmYzLg0uyyz/aUz5
3jj1b8rsGv23wNaBZZvD5wLldXwRP3o3p1kEQZ0V80kW3D/skbBwYBmi8Wj1
Lcq0qpgwUkGEQSXLf25PO/l/5d4mr+A2zzulXizw6q7J+cvuVLINvY2DG8iX
+jnyIAwbYEllJnQFNx8vm1JXgzBp589h32eUHYvMCo35OfHw8xL40RSYb50j
S5ovxvnQNQg/tp2JauF+VxOwgZOT6xnQwYv0egxEVRGDTydjdw729Q0y7Y8p
mB5nWU1MMCZ4sjzA3kVhD2PdjSCf7T1RswL/uV4FNp9u8B6iP7eOAPErGxDg
vRQzvttlfgN8NDkHaQBCwWrA8AXErURNTArcyOE4Y1gc8gC16pErjtvtJj9k
rlfzepvW5Kh4UYxGeVviR0ftIgbHdAdTf11MUHu77tKPLMNnR9hr7MNRIUmO
sUdyEHBdTsy7kMPjp0+UP+G/O81My5JeAF0cgai5LfPrm3rnqPjEBPkfsNk/
I9H8++IeXAo/fVcutYpKfgDhmcP1fDs6ImUKnkcwU7ja6VgcVc5fxXdwX5PX
9EY5bt7ai2KanGY18mYjROSEnJwQbspbjKKzyJqkwA0KGMinjEamemBY6CJC
LvpF9A7Ef/VHyViwaxQPy7yEobFmlRK9ITKVTN9syd0UENd52jC7L3naK7nl
t/hXdwHLXMBbadm4XNGhNk4uJoymeIj5eXxLYplu7r9rKdYvi8X1JEUVZ1Zf
F2A3LmONsMNzuVpJsiR7MgED4fu0hA/ckMM2aGnOWwivJgXJrR8yRuehhb3J
qgmaG+RRhRVM2QZIDhfAvXAk9K6619gCEZd/Tk6n5O2inN8syeRBl+LbXbga
cLAfxVf8MRNPMf/7NIVDrmt1xV6VBMCVzQIqrOR+NfxolHtvf3Xm145KVPIt
hQALZXojT58SVuoc28rn0rTiK4aaKfEm4308+u7s7PjdxY/np8dHnA/gI5Gf
v2LY2oxQEiTcKNEJg6iHKJVU9oTZAdnoZkYo2ApKarrSJFIt0ICAIceeD69G
2TrNoCh3vdHpuzA2QpO1BiWElzZQDmzvWZYiGXOHsMy2Ns4+qnZnorOJBEdw
T53vl06A3JyU/fnzyc7L3Tyrr3bycblzeT3fYacTVlNzQGaAdQPlWLDT2CMl
Ulziq/UNh7czGLbivqcIhSqp6WOgp0kxZ+hfYpvfi4t9by9hYFuB/6FGtuiA
5xzTrIQ/poR9e0Q9+PCJqliUI2Iwb9PywxhhPTjzbzceer8xsjr8hskg1Hvs
cL3Hzg9Yzv7dLP/bguGJThTlv0QsbSR4jOY9HOxKF3KkUDBfC8xkr/zQCHaC
25N8tf94u+vzj/eewucFGKbScRFLIce8UgIdfCugg5QcMsDkkd5PwnDmk08Q
4RY+ejgeU8HPvCAa8abvk71HydagXS/+Nr+WHnhvMyT9vJoSgjge7AXpMcfU
abWyXU40XdLXZQ+2w1QO9mUqbwlN35s6W4OXArV1HJoqn5bFPBWs6xeKnaRl
iTDMqTTnwg/07QSObj5/0Po86TBbgxecX/1NikEqZPWCBPWQo7UPtwm8kODl
GOF0sL1i/3FQ89VHdOSH0rzq5PDdoeoOnh2qWxeOhH4/kgspPhBfFpv4UR89
lLWcw3wHFQdhQ7oIYRgg2KFv1MYYsun0Mr9e+CI8ypFxiU1u9R94LB84IjQO
JJxBWaTjaTofhFGZEUjPaPZLDOjfN8SpBnbqF1SmRSN4lkuVl9TqKKcOAdcl
xZUFdrnMvq4IhxODqoLzjDhYKDA1r8zMGO4QiJPJxI6li7gJaGkDrQATYBrs
PVZqKuAAN6rxhCJfJpR3NghffPxAhj/jTs+S9kDYRCER91QKZAjo4pJxn3LK
aQzZPTAMpfSOtXpI2sMAD5ugzi4kztBFC24UJcU1i1mOkUlU4nAUrRhi/h8A
ljRMQ02psRtnURFqhwH7YPgLBkofZSVKFV3pU12p5ENJZnGy86+8O/Lf5gWl
zwucfoa1n4jfAkNTIcIsRs8bEK48Caw826GiAUoi09Ge7dEd0m1OgUAwAinn
mXe1BxwYyDM+B0QaD/dswb1pOGnPfurRULXiIYdZpPIQzdFsFngpN3qSL1N9
ooJY4y3ulp2GK+/t05LeEiCaZJNL7yCGwkke7GAvEKIarlrXalzv2wfmA1s1
xiOr0iViNqW1dKfg/LFlVH6UbNV4l3fSakcb8m7bGR0oo1ImdY2og0upMmW+
HiXt2pcf0Muv8k8GhJMVqrmWcCHo8RGCgJXT5PgjjnJgRePeMxriCDs3XkmP
Ol/PKlnAh+dc55pz+TpDbTHA11BSWHEzlqBafRLcr7iaYoiTmqNUFQLwPcUJ
80MJRbo2MEdDTCREO5LcPMMA9vf3Ig6QTNnjWHlVa+9gT3JacEuVG5oBHkaL
xiJtQgbcQhZICyIcrO3kMh0nVLe/Ewgtp7Ygh6GZIdIh7WyQGcR2UW7VBLCQ
5mMUF3JFCHoDl4t5mWQGItp7nQzInQILPQIei+Ye3F5OQ4CtWnAtBiFF4VXM
EfmgKKx02t9/Svti9a4DXOcLUvxYkcaO7guyhPEGWIgebvETpU1RgxGhTr8B
lffYPn4EonpwjPiOyELfao6luBRFoRps01k47uOFtzwAO4M6nWh3zboAI8OS
98GD1nIe4HIuyALIp1jfYtPtvFdAc0bySlshk9oXonOwZ4MzApIbN9J+vRYo
eaOyJtJ3wkY/20YScEEVmS8IoR2zlzBNSnK5GQYeCONPcQT5uWtIL9/AR0rd
BosZavnX2Hl2TA1TdgQyz6sMA3vwD1RteImF1NxWRxbA16xSJfdgB1RuENnP
WDbt7yOGBbdLwomQGNJmoIQ4oJaLXlfNa0chRo2wSt8yySUREmNlMuNL2ews
qoUx2FERHT8A5dm98NMSEayA3kzHQ4YKF+RM2xCouGTYPkI1w7RhTLxd1Awf
9Nx5nXyOYpA1OE4rbgKEcUYhOjIIAYMfRcuTmJVHFr1cNkEWhTl5ow+vf2Cc
dOMxe77E1I3kHXKI18BdxTbkCl10CHHSvMA3hIoc3LiBFMapCZQTLKfwQSZE
IXRW6lIO0CAYE10OUm5YPRuHwUQLa0irAXcZkov3g/x1pn06GVEDRyedkaDC
t2xxANbic94UrQnzr48OT8930Q+I4GyJfTSZ5p+y8Q4BUIZtJLErSdhXC9w/
1f3HgX7zWrEkGCFSUwucVnbCSKEhyjgfE5JpBjYXXIycoHSpY+gC20ZT6hiG
u2g0JHiST5L5RYwr8EZSjqg8gYEikZxIKxiEWzzglh670mzH93u+pEvHV2jC
NwabO41ttgO22SCVkk63FFUdtdKU+sKekG6H9EIBl9vs64+ZaC+kKVEvlCSX
LF/uMsIMmO+jgXBjdW2ZUAvtaIVhfWwqH746GSbn9P/D//cn/tfb0x/Pjg+P
Xv+IzXqHOBr85bt34W9Cr1OkQOrFDrKISZpkPuUIcq9OOIZK8algHLpNQAdc
NM65oMgTpQcWwoOPEYlx/CeYG9LJGLbquTTqwbHBLuOqLasfSZUTXbG31TXI
AmwCRIknmPebauY7qjfkD0BeROm58OlgHiAlYZtlDeARwfJuYw47moRYgYw0
RFALaHshA0tO8KRQw4VXv9p/uEee2pLy2lUVIdrF4mvf+HlMuoMcjtYAPAWR
9s0iH2NfMD4fcQMLDPp55LkabAvLYKoWt4hyLhKwN/mkqAr4P+iEQ66hjnf9
4r4MYd8/qeVoiUHiOsHUHSFHYWBN6h4FxP0pqdMJl7T62m6ixR1fJ5mEKXAr
3zKjrGaGSrWl14xHQj3REU5I+T91f/Jgl3rhJ4xKwH1qcjLxUp20Ahmk0uQb
PorTkPmFnZ6m1K1rIkegkooURyZYZVhhb5gaspAVi0/jsBJ2s/4AD7N+RbQ8
2yExYpt30h2+grNGO6HgtsXc0BfGEcRq8sEOZKhBRPaolcJhAU0vLi9Vb7kE
y2OGba6J9lg/5aaBmLKJXdkrdAjsNnWyh65XQ6RMs60B0Z9RCl8hlEcLjhfG
FR/Y1uH5tmI0ns/hJESF9Bm9vUoknnhTjRSt2DqgMK9jmAyOLMwWVybvGbgl
Y3Ic7G0nhzTFUD9NjQyQYizcOcHA18V8Z4Ju1uCyGah3yyFQj7QIrOALr+iI
bwWDR7Ltb+h4JUXOCBbf1bZSOC1UCg0cCg2iwMVAZJqVIbVz/2ubrigOQPKH
eigsKX8aDxqeGTODItdPxeKw9qFIWc2fwc5l8qAmR8DB0e/EACrSfADr98y8
bxkKF4xIzjiSC0anBc9NsbIbxRPYz7eYdDAmL7NxGO49OYA99JZGVyz6DZdq
qf4OYxPapijwK3zFOLg56YfbSctf+eTJQ/i8KteeWqjAvFXei9uFZo9VaR8+
2ebvl4qhjX6SGvVBbO+XcbkNO+gbfVkZA8Noyl6xRIhS05rQXnCQ4TnXm4Va
HhonOF/Qcr9FE0UMBrZZxanIWMqT66IEJjKFQSaTdF5lwlQHRCg4yb5WuIPd
JD5BzD7vcrYfZVjv966oDQKvnpg1CR6SP914Fccdd8OUARK7kGCPiJ6T048P
VYYy5dnfG4EGIRfq6VmJRwI25gNrDHiJMU1Yw0ExdjRqbClpUYhvp54qb7Yo
ehadqkCMm3WId4n1DdPbRGaexD18sBgzieb9fsaXjShd6qFyQoUADYWXiqe2
o1qma/RLxbnAPdeJNjeG4BzYCZrNAjkTXaDoxH32c+UhOgIyj/a24/jQI/Fj
Me5mMqGKHzIR2cfNcKWNqdymBh4WBWgVf3+omcSlpqppEMznm6uAbjj69x+x
h+gbWGiZe/xe30jhTxhxA4UEuRD8l7HQ6/QTCrQlKb+3oMFkoriQ2aZIkdIn
MeBFIqQ4XFQ4eS5xm0iPRQny6KikH2boRuGMLmmMqziHyheHWNmjSJQSPFKH
ODnX2eBdttYVKxmYv4Wms1ii6KAuESzKONv1ZKKyWXbvi8yJ2OCz7RA4eLRt
LP6n9j+etfw+j9ljgoD/sG3dHQPYfO1rUoAmhHhkrSvxkSoHjeAg1naghtDf
i4PUK4lDrghL4UA2EgmKRNyzg0MraBn4Q5BmSJhjjAfVjen9Z3I1f12S/WgA
X6jS0kClvdMUv93OhaKKBgv99SraimAsfMJuwUMO4yHZUL+CrMUlk48i5nh2
phIxDc1HMH1NCdNinWNDe8beHIfOgAgbj5p060u5byVKOQ5qFyNQ7oxPQ7V9
r0xpbT5MAI9lVy0DGAhjut6VSPKN0ahrCpn69gzp+GNe0XWbseuEdg3GRv9b
c3S30rp9V/gMCeZzuGqpuaS+a3FLTMPv1FvOx4NHi1onvsNO65rbs15NKNqc
wulNJTPQp4scGCrLylQAFxQyU/JIEIAOHZw1ScQwHVICZ2j54jfZTmHjIrk4
OhVeJmf+FmybF1nyXaV2De7t56/q0RwOGOHdsdO19CwVrHYcA6yykkNtV2jP
RW0f8PfT785fJ1eLGSvpCIUy4y5NpnGYFbjIVKfYl0lmwe9P0mtq4uTOs5rs
3PBnOMSRNGP1fcjY6WPHkhoXiRiRPwa2erLcveu6KpkAru/lOTxIzjmnbW0p
0w1vN45hGr8ZMK74F2nusCQ1I+yDOCxoC0ic7O0cKIGFz2qrnf39vWQLS5nL
5XZnIwYGXg+1ljSJty8fyeXl1iIHD54+wk5FQB1w3UCKw02PA/bak3fd6Jgf
x7BT9PtU0yxcBKeGNwO/GX2dw+mNAXw3amlG4vyI0jQag64EaNLZ/YxoI/1A
+G7kl8PVE1Ab6PDslERSoekXVxRNhj9codap6Ew0HsWuGWm+8D0hwlHuFNhd
mQPUyAJw/6jKI61Tx2gPzYXxfDFvZacudugf2sDP5EL5iTuutdW1i/i3e8n7
V6H3s/yYj0T6UcUAh+AdRx4lGf0n+iehEACtoRY1n0uLCpCIaPxggLj2fK3c
4T1wDfJGWJTLijMDfARyGrJriMNklFWDT1SZq5TCdKJD+Sgamqhcg/pXLuby
ePM6CZ9207QCawjhGbh1yyS7BkEwpZbE4cRgdi9MBCaQo9lA/AE3sdXzA8fZ
oTZCy8bpDWUpdl7sIULTk7YWFUdxNEwrVjuBIy/9/rLyjN2hJOmBTwfdHOGe
wgu0hnPKEJQ32Z0WIhnjDN1uIO+4Izi8R0gMg8uy+JDNBggqNAAKL67QT26Z
pVQ6rKQqWPh16PxGAn7CR3KTwWQWUwVW2H+8g80+PGNvkDuForfeHh5tJwrl
hooFlnK4QvHrqasitShJgxjRDymGDYzBRqBgvqSo5Oy4WyqbqW68xIGvvXzE
DZ81Lo4+FqD05EO2FG4D/6IugTeYKOszFe2VV6NTsbE1HkfzkLQG3ywdlQw0
MBH2QZcnEL5K4uwuVVKjtOWUylhUr8DJAbMl8Fj0YzVZLmVPBJaLupgeILtB
8QHHzT/RY8b+yzRE1AvKk6OrT073uod3ehLws2WmhJY3d1DHmw6K3DXyDWm2
fe07hwxdaBiq9XHsAIH/3Nalmo5ZvF/0A+ztLkUl3INHjw8EFwf/CSJ2yyap
kJ9K07q39eZytCy5Vo+95n/DEaVD7UDFD5YyCKMq2F3VtxH8m4IFWeUEIHFM
OCYjIqQkQHLQSjRjWLqkaJs6VHwctmPkO84NaRS7neheSNEP4nHL8FnWIlxx
dUUg6S0WqtwHO9ADSxwPEz6O8UKbA+ZoXuKdcWVekacFNxwYBgU/GBSMSV7I
eUxw6qhVakokGk5OJSHzjnCCOGW8EnyMvPKwNdIvDoksL8YcpsW4g4u6zgKl
I9Q8XVXcDjNDCrP7cq9RuZzXBFUFDMbx1WKCSYhgJA+bEpHx0UI+jD5cEWeY
MCb+CrKAXKonwJ3dszFyUUrKmxZVPUye7QFrWqK8e4tOXOy0vkCxRxNlI8FR
qlZ3B90G+9+y3hWM03zMtlkcwG5dwUEhkDl8y3fPTFnIIoINmrJgsAa+Tckl
dErkJgRh4dRskaQJQv4js/QKeGRuWj0JdRXs2KIoCxojGdM6meDNnp7Mm5a+
AxBdF9x7sk3kErmuDUK440txnw/ZGBAawYc0QjTCsNJMVPlxjtqYdhNPZ84z
UmTGwH21/Q8ntSNERtLSNfefPNpjtY/b0opHX5lV0DNhs/Dec3zA/AwkaXk9
qZ5OrzwcJd4DIUBimUjg7Ahq7p1hM/iSG5geQIxPJG7qOfyjJhX18Pzo5AT/
9HQvQRlbade63YFhkp7mw53U0AJVyXwiLWP/AGdw8FAHutIt2ZpX2WJc7PB/
bpPpoSIXfbVpXpJQi1EJbcEDugzwThbX6M1AXuB93L6Zbb2cS44G3zKebNT+
F3Td/cc0SVltrHRnMwouSt9eTneVBgkg8DDoLfEjbvg7DExBnSfYcERltk4o
OTw6hz0W25y5Ap0x95ZgskS0OZXScIQoKilxVWNJSMOCaWcp0AtSsUc+LiYz
TU0lJ5VA7lE/Ll9rkM98E9kDMc268qg/fwU6Qkot2LCU6MY0NXsFNjLYbfSW
BEe4iAKFLWVAY1KuZkRKLg/5qroGGjgPBJUlvdnlmFu+bQJHA4GMYtNugrY2
OXMw4Dkibnsu7KxKDhUy+wVbvQ+so5P3g/0YV9MazUV4LHk4BMlXfqAMCo21
DNHpg7KWrxW8OAaTrt7xyavqttoJHuKdvQPSCybUpbGU7DFUrjd49WHIJ7jk
TigRQii5rhstjEHxAyl+kwMVjXdhq9kPnXPuyC3cGVKZBPa8qC2gYpVesUyv
sKQHtuvvtBOnRcUhjr8n71CdMP/7e3Lm8yvlL+7vO9H/Gv/Z/Rf40l48rg8V
+r9sRYV22/ilZD9+KXjPV710EL+kDvbVX3oQv+RDmhK+7H7pYfySyfJb8aVH
O0/sS9/N+Dj0pfb//k5X1KdxXhDwqjuUmHvkw9JuFKC1Pd25xB4n2tMZXhpK
AhRyU7zaDkNGIy1oYFsFc7tD7M1fcTJl/SWXmTiayQCV0S5GIQlynGZvssG7
cP48BB7f2Samg10FZmn+PabTvyffU29W+Ae2DfEhu9X02ibTnb8n7u8UnTZD
Cw3+PTnPMuAj6GMjLkJDSzJnePggetgwHfwjzNvkYdLzD6LnZxhvXZrnvz0+
Pj18c/L9sY7/MHr+Q5bNUzThwyvu1aJeIB8hopL6wlIFEXmhAypuk4MqFKyL
WCciH+wfPCY/26EZViQ6ax8YAvJVbqTw7HZJFiHeCyHcGAWWbRFGSibHnHTA
iccgjQAztUkJDEOHEkIl/vizIP/GWSBWpwFdS/LUki7Q/bBB+I2JDDaj3sZb
YTJEyi2ea+iZeEpEzl0U3aDmrl934DtSTxF9Rxmsp25yOAIpIaPSKofohYP4
hbSi3qe/ELUm747/evHj6/en0RsP4jewteFNMddX3n735uLkx+O/nlz8+PLk
/MhSuX9lmo1lSm/eHx2++fH07PiV+cCj+GnyygMjvtJlXLx/e3LksYiP6Z3H
jWXUYCuO9IWQrhA+8qTxgiR4YD9dZNB/sFvHyfNEY+GyRcxHWarv6aSXJrxq
5AWrgveVFzSk27LZJNs8uYHaCWuukFlPz51p3R17dTpvzDqBgKSgMvc11RPL
NOQ7/uoAgVbXN/REVpbMh5G0bZ6TfRV/Pwgvo0SBAfRVeDGucYi/+iC8yNIl
fjUUZYIKw0B4/psPw6uYGIY64//f3LG2tBEEv++vuOZTAjExaqUvCpZaCLQg
TVsLpZSYRA1YDbn4KObH9+a1O3u7t3c1Iu03qzs3uzszO+9Zzu4WanV1ie3a
cdn9/Wn+Wy2iVKH4Xey7RRP4M7vs/2QYSYN6GM/wau954v+TeZ0nzipRNpEY
2RR8BXUVJhMtjWZFwvk6V5CuqRIbI9e61S6D65mGXAvxQIwyIPNiKyzFtnIm
rW4mjZA5bOzXxNn4rMMa2hDjNZuNrlkZcmaTa8bTkK1jydz1id0CVqFYhdon
B7tRI6ZuVC5IMQ/kDMUU4iXmyZCHQX9a69SVEKNS0vhSshZOjexU4rOx9FRy
M6ZQgzS7tOl4se9te+9qIElBwLi4N2QMjf5cTs6XV1SDZeVwCsC7sSuCY3tO
Y7DzTwBQe/O3sFsD4DEpL/KobER3aXjxt7lEdgkQ9QQXpTj+TR3hJSgPdcsk
5QWk573DTLg2nU0y3ji1KgsJL1gORHMEUbGDUfTrO/XLS3mVCaJLIh+mZa9L
hmSw/IfzZfyMIf/cW07OxkGx9kDqSA5YlbmEEOWCvNFWOXFw9tNoVGUN2oHL
a1DMZflkvMBiFVLJH5HpogrZRmxXB7ER4yWBNGA9OPmHM5/ju7jDL819eOvI
gb6zxLv+T27QjzXlP8Ijr0AM0iC+6ordY5cP7AC2nf+3wwZuCqU5deWLgvJg
MX67aXglXzlfYhmO2u9eU3j80iUBsvWcgAdFMRfzqXgP4sem4e2n4aUFS2Zt
7XrRIphZp0MStwLsizRmVko6OImzK+C9bHZy3K68MK4g+c7b6aA5/bMvpoow
GF6SGYy0Q7LmAJWAa7lUbQFa8djqxQND7O8lmKopA8ew+Sttmgx8A2W1F10e
hTqd38ynMLsTbSXMaMs7EV+xGphQuQOuXInZbfnT7kDWCSRBProznHtGdzzi
riLsK31AFC4K6QnDcN8o4L2NJhj0baHGKxg/nfYy/vWAfl2K1RlxKv7KZ2fo
8AdT74vYcXkhUGHZXjcrW/88uVGa4xluWwJ9eNyMUhcYs71ObCkPHQmU0lL9
mHGzIhF/TGuZeh3vllg5ihEpagLTydy7W8gIeV5dGA0002qDqcE/0ovoLFGJ
XZO28F60BfbdwiY8cQEa6zqr+mPeKeilFQDLAzRBB117R1/+wwCBvcgCtRcg
lfDjwBvWVAl1WeGTY5l1iIPRJl4uPRUqIifZaBuSE1EnNe0rx/xwEiLys2Wa
OixaRvixl1XhUxrwZTsMc3q+sS0UXqPDp5uMrvmyCrXOU0xwCdqWFof4mXAb
q2oBN6clUJcDyaJ0cHLeQkJirr9v5rq4ZsQVdVqTDYtwIvszif2Vt9X8cMBJ
5ZX48K2a2lt1RyEHPAt2JiesS62D+v40umOq6/BrtbHE3BfapoHQthjTTC9F
GFm5oX6F8UKl9lGcMo3U8Ajar96aoeo7dniHWUrt4dGH4fdOdgjRgLk+R8Jq
vDLnq9Uif9Xv397e9iAdpXe1POsrb2F/vjgtVD70PPp4lE//zbOtLZj9qMpz
7czFUkUutFfjspy80MkKNtCN4sY5plFAm7Y2JLROjF4LVUELyAHMC5kPDWPc
yh5UrsOPdy1XimMbK0BmSfHsUFrx+AIyA7kXiCRcSXs6tv786s8cPoRp/Rod
6mRomUvKvL3tYM4qQZ569crGzFYTmJz51vwFvufusNeYAwA=

-->

</rfc>
