circle left

Contents

1. Technical Requirements

2. Route Server Policies

3. Ts & Cs

4. Privacy

 

1. Technical Requirements

NetIX Ports

The common network platform of the NetIX nodes is based on Ethernet technology (IEEE 802.3).

 

Interfaces NetIX Offers

- Copper port 100/1000 Mbps RJ45 (802.3u, 802.3ab)
- Optical 1Gbps port with SFP module LX (13100nm singlemode, 802.3z)
- Optical 10Gbps port with LR module (1310nm singlemode, 802.3ae)
- Optical 25Gbps port with LR module (1310nm singlemode, 802.3cc)
- Optical 40Gbps port with LR4 module (1310nm singlemode, 802.3ba)
- Optical 100Gbps port with LR4 module (1310nm singlemode, 802.3ba)
- Other, not mentioned above modules, specified by responsible engineers of NetIX (e.g. modules SX, ER, ZR, SR etc.)

 

Physical Requirements

All Ethernet interfaces attached to NetIX shall be explicitly configured with duplex, speed and other configuration settings and shall not be auto-sensing.

 

Technical Requirements

Member's use of NetIX services shall at all times conform to the standards as laid out in IETF STD0001 and associated Internet STD documents.

 

MAC Layer

Frames forwarded to NetIX 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 NetIX. In the event of exceeding the maximum number of allowed MAC addresses the related NetIX port is automatically blocked to ensure stability for the entire platform.

Member shall send Ethernet frames from an interface connected to NetIX only to MAC addresses learned via that interface.
 

All frames forwarded to NetIX 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:

- IRDP
- ICMP redirects
- IEEE802 Spanning Tree
- Vendor proprietary discovery protocols (e.g. CDP)
- Interior routing protocol broad/multicasts (e.g. OSPF, IS-IS, IGRP, EIGRP)
- BOOTP/DHCP
- PIM-SM
- PIM-DM
- DVMRP

Use of proxy ARP on the router's interface to the NetIX is not allowed.

 

IP Layer

On all interfaces connected to NetIX Global Internet Exchange network only IP address and network mask assigned by NetIX 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 NetIX Global Internet Exchange peering LAN directed broadcast address shall not be automatically forwarded to NetIX ports.

 

Routing

All exchange of routes across the NetIX Global Internet Exchange network shall be via BGP4(+).

All AS numbers used for peering sessions across the NetIX Global Internet Exchange network shall not be from range reserved for private use (64512-65535).

Member shall forward traffic via NetIX Global Internet Exchange only to addresses announced to the member via NetIX.

IP address space assigned to NetIX Global Internet Exchange peering LAN shall not be advertised to other networks without explicit permission of NetIX.

Member shall not announce to Route Server (AS57463) 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.
- NetIX 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 NetIX 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 NetIX 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.


 

2. Route Server Policies

About Route Server

The Route Server (RS) is used to facilitate interconnection between multiple Internet routers. It is a network service that reduces the number of individually configured peering sessions between NetIX participants. NetIX operates two geographically diverse Route Servers for resilience.

Start Using Route Server

  RS1 RS2
AS Number AS57463 AS57463
IPv4 address 193.218.0.100 193.218.0.200
IPv6 address 2001:67c:29f0::A:5:7463:100 2001:67c:29f0::A:5:7463:200
AS-SET AS-NETIX-NET AS-NETIX-NET
Platform BIRD BIRD

Route Server Policy

Two policy groups are present:

Basic Routing Policy

- 57463:57463 -announce prefix to all members
- 57463:peer-as - announce prefix to AS peer-as
- 0:57463 - block announcement of prefix to all members
- 0:peer-as - block announcement of prefix to AS peer-as

Extra Routing Policy

- peer-as:999 - announce prefix with well-known community no-export
- 57463:65000 - set local preference 0
- 57463:65050 - set local preference 50

Connected IXPs

