Terms and SpecificationsTerms and Specifications
Technical terms for interconnection to the w-ix
1. The connection to the W-IX is done via crossconnections between the port equipment node W-IX and customer hardware.
Organization of the inhouse cabling is the customer responsibility.
2. Crossconnection interfaces could be the following types :
- 100Base-TX
- 1000Base-TX
- 1000 Base-LX
- 10000 Base-LR
3. The access to the W-IX can be implemented if the customer has its own Autonomous System (Autonomous System, AS) only.
4. The customer is obliged to keep up to date routing network policy of its own AS in the registry's of Internet routes (Internet Routing Registry, IRR) RIPE, ARIN, or RADB.
5. The customer shall disable auto-sensing mode at all interfaces and explicitly define the configuration interface (duplex, speed, etc.).
6. The customer shall disable ARP proxy, Broadcast forwarding, Spanning tree, IP Redirects, CDP, as well as all kinds of layer2 broadcast, with the exception of ARP and ICMPv6 Neighbor Discovery - at all interfaces .
7. The customer is obliged to indicate MAC-addresses of all logical interfaces used to connect to the W-IX.
8. The customer shall transmit Ethernet-frames only on the MAC-addresses, at each interface used for connection to W-IX, received via this interface.
9. The customer is obliged to send Ethernet-frames from the only one logical interface for each port dedicated to connect W-IX.
10. The customer is obliged to transmit only Ethernet-frames of the following types (http://www.iana.org/assignments/ethernet-numbers): 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6, as at general and on the multicast VLAN.
11. The customer is obliged to use on all interfaces utilized for connection to W-IX only allocated IP-address and netmask. Customer shall not announce IP-address W-IX third party.
12. The customer is obliged to use the BGP4 protocol to establish peering sessions.
13. The customer is obliged to direct traffic through the W-IX only into the networks, announced for the customer through W-IX.
13.1. Customer is obliged to keep up to date in the registry's Internet routes RIPE, ARIN, or objects such as RADB route and / or route6 for all its networks AS, advertised by the Customer in RS.
13.2. The customer is obliged to announce RS network in accordance with the description of routing policy of thes networks in the registry's Internet routes. In particular, the attributes AS_PATH announced networks last AS number must match the field of origin of the object like "route" and / or route6 in the registry's Internet routes.
13.3. Customer shall not advertise RS private network, private AS, the default route (default route).
14. The Customer undertakes to ensure the connectivity of its own network with other participants of W-IX.
15. The provisions of Sections 13.1-13.3 apply to the use of Route Server (RS) service.