Русский
MSK-IX / Internet Exchange / Technological requirements
← Go back
Technological requirements
Attention:

  1. Technological requirements are mandatory for observance by all Customers during the whole time of connection to MSK-IX.

  2. 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.

  3. 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.

  1. The Customer shall clearly specify the duplex speed and mode in their IX network connection interfaces of the types 10BASE-T, 100BASE-TX or 1000BASE-T.

  2. When using the Services, the Customer shall comply with the standards determined in IETF STD1 (http://www.rfc-editor.org/rfcxx00.html).

  3. Clauses 3.1 to 3.13 apply only to interfaces connecting to the public peering VLAN of the MSK-IX network.

    1. The Customer shall have the number of an autonomous system (“Autonomous System” or “AS”) registered with one of the regional internet registries (“Regional Internet Registry” or “RIR”). RIPE NCC is the registry covering the territory of the Russian Federation (http://www.ripe.net).

    2. The Customer shall maintain and update the data about the network routing policy of its AS in one of the following internet routing registries (“Internet Routing Registry” or “IRR”): RIPE, ARIN, RADB, AFRINIC, APNIC or LACNIC.

    3. The Customer shall turn off Proxy ARP, broadcast forwarding, spanning tree, IP redirects, Link Layer Discovery Protocols (LLDP, etc.), as well as the protocols of hardware manufacturers that initiate transmission of external Ethernet frames (CDP, Layer 2 keepalive, etc.), except for LACP, in the interfaces connecting to the IX network.

    4. The Customer shall provide the Contractor with the MAC addresses of all the logical interfaces used to connect to the IX network. For each physical interface used by the Customer to connect to the IX network, it is only permitted to use one MAC address, except during periods when the Customer’s equipment is being replaced, upon prior agreement with the Contractor.

    5. The Customer shall transfer Ethernet frames via each IX network connection interface, apart from ARP and ICMPv6 Neighbor Discovery, only to the MAC addresses examined via this interface.

    6. The Customer shall not transfer multicast Ethernet frames, except for ICMPv6 Neighbor Discovery, to the IX network via the Peering VLAN.

    7. The Customer shall transfer only Ethernet frames of the following types via the IX network (http://www.iana.org/assignments/ethernet-numbers): 0x0800 – IPv4, 0x0806 – ARP, 0x86dd – IPv6, 0x8100 – 802.1Q

    8. The Customer shall use only the IP addresses and network masks dedicated by the Contractor, in the IX network connection interfaces.

    9. The Customer shall not advertise the IP addresses of the IX network outside its AS.

    10. The Customer shall use the BGP4 protocol to establish peering sessions on the Peering VLAN.

    11. The Customer shall use only one number of the AS in each logical interface of the IX network connection for BGP4 protocol interactions.

    12. The Customer shall route traffic via the IX network only to the networks advertised to the Customer from the IX network and ensure that traffic is transmitted from the IX network to the networks advertised by the Customer in the IX network.

    13. The Customer shall specify the value of IPv4/IPv6 MTU as 1,500 bytes in the logical interfaces of the IX network connection.

    14. Clauses 3.14.1 to 3.14.5 shall apply only when the Customer uses the Route Server (RS) service.

      1. The Customer shall maintain and update route and/or route6 objects in the Internet Routing Registry for the networks of its AS advertised by the Customer on RS.

      2. The Customer shall establish BGP sessions with every route server of the IX network according to the data available on the Contractor’s website.

      3. The Customer shall advertise RS of the network in line with the network data routing policy in the Internet Routing Registry. In particular, in the AS_PATH attributes of the advertised networks, the number of the last AS shall match the ‘origin’ field of the respective route and/or route6 object in the Internet Routing Registry.

      4. The Customer shall not advertise private networks, private autonomous systems, a default route or the complete routing chart, on RS.

      5. The Customer shall advertise networks with a modified AS-PATH attribute on RS (the Customer’s AS shall be added to the attribute).

  4. Clauses 4.1-4.2 shall apply only to the private VLAN connection interfaces of the MSK-IX network.

    1. The Customer shall turn off the Spanning Tree protocol in the MSK-IX network connection interfaces, except for the Q-in-Q configuration.

    2. The Customer shall agree the maximum acceptable number of MAC addresses used for connection to the MSK-IX network, with the Contractor.

←Back to list
Categories