… what buyers need to understand … what providers need to communicate Ralph Santitoro Co-chair, MEF Technical Marketing Committee [email protected]

… what buyers need to understand … what providers need to communicate

Ralph SantitoroCo-chair, MEF Technical Marketing Committee

[email protected]

Metro Ethernet Services

Metro Ethernet Services Overview v1.22

Contents

• Ethernet as a Service• Ethernet Service Benefits• MEF Phase I Service Documents• Defining an Ethernet Service• Example E-Line and E-LAN Services• Ethernet SLAs• Ethernet Service Summary• References and Resources


Ethernet as a Service

• Ethernet’s origins in the Enterprise– Used as a LAN connectivity technology– Just plug it in and start using it

• Ethernet’s new usage as a Service– Requires “service attributes” like other MAN / WAN

services• Ethernet UNI, Ethernet “VC”, Service Performance, etc.

Same Ethernet technology just used in a new waySame Ethernet technology just used in a new way


Ethernet Service Benefits

• Ease of use– Widely available, well understood technology– Simplifies network operations (OAM&P)

• Cost Effectiveness– Widespread use of Ethernet interface– Purchase bandwidth only when needed

• Flexibility– Single UNI can connect to multiple services

• Internet, VPN, Extranet supplier, Storage Provider

– Bandwidth can be added in 1Mbps increments


Let’s look at TDM and other L2 Services

Inflexible Bandwidth Scalability• Increasing non-Ethernet service

bandwidth often requires:– New service (step function)

• T1T3, FRATM

– New hardware• new interface or equipment

– New service provisioning • different protocols / technologies

• Often resulting in:– Oversubscribing to meet growing

bandwidth needs

OC-48

OC-12

OC-3

T3

T1

1.5M 45M 155M 622M 2.4G

TDM hierarchy or L2 Service dictates bandwidth increments

and technology

Frame Relay

POS

ATM


Ethernet Service Benefits over TDM/other L2 Services

Flexible Bandwidth Scalability• Increasing Ethernet service

bandwidth:– Requires just bandwidth provisioning

– Provision only amount of BW needed

• Same protocol for LAN and MAN

• Lower OpEx & CapEx with Ethernet– 25-40% lower cost than

• TDM, Frame Relay, ATM interfaces1

– 10x lower cost• than high speed SONET interfaces1

– Easier and less costly to meet growing bandwidth needs

OC-48

OC-12

OC-3

T3

T1

1.5M 45M 155M 622M 2.4G

Ethernet provides flexible bandwidth increments using

same technology

Frame Relay

POS

ATM

1GbE

10/100MbE

1 Source: Network Strategy Partners, LLC

Ethernet


MEF Phase I Service Documents

• Phase I consists of 3 technical specifications– Ethernet Services Model (ESM - MEF 1.0 standard)

• Defines Ethernet service building blocks (service attributes)• Defines a framework describing how to build an Ethernet service

– does not define Ethernet services

– Ethernet Services Definitions (ESD)• Defines how to apply the ESM building blocks to create services• Defines Ethernet Line (E-Line) and Ethernet LAN (E-LAN)

service types and instances of them (EPL, EVPL, EIA, etc.)

– Ethernet Traffic Management (ETM)• Defines traffic management and service performance

requirements to create CoS-based SLAs


Relationship between MEF Phase I Service documents

MEF 1.0 - Ethernet Service Model (ESM)

(Ratified Sept. 2003)

Ethernet Service Definitions (ESD)

Ethernet Traffic Management (ETM)


Ethernet Services Model (ESM)

• Ratified by MEF Tech. Committee - Sept. 2003– into Technical Specification MEF 1.0

• Defines building blocks for creating services• Building blocks consist of Ethernet Service

Attributes and Parameters defined for:– Ethernet UNI (User Network Interface)– Ethernet Virtual Circuit (EVC)

MEF 1.0 defines the building blocks to create servicesMEF 1.0 defines the building blocks to create services


