Generalized EC Type 2 support EC Type 1&2 supporting bridges

1

Generalized EC Type 2 support

EC Type 1&2 supporting bridges

Maarten Vissers2011-07-21

v01

2

Introduction

http://www.ieee802.org/1/files/public/docs2011/new-vissers-pbb-pbbte-eotn-common-network-arch-0511-v01.pptx presented common network architectures for PBB, PBB-TE and EOTN networks to determine the Tagging method of EC Type 2 signals in an EOTN

The last two slides in the above presentation indentified implications of the Tagging methods within PB, PBB I and PBB-TE networks

These slides were not addressed in Santa Fe meeting due to time constraints

This new presentation addresses the implications of the choice of I+S-Tagging of EC Type 2 signals in PB, PBB I and PBB-TE networks

Furthermore, this presentation presents some initial feedback on the tagging choice and based on this feedback an alternative Tagging method

http://www.ieee802.org/1/files/public/docs2011/new-vissers-pbb-pbbte-eotn-common-network-arch-0511-v01.pptx

http://www.ieee802.org/1/files/public/docs2011/new-vissers-pbb-pbbte-eotn-common-network-arch-0511-v01.pptx

3

EC Type 2 support beyond PBB and EOTN

One may expect that EC Type 2 signal support will be required beyond the PBB II and EOTN networks in future; e.g. in EoSDH, EoMPLS(-TP)/VPLS, PBB-TE, PBB I and PB networks

EoSDH transports S-Tagged EC Type 1 signals via GFP-F over SDH VC-n connections; this is a similar environment as in EOTN and I+S-Tagged EC Type 2 signals would be applicable

PB, PBB-TE and PBB I transport S-Tagged EC Type 1 signals; should/could EC Type 2 signals be transported with I+S-Tags?

NOTE: EC Type 2 support in EoMPLS(-TP)/VPLS is TBA

4

EC frame tagging in PB, PBB, PBB-TE, EOTN

Network EC Type 1 frame tag EC Type 2 frame tagPB + PBB I(PEB, PB, IB-BEB, BCB only)

S-Tag

Note: in B-VLAN an I-Tag or S+I-Tag is used

I+S-Tag ?

PB + PBB II(PEB, PB, IB-BEB, TB-BEB, I-BEB, B-BEB, BCB)

S-Tag

Note: Inside PBB network the EC frames are carried inside a 2nd EC frame, which is I-Tagged

I-Tag

PB + PBB-TE(PEB, PB, IB-BEB, BCB)

S-Tag

Note: in ESP an I-Tag or S+I-Tag is used

I+S-Tag ?

EOTN(TEB,TB, OTN XC)

S-Tag I+S-Tag

Note: agreed in Santa Fe meeting

EC Type 1: EC carrying an EVC which is not-MAC-in-MAC encapsulatedEC Type 2: EC carrying an EVC which is MAC-in-MAC encapsulated

5EC T

ype

1&2

supp

ortin

g PE

B

S-Tagged LANs

S(B

)-VLA

N C

ompo

nent

S-VLANComponent

C-VLANComponent

EC Type 1 & 2 supporting Provider Edge Bridge (PEB2)

CEP

C-VLANComponent CEP PAP

PAP

PEP

PEPCNP

CNP

CNP

CNP

CNP

CNP

RCAP

PNP

PEP

PEP

Remote Customers S-Tagged Service interface

CNP

CBPI-Tagged service interface(I-Tagged)

I-Component

CNP

PIP

PIPCBP

CBP

CNP

C-VLANComponent

CNP PEP

PEPCEP

CNP

S-Tagged Service Interface(S-Tagged)CNP

C-Tagged Service Interface(un-, priority-C-. C-Tagged)

Port Based Service Interface(un- C-, priority-S- I-Tagged)

Port-based, S- & C-Tagged Service Interface(S-, S+C-Tagged)

C-Tagged Service Interface(un-, priority-C-, C-Tagged)

Port Based Service Interface(un-, C-, priority-S- I-Tagged)

S-Tagged Service Interface(S-Tagged)

Individual or bundled I-Tagged Services

Individual S-VLAN Service

Remote Customer Port-based Service Interface

Remote Customers C-Tagged service interface

T-Component CNP

Transparent Service Interface(un-, C-, S-, I-Tagged)

PIPCBP

S-VLANComponent


PAP

CNP

CNP

CNP

CNP

RCAP

PNP

PEP

PEP


