Routing Policies – Knowledgebase

Knowledgebase Contents

Overview

Inter.link offers a pan-european 100G network with high-quality connectivity to carriers, content providers, and internet exchanges.

This section of the knowledgebase explains Inter.link’s routing policies. Routing policies are sets of rules that control how network traffic and data packets are forwarded, filtered, and processed.

General

  • Prefixes with RPKI validation-state invalid are dropped (except RTBH prefixes)
  • Prefixes with RPKI validation-state valid are accepted unconditionally
  • Only prefix lengths between /8 – /24 for IPv4 and /19 – /48 for IPv6 are accepted (except RTBH prefixes)
  • Bogon prefixes and Bogon ASNs are rejected on ingress
  • Strict prefix filtering based on IRR data is applied on all BGP sessions
  • This includes both prefix and ASN (AS Path Validation) filters
  • Mirrored IRR databases: APNIC, AFRINIC, ARIN, RIPE, LACNIC, RADB
  • Inter.link does not accept prefixes registered in other IRRs (e.g. NTTCOM, ALTDB, etc.)
  • Maximum accepted AS-Path length is 50
  • “Tier-1” ASNs in the as-paths from downstreams and peers are rejected
  • The first ASN (left most) in the AS-Path must equal the peer ASN
  • Inter.link does not use route-dampening
  • The Multi-exit Discriminator (MED) set by customers is honored. If unset the lowest (best) value 0 is used
  • Prefix filters are updated once a day every night at 4 AM CE(S)T / UTC +1 (CET) or UTC +2 (CEST)