Service Description Consorzio TOP-IX...Service Description Consorzio TOP-IX Date 07/08/2018 Version 2.0 Via Maria Vittoria 38 10123 Torino P.IVA 08445410015 Tel. +39 011 8390191 Fax

Service Description

Consorzio TOP-IX

Date 07/08/2018 Version 2.0

Via Maria Vittoria 38

10123 Torino

P.IVA 08445410015

Tel. +39 011 8390191

Fax +39 011 8802619

[email protected]

www.top-ix.org

Consorzio TOP-IX: Service Description (07/08/2018) pag. 2/30


Indice

1 INTRODUCTION ................................................................................................................... 5

2 TOP-IX BACKBONE ARCHITECTURE ....................................................................................... 7

2.1 Access nodes to the infrastructure........................................................................................... 8

2.2 Interface and access standards to the infrastructure ............................................................ 10

2.3 Interconnection to the infrastructure ...................................................................................... 11 2.3.1 Direct access without housing equipment ........................................................................... 12 2.3.2 Direct access involving housing equipment ......................................................................... 12 2.3.3 Consortium service boundary ............................................................................................. 13

2.4 Infrastructure service types .................................................................................................... 15

3 PEERING SERVICE ............................................................................................................... 16

3.1 How to access the service ....................................................................................................... 16 3.1.1 Direct access ..................................................................................................................... 16 3.1.2 Remote access .................................................................................................................. 16 3.1.3 IX partner access ............................................................................................................... 17

3.2 Requirements for peering service access .............................................................................. 17

3.3 Route Servers .......................................................................................................................... 18

3.4 Peering agreements ................................................................................................................. 19

4 MARKETPLACE SERVICES .................................................................................................... 21

4.1 How to access the services ..................................................................................................... 21

4.2 Requirements for service access ............................................................................................ 21

5 TRANSPORT SERVICES ........................................................................................................ 23

5.1 How to access the services ..................................................................................................... 23

5.2 Requirements for service access ............................................................................................ 23

5.3 Additional included services ................................................................................................... 24


6 SERVICE SUPPLY PROCESS .................................................................................................. 25

6.1 Provisioning ............................................................................................................................. 25

6.2 Management ............................................................................................................................. 25

6.3 Maintenance ............................................................................................................................. 26

6.4 Operational communications .................................................................................................. 27

7 QUALITY STATEMENTS ....................................................................................................... 28

7.1 Provisioning ............................................................................................................................. 28

7.2 Management ............................................................................................................................. 28

7.3 Maintenance ............................................................................................................................. 29 7.3.1 Availability .......................................................................................................................... 29 7.3.2 Recovery time .................................................................................................................... 30

7.4 Performance monitoring activities carried out by TOP-IX ..................................................... 30

7.5 Access to traffic statistics ....................................................................................................... 30


1 Introduction Interconnection services offered to consortium members and partners by Consorzio TOP-IX (TOP-IX Consortium) are based on the use of a geographically distributed transmission infrastructure across North-West Italy, and designed to allow the following types of connection to be implemented:

• Peering using BGP protocol to implement sessions of mutual visibility between the Autonomous System of members and partners connected to the Internet Exchange infrastructure.

• Marketplace designed to allow the interchange of services (e.g. IP Transit, Cloud, remote Ethernet, etc.) between members and persons connected to the Internet Exchange infrastructure.

• Transit designed to implement point-to-point or multipoint connections for private requirements (e.g. backhauling) for members and persons connected to the Consortium infrastructure.

Any interaction between connecting bodies is carried out directly between the relevant parties involved without any technical or financial involvement from TOP-IX. The Consortium is solely responsible for providing the configurations required by members on the transmission structure.

Platform flexibility enables logically separate networks to be configured at Level 2. These networks are geared towards implementing the services listed above. In the first case, these are agreements free of charge with the forecast use of a VLAN (so called public peering) made available to all interested parties to whom IP Transit is not permitted. The other cases involve private agreements implemented on dedicated (private) VLANs and made available only to parties interested in the agreement itself. The Consortium has made available the following services in order to maximize infrastructure operations and facilitate traffic exchange between Consortium members:

• Route Server to facilitate and automate peering management operations between consortium members wishing to use the service;


• F-Root Server (with distributed architecture on multiple consortium data centres in order to guarantee a high degree of reliability) and J-root server.

