The undersigned confirms the participation of the below mentioned network in the <FULL NAME OF IXP> and that the Technical, Organizational, and Commercial requirements listed within this document are accepted and shall be adhered to.

A. Technical requirements

1. Participants shall be provided with 2U rack space. Participants who wish to utilize additional rack-space must acquire written consent from the <IXP> Management Team.
2. All participant equipment must be rack-mountable and installed within the participant’s designated rack-space. Any equipment that is not rack-mountable must be specifically approved in writing by the <IXP> management team prior to installation. All other equipment shall be removed without warning.
3. <IXP> provides all participants with a layer-2 switch fabric, a designated switch port, and BGP route servers.
4. Participants may only connect equipment which they own and operate themselves to the <IXP>. They may not connect equipment on behalf of third parties.
5. Peers may only utilize a single layer-2 MAC address to connect a single layer-3 router to the <IXP> switch fabric.
6. <IXP> participants are encouraged to advertise their IP address prefix(es) to the <IXP> route servers. Peers shall not advertise IP address prefix(es) other than their own without the prior written permission of the assigned holder of the address space. A copy of this written permission must be submitted to the <IXP>.
7. Peers shall not use any <IXP> switch port other than the one allocated to them. Participants who wish to use additional ports must first acquire the written consent of the <IXP> Management Team.
8. Peers shall not advertise a next-hop other than their own.
9. Peering between routers across <IXP> shall be via BGP-4.
10. Peers shall not generate unnecessary route flap.
11. Peers are strongly encouraged to make consistent routing announcements to <IXP> neighbors, upstream neighbors, and all other IP peering interconnects.
12. Peers shall not point their default route to the <IXP> or any peer.
13. Participants must, on all interfaces connected to the <IXP> switch fabric, disable Proxy ARP, ICMP redirect, CDP, IRDP, directed broadcasts, IEEE802 Spanning Tree, any interior routing protocol broadcasts, and any MAC layer broadcasts other than ARP or inverse-ARP.
14. Peers must, on all interfaces connected to the <IXP> switch fabric, disable any duplex, speed, or other link parameter auto-sensing.
15. Peers must set netmasks on all interfaces connected to the <IXP> to include the entire <IXP> peering LAN (currently XXX.XXX.XXX.XXX/24 and XXXX:XXXX:XXXX:/112).
16. Peers shall avoid congestion on their interfaces or transmission links at or into <IXP> so as to not cause unwanted latency or packet loss for traffic at the <IXP>.
17. Participants shall not announce ("leak") prefixes including some or all of the <IXP> peering LAN to other networks without explicit permission of <IXP>.
18. Participants must clearly label all equipment that resides at the <IXP> facility with ownership and contact information.
19. Participants must not touch any equipment and/or cabling owned by other <IXP> participants without the explicit permission of the <IXP> or the participant who owns the equipment.
20. Participants shall not install traffic monitoring software to monitor traffic passing through <IXP>, except through their own router ports. <IXP> may monitor any port, however any information gathered shall be kept strictly confidential except where required by law or where a violation of this Memorandum of Understanding has been determined by the <IXP> Management Team. The <IXP> Management Team shall notify all participants of any monitoring system implementations or changes.
21. Participants shall endeavor to provide advance notice via email to each of their BGP peers, in the event that a service disruption or discontinuity of BGP peering can be foreseen.
22. The <IXP> shall publicly publish per-port and aggregate statistics of traffic flowing over the exchange switch.
23. Participants shall not intentionally provide transit services across the <IXP> switch fabric.
24. Failure to comply with any of the above requirements may result in temporary or permanent disconnection.

B. Organizational Requirements

1. Participants have a duty of confidentiality to the other <IXP> participants in <IXP> affairs.
2. Peers must provide 24x7 contact details for use by <IXP> staff.
3. In matters of the <IXP>, the primary means of communication shall be via email.
4. Peers must not refer customers or customers' agents to <IXP> staff. All queries must be directed through the peer's support staff.
5. Peers must not carry out any illegal activities through <IXP>. All participants are to obey the laws of the country. Failure to comply may result in temporary or permanent disconnection.
6. Participants are required to pay all fees (according to Section C of this document) in advance. Failure to do so shall result in immediate disconnection.
7. Participants are responsible for ensuring that all contact information held by the <IXP> in connection with their participation is correct and up to date.
8. Participants are responsible for ensuring that their employees register for secure access to the <IXP> facility.
9. All applications to join the <IXP> must follow the correct joining procedure as follows:

1. A formal request letter is submitted to the <IXP> Management Team, signed by an authorized representative of the requesting company/participant
2. Applications shall be accepted provided that this MoU is accepted and signed by an authorized representative of the requesting company/participant
3. Applications must be accompanied by any fees required according to Section C of this document.

10. Any complaints must be made in writing to the <IXP> Management Team. All decisions made by the <IXP> Management Team shall be final.
11. The <IXP> shall not provide rebates of any sort for down time. The <IXP> does not warrant or assume any liability or responsibility for services provided or not provided.
12. Participants of the <IXP> are requested to give 3 months notice in writing to the <IXP> Management Team if they intend to stop using the <IXP>. There shall be no refund on charges under any circumstances.

C. Fee schedule

1. PAYMENT RELATED TERMS GO IN THIS SECTION
2. Please refer to the Af-IX website and mailing list for suggestions
3. http://www.af-ix.net