Systems and protocols · Intermediate

BGP: exchanging reachability under routing policy

Follow prefix advertisements and AS paths without confusing policy-driven route selection with geographic or latency optimization.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. Advertisements and forwarding are different
  2. Trace an AS path
  3. Selection reflects administrative policy
  4. Operational and trust boundaries
  5. Ask Logeia about this articleCheck your understanding

Advertisements and forwarding are different

BGP exchanges reachability for IP prefixes, especially between autonomous systems. An advertised route carries attributes such as an AS path, and receivers apply their own selection and export policies. The control-plane session is not the channel carrying every user packet. Actual forwarding depends on the resulting routing and forwarding state, including resolution of the next hop. Seeing an advertisement is therefore different from proving that application traffic can traverse the entire route. Separate the information received from the policy decision and from the eventual packet-forwarding behavior.

Trace an AS path

Imagine AS 64500 advertising 203.0.113.0/24 through AS 64501 to AS 64502. The receiver can inspect the sequence of autonomous systems through which the route was advertised. Rejecting paths that already contain the local AS helps prevent AS-level loops. However, the path is not a distance in kilometers, nor does a shorter list guarantee a smaller round-trip time. The example uses illustrative autonomous-system numbers and a documentation prefix. Its purpose is to trace how path information changes, not to describe an actual Internet relationship.

Selection reflects administrative policy

Two neighbors can advertise the same prefix while the local operator prefers one relationship for commercial or operational reasons. A LOCAL_PREF decision within an AS can take precedence over comparing AS-path lengths, so describing BGP as simply choosing the shortest path is misleading. Eligibility and implementation-specific decision details also matter. Import policy and export policy answer different questions: accepting a route does not imply permission to advertise it to every other neighbor. An unintended export can influence traffic well beyond the system where the policy mistake originated.

Operational and trust boundaries

An Established session does not imply that a particular route was accepted, installed or usable. Inspect neighbor state, received attributes, policy outcomes and forwarding entries in sequence. The base protocol does not cryptographically establish that every origin is authorized to announce every prefix; route-origin validation and related operational controls are additional mechanisms. Convergence also takes time after failures and policy changes. A single routing-table snapshot cannot describe the entire transition. Compare observations at known times and distinguish control-plane session health from correct, authorized and usable reachability.

Reading and practice are recorded separately in this browser, for each language.

Learn this in order

Understand the systems behind the web · STEP 9

Choose a learning path