Additional services may vary according to market needs and reference standards.


2 Top-IX backbone architecture The broadband interconnection infrastructure made available by the Consortium operates at Level 2 (Ethernet). It is highly reliable and widely available due to the redundant architecture characterizing both the local platforms that make up the network nodes and their interconnecting backbones. As shown in Fig. 1, the infrastructure currently covers all the main centers in the Piedmont and Valle d'Aosta regions, as well as some sites in the Milan metropolitan area.

Fig, 1 – TOP-IX infrastructure

TORINO (3)Via Livorno 60

(Colt)

TORINO (2)Corso Svizzera 185

(Itgate)

TORINO (1)Corso Unione Sovietica 216

(CSI Piemonte)

CUNEOCorso Soleri 2

(Provincia di Cuneo)

ASTI (1)Viale Pilone 111(Comune di Asti)

PONT SAINT MARTINViale Carlo Viola 76

(Engineering)

IVREAStrada Torino 50

(Provincia di Torino)

BIELLA (1)Via Quintino Sella, 12(Provincia di Biella)

VERCELLI (1)Via San Cristoforo, 3(Provincia di Vercelli)

MILANO (1)Via Caldera 21

(Infracom)

NOVARA (1)Viale Manzoni, 26

(Comune di Novara)

VERBANIA (1)Via dell’Industria 29/1 (retro)

(Tecnoparco)

FOSSANOVia Torino 166/168

(Unione del Fossanese)

VERRESVia Luigi Barone 8

(Politecnico di Torino)

ALESSANDRIALungo Tanaro Magenta 7/a(Provincia di Alessandria)

AOSTAVia Lavoratori Vittime col Du Mont 24

(Regione Valle d’Aosta)

RIVOLIAutostrada A32

(SITAF)

AVIGLIANAAutostrada A32

(SITAF)

BUSSOLENOAutostrada A32

(SITAF)SUSA

Autostrada A32(SITAF)

OULXAutostrada A32

(SITAF)

BARDONECCHIAAutostrada A32

(SITAF)

BRISSOGNELoc. Ile Blonde, 5

(Regione Valle d’Aosta)

CHATILLONVia Tornafol(Uffici CVA)

SANSECONDODI PINEROLO

Via della Repubblica 1

SETTIMO TORINESE (1)ATIVA - OADM CWDM(solo collegamento f.o.)

SAN GIUSTOATIVA - OADM CWDM(solo collegamento f.o.)

SETTIMO TORINESE (3)(Ospedale)

BIELLA (2)(Radio)

VERCELLI (2)(Radio)

NOVARA (2)(Radio)

ASTI (2)(Radio)

MILANO (2)Via Savona 125

(Equinix)

VERBANIA (2)(Radio)


2.1 Access nodes to the infrastructure Based on the specific features of components making up the local platforms and connected backbones, four types of node can be identified. Each node differs in terms of its level of reliability, robustness and performance.

• CORE: Core nodes feature robust, reliable and high-performance platforms comprising completely redundant equipment. The backbones connecting the nodes to the rest of the infrastructure (thereby creating a meshed network architecture across physically detached routes) have a link speed of 10 Gbps.

• BACKBONE: Backbone nodes feature reliable high-performance platforms. The backbones connecting the nodes to the rest of the infrastructure (thereby creating a meshed network architecture across physically and/or logically detached routes) have a link speed of at least 10 Gbps.

• EDGE: Edge nodes feature a reliable high-performance platform. The backbones connecting the nodes to the rest of the infrastructure have a link speed of at least 1 Gbps. However, the network architecture is only “meshed” in certain cases.”

• REMOTE ACCESS: These nodes are characterized by a passive "one way" interconnection infrastructure with CWDM / DWDM technology. This provides access to the active network infrastructure which is typically, but not exclusively, with radio devices.

