1. HUAWEI TECHNOLOGIES CO., LTD. Page 1 25 March 2009 Peer Interworking Ethernet and PDH service cases Maarten Vissers

2. Page 2 Introduction Two most deployed services are  Ethernet services E-LINE, E-TREE and E-LAN  PDH circuit emulation services  Two IWF specifications available  MEF8 for PDH over Ethernet  RFC4553 for PDH over MPLS Do we need peer-interworking functions for those services?  For the case of MPLS-TP deploying EVC as generic transport service layer  For the case of MPLS-TP deploying EVC as mp2mp/rmp transport service layer and MPLS-TP VC (MS-PW) as p2p/p2mp transport service layer

3. HUAWEI TECHNOLOGIES CO., LTD. Page 3 25 March 2009 MPLS-TP deploys -EVC as generic transport service layer (p2p/p2mp and mp2mp/rmp)

4. Page 4 E-LINE, E-TREE, E-LAN services MPLS-TP deploys EVC as generic transport service layer IWF (TAG) EVC Ethernet VP Ethernet VS PHY EVC MPLS-TP VP (LSP) Ethernet VS PHY EVC MPLS VP (LSP) PHY Application Services layers IWF (TAG) UNI No peer-interworking function necessary for E-LINE & E-TREE & E-LAN services. Ethernet, MPLS-TP and IP/MPLS deploy EVC as their transport service layer for Ethernet services. Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) IP/MPLS IWF (TAG) UNI

5. Page 5 Ethernet and MPLS-TP no peer-interworking function necessary for PDH CES services; both deploy EVC Ethernet and IP/MPLS: MEF8<>RFC4553 & EVC OAM<>VCCV OAM peer-interworking function required for PDH CES services; IP/MPLS does not have a transport service layer MPLS-TP and IP/MPLS: MEF8<>RFC4553 & EVC OAM<>VCCV OAM peer-interworking function required for PDH CES services; IP/MPLS does not have a transport service layer PDH-CES services MPLS-TP deploys EVC as generic transport service layer IWF (MEF8) EVC Ethernet VP Ethernet VS PHY EVC MPLS-TP VP (LSP) Ethernet VS PHY MPLS VP (LSP) PHY Application Services layers IWF (MEF8) UNI Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) IP/MPLS IWF (RFC4553) IWF #2 MEF8 <> RFC4553 IWF #1 MEF8 <> RFC4553 UNI

6. Page 6 Ethernet (MEN, CEN) IP/MPLS MEF8<>RFC4553 IWF #1 IWF #1 MEF8 <> RFC4553 EVC MAC Service Data Unit (client) TPID SA DA PCP DEI EVP VID>0 TYPE PCP DEI EVC VID>0 TPID TYPE 88-d8 TS SSRC TDM data ECID (fixed to zero)0001 0000 0010 LENLM Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number PW Label >15TC1TTL LSP Label >15TC0TTL TYPE (MPLS) SA DA TS SSRC TDM data LENL RES Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number IWF (MEF8) IWF (RFC4553) 802.3 Ethernet domain data frame format IP/MPLS domain data frame format RFC4553 does not support bundling of TDM signals behind one PW; therefore MEF8 bundling capability (reflected in ECID) can not be used and ECID must be fixed to zero.

7. Page 7 EVC (PW) Label >15TC1TTL MVP (LSP) Label >15TC0TTL 0000Seq Number = all-0’s Reserved = all-0’s TYPE (MPLS) SA DA SA DA SA MPLS-TP (MEN, CEN) IP/MPLS MEF8<>RFC4553 IWF #2 IWF #2 MEF8 <> RFC4553 PW Label >15TC1TTL LSP Label >15TC0TTL TYPE (MPLS) SA DA TS SSRC TDM data LENL RES Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number IWF (MEF8) IWF (RFC4553) 802.3 MPLS-TP domain data frame format (case of MPLS-TP with EVC layer) IP/MPLS domain data frame format TS SSRC TDM data LENL RES Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number TYPE 88-d8 TS SSRC RFC4553 does not support bundling of TDM signals behind one PW; therefore MEF8 bundling capability (reflected in ECID) can not be used and ECID must be fixed to zero.

8. HUAWEI TECHNOLOGIES CO., LTD. Page 8 25 March 2009 MPLS-TP deploys -EVC as mp2mp/rmp transport service layer and -MPLS-TP VC (MS-PW) as p2p/p2mp transport service layer