How the MEF defines an Ethernet Service• MEF 1.0 defines the Ethernet Service Definition

Framework • A service is defined via

– Service Type– Service Attributes– Service Attribute Parameters

Defined in Defined in ESDESD

Defined in ESM Defined in ESM (MEF 1.0) and (MEF 1.0) and

ETMETM Defined in ESM Defined in ESM (MEF 1.0) and (MEF 1.0) and

ETMETM


Ethernet Service – Basic Model defined in MEF 1.0

• Customer Equipment (CE) attaches to UNI

• CE can be – router– IEEE 802.1Q bridge (switch)

• UNI (User Network Interface)– Standard IEEE 802.3 Ethernet PHY and

MAC– 10Mbps, 100Mbps, 1Gbps or 10Gbps

• Metro Ethernet Network (MEN)– May use different transport and service

delivery technologies• SONET/SDH, WDM, RPR, MAC-in-MAC,

Q-in-Q, MPLS

CE

CE

CE

UNI

Metro Metro Ethernet Ethernet Network Network (MEN)(MEN)

UNI


Ethernet Service Type defined in ESD

• Ethernet Service Type– Generic Ethernet connectivity service construct

• Each Ethernet Service Type– has a set of Ethernet Service Attributes

• MEF has defined 2 Ethernet Service Types– Ethernet Line (E-Line) Service

• Provides Point-to-Point connectivity– Ethernet LAN (E-LAN) Service

• Provides Multipoint-to-Multipoint (Any-to-Any) connectivity

Service Types are generic Service Types are generic constructs used to create servicesconstructs used to create services


UNIMEN

UNI

Point-to-Point EVC

Ethernet Virtual Connection (EVC) defined in MEF 1.0

• An EVC is “an instance of an association of 2 or more UNIs”

• EVCs help visualize the Ethernet connections– Like Frame Relay and ATM PVCs

• MEF has defined 2 EVC types– Point-to-Point– Multipoint-to-Multipoint

EVCs help conceptualize the service connectivityEVCs help conceptualize the service connectivity

MEN

Multipoint-to-Multipoint EVC


Ethernet Service Attributes defined in MEF 1.0, ESD and ETM

• Service Attributes define – the capabilities of the Ethernet Service Type

• Service Attributes defined for UNI and EVC:– Physical Interface– Bandwidth Profiles– Service Performance – Service Frame Delivery– Service Multiplexing– Etc….

Service Attributes define the service characteristicsService Attributes define the service characteristics

UNI and EVC Service Attribute Details

Service Attributes defined in MEF 1.0 Technical Specification


EVC Service AttributesService AttributeService Attribute Service Attribute ParametersService Attribute Parameters

EVC Type Point-to-Point or Multipoint-to-Multipoint

UNI ListA list of UNIs (identified via the UNI Identifier service attribute) used with the EVC

CE-VLAN ID Preservation

Yes or No. Specifies whether customer VLAN ID is preserved or not.

CE-VLAN CoS Preservation

Yes or No. Specifies whether customer VLAN CoS (802.1p) is preserved or not.

Unicast Service Frame Delivery

Specifies whether unicast frames are Discarded, Delivered Unconditionally or Delivered Conditionally

Multicast Service Frame Delivery

Specifies whether multicast frames are Discarded, Delivered Unconditionally or Delivered Conditionally

Broadcast Service Frame Delivery

Specifies whether broadcast frames are Discarded, Delivered Unconditionally or Delivered Conditionally

Layer 2 Control Protocol Processing

Discard or Tunnel per protocol

Service PerformanceSpecifies the Frame Delay, Frame Jitter and Frame Loss per EVC or frames within an EVC identified via their CE-VLAN CoS (802.1p) value


UNI Service AttributesService AttributeService Attribute Service Attribute ParametersService Attribute Parameters

UNI Identifier A string used to identity of a UNI, e.g., NYCBldg12Rm102Slot22Port3

Physical Medium Standard Ethernet PHY

