Ethernet OAM study in ITU-T SG13, Q.3/13 March 17, 2004 ...grouper.ieee.org/groups/802/1/files/public/docs2004/Mar04-liaison-IT… · 2 Current status • Last ITU-T SG13 meeting:

1

Ethernet OAM study in ITU-T SG13, Q.3/13

March 17, 2004Hiroshi Ohta

ITU-T SG13, Q.3/13 rapporteur

2

Current status

• Last ITU-T SG13 meeting: Feb. 3-12, 2004• Ethernet OAM requirements: Y.1730

– Approved in Jan. 2004– Aligned with Ethernet architecture study in SG15 (G.8010/G.8011)

• Ethernet OAM mechanisms: Y.17ethoam– Under development– Discussed by people from IEEE 802.1 and MEF also– Progressed the area of maintenance entity and modeling– Worked on dual-bridge model– Clarified the relationships between IEEE 802.1 bridge model

(baggy pants diagram) and ITU-T model (G.805/G.809 model)– Introduced a section on performance monitoring– Applicability where lower layer is not Ethernet phy (e.g., MPLS)– Need feedback from IEEE 802.1 and to be aligned with work here.

3

Maintenance entity (ME)

• OAM target includes multipoint-to-multipoint connectivities• ME is defined for point-to-point connectivities• A multipoint connectivity is handled using a group of MEs.

ETHLink

ETHLink

ETHLink

ETHLink

Service Provider Y

Network Operator BNetwork Operator AUser X User X

UNI NNI UNI

UNI

ETHLink

UNI

ETH

ETH

ETH-CC

ETH-CC

ETH-CC

1

2

3

4

1 2

1 2

1

2

3

4

1 2

1 2

1

2

3 1 2 1 2

3

3

112

2

3

1

2

1

2

1

3

32

3

1

1

12

4

2

4

3

243

3

1

1

12

2

2

3

3 4

4

4

1

21

2

1

21

2

4

Multi-level Ethernet maintenance entities

ETH_TFPETH_FP ETH_FP

ETHFPPLink ETH_FP ETH_FP

ETHFPPLink

Service ProviderNetwork Operator BNetwork Operator ACE

UNI NNI

ETH_FPETH_TFPETH_FP

ETHFPPLink

CE

UNI

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

1 2 3 4 5 6 7 8 9

ETH

ETH orSRV



ETHFPPLink


UNI NNI

ETH_FPETH_TFPETH_FP

ETHFPPLink

CE

UNI

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

1 2 3 4 5 6 7 8 9



ETHFPPLink


UNI NNI

ETH_FPETH_TFPETH_FP

ETHFPPLink

CE

UNI

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges



ETHFPPLink


UNI NNI

ETH_FPETH_TFPETH_FP

ETHFPPLink

CE

UNI



ETHFPPLink


UNI NNI

ETH_FPETH_TFPETH_FP

ETHFPPLink

CE

UNI

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

1 2 3 4 5 6 7 8 9

ETH

ETH orSRV

Provides OAM capabilities for network operators (link and edge-to-edge), service providers and users

5

MEP and MIP models using G.805/G.809

ETHS

CCRDI

CCRDIAIS

FDI

MEP symbol

ETH_FP

ETH_FP

ETHD

LBTR

LBTR

ETH_FP

MIPsymbol

ETHD

LBTR

LBTR

ETH_FP

ETHD

LBTR

LBTR

ETH_FP

ETH_FP

MEP: Maintenance End Point

MIP: Maintenance Intermediate model

6

OAM (Connectivity Monitering) shim in the baggy pants model

LLC

Higher Layer Entities

802.1agUp CMShim

Relay

802.3

LLC LLCLLC

802.1agDownCMShim

MAC Dependent Functions

802.1Q Tagging “Y” Selected CM

frames

All otherframes

LLC

Higher Layer Entities

802.1agUp CMShim

RelayRelay

802.3

LLC LLCLLC

802.1agDownCMShim

MAC Dependent Functions

802.1Q Tagging “Y” Selected CM

frames

All otherframes

7

Baggy pants model and G.805/G.809 notation

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

Shim

LLCLLC LLC

D

D

D

S

D

S

MIP

MEP

MEP

D

D

D

S

D

S

D

SMEP

MIP

MEP

MEP

RelayRelay

S

DMEP

D

SMEP

D

SMEP

Some MEPs or MIPs may not be activated depending on the location of the bridge.

8

Dual-relay model with service bundling

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

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

11122122

11122122

1020

C-Tag

S-Tag

Untagged

C-Tag

CustomerEquipment

CustomerEquipment

Operator ABridges

Operator BBridges

ETH

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

11122122

11122122

1020

C-Tag

S-Tag

Untagged

C-Tag

2a, 6a: peer customer L2CP protocols, multiplex user flow2b, 6b: accommodate multiplexed user flow into a VLAN

9

Application example to Ethernet over MPLS

Eth Access

MPLS CoreMPLS Access

Customer CustomerService Provider

Customer Domain OAM

Provider Domain OAM

Operator Domain OAM Operator Domain OAM

Operator Domain OAM

bridge/bridge equivalent … OAM MEP/MIP

10

Looking into more details …

Customer Domain

Provider Domain

Operator Domain Operator Domain

Operator Domain

Eth Access MPLS Core MPLS Access

Customer CustomerService Provider

MPLS Domain MPLS Domain

Maintenance PointIntermediate Point

Network OAM

Service OAM

PW/MPLS OAM

11

Other topics

• Y.17ethps: Ethernet protection switching– Started developing a draft Recommendation– Requirements to fast protection switching was

included– Mechanisms which should be used for fast

protection is for further study (e.g., link aggregation or new one)

• Y.ethperf: Ethernet performance– Studied within Q.6/13 jointly with Q.3/13

12

Summary and Future ITU-T meetings

• SG13, Q.3/13 is working on Ethernet OAM• Would like to have feedbacks from IEEE

802.1• Need alignment and cooperation with IEEE

802.1 and MEF• Future ITU-T meetings

– Interim: June 7-11 in Geneva– Additional interim: September ?– SG13 plenary: Nov. 30 – Dec. 10 in Geneva

Documents

Ethernet OAM study in ITU-T SG13, Q.3/13 March 17, 2004 ...grouper.ieee.org/groups/802/1/files/public/docs2004/Mar04-liaison-IT… · 2 Current status • Last ITU-T SG13 meeting: