1 / 15

Peer Interworking Ethernet and PDH service cases

Peer Interworking Ethernet and PDH service cases. Maarten Vissers. 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

wyatt
Download Presentation

Peer Interworking Ethernet and PDH service cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Peer InterworkingEthernet and PDH service cases Maarten Vissers

  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. MPLS-TP deploys - EVC as generic transport service layer (p2p/p2mp and mp2mp/rmp)

  4. E-LINE, E-TREE, E-LAN servicesMPLS-TP deploys EVC as generic transport service layer UNI UNI UNI Application Services layers IWF(TAG) IWF(TAG) IWF (TAG) Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) EVC EVC Ethernet VP MPLS-TP VP (LSP) Ethernet VS Ethernet VS IP/MPLS PHY PHY EVC MPLS VP (LSP) UNI PHY 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.

  5. PDH-CES servicesMPLS-TP deploys EVC as generic transport service layer UNI UNI UNI Application Services layers IWF(MEF8) IWF(RFC4553) IWF (MEF8) Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) EVC EVC Ethernet VP MPLS-TP VP (LSP) IWF #2 MEF8 <> RFC4553 IWF #1MEF8 <> RFC4553 Ethernet VS Ethernet VS IP/MPLS PHY PHY MPLS VP (LSP) PHY • 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

  6. MEF8<>RFC4553 IWF #1 IP/MPLS Ethernet (MEN, CEN) IWF(MEF8) IWF (RFC4553) IWF #1MEF8 <> RFC4553 802.3 802.3 IP/MPLS domain data frame format Ethernet domain data frame format DA DA DA DA SA SA TPID SA TYPE (MPLS) SA EVP VID>0 TPID PCP DEI LSP Label >15 TC 0 TTL EVC VID>0 TYPE PCP DEI EVC MAC Service Data Unit (client) TYPE 88-d8 PW Label >15 TC 1 TTL ECID (fixed to zero) 0001 0000 0010 0000 L R RES FRG LEN Sequence Number 0000 L R M FRG LEN Sequence Number V=2 P=0 X=0 CC=0 M=0 PT Sequence Number V=2 P=0 X=0 CC=0 M=0 PT Sequence Number TS TS SSRC SSRC TDM data TDM data 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. MEF8<>RFC4553 IWF #2 IP/MPLS MPLS-TP (MEN, CEN) IWF(MEF8) IWF (RFC4553) IWF #2MEF8 <> RFC4553 802.3 802.3 MPLS-TP domain data frame format (case of MPLS-TP with EVC layer) IP/MPLS domain data frame format DA DA DA DA SA SA TYPE (MPLS) SA TYPE (MPLS) SA LSP Label >15 TC 0 TTL MVP (LSP) Label >15 TC 0 TTL PW Label >15 TC 1 TTL EVC (PW) Label >15 TC 1 TTL 0000 L R RES FRG LEN Sequence Number 0000 Seq Number = all-0’s Reserved = all-0’s V=2 P=0 X=0 CC=0 M=0 PT Sequence Number DA TS DA SA SSRC SA TYPE 88-d8 0000 L R RES FRG LEN TDM data Sequence Number V=2 P=0 X=0 CC=0 M=0 PT Sequence Number TS 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. SSRC TS SSRC TDM data SSRC

  8. MPLS-TP deploys - EVC as mp2mp/rmp transport service layer and - MPLS-TP VC (MS-PW) as p2p/p2mp transport service layer

  9. rmp E-TREE, E-LAN servicesMPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer UNI UNI UNI Application Services layers IWF(TAG) IWF(TAG) IWF (TAG) Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) EVC EVC Ethernet VP MPLS-TP VP (LSP) Ethernet VS Ethernet VS IP/MPLS PHY PHY EVC MPLS VP (LSP) UNI PHY 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.

  10. E-LINE, p2mp E-TREE servicesMPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer UNI UNI UNI Application Services layers IWF(TAG) IWF(TAG) IWF (TAG, CW) Ethernet (MEN, CEN) MPLS-TP (MEN, CEN) IWF #3 EVC <> MVC EVC MPLS-TP VC (MS-PW) Ethernet VP MPLS-TP VP (LSP) IWF #4 MVC <> EVC Ethernet VS Ethernet VS IP/MPLS PHY PHY EVC MPLS VP (LSP) UNI PHY • 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

  11. PDH-CES servicesMPLS-TP deploys EVC as mp2mp/rmp transport service layer and MVC as p2p/p2mp transport service layer UNI UNI UNI Application Services layers IWF(MEF8) IWF(RFC4553) IWF (RFC4553) Ethernet (MEN, CEN) MPLS-TP IWF #5MEF8 <> RFC4553 EVC MPLS-TP VC (MS-PW) Ethernet VP MPLS-TP VP (LSP) IWF #6 SSPW <> MSPW IWF #1MEF8 <> RFC4553 Ethernet VS Ethernet VS IP/MPLS PHY PHY MPLS VP (LSP) PHY • 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

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

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

  14. Conclusion

  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”

More Related