1

Agenda
Elements of a Global Network
UNI Type II ENNI
Class of Service Alignment

OAM Enables Global Interconnect

End-to-End OAM Architecture Service OAM Fault Management Service OAM Performance Management

Ubiquitous Footprint Drives Interconnect

Carrier B Carrier A

Expanding Service Areas and Acquiring New Customers National and Global Service Providers need Local Service Providers (Operators) for Local Access Local Operators need new revenues from wholesaling to Global Service Providers Multi-operator networks are more complex Challenge: maintain service consistency across the network Challenge: end-to-end fault detection and performance monitoring (a.k.a. OAM)
3

Carrier Ethernet Demarcation Points

UNI ENNI ENNI UNI

Access Network Provider

Subscriber

Transport Network Provider

Ethernet Service Provider

Subscriber

EVC

UNI - User-to-Network Interface Demarcation point between Service Provider and Subscriber Ethernet Service starting point and ending point ENNI - External Network-to-Network Interface Demarcation point between operators EVC - Ethernet Virtual Connection Ethernet service connecting two or more UNIs
4

User to Network Interface (UNI)

Defines an Ethernet service demarcation point between customer (subscriber) and service provider Uses a physical Ethernet Interface at operating speeds 10Mbs, 100Mbps, 1Gbps or 10Gbps Defines service personality service attributes, traffic classification, bandwidth profiles, tagging, etc.
CE NID

Carrier Ethernet Network

Service Provider responsibility

Customer responsibility

UNI

MEF UNI Attributes

UNI type 1 (MEF 13)
Defines service attributes Traffic classification & bandwidth profile(s)

UNI type 2 (MEF 20)

UNI Type 2.1
Mandatory Features Backward comp. to UNI Type 1 Service OAM Enhanced UNI attributes L2CP Handling Optional Features Link OAM Protection E-LMI

UNI Type 2.2

Mandatory Features Backward comp. to UNI Type 1 Service OAM Enhanced UNI attributes L2CP Handling Link OAM Protection E-LMI

For Global Interconnect, support for end-to-end OAM is mandatory

Provides fault detection and performance monitoring for subscriber, operator and service provider

External Network-to-Network Interface (ENNI)

Proprietary Implementation vs. Standardized Ethernet Interconnects
Proprietary interconnect ENNI

Operator A
Proprietary interconnect

Operator B
Proprietary interconnect

Operator A
ENNI

Operator B
ENNI

Operator C

Operator D
Proprietary interconnect

Operator C
ENNI

Operator D

Proprietary implementations
Limited in features, proprietary and/or ad-hoc Require extensive coordination between operators to match their service, operation and interface capabilities Very long turn-up time

MEF Standardized Interconnect

Provide wide range of well defined standardized services to enterprise customers Standardized interconnects (ENNI) streamline operators interconnect operations; reduces time-to-market and time-to-revenue Easily scalable to enable alignment between investment and revenue
7

MEF ENNI Attributes

UNI
Operator 1 network
Ethernet Virtual Connection

ENNI
Reference Point

Operator 2 network

UNI

Requirements
Physical Interface Service Attributes L2CP Handling Service Mapping Service Tunneling OAM Class of Service Protection

OAM
Link OAM IEEE 802.3ah Service OAM IEEE 802.1ag (for fault detection) ITU-T Y.1731 (for performance monitoring)

ENNI specification is in final stages of approval and ratification by MEF (Planned 2010H1)

CoS
CoS Alignment

Critical Area !

What is Class of Service ?

A specific performance level for a particular type of service traffic For example:
Video, Voice = high Data storage = medium File transfer = low

Service names and types vary

Example: Silver, Gold, Platinum Example: Economy, Premium, PremiumPlus

Class of Service Alignment [MEF 23]

Solving the problem of Class of Service spanning two or more Service Providers requires:

Common Class of Service lexicon between the service providers on either side of the standardized Ethernet interconnect Alignment of the respective Classes of Service at the ENNI

10

Scope & Applicability

The scope and applicability of the Class of Service Implementation Agreement (MEF 23) to both UNI and ENNI, to both Multipoint and Point-Point and to both single and multiple MENs is represented here:
Multipoint EVC UNI CE UNI UNI UNI CE Point-Point EVC UNI CE MEN 1 ENNI MEN 2 UNI CE UNI CE MEN UNI CE MEN 1 MEN 2 UNI CE Multipoint EVC

