Common network architectures for PBB, PBB

Report
Common network architectures for PBB,
PBB-TE and EOTN networks
version 01
Maarten Vissers
2011-05-12
v01 includes new slides 10 and 12:
Slide 10 presents the information in slide 9 in the form of 802.1Q primitive parameters.
Slide 12 presents the information in slide 11 in the form of 802.1Q primitive parameters.
1
1. PBB and PBB-TE network
EVC(C-VLAN) via EC(S-VLAN)
S-VID Translation locations
CBP
I
CBP
CBP
mp2mp B-VLAN
or p2p TESI
CNP
UNI CEP
UNI CNP
B(I)
I
CBP
B(I)
CNP
S
(I)B-BEB
B(I)
BCB
UNI
CNP
IB-BEB
• 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 singledomain PBBNs)
BCB
B(I)
mp2mp B-VLAN
or p2p TESI
UNI
B(I)
B(I)
B(I)
BCB
I
S
(I)B-BEB
PIP
CNP
(I)B-BEB
S
BCB
S
I-BEB
UNI
IB-BEB
PNP
PNP
CNP
(I)B-BEB
UNI CEP
CNP
(I)B-BEB
PEB
UNI
CBP
mp2mp B-VLAN
or p2p TESI
2
2. PBB network
EVC(S-VLAN) via EC(BSI)
UNI
B(I)
CBP
I
CBP
CBP
mp2mp B-VLAN
CNP
B(I)
UNI CNP
CNP
S
(I)B-BEB
B(I)
BCB
UNI
CNP
I
CBP
(I)B-BEB
UNI CEP
IB-BEB
• 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)
B(I)
BCB
B(I)
B(I)
B(I)
BCB
I
I-BEB
PIP
S
(I)B-BEB
S
BCB
S
CNP
mp2mp B-VLAN
UNI
IB-BEB
PNP
PNP
CNP
(I)B-BEB
UNI CEP
CNP
(I)B-BEB
PEB
UNI
CBP
mp2mp B-VLAN
I-SID Translation locations
3
3. PBB network
EVC(C-VLAN) via EC1(S-VLAN) over EC2(BSI)
S-VID Translation location
UNI
B(I)
B(I)
CBP
I
CBP
CBP
B-VLAN
B-VLAN
CNP
UNI CNP
B(I)
I
CBP
B(I)
CNP
S
(I)B-BEB
B(I)
BCB
UNI
CNP
(I)B-BEB
UNI CEP
IB-BEB
• 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(I)
BCB
I
S
B(I)
BCB
PIP
CNP
(I)B-BEB
S
BCB
S
I-BEB
UNI
IB-BEB
PNP
PNP
CNP
(I)B-BEB
UNI CEP
CNP
(I)B-BEB
PEB
UNI
CBP
B-VLAN
I-SID Translation locations
4
4. EOTN network
EVC(C-VLAN) via EC(S-VLAN)
S-VID Translation locations
PEB
I
S
S
???
p2p ODUk
p2p ODUk
UNI
S
CNP
S
S
ONP
S
TB
UNI
OXC
UNI CEP
TEB
• 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
S
OXC
PIP
ONP
OXC
S
TB
S
I-BEB
UNI
IB-BEB
PNP
PNP
T(E)B
UNI CEP
PNP
OXC
UNI
UNI CNP
p2p ODUk
5
EC frame tagging in PB, PBB, PBB-TE, EOTN
Network
PB + PBB I
(PEB, PB, IB-BEB,
BCB only)
PB + PBB II
(PEB, PB, IB-BEB,
TB-BEB, I-BEB, BBEB, BCB)
PB + PBB-TE
(PEB, PB, IB-BEB,
BCB)
EOTN
(TEB,TB, OTN XC)
EC type 1 frame tag
EC type 2 frame tag
S-Tag
To be defined
Note: in B-VLAN an I-Tag or S+I-Tag is used
S-Tag
I-Tag
Note: Inside PBB network the EC frames are
carried inside a 2nd EC frame, which is I-Tagged
S-Tag
To be defined
Note: in ESP an I-Tag or S+I-Tag is used
S-Tag
To be defined
EC Type 1: EC carrying an EVC which is not-MAC-in-MAC encapsulated
EC Type 2: EC carrying an EVC which is MAC-in-MAC encapsulated
6
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)
PEP
CNP
CNP
PIP
PNP
CNP
PIP
PNP
CNP
PIP
PNP
PB + PBB II
(PEB, PB, IB-BEB,
TB-BEB, I-BEB, BBEB, BCB)
PEP
CNP
PIP
CBP
CNP
PIP
CBP
PNP
CNP
PIP
CBP
PNP
CNP
PIP
CBP
PNP
PB + PBB-TE
(PEB, PB, IB-BEB,
BCB)
CEP
CNP
CNP
PIP
PNP
CNP
PIP
PNP
CNP
PIP
PNP
EOTN
(TEB,TB, OTN XC)
CEP
CNP
CNP
PNP
ONP
PNP
ONP
PNP
ONP
7
Analysis of EC Type 2 Tagging options
For deployment in PB+PBB I, PB+PBB-TE and EOTN
8
Untagged EC Type 2 frame format
B-DA
B-SA
Type = 89-10
C-DA
C-DA
C-SA
Type
C-SA
Type
MSDU
MSDU
EVC Frame
Untagged EC Type 2 Frame
(= untagged BSI Frame)
B-DA
B-SA
Type = 89-02
OAM PDU
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
Untagged EC Type 2 OAM Frame
9
Slide 9 in 802.1Q primitive format
EVC primitive parameters
- destination_address (=C-DA)
- source_address (=C-SA)
- mac_service_data_unit =
EC Type 2 primitive parameters
- destination_address (=B-DA)
-source_address (=B-SA)
- mac_service_data_unit =
Type = 89-10
C-DA
Type
C-SA
Type
MSDU
MSDU
EC Type 2 OAM primitive parameters
- destination_address (=B-DA)
- source_address (=B-SA)
- mac_service_data_unit =
Type = 89-02
OAM PDU
The “frame” formats presented in
slide 9 represent the ETH_AI_D
and ETH_CI_D information on
ETH_AP, ETH_TFP and ETH_FP
reference points within ITU-T’s
Ethernet functional model.
The 802.1Q equivalent information
are the primitive parameters
mac_service_data_unit,
source_address and
destination_address as illustrated
on the left.
Note: The ETH_xI_D (x = A,C) is
complemented by e.g. ETH_xI_P
(priority parameter), ETH_xI_DE
(drop_eligible parameter),
ETH_AI_TSF, ETH_AI_TSD,
ETH_CI_SSF (no equivalent
primitive parameters in 802.1Q)
10
Tagged EC Type 2 frame format alternatives
B-DA
B-SA
TPID = 88-E7
B-SA
I-SID
S-VID
TPID = 88-E7
PCP
S-VID
DEI
Res2
PCP
TPID = 88-a8
DEI
0
TPID = 88-a8
PCP
Res1
B-DA
DEI
B-DA
Res1
PCP
DEI
B-SA
0
Res2
I-SID
I-SID
Type = 89-10
C-DA
C-DA
I-SID = S-VID + 4096
C-DA
C-SA
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
I-Tagged EC Type 2
Frame
S-Tagged EC Type 2
Frame
I+S-Tagged EC Type 2
Frame
There are three
EC Type 2
frame tagging
alternatives
1. I-Tagging
2. S-Tagging
3. I+S-Tagging
B-DA = f(B-DA,DBD)
B-SA
B-DA = f(B-DA,DBD)
I-SID
B-DA
PCP
S-VID
TPID = 88-E7
0
Res1
Res2
PCP
DEI
0
Res1
PCP
DEI
B-SA
TPID = 88-E7
DEI
TPID = 88-a8
Res2
I-SID
B-SA
I-SID = S-VID + 4096
C-DA = B-DA
TPID = 88-a8
C-DA = B-DA
S-VID
Type = 89-02
C-SA = B-SA
Type = 89-02
OAM PDU
OAM PDU
OAM PDU
I-Tagged EC Type 2
OAM Frame
S-Tagged EC Type 2
OAM Frame
I+S-Tagged EC Type 2
OAM Frame
C-SA = B-SA
Type = 89-02
PCP
DEI
I-SID = f(ETH_FP)
11
Slide 11 in 802.1Q primitive format
DEI
I+S-Tagged EC Type 2
primitive parameters
I-Tagged EC Type 2
S-Tagged EC Type 2
- destination_address (=B-DA)
primitive parameters
primitive parameters
-source_address (=B-SA)
- destination_address (=B-DA) - destination_address (=B-DA) - mac_service_data_unit =
-source_address (=B-SA)
-source_address (=B-SA)
TPID = 88-a8
- mac_service_data_unit =
- mac_service_data_unit =
The “frame” formats
PCP
S-VID
S-VID
PCP
0
Res2
I-SID
I-SID
Type = 89-10
C-DA
C-DA
I-SID = S-VID + 4096
C-DA
C-SA
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
I-Tagged EC Type 2
OAM primitive parameters
- destination_address
(=f(C-DA,DBD))
-source_address (=C-SA)
- mac_service_data_unit =
I+S-Tagged EC Type 2
OAM primitive parameters
- destination_address
(=f(C-DA,DBD)
-source_address (=C-SA)
- mac_service_data_unit =
C-DA = B-DA
TPID = 88-a8
C-DA = B-DA
S-VID
Type = 89-02
C-SA = B-SA
Type = 89-02
OAM PDU
OAM PDU
C-SA = B-SA
Type = 89-02
OAM PDU
PCP
PCP
S-VID
TPID = 88-E7
0
Res1
I-SID
PCP
DEI
Res2
TPID = 88-a8
DEI
Res1
DEI
0
DEI
I-SID = f(ETH_FP)
S-Tagged EC Type 2
OAM primitive parameters
- destination_address (=B-DA)
-source_address (=B-SA)
- mac_service_data_unit =
TPID = 88-E7
PCP
PCP
Res1
I-SID
DEI
Res2
TPID = 88-E7
TPID = 88-a8
DEI
0
Res1
PCP
DEI
TPID = 88-E7
Res2
presented in slide 11
represent the ETH_AI_D
information on a server
layer ETH_AP reference
points within ITU-T’s
Ethernet functional
model.
The 802.1Q equivalent
information are the
primitive parameters
mac_service_data_unit,
source_address and
destination_address as
illustrated on the left.
I-SID
I-SID = S-VID + 4096
12
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
13
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
14

similar documents