BGP
Border Gateway Protocol is the routing protocol that connects autonomous systems on the internet. It exchanges reachability information between networks so that traffic can find a path from any source to any destination across independently operated infrastructure.
itNetworking | OpenSkills.info
Intro
BGP
The Internet is not one network. It is a network of networks, each run under its own policy. Border Gateway Protocol, or BGP, is how those networks exchange reachability information.
BGP answers a practical question: which neighboring network should receive traffic for a destination prefix? It carries possible paths and enough attributes for each network to apply its own policy. That makes BGP different from an interior routing protocol. An interior protocol usually seeks efficient paths inside one administration. BGP coordinates paths between administrations that may have different technical and business goals.
The core mental model
Think of a BGP route as a claim with context:
I can reach this IP prefix through this path, and here are attributes you can use when deciding what to do with the claim.
A BGP speaker sends that claim to a configured peer. The receiving speaker applies import policy. It rejects or accepts the route, compares accepted routes, and selects a preferred route. It may then apply export policy and advertise a route to other peers.
That flow matters more than any vendor command:
peer advertisement
↓
import policy
↓
candidate routes
↓
decision process
↓
selected route
↓
export policy
↓
advertisement to another peer
BGP does not discover peers automatically. Operators configure the neighbor relationship and the policy around it. Modern default-reject behavior requires explicit import and export policy before an external BGP session can use or advertise routes.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.rfc-editor.org/rfc/rfc4271.html
Supports
- BGP as an inter-autonomous-system routing protocol
- Autonomous system, eBGP, iBGP, peer, route, prefix, and BGP speaker definitions
- TCP port 179 and OPEN, UPDATE, KEEPALIVE, and NOTIFICATION messages
- Incremental updates after initial routing exchange
- Adj-RIB-In, Loc-RIB, and Adj-RIB-Out conceptual stores
- AS_PATH loop detection and base path attributes
- LOCAL_PREF, MED, NEXT_HOP, ORIGIN, and decision-process behavior
- Full-mesh iBGP assumption and next-hop resolvability
- https://www.rfc-editor.org/rfc/rfc1997.html
Supports
- Communities as route labels used by policy
- NO_EXPORT, NO_ADVERTISE, and NO_EXPORT_SUBCONFED propagation behavior
- https://www.rfc-editor.org/rfc/rfc4456.html
Supports
- Route reflection as an alternative to full-mesh iBGP
- Route-reflector client and non-client behavior
- ORIGINATOR_ID and CLUSTER_LIST loop controls
- Best-path visibility and topology effects on route selection
- https://www.rfc-editor.org/rfc/rfc6793.html
Supports
- Expansion from two-octet to four-octet AS numbers
- Four-octet ASN capability negotiation
- AS4_PATH, AS4_AGGREGATOR, and AS_TRANS compatibility mechanisms
- https://www.rfc-editor.org/rfc/rfc7454.html
Supports
- Prefix and AS-path filtering by peer relationship
- Maximum-prefix limits and the need to review thresholds
- BGP session and control-plane protection
- Communities and next-hop filtering
- Layering route-origin validation with other operational controls
- https://www.rfc-editor.org/rfc/rfc8212.html
Supports
- Explicit import and export policy requirement for eBGP
- Received routes remaining ineligible without import policy
- Routes remaining absent from Adj-RIB-Out without export policy
- Permissive defaults as a route-leak risk
- https://www.rfc-editor.org/rfc/rfc6811.html
Supports
- Validated ROA payload fields
- Valid, Invalid, and NotFound origin-validation states
- Validation of prefix, length, and origin ASN
- Origin validation not providing complete AS-path attestation
- https://www.rfc-editor.org/rfc/rfc9234.html
Supports
- Route leaks as propagation contrary to expected relationships
- BGP Role capability and external peer relationship roles
- Only to Customer attribute for route-leak prevention and detection
