Technological requirements are mandatory for observance by all Customers during the whole time of connection to MSK-IX.
In the event of breach of the Technological Requirements by the Customer, the Service Provider has the right to notify via email Customer's Administrative and Technical Representatives and to disconnect Customer's port(s) from MSK-IX Network, or to transfer Customer's port(s) to the Quarantine VLAN operated in conformance with the Service Description.
The Service Provider shall restore configuration of Customer's port(s) within 24 (twenty-four) hours upon reception by Administrative and Technical Representatives of the Service Provider of Customer's notification that the breach has been cured and positive verification by the Service Provider of Customer's compliance with the Technological Requirements.
The Customer's use of Internet Exchange service shall at all times conform to the relevant standards defined in the list https://www.rfc-editor.org/standards.
The Customer must explicitly define the speed and duplex settings on the interfaces of type 10BASE-T, 100BASE-TX, 1000BASE-T connected to MSK-IX Network.
The provisions of Sections 3.1-3.15 apply only to the Customer's use of the interfaces connected to the Common VLAN or to the Multicast VLAN of MSK-IX Network.
3.1. The Customer must use the Autonomous System (AS) number obtained from one of the Regional Internet Registries (RIR). The RIR serving the Russian Federation is RIPE NCC (http://www.ripe.net).
3.2. The Customer must maintain an up-to-date routing policy description for every used AS in one of the following Internet Routing Registries (IRR): RIPE, ARIN, RADB, AFRINIC, APNIC, or LACNIC.
3.3. On all the interfaces connected to MSK-IX Network, the Customer must disable ARP proxy, Broadcast forwarding, Spanning tree, IP redirects, link-layer protocols (LLDP, etc.), and vendor-specific protocols sending extraneous Ethernet frames (CDP, Layer 2 keepalive, etc.), except for LACP protocol when connecting via EtherChannel.
3.4. The Customer must inform the Service Provider of the MAC addresses of all the logical interfaces connected to MSK-IX Network. A single MAC address per physical interface is allowed at all times, except for maintenance periods, which must be pre-agreed with the Service Provider.
3.5. On all the interfaces connected to MSK-IX Network, the Customer must send Ethernet frames only to MAC addresses learned via that interface, except when using ARP or ICMPv6 Neighbor Discovery protocols.
3.6. The Customer must send multicast Ethernet frames to MSK-IX Network only on the Multicast VLAN, except when using ICMPv6 Neighbor Discovery protocol.
3.7. The Customer must send to MSK-IX Network only Ethernet frames of the following types (https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml): 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6.
3.8. On all the interfaces connected to MSK-IX Network, the Customer must use only the IP-addresses and the network masks allocated to the Customer by the Service Provider.
3.9. The Customer must not announce the IP-addresses allocated by the Service Provider without the Service Provider's prior written consent.
3.10. The Customer must use BGP4 protocol to establish peering sessions on the Common VLAN.
3.11. The Customer using BGP4 must use only one AS number per interface connected to MSK-IX Network.
3.12. The Customer must use MSDP/MBGP protocols to establish peering sessions on the Multicast VLAN.
3.13. The Customer must forward traffic via MSK-IX Network only to the addresses announced to the Customer via MSK-IX. The Customer must ensure forwarding of the incoming traffic from MSK-IX Network to the addresses announced by the Customer via MSK-IX.
3.14. On all the logical interfaces connected to MSK-IX Network, the Customer must set the value of IPv4/IPv6 MTU to 1500 bytes.
3.15. The provisions of Sections 3.15.1-3.15.4 apply only to the Customer's use of the Route Server (RS) available at the Common VLAN of MSK-IX Network.
3.15.1. For the AS advertised by the Customer to the RS, The Customer must maintain an up-to-date description of the route and/or route6 objects in the IRR.
3.15.2. The Customer must establish BGP sessions with each of the BGP speakers of the RS in accordance with the peering information published on the Service Provider's web site.
3.15.3. The Customer's announcements to the RS must conform to the Customer's routing policy description in the IRR. In particular, the last AS number listed in the AS_PATH attribute must match the AS number in the origin field of the corresponding route and/or route6 object in the IRR.
3.15.4. The Customer must not announce to the RS private addresses, private AS numbers, the default route and the full routing table.
The provisions of Sections 4.1-4.2 apply only to the Customer's use of the interfaces connected to Private VLANs of MSK-IX Network.
4.1. On all the interfaces connected to MSK-IX Network, the Customer must disable the Spanning Tree protocol, except when using Q-in-Q.
4.2. The Customer must agree with the Service Provider the maximum number of MAC addresses to be used to connect to MSK-IX Network.