Balcan-IX Services Description

Transcription

1 Safe and easy communication Balcan-IX Services Description Annex B

2 A. Balcan-IX Services Description Balcan-IX, countrywide Internet Exchange platform in Romania, offers access to IP networks connected in all its Service Access Points (SAPs), hosted by the Neutral Collocation Center (NCC). Balcan-IX offers to its Customers two peering Services a Public Peering service and a Virtual Private Interconnect service, for private peerings. Public Peering allows free exchange of traffic between all the participants connected to the Balcan-IX SAPs. Virtual Private Interconnect consists in supplying a logical point-to-point connection between the equipments of two Public Peering Balcan-IX customers, in order to allow private exchange of traffic between them. Private peering agreements are in Customer s responsibility, the Balcan-IX platform works only as Layer 2 facilitator. The Balcan-IX platform has redundant and resilient network architecture. All SAPs are connected in a ring topology at 10G capacity. The flexible design allows introduction of new SAPs and upgrade of the existing capacity in order to dynamic adapt to customer needs. The Balcan-IX platform has an independent BGP policy, having its own ASN (24745). Definitions Capacity/ Bandwidth - traffic indicator representing the maximum bidirectional data flow (measured in Mbps/Gbps) that can be supplied on the connection(s) between Balcan-IX infrastructure and Customer s access equipment. AS - Autonomous System O reţea sau un grup de reţele IP care au o politică de rutare comună aflate sub administrarea unei organizaţii. Port load physical or logical (in case of port channeling) port capacity / bandwidth usage ratio at a specific moment. AS - Autonomous System a network or a group of IP networks controlled by a unique organization and having a common routing policy. ASN - Autonomous System Number number uniquely identifying each AS in Internet. ASBR - equipment routing traffic between Autonomous Systems. Page 2

3 B. Basic Funtionalities B.1. Access to the platform The Public Peering Service is mainly addressing the Customers hat already bought a collocation service (physical or virtual) in a NCC location. If Customer is not already collocated in a NCC location, the access to the platform may be provided through an access line assuring the connectivity between the Customer location (or a physical interconnection point) and the Balcan-IX SAP. The access line is a dedicated permanent point to point connection either optical or electrical Ethernet connection, assuring connectivity between Customer ASBR and the aggregation switch. B.2 Port The Services offered by the Balcan-IX platform are supplied through 100 Mbps / 1 Gbps / 10 Gbps Ethernet ports. If the Service is delivered over optical ports, the Customer equipment must be equipped with a transceiver compliant with the specifications from the Annex 2. All ports support a traffic load up to the maximum port speed / No software limitation shall be applied, the traffic will be limited by the hardware port capacity only. Port channeling (LACP) For bandwidths higher than 1 Gbps, a number of 2 or 4 Gbps physical ports may be aggregated in a logical port, using the port channeling function. The bundling of many physical ports in a logical port shall be made using the LACP protocol. The logical 2 Gbps or 4 Gbps ports shall be delivered according to the resources availability in the requested locations. This is why Customer and Provider shall agree in advance the bandwidth parameters and the implementation schedule. The Provider will assure, though being limited to the available resources, the connection of the port channel links over many modules of the same equipment. Access port load limit In order to maintain high quality Services and to avoid congestions within Balcan- IX, the Provider may request the Customer to upgrade the achieved capacity if the Port load exceeds 80% of the maximum contracted port capacity, longer than 120 hours/month. If the Customer does not take the necessary measures to reduce the port load (either through capacity upgrade, either through traffic reduction) in the next 30 days from the Provider request, the Customer will be obliged to pay a penalty fee equal to the monthly fee of any Service supplied over the congested port. If no measure is taken in the next 30 days from the request, the Provider has the right to suspend the implied Services as to the capacity upgrade. A single MAC address will be allowed per VLAN, for each Customer. Customers may change the MAC address for free once a month. For more frequent MAC address changes, a fee will be charged, according to the tariff plan at that moment. The trunking function (dot1q) offers the Customer the possibility to connect through many VLANs. There is a limit of a maximum number of 10 VLANs/Customer/port (physical or logical). This functionality has a one time fee, charged at installation. The trunking function is applied at Customer request. Page 3

