Participant Info

  • Areas ServedUS
  • ASNs11232 16739 18817 11055

Implementation of MANRS Actions

  • Action 1: Prevent propagation of incorrect routing information Customer BGP sessions are filtered to accept only authorized announcements. Announcements to peers and transit are controlled via BGP communities. as-set is maintained to allow ingress filtering by adjacent networks.
  • Action 2: Prevent traffic with spoofed source IP addresses Midco implements data plane filtering to prevent routing traffic with a spoofed source address to the global Internet.
  • Action 3: Facilitate global operational communication and coordination Contact information is available from well known sources such as ARIN and peeringDB.
  • Action 4: Facilitate validation of routing information on a global scale Midco allocations have route(6) objects in the ARIN IRR database. Midco ensures that transit customer prefixes have matching route(6) objects in an IRR database from the following list: AFRINIC, APNIC, ARIN, LACNIC, RIPE, RADB, LEVEL3, NTTCOM. Midco RIR allocations and more specifics have ROAs.