1. 1 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.

2. 2 1. PBB and PBB-TE network EVC(C-VLAN) via EC(S-VLAN) IB-BEB UNI PNP S mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI 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. 3 2. PBB network EVC(S-VLAN) via EC(BSI) IB-BEB 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 I-SID Translation locations

4. 4 3. PBB network EVC(C-VLAN) via EC1(S-VLAN) over EC2(BSI) IB-BEB 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 I-SID Translation locations S-VID Translation location

5. 5 4. EOTN network EVC(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 p2p ODUk S-VID Translation locations

6. 6 EC frame tagging in PB, PBB, PBB-TE, EOTN NetworkEC type 1 frame tagEC 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 2 nd 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-TagTo 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

7. 7 EC awareness in PB, PBB, PBB-TE, EOTN NetworkEVC-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 PIP PNP CNP PIP PNP CNP PIP PNP PB + PBB II (PEB, PB, IB-BEB, TB-BEB, I-BEB, B- BEB, 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 PIP PNP CNP PIP PNP CNP PIP PNP EOTN (TEB,TB, OTN XC) CEP CNP PNP ONP PNP ONP PNP ONP

8. 8 Analysis of EC Type 2 Tagging options For deployment in PB+PBB I, PB+PBB-TE and EOTN

9. 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. 10 Slide 9 in 802.1Q primitive format 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) MSDU Type 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 = C-DA C-SA MSDU Type = 89-10 Type EC Type 2 OAM primitive parameters - destination_address (=B-DA) - source_address (=B-SA) - mac_service_data_unit = OAM PDU Type = 89-02

11. 11 Tagged EC Type 2 frame format alternatives There are three EC Type 2 frame tagging alternatives 1.I-Tagging 2.S-Tagging 3.I+S-Tagging TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 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-VIDPCP DEI TPID = 88-a8 B-DA B-SA C-DA C-SA MSDU Type I+S-Tagged EC Type 2 Frame S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = S-VID + 4096 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 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-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 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-VIDPCP DEI TPID = 88-a8

12. 12 Slide 11 in 802.1Q primitive format The “frame” formats 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. TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID C-DA C-SA MSDU Type C-DA C-SA MSDU Type Type = 89-10 S-VIDPCP DEI TPID = 88-a8 C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = S-VID + 4096 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = f(ETH_FP) C-DA = B-DA C-SA = B-SA OAM PDU Type = 89-02 OAM PDU Type = 89-02 S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = S-VID + 4096 C-DA = B-DA C-SA = B-SA OAM PDU Type = 89-02 S-VIDPCP DEI TPID = 88-a8 I-Tagged EC Type 2 primitive parameters - destination_address (=B-DA) -source_address (=B-SA) - mac_service_data_unit = S-Tagged EC Type 2 primitive parameters - destination_address (=B-DA) -source_address (=B-SA) - mac_service_data_unit = I+S-Tagged EC Type 2 primitive parameters - destination_address (=B-DA) -source_address (=B-SA) - mac_service_data_unit = I-Tagged EC Type 2 OAM primitive parameters - destination_address (=f(C-DA,DBD)) -source_address (=C-SA) - mac_service_data_unit = S-Tagged EC Type 2 OAM primitive parameters - destination_address (=B-DA) -source_address (=B-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 =

13. 13 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

14. 14 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