1. WORKSHOP I Standardizing MEF 3.0 Services Optical, CE, IP & SD-WAN
Jan. 30, 2018

2. Speakers Kevin Vachon David Martin COO, MEF
L1CS Editor in MEF; Senior Systems Engineer, IP/Optical Networking Business Group, Nokia
David Ball
Joe Ruffles
Services Committee Co-Chair, MEF; Senior Architect, Cisco
SD-WAN Project Co-Leader, MEF; Global Standards Architect- Strategy & Innovation, Riverbed Technology

3. Topics MEF 3.0 Services Overview
MEF 3.0 Services Specification Development & Projects
MEF 3.0 CE
MEF 3.0 Optical
MEF 3.0 IP
MEF 3.0 SD-WAN
MEF 3.0 Survey

4. MEF 3.0 Services Overview

5. MEF 3.0 Global Services Framework
Optical
Expanded CE
IP VPNs
SD-WAN
Security-as-a-Service
Application Services
LSO APIs
Orchestration across multiple service providers
Orchestration over multiple network technology domains
SDKs and specifications
Certification
Cloud-based test platform
Services & LSO APIs
Subscription-based
Community
MEF global membership
MEF developer community
Certified professionals
Open source projects & SDOs
Enterprise advisory council
MEF 3.0 projects on MEFnet
MEF 3.0 services will deliver the dynamic performance, security, and agility that will enable users to thrive in the digital economy.
MEF 3.0 has 4 key elements:
MEF 3.0 blends an expanded set of sophisticated, standardized services with an emerging suite of LSO APIs to provide an on-demand, cloud-centric experience with unprecedented user- and application-directed control over network resources and service capabilities.
We also are increasing the agility of our popular service and equipment certification programs to accelerate availability and adoption of MEF 3.0 certified services and technologies.
And we are working with a broader community, including the world’s leading service and technology providers, open source projects, standards associations, and enterprises, in order to realize the shared vision of orchestrating dynamic services across multiple providers and network technology domains.

6. A New, Revenue-Generating Multi-Service Framework
Optical CE IP SD-WAN SECaaS Apps
Mobile
Commercial
Self-service
Web Portal
Data Center
Cloud Service Provider
Internet Cloud
Retail Service Provider
Wholesale Operator
Residential
FRAMEWORK
What does MEF 3.0 bring to the table compared to the dynamic services that already are in the market?
In recent years, a number of service providers have introduced dynamic connectivity and virtualized services, but their innovation primarily has been limited to services delivered over individual networks. To realize the full potential of our market, we have to move beyond independent islands of excellence. We need to enable dynamic services across multiple provider networks. Inter-provider automation is a huge driver for MEF 3.0.

7. Agile, Assured & Orchestrated Services Across a Global Ecosystem of Automated Networks
On-demand, cloud-centric experience
Unprecedented user- and application-directed control over network resources & service capabilities
Most advanced standardized services, interconnected on a global basis
MEF 3.0 blends an expanded set of sophisticated, standardized services with an emerging suite of LSO APIs to provide an on-demand, cloud-centric experience with unprecedented user- and application-directed control over network resources and service capabilities.
MEF 3.0 is driving continuous development of the world’s most advanced standards-based network services that can be interconnected on a global basis.

8. Agile Services Release Approach
Services released in streams (e.g., Optical, CE, IP, SD-WAN)
Releases aligned with new specification-supported services functionality
First MEF 3.0 release is MEF 3.0 CE R1, next will be MEF 3.0 CE R2
MEF 3.0 services are being released in streams, and these releases are aligned with new specification-supported service functionality.
The first MEF 3.0 service release is MEF 3.0 Carrier Ethernet Release 1, which will be an orchestration-ready service.
MEF 3.0 CE enhances CE 2.0 E-line, E-LAN, and E-Tree services with new and re-defined service attributes included in a package of MEF specifications published between 2013 and MEF 3.0 CE also includes new Access E-line and Transit E-line services based on specifications published in 2016 and 2017.

9. MEF 3.0 Services Specification Development & Projects

10. Services Specification Development Flow Chart
Abstract Test Suites
Service Definitions
Certification
Service Attributes
Special Topic Ias
(e.g. SOAM, SAT, CoS, etc.)
APIs
Info/Data Models
MEF specifies services by describing external behavior without constraining how services are implemented.

