Path from CE 2.0 to Dynamic Services Roadmap

Sponsored by: Path from CE 2.0 to Dynamic Services Roadmap Hernán Contreras G. Technical Solutions Architect Cisco

Agenda 1 MEF s Carrier Ethernet and other Dynamic Services 2 Lifecycle Service Orchestration (LSO) 3 From Technical Specifications to MEF Products 2

The Journey to Dynamic Services MEF s initial focus on Ethernet Layer 2 Services MEF Ethernet Services defined independently of the Layer 1 network used to transport them E.g., Ethernet Private Line can be transported over SONET/SDH, OTN, or IEEE 802.3 Layer 1 network Initial MEF work focused on automating and orchestrating MEF Ethernet services Info Models, YANG modules, LSO APIs, etc. To offer agile, assured and orchestrated Third Network Services, MEF standardizes the service model for Layer 1 and Layer 3 services 3

MEF Carrier Ethernet 2.0 Current Generation of MEF Services Carrier Ethernet delivers 3 powerful features: Standardized Multi- Class of Service Interconnected CENs Manageability Globally adopted connectivity service framework Foundation for agile, assured and orchestrated connectivity services 4

How the MEF Defines Connectivity Services Subscriber Services (EVC) consist of: User to Network Interfaces (UNIs) Demarcation between Service Provider and Subscriber Virtual Connections (VC) at or between UNIs UNI, VC, and VC End Point Service Attributes EVC-based services defined in MEF 6.2 UNI Service Provider VC UNI Operator Services (OVC) consist of: UNI(s) External Network to Network Interfaces (ENNIs) Demarcation between Operators VCs at or between the UNI(s) or ENNI(s) UNI, ENNI, VC, and VC End Point Service Attributes OVC-based services defined in MEF 26.1 (ENNI) and MEF 33. EVC: Ethernet Virtual Connection UNI OVC: Operator Virtual Connection VC Service Provider For Ethernet Services, VCs are EVCs or OVCs ENNI VC Operator UNI 5

CE 2.0 Retail Services Types (EVC) E-Line Point-to-Point Ethernet Private Lines (EPL) Ethernet Virtual Private Lines (EVPL) UNI Point-to-Point EVC UNI E-LAN Multipoint L2 VPNs Transparent LAN Service Multicast Networks EP-LAN, EVP-LAN Multi-point to Multi-point EVC UNI UNI UNI UNI E-Tree Rooted Multi-Point L2 VPNs Traffic Segregation EP-Tree, EVP-Tree UNI Rooted Multi-point EVC UNI UNI 6

Goal to Standardize and Unify Service Components to Simplify Modeling and APIs UNI Service end point and demarcation between subscriber and service provider Model it using common attributes that different values depending whether it is for an IP Service, Ethernet Service or L1 Service ENNI Service end point and demarcation between operators Model it using common attributes that different values depending whether it is for an IP Service, Ethernet Service or L1 Service VC Term to describe the interconnection of two demarcation points EVC/OVC for Ethernet services, IPVC for IP Services, L1VC not yet created VC End Point Term to describe the VC capabilities at a particular service end point, e.g., UNI or ENNI 7

MEF Carrier Ethernet 2.0 Retail (EVC Services) E-Line E-LAN E-Tree Globally Adopted, Certifiable, Connectivity Services Framework Wholesale (OVC Services) E-Access Access E-Line Access E-LAN E-Transit Transit E-Line Transit E-LAN EVC: Ethernet Virtual Connection OVC: Operator Virtual Connection 8

What is an MEF E-Access Service? Retail Service Provider buys E-Access services to reach off-net customer locations Wholesale Access Provider sells E-Access services to provide access to locations on its network ENNI (external NNI) is point of interconnection between Retail and Wholesale providers Operator Virtual Connection (OVC) between UNIs and ENNIs Point-to-Point (E-Line) or Multipoint (E-LAN) MEF 33 Retail Service Provider The Buyer (Has relationship with end-customer) ON-NET CUSTOMER LOCATIONS Wholesale Access Service Provider The Seller (Provides Access to remote customer location) OFF-NET CUSTOMER LOCATIONS End User Subscriber Headquarters UNI Carrier Ethernet Network ENNI Carrier Ethernet Network UNI End User Subscriber Branch Site CE CE End-to-End Carrier Ethernet Service E-Access Service (OVC) Multi-CoS capable Service OAM 9