Port-based , S- & C-Tagged Service Interface(S-, S+C-Tagged)



Tributary Port functonalityLine Port functionality

To/from PEB & PEB2 & PB &

PB2 & IBBEB & IBBEB2 & MEF

E-NNI

B-Com-ponentPNP

PNPPNP

CBPCBP

B-Com-ponentPNP

PNPPNP

CBPCBP

B-Com-ponentPNP

PNPPNP

CBPCBP

EC Type 1

EC Type 2

EC Type 1&2

PNP ports in PEB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs

EC Type 2 UNI-N tributary ports are added to PEB node

6

S(B

)-VLA

N C

ompo

nent

EC Type 1 & 2 supportingProvider Bridge (PB2)

B-Com-ponent

S-Tagged LANsPNP

Line Port functionality

PNPPNP

CBPCBP

B-Com-ponentPNP

PNPPNP

CBPCBP

B-Com-ponent

S-Tagged LANsPNP

Line Port functionality

PNP PNP

CBP CBP

B-Com-ponent PNP

PNP PNP

CBP CBP

B-Com-ponentPNP

PNPPNP

CBPCBP

B-Com-ponent PNP

PNP PNP

CBP CBP

EC Type 1&2 supporting PB

PNP ports in PB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs

NOTE: BCB node does not need to support EC Type 2

B-Com-ponent

PNPPNP

CBPCBPPNP

PNP2 = EC Type 1 & 2 supporting PNP

EC Type 1 signals

EC Type 2 signals

7

EC Type 1&2 supporting PBB-TE IB-BEB

CNP and PIP ports in PBB-TE IB-BEB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs

B-Tagged LANs

B-V

LAN

Com

pone

nt

EC Type 1 & 2 supporting PBB-TE IB Backbone Edge Bridge (IB-BEB2)

PNP

PNP

I-Component

B-Com-ponent

PNPPNP

CBPCBP

B-Com-ponent

PNPPNP

CBPCBP

B-Com-ponent CNP

PNP PNP

CBP CBP

B-Com-ponent CNP

PNP PNP

CBP CBP

PIP

PIPCBP

CBPS-Tagged LAN

S-Tagged LANPNP

PNP

I-Component

B-Com-ponent

PNPPNP

CBPCBP

B-Com-ponent

PNPPNP

CBPCBP

B-Com-ponent CNP

PNP PNP

CBP CBP

B-Com-ponent CNP

PNP PNP

CBP CBP

PIP

PIPCBP

CBPS-Tagged LAN

S-Tagged LAN

EC Type 1 & 2 signals must pass through I-Component- ESP-MAC is not the

same as B-MAC

8

EC Type 1&2 supporting PBB I IB-BEB

CNP ports in PBB I IB-BEB node are replaced by B-component complex to support EC Type 2

B-Tagged LANs

B-V

LAN

Com

pone

nt

EC Type 1 & 2 supporting PBB I IB Backbone Edge Bridge (IB-BEB2)

PNP

PNP

I-Component

B-Com-ponent CNP

CBP

PNP PNP

B-Com-ponent CNP

PNP PNPCBP CBP

PIP

PIPCBP

CBP

S-Tagged LAN

S-Tagged LANPNP

PNP

S-Tagged LAN

S-Tagged LAN

CBP

I-Component

B-Com-ponent CNP

CBP

PNP CBP

B-Com-ponent CNP

PNP PNPCBP

PIP

PIPCBP

CBP

CBP

CBP

EC Type 2 signals can bypass I-Component

9

Initial feedback

I+S-Tagged EC Type 2 OAM is not acceptable

EC Type 2 OAM should be S-Tagged like EC Type 1 OAM

Use of S-Tagged EC Type 2 OAM will allow reuse of existing EC Type 1 NNI ports in packet and packet-optical transport networks

Considerations I-Tagged LANs are not in the network/do not exist I-Tagged Ethernet OAM (BSI OAM) is not in the network/does not

exist PBB network deployments are single domain PBB networks with S-

Tagged LAN ingress/egress interfaces No need for EC Type 2 to interwork with PIP in IB-BEB

10

How to continue?

Ignore initial feedback and continue with I+S-Tagged EC-Type 2 OAM in standards?

Extend 802.1Q PEB, PB, PBB I IB-BEB and PBB-TE IB-BEB nodes with I+S-Tagged EC Type 2 MEP and MIP support

Let ITU-T SG15 add I+S-Tagged EC Type 2 specifications to its transport network recommendations

