INX-ZA is responsible for the administration of the INXes and determines policies relating to the INXes.
Each INX participant is responsible for obtaining one or more circuits to the relevant INX facilities, and for all costs associated with those circuits. INX participants are also responsible for supplying any equipment, such as routers, they require to connect their networks to the INX switches.
There is no restriction on circuits a participant may terminate at the INXes and participants may use an INX as a key node on their backbone network, provided that they comply with all of the INX policies.
A connection to an INX is not the same as an interconnection with other organisations using that Internet Exchange. INX-ZA does not require INX participants to interconnect with all other INX participants. Each organisation connecting to an INX is free to establish its own policy for interconnection. It is up to each participant at an INX to negotiate interconnection agreements with the other INX participants. INX-ZA Ops does provide an optional to use, BGP Route Server service to facilitate this.
Peers are required to peer with the BGP Route-Collector service that is operated by INX-ZA Ops to facilitate debugging.
Traffic shall not be routinely exchanged between two member interfaces connected to the same peering fabric, operated by the same member.
There are no joining fees for the INXes.
Monthly port charges apply to connections to the INXes. The port charges will be reviewed on an annual basis by the community elected INX management committee.
Port fees may be waived for ports used by Critical Infrastructure (such as DNS Root Servers), and other not-for-profit associations deemed to be good for the Internet. The INX management committee remains responsible for determining which services are appropriate to have hosted at the INXes, and when port fees should be waived.
|Primary port||Max rack space|
Hosting of servers
The INX-ZA management committee reserves the right to make changes to its INX policies, following due consultation with the peering participants. This policy should be read alongside the INX Technical policy which covers specific technical rues for the IX.