Speed 10 Mbps, 100 Mbps, 1 Gbps or 10 Gbps

Mode Full Duplex or Auto negotiation

MAC Layer IEEE 802.3-2002

Service Multiplexing Yes or No. Defines whether multiple services can be on the UNI

UNI EVC ID A string used identify an EVC, e.g., NYCBldg1Rm102Slot22Port3EVC3

CE-VLAN ID / EVC Map Mapping table of customer VLAN IDs to EVC

Max. Number of EVCs The maximum number of EVCs allowed per UNI

BundlingNo or Yes. Specifies that one or more customer VLAN IDs are mapped to an EVC at the UNI

All to One Bundling No or Yes (all customer VLAN IDs are mapped to an EVC at the UNI).

Ingress Bandwidth Profile Per Ingress UNI

None or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames across the UNI.

Ingress Bandwidth Profile Per EVC

None or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames over particular EVC.

Ingress Bandwidth Profile Per CoS ID

None or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames marked with a particular CoS ID over an EVC.

Layer 2 Control Protocol Processing

Discard, Peer or Pass to EVC per protocol


E-Line and E-LAN Service Types defined in ESD

• E-Line Service used to create– Private Line Services– Ethernet Internet Access– Point-to-Point VPNs

• E-LAN Service used to create– Multipoint VPNs– Transparent LAN Service

CE

CE

Point-to-Point EVC

MENUNI

UNI

E-Line Service type

CE

CE

CE

MEN

CE

Multipoint-to-Multipoint EVC

UNI

UNI

UNI

UNI

E-LAN Service type


Example Service using E-Line Service Type

• Ethernet Virtual Private Line– Supports Service Multiplexed UNI– Point-to-Point VPN for site interconnectivity

CECE

MEN

Ethernet UNI

Ethernet UNIService

Multiplexed Ethernet

UNI

Point-to-Point EVCs

CE FR CPE

FR CPE

MEN

FR UNI

FR UNI

FR UNI

Point-to-Point FR PVCs

Ethernet Virtual Private Line using E-Line Service type

Frame Relay Analogy to E-Line Service

FR CPE


Example Service using E-Line Service Type

• Ethernet Private Line– Dedicated UNIs for Point-to-Point connections

MEN

Ethernet UNI

Ethernet UNI

Ethernet UNI

Point-to-Point EVCs (dedicated BW)

CE

Ethernet Private Line using E-Line Service type

Private Line Analogy to E-Line Service

Internet

ISPPOP

Storage SP

Ethernet UNI

MEN

OC-3

OC-3

DS1

Dedicated TDM circuits

CE

Internet

ISPPOP

Storage SP

DS3CE

CE

CE

CE


Example Service using E-LAN Service Type

• Transparent LAN Service (TLS) provides– Intra-company Connectivity

– Full transparency of control protocols (BPDUs)

• New VLANs added– without coordination with

provider

Multipoint-to-Multipoint EVCUNI 1

UNI 3

UNI 4

UNI 2

MENVLANs

Engineering

VLANsSales

Customer ServiceEngineering

VLANsSales

VLANsSales

Customer Service

TLS makes the MEN TLS makes the MEN look like a LANlook like a LAN

Transparent LAN Service


Ethernet SLAs• Many Enterprise customers will not use

Metro Ethernet services unless: – There are SLAs with performance assurances– There is availability of service to all critical locations

• Such enterprises will build private networks• Critical SLA Service Attributes

– Bandwidth Profile– Service Performance

Enterprise customers require CoS-based SLAs Enterprise customers require CoS-based SLAs with service performance assuranceswith service performance assurances


Bandwidth Profiles defined in ETM

• MEF has defined three bandwidth profiles

– Ingress Bandwidth Profile Per Ingress UNI

– Ingress Bandwidth Profile Per EVC

– Ingress Bandwidth Profile Per CoS ID

• 4 parameters <CIR, CBS, EIR, EBS>

– CIR/CBS determines frame delivery per service level objectives