11. MEF 3.0 Services Specs – Completed & In Progress
Spec Type
Carrier Ethernet IP
Optical
SD-WAN
Service Attributes
Ethernet Subscriber Service Attributes (MEF 10.3, MEF , MEF , MEF 10.4)
Ethernet Operator Service Attributes (MEF 26.2)
IP Subscriber Service Attributes
L1 Subscriber Services and Attributes
L1 Operator Services and Attributes
SD-WAN Services and Attributes
Service Definitions
Ethernet Subscriber Services (MEF 6.2)
Access E-Line Services (MEF 33)
Ethernet Operator Services (MEF 51, Ethernet Operator Services revision)
Mobile Backhaul (MEF 22.3)
Virtual NID Services (MEF 47)
Managed Access E-Line Services
Simplified Transit E-Line Services
Special Topic IAs
Service OAM Fault Management (MEF 30.1)
Service OAM Fault Management (MEF 35.1)
Layer 2 Control Protocols (MEF 45)
Class of Service and Bandwidth Profiles (MEF 23.2, MEF )
Service Activation Testing (MEF 48, MEF 48.1)
Transport for 5G
SOAM for IP Services,
SAT for IP Services
Info/Data Models
Carrier Ethernet info Model (MEF 7.3)
SOAM FM MIB (MEF 31.1)
SOAM PM MIB (MEF 36)
SOAM FM Yang (MEF 38)
SOAM PM Yang (MEF 39)
Subscriber Services MIB (MEF 40)
Operator Services MIB (MEF 42)
Legato Interface Profile (MEF 56)
Subscriber Services Yang (MEF 58)
Note: In progress projects shown in blue

12. MEF 3.0 Services Project Status
Editor
Kick-off
CfC1
CfC2
CfC3 LB
Published
Architecture
Cloud Services Architecture
Mehmet Toy
Proposed IP
IP Service Attributes
David Ball
1Q2016
Motion
SAT for IP Services
Mike Bencheck
SOAM for IP Services CE
MBH IA – Phase 3
Glenn Parsons
3Q2013 *
---
Managed Access E-Line
Vin Alesi
4Q2015
Service Activation Testing
Isabelle Morency
MEF 10.4
Bob Klessig
4Q2016
Request
Transport for 5G
1Q2017
OVC Services revision
Bill Bjorkman
4Q2017
Simplified Transit E-Line
Bruce Eldridge
CE for Cloud revision
Raghu Ranganathan
Optical
Layer 1 Services
David Martin

13. MEF 3.0 Services Project Status
Editor
Comment
SD-WAN (Applications Committee)
SD-WAN Service Definition
Ralph Santitoro
SD-WAN (MEF Community)
Multi-Vendor Implementation
Joe Ruffles, Tim Van Herck

14. Preliminary MEF Services Roadmap* MEF 3.0 Optical MEF 3.0 CE
Completed
In Development
Planned
Q1 2018
Q2 2018
Q3 2018
Q4 2018
Q1 2019
MEF 3.0 Optical R1
Subscriber Services R2
Operator Services R2
Managed Access E-Line, OVC Services (51.1) & MBH IA Phase III (22.3), SAT Phase II (48.1), CE Service Attributes (10.4) R3
Simplified Transit E-Line , Transport for 5G IA
MEF 3.0 CE
Preliminary R1
MEF 3.0 IP R1
Service Attributes R2
Operator Services R3
Service Definitions
MEF 3.0 SD-WAN R1
Performance Tiers R2
Services and Attribute
MEF 3.0 SECaaS (tbd)
This is a mock-up
*. Proposal is to have release dates align to when a document goes to letter ballot, for planning purposes

15. MEF 3.0 CE

16. MEF 3.0 CE R1 – Orchestration-Ready Services
Enhances subscriber
CE 2.0 E-Line, E-LAN, E-Tree (specs )
New operator
Access E-Line, Transit E-Line, Access E-LAN, Transit E-LAN (specs )
Highest level of performance, assurance, agility in market
MEF 3.0 services are being released in streams, and these releases are aligned with new specification-supported service functionality.
The first MEF 3.0 service release is MEF 3.0 Carrier Ethernet Release 1, which will be an orchestration-ready service.
MEF 3.0 CE enhances CE 2.0 E-line, E-LAN, and E-Tree services with new and re-defined service attributes included in a package of MEF specifications published between 2013 and MEF 3.0 CE also includes new Access E-line and Transit E-line services based on specifications published in 2016 and 2017.

17. MEF 3.0 CE R1 & CE 2.0 Specs Compared

18. MEF 3.0 CE Resources – Overview Documents