MEF 51 E-Access Services E-Access Services: based on Operator Virtual Connection (OVC) between User Network Interface (UNIs) and External Network Network Interface (ENNIs) Access E-Line Service Access E-LAN Service S-VLAN ID 1011 ENNI_AB CEN A CE-VLAN IDs 3, 4, 5 UNI_1 CE-VLAN ID 34 S-VLAN ID 3398 ENNI_1 CEN A Access E-LAN UNI_1 OVC End Point Map @ UNI: 1, >1 or all CE-VLAN IDs S-VLAN ID 253 ENNI_AC S-VLAN ID 267 UNI_2 Full Map: All CE-VLAN IDs map to the Blue OVC End Point ENNI_N S-VLAN ID 115 UNI_N OVC End Point Map @ UNI: 1, >1 or all CE-VLAN IDs Key Characteristics of Access E-Line Point-to-Point, UNI-ENNI Flexible OVC End Point Map at UNI Multi-CoS capable Service OAM Enhanced Access EPL/Access EVPL Key Characteristics of Access E-LAN Multipoint-to-Multipoint, UNI-ENNI - Supports >1 UNI and/or >1 ENNI Flexible OVC End Point Map at UNI Multi-CoS capable Service OAM 10

New CE 2.0 E-Transit Services Key Characteristics of an E-Transit Service: Connects two or more CENs together using an Operator Virtual Connection (OVC) External Network Network Interfaces (ENNIs) at the CEN boundaries Point-to-Point or Multipoint-to-Multipoint OVCs provide the connectivity Can support all EVC-based services (i.e., Private and Virtual Private ) Multi-CoS capable Service OAM support MEF 51 UNI ENNI CEN ENNI CEN UNI CE End User Subscriber Headquarters Carrier Ethernet Network (CEN) E-Transit Service (OVC) E-Access Service CE End User Subscriber Branch Site End-to-End Carrier Ethernet Service 11

MEF 51 E-Transit Services E-Transit Services: based on Operator Virtual Connection (OVC) between External Network Network Interface (ENNIs) Transit E-Line Service Operator C s CEN is to the right of this ENNI Transit E-LAN Service ENNI_AC CEN A S-VLAN ID 923 CEN A ENNI_AB1 S-VLAN ID 51 S-VLAN IDs 101-150 Operator B s CEN is to the left of this ENNI ENNI_AB2 S-VLAN IDs 101-150 Operator B s CEN is to the right of this ENNI ENNI_AB S-VLAN ID 984 S-VLAN ID 253 Hairpin switching Transit E-LAN ENNI_AC S-VLAN ID 2033 Key Characteristics of Transit E-Line Point-to-Point, ENNI-ENNI Flexible OVC End Point Map Preservation of CE-VLAN Tag Multi-CoS capable Service OAM Key Characteristics of Transit E-LAN Multipoint-to-Multipoint, ENNIs Preservation of CE-VLAN Tag Multi-CoS capable Service OAM 12

Some Service Delivery Permutations Service Provider may deliver: Layer 1 Service, e.g., Optical Wavelength Service (OWS) Delivered over an OTN Layer 1 transport OWS over OTN MEF Layer 2 Ethernet Service, e.g., EPL Delivered over a SONET/SDH Layer 1 transport IP (Layer 3) Service, e.g., Internet Access Delivered over a Carrier Ethernet access network over IEEE 802.3 Layer 1 transport EPL SONET/SDH Internet Access EVPL IEEE 802.3 MEF standardizes the service model for each of the three network layers to facilitate automation and orchestration 13

MEF Layer 1 Services Project

Layer 1 Service Definitions and Attributes Project Industry Challenge: No standard definition of Layer 1 Services Layer 1 services broadly available but lack standardized service attributes Lack of standardized ENNI results in ad hoc operator interconnects Project: Define Service Attributes for Managed Layer 1 Services End-to-end (subscriber) and inter-provider (operator) service attributes Analogous to EVC/UNI and OVC/UNI/ENNI attributes for Carrier Ethernet Why do this? Enable on-demand, dynamic Third Network Layer 1 services Requires standardized APIs and orchestration across network domains Enable on-demand, dynamic Layer 1 service creation and assurance 15

