- Areas ServedUS
Implementation of MANRS Actions
- Action 1: Prevent propagation of incorrect routing information 3ROX performs prefix-based ingress filtering on downstream BGP sessions.
- Action 2: Prevent traffic with spoofed source IP addresses 3ROX uses firewall filters (or the equivalent) on downstream interfaces to restrict source addresses to those expected by the BGP announcements (or static configuration). There are a few exceptions with private peering sessions, but traffic to transit and peer R&E networks is clean.
- Action 3: Facilitate global operational communication and coordination Full contact information for 3ROX is in our PeeringDB entry; partial, but accurate contacts are in ARIN and RADB.
- Action 4: Facilitate validation of routing information on a global scale 3ROX uses the RADB to record route, route6 and aut-num objects for the prefixes and ASNs we announce.
Why Three Rivers Optical Exchange (3ROX) Supports MANRS
For a number of years, we have been doing most of the components of MANRS, perhaps in a rather haphazard fashion. Joining MANRS provides us with motivation to do things with a little more rigor.