Technical Requirements

Extreme IX aims to ensure the Members reliable and uninterrupted Service as well as to limit the risks of deliberate or accidental mistakes, defective equipment or lack of speed of certain Member to reflect the quality of the others.

IP traffic should be exchanged between Extreme IX members using BGP protocol by the following ways:

1. Using Route Servers (RS) – two RSs for redundancy and resilience.
2. Bilateral BGP sessions between Extreme IX Members / Content providers with theirs mutual agreements.

1. Disabling first AS check

   The Route Servers do not have their AS first in the AS_PATH. In some cases you might need to disable the first AS check in your BGP configuration.

   • On Cisco routers please specify no bgp enforce-first-as or bgp enforce-first-as disable to disable the enforcement.
   • On Huawei routers please specify undo check-first-as to disable the enforcement.
2. Autonomous System Number (ASN)

   Extreme IX supports both 16-bit and 32-bit AS numbers.

3. Incoming Prefixes Filtering

   Extreme IX Route Servers’ filtering policy is as follows:

   • Drop small prefixes – longer than /24 for ipv4 and longer than /48 for ipv6.
   • Drop all well-known Martians and bogons.
   • Ensure that there is at least 1 ASN and less than 64 ASNs in the AS path.
   • Ensure that the peer AS is the same as the first AS in the AS path.
   • Drop any prefix where the next-hop IP address is not the same as the peer IP address. This prevents prefix hijacking.
   • Drop any prefix with a transit network (Internet or IP Transit) ASN in the AS path.
   • Ensure that origin AS is in the set of ASNs from the client’s IRRDB AS-SET.
   • If the prefix is evaluated as RPKI valid, it is accepted.
   • If the prefix is evaluated as RPKI invalid, it will be dropped.
   • If the prefix is evaluated as RPKI unknown, revert to the standard IRRDB prefix filtering.