Subscriber Layer 1 Connectivity Services Layer 1 Connectivity Services (UNI-to-UNI) characteristics: Topology - point-to-point only Rate - full port rate (wire speed) only High Bandwidth: 155Mb/s STM-1 up to 100Gb/s Ethernet Multi-protocol - Ethernet, Fibre Channel, FICON, InfiniBand, SONET/SDH, OTN High performance - lowest latency, jitter, loss Same MEF UNI and ENNI terms Redefined to encompass Layer 1 attributes 16

UNI and ENNI Protocols UNI Data Client Protocol Rate (Gb/s) GigE (1000BASE-X) 1.250 10GigE WAN (10GBASE-W) 9.95328 10GigE LAN (10GBASE-R) 10.3125 40GigE (40GBASE-R) 41.250 100GigE (100GBASE-R) 103.125 FC-100 1.0625 FC-200 2.125 FC-400 4.250 FC-800 8.500 FC-1200 10.51875 FC-1600 14.025 FC-3200 28.05 ENNI Protocol Rate (Gb/s) ODU1 (OTU1 interface) 2.498 775 126 ODU2 (OTU2 interface) 10.037 273 924 ODU2e (OTU2e interface) 10.399 525 316 ODU3 (OTU3 interface) 40.319 218 983 ODU4 (OTU4 interface) 104.794 445 815 UNI TDM Client Protocol Rate (Gb/s) OC-3/STM-1 0.15552 OC-12/STM-4 0.62208 OC-48/STM-16 (CBR2G5) 2.48832 OC-192/STM-64 (CBR10G) 9.95328 17

MEF IP Project

IP Service Attributes Project Industry Challenge: No standard definition of IP Services IETF defines a lot of control plane technology Little consideration of how to operationalize (particularly inter-provider) Project: Define Service Attributes for Managed IP Services IP VPNs and Internet Access End-to-end (subscriber) and inter-provider (operator) service attributes Analogous to EVC/UNI and OVC/UNI/ENNI attributes for CE Why do this? Enable on-demand, dynamic Third Network IP services Requires standardized APIs and orchestration across network domains Enable on-demand, dynamic IP service creation and service assurance 19

Subscriber IP Service - VPN Service attributes for UNI, IPVC, IPVC End Point UNI Service Provider IPVC UNI IPVC EP Subscriber Branch Office Subscriber Head Office IPVC EP IPVC EP UNI Subscriber Branch Office 20

Subscriber and Operator IP Services Subscriber IP Services Attributes defined for VPN and Cloud Access services Includes Internet Access and Private Cloud Access Re-using UNI construct from Ethernet services UNI is the demarcation of responsibility between the Service Provider and Subscriber Operator IP Services Re-using ENNI construct from Ethernet services ENNI is the demarcation of responsibility between the Operators 21

Subscriber IP Service Cloud Access Internet Access or Private Cloud Access E.g., AWS, Google Cloud Could consist of only a single UNI Cloud Service Provider or DC UNI IPVC Service Provider Subscriber 22

Operator IP Service Service Provider uses another operator to reach a off-net subscriber UNI to deliver IP Service Service Provider UNI UNI Service Provider Operator 1 Network ENNI IP Operator Service (IPVC) IP Operator Service (IPVC) IP Subscriber Service (IPVC) 23

Problems Being Addressed by IP Services Project Multi-provider L3 VPNs are a particular pain point No standards for peering mechanism, QoS, SLS, etc. Bilateral agreements required with each peering Service Provider No automation Different manual process required for each peering Service Provider Each Service Provider has a unique implementation LSO abstractions, APIs (technical & business), automation applied 24

MEF IP Services Categorization and Use Cases

Lifecycle Service Orchestration (LSO)

Dynamic Orchestrated Services Orchestrated Services Optical Carrier Ethernet IP L4-L7 Point Services SD-WAN Security Applications 27

What is MEF Lifecycle Service Orchestration (LSO)? LSO provides for the orchestrated management and control of Third Network Connectivity Services LSO Reference Architecture characterizes the management and control domains and entities that enable the cooperative LSO capabilities LSO overcomes existing complexity by defining product, service, and resource abstractions that hide the complexity of underlying technologies and network layers from the applications and users of the services Service Lifecycle Management includes Product Lifecycle management and Service Operations Lifecycle management 28

