TOP-IX Consortium Service Description

DATE 01.03.2020

REV. 2020.03

Service Description 1. Introduction ...... 4 2. TOP-IX backbone architecture ...... 5 2.1 Access nodes to the infrastructure ...... 6 2.2 Interface and access standards to the infrastructure ...... 8 2.3 Interconnection of the infrastructure ...... 10 2.3.1 Direct access without housing equipment ...... 10 2.3.2 Direct access involving housing equipment ...... 11 2.3.3 Consortium service boundary ...... 12 2.4 Infrastructure service types ...... 13 3. Peering service ...... 14 3.1 How to access the service ...... 14 3.1.1 Direct access ...... 14 3.1.2 Remote access ...... 14 3.1.3 IX partner access ...... 15 3.2 Peering service access requirements ...... 15 3.3 Route Servers...... 16 3.4 Peering agreements ...... 17 3.5 Additional included services...... 17 4. Marketplace Services ...... 19 4.1 How to access services ...... 19 4.2 Additional included services...... 20 5. Transit services ...... 21 5.1 How to access the services ...... 21 5.2 Service access requirements ...... 21 5.3 Additional included services...... 22 6. Service supply process ...... 23 6.1 Provisioning ...... 23 6.2 Management ...... 23 6.3 Maintenance ...... 24 6.4 Operational communications ...... 25 7. Quality Statements ...... 26

Consorzio TOP-IX | Service Description v 2020.03 Pag. 2 di 28

7.1 Provisioning ...... 26 7.2 Management ...... 26 7.3 Maintenance ...... 27 7.3.1 Availability ...... 27 7.3.2 Recovery time ...... 28 7.4 Performance monitoring activities carried out by TOP-IX ...... 28 7.5 Access to traffic statistics ...... 28

Consorzio TOP-IX | Service Description v 2020.03 Pag. 3 di 28

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 , 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. In the second case, these are private agreements implemented on dedicated (private) VLANs and made available only to parties interested in the agreement itself. The final case covers private VLANs used by individual members of the Consortium and used by these individual members to interconnect ports assigned to them.

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 and J-Root Server.

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

Consorzio TOP-IX | Service Description v 2020.03 Pag. 4 di 28

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 centres in the and Valle d'Aosta regions, as well as some sites in the Milan metropolitan area

VB001 VB001

AO001 BRI01 CHA01

VER01

BI002 PSM01 PSM02 BI001

IV001 NO002 MI001 MI003

VC002 NO001 MI002

MI004

VC001 SGC01

SUS01

TO002 RIV01 SET04 BAR01 TO003 BUS01 SET03 AVI01 TO004 SET01 TO001 OUL01 RPC01

PIN01 AT001

FRO01 AL001 AT002 SSP01

FOS01

CU001

Fig. 1 - TOP-IX infrastructure

Consorzio TOP-IX | Service Description v 2020.03 Pag. 5 di 28

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 at least Nx10 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 TORINO Corso Unione Sovietica 216 (CSI Piemonte) TO002 TORINO Centro Piero della Francesca Corso Svizzera 185 (It.Gate) MI001 MILANO Via Caldera 21 Palazzina D (Irideos)

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) MI002 MILANO Via Savona 125 (Equinix ML2) MI004 MILANO Via Monzoro, 101-105 Cornaredo (Data4) NO001 NOVARA Viale Manzoni, 26 (Municipality of Novara) VB001 VERBANIA Via dell’Industria, 29/1 (Tecnoparco / Province of Verbania)

Consorzio TOP-IX | Service Description v 2020.03 Pag. 6 di 28

VC001 VERCELLI Via San Cristoforo, 3 (Province of Vercelli)

EDGE NODES

