Peering

Peering is the direct interconnection between Comnet Turkey network and another network to support the exchange of traffic.

Comnet Turkey has an open peering policy, subject to the few basic technical, commercial, and legal requirements expressed in our peering policy, and to any local infrastructure requirements or constraints.

Our autonomous systems (AS number):

• AS61135 or AS-COMNET-INT

We are able to peer at the Internet Exchanges (IXPs) and private facilities listed in our PeeringDB entry. Please note that not all interconnect locations may be available for all networks.

Peering Policy

Comnet Turkey is listed in PeeringDB, the industry database for peering information for network operators. Please review our PeeringDB entry for the most current list of Comnet Turkey’s public and private peering locations. New peering requests should be submitted with email [email protected]

Comnet Turkey has an open peering policy, subject to certain technical, commercial and legal requirements. At times, local infrastructure requirements or constraints may modify these requirements on a temporary or long-term basis.

Technical requirements

Networks wishing to peer with Comnet Turkey must have the following:

• Publicly routable ASN
• Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)
• ASN record completed in PeeringDB
• 24×7 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 as below
• Up to date Maintainer, ASN, AS-SET, and Route/Route6 objects in a IRR that Comnet Turkey supports

Private peering physical requirements

• Standard port types: 10G Duplex Ethernet LR (LAN-PHY), 100G Ethernet LR4
• Link aggregation via LACP, prefer even for single links
• No support for high-MTU “jumbo frames”
• Optical physical layer: Single Mode Optical Fiber
• Direct point-to-point links only, only one device on each side, no support for switches in path to multiple routers or MLAG
• Only /30 & /31 IPv4 subnet sizes supported

BGP configuration requirements

• No support for MED
• No support for multihop
• Prefer MD5 authentication
• Most specific prefix accepted /24 (IPv4), /48 (IPv6)

Traffic requirements – public peering

Comnet Turkey generally does not have a minimum traffic requirement for public peering (subject to any specific market conditions).

Although Comnet Turkey connects to Internet Exchange route servers where present, Comnet Turkey prefers to establish direct BGP sessions for traffic exchange.

Traffic requirements – private peering

For networks with sufficient traffic (generally above 10Gb/s), Comnet Turkey prefers private peering, also known as Private Network Interconnect (PNI)

Regional traffic requirement

In general, Comnet Turkey will only 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.

Routing policy

In general, peering sessions with AS61135 will advertise all COMNET-ASN routes. At times, local infrastructure requirements or constraints may result in a more limited set of routes being advertised via AS61135.

Traffic exchange preferences

For traffic exchange, Comnet Turkey will generally prefer private peering links over public peering links, and public peering links over route-server paths. We will generally not support public peering or route-server learned routes with a network where we have private peering links within the same continent. Note that via route-servers, Comnet Turkey only advertises aggregate routes

Maximum prefixes

We suggest peers set a max-prefix of 15,000 (IPv4) and 1,000 (IPv6) routes on peering sessions with Comnet Turkey.

Related ASNs

Alongside AS61135 and AS-COMNET-INT

Traffic Management

This section explains how Comnet Turkey does traffic management, and what we ask from peers.

Traffic delivery

Comnet Turkey Mostly:

• Carries traffic on our own network as close to users as possible
• Serves traffic from edge nodes (GGC) preferentially, then direct peering, then via indirect paths
• Optimizes traffic delivery for end-user performance
• Respects AS path length and prefix specifics when deciding how to exchange traffic with peers

At times our traffic may not follow these guidelines as a result of observed performance between Comnet Turkey serving locations and the end-user.

Routing announcements

Comnet Turkey asks that peers advertise all their routes in all locations where they peer with Comnet Turkey , unless an alternative route advertisement policy has been agreed. Comnet Turkey will manage traffic routing and delivery to ensure optimal performance for end-users.

Capacity augments

To ensure sufficient peering capacity in the event of an outage we recommend that peers connect with us at more than one location and augment their peering connections when peak traffic exceeds 50%.

If a peering port becomes full due to an outage or other capacity issue, then Comnet Turkey’s traffic management systems will overflow excess traffic to other peering ports or other alternative paths.

Comnet Turkey congestion management

Comnet Turkey can generally run peering ports at 100% capacity, with low (<1-2%) packet loss for most services. Peers should abide by the capacity augments guideline above.