Service Lifecycle Process Model (MEF 50) Product Lifecycle Market Analysis & Product Strategy Service Operations Lifecycle Marketing Fulfillment Response Product Design Sales Proposal & Feasibility Serviceability Service & Resource Design Customer Order Product Launch Service Configuration & Activation Fulfillment MEF 50 leverages the TM Forum s Business Process Framework, also referred to as the enhanced Telecom Operations Map (etom). Fault Management Quality Management Service Termination Revenue Management Operation 29

LSO and Lifecycle Frameworks LSO Capabilities Fulfillment Performance Control Assurance Usage Analytics Security Policy Product Catalogue* Service Activation* Service Ordering (MEF 57) Performance Reporting (MEF 52) Service Qualification Questionnaire (MEF 53) Service Lifecycle Process Model (MEF 50) * Future MEF Framework Specification 30

MEF 53 Overview MEF 53 defines the use cases, process, and content for a standardized MEF Carrier Ethernet Services Qualification Questionnaire. The purpose of this questionnaire is to encourage service providers buying and/or selling Ethernet services to use MEF-standardized questions to reduce the time and effort required to obtain interconnect information from access or service provider partners. 31

LSO Reference Architecture and Capabilities (MEF 55) The LSO architecture and framework enables automated management and control of end-to-end Connectivity Services that span multiple provider domains FRAMEWORK FRAMEWORK LSO Cantata LSO Allegro Business Applications LSO Legato LSO Sonata Business Applications LSO Legato Fulfillment Performance Control Assurance Usage Analytics Security Policy Self-service Web Portal SOF LSO Presto LSO Interlude SOF LSO Presto User Service Endpoint NFV MANO SDN Controller Operator Service Endpoint Packet SDN Controller Traditional EMS User Service Endpoint LSO Adagio LSO Adagio Packet PNFs Packet PNFs Head Office UNI SDN Switch Network Operator 1 ENNI Network Operator 2 UNI Cloud Service Provider End-to-End Network-as-a-Service EMS: Element Management System PNF: Physical Network Function SOF: Service Orchestration Function 32

MEF 55 LSO Reference Architecture MEF 55 define a reference architecture that describes the functional management and control entities needed to support LSO, and the Management Interface Reference Points between them. CANTATA (CUS:BUS) Business Applications SONATA (BUS:BUS) Business Applications Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) ALLEGRO (CUS:SOF) Service Orchestration Functionality INTERLUDE (SOF:SOF) Service Orchestration Functionality PRESTO (SOF:ICM) PRESTO (SOF:ICM) Infrastructure Control and Management Infrastructure Control and Management ADAGIO (ICM:ECM) ADAGIO (ICM:ECM) Element Control and Management Element Control and Management information and data models that enable the definition of open and interoperable APIs supporting LSO functionality Key CUS: Customer Application Coordinator BUS: Business Applications SOF: Service Orchestration Functionality ICM: Infrastructure Control and Management ECM: Element Control and Management Network Infrastructure

Product catalog; Product feasibility; Product ordering; Acceptance testing info; Billing and usage; Trouble reports / status; Product level quality; MEF LSO Related Modeling Projects CANTATA (CUS:BUS) Service feasibility; Service activation; Usage events & metrics; Service performance & quality; Service policy Business Applications SONATA (BUS:BUS) Serviceability & qualification; Product catalog; Product ordering; Acceptance testing info Billing exchange; Trouble reports / status; Product level quality; Business Applications Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) ALLEGRO (CUS:SOF) Service Orchestration Functionality INTERLUDE (SOF:SOF) Service Orchestration Functionality Dynamic service control; Service state info; Service performance & quality; Service related alerts; Key CUS: Customer Application Coordinator BUS: Business Applications SOF: Service Orchestration Functionality ICM: Infrastructure Control and Management ECM: Element Control and Management Create and manage connectivity and logical network functions; Topology and routing; Performance and Fault; Resource inventory; Connectivity policy PRESTO (SOF:ICM) Infrastructure Control and Management ADAGIO (ICM:ECM) Element Control and Management Network Infrastructure PRESTO (SOF:ICM) Dynamic service control; Service Infrastructure parameter config; Control Service and state Management info; Service performance info; ADAGIO (ICM:ECM) Service problem alerts Element Control and Management Manage fabric or network functions on specific elements; Element level configuration ; Element resource state; Element fault and performance; Element level policy;

