path from ce 2.0 to dynamic services roadmap...path from ce 2.0 to dynamic services roadmap 45 min 2...

Sponsored by:

Hernán Contreras G.Technical Solutions Architect

Cisco

Path from CE 2.0 to Dynamic Services Roadmap

45 min

2

Agenda

MEF’s Carrier Ethernet and other Dynamic Services

1

Lifecycle Service Orchestration (LSO)

2

From Technical Specifications to MEF Products

3

3

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

4

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

5

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

• 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.

Service ProviderUNI

“VC”

UNI

Service Provider

Operator

UNI

“VC” “VC”UNI

ENNI

For Ethernet Services, “VCs” are EVCs or OVCs

EVC: Ethernet Virtual Connection OVC: Operator Virtual Connection

6

CE 2.0 Retail Services Types (EVC)

E-Line

• Point-to-Point

• Ethernet Private Lines (EPL)

• Ethernet Virtual Private Lines (EVPL)

E-LAN

• Multipoint L2 VPNs

• Transparent LAN Service

• Multicast Networks

• EP-LAN, EVP-LAN

E-Tree

• Rooted Multi-Point L2 VPNs

• Traffic Segregation

• EP-Tree, EVP-Tree

UNI

Point-to-Point EVC

UNI

Rooted Multi-point EVC

UNI

UNI

UNI

Multi-point to Multi-point EVC

UNI

UNIUNI UNI

7

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

8

MEF Carrier Ethernet 2.0

EVC: Ethernet Virtual ConnectionOVC: Operator Virtual Connection

Globally Adopted, Certifiable, Connectivity

Services Framework

Retail (EVC Services)

E-Line

E-LAN

E-Tree

Wholesale (OVC Services)

E-Access

E-Transit

Access E-Line Access E-LAN

Transit E-Line Transit E-LAN

9

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

End-to-End Carrier Ethernet Service

E-Access Service (OVC)

CE

UNI

CE

ENNIUNIEnd User

Subscriber Headquarters

End User Subscriber Branch Site

Carrier Ethernet Network Carrier Ethernet Network

ON-NET CUSTOMER LOCATIONS

OFF-NET CUSTOMER LOCATIONS

Retail Service Provider – The Buyer(Has relationship with end-customer)

Wholesale Access Service Provider – The Seller(Provides Access to remote customer location)

• Multi-CoS capable• Service OAM

10

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)

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

Access E-Line Service

UNI_1

UNI_2

ENNI_AB

CEN A

CE-VLAN IDs 3, 4, 5

ENNI_AC

CE-VLAN ID 34

Full Map: All CE-VLAN IDs map to the Blue OVC End Point

S-VLAN ID 1011

S-VLAN ID 253

S-VLAN ID 267

Access E-LAN Service

CEN A

Access E-LAN

UNI_1

UNI_N

ENNI_1

ENNI_N

OVC End Point Map @ UNI: 1, >1 or all CE-VLAN IDs

OVC End Point Map @ UNI: 1, >1 or all CE-VLAN IDs

S-VLAN ID 115

S-VLAN ID 3398

11

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

CE

UNI

CE

ENNIUNI

End User Subscriber

Headquarters

End User Subscriber Branch Site

Carrier Ethernet Network(CEN)

CENENNI

E-Access ServiceE-Transit Service

(OVC)

End-to-End Carrier Ethernet Service

CEN

12

MEF 51 E-Transit ServicesE-Transit Services: based on Operator Virtual Connection (OVC) between External Network Network Interface (ENNIs)

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

Transit E-Line Service

ENNI_AC

ENNI_AB1

CEN A S-VLAN ID 923

S-VLAN ID 51

ENNI_AB2

S-VLAN IDs 101-150

S-VLAN IDs 101-150Operator B’s CEN is to the left of this ENNI

Operator B’s CEN is to the right of this ENNI

Operator C’s CEN is to the right of this ENNI Transit E-LAN Service

ENNI_ACENNI_AB

CEN A

S-VLAN ID 984

S-VLAN ID 253

Transit E-LAN

S-VLAN ID 2033

Hairpin switching

13

Some Service Delivery Permutations

• Service Provider may deliver:– Layer 1 Service, e.g., Optical Wavelength Service (OWS)

• Delivered over an OTN Layer 1 transport

– 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

OWS over OTN

MEF standardizes the service model for each of the three network layers to facilitate automation and orchestration

SONET/SDHEPL

IEEE 802.3EVPL

Internet Access

MEF Layer 1 Services Project

15

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

16

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

17

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


ODU2e (OTU2e interface) 10.399 525 316



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

MEF IP Project

19

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

20

Subscriber IP Service - VPN

• Service attributes for UNI, IPVC, IPVC End Point

Service Provider

SubscriberHead Office

SubscriberBranch Office

SubscriberBranch Office

UNI

UNI

UNI

IPVC

IPVC EP

IPVC EP

IPVC EP

21

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

22

Subscriber IP Service – Cloud Access

