Connection of the Participant to the exchange Network of DC “UA-IX” (hereinafter referred to as the Network) shall be performed by means of connection to the port of the nearest switchboard of DC “UA-IX”. The Participant shall be obliged to provide a galvanic isolation of its connection or to use a screened twisted pair combined with obligatory earthing on its part.
The Participant’s interface operating at 100 Mbps shall have a fixed (not automatic) speed and duplex configuration.
The following types of Ethernet-frames shall be allowed on the Participant’s ports: 0x0800 – IPv4, 0x0806 – AR, 0x86DD (IPv6) and 0x8100 (802.1Q – for hybrid ports).
Use of link-local protocols except for ARP shall be not allowed, in particular: IRDP; ICMP redirects; IEEE 802 SpanningTree; Vendorproprietarydiscoveryprotocols (i.e. CDP, EDP); Interiorroutingprotocolbroadcasts (i.e. OSPF, ISIS, IGRP, EIGRP); BOOTP / DHCP; PIM-SM; PIM-DM; DVMRP; ICMPv6 ND-RA; IPv6 ND.
IP packages addressed at 188.8.131.52 and 184.108.40.206 shall not be redirected in all ports of UA-IX (noipdirected-broadcast).
The Participant’s equipment shall comply with IEEE 802.3 standard.
In order to participate at the traffic exchange point it shall be necessary to confirm the following:
Availability of own autonomous system (hereinafter referred to as AS) registered in RIPE and recorded in RIPE database in a proper way (hereinafter referred to as RIPEdb).
Availability of an address block connected with this AS by appropriate records in RIPE database.
Availability of one set BGP peering at least and one stable operating path “own address block in the name of own AS” at least in the global routing table. The stability criterion is the statistics from the project RoutingInformationService (http://www.ris.ripe.net/) and the flap-statistics regarding the Claimant's address block. The test points shall be randomly selected by DC “UA-IX” in order to check the Participant for compliance with the requirements of this paragraph.
Interaction between the Participants shall be performed through BGPv4 by means of routing table exchange between the Participant’s router and the router of DC “UA-IX” (hereinafter referred to as RS). Besides, the traffic between the Participants shall be performed directly through the switchboard ports passing RS. Two interchangeable routers shall be used as RS; the Participant shall support identical BGP-sessions with each of them.
The Participanthave have to advertise routing tables of its AS to RS and have a right to advertise AS routing tables of its clients and partners provided that they accept routing tables of DC “UA-IX” obligatory.
The Participant shall be obliged to register its interaction policy with DC “UA-IX” in RIPEdb. RS shall accept the announcements of AS which are described in RIPEdb as announcements for DC “UA-IX” (AS15645) only from the Participant. RS shall not accept the announcements of private networks, the announcements of private AS, default announcements.
The Participant shall not announce the network dedicated to ensure operation of DC “UA-IX” (220.127.116.11/23).
The priority of the announcements obtained from DC “UA-IX” within the Participant’s autonomous system shall be higher that the priority of the same announcements obtained by other methods (except for cases of explicit agreement of the Participants).
The Ethernet frames which are received from the Participant’s port in the direction of other Participants of DC “UA-IX” shall have one fixed MAC address in the source field.
The Participant shall use the IP address and the netmask only which are dedicated to it by DC “UA-IX” on the router interface. Only this address can be used as a next-hop parameter for all Participant’s announcements.
The Ethernet frames shall not use broadcast MAC addresses, except for ARP packages. Use of proxy ARP on the router interface connected to DC “UA-IX” shall be not allowed.
The Participant’s port shall be in the quarantine mode during connection of a new Participant. The quarantine is an isolated segment of a local network in which there is only the monitoring system in addition to the Participant. If the monitoring system confirms full compliance of the port of a new Participant with the requirements prescribed in p. 1.2. – 1.15., the quarantine mode shall be disabled for the port.