From Technical Specifications to MEF Products

LSO Engineering Methodology TOC: Product Catalog, Ordering, Performance Reporting, Serviceability API Implementations Certifications LSO Reference Architecture & Framework MEF LSO Reference Architecture & UNITE Common Information Models MEF 7.3, Common Model, Resource Model, Cloud Services NRP API Test Suite MEF Service Definitions (including virtualization) MEF 6.2, 33, 51, 10.3, 26.2, etc. LSO Hackathon, ODL project, OPNFV Reference Implementations Business Process Flows MEF 50.x JSON, SCA, YANG, etc. API Specifications & Data Models Interface Profiles Profiles for LSO Presto, LSO Legato, etc. 36

LSO and Open API Initiatives To start the respective agile sprints to develop two sets of APIs to be used for orchestrating MEF-defined services (like E-Line, E-Access etc) at LSO Sonata and LSO Presto respectively that will culminate in publication of these open APIs during the course of 2017, and to ensure that they enable certification of orchestrated MEF-defined services. 37

LSO Presto R1 APIs

LSO Presto R1 Intra-provider Open APIs Presto FRAMEWORK Self-service Web Portal Customer Facing Open APIs Business Applications Service Orchestration Fulfillment Performance Control Assurance Usage Analytics Security Policy Technology Domains Open APIs User Service Endpoint User Service Endpoint Network Operator 1 UNI UNI Head Office Cloud Service Provider End-to-End Network-as-a-Service

LSO Presto R1 APIs Project LSO Presto R1 is the first set of APIs being developed in support of MEF's agile specifications development of Interface Profile Specifications at LSO Presto. R1 includes one Epics and three User Stories: Provisioning a connectivity service for an EPL between two customer locations Provisioning a connectivity service for an EPL between two customer locations 40

LSO Sonata R1 APIs

LSO Sonata R1 Inter-provider Open APIs Sonata FRAMEWORK FRAMEWORK Self-service Web Portal Customer Facing Open APIs Business Applications Service Orchestration Inter-Provider Open APIs Business Applications Service Orchestration Fulfillment Performance Control Assurance Usage Analytics Security Policy User Service Endpoint Technology Domains Open APIs Technology Domains Open APIs User Service Endpoint UNI Network Operator 1 ENNI Network Operator 2 UNI Cloud Service Provider Head Office End-to-End Network-as-a-Service

LSO Sonata R1 API Project LSO Sonata R1 is the first set of APIs being developed in support of MEF's agile specifications development of Interface Profile Specifications at LSO Sonata based on TM Forum s Open API Framework R1 includes two Epics and three User Stories: Provide inter-carrier service availability capabilities Provide inter-carrier service ordering capabilities Service Provider place an order for a new Access EPL or an Access EVPL service at customer site(s) within my Partner s domain. 43

MEF PR LSO Sonata R1 44

MEF LSO Ecosystem Capabilities E2E Fulfillment Orchestration Service delivery orchestration Testing orchestration and turn-up Coordination of all provisioning tasks Order and Request management and tracking Design of E2E services and assignment of resources 45

MEF TM Forum LSO APIs Collaboration Framework Open API Framework Develop a complete suite of inter-provider LSO APIs that use the MEF LSO Framework enabling agile, assured, and orchestrated Third Network services over more automated, virtualized, and interconnected networks globally. Leveraging TM Forum s Open API framework, digital business architecture, industry standard Information Framework and tools for end-to-end service management and orchestration. The inter-provider LSO API standardization work can be utilized in the future for orchestrated optical and IP services being defined by MEF and to advance digital ecosystem 46

MEF s Intra-operator APIs and Open Initiatives Service Level Orchestration Open APIs Service Orchestration Fulfillment Performance Policy Control Assurance Usage Security Analytics Network Level Orchestration Open APIs Technology Domains Open APIs SD-WAN Data Center Packet WAN Optical Transport NFV Cloud Exchange 5G Wireless Orchestrated Services Services E-Line E-LAN E-Tree E-Access E-Transit Wavelength Internet Access L3 VPNs IP Transit SECaaS App Services 47