Build equipment with (non-standard) S-Tagged EC Type 2 OAM support

Revise our May 2011 decision? Consider that BEBs are used only within the network, not as

Network Termination (NT)/Network Interface Device (NID); i.e. BEBs have no UNI-N ports, BEBs only have NNI ports

Extend 802.1Q PEB node with EC Type 2 UNI-N ports and S-Tagged EC Type 2 OAM

11

Alternative solution

12

Alternative for the May 2011 Solution

Deploy the I-Component plus one or more CBPs as UNI-N tributary port functionality for EC Type 2

Add those UNI-N ports to PEB nodes

Use “B-VLAN MEP” functions on CBP to generate/terminate S-Tagged EC Type 2 OAM

Do not use BSI MEP and MIP functions

I-Tag is part of EVC encapsulation

No changes to other nodes necessary; i.e. a backwards compatible solution

13

Alternative EC frame tagging in PB, PBB, PBB-TE, EOTN

Network EC Type 1 tag EC Type 2 tagPB + PBB I(PEB, PB, IB-BEB, BCB only)

S-Tag


S-Tag


PB + PBB II(PEB, PB, IB-BEB, TB-BEB, I-BEB, B-BEB, BCB)

S-Tag

Note: Inside PBB network the EC frames are carried inside a 2nd EC

frame, which is I-Tagged

I-Tag S-Tag

Note: Inside PBB network the EC frames are carried inside a 2nd EC

frame, which is I-Tagged

PB + PBB-TE(PEB, PB, IB-BEB, BCB)

S-Tag


S-Tag


EOTN(TEB,TB, OTN XC)

S-Tag I+S-Tag

Note: agreed in Santa Fe meeting

EC Type 1: EC carrying an EVC which is not-MAC-in-MAC encapsulatedEC Type 2: EC carrying an EVC which is MAC-in-MAC encapsulated

14Alte

rnat

ive

EC T

ype

1&2

supp

. PEB

S-Tagged LANs

S-VL

AN

Com

pone

nt

S-VLANComponent

C-VLANComponent

EC Type 1 & 2 supporting Provider Edge Bridge

CEP


PAP

PEP

PEPCNP

CNP

CNP

CNP

CNP

CNP

RCAP

PNP

PEP

PEP


CNP

CBPI-Tagged service interface(I-Tagged)

I-Component

CNP

PIP

PIPCBP

CBP

CNP

C-VLANComponent

CNP PEP

PEPCEP

CNP

S-Tagged Service Interface(S-Tagged)CNP

C-Tagged Service Interface(un-, priority-C-. C-Tagged)

Port Based Service Interface(un- C-, priority-S- I-Tagged)

Port-based, S- & C-Tagged Service Interface(S-, S+C-Tagged)

C-Tagged Service Interface(un-, priority-C-, C-Tagged)

Port Based Service Interface(un-, C-, priority-S- I-Tagged)

S-Tagged Service Interface(S-Tagged)

Individual or bundled I-Tagged Services

Individual S-VLAN Service



T-Component CNP

Transparent Service Interface(un-, C-, S-, I-Tagged)

PIPCBP

S-VLANComponent


PAP

CNP

CNP

CNP

CNP

RCAP

PNP

PEP

PEP


Port-based , S- & C-Tagged Service Interface(S-, S+C-Tagged)



Tributary Port functonalityLine Port

To/from PEB & PEB2 & PB &

PB2 & IBBEB & IBBEB2 & MEF

E-NNI

PNP

PNP

PNP

EC Type 1

EC Type 2

EC Type 1&2

Regular PNP ports are capable to support EC Type 1 & 2

EC Type 2 UNI-N tributary ports are added to PEB node

15

EVC into EC Type 2 encapsulationS-VID/PCP/DEI preserved, Individual or Bundled S-VLAN service

EC Type 2 primitive parameters- destination_address- source_address - priority- drop_eligible- vlan_identifier- mac_service_data_unit =

C-DAC-SA

MSDU

TypeS-VID PCP DEI

TPID = 88-a8

S-Tagged EVC primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

TPID = 88-E7I-SIDPCP D

EI Res20 Res

1

I-SID = ??C-DAC-SA

MSDU

TypeS-VID PCP D

EI

TPID = 88-a8 S-VID,S-PCP,S-DEI

preserved

What value should the ISID have?

ISID is only visible in the EC Type 2 UNI-N tributary ports in PEB nodes

