Skip to content
Home

Border Gateway Protocol (BGP) — the Internet's interdomain routing protocol

BGP is the protocol that exchanges routing information between autonomous systems on the Internet. It determines interdomain paths, supports policy-based routing, and underpins global connectivity.

Overview

The Border Gateway Protocol (BGP) is the standardized routing protocol used to exchange reachability information between separate administrative networks, called autonomous systems (ASes). Unlike protocols that compute shortest paths, BGP is policy-driven: operators express preferences and constraints that influence how traffic flows across the global Internet. Although most end users never see BGP directly, it is fundamental to how data travels between service providers, enterprises, content networks, and exchange points. For more introductory material see background.

How BGP works — main concepts

BGP is a path-vector protocol: routes are advertised with attributes that describe origin, the sequence of ASes traversed (AS_PATH), and other metadata used to select and filter routes. Peering sessions run over TCP and exchange four basic message types: Open, Update, Notification and Keepalive. Operators separate BGP into external BGP (eBGP) for inter-AS links and internal BGP (iBGP) for routes shared inside an AS. Typical components and attributes include:

  • AS_PATH — chain of autonomous systems a prefix traversed;
  • Next-hop — the next router to reach a prefix;
  • Local preference, MED, communities — policy knobs used to prefer or de-prefer routes;
  • Route reflectors and confederations — mechanisms to scale iBGP within large networks.

History and development

BGP evolved to replace older interdomain routing approaches as the early Internet grew beyond simple, centrally coordinated topologies. Its design emphasizes scalability, administrative control and the ability to express routing policies rather than purely technical metrics. Over time BGP received extensions to support Classless Inter-Domain Routing (CIDR), route aggregation, multiprotocol extensions (for IPv6 and VPNs), and operational practices that improved stability at large scale.

Uses, examples and importance

BGP is used by internet service providers (ISPs), large enterprises, content delivery networks and cloud providers to announce which IP address ranges they serve and to control the ingress and egress of traffic. Common real-world uses include multihoming (connecting to more than one provider for redundancy), traffic engineering (shaping flows via local preference and MED), and peering at Internet Exchange Points. Operators often consult route viewers and policy documentation at operator portals such as external resources while configuring relationships with peers.

Challenges, security and best practices

BGP was not originally designed with strong cryptographic security, so misconfiguration or malicious announcements can cause traffic misdirection or large outages. Notable issues include route leaks and prefix hijacks. Mitigations include prefix filtering, RPKI-based origin validation, careful peering policies, and emerging standards for stronger validation. Network operators and researchers continually refine operational practices to reduce accidental disruptions. Practical guidance and operator toolsets are discussed in many community-maintained documents and training resources such as operator guides.

Notable distinctions and facts

Unlike interior routing protocols that favor shortest-path metrics, BGP prioritizes policy and stability. Route selection follows a predictable sequence of attribute comparisons, but final decisions reflect human-defined policies. Because BGP ties together independently managed networks, it is sometimes described as the protocol that "glues" the Internet together: small changes in one AS can have global impact, which makes careful design and coordination essential for a resilient global routing system.

Related articles

Author

AlegsaOnline.com Border Gateway Protocol (BGP) — the Internet's interdomain routing protocol

URL: https://en.alegsaonline.com/art/13073

Share