Technical & Security working group Interconnectivity Peering Blueprint DRAFT Work In Progress Marco Dellarole - Accenture Keith Smith Virgin Media London June 16, 2016
Objectives of this deck This deck provides a work in progress blueprint of the hybrid peering realized by combining the reuse of with a peering solution based on Carrier Neutral Facilities: Technical and Security peering blueprint Evolution of towards a CNF approach High level roadmap, dependencies and critical path Commercial considerations This document is a work in progress draft created by Accenture and Virgin Media in the spirit to collaborate with the Technical & Security Working group to provide an analysis of peering options for the network architecture and to help the working group to select the best option and architecture among the following. 2
Health and Social Care Network () vision The Health and Social Care Network () programme ambition is to provide a reliable, efficient and flexible way for health and care organisations to access and exchange electronic information by reducing costs and complexity, standardising networks, enabling service sharing and extending the parameters of collaborative working. This will be achieved by migrating out from current N3, whilst embracing the by: Establishing network arrangements that support the integration of health and social care, regional collaboration and flexible work patterns Creating a marketplace of assured network services that drives competition amongst suppliers, improves consumer choice, supports innovation and delivers value for money Reducing duplication by enabling health and social care organisations to reuse and share existing network infrastructure and services to access the information they need Reducing reliance on a centrally managed, national, private network Source: 3
peering architecture blueprint: hybrid peering realized by combining the reuse of with a peering solution based on Carrier Neutral Facilities ILLUSTRATIVE Ready architecture for the Digital era A B N Direct access to Internet and Cloud Major tier-1 and tier-2 Service and Carriers already at the CNF Easy path for Service and Carriers to join, creating a market opportunity beyond Internet Cloud High performance eliminating proliferation of NNI and traverse traffic performance issues Provides hosting for, Service and Carriers and end-customer for any additional devices Highly resilient, high performance, security N3 / Transition Networks Fast implementation with ready to go facilities Reuse of Management (NSI) 4
Dual Mode of Operation to support the transition from N3 / Transition Networks to peering architecture simplifies and de-risk transition between N3 / Transition Networks and by establishing a simple, reliable, high performance and secure Dual Mode of Operation () A ILLUSTRATIVE DRAFT WORK IN PROGRESS Dual Mode of Operation () will be realized at CNF with a LAN interface, plus required security and firewalling, at CNF to bridge N3 / Transition Networks and B N Internet Cloud provides a seamless communication between the Current Mode of Operation (endcustomer s locations still on N3 / Transition Networks) and the Future Mode of Operation (end-customer s migrated to ) Service and Carriers would just need to adopt, wherever needed, the configuration of the routing, VRF and VPN tunnels, without any additional physical infrastructure re-provisioning N3/Transition Network N3 / Transition Networks Highly resilient, high performance, security Fast implementation with ready to go facilities Management (NSI) 5
peering architecture blueprint: VRF segregation Health VRF ILLUSTRATIVE Health VRF A B N Internet Questions: Does require a segregation between HCSN and? Does require a segregation between HCSN and N3/Transition Network? Is the concept of Health VRF the same on and? Cloud Transition VRF? N3 / Transition Networks Management (NSI) 6
Evolution towards a CNF approach and convergence towards model Overview of architecture for Heath today high level representation Health PanVPN TNP COIN 1 VPN Health PanVPN Health PanVPN COIN 2 VPN Operator 1 Operator 2 (network of networks) 7
Evolution towards a CNF approach and convergence towards model Overview of architecture for Heath today high level representation GCN SPs Operators Customers 8
Evolution towards a CNF approach and convergence towards model Evolution currently being discuss at Cabnet Office for the evolution of peering GCN Peering Point Peering Point Operators Customers (network of networks) 9
High level roadmap, dependencies and critical path of the peering Peering blueprint M1 M2 M3 M4 M5 M6 M7 CNF Selection CNF 3rd party Contracted ILLUSTRATIVE NSI Selection (Design/Build/Test/Run) NSI Contracted Peeing HLD Peeing LLD BOM Ready Procurement HW HW Delivered Build and Test Build and Test Peering live NSI Run Setup NSI Run Assumptions and Assumptions and Considerations: Considerations: Peering blueprint available Feasibility to run a selection process for CNF facility and NSI in 3 months (tenders are not massive) No needs to provision circuits, only hardware procurement (lead time ~20 days) Interconnection on 3 options: 1. New links -> 2 diverse links from into the 2 CNFs to be provisioned (1 months for link negotiation and selection plus ~3 months circuit provisioning lead time) 2. Selection of a CNF 3 rd party in where today the 4 carriers for GCN are present already no link required 3. Wait for the GCN to be hosted at CNF timeline not defined yet requires a strong push to accelerate this 10
peering commercial consideration COST CONSIDERATIONS Approach 1 CAPEX and OPEX CAPEX for the build and test of the Core peering OPEX for the management of the Core peering and also network management (NSI + OPEX costs) Most optimized TCO Approach 2 Network as a Service Zero CAPEX for the build and test of the core peering Purely OPEX costs including infrastructure of the peering and network management (NSI + OPEX costs) Higher TCO in the range of 3~10% PRICINGS CONSIDERATIONS Price Option 1 funded to cover the costs Price Option 2 Carrier and SP interconnection fee Cost covered by an interconnection fee fairly defined for Carries and Service Price Option 3 End customer bundled prices Bundled offerings and prices for End customer prenegotiated by with peering cost included Question for the commercial working group: how will cover the costs for the technical and security peering, service management, central service and product catalogue, etc.? 11