OPERATING RULES OF NIX.CZ ASSOCIATION

(Version 9.0 dated 12.1.2011 with effect from 1.2.2011)

Article I.
PREREQUISITES FOR MEMBERSHIP IN ASSOCIATION

1. 1.Each legal entity applying for membership in NIX.CZ Association shall comply with the following conditions:
1. a) carries out activities related to the Internet;
2. b) has been assigned their own Autonomous System Number (ASN). In case any legal entity applying for membership in NIX.CZ Association have not been assigned their own ASN, it is necessary to provide written permission from the owner of the ASN.

Article II.
PREREQUISITES FOR entering into customer contract with association

1. 2.1 Each legal entity requesting to enter into a customer contract with NIX.CZ Association shall comply with the following conditions:
1. a) Complies with the conditions set out in Clause.
2. b) Undertakes to comply with the conditions set out in these Operating Rules of NIX.CZ Association and in the Price list of NIX.CZ Association.

Article III.
OPERATING CONDITIONS

1. 3.1 Connection to NIX.CZ nodes shall be permitted after the relevant membership fee has been paid (by a member of the Association) or the service contract has been signed (by a customer of the Association).
2. 3.2 Each member/customer is obliged to cooperate with the employee of NIX.CZ Association who is in charge of establishing or maintaining the connection to NIX.CZ nodes. Any data circuit, cable or fibre connected to the NIX.CZ infrastructure shall be clearly identified by the name of the supplier and the name of the member/customer the service is provided to.
3. 3.3 Before connecting to the NIX.CZ infrastructure, each member/customer is obliged to enter and keep updated the following information on the Intranet of the Association:
1. a) operation contact containing:
1. i. telephone number available 24 hours a day, 7 days a week
2. ii. e-mail address to their NOC (Network Operation Centre);
2. b) e-mail addresses to be listed in the NIX.CZ contact register for the purpose of correspondence between members/customers;
3. c) Autonomous System Number (ASN) assigned to the relevant member/customer;
4. d) full canonical name for member’s/customer’s router to be registered in the reverse domains (in-addr.arpa and Ip6.arpa) within the domain name system assigned to NIX.CZ Association;
5. e) URL to member’s/customer’s website, if the member/customer requires a link from the website of the Association;
6. f) e-mail address for sending peering requests;
7. g) member’s/customer’s contact information.
4. 3.4 Members/customers are not entitled to use the NIX.CZ infrastructure for internal connection of their networks.
5. 3.5 Each member/customer shall be connected to the NIX.CZ node under their own Autonomous System Number (ASN). In case a member/customer is not the owner of the connected AS, it is necessary to provide written permission from the owner of the relevant AS connected to the NIX.CZ node.
6. 3.6 In case the stability and functionality of NIX.CZ equipment gets jeopardized by an equipment/connection belonging to a member/customer, the Association shall be entitled to block the relevant member’s/customer’s port until the problem has been resolved by the member/customer. Association employees will, in such a case, immediately inform the NOC contact (as registered on the Association Intranet) by e-mail. This obligation to inform does not apply to the automatic port blocking pursuant to Item 1 hereof.
7. 3.7 Technical operating conditions are set out in Annex I to these Operating Rules.

Article IV
OTHER CONDITIONS OF USING NIX.CZ NODE

1. 4.1 Members/customers shall make sure that their connection to the NIX.CZ node does not hamper the use of NIX.CZ services by other members/customers.
2. 4.2 Members/customers shall not use NIX.CZ to carry out any illegal activities.
3. 4.3 Members/customers shall not, in particular, monitor and record data transmitted through the common segment, except for short-term monitoring of the BGP-4 update, serving to trace routing problems. NIX.CZ Association may implement systems for statistical purposes and for monitoring the traffic through NIX.CZ in order to identify and remedy potential problems in individual members’/customers’ peering and in the NIX.CZ network workload.

Article V
INSURANCE and liability

1. 5.1 In the event of any claims for damage caused by any member/customer of the Association to another member/customer or to the Association itself, the case shall proceed pursuant to the provisions of the Commercial Code.

Article VI
RULES FOR entering NIX.CZ nodes

1. 6.1 The premises of NIX.CZ nodes may only be entered by member's/customer's employees if accompanied by the Association Director or an authorized person.
2. 6.2 Members/customers entering the premises of NIX.CZ nodes shall observe the safety regulations in the buildings where the NIX.CZ nodes are located.

Annex I
Technical Operating Conditions