– EIR/EBS determines amount of excess frame delivery allowed


Three Types of Bandwidth Profiles defined in ETM

UNI

EVC 1

EVC 2

EVC 3

Ingress Bandwidth Profile Per Ingress UNI UNI

EVC 1

EVC 2

EVC 3

Ingress Bandwidth Profile Per EVC1



UNI EVC 1

CE-VLAN CoS 6 Ingress Bandwidth Profile Per CoS ID 6

CE-VLAN CoS 4

CE-VLAN CoS 2

Ingress Bandwidth Profile Per CoS ID 4Ingress Bandwidth Profile Per CoS ID 2

EVC 2


Service Performance (QoS) defined in ETM

• Service Performance Parameters– Availability– Frame Delay– Frame Jitter– Frame Loss

• Service performance level to delivery determined via: – Per CoS ID, e.g., 802.1p user priority per EVC– Per UNI (port), i.e., 1 CoS for all EVCs at UNI


Example CoS-based Metro Ethernet SLA• E-Line Service• 4 Classes of Service• CoS determined via 802.1p CoS ID• Common type of SLA used with

CoS-based IP VPNs

Service Service ClassClass Service CharacteristicsService Characteristics CoS IDCoS ID Bandwidth Profile Bandwidth Profile

per EVC per CoS IDper EVC per CoS IDService Service

PerformancePerformance

Premium Real-time IP telephony or IP video applications 6, 7 CIR > 0

EIR = 0

Delay < 5msJitter < 1ms

Loss < 0.01%

SilverBursty mission critical data applications requiring low loss and delay (e.g., Storage)

4, 5 CIR > 0EIR ≤ UNI Speed

Delay < 5msJitter = N/S

Loss < 0.01%

BronzeBursty data applications requiring bandwidth assurances

3, 4 CIR > 0EIR ≤ UNI Speed


Loss < 0.1%

Standard Best effort service 0, 1, 2 CIR=0 EIR=UNI speed


Loss < 0.5%


E-Line and E-LANE-Line and E-LAN(Virtual and Private)(Virtual and Private)

Enabled Enabled Service over Service over

EthernetEthernetStorageStorage Video on Video on

DemandDemandInternet Internet AccessAccess

Service Service Delivery Delivery

TechnologyTechnologyEthernet Ethernet

over Fiberover Fiber

Ethernet Ethernet over over

SONET/SDHSONET/SDHEthernet Ethernet over RPRover RPR

Ethernet Ethernet over MPLSover MPLS

Ethernet Ethernet over WDMover WDM

Ethernet Ethernet Connectivity Connectivity

ServiceService

IP VPNIP VPN IP IP TelephonyTelephony

Summary of Metro Ethernet Services


Summary• Ethernet Services

– Same Ethernet… just used in new way

• E-Line and E-LAN Service types create– broad range of point-to-point and multipoint services

• Ethernet Services Framework– Defines service attributes that define the service

characteristics

• Ethernet Services need CoS-based SLAs– to increase Enterprise usage for mission critical apps


References and Resources• Metro Ethernet Services – A Technical Overview

– http://www.metroethernetforum.org/metro-ethernet-services.pdf

• Bandwidth Profiles for Ethernet Services– http://www.metroethernetforum.org/PDFs/WhitePapers/Bandwidth-Profiles-for-

Ethernet-Services.pdf

• MEF 1.0 “Ethernet Service Model, Phase 1”– http://www.metroethernetforum.org/PDFs/Standards/MEF-1.0.doc

• Metro Ethernet Services for Enterprises– http://www.metroethernetforum.org/businesscase_wp_092702f.pdf

• Business Case for Enterprise Metro Ethernet– http://www.metroethernetforum.org/presentations/Supercomm2003-Metro-

Ethernet-Business-Case21.ppt

• Metro Ethernet Networks - A Technical Overview– http://www.metroethernetforum.org/PDFs/WhitePapers/

meftechoverviewwhitepaper102903.pdf