A Border Gateway Protocol 4 (BGP-4), January Canonical URL: https:// ; File formats: Plain Text PDF; Status: DRAFT. Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to RFC corrected errors, clarified ambiguities and updated the. RFC (part 1 of 4): A Border Gateway Protocol 4 (BGP-4).

Author: Kagabei Grobei
Country: Iran
Language: English (Spanish)
Genre: Health and Food
Published (Last): 13 March 2012
Pages: 397
PDF File Size: 5.40 Mb
ePub File Size: 1.72 Mb
ISBN: 183-3-91413-152-9
Downloads: 68953
Price: Free* [*Free Regsitration Required]
Uploader: Bragor

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. Such cases will increase the number of routes as seen on the global BGP table. New text Section 6.

This eliminates the need to implement explicit update fragmentation, retransmission, acknowledgement, and sequencing.

While the reported number of IPv6 advertised routes was only about 20k, the number of advertised IPv4 routes reached the default limit, causing a spillover effect as routers attempted to compensate for the issue by using slow software routing as opposed to fast hardware routing via TCAM. Archived from the original on They exchange messages to open and confirm the connection parameters.

The exact nature of this policy information, and the computation involved, is a local matter. This optimization is entirely optional. 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.

The suggested default value for the ConnectRetryTime is seconds. BGP may be used for routing within an autonomous system. To ensure that Hold Timers are symmetric, the Hold Timer is now negotiated on a per-connection basis.

Supported Standards for BGP

While it is common to say that BGP allows an administrator to set policies on how prefixes are handled by ISPs, this is generally not possible, strictly speaking. If a router is misconfigured or mismanaged then it may get into a rapid cycle between down and up states.

This network reachability information includes information on the list of Autonomous Systems that reachability information traverses. 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.

Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights.


For example, 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.

The additional information tells the BGP process such things as whether individual entries belong in the Adj-RIBs for specific neighbors, whether the peer-neighbor route selection process made received policies eligible for the Loc-RIB, and whether Loc-RIB entries are eligible to be submitted to the local router’s routing table management process.

BGP is an inter-Autonomous System routing protocol.

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. A compliant implementation must support this mechanism, and must allow a network administrator to activate it on a per-peer basis.

RFC – part 1 of 4

RFC corrected errors, clarified ambiguities and updated the specification with common industry practices. This requires a reboot on most routers. Note that some bfp cannot be supported by the destination-based forwarding paradigm, and thus require techniques such as source routing aka explicit routing to be enforced.

The full operation of these optional timers is outside the scope of this document. For each newly received or replacement feasible route, the local BGP speaker determines a degree of preference as follows: After verifying that the next hop is reachable, if the route comes from an internal i. If AS1 later decides to drop the route If unsuccessful, it starts the ConnectRetry timer and transitions to the “Active” state upon expiration. In common practice, [14] only one of the confederation AS numbers is seen by the Internet as a whole.

BGP neighbors, called peers, are established by manual configuration among routers to create a TCP session on port Views Read Edit View history.

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 471 describing a larger set of destinations is said to be less specific than a route describing a smaller set of destinations.

IGP routes and routes to directly connected networks are expected bhp specify the outbound interface. These side-effects would quite likely be worse than the impact caused by simply not running flap damping at all.


Information on RFC ยป RFC Editor

The following list the technical changes: Another application of MEDs is to advertise the value, typically based on delay, of multiple AS that have presence at an Bpthat they impose to send traffic to some destination. 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.

This segment is then placed between the two consecutive ASes identified in a of rcc aggregated attribute. 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.

These mechanisms include support for advertising a set of destinations as an IP prefix and eliminating the concept of network “class” within BGP.

Multiprotocol BGP allows information about the topology of IP multicast-capable routers to be exchanged separately from the topology of normal IPv4 unicast routers. A given BGP speaker MAY apply the same jitter to each of these quantities, regardless of the destinations to which the rtc are being sent; that is, jitter need not be configured on a per-peer basis.

Because the mechanism defined in the RFC does not provide peer-entity authentication, these connections may be subject to some forms of replay attacks rc will not be detected at the TCP layer. After the abnormalities have ceased and a suitable length of time has passed for the offending route, prefixes can be reinstated and its slate wiped clean. In the “OpenSent” state, the router sends an Open message and waits for one in return in order to transition to the “OpenConfirm” state.

Bfp first decision point for evaluating NLRI is that its next-hop attribute must be reachable or resolvable. The BGP design is such that delivery of traffic may not function rcc routes are being updated.

Retrieved March 16, 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.

Subscribe US Now