Connection Policy

Member must:

Have registered AS number (autonomous system) and at least one IP prefix.
Maintain a complete and current https://peeringdb.com profile.
Use on the connection interface only those IP addresses and network masks which were provided by TurkIX, and only those MAC addresses which were reported to TurkIX.
Announce BGP prefixes in accordance with routing policy in RIPE, ARIN or RADB databases. In addition, maintain complete and current AS-SET objects. In addition, maintain complete and current ROA objects for the RPKI protocol.
Only announce prefixes with its own next-hop IP address.
Forward traffic only to BGP prefixes received from the connection interface to TurkIX. Do not use a static route on the connection to TurkIX, or otherwise send traffic to TurkIX through any route not received via BGP.
Not redistribute Peering LAN networks of the traffic exchange point (194.42.47.0/26, 2001:7f8:161::/64) beyond the member's router.
Transmit only Ethernet frames of types: 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6, 0x8100 - IEEE 802.1q.
Address Ethernet frames only to MAC addresses received on the connection interface to TurkIX, or to the broadcast address of ARP packets, or to the multicast address of the ICMPv6 Neighbor Discovery protocol.
On the interfaces connecting to TurkIX, disable all link-local protocols, Proxy ARP, IP directed broadcast, and IP redirects.

Examples of prohibited protocols: