1

MEF Report: User to Network Interface (UNI)

Network-to-Network Interfaces (E-NNI)and Global Interconnection Tools

Arie Goldberg,CEO, Omnitron System Technology, Inc.

Board Member, Metro Ethernet Forum

2

Agenda

• Carrier Ethernet Challenges and Services• Ethernet Services Network Demarcation:

– UNI and E-NNI

• NID Project• Global Interconnect Tools

– Global Services Directory– Wholesale Access Template

3

Carrier Ethernet Challenges and Services

4

Demand Drivers – Services and Bandwidth

On-line Government Education Remote learning Healthcare date & Tele-medicine

Commerce, On-line Business, Tele-workers, On-lineFinancial Services, On-line

NEWtools!Apps!

BackhaulApps

$$$$

$$$$

$$

$$$$

$$

VoIPVoDIPTV E-Line

E-LAN)

Low CAPEXLow OPEX

Low Cost to Subscribers

5

Some of the Challenges of CE Service Providers

• Turn-up services quickly and efficiently - ASAP

• On/Off-Net services – meet global customer needs - buy and sell / wholesale with other providers - generate revenue on and off-net

• Reliability/Up-time (99.999%) - enable high value services with SLAs for higher rate revenues

• Quality – build customer satisfaction – increase customer retention – keep revenues coming

• Efficient operation - keep OpEx costs down – be competitive and profitable

6

The MEF 5-Attributes of Carrier Ethernet

• Carrier Ethernet is a ubiquitous, standardized, carrier-class SERVICE defined by five attributes that distinguish Carrier Ethernet from familiar LAN based Ethernet

• It brings the compelling business benefit of the Ethernet cost model to achieve significant savings

Carrier Ethernet

• Scalability

• Standardized Services

• Service Management

• Quality of Service

• Reliability

Carrier Ethernet Attributes

7

MEF defined Basic CE Services

E-LINEEPL: Private LineEVPL: Virtual Private Line

E-LANEP-LAN: Private LANEVP-LAN: Virtual Private

LAN

Point to PointSite2Site L2 VPNs

E-TREEEP-Tree: Private TreeEVP-Tree: Virtual Private

Tree

Point to Multi-PointBroadcasting ServicesTriple Play backhaulMobile backhaul

Multi-Point to Multi-PointMulti-Site L2 VPNsTransparent LANs

Point-to-Point EVC

CPECPEUNIUNI

UNIUNI

CPECPE

CPECPE

UNIUNI CPECPEUNIUNI

Multipoint EVC

Rooted Multipoint EVC

CPECPE UNIUNI

CPECPEUNIUNI

CPECPEUNIUNI

8

Global Services crossing carrier boundaries

Carrier AService Provider

Carrier CAccess Provider

Carrier BTransport Provider

E-NNI

Multi-point to Multi-point EVCMulti-point to Multi-point EVC

UNI

UNI

UNI UNI

UNI

E-NNI

9

Carrier Ethernet’s “Evolution”

• Basic Ethernet Access Services definition• From Metro to Regional Services• From Regional to National Services• From National to International / Global Services• From Intra-Provider (In-franchise/IF) to Inter-

Provider (out-of-franchise/OOF) Services

1999, Europe:First Metro Ethernet

LAN

WAN OOF WANGlobal InterconnectMAN

1010

Three Phases of Carrier Ethernet2004

Carrier Ethernet Defined

2001-3

First MEF specs

2005-7 2008-10

Global Interconnect

UbiquityRevenues>$30bn

Phases Timeline

Carrier Ethernet Milestones

Phase 1: Architecture and Definition

Carrier Ethernet defined

First specifications definedImplementation beginsDefinitions of Ethernet services

Phase 2: Implementation and CertificationMEF Certification ProgramLarge scale deployment beginsCarrier Ethernet extends from Metro

Phase 3: Global Interconnect Specification for Carrier Ethernet InterconnectSpecifications for automated management of UNIService OAM fault and performance specificationsClass of Service alignmentOperational tools: WAIG, GSD

2011-14

11

Carrier Ethernet Networks Demarcation:UNI and E-NNI

12

Carrier Ethernet Demarcation Points

• UNI - User-to-Network Interface– Demarcation point between

• Ethernet Service Provider/Access Network Provider and Subscriber

– Ethernet Service / Ethernet Virtual Connection (EVC) starting / ending point

• E-NNI - External Network-to-Network Interface– Demarcation point between:

• Ethernet Service Provider and Access Network Provider

