TunIXP Peering Policy

This Policy is a set of guidelines used to evaluate all requests for interconnection at TunIXP. It will be reviewed and maintained and TunIXP reserves the right to update it at any time.

1. Service Details

Only layer 3 connexions are allowed. The service offers access to the multitude of networks connected to the TunIXP platform with a single connection.

The Internet Peering connexion is an Ethernet based Unicast service, enabled to support both IPv4 and IPv6 natively. The service offers interface speeds of 1 Gigabit per second Ethernet (1GE), 10 Gigabit per second Ethernet (10GE), 40 Gigabit per second Ethernet (40GE) or 100 Gigabit per second Ethernet (100GE). The peering connexion is monitored 24×7 by our NOC.

1.1 Ports available

The following ports are available at the TunIXP Platform:

1 Gbit/s “GE” (1000BaseSX, 1000BaseLX, 1000BaseLH)
10 Gbit/s “10GE” (10000BaseSX, 10000BaseLR, 10000BaseER)
40 Gbit/s “40GE” (40000BaseSX, 40000BaseLR)
100 Gbit/s “100GE” (100000BaseSX, 100000BaseLR)

1.2 Features

Provisioning of non-blocking GE. Mutiple connexion can be provided by each POP and can be aggregated.
IPv4 and/or IPv6 (native) are available
Live monitoring of traffic over TunIXP member ports is provided
Daily, weekly, monthly and yearly volume reports are available online

1.3 IP details

One IPv4 address (1 per port) and/or IPv6 out of the prefix that is in use on the TunIXP infrastructure

1.4 Service Level & Responsibilities:

TunIXP delivers a service from the port to the patch panel.
TunIXP is responsible for correct functioning of TunIXP infrastructure between its equipments.
The member is responsible for its peering and correct functioning of its own network.
The member is responsible for the necessary cabling between their router and the TunIXP panel at the colocation.
The TunIXP Network Operations Centre (NOC) actively monitors the TunIXP platform 24×7.
Problems can be reported to the TunIXP NOC via email or telephone.
TunIXP offers assistance to all members and can organise meeting to discuss any issue or member special requests

2. The Policies

The requesting peer network must fulfil the following conditions and requirements in order to qualify for a Peering Agreement with TunIXP.

2.1 Governance

TuNOG (Tunisian Operators Networks Group) Board members will govern the IX in accordance with technical and policy best practices generally accepted within the global community of IX operators as represented by the African Internet Exchange Task Force, Europe Internet Exchange Portal (Euro-IX), and similar associations.
General TunIXP technical and operational policies shall be made publicly available on the TunIXP web site.
The TunIXP shall impose no restriction upon the types of organization or individual who may become members and connect to the exchange.
The TunIXP shall impose no restrictions upon the internal technical, business, or operational policies of its members.
Members shall be required to sign an agreement, indicating that they understand and agree to abide by its policies, before any resources shall be allocated to them.
Members have a duty of confidentiality to the other TunIXP Members in TunIXP affairs.
Members must not refer their customers, or any agent of their customers, directly to TunIXP member's support staff.
Members must ensure that all contact information held by TunIXP in connection with their membership is correct and up to date.
Members must provide 24×7 operational contact details for the use of TunIXP staff and other Members.
Members shall be required to provide and maintain current technical contact information. This information shall include the website and the member's Autonomous System Number if they have one.

2.2 Infrastructure and Operational Requirements

The Requesting Network shall have a fully redundant backbone network with enough capacity to exchange traffic without congestion.
The requesting network should operate a fully staffed, 24/7/365 network operations centre (NOC).
Each Network must be responsive to routing and security issues, providing a knowledgeable technical response within a 24-hour period after notice for network and operational issues and a 2-hour period for security related issues.
The TunIXP platform is designed to carry Ethernet frames with a payload of up to 1500 bytes. MTU settings must be configured accordingly.
Members may only connect equipment that is owned and operated by that Member to TunIXP. Members may not connect equipment to TunIXP on behalf of third parties.
Members must only use IP addresses on the interface(s) of their router(s) connected to the TunIXP allocated to them by the TunIXP.
Members may only present a single MAC address to any individual TunIXP port that is allocated to them.
It is preferred that each member have their own Public Autonomous System Number.
TunIXP may monitor any port but will keep any information gathered confidential, except where required by law or where a violation of this Memorandum of Understanding has been determined by the TunIXP Management.
Members will be required to install at their ends routers that support the full BGP-4 standard.
The technical staff will set up certain monitoring features on the server at the TunIXP.
Members must not carry out any illegal activities through TunIXP.

2.3 Connectivity

The requesting networks must be able to interconnect with TunIXP at a minimum of 1 point. It is recommended to connect to more than one TunIXP POP for resiliency. Currently we have 3 POPs in Tunis : Belvedere, Kasba and Wardia.

2.4 Peering

The requesting network should be able to provide and maintain a consistent route announcement at all peering points with AS 5438 unless otherwise agreed in advance.
The requesting network must be registered as a Local Internet registry (LIR) with the appropriate Regional Internet Registry (RIR) e.g. RIPE, ARIN, LACNIC, APNIC, AFRINIC. Only routes specified by the appropriate RIR are accepted from peers.
Routes should be aggregated as much as possible by the requesting network.
Members shall not generate unnecessary route flap, or advertise unnecessarily specific routes in peering sessions with other Members across TunIXP.
Members may not advertise routes with a next-hop other than that of their own routers without the prior written permission of the advertised party.
Members may not forward traffic across TunIXP unless either the traffic follows a route advertised in a peering session at TunIXP or where prior written permission of the Member to whom the traffic is forwarded has been given.

2.5 Contact Information

A contact point (real person, or role account) for abuse/security issues, and a real person escalation contact should be provided, complete with phone numbers by the requesting network and TunIXP should be notified of any changes to these details.
A contact point for network related issues, outages and operational issues (A NOC and peering contact) should be provided by the requesting network and TunIXP should be notified of any changes to these details.

2.6 Additional Information

These criteria are only guidelines and are not exhaustive. Any final peering executed by TunIXP between potential peers may contain additional terms and conditions. Colt reserves the right to decline to enter into a Peering Agreement even if the above criteria are nominally met by a potential peering partner
If a network fulfils all of the requirements outlined above and wishes to proceed with an Internet Peering Agreement at TunIXP, please contact com@tunixp.tn.
A peer is expected to continually fulfil TunIXPs peering policy for the duration of the peering. If a peer no longer meets TunIXP peering policy, TunIXP reserves the right to remove the peering with short notice.
TunIXP reserves the right to revise or change this document at any time and from time to time without notice. As a living document, this guide will be updated as necessary to enhance and/or expand the information contained herein.

Member of