CORE nodes TO001 TURIN Corso Unione Sovietica 216 (CSI Piemonte) TO002 TURIN Centro Piero della Francesca Corso Svizzera 185 (IT.Gate) MI001 MILAN Via Caldera 21 Palazzina D (Infracom) BACKBONE nodes AL001 ALESSANDRIA Lungo Tanaro Magenta 7/a (Municipality of Alessandria) AT001 ASTI Viale Pilone 103 (Municipality of Asti) BI001 BIELLA Via Quintino Sella, 12 (Province of Biella) NO001 NOVARA Viale Manzoni, 26 (Municipality of Novara) VB001 VERBANIA Via dell’Industria, 29/1 (Tecnoparco / Province of Verbania) VC001 VERCELLI Via San Cristoforo, 3 (Province of Vercelli) EDGE nodes TO003 TURIN Environment Park Via Livorno 60 (Colt Technology Services)


MI002 MILAN Via Savona 125 (Equinix ML2) CN001 CUNEO Corso Soleri 2 (Province of Cuneo) IV001 IVREA Strada Torino 50 (City of Torino) FOS01 FOSSANO Strada Torino 164/166 (Association of municipalities of Fossanese) PSM01 PONT SAINT MARTIN Viale Carlo Viola 76 (Aosta Valley regional government offices /

Engineering) VER01 VERRES Via Luigi Barone (Aosta Valley regional government offices / Polytechnic of

Torino) CHA01 CHATILLON Via Tornafol (Aosta Valley regional government offices / CVA) BRI01 BRISSOGNE Località Ile Blonde, 5 (Aosta Valley regional government offices / INVA) AO001 AOSTA Via Lavoratori Vittime col Du Mont 24 (Aosta Valley regional government offices) RIV01 RIVOLI lungo Autostrada A32 Galleria “La Perosa” lato Torino (SITAF) AVI01 AVIGLIANA lungo Autostrada A32 Casello lato Torino (SITAF) BUS01 BUSSOLENO lungo Autostrada A32 Galleria “Prapontin” (SITAF) SUS01 SUSA lungo Autostrada A32 PCC / Autoporto (SITAF) OUL01 OULX lungo Autostrada A32 cavalcavia SS335 (SITAF) BAR01 BARDONECCHIA lungo Autostrada A32, svincolo A32 direzione Torino (SITAF) REMOTE ACCESS nodes MI003 MILANO Via Caldera 21 (Caldera21 – CDLAN) (location with single connection to node MI001) AT002 ASTI Piazza Catena 3 (Municipality of Asti) (location with single connection to node AT001) BI002 BIELLA Via Fratelli Rosselli 2 (IIS “Sella”) (location with single connection to node BI001) NO002 NOVARA Via San Bernardino da Siena 10 (IIS “Nervi”) (location with single connection to node NO001) SSP01 S. SECONDO DI PINEROLO Via Repubblica 1 TOP-IX (Secondary school, “F.

Brignone”) (location with single connection to node TO001) VB002 VERBANIA Via dell’Industria, 29/1 (Tecnoparco / Province of Verbania) (location with single connection to node VB001) VC002 VERCELLI Piazza Risorgimento 12 (CCIAA) (location with single connection to node VC001) SG001 SAN GIUSTO CANAVESE lungo Autostrada A4 (GPS 45.320261N,7.816706E) (location with single connection to node TO001) SET01 SETTIMO TORINESE – lungo Autostrada A4 (GPS 45.159945N,7.751656E) (location with single connection to node TO001) SET03 SETTIMO TORINESE – Via San Cristina, 3 (Municipality of Settimo Torinese / Hospital) (location with single connection to node TO001)


PSM02 PONT SAINT MARTIN Viale Carlo Viola 76 (Aosta Valley regional government offices / Pépinière)

(location with single connection to node PSM01)

2.2 Interface and access standards to the infrastructure TOP-IX transmission infrastructure employs both copper and fiber optic Ethernet access interfaces. The access speeds listed below are available:

• 100 Mbps Ethernet switch port (Ethernet 100BASE-TX);

• 1 Gbps Ethernet switch port (Ethernet 1000BASE-T o 1000BASE-LX/LH); • 10 Gbps Ethernet switch port (10GBASE-LR);

• 100 Gbps Ethernet switch port (Ethernet 100GBASE-LR4). The technological platform used for the node governs both the type and speed of available infrastructure access port, and also the relative “standard”. As such, they are not uniform across the entire infrastructure. The following table highlights the potential available options for each node. TYPE OF NODE Ethernet

100 Mbps (copper)

Ethernet 1 Gbps

(copper)

Ethernet 1 Gbps

(optic fiber)

Ethernet 10 Gbps

(optic fiber)

