Policy

Basic principles

1.  INX-ZA is responsible for the administration of the INXes and determines policies relating to the INXes.
2. The host provides resources essential to the operation of the INX facilities, including power, air- conditioning and secure access to the site.
3. 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.
4. 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.

Fees

1. There are no joining fees for the INXes.

2. Monthly port charges apply to connections to the INXes. These charges depend on the speed of each port used by an ISP. The port charges will be reviewed on an annual basis by the INX management committee.
3. Port fees may be waived for ports used by Critical Infrastructure (such as DNS Root Servers) located at an INX.  The INX management committee remains responsible for determining which services it is appropriate to have hosted at the INXes, and when port fees should be waived.

Requirement to exchange traffic via the INX switch fabric

17. With the exception noted, all interconnection at each INX must take place via the INX switch fabric. This means that within each INX cage there may be no peer-to-peer interconnection, and all traffic exchanged must be via the switch.

18. The above policy does not apply to any ISP paying the 10 Gbps port charge; this gives that ISP the right to interconnect privately. An INX user is welcome to pay the 10 Gbps port charge to gain this benefit, but make use of a lower speed port on the switch. For the avoidance of doubt, both parties interconnecting privately must be paying the 10 Gbps port charge, in order to have the right to interconnect with each other.

19. The INX management committee retains the right to grant additional exceptions to the above clause, where technically necessary. (The specific example was put forward of voice traffic exchanged via SS7. The JINX switch does not support this, and it would have to bypass the switch.)

Rack space

1. The monthly port charge gives that INX user the right to use a maximum amount of rack space depending on the primary port used, as indicated below.  ISPA reserves the right to impose additional charges for ISPs using more than this, with appropriate fees to be determined by the INX committee.  Rack space may only be available at specific locations.

1. The above rack space allocation includes any telco infrastructure associated with an INX user.
2. All equipment hosted at the INXes must be rack-mounted. ISPA reserves the right to disconnect any equipment which is not rack-mounted. The INX management committee may grant exceptions to this rule on case-by-case basis.
3. The above policies on rack space are intended to ensure that each INX remains an Internet exchange, and not an equipment hosting facility. Additional rack space will not be made available to INX participants.
4. Rack space allocations are not transferable. INX participants may not resell, sublet or give away rack space without permission from ISPA.

Cabling

1. The INX host will provide all ethernet patch cabling for the INX facilities. ISPA members may not supply their own ethernet cabling. ISPA members are, however, responsible for their own power cables. These rules are subject to the discretion of the INX host.
2. The host may levy a cabling fee of R1200 (excl. VAT) per port used for connections into the JINX and CINX facilities. This fee is for the cabling between the host’s meet-me room and the INX environment and is a per-cable installation fee, and not a recurring cost.
3. For transparency and fairness, the host must publish a list of prices for other cabling projects within the hosting facility.

Wireless connections and roof access

1. For transparency and fairness, the host must provide up-to-date information on the availability of roof space at the hosting location for the purposes of wireless links. Contact details for further enquiries should also be provided.

Participants’ interconnection policies

1. A connection to an INX is not the same as interconnection with other organisations using that INX. ISPA 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 user of an INX to negotiate interconnection agreements with the other INX participants.
   
   

Hosting of servers

1. No servers or other non-standard equipment may be hosted at an INX without the explicit permission of the INX management committee. Any requests to host third party equipment (e.g. monitoring devices) will be dealt with by the INX management committee on a case-by-case basis.

SNMP access

1. No participant may have access to the community string for the INX switches unless cleared to do so by the INX management committee.

Insurance

1.  Members are responsible for the insurance of their own equipment.

Liability for outages

1. ISPA members using the INXes cannot hold ISPA or other INX participants liable for network outages of any kind.

Non-compliance

1. ISPA reserves the right to terminate any INX user’s access to an INX for non-compliance with INX policies.

Changes to this policy

INX-ZA reserves the right to make changes to its INX policies, following due consultation with the participants.