Passive sessions are configured toward neighbors.
GTSM (Generalized TTL Security Mechanism - RFC5082) is disabled on sessions toward the neighbors.
ADD-PATH capability (RFC7911) is not negotiated by default.
Route server ASN is not prepended to the AS_PATH of routes announced to clients (RFC7947 section 22.214.171.124).
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 .
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.
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.
RPKI BGP Prefix Origin Validation of routes received by the route server is disabled.
Only prefixes whose length is in the following range are accepted by the route server:
Routes tagged with the NO_EXPORT or NO_ADVERTISE communities received by the route server are propagated to other clients with those communities unaltered.