19. MEF 3.0 CE Resources – Technical Documents
Technical Foundations
Technical Specifications Contribution to
CE 2.0 and MEF 3.0

20. MEF 3.0 Optical

21. MEF 3.0 Optical Service - Motivation
Standard set of L1 service definitions (similar to L2 and emerging L3)
Provides subscribers with consistent offerings for comparison (e.g., performance)
Standard definition of an L1 ENNI and associated Operator services
Enables simplified, faster interconnect between Service Providers / Operators
Certification of another set of Service Provider offerings
Should be lower cost than CE 2.0 certification since fewer service attributes to test for compliance
Will allow Service Providers to leverage LSO service management benefits for L1 services
Improved service delivery times through automated service ordering and configuration processes
Faster time-to-revenue and lower OPEX

22. Subscriber Optical Service (UNI-UNI)
Point-to-point, bi-directional, full port rate (wire speed)
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
1000BASE-X (8B/10B), FC-1600 (64B/66B)
An encoded data block is the entity (L1 Characteristic Information) transported by the L1 Virtual Connection (L1VC)
Physical port at each UNI may have a different optical interface function
Short reach, intermediate reach, long reach, etc

23. Subscriber Optical Service Attributes
UNI Service Attributes (2)
UNI ID, Physical Layer
Subscriber L1VC Service Attributes (3)
Subscriber L1VC ID, Subscriber L1VC End Point List, Subscriber L1VC SLS
Service Level Spec includes five Performance Metrics
One-way Delay, Errored Second (ES), Severely Errored Second (SES), Unavailable Second (UAS), Availability
Subscriber L1VC End Point Service Attributes (2)
Subscriber L1VC End Point ID, Subscriber L1VC End Point UNI
L1VC Layer 1 Virtual Connection
SLS Service Level Specification

24. Subscriber Optical Service
UNI1 SAs
UNI2 SAs
UNI1 ID
UNI2 ID
Physical Layer1: (p, c, o)
Client protocol
Coding function
Optical Interface function
Physical Layer1: (p, c, o)
Client protocol = UNI1 (p)
Coding function = UNI1 (c)
Optical Interface may differ SE
UNI 1
UNI 2
Service Provider Network
Subscriber LIVC
Subscriber L1VC End Point2 SAs
Subscriber L1VC End Point1 SAs
Subscriber L1VC SAs
L1VC End Point ID1
Subscriber L1VC ID
L1VC End Point ID2
L1VC End Point UNI1
Subscriber L1VC End Point List
L1VC End Point UNI2
Subscriber L1VC SLS: (ts, T, PM)
PMs (Delay, ES, SES, UAS, Availability)
Subscriber L1VC End Point
SA Service Attribute
SE Subscriber Equipment

25. Subscriber Optical Service Use Case Data Center Interconnect
Need high rates (10G-100G), lowest latency, lowest loss
Enterprise to a co-location site (outsourcing)
Co-location site to a web-scale Cloud Provider (Hybrid Cloud)

26. Enterprise Leases Subscriber Optical Service from CSP
Subscriber Optical Service Use Case Enterprise Outsourcing to Co-location
Enterprise outsources to co-location site for BC/DR or Cloud services where it can
Uses its own equipment and lease space, power, remote hands, or
Leases computing/storage from an IT provider (CNP case), or the CSP for IaaS, PaaS, SaaS
Enterprise Leases Subscriber Optical Service from CSP
Co-location
Site HQ
Branch
IP VPN
EVP-LAN/
UNI
Subscriber L1CS
Client Protocols
FC-800
FC-1200 (10GFC)
FC-1600
10GigE WAN (10GBASE-W)
10GigE LAN (10GBASE-R)
40GigE (40GBASE-R)
100GigE (100GBASE-R)
FC-3200
SAN
Extension
LAN
Extension
CNP Carrier Neutral Provider
CSP Communications Service Provider
BC Business Continuity
DR Disaster Recovery

27. Subscriber Optical Service Use Case Enterprise Hybrid Cloud
Express Route (MS)
Direct Connect (AWS)
Cloud Interconnect (GCI)
Direct Link (SoftLayer)
UNIs
ICPs
Subscriber L1CS
Web-scale Cloud Provider Leases Subscriber Optical Service from CSP to Provide Presence in Colo HQ
Branch
IP VPN
EVP-LAN/
UNI
Subscriber L1CS
Back-up
Colo with
Cloud Exchange
UNIs
Client Protocols
10GigE WAN (10GBASE-W)
10GigE LAN (10GBASE-R)
40GigE (40GBASE-R)
100GigE (100GBASE-R)
ICP Internet Content Provider

