1

Common network architectures for PBB, PBB-TE and EOTN networks

Maarten Vissers2011-05-11

2

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

PE

BI-

BE

B

BC

B

(I)B

-BE

B

CBP

CNP

PIP

PNP

(I)B

-BE

B

(I)B

-BE

B

BC

B

CBP

CNP

CBP

CNP

I

S

I

S

B(I) B(I)

B(I)

UNI

UNI

UNI

B(I)

BC

B

(I)B

-BE

B

(I)B

-BE

B

CBP

CNP

CBP

CNP

I

S

B(I)BC

B

IB-B

EB

B(I) B(I)

UNI

UNI

UNI

CEP

CEP

CNP

CNP

IB-B

EB

UNI

PNP S

mp2mp B-VLANor p2p TESI

mp2mp B-VLANor p2p TESI

mp

2mp

B-V

LA

No

r p2p

TE

SI• EVC = C-VLAN

• EC = S-VLAN• S-VID Translation at PBBN domain

boundaries (in CNPs)• mp2mp B-VLANs or p2p TESIs in

each domain• no MAC address collisions in

PBBN domains (multiple single-domain PBBNs)

S-VID Translation locations

3

2. PBB networkEVC(S-VLAN) via EC(BSI)

PE

BI-

BE

B

BC

B

(I)B

-BE

B

CBP

CNP

PIP

PNP

(I)B

-BE

B

(I)B

-BE

B

BC

B

CBP

CNP

CBP

CNP

I

S

I

S

B(I) B(I) B(I)

UNI

UNI

UNI

B(I)

BC

B

(I)B

-BE

B

(I)B

-BE

B

CBP

CNP

CBP

CNP

I

S

B(I)BC

B

IB-B

EB

B(I) B(I)

UNI

UNI

UNI

CEP

CEP

CNP

CNP

IB-B

EB

UNI

PNP S

• EVC = S-VLAN• EC = BSI• I-SID Translation at PBBN domain

boundaries (in CBPs)• mp2mp B-VLANs in each domain• potential MAC address collisions

in PBBN domains (multi-domain PBBN)

mp2mp B-VLAN

mp2mp B-VLAN

mp

2mp

B-V

LA

N

I-SID Translation locations

4

3. PBB networkEVC(C-VLAN) via EC1(S-VLAN) over EC2(BSI)

PE

BI-

BE

B

BC

B

(I)B

-BE

B

CBP

CNP

PIP

PNP

(I)B

-BE

B

(I)B

-BE

B

BC

B

CBP

CNP

CBP

CNP

I

S

I

S

B(I) B(I) B(I)

UNI

UNI

UNI

B(I)

BC

B

(I)B

-BE

B

(I)B

-BE

B

CBP

CNP

CBP

CNP

I

S

B(I)BC

B

IB-B

EB

B(I) B(I)

UNI

UNI

UNI

CEP

CEP

CNP

CNP

IB-B

EB

UNI

PNP S

• EVC = C-VLAN• EC1 = S-VLAN, EC2 = BSI• S-VID Translation at PBBN

network boundary (in CNP)• I-SID Translation at PBBN domain

boundaries (in CBPs)• mp2mp B-VLANs in each domain• potential MAC address collisions

in PBBN domains (multi-domain)

B-VLAN

B-VLAN

B-V

LA

N

I-SID Translation locations

S-VID Translation location

5

PE

BI-

BE

B

OX

C

T(E

)B

???

PNP

PIP

PNP

TB

OX

C

I

S

S S S

UNI

UNI

UNI

S

OX

CTB

SOX

CTE

B

S S

UNI

UNI

UNI

CEP

CEP

CNP

CNP

IB-B

EB

UNI

PNP S

4. EOTN networkEVC(C-VLAN) via EC(S-VLAN)

• EVC = C-VLAN• EC = S-VLAN• S-VID Translation at EOTN

network boundary (in ONP and PNP)

• p2p ODUk connections in each domain

• no MAC address collisions (no PBBN domains)

ONP ONP

ONP ONP

p2p ODUk

p2p ODUk

p2p

OD

Uk

S-VID Translation locations

6

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

Network EC type 1 frame tag EC type 2 frame tag

PB + PBB I(PEB, PB, IB-BEB, BCB only)

S-Tag

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

To be defined

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

To be defined

EOTN(TEB,TB, OTN XC)

S-Tag To be defined

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

7

EC awareness in PB, PBB, PBB-TE, EOTN

Network EVC-to-EC mapping