9. Page 9 rmp E-TREE, E-LAN services MPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer IWF (TAG) EVC Ethernet VP Ethernet VS PHY EVC MPLS-TP VP (LSP) Ethernet VS PHY EVC MPLS VP (LSP) PHY Application Services layers IWF (TAG) UNI No peer-interworking function necessary for rmp E-TREE & E-LAN services. Ethernet, MPLS-TP and IP/MPLS deploy EVC as their mp2mp/rmp transport service layer for Ethernet services. Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) IP/MPLS IWF (TAG) UNI

10. Page 10 Ethernet and MPLS-TP EVC<>MVC peer-interworking function necessary for E-LINE & p2mp E-TREE services due to the use of different transport service layer technologies Ethernet and IP/MPLS: no peer-interworking function required for E-LINE & p2mp E-TREE services MPLS-TP and IP/MPLS: EVC<>MVC peer-interworking function required for E-LINE & p2mp E-TREE services due to use of different transport service layer technologies E-LINE, p2mp E-TREE services MPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer IWF (TAG) EVC Ethernet VP Ethernet VS PHY MPLS-TP VC (MS-PW) MPLS-TP VP (LSP) Ethernet VS PHY EVC MPLS VP (LSP) PHY Application Services layers IWF (TAG, CW) UNI Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) IP/MPLS IWF (TAG) UNI IWF #4 MVC <> EVC IWF #3 EVC <> MVC UNI

11. Page 11 Ethernet and MPLS-TP MEF8<>RFC4553 & EVC OAM<>MVC OAM peer-interworking function necessary for PDH CES services due to use of different transport service layer technologies Ethernet and IP/MPLS: MEF8<>RFC4553 & EVC OAM<>VCCV OAM peer-interworking function required for PDH CES services; IP/MPLS does not have a transport service layer MPLS-TP and IP/MPLS: SSPW<>MSPW (OAM) & MVC OAM<>VCCV OAM peer-interworking function required for PDH CES services; IP/MPLS does not have a transport service layer PDH-CES services MPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer IWF (MEF8) EVC Ethernet VP Ethernet VS PHY MPLS-TP VC (MS-PW) MPLS-TP VP (LSP) Ethernet VS PHY MPLS VP (LSP) PHY Application Services layers IWF (RFC4553) UNI Ethernet (MEN, CEN) MPLS-TP IP/MPLS IWF (RFC4553) IWF #6 SSPW <> MSPW IWF #1 MEF8 <> RFC4553 UNI IWF #5 MEF8 <> RFC4553

12. Page 12 MEF8<>RFC4553 IWF #5 IWF #5 MEF8 <> RFC4553 & EVC <> MVC OAM EVC MAC Service Data Unit (client) TPID SA DA PCP DEI EVP VID>0 TYPE PCP DEI EVC VID>0 TPID TYPE 88-d8 TS SSRC TDM data ECID (fixed to zero)0001 0000 0010 LENLM Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number MVC (PW) Label >15TC1TTL MVP (LSP) Label >15TC0TTL TYPE (MPLS) SA DA TS SSRC TDM data LENL RES Sequence Number 0000R FRG CC=0 P=0 PT X=0 V=2 M=0 Sequence Number IWF (MEF8) IWF (RFC4553) 802.3 Ethernet domain data frame format MPLS-TP domain data frame format (case of MPLS-TP with MVC layer) UNI E1/DS1 Ethernet (MEN, CEN) MPLS-TP

13. Page 13 EVC OAM<>MVC OAM IWF #5 IWF #5 MEF8 <> RFC4553 & EVC <> MVC OAM TPID SA DA PCP DEI EVP VID>0 PCP DEI EVC VID>0 TPID MVC (PW) Label >15TC1TTL MVP (LSP) Label >15TC0TTL TYPE (MPLS) SA DA IWF (MEF8) IWF (RFC4553) 802.3 EVC OAM frame format MPLS-TP VC OAM frame format (draft-bhh-mpls-tp-oam-y1731 Option 1) UNI E1/DS1 Ethernet (MEN, CEN) MPLS-TP OAM function specific (Y.1731 based) EndTLV OpCodeFlagsTLV Offset 00010000 CT=0x89020000 MELVersion OAM function specific (Y.1731) EndTLV OpCodeFlagsTLV Offset MEL Version TYPE 89-02

14. HUAWEI TECHNOLOGIES CO., LTD. Page 14 25 March 2009 Conclusion

15. Page 15 Conclusion Number of peer-interworking functions is minimized when MPLS-TP deploys EVC layer as generic transport service layer  Peer-interworking only necessary between IP/MPLS and multi- technology (ethernet & mpls-tp) packet transport network for non- Ethernet services  Peer-interworking simplest via “stitching”