The common network platform of the TurkIX nodes is based on Ethernet technology (IEEE 802.3).
Interfaces TurkIX Offers
> Copper port 10/100/1000 Mbps RJ45 - certain nodes only
> Optical 1Gbps port with SFP module SX (850nm - multimode) or LX (1310nm signlemode) - certain nodes only
> Optical 10Gbps port with LR module (1310nm singlemode)
> Other, not mentioned above modules, specified by responsible engineers of TurkIX (e.g. modules ER, ZR, SR etc.)
All Ethernet interfaces attached to TurkIX shall be explicitly configured with duplex, speed and other configuration settings and shall not be auto-sensing.
Member's use of TurkIX services shall at all times conform to the standards as laid out in IETF STD0001 and associated Internet STD documents.
> Frames forwarded to TurkIX ports shall have one of the following ether types:
> 0x0800 - IPv4
> 0x0806 - ARP
> 0x86dd - IPv6
All frames of a service forwarded to an individual port shall have the same source MAC address. Only one predefined MAC address is allowed on a service port. If any additional need arise, the number of associated MAC addresses may be increased by TurkIX. In the event of exceeding the maximum number of allowed MAC addresses the related TurkIX port is automatically blocked to ensure stability for the entire platform.
Member shall send Ethernet frames from an interface connected to TurkIX only to MAC addresses learned via that interface.
All frames forwarded to TurkIX ports shall not be addressed to a multicast or broadcast MAC destination address, with the following exceptions:
> Broadcast ARP packets
> Multicast IPv6 Neighbor Discovery (ND) packets
> Others, if explicitly allowed for that port (e.g. multicast service)
> Traffic for link-local protocols shall not be forwarded to NetIX ports except for the following:
> ARP except proxy ARP
> IPv6 Neighbor Discovery
> These link-local protocols include but are not limited to the following list:
> ICMP redirects
> IEEE802 Spanning Tree
> Vendor proprietary discovery protocols (e.g. CDP)
> Interior routing protocol broad/multicasts (e.g. OSPF, IS-IS, IGRP, EIGRP)
Use of proxy ARP on the router's interface to the NetIX is not allowed.
> On all interfaces connected to TurkIX Global Internet Exchange network only IP address and network mask assigned by TurkIX shall be used.
> IPv6 addresses shall be statically configured (no use of automatic configuration). IPv6 site local addresses shall not be used.
> IP packets addressed to TurkIX Global Internet Exchange peering LAN directed broadcast address shall not be automatically forwarded to TurkIX ports.
> All exchange of routes across the TurkIX Global Internet Exchange network shall be via BGP4(+).
> All AS numbers used for peering sessions across the TurkIX Global Internet Exchange network shall not be from range reserved for private use (64512-65535).
> Member shall forward traffic via TurkIX Global Internet Exchange only to addresses announced to the member via TurkIX.
> IP address space assigned to TurkIX Global Internet Exchange peering LAN shall not be advertised to other networks without explicit permission of TurkIX.
> Member shall not announce to Route Server (AS209702) private addresses, private ASes or default route.
The members are recommended to:
> Register their routing policy for each connected ASN in the appropriate RIR database and keep it updated.
> For all networks advertised via BGP register a route (or route6) object in the RIPE database or other public routing register and keep it updated.
> Use an as-set object registered in RIPE database or similar register.
> TurkIX Global Internet Exchange members are encouraged to do the best to aggregate their routes in accordance with RFC2519 (A Framework for Inter-Domain Route Aggregation).
> All prefixes advertised across the TurkIX Global Internet Exchange network shall have their next-hope attribute pointing to the IP address of the advertising router UNLESS agreement has been made in advance in writing by TurkIX and the members involved.
> Newly installed ports are initially connected to the isolated testing segment to verify whether the member’s equipment is configured correctly. Connection to the production network is possible only after all detected defects are removed.