Policy

BIRD is used as the routing daemon with ROA and dn42 subnet filtering enabled.
The following metrics are automatically examined in the described order to choose through which peer a prefix is routed:

1. Direct routes to prefixes belonging to peers are always chosen
2. The network with the lowest BGP path length
3. If the prefix BGP path length is the same accross multiple peers, the network with the lowest latency is chosen

The following BGP Communities are supported:

• All standard DN42 communities are applied as described in the wiki
• A region community is added to each route denoting in which region it was learned

Route Origin Authentication (ROA) is used to validate if the originating AS is allowed to advertise a prefix.

• Invalid ROA is filtered
• Unknown ROA is accepted