Ethernet 100 Gbps

(optic fiber)

Passive Lambda

WDM

CORE - - X X X -

BACKBONE X X X X(1) - -

EDGE X X - - - -

REMOTE ACCESS - - - - - X(2)

(1) The 10 Gbps port in optical fiber is available for all BACKBONE nodes except for the AL001

(Alessandria) and AT001 (Asti) sites.

(2) The use of CWDM / DWDM passive Lambda for REMOTE ACCESS nodes is only possible in when combined with the request for a fiber optic port on an adjacent BACKBONE / EDGE node.


In the event that requirements differ to those outlined, TOP-IX may choose (based on project parameters) to use an alternative type of interface. The true potential to employ a different standard, however, depends on the characteristics and features of each individual node and operating conditions. In the case of connections where multiple-port nodes are forecast, an LACP-mode configuration can be set-up. This allows users to join multiple Ethernet links and use them as if they were a single connection This type of connection must be compatible with the equipment and devices of the user wishing to use such a system format. In the specific case of ports that carry out solely the Transit function (therefore, excluding those that also perform Peering or Marketplace functions), it is possible to request to implement a QinQ tunnel (L2 double tagging) in order to free the user from the need to comply with the VLAN allocation plan used on the Consortium backbone. It should be remembered that the actual potential node interface availability can only be assessed case by case. In the event that a port is not immediately available, it is necessary to calculate the time required to upgrade the equipment. The backbone does not implement QoS (Quality of Service) management mechanisms. Any such performance requirements will be assessed case by case and managed on a project basis in line with the available operating platform potential.

2.3 Interconnection to the infrastructure Each individual Consortium member reserves the right to choose the type of access node and connection speed. Consortium members may also select one of the following alternatives: • Implement a direct connection from its own location to the selected TOP-IX node while

maintaining the equipment used to carry out interconnection activities onsite. • Use the housing location where the TOP-IX node is located to install equipment

required for interconnection activities.


2.3.1 Direct access without housing equipment In the event of direct access to the TOP-IX infrastructure, the connection from the member site to the Consortium backbone node should conform fully with specifications and standards stipulated by the Consortium. Forecast architecture for such types of connection are shown in Fig. 2a.

Figura 2a – Access without housing equipment

2.3.2 Direct access involving housing equipment In the event that members choose a housing location for their access equipment, only the internal re-activation from consortium member equipment to the TOP-IX node will need to comply with Consortium specifications and standards. Connection of the equipment to the member infrastructure is at the member discretion (in terms of band and standards to be adopted). Requesting parties are free to choose housing locations on the basis of the service offer and distance from their offices. The high-speed node connection operated by TOP-IX represents guaranteed service quality uniformity at all distributed architecture points.


Fig. 2b – Access with housing equipment

TOP-IX offers housing space at some nodes. This housing space is dedicated solely to accommodating transmission devices equal to 3 Rack Units. Details of the six sites where this accessory service is provided (which shall be considered included in interconnection service supply) - i.e. the port on the TOP-IX node - is shown in the following paragraphs. Any additional spaces and/or spaces at sites that do not foresee this accessory service must be requested as an additional service. In such cases the consortium should be contacted or, alternatively, the housing location operator may be contacted directly.

2.3.3 Consortium service boundary The boundary of the service offered by the Consortium is established by the Layer 2 physical port made available to the consortium member on the network node chosen by the member. The consortium members are responsible for supplying, where necessary, patch cord (copper and/or fibre optic), media adapters, etc. required for the link extension from the TOP-IX node port to its infrastructure or installed equipment.

Fig. 3 – TOP-IX Consortium service boundary



2.4 Infrastructure service types Three different types of service can be implemented on the TOP-IX platform. If required, these serves can share the same access port:

• Public Peering: basic function of the Internet Exchange in order to allow bilateral peering sessions (i.e. set up between two different ASs with direct BGP sessions) or multilateral peering sessions (i.e. set up by an AS towards a group of ASs through Route Servers);

• Marketplace: opportunity to buy and/or sell services such as IP Transit, cloud access, Ethernet and security, to/from other consortium members;

• Transit: opportunity to create private point-to-point or multi-point connections for backhauling requirements.

There are two different potential categories of ports depending on the services requested:

