Q: What equipment is required for connecting to JINX?
A: You require a router that supports BGP4, and unless you are located within the same building, one that has an x.21 interface to connect your Telkom circuit. BGP4 is supported by default on Cisco 2600-series and higher models. The 1700-series models also support BGP4, but only after fairly costly flash memory and software upgrades.
Q. What is BGP4 and where can I find out more about it?
A. BGP4 stands for Border Gateway Protocol version 4. It is a protocol used to exchange routing information between different ISP’s or autonomous networks.
More information can be found at:
Q: Can I get international bandwidth via JINX?
A: ISPA isn’t in the business of selling international capacity. Connecting to one of the INXes will not get you any sort of bandwidth local or international. A connection to an INX merely provides you with the opportunity to exchange traffic with the other networks connected to the same INX. Exactly what traffic you exchange depends on the arrangements you make with those other networks. Some of the other participants may be willing to provide you with international capacity (or, more correctly, an international transit service). There is nothing in ISPA’s INX policies preventing a member from offering such a service, but it is not a service that ISPA provides.
Q: Why can’t I host my server at JINX?
A: ISPA is not in the server-hosting business. Most of ISPA’s members provide hosting services, and ISPA does not want to compete with its own members. Technically, while it may seem appealing to host a server at a central location, there is a negligible difference in performance if the server is hosted on the network of an ISPA member with a high-speed connection to the INX.
You can access statistics for the exchange here:
Q: Why isn’t there an INX in Durban?
A: Because there isn’t enough support from ISPs with a presence in Durban to warrant one. ISPA has (twice) investigated the creation of a Durban exchange. Both times there was a reasonable amount of support for a DINX in principle, but when ISPs were asked to commit themselves to connecting to a DINX, there was never support from more than two ISPs. (It doesnt make economic sense to run an exchange for less than three networks.) ISPA may revisit the idea of a Durban INX eventually.
Q: Who sets the rules/policy for the INXes?
A: ISPA’s INX committee is in charge of INX policy. This committee is open to all of ISPA’s members. As far as possible, the INX committee tries to give ISPA’s general membership an opportunity to comment on any decisions regarding INX policy that may be contentious. ISPA’s Management Committee must approve any policy decisions that have an impact on ISPA’s budget before they come into effect.