4 C. Public Peering Public Peering is a Service offering connectivity to the public peering community hosted by Balcan-IX. The Service is delivered through a public VLAN and a BGPv4 session with the route-server. Public Peering (PP) service allowing the free exchange of IP traffic between Customers, irrespective of the SAP of presence. C.1. Bandwidth Location 100 Mbps Bandwidth 1 Gbps 2 Gbps 4 Gbps 10 Gbps Bucureşti-Dacia * Bucureşti-Piscului * Bucureşti-NXDATA2 * Bacău * Cluj-Napoca * Constaţa * Galaţi * Iaşi * Oradea * Timişoara * C.2. IP Addressing An IPv4 address from the Balcan-IX range will be assigned by the Supplier for each Public Peering port (physical or logical). C.3. BGPv4 session with the router server Each Customer must maintain a BGPv4 session with the route server. C.4. The route server service The role of the route server is to facilitate the technical and commercial implementation of the Public Peering Service and also the access of new participants to the peering platform. Through the route server Service, the new members of the Balcan- IX platform will have instant access to the peering community, without the need to negotiate peering agreements with each partner. The route server collects routing informations from Customers and distributes them to the other peering participants routers, thus assuring the following: Page 4

5 a. System resilience (two route servers) - each Customer shall establish a BGPv4 session with the Route Server in order to advertise his routes; a second BGP session shall be established by each Customer with the backup Route Server. b. Filtering: b.1 Prefix list filtering: Customers prefix list will be filtered. The filters are generated automatically, based on the RIPE database records. b.2 Communities: Customers have the option to use selective advertising of their prefix lists by choosing one of the following communities types: Communities for blocking prefix advertising to a peer from a specific site. Communities for blocking prefix advertising to all the Public Peering members from one or more sites. Profil0065 Does not advertise to operators connected in SAP CD Does not advertise to the operator EF from SAP CD Parameters Value SAP ID 24745:21CD00 SAP ID Customer ID 24745:21CDEF Other functionalities - Balcan-IX ASN hiding (by demand) advertising of the Balcan-IX network prefix list without adding the AS_PATH attribute and the Balcan-IX ASN. - Advertisement of the prefix list with the original next hop of the originating Customer (default) - MED attribute (by demand) advertisement of the prefix list including the MED attribute as it was sent by the other members of the peering. Note: Balcan-IX ASN masking usually requires the reconfiguration of the peering session. C.5. SLA (Service Level Agreement) Provider guarantees availability for the Public Peering Service according to the terms in the Service Order Form. Note: Service Availability is measured taking into consideration the existence of two BGP sessions, with the main and the backup route servers. C.6. Secured traffic statistics & Monitoring The following Services shall be available via the Balcan-IX, web-site, -ix.net: Throughput traffic statistics daily, monthly, yearly; Looking Glass. Page 5

