Data Center Solutions       Powered Shell Data Centers


SAT-IX requires peering participants to follow the below set of rules to ensure the health of the exchange and other participants:

  • Participants must use BGP-4 or its successor and must set NEXT_HOP_SELF if advertising routes from other SAT-IX participants.
  • Participants must not point default or otherwise use another participant’s or SAT-IX resources without permission.
  • There are only three (3) ethertypes allowed: 0x0800 (IPv4), 0x0806 (ARP) and 0x86dd (IPv6).
  • Peering is bilateral, except for route servers [there is no Multi-Lateral Peering Agreement (MLPA)].
  • The only non-unicast traffic allowed is broadcast ARP and multicast ICMPv6 Neighbor Discovery packets. Per-neighbor timeouts that result in flooded (broadcast/multicast) packets should be set to four (4) hours or as close to that as able in the case of vendor limitations. Short timeouts may result in a quarantine.
  • Participants must not allow SAT-IX subnets to propagate externally from their network and should minimize internal propagation as much as able. If a participant’s network beyond their SAT-IX edge router(s) can reach the SAT-IX subnet addresses, ACLs are requested in order to prevent this.
  • Participant ACLs must not violate neighbor discovery norms, since doing so will result in excess flooded packets on the community fabric. For IPv4 this means that a participant’s router must be configured to receive and respond to ARP packets from all SAT-IX participants, even those that are not direct peers. For IPv6, this means that participant routers must receive and respond to ICMPv6 neighbor solicitation packets from both fe80::/10 and all SAT-IX participant addresses, including those that are not direct peers, directed toward fe80::/10, ff02::1:ff00:0/104, and the participant’s unicast SAT-IX assignments.
  • Participants may not sniff traffic between other participants.
  • Participants must be responsive to other participants and SAT-IX administrators to protect the exchange fabric. Urgent issues may result in suspension of a participant to protect the exchange. For non-urgent issues, if a participant is unresponsive to concerns raised by a SAT-IX administrator, a SAT-IX administrator will notify the non-responding participant via their PeeringDB and SAT-IX contact emails if a response is needed to avoid suspension from the SAT-IX. The length of time to determine if a participant is unresponsive and time to suspension will depend on the severity of the matter, in SAT-IX’s sole determination.
    First Name*
    Last Name*
    How Can We Help?*
    Lead Source