TO003 TORINO Environment Park Via Livorno 60 (Colt Technology Services) MI003 MILANO Via Caldera 21 (Caldera21 – CDLAN) CN001 CUNEO Corso Soleri 2 (Province of Cuneo) IV001 Strada Torino 50 (City of Torino) FOS01 FOSSANO Strada Torino 164/166 (Association of municipalities of Fossano) 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 lungo Autostrada A32 Casello lato Torino (SITAF) BUS01 lungo Autostrada A32 Galleria “Prapontin” (SITAF) SUS01 SUSA lungo Autostrada A32 PCC / Autoporto (SITAF) OUL01 lungo Autostrada A32 cavalcavia SS335 (SITAF) BAR01 lungo Autostrada A32 svincolo accesso A32 direzione Torino (SITAF)

REMOTE ACCESS NODES

AT002 ASTI Piazza Catena 3 (Municipality of Asti) (location with single connection to AT001 node) BI002 BIELLA Via Fratelli Rosselli 2 (IIS “Sella”) (location with single connection to BI001 node) NO002 NOVARA Via San Bernardino da Siena 10 (IIS “Nervi”) (location with single connection to NO001 node)

Consorzio TOP-IX | Service Description v 2020.03 Pag. 7 di 28

SSP01 S. SECONDO DI Via Repubblica 1 TOP-IX (Scuola Secondaria “F. Brignone”) (location with single connection to TO001 node) VB002 VERBANIA Via dell’Industria, 29/1 (Tecnoparco / Provincia di Verbania) (location with single connection to VB001 node) VC002 VERCELLI Piazza Risorgimento 12 (CCIAA) (location with single connection to VC001 node) SET03 – Via San Cristina, 3 (Municipality of Settimo Torinese / Hospital) (location with single connection to TO001 node) SET04 SETTIMO TORINESE – Piazza Freidano (Municipality of Settimo Torinese / Traliccio) (location with single connection to TO002 node) PSM02 PONT SAINT MARTIN Viale Carlo Viola 76 (Aosta Valley regional government offices / Pépinière) (location with single connection to PSM01 node) RPC01 RIVA PRESSO – Via Andriano 12 (former Embraco industrial area) (location with single connection to TO002 node) PIN01 – Via Pola 2-6 (Municipality of Pinasca) (location with single connection to TO001 node) FRO01 FROSSASCO – Via Rinaldo Asvisio 2 (Municipality of Frossasco) (location with single connection to TO001 node)

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 or 1000BASE-LX/LH); • 10 Gbps Ethernet switch port (10GBASE-LR); • 100 Gbps Ethernet switch port (Ethernet 100GBASE-LR4).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 8 di 28

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.

Ethernet Ethernet Ethernet Ethernet Ethernet Passive 1 Gbps 10 Gbps 100 Gbps TYPE OF NODE 100 Mbps 1 Gbps Lambda (optic (optic (optic (copper) (copper) WDM fibre) fibre) fibre) CORE - - X X X - BACKBONE - - X X - -

EDGE X X X1 X2 - -

REMOTE ACCESS - - - - - X3

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.

1 Assessed on a project-by-project basis after having checked availability on the local platform constituting the node. 2 Assessed on a project-by-project basis after having checked availability on the local platform constituting the node. 3 The use of passive CWDM/DWDM lambda for REMOTE ACCESS nodes is only possible when combined with the request for a fiber optic port on an adjacent BACKBONE / EDGE node. The lambda will allow direct interconnection between the applicant's equipment (active on the REMOTE ACCESS node) and the dedicated port on the adjacent TOP-IX node (CORE, BACKBONE or EDGE). The use of the lambda for other purposes (e.g. direct interconnection between the applicant's devices located at both ends of the link) is normally not permitted.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 9 di 28

In the specific case of ports that carry out solely Transit functions (i.e. excluding those that also perform Peering or Marketplace functions), users may request to implement a QinQ tunnel (L2 double tagging) in order for the user to avoid the need to comply with the VLAN allocation plan used on the Consortium backbone.

It should be remembered that 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 OF 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, whenever housing space managed by TOP- IX is available at the requested location.

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. (Section 2.2).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 10 di 28

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. (Section 2.2). Connection of the equipment to the member infrastructure is at 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.

TOP-IX offers housing space at some nodes equal to 3 Rack Units per site in shared space (200 Watt max of power consumption). This housing space is dedicated solely to accommodating transmission devices (installation of equipment such as servers, storage, etc. is not permitted).

