Developing Implementing MEF 3 0 Carrier Ethernet Optical

Developing & Implementing MEF 3. 0 Carrier Ethernet, Optical Transport & IP Services David Ball, LSO Committee Co-Chair (former Services Committee Co-Chair), MEF; Principal Engineer, Cisco David Martin, Senior Systems Engineer, IP/Optical Networking Business Group, Nokia MEF Q 3/19 Members Meeting, July 2019

Topics & Speakers Developing & Implementing MEF 3. 0 Carrier Ethernet, Optical Transport & IP Services MEF 3. 0 Services Overview David Ball, LSO Committee Co-Chair (former Services Committee Co-Chair), MEF; Principal Engineer, Cisco MEF 3. 0 Carrier Ethernet & IP Services David Ball, LSO Committee Co-Chair (former Services Committee Co-Chair), MEF; Principal Engineer, Cisco MEF 3. 0 Optical Transport Services David Martin, Senior Systems Engineer, IP/Optical Networking Business Group, Nokia

MEF 3. 0 Services Overview

MEF 3. 0 Global Services Framework Accelerate assured services across automated networks Automated Assured • • • Applications Security SD-WAN IP Carrier Ethernet Optical Transport • Orchestration across multiple service providers • Orchestration over multiple network technology domains • Specifications and SDKs Agile • Cloud-based test & certification platform • On-demand, user-initiated • For both services & LSO APIs • Plus certified professionals Expanded • • • MEF global membership MEF 3. 0 Proof of Concepts MEF LSO Developer Community Open source projects & SDOs Enterprise Advisory Council Events, workshops, webinars

What is a MEF 3. 0 Service? Technical Definition of functionality Independent of service implementation Described by externally visible behaviour Provided by one organization to another

Describing MEF 3. 0 Services Committee Service Definitions Service Attributes Special Topics Certificatio n (e. g. SOAM, SAT, Co. S, etc. ) Info/Data Models LSO APIs

Subscriber and Operator Services London Philadelphia AT&T Subscriber Service Operator Service Telecom Italia Rome Subscriber Services (Provided to end users) • Define common terminology • Allow users to easily compare offerings • Enable certification of services • Assist automation of service lifecycle Rome Operator Services (between Providers) • Define common terminology • Enable common operations • Enable automation of service lifecycle

MEF 3. 0 Services Roadmap Completed Application Services Intent-Based Orchestration / Use Cases SECaa. S Application Security for SD-WAN Attributes & Definition (88) SD-WAN Service Attributes & Services Definition (70) Service Attributes & Services Phase 2 (70. 1) Service Attributes (61. 1) Subscriber Service Definitions (69), SOAM for IP (66), SAT for IP (67) Subscriber Attributes (10. 4), Operator Service Definitions (51. 1), L 2 CP (45. 1) Managed Access ELine (62) SAT for P 2 P Services (48. 1), Simplified Transit E-Line (65), Transport for 5 G (22. 3. 1) Subscriber Attributes & Service Definition (63) Operator Attributes & Service Definition (64) IP Carrier Ethernet Optical Transport In Development Planned SD-WAN Data Models and LSO APIs Subscriber Service Definition (6. 3), CE for Cloud (47. 1), Cloud Services Architecture (68) See LSO API Roadmaps for LSO Presto-related work associated with specific MEF 3. 0 services

MEF 3. 0 Carrier Ethernet

MEF 3. 0 CE – Latest Standards

Key MEF 3. 0 CE Standards Subscriber Services Operator Services Service Attributes Service Definitions • • MEF 10. 4 - Subscriber Ethernet Service Attributes • • • MEF 26. 2 - ENNIs and Operator Ethernet Service Attributes • • • Special Topics • • • MEF 6. 2 - Subscriber Ethernet Services MEF 22. 3 Transport Services for Mobile Networks MEF 47 Cloud Ethernet Services MEF 51. 1 - Operator Ethernet Services MEF 62 - Managed Access E-Line WIP – Simplified Transit E-Line MEF 30. 1 – Service OAM Fault Management MEF 35. 1 – Service OAM Performance Monitoring MEF 45. 1 – Layer 2 Control Protocols MEF 23. 2, 23. 2. 1– Class of Service and Bandwidth Profiles MEF 48 – Service Activation Testing MEF 6. 3, MEF 22. 3. 1, MEF 47. 1, MEF 48. 1: updates in progress

MEF 10. 4 – Subscriber Ethernet Service Attributes • Service Provider Key Concepts: – Service Provider, Subscriber – UNI, EVC End Point • Key Service Attributes – End Point VLAN Map – Class of Service Map UNI EVC End Point – Service Level Specification – Bandwidth Profiles – PCP/DEI Preservation Subscriber

MEF 6. 2 – Subscriber Ethernet Service Definitions SP • E-Line Three Service Types: – E-Line – point-to-point – E-LAN – multipoint – E-Tree – rooted multipoint • Specific Services – “Port”based or “VLAN”-based: – E-Line type: EPL and EVPL – E-LAN type: EP-LAN and EVP-LAN – E-Tree type: EP-Tree and EVP-Tree SP E-LAN SP ETree