• Peering ports: ports reserved exclusively for public peering services. No Marketplace and Transit type services are permitted on these ports (100 Mbps / 1 Gbps / 10 Gbps / 100 Gbps speeds available);

• Marketplace and dedicated services ports: ports where users may request one or more of the available services, i.e. public peering and/or marketplace and/or transit (100 Mbps / 1 Gbps / 10 Gbps speeds available).


3 Peering service The TOP-IX Consortium offers members and partners access to the Layer 2 distributed Internet infrastructure in order to implement Internet peering agreements with other bodies/organizations/companies that are connected either directly or indirectly to its broadband backbone. The peering service may be used solely to implement BGP sessions of mutual visibility between Consortium members/partners. It is forbidden to use the public peering infrastructure of the Consortium for any other functions or operations, such as transit, resale of transit, etc.

3.1 How to access the service The peering service is available in the following three forms of access:

• Direct access;

• Remote access;

• Access though an IXP partner.

3.1.1 Direct access Direct access is used when the service user is directly connected to one or more active ports at nodes belonging to the TOP-IX infrastructure. The service can be provided either through "peering ports” or "marketplace ports".

3.1.2 Remote access Public peering services offered by the Consortium can be accessed through a partner (reseller). Resellers can be chosen from among those selected by TOP-IX. In such cases, any agreement shall be between the user of the service and the TOP-IX partner directly. The peering service extension (Layer 2) between the Consortium infrastructure and that of the service user shall be carried out by the reseller through the reseller infrastructure.


3.1.3 IX partner access The Consortium's public peering infrastructure is also available on the Internet Exchange, to which TOP-IX is interconnected (VSIX, Lyon-IX and France-IX). Members of these IXPs can request access to TOP-IX public peering from their own IXP. It will be the task of the IXP to act as an "intermediary" by extending the TOP-IX Level 2 to the applicant's port. This service is a “best effort” classified service and so the Quality Statements described below therefore do not apply.

3.2 Requirements for peering service access Access to the TOP-IX public peering service should be carried out in full compliance with the constraints and requirements outlined below. Physical layer: (applicable only to direct access users)

