Listen "BGP Policies (Part 4)"
Episode Synopsis
At the most basic level, there are only three BGP policies: pushing traffic through a specific exit point; pulling traffic through a specific entry point; preventing a remote AS (more than one AS hop away) from transiting your AS to reach a specific destination. In this series I'm going to discuss different reasons for these kinds of policies, and different ways to implement them in interdomain BGP.
In this post, I'll cover the first of a few ways to give surrounding autonomous systems a hint about where traffic should enter a network. Note this is one of the most vexing problems in BGP policy, so there will be a lot of notes across the next several posts about why some solutions don't work all that well, or when they will and won't work.
There are at least three reasons an operator may want to control the point at which traffic enters their network, including:
More episodes of the podcast TECH – rule 11 reader
Hedge 218: Longer than /24’s
21/03/2024
Hedge 144: IPv6 Lessons Learned
25/08/2022
Route Servers and Loops
16/08/2022
BGP Peering (2)
15/08/2022
Hedge 135: Simon Sharwood, China, and IPv6
22/06/2022
BGP Intra-AS and Route Reflection
21/06/2022
Revisiting BGP Convergence
06/06/2022
How BGP Really Converges
31/05/2022
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.