• Ethernet Access Provider and Transport Network Provider

• EVC - Ethernet Virtual Connection– Ethernet service connecting between 2 or more UNIs

E-NNI E-NNIAccess Network Access Network

ProviderProvider

E-NNI Transport Transport

Network ProviderNetwork ProviderEthernet Service Ethernet Service

ProviderProvider

UNI UNI

EVCEVCSubscriber Subscriber

13

Service provider responsibilityUNIUNI

Carrier Ethernet Network

The MEF User Network Interface

• The User Network Interface (UNI)– The UNI is the single point that is the demarcation

between the customer and the service provider/Cable Operator/Carrier/MSO

– The UNI is typically at a port on an active device owned and operated by the Service Provider

– The UNI in a Carrier Ethernet Network uses a physical Ethernet Interface at operating speeds 10Mbs, 100Mbps, 1Gbps or 10Gbps

CECE

In this instance the UNI is located at the port of the service provider edge device located at the customer premises.

The service provider “cloud” is shown terminating in the customer premises

customer responsibility

14

Functional Elements of the UNI

• There are two functional elements (typically*) located in two connected devices situated on either side of the UNI demarcation point:

• UNI-C: Executes the processes of the customer side• UNI-N: Executes the processes of the network side

* All the functions of the UNI-N and UNI-C need not be located in the same physical device as they may be located in several devices

Service provider responsibilityUNIUNI

CECE

customer responsibility

UNI-CUNI-C

UNI-NUNI-N

Carrier Ethernet Network

15

From UNI 1 to UNI 2

MEF 11 introduced 3 types of UNI– UNI Type 1 (now defined in MEF 13), November 2005

• Service Provider and Customer manually configure the UNI-N and UNI-C for services

• UNI Type 1.1 and 1.2 are defined

– Type 1.1 : Non-multiplexed UNI for Services like EPL– Type 1.2 : Multiplexed UNI for Services like EVPL

– UNI Type 2 (now defined in MEF 20)• An automated implementation model allowing UNI-C to retrieve EVC

status and configuration information from UNI-N• Enhanced UNI attributes • Additional fault management and protection functionality• UNI Type 2.1 and 2.2 are defined

– Backward compatibility with UNI Type 1

– UNI Type 3 (Possible future MEF Specification)• Allows the UNI-C to request, signal and negotiate EVCs and its

associated Service Attributes to the UNI-N. UNI • Type 3 is for further study.

16

Functionality and Scope of MEF 20

• Ethernet Local Management Interface (E-LMI)– Allows UNI-C to retrieve EVC status and service attributes from

UNI-N as specified in MEF 16• Link OAM (Operation, Administration and Management)

– Allows customer and service provider to monitor and diagnose the UNI connectivity via Link OAM (link level)

• Service OAM– Allows customer and service provider to monitor and diagnose

the UNI connectivity via Service OAM (end-to-end)• Protection

– Capability to protect UNI against port failure via Link Aggregation protocol

• Enhanced UNI Attributes– Such as bandwidth profile per egress UNI, Maximum Transfer Unit

size, etc. as defined in MEF 10., MEF 6.1• L2CP Handling

– Governs the passing or filtering of Layer 2 control protocols to the Ethernet Virtual Connections

17

UNI 2 - MEF 20 Implementation Options

MEF 20 Specifies phased/alternate implementation. This allows quicker time to market and faster time to revenue for all concerned

UNI Type 2.1Mandatory Features

• Backward comp. to UNI Type 1

• Service OAM

• Enhanced UNI attributes

• L2CP handling

Optional Features• Link OAM

• Protection

• E-LMI

UNI Type 2.2Mandatory Features

• Backward comp. to UNI Type 1

• Service OAM

• Enhanced UNI attributes

• L2CP handling

• Link OAM

• Protection

• E-LMI

18

Testing UNI Types 1 & 2

MEF 20UNI Type 2

Implementation Agreement

Abstract Test Suite for UNI Type 2 Part 6: L2CP Handling

Abstract Test Suite for UNI Type 2 Part 5: Enhanced UNI Attributes

Abstract Test Suite for UNI Type 2 Part 4: Protection

Abstract Test Suite for UNI Type 2 Part 3: Service OAM

(Straw Ballot)Abstract Test Suite for UNI Type 2

Part 2: E-LMI (working Document)

MEF 21Abstract Test Suite for UNI Type 2 Part 1: Link OAM

MEF 13UNI Type 1

Implementation Agreement

