Welcome to Sudan Internet Exchange Point!

Technical Agreement

Technical Agreement

The undersigned confirms the participation of the below mentioned network in the Sudan IXP and that the Technical and Organizational requirements listed within this document are accepted and shall be adhered to:

A. Connecting Rules at SIXP to be adhered by Member :
  • Members shall an ASN (Autonomous System Number) and use BGP (+) for peering.
  • The Autonomous System Number, which the Member provides to SIXP, should be visible from the SIXP router.
  • All members to ensure forwarding local traffic through their direct SIXP links and not through other member.
  • Members will be allowed to do bilateral peering/transit amongst themselves without using the SIXP routers or any other SIXP networking equipment’s (under the condition that those links will carry local traffic only and only if SIXP services become thoroughly down).

  • B. Technical Requirements :-
  • Members shall be provided with 2U rack space. Members who wish to utilize additional rack-space must acquire written consent from the SIXP Management Team.
  • 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 SIXP management team prior to installation.
  • SIXP provides all Members with a layer-3 for national traffic and a layer-2 switch fabric, a designated switch port, and BGP route servers for services (DNS node , QUAD9 ,.SD,......etc).
  • Members may only connect equipment which they own and operate themselves to the SIXP. They may not connect equipment on behalf of third parties.
  • Peers may only utilize a single layer-2 MAC address to connect a single layer-3 router to the SIXP switch fabric.
  • SIXP Members are encouraged to advertise their IP address prefix(es) to the SIXP 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 SIXP.
  • Peers shall not use any SIXP switch port other than the one allocated to them. Members who wish to use additional ports must first acquire the written consent of the SIXP Management Team.
  • Peers shall not advertise a next-hop other than their own.
  • Peering between routers across SIXP shall be via BGP-4.
  • Peers shall not generate unnecessary route flap.
  • Peers are strongly encouraged to make consistent routing announcements to SIXP neighbors, upstream neighbors, and all other IP peering interconnects.
  • Peers shall not point their default route to the SIXP or any peer.
  • Peers must, on all interfaces connected to the SIXP switch fabric, disable any duplex, speed, or other link parameter auto-sensing.
  • Peers must set netmasks on all interfaces connected to the SIXP to include the entire SIXP peering LAN (currently 196.223.20. 0/24 and 2001:43f8:7f0::/48 ) .
  • Peers shall avoid congestion on their interfaces or transmission links at or into SIXP so as to not cause unwanted latency or packet loss for traffic at the SIXP.
  • Members shall not announce ("leak") prefixes including some or all of the SIXP peering LAN to other networks without explicit permission of SIXP.
  • Members must clearly label all equipment that resides at the SIXP facility with ownership and contact information.
  • Members must not touch any equipment and/or cabling owned by other SIXP Members without the explicit permission of the SIXP or the participant who owns the equipment.
  • Members shall not install traffic monitoring software to monitor traffic passing through SIXP, except through their own router ports. SIXP 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 SIXP Management Team. The SIXP Management Team shall notify all Members of any monitoring system implementations or changes.
  • Members 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.
  • The SIXP shall publicly publish per-port and aggregate statistics of traffic flowing over the exchange switch.
  • Members shall not intentionally provide transit services across the SIXP switch fabric.

  • C. Services provided by SIXP to Member SIXP shall:
  • Provide and maintain the connection for a member.
  • Members are totally responsible provisioning and configuring their routers. However, SIXP personnel may provide Members with remote hand support- i.e. power on/off, reseat cards/cables, etc.) but no login to the routers.
  • SIXP wit provides Members with /31, /127 public IPs for the point to point (SIXP-to-MEMBERS) connections in layer-3 and /24 in layer-2.
  • Provides all Members with a layer-2 switch fabric, a designated switch port, and BGP route servers.
  • Allow access to the core area only to authorized personnel of member under supervision of SIXP staff.
  • Provide 24 x 7 monitoring of the SIXP network and support.
  • Provide installation & support services.
  • Provide reasonable efforts to ensure that the service is available 99.99% of the time as measured seven (7) days a week, twenty-four (24) hours a day on a monthly basis, excluding periods of scheduled maintenance.
  • Ensure zero packet-loss at all time within its demarcation area, from its member’s routers (Delay and jitter to be included).
  • If a MEMBERS experiences an outage of any kind and the faults “within” SIXP demarcation area, MEMBERS is expected to notify SIXP, and SIXP will analyze the problem and respond to the MEMBERS via telephone within thirty (30) minutes.
  • Provide network management related services.
  • Provide any other services as decided by ALL SIXP MoU members.
  • Peers must not refer customers or customers' agents to SIXP staff. All queries must be directed through the peer's support staff.

  • D. Responsibilities of Members Members shall:
  • Responsible for ensuring that their employees register for secure access to the SIXP facility.
  • All applications to join the SIXP must follow the correct joining procedure as follows:
  • - formal request letter is submitted to the SIXP Management Team, signed by an authorized representative of the requesting company/participant
    - Applications shall be accepted provided that this MoU is accepted and signed by an authorized representative of the requesting company/participant.
  • At their own cost ensure the faultless connection of its network through leased line (or any other connecting medium such as radio link, VSAT, Fiber, WiMAX, ATM, Frame relay etc.) to the SIXP network, as per the Technical Requirements of SIXP (Technical Requirement is attached with this document). In case the media is wireless, then the presence of security constraints is a MUST (i.e. encryption AES, DES, 3DES, etc.).
  • MEMBERS shall advertise all block IP.
  • Members have a duty of confidentiality to the other SIXP Members in SIXP affairs.
  • Peers must provide 24x7 contact details for use by SIXP staff.
  • In matters of the SIXP, the primary means of communication shall be via email.
  • Peers must not refer customers or customers' agents to SIXP staff. All queries must be directed through the peer's support staff.
  • Peers must not carry out any illegal activities through SIXP. All Members are to obey the laws of the country. Failure to comply may result in temporary or permanent disconnection.
  • Members are responsible for ensuring that all contact information held by the SIXP in connection with their participation is correct and up to date.
  • Members are responsible for ensuring that their employees register for secure access to the SIXP facility.
  • If an MEMBERS experiences an outage of any kind and the faults falls “out of” SIXP demarcation area, the expected Time To Repair (TTR) is not to exceed 6 hrs (for configuration problems) and 12 hrs other problems (including hardware replacement).
  • Be solely responsible for all charges (including maintenance, repairs, configuration, and operations) related to the Member Equipment.
  • Provide 24*7 operational contact details for the use of SIXP staff and other SIXP Members as required by SIXP.
  • Ensure that its usage of the Connection/ SIXP’s network is not detrimental in any way and does not cause damage to the SIXP network / infrastructure or to the usage of SIXP by the other SIXP Members or to the traffic exchange thereon.
  • MEMBERS shall not refuse to accept other member prefixes through SIXP.
  • Members of the SIXP are requested to give 3 weeks’ notice in writing to the SIXP Management Team if they intend to stop using the SIXP.