Regulations

These regulations define requirements and conditions which all Participants using services of a point of exchange of KazNIX traffic have to observe. This document can regularly be reconsidered and be subject to adjustment, with the purpose to provide quality of the provided services on KazNIX. The changes made to this document in the subsequent come into force within 10 days from the moment of placement of new regulations on the official site of KazNIX.

General provisions

KazNIX is a neutral and independent infrastructure under control of "Kazakh Center of Network Information" where all Participants can exchange among themselves traffic directly.
The participant of KazNIX has to represent any legal entity and have own Autonomous System (Autonomous System Number, ASN) appropriated by one of regional Internet registrars (RIPE-NCC, APNIC, LACNIC, ARIN) or local Internet registrar (Local Internet registry, LIR). At filing of application on participation in KazNIX, ASN it has to be correlated to the specified legal entity.
When using of KazNIX of services, its Participants independently define the peering policy, as on the basis of separate bilateral agreements directly among themselves, and on the basis of the RS service (Route Server) or other services operating in structure of KazNIX.

Connection order

For connection to KazNIX the applicant fills out the questionnaire or submits the application in a free form for the email adress ixp-request@nic.kz where he whenever possible specifies:
  • full and short name of the organization - the legal entity;
  • the autonomous system number (ASN);
  • company details;
  • contact data (full name of the contact person, phone);
  • an estimated point of connection (the list of possible points of connection is published on the official site of KazNIX), the interface and speed of connection.
After coordination of technical capability and parameters of connection, the applicant signs the contract for services with "Kazakh Center of Network Information". Further, number of the contract will be the identifier of the Participant which the Participant will have to specify at the appeal to technical and administrative services KazNIX.
Connection to KazNIX is made by the organization of the connecting line between port on the equipment KazNIX and the equipment of the Participant.
After connection the Participant reports to administration of KazNIX about the readiness and together with technical specialists of KazNIX performs works on inclusion control. For the period of debugging works and testing, the port of the Participant can be placed in a quarantine.

Technical requirements

The participant when using of KazNIX of services has to conform to requirements of the standards defined in the document IETF STD1 (Official Internet Protocol Standards, http://www.rfc-editor.org/rfcxx00.html).
Physical level (Ethernet layer)
The participant is obliged to determine explicitly the speed and the mode of duplex in setting up the interfaces of connection to 10BASE-T, 100BASE-TX, 1000BASE-T KazNIX Network, etc.
Ethernet кадры, передаваемые в сети KazNIX должны иметь один из следующих типов (ethertypes, http://www.iana.org/assignments/ethernet-numbers):
  • 0x0800 - IPv4;
  • 0x0806 - ARP;
  • 0x86dd - IPv6;
  • 0x8100 - IEEE 802.1Q VLAN-tagged frames.
All Ethernet shots which go through individual port to KazNIX network have to have the MAC address defined for this port.
Ethernet the shots transferred to KazNIX network should not be addressed to the group or broadcasting MAC address, except for the following cases:
  • broadcast ARP;
  • multicast IPv6 Neighbor Discovery (ND);
  • when it is obviously authorized rules of KazNIX.
Traffic of link-local of protocols should not be transferred to KazNIX network, except for the following: ARP (except proxy ARP) and IPv6 ND. The list of the forbidden protocols (but it is not limited only to them) includes: IRDP, ICMP Redirect, IEEE802 Spanning Tree, proprietary protocols of detection (for example CDP or EDP), internal protocols of routing / multiple-address mailing (OSPF, IS-IS, IGRP, EGRP), BOOTP/DHCP, PIM-SM, PIM-DM, DVRM, L2 Keepalive and others.
Traffic of ARP should not exceed 20 packages a second on port / VLAN.
The standard size (MTU) of a shot Ethernet is 1554 bytes.
IP level
On all interfaces of connection to KazNIX network only the IP addresses with the corresponding mask of a subnet (prefix lengths) allocated directly with administration of KazNIX have to be used. The participant should not announce the IP addresses of KazNIX network to the third party without preliminary written consent of administration of KazNIX.
The standard size (MTU) of IP of a package is 1500 bytes.
Routing
Exchange of route information through KazNIX network on peer-to-peer VLAN(1299) has to be carried out only through the protocol of routing of BGP4(KazNIX ASN 44025).
Numbers AS announced by the Participant on BGP through peer-to-peer VLAN should not be from the range reserved for private use.
The participant is obliged to direct traffic through KazNIX network only to networks which are announced to the Participant through KazNIX network.
All routes which the Participant announces through KazNIX network have to be specified in RIPE or other register of Internet routes. Participants can use more than one ASN for peering in KazNIX network provided that ASN announced through the Participant are operated by the same technical service (NOC) and has the general contact information, or under the separate written agreement with administration of KazNIX.
Direction of traffic (Forwarding)
The participant of KazNIX has to direct traffic to other Participant of KazNIX through KazNIX network only in case:
  • the route was announced through KazNIX, directly or through RS service (or other services operating in structure of KazNIX);
  • permission in writing from other Participant to whom traffic will go is obviously got.
BGP Community Policy
  • BGP community attributes. Should be used if peer-as < 65535.
    0:peer-as - do no announce the prefix to the participant with the AS number peer-as
    44025:peer-as - announcement of a prefix to a participant with AS number peer-as
    0:44025 - ban on announcing the prefix to all participants
    1:peer-as - add one prepend for this prefix to the participant with the AS number peer-as
    2:peer-as - add two prepends for this prefix to the participant with the AS number peer-as
    3:peer-as - add three prepends for this prefix to the participant with the AS number peer-as

    The remaining BGP-community type 44025:* and 0-3:* are deleted.
    Other BGP-community type *.* are passed without restrictions.
  • BGP-extended-community attributes. Should be used if peer-as > 65535.
    ro:0:peer-as - do not announce the prefix to the participant with the AS number peer-as
    ro:44025:peer-as - announcement of a prefix to a participant with AS number peer-as
    ro:0:44025 - prohibition on prefix announcement to all participants
    ro:1:peer-as - add one prepend for this prefix to the participant with the AS number peer-as
    ro:2:peer-as - add two prepends for this prefix to the participant with AS number peer-as
    ro:3:peer-as - add three prepends for this prefix to the participant with the AS number peer-as

    The remaining BGP-community types ro:44025:* and ro:0-3:* are deleted.
    The rest of the BGP-community type *.*.* are passed without restrictions.
In case of violation by the Participant of KazNIX of requirements of the present regulations, the administration of KazNIX in the person "Kazakh Center of Network Information" reserves the right to disconnect, or to transfer ports of this Participant to a quarantine, previously having notified him by e-mail to the addresses of the administrative and technical representative. Restoration of a configuration of port is made after elimination of violations and check by technical specialists of KazNIX.