How can we help you?
Frequently searched topics
home/ Network/ Routing Policy
RETN no longer accepts or redistribute BGP route announcement considered “invalid” upon Origin Validation process (RFC 6811). Customers owning IP resources are welcome to certify which ASes are authorised to originate their IP prefixes creating Route Origin Authorisations (ROAs) using the services from the different Regional Internet Registries and National Internet Registries (i.e. RIPE).
BGP Filter Policy
RETN accepts prefixes from peers of the following size:
RETN does not accept prefixes that are labelled as “Reserved”
RETN does not accept prefixes (including more specific) of peers we currently peer within Public Internet Exchanges.
RETN accepts from Customers only routes registered in:
Routes registered in ARIN, AFRINIC and LACNIC can be accepted too: customers need to request this specifically.
Routes registered on other IRRs will NOT be accepted.
RETN accepts prefixes from customers of the following size:
between /8 and /29 included for IPv4
between /16 and /48 included for IPv6
Prefix-limit is configured as group-level for peers on Public Internet Exchanges (IXP) by default: it will be applied if there is not a personal (neighbour-level) limit configured on the specific peer.
Prefix-limit for private peers is configured as neighbour-level, only for those peers that do regularly announce more than half the number of prefixes present on the group level.
IPV4 prefixes longer than /29 will not be announced externally and will only be visible within RETN Network.
IPV6 prefixes longer than /48 will not be announced externally and will only be visible within RETN Network.
RETN is not accepting so-called private IP address blocks (RFC 1918) from our customers or peer, and do not advertise them to any network RETN is interconnected with.
RETN uses Route Dampening
RETN accepts MEDs from customers with more than one connection in more than one location.