Connection Agreement for DIX i2, which operates DIX, the Danish Internet eXchange, and THE_OPERATOR hereby enter into this Agreement on cooperation, as set out below, between the peering point and THE_OPERATOR’s network OP_NET. 1. Objective of this Agreement DIX, the Danish Internet eXchange is operated by i2. The general purpose of the peering point is to promote the use of data communications and to provide a framework for cooperation that will allow the users of the participating networks to communicate with each other in the easiest way possible. The cooperation will, by implication, follow the prevailing rules and practices of the worldwide IP-network, the Internet, which each of the participating networks are a part of. 2. Connecting OP_NET to the DIX 2.1 General provisions THE_OPERATOR establishes a network connection to one or more of the locations where the DIX is present. If this requires power, hosting or other services at these locations, this is not included in the present agreement and must be purchased separately. The DIX locations are described on the web page of the DIX, www.dix.dk. THE_OPERATOR may order one or more connections to the neutral DIX backbone network. Choice and configuration of terminal equipment must be made in consultation with the master operator in charge of the DIX (UNI-C). The following principles apply to the DIX backbone network: a) The connection must be implemented such that each network operator is able to control its internal traffic. Consequently, traffic being addressed within OP_NET will remain on OP_NET. b) Operators joining the neutral DIX backbone network are free to set up bilateral network connections independently of the DIX. c) Routing must be structured such that a network is always identified as being the same AS as ‘source as’ even when it involves more than one peering point. d) The connection is implemented by way of a BGP protocol. Currently BGP4 is being used. e) Each operator is free to determine its policy towards each of the other network operators connected to the DIX. f) IGP-protocols (RIP, IGRP, ISIS, OSPF, etc.) must not be used or transmitted on the neutral DIX backbone network. THE_OPERATOR will pay all costs related to connecting the OP_NET to the DIX. Correspondingly, i2 undertakes to cooperate with THE_OPERATOR in respect of the function of the peering point and also to provide the necessary assistance to THE_OPERATOR on normal terms. 2.2 Exclusion and disruption The parties are entitled to verify, by the use of spot checks, that the conditions applying to traffic on their own network are being adhered to. Under certain circumstances, i2 or THE_OPERATOR may disrupt the connection between the neutral LAN network and the OP_NET. These circumstances are: - if the operations are in conflict with the rules stipulated by international networks to which either OP_NET or other participating operators are connected. - if the users deliberately misuse the networks in any other way, or - if such use causes an unreasonable load to the network of individual parties or in any other way becomes a threat to the function and applicability of the network. Each party shall seek to contact the other before such disruption is effected. In matters of urgency, however, disruption may be effected immediately. Regarding the DIX, contact must be made to a member of the i2 operations staff. 3. International connections This Agreement confers no rights upon either party to use the other party’s international connections. 4. Rights All parties undertake to observe any and all rights owned by equipment and software suppliers servicing any other party connected to the DIX. 5. Liability a) No party to this Agreement can be held liable for indirect or consequential damage. b) All liability rests with the users of OP_NET with respect to the correctness and suitability of any and all information transmitted and any and all results thereby obtained. 6. Updating of equipment The parties are entitled to install new versions of equipment and software. 7. Other provisions 7.1 Transfer No party to this Agreement may transfer its part of this Agreement to any third party without the approval of the other party. THE_OPERATOR may, however, transfer its part of this Agreement to a sub-supplier or a service provider upon giving notice to i2 of such transfer. 7.2 Legal disputes Any dispute and controversy arising out of or in connection with this Agreement shall be referred to arbitration according to Danish law. 8. Duration of this Agreement This Agreement shall take effect as from the date of signature and remain in force until the end of the calendar year, after which it is extended automatically for the next calendar year unless terminated by either party giving three months’ notice in writing prior to the end of the year. 9. Agreed delivery & pricing The prices for each year are published on the website of the DIX, www.dix.dk, at the beginning of the year. At the beginning of this agreement, the following services are provided to THE_OPERATOR: Membership fee: DKK XXXXX for the current year DKK 22.000 for the next year (subject to change) XX ports of XX Gbit/s at _LOCATION_: DKK XXXXX for the current year DKK XXXXX for the next year (subject to change) 10. Contact persons i2 administrative contacts are: Martin Bech (primary) i2 DTU bldg. 356 DK-2800 Lyngby Denmark Tel: +45 35 888 200 Email: Martin.Bech@i2.dk Jan Ferré (secondary) i2 DTU bldg. 356 DK-2800 Lyngby Denmark Tel: +45 35 888 200 Email: netdrift@deic.dk i2 technical contacts are: i2 netdrift, DIX@uni-noc.dk, +45 35 888 222 OP_NET administrative contacts to be included on the Administrative contacts list and dix-adm mailing list are: Admin 1, Address, Phone, Mail Admin 2, Address, Phone, Mail OP_NET technical contacts to be included on the Technical contacts list and dix-tech mailing list are: Technical 1, Address, Phone, Mail Technical 2, Address, Phone, Mail OP_NET financial contacts (if different from the administrative contacts) are: Financial 1, Address, Phone, Mail Financial 2, Address, Phone, Mail 11. Signatures For and on the behalf of i2: For and on the behalf of THE_OPERATOR: