Optimizing Ethernet deployments

what buyers need to understand

what providers need to communicate

David Noguer
Optical Ethernet - Product Marketing
dnoguer@nortelnetworks.com

Topics for discussion

Architecture options

VPN/EVC (Ethernet Virtual Connection) separation

The role of the UNI

CoS/QoS
2

Metro Ethernet Architecture

Metro
Core

Net Mgmt
Svc Mgmt
Traffic Engineering

Native Ethernet
Over Sonet/SDH
Over DWDM
10Gbs+

Metro Access
and Aggregation

Metro
Edge
Metro
Routers/Switches

Ethernet switch
DSL, ATM, IP, TDM
Devices with Ethernet Uplinks

Metro
Core

Metro
Edge

Metro Access
and Aggregation

Scaleable
Reliable
Traffic Engineering

Distributed Switching
Centralized Routing
Manageable

Ubiquity
Availability
Density
3

Building Blocks for the Infrastructure

Customer
Prem Access

Metro Ethernet
Access/Aggregation

Metro Core
QinQ
Or
MinM

U-PE

WAN

MPLS

MPLS
Networks

PE
N-PE

Q
Qin

Building Blocks for the Infrastructure

Customer
Prem Access

Metro Ethernet
Access/Aggregation
QinQ
Or
MinM

50ms Ethernet
Access Ring
U-PE

Metro Core
QinQ
Or
MinM

WAN

MPLS

MPLS
Networks

N-PE

Q
Qin

nM
Mi

Solution depends upon network architecture, location and

density of enterprise customers
5

Building Blocks: Focus on Access

Ethernet Intelligence
Customer
Premises

CPE

CO/POP
Ethernet

NTU

Edge
Device

Backbone
Access
Aggregator

Some Ethernet capabilities - Ethernet Intelligence - can be

distributed between NTU and access aggregator/edge device
Traffic tagging and/or re-tagging including VLAN stacking
Queuing and bandwidth management
OAM, alarms and fault notification, diagnostics
Optional interworking
6

Ethernet in the First Mile

Architectures

Fiber
(GbE)
1Gbps

Copper
10Mbps

Point-to-Point
Copper Drop

Fiber
(GbE)
1Gbps

Fiber
100 Mbit/s

Point-to-Point
Fiber Drop

Fiber
(GbE)
1Gbps

Fiber
1Gbps

Fiber
Shared bw

Point-to-Multipoint
Ethernet PON

Point-to-Point
Fiber
8

Topics for discussion

Architecture options

VPN/EVC (Ethernet Virtual Connection) separation

The role of the UNI

CoS/QoS
9

EVC separation introduction

Two primary models:
- IEEE802.1ad QinQ (Stacked VLAN)
- IEEE802.1ah MinM (Backbone Provider Bridge)
MinM
User
data

Enterprise
Ethernet
header

QinQ
SP Ethernet
header

SP Ethernet header contains Src and

Dest MAC address used to transport
packet across service providers
network
Enables duplicate VLAN IDs in
Enterprise header

User
data

Enterprise
Ethernet
header

VLAN IDs

VLAN IDs sacked one before the other

Enables duplicate VLAN IDs in sub
fields
10

MinM principles
Ethernet
packet arrives
from enterprise
CPE node at SP
ingress switch

SP Ingress switch
adds SP Ethernet
header
Src and Dest MAC
addresses are
Ethernet UNI ports

Ethernet packet
switched across
the Service
Provider network
using details in SP
Ethernet header

SP Egress switch
removes SP
Ethernet header
And forwards
original Ethernet
packet to end
customer CPE

Ethernet
Switches

Site Y

Ethernet
UNI
(destination)

Site X

Ethernet
UNI
(source)

Service Provider
Metro Ethernet
network

User
data

Enterprise
Ethernet
header

SP Ethernet
header
11

Mac in Mac data plane frame format

Destination MAC address
If destination unknown, then
0xFFFFFF

SP MAC
DA
SP Header

Source MAC address

SP MAC
SA

Traffic Management
3

ET=0x810
0

Pbits

SP Q-tag1
SP Payload

C
F
I

12

Tunnel ID
(XXX)

ET=MiM
Service
Tag
Customer
Ethernet
Frame
SP FCS

Reserv
ed
Future
Growth.
Vendor
specific
fields.

P
T

24

Service ID
(YYY)

Payload Type
(data or control)

EVC ID
16M

12

ET: Ethertype
CTI: Canonical Field Identifier

QinQ principles

a1

Enterprise
CPE

Carrier
Access

Carrier
Core

Carrier
Core

Carrier
Access

a1 b1 Q

a1 b1

a1 b1 Q Q

a1 b1

a1 b1

Q Q Q

a1 b1

b1

Enterprise
CPE

Q Q Q

Q Q

13

Q in Q data frame format

Customer internal MAC
P-Ethertype
C-MAC DA
S TagSA
C-MAC

P-VLAN
CoS

C Tag

P CFI

C-Payload

P VLAN ID

SP CoS

SP EVC ID
4096

C-FCS
Customer original Tag

14

Topics for discussion

Architecture options
VPN/EVC (Ethernet Virtual Connection) separation
The role of the UNI

CoS/QoS

16

Ethernet UNI
Secure separation and privacy
Customer traffic is identified and marked
immediately upon entry

Service delineation
Demarcation point provides service multiplexing
onto a single physical link

Customer
Customer
Data
Data

EVC End Point

Sub 1

UNI

Scalability Subscriber Multiplexing

Sub 2

UNI

Provider
Edge
Device

IEEE 802.1ad stacked .1q tags

IEEE 802.1ah Mac in Mac encapsulation

Ethernet Link Level Security

802.1x Subscriber Authentication

Provider
ProviderTag
Tag

Customer
Customer
Data
Data

MAN
Network

Traffic prioritization / Bandwidth control

Enables differentiated services
17

UNI Service Attributes

Service Attribute

Service 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

Bundling

No 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.
18

Layer 2 Control Protocol

Discard, Peer or Pass to EVC per protocol

EVC Service Attributes

Service Attribute

Service Attribute Parameters

EVC Type

Point-to-Point or Multipoint-to-Multipoint

UNI List

A 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 Performance

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

19

Terminating Ethernet Services at

the Customer Premises
Customer Premises

CPE

CO/POP
Ethernet

Edge
Device

Backbone

NTU

End-to-end Control

Enables control and quality assurance up to the carrier demarcation

point at customer premises
Control of both access path and customer equipment connectivity
Traffic management (priority support, policing, shaping)
End-to-end QoS/SLA assurance

Optional legacy user interfaces (TDM, voice)

20

Topics for discussion

Architecture options

VPN/EVC (Ethernet Virtual Connection) separation

The role of the UNI

CoS/QoS
21

QoS Layers
QoS can be viewed through a layered approach
from the physical layer to applications

Different forms of QoS apply at each layer

QoS Monitoring and

Measurement

to create the end-to-end service

Application-signaled
QoS

SIP/SDP, H.323

IP QoS

IP Differentiated Services (DiffServ)

Network-signaled QoS

ATM PNNI, MPLS RSVP-TE or CR-LDP

Traffic Engineered Paths

ATM PVCs, MPLS E-LSPs and L-LSPs

Link Layer QoS

Ethernet 802.1p, VLANs, ATM, PPP, MPLS EXP,

DOCSIS, Frame Relay, 802.11e WLAN QoS

Physical Layer QoS

s, Virtual Circuits (VCs), Ports, Frequencies

No single technology provides end-to-end QoS

22

End-to-End (E2E) QoS Example

E2E QoS achieved through many different
technologies
DiffServ, MPLS, Ethernet 802.1p, RSVP-TE, DOCSIS
QoS Monitoring / Measurement
Traffic Engineered
Paths - MPLS

Link Layer QoS

DOCSIS
Cable
Modem

Cable
Access
Provider
CMTS

Link Layer QoS

Ethernet 802.1p
L3
Ethernet
Switch

OE MAN
Network-signaled
QoS RSVP-TE

OE
Switch

L2
Ethernet
Switch

Physical Layer QoS

Port Prioritization

IP QoS - DiffServ

Which QoS technologies should you use?

How to you offer an end-to-end service?

23

Ethernet SLAs
Many Enterprise customers will not move to
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 with

service performance assurances
24

Service Performance (QoS)

defined in MEF 5
Service Performance Parameters
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

25

Example CoS-based Metro Ethernet SLA

Service
Class
Premium

Silver

Bronze

Standard

Service Characteristics

E-Line Service
4 Classes of Service
CoS determined via 802.1p CoS ID
Common type of SLA used with
CoS-based IP VPNs

CoS ID

Bandwidth Profile per

EVC per CoS ID

Service
Performance

6, 7

CIR > 0
EIR = 0

Delay < 5ms

Jitter < 1ms
Loss < 0.001%

Bursty mission critical data

applications requiring low
loss and delay (e.g., Storage)

4, 5

CIR > 0
EIR UNI Speed

Delay < 5ms

Jitter = N/S
Loss < 0.01%

Bursty data applications

requiring bandwidth
assurances

3, 4

CIR > 0
EIR UNI Speed

Delay < 15ms

Jitter = N/S
Loss < 0.1%

CIR=0
EIR=UNI speed

Delay < 30ms

Jitter = N/S
26
Loss < 0.5%

Real-time IP telephony or IP
video applications

Best effort service

0, 1, 2

In conclusion
Many different architectures for Ethernet in the
Metro
VPN separation has to be carefully considered
and be based on requirements
UNI provides clear separation between
enterprise and service provider
CoS/QoS is a must for enterprise to take up a
Metro Ethernet service

27

Thank you
dnoguer@nortelnetworks.com