1. PI/1. The common network segment of the NIX.CZ nodes is based on Ethernet technology (IEEE 802.3).
2. PI/2. NIX.CZ offers the following interfaces:
1. a) metallic port 10/100/1000 Mbps RJ45 – certain nodes only
2. b) optical 1Gbps port with SFP module SX (850nm – multimode) or LX (1310nm signlemode) – certain nodes only
3. c) optical 10Gbps port with SR module; (850nm – multimode) or LR (1310nm singlemode)
4. d) other, not mentioned modules, specified by responsible employees of the Association (especially modules ER, ZR etc.)
5. e) interfaces for the ports installed before 1.1.2011 are according to operating rules valid at the time of installation.
3. PI/3. Several physical ports of one member/customer of at least 1GB link speed terminated on the same NIX.CZ switch can be grouped into one logical port (Etherchannel). Ports group is configured statically, no dynamic negotiation protocols are allowed. Each member/customer undertakes to realize such connection by means of direct connections to their border router without any additional L2 equipment.
4. PI/4. Each member/customer single-channel link is limited to 2 source dynamic MAC addresses. A multiple channel connection (Etherchannel) is limited to 1 MAC address only on the logical port (configured by Association employees).
5. PI/5. Ethernet frames forwarded by the connected equipment into the common network segment shall have of one of the following ether-types:
1. a) 0x0800 - IPv4;
2. b) 0x0806 - ARP;
3. c) 0x86dd - IPv6;
4. d) 0x9000 - loopback/keepalive.
PI/6. All frames forwarded into the common network segment shall not be addressed to the multi-cast or broadcast MAC address, with the following exceptions:
1. a) ARP broadcast;
2. b) IPv6 neighbour discovery
3. c) others based on permission by NIX.CZ Association
6. PI/7. Traffic for link-local (see Item 8) protocol shall not be forwarded into the common network segment, with the following exceptions:
1. a) ARP (except Proxy-ARP);
2. b) IPv6 neighbour discovery.
7. PI/8. Link-local protocols (PI/7) include but are not limited to the following list: IRDP, ICMP redirect, IEEE 802 Spanning Tree, vendor discovery protocols (CDP etc.), internal routing protocols (OSPF, ISIS, EIGRP), BOOTP/DHCP, PIM-SM/PIM-DM, DMVRP, IPv6 router advertisement and others.
8. PI/9. Traffic generated by ARP shall not exceed 20 packets per second.
9. PI/10. Newly installed ports are initially connected to the isolated testing segment to verify whether the member’s/customer’s equipment is configured correctly. Connection to the production network is possible only after all detected defects are removed.
10. PI/11. In the event of exceeding the maximum number of allowed MAC addresses at one port/link, the related switch port is automatically blocked to ensure stability for the switches of the Association.
11. PI/12. Ports connected to the common network segment shall use only the IP address and network mask assigned by the responsible employee of NIX.CZ Association. One physical (logical) port is assigned with one IP address IPv4 and potentially with one IPv6 address (if required by the member/customer).
12. PI/13. IPv6 addresses shall be statically configured (no use of automatic configuration). IPv6 site local addresses shall not be used.
13. PI/14. Member’s/customer’s port shall not forward to the common network segment any IP packets with the broadcast address of the common network segment.
14. PI/15. The routing protocol of NIX.CZ nodes is BGP-4 (RFC-4271) with possible extension to MP-BPG-4 (RFC4760, RFC-2545) – only unicast IPv4 and IPv6.
15. PI/16. Addresses of the common network segment shall not be advertised to other networks without explicit permission of NIX.CZ Association.
16. PI/17. Traffic from the port of one member/customer can be forwarded to the address of another member/customer only upon peering agreement and only via BGP-4 protocol (see PI/15).
17. PI/18. All routes advertised across the common network segment shall point to the router advertising it unless an agreement has been made in advance in writing by NIX.CZ and the members involved.
18. PI/19. The members/customers are recommended to:
1. a) register their routing policy for each connected ASN in the RIPE database and keep it updated;
2. b) for all networks advertised via BGP register a route (or route6) object in the RIPE database or similar register and keep it updated;
3. c) not generate useless “route flap”;
4. d) not advertise useless specific routes when peering with other members/customers of the NIX.CZ Association;
5. e) use an as-set object registered in RIPE database or similar register.
19. PI/20. Maximum Load per Port/ Ports overload Charge/ Additional Port Requirement
1. The load on the port/ports used by members and customers (further participants) may not exceed the following values for each port in more than 150h/month:
   1. FastEthernet           (100Mb/s)      90%
   2. GigabitEthernet      (1000Mb/s)    90%
   3. 10GigabitEthernet (10000Mb/s)  90%
2. If the portload (upload or download) exceeds the aforementioned value in more than 150h/month, NIX.CZ is entitled to charge an overload fee for the current month. The overload fee is equal to the cost of an additional equivalent port. The period of the port overload is based on the multiple of 5 minutes average values of the port overload above the declared limit. Regardless of the possibility of the overload fee being charged, the following applies: If the load on one or more ports (port-channel) exceeds the maximum allowed value within a period of two consecutive months or three times within a period of six months, NIX.CZ notifies the participant and asks him for the sake of maintaining quality to decrease the port load or after mutual agreement the participant will order another connection capacity upgrade.