Where provided, the service shall be considered included in the interconnection service operating at the site itself i.e. the ports on the TOP-IX node.

The 3 Rack Units can be requested from the following TOP-IX nodes The conditions of use of any three Rack Units included in the transport service at some TOP-IX nodes are those detailed in the document describing the housing services available on the Consortium website.: TO001, TO002, AL001, AT001, BI001, NO001, VB001, VC001, CN001, IV001, FOS01, RIV01, AVI01, BUS01, SUS01, OUL01, BAR01, AT002, BI002, NO002, SSP01, VB002, VC002, SET03, SET04, RPC01, PIN01, FRO01.

The conditions of use of any three rack units included in transit service at some TOP-IX nodes are detailed in the document describing housing services and available on the Consortium website.

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.

Third party equipment housed at Consortium nodes may only be interconnected to TOP- IX or Consortium equipment. Under no circumstances are direct copper or fibre optic connections between equipment of Consortium members allowed.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 11 di 28

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.

y Consortium member site

r

a

d

n

u

o

b

e Consortium member connection

c i

v (to TOP-IX node)

r Consortium member e

S infrastructure Housing Location Consortium member Consortium member peering router Housing location peering router internal connection

Nodo TOP-IX

Consortium member site Technical room Technical room

TOP-IX node Housing service y

r Consortium member a

d Consortium member connection infrastructure n

u (to TOP-IX node)

o

b

e

c

i

v

r e S

Fig 2 - TOP-IX Consortium service boundary

Consorzio TOP-IX | Service Description v 2020.03 Pag. 12 di 28

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: • 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, etc. to/from other consortium members (any exchange of services via VLAN between two ports of this type is not permitted); • Transit: opportunity to buy services such as IP transit, cloud access, security, etc. from other consortium members, or create private point-to-point or multi-point connections for backhauling requirements.

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

• Peering ports: ports reserved exclusively for peering services. No other services are permitted on these ports (1 Gbps / 10 Gbps / 100 Gbps speeds available); • Marketplace ports: ports where users may request one or more of the services available for this type of port, i.e. peering and/or marketplace (1 Gbps / 10 Gbps / 100 Gbps speeds available)4. • Transit ports: ports where users may request one or more of the available services, i.e. peering and/or marketplace and/or transit (100 Mbps / 1 Gbps / 10 Gbps speeds available)

Marketplace ports may only be requested from service vendors authorized by the TOP- IX Consortium, and is subject to an initial analysis of the technical requirements.

4 The following ports are not classified as being marketplace ports: · Any ports that collect wired network traffic made available by the TOP-IX Consortium, even if the traffic is carried by electronic communications equipment owned by the Consortium or third parties. · Any ports that collect radio network traffic through passive infrastructures (poles, masts, pylons, etc.) made available by the TOP-IX Consortium, even if the traffic is carried by electronic communications equipment owned by the Consortium or third parties.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 13 di 28

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 through 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”, "marketplace" or “transit” 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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 14 di 28

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

Consortium public peering infrastructure is also available on the Internet Exchange, to which TOP-IX is interconnected (VSIX, Lyon-IX and France-IX).

IXP members can request access to TOP-IX public peering from their own IXP. The IXP is responsible for acting 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 PEERING SERVICE ACCESS REQUIREMENTS

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 TOP- IX.

MAC and VLAN layer: • All frames sent to Consortium public peering infrastructure access ports 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. • Permitted protocols are exclusively: IPv4 (Ethertype 0x0800), ARP (Ethertype 0x0806) and IPv6 (Ethertype 0x86dd).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 15 di 28

• ARP and ICMPv6 transit is limited in the same way as "unknown-unicast" transit. • All Layer 2 protocols (STP, bridging protocols) as well as Router Advertisement / Router Solicitation (RA / RS) will also be filtered. • 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). • MTU is set at 1500 bytes. • “Non unicast” packets are not permitted with the exception of ARP and ICMPv6 Neighbour Advertisement/Solicitation (IPv4 multicast transit is not permitted).

