Participant Info

  • Areas ServedUS
  • ASNs14361

Implementation of MANRS Actions

  • Action 1: Prevent propagation of incorrect routing information prefix-list filter out at all BGP peers for route announcements, only allowing our and our customer routes out. Also prefix-list filter in on all BGP customer peering sessions, only allowing their routes in. Verification of prefix ownership by customer or customer of customer of all BGP customers. In addition, communities tags used to tag and filter prefixes also.Everything is published in RADB. See RADB::AS14361.
  • Action 2: Prevent traffic with spoofed source IP addresses ACLs in place on all VLANs that only allow in and out traffic to and from the IPs on the VLAN and deny all else.
  • Action 3: Facilitate global operational communication and coordination Up-to-date information on RADB & in PeeringDB (AS14361).
  • Action 4: Facilitate validation of routing information on a global scale Everything is published in RADB. See RADB::AS14361.

Why HopOne Internet Corp. Supports MANRS

MANRS documents what we have been doing for well over a decade - ever since the early 2000s. Namely, having multiple layers of protection (communities, prefix-lists, AS-path filters) to avoid route leaks, spoofed IP traffic, and to clearly communicate our routing policy to our peers and enable them to build their own prefix and AS-path lists for us off the RADB entries dynamically.

{Contact Job Title:9}, {Organization Name:1}