Regulatory Implications Of SDN & NFV: An ONF Perspective

BoR (16) 10 Regulatory Implications of SDN & NFV: An ONF Perspective Sandra Scott-Hayward, Queen’s University Belfast Public BEREC Expert Workshop, January 21st, 2016, Brussels 2016 Open Networking Foundation

Centre for Secure Information Technologies Est.2009, Based in The ECIT Institute Initial funding over 30M (CSIT 2 - 38M) GLOBAL INNOVATION HUB FOR CYBER SECURITY 90 People Researchers Engineers Business Development Largest UK University lab for cyber security technology research GCHQ Academic Centre of Excellence Industry Informed Open Innovation Model Strong international links ETRI, CyLab, GTRI, SRI International Cyber Security Technology Summit 2016 Open Networking Foundation 2

Open Networking Foundation The Open Networking Foundation (ONF) is a user-driven organization dedicated to the promotion and adoption of Software-Defined Networking (SDN). 2016 Open Networking Foundation 3

Recent ONF Tech Community Developments Northbound APIs – Intent-based framework (into ODL) – Flow Objectives (into ONOS) – Real-time media automating QoS/QoE (into IMTC) Information Modeling – Consistent way to specify APIs – Essential for end-to-end services Layer 4-7 – Service Function Chaining Solution Architecture – OpenFlow support for SFC header extensions Carrier-grade SDN – Meeting of carrier-grade and service quality – Migration methods and techniques Instantiations – AppFest: medical researchers, NRENs, government agencies – SDN Solutions Showcase Skills certification – ONF-Certified SDN Associate (OCSA) – ONF-Certified SDN Engineer (OCSE) 2016 Open Networking Foundation 4

Open Source SDN (opensourcesdn.org) ONF coordinates: repository, governance, communities Open to the public Destination for much of our committee work 16 Projects – Aspen (Real-Time Media NBI) – Atrium (L3 SDN distribution) BGP, Flow objectives, OpenFlow 1.3, OCP, vendors ONOS in release 2015/A, ODL in release 2016/A – Boulder (Intent NBI) – Centennial (Wireless Backhaul PoC) – Durango (OVS support in OF-Config) – Englewood (Transport API) – Florence (Security assessment tools) – Frontier (SDN “flight data recorder”) – PIF (Protocol-Independent Forwarding intermediate representation) – Steamboat (L2 SDN distribution) – Telluride (End-to-End WAN as a Service) – Vail (Cloud access for enterprises) – 2016 Open Networking Foundation 5

OpenFlow Developments Optical & wireless extensions – Packet-optical integration PoC – Wireless transport PoC Interoperability – TTPs – Flow Objectives 1.3 in hardware – Atrium (7 switches) – 1.3 conformance spec (basic, single-table) Evolution – PIF Remember: OpenFlow is three things: An architecture (separation of forwarding/control) A model (match-action forwarding plane) A protocol (to load the Forwarding Information Base) 2016 Open Networking Foundation 6

Questions regarding regulatory implications of SDN and NFV 2016 Open Networking Foundation

Q1. Do SDN and NFV enable fixed network access which gives alternative network operators more control over the network of the incumbent compared to current layer 2 wholesale access products (also known as Ethernet bitstream or virtual unbundled local access (VULA))? – Is this possible in principle? – Will SDN and NFV also be standardized in a way (including multi-tenant support) which will make such forms of network access possible based on SDN/NFV? – Will SDN and NFV also be offered by vendors (and/or open source) which will make such forms of network access possible based on SDN/NFV? 2016 Open Networking Foundation 8

A1. 2016 Open Networking Foundation 9

A1. Service invocation/ control Management-control Service requestor role Applications plane Service provider role Applications-controller plane interface A-CPI R Controller plane R R SDN controller Service consumer Service requestor role Data-controller plane interface D-CPI Service provider role Data plane Local data consumption/ production 2016 Open Networking Foundation R Data exchange Resource user role R R Resource group R R 10

A1. Administrator Blue Application Blue .n SDN controller Green Application Red Service requestor Resource group A-CPI Resource group A-CPI Client Service provider A-CPI A-CPI Resource group Resource group Resource group Resource group Client context Blue.admin Client context Blue .n Client context Green Client context Red Server Orchestration Virtualization SDN controller Server context Blue.1 Server context Blue.2 Server context Aqua Server context Gold Server context Green Client D-CPI D-CPI D-CPI D-CPI Service requestor Service provider Resource group 2016 Open Networking Foundation Resource group Resource group Resource group Server Resource group 11