IXP Name ASN Communities Supported Community
AMS-IX 6777 Basic & Extra Routing Policy 64700:6777
DE-CIX Fra 6695 Basic & Extra Routing Policy 64700:6695
DTEL-IX 31210 Basic & Extra Routing Policy 64700:31210
EPIX War 48850 Basic & Extra Routing Policy 64700:48850
Equinix Paris 24115 Basic & Extra Routing Policy 64700:24115
ESPANIX 6895 Basic & Extra Routing Policy 64700:6895
FL-IX 63221 Basic & Extra Routing Policy 64700:63221
GR-IX Athens 50745 Basic & Extra Routing Policy 64700:50745
iHome 25478 Basic & Extra Routing Policy 64700:25478
InterLAN 39107 Basic & Extra Routing Policy 64700:39107
IX.br SP 26162 Basic & Extra Routing Policy 64700:26162
LINX 8714 Basic & Extra Routing Policy 64700:8714
LyonIX 43100 Basic & Extra Routing Policy 64700:43100
MiX 61968 Basic & Extra Routing Policy 64700:61968
MSK-IX 8631 Basic & Extra Routing Policy 64700:8631
Netnod 52005 Basic & Extra Routing Policy 64700:52005
NIX.cz 47200 Basic & Extra Routing Policy 64700:47200
NYIIX New York 13538 Basic & Extra Routing Policy 64700:13538
Peering.cz 61195 Basic & Extra Routing Policy 64700:61195
SOX 13004 Basic & Extra Routing Policy 64700:13004
Speed-IX 41441 Basic & Extra Routing Policy 64700:41441
Thinx 24748 Basic & Extra Routing Policy 64700:24748
UA-IX 15645 Basic & Extra Routing Policy 64700:15645
VIX 1120 Basic & Extra Routing Policy 64700:1120
W-IX 50384 Basic & Extra Routing Policy 64700:50384

Connected Content Generators

Company Community Tag Communities Supported
Akamai 20940 Basic & Extra Routing Policy
Facebook 32934 Basic & Extra Routing Policy
Google Global Cache 65535 Basic & Extra Routing Policy

Important

- If prefix with missing BGP community attribute or non-conformant with the list above is received, the prefix is accepted and announced to all members.
- All prefixes are set by default local-preference 100.
- Prefixes received with well-known no-export attribute (65535:65281) are announced with the attribute unchanged to members.
- To use BGP communities with 32-bit AS numbers set peer-as value as listed above.
- All 32-bit AS numbers are mapped by NetIX statically to 16-bit numbers:

 

Member ASN BGP Community (peer-as)
Azertelecom 196925 65003:317
CONNECTICORE SA 197580 65003:972
Euroweb 202129 65003:5521
Global Best Brands 200141 65003:3533
Histate Global Corp. 206776 65003:10168
Level Next Direct 200454 65003:3846
NetX 204281 65003:7673
Silistra Telecom 198228 65003:1620

Prefix Validation

NetIX validates prefixes at ingress on all route servers. The validation is based IRR Object presence. We are looking for a valid Route Origin Authorization (ROA) for all the announced prefixes in RADB Internet Routing Registry (IRR).

For any additional information on this matter you can contact us on noc@netix.net.

 

 

 

3. Terms and Conditions (Ts & Cs)

Still to come.

 

 

4. Privacy

We do not collect personal information on our website.

The information we use includes website visiting times, access times, operating systems, browser versions and other information unrelated to the user. This data helps us to keep track of our visitors, for example what pages they visit and for how long time. With this information, we can improve the efficiency and composition of our website.

The information you leave at our website is used only to send you information concerning your choice for example in job seeking sections or when you send a question via this website. In this case, the information you submit is used only for this specific purpose, unless you agree otherwise or is stipulated by law. We do not share this kind of information with third parties and we make every endeavour to ensure the correct use of it, but we can not guarantee and we have no control over the networks of a third parties through which visitors send their information to our website.

This website provides hyperlinks, which take you to another website of our partners, not controlled by NetIX and for that reason we are not liable for use or disclosure of data, collected through these websites.

 

 

circle right