Passive sessions are configured toward neighbors.
GTSM (Generalized TTL Security Mechanism - RFC5082) is disabled on sessions toward the neighbors.
ADD-PATH capability (RFC7911) is negotiaded by default; the route server is configured as "able to send multiple paths to its peer".
Route server ASN is not prepended to the AS_PATH of routes announced to clients (RFC7947 section 126.96.36.199).
Route server does implement path-hiding mitigation techniques (RFC7947 section 2.3.1).
The route server verifies that the NEXT_HOP attribute of routes received from a client matches the IP address of the client itself or one of the IP addresses of other clients from the same AS. This "allows an organization with multiple connections into an IXP configured with different IP addresses to direct traffic off the IXP infrastructure through any of their connections for traffic engineering or other purposes." RFC7948, section 4.8
Routes whose AS_PATH is longer than 32 ASNs are rejected.
The left-most ASN in the AS_PATH of any route announced to the route server must be the ASN of the announcing client.
Routes whose AS_PATH contains private or invalid ASNs are rejected.
Routes with an AS_PATH containing one or more of the following "transit-free" networks' ASNs are rejected.
Origin ASN validity is enforced. Routes whose origin ASN is not authorized by the client's AS-SET are rejected.
Announced prefixes validity is enforced. Routes whose prefix is not part of the client's AS-SET are rejected. Longer prefixes that are covered by one entry of the resulting route set are accepted.
Use RPKI ROAs to validate routes whose origin ASN is authorized by the client's AS-SET but whose prefix is not.
Use ARIN Whois DB dump to validate routes whose origin ASN is authorized by the client's AS-SET but whose prefix is not.
Database is fetched from http://irrexplorer.nlnog.net/static/dumps/arin-whois-originas.json.bz2.
Use NIC.BR Whois DB dump to validate routes whose origin ASN is authorized by the client's AS-SET but whose prefix is not.
Database is fetched from ftp://ftp.registro.br/pub/numeracao/origin/nicbr-asn-blk-latest.txt.
Route validity state is signalled to route server clients using the following BGP communities:
|Prefix is included in client's AS-SET||64512:11||rt:64512:11||132213:64512:11|
|Prefix is NOT included in client's AS-SET||64512:10||rt:64512:10||132213:64512:10|
|Origin ASN is included in client's AS-SET||64512:21||rt:64512:21||132213:64512:21|
|Origin ASN is NOT included in client's AS-SET||64512:20||rt:64512:20||132213:64512:20|
|Prefix matched by a RPKI ROA for the authorized origin ASN||64512:31||rt:64512:31||132213:64512:31|
|Prefix matched by an entry of the ARIN Whois DB dump||64512:51||rt:64512:51||132213:64512:51|
|Prefix matched by an entry of the NIC.BR Whois DB dump||64512:61||rt:64512:61||132213:64512:61|
|Route authorized soley because of a client white list entry||64512:41||rt:64512:41||132213:64512:41|
RPKI BGP Origin Validation of routes received by the route server is enabled.
When an INVALID route is received by the route server, it is rejected.
The following communities are used to keep track of the validity state of the routes (only internally to the route server, they are not propagated to the clients):
In circumstances (if any) where BGP Origin Validation is not performed, the following BGP communities are attached to the route:
|RPKI BGP Origin Validation not performed||None||None||132213:1000:3|
RPKI ROAs are fetched via RTR protocol from an external validating cache.
A max-prefix limit is enforced; when it triggers, the session with the announcing client is shutdown.
The limit, if not provided on a client-by-client basis, is learnt from the client's PeeringDB record.
If no more specific limits exist for the client, the general limit of 170000 IPv4 routes and 12000 IPv6 routes is enforced.
Only prefixes whose length is in the following range are accepted by the route server:
The following prefixes are unconditionally rejected:
|188.8.131.52/24||any more specific prefix||None|
|2001:de8:1d::/64||any more specific prefix||None|
Bogon prefixes are rejected too. Click to expand the list of these prefixes.
|0.0.0.0/0||only the exact prefix||Default route|
|0.0.0.0/8||any more specific prefix||IANA - Local Identification|
|10.0.0.0/8||any more specific prefix||RFC 1918 - Private Use|
|127.0.0.0/8||any more specific prefix||IANA - Loopback|
|169.254.0.0/16||any more specific prefix||RFC 3927 - Link Local|
|172.16.0.0/12||any more specific prefix||RFC 1918 - Private Use|
|192.0.2.0/24||any more specific prefix||RFC 5737 - TEST-NET-1|
|184.108.40.206/24||any more specific prefix||RFC 3068 - 6to4 prefix|
|192.168.0.0/16||any more specific prefix||RFC 1918 - Private Use|
|198.18.0.0/15||any more specific prefix||RFC 2544 - Network Interconnect Device Benchmark Testing|
|198.51.100.0/24||any more specific prefix||RFC 5737 - TEST-NET-2|
|203.0.113.0/24||any more specific prefix||RFC 5737 - TEST-NET-3|
|220.127.116.11/3||any more specific prefix||RFC 5771 - Multcast (formerly Class D)|
|100.64.0.0/10||any more specific prefix||RFC 6598 - Shared Address Space|
|::/0||only the exact prefix||Default route|
|::/8||any more specific prefix||loopback, unspecified, v4-mapped|
|64:ff9b::/96||any more specific prefix||RFC 6052 - IPv4-IPv6 Translation|
|100::/8||any more specific prefix||RFC 6666 - reserved for Discard-Only Address Block|
|200::/7||any more specific prefix||RFC 4048 - Reserved by IETF|
|400::/6||any more specific prefix||RFC 4291 - Reserved by IETF|
|800::/5||any more specific prefix||RFC 4291 - Reserved by IETF|
|1000::/4||any more specific prefix||RFC 4291 - Reserved by IETF|
|2001::/33||any more specific prefix||RFC 4380 - Teredo prefix|
|2001:0:8000::/33||any more specific prefix||RFC 4380 - Teredo prefix|
|2001:2::/48||any more specific prefix||RFC 5180 - Benchmarking|
|2001:3::/32||any more specific prefix||RFC 7450 - Automatic Multicast Tunneling|
|2001:10::/28||any more specific prefix||RFC 4843 - Deprecated ORCHID|
|2001:20::/28||any more specific prefix||RFC 7343 - ORCHIDv2|
|2001:db8::/32||any more specific prefix||RFC 3849 - NON-ROUTABLE range to be used for documentation purpose|
|2002::/16||any more specific prefix||RFC 3068 - 6to4 prefix|
|3ffe::/16||any more specific prefix||RFC 5156 - used for the 6bone but was returned|
|4000::/3||any more specific prefix||RFC 4291 - Reserved by IETF|
|5f00::/8||any more specific prefix||RFC 5156 - used for the 6bone but was returned|
|6000::/3||any more specific prefix||RFC 4291 - Reserved by IETF|
|8000::/3||any more specific prefix||RFC 4291 - Reserved by IETF|
|a000::/3||any more specific prefix||RFC 4291 - Reserved by IETF|
|c000::/3||any more specific prefix||RFC 4291 - Reserved by IETF|
|e000::/4||any more specific prefix||RFC 4291 - Reserved by IETF|
|f000::/5||any more specific prefix||RFC 4291 - Reserved by IETF|
|f800::/6||any more specific prefix||RFC 4291 - Reserved by IETF|
|fc00::/7||any more specific prefix||RFC 4193 - Unique Local Unicast|
|fe80::/10||any more specific prefix||RFC 4291 - Link Local Unicast|
|fec0::/10||any more specific prefix||RFC 4291 - Reserved by IETF|
|ff00::/8||any more specific prefix||RFC 4291 - Multicast|
IPv6 prefixes are accepted only if part of the IPv6 Global Unicast space 2000::/3.
Routes tagged with the GRACEFUL_SHUTDOWN BGP community (65535:0) have their LOCAL_PREF attribute lowered to 0.
Routes tagged with the NO_EXPORT or NO_ADVERTISE communities received by the route server are propagated to other clients with those communities unaltered.
|Do not announce to any client||0:65534||rt:0:65534||132213:0:0|
|Announce to peer, even if tagged with the previous community||65534:peer_as||rt:65534:peer_as||132213:1:peer_as|
|Do not announce to peer||0:peer_as||rt:0:peer_as||132213:0:peer_as|
|Prepend the announcing ASN once to peer||65511:peer_as||rt:65511:peer_as||132213:101:peer_as|
|Prepend the announcing ASN twice to peer||65512:peer_as||rt:65512:peer_as||132213:102:peer_as|
|Prepend the announcing ASN thrice to peer||65513:peer_as||rt:65513:peer_as||132213:103:peer_as|
|Prepend the announcing ASN once to any||65501:65534||rt:65501:65534||132213:101:0|
|Prepend the announcing ASN twice to any||65502:65534||rt:65502:65534||132213:102:0|
|Prepend the announcing ASN thrice to any||65503:65534||rt:65503:65534||132213:103:0|
|Add NO_EXPORT to peer||65281:peer_as||rt:65281:peer_as||132213:65281:peer_as|
|Add NO_ADVERTISE to peer||65282:peer_as||rt:65282:peer_as||132213:65282:peer_as|
The following values are used to identify the reason for which routes are rejected. This is mostly used for troubleshooting, internal reporting purposes, looking glasses or in the route server log files.
Routes which are rejected are tagged with the BGP community that represents the reason for which they were discarded.
|0||Generic code: the route must be treated as rejected||65520:0||rt:65520:0||132213:65520:0|
|1||Invalid AS_PATH length||65520:1||rt:65520:1||132213:65520:1|
|2||Prefix is bogon||65520:2||rt:65520:2||132213:65520:2|
|3||Prefix is in global blacklist||65520:3||rt:65520:3||132213:65520:3|
|6||Invalid left-most ASN||65520:6||rt:65520:6||132213:65520:6|
|7||Invalid ASN in AS_PATH||65520:7||rt:65520:7||132213:65520:7|
|8||Transit-free ASN in AS_PATH||65520:8||rt:65520:8||132213:65520:8|
|9||Origin ASN not in IRRDB AS-SETs||65520:9||rt:65520:9||132213:65520:9|
|10||IPv6 prefix not in global unicast space||65520:10||rt:65520:10||132213:65520:10|
|11||Prefix is in client blacklist||65520:11||rt:65520:11||132213:65520:11|
|12||Prefix not in IRRDB AS-SETs||65520:12||rt:65520:12||132213:65520:12|
|13||Invalid prefix length||65520:13||rt:65520:13||132213:65520:13|
|14||RPKI INVALID route||65520:14||rt:65520:14||132213:65520:14|
|15||Never via route-servers ASN in AS_PATH||65520:15||rt:65520:15||132213:65520:15|