1 / 12

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

Common network architectures for PBB, PBB-TE and EOTN networks. Maarten Vissers 2011-05-11. 1. PBB and PBB-TE network EVC(C-VLAN) via EC(S-VLAN). S-VID Translation locations. PEB. UNI. CNP. CNP. CNP. (I)B-BEB. (I)B-BEB. (I)B-BEB. S. S. CEP. PNP. UNI. BC B. BC B. B(I). PIP.

lluvia
Download Presentation

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

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. Common network architectures for PBB, PBB-TE and EOTN networks Maarten Vissers 2011-05-11

  2. 1. PBB and PBB-TE networkEVC(C-VLAN) via EC(S-VLAN) S-VID Translation locations PEB UNI CNP CNP CNP (I)B-BEB (I)B-BEB (I)B-BEB S S CEP PNP UNI BCB BCB B(I) PIP B(I) B(I) I I PNP I-BEB S CBP CBP CBP IB-BEB UNI UNI CNP mp2mp B-VLAN or p2p TESI B(I) mp2mp B-VLAN or p2p TESI UNI CEP CNP CNP IB-BEB (I)B-BEB (I)B-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 single-domain PBBNs) S BCB BCB UNI B(I) B(I) B(I) I CNP CBP CBP UNI mp2mp B-VLAN or p2p TESI

  3. 2. PBB networkEVC(S-VLAN) via EC(BSI) PEB UNI CNP CNP CNP (I)B-BEB (I)B-BEB (I)B-BEB S S CEP PNP UNI BCB BCB PIP B(I) B(I) B(I) I I PNP I-BEB S CBP CBP CBP IB-BEB UNI UNI CNP mp2mp B-VLAN B(I) mp2mp B-VLAN UNI CEP CNP CNP IB-BEB (I)B-BEB (I)B-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) S BCB BCB UNI B(I) B(I) B(I) I CNP CBP CBP UNI mp2mp B-VLAN I-SID Translation locations

  4. 3. PBB networkEVC(C-VLAN) via EC1(S-VLAN) over EC2(BSI) S-VID Translation location PEB UNI CNP CNP CNP (I)B-BEB (I)B-BEB (I)B-BEB S S CEP PNP UNI BCB BCB PIP B(I) B(I) B(I) I I PNP I-BEB S CBP CBP CBP IB-BEB UNI UNI CNP B-VLAN B(I) B-VLAN UNI CEP CNP CNP IB-BEB (I)B-BEB (I)B-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) S BCB BCB UNI B(I) B(I) B(I) I CNP CBP CBP UNI B-VLAN I-SID Translation locations

  5. 4. EOTN networkEVC(C-VLAN) via EC(S-VLAN) S-VID Translation locations PEB UNI PNP T(E)B TB S CEP PNP UNI OXC OXC PNP ONP ONP S IB-BEB PIP S S S I I-BEB UNI ??? p2p ODUk UNI CNP p2p ODUk S • 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) UNI CEP TEB TB OXC OXC ONP ONP UNI S S S CNP UNI p2p ODUk

  6. EC frame tagging in PB, PBB, PBB-TE, EOTN 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. EC awareness in PB, PBB, PBB-TE, EOTN

  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 B-DA B-SA Type = 89-10 C-DA C-DA C-SA C-SA Type MSDU Type MSDU Untagged EC Type 2 Frame(= untagged BSI Frame) EVC Frame B-DA B-SA Type = 89-02 OAM PDU Untagged EC Type 2 OAM Frame

  10. Tagged EC Type 2 frame format alternatives B-DA B-SA B-DA TPID = 88-a8 B-DA • There are three EC Type 2 frame tagging alternatives • I-Tagging • S-Tagging • I+S-Tagging B-SA PCP DEI S-VID B-SA TPID = 88-E7 TPID = 88-E7 TPID = 88-a8 PCP DEI 0 Res1 Res2 I-SID PCP DEI 0 Res1 Res2 I-SID PCP DEI S-VID I-SID Type = 89-10 I-SID = S-VID + 4096 C-DA C-DA C-DA C-SA C-SA C-SA Type Type Type MSDU MSDU MSDU I-Tagged EC Type 2 Frame I+S-Tagged EC Type 2 Frame S-Tagged EC Type 2 Frame B-DA = f(B-DA,DBD) B-SA B-DA = f(B-DA,DBD) TPID = 88-a8 B-SA PCP DEI S-VID TPID = 88-E7 TPID = 88-E7 PCP DEI 0 Res1 Res2 I-SID PCP DEI 0 Res1 Res2 I-SID B-DA I-SID = f(ETH_FP) I-SID = S-VID + 4096 B-SA C-DA = B-DA C-DA = B-DA TPID = 88-a8 C-SA = B-SA C-SA = B-SA PCP DEI S-VID Type = 89-02 Type = 89-02 Type = 89-02 OAM PDU OAM PDU OAM PDU S-Tagged EC Type 2 OAM Frame I-Tagged EC Type 2 OAM Frame I+S-Tagged EC Type 2 OAM Frame

  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

More Related