Options:1) Fixed ISID value2) ISID locked to

customer’s SVID3) Configurable ISID

16

EVC into EC Type 2 encapsulationS-VID/PCP/DEI not preserved, Individual S-VLAN service

EC Type 2 primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

C-DAC-SA

MSDU

TypeS-VID PCP D

EI

TPID = 88-a8

S-Tagged EVC primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =


EI Res20 Res

1

I-SID = ??C-DAC-SA

MSDU

Type

C-DAC-SA

MSDU

Type

untagged EVC primitive parameters-destination_address- source_address - priority- drop_eligible- vlan_identifier- mac_service_data_unit =

EC Type 2 OAM primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

OAM PDU

Type = 89-02



Options:1) Fixed ISID value2) Configurable ISID

17

EVC into EC Type 2 encapsulationTransparent service


C-DAC-SA

MSDU

TypeS-VID PCP D

EI

TPID = 88-a8

Transparent EVC primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =


EI Res20 Res

1

I-SID = ??C-DAC-SA

MSDU

TypeS-VID PCP D

EI

TPID = 88-a8

OAM PDU

Type = 89-02

C-DAC-SA

OAM PDU

Type = 89-02


EI Res20 Res

1

I-SID = ??C-DAC-SA

OAM PDU

Type = 89-02








18

EC Type 2 Tag

EC Type 2 primitive parameters- destination_address- source_address - priority- drop_eligible- vlan_identifier- mac_service_data_unit =

EC Type 2 OAM primitive parameters- destination_address- source_address - priority- drop_eligible- vlan_identifier- mac_service_data_unit =

OAM PDU

Type = 89-02

S-VID PCP DEI

TPID = 88-a8


EI Res20 Res

1

I-SID = ??

OAM PDU

Type = 89-02S-VID PCP D

EI

TPID = 88-a8

S-Tagged EC Type 2 primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

S-Tagged EC Type 2OAM primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =


EI Res20 Res

1

I-SID = ??C-DAC-SA

MSDU

Type

C-DAC-SA

MSDU

Type

19

I-SID value Option I

Backbone Service Instance Table (c6.11 CBP function)Backbone-

VIDBackbone-

SIDLocal-SID Default

Backbone Destination

A 4096 4096+A

B 4096 4096+B

C 4096 4096+C

D 4096 4096+D

E 4096 4096+E

Backbone Service Instance Table (c6.10 PIP function)VIP-ISS VIP-ISID Default


adminPointToPointMAC

enableConnectionIdentifier

A 4096+A

B 4096+B

C 4096+C

D 4096+D

E 4096+E

VIP-ISID and Local-SID parameters have local significance only; no need to coordinate I-SID value with other EC Type 2 UNI-N ports

Text in c6.11.1 supports this approach. Text in c6.11.2 seems not to support this approach; B-SIDs must be unique as B-VID is not used in row selection process. Correct?

20

I-SID value Option II

Backbone Service Instance Table (c6.11 CBP function)

Backbone-VID Backbone-SID

ABC a

DEF b

GHI c

JKL d

MNO e

Backbone Service Instance Table (c6.10 PIP function)VIP-ISS VIP-ISID Default


adminPointToPointMAC

enableConnectionIdentifier

A a

B b

C c

D d

E e

VIP-ISID/Backbone-SID values must be negotiated amongst the EC Type 2 UNI-N ports

High probability that the M (2≤M≤8192) UNI-N ports in EC Type 2 have at least one I-SID value available

21

Backup I+S-Tagged EC Type 2

(May 2011 solution)

EC Type1 and EC Type 2 examples including EC/ESP layer stack and

EC/ESP identifiersEC Type1 and EC Type 2 (un)tagged

primitive formats

22

1. PBB I and PBB-TE networkEVC(C-VLAN) via EC Type 1

PEB

2

BC

B

IB-B

EB2

CNP2

PNP2

IB-B

EB2

IB-B

EB2

BC

B

CNP2

CNP2

CNP2

CNP2

S

S

S

B(I) B(I)

B(I)

UNI

UNI

B(I)

BC

B

IB-B

EB2

IB-B

EB2

CNP2

CNP2

CNP2

CNP2

S

S

B(I)BC

B

IB-B

EB2

B(I) B(I)

CEP

CNP2

CNP2

mp2mp B-VLANor p2p TESI


mp2m

p B-VLA

Nor p2p TESI