MEF 26. 2 – Operator Ethernet Service Attributes Operator • • Key New Concepts: – Operator, Super-Operator – ENNI, OVC End Point – VUNI, Feeder OVC Key Service Attributes: – As for Subscribers, plus: – OVC EP VLAN Map – OVC EP Egress Co. S Map – Available MEG Level – ENNI S-VLAN ID Control • ENNI Common and Multilateral Attributes UNI OVC Peer Operators OVC End Point ENNI

MEF 51. 1 – Operator Ethernet Service Definitions • Three General Services – O-Line (P 2 P) SP E-LAN Access E-LAN – O-LAN (MP) – O-Tree (Rooted MP) • Four Specific Services Operator B Operator A – Access E-Line (P 2 P, Transit E-Line ENNI+UNI) Operator C – Access E-LAN (MP, ENNI+UNI) – Transit E-Line (P 2 P, ENNI only) – Transit E-LAN (MP, ENNI only) Access E-LAN Operator E Transit E-LAN Operator D Access E-Line Operator F

MEF 3. 0 IP

Motivation for Standardizing IP Services • SP must partner with other Operators to reach remote Subscribers • Each uses different terminology and describes services in a different way • Bilateral agreement needed with each partner • Orchestration and automation extremely challenging Partner 1 Partner 3 Service Provider Partner 2 Goal: Automate inter-provider service lifecycle Step 1: Define IP Services using Service Attributes Partner 4

Initial Standard: MEF 61 – Subscriber IP Service Attributes • Key Concepts: Service Provider – UNI, IPVC End Point – IP-VPN and Internet Access • Key Service Attributes – UNI Routing Protocols – Class of Service Maps UNI IPVC – UNI Connection Addressing IPVC End Point – Service Level Specification – Bandwidth Profiles Subscriber

Latest Standard: MEF 61. 1 – IP Service Attributes • Adds Operator Services – Agreed between SP and an Operator – New concepts: ENNIs, Operators • RFC 4364 Option A – No MPLS Labels at the IPVC End Point Operator IPVCs UNI ENNI – New attributes for mapping services across an ENNI • More to do… – E. g. Option B and C Operator A Operator B ENNI

Forthcoming Standard: MEF 69 – Internet Access Service Subscriber • • Based on MEF 61. 1 Service Attributes Two types of Internet Access: – Basic • Best-effort, plug and play • Residential or SME use – Advanced • SLS, static addressing, etc • Commercial use Internet IPVC (Internet) Service Provider Boundary between the ISP and “the Internet” is invisible to the Subscriber: • Internet Access can include access to things within the SP’s own network and outside it • Can include caching and similar

Active IP Projects Subscriber IP Service Definitions • Internet Access (MEF 69) • IP VPN Service Definitions Service OAM for IP Services (MEF 66) SAT for IP Services (MEF 67) Service Attributes Special Topics Certificatio n (e. g. SOAM, SAT, Co. S, etc. ) IP Service Attributes (MEF 61. 1) Info/Data Models LSO APIs

MEF 3. 0 Optical Transport

MEF 3. 0 Optical Transport Services - Motivation • Standard set of L 1 service definitions* (similar to L 2 CE and emerging L 3 IP) – Provides subscribers with consistent offerings for comparison (e. g. , performance) • Standard definition of a L 1 ENNI and associated Operator services – Enables simplified, faster interconnect between Operators / Service Providers • Certification of another set of Service Provider offerings – Marketing benefit to advertise services as MEF compliant • Will allow Service Providers to leverage LSO service management benefits for L 1 services – Improved service delivery times through automated service ordering and configuration processes – Faster time-to-revenue and lower OPEX *Often referred to as Wavelength Services commercially

Subscriber Layer 1 Service Use Cases • When the highest rates (10 G-100 G) and highest performance are required – Lowest latency, negligible variation, zero loss • Data centre interconnect use cases 1) Enterprise to a co-location site (outsourcing) 2) Co-location site to a web-scale Cloud Provider (Hybrid Cloud) LAN / SAN extension

Enterprise Outsourcing to Co-location Use Case Enterprise Leases Subscriber Layer 1 Service from CSP (HQ to Colo) Co-location Site HQ UNI Subscriber L 1 Service Back-up EVP-LAN/ IP VPN Enterprise outsources to co-location site for BC/DR or Cloud services where it can • Use its own equipment and lease space, power, remote hands, or • Lease computing/storage from an IT provider (CNP case), or the CSP for Iaa. S, Paa. S, Saa. S Client Protocols FC-1200 (10 GFC) Branch FC-1600 FC-3200 Branch CNP Carrier Neutral Provider CSP Communications Service Provider Branch BC DR Business Continuity Disaster Recovery 10 Gig. E LAN (10 GBASE-R) 40 Gig. E (40 GBASE-R) 100 Gig. E (100 GBASE-R) SAN Extension LAN Extension