MEF 19Abstract Test Suite for UNI

Type 1

MEF 11User Network Interface (UNI)

Requirements and Framework

Work in Progress / possible projects

• First Testing of MEF 20 is specified in MEF 21• Thorough testing is reflected in large number

of test cases• Further Test projects are in preparation• E-NNI will leverage MEF 21 test cases• MEF Certification will be decided in due course

19

Global Interconnect: E-NNI is a Key element

• External Network to Network Interface (E-NNI)– A reference point where 2 Service Providers meet in support of specified

MEF Services• Supports

– Multiple Carrier Ethernet networks and services, management, QoS , etc.– Supports simple interconnect and tunneling

• Impact on the Industry– Creates ubiquitous service level network for large and mid-size businesses– Generates new worldwide business opportunities for service providers at

lower cost– Brings new product and revenue opportunities for vendors

UNIUNI UNIUNI

UNIUNIE-NNIE-NNI

UNIUNI

Reference Point

Ethernet Virtual ConnectionCarrier A

network

Carrier Bnetwork

20

E-NNI Phase I

In Scope:

• E-LINE and E-LAN services (but not E-TREE)

• Multiple CENS– Inc. multiple E-NNIs or links between two CENs

• E-NNI protection (but not End-to-End service protection)– Customers & SP must provide loop-free connectivity

• End-to-End OAM and QoS– Inc. traffic “coloring” via IEEE PCPs or IETF DSCPs

• Service Frame delineation via IEEE 802.1

– No S-Tag or single S-Tag

21

• Service– Type– MTU

• Endpoint– Service Mux– Tag ID/CoS

Preservation

• Link – Rate– L2CPs

Basic OAM Protection QoS

• Link OAM–IEEE 802.3ah

• Service OAM–IEEE 802.1ag & ITU-T Y.1731

• Link Protection– IEEE 802.3ad

(LAG)

• Service Protection– IEEE 802.1D

(STP/MSTP)

• BandwidthProfiles

– By EI – By EVC– By PCP– By DSCP

• Performance– Delay / Jitter– Loss– Availability

E-NNI Attributes

Similar attribute structure as current MEF specifications

E-NNI Attributes

22

E-NNI Constructs: Putting it all together

E-NNI UNI2

• Access Network Provider – Provides CEVC1 connection between Subscriber UNI1 (RUNI) and

VUNI1 at E-NNI1 with Transport Network Provider

• Transport Network Provider– Provides CEVC2 connection between E-NNI1 (VUNI2) and E-NNI2

(VUNI3) with Ethernet Service Provider

• Ethernet Service Provider– Provides connection to E-NNI2 with Transport Network Provider– Provides End-to-End Ethernet Service to Subscriber

• Provides EVC between UNI1 and UNI2

UNI1 Transport Transport

Network ProviderNetwork Provider

Ethernet Service Ethernet Service ProviderProvider

Transit TunnelTransit TunnelTerminating TunnelTerminating Tunnel

EVC

Access Network Access Network

ProviderProvider

RUNI VUNI1 VUNI2 and VUNI3

E-NNI1 E-NNI2

SubscriberCEVC1 CEVC2Subscriber

23

Global Interconnect: E-NNI is a Key element

– MEF is acutely aware of the impact on the industry – Strong push from the board to release a spec this year

24

NID Project

25

Network Interface Device (NID)

• A device that provides the point of demarcation between an operator and a subscriber

• UNI-N functions are partitioned between the NID and the Network Edge device

• Provides the physical interface to the subscriber (fiber, copper)

• Owned by the Operator / Service Provider• managed by Operator / Service Provider• Provides fault and performance management for E2E services• Complex device

Service Provider Network Operator Network

E-NNI UNIUNI

CE

CE

NID NID

26

NID Types: Transport NID

• Transparent Media Converter - Not service or CE-VLAN aware • No UNI-N functions – all UNI-N functions handled b Network Edge Device• Supports Link OAM only (Across the UNI)• No Performance Monitoring• Managed

Service Provider Network Operator Network

E-NNI UNIUNI

CE

CE

Service NID(1) Transport NID

Network Edge Device

• All UNI-N is implemented here

IMPORTANT NOTEThis information is preliminary

and is subject to change

27

NID Types: Service NID

• Service / CE-VLAN awareness • UNI-N functions are divided with Network Edge Device• May support CoS, queues, congestion management• May enforce Bandwidth profiles• Supports Link OAM and Service OAM• No Tunnel Service awareness• Managed

