ethernet oam maintenance entities in itu-t q.3/13

1

Ethernet OAM Maintenance Entities in ITU-T Q.3/13

Dinesh Mohan Paul Bottorff

Nortel Networks

2

OAM Layering

3

Ethernet OAM Layering

CE U-PE U-PEN-PEN-PE CEB B P P P PDevice View

Ethernet Layer

Eth Access MPLS Core MPLS Access

Customer CustomerService Provider

• An example to highlight network/service involving Ethernet and other technologies

• The Ethernet Layer implies the visibility to Ethernet frames

4

OAM Domain – Service/Network

Eth Access MPLS Core MPLS Access

Customer CustomerService Provider

Customer Domain

Provider Domain

Operator Domain Operator Domain

Operator Domain

• Domains concept is necessary to contain OAM flows & bound OAM responsibilities

5

Maintenance Entity Points (MEP) & Maintenance Intermediate Points (MIP)

Customer Domain

Provider Domain

Operator Domain Operator Domain

Operator Domain

Eth Access MPLS Core MPLS Access

Customer CustomerService Provider

MPLS Domain MPLS Domain

Maintenance Entity PointMaintenance Intermediate Point

• Location of MEPs and MIPs is dependent on Business Models & Deployment Scenarios

Network OAM

Service OAM

PW/MPLS OAM

6

Service/Network OAM – How does it come together?

Ethernet link OAM

PW/MPLSOAM

EoSONET OAM

Other OAM

Network OAM

Service OAM

Transport Links

Network

Services

• OAM Interworking possible to utilize OAM across Layers• However, each layer must support OAM capabilities independently

7

Q.3/13Maintenance Entity Points (MEP)

& Maintenance Intermediate Points (MIP)

8

Networks using MEPs & MIPs

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

ETH orSRV

1 2 3 4 5 6 7 8 9

• MEPs and MIPs used to identify Maintenance Entities (MEs)• MEs identifies what need to be managed

Maintenance Entity PointMaintenance Intermediate Point

9

Dual Relay Model

as

Single Integrated Provider Device

10

MEP, MIP, TCP for Dual-Relay Model:Single Integrated Provider Device

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

1 2a 2b 3 4 5 6b 6a 7

• 2a and 6a allow for peering of L2CP + multiplexing of user flows• Additional MEs may need to be managed

11

Customer Bridge 1Example without ETH link ME

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

ShimLLCLLC LLC

MEP

Relay

12

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Provider Bridge 2aExample without ETH link ME

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

Shim

Relay

LLCLLC LLC

MIP

MEP

MIP

MEP

13

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Provider Bridge 2bExample without ETH link ME

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

Shim

Relay

LLCLLC LLC

MEP

MEP

MIPMIP

14

Dual Relay Model

with

Single Relay as Provider Device

15

MEP, MIP, TCP for Dual-Relay Model:Single Relay as Provider Device

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

1 2b 3 4 5 6b 7

• 2b and 6b do not allow for peering of L2CP + single service per customer link• Additional MEs may be needed at Customer side

16

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Customer Bridge 1Example without ETH link ME

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

ShimLLCLLC LLC

MEP

Relay

17

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Provider Bridge 2bExample without ETH link ME

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

Shim

Relay

LLCLLC LLC

MEP

MEP

MIPMIP

18

Dual Relay Model

with

Bundling for

Single Integrated Provider Device

19

C-Tag

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

1 2a 2b 3 4 5 6b 6a 7

11122122

11122122

1020S-Tag

Untagged

C-Tag

MEP, MIP, TCP for Dual-Relay Model:Bundling - Single Integrated Provider Device

20

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Customer Bridge 1Example without ETH link ME - TBD

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

ShimLLCLLC LLC

MEP

Relay

MEP MEP MEP

21

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Provider Bridge 2aExample without ETH link ME - TBD

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

Shim

Relay

LLCLLC LLC

MIP

MEP

MIP

MEP

MIP

MEP

MIP

MEP

22

802.1Q Tagging “Y”80

2.1Q

Tag

ging

“Y”

Provider Bridge 2bExample without ETH link ME - TBD

LLCHigher Layer Entities

LLC LLC

802.

1ag

Up

CM

Shi

m

802.

1ag

Dow

n C

M S

him

802.1ag Up C

M Shim

802.1ag Dow

n CM

Shim

Relay

LLCLLC LLC

MEP

MEP

MIP

MEP

MEP

MIP

23

Dual Relay Model

with

Bundling for

Single Relay as Provider Device

24

MEP, MIP, TCP for Dual-Relay Model:Bundling - Single Relay as Provider Device

C-Tag

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

1 2b 3 4 5 6b 7

11122122

1020S-Tag

Untagged

25

Dual Relay Model

with

All-to-One Bundling for

Single Relay as Provider Device

26

MEP, MIP, TCP for Dual-Relay Model:All-to-One Bundling

C-Tag

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

1 2b 3 4 5 6b 7

11122122

10S-Tag

Untagged