Policy of connection to UZ-IX network
Policy of connection to UZ-IX network Uz-IX is an infrastructure managed by Uzbektelecom JSС, where all Participants (peering partners) can exchange traffic between them directly.
This document describes the general technical characteristics, basic criteria and rules for establishing peer-to-peer interaction with data transmission network of Uzbektelecom JSC, defines the requirements and conditions to be observed by all Participants (peering partners) using Uz-IX traffic exchange point services.
This document may be regularly reviewed and subject to adjustment to ensure the quality of services provided at Uz-IX. Subsequent amendments to this document will take effect within 10 days from the date of posting of the new specifications on the Company’s official website.
The possibility of establishing a peer-to-peer connection is determined individually. Uzbektelecom JSC has the right to change this peer-to-peer policy at any time, in the prescribed manner.
The participant (peer partner) of Uz-IX must represent any legal entity and have its own Autonomous System Number (ASN) assigned by one local Internet registrar (Local Internet registry, LIR). When applying for participation in Uz-IX, the ASN must be correlated with the designated legal entity.
A request to establish a peer-to-peer connection must be sent by official letter to Uzbektelecom JSC.
This policy applies to both IPv4 and IPv6 address space.
General requirements:
- The Participant’s network (peering partner) must have an Autonomous System Number (ASN) registered with one of the 5 Regional Internet Registrars (RIR) and use BGPv4 protocol to establish a peering session.
- The participant (peering partner) must not break the peer-to-peer relationship by setting a default route, changing or transmitting the next hop address, etc. without the consent of Uzbektelecom JSC.
- The Participant (peering partner) is obliged to inform Uzbektelecom JSC about any emergency situations or scheduled works on the partner's side, which can negatively affect the peering connection via email.
- The participant (peering partner) should appoint a responsible specialist and give his contacts to Uzbektelecom JSC
- For interfaces connecting to Uz-IX of Ethernet 1000Base-X type, the participant (peering partner) must disable the automatic speed and duplex matching (auto-negotiation) on all interfaces connecting to UzIX and explicitly define the interface configuration.
- Ethernet frames transmitted in the Uz-IX network must have one of the following types
o 0x0800 - IPv4;
o 0x0806 - ARP;
o 0x86dd - IPv6;
o 0x8100 - IEEE 802.1Q VLAN-tagged frames.
- The participant (peering partner) is obliged to inform Uz-IX administrators about all MAC addresses of all logical interfaces used to connect to Uz-IX.
- The participant (peering partner) is obliged to transmit Ethernet frames on each connection interface to Uz-IX only to those MAC addresses received through this interface.
- All Ethernet frames that are routed through an individual port to the Uz-IX network must have a MAC address defined for that port.
- Ethernet frames transmitted to the Uz-IX network must not be addressed to a multicast or broadcast MAC address, except in the following cases:
o broadcast ARP;
o multicast IPv6 Neighbor Discovery (ND);
o when explicitly permitted by Uz-IX rules
- Link-local protocol traffic should not be transmitted to the Uz-IX network.
- The participant (peering partner) must disable the connection to Uz-IX on all interfaces:
o ARP proxy;
o Broadcast forwarding;
o IP Redirects.
- The list of prohibited protocols (this list is not limited to these protocols) includes:
o IRDP;
o ICMP Redirect;
o IEEE802 Spanning Tree;
o proprietary detection protocols (e.g: CDP or EDP);
o internal routing/multicast protocols (OSPF, IS-IS, IGRP, EGRP);
o BOOTP/DHCP;
o PIM-SM;
o PIM-DM;
o DVRM;
o L2 Keepаlive and others.
- ARP traffic must not exceed 20 packets per second per port.
- Only IP-addresses with the appropriate subnet mask (prefix lengths) allocated directly by Uzbektelecom JSC must be used on all interfaces to the Uz-IX network. Participant (peering partner) must not announce IP-addresses of Uz-IX network to a third party without prior written consent of Uzbektelecom JSC
- The exchange of routing information through the Uz-IX network must be carried out only via the BGPv4 routing protocol.
- AS numbers announced by the Participant (Peering Partner) over BGP must not be in the range reserved for private use.
- The Participant (peering partner) is obliged to direct traffic via the UzIX network only to networks that are announced to the Participant via the Uz-IX network.
- All routes that the Participant (peering partner) announces through the Uz-IX network must be listed in the RIPE or other registry of Internet Routes. The Participants (peering partners) may use more than one ASN for peering in the Uz-IX network, provided that the ASNs announced through the Participant (peering partner) are managed by the same technical service (NOC) and have common contact information, or under a separate written agreement with Uzbektelecom JSC.
- The participant (peering partner) has the right to apply filtering (AS, routes, prefix-limit), and, at the request of “Uzbektelecom” JSC, provide information about the applied filters.
- The participant (peering partner) must not announce networks more specific than /24.
- The participant (peering partner) must not block AS traffic belonging to the as-set of Uzbektelecom JSC, except for the cases of DDoS attacks from the network of Uzbektelecom JSC.
- The volume of traffic on a peer-to-peer connection must not exceed 75% of the permissible capacity of the connection. In the case of recycling more than 75%, the peering partner must take measures to increase throughput capacity.
In case the Participant (peering partner) of Uz-IX violates the requirements of this document, “Uzbektelecom” JSC reserves the right to disable or transfer the ports of this Participant (peering partner) to quarantine, having previously notified him by e-mail to the addresses of the administrative and technical representative. Restoration of the port configuration is carried out after elimination of violations and verification by Uz-IX technical specialists.
Peering policy at Uz-IX
“Uzbektelecom” JSC establishes direct BGP sessions with Participants (peering partners) at the following Uz-IX traffic exchange points with additional restrictions:
- ATS-244 - conditions and restrictions; Types of interfaces for connecting to the Uz-IX network: - 1Gbps GigabitEthernet (copper: 1000Base-T); - 1Gb/s GigabitEthernet (optics: 1000BaseLX, single mode fiber, dual fiber, 1310 nm, 10 km); - 10 Gigabit Ethernet (optics: 10000BaseLR Single-mode fiber, dual fiber, 1310 nm, 10 km);
- ATS-252 - conditions and restrictions; Types of interfaces for connecting to the Uz-IX network: - 1Gbps GigabitEthernet (copper: 1000Base-T); - 1Gb/s GigabitEthernet (optics: 1000Base-LX, single mode fiber, dual fiber, 1310 nm, 10 km); - 10 Gigabit Ethernet (optics: 10000Base-LR Single-mode fiber, dual fiber, 1310 nm, 10 km).
- ATS-233 - conditions and restrictions; Types of interfaces for connecting to the Uz-IX network: - 1Gbps GigabitEthernet (copper: 1000Base-T); - 1Gb/s GigabitEthernet (optics: 1000Base-LX, single mode fiber, dual fiber, 1310 nm, 10 km); - 10 Gigabit Ethernet (optics: 10000Base-LR Single-mode fiber, dual fiber, 1310 nm, 10 km).
- ATS-234 - conditions and restrictions; Types of interfaces for connecting to the Uz-IX network: - 1Gbps GigabitEthernet (copper: 1000Base-T); - 1Gb/s GigabitEthernet (optics: 1000Base-LX, single mode fiber, dual fiber, 1310 nm, 10 km).
Support for both IPv4 and IPv6 peering attachments is preferred.