- BGP-4 or successor is used for peering and peers must set NEXT_HOP_SELF if advertising routes from other INX participants.
- Broadcast traffic may not delivered to the exchange, except as needed for normal operation and debugging.
- We operate a unicast fabric; multicast except for regular IPv6 operations is not permitted.
- Participants should ensure that only a single MAC address is visible via their ports, unless they are a reseller, and have made prior arrangements with the Ops team
- Mac addressed are hard-coded to peer ports.
- Participants may not point default or otherwise use another participant's resources without permission.
- Peering is bilateral with the exception of the BGP Route Servers service. Peers are encouraged to setup their own bilateral sessions where appropriate.
- Participants may not sniff traffic between other participants.
- No participant may have access to the SNMP community strings for the INX switches unless cleared to do so by the INX management committee.
- Peer are expected to respond timeously to concerns raised by the Ops team. Non response may result in ports being disabled.