Routing: • Peering sessions set up through the Consortium 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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 16 di 28

Information regarding Route Server system use is available at the following address:

https://www.top-ix.org/it/ix/routeserver/

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.

A Looking Glass is available to check Route Server system operations at the following address:

https://lg.top-ix.org

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.

3.5 ADDITIONAL INCLUDED SERVICES

The interconnection service described above also includes the following:

Consorzio TOP-IX | Service Description v 2020.03 Pag. 17 di 28

• An IPv4 address and an IPv6 address 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 costs5; • Costs for consortium member site connection to TOP-IX site; • Consortium member equipment configuration.

5 3-rack units are included in the supply contract at some TOP-IX infrastructure nodes (refer to section 2.3.2 for details of the sites).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 18 di 28

4. MARKETPLACE SERVICES

Marketplace services are dedicated to allowing the sale of services (IP Transit, cloud access, Ethernet and security, etc.) to 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.

Marketplace services may be requested solely between a Marketplace port and Transit port, or between two Transit ports. This type of service may not be carried out between two Marketplace ports.

4.1 HOW TO ACCESS SERVICES

Marketplace services are available solely in direct access mode to the TOP-IX infrastructure and can be provided on both Marketplace and Transit ports.

Service access requirements

Access to the services should be carried out in full compliance with the constraints and requirements outlined below.

Physical layer: • 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). • Agreements (IP Transit, cloud access, etc.) are negotiated directly between Consortium members/partners without any interference by TOP-IX.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 19 di 28

• Permitted protocols are exclusively: IPv4 (Ethertype 0x0800), ARP (Ethertype 0x0806) and IPv6 (Ethertype 0x86dd). • ARP and ICMPv6 transit is limited in the same way as "unknown-unicast" transit. • All Layer 2 protocols (STP, bridging protocols) as well as Router Advertisement / Router Solicitation (RA / RS) will also be filtered. • 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). • MTU is set at 1500 bytes. • “Non unicast” packets are not permitted with the exception of ARP and ICMPv6 Neighbor Advertisement/Solicitation (IPv4 multicast transit is not permitted).

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

4.2 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); • 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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 20 di 28

Consortium services do NOT include the following: • Housing costs 6; • Costs for consortium member site connection to TOP-IX site; • Consortium member equipment configuration.

5. TRANSIT SERVICES

Transit services are dedicated to allowing the sale of services (IP Transit, cloud access, etc.) to other consortium members via a dedicated VLAN and/or by implementing Layer 2 Transit using ports assigned to members or partners requesting the service.

5.1 HOW TO ACCESS THE SERVICES

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

5.2 SERVICE ACCESS REQUIREMENTS

Access to the services should be carried out in full compliance with the constraints and requirements outlined below.

Physical layer: • 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. •

6 3-rack units are included in the supply contract at some TOP-IX infrastructure nodes (refer to section 2.3.2 for details of the sites).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 21 di 28

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 public peering 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 VLANs to other Consortium member/partner ports which use the transit service (VLAN used for transit services may not be extended to other members/partners); • Access to statistical data handled by TOP-IX concerning 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 costs7; • Costs for consortium member site connection to TOP-IX site; • Consortium member equipment configuration.

7 3-rack units are included in the supply contract at some TOP-IX infrastructure nodes (refer to section 2.3.2 for details of the sites).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 22 di 28

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.

Requests for service activation and/or upgrade will not be carried out in the event that administrative matters are pending or outstanding.

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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 23 di 28

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).

Consorzio TOP-IX | Service Description v 2020.03 Pag. 24 di 28

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.)

Consorzio TOP-IX | Service Description v 2020.03 Pag. 25 di 28

7. QUALITY STATEMENTS

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 shall be carried out within 5 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 shall 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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 26 di 28

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.

Consorzio TOP-IX | Service Description v 2020.03 Pag. 27 di 28

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

Consorzio TOP-IX | Service Description v 2020.03 Pag. 28 di 28