AIXP Memorandum of Understanding
The undersigned, representative of______________________ (ISP), hereby confirms theparticipation of the above mentioned ISP in the
Arusha Internet Exchange (AIXP). The Technical andOrganizational Requirements below are accepted
and will be adhered to.
Company Name: _______________________
Address:________________________________________________________________
Admin Contact: _________________ (Name)____________________________(Email)Technical Contact:________________ (Name)______________________________(Email)Signature:___________________Name in print: ___________________
Date:___________________
Filled by AIXP:Port on AIXP switch: ____________IP on AIXP net:
196.223. __ . ___ASN:____________
A. Technical requirements
1. Peers will be provided with 2U rack space.
There might be restrictions in the futurewhen capacity is limited.
2. AIXP provides its participants with a layer-2
Ethernet switch fabric and a layer-3 routeserver.
3. Participants may only connect equipment
which they own and operate themselves tothe AIXP. They may not connect equipment
on behalf of third parties.
4. Peers may only utilize a single layer- 2 MAC
address to directly connect a single layer-3
router per port allocated from the AIXP switch
fabric.
5. It is preferred that each participant have theirown
Autonomous System number, peers
without an ASN allocation will be assigned
an ASN from private ASN space by the AIXPManagement Committee. Any peer who has
previously been connected to the AIXP using
private ASN and then later acquires their own
public ASN must notify the AIXP Management
Committee as soon as possible in order toincorporate this development into the BGP
peering at AIXP.
6. AIXP participants will advertise routes to their
IP address range(s) to the AIXP routeserver(s). Peers shall not advertise routes
other than their own, without the priorwritten permission of the assigned holder ofthe address space.
7. Peers shall not advertise a next-hop otherthan their own.
8. Peering between routers across AIXP will bevia BGP
9. Peers shall not generate unnecessary routeflap, or advertise unnecessarily specificroutes in peering sessions with otherparticipants across AIXP.
10. Peers shall not point their default route to theAIXP.

11. Participants must, on all interfaces connectedto the AIXP switch fabric, disable Proxy ARP,
ICMP redirect, CDP, IRDP, directedbroadcasts, IEEE802 Spanning Tree, anyinterior routing protocol broadcasts, and any
MAC layer broadcasts other than ARP orinverse-ARP.
12. Peers must set netmasks on all interfaces
connected to the AIXP to include the entire
AIXP peering LAN.
13. Participants shall not announce ("leak")prefixes including some or all of the AIXP
peering LAN to other networks without
explicit permission of AIXP.
14. Participants must clearly label all equipmentthat resides at the AIXP facility withownership and contact information.
15. Participants will not touch equipment and/or
cabling owned by other participants andinstalled at AIXP or in the room containing
the AIXP without the explicit permission ofthe participant who owns the equipment.
16. Peers should not routinely use the AIXP
switch fabric for carrying traffic between theirown routers.
17. Participants will not install traffic monitoring
software to monitor traffic passing through
AIXP, except through their own ports. AIXP
may monitor any port
18. AIXP does make statistics of the aggregate
traffic flow over the exchange switch
available to the public.
19. Participants shall endeavor to provide
advance notice via email to each of their BGP
peers, in the event that a service disruptionor discontinuity of BGP peering can beforeseen.
For clarification:
1. ISPs should advertise all their networks to theIXP.
2. ISPs should not use multiple links to the IXP
for the purpose of routing their internaltraffic.
3. ISPs should accept all routes advertised by allother peers and route traffic through theExchange (the purpose of it).
B. Organizational Requirements
1. Participants have a duty of confidentiality tothe other AIXP Participants in AIXP affairs.
2. Peers must provide 24x7 contact details foruse by AIXP staff.
3. In matters of AIXP, the primary means ofcommunication will be via email.
4. Peers must not refer customers or customers'
agents to AIXP staff. All queries must be
directed through the peer's support staff.
5. Peers must not carry out any illegal activities
through AIXP. They are to obey the laws of
the country.
6. Participants will pay annual fees in advance.
Failure to do so will result in immediatedisconnection. Fees are detailed in Annex Cbelow. It is Participants' responsibility toensure that all contact information held byAIXP in connection with their participation iscorrect and up to date.
7. All applications to join the AIXP must follow
the correct joining procedure as follows:
Applications will be accepted, provided thisMoU including the Technical andOrganisational Requirements as well as theFees are accepted and the MoU is signed andnecessary details given. Applications must beaccompanied by the setup fee and the fullport connection fee for the current calenderyear.
8. Any complaints must be referred in writing tothe AIXP Management Committee of TISPA.
The working group will discuss them at thenext meeting. The decision can be revised by
the Board of TISPA, in which case that will befinal.
9. The AIXP will not provide rebates of any sortfor down time. TISPA and AIXP do not warrant
or assume any liability or responsibility forservices provided or not provided.
10. Participants of the AIXP must give 3 months
notice in writing to TISPA if they intend tostop using the IXP. There will be no refund oncharges under any circumstances.
C. Fees schedule
AIXP will charge each participant a port connection
fee. This will allow the peer to connect to thedesignated 10/100Mbit port on the AIXP switchingfabric.
The fee is set to USD 500.00 for one calendar year,
payable in advance. A once-off registration fee of
USD 1,000.00 will be charged.