28. Operator Optical Service (UNI-ENNI, ENNI-ENNI)
Same client protocols at the UNI as for Subscriber L1CS (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, 2e, 3, 4)
ENNI interface rates of 2.5G, 10G, 40G, 100G
Access L1 Virtual Connections from multiple UNIs may be aggregated to a single OTUk port at the ENNI
Transit L1 Virtual Connections from multiple ENNIs may be aggregated to a single OTUk port at another ENNI
An ENNI may support multiple Service Provider L1 Virtual Connections (Shared ENNI)

29. Operator Access & Transit Aggregation, Shared ENNI
Service Provider A SE
Operator C aggregates Access L1VCs to ENNI 2
Operator D aggregates Transit L1VCs to ENNI 2
Service Provider A is responsible for the e2e Subscriber L1CS between UNIs 1 and 2
Service Provider B is responsible for the e2e Subscriber L1CS between UNIs 3 and 4
Their services are carried over shared ENNI 2
Operator E
L1CS UNI 2
L1CS UNI 1
L1CS ENNI 3
Access L1VC SE
Operator C
Operator D
Access L1VCs
Transit L1VCs SE
L1CS ENNI 2
Operator F
L1CS ENNI 4
L1CS UNI 3
Access L1VC
L1CS UNI 4 SE
Service Provider B
Multiplexed L1VC End Points
Operator L1VC End Point
Multiplexed L1VC End Point (some capacity unused)

30. MEF 3.0 Optical Transport Implementation Project
L1CS
Service Attributes
CTO project is underway to develop a Proof-of-Concept for L1CS – first step to full LSO support for L1CS/λ
NRM
Network Resource Information Model
Self-service
Web Portal
NRP
Network Resource Provisioning Information Model
LSO Presto
ONF Transport-API (TAPI)
ONF TAPI Northbound (NBI)
EMS/T-SDN
Controller
Optical Transport SDN Controller
NFV MANO
SDN Controller
VNF
ETH/OTN
OTN
OTN
ETH/OTN
VNF
VNF
UNI
SDN Switch
Head Office
Data Center or Head End
Wide Area Network

31. MEF 3.0 IP

32. MEF 3.0 IP Service Attributes Project
Project goals
Define Service Attributes for Managed IP Services
Subscriber (end-to-end) services
Operator (inter-provider) services
Phase 1 Scope
IP VPNs and Internet Access (not internet peering)
Redundant access links to same provider
Includes SOAM, SLS, QoS, IPv4/v6 and dual-stack
Excludes multicast and dual-homing to different providers (in phase 1)
End goal
LSO for IP Services (Info & Data Models, APIs, etc)

33. IP Service Attributes for Subscriber IP Services Stage: Letter Ballot
Service Attributes agreed between an SP and a Subscriber for MEF IP Services.
Key concepts are introduced, including IP UNIs, IP Virtual Connections, IP Virtual Connection End Points and IP UNI Access Links.
Specific Service Attributes and corresponding behavioral requirements are defined for each of these entities.
Includes VPNs and Internet Access
SAs include support for assured services, e.g. multiple Classes of Service, performance objectives specified in a Service Level Specification, and Bandwidth Profiles.

34. Two Management Models at a UNI
UNI can have one or more IP links
UNI Routing – BGP, Static, OSPF
Terminate at one or more devices
UNI Link Addressing
Separate physical or at L2 (e.g. VLANs)
Static, DHCP, SLAAC
UNI Routing – BGP, OSPF, Static
UNI AL Addressing – Static, DHCP, Unnumbered/LL-only, SLAAC
DHCP Relay, DHCPv6-Prefix Delegation
UNI AL L2 Technology – Ethernet, VLANs, LAG, PPPoE, etc

35. VPN Services VPN Services Multi-CoS Bandwidth Profiles
SLS Performance Objectives between UNIs or other reference points
Multipoint or Rooted Multipoint
Extranets

36. Cloud Access Services Phase 1 - Internet Access NAT DNS
Bandwidth Profiles
Data Limits
Phase 2 – Private Cloud Access
TBD

37. Class of Service and L3 Control Protocols

38. Service Level Specification
Performance Objectives
Per Class of Service
Set of End Point pairs
Performance Metrics
Packet Delay Percentile
Mean Packet Delay
Inter-Packet Delay Variation
Packet Delay Range
Packet Loss Ratio
Service Uptime