• Internet Access or Private Cloud Access

• E.g., AWS, Google Cloud

• Could consist of only a single UNI

Service Provider

Subscriber

UNI

Cloud Service Provider or DC

IPVC

23

Operator IP Service• Service Provider uses another operator to reach a off-net

subscriber UNI to deliver IP Service

Service Provider

UNI UNI

ENNI

Operator 1 Network

Service Provider

IP Operator Service (IPVC)IP Operator Service (IPVC)

IP Subscriber Service (IPVC)

24

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

MEF IP Services Categorization and Use Cases

Lifecycle Service Orchestration (LSO)

27

Dynamic Orchestrated Services

Orchestrated Services

OpticalCarrier

EthernetIP

L4-L7 Point Services

Security ApplicationsSD-WAN

28

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

29

Service Lifecycle Process Model (MEF 50)

Product Lifecycle Service Operations Lifecycle

Market Analysis & Product Strategy

Product Design

Service & Resource Design

Product Launch

Marketing Fulfillment Response

Sales Proposal & Feasibility

Customer Order

Service Configuration &

Activation

Fault Management

Quality Management

Revenue Management

Service Termination

Serviceability

Fulfillment

Operation

MEF 50 leverages the TM Forum’s Business Process Framework, also referred to as the enhanced Telecom Operations Map (eTOM).

30

Service Lifecycle Process Model (MEF 50)

Product Catalogue*

Service Ordering (MEF 57)

Service Activation*

Performance Reporting (MEF 52)

LSO and Lifecycle Frameworks

LSO CapabilitiesFulfillment | Performance | Control | Assurance

Usage | Analytics | Security | Policy

* Future MEF Framework Specification

Service Qualification Questionnaire (MEF 53)

31

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.

32

LSO Reference Architecture and Capabilities (MEF 55)

Network Operator 2Network Operator 1

UserService

Endpoint

UserService

Endpoint

OperatorService Endpoint

End-to-End Network-as-a-Service

Cloud ServiceProvider

SDN Switch

Packet PNFs

UNIUNI ENNI

Packet PNFs

Traditional EMS

SDN Controller

NFV MANO

Packet SDN Controller

EMS: Element Management System PNF: Physical Network Function SOF: Service Orchestration Function

Head Office

FRAMEWORKFRAMEWORK

Self-serviceWeb Portal

LSO Interlude

LSO Presto

LSO SonataLSO Cantata

LSO Allegro LSO Legato

Business Applications

SOF SOF

LSO Legato

LSO Presto


LSO AdagioLSO Adagio

• Fulfillment• Performance• Control• Assurance

• Usage• Analytics• Security• Policy

The LSO architecture and framework enables automated management and control of end-to-end Connectivity Services that span multiple provider domains

MEF 55 LSO Reference Architecture

Network Infrastructure

CustomerApplication Coordinator

Element Control and Management

Infrastructure Control and Management

Service Orchestration Functionality


PRESTO(SOF:ICM)

LEGATO(BUS:SOF)



ADAGIO (ICM:ECM)

LEGATO(BUS:SOF)

PRESTO(SOF:ICM)

ADAGIO (ICM:ECM)



SONATA(BUS:BUS)

INTERLUDE (SOF:SOF)

CANTATA(CUS:BUS)

ALLEGRO(CUS:SOF)

KeyCUS: Customer Application CoordinatorBUS: Business ApplicationsSOF: Service Orchestration FunctionalityICM: Infrastructure Control and ManagementECM: Element Control and Management

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.

information and data models that enable the definition of open and interoperable APIs supporting LSO functionality

MEF LSO Related Modeling Projects

Network Infrastructure

CustomerApplication Coordinator




PRESTO(SOF:ICM)

ALLEGRO(CUS:SOF)

LEGATO(BUS:SOF)

CANTATA(CUS:BUS)



ADAGIO (ICM:ECM)

LEGATO(BUS:SOF)

PRESTO(SOF:ICM)

ADAGIO (ICM:ECM)

INTERLUDE (SOF:SOF)

SONATA(BUS:BUS)




KeyCUS: Customer Application CoordinatorBUS: Business ApplicationsSOF: Service Orchestration FunctionalityICM: Infrastructure Control and ManagementECM: Element Control and Management

Product catalog;Product feasibility;Product ordering;

Acceptance testing info;Billing and usage;

Trouble reports / status;Product level quality;

Dynamic service control;Service state info;

Service performance & quality;Service related alerts;

Create and manage connectivity and logical network functions;

Topology and routing;Performance and Fault;

Resource inventory;Connectivity policy

Serviceability & qualification;Product catalog;

Product ordering;Acceptance testing info

Billing exchange;Trouble reports / status;

Product level quality;

Service feasibility;Service activation;

Usage events & metrics;Service performance & quality;

Service policy

Dynamic service control;Service parameter config;

Service state info;Service performance info;

Service problem alerts

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

36

LSO Engineering Methodology

