Customer must be a recognized legal entity and must use an Autonomous System Number (AS) issued by a recognized Regional Internet Registry (RIR). The RIR for Russian Federation is RIPE NCC (http://www.ripe.net).
Customer's use of Service shall at all times conform to the relevant standards as laid out in IETF STD0001 document (http://www.rfc-editor.org/rfcxx00.html).
Customer must register and maintain the actual state of its AS routing policy in one of the following Internet Routing Registries (IRR): RIPE, ARIN, or RADB.
Customer must disable auto-sensing and explicitly define configuration (duplex, speed, etc) of all interfaces connected to MSK-IX Network.
On all interfaces connected to MSK-IX Network, Customer must disable ARP proxy, Broadcast forwarding, Spanning tree, IP Redirects, CDP, and all kinds of layer2 broadcast except for ARP and ICMPv6 Neighbor Discovery. Customer must forward multicast Ethernet frames only to Multicast VLAN.
Customer must communicate to Service Provider the MAC addresses of all interfaces connected to MSK-IX Network.
Customer must send Ethernet frames from an interface connected to MSK-IX only to MAC addresses learned via that interface.
Customer must send Ethernet frames from only one MAC address for every physical interface that belongs to Common or to Multicast VLAN of MSK-IX Network.
Customer must forward to MSK-IX Network only Ethernet frames of the following types (http://www.iana.org/assignments/ethernet-numbers): 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6.
Customer must use on all interfaces connected to MSK-IX Network only IP addresses and netmasks allocated by Service Provider. Customer must not announce IP addresses of MSK-IX Network without prior written consent of Service Provider.
Customer must use BGP4 protocol for establishing peering sessions on Common VLAN.
Customer must use MSDP/MBGP protocols for establishing peering sessions on Multicast VLAN.
Customer must forward traffic via MSK-IX Network only to addresses announced to Customer via MSK-IX Network.
Provisions of Sections 14.1-14.4 apply for Customer's use of Route-Server (RS) service.
14.1. For all prefixes originating from Customer's AS and announced to RS (AS8631), Customer must register and maintain the actual state of route and/or route6 objects in one of the following Internet Routing Registries (IRR): RIPE, ARIN, or RADB.
14.2. Customer should establish BGP sessions with every route-server of MSK-IX Network in accordance with the details published at Service Provider's web site.
14.3. Customer's announcements of prefixes to RS (AS8631) must be conformant with routing policy description in IRR database. In particular, the last AS number in the AS_PATH attribute of the announced prefixes must match the origin field of the corresponding route and/or route6 object in IRR database.
14.4. Customer must not announce to RS (AS8631) private addresses, private ASes, default route.
In the event of breach of Technological Requirements by Customer, 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 Quarantine VLAN operated in conformance with Service Description.
Service Provider shall restore configuration of Customer's port(s) within 24 (twenty-four) hours upon reception by Administrative and Technical Representatives of Service Provider of Customer's notification that the breach has been cured and positive verification by Service Provider of Customer's compliance with Technological Requirements.