MEF s Inter-operator APIs and Open Initiatives Service Orchestration Inter-Operator Open APIs Serviceability Ordering Address Validation Others Service Orchestration Inter-Operator Open APIs Service Orchestration Technology Domain Technology Domain Technology Domain Orchestrated Services Services E-Line E-LAN E-Tree E-Access E-Transit Wavelength Internet Access L3 VPNs IP Transit SECaaS App Services AT&T Announcement MEF & TM Forum Announcement 48

Nature of OpenLSO: A MEF-facilitated open service orchestration ecosystem Collaboration environment for MEF member companies to maximize the alignment of market implementations of LSO Both Open Source and proprietary components using MEF-defined LSO specifications to foster best-of-breed solutions Objectives Simplify and accelerate adoption of LSO specs for orchestration of Third Network services Iterative work towards APIs that are standardized and open Maximize alignment of LSO specifications and Open Source code for consistency with LSO use cases and capabilities Low-risk experience, rapid feedback, agile development 49

OpenLSO Capabilities Analytics and Assurance Projects Reference implementation of LSO Analytics using the PNDA.io analytics platform To demonstrate analytics as part of Third Network services user stories Feed requirements into specifications work in MEF Supports other LSO capabilities such as LSO Assurance and LSO Performance Aims to demonstrate examples of these interrelationships via the LSO sub-architecture Customer Application Coordinator Partner SOF 50

Nature of OpenCS OpenCS is a MEF-facilitated ecosystem that provides reference implementations of MEF-defined connectivity services (e.g. E-Line) Uses combinations of open source and proprietary components and CE 2.0-certified network devices Objective Simplify and accelerate adoption of MEF specs to develop Third Network services based on any infrastructure Any combination of SDN controllers, NFV infrastructure, VNFs, white boxes and traditional PNFs 51

OpenCS SD-WAN Use Case The OpenCS SD-WAN project is creating for service providers reference SD-WAN implementations that can be service orchestrated by LSO (MEF-defined Lifecycle Load Bal. Service Orchestration) and integrated into multi-operator agile, assured and orchestrated end to end L2 and L3 services. Self-service Web Portal CPE Internet Presto APIs SD-WAN Controller NFV MANO Presto APIs Presto APIs SDN Controller SDN Switch SD-WAN RO - Resource Orchestrator GW - Gateway CPE - Customer Premise Equipment UNI CE 2.0 / MPLS GW SD-WAN Central Office, Data Center or Head End SDN Switch UNI 52

MEF Development Model

MEF Development Model MEF Agile Development Lifecycle Liaisons to SDOs MEF Reference Implementations Accelerator This is a sample text Open Source Projects MEF Dev. Community Platform Collaboration 54

What is MEFnet? A physical and virtual hosting environment for the hardware and software components of OpenLSO and OpenCS implementations Includes OpenLSO and OpenCS instances comprised of solutions from Open Source Projects and Closed Source industry products Supports distributed and interconnected member and partner labs, accessible for LSO Hackathons and ongoing MEF development and testing work Ample resources, 100+ VMs 55

MEFnet Projects - Inter-carrier Orchestrated L3VPN 56

LSO Hackathons: Accelerate the development of comprehensive OpenLSO and OpenCS instances as part of the MEF's Open Initiatives Provide feedback to ongoing MEF projects in support of the MEF's Agile Standards Development approach to MEF specification development Facilitate discussion, collaboration, and the development of ideas, sample code, and solutions Encourage interdepartmental collaboration and communications within MEF member companies Held several times a year Offer both learning & commercial value

MEF Software Development Community Internships for telecom university grad programs and their students Council of university professors to advise on program Special designation for interns in MEF branding for access to jobs Additional information to be available at official launch 58

MEF UNITE Program To coordinate internal & external engagement with Standards Development Organizations, Industry Consortia, & Open Source Projects To avoid duplication of effort To bring technology silos into a coherent whole 59

60 Industry White Paper of Third Network Services Third Network Services http://mef.net/tgn 60

In Summary MEF is not just Carrier Ethernet anymore. Defining and documenting all services to be automated Lifecycle Service Orchestration The key to Agile, Assured and Orchestrated Services From Technical Specifications to code 61

MEF Advancing the Industry -Video- 62

63

Sponsored by: Path from CE 2.0 to Dynamic Services Roadmap Hernán Contreras G. Technical Solutions Architect Cisco