Nexril (AS13830) Peering Policy


Peering Requirements

  • Have a publicly routable ASN with IP space (at least one /24 or one /48).
  • Maintain an up-to-date and valid PeeringDB entry.
  • Have a NOC that is able to respond quickly to routing issues and abuse complaints.
  • Peer in all common facilities and/or exchanges.
  • Never point a default or static route towards our network: only traffic from advertised prefixes may be routed towards us.
  • We do not have a minimum traffic requirement.

Peering Filter Policy

  • A prefix-set will be rebuilt every 12 hours based on the peer's IRR record.
  • Bogons from RFC6890 will be dropped, regardless of inclusion within the prefix-set.
  • IPv4 prefixes le 7 or ge 25 (apart from /32 RTBH) and IPv6 prefixes le 15 or ge 49 (apart from /128 RTBH) will be dropped, regardless of inclusion within the prefix-set.
  • Prefixes with invalid RPKI origins will be dropped, regardless of inclusion within the prefix-set.
  • Prefixes with valid RPKI origins and an AS Path that matches the peer's as-path-set will be accepted, regardless of inclusion within the prefix-set.
  • Prefixes within the peer's prefix-set will be accepted.
  • We will only announce prefixes originating from our AS or a downstream customer AS to peers, unless said prefixes include export control communities.
  • We will only export received prefixes to our downstream customer AS's, unless said prefixes include export control communities.

Customer Filter Policy

  • A prefix-set must be manually generated using a list of validated prefixes supplied by the customer.
  • Bogons from RFC6890 will be dropped, regardless of inclusion within the prefix-set.
  • IPv4 prefixes le 7 or 25 (apart from /32 RTBH) and IPv6 prefixes le 15 or ge 49 (apart from /128 RTBH) will be dropped, regardless of inclusion within the prefix-set.
  • Prefixes with invalid RPKI origins will be dropped, regardless of inclusion within the prefix-set.
  • Prefixes within the customer's prefix-set will be accepted.
  • We will announce prefixes originating from our transit, peering, and other customer sessions to customers, unless said prefixes include export control communities.
  • We will export received prefixes to our transit, peering, and other customer sessions, unless said prefixes include export control communities.

BGP Communities


  • Communities marked with may be used by customers.
  • Communities marked with may be used by peers.
  • Communities marked with support extended route target (rt:) communities in addition to normal communities.
  • All communities except those listed below are stripped from customer and peer announcements. Large communities are not supported at all and will be stripped.
  • Origin communities are purely informational.

Local Preference

13830:80   Local Preference = 80 (Below Transit)
13830:110   Local Preference = 110 (Below Peers)
13830:125   Local Preference = 125 (Below Customers)
13830:135   Local Preference = 135 (Above Customers)

AS Prepend

65001:n   Prepend AS13830 1x to n (use n=0 for all)
65002:n   Prepend AS13830 2x to n (use n=0 for all)
65003:n   Prepend AS13830 3x to n (use n=0 for all)
65004:n   Prepend AS13830 4x to n (use n=0 for all)

Blackhole

13830:666   BGP Blackhole (/32 IPv4 or /128 IPv6 Only)

Do Not Export

13830:2001   Do not export to customers
13830:2002   Do not export to peers
13830:2003   Do not export to transit providers
65100:n   Do not export to n (use n=0 for all)
65200:n   Do not export to anyone except n
65300:n   Send "no-export" to n (use n=0 for all)

Origin Communities

13830:3000 Internal Route
13830:3001 Customer Route
13830:3002 Peer Route
13830:3003 Transit Route
13830:4000 Route learned in Dallas, Texas
13830:5000 Route learned in North America


Examples

65001:0 Prepend AS13830 1x to all customers, peers, and transit providers.
65002:174 65003:29802 65004:0 Prepend AS13830 2x to AS174, 3x to AS29802 and 4x to all other customers, peers, and transit providers.
65200:174 65200:29802 Only export routes to AS174 and AS29802.
65200:174 65200:29802 65300:174 Only export routes to AS174 and AS29802, in addition send the no-export community on routes exported to AS174.
13830:666 65200:174 Announce RTBH route to AS174 only.
65100:62499 Do not export to DE-CIX Dallas route servers.
65100:13335 Do not export to AS13335.
Note: AS13335 may still receive this prefix over IX route servers.