6 Access to the traffic statistics is available through username and password. The Customer is the only responsible for ensuring confidentiality of the data allowing access to these statistics. The Supplier may not be responsible in any way for unauthorized access to these informations. C.7. Customer Care Services The Balcan-IX platform is permanently monitored 24/7/365. Any issue may be announced by contacting the Balcan-IX customer care department, using the contact informations in Annex 1. D. Virtual Private Interconnection (VPI) for private peering (private VLAN) Virtual Private Interconnection (VPI) is a Service offered to Customers which previously purchased a Public Peering Service. Virtual Private Interconnection (VPI) involves a partnership between two entities - Initiator, considered as contact point and responsible for VLAN, and Partner the other party participating to the private peering service. A unique VLAN ID will be assigned by the provider to both service Customers of VPI. VPI service can be offered in two ways: either on a separate port, either on the same port with the Public Peering Service. When VPI Service is provided on the same port with Public Peering, the trunking / dot1q functionality must be enabled. A VPI port can carry up to 10 VLANs. Multiple VPI Services may be delivered on the same port, thus requiring the trunking/dot1q functionality (if not already active). Customer is responsible for the data transmitted through the VLANs, for the bandwidth limitation per VLAN and for the configuration required to establish the private peering session. Provider does not assign any IP addresses for private VLANs. D.1. Secured traffic statistics Throughput traffic statistics shall be accessible through the Balcan-IX web-site net, based on username and password. Statistics frequency: daily, monthly, yearly The Customer is the only responsible for assuring confidentiality of the data allowing access to these statistics. The Supplier may not be responsible in any way for unauthorized access to these informations. D.2. SLA (Service Level Agreement) Provider guarantees availability for the VPI Service according to the terms in the Service Order Form. D.3. Customer Care Services The Balcan-IX platform is permanently monitored 24/7/365. Page 6

7 Any issue may be announced by contacting the Balcan-IX customer care department, using the contact informations from Annex 1. E. Service components E.1. Interfaces 1. Access Interface - connects the access line to the customer equipment. This must be compliant with the Provider specifications from Annex Network Interface - connects the access line to the aggregation switch from the Balcan-IX SAP. E.2. CE ( Customer Edge) CE means the equipment used by the Customer for physical connection to the Balcan-IX platform, compliant with specifications from Appendix 2. CE must be a router / Layer 3 equipment. If a Layer 3 switch is used, each VLAN configured on the access line must map to a unique Layer 3 interface in the Customer network. E.3. Access Line (AL) AL is a point-to-point connection between the Customer equipment (router / Layer 3 switch) and the port from the Balcan-IX platform. E.4. Public VLAN A common environment with a unique VLAN ID for all SAPs is dedicated to traffic exchange between participants to the Public Peering Service. E.5. Private VLAN Private VLAN is a permanent Layer 2 point-to-point connection between the ports of two Customers connected to Balcan-IX. E.6. Routing Protocol BGPv4 will be used to announce the routes between Customer equipment and the route server. E.7. IP Address A Balcan-IX IP address is allocated per each port (physical or logical) assigned to the Public Peering Service. Page 7

8 F. Eligibility & Restraints F.1. Terms & Conditions i) Customers owning multiple ASNs may access the Public Peering Service in different sites by using different ASN per each site. ii) Customers may not use the Virtual Private Interconnect Service to connect ports located in different SAPs. F.2. Technical Specifications In order to participate to a Private Peering Service using Balcan-IX, the Customers must follow the technical requirements bellow: a) General conditions Customers shall own an ASN; Customer shall own at least one /24 IP Class; The equipment used for interconnect should have Layer 3 capabilities. b) For Public Peering and VPI i) Layer 1 Ethernet interfaces related to Balcan-IX ports shall be configured with explicit duplex and speed, and the other default settings. ii) Layer 2 Frames forwarded to Balcan-IX ports shall have one of the following ethertypes: 0x IPv4 0x ARP Frames forwarded to Balcan-IX ports shall all have the same MAC source address. ARP traffic will be limited to 20 pps per port/vlan. Frames forwarded to Balcan-IX ports shall not be addressed to a multicast or a broadcast MAC destination except for ARP traffic. Traffic from local-link protocols shall not be forwarded to Balcan-IX ports, except for the APR traffic. Note: Local-link protocols not permitted by Balcan-IX, include but are not limited to: o IRDP o ICMP redirects o IEEE802 Spanning Tree o Discovery protocols (ex. CDP) o Broadcast or multicast traffic generated by routing protocols (ex. OSPF, IS- IS, IGRP, EIGRP) o BOOTP/DHCP o PIM-SM o PIM-DM o DVMRP c) For Peering Public Service IP Layer 3 Interfaces connected to Balcan-IX ports shall only use IP addresses and netmasks assigned by Provider. Page 8