MEF Service Definitions(including virtualization)

Common Information Models

LSO ReferenceArchitecture & Framework

Business Process Flows

Interface ProfilesAPI Specifications& Data Models

ReferenceImplementations

API ImplementationsCertifications

MEF 7.3, Common Model, Resource

Model,Cloud Services

MEF 50.x

Profiles for LSO Presto, LSO Legato, etc.

JSON, SCA, YANG, etc.

LSO Hackathon,

ODL project, OPNFV

MEF LSO Reference

Architecture& UNITE

NRP API Test Suite

TOC: Product Catalog, Ordering, Performance

Reporting, Serviceability

MEF 6.2, 33, 51, 10.3, 26.2, etc.

37

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 Prestorespectively 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.

LSO Presto R1 APIs

FRAMEWORK


Service Orchestration

Network Operator 1

UserService

Endpoint

UserService

Endpoint


Self-service Web Portal


UNIUNI

Head Office

Customer Facing

Open APIs

Intra-provider Open APIsPresto

Technology DomainsOpen APIs



LSO Presto R1

40

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

LSO Sonata R1 APIs

FRAMEWORK



FRAMEWORK

Network Operator 2Network Operator 1

UserService

Endpoint

UserService

Endpoint


Self-service Web Portal


UNIUNI ENNI

Head Office

Customer Facing

Open APIs

Inter-Provider

Open APIs

Inter-provider Open APIsSonata





LSO Sonata R1



43

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.

44

MEF PR LSO Sonata R1

45

MEF LSO Ecosystem Capabilities

• E2E Fulfillment Orchestration

Design of E2E services and assignment of resources

Order and Request management and tracking

Coordination of all provisioning tasks

Testing orchestration and turn-up

Service delivery orchestration

46

MEF – TM Forum LSO APIs Collaboration

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

orchestration and management work being led by TM Forum.

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.

Framework

Leveraging TM Forum’s Open API framework, digital business architecture, industry standard Information Framework and tools for end-to-end service management and orchestration.

Open APIFramework

47

Network Level Orchestration Open APIs

MEF’s Intra-operator APIs and Open Initiatives

Fulfillment Performance Policy

Control Assurance Usage

Security

Analytics


Technology Domains

Service Level Orchestration Open APIs

Open APIs

NFVData Center Packet WAN Optical TransportSD-WAN Cloud Exchange 5G Wireless

Services


E-Line E-LAN E-Tree E-AccessSECaaS

E-Transit

Internet Access L3 VPNs IP TransitWavelength

AppServices

48

MEF’s Inter-operator APIs and Open InitiativesInter-Operator

Open APIsService Orchestration



Inter-OperatorOpen APIs

ServiceabilityOrdering

Address Validation… Others

Technology Domain Technology Domain Technology Domain

Services


E-Line E-LAN E-Tree E-AccessSECaaS

E-Transit

Internet Access L3 VPNs IP TransitWavelength

AppServices

AT&T Announcement

MEF & TM Forum Announcement

http://about.att.com/story/industry_leaders_collaborate_on_common_sdn_business_api_standards.html

https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwidloCaw-nSAhVC0xQKHbSFBSkQFggaMAA&url=https://www.tmforum.org/press-and-news/mef-tm-forum-carriers-collaborate-apis/&usg=AFQjCNFoSuxdSbW6vVINsmqzrPbgFoZAyg&bvm=b

49

• 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

50

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 inter-relationships via the LSO sub-architecture

Customer Application Coordinator

PartnerSOF

http://pnda.io/

https://wiki.mef.net/display/CTO/Open+LSO+APIs+Home+Page

51

• 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

52

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 Service Orchestration) and integrated into multi-operator agile, assured and orchestrated end to end L2 and L3 services.

Load Bal.

Central Office, Data Center or Head End

CPE

Presto APIs

SD-WANController

GW

UNI

SDNSwitch

CE 2.0 / MPLS

Self-serviceWeb Portal

SDNController SDN

SwitchNFV

MANO

UNI

SD-WAN

SD-WAN

Internet

RO - Resource OrchestratorGW - GatewayCPE - Customer Premise Equipment

Presto APIsPresto APIs

MEF Development Model

54

MEF Development Model

Liaisons to SDOs

Open Source Projects

Collaboration

MEF Agile Development Lifecycle

Accelerator

MEF Reference Implementations

PlatformMEF Dev.

Community

This is a

sample text

55

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

56

MEFnet Projects - Inter-carrier Orchestrated L3VPN

• 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

58

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

59

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

60

Industry White Paper of Third Network Services

60

Third Network Services

http://mef.net/tgn

http://mef.net/tgn

61

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

62

MEF – Advancing the Industry-Video-

Sponsored by:

Hernán Contreras G.Technical Solutions Architect

Cisco

Path from CE 2.0 to Dynamic Services Roadmap

45 min

path from ce 2.0 to dynamic services roadmap...path from ce 2.0 to dynamic services roadmap 45 min 2...

Documents