1. connect communicate collaborate Federated POP: a successful real-world collaboration Milosz Przywecki, PSNC TNC2012, Reykjavik, Iceland, 22.05.2012 Maribel Cosin *, Paul van Daalen **, Ivana Golub ***, Peter Kaufmann ****, Gerben van Malenstein **, Jari Miettinen *****, Ralf Paffrath ****, Darko Paric *** *RedIRIS, **SURFnet, ***CARNet, ****DFN, *****CSC

2. connect communicate collaborate 2 Outline What is a federated PoP? Why federated PoP ? F-PoP features Implementation of F-PoP in Hamburg Future of Hamburg F-PoP

3. connect communicate collaborate 3 GN3 JRA1T3 group - background JRA1T3 (Federated Network Architectures) was a task within GN3 JRA1 (Future Networks) activity JRA1T3 team consists of CARNet, DFN, NORDUnet, PSNC, RedIRIS and SURFnet Main objectives across Y1-Y3 of GN3 Conduct a state-of-the-art paper study in order to describe different GÉANT, NREN and third party network architectures Definition of a test case – Conduct testing. – Analyse results and findings

4. connect communicate collaborate 4 What is a federated PoP ? The federated PoP is a physical site where several networks such as NREN and/or GÉANT are co- located to offer services in a joint manner. Inside the federated PoP network operations are carried out in accordance with collaborative agreements and equipment is shared where possible by the network entities present in the federated PoP

5. connect communicate collaborate 5 Why federated PoP ? To share the costs (reduction of capital and operation expenditures) To optimize usage of CBFs and NREN’s network To provision common services To increase resiliency of the network To open new opportunities for collaboration between NRENs

6. connect communicate collaborate 6 Impementation options Main types of F-PoP include Lightweight (optical only) Switching (optical, and switching) Routing (optical and routing) Full service (optical, switching and routing) Number and type of services in F-PoP depends on the available hardware

7. connect communicate collaborate 7 Hamburg F-PoP genesis In the research phase of the project, JRA1T3 considered four practical applications of conducted research as possible test case for testing federated network model. Those are: Using CBF for GÉANT PoP-to-PoP connection. The main idea is to use resources owned and operated by NRENs to replace dedicated GÉANT capacity needed to connect GÉANT PoPs, Using CBF as an element in regional links to reduce cost of connecting NREN to a GÉANT PoP, Remote IP backup with CBF where the goal is to increase resiliency by using CBF to connect to GÉANT PoP in other country Federated PoP. The main idea was to serve several NRENs that are present in one place in the same PoP and use NRENs resources (CBFs) to provide the connectivity. This case can be also seen as an opportunity to build a federated GÉANT PoP which can serve several NRENs.

8. connect communicate collaborate 8 F-PoP in Hamburg: background CBFs available to Hamburg 4 NRENs already present in Hamburg: DFN, NORDUnet, PIONIER and SURFnet NRENs present in Hamburg had their representatives in JRA1T3 group Collaboration already established CBFs in Europe (TERENA compendium 2011)

9. connect communicate collaborate 9 Situation before F-PoP establishment NORDUnet-SURFnet: two  (1x10G + alien wave) PIONIER-SURFnet two  (2x10G) NORDUnet-PIONIER one  (1x10G) Two nearby co-location centres are used, NORDUnet and SURFnet located in one and PIONIER in second centre

10. connect communicate collaborate 10 Hamburg F-PoP connectivity

11. connect communicate collaborate 11 Federated network architecture: a general view Three main layers: Service Operations Infrastructure Internal communication channel in each layer Communication channels between layers

12. connect communicate collaborate 12 F-PoP in Hamburg: a real life example Three NRENs involved: 10G interconnections at the Infrastructure layer Cooperation at the operation layer (e.g. monitoring) Multidomain services e.g. Bandwidth on Demand at Service Layer

13. connect communicate collaborate 13 Entities involved in F-PoP F-PoP Owner – external entity, independent from NRENs F-PoP host – SURFnet providing communication between invloved NRENs and F-PoP Owner F-PoP members – NORDUnet, PIONIER and SURFnet physically inteconnected in F-PoP Hamburg F-PoP pilot team - a group of people involved in GN3 JRA1T3 activity

14. connect communicate collaborate 14 Hamburg F-PoP case study: Technical resources Establishing connectivity (either via dark fiber or through a managed service) between NREN’s network and Hamburg co-location centre Establishing required connectivity between two sites in Hamburg where NRENs were present Overcoming formal and technical difficulties - making sure that all requirements like power, space can be fulfilled for the proposed hardware Installation of the switch and patching Selection of services to be deployed in the federated PoP (strictly related to the hardware installed in the federated PoP)

15. connect communicate collaborate 15 Hamburg F-PoP case study: Non-technical resources A strong will to interconnect with other NRENs Allocation of human resources that are required to maintain the connection. Allocation of resources and necessary manpower to run, manage and monitor the services. An agreement on sharing responsibilities is also needed. Agreement on operation of federated PoP

16. connect communicate collaborate 16 F-PoP: Future ? New services can be deployed if needed Operation of BoD-based service will be further investigated Operation and maintenance procedures will be further investigated and validated

17. connect communicate collaborate 17 Questions ? THANK YOU hamburg-fpop@lists.man.poznan.pl