To join in RTIX write to **help@ria.ee** # Community based prefix filtering The RTIX route server system also provides well known communities to allow members to control the distribution of their prefixes. These communities are defined as follows: - Prevent announcement of a prefix to a peer: **0:peer-as** - Announce a route to a certain peer: **1:peer-as** - Prevent announcement of a prefix to all peers: **0:0** - Announce a route to all peers: **1:1** To instruct the route servers to distribute a particular prefix only to AS64111 and AS64222, the prefix should be tagged with communities: **0:0**, **1:64111** and **1:64222** Alternatively, to announce a prefix to all RTIX members, excluding AS64333, the prefix should be tagged with community **0:64333**. The RTIX route server supports BGP large community prefix distribution control, using the following policy: - Prevent announcement of a prefix to a peer: **207800:0:peer-as** - Announce a route to a certain peer: **207800:1:peer-as** - Prevent announcement of a prefix to all peers: **207800:0:0** - Announce a route to all peers: **207800:1:1** ## Filtering Policy 1. Drop all well-known martians and bogons. 2. Ensure that the peer AS is the same as the first AS in the AS path. 3. Drop any prefix with a transit network ASN in the AS path. 4. If the prefix is evaluated as RPKI valid, accept. 5. If the prefix is evaluated as RPKI invalid, drop.

ok

2024-01-24T04:50:42Z