Service Provider Network Operator Network

E-NNI UNIUNI

CE

CE

Service NID(2) Service NID

Network Edge Device

• UNI-N is divided

IMPORTANT NOTEThis information is preliminary

and is subject to change

28

Service Provider Network Operator Network

E-NNI UNIUNI

CE

CE

(2) Service NID(3) Tunnel NID

(4) Tunnel + Service NID(5) Hybrid NID

Service NID

Tunnel / Tunnel + Transport / Hybrid NIDs

Tunnel:• Tunnel Service / S-VLAN aware• Not service / CE-VLAN aware• No UNI-N functions – Similar to E-NNI function• May enforce Tunnel (Operator’s) Bandwidth profiles• Supports Link OAM and SOAM

Tunnel + Service NID• Combine Tunnel + Service in One box

Hybrid NID• Tunnel + Service + managed by both Operator and Service Provider

IMPORTANT NOTEThis information is preliminary

and is subject to change

29

MEF Global Interconnect Tools

February 2009

30

• MEF worked with Heavy Reading to develop database of Ethernet Service Providers worldwide– Identifies Carrier Ethernet services by city, country,

and service application– Four phase project to:

1. Cover MEF Service Providers with basic service and location information - Now

2. Add more service providers and allow real time updates via Service Provider back-end

3. Provide in-depth service information,

4. Non-MEF Service Providers (TBD)

Global Services Directory Summary

31

Global Services Directory Summary• Business Users

– Find Carrier Ethernet services anywhere in the world.

• Service Providers– Find a partner to build a global Carrier Ethernet service.

• Featuring– Free access to interactive map driven system– Latest info on available services globally, locally– http://www.metroethernetforum.org/gsd

32

Global Services Directory Summary• Business Users

– Find Carrier Ethernet services anywhere in the world.

• Service Providers– Find a partner to build a global Carrier Ethernet service.

• Featuring– Free access to interactive map driven system– Latest info on available services globally, locally– http://www.metroethernetforum.org/gsd

33

Wholesale Access Interconnection Group (WAIG)

Charter:

Define Standard template and procedure for ordering wholesale Ethernet services between service providers

Objectives:

To enable efficient communication of network capabilities between Service Providers and prospective wholesale partners

Scope Expanded:Global Interconnection Group (GIG?)

34

WAIG Template

1. Physical Customer Interfaces• For different services (UNI and NNI) provide physical

interface options (fiber, copper, rates etc.)2. Path Diversity and Protection

• For topology and protocol options (xSTP etc.) 3. Ethernet Frames

• Frame type and size options• Service multiplexing (EVCs etc.) options

4. Performance and Class of Service (CoS) Requirements• CoS options• Performance per CoS options

5. Service Technology Questions• Service / BW Profile options• Frame tagging options

35

6. Network Management• Maintenance Points for Fault, Performance OAM options• OAM Protocol options• Administrative options• Wholesale partner administrative and logistical options

7. Performance and SLA Reporting Capability• On and Off-line performance reporting options

8. Security• Threat detection and defense options

9. Connection Admission Control (CAC) Rules• CoS traffic handling

10. EVC and NNI Speeds• Throughput information

WAIG Template (cont.)

36

Global WAIG Status

• Template is available to MEF member companies

• Streamlined template draft published – 1Q09 MEF meeting (San Francisco)

• Early adaptors can start using Templates - Now

3737

Three Phases of Carrier Ethernet2004

Carrier Ethernet Defined

2001-3

First MEF specs

2005-7 2008-10

Global Interconnect

UbiquityRevenues>$30bn

Phases Timeline

Carrier Ethernet Milestones

Phase 1: Architecture and Definition

Carrier Ethernet defined

First specifications definedImplementation beginsDefinitions of Ethernet services

Phase 2: Implementation and CertificationMEF Certification ProgramLarge scale deployment beginsCarrier Ethernet extends from Metro

Phase 3: Global Interconnect Specification for Carrier Ethernet InterconnectSpecifications for automated management of UNIService OAM fault and performance specificationsClass of Service alignmentOperational tools: WAIG, GSD

2011-14

brings all interconnect initiatives into a single

market focus

38

Summary - Carrier Ethernet’s “Evolution”

2009, Carrier Ethernet We are here

LAN

WAN

GlobalOOF WAN

MAN

Finish E-NNI specFinish NID specRefine GS Directory – add SPsStart use of WAIG Templates

39

Thank You

Presentations are availableat

www.metroethernetforum.org