9 IPv6 addresses are not supported; IP Packets addressed broadcasted on the Public Peering VLAN will not be automatically forwarded to Balcan-IX ports. i) Routing BGPv4 is the only protocol that shall be used by Customers to exhange routing informations The Customers shall use a public ASN in order to establish a BGPv4 session with the Balcan-IX route servers. Advertised IP addresses shall be as aggregated as possible. IP addresses assigned to Balcan-IX VLAN shall not be advertised to other networks without explicit permission of Provider. All routes advertised across the Balcan-IX peering platform shall only announce their source router, except for other specific agreements. All advertised routes across Balcan-IX shall be registered at RIPE or any other internet registry. ii) Forwarding The traffic shall be forwarded to a Balcan-IX Customer only after his own routes advertisement or according to a written agreement. G. Additional Services 1. IP Transit IP Transit Services are available in Balcan-IX SAPs. These services are operated on a different infrastructure and delivered on a different access port. Note: If Customer requires a Public Peering Service and an IP Transit Service, the access to Romtelecom IP network will be provided on different port, in the following ways: Differentiated bandwidth for Romtelecom peering; Common Bandwidth for Romtelecom peering and IP Transit. These services are supplied using a different contract. 2. L2 Connect/ Clear Channel The Ethernet virtual connectivity point-to-point Services (L2Connect, Clear Channel are available on Balcan-IX SAPs. These services are operated on a separate infrastructure from Balcan-IX platform and delivered on a different access port. These services are supplied using a different contract. 3. Support Services Engineering services configuration works, Service optimization; On-site interventions involves all operations requiring personnel displacement to NCC locations outside business hours (e.g.: cabling, resets); Remote hands operations that do not require personnel displacement (cable checking, modules and equipment resets/replacements (no configuration works included) supplied during business hours, in SAPs served by personnel) Page 9

10 Annex 1 - Contact Points 1. Commercial Contact Points: Provider Phone: ; Facsimile: sales@balcan-ix.net Customer Peering Policy: 2. Technical Contact Points: Provider Phone: Facsimile: tech_support@balcan-ix.net Customer 3. Customer Care Contact Points: Provider Phone: Facsimile: customer_services@balcan-ix.net Customer Page 10

11 Annex 2 - Technical specifications for Customer EDGE a) Interfaces Interface 100BASE-TX Fast Ethernet 1000BASE-T Gigabit Ethernet 1000BASE-X Gigabit Ethernet 10GBASE-SR TenGigabit Ethernet 10GBASE-LR TenGigabit Ethernet Features Standard interfaces complaint with IEEE802.3u Transfer rate 100 Mbps UTP cat. 5 RJ-45 Connector Length max 100 m Standard interfaces complaint with IEEE802.3ab Transfer rate 1000 Mbps UTP cat. 5e RJ-45 Connector Length max 100 m Standard interfaces complaint with IEEE802.3z Transfer rate 1000 Mbps FO cable SC/PC Connector or LC/PC multi-mode FO 50/125 microns, 850nm, for SX single-mode FO 9/125 microns, 1310nm, for LX single-mode FO 9/125 microns, 1550nm, for ZX Length max 550 m 1000Base-SX max 5 km 1000Base-LX max 70 km 1000Base-ZX Standard interfaces complaint with IEEE802.3ae Transfer rate: 10 Gbps duplex SC/LC Connector FO cable multi-mode FO,850nm Length: max 300 m multi-mode FO 62,5/125 microns 850nm, Length: max 33 m Standard interfaces complaint with IEEE802.3ae Transfer rate: 10 Gbps SC/PC Connector or LC/PC duplex FO cable multi-mode FO 9/125 microns, 1310nm, Length: max 10 km b) Hardware & Software additional informations: - Supports BGPv4 routing protocol; - Supports WAN connectivity (Fast Ethernet, Gigabit Ethernet, 10 Gigabit Ethernet); - Enough memory to store the routing table; - Supports automatically update for BGP routing, BGP soft reconfiguration, BGP dampening, BGP communities. Page 11