fbpx fbpx

Fulfill the technical conditions

The date of the last review: 10.04.2017

These technical requirements define conditions of providing of DTEL-IX Services (further – Services) and its aim is to guarantee maximum protection and quality of Services provided to Member by DTEL-IX.

1. DTEL-IX Services may be provided to the Member (legal entity, existing Customer of DTEL-IX) that has an Autonomous System (AS) number and is registered in a Regional Internet Registry (RIR). The territory of Ukraine is under the RIPE NCC registry .

2. At all DTEL-IX connection interfaces the Member shall turn off the autonomous speed synchronization and duplex (auto-negotiation) function and shall clearly define its interface configuration.

3. At all DTEL-IX connection interfaces the Member shall turn off ARP proxy, Broadcast forwarding, Spanning tree, IP Redirects, CDP, as well as any type of layer2 protocols, except for ARP і ICMPv6 Neighbor Discovery. Multicast Ethernet frame transfer via DTEL-IX network shall be allowed exclusively on multicast VLAN.

4. The Member is obliged to inform DTEL-IX of all logic interface MAC addresses used for connecting to DTEL-IX.

5. At each DTEL-IX connection interface the Member shall transfer Ethernet frames only to the MAC addresses received via the interface.

6. For each individual DTEL-IX port, the Member shall transfer Ethernet frames on general and multicast VLAN from only one logic interface.

7. On general and multicast VLAN the Member shall transfer only Ethernet frames of the following types (http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml): 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6, 0x8100 — IEEE 802.1q. On private VLANs the Member shall transfer only  Ethernet frames of the 0x8100 type. Transferring any other types of frames should be mutually agreed by the Parties. 

8. The Member shall at all DTEL-IX connection interfaces use only the IP addresses and net masks provided by DTEL-IX. The Member shall not announce DTEL-IX IP addresses without prior written consent.

9. The Member shall use BGP4 protocol for establishing peering sessions on the general VLAN.

10. The Member shall use MSDP/MBGP protocols for establishing peering sessions on the multicast VLAN.

11. The Member shall direct traffic via DTEL-IX only to autonomous systems (networks) announced to the Member thought DTEL-IX.

12. It is prohibited for the Member to use “static route” on any DTEL-IX Members.

13. The provisions of Clauses 13.1-13.5 shall be applied only in case of use of Route Server (RS) service:

13.1 Filter update at DTEL-IX route servers for each Member is done automatically, with the use of the up-to-date records in RIPE, ARIN or RADB data bases once a day. The update time shall be determined by the technical team.

13.2 The Member undertakes to establish BGP sessions with each DTEL-IX route server.

13.3 The Member undertakes to announce to DTEL-IX route servers (AS31210) networks in accordance with their routing policy description at the RIPE, ARIN or RADB data bases. As well as in the AS_PATH attributes of the announced networks the number of the most recent AS must be identical with the origin field of the corresponding object of route and/or route6 type in the Internet Routing Registry.

13.4 The Member shall not announce to DTEL-IX route servers (AS31210) any private networks, private AS, default route, full view.

13.5 The Member shall keep up-to-date its autonomous system routing support policy information at the Internet Routing Registry (IRR) RIPE, ARIN or RADB.

13.6 The Member shall ensure no Route Leaking, i.e. shall not announce to DTEL-IX route servers any networks of its peering partners that have not been obtained from the peering partners DIRECTLY.

Should the Member breach the Technical Requirements provided in this Annex, DTEL-IX has the right to stop providing the Services and to move the Member’s port (ports) to quarantine VLAN having notified the Member ahead of time by sending a message via electronic mail to an administrative or technical representative of the Member.

The Member’s port (ports) configuration restoration can be done by DTEL-IX within 24 hours of receipt of an electronic mail message from the Member’s administrative or technical representative on elimination of the breach of the Technical Requirements provided in this Annex, as well as after a detailed inspection by DTEL-IX targeted at verification of the fact of elimination of the breach.