39. Bandwidth Profiles

40. Where Next for the IP Service Attributes Project?
IP Subscriber Service Attributes is ready for Letter Ballot
But a number of topics were deferred:
Multicast
Private cloud access
Policy Based Routing and Route manipulation
Egress Class of Service Map
BFD and OSPF Authentication, and OSPF sham links
Operator Service Attributes are TBD
Lots of work still to do!

41. Where Next for Other IP Projects?
SOAM and SAT - proposed at this meeting (c.f. MEF 30.1, 35.1, 48)
Subscriber Service Definitions (c.f. MEF 6.2)
E.g. define a simple VPN Service and IP Access Service
Needed for certification etc
CoS and BWP Implementation Agreement (c.f. MEF 23.2)
May be able to re-use some MEF 23.2 work
LSO
Info/Data models
APIs for Legato, Presto, etc
If interested, please contact the relevant Co-Chairs

42. MEF 3.0 SD-WAN

43. SD-WAN – Service Provider Threat or Opportunity?
Will SD-WAN Services cannibalize MPLS VPN Services ?
Is it possible to deliver a good SLA using an OTT SD-WAN service ?
Can SD-WAN services really bring new sites in minutes instead of weeks ?
Can SD-WAN services connect off-net site without peering agreements ?
Source: Emerging Third Network Services Enabled By LSO, SDN, NFV & CE 2.0, MEF & Vertical Systems Survey Report, Jan 2017

44. Concepts: Overlay and Underlay Networks
The physical transport network
Overlay Network
Virtual Network abstracted from the transport network (underlay network)
Overlay networks are tunneled over Underlay network
Using an encapsulation protocol, e.g., VxLAN, NVGRE, IPSec tunnel
Overlay/Underlay terminology used in DC Networking
Terminology usage more recent with WAN (SD-WAN)
Although, MEF has defined Carrier Ethernet as a virtual overlay service

45. What is an SD-WAN?

46. What is an SD-WAN? ?

47. What is an SD-WAN?
Currently no industry standard definition but described as follows:
Specific application of an SDN applied to WAN connections
A Virtual (Overlay) Network that runs on top of public Internet and VPNs
Operates over existing wireline or wireless networks
Has no interaction with the (underlay) network over which it operates
VPN
SD-WAN
Internet

48. Fundamental Capabilities of SD-WAN Services
Secure IP-based Virtual Overlay Network
Policy-based Application Forwarding
Encrypted IP tunnels over transport networks
Applications forwarded based on QoS, Security and Business Priority
Transport-independence from Underlay
Operates over any type of underlay network
Service Automation via Centralized Management, Control & Orchestration
Service Assurance of SD-WAN Tunnels
Zero Touch Provisioning
Centralized Policy Management
Real-time QoS performance measurements used to make application forwarding decisions
Application-Driven Packet Forwarding
WAN Optimization (optional)
Traffic forwarded based on application type
Data compression, TCP optimization, data caching, data de-duplication to minimize BW
Forward Error Correction to reduce packet loss introduced by underlay network
High Availability via Multiple WANs
WAN load balancing, diverse WAN providers, wireless and wireline WANs

49. SD-WAN Service Components
SD-WAN Edge
Physical or Virtual
SD-WAN Gateway
Between SD-WAN and CE/MPLS
SD-WAN Controller
Centralized Management of SD-WAN Edges & Gateways
Service Orchestrator
Lifecycle Service Orchestration of SD-WAN and other services
Subscriber Web Portal
Subscriber service ordering and modification
OSS/BSS Apps
Service
Orchestrator
Subscriber Web Portal
SD-WAN
Controller
Internet
VNFM
SD-WAN
Edge
CE / MPLS
SD-WAN
Edge
SD-WAN Overlay Tunnel
SD-WAN
Gateway
SD-WAN Service Components

50. SD-WAN Service Components in MEF LSO RA
Customer Domain
Service Provider Domain
Customer Domain
Service Provider Domain
Self-service
Web Portal
OSS/BSS Applications
Service Orchestrator
SD-WAN Controller
SD-WAN Edge
Cantata
Allegro
Legato
Presto
Adagio
SD-WAN Gateway
OSS/BSS Applications
Cantata
Legato
Self-service
Web Portal
Service Orchestration Functionality
Allegro
Presto
Domain Controller
Adagio
Element Management