Point-Point EVC MEN UNI CE

UNI Carrier Ethernet CoS IA Application Point (recommended PCP/DSCP values, mandatory Performance Objectives)

ENNI Carrier Ethernet CoS IA Application Point (mandatory PCP Values if 802.1ad and mandatory Performance Objectives)

11

MEF 23 in a Nutshell
Carrier Ethernet CoS Implementation Agreement Phase 1 Specifies a 3 CoS Model and allows for subsets and extensions CoS IA PCP or DSCP values recommended for UNI CoS IA S-tag PCP values mandatory for ENNI PCP/DSCP mandatory values are subset of the total value Guidance on Bandwidth Profile constraints
Includes consideration for frame disposition (i.e., Color)

Performance Objectives for FD, IFDV/FDV and FLR positioned as placeholders (define in MEF Phase 2)
Quantification in future phase (will likely add MFD and FDR) May vary for Point to Point vs Multipoint EVC types Positions for future certification

12

Global Interconnect: ENNI and OAM Agenda

Elements of a Global Network UNI Type II ENNI
Class of Service Alignment

OAM Enables Global Interconnect End-to-End OAM Architecture Service OAM Fault Management Service OAM Performance Management

13

Driving Demand for Service OAM: Reliability

Reliability is Essential to Enterprise Customers

2008 Report from Heaving Reading:

What Makes an Ethernet Service Provider Attractive for Enterprise Customers?

14

Driving Demand for Service OAM: SLAs

What is holding service providers back from deploying Ethernet more aggressively? 16% 18% 66% Better alternative solutions Price Performance monitoring/SLAs inadequate

SLAs are an essential element of Carrier Ethernet Frame Relay, Private Line, ATM support SLAs Subscribers want SLAs and proof of compliance Management and reporting are a key element of the solution Global Interconnect present challenges for SLAs Need tools to determine performance and quickly isolate fault locations across multiple operators
15

Driving Demand for Service OAM: OPEX

OPEX CAPEX

Legacy Services

Best Effort Ethernet

Carrier Ethernet

Reducing Operating Costs is essential to Service Providers The cost of truck rolls range from $200 to $400 per event Service OAM provides the maintenance and troubleshooting tools equivalent to TDM services Service OAM enables the combination of Low CAPEX of Ethernet equipment Low OPEX equivalent to TDM equipment.
16

Ethernet OAM Jurisdictions

Customer Site UNI NID Operator 1 ENNI Operator 2 UNI NID Customer Site

Service OAM
ITU-T Y.1731 End-to-End Performance Monitoring
MEF NID/UNI

MEF NID/UNI

IEEE 802.1ag End-to-End Connectivity Fault Management

Link OAM
Link OAM

IEEE 802.3ah

Link OAM

17

Link OAM
IEEE 802.3ah - Ethernet in the First Mile (EFM) First Ethernet OAM standard completed (2004) Supports:
Remote loopback Remote failure indication (dying gasp, link fault and critical event) Link monitoring Loopback Control Discovery

Focused on point to point Ethernet link OAM

Does not propagate beyond a single link or hop Maintenance OAM, not service

18

Link OAM
Customer Premises UNI Operator 1 ENNI Operator 2 UNI Customer Premises

802.3ah

802.3ah 802.3ah

802.3ah

802.3ah

802.3ah

802.3ah

802.3ah

802.3ah

IEEE 802.3ah Per physical network link (point-to-point): Good for single links, but does not monitor across EVC Used for troubleshooting network links

19

End-to-End Service OAM

What is Service OAM?
Enables fault detection and performance monitoring of the Ethernet Service (EVC) from End-to-End Uses synthetic traffic Supports multiple layers of OAM and maintenance regions Supports multiple networks and operators

Includes:
IEEE 802.1ag provides Connectivity Fault Management ITU-T Y.1731 provides Performance Monitoring

20

Service OAM - Domains

Customer Premises UNI Operator 1 ENNI Operator 2 UNI Customer Premises

Customer MA Provider MA Operator MA Operator MA

