The Israeli Internet eXchange is the central meeting point of the Internet Service Providers in Israel. Its purpose is to route all intra-Israel Internet traffic, among the operators, as efficiently as possible.
IIX is managed by the Israeli Internet Society (ISOC-IL), and is operated by delegates thereof. ISOC-IL makes all efforts to operate the IIX in a professional manner and to provide an excellent service to its Peers.
ISOC-IL, and hence the IIX operation, is a not-for-profit operation.
An organization that is licensed to be an IP service provider (by the Ministry of Communications), can become an IIX Peer. It can then connect to the IIX (for a fee, as described below) and receive the routing services provided by the IIX.
ISOC-IL will allow only IIX Peers who have met their IIX dues to connect to the IIX.
At present, connection can be made in one of the following way:
- A LAN based connection, at certain speeds, via a licensed carrier.
Connections will be ordered and paid for by the connecting Peer. Limitations on the capacity parameters of the connection will be listed below.
The connection fees will be based on the connection speed, according to the price list.
Each Peer must be directly connected to the IIX. Indirect connections (i.e., one IP service operator passing network traffic for another via the IIX) will not be allowed.
Any Peer connecting to the IIX will be required to use the BGP4 routing protocol, and have their own registered Autonomous System Number (ASN).
Only intra-country, between-Peers IP traffic is allowed. It is not allowed for a Peer to have the IIX designated as a default route, or in any way use the IIX to pass traffic that is not destined to another IIX Peer.
Network routing announcement will be filtered upon entry to the IIX, so as to stabilize the national network and prevent errors. Hence, network blocks that are used by Peers will have to be registered with the IIX.
Registration will be done by sending mail to email@example.com. In case of a network registration dispute, the ruling will be made according to the registration at the RIPE IRR (Internet Routing Registry).
The IIX will not maintain or own any proxy servers, Usenet servers or other major source of content. The IIX will act strictly as a meeting point for Israeli Service Providers.
The maintainers of the IIX will be committed to add a new route within 3 business days of receiving the request. The maintainers of the IIX will be on call 24 hours a day and will be responsible to handle routing problems within 4 hours of receiving the call if received between 08:00-18:00 on business days, and within 8 hours otherwise.
(This section has been moved to a separate document ).
Limitation of Liability
Under no circumstances shall the Israeli Internet Society, or any one of its members be liable for any direct, indirect, incidental consequential, commercial or other damages, losses, liabilities, claims or expenses to an IIX peer, to a customer thereof, or to any third party arising out of a peer’s agreement to connect to the Israeli Internet Exchange (IIX).
The IIX peer agrees that the use of the service provided by the IIX is at the peer’s own risk. The peers have been advised of the possibility of failures, interruptions, incompetencies, negligence, postponements and cessation of service, and will not hold the IIX liable for damages of any kind (including loss of profits) however caused, whether grounded in contract, tort (including negligence) or strict liability.
In case of permanent stoppage of the service, the Israeli Internet Society will notify you 60 days in advance. A peer will notify the Israeli Internet Society in writing 60 days in advance in case it decides to disconnect from the service.
The peer will be responsible for assessing its own need for property, casualty, liability and other insurance, and will obtain such insurance as they see fit. It will bear the risk of any losses and agree not to make any claims against ISOC-IL or any one of its members.
ISOC-IL will not be held responsible for any confidential or copyrighted information which might have inadvertantly been transmitted over the networks.
- Checking the ASN/AS-SET of the holder of the network in order to ascertain that they allow the relevant ISP to advertise them (if the holder is not a direct client of the ISP – the entire chain of ASNs will be checked)
- The holder of the network will send an e-mail to firstname.lastname@example.org, authorising the relevant ISP (member of the IIX) to advertise their network to the exchange