51. SD-WAN Service Use Case Hybrid WAN: SD-WAN Service over Internet and MPLS WANs
Subscriber
Web Portal
OSS/BSS Applications
Cantata
Encrypted SD-WAN tunnel over the Internet
Can often increase site-to-site bandwidth at no additional cost
Increased network availability and resiliency
Internet and MPLS VPNs can be provided by different Service Providers
Legato
Service Orchestrator
Allegro
Presto
SD-WAN Controller
Adagio
Adagio
Internet Cloud
SD-WAN Edge CPE
SD-WAN Edge CPE
MPLS VPN
CSP/MSP Network
SD-WAN Tunnel

52. SD-WAN Service Use Case WAN Resiliency: SD-WAN Service over Multiple ISPs
Subscriber
Web Portal
OSS/BSS Applications
Cantata
SD-WAN service across multiple ISPs to achieve the WAN resiliency
Easily add off-net sites to an existing SD-WAN service deployment
Leverage Forward Error Correction to achieve better SLA than Internet underlay network
Legato
Service Orchestrator
Allegro
Presto
SD-WAN Controller
Adagio
Adagio
ISP X
ISP A
SD-WAN Edge CPE
SD-WAN Edge CPE
ISP Y
ISP B
CSP/MSP Network
SD-WAN Tunnel

53. NFV Resource Orchestrator
SD-WAN Service Use Case SD-WAN Edge VNF on vCPE: Multiple Virtual Network Services
Subscriber
Web Portal
OSS/BSS Applications
Cantata
Use SD-WAN Edge VNF on vCPE for additional virtual network services
VNFs on vCPE use NFV Resource Orchestrator
SD-WAN Controller and NFV Resource Orchestrator managed by Service Orchestrator
Legato
Service Orchestrator
Allegro
Presto
Presto
SD-WAN Controller
NFV Resource Orchestrator
Adagio
Adagio
Adagio
SD-WAN Edge CPE
SD-WAN Edge vCPE
VNF
WANs
WANs
VNF
CSP/MSP Network
SD-WAN Tunnel

54. SD-WAN Service Use Case SD-WAN Edge VNF Running in the Cloud
Subscriber
Web Portal
OSS/BSS Applications
SD-WAN service between SD-WAN Edge CPE and SD-WAN Edge VNF in the cloud
Enterprises want to extend their networks to applications running in public and virtual private clouds
SD-WAN provides secure connectivity between site and cloud applications
Cantata
Legato
Service Orchestrator
Allegro
Presto
Presto
SD-WAN Controller
NFV Resource Orchestrator
Adagio
Adagio
Adagio
SD-WAN Edge CPE
VNF
WANs
WANs
Cloud Service Provider
SD-WAN service across multiple WANs with an SD-WAN Edge CPE and a SD-WAN Edge VNF running in a cloud environment
SD-WAN service tunnel begins on the SD-WAN Edge CPE and terminates on the physical compute server or virtual machine (VM)
SD-WAN tunnel terminating on the server or VM provides secure connectivity between site and the cloud applications
Figure 7 from SD-WAN white paper
Figure 7 illustrates a use case for an SD-WAN service across multiple WANs with an SD-WAN Edge CPE (left site) and a SD-WAN Edge VNF running in a cloud environment. In this use case, the SD-WAN service tunnel begins on the SD-WAN Edge CPE at the left site and terminates on the physical compute server or virtual machine (VM) where the application is running, e.g., in a cloud service provider environment.
The benefit of terminating the SD-WAN tunnel on the server or VM is that the SDWAN tunnel provides secure connectivity between the site on the left and the cloud
applications inside the cloud service provider’s data center.
CSP/MSP Network
SD-WAN Tunnel

55. Learning and Contributing to MEF SD-WAN Work
Developing Use Cases and User Stories
Building Reference Implementations within the MEF LSO framework
wiki.mef.net/display/CTO/OpenC S+SD-WAN+Project
Developing SD-WAN Technical Specification Standard
Service Definition, Attributes, Use Cases, Deployment Models
wiki.mef.net/display/APP/SD- WAN+Service+Definition+Techni cal+Specification
Developing Use Cases
Developing white papers, webinars and workshops
wiki.mef.net/display/MC/SD- WAN+Market+Education+Project
SD-WAN Implementation Project
SD-WAN Technical Specification Project
SD-WAN Market Education Project

56. 2018 MEF 3.0 Survey Joint with Feb 2018
PLEASE PARTICIPATE
2018 MEF 3.0 Survey Joint with Feb 2018