Enterprise Hybrid Cloud Use Case Web-scale Cloud Provider (ICP) leases Subscriber Layer 1 Service from CSP to provide presence in Colo ICP Internet Content Provider UNIs UNI Subscriber L 1 Service Direct Connect (AWS) Google Cloud Interconnect (GCI) Colo with Cloud Exchange UNI EVP-LAN/ IP VPN Express Route (MS) Subscriber L 1 Services UNIs HQ ICPs Direct Link Back-up (Soft. Layer) Client Protocols Branch 10 Gig. E LAN (10 GBASER) 40 Gig. E (40 GBASE-R) 100 Gig. E (100 GBASE-R)

MEF 63 – Subscriber Layer 1 Service (UNI-UNI) • Point-to-point, bi-directional, full port rate (wire speed) connectivity with a single service instance per UNI – No service multiplexing • The same client protocol at both UNIs – Ethernet, Fibre Channel, SONET, SDH • Physical ports at both UNIs have same rate and coding function, such as – 1000 BASE-X (8 B/10 B), FC-1600 (64 B/66 B), SONET/SDH (section frame) – An encoded data block is the entity (L 1 Characteristic Information) transported by the L 1 Virtual Connection (L 1 VC) • Physical port at each UNI may have a different optical interface function – Short reach, intermediate reach, long reach, etc

MEF 63 – Subscriber Layer 1 Service Attributes • UNI Service Attributes (2) L 1 VC Layer 1 Virtual Connection – UNI ID, Physical Layer • Subscriber L 1 VC Service Attributes (3) – Subscriber L 1 VC ID, Subscriber L 1 VC End Point List, Subscriber L 1 VC Service Level Specification – The Service Level Specification (SLS) includes five Performance Metrics • One-way Delay, Errored Second (ES), Severely Errored Second (SES), Unavailable Second (UAS), Availability • Subscriber L 1 VC End Point Service Attributes (2) – Subscriber L 1 VC End Point ID, Subscriber L 1 VC End Point UNI • With only 7 attributes, certification testing for both services and equipment should be faster and less expensive than for CE

Subscriber Layer 1 Service Instance Subscriber L 1 VC End Point UNI 1 SAs UNI 1 ID Physical Layer 1: (p, c, o) Client protocol Coding function Optical Interface function SN Service Provider Network UNI 2 SAs UNI 2 Subscriber LIVC SA Service Attribute SN Subscriber Network SN UNI 2 ID Physical Layer 2: (p, c, o) Client protocol = UNI 1 (p) Coding function = UNI 1 (c) Optical Interface may differ Subscriber L 1 VC SAs Subscriber L 1 VC ID Subscriber L 1 VC End Point 2 SAs L 1 VC End Point ID 1 Subscriber L 1 VC End Point List L 1 VC End Point ID 2 L 1 VC End Point UNI 1 Subscriber L 1 VC SLS: (ts, T, PM) Metrics: Delay, ES, SES, UAS, Availability L 1 VC End Point UNI 2 Subscriber L 1 VC End Point 1 SAs

Operator Layer 1 Services (UNI-ENNI, ENNI-ENNI) • Same client protocols at the UNI as for Subscriber Layer 1 Service (by definition) – Ethernet, Fibre Channel, SONET, SDH • The client protocol at the ENNI is OTN and the physical port is an OTUk (k=1, 2, 2 e, 3, 4) – ENNI interface rates of 2. 5 G, 10 G, 40 G, 100 G • Access L 1 Virtual Connections from multiple UNIs may be aggregated to a single OTUk port at the ENNI • Transit L 1 Virtual Connections from multiple ENNIs may be aggregated to a single OTUk port at another ENNI • An ENNI may support multiple Service Provider L 1 Virtual Connections (Shared ENNI)

Status of Layer 1 Services and Related Projects • Subscriber Layer 1 Service Attributes – Published in August 2018 as MEF 63 – Note it also inherently defines a Subscriber L 1 Service as there are no options • Operator Layer 1 Service Attributes and Services – Resolving comments from Cf. C 2 on what is known as MEF 64 – Targeting Letter Ballot by 4 Q 2019 • In LSO Committee, the Network Resource Management Information Model for L 1 – Added support for Subscriber L 1 Service UML constructs in MEF 72 – Work is underway to add support for Operator L 1 Service constructs in MEF 89 • In MEF 3. 0 Proof of Concepts, the Orchestrated Optical Transport Services project is ongoing – Intent is to gain early experience and provide feedback into related projects

Future Work • Service OAM for Subscriber and Operator Layer 1 Services – Equivalents of MEF 30 (Fault Management) and MEF 35 (Performance Monitoring) • Service Activation Testing for Layer 1 Services – Equivalent of MEF 48 • Amendment to Subscriber Layer 1 Service Attributes – Add latest IEEE 802. 3 Ethernet and INCITS T 11 Fibre Channel interfaces • Amendment to Operator Layer 1 Service Attributes – Add support for ‘Beyond 100 G’ OTN ENNI and Flex. O interfaces • In LSO Committee, enhance Network Resource Provisioning IPS for Layer 1 (Presto) – NRP Classes, data types, service operations • In LSO Committee, add support for Subscriber and Operator L 1 Services (Legato) – APIs for Service Catalog, Ordering, Inventory, Topology, Notification

Thank You