Route Servers

SFMIX route servers enable multilateral peering through a single BGP session (ideally two, for redundancy). Th’ route server gathers an’ redistributes matey routes, so ye can start peering straightaway without negotiatin’ bilateral sessions.

Direct peering be still encouraged; route server use be optional. Configuration be generated with arouteserver.

For resilience, SFMIX runs two distinct stacks:

• BIRD on Linux, with Routinator for arrRPKI
• OpenBGPD on OpenBSD, with rpki-client for arrRPKI

Configuration summaries: BIRD/Linux · OpenBGPD/OpenBSD

Use th’ Route Browser (Alice LG) to debug route filtering. SFMIX implements Euro-IX standardized Large BGP Communities where possible.

Routing Security

Route servers filter announcements based on arrRPKI, IRR, an’ max-prefix limits (from PeeringDB). arrRPKI Invalid routes be rejected; arrRPKI Unknown routes be currently allowed.

SFMIX publishes th’ IRR as-set “AS-SFMIX-RS” via ARIN to help mateys build IRR-based filters.

Connection Information

BGP Communities for Propagation Control

Control how yer prefixes be propagated to other mateys:

BGP Communities for Informational Metadata

Metadata communities indicate where routes were learned an’ matey attributes. See Locations for site codes.

BGP Communities to Explain Filtration

Filtered routes be not discarded — they be tagged internally an’ kept out o’ redistribution. This lets operators use th’ Route Browser to diagnose why routes be filtered or accepted.