EC MEP/MIP functions

EC AIS/LCK insertion

EC-to-server mapping

PB + PBB I(PEB, PB, IB-BEB, BCB only)

PEPCNP

CNPPIPPNP

CNPPIPPNP

CNPPIPPNP

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

PEPCNPPIPCBP

CNPPIPCBPPNP

CNPPIPCBPPNP

CNPPIPCBPPNP

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

CEPCNP

CNPPIPPNP

CNPPIPPNP

CNPPIPPNP

EOTN(TEB,TB, OTN XC)

CEPCNP

CNPPNPONP

PNPONP

PNPONP

8

Analysis of EC Type 2 Tagging options

For deployment in PB+PBB I, PB+PBB-TE and EOTN

9

Untagged EC Type 2 frame format

Untagged EC Type 2 frames are EVC frames with additional MAC Header including TYPE (89-10), B-SA, B-DA fields

Format is present at input/output ports of EC MEP and MIP functions

Untagged EC Type 2 OAM frames are OAM PDUs with additional MAC Header including TYPE (89-02), B-SA, B-DA

MSDU

Type

EVC Frame

C-DA

C-SA

Untagged EC Type 2 Frame(= untagged BSI Frame)

B-DA

B-SA

C-DA

C-SA

MSDU

Type = 89-10

Type

Untagged EC Type 2 OAM Frame

B-DA

B-SA

OAM PDU

Type = 89-02

10

Tagged EC Type 2 frame format alternatives

There are three EC Type 2 frame tagging alternatives1. I-Tagging2. S-Tagging3. I+S-Tagging

TPID = 88-E7

I-SIDPCP DE

I Res20 Res

1

B-DA

I-SID

B-SA

C-DA

C-SA

MSDU

Type

I-Tagged EC Type 2 Frame

B-DA

B-SA

C-DA

C-SA

MSDU

Type

S-Tagged EC Type 2 Frame

Type = 89-10

S-VID PCP DE

I

TPID = 88-a8

B-DA

B-SA

C-DA

C-SA

MSDU

Type

I+S-Tagged EC Type 2 Frame

S-VID PCP DE

I

TPID = 88-a8

TPID = 88-E7

I-SIDPCP DE

I

Res20 Res

1

I-SID = S-VID + 4096

TPID = 88-E7

I-SIDPCP DE

I

Res20 Res

1

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

I-SID = f(ETH_FP)

B-SA

C-DA = B-DA

C-SA = B-SA

OAM PDU

Type = 89-02

I-Tagged EC Type 2 OAM Frame

B-DA

B-SA

OAM PDU

Type = 89-02

S-Tagged EC Type 2 OAM Frame

S-VID PCP DE

I

TPID = 88-a8

TPID = 88-E7

I-SIDPCP DE

I

Res20 Res

1

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

I-SID = S-VID + 4096

C-DA = B-DA

C-SA = B-SA

B-SA

OAM PDU

Type = 89-02

I+S-Tagged EC Type 2 OAM Frame

S-VID PCP DE

I

TPID = 88-a8

11

S-Tagged EC Type 2 implications in PB, PBB I, PBB-TE, EOTN networks

New UNI-N port is to be specified to support this format Today’s NID devices do not support MAC-in-MAC encapsulation Next gen NID device can include this MAC-in-MAC encapsulation

format with S-Tagged EC

NNI ports with EC awareness can support this format NNI ports: CNP, PNP, PIP, ONP

NNI ports can treat the EC Type 1 and EC Type 2 signals as a single EC signal type; this behaviour is consistent with NNI requirement to be agnostic to the type of client encapsulation

12

I+S-Tagged EC Type 2 implications in PB, PBB I, PBB-TE, EOTN networks

UNI-N and NNI ports need to distinguish between EC Type 1 and EC Type 2 signals; EC Type 1 and 2 signals require different tagging

Tag type to be administered on a per S-VID (EC) basis Violates requirement that NNI is agnostic to client mapping EC Type 1 MEP/MIP will not be able to detect EC Type 2 OAM EC Type 2 MEP/MIP will not be able to detect EC Type 1 OAM

New UNI-N port is to be specified to support this format Today’s NID devices do not support MAC-in-MAC encapsulation Next gen NID device can include this MAC-in-MAC encapsulation

format with I+S-Tagged EC

NNI ports with EC awareness do not support this format CNP, PNP, PIP, ONP need to be extended with I+S-tagging

capability, configurable on a per S-VID basis