BOSIX Configuration Guide

BOSIX has deployed a pair of Juniper Networks MX204 routers to act as redundant BGP route servers – as described in RFC 7947 – in order to facilitate multilateral interconnection among its clients. By peering with these routers, a client may exchange BGP announcements with the other clients also peering with the route servers. Clients still maintain the ability to control the announcement of each route to individual ASNs through the use of BGP communities described below.

Announcement Filtering

Routes received from clients will be filtered in accordance with best practices for Internet BGP Route exchange. Specifically, routes will be checked to avoid:

• Routes longer than a /24 for IPv4 or a /48 for IPv6
• Any bogon/martian routes
• Any Boston IX subnets, specifically the 206.108.236.0/24 network
• Routes containing bogon ASNs
• Routes whose AS path begins with a different ASN than the peer’s ASN (excepting AS-SETs)
• Routes whose AS path contains more than 32 hops
• Routes longer than a /8 for IPv4 or a /19 for IPv6
• Default routes for either IPv4 or IPv6

Additionally, your incoming routes will be checked against the Merit RADb IRR so ensure that your routes are registered correctly. Updates will be pulled twice daily, at 06:00 and 18:00 EST, so please ensure that any new routes that you wish to advertise are registered in time for the appropriate update or else they may not be available for up to 14 hours.

Route Announcement Control

As noted above you maintain control over who your routes are advertised to. If you would like all of your routes to be advertised to all route server peers tag all the routes with the BGP community 17360:17360. Routes may also be tagged with the other communities in the table below in order to selectively allow or block advertisement of each route to all peers or specific peers.