A1. Impact: - Security - Multi-Tenant Segmentation - Multi-Controller Interaction - Multi-OSS Environment These aspects discussed in ONF Technical Communities. 2016 Open Networking Foundation 12

A1. Do SDN and NFV enable fixed network access which gives alternative network operators more control over the network of the incumbent compared to current layer 2 wholesale access products (also known as Ethernet bitstream or virtual unbundled local access (VULA))? Yes, granularity – Is this possibleofinOpenFlow, principle?recursive control/services – Will SDN and NFVinformation also be standardized in aunder way development (including to Defined Interfaces, models, etc. are enable this. These elements notmake necessarily be standardized multi-tenant support) whichwill will such forms of networkbut follow the softwarebased model on (e.g. software APIs) supporting evolution to access possible SDN/NFV? incorporate new capabilities. – Will SDN and NFV also of beprovisions/options offered by vendors open Indeed. Currently a range exist(and/or in an evolving vendor landscape platformsaccess for VNFs, overlay source) which will(orchestration make such solutions, forms of network possible solutions) “vendor SDN” versus “open SDN” based on –SDN/NFV? CAVEAT: Outstanding security questions to be resolved 2016 Open Networking Foundation 13

Q2. Will SDN and NFV enable other new forms of network access or network sharing? – If this is the case, please present them. – Will SDN and NFV facilitate new services that enable end users to set up data (Ethernet) connections dynamically on-demand similar to phone calls? – Will SDN and NFV enable network operators to offer Virtual Network Functions (VNF) as a service to other operators? Do you expect that this will happen? Which VNFs? 2016 Open Networking Foundation 14

A2. Operator Open SDN Deployments Every trial of ONOS, ODL, Ryu; Dynamic Provisioning; their own DCs; SD-WAN; Transport SDN Virtualization & abstraction, layer separation, scaling Telecom Operators SFC in hypervisors, match-action paradigm NFV Trials . Cloud Providers Simplification, OpEx reduction SMEs “Open” published but not controlled by a single party 2016 Open Networking Foundation 15

A2. Will SDN and NFV enable other new forms of network access or network sharing? and currently – IfYes, thispossible is the case, please offered present them? Yes, SDN Carrier Ethernet e.g. MEF new services which enables end – Will and NFV facilitate Lifecycle Service data Orchestration users to set-up (Ethernet) connections dynamically ondemand similar to phone calls? – Will and NFV– enable Yes, SDN a whole range e.g. NTTnetwork operators to offer Virtual Network Functions (VNF) as a service to other operators? Do you expect that this will happen? Which VNFs? Ref: “The Third Network: Lifecycle Service Orchestration Vision”, MEF 2015 Ref: “Delivering a Carrier-Class NFV Use-Case”, NTT Group, OpenStack Summit, May 2015 2016 Open Networking Foundation 16

Q3. Will SDN and NFV have an (further) impact on the current value chain? If this is the case, please present how SDN and NFV will alter the current value chain. A3. Yes. APP 1 APPLICATIONS CONTROL NETWORK ELEMENTS Current – All-in-One, Dedicated 2016 Open Networking Foundation APP 2 APP n Better Services, CONTROLInnovation, MGMT Faster More Opportunities NE 1 NE 2 NE n General-Purpose Products – Specialists in Individual Components & Technologies 17

Q4. Will SDN and NFV have an impact on the relation between OTT and telecommunications service providers? If this is the case, please present how SDN and NFV will alter the role and possibilities of OTT and telecommunications service providers. 2016 Open Networking Foundation 18

A4. Yes, SDN and NFV enable TSPs to become more competitive with OTTs and more like the OTTs OTT: Swifter at creating new services; Software skills and commodity hardware expertise; Unimagined scale; Building private telco facilities; Deploy highly optimized, unique, dynamic services TSP: Diversity reflecting local needs, cultures, and societies; Exploit SDN/NFV to streamline, serve more specific customer needs; Unimagined scale in China 2016 Open Networking Foundation 19

Q5. Do SDN and NFV have other regulatory implications? A5. Early days - gradual transition with great benefits Recommendations: Don’t stifle innovation by regulating SDN and NFV just yet! Focus on standardized, open interfaces. 2016 Open Networking Foundation 20

Thank You! Questions? 2016 Open Networking Foundation

Regulatory Implications of SDN & NFV: An ONF Perspective Author: ONF Subject: BoR;Others;16;BoR (16) 10;2016.01.26 Keywords: Presentation " Regulatory Implications of SDN & NFV:An ONF Perspective" given on 21 Janury 2016 during the public BEREC expert workshop on "Regulatory implications of SDN and NFV". Created Date: 1/26/2016 3:21:20 PM