• The physical interfaces of devices connected to the TOP-IX infrastructure must comply with interconnection requirements defined in paragraph 2.2 (any exceptions must be agreed with TOP-IX and must be explicitly authorized by the latter.

MAC and VLAN layer:

• All frames sent to access ports to the Consortium public peering infrastructure should have the same MAC source address associated with the relative IP supplied by TOP-IX (a different MAC address, however, may be used for each supplied IPv4 and/or IPv6 if there are more than one).

• Public peering agreements are implemented on a single public VLAN. Peering agreements are free of charge with no transit service forecast.

• The TOP-IX public peering infrastructure does not allow the use of STP (spanning-tree protocol).

IP layer:

• All Layer 3 interfaces connected to the Consortium public peering infrastructure shall have IPv4 and/or IPv6 addresses provided by TOP-IX (no addresses other than those assigned may be used).


Routing:

• Peering sessions set up through the Consortium's public peering infrastructure shall use the BGP-4 protocol.

• AS numbers used during BGP sessions must be public and registered with an RIR (RIPE, etc.) in the name of the member/partner (the use of ASs from among those reserved for private use is not allowed).

• All specified routes should be clustered to the greatest extent possible.

• Any IP address (IPv4 and/or IPv6) assigned by TOP-IX may under no circumstances be announced by BGP

• All routes specified during peering sessions should be registered with RIPE or other public Internet Routing Registry.

3.3 Route Servers TOP-IX provides Route Server systems in order to facilitate and incentivize public peering on its infrastructure. These systems automate peering operations management between members and partners who use this tool. Route Servers do not route traffic but solely redistribute routes (arising from BGP protocol) between Consortium members. Doing so, a single BGP session can make available all the announcements generated by all the Autonomous Systems connected to the Route Servers. Each connected member can influence the performance of the Route Servers in order to change the system of forwarding announcements about its own networks to other users connected to the systems mentioned earlier. Interaction between individual users of the Route Server and other users takes place through BGP communities. BGP communities:

• allow/deny the forwarding of their own BGP ads to other members;

• change the MED parameter of their BGP ads to other members;

• request the "prepend" function of their BGP ads to other members. Route Servers are active on Autonomous System 25309, which has been assigned to TOP-IX. Details of the BGP communities to be used to influence the routing of their routes


to other members are available in the section relative to AS25309 on the RIPE website (RIR of reference for the region in which the Consortium operates).

https://apps.db.ripe.net/db-web-ui/#/query?searchtext=as25309#resultsSection

The role performed by the Route Servers inside the Internet Exchange architecture is highly-important. As a result, the systems are redundant. In order for these systems to be used correctly, it is therefore necessary to configure two BGP sessions. The use of the TOP-IX Route Server systems, however, remains at the discretion of each individual member, who can freely decide whether to use it or not.

3.4 Peering agreements Interaction between members is performed in peer-to-peer mode using BGP-4 protocol (Border Gateway Protocol - version 4) or BGP -4+ (for IPv6 protocol) without any direct technical or financial involvement by TOP-IX. This is implemented on a public VLAN where potentially interested parties or members can draw up peering agreements involving reciprocal visibility. Such agreements are free of charge with no transit service forecast. Additional included services The interconnection service described above also includes the following: • One or more IP addresses belonging to the TOP-IX Autonomous System (based on

the requested services) to be used in order to finalise connection agreements with other consortium members. TOP-IX may, at its own discretion, choose to provide additional IP addresses.


• Access to statistical data handled by TOP-IX concerning the traffic flow volume through the TOP-IX Consortium backbone port.

• Inclusion in the TOP-IX mailing list;

• System support for port configuration updates;

• System support for TOP-IX infrastructure malfunction, and consequent operating failure.

Consortium services do NOT include the following:

• Housing costs (1);

• Costs for consortium member site connection to TOP-IX site; • Consortium member equipment configuration.

(1) Some TOP-IX infrastructure nodes are included in the 3-rack unit used to host the requesting partner/member equipment. Any additional spaces that may be required may be requested from TOP-IX (and subject of a specific additional quotation) or requested directly from the Housing Location operator that houses the Consortium node.

3-rack units are available from the following nodes: TO001, TO002, AL001, AT001, BI001, NO001, VB001, VC001, TO003, CN001, IV001, FOS01, RIV01, AVI01, BUS01, SUS01, OUL01, BAR01 , AT002, BI002, NO002, SSP01, VB002, VC002, SET03.


4 Marketplace services Marketplace services are dedicated to allowing the resale of services (IP Transit, cloud access, Ethernet and security, etc.) between various consortium members directly connected to the TOP-IX infrastructure. The service includes solely Layer 2 transit between the two requesting parties. The services provided through the aforementioned transit are subject to agreements signed directly between the two members/partners involved.

4.1 How to access the services Marketplace services are available solely in direct access mode to the TOP-IX infrastructure and can only be provided on "Marketplace" ports.

4.2 Requirements for service access Access to the services should be carried out in full compliance with the constraints and requirements outlined below. Physical layer:


MAC and VLAN layer:

• All frames sent to access ports to the Consortium public peering infrastructure should have the same MAC source address associated with the relative IP supplied by TOP-IX (a different MAC address, however, may be used for each supplied IPv4 and/or IPv6 if there are more than one).

• Agreements (IP Transit, cloud access, etc.) are negotiated directly between Consortium members/partners without any third party interference.

• The TOP-IX infrastructure does not allow the use of STP (spanning-tree protocol).


IP layer:

• All Layer 3 interfaces connected to the Consortium Marketplace services infrastructure and used for the resale of services that foresee the employment of BGP sessions, shall have IPv4 and/or IPv6 addresses provided by TOP-IX (no addresses other than those assigned may be used).

Routing:

• Any IP address (IPv4 and/or IPv6) assigned by TOP-IX may under no circumstances be announced by BGP.

Additional included services The service also includes the following:

• One or more IP addresses belonging to the TOP-IX Autonomous System (based on the requested services) to be used in order to carry out any required BGP sessions;

• One or more VLANs to other Consortium members/partners (every individual VLAN may be set up solely between two members/partners);



• System support for port configuration updates;

• System support for TOP-IX infrastructure malfunction, and consequent operating failure.


• Housing costs (1);

• Costs for consortium member site connection to TOP-IX site;

• Consortium member equipment configuration.



3-rack units are available from the following nodes: TO001, TO002, AL001, AT001, BI001, NO001, VB001, VC001, TO003, CN001, IV001, FOS01, RIV01, AVI01, BUS01, SUS01, OUL01, BAR01, AT002, BI002, NO002, SSP01, VB002, VC002, SET03.

5 Transport services Transport services are exclusively dedicated to an individual member/partner of the consortium. Transit services allow dedicated Layer 2 connectivity to be carried out on behalf of the member/partner using ports that are active on the consortium infrastructure and assigned to the member/partner.

5.1 How to access the services Transport services are available solely in direct access mode to the TOP-IX infrastructure and can only be provided on "Marketplace" ports.

5.2 Requirements for service access Access to the services should be carried out in full compliance with the constraints and requirements outlined below. Physical layer:


MAC and VLAN layer:

• The service is aimed at allowing connectivity between Layer 3 devices of the Consortium members/partners. A limit is therefore imposed on the number of MAC addresses that can be routed through the TOP-IX infrastructure (this limit is necessary in order to guarantee the correct functioning of the backbone itself). The maximum number of MAC address accepted on a single interconnection port is equal to 2 for each requested VLAN.


• The TOP-IX infrastructure does not allow the use of STP (spanning-tree protocol).

5.3 Additional included services The service also includes the following:

• One or more IP addresses belonging to the TOP-IX Autonomous System (based on the requested services) to be used in order to carry out any required BGP sessions;

• One or more VLANs to other Consortium members/partners using transit services (VLAN employed for transit services may not be extended to other members/partners);



• System support for port configuration updates; • System support for TOP-IX infrastructure malfunction, and consequent operating

failure.


• Housing costs (1); • Costs for consortium member site connection to TOP-IX site;

• Consortium member equipment configuration.


3-rack units are available from the following nodes: TO001, TO002, AL001, AT001, BI001, NO001, VB001, VC001, TO003, CN001, IV001, FOS01, RIV01, AVI01, BUS01, SUS01, OUL01, BAR01, AT002, BI002, NO002, SSP01, VB002, VC002, SET03.


6 Service supply process The following sections describe the operational procedures and contact points for Provisioning processes (port and service activation/expansion/termination), Management processes (changes in configurations), and Maintenance processes (malfunction management).

6.1 Provisioning Requests related to activating/deactivating/modifying ports and/or services by Consortium members/partners should be made by filling in the form available from the Consortium website, https://www.top-ix.org (Internet Exchange/Subscription and Fees). Request forms should be sent by e-mail to the following address:

[email protected] During the request phase, the consortium member/partner is required to indicate the technical person responsible for coordinating activities on behalf of the consortium member/partner. Requests will be handled in the manner, and timeframes, stipulated in the "Quality Statements" section of this document. Should requests necessitate contractual changes being made, please refer to the Consortium website at https://www.top-ix.org ((Internet Exchange/Subscription and Fees) for current financial terms and conditions.

6.2 Management The operations management service offered by TOP-IX includes the implementation of any configuration modifications requested by consortium members/partners that do not affect the service contract agreement, or require hardware/software updates to the Consortium backbone platform. Operations do not include actions involving activating new ports, changes to speed or the discontinuation of existing ports (operations which should be handled as described in the “Provisioning” section).


Any requests to modify the configurations may be requested:

• By email to [email protected] (available only during normal business hours, from Monday to Friday, 9:00-13:00 and 14:00-18:00, public holidays excluded).

Requests involving this type of activity must be complete with all the necessary technical information in order to implement changes correctly. The minimum amount of information required in order to deal with the request is as follows:

• Details of the consortium member in charge of coordinating the activity.

• Detailed technical description of the request.

• Any impact of the modification on other consortium members and, if so, contact details of these members in order to implement the request.

Operations management service coverage as described above is active Mondays to Fridays, 0900-1300 and 1400-1800 (public holidays excluded).

6.3 Maintenance Maintenance services offered by the Consortium allow services to be restored swiftly in the event of TOP-IX infrastructure malfunction. Any faults or malfunction that interfere with the smooth running of infrastructure operations and, consequently the supply of services to consortium members, can be reported using the following methods:

• By email to [email protected] (available only during normal business hours, from Monday to Friday, 9: 00-13: 00 and 14: 00-18: 00, public holidays excluded);

• By telephone +39 011 0883150 (available 24/7). The contact details reported above are in use solely to report faults and malfunctioning that involve Consortium services. The contact numbers do not respond to issues regarding management activities (e.g. configuration modification, expansion, etc.) or


consortium member system components that do not come under TOP-IX service responsibility (i.e. Layer 2 port on TOP-IX node). It is also necessary to supply all relevant information in order to facilitate initial remote fault diagnosis, i.e.:

• Name of the consortium member affected by the fault or malfunction.

• Name and relevant details of the technical person appointed by the consortium member to deal with the fault.

• Number of active ports on the TOP-IX infrastructure and characteristics.

• Detailed description of the technical problem reported.

• Any impact of the fault on other consortium members (if known).

Maintenance service coverage as described above is active 24/7 and 365 days/year.

6.4 Operational communications In addition to the above, the mailing list, [email protected] is available to:

• communicate planned maintenance to the infrastructure carried out by the Consortium;

• report any malfunction or unforecast events that may impact on the services provided by the Consortium.

The same mailing list may be modified by the Consortium and used by members and partners to:

• report activities they have carried out that have an impact on the operations of other members and partners (for example changes to BGP announcements, etc.)


7 Quality Statements The Quality Statements described below concern procedures for implementation, maintenance and service management. They are to be considered the target set by the Consortium in order to guarantee consortium members an adequate level of quality. TOP-IX shall monitor actual compliance with defined parameters and take any necessary action to guarantee required values are maintained in the event of deviation or variance.

7.1 Provisioning Service activation time is subject to whether the type of port required is available on the infrastructure and, in particular, on the TOP-IX node platform in question. The following list describes the implementation times required following a request for certain activities:

• TOP-IX node port activation/expansion requiring no hardware expansion – The requested activity can be carried out within 3 working days.

• TOP-IX node port activation/expansion (requiring hardware expansion) - Implementation time to be defined (the Consortium shall assess the actions required for platform expansion and provide the requesting party with the estimated timeframes).

• Port activation/expansion based on customised interconnection project design.- Implementation time subject to nature of project design.

• TOP-IX node port discontinuation – The requested activity can be carried out within 3 working days.

7.2 Management Implementation times for any requested changes is a maximum of 3 working days from receiving the request, complete with all the information required in order to perform the work.


7.3 Maintenance

7.3.1 Availability The Consortium has set an annual minimum service availability target for each individual port of 99.95%. Actual availability for each individual port is calculated as follows:

Where: Availability The availability of the relative port, measured during the base

period. Base period The base period during which any downtime is measured, i.e. a

year. Σ Downtime The sum of all port downtime measured during the base period in

question. Analysis does not include standard scheduled maintenance and/or infrastructure update activities, which are carried out to ensure improved performance and reliability. These activities are managed on a per-project basis and planned in order to minimise any impact on service supply. Consortium members are notified in the following way and according to the following timeframes:

• by e-mail with 10 working days’ notice for activities with a significant impact on the services provided;

• by e-mail with 5 working days’ notice for activities with a limited impact on the services provided.


7.3.2 Recovery time The target times set by the Consortium to restore the service in the event of a failure on its infrastructure are as follows:

• 10 hours from reporting the malfunction in 95% of cases;

• 24 hours from reporting the malfunction in 100% of cases.

7.4 Performance monitoring activities carried out by TOP-IX The Consortium monitors router traffic from its infrastructure network in order to guarantee an efficient high-performance network and, when required, expand any particularly heavily loaded links. Infrastructure monitoring activities pay especially close attention to the following: • Infrastructure backbones to ensure adequate dimension.

• Ports used by consortium members in order to identify potential heavy traffic loads that might require an increase in transmission capacity.

The monitoring system also offers consortium members the following WEB-based information: • Analysis of total Consortium infrastructure router traffic (available to all members from

the Consortium website home page). • Analysis of traffic for each individual member port (available from the member area;

password protected).

7.5 Access to traffic statistics Access to information regarding allocated resources, active services, and traffic on individual interfaces is available to Consortium members and partners through the members area of the TOP-IX website, available at:

https://membersarea.top-ix.org

Documents

Service Description Consorzio TOP-IX...Service Description Consorzio TOP-IX Date 07/08/2018 Version 2.0 Via Maria Vittoria 38 10123 Torino P.IVA 08445410015 Tel. +39 011 8390191 Fax