• EVC = C-VLAN• EC Type 1• S-VID Translation at

PBBN domain boundaries (in CNP2)

• PBB I: few mp2mp B-VLANs in each domain; B-MAC per domain

• PBB-TE: full mesh of p2p TESIs in each domain; ESP-MAC per domain

• no MAC address collisions in PBBN domains (multiple single-domain PBBNs)

S-VID Translation locations

PEB

PNP

UNI

UNI CEP

S

PEB

2

PNP2

S

UNI

UNI

CNP

23

2. PBB I and PBB-TE networkEVC(S-VLAN) via EC Type 2

PEB

2

BC

B

IB-B

EB2

CNP2

PNP2

IB-B

EB2

IB-B

EB2

BC

B

CNP2

CNP2

CNP2

CNP2

S

S

S

B(I) B(I)

B(I)

UNI

UNI

B(I)

BC

B

IB-B

EB2

IB-B

EB2

CNP2

CNP2

CNP2

CNP2

S

S

B(I)BC

B

IB-B

EB2

B(I) B(I)

CEP

CNP2

CNP2



mp2m

p B-VLA

Nor p2p TESI

S-VID/I-SID Translation locations

PEB

PNP

UNI

UNI CEP

S

PEB

2

PNP2

S

UNI

UNI

CNP

• EVC = S-VLAN• EC Type 2, “Service B-

MAC” from UNI-N to UNI-N

• S-VID/I-SID Translation at PBBN domain boundaries (in CNP2)

• PBB I: few mp2mp B-VLANs in each domain; B-MAC per domain

• PBB-TE: full mesh of p2p TESIs in each domain; ESP-MAC per domain

• no MAC address collisions in PBBN domains (multiple single-domain PBBNs)

24

Layer stack PB + PBB-TE forEVC(C-VLAN) via EC Type 1

EVC

EC (Type 1 and Type 2)

ESP

EC EC

PHY PHY

EC

PHY

ESP

EC EC

PHY PHY

EC

PHY

ESP

EC EC

PHY PHY

PHY

EC

PHY

C-VID

EC(link)

I-SID I-SID I-SIDS-VID S-VID S-VID

S-VID S-VID S-VID S-VID

ESP-VIDESP-MAC

ESP-VIDESP-MAC

ESP-VIDESP-MAC

S-VID is optional; typically not present in a 1:1 case

C-MAC

25

Layer stack PB + PBB-TE forEVC(S-VLAN) via EC Type 2

EVC


ESP

EC EC

PHY PHY

EC

PHY

ESP

EC EC

PHY PHY

EC

PHY

ESP

EC EC

PHY PHY

EC

PHY

EC

PHY

I-SIDS-VID

I-SIDS-VID

I-SIDS-VID

I-SID I-SID I-SIDS-VIDI-SID

S-VIDI-SID

ESP-VIDESP-MAC

ESP-VIDESP-MAC

ESP-VIDESP-MAC

S-VIDI-SID

S-VIDI-SID

S-VIDService B-MAC

S-VID is optional; typically not present in a 1:1 caseC-VID

I-SID = S-VID+4096

26

Layer stack PB + PBB I forEVC(C-VLAN) via EC Type 1

EVC


EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC(link)

PHY

EC

PHY

C-VID

B-MAC B-MAC B-MACI-SIDS-VID

I-SIDS-VID

I-SIDS-VID

B-VID B-VID B-VID

S-VID S-VID


C-MAC

27

Layer stack PB + PBB I forEVC(S-VLAN) via EC Type 2

EVC


EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC

PHY

S-VID

B-VID B-VID B-VID

B-MAC B-MAC B-MACI-SIDS-VID

I-SIDS-VID

I-SIDS-VID

I-SID I-SID I-SIDS-VIDI-SID

S-VIDI-SID

S-VIDI-SID

S-VIDI-SID

Service B-MAC


C-VID

I-SID = S-VID+4096

28

3. PBB II networkEVC(C-VLAN) via EC Type 1

PEB

2

BC

B

IB-B

EB2

CNP2

PNP2

B-B

EB

B-B

EB

BC

B

CBP

CBP

CBP

CBP

S

I

I

B(I) B(I)

B(I)

UNI

UNI

B(I)

BC

B

B-B

EB

B-B

EB

CBP

CBP

CBP

CBP

I

I

B(I)BC

B

IB-B

EB2

B(I) B(I)

CEP

CNP2

CNP2

mp2mp B-VLAN