A flat network is difficult to manage and define accountabilities Hierarchical Maintenance Domains define OAM Flows and OAM responsibilities
Maintenance Domain (MD) defines the boundary of responsibility of each stakeholder as a specific level within the network Maintenance Association (MA) defines the path of the service within each MD level
21

Service OAM Framework - Detail

Customer Premises UNI Operator 1 ENNI Operator 2 UNI Customer Premises

Customer MA Provider MA Operator MA Operator MA

Maintenance End Points (MEP) End Points that define the boundaries of the MA Maintenance Intermediate Points (MIP) Intermediate Points within MA

22

802.1ag Connectivity Fault Management

802.1ag CFM Defines the Framework for Service OAM Provides mechanisms to detect, verify, isolate and report end-to-end Ethernet connectivity faults
Connectivity Check Message fault detection during operation Loopback test Linktrace fault isolation

Scalable to provide connectivity checking and fault detection across multiple networks and multiple domains
Partitions the network into Domains to define responsibilities of different stakeholders. Supports up to 8 Maintenance Domains Connectivity Fault Management provided by Carrier Ethernet network elements and NIDs
23

Service OAM - Continuity Check

Customer Premises UNI Operator 1 ENNI Operator 2 UNI Customer Premises

Customer MA Provider MA
MEP 1 CCM CCM MEP 2

Operator MA

Operator MA

Continuity Check Message (CCM) OAMPDUs provide periodic monitoring function exchanged between MEPs Continuous, non-intrusive monitoring proactively tests circuit

24

Service OAM Link Trace

Customer Premises UNI Operator 1 ENNI Operator 2 UNI Customer Premises

Customer MA Provider MA
MEP 1

LTM LTR
Operator MA Operator MA

MEP 2

Link Trace Message (LTM) and Link Trace Response (LTR) An initiated command to trace intermediate points (MIP) from one end point (MEP) to another end point (MEP) Finds faults in defined MAs along an Ethernet Service
25

ITU-T Y.1731 Performance Monitoring

ITU-T Y.1731 Mechanisms that provide fault and performance monitoring for point-to-point Ethernet services Builds on 802.1ag functionality and adds:
Introduces performance measurements for SLA monitoring Delay Measurement (DM) Delay Variation Measurement (DVM) Loss Measurement (LM) Expands on fault notification and isolation Automatic Protection Switching (APS) G.8031 Ethernet Alarm Indication Signal function: Y.1731 ETH-AIS Ethernet Test Signal function: Y.1731 ETH-TEST

26

Service Performance Management

Key Metrics for Performance Monitoring
1. 2. 3. 4. Frame/Packet Delay Latency (e.g. UNI/UNI 30ms@99.9%@15min) Frame/Packet Delay Variation Jitter (e.g. 10ms@99.9%@15min) Frame/Packet Loss Ratio (e.g. CIR FL=1%@15min) Service Availability (e.g. 99.99%@30days)

ITU-T has defined measurement metrics for items 1-3

Packet-based measurements (granularity to Class of Service) ITU-T Y.1731 defines how to use 802.1ag to measure performance

MEF has defined measurement framework for items 1-4

Ethernet Frame-based measurements MEF 10.1 defines formulae for metrics calculation

The combination of IEEE 802.1ag, ITU-T Y.1731 802. ITU- Y.1731 and MEF 10.1 define Ethernet Service Performance 10.
27

Enabling Global Interconnect

E2E Service OAM: Fault-802.1ag Perform-Y.1731 UNI

Point-to-Point EVC

UNI Link OAM 802.3ah

Carrier B ENNI Carrier A

CoS Alignment

28

Summary
Implementation of Ethernet interconnects has begun and will rapidly accelerate in 2010 To enable the growth of Carrier Ethernet, Interconnect SPs need to: Deliver high reliability/up-time Commit-to and deliver SLAs Provide services efficiently with low OPEX MEF specifications, certification and operational tools provide a common and efficient framework for Carrier Ethernet interconnects UNI and ENNI specifications OAM Solutions
P2P Link OAM (802.3ah) Link Fault Monitoring E2E Service OAM (802.1ag) Service Fault Monitoring E2E Service OAM (Y.1731) Service Performance Monitoring

Enables the Global Interconnect

29

Thank You
For more information, visit:

www.metroethernetforum.org

30