Participant Info

  • LocationCA
  • Network ASNs26268
  • IX-F IDs882

Implementation of MANRS Actions

  • Action 1: Filtering of Route Announcements Drop small prefixes – longer than /24 for ipv4 and longer than /48 for ipv6. Drop all well-known martians and bogons. Ensure that there is at least 1 ASN and less than 64 ASNs in the AS path. Ensure that the peer AS is the same as the first AS in the AS path. Drop any prefix where the next-hop IP address is not the same as the peer IP address. This prevents prefix hijacking. Drop any prefix with a transit network ASN in the AS path. Ensure that origin AS is in set of ASNs from the client’s IRRDB AS-SET. If the prefix is evaluated as RPKI valid, accept. If the prefix is evaluated as RPKI invalid, drop. If the prefix is evaluated as RPKI unknown, revert to standard IRRDB prefix filtering.
  • Action 2-1: Offer assistance to its members to maintain accurate routing information in an appropriate repository (IRR and/or RPKI) Resources and help with setting up IRR and RPKI
  • Action 2-2: Offer assistance in implementing MANRS ISP Actions for the members
  • Action 2-3: Indicate MANRS participation on the member list and the website MANRS badge on member list
  • Action 3: Protect the peering platform
  • Action 4: Facilitate global operational communication and coordination between network operators
  • Action 5: Provide monitoring and debugging tools to the members