mp2mp B-VLAN

mp2m

p B-VLA

N• EVC = C-VLAN• EC Type 1• EC Type 1 over

EC(BSI) in PBBN• S-VID Translation at

PBBN network boundary (in CNP2)

• I-SID Translation at PBBN domain boundaries (in CBP)

• PBB II: few mp2mp B-VLANs in each domain; B-MAC per network

• potential MAC address collisions in PBBN domains


PEB

PNP

UNI

UNI CEP

S

PEB

2

PNP2

S

UNI

UNI

CNP

I-SID Translation locations

29

4. PBB II networkEVC(S-VLAN) via EC Type 2

PEB

2

BC

B

IB-B

EB2

CNP2

PNP2

B-B

EB

B-B

EB

BC

B

CBP

CBP

CBP

CBP

S

I

I

B(I) B(I)

B(I)

UNI

UNI

B(I)

BC

B

B-B

EB

B-B

EB

CBP

CBP

CBP

CBP

I

I

B(I)BC

B

IB-B

EB2

B(I) B(I)

CEP

CNP2

CNP2

mp2mp B-VLAN

mp2mp B-VLAN

mp2m

p B-VLA

N• EVC = S-VLAN• EC Type 2, “Service B-

MAC” from UNI-N to UNI-N

• EC Type 2 over EC(BSI) in PBBN

• S-VID Translation at PBBN network boundary (in CNP2)

• I-SID Translation at PBBN domain boundaries (in CBP)

• PBB II: few mp2mp B-VLANs in each domain; B-MAC per network

• potential MAC address collisions in PBBN domains


PEB

PNP

UNI

UNI CEP

S

PEB

2

PNP2

S

UNI

UNI

CNP

I-SID Translation locations

30

Layer stack PB + PBB II for EVC(C-VLAN) via EC Type 1

EVC


EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC

PHY

EC(BSI)

C-VID

B-MACS-VID

I-SIDI-SID I-SID

B-VID B-VID B-VID

S-VID S-VID

I-SID I-SID


C-MAC

31

Layer stack PB + PBB II for EVC(S-VLAN) via EC Type 2

EVC


EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC(BVLAN)

EC EC

PHY PHY

EC

PHY

EC

PHY

S-VID

I-SIDI-SID I-SID

B-VID B-VID B-VID

S-VID S-VIDI-SID I-SID

Service B-MAC

I-SID I-SID

C-VIDI-SID = S-VID+4096

32

EC Type 1 Tag


MSDU

Type <> 89-10

EC Type 2 OAM primitive parameters- destination_address (=B-DA)- source_address (=B-SA)- priority- drop_eligible- mac_service_data_unit =

OAM PDU

Type = 89-02

MSDU

S-VID PCP DEI

TPID = 88-a8

OAM PDU

Type = 89-02S-VID PCP D

EI

TPID = 88-a8

S-Tagged EC Type 1 primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

S-Tagged EC Type 1OAM primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

Type <> 89-10

33

EC Type 2 TagEC Type 2 primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

C-DAC-SA

MSDU

Type = 89-10

Type


OAM PDU

Type = 89-02

C-DAC-SA

MSDU

Type

S-VID PCP DEI

TPID = 88-a8


EI Res20 Res

1

I-SID = S-VID + 4096


EI Res21 Res

1

I-SID = S-VID + 4096C-DA = B-DAC-SA = B-SA

OAM PDU

Type = 89-02

S-VID PCP DEI

TPID = 88-a8

I+S-Tagged EC Type 2 primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

I+S-Tagged EC Type 2OAM primitive parameters-destination_address- source_address - priority- drop_eligible- mac_service_data_unit =


EI Res20 Res

1

I-SIDC-DAC-SA

MSDU

Type


EI Res20 Res

1

I-SIDC-DA = B-DAC-SA = B-SA

OAM PDU

Type = 89-02

I-Tagged EC Type 2primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

I-Tagged EC Type 2OAM primitive parameters- destination_address- source_address - priority- drop_eligible- mac_service_data_unit =

(destination address = f(B-DA,DBD)

34

Backup S-Tagged EC Type 2

(Proposed July 2011 solution)

EC Type1 and EC Type 2 examples including EC/ESP layer stack and

EC/ESP identifiersEC Type1 and EC Type 2 (un)tagged

primitive formats

35

To be added in v02

Documents

Generalized EC Type 2 support EC Type 1&2 supporting bridges