Peering is the direct interconnection between Comnet Turkey's network and another network to support the exchange of traffic.
Comnet Turkey maintains an open peering policy, subject to specific technical, commercial, and legal requirements as outlined in our peering policy, as well as any local infrastructure prerequisites or limitations.
Our Autonomous Systems (AS Numbers):
- AS61135 (or AS-COMNET-INT)
We are available for peering at the Internet Exchanges (IXPs) and private facilities listed in our PeeringDB entry. Please note that not all interconnect locations may be accessible to all networks.
Comnet Turkey is listed in PeeringDB, the industry database for peering information for network operators. For the most up-to-date list of Comnet Turkey's public and private peering locations, please refer to our PeeringDB entry. New peering requests should be submitted via email to firstname.lastname@example.org.
Comnet Turkey maintains an open peering policy, contingent on specific technical, commercial, and legal requirements. Occasionally, local infrastructure prerequisites or constraints may temporarily or permanently modify these requirements.
Networks seeking to peer with Comnet Turkey must meet the following criteria:
- Publicly routable Autonomous System Number (ASN)
- Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)
- Completed ASN record in PeeringDB
- 24x7 Network Operations Center (NOC) contact capable of resolving BGP routing issues
- Presence at one or more of the 90+ Internet Exchanges or 100+ private peering interconnection facilities listed for Comnet Turkey in PeeringDB
- Minimum traffic requirements (specified below)
- Up-to-date Maintainer, ASN, AS-SET, and Route/Route6 objects in an Internet Routing Registry (IRR) that Comnet Turkey supports
Private Peering Physical Requirements
Comnet Turkey supports the following standard port types for private peering:
- 10G Duplex Ethernet LR (LAN-PHY)
- 100G Ethernet LR4
Additional requirements include link aggregation via LACP (preferably even for single links), no support for high-MTU "jumbo frames," optical physical layer using Single Mode Optical Fiber, direct point-to-point links only (with only one device on each side, and no support for switches in the path to multiple routers or MLAG), and support for only /30 & /31 IPv4 subnet sizes.
BGP Configuration Requirements
Comnet Turkey's BGP configuration requirements include:
- No support for MED
- No support for multihop
- Prefer MD5 authentication
- Acceptance of the most specific prefix (at least /24 for IPv4 and /48 for IPv6)
Traffic Requirements – Public Peering
Comnet Turkey generally does not impose a minimum traffic requirement for public peering, subject to specific market conditions.
While Comnet Turkey connects to Internet Exchange route servers when available, it prefers to establish direct BGP sessions for traffic exchange.
Traffic Requirements – Private Peering
For networks with significant traffic (usually exceeding 10Gb/s), Comnet Turkey prefers private peering, also known as Private Network Interconnect (PNI).
Regional Traffic Requirement
In general, Comnet Turkey will peer with a network in a region where the peer has sufficient end-user traffic within that region to meet the above public or private traffic requirements.
Peering sessions with AS61135 (Comnet Turkey) will advertise all COMNET-ASN routes. However, local infrastructure requirements or constraints may sometimes result in a more limited set of routes being advertised via AS61135.
Traffic Exchange Preferences
For traffic exchange, Comnet Turkey generally prioritizes private peering links over public peering links, and public peering links over route-server paths. Comnet Turkey generally does not support public peering or route-server-learned routes with a network where private peering links exist within the same continent. Note that Comnet Turkey only advertises aggregate routes via route servers.
Peers are encouraged to set a maximum prefix limit of 15,000 (IPv4) and 1,000 (IPv6) routes on peering sessions with Comnet Turkey.
In addition to AS61135 and AS-COMNET-INT, Comnet Turkey may have other related ASNs for specific purposes.
This section outlines Comnet Turkey's traffic management procedures and expectations from peers.
Comnet Turkey's traffic management prioritizes:
- Carrying traffic on its own network as close to users as possible
- Serving traffic from edge nodes (GGC) first, then direct peering, and finally via indirect paths
- Optimizing traffic delivery for end-user performance
- Respecting AS path length and prefix specifics when deciding how to exchange traffic with peers
There may be exceptions to these guidelines based on observed performance between Comnet Turkey serving locations and end-users.
Comnet Turkey requests that peers advertise all their routes in all locations where they peer with Comnet Turkey unless an alternative route advertisement policy has been agreed upon. Comnet Turkey manages traffic routing and delivery to ensure optimal performance for end-users.
To ensure ample peering capacity in the event of an outage, Comnet Turkey recommends that peers establish connections at more than one location and augment their peering connections when peak traffic exceeds 50%.
If a peering port reaches full capacity due to an outage or other capacity issue, Comnet Turkey's traffic management systems will redirect excess traffic to other peering ports or alternative paths.
Comnet Turkey Congestion Management
Comnet Turkey can typically run peering ports at 100% capacity with low packet loss for most services (usually less than 1-2%). Peers are expected to adhere to the capacity augmentation guideline mentioned above.