Bi-lateral peering is considered best practice !
While the BGP Route Server service is made available as a convenience, it is strongly recommended that, in addition to any sessions you plan to establish with the BGP Route Servers, you still maintain direct bi-lateral peering sessions with peers that you feel are important to your network! BGP Route Servers should be used to pickup quick/easy/additional peers only, and not as a replacement for your discrete peering policy!
In particular there are many peers that advertise only a subset of their prefixes to the BGP Route Server. Always aim for a bilateral session !
There are two BGP separate route servers on each peering LAN. It is recommended to always peer with both BGP Route Servers at a location, as sessions to both servers ensure that there is no disruption to your routing should it be necessary to performance maintenance. The Route Servers do not peer with each other, so peering with only one server is an unnecessary risk.
Ensure that if you do plan on peering with the BGP Route Servers, you understand that the BGP-RS does not attach its ASN to outbound BGP messages.
Please implement the IOS "no bgp enforce-next-as" (or IOS-XR "enforce-first-as disable"), or appropriate equivalent, for your platform.
Filtering policy and process
INX has always believed in filtering and we filter all client sessions to the BGP-RS service. We encourage peers to keep their IRR objects accurate to help us to autogenerate these filters.
- Filters are built based on IRRDB registered objects.
- Filter generation happens automatically at 04h00 SAST daily.
- We search the AfriNIC, RADB and RIPE registries (in that order).
- We permit more specific (longer match) paths for IPv4, but not for IPv6.
- Some prefixes are automatically filtered by the route servers (eg. bogons and martians).
- We do not accept BGP announcements from private ASNs
BGP Communities for policy control
A simple set of BGP communities are made available for rudimentary policy control. These will be expanded on, as the BGP Route Server service is improved.
Remember to use the correct ASN
|0:peer-asn||deny to peer-asn||block announcement of prefix to peer-as|
|0:37700||block all||block announcement of prefix to all peers|
|37700:peer-asn||allow to peer-asn||announce prefix to specific peer-as (in conjunction with block all)|
|37700:37700||allow all||announce prefix to all peers (implicit default)|
We honour the well-known no-export and no-advertise communities as if they were sent to us as a regular peer. If you would specifically like us to propagate these, then please tag as below:
|37700:65281||add no-export||adds the well known no-export community to all routes sent to peers|
|37700:65282||add no-advertise||adds the well known no-advertise community to all routes sent to peers|
BGP Large Community Support for policy control
|37700:0:peer-asn||deny to peer-asn||block announcement of prefix to peer-asn|
|37700:1:0||block all||announce prefix to specific peer-as (in conjunction with block all)|
|37700:0:peer-asn||allow to peer-as||block announcement of prefix to all peers|
|37700:1:0||allow all||announce prefix to all peers (implicit default)|
Individual network filtering
The BGP route servers do not add their own ASN in the advertised path, so if you're planning on constructing a filter list to filter the BGP Route servers, do not use the BGP route servers ASN in the path!
We do not yet publish a route object for the route-servers. We will add that in the future, so, for now, please reach out to the Ops team to see how to do this most efficiently.
Prefixes auto-filtered by the Route Servers
For the overall safety and security of our participants, we actively filter the following prefixes at the Route Servers. That is, advertisements from peers, containing the following networks, will be dropped, and not onward announced.