Internet Service Providers' Association

Frequently asked questions

---

Routers and BGP4

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:

• http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca763.html
• http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1771.html
• http://www.freedman.net/bigbgp.ppt
• http://www.freedman.net/bgp102.ppt
• http://www.cisco.com/en/US/tech/tk648/tk365/tk80/tech_protocol_home.html

Connections

Q: How can companies that arent members of ISPA connect to the INXes?

A: ISPA is an association of Internet service providers. If a company is not in the business of providing Internet services, that company cant become a member of ISPA, and is not eligible to connect its network to the INXes. However, there is nothing prohibiting ISPA members from connecting their customers networks directly to an INX. If, for some reason, it is important for your company to have a direct connection to an INX, but the company does not meet the criteria for ISPA membership, you should approach those ISPA members already connected to that INX with your connectivity requirements.

Q: Can I get international bandwidth via JINX?

A: ISPA isnt in the business of selling international capacity. Connecting to one of the INXes will not get you any sort of bandwith 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 ISPAs INX policies preventing a member from offering such a service, but it is not a service that ISPA provides.

Hosting equipment

Q: Why cant I host my server at JINX?

A: ISPA is not in the server-hosting business. Most of ISPAs 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.

Equivalent line charges

Q: I think the equivalent line charges are unfair/a really bad idea/extortion. Why doesnt ISPA scrap them?

A: Before the equivalent line charges were introduced, some members could link to the INXes at no cost to themselves, while others had to pay significant Telkom line rental charges to do so. To many ISPA members, this situation seemed unfair, so the equivalent line charges were introduced to try to balance things out. The equivalent line charge model was the result of more than a year of discussion and negotiation between ISPAs members. The equivalent line charges probably arent an ideal way to ensure fairness, but so far, nobody has come up with a better suggestion. If you can think of a better way to ensure that all INX users have fair and equal access to the INXes, please let us know. If you dont have a better idea, but you still want to criticise the equivalent line charges, expect to be glared at sullenly.

Statistics

You can access statistics for the exchange here:

http://stats.jinx.net.za

An exchange in Durban

Q: Why isnt there an INX in Durban?

A: Because there isnt 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.

INX policy

Q: Who sets the rules/policy for the INXes?

A: ISPAs INX committee is in charge of INX policy. This committee is open to all of ISPAs members. As far as possible, the INX committee tries to give ISPAs general membership an opportunity to comment on any decisions regarding INX policy that may be contentious. ISPAs Management Committee must approve any policy decisions that have an impact on ISPAs budget before they come into effect.

Q: I think that ISPAs policy on sucks. How do I get it changed?

A: All of the policies in this document are the result of substantial discussion and debate. In some cases, the policy represents a carefully negotiated approach to a difficult issue. That means that the INX committee is unlikely to make sweeping changes simply because someone asks. The best way to influence policy is to become an active participant in the INX committee. The committee has a mailing list and meets roughly once every two to three months. If you are an ISPA member and youd like to join the committee, let know. If you are not an ISPA